WO2024031395A1 - 重复传输方法、终端设备和网络设备 - Google Patents
重复传输方法、终端设备和网络设备 Download PDFInfo
- Publication number
- WO2024031395A1 WO2024031395A1 PCT/CN2022/111286 CN2022111286W WO2024031395A1 WO 2024031395 A1 WO2024031395 A1 WO 2024031395A1 CN 2022111286 W CN2022111286 W CN 2022111286W WO 2024031395 A1 WO2024031395 A1 WO 2024031395A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- downlink data
- equal
- repeated transmissions
- information
- network device
- Prior art date
Links
- 230000005540 biological transmission Effects 0.000 title claims abstract description 373
- 238000000034 method Methods 0.000 title claims abstract description 143
- 238000012545 processing Methods 0.000 claims abstract description 62
- 238000004891 communication Methods 0.000 claims description 53
- 230000015654 memory Effects 0.000 claims description 38
- 238000012790 confirmation Methods 0.000 claims description 35
- 238000004590 computer program Methods 0.000 claims description 27
- 230000011664 signaling Effects 0.000 claims description 14
- 238000010586 diagram Methods 0.000 description 20
- 230000006870 function Effects 0.000 description 17
- 230000008569 process Effects 0.000 description 16
- 238000001228 spectrum Methods 0.000 description 13
- 230000007774 longterm Effects 0.000 description 9
- 238000005516 engineering process Methods 0.000 description 8
- 101150051118 PTM1 gene Proteins 0.000 description 5
- 238000013461 design Methods 0.000 description 5
- 230000001360 synchronised effect Effects 0.000 description 5
- 101150071746 Pbsn gene Proteins 0.000 description 3
- 230000002776 aggregation Effects 0.000 description 3
- 238000004220 aggregation Methods 0.000 description 3
- 125000004122 cyclic group Chemical group 0.000 description 3
- 238000007726 management method Methods 0.000 description 3
- 238000010295 mobile communication Methods 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 230000003190 augmentative effect Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 2
- 230000008859 change Effects 0.000 description 2
- 230000009977 dual effect Effects 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- 238000012546 transfer Methods 0.000 description 2
- 239000002699 waste material Substances 0.000 description 2
- XLYOFNOQVPJJNP-UHFFFAOYSA-N water Substances O XLYOFNOQVPJJNP-UHFFFAOYSA-N 0.000 description 2
- VZSRBBMJRBPUNF-UHFFFAOYSA-N 2-(2,3-dihydro-1H-inden-2-ylamino)-N-[3-oxo-3-(2,4,6,7-tetrahydrotriazolo[4,5-c]pyridin-5-yl)propyl]pyrimidine-5-carboxamide Chemical compound C1C(CC2=CC=CC=C12)NC1=NC=C(C=N1)C(=O)NCCC(N1CC2=C(CC1)NN=N2)=O VZSRBBMJRBPUNF-UHFFFAOYSA-N 0.000 description 1
- 230000006399 behavior Effects 0.000 description 1
- 230000008901 benefit Effects 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 239000003795 chemical substances by application Substances 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000008713 feedback mechanism Effects 0.000 description 1
- 239000011521 glass Substances 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000008450 motivation Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 230000008520 organization Effects 0.000 description 1
- 238000011160 research Methods 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 239000004984 smart glass Substances 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 238000001356 surgical procedure Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
Definitions
- the present application relates to the field of communications, and more specifically, to a repeated transmission method, terminal equipment and network equipment.
- repeated transmission may be required.
- MBS Multimedia Broadcast Multicast Services
- MBS Multicast Broadcast Service
- repeated transmissions are performed according to the number of repeated transmissions for a long period of time before the signaling is updated, which may easily cause a waste of transmission resources.
- Embodiments of the present application provide a repeated transmission method, terminal equipment, and network equipment.
- Embodiments of the present application provide a repeated transmission method, which includes: a terminal device performing subsequent repeated transmission related processing according to the first number of repeated transmissions of downlink data and the transmission status of the downlink data.
- Embodiments of the present application provide a repeated transmission method, which includes: the network device performs subsequent repeated transmission related processing according to the first number of repeated transmissions of downlink data and the feedback status of the downlink data.
- Embodiments of the present application provide a terminal device, including: a processing unit configured to perform subsequent repeated transmission related processing according to the first number of repeated transmissions of downlink data and the transmission status of the downlink data.
- An embodiment of the present application provides a network device, including: a processing unit configured to perform subsequent repeated transmission related processing based on the first number of repeated transmissions of downlink data and the feedback status of the downlink data.
- An embodiment of the present application provides a terminal device, including a processor and a memory.
- the memory is used to store computer programs, and the processor is used to call and run the computer program stored in the memory, so that the terminal device performs the above-mentioned repeated transmission method.
- An embodiment of the present application provides a network device, including a processor and a memory.
- the memory is used to store computer programs
- the processor is used to call and run the computer programs stored in the memory, so that the network device performs the above-mentioned repeated transmission method.
- An embodiment of the present application provides a chip for implementing the above repeated transmission method.
- the chip includes: a processor for calling and running a computer program from the memory, so that the device installed with the chip performs the above-mentioned repeated transmission method.
- Embodiments of the present application provide a computer-readable storage medium for storing a computer program.
- the computer program When the computer program is run by a device, it causes the device to perform the above repeated transmission method.
- An embodiment of the present application provides a computer program product, including computer program instructions, which cause a computer to execute the above repeated transmission method.
- An embodiment of the present application provides a computer program that, when run on a computer, causes the computer to perform the above repeated transmission method.
- Figure 1 is a schematic diagram of an application scenario according to an embodiment of the present application.
- FIGS 2a to 2c are schematic diagrams of examples of BWP.
- FIG. 3 is a schematic diagram of SC-PTM according to an embodiment of the present application.
- Figures 4a to 4c are schematic diagrams of NR MBS scheduling methods according to embodiments of the present application.
- Figure 5 is a schematic flow chart of a repeated transmission method according to an embodiment of the present application.
- Figure 6 is a schematic flow chart of a repeated transmission method according to another embodiment of the present application.
- Figure 7 is a schematic flow chart of a repeated transmission method according to another embodiment of the present application.
- Figure 8 is a schematic flow chart of a repeated transmission method according to an embodiment of the present application.
- Figure 9 is a schematic flow chart of a repeated transmission method according to another embodiment of the present application.
- Figure 10 is a schematic flow chart of a repeated transmission method according to another embodiment of the present application.
- Figure 11 is a schematic block diagram of a terminal device according to an embodiment of the present application.
- Figure 12 is a schematic block diagram of a terminal device according to another embodiment of the present application.
- Figure 13 is a schematic block diagram of a network device according to an embodiment of the present application.
- Figure 14 is a schematic block diagram of a network device according to another embodiment of the present application.
- Figure 15 is a schematic diagram of configuring an uplink feedback resource PUCCH according to an embodiment of the present application.
- Figure 16 is a schematic diagram of configuring two uplink feedback resources PUCCH according to an embodiment of the present application.
- Figure 17 is a schematic diagram of sending TB1 to a group of UEs through PTM according to an embodiment of the present application.
- Figure 18 is a schematic diagram of TB repeated transmission in SPS according to an embodiment of the present application.
- Figure 19 is a schematic block diagram of a communication device according to an embodiment of the present application.
- Figure 20 is a schematic block diagram of a chip according to an embodiment of the present application.
- Figure 21 is a schematic block diagram of a communication system according to an embodiment of the present application.
- GSM Global System of Mobile communication
- CDMA Code Division Multiple Access
- WCDMA broadband code division multiple access
- GPRS General Packet Radio Service
- LTE Long Term Evolution
- LTE-A Advanced long term evolution
- NR New Radio
- NTN Non-Terrestrial Networks
- UMTS Universal Mobile Telecommunication System
- WLAN Wireless Local Area Networks
- WiFi wireless fidelity
- 5G fifth-generation communication
- the communication system in the embodiment of the present application can be applied to a carrier aggregation (Carrier Aggregation, CA) scenario, a dual connectivity (Dual Connectivity, DC) scenario, or a standalone (Standalone, SA)Network scene.
- Carrier Aggregation, CA Carrier Aggregation, CA
- DC Dual Connectivity
- SA Standalone
- the communication system in the embodiment of the present application can be applied to unlicensed spectrum, where the unlicensed spectrum can also be considered as shared spectrum; or, the communication system in the embodiment of the present application can also be applied to licensed spectrum , among which, licensed spectrum can also be considered as non-shared spectrum.
- the embodiments of this application describe various embodiments in combination with network equipment and terminal equipment.
- the terminal equipment may also be called user equipment (User Equipment, UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent or user device, etc.
- User Equipment User Equipment
- the terminal device can be a station (ST) in the WLAN, a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a wireless local loop (Wireless Local Loop, WLL) station, or a personal digital processing unit.
- ST station
- SIP Session Initiation Protocol
- WLL Wireless Local Loop
- PDA Personal Digital Assistant
- the terminal device can be deployed on land, including indoor or outdoor, handheld, wearable or vehicle-mounted; it can also be deployed on water (such as ships, etc.); it can also be deployed in the air (such as aircraft, balloons and satellites). superior).
- the terminal device may be a mobile phone (Mobile Phone), a tablet computer (Pad), a computer with a wireless transceiver function, a virtual reality (Virtual Reality, VR) terminal device, or an augmented reality (Augmented Reality, AR) terminal.
- Equipment wireless terminal equipment in industrial control, wireless terminal equipment in self-driving, wireless terminal equipment in remote medical, wireless terminal equipment in smart grid , wireless terminal equipment in transportation safety, wireless terminal equipment in smart city, or wireless terminal equipment in smart home, etc.
- the terminal device may also be a wearable device.
- Wearable devices can also be called wearable smart devices. It is a general term for applying wearable technology to intelligently design daily wear and develop wearable devices, such as glasses, gloves, watches, clothing and shoes, etc.
- a wearable device is a portable device that is worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not just hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction.
- wearable smart devices include full-featured, large-sized devices that can achieve complete or partial functions without relying on smartphones, such as smart watches or smart glasses, and those that only focus on a certain type of application function and need to cooperate with other devices such as smartphones.
- the network device may be a device used to communicate with mobile devices.
- the network device may be an access point (Access Point, AP) in WLAN, or a base station (Base Transceiver Station, BTS) in GSM or CDMA.
- BTS Base Transceiver Station
- it can be a base station (NodeB, NB) in WCDMA, or an evolutionary base station (Evolutional Node B, eNB or eNodeB) in LTE, or a relay station or access point, or a vehicle-mounted device, a wearable device, and an NR network network equipment (gNB) or network equipment in the future evolved PLMN network or network equipment in the NTN network, etc.
- AP Access Point
- BTS Base Transceiver Station
- NodeB, NB base station
- Evolutional Node B, eNB or eNodeB evolution base station
- gNB NR network network equipment
- the network device may have mobile characteristics, for example, the network device may be a mobile device.
- the network device can be a satellite or balloon station.
- the satellite can be a low earth orbit (LEO) satellite, a medium earth orbit (MEO) satellite, a geosynchronous orbit (geostationary earth orbit, GEO) satellite, a high elliptical orbit (High Elliptical Orbit, HEO) satellite ) satellite, etc.
- the network device may also be a base station installed on land, water, etc.
- network equipment can provide services for a cell, and terminal equipment communicates with the network equipment through transmission resources (for example, frequency domain resources, or spectrum resources) used by the cell.
- the cell can be a network equipment ( For example, the cell corresponding to the base station), the cell can belong to the macro base station, or it can belong to the base station corresponding to the small cell (Small cell).
- the small cell here can include: urban cell (Metro cell), micro cell (Micro cell), pico cell ( Pico cell), femto cell (Femto cell), etc. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-rate data transmission services.
- Figure 1 illustrates a communication system 100.
- the communication system includes a network device 110 and two terminal devices 120.
- the communication system 100 may include multiple network devices 110 , and the coverage of each network device 110 may include other numbers of terminal devices 120 , which is not limited in this embodiment of the present application.
- the communication system 100 may also include other network entities such as Mobility Management Entity (MME), Access and Mobility Management Function (AMF), etc.
- MME Mobility Management Entity
- AMF Access and Mobility Management Function
- network equipment may include access network equipment and core network equipment. That is, the wireless communication system also includes multiple core networks used to communicate with access network equipment.
- the access network equipment can be a long-term evolution (long-term evolution, LTE) system, a next-generation (mobile communication system) (next radio, NR) system or authorized auxiliary access long-term evolution (LAA- Evolutionary base station (evolutional node B, abbreviated as eNB or e-NodeB) macro base station, micro base station (also known as "small base station"), pico base station, access point (access point, AP), Transmission point (TP) or new generation base station (new generation Node B, gNodeB), etc.
- LTE long-term evolution
- NR next-generation
- LAA- Evolutionary base station evolutional node B, abbreviated as eNB or e-NodeB
- eNB next-generation
- NR next-generation
- LAA- Evolutionary base station evolutional node B, abbre
- the communication equipment may include network equipment and terminal equipment with communication functions.
- the network equipment and terminal equipment may be specific equipment in the embodiments of the present application, which will not be described again here; the communication equipment also It may include other devices in the communication system, such as network controllers, mobility management entities and other network entities, which are not limited in the embodiments of this application.
- the "instruction” mentioned in the embodiments of this application may be a direct instruction, an indirect instruction, or an association relationship.
- a indicates B which can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also mean that there is an association between A and B. relation.
- correlate can mean that there is a direct correspondence or indirect correspondence between the two, it can also mean that there is an associated relationship between the two, or it can mean indicating and being instructed, configuration and being. Configuration and other relationships.
- 5G 3rd Generation Partnership Project
- eMBB enhanced mobile ultra-broadband
- URLLC Ultra Reliability and Low Latency Communication
- mMTC massive machine type communications
- eMBB still aims at users to obtain multimedia content, services and data, and its demand is growing rapidly.
- eMBB may be deployed in different scenarios, such as indoors, urban areas, rural areas, etc., its capabilities and requirements are also quite different, so it cannot be generalized and must be analyzed in detail based on specific deployment scenarios.
- Typical applications of URLLC include: industrial automation, power automation, telemedicine operations (surgery), traffic safety and security, etc.
- Typical features of mMTC include: high connection density, small data volume, delay-insensitive services, low cost and long service life of the module.
- RRC Radio Resource Control
- RRC_IDLE Mobility is cell selection reselection based on User Equipment (User Equipment, UE). Paging is initiated by the Core Network (Core Network, CN), and the paging area is configured by the CN. There is no UE Access Stratum (AS) context on the base station side. There is no RRC connection.
- UE User Equipment
- CN Core Network
- AS UE Access Stratum
- RRC_CONNECTED There is an RRC connection, and the base station and the UE have a UE AS context. The network side knows the location of the UE at the specific cell level. Mobility is network-side controlled mobility. Unicast data can be transmitted between the UE and the base station.
- RRC_INACTIVE Mobility is UE-based cell selection reselection. There is a connection between CN and New Radio Technology (New Radio, NR). The UE AS context exists on a base station. Paging is performed by the Radio Access Network (Radio Access Network). , RAN) trigger, the RAN-based paging area is managed by the RAN, and the network side knows that the location of the UE is based on the RAN paging area level.
- Radio Access Network Radio Access Network
- RAN Radio Access Network
- the maximum channel bandwidth can be 400MHZ (bandwidth carrier), which is very large compared to the maximum 20M bandwidth of Long Term Evolution (LTE). If the UE keeps working on a wideband carrier, the power consumption of the UE is very large. Therefore, it is recommended that the RF bandwidth of the UE can be adjusted according to the actual throughput of the UE.
- the motivation for introducing the BandWidth Part (BWP) for this purpose is to optimize the power consumption of the UE. For example, if the UE's rate is very low, a smaller bandwidth can be configured for the UE ( Figure 2a). If the UE's rate requirements are very high, a larger bandwidth can be configured for the UE ( Figure 2b). If the UE supports high rates or operates in Carrier Aggregation (CA) mode, multiple BWPs can be configured ( Figure 2c). Another purpose of BWP is to trigger the coexistence of multiple basic parameter sets (numerology) in a cell.
- CA Carrier Aggregation
- the UE currently in idle state or inactive state resides on the initial BWP.
- This BWP is visible to UE in idle state or inactive state.
- you can obtain information such as Master Information Block (MIB), Remaining Minimum System Information (RMSI), Open Systems Interconnection (OSI), and paging.
- MIB Master Information Block
- RMSI Remaining Minimum System Information
- OSI Open Systems Interconnection
- CFR Common frequency resource
- MBMS Multimedia Broadcast Multicast Services
- MBS Multicast Broadcast Service
- CFR is a design concept introduced during the NR MBS discussion to distinguish it from BWP.
- CFR is a continuous set of frequency domain resources located on the carrier and is used to receive MBS services. From the perspective of a single UE, a CFR is a continuous set of frequency domain resources used to receive downlink MBS service data. From a system perspective, CFR is used to send MBS service data.
- a group of UEs in the connected state (RRC_CONNECTED) receive MBS multicast/multicast in the CFR, and UEs in the non-connected state (RRC_IDLE/RRC_INACTIVE) receive MBS multicast on the CFR. Receive MBS broadcasts.
- Multimedia Broadcast Multicast Service is a service introduced in 3GPP Release 6 (Release 6, R6).
- Multimedia broadcast multicast service is a technology that transmits data from one data source to multiple user devices by sharing network resources. While providing multimedia services, it can effectively utilize network resources and achieve higher-rate (256kbps) multimedia service broadcasting. and multicast.
- 3GPP Due to the low spectrum efficiency of MBMS in 3GPP R6, it is not enough to effectively carry and support the operation of mobile TV-type services. Therefore, in the wireless access network long-term evolution standard (Long Term Evolution, LTE) project, 3GPP clearly proposed to enhance the support capabilities for downlink high-speed multimedia broadcast multicast service services, and determined the design requirements for the physical layer and air interface.
- LTE Long Term Evolution
- eMBMS was introduced to LTE networks in R9.
- eMBMS proposes the concept of Single Frequency Network (SFN), which uses a unified frequency to send data to all cells at the same time, but must ensure synchronization between cells. This method can greatly improve the overall signal-to-noise ratio distribution of the cell, and the spectrum efficiency will also be greatly improved accordingly.
- SFN Single Frequency Network
- IP Internet Protocol
- MBMS In LTE/Long Term Evolution Advanced (LTE-A), MBMS only has a broadcast bearer mode and no multicast bearer mode.
- LTE-A Long Term Evolution Advanced
- Reception of MBMS services is applicable to UEs in RRC_CONNECTED or RRC_IDLE state.
- SC-PTM is introduced in R13.
- SC-PTM is based on the MBMS network architecture, and the Multi-cell/multicast Coordination Entity (MCE) decides to use the SC-PTM transmission method or the Multimedia Broadcast multicast service Single Frequency Network (Multimedia Broadcast multicast service Single Frequency Network , MBSFN) transmission method.
- MCE Multi-cell/multicast Coordination Entity
- SC-MCCH Single Cell Multicast Control Channel
- SC-MTCH Single Cell Multicast Transport Channel
- PDSCH Physical Downlink Shared Channel
- SIB system information block
- SIB20 to transmit SC-MCCH configuration information.
- Configuration information includes: SC-MCCH modification period, repetition period, and radio frame and subframe configuration information.
- SC-MCCH-Subframe subframe
- SC-MCCH only transmits one message SC-PTMConfiguration (configuration), which is used to configure the configuration information of SC-PTM.
- configuration which is used to configure the configuration information of SC-PTM.
- RNTI Radio Network Temporary Identifier
- SC-RNTI single cell RNTI
- FFFC Fixed Value FFFC
- SC-N-RNTI Single Cell Notification RNTI
- DCI Downlink Control Information 1C
- SFN mod m 0, where m is the modification period configured in SIB20 such as sc-mcch-ModificationPeriod; mod represents the modulo operation.
- the Radio Link Control (Radio Link Control, RLC) Acknowledgment Mode (AM) mode has an Automatic Repeat-reQuest (ARQ) feedback mechanism.
- the receiving end sends an RLC status report to feedback whether the reception status of the RLC packet is Acknowledgment (ACK) or No Acknowledge (NACK).
- the sender can repeatedly transmit the RLC packet that feeds back the NACK number of the Secondary Node (SN).
- the downlink BWP is configured through the BWP-Downlink (bandwidth part downlink) parameter.
- this parameter includes the bwp-Id (bandwidth part identification) field to identify the ID of the current BWP, and bwp-Common (the bandwidth part public) is used to Configure the public parameters of the downlink BWP.
- the genericParameters general parameters
- BWP-DownlinkCommon bandwidth part downlink common
- PRB Physical Resource Block
- the bwp-Dedicated (bandwidth part dedicated) parameter in BWP-Downlink will configure the downlink reception parameters on the downlink BWP.
- it includes at least pdcch-Config (PDCCH configuration), pdsch-Config (PDSCH configuration), and sps-Config (SPS configuration).
- pdcch-Config is used to indicate the PDCCH transmission mode on the downlink BWP
- pdsch-Config is used to indicate the PDSCH transmission mode on the downlink BWP
- sps-Config is used to indicate the PDCCH transmission mode on the downlink BWP.
- base station scheduling and transmission methods include the following:
- Sending MBS services by broadcasting is applicable when the terminal is in the RRC_IDLE/RRC_INACTIVE (non-connected) state, and when the terminal is in the RRC_CONNECTED (connected) state.
- the MBS service transmitted through broadcasting can be received by the terminal no matter what link state it is in, as long as it is within the coverage area.
- Sending MBS services to a group of terminals in multicast mode is applicable when all terminals in the group are in the RRC_CONNECTED state.
- the base station sends the same MBS service to a group of terminals through one-to-many PTM transmission.
- Sending MBS services to each terminal in unicast mode is suitable for terminals in the RRC_CONNECTED state.
- the base station sends the same MBS services to each terminal through one-to-one PTP transmission.
- CFR configuration methods exist:
- the CFR is configured as an MBS-specific BWP.
- the MBS-specific BWP is associated with the terminal's dedicated unicast BWP, and the subcarrier spacing and cyclic prefix configured on the CFR are the same as those configured on the terminal's dedicated unicast BWP.
- CFR is configured as multiple consecutive PRBs within the terminal-specific unicast BWP range.
- the advantage of the first method is that CFR can continue to use the relevant BWP signaling configuration, which helps reduce the workload of the standard.
- CFR is defined as BWP
- if the terminal is required to receive unicast in the dedicated unicast BWP and receive multicast in the CFR at the same time it means that the terminal needs to receive downlink transmission on both BWPs at the same time.
- the terminal is only capable of receiving downlink on one BWP at a given time.
- BWP switching delay will be introduced.
- the second method can avoid the problem of BWP handover, but because the CFR in this method is multiple consecutive PRBs, the current BWP-based signaling configuration cannot be used, and the resource range and uplink and downlink transmission parameters of the CFR need to be redesigned.
- the configuration method has a greater impact on the standard.
- the terminals since the public PDCCH that schedules the public PDSCH needs to be sent to multiple receiving terminals at the same time, in order to ensure that the number of public DCI bits carried in the public PDCCH determined by the multiple terminals is the same, the terminals cannot determine according to the configuration of their respective dedicated unicast BWPs. The number of bits of the public DCI.
- the number of PRBs in the CFR may be different from the initial BWP or CORESET (ControlResourceSet, Control Resource Set) #0 (COntrol REsource SET 0) currently configured by the terminal, the terminal cannot determine the public DCI bits through the initial BWP or CORESET#0 number.
- the number of public DCI bits may be different from the number of DCI bits received by the terminal in the relevant USS or CSS. Then, in order to reduce the implementation complexity of the terminal, currently the terminal can only receive up to 4 DCI bits with different numbers in a cell. Among them, the number of DCI bits scrambled by the cell-specific RNTI (Cell RNTI, C-RNTI) does not exceed 3 types.
- Group-shared PDCCH/PDSCH means that the PDCCH/PDSCH sent by the base station on a set of time-frequency resources can be received by multiple UEs in the same group.
- the PTM scheduling method mentioned in this solution can refer to PTM1.
- the group-shared PDCCH is used to schedule the group-shared PDSCH.
- the cyclic redundancy check (Cyclic Redundancy Check, CRC) of the group-shared PDCCH is scrambled using the group-shared RNTI, and the group-shared PDSCH is used. Use the same group to share RNTI for scrambling.
- PTM 2 For multiple UEs in the same group in the connected state, use the UE-specific PDCCH scheduling group to share the PDSCH for each UE.
- the CRC of the UE-specific PDCCH is scrambled using the UE-specific RNTI (i.e. C-RNTI), and the group-shared PDSCH is used.
- Group shared RNTI scrambling.
- each UE uses the UE-specific PDCCH to schedule the UE-specific PDSCH.
- the CRC of the UE-specific PDCCH is scrambled using the UE-specific RNTI (i.e., C-RNTI).
- the UE-specific PDSCH uses the UE-specific RNTI (i.e., C-RNTI). RNTI) scrambling.
- the MBS service retransmission mechanism based on HARQ-ACK feedback in the connected state can support the following methods:
- NR MBS multicast and unicast use HARQ process ID (HARQ process ID, HPID)
- HPID of the system is shared between multicast/multicast and unicast (HARQ process ID: 0 ⁇ 15).
- the specific allocation of HPID is determined by the base station implementation. If HPID#1 is first allocated to the transmission of a transport block (TB) 1 of the MBS service, when the initial transmission and potential retransmission of TB1 are completed, the base station will continue to allocate HPID#1 to the transmission of TB2. , at this time TB2 is used for unicast transmission of UE3. When the initial transmission and potential retransmission of TB2 are completed, the base station will continue to allocate HPID#1 to the transmission of TB3. At this time, TB3 is used for the transmission of MBS services.
- TB transport block
- HPID and New Data Indicator determine the method of initial transmission and retransmission
- the UE will clear the data information of the previous TB stored in the cache, and then store the initial transmission of the newly received TB and the potentially received retransmission in the cache for soft merging.
- the network side determines the number of TB repeated transmissions of an MBS service through configuration. Once the configuration is determined, if a TB is repeated 4 times, the number of repeated transmissions for all TBs corresponding to this service will be 4 times for a long period of time before the signaling is updated. In addition, each TB is configured with only one opportunity to provide feedback in the uplink feedback resource at the end of the repeated transmission.
- repeated transmission of TB is as described above. Once the number of TB repetitions is configured, it cannot be changed in the short term. When the channel conditions are very good, when all UEs receive a TB, they can decode it correctly after receiving it once or twice. Repeated transmission of the remaining TB is obviously redundant and takes up a lot of downlink transmission resources, causing waste. In addition, the feedback for each TB is uniformly fed back to one TB at the end of the repeated transmission. If the number of repeated transmissions of a TB is 8, then the UE needs to complete 8 transmissions before it can provide feedback for this TB. If the UE decodes successfully the first time, the waiting time will be very long, resulting in a long delay.
- Figure 5 is a schematic flow chart of a repeated transmission method 500 according to an embodiment of the present application. This method can optionally be applied to the system shown in Figure 1, but is not limited thereto. The method includes at least part of the following.
- the terminal device performs subsequent repeated transmission related processing according to the first number of repeated transmissions of the downlink data and the transmission status of the downlink data.
- the downlink data is in the transport block TB and/or the physical downlink shared channel PDSCH.
- the terminal device may perform subsequent processing related to the repeated transmission of the TB based on the first number of repeated transmissions of the TB and the transmission status of the TB.
- the terminal equipment may perform subsequent processing related to the repeated transmission of the PDSCH based on the first number of repeated transmissions of the PDSCH and the transmission situation of the PDSCH.
- the subsequent repeated transmission related processing performed by a terminal device such as a UE may include a variety of processes, which may mainly include: after receiving the current TB and/or PDSCH, the UE performs processing related to the TB and/or the PDSCH. Repeat some operations related to transmission. For example, stop receiving repeated transmissions, continue to receive repeated transmissions, perform uplink feedback, etc.
- performing subsequent repeated transmission related processing includes: determining whether to receive the repeatedly transmitted downlink data.
- the UE may determine whether downlink data is received, the current number of received downlink data, the number of first repeated transmissions N (that is, the total number of times), and the decoding situation after the received downlink data. or multiple methods to determine whether to continue to receive the downlink data repeatedly transmitted by the network device.
- determining whether to receive the repeatedly transmitted downlink data includes:
- Method 1 If the terminal device successfully decodes the downlink data received at least once, it will no longer receive the repeatedly transmitted downlink data.
- the UE successfully decodes this TB1 it may no longer receive the third to sixth transmissions of TB1 from the network device. Repeat the transfer.
- the network side may not repeatedly transmit the third to sixth TB1 after learning that the UE has successfully decoded the second TB1.
- Method 2 When the received downlink data fails to be decoded, the terminal device continues to receive the repeatedly transmitted downlink data until the current number of transmissions reaches the first number of repeated transmissions or the received downlink data is successfully decoded.
- the UE fails to decode this time TB2
- the UE continues to receive the third repeated transmission of TB2. If the third received TB2 is decoded successfully, the network device may no longer receive repeated transmissions of TB2 from the fourth to sixth times. If the decoding of the 3rd to 6th received TB2 fails, stop receiving repeated transmissions of TB2.
- Method 3 In the case where no downlink data is received, the terminal device continues to receive the repeatedly transmitted downlink data until the current number of transmissions reaches the first number of repeated transmissions or the received downlink data is decoded successfully.
- the UE continues to receive the fourth repeated transmission of TB3. If the fourth received TB3 is successfully decoded, the network device may no longer receive repeated transmissions of the fifth to sixth TB3s. If the decoding of the 4th to 6th received TB3 fails, stop receiving repeated transmissions of TB2.
- the method 600 includes: S610.
- the terminal device receives first indication information, where the first indication information includes the first number of repeated transmissions and/or the first repetition interval.
- the steps of the method 600 and the above-mentioned method 500 can be implemented separately or combined.
- the UE may receive first indication information from a network device such as a base station.
- the indication information may be dynamically configured or semi-statically configured.
- the first number of repeated transmissions may be the total number of repeated transmissions of downlink data by the network device, or the total number of repeated transmissions of the terminal device receiving downlink data.
- the total number of times the network device repeatedly transmits downlink data and the total number of times the terminal device receives downlink data can be the same or different.
- the first repetition interval may represent an interval for repeated transmission of downlink data, and the first repetition interval may be a time slot or a symbol.
- the first indication information is in at least one of the following: radio resource control (RRC) signaling; downlink control information (DCI).
- RRC radio resource control
- DCI downlink control information
- RRC signaling is a kind of high-level configuration information.
- the network device may first deliver the first indication information to the terminal device through high-level configuration information.
- DCI is a dynamic indication method.
- the network device can send a PDCCH to the terminal device, the PDCCH carries DCI, and the DCI carries the first indication information.
- the terminal device may use the first indication information to include the first number of repeated transmissions and/or the first repetition interval to perform subsequent repeated transmission related processing.
- the feedback mode of the terminal device may be an acknowledgment/non-acknowledgment (ACK/NACK) feedback mode or a non-acknowledgement (NACK-only) feedback mode.
- Feedback mode can also be called feedback mode.
- the terminal device can feed back confirmation information to the network device, and can also feed back non-confirmation information to the network device.
- the uplink feedback information sent by the terminal device may be acknowledgment (ACK) information or non-acknowledgement (NACK) information.
- the NACK-only feedback mode if it is in the confirmation state, the terminal device does not feedback information. It only feeds back non-confirmation information to the network device in the non-confirmation state.
- performing subsequent repeated transmission related processing also includes:
- the terminal device After receiving n times of downlink data, the terminal device sends uplink feedback information once; where n is greater than or equal to 1, and n is less than or equal to the first number of repeated transmissions N, and N is greater than or equal to 1.
- the uplink feedback information is in a physical uplink control channel (Physical Uplink Control Channel, PUCCH) and/or a physical uplink shared channel (Physical Uplink Shared Channel, PUSCH).
- PUCCH Physical Uplink Control Channel
- PUSCH Physical Uplink Shared Channel
- the terminal device may send a PUCCH carrying uplink feedback information to the network device every time it receives a TB or PDSCH.
- the terminal device can send a PUCCH carrying uplink feedback information to the network device once every time it receives TB or PDSCH twice.
- the terminal device after receiving n times of downlink data, the terminal device sends uplink feedback information once, including:
- the terminal device sends the uplink feedback information including confirmation information;
- the terminal device When decoding of m times of downlink data received among the n times of downlink data fails, the terminal device sends the uplink feedback information including non-confirmation information; where m is greater than or equal to 1 and m is less than or equal to n.
- the terminal device provides feedback every n times when it receives downlink data.
- m can represent the threshold of the number of decoding failures.
- the terminal device can feedback non-confirmation information if the number of decoding failures is greater than the threshold.
- the terminal equipment receives 1 uplink feedback information every 3 times of TB or PDSCH feedback. If the TB or PDSCH received three times are all decoded successfully, or one or two times are decoded successfully, the terminal device can send a PUCCH including ACK information to the network device. If these three received TBs or PDSCHs all fail to be decoded or the number of decoding failures is greater than a certain threshold, such as 2 times, the terminal device sends a PUCCH including NACK information.
- a certain threshold such as 2 times
- the terminal equipment receives 1 uplink feedback information every 3 times of TB or PDSCH feedback. If the TB or PDSCH received three times are all decoded successfully, or one or two times are decoded successfully, the terminal device does not send the PUCCH. If these three received TBs or PDSCHs all fail to be decoded or the number of decoding failures is greater than a certain threshold, such as 2 times, the terminal device sends a PUCCH including NACK information.
- a certain threshold such as 2 times
- the terminal device when at least one of the s downlink data received is decoded successfully, the terminal device does not receive the repeatedly transmitted downlink data, where s is greater than or equal to 1, and s is less than The first number of repeated transmissions is N.
- s may represent the number of times the terminal device receives downlink data. For example, if the first number of repeated transmissions N is equal to 4, and the terminal device receives the first TB and successfully decodes the TB, it will no longer receive repeated transmissions from the second to the fourth TB. For another example, if the first number of repeated transmissions N is equal to 5 and the terminal device does not receive the first PDSCH, the terminal device continues to receive the second repeated transmission of the PDSCH. If the second PDSCH is decoded successfully, the terminal device will no longer receive the repeated transmission of the third, fourth and fifth PDSCH.
- the terminal equipment receives the 1st, 2nd and 3rd PDSCH, and the 2nd PDSCH is decoded successfully, the terminal equipment will no longer receive the 4th and 5th times. Repeated transmission of PDSCH.
- the method 700 includes: S710, the terminal device receives second indication information, the second indication information includes a second number of repeated transmissions and/or a second repetition interval, wherein, The second number of repeated transmissions is determined based on the feedback situation of the downlink data and the first number of repeated transmissions, and the second number of repeated transmissions is different from the first number of repeated transmissions.
- the method 700 and the steps of the above-mentioned methods 500 and/or 600 can be implemented separately or combined.
- the first indication information may indicate that the current number of repeated transmissions of the TB and/or the PDSCH is the first number of repeated transmissions.
- the second indication information may indicate that the number of repeated transmissions of the next TB and/or PDSCH is adjusted to the second number of repeated transmissions.
- the terminal equipment can determine whether to receive the repeatedly transmitted downlink data based on the first number of repeated transmissions of downlink data and the transmission situation of the downlink data, and determine whether to receive the repeatedly transmitted downlink data for the next TB and/or PDSCH.
- the second number of repeated transmissions of the downlink data and the transmission situation of the downlink data are used to determine whether to receive the repeatedly transmitted downlink data.
- the terminal equipment receives all the data according to the first number of repeated transmissions, and for the next TB and/or PDSCH, the second number of repeated transmissions of downlink data and the transmission status of the downlink data are used to determine whether Receive the repeatedly transmitted downlink data.
- the network device can appropriately reduce the first number of repeated transmissions N to obtain the second number of repeated transmissions N. '. If the terminal device cannot receive and successfully decode the downlink data N times, the network device can appropriately increase the first number of repeated transmissions N to obtain the second number of repeated transmissions N'.
- the second indication information is in DCI.
- the second number of repeated transmissions can be configured in a dynamic indication manner.
- the terminal device receives a PDCCH from the network device, the PDCCH carries DCI, and the DCI carries second indication information.
- the DCI carrying the first indication information and the DCI carrying the second indication information may be different or the same.
- the network device may send the same downlink data to multiple terminal devices at one time. Some terminal devices may be able to receive and successfully decode the downlink data, while other terminal devices may not receive or successfully decode the downlink data.
- the feedback modes of the terminal device also include the above-mentioned ACK/NACK feedback mode and NACK-only feedback mode. Therefore, there may be multiple specific feedback situations from the terminal device. Based on different feedback conditions from the terminal device, the network device may need to adjust the number of repeated transmissions.
- the first number of repetitions is adjusted by the network device to the second number of repetitions:
- the uplink feedback information of the M target terminal devices includes acknowledgment information (ACK/NACK feedback mode);
- the uplink feedback information of P target terminal devices includes non-acknowledgement information (ACK/NACK feedback mode or NACK-only feedback mode);
- P target terminal devices did not feed back uplink feedback information (NACK-only feedback mode);
- M is less than or equal to the total number Y of target terminal devices sent by the network device through point-to-multipoint (PTM), and M is greater than or equal to the first threshold; and/or, M is less than or equal to the first number of repeated transmissions N, And the ratio of M to Y is greater than or equal to the second threshold;
- PTM point-to-multipoint
- P is less than or equal to Y, and P is less than or equal to the third threshold; and/or, P is less than or equal to the first number of repeated transmissions N, and the ratio of P to Y is less than or equal to the fourth threshold.
- Figure 8 is a schematic flow chart of a repeated transmission method 800 according to an embodiment of the present application. This method can optionally be applied to the system shown in Figure 1, but is not limited thereto. The method includes at least part of the following.
- the network device performs subsequent repeated transmission related processing based on the first number of repeated transmissions of the downlink data and the feedback of the downlink data.
- performing subsequent repeated transmission related processing includes: determining whether to repeatedly transmit the downlink data.
- determining whether to repeatedly transmit the downlink data includes at least one of the following:
- the network device If the network device receives at least one uplink feedback information for the downlink data including acknowledgment information, the network device will not re-transmit the downlink data;
- the network device does not receive uplink feedback information for the downlink data, it will not re-transmit the downlink data;
- the network device When the network device receives the uplink feedback information for the downlink data that includes non-confirmation information, it repeatedly transmits the downlink data until it receives the uplink feedback information for the downlink data that includes confirmation information or the current number of transmissions reaches the th. until the number of repeated transmissions.
- the method 900 includes: S910.
- the network device sends first indication information, where the first indication information includes the first number of repeated transmissions and/or the first repetition interval.
- the steps of the method 900 and the above-mentioned method 800 can be implemented separately or combined.
- the first indication information is in at least one of the following: RRC signaling; DCI.
- the method further includes: the network device receiving uplink feedback information once after sending downlink data n times; wherein n is greater than or equal to 1, and n is less than or equal to the first number of repeated transmissions N, N is greater than or equal to 1.
- the network device after sending downlink data n times, the network device receives uplink feedback information once, including:
- the network device receives the uplink feedback information including confirmation information
- the network device When decoding of m times of downlink data among the n times of sent downlink data fails, the network device receives the uplink feedback information including non-acknowledgment information; where m is greater than or equal to 1 and less than or equal to n.
- performing subsequent repeated transmission related processing includes:
- the network device adjusts the first number of repeated transmissions according to the feedback of the downlink data.
- the network device adjusts the first number of repeated transmissions according to the feedback of the downlink data, including:
- the network device adjusts the first number of repeated transmissions to a second number of repeated transmissions according to the feedback of the downlink data.
- the second number of repeated transmissions is different from the first number of repeated transmissions.
- the feedback situation of the downlink data satisfies at least one of the following:
- the uplink feedback information of the M target terminal devices includes confirmation information
- the uplink feedback information of P target terminal devices includes non-confirmation information
- P target terminal devices did not feed back uplink feedback information
- M is less than or equal to the total number Y of target terminal devices sent by the network device through point-to-multipoint PTM, and M is greater than or equal to the first threshold; and/or, M is less than or equal to the first number of repeated transmissions N, and M The ratio to Y is greater than or equal to the second threshold;
- P is less than or equal to Y, and P is less than or equal to the third threshold; and/or, P is less than or equal to the first number of repeated transmissions N, and the ratio of P to Y is less than or equal to the fourth threshold.
- the network device sends TB1 to Y terminal devices, and the first number of repeated transmissions of TB1 is N.
- the network device receives uplink feedback information including ACK information from M target terminal devices, and M is greater than If the first threshold of the number of successfully transmitted devices is set, and M is less than N, then the network device adjusts the first number of repeated transmissions to the second number of repeated transmissions. In this case, the second number of repeated transmissions may be smaller than the first number of repeated transmissions. For example, if the first number of repeated transmissions is 8, the network device sends TB1 to 40 terminal devices, and receives ACK information fed back by 30 terminal devices.
- the network device adjusts the first number of repeated transmissions to the second number of repeated transmissions, which is 4.
- the second threshold is 70%
- the network device sends TB1 to Y terminal devices, and the number of first repeated transmissions of TB1 is N.
- the network device does not receive the uplink feedback information from M target terminal devices.
- the first number of repeated transmissions is adjusted to the second number of repeated transmissions. For example, if the first number of repeated transmissions is 8, the network device sends TB1 to 40 terminal devices, but no ACK information is received from 30 terminal devices. Assuming that the first threshold is 25 and the number 30 of terminal devices that have not fed back information is greater than the second threshold, the network device adjusts the first number of repeated transmissions to the second number of repeated transmissions, which is 4.
- the network device adjusts the first number of repeated transmissions to the second number of repeated transmissions. is 4.
- the network device sends TB1 to Y terminal devices, and the first number of repeated transmissions of TB1 is N.
- the network device receives NACK messages from P target terminal devices.
- the first number of repeated transmissions is adjusted to the second number of repeated transmissions. For example, if the first number of repeated transmissions is 8, the network device sends TB1 to 40 terminal devices, receives ACK information from 30 terminal devices, and the first threshold is 25, then the network device adjusts the first number of repeated transmissions to 40 terminal devices.
- the number of repeated transmissions is 4.
- the network device sends TB1 to Y terminal devices, and the number of first repeated transmissions of TB1 is N.
- the network device does not receive uplink feedback information from P target terminal devices.
- the first number of repeated transmissions is adjusted to the second number of repeated transmissions. For example, if the first number of repeated transmissions is 8, the network device sends TB1 to 40 terminal devices, but no ACK information is received from 30 terminal devices, and the first threshold is 25, then the network device adjusts the first number of repeated transmissions to The second number of repeated transmissions is 4.
- the adjusted second number of repeated transmissions can be used for repeated transmissions of TB2 or TB3 after this time TB1.
- the method 1000 further includes: S1010.
- the network device sends second indication information, where the second indication information includes a second number of repeated transmissions and/or a second repetition interval.
- the method 1000 and the steps of the above-mentioned methods 800 and/or 900 can be implemented separately or combined.
- the second indication information is in DCI.
- the uplink feedback information is in PUCCH and/or PUSCH.
- the downlink data is in TB and/or PDSCH.
- network device execution methods 800, 900, and 1000 in this embodiment please refer to the relevant descriptions of network devices such as base stations in the above methods 500, 600, and 700. For the sake of brevity, they will not be described again here.
- Figure 1100 is a schematic block diagram of a terminal device 1100 according to an embodiment of the present application.
- the terminal device 1100 may include:
- the processing unit 1110 is configured to perform subsequent repeated transmission related processing according to the first number of repeated transmissions of downlink data and the transmission status of the downlink data.
- the processing unit is configured to perform subsequent repeated transmission related processing, including: determining whether to receive the repeatedly transmitted downlink data.
- the terminal device 1200 may include the above-mentioned processing unit 1110.
- the terminal device 1200 may also include a first receiving unit 1210.
- the processing unit 1110 is used to determine whether to receive the repeatedly transmitted Downstream data includes:
- the first receiving unit 1210 If the received downlink data fails to be decoded, instruct the first receiving unit 1210 to continue receiving the repeatedly transmitted downlink data until the current number of transmissions reaches the first number of repeated transmissions or the received downlink data is decoded successfully;
- the first receiving unit 1210 is instructed to continue receiving the repeatedly transmitted downlink data until the current number of transmissions reaches the first number of repeated transmissions or the received downlink data is successfully decoded.
- the terminal device 1200 further includes: a second receiving unit 1220, configured to receive first indication information, where the first indication information includes the first number of repeated transmissions and/or First repeat interval.
- the first indication information is in at least one of the following:
- DCI Downlink Control Information
- the terminal device further includes a sending unit 1240, and the processing unit 1110 is configured to instruct the sending unit to send uplink feedback information once after receiving n times of downlink data; where n is greater than or equal to 1, and n is less than or equal to the first number of repeated transmissions N, and N is greater than or equal to 1.
- the processing unit 1110 is configured to instruct the sending unit to send uplink feedback information once after receiving n times of downlink data, including:
- the processing unit 1110 is also configured to instruct the first receiving unit 1210 not to receive the repeatedly transmitted downlink data when at least one of the s downlink data received is successfully decoded, wherein , s is greater than or equal to 1, and s is less than the first number of repeated transmissions N.
- the terminal device 1200 further includes: a third receiving unit 1230, configured to receive second indication information, where the second indication information includes a second number of repeated transmissions and/or a second The repetition interval, wherein the second number of repeated transmissions is determined based on the feedback situation of the downlink data and the first number of repeated transmissions, and the second number of repeated transmissions is different from the first number of repeated transmissions.
- a third receiving unit 1230 configured to receive second indication information, where the second indication information includes a second number of repeated transmissions and/or a second The repetition interval, wherein the second number of repeated transmissions is determined based on the feedback situation of the downlink data and the first number of repeated transmissions, and the second number of repeated transmissions is different from the first number of repeated transmissions.
- the second indication information is in DCI.
- the feedback situation of the downlink data satisfies at least one of the following:
- the uplink feedback information of the M target terminal devices includes confirmation information
- the uplink feedback information of P target terminal devices includes non-confirmation information
- P target terminal devices did not feed back uplink feedback information
- M is less than or equal to the total number Y of target terminal devices sent by the network device through point-to-multipoint PTM, and M is greater than or equal to the first threshold; and/or, M is less than or equal to the first number of repeated transmissions N, and M The ratio to Y is greater than or equal to the second threshold;
- P is less than or equal to Y, and P is less than or equal to the third threshold; and/or, P is less than or equal to the first number of repeated transmissions N, and the ratio of P to Y is less than or equal to the fourth threshold.
- the uplink feedback information is in the physical uplink control channel PUCCH and/or the physical uplink shared channel PUSCH.
- the downlink data is in the transport block TB and/or the physical downlink shared channel PDSCH.
- the terminal devices 1100 and 1200 in the embodiment of the present application can realize the corresponding functions of the terminal devices in the foregoing method 500, 600 and 700 embodiments.
- each module (sub-module, unit or component, etc.) in the terminal equipment 1100 and 1200 please refer to the corresponding description in the above method embodiment, and will not be described again here.
- the functions described for each module (sub-module, unit or component, etc.) in the terminal devices 1100 and 1200 of the application embodiment can be implemented by different modules (sub-module, unit or component, etc.), or can be implemented by Implemented by the same module (submodule, unit or component, etc.).
- FIG. 13 is a schematic block diagram of a network device 1300 according to an embodiment of the present application.
- the network device 1300 may include:
- the processing unit 1310 is configured to perform subsequent repeated transmission related processing according to the first number of repeated transmissions of downlink data and the feedback status of the downlink data.
- the processing unit 1310 is configured to perform subsequent repeated transmission related processing, including: determining whether to repeatedly transmit the downlink data.
- the network device 1400 also includes a first sending unit 1410.
- the processing unit 1310 is also used to determine whether to repeatedly transmit the downlink data, including at least one of the following:
- the received at least one uplink feedback information for the downlink data includes acknowledgment information, instruct the first sending unit 1410 not to repeatedly transmit the downlink data;
- the first sending unit 1410 When receiving the uplink feedback information for the downlink data including non-confirmation information, instruct the first sending unit 1410 to repeatedly transmit the downlink data until the uplink feedback information for the downlink data includes acknowledgment information or the current The number of transmissions reaches the first number of repeated transmissions.
- the network device 1400 further includes: a second sending unit 1420, configured to send first indication information, where the first indication information includes the first number of repeated transmissions and/or First repeat interval.
- the first indication information is in at least one of the following: RRC signaling; DCI.
- the network device 1400 further includes: a receiving unit 1430, configured to receive uplink feedback information once after sending n downlink data; where n is greater than or equal to 1, and n is less than or equal to the first number of repeated transmissions N, and N is greater than or equal to 1.
- the receiving unit 1430 is used for:
- the uplink feedback information including non-acknowledgment information is received; where m is greater than or equal to 1 and less than or equal to n.
- the processing unit 1310 is also configured to perform subsequent repeated transmission related processing, including: adjusting the first number of repeated transmissions according to the feedback of the downlink data.
- the processing unit 1310 is further configured to adjust the first number of repeated transmissions according to the feedback of the downlink data, including: adjusting the first number of repeated transmissions to the second number of times according to the feedback of the downlink data.
- the second number of repeated transmissions is different from the first number of repeated transmissions.
- the feedback situation of the downlink data satisfies at least one of the following:
- the uplink feedback information of the M target terminal devices includes confirmation information
- the uplink feedback information of P target terminal devices includes non-confirmation information
- P target terminal devices did not feed back uplink feedback information
- M is less than or equal to the total number Y of target terminal devices sent by the network device through point-to-multipoint PTM, and M is greater than or equal to the first threshold; and/or, M is less than or equal to the first number of repeated transmissions N, and M The ratio to Y is greater than or equal to the second threshold;
- P is less than or equal to Y, and P is less than or equal to the third threshold; and/or, P is less than or equal to the first number of repeated transmissions N, and the ratio of P to Y is less than or equal to the fourth threshold.
- the network device 1400 further includes: a third sending unit 1440, configured to send second indication information, where the second indication information includes the second number of repeated transmissions and/or the second Two repetition intervals.
- the second indication information is in DCI.
- the uplink feedback information is in PUCCH and/or PUSCH.
- the downlink data is in TB and/or PDSCH.
- the network devices 1300 and 1400 in the embodiments of this application can implement the corresponding functions of the network devices in the aforementioned method 800, 900 and 1000 embodiments.
- each module (sub-module, unit or component, etc.) in the network devices 1300 and 1400 please refer to the corresponding description in the above method embodiment, and will not be described again here.
- the functions described for each module (sub-module, unit or component, etc.) in the network devices 1300 and 1400 of the application embodiment can be implemented by different modules (sub-module, unit or component, etc.), or can be implemented by Implemented by the same module (submodule, unit or component, etc.).
- the repeated transmission method provided by the embodiment of the present application may be a method of repeatedly sending TBs in a broadcast multicast service.
- This method can mainly include the following:
- the base station determines whether to continue to send the remaining repeated transmissions of this TB or not to send them again based on the current feedback information.
- the number of repeated transmissions, intervals, and time-frequency resource locations of one TB in each cycle are determined through configuration.
- the UE decides whether to receive the remaining retransmissions of the TB based on whether the decoding of the TB has been received successfully; if the UE does not receive a certain transmission of a TB, it will continue to receive subsequent transmissions of the TB. Repeat the transfer.
- Example 1 One TB, semi-static configuration feedback times
- one PDSCH/TB is sent repeatedly N times, and the N PDSCH sending interval is G, where N ⁇ 1 is a positive integer and G ⁇ 0 is an integer.
- uplink feedback can be performed after N times of repeated transmission of a TB.
- ACK/NACK feedback mode If the receiving UE successfully decodes the PDSCH at least once in ⁇ N receptions, it will feed back ACK to the base station through the uplink resource physical uplink control channel (PUCCH) or physical uplink shared channel (PUSCH); If the receiving UE does not successfully decode the PDSCH in ⁇ N receptions, it will feed back NACK to the base station through the uplink resource PUCCH or PUSCH. or
- PUCCH physical uplink control channel
- PUSCH physical uplink shared channel
- NACK-only feedback mode The receiving UE successfully decodes the PDSCH at least once in ⁇ N receptions, and does not feed back any information to the base station through the uplink resource PUCCH or PUSCH; the receiving UE does not feedback any information to the base station in ⁇ N receptions. If the PDSCH is not decoded successfully, NACK is fed back to the base station through the uplink resource PUCCH or PUSCH.
- the base station can decide whether to continue sending the remaining PDSCH repetitions based on the feedback of a group of UEs (for example, Y UEs).
- the number of repeated transmissions of a TB is a positive integer N ⁇ 1, for example, the priority candidate value is ⁇ 2, 4, 6, 8, 16 ⁇ .
- the PDSCH transmission interval is G.
- G 0
- the N repeated transmissions of the PDSCH are continuous transmissions, that is, the time slot in which the PDSCH is located is a continuous time slot.
- a TB is sent repeatedly 4 times.
- an uplink feedback resource PUCCH is configured. If the UE successfully decodes the PDSCH at least once in 4 (or less than 4) receptions, it passes the uplink resource Feed back ACK to the base station. If the UE does not successfully decode the PDSCH in 4 receptions (or less than 4 times), it will feed back NACK to the base station through the uplink resources.
- a TB is sent repeatedly 4 times.
- two uplink feedback resources PUCCH are configured, one PUCCH resource after the first two repeated transmissions, and one PUCCH resource after the last two repeated transmissions.
- a UE's perspective If the UE successfully decodes at least one of the first two PDSCHs received and feeds back ACK on the first PUCCH, the UE does not need to receive the last two PDSCHs.
- ACK/NACK feedback For the first two PDSCH transmissions, the feedback from all receiving UEs is ACK, then the base station will no longer send the next two PDSCHs; for the first two PDSCH transmissions, if there is K (K ⁇ 1) UEs feedback NACK, then the base station continues to send the last two PDSCHs.
- NACK-only feedback For the first two PDSCH transmissions, all UEs do not feedback any information to the base station (that is, the decoding is successful), then the base station will no longer send the next two PDSCHs; for the first two PDSCH transmissions, If K (K ⁇ 1) UEs feedback NACK, the base station continues to send the last two PDSCHs.
- Example 1 after each PDSCH, there is a PUCCH resource for the UE to send feedback information.
- Example 2 One TB, dynamically indicating the number of feedback times
- the indication information of PDCCH/DCI it is indicated that the number of repeated transmissions of one PDSCH/TB is N times, and the transmission interval of N PDSCHs is G, where N ⁇ 1 is a positive integer and G ⁇ 0 is an integer.
- X% may be the ratio of the number of UEs that feed back ACK (ACK/NACK feedback mode) or no feedback information (NACK-only feedback mode) to the total number of UEs (in a PTM scenario).
- the PDCCH indicates that the number of repetitions is 4 times.
- This group of UEs perform feedback on PUCCH resources. If M UEs among Y UEs feedback ACK (ACK/NACK feedback mode), or M UEs among Y UEs do not feedback (NACK-only feedback) model).
- M UEs among Y UEs feedback ACK (ACK/NACK feedback mode), or M UEs among Y UEs do not feedback (NACK-only feedback) model).
- the base station sends TB2
- it dynamically adjusts the number of repeated transmissions of TB2 and indicates the number of repetitions through the PDCCH.
- the base station sends TB1 to 100 UEs through PTM and repeats it 4 times, and 90 UEs feedback ACK on the PUCCH, then when the base station sends TB2, it only repeats it 2 times.
- the number of repetitions is adjusted based on the number of UEs that feedback NACK. If M UEs among Y UEs feedback NACK (both ACK/NACK and NACK-only feedback modes are available), when the base station sends TB2, it dynamically adjusts the number of repeated transmissions of TB2 and indicates the number of repetitions through the PDCCH.
- the base station sends TB1 to 100 UEs four times and 10 UEs respond with NACK, then when the base station sends TB2, it can only send TB2 twice.
- the number of repeated transmissions of one PDSCH/TB in each cycle is N
- the repetition interval is G
- N and G are both positive integers.
- N repetitions there are corresponding PUCCH resources for the UE to report feedback information.
- the UE When the UE receives a TB within a cycle, it can decide whether to continue to receive the next repetition of this TB based on each reception.
- the UE when receiving TB1, the UE first receives the first transmission of TB1. If the decoding is successful, the UE will no longer receive the remaining two transmissions of TB1. The UE feeds back ACK on the PUCCH resource (ACK/NACK feedback mode) or does not feed back (NACK-only feedback mode).
- the UE when the UE receives TB3, it does not receive the first transmission of TB3 due to some reasons, so it receives TB3 at the second transmission position of TB3; if the decoding fails, it continues in the third transmission.
- Location receives TB3.
- the UE determines the feedback information on the PUCCH based on the last two receptions of TB3 and whether the decoding is correct; if neither is decoded correctly, NACK is fed back.
- the embodiment of the present application provides a method for repeatedly sending TBs in a broadcast multicast service.
- Multiple uplink feedback resources are configured for multiple repeated transmissions of a TB, and the base station adjusts the remaining repeated transmissions of this TB based on the feedback information.
- the base station can dynamically adjust the number of repeated transmissions of the next TB based on the feedback of the previous TB.
- the UE can also decide whether to continue to receive the remaining repeated transmissions of this TB based on the reception/decoding situation of the current TB.
- This solution also designs the UE receiving behavior for the repeated transmission of semi-persistent scheduling SPS.
- the design of the embodiment of the present application can adjust parameter information such as the number of repeated transmissions and intervals in real time, and extremely flexibly use feedback information to make changes flexibly, which greatly improves resource utilization efficiency. In addition, it can also ensure the reliability of transmission. Generate redundant transmission.
- Figure 19 is a schematic structural diagram of a communication device 1900 according to an embodiment of the present application.
- the communication device 1900 includes a processor 1910, and the processor 1910 can call and run a computer program from the memory, so that the communication device 1900 implements the method in the embodiment of the present application.
- communication device 1900 may also include memory 1920.
- the processor 1910 can call and run the computer program from the memory 1920, so that the communication device 1900 implements the method in the embodiment of the present application.
- the memory 1920 may be a separate device independent of the processor 1910, or may be integrated into the processor 1910.
- the communication device 1900 may also include a transceiver 1930, and the processor 1910 may control the transceiver 1930 to communicate with other devices. Specifically, the communication device 1900 may send information or data to other devices, or receive information sent by other devices. information or data.
- the transceiver 1930 may include a transmitter and a receiver.
- the transceiver 1930 may further include an antenna, and the number of antennas may be one or more.
- the communication device 1900 may be a network device according to the embodiment of the present application, and the communication device 1900 may implement the corresponding processes implemented by the network device in the various methods of the embodiment of the present application. For the sake of brevity, the communication device 1900 will not be mentioned here. Again.
- the communication device 1900 can be a terminal device in the embodiment of the present application, and the communication device 1900 can implement the corresponding processes implemented by the terminal device in the various methods of the embodiment of the present application. For the sake of brevity, this is not mentioned here. Again.
- Figure 20 is a schematic structural diagram of a chip 2000 according to an embodiment of the present application.
- the chip 2000 includes a processor 2010, and the processor 2010 can call and run a computer program from the memory to implement the method in the embodiment of the present application.
- chip 2000 may also include memory 2020.
- the processor 2010 can call and run the computer program from the memory 2020 to implement the method executed by the terminal device or the network device in the embodiment of the present application.
- the memory 2020 may be a separate device independent of the processor 2010 , or may be integrated into the processor 2010 .
- the chip 2000 may also include an input interface 2030.
- the processor 2010 can control the input interface 2030 to communicate with other devices or chips. Specifically, it can obtain information or data sent by other devices or chips.
- the chip 2000 may also include an output interface 2040.
- the processor 2010 can control the output interface 2040 to communicate with other devices or chips. Specifically, it can output information or data to other devices or chips.
- the chip can be applied to the network device in the embodiment of the present application, and the chip can implement the corresponding processes implemented by the network device in the various methods of the embodiment of the present application. For the sake of simplicity, they will not be described again. .
- the chip can be applied to the terminal device in the embodiment of the present application, and the chip can implement the corresponding processes implemented by the terminal device in each method of the embodiment of the present application. For the sake of brevity, details will not be repeated here. .
- the chips used in network equipment and terminal equipment can be the same chip or different chips.
- chips mentioned in the embodiments of this application may also be called system-on-chip, system-on-a-chip, system-on-chip or system-on-chip, etc.
- the processor mentioned above can be a general-purpose processor, a digital signal processor (DSP), an off-the-shelf programmable gate array (FPGA), an application specific integrated circuit (ASIC), or Other programmable logic devices, transistor logic devices, discrete hardware components, etc.
- DSP digital signal processor
- FPGA off-the-shelf programmable gate array
- ASIC application specific integrated circuit
- the above-mentioned general processor may be a microprocessor or any conventional processor.
- non-volatile memory may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory.
- non-volatile memory can be read-only memory (ROM), programmable ROM (PROM), erasable programmable read-only memory (erasable PROM, EPROM), electrically removable memory. Erase electrically programmable read-only memory (EPROM, EEPROM) or flash memory.
- Volatile memory can be random access memory (RAM).
- the memory in the embodiment of the present application can also be a static random access memory (static RAM, SRAM), a dynamic random access memory (dynamic RAM, DRAM), Synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection Dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM) and so on. That is, memories in embodiments of the present application are intended to include, but are not limited to, these and any other suitable types of memories.
- Figure 21 is a schematic block diagram of a communication system 2100 according to an embodiment of the present application.
- the communication system 2100 includes a terminal device 2110 and a network device 2120.
- the terminal device 2110 is configured to perform subsequent repeated transmission related processing based on the first number of repeated transmissions of downlink data and the transmission status of the downlink data;
- the network device 2120 is configured to perform subsequent repeated transmission related processing based on the first number of repeated transmissions of the downlink data and the feedback status of the downlink data.
- the terminal device 2110 can be used to implement the corresponding functions implemented by the terminal device in the above method
- the network device 2120 can be used to implement the corresponding functions implemented by the network device in the above method.
- no further details will be given here.
- the computer program product includes one or more computer instructions.
- the computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
- the computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted over a wired connection from a website, computer, server, or data center (such as coaxial cable, optical fiber, Digital Subscriber Line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) means to transmit to another website, computer, server or data center.
- the computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center integrated with one or more available media.
- the available media may be magnetic media (eg, floppy disk, hard disk, tape), optical media (eg, DVD), or semiconductor media (eg, Solid State Disk (SSD)), etc.
- the size of the sequence numbers of the above-mentioned processes does not mean the order of execution.
- the execution order of each process should be determined by its functions and internal logic, and should not be used in the embodiments of the present application.
- the implementation process constitutes any limitation.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
本申请涉及一种重复传输方法、终端设备和网络设备。该重复传输方法可以包括:终端设备根据下行数据的第一重复传输次数和该下行数据的传输情况,执行后续的重复传输相关处理。本申请实施例,根据下行数据的第一重复传输次数和该下行数据的传输情况,能够合理地执行后续的重复传输相关处理,节约传输资源。
Description
本申请涉及通信领域,更具体地,涉及一种重复传输方法、终端设备和网络设备。
在一些通信业务例如多媒体广播多播服务(Multimedia Broadcast Multicast Services,MBMS)、多播广播服务(multi broadcast service,MBS)等中,可能需要进行重复传输。通常,如果确定了一个MBS业务的重复传输次数,则在信令更新前的较长一段时间内,按照该重复传输次数进行重复传输,容易造成传输资源的浪费。
发明内容
本申请实施例提供一种重复传输方法、终端设备和网络设备。
本申请实施例提供一种重复传输方法,包括:终端设备根据下行数据的第一重复传输次数和该下行数据的传输情况,执行后续的重复传输相关处理。
本申请实施例提供一种重复传输方法,包括:网络设备根据下行数据的第一重复传输次数和该下行数据的反馈情况,执行后续的重复传输相关处理。
本申请实施例提供一种终端设备,包括:处理单元,用于根据下行数据的第一重复传输次数和该下行数据的传输情况,执行后续的重复传输相关处理。
本申请实施例提供一种网络设备,包括:处理单元,用于根据下行数据的第一重复传输次数和该下行数据的反馈情况,执行后续的重复传输相关处理。
本申请实施例提供一种终端设备,包括处理器和存储器。该存储器用于存储计算机程序,该处理器用于调用并运行该存储器中存储的计算机程序,以使该终端设备执行上述的重复传输方法。
本申请实施例提供一种网络设备,包括处理器和存储器。该存储器用于存储计算机程序,该处理器用于调用并运行该存储器中存储的计算机程序,以使该网络设备执行上述的重复传输方法。
本申请实施例提供一种芯片,用于实现上述的重复传输方法。
具体地,该芯片包括:处理器,用于从存储器中调用并运行计算机程序,使得安装有该芯片的设备执行上述的重复传输方法。
本申请实施例提供一种计算机可读存储介质,用于存储计算机程序,当该计算机程序被设备运行时使得该设备执行上述的重复传输方法。
本申请实施例提供一种计算机程序产品,包括计算机程序指令,该计算机程序指令使得计算机执行上述的重复传输方法。
本申请实施例提供一种计算机程序,当其在计算机上运行时,使得计算机执行上述的重复传输方法。
本申请实施例,根据下行数据的第一重复传输次数和该下行数据的传输情况,能够合理地执行后续的重复传输相关处理,节约传输资源。
图1是根据本申请实施例的应用场景的示意图。
图2a至图2c是BWP的示例的示意图。
图3是根据本申请实施例的SC-PTM的示意图。
图4a至图4c是根据本申请实施例的NR MBS调度方式的示意图。
图5是根据本申请一实施例的重复传输方法的示意性流程图。
图6是根据本申请另一实施例的重复传输方法的示意性流程图。
图7是根据本申请另一实施例的重复传输方法的示意性流程图。
图8是根据本申请一实施例的重复传输方法的示意性流程图。
图9是根据本申请另一实施例的重复传输方法的示意性流程图。
图10是根据本申请另一实施例的重复传输方法的示意性流程图。
图11是根据本申请一实施例的终端设备的示意性框图。
图12是根据本申请另一实施例的终端设备的示意性框图。
图13是根据本申请一实施例的网络设备的示意性框图。
图14是根据本申请另一实施例的网络设备的示意性框图。
图15是根据本申请实施例的配置一个上行反馈资源PUCCH的示意图。
图16是根据本申请实施例的配置两个上行反馈资源PUCCH的示意图。
图17是根据本申请实施例的通过PTM向一组UE发送TB1的示意图。
图18是根据本申请实施例的SPS中TB重复传输的示意图。
图19是根据本申请实施例的通信设备示意性框图。
图20是根据本申请实施例的芯片的示意性框图。
图21是根据本申请实施例的通信***的示意性框图。
下面将结合本申请实施例中的附图,对本申请实施例中的技术方案进行描述。
本申请实施例的技术方案可以应用于各种通信***,例如:全球移动通讯(Global System of Mobile communication,GSM)***、码分多址(Code Division Multiple Access,CDMA)***、宽带码分多址(Wideband Code Division Multiple Access,WCDMA)***、通用分组无线业务(General Packet Radio Service,GPRS)、长期演进(Long Term Evolution,LTE)***、先进的长期演进(Advanced long term evolution,LTE-A)***、新无线(New Radio,NR)***、NR***的演进***、非授权频谱上的LTE(LTE-based access to unlicensed spectrum,LTE-U)***、非授权频谱上的NR(NR-based access to unlicensed spectrum,NR-U)***、非地面通信网络(Non-Terrestrial Networks,NTN)***、通用移动通信***(Universal Mobile Telecommunication System,UMTS)、无线局域网(Wireless Local Area Networks,WLAN)、无线保真(Wireless Fidelity,WiFi)、第五代通信(5th-Generation,5G)***或其他通信***等。
通常来说,传统的通信***支持的连接数有限,也易于实现,然而,随着通信技术的发展,移动通信***将不仅支持传统的通信,还将支持例如,设备到设备(Device to Device,D2D)通信,机器到机器(Machine to Machine,M2M)通信,机器类型通信(Machine Type Communication,MTC),车辆间(Vehicle to Vehicle,V2V)通信,或车联网(Vehicle to everything,V2X)通信等,本申请实施例也可以应用于这些通信***。
在一种实施方式中,本申请实施例中的通信***可以应用于载波聚合(Carrier Aggregation,CA)场景,也可以应用于双连接(Dual Connectivity,DC)场景,还可以应用于独立(Standalone,SA)布网场景。
在一种实施方式中,本申请实施例中的通信***可以应用于非授权频谱,其中,非授权频谱也可以认为是共享频谱;或者,本申请实施例中的通信***也可以应用于授权频谱,其中,授权频谱也可以认为是非共享频谱。
本申请实施例结合网络设备和终端设备描述了各个实施例,其中,终端设备也可以称为用户设备(User Equipment,UE)、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置等。
终端设备可以是WLAN中的站点(STAION,ST),可以是蜂窝电话、无绳电话、会话启动协议(Session Initiation Protocol,SIP)电话、无线本地环路(Wireless Local Loop,WLL)站、个人数字处理(Personal Digital Assistant,PDA)设备、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备、下一代通信***例如NR网络中的终端设备,或者未来演进的公共陆地移动网络(Public Land Mobile Network,PLMN)网络中的终端设备等。
在本申请实施例中,终端设备可以部署在陆地上,包括室内或室外、手持、穿戴或车载;也可以部署在水面上(如轮船等);还可以部署在空中(例如飞机、气球和卫星上等)。
在本申请实施例中,终端设备可以是手机(Mobile Phone)、平板电脑(Pad)、带无线收发功能的电脑、虚拟现实(Virtual Reality,VR)终端设备、增强现实(Augmented Reality,AR)终端设备、工业控制(industrial control)中的无线终端设备、无人驾驶(self driving)中的无线终端设备、远程医疗(remote medical)中的无线终端设备、智能电网(smart grid)中的无线终端设备、运输安全(transportation safety)中的无线终端设备、智慧城市(smart city)中的无线终端设备或智慧家庭(smart home)中的无线终端设备等。
作为示例而非限定,在本申请实施例中,该终端设备还可以是可穿戴设备。可穿戴设备也可以称为穿戴式智能设备,是应用穿戴式技术对日常穿戴进行智能化设计、开发出可以穿戴的设备的总称,如眼镜、手套、手表、服饰及鞋等。可穿戴设备即直接穿在身上,或是整合到用户的衣服或配件的一种便携式设备。可穿戴设备不仅仅是一种硬件设备,更是通过软件支持以及数据交互、云端交互来实现强大的功能。广义穿戴式智能设备包括功能全、尺寸大、可不依赖智能手机实现完整或者部分的功能,例如:智能手表或智能眼镜等,以及只专注于某一类应用功能,需要和其它设备如智能手机配合使用,如各类进行体征监测的智能手环、智能首饰等。
在本申请实施例中,网络设备可以是用于与移动设备通信的设备,网络设备可以是WLAN中的接 入点(Access Point,AP),GSM或CDMA中的基站(Base Transceiver Station,BTS),也可以是WCDMA中的基站(NodeB,NB),还可以是LTE中的演进型基站(Evolutional Node B,eNB或eNodeB),或者中继站或接入点,或者车载设备、可穿戴设备以及NR网络中的网络设备(gNB)或者未来演进的PLMN网络中的网络设备或者NTN网络中的网络设备等。
作为示例而非限定,在本申请实施例中,网络设备可以具有移动特性,例如网络设备可以为移动的设备。可选地,网络设备可以为卫星、气球站。例如,卫星可以为低地球轨道(low earth orbit,LEO)卫星、中地球轨道(medium earth orbit,MEO)卫星、地球同步轨道(geostationary earth orbit,GEO)卫星、高椭圆轨道(High Elliptical Orbit,HEO)卫星等。可选地,网络设备还可以为设置在陆地、水域等位置的基站。
在本申请实施例中,网络设备可以为小区提供服务,终端设备通过该小区使用的传输资源(例如,频域资源,或者说,频谱资源)与网络设备进行通信,该小区可以是网络设备(例如基站)对应的小区,小区可以属于宏基站,也可以属于小小区(Small cell)对应的基站,这里的小小区可以包括:城市小区(Metro cell)、微小区(Micro cell)、微微小区(Pico cell)、毫微微小区(Femto cell)等,这些小小区具有覆盖范围小、发射功率低的特点,适用于提供高速率的数据传输服务。
图1示例性地示出了一种通信***100。该通信***包括一个网络设备110和两个终端设备120。在一种实施方式中,该通信***100可以包括多个网络设备110,并且每个网络设备110的覆盖范围内可以包括其它数量的终端设备120,本申请实施例对此不做限定。
在一种实施方式中,该通信***100还可以包括移动性管理实体(Mobility Management Entity,MME)、接入与移动性管理功能(Access and Mobility Management Function,AMF)等其他网络实体,本申请实施例对此不作限定。
其中,网络设备又可以包括接入网设备和核心网设备。即无线通信***还包括用于与接入网设备进行通信的多个核心网。接入网设备可以是长期演进(long-term evolution,LTE)***、下一代(移动通信***)(next radio,NR)***或者授权辅助接入长期演进(authorized auxiliary access long-term evolution,LAA-LTE)***中的演进型基站(evolutional node B,简称可以为eNB或e-NodeB)宏基站、微基站(也称为“小基站”)、微微基站、接入站点(access point,AP)、传输站点(transmission point,TP)或新一代基站(new generation Node B,gNodeB)等。
应理解,本申请实施例中网络/***中具有通信功能的设备可称为通信设备。以图1示出的通信***为例,通信设备可包括具有通信功能的网络设备和终端设备,网络设备和终端设备可以为本申请实施例中的具体设备,此处不再赘述;通信设备还可包括通信***中的其他设备,例如网络控制器、移动管理实体等其他网络实体,本申请实施例中对此不做限定。
应理解,本文中术语“***”和“网络”在本文中常被可互换使用。本文中术语“和/或”,仅仅是一种描述关联对象的关联关系,表示可以存在三种关系,例如,A和/或B,可以表示:单独存在A,同时存在A和B,单独存在B这三种情况。另外,本文中字符“/”,一般表示前后关联对象是一种“或”的关系。
应理解,在本申请的实施例中提到的“指示”可以是直接指示,也可以是间接指示,还可以是表示具有关联关系。举例说明,A指示B,可以表示A直接指示B,例如B可以通过A获取;也可以表示A间接指示B,例如A指示C,B可以通过C获取;还可以表示A和B之间具有关联关系。
在本申请实施例的描述中,术语“对应”可表示两者之间具有直接对应或间接对应的关系,也可以表示两者之间具有关联关系,也可以是指示与被指示、配置与被配置等关系。
为便于理解本申请实施例的技术方案,以下对本申请实施例的相关技术进行说明,以下相关技术作为可选方案与本申请实施例的技术方案可以进行任意结合,其均属于本申请实施例的保护范围。
当前,随着人们对速率、延迟、高速移动性、能效的追求以及未来生活中业务的多样性、复杂性,为此第三代合作伙伴计划(3
rd Generation Partnership Project,3GPP)国际标准组织开始研发5G。5G的主要应用场景为:增强移动超宽带(enhanced Mobile Broadband,eMBB)、低时延高可靠通信(Ultra Reliability and Low Latency Communication,URLLC)、大规模机器类通信(Massive Machine Type Communications,mMTC)。
eMBB仍然以用户获得多媒体内容、服务和数据为目标,其需求增长十分迅速。另一方面,由于eMBB可能部署在不同的场景中,便如室内,市区,农村等,其能力和需求的差别也比较大,所以不能一概而论,必须结合具体的部署场景详细分析。URLLC的典型应用包括:工业自动化,电力自动化,远程医疗操作(手术),交通安全保障等。mMTC的典型特点包括:高连接密度,小数据量,时延不敏感业务,模块的低成本和长使用寿命等。
5G网络环境中为了降低空口信令和快速恢复无线连接,快速恢复数据业务的目的,定一个一个新的无线资源控制(Radio Resource Control,RRC)状态,即RRC_INACTIVE状态。这种状态有别于 RRC_IDLE和RRC_ACTIVE状态。
RRC_IDLE:移动性为基于用户设备(User Equipment,UE)的小区选择重选,寻呼由核心网(Core Network,CN)发起,寻呼区域由CN配置。基站侧不存在UE接入层(Access Stratum,AS)上下文。不存在RRC连接。
RRC_CONNECTED:存在RRC连接,基站和UE存在UE AS上下文。网络侧知道UE的位置是具体小区级别的。移动性是网络侧控制的移动性。UE和基站之间可以传输单播数据。
RRC_INACTIVE:移动性为基于UE的小区选择重选,存在CN-新无线电技术(New Radio,NR)之间的连接,UE AS上下文存在某个基站上,寻呼由无线接入网(Radio Access Network,RAN)触发,基于RAN的寻呼区域由RAN管理,网络侧知道UE的位置是基于RAN的寻呼区域级别的。
5G中,最大的信道带宽可以是400MHZ(带宽载波),相比于长期演进(Long Term Evolution,LTE)最大20M带宽来说,带宽很大。如果UE保持工作在宽带载波(wideband carrier)上,则UE的功率消耗是很大的。所以建议UE的RF带宽可以根据UE实际的吞吐量来调整。为此引入带宽部分(BandWidth Part,BWP)的动机是优化UE的功率消耗。例如UE的速率很低,可以给UE配置小一点的带宽(图2a),如果UE速率要求很高,则可以给UE配置大一点的带宽(图2b)。如果UE支持高速率,或者操作在载波聚合(Carrier Aggregation,CA)模式下,可以给配置多个BWP(图2c)。BWP的另一个目的是触发一个小区中多个基础参数集(numerology)共存。
目前空闲(idle)状态或者非激活的(inactive)状态的UE驻留在初始(initial)BWP上。这个BWP对于idle状态或者inactive状态UE是可见的。在这个BWP里面可以获取主信息块(Master Information Block,MIB),剩余最小***信息(Remaining Minimum System Information,RMSI),开放***互联(Open Systems Interconnection,OSI)以及寻呼(paging)等信息。
NR多媒体广播多播服务(Multimedia Broadcast Multicast Services,MBMS)/多播广播服务(multi broadcast service,MBS)的公共频域资源(common frequency resource,CFR)。
CFR是在NR MBS讨论过程中引入的一个设计概念,为了区别于BWP。CFR是位于载波上的一段连续的频域资源集合,用于接收MBS业务。从单个UE的角度来看,一个CFR是一个连续的频域资源集合,用于接收下行MBS业务数据。从***角度来看,CFR用于发送MBS业务数据,处于连接态(RRC_CONNECTED)的一组UE在CFR中接收MBS的组播/多播,处于非连接态(RRC_IDLE/RRC_INACTIVE)的UE在CFR上接收MBS的广播。
LTE中的MBMS和单小区点到多点(Single Cell Point To Multiploint,SC-PTM)***
多媒体广播多播服务(MBMS)是在3GPP版本6(Release 6,R6)中引入的一项业务。多媒体广播多播服务是一种通过共享网络资源从一个数据源向多个用户设备传送数据的技术,在提供多媒体业务的同时能有效地利用网络资源,实现较高速率(256kbps)的多媒体业务广播和组播。
由于3GPP R6中的MBMS频谱效率较低,不足以有效地承载和支撑手机电视类型业务的运营。因此在无线接入网长期演进标准(Long Term Evolution,LTE)项目中,3GPP明确提出增强对下行高速多媒体广播多播服务业务的支持能力,并确定了对物理层和空中接口的设计要求。
eMBMS是R9引入到LTE网络的。eMBMS提出了单频网络(Single Frequency Network,SFN)的概念,即采用统一频率在所有小区同时发送数据,但是要保证小区间的同步。这种方式可以极大的提高小区整体信噪比分布,频谱效率也会相应的大幅提高。并基于互联网协议(Internet Protocol,IP)多播协议实现业务的广播和多播。
在LTE/长期演进高阶(Long Term Evolution Advanced,LTE-A)中,MBMS只有广播承载模式,没有多播承载模式。
MBMS业务的接收适用于RRC_CONNECTED或者RRC_IDLE状态的UE。
如图3所示,R13中引入SC-PTM。SC-PTM基于MBMS网络架构,多小区/多播协调实体(Multi-cell/multicast Coordination Entity,MCE)决定采用SC-PTM传输方式还是多媒体广播多播服务单频网络(Multimedia Broadcast multicast service Single Frequency Network,MBSFN)传输方式。
引入新的逻辑信道单小区多播控制信道(Single Cell Multicast Control Channel,SC-MCCH)(逻辑信道标识(logical channel identify,LCID)=11001)和单小区多播传输信道(Single Cell Multicast Transport Channel,SC-MTCH)(LCID=11001),映射到DL-SCH传输信道,物理下行共享信道(Physical Downlink Shared Channel,PDSCH)物理信道上。SC-MCCH和SC-MTCH不支持混合自动重传请求(Hybrid Automatic Repeat-reQuest,HARQ)操作。
引入新的***信息块(System Information Block,SIB)类型,SIB20来传输SC-MCCH的配置信息,一个小区只有一个SC-MCCH。配置信息包括:SC-MCCH的修改周期、重复周期,以及无线帧和子帧配置信息。
SC-MCCH调度的无线帧:SFN mod MCCH-重复周期(Repetition Period)=MCCH-Offset(偏移)。
SC-MCCH调度的子帧通过SC-MCCH-Subframe(子帧)指示。
SC-MCCH只传输一个消息SC-PTMConfiguration(配置),该消息用于配置SC-PTM的配置信息。引入新的无线网络临时标识(Radio Network Temporary Identifier,RNTI),单小区RNTI(Single Cell RNTI,SC-RNTI)(可以固定取值FFFC)来识别SC-MCCH在物理下行控制信道(Physical Downlink Control Channel,PDCCH)上的调度信息。
引入新的RNTI,单小区通知RNTI(Single Cell Notification RNTI,SC-N-RNTI)(可以固定取值FFFB),来识别SC-MCCH的变更通知的PDCCH。用下行控制信息(Downlink Control Information,DCI)1C中8个比特(bit)中的一个bit来指示变更通知。修改周期边界定义为SFN mod m=0,其中m是SIB20中配置的修改周期例如sc-mcch-ModificationPeriod;mod表示取模运算。
在NR中,无线链路控制(Radio Link Control,RLC)确认模式(Acknowledgement Mode,AM)模式是带有自动重传请求(Automatic Repeat-reQuest,ARQ)反馈机制的。接收端发送RLC状态报告来反馈RLC包的接收状态为确认(Acknowledge,ACK)或者非确认(No Acknowledge,NACK)。发送端可以重复传输反馈NACK的辅节点(Secondary Node,SN)号的RLC包的重复发送。
下行BWP配置
下行BWP通过BWP-Downlink(带宽部分下行)参数配置。如下面第一段自治***号(Autonomous System Number,ASN).1编码所示,该参数中包括bwp-Id(带宽部分标识)域标识当前BWP的ID,bwp-Common(带宽部分公共)用于配置该下行BWP的公共参数。如下面第二段ASN.1编码所示,其中BWP-DownlinkCommon(带宽部分下行公共)中的genericParameters(通用参数)用于配置该下行BWP的频域起点和包含的物理资源块(Physical Resource Block,PRB)个数。对于一个终端专用单播BWP,BWP-Downlink中的bwp-Dedicated(带宽部分专用)参数将配置该下行BWP上的下行接收参数。如下面第三段ASN.1编码所示,至少包括pdcch-Config(PDCCH配置),pdsch-Config(PDSCH配置),和sps-Config(SPS配置)。第二段ASN.1编码所示,pdcch-Config用于指示该下行BWP上的PDCCH发送方式,pdsch-Config用于指示该下行BWP上的PDSCH发送方式,sps-Config用于指示该下行BWP上的SPS配置。
第一段ASN.1编码:
第二段ASN.1编码:
第三段ASN.1编码:
...,
NR MBS的传播方式
对于MBS业务,基站调度发送的方式包括如下几种:
(1)广播(Broadcast)
通过广播的方式发送MBS业务,适用于终端处于RRC_IDLE/RRC_INACTIVE(非连接)态,以及终端处于RRC_CONNECTED(连接)态。也即是说,通过广播发送的MBS业务,终端无论处于哪种链接状态,只要在覆盖范围内能够接收到就行。
(2)组播/多播(Multicast)
通过组播的方式向一组终端发送MBS业务,适用于组内终端都处于RRC_CONNECTED态,基站通过一对多PTM的发送方式,向一组终端发送相同的MBS业务。
(3)单播(Unicast)
通过单播的方式向每一个终端发送MBS业务,适用于终端处于RRC_CONNECTED态,基站通过一对一PTP的发送方式,向每一个终端发送相同的MBS业务。
NR MBS组调度方式
在NR MBS中需要支持一对多的组播传输,在这种传输方式中,基站需要通过发送公共的下行控制信道调度公共的PDSCH,该公共PDCCH和公共PDSCH在一段公共的频域范围(CFR,Common Frequency Resource)内发送。目前,存在以下备选CFR配置方式:
第一种:CFR配置为MBS专用的BWP,MBS专用BWP和终端的专用单播BWP关联,而且CFR上配置的子载波间隔和循环前缀和终端专用单播BWP上的配置相同。
第二种:CFR配置为终端专用单播BWP范围内连续的多个PRB。
第一种方式的优点在于CFR可以沿用相关的BWP信令配置,有利于减少标准的工作量。但是,由于CFR定义为BWP,如果要求终端同时在专用单播BWP接收单播和在CFR内接收组播,意味着终端需要同时在两个BWP上接收下行传输。然而终端在既定时刻只有能力在一个BWP上接收下行。另外,即使终端在不同的时间接收单播和组播,由于两者位于不同的BWP,也会引入BWP切换时延。第二种方式可以避免BWP切换的问题,但是由于这一方式中CFR是连续的多个PRB,无法沿用目前以BWP为基础的信令配置,需要重新设计CFR的资源范围和上下行传输参数等的配置方式,对标准影响较大。
此外,由于调度公共PDSCH的公共PDCCH需要同时发送给多个接收终端,为了保证该多个终端确定的公共PDCCH中承载的公共DCI的比特数相同,终端不能根据各自的专用单播BWP的配置确定公共DCI的比特数。另外,由于CFR的PRB个数可能和终端当前配置的初始BWP或CORESET(ControlResourceSet,控制资源集)#0(COntrol REsource SET 0)不同,终端也无法通过初始BWP或CORESET#0确定公共DCI的比特数。所以,不可避免的,公共DCI的比特数可能和终端在相关USS或CSS中接收的DCI比特数不同。然后,为了降低终端的实现复杂度,目前终端在一个小区内最多只能接收4个不同比特数的DCI,其中,由小区专属RNTI(Cell RNTI,C-RNTI)加扰的DCI比特数不超过3种。
NR MBS组调度的方式
如图4a、图4b和图4c所示,可以有如下三种调度传输MBS业务的方式,其中PTM1和点对点传输(Point to Point,PTP)已经支持。组共享PDCCH/PDSCH是指基站在一套时频资源上发送的PDCCH/PDSCH,能够被同一组的多个UE接收。本方案中提及的PTM调度方式可以指PTM1。
PTM 1:对于连接态的同一组的多个UE,使用组共享PDCCH调度组共享PDSCH,其中组共享PDCCH的循环冗余校验(Cyclic Redundancy Check,CRC)使用组共享RNTI加扰,组共享PDSCH使用同一个组共享RNTI加扰。
PTM 2:对于连接态的同一组的多个UE,对每个UE使用UE专属PDCCH调度组共享PDSCH,其中UE专属PDCCH的CRC使用UE专属RNTI(即C-RNTI)加扰,组共享PDSCH使用组共享RNTI加扰。
PTP:对于连接态UE,对每个UE使用UE专属PDCCH调度UE专属PDSCH,其中UE专属PDCCH的CRC使用UE专属RNTI(即C-RNTI)加扰,UE专属PDSCH使用UE专属RNTI(即C-RNTI)加扰。
NR MBS组调度的传输方式
MBS业务在连接态基于HARQ-ACK反馈的重传机制可以支持如下几种方式:
方式一:初传PTM1+重传PTM1
方式二:初传PTM1+重传PTP
NR MBS组播和单播使用HARQ过程ID(HARQ process ID,HPID)的方式
组播/多播和单播之间共享***的HPID(HARQ process ID:0~15),具体如何分配HPID由基站实现决定。如果HPID#1首先被分配给MBS业务的一个传输块(Transport Block,TB)1的传输使用,当TB1的初传和潜在重传都结束,基站会将HPID#1继续分配给TB2的传输使用,此时TB2用于UE3的单播传输。当TB2的初传和潜在重传都结束,基站会将HPID#1继续分配给TB3的传输使用,此时TB3用于MBS业务的传输。
HPID和新的数据标识(New Data Indicator,NDI)确定初传和重传的方法
HPID和NDI共同确定了当前传输的TB是初传还是重传。例如,当前接收到的HPID#1,对应DCI中携带的NDI=0,
对比前一个收到的HPID#1对应的NDI=1,此时可以确定当前收到的TB为一个新TB的初传。UE会将缓存中存储的上一个TB的数据信息清空,然后将新收到的TB的初传以及潜在收到的重传存入缓存中,以供软合并使用。
对比前一个收到的HPID#1对应的NDI=0,此时可以确定当前收到的TB为重传。
相关技术中,网络侧通过配置确定一个MBS业务的TB重复传输次数。一旦配置确定,如一个TB重复4次,则在信令更新前的较长一段时间内,这个业务对应的所有TB的重复传输次数都是4次。此外,每个TB在重复传输的最后,仅对应配置一次机会在上行反馈资源进行反馈。
相关技术中,TB的重复传输如上所述。TB的重复次数一旦配置确定,短期内就无法改变。当信道条件非常好时,所有UE接收一个TB时,接收一次或两次就可以正确解码,剩下的TB重复传输显然就冗余了,而且占用了大量的下行传输资源,造成浪费。此外,对于每一个TB的反馈,都是在重复传输的末尾统一对一个TB进行反馈。如果一个TB的重复传输次数为8次,那么UE需要在8次传输完以后才能针对这个TB进行反馈。如果UE在第一次就解码成功,需要等待的时间会非常久,造成较长时间的延时。在相关技术中,一个TB的多次重复传输,是要求UE都必须接收的,时刻让UE多次接收实际上会让UE不停的解码,不仅费电,而且也不利于资源的有效利用。
图5是根据本申请一实施例的重复传输方法500的示意性流程图。该方法可选地可以应用于图1所示的***,但并不仅限于此。该方法包括以下内容的至少部分内容。
S510、终端设备根据下行数据的第一重复传输次数和该下行数据的传输情况,执行后续的重复传输相关处理。
在一种实施方式中,该下行数据在传输块TB和/或物理下行共享信道PDSCH中。
在本申请实施例中,终端设备可以根据TB的第一重复传输次数,以及该TB的传输情况,执行后续的该TB的重复传输相关处理。终端设备可以根据PDSCH的第一重复传输次数,以及该PDSCH的传输情况,执行后续的该PDSCH的重复传输相关处理。
在本申请实施例中,终端设备例如UE执行后续的重复传输相关处理可以包括多种,主要可以包括在接收到本次TB和/或PDSCH之后,UE执行的与该TB和/或该PDSCH的重复传输相关的一些操作。例如,停止接收重复传输、继续接收重复传输、进行上行反馈等。
在一种实施方式中,执行后续的重复传输相关处理,包括:确定是否接收重复传输的该下行数据。
在本申请实施例中,UE可以根据是否收到下行数据、收到的下行数据的当前次数、第一重复传输次数N(即总次数),以及收到的下行数据后的解码情况的一种或者多种,来确定是否继续接收网络设备重复传输的该下行数据。
在一种实施方式中,确定是否接收重复传输的该下行数据,包括:
方式1:该终端设备在收到的至少一次该下行数据解码成功的情况下,不再接收重复传输的该下行数据。
例如,如果TB1的当前传输次数为第2次,第一重复传输次数N为6次,并且,UE对本次TB1解码成功,则可以不再接收网络设备第3次到第6次的TB1的重复传输。当然,网络侧也可以在获知UE对第2次TB1解码成功之后,不再重复传输第3次到第6次的TB1。
方式2:该终端设备在收到的该下行数据解码失败的情况下,继续接收重复传输的该下行数据,直至当前传输次数达到第一重复传输次数或收到的下行数据解码成功为止。
再如,如果TB2的当前传输次数为第2次,第一重复传输次数N为6次,但是UE对本次TB2解码失败,则UE继续接收第3次TB2的重复传输。如果收到的第3次TB2解码成功,则可以不再接收网络设备第4次到第6次的TB2的重复传输。如果收到的第3次到第6次TB2均解码失败,则停止接收TB2的重复传输。
方式3:该终端设备在未收到的下行数据的情况下,继续接收重复传输的该下行数据,直至当前传输次数达到第一重复传输次数或收到的下行数据解码成功为止。
再如,如果TB3的当前传输次数为第3次,第一重复传输次数N为6次,但是UE未收到第3次TB3的重复传输,则UE继续接收第4次TB3的重复传输。如果收到的第4次TB3解码成功,则可以不再接收网络设备第5次到第6次的TB3的重复传输。如果收到的第4次到第6次TB3均解码失败,则停止接收TB2的重复传输。
在一种实施方式中,如图6所示,该方法600包括:S610、该终端设备接收第一指示信息,该第一指示信息中包括该第一重复传输次数和/或第一重复间隔。
在本申请实施例中,该方法600和上述的方法500的步骤可以单独实施,也可以结合。
在本申请实施例中,UE可以从网络设备例如基站接收第一指示信息,该指示信息可以是动态配置的,也可以是半静态配置的。第一重复传输次数可以是网络设备重复传输下行数据的总次数,也可以是终端设备接收下行数据的重复传输的总次数。网络设备重复传输下行数据的总次数与终端设备接收下行数据的重复传输的总次数,可以相同,也可以不同。第一重复间隔可以表示下行数据的重复传输的间隔,第一重复间隔可以是时隙,也可以是符号。
在一种实施方式中,该第一指示信息在以下至少之一中:无线资源控制(RRC)信令;下行控制信息(DCI)。
在本申请实施例中,RRC信令是一种高层配置信息。网络设备可以先通过高层配置信息将第一指示信息下发至终端设备。DCI是一种动态指示方式,网络设备可以向终端设备发送PDCCH,在PDCCH中携带DCI,在DCI中携带第一指示信息。在终端设备中可以利用该第一指示信息中包括该第一重复传输次数和/或第一重复间隔,执行后续的重复传输相关处理。
在本申请实施例中,终端设备的反馈模式可以是确认/非确认(ACK/NACK)反馈模式,也可以是仅非确认(NACK-only)反馈模式。反馈模式也可以称为反馈方式。在ACK/NACK反馈模式中,终端设备可以向网络设备反馈确认信息,也可以向网络设备反馈非确认信息。这种情况下,终端设备发送的上行反馈信息可能是确认(ACK)信息,也可能是非确认(NACK)信息。在NACK-only反馈模式中,如果是确认状态,终端设备不反馈信息,仅在非确认状态,向网络设备反馈非确认信息。
在一种实施方式中,执行后续的重复传输相关处理,还包括:
该终端设备在收到n次下行数据后,发送一次上行反馈信息;其中,n大于或等于1,且n小于或等于该第一重复传输次数N,N大于或等于1。
在一种实施方式中,该上行反馈信息在物理上行控制信道(Physical Uplink Control Channel,PUCCH)和/或物理上行共享信道(Physical Uplink Shared Channel,PUSCH)中。
例如,终端设备可以在每收到1次TB或PDSCH后,向网络设备发送一次携带上行反馈信息的PUCCH。再如,终端设备可以在每收到2次TB或PDSCH后,向网络设备发送1次携带上行反馈信息的PUCCH。
在一种实施方式中,该终端设备在收到n次下行数据后,发送一次上行反馈信息,包括:
在收到的该n次下行数据中的至少一次下行数据解码成功的情况下,该终端设备发送包括确认信息的该上行反馈信息;和/或
在收到的该n次下行数据中的m次下行数据解码失败的情况下,该终端设备发送包括非确认信息的该上行反馈信息;其中,m大于或等于1且m小于或等于n。
在本申请实施例中,终端设备每收到n次下行数据进行一次反馈。m可以表示解码失败次数阈值,解码失败次数大于该阈值终端设备可以反馈非确认信息。
例如,ACK/NACK反馈模式中,终端设备每收到3次TB或PDSCH反馈1次上行反馈信息。如果这3次收到的TB或PDSCH均解码成功,或者有1次或2次解码成功,终端设备可以向网络设备发送包括ACK信息的PUCCH。如果这3次收到的TB或PDSCH均解码失败或者解码失败的次数大于某个阈值例如2次,则终端设备发送包括NACK信息的PUCCH。
再如,NACK-only反馈模式中,终端设备每收到3次TB或PDSCH反馈1次上行反馈信息。如果这3次收到的TB或PDSCH均解码成功,或者有1次或2次解码成功,终端设备不发送PUCCH。如果这3次收到的TB或PDSCH均解码失败或者解码失败的次数大于某个阈值例如2次,则终端设备发送包括NACK信息的PUCCH。
在一种实施方式中,在收到的s次下行数据中的至少一次下行数据解码成功的情况下,该终端设备不接收重复传输的该下行数据,其中,s大于或等于1,且s小于该第一重复传输次数N。
在本申请实施例中,s可以表示终端设备收到下行数据的次数。例如,第一重复传输次数N等于4,终端设备收到第1次TB,并且该TB解码成功,则不再接收第2次至第4次TB的重复传输。再如, 第一重复传输次数N等于5,终端设备未收到第1次PDSCH,则终端设备继续接收第2次PDSCH的重复传输。如果第2次PDSCH解码成功,则终端设备不再接收第3次、第4次和第5次PDSCH的重复传输。再如,第一重复传输次数N等于5,终端设备收到第1次、第2次和第3次PDSCH,并且第2次PDSCH解码成功,则终端设备不再接收第4次和第5次PDSCH的重复传输。
在一种实施方式中,如图7所示,该方法700包括:S710、该终端设备接收第二指示信息,该第二指示信息包括第二重复传输次数和/或第二重复间隔,其中,该第二重复传输次数是根据该下行数据的反馈情况和该第一重复传输次数确定的,该第二重复传输次数与该第一重复传输次数不同。
在本申请实施例中,该方法700和上述的方法500和/或600的步骤可以单独实施,也可以结合。例如,第一指示信息可以指示当前的TB和/或PDSCH的重复传输次数为第一重复传输次数。第二指示信息可以指示下一个TB和/或PDSCH的重复传输次数被调整为第二重复传输次数。再如,对于当前的TB和/或PDSCH,终端设备可以根据下行数据的第一重复传输次数和该下行数据的传输情况确定是否接收重复传输的该下行数据,并对于下一个TB和/或PDSCH采用下行数据的第二重复传输次数和该下行数据的传输情况确定是否接收重复传输的该下行数据。再如,对于当前的TB和/或PDSCH,终端设备按照第一重复传输次数全部进行接收,对于下一个TB和/或PDSCH采用下行数据的第二重复传输次数和该下行数据的传输情况确定是否接收重复传输的该下行数据。
在本申请实施例中,如果终端设备收到并成功解码下行数据的当前传输次数,小于第一重复传输次数N,网络设备可以将第一重复传输次数N适当调小得到第二重复传输次数N’。如果终端设备N次不能收到并成功解码下行数据,网络设备可以将第一重复传输次数N适当调大得到第二重复传输次数N’。
在一种实施方式中,该第二指示信息在DCI。
在本申请实施例中,第二重复传输次数可以采用动态指示的方式进行配置。例如,终端设备从网络设备接收PDCCH,该PDCCH中携带DCI,该DCI中携带第二指示信息。携带第一指示信息的DCI和携带第二指示信息的DCI可以不同,也可以相同。
在本申请实施例中,在多播、组播等相关业务场景中,网络设备可能一次向多个终端设备发送相同的下行数据。可能有部分终端设备能够接收并成功解码该下行数据,另一部分终端设备未收到或未成功解码该下行数据。此外,终端设备的反馈模式还包括上述的ACK/NACK反馈模式和NACK-only反馈模式。因此,终端设备的具体反馈情况也可能存在多种。基于终端设备的不同的反馈情况,网络设备可能需要调整重复传输次数的方式。
在一种实施方式中,该下行数据的反馈情况满足以下至少之一,则第一重复次数次数被网络设备调整为第二重复传输次数:
M个目标终端设备的上行反馈信息包括确认信息(ACK/NACK反馈模式);
M个目标终端设备未反馈上行反馈信息(NACK-only反馈模式);
P个目标终端设备的上行反馈信息包括非确认信息(ACK/NACK反馈模式或NACK-only反馈模式);
P个目标终端设备未反馈上行反馈信息(NACK-only反馈模式);
其中,M小于或等于网络设备通过点到多点(PTM)发送的目标终端设备的总数Y,且M大于或等于第一阈值;和/或,M小于或等于该第一重复传输次数N,且M与Y的比值大于或等于第二阈值;
其中,P小于或等于Y,且P小于或等于第三阈值;和/或,P小于或等于该第一重复传输次数N,且P与Y的比值小于或等于第四阈值。
在本申请实施例中,网络设备调整重复传输次数的具体示例,可以参见下述关于网络设备的实施例的相关描述。
图8是根据本申请一实施例的重复传输方法800的示意性流程图。该方法可选地可以应用于图1所示的***,但并不仅限于此。该方法包括以下内容的至少部分内容。
S810、网络设备根据下行数据的第一重复传输次数和该下行数据的反馈情况,执行后续的重复传输相关处理。
在一种实施方式中,执行后续的重复传输相关处理,包括:确定是否重复传输该下行数据。
在一种实施方式中,确定是否重复传输该下行数据,包括以下至少之一:
该网络设备在收到的针对该下行数据的至少一次上行反馈信息中包括确认信息的情况下,不重复传输该下行数据;
该网络设备在未收到针对该下行数据的上行反馈信息的情况下,不重复传输该下行数据;
该网络设备在收到针对该下行数据的上行反馈信息中包括非确认信息的情况下,重复传输该下行数据,直至收到针对该下行数据的上行反馈信息中包括确认信息或当前传输次数达到第一重复传输次数为止。
在一种实施方式中,如图9所示,该方法900包括:S910、该网络设备发送第一指示信息,该第 一指示信息中包括该第一重复传输次数和/或第一重复间隔。
在本申请实施例中,该方法900和上述的方法800的步骤可以单独实施,也可以结合。
在一种实施方式中,该第一指示信息在以下至少之一中:RRC信令;DCI。
在一种实施方式中,该方法还包括:该网络设备在发送n次下行数据后,接收一次上行反馈信息;其中,n大于或等于1,且n小于或等于该第一重复传输次数N,N大于或等于1。
在一种实施方式中,该网络设备在发送n次下行数据后,接收一次上行反馈信息,包括:
在发送的该n次下行数据中的至少一次下行数据解码成功的情况下,该网络设备接收包括确认信息的该上行反馈信息;和/或
在发送的该n次下行数据中的m次下行数据解码失败的情况下,该网络设备接收包括非确认信息的该上行反馈信息;其中,m大于或等于1且小于或等于n。
在一种实施方式中,执行后续的重复传输相关处理,包括:
该网络设备根据该下行数据的反馈情况调整该第一重复传输次数。
在一种实施方式中,该网络设备根据该下行数据的反馈情况调整该第一重复传输次数,包括:
该网络设备根据该下行数据的反馈情况,将该第一重复传输次数调整为第二重复传输次数,该第二重复传输次数与该第一重复传输次数不同。
在一种实施方式中,该下行数据的反馈情况满足以下至少之一:
M个目标终端设备的上行反馈信息包括确认信息;
M个目标终端设备未反馈上行反馈信息;
P个目标终端设备的上行反馈信息包括非确认信息;
P个目标终端设备未反馈上行反馈信息;
其中,M小于或等于网络设备通过点到多点PTM发送的目标终端设备的总数Y,且M大于或等于第一阈值;和/或,M小于或等于该第一重复传输次数N,且M与Y的比值大于或等于第二阈值;
其中,P小于或等于Y,且P小于或等于第三阈值;和/或,P小于或等于该第一重复传输次数N,且P与Y的比值小于或等于第四阈值。
例如,网络设备向Y个终端设备发送TB1,TB1的第一重复传输次数为N,在ACK/NACK反馈模式下,网络设备在收到M个目标终端设备的上行反馈信息包括ACK信息,M大于设置的成功传输设备数量的第一阈值,并且M小于N,则网络设备将第一重复传输次数调整为第二重复传输次数。这种情况下,第二重复传输次数可以小于第一重复传输次数。具体例如,第一重复传输次数为8,网络设备向40个终端设备发送TB1,收到30个终端设备反馈的ACK信息。假设第一阈值为25,反馈的ACK信息终端设备数量30大于第二阈值,则网络设备将第一重复传输次数调整为第二重复传输次数为4。假设第二阈值为70%,则反馈的ACK信息的终端设备的数量M=30与Y=40的比值为75%大于第二阈值,则网络设备将第一重复传输次数调整为第二重复传输次数为4。
再如,网络设备向Y个终端设备发送TB1,TB1的第一重复传输次数为N,在NACK-only反馈模式下,网络设备在未收到M个目标终端设备的上行反馈信息的情况下,将该第一重复传输次数调整为该第二重复传输次数。具体例如,第一重复传输次数为8,网络设备向40个终端设备发送TB1,未收到30个终端设备反馈的ACK信息。假设第一阈值为25,未反馈信息的终端设备数量30大于第二阈值,则网络设备将第一重复传输次数调整为第二重复传输次数为4。假设第二阈值为70%,则未反馈信息的终端设备的数量M=30与Y=40的比值为75%大于第二阈值,则网络设备将第一重复传输次数调整为第二重复传输次数为4。
再如,网络设备向Y个终端设备发送TB1,TB1的第一重复传输次数为N,在ACK/NACK反馈模式或者NACK-only反馈模式下,网络设备在收到P个目标终端设备的包括NACK信息的上行反馈信息,将该第一重复传输次数调整为该第二重复传输次数。具体例如,第一重复传输次数为8,网络设备向40个终端设备发送TB1,收到30个终端设备反馈的ACK信息,第一阈值为25,则网络设备将第一重复传输次数调整为第二重复传输次数为4。
再如,网络设备向Y个终端设备发送TB1,TB1的第一重复传输次数为N,在NACK-only反馈模式下,网络设备在未收到P个目标终端设备的上行反馈信息的情况下,将该第一重复传输次数调整为该第二重复传输次数。具体例如,第一重复传输次数为8,网络设备向40个终端设备发送TB1,未收到30个终端设备反馈的ACK信息,第一阈值为25,则网络设备将第一重复传输次数调整为第二重复传输次数为4。
上述调整后的第二重复传输次数可以用于本次TB1之后的TB2或TB3等的重复传输。
在一种实施方式中,如图10所示,该方法1000还包括:S1010、该网络设备发送第二指示信息,该第二指示信息包括第二重复传输次数和/或第二重复间隔。
在本申请实施例中,该方法1000和上述的方法800和/或900的步骤可以单独实施,也可以结合。
在一种实施方式中,该第二指示信息在DCI。
在一种实施方式中,该上行反馈信息在PUCCH和/或PUSCH中。
在一种实施方式中,该下行数据在TB和/或PDSCH中。
本实施例的网络设备执行方法800、900、1000的具体示例可以参见上述方法500、600、700的中关于网络设备例如基站的相关描述,为了简洁,在此不再赘述。
图1100是根据本申请一实施例的终端设备1100的示意性框图。该终端设备1100可以包括:
处理单元1110,用于根据下行数据的第一重复传输次数和该下行数据的传输情况,执行后续的重复传输相关处理。
在一种实施方式中,该处理单元用于执行后续的重复传输相关处理,包括:确定是否接收重复传输的该下行数据。
在一种实施方式中,如图12所示,该终端设备1200可以包括上述的处理单元1110,该终端设备1200还包括第一接收单元1210,该处理单元1110用于确定是否接收重复传输的该下行数据,包括:
在收到的至少一次该下行数据解码成功的情况下,指示该第一接收单元1210不再接收重复传输的该下行数据;
在收到的该下行数据解码失败的情况下,指示该第一接收单元1210继续接收重复传输的该下行数据,直至当前传输次数达到第一重复传输次数或收到的下行数据解码成功为止;
在未收到的下行数据的情况下,指示该第一接收单元1210继续接收重复传输的该下行数据,直至当前传输次数达到第一重复传输次数或收到的下行数据解码成功为止。
在一种实施方式中,如图12所示,该终端设备1200还包括:第二接收单元1220,用于接收第一指示信息,该第一指示信息中包括该第一重复传输次数和/或第一重复间隔。
在一种实施方式中,该第一指示信息在以下至少之一中:
无线资源控制(RRC)信令;
下行控制信息(DCI)。
在一种实施方式中,该终端设备还包括发送单元1240,该处理单元1110用于在收到n次下行数据后,指示该发送单元发送一次上行反馈信息;其中,n大于或等于1,且n小于或等于该第一重复传输次数N,N大于或等于1。
在一种实施方式中,该处理单元1110用于在收到n次下行数据后,指示该发送单元发送一次上行反馈信息,包括:
在收到的该n次下行数据中的至少一次下行数据解码成功的情况下,指示该发送单元1240发送包括确认信息的该上行反馈信息;和/或
在收到的该n次下行数据中的m次下行数据解码失败的情况下,指示该发送单元1240发送包括非确认信息的该上行反馈信息;其中,m大于或等于1且m小于或等于n。
在一种实施方式中,该处理单元1110还用于在收到的s次下行数据中的至少一次下行数据解码成功的情况下,指示第一接收单元1210不接收重复传输的该下行数据,其中,s大于或等于1,且s小于该第一重复传输次数N。
在一种实施方式中,如图12所示,该终端设备1200还包括:第三接收单元1230,用于接收第二指示信息,该第二指示信息包括第二重复传输次数和/或第二重复间隔,其中,该第二重复传输次数是根据该下行数据的反馈情况和该第一重复传输次数确定的,该第二重复传输次数与该第一重复传输次数不同。
在一种实施方式中,该第二指示信息在DCI。
在一种实施方式中,该下行数据的反馈情况满足以下至少之一:
M个目标终端设备的上行反馈信息包括确认信息;
M个目标终端设备未反馈上行反馈信息;
P个目标终端设备的上行反馈信息包括非确认信息;
P个目标终端设备未反馈上行反馈信息;
其中,M小于或等于网络设备通过点到多点PTM发送的目标终端设备的总数Y,且M大于或等于第一阈值;和/或,M小于或等于该第一重复传输次数N,且M与Y的比值大于或等于第二阈值;
其中,P小于或等于Y,且P小于或等于第三阈值;和/或,P小于或等于该第一重复传输次数N,且P与Y的比值小于或等于第四阈值。
在一种实施方式中,该上行反馈信息在物理上行控制信道PUCCH和/或物理上行共享信道PUSCH中。
在一种实施方式中,该下行数据在传输块TB和/或物理下行共享信道PDSCH中。
本申请实施例的终端设备1100、1200能够实现前述的方法500、600、700实施例中的终端设备的对应功能。该终端设备1100、1200中的各个模块(子模块、单元或组件等)对应的流程、功能、实现方式以及有益效果,可参见上述方法实施例中的对应描述,在此不再赘述。需要说明,关于申请实施例的终端设备1100、1200中的各个模块(子模块、单元或组件等)所描述的功能,可以由不同的模块(子模块、单元或组件等)实现,也可以由同一个模块(子模块、单元或组件等)实现。
图13是根据本申请一实施例的网络设备1300的示意性框图。该网络设备1300可以包括:
处理单元1310,用于根据下行数据的第一重复传输次数和该下行数据的反馈情况,执行后续的重复传输相关处理。
在一种实施方式中,该处理单元1310用于执行后续的重复传输相关处理,包括:确定是否重复传输该下行数据。
在一种实施方式中,如图14所示,该网络设备1400还包括第一发送单元1410,该处理单元1310还用于确定是否重复传输该下行数据,包括以下至少之一:
在收到的针对该下行数据的至少一次上行反馈信息中包括确认信息的情况下,指示该第一发送单元1410不重复传输该下行数据;
在未收到针对该下行数据的上行反馈信息的情况下,指示该第一发送单元1410不重复传输该下行数据;
在收到针对该下行数据的上行反馈信息中包括非确认信息的情况下,指示该第一发送单元1410重复传输该下行数据,直至收到针对该下行数据的上行反馈信息中包括确认信息或当前传输次数达到第一重复传输次数为止。
在一种实施方式中,如图14所示,该网络设备1400还包括:第二发送单元1420,用于发送第一指示信息,该第一指示信息中包括该第一重复传输次数和/或第一重复间隔。
在一种实施方式中,该第一指示信息在以下至少之一中:RRC信令;DCI。
在一种实施方式中,如图14所示,该网络设备1400还包括:接收单元1430,用于在发送n次下行数据后,接收一次上行反馈信息;其中,n大于或等于1,且n小于或等于该第一重复传输次数N,N大于或等于1。
在一种实施方式中,该接收单元1430用于:
在发送的该n次下行数据中的至少一次下行数据解码成功的情况下,接收包括确认信息的该上行反馈信息;和/或
在发送的该n次下行数据中的m次下行数据解码失败的情况下,接收包括非确认信息的该上行反馈信息;其中,m大于或等于1且小于或等于n。
在一种实施方式中,该处理单元1310还用于执行后续的重复传输相关处理,包括:根据该下行数据的反馈情况调整该第一重复传输次数。
在一种实施方式中,该处理单元1310还用于根据该下行数据的反馈情况调整该第一重复传输次数,包括:根据该下行数据的反馈情况,将该第一重复传输次数调整为第二重复传输次数,该第二重复传输次数与该第一重复传输次数不同。
在一种实施方式中,该下行数据的反馈情况满足以下至少之一:
M个目标终端设备的上行反馈信息包括确认信息;
M个目标终端设备未反馈上行反馈信息;
P个目标终端设备的上行反馈信息包括非确认信息;
P个目标终端设备未反馈上行反馈信息;
其中,M小于或等于网络设备通过点到多点PTM发送的目标终端设备的总数Y,且M大于或等于第一阈值;和/或,M小于或等于该第一重复传输次数N,且M与Y的比值大于或等于第二阈值;
其中,P小于或等于Y,且P小于或等于第三阈值;和/或,P小于或等于该第一重复传输次数N,且P与Y的比值小于或等于第四阈值。
在一种实施方式中,如图14所示,该网络设备1400还包括:第三发送单元1440,用于发送第二指示信息,该第二指示信息包括该第二重复传输次数和/或第二重复间隔。
在一种实施方式中,该第二指示信息在DCI。
在一种实施方式中,该上行反馈信息在PUCCH和/或PUSCH中。
在一种实施方式中,该下行数据在TB和/或PDSCH中。
本申请实施例的网络设备1300、1400能够实现前述的方法800、900、1000实施例中的网络设备的对应功能。该网络设备1300、1400中的各个模块(子模块、单元或组件等)对应的流程、功能、实现方 式以及有益效果,可参见上述方法实施例中的对应描述,在此不再赘述。需要说明,关于申请实施例的网络设备1300、1400中的各个模块(子模块、单元或组件等)所描述的功能,可以由不同的模块(子模块、单元或组件等)实现,也可以由同一个模块(子模块、单元或组件等)实现。
本申请实施例提供的重复传输方法可以是一种广播多播业务中重复发送TB的方法。该方法主要可以包括以下内容:
(1)根据半静态配置一个TB的重复次数和发送间隔。
(2)根据PDCCH指示一个TB的重复次数和发送间隔,且根据前一个TB的HARQ-ACK反馈情况,调整下一个TB的重复次数、发送间隔等参数,并通过PDCCH动态指示当前被调度TB的重复传输信息。
(3)针对一个TB的重复传输,如果存在多次上行反馈,则基站根据当前的反馈信息,决定这个TB剩下的重复传输是否继续发送或不再发送。
(4)在半持续调度(Semi-Persistent Scheduling,SPS,或称为半静态调度)中,通过配置确定每个周期内一个TB的重复传输次数、间隔和时频资源位置。对于一个TB的多次重复传输,UE根据已经收到这个TB的解码是否成功,决定是否接收这个TB剩余的重传;如果UE没有收到一个TB的某次传输,则继续接收这个TB后续的重复传输。
示例1:一个TB,半静态配置反馈次数
(1)根据高层配置参数的配置的指示信息,一个PDSCH/TB重复发送N次,N个PDSCH发送间隔为G,其中N≥1的正整数,G≥0的整数。
(2)根据高层配置参数的配置或PDCCH/DCI的指示信息,一个TB的N次重复发送之后,可以进行上行反馈。
(a)ACK/NACK反馈模式:接收UE在≤N次的接收中,至少有一次解码PDSCH成功,则通过上行资源物理上行控制信道(PUCCH)或物理上行共享信道(PUSCH)向基站反馈ACK;接收UE在≤N次的接收中,没有一次解码PDSCH成功,则通过上行资源PUCCH或PUSCH向基站反馈NACK。或
(b)NACK-only反馈模式:接收UE在≤N次的接收中,至少有一次解码PDSCH成功,则通过上行资源PUCCH或PUSCH向基站不反馈任何信息;接收UE在≤N次的接收中,没有一次解码PDSCH成功,则通过上行资源PUCCH或PUSCH向基站反馈NACK。
(3)如果PDSCH的N次重复传输对应多个上行反馈资源,基站可以根据一组UE(例如Y个UE)的反馈情况来决定是否继续发送剩余的PDSCH重复。
(4)上述配置参数中,一个TB的重复发送次数N≥1的正整数,例如,优先候选取值{2,4,6,8,16}。
(5)上述配置参数中,PDSCH发送间隔G。例如,当G=0时,表示PDSCH的N次重复传输为连续传输,即PDSCH所在的时隙为连续时隙。
示例1-1
(1)如图15,一个TB重复发送4次,此时配置了一个上行反馈资源PUCCH,UE在4次(或少于4次)的接收中,解码PDSCH至少有一次成功,就通过上行资源向基站反馈ACK。UE在4次(或少于4次)的接收中,解码PDSCH没有一次成功,就通过上行资源向基站反馈NACK。
(2)如图16,一个TB重复发送4次,此时配置了两个上行反馈资源PUCCH,分别是前两次重复传输后有一个PUCCH资源,后两次重复传输后有一个PUCCH资源。
一个UE的角度:如果UE在前2次接收的PDSCH中,至少有一次解码成功,且在第一个PUCCH上反馈ACK,则UE可以不接收后两次PDSCH。
基站和所有UE角度(PTM发送的情况):
(a)ACK/NACK反馈:对于前两次PDSCH的发送,所有接收UE的反馈都是ACK,则基站不再发送后两次的PDSCH;对于前两次PDSCH的发送,如果有K(K≥1)个UE反馈了NACK,则基站继续发送后两次的PDSCH。
(b)NACK-only反馈:对于前两次PDSCH的发送,所有UE都没有向基站反馈任何信息(即解码成功),则基站不再发送后两次的PDSCH;对于前两次PDSCH的发送,如果有K(K≥1)个UE反馈了NACK,则基站继续发送后两次的PDSCH。
示例1的一个特例状态:每一次PDSCH后都有一个PUCCH资源供UE发送反馈信息。
示例2:一个TB,动态指示反馈次数
(1)根据PDCCH/DCI的指示信息,指示一个PDSCH/TB的重复发送次数为N次,N个PDSCH发送间隔为G,其中N≥1的正整数,G≥0的整数。
(2)根据前一个TB发送后的反馈情况,如果所有UE或X%以上的UE反馈了ACK(ACK/NACK反馈模式)或没有反馈信息(NACK-only反馈模式),那么在发送下一个TB的时候,重复次数可以由N变 为N’,并且可以在PDCCH中指示更新后的N’信息。其中,X%可以是反馈了ACK(ACK/NACK反馈模式)或没有反馈信息(NACK-only反馈模式)的UE数量与UE总数(PTM场景下)的比值。
示例2-1
(1)如图17所示,基站通过PTM向一组Y(Y正整数)个UE发送TB1时,PDCCH指示了重复次数为4次。
(2)这组UE在PUCCH资源上进行反馈,如果Y个UE中有M个UE反馈了ACK(ACK/NACK反馈模式),或Y个UE中有M个UE都没有反馈(NACK-only反馈模式)。基站在发送TB2时,动态调整TB2的重复发送次数并通过PDCCH指示出重复次数。
例如,基站通过PTM向100个UE发送TB1且重复4次,有90个UE在PUCCH上反馈了ACK,则基站在发送TB2时,仅重复发送2次。
(3)还可以换一种描述:根据反馈NACK的UE个数来决定调整重复次数。如果Y个UE中有M个UE反馈了NACK(ACK/NACK和NACK-only反馈模式都可以),基站在发送TB2时,动态调整TB2的重复发送次数并通过PDCCH指示出重复次数。
例如,基站向100个UE发送TB1重复4次,有10个UE反馈了NACK,则基站在发送TB2时,可以仅重复发送2次TB2。
示例3:SPS中TB重复传输
(1)根据高层配置信息,半持续调度中,每个周期内的一个PDSCH/TB的重复传输次数为N次,重复间隔为G,N和G均为正整数。在N次重复之后对应有PUCCH资源供UE上报反馈信息。
(2)UE在一个周期内接收TB时,可以根据每一次的接收决定是否接续接收这个TB的下一次重复。
(3)如图18所示,UE在接收TB1时,先接收TB1的第一个传输,如果解码成功,则UE不再接收TB1的剩余两次传输。UE在PUCCH资源上反馈ACK(ACK/NACK反馈模式)或这不反馈(NACK-only反馈模式)。
(4)如图18所示,UE在接收TB2时,如果TB2的第一次接收解码失败,则继续接收TB2的第二次传输;如果仍然解码失败,则继续接收第三次传输,直到把本周期内TB2的所有重复传输都接收并解码。UE根据这三次对于TB2的解码决定在PUCCH反馈的信息;如果都没有解码成功,则反馈NACK。
(5)如图18,UE在接收TB3时,由于某些原因没有收到TB3的第一次传输,则在TB3的第二次传输位置接收TB3;如果解码失败,则继续在第三次传输位置接收TB3。UE根据后两次接收TB3以及解码是否正确,决定在PUCCH上的反馈信息;如果都没有解码正确,则反馈NACK。
本申请实施例提供了一种广播多播业务中重复发送TB的方法。为一个TB的多次重复传输配置多个上行反馈资源,基站根据反馈信息来调整这个TB剩余的重复发送。此外,基站可以根据前一个TB的反馈情况来动态调整下一个TB的重复传输次数。UE也可以根据当前TB的接收/解码情况来决定是否继续接收这个TB剩余的重复传输。此方案还针对半持续调度SPS的重复传输设计了UE接收的行为。本申请实施例的设计可以实时调整重复传输的次数、间隔等参数信息,极其灵活的利用反馈信息来灵活改变,大大提高了资源利用效率,此外,还能保证传输的可靠性的基础上,不产生冗余发送。
图19是根据本申请实施例的通信设备1900示意性结构图。该通信设备1900包括处理器1910,处理器1910可以从存储器中调用并运行计算机程序,以使通信设备1900实现本申请实施例中的方法。
在一种实施方式中,通信设备1900还可以包括存储器1920。其中,处理器1910可以从存储器1920中调用并运行计算机程序,以使通信设备1900实现本申请实施例中的方法。
其中,存储器1920可以是独立于处理器1910的一个单独的器件,也可以集成在处理器1910中。
在一种实施方式中,通信设备1900还可以包括收发器1930,处理器1910可以控制该收发器1930与其他设备进行通信,具体地,可以向其他设备发送信息或数据,或接收其他设备发送的信息或数据。
其中,收发器1930可以包括发射机和接收机。收发器1930还可以进一步包括天线,天线的数量可以为一个或多个。
在一种实施方式中,该通信设备1900可为本申请实施例的网络设备,并且该通信设备1900可以实现本申请实施例的各个方法中由网络设备实现的相应流程,为了简洁,在此不再赘述。
在一种实施方式中,该通信设备1900可为本申请实施例的终端设备,并且该通信设备1900可以实现本申请实施例的各个方法中由终端设备实现的相应流程,为了简洁,在此不再赘述。
图20是根据本申请实施例的芯片2000的示意性结构图。该芯片2000包括处理器2010,处理器2010可以从存储器中调用并运行计算机程序,以实现本申请实施例中的方法。
在一种实施方式中,芯片2000还可以包括存储器2020。其中,处理器2010可以从存储器2020中调用并运行计算机程序,以实现本申请实施例中由终端设备或者网络设备执行的方法。
其中,存储器2020可以是独立于处理器2010的一个单独的器件,也可以集成在处理器2010中。
在一种实施方式中,该芯片2000还可以包括输入接口2030。其中,处理器2010可以控制该输入接口2030与其他设备或芯片进行通信,具体地,可以获取其他设备或芯片发送的信息或数据。
在一种实施方式中,该芯片2000还可以包括输出接口2040。其中,处理器2010可以控制该输出接口2040与其他设备或芯片进行通信,具体地,可以向其他设备或芯片输出信息或数据。
在一种实施方式中,该芯片可应用于本申请实施例中的网络设备,并且该芯片可以实现本申请实施例的各个方法中由网络设备实现的相应流程,为了简洁,在此不再赘述。
在一种实施方式中,该芯片可应用于本申请实施例中的终端设备,并且该芯片可以实现本申请实施例的各个方法中由终端设备实现的相应流程,为了简洁,在此不再赘述。
应用于网络设备和终端设备的芯片可以是相同的芯片或不同的芯片。
应理解,本申请实施例提到的芯片还可以称为***级芯片,***芯片,芯片***或片上***芯片等。
上述提及的处理器可以是通用处理器、数字信号处理器(digital signal processor,DSP)、现成可编程门阵列(field programmable gate array,FPGA)、专用集成电路(application specific integrated circuit,ASIC)或者其他可编程逻辑器件、晶体管逻辑器件、分立硬件组件等。其中,上述提到的通用处理器可以是微处理器或者也可以是任何常规的处理器等。
上述提及的存储器可以是易失性存储器或非易失性存储器,或可包括易失性和非易失性存储器两者。其中,非易失性存储器可以是只读存储器(read-only memory,ROM)、可编程只读存储器(programmable ROM,PROM)、可擦除可编程只读存储器(erasable PROM,EPROM)、电可擦除可编程只读存储器(electrically EPROM,EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory,RAM)。
应理解,上述存储器为示例性但不是限制性说明,例如,本申请实施例中的存储器还可以是静态随机存取存储器(static RAM,SRAM)、动态随机存取存储器(dynamic RAM,DRAM)、同步动态随机存取存储器(synchronous DRAM,SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM,DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM,ESDRAM)、同步连接动态随机存取存储器(synch link DRAM,SLDRAM)以及直接内存总线随机存取存储器(Direct Rambus RAM,DR RAM)等等。也就是说,本申请实施例中的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
图21是根据本申请实施例的通信***2100的示意性框图。该通信***2100包括终端设备2110和网络设备2120。
终端设备2110,用于根据下行数据的第一重复传输次数和该下行数据的传输情况,执行后续的重复传输相关处理;
网络设备2120,用于根据下行数据的第一重复传输次数和该下行数据的反馈情况,执行后续的重复传输相关处理。
其中,该终端设备2110可以用于实现上述方法中由终端设备实现的相应的功能,以及该网络设备2120可以用于实现上述方法中由网络设备实现的相应的功能。为了简洁,在此不再赘述。
在上述实施例中,可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时,可以全部或部分地以计算机程序产品的形式实现。该计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行该计算机程序指令时,全部或部分地产生按照本申请实施例中的流程或功能。该计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。该计算机指令可以存储在计算机可读存储介质中,或者从一个计算机可读存储介质向另一个计算机可读存储介质传输,例如,该计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(Digital Subscriber Line,DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。该计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。该可用介质可以是磁性介质,(例如,软盘、硬盘、磁带)、光介质(例如,DVD)、或者半导体介质(例如固态硬盘(Solid State Disk,SSD))等。
应理解,在本申请的各种实施例中,上述各过程的序号的大小并不意味着执行顺序的先后,各过程的执行顺序应以其功能和内在逻辑确定,而不应对本申请实施例的实施过程构成任何限定。
所属领域的技术人员可以清楚地了解到,为描述的方便和简洁,上述描述的***、装置和单元的具体工作过程,可以参考前述方法实施例中的对应过程,在此不再赘述。
以上所述仅为本申请的具体实施方式,但本申请的保护范围并不局限于此,任何熟悉本技术领域的技术人员在本申请揭露的技术范围内,可轻易想到变化或替换,都应涵盖在本申请的保护范围之内。因此,本申请的保护范围应以该权利要求的保护范围为准。
Claims (61)
- 一种重复传输方法,包括:终端设备根据下行数据的第一重复传输次数和所述下行数据的传输情况,执行后续的重复传输相关处理。
- 根据权利要求1所述的方法,其中,执行后续的重复传输相关处理,包括:确定是否接收重复传输的所述下行数据。
- 根据权利要求2所述的方法,其中,确定是否接收重复传输的所述下行数据,包括:所述终端设备在收到的至少一次所述下行数据解码成功的情况下,不再接收重复传输的所述下行数据;所述终端设备在收到的所述下行数据解码失败的情况下,继续接收重复传输的所述下行数据,直至当前传输次数达到第一重复传输次数或收到的下行数据解码成功为止;所述终端设备在未收到的下行数据的情况下,继续接收重复传输的所述下行数据,直至当前传输次数达到第一重复传输次数或收到的下行数据解码成功为止。
- 根据权利要求1至3中任一项所述的方法,其中,所述方法还包括:所述终端设备接收第一指示信息,所述第一指示信息中包括所述第一重复传输次数和/或第一重复间隔。
- 根据权利要求4所述的方法,其中,所述第一指示信息在以下至少之一中:无线资源控制RRC信令;下行控制信息DCI。
- 根据权利要求1至5中任一项所述的方法,其中,执行后续的重复传输相关处理,还包括:所述终端设备在收到n次下行数据后,发送一次上行反馈信息;其中,n大于或等于1,且n小于或等于所述第一重复传输次数N,N大于或等于1。
- 根据权利要求6所述的方法,其中,所述终端设备在收到n次下行数据后,发送一次上行反馈信息,包括:在收到的所述n次下行数据中的至少一次下行数据解码成功的情况下,所述终端设备发送包括确认信息的所述上行反馈信息;和/或在收到的所述n次下行数据中的m次下行数据解码失败的情况下,所述终端设备发送包括非确认信息的所述上行反馈信息;其中,m大于或等于1且m小于或等于n。
- 根据权利要求1至7中任一项所述的方法,其中,在收到的s次下行数据中的至少一次下行数据解码成功的情况下,所述终端设备不接收重复传输的所述下行数据,其中,s大于或等于1,且s小于所述第一重复传输次数N。
- 根据权利要求1至8中任一项所述的方法,其中,所述方法还包括:所述终端设备接收第二指示信息,所述第二指示信息包括第二重复传输次数和/或第二重复间隔,其中,所述第二重复传输次数是根据所述下行数据的反馈情况和所述第一重复传输次数确定的,所述第二重复传输次数与所述第一重复传输次数不同。
- 根据权利要求9所述的方法,其中,所述第二指示信息在DCI。
- 根据权利要求9或10所述的方法,其中,所述下行数据的反馈情况满足以下至少之一:M个目标终端设备的上行反馈信息包括确认信息;M个目标终端设备未反馈上行反馈信息;P个目标终端设备的上行反馈信息包括非确认信息;P个目标终端设备未反馈上行反馈信息;其中,M小于或等于网络设备通过点到多点PTM发送的目标终端设备的总数Y,且M大于或等于第一阈值;和/或,M小于或等于所述第一重复传输次数N,且M与Y的比值大于或等于第二阈值;其中,P小于或等于Y,且P小于或等于第三阈值;和/或,P小于或等于所述第一重复传输次数N,且P与Y的比值小于或等于第四阈值。
- 根据权利要求6、7或11所述的方法,其中,所述上行反馈信息在物理上行控制信道PUCCH中。
- 根据权利要求1至12中任一项所述的方法,其中,所述下行数据在传输块TB和/或物理下行共享信道PDSCH中。
- 一种重复传输方法,包括:网络设备根据下行数据的第一重复传输次数和所述下行数据的反馈情况,执行后续的重复传输相关处理。
- 根据权利要求14所述的方法,其中,执行后续的重复传输相关处理,包括:确定是否重复传输所述下行数据。
- 根据权利要求15所述的方法,其中,确定是否重复传输所述下行数据,包括以下至少之一:所述网络设备在收到的针对所述下行数据的至少一次上行反馈信息中包括确认信息的情况下,不重复传输所述下行数据;所述网络设备在未收到针对所述下行数据的上行反馈信息的情况下,不重复传输所述下行数据;所述网络设备在收到针对所述下行数据的上行反馈信息中包括非确认信息的情况下,重复传输所述下行数据,直至收到针对所述下行数据的上行反馈信息中包括确认信息或当前传输次数达到第一重复传输次数为止。
- 根据权利要求14至16中任一项所述的方法,其中,所述方法还包括:所述网络设备发送第一指示信息,所述第一指示信息中包括所述第一重复传输次数和/或第一重复间隔。
- 根据权利要求17所述的方法,其中,所述第一指示信息在以下至少之一中:RRC信令;DCI。
- 根据权利要求14至18中任一项所述的方法,其中,所述方法还包括:所述网络设备在发送n次下行数据后,接收一次上行反馈信息;其中,n大于或等于1,且n小于或等于所述第一重复传输次数N,N大于或等于1。
- 根据权利要求19所述的方法,其中,所述网络设备在发送n次下行数据后,接收一次上行反馈信息,包括:在发送的所述n次下行数据中的至少一次下行数据解码成功的情况下,所述网络设备接收包括确认信息的所述上行反馈信息;和/或在发送的所述n次下行数据中的m次下行数据解码失败的情况下,所述网络设备接收包括非确认信息的所述上行反馈信息;其中,m大于或等于1且小于或等于n。
- 根据权利要求14至20中任一项所述的方法,其中,执行后续的重复传输相关处理,包括:所述网络设备根据所述下行数据的反馈情况调整所述第一重复传输次数。
- 根据权利要求21所述的方法,其中,所述网络设备根据所述下行数据的反馈情况调整所述第一重复传输次数,包括:所述网络设备根据所述下行数据的反馈情况,将所述第一重复传输次数调整为第二重复传输次数,所述第二重复传输次数与所述第一重复传输次数不同。
- 根据权利要求22所述的方法,其中,所述下行数据的反馈情况满足以下至少之一:M个目标终端设备的上行反馈信息包括确认信息;M个目标终端设备未反馈上行反馈信息;P个目标终端设备的上行反馈信息包括非确认信息;P个目标终端设备未反馈上行反馈信息;其中,M小于或等于网络设备通过点到多点PTM发送的目标终端设备的总数Y,且M大于或等于第一阈值;和/或,M小于或等于所述第一重复传输次数N,且M与Y的比值大于或等于第二阈值;其中,P小于或等于Y,且P小于或等于第三阈值;和/或,P小于或等于所述第一重复传输次数N,且P与Y的比值小于或等于第四阈值。
- 根据权利要求22或23所述的方法,其中,所述方法还包括:所述网络设备发送第二指示信息,所述第二指示信息包括所述第二重复传输次数和/或第二重复间隔。
- 根据权利要求24所述的方法,其中,所述第二指示信息在DCI。
- 根据权利要求16、19、20或23所述的方法,其中,所述上行反馈信息在PUCCH中。
- 根据权利要求14至26中任一项所述的方法,其中,所述下行数据在TB和/或PDSCH中。
- 一种终端设备,包括:处理单元,用于根据下行数据的第一重复传输次数和所述下行数据的传输情况,执行后续的重复传输相关处理。
- 根据权利要求28所述的终端设备,其中,所述处理单元用于执行后续的重复传输相关处理,包括:确定是否接收重复传输的所述下行数据。
- 根据权利要求29所述的终端设备,其中,所述终端设备还包括第一接收单元,所述处理单元用于确定是否接收重复传输的所述下行数据,包括:在收到的至少一次所述下行数据解码成功的情况下,指示所述第一接收单元不再接收重复传输的所述下行数据;在收到的所述下行数据解码失败的情况下,指示所述第一接收单元继续接收重复传输的所述下行数 据,直至当前传输次数达到第一重复传输次数或收到的下行数据解码成功为止;在未收到的下行数据的情况下,指示所述第一接收单元继续接收重复传输的所述下行数据,直至当前传输次数达到第一重复传输次数或收到的下行数据解码成功为止。
- 根据权利要求28至30中任一项所述的终端设备,其中,所述终端设备还包括:第二接收单元,用于接收第一指示信息,所述第一指示信息中包括所述第一重复传输次数和/或第一重复间隔。
- 根据权利要求31所述的终端设备,其中,所述第一指示信息在以下至少之一中:无线资源控制RRC信令;下行控制信息DCI。
- 根据权利要求28至32中任一项所述的终端设备,其中,所述终端设备还包括发送单元,所述处理单元用于在收到n次下行数据后,指示所述发送单元发送一次上行反馈信息;其中,n大于或等于1,且n小于或等于所述第一重复传输次数N,N大于或等于1。
- 根据权利要求33所述的终端设备,其中,所述处理单元用于在收到n次下行数据后,发送一次上行反馈信息,包括:在收到的所述n次下行数据中的至少一次下行数据解码成功的情况下,指示所述发送单元发送包括确认信息的所述上行反馈信息;和/或在收到的所述n次下行数据中的m次下行数据解码失败的情况下,指示所述发送单元发送包括非确认信息的所述上行反馈信息;其中,m大于或等于1且m小于或等于n。
- 根据权利要求28至34中任一项所述的终端设备,其中,所述处理单元还用于在收到的s次下行数据中的至少一次下行数据解码成功的情况下,指示第一接收单元不接收重复传输的所述下行数据,其中,s大于或等于1,且s小于所述第一重复传输次数N。
- 根据权利要求28至35中任一项所述的终端设备,其中,所述终端设备还包括:第三接收单元,用于接收第二指示信息,所述第二指示信息包括第二重复传输次数和/或第二重复间隔,其中,所述第二重复传输次数是根据所述下行数据的反馈情况和所述第一重复传输次数确定的,所述第二重复传输次数与所述第一重复传输次数不同。
- 根据权利要求36所述的终端设备,其中,所述第二指示信息在DCI。
- 根据权利要求36或37所述的终端设备,其中,所述下行数据的反馈情况满足以下至少之一:M个目标终端设备的上行反馈信息包括确认信息;M个目标终端设备未反馈上行反馈信息;P个目标终端设备的上行反馈信息包括非确认信息;P个目标终端设备未反馈上行反馈信息;其中,M小于或等于网络设备通过点到多点PTM发送的目标终端设备的总数Y,且M大于或等于第一阈值;和/或,M小于或等于所述第一重复传输次数N,且M与Y的比值大于或等于第二阈值;其中,P小于或等于Y,且P小于或等于第三阈值;和/或,P小于或等于所述第一重复传输次数N,且P与Y的比值小于或等于第四阈值。
- 根据权利要求33、34或38所述的终端设备,其中,所述上行反馈信息在物理上行控制信道PUCCH和/或物理上行共享信道PUSCH中。
- 根据权利要求28至39中任一项所述的终端设备,其中,所述下行数据在传输块TB和/或物理下行共享信道PDSCH中。
- 一种网络设备,包括:处理单元,用于根据下行数据的第一重复传输次数和所述下行数据的反馈情况,执行后续的重复传输相关处理。
- 根据权利要求41所述的网络设备,其中,所述处理单元用于执行后续的重复传输相关处理,包括:确定是否重复传输所述下行数据。
- 根据权利要求42所述的网络设备,其中,所述网络设备还包括第一发送单元,所述处理单元用于确定是否重复传输所述下行数据,包括以下至少之一:在收到的针对所述下行数据的至少一次上行反馈信息中包括确认信息的情况下,指示所述第一发送单元不重复传输所述下行数据;在未收到针对所述下行数据的上行反馈信息的情况下,指示所述第一发送单元不重复传输所述下行数据;在收到针对所述下行数据的上行反馈信息中包括非确认信息的情况下,指示所述第一发送单元重复传输所述下行数据,直至收到针对所述下行数据的上行反馈信息中包括确认信息或当前传输次数达到第一重复传输次数为止。
- 根据权利要求41至43中任一项所述的网络设备,其中,所述网络设备还包括:第二发送单元,用于发送第一指示信息,所述第一指示信息中包括所述第一重复传输次数和/或第一重复间隔。
- 根据权利要求44所述的网络设备,其中,所述第一指示信息在以下至少之一中:RRC信令;DCI。
- 根据权利要求41至45中任一项所述的网络设备,其中,所述网络设备还包括:接收单元,用于在发送n次下行数据后,接收一次上行反馈信息;其中,n大于或等于1,且n小于或等于所述第一重复传输次数N,N大于或等于1。
- 根据权利要求46所述的网络设备,其中,所述接收单元用于:在发送的所述n次下行数据中的至少一次下行数据解码成功的情况下,接收包括确认信息的所述上行反馈信息;和/或在发送的所述n次下行数据中的m次下行数据解码失败的情况下,接收包括非确认信息的所述上行反馈信息;其中,m大于或等于1且小于或等于n。
- 根据权利要求41至47中任一项所述的网络设备,其中,所述处理单元还用于根据所述下行数据的反馈情况调整所述第一重复传输次数。
- 根据权利要求48所述的网络设备,其中,所述处理单元用于根据所述下行数据的反馈情况调整所述第一重复传输次数,包括:根据所述下行数据的反馈情况,将所述第一重复传输次数调整为第二重复传输次数,所述第二重复传输次数与所述第一重复传输次数不同。
- 根据权利要求49所述的网络设备,其中,所述下行数据的反馈情况满足以下至少之一:M个目标终端设备的上行反馈信息包括确认信息;M个目标终端设备未反馈上行反馈信息;P个目标终端设备的上行反馈信息包括非确认信息;P个目标终端设备未反馈上行反馈信息;其中,M小于或等于网络设备通过点到多点PTM发送的目标终端设备的总数Y,且M大于或等于第一阈值;和/或,M小于或等于所述第一重复传输次数N,且M与Y的比值大于或等于第二阈值;其中,P小于或等于Y,且P小于或等于第三阈值;和/或,P小于或等于所述第一重复传输次数N,且P与Y的比值小于或等于第四阈值。
- 根据权利要求49或50所述的网络设备,其中,所述网络设备还包括:第三发送单元,用于发送第二指示信息,所述第二指示信息包括所述第二重复传输次数和/或第二重复间隔。
- 根据权利要求51所述的网络设备,其中,所述第二指示信息在DCI。
- 根据权利要求43、46、47或50所述的网络设备,其中,所述上行反馈信息在PUCCH和/或PUSCH中。
- 根据权利要求41至53中任一项所述的网络设备,其中,所述下行数据在TB和/或PDSCH中。
- 一种终端设备,包括:处理器、存储器和收发器,所述处理器用于控制所述收发器与其他设备进行通信,所述存储器用于存储计算机程序,所述处理器用于调用并运行所述存储器中存储的计算机程序,以使所述终端设备执行如权利要求1至13中任一项所述的方法。
- 一种网络设备,包括:处理器、存储器和收发器,所述处理器用于控制所述收发器与其他设备进行通信,所述存储器用于存储计算机程序,所述处理器用于调用并运行所述存储器中存储的计算机程序,以使所述网络设备执行如权利要求14至27中任一项所述的方法。
- 一种芯片,包括:处理器,用于从存储器中调用并运行计算机程序,使得安装有所述芯片的设备执行如权利要求1至13或14至27中任一项所述的方法。
- 一种计算机可读存储介质,用于存储计算机程序,当所述计算机程序被设备运行时使得所述设备执行如权利要求1至13或14至27中任一项所述的方法。
- 一种计算机程序产品,包括计算机程序指令,该计算机程序指令使得计算机执行如权利要求1至13或14至27中任一项所述的方法。
- 一种计算机程序,所述计算机程序使得计算机执行如权利要求1至13或14至27中任一项所述的方法。
- 一种通信***,包括:终端设备,用于执行如权利要求1至13中任一项所述的方法;网络设备,用于执行如权利要求14至27中任一项所述的方法。
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/CN2022/111286 WO2024031395A1 (zh) | 2022-08-09 | 2022-08-09 | 重复传输方法、终端设备和网络设备 |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/CN2022/111286 WO2024031395A1 (zh) | 2022-08-09 | 2022-08-09 | 重复传输方法、终端设备和网络设备 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2024031395A1 true WO2024031395A1 (zh) | 2024-02-15 |
Family
ID=89850067
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2022/111286 WO2024031395A1 (zh) | 2022-08-09 | 2022-08-09 | 重复传输方法、终端设备和网络设备 |
Country Status (1)
Country | Link |
---|---|
WO (1) | WO2024031395A1 (zh) |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1411187A (zh) * | 2001-09-25 | 2003-04-16 | 华为技术有限公司 | 基于自适应编码调制和自动重传请求的链路自适应方法 |
CN101789815A (zh) * | 2009-01-24 | 2010-07-28 | 夏普株式会社 | 下行数据传输方法及基站 |
CN105897386A (zh) * | 2016-03-30 | 2016-08-24 | 京信通信技术(广州)有限公司 | 一种信令重配置处理方法及装置 |
CN112825589A (zh) * | 2019-11-21 | 2021-05-21 | 维沃移动通信有限公司 | 一种进入休眠行为的方法和终端 |
EP3998825A1 (en) * | 2019-07-10 | 2022-05-18 | Beijing Xiaomi Mobile Software Co., Ltd. | Data transmission method and apparatus based on unlicensed uplink scheduling, and storage medium |
-
2022
- 2022-08-09 WO PCT/CN2022/111286 patent/WO2024031395A1/zh unknown
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1411187A (zh) * | 2001-09-25 | 2003-04-16 | 华为技术有限公司 | 基于自适应编码调制和自动重传请求的链路自适应方法 |
CN101789815A (zh) * | 2009-01-24 | 2010-07-28 | 夏普株式会社 | 下行数据传输方法及基站 |
CN105897386A (zh) * | 2016-03-30 | 2016-08-24 | 京信通信技术(广州)有限公司 | 一种信令重配置处理方法及装置 |
EP3998825A1 (en) * | 2019-07-10 | 2022-05-18 | Beijing Xiaomi Mobile Software Co., Ltd. | Data transmission method and apparatus based on unlicensed uplink scheduling, and storage medium |
CN112825589A (zh) * | 2019-11-21 | 2021-05-21 | 维沃移动通信有限公司 | 一种进入休眠行为的方法和终端 |
Non-Patent Citations (1)
Title |
---|
GUANGDONG OPPO MOBILE TELECOM: "Uplink grant-less transmission for URLLC", 3GPP DRAFT; R1-1700571, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. Spokane, USA; 20170116 - 20170120, 9 January 2017 (2017-01-09), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051202303 * |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US12028169B2 (en) | Wireless communication method, receiving-end device, and sending-end device | |
US11949598B2 (en) | Window adjustment method and apparatus, network device, terminal device | |
WO2020259611A1 (zh) | 一种通信方法、装置及存储介质 | |
US11963199B2 (en) | Semi-persistent scheduling method and apparatus for MBS service, and terminal device and network device | |
US20230283498A1 (en) | Method for improving reliability of mbs service and network device | |
CN113678500B (zh) | 一种反馈资源配置方法及通信方法、装置、通信设备 | |
US20230076835A1 (en) | Harq feedback method and apparatus, terminal, and network device | |
WO2024031395A1 (zh) | 重复传输方法、终端设备和网络设备 | |
WO2022021811A1 (zh) | 无线通信方法、终端设备和网络设备 | |
CN115243384B (zh) | 业务冲突的解决方法、装置、设备及存储介质 | |
WO2023004584A1 (zh) | 无线通信的方法、终端设备和网络设备 | |
WO2023050319A1 (zh) | 无线通信的方法、终端设备和网络设备 | |
WO2023155151A1 (zh) | 无线通信的方法、终端设备和网络设备 | |
WO2024031307A1 (zh) | 混合自动重传请求harq反馈方法、装置、设备及介质 | |
WO2023097601A1 (zh) | 一种drx定时器的运行方法及装置、终端设备 | |
WO2023115411A1 (zh) | 通信方法及装置 | |
WO2023102833A1 (zh) | 一种反馈状态的指示方法及装置、终端设备、网络设备 | |
WO2023097665A1 (zh) | 一种数据接收方法及装置、终端设备 | |
WO2023102898A1 (zh) | 重传方式的确定方法及定时器的控制方法、装置 | |
WO2023115491A1 (zh) | 通信方法、终端设备和网络设备 | |
US20230209652A1 (en) | Communication method and communication apparatus | |
WO2023115492A1 (zh) | 信息发送方法、信息接收方法、终端设备和网络设备 | |
WO2023097613A1 (zh) | 一种信息确定方法及装置、终端设备 | |
WO2022061548A1 (zh) | 无线通信的方法、终端设备和网络设备 | |
WO2022151385A1 (zh) | 无线通信方法、终端设备和网络设备 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 22954371 Country of ref document: EP Kind code of ref document: A1 |