WO2020244645A1 - 一种通信方法及装置 - Google Patents

一种通信方法及装置 Download PDF

Info

Publication number
WO2020244645A1
WO2020244645A1 PCT/CN2020/094750 CN2020094750W WO2020244645A1 WO 2020244645 A1 WO2020244645 A1 WO 2020244645A1 CN 2020094750 W CN2020094750 W CN 2020094750W WO 2020244645 A1 WO2020244645 A1 WO 2020244645A1
Authority
WO
WIPO (PCT)
Prior art keywords
cell
data
correspondence
harq entity
dci
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2020/094750
Other languages
English (en)
French (fr)
Inventor
肖洁华
李新县
唐浩
王轶
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to EP20818653.6A priority Critical patent/EP3982578A4/en
Publication of WO2020244645A1 publication Critical patent/WO2020244645A1/zh
Priority to US17/532,798 priority patent/US12041598B2/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

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
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H04L1/1893—Physical mapping arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • 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
    • H04L1/1812—Hybrid protocols; Hybrid automatic repeat request [HARQ]
    • 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
    • H04L1/1822—Automatic repetition systems, e.g. Van Duuren systems involving configuration of automatic repeat request [ARQ] with parallel processes
    • 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
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H04L1/1896—ARQ related signaling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal

Definitions

  • This application relates to the field of communication technology, and in particular to a communication method and device.
  • HARQ hybrid automatic repeat request
  • FEC forward error correction
  • ARQ automatic repeat reQuest
  • the present application provides a communication method and device to implement initial transmission and retransmission of data using different cells.
  • a communication method including: receiving first data initially transmitted in the first cell according to the corresponding relationship between the first cell and the first hybrid automatic repeat request HARQ entity; receiving first indication information , The first indication information is used to indicate the correspondence between the second cell and the first HARQ entity; according to the correspondence between the second cell and the first HARQ entity, the second cell is received in the second cell The first data transmitted.
  • the first indication information is used to indicate the correspondence between the first HARQ entity and the second cell, so that the second cell is used to retransmit the first data corresponding to the first HARQ entity;
  • the way that a cell returns to normal and the first data is retransmitted can increase the data throughput.
  • the second cell includes a first bandwidth part BWP
  • the correspondence between the second cell and the first HARQ entity includes: the first BWP and the first HARQ Correspondence of entities.
  • the first indication information is an identifier of the first BWP
  • the method further includes: determining the first BWP and the first HARQ according to the identifier of the first BWP Correspondence of entities.
  • the method further includes: sending second indication information, where the second indication information is used to indicate that the link of the first cell is interrupted, or the beam mismatch of the first cell.
  • the first data includes a first data block
  • the method further includes: receiving first downlink control information DCI, where the first DCI is used for scheduling the first data block Retransmission;
  • the receiving the retransmitted first data in the second cell according to the correspondence between the second cell and the first HARQ entity includes: according to the relationship between the second cell and the first HARQ entity Correspondence, receiving the retransmitted first data block in the second cell.
  • the first data includes a second data block
  • the method further includes: receiving a second DCI, where the second DCI is used to schedule retransmission of the second data block;
  • the receiving the retransmitted first data according to the correspondence between the second cell and the first HARQ entity includes: according to the correspondence between the second cell and the first HARQ entity, Receiving the retransmitted second data block in the second cell.
  • the first data includes the first data block and the second data block, and the retransmission of the first data block and the second data block are both in the second cell, which improves the utilization of the second cell rate.
  • the method further includes: receiving the retransmitted first data in the third cell according to the correspondence between the third cell and the first HARQ entity.
  • the first data includes a second data block
  • the method further includes: receiving a third DCI, where the third DCI is used to schedule retransmission of the second data block;
  • the receiving the retransmitted first data in the third cell according to the correspondence between the third cell and the first HARQ entity includes: according to the correspondence between the third cell and the first HARQ entity Correspondence, receiving the retransmitted second data block in the third cell.
  • the first data includes the first data block and the third data block.
  • the retransmission of the first data block is in the second cell, and the retransmission of the second data block is in the third cell. , Can improve the efficiency of data transmission.
  • the first DCI is also used to indicate at least one of the index, start identifier, or end identifier of the first data block
  • the second DCI or the third DCI is also used to Indicate at least one of the index, start identifier, or end identifier of the second data block; wherein the start identifier indicates the first retransmitted data block in the retransmitted first data, and the end identifier indicates Among the first retransmitted data, the last retransmitted data block.
  • the method further includes: sending a fourth DCI, where the fourth DCI is used to schedule retransmission of the second data and the third data, and the second data and the third data
  • the initial transmission is in the second cell; the second data and the third data are retransmitted in the first cell; or the second data and the third data are retransmitted in the fourth cell.
  • an application scenario is provided.
  • the transmission bandwidth of the first cell or the fourth cell is greater than the transmission bandwidth of the second cell; the first transmission of the second data and the third data is in the second cell.
  • the second data and the third data can be retransmitted in the first cell; or the second data and the third data can be retransmitted in the fourth cell to improve the data transmission efficiency.
  • a communication method including: initially transmitting first data in the first cell according to the corresponding relationship between the first cell and the first hybrid automatic repeat request HARQ entity; sending first indication information, so The first indication information is used to indicate the correspondence between the second cell and the first HARQ entity; according to the correspondence between the second cell and the first HARQ entity, retransmit the First data.
  • the second cell includes a first bandwidth part BWP
  • the correspondence between the second cell and the first HARQ entity includes the correspondence between the first BWP and the first HARQ entity relationship.
  • the first indication information is an identifier of the first BWP.
  • the method further includes: receiving second indication information, where the second indication information is used to indicate that the link of the first cell is interrupted or the beam mismatch of the first cell.
  • the first data includes a first data block
  • the method further includes: sending first downlink control information DCI, where the first DCI is used to schedule the first data block Retransmission;
  • the retransmitting the first data in the second cell according to the correspondence between the second cell and the first HARQ entity includes: according to the relationship between the second cell and the first HARQ entity Corresponding relationship, the first data block is retransmitted in the second cell.
  • the first data includes a second data block
  • the method further includes: sending a second DCI, where the second DCI is used to schedule retransmission of the second data block;
  • the retransmitting the first data in the second cell according to the correspondence between the second cell and the first HARQ entity includes: according to the relationship between the second cell and the first HARQ entity Correspondence, the second data block is retransmitted in the second cell.
  • the method further includes: retransmitting the first data in the third cell according to the correspondence between the third cell and the first HARQ entity.
  • the first data includes a second data block
  • the method further includes: sending a third DCI, where the third DCI is used to schedule retransmission of the second data block;
  • the retransmitting the first data in the third cell according to the correspondence between the third cell and the first HARQ entity includes: according to the correspondence between the third cell and the first HARQ entity , Retransmit the second data block in the third cell.
  • the first DCI is also used to indicate at least one of the index, start identifier, or end identifier of the first data block
  • the second DCI or the third DCI is also used to Indicate at least one of the index, start identifier, or end identifier of the second data block; wherein the start identifier indicates the first retransmitted data block in the retransmitted first data, and the end identifier indicates Among the first retransmitted data, the last retransmitted data block.
  • the method further includes: sending a fourth DCI, where the fourth DCI is used to schedule retransmission of the second data and the third data, and the second data and the third data
  • the initial transmission is in the second cell; the second data and the third data are retransmitted in the first cell; or the second data and the third data are retransmitted in the fourth cell.
  • a communication device may be a terminal device, a device in a terminal device, or a device that can be used with the terminal device.
  • the device may include a transceiver module and a processing module, and the transceiver module
  • the and processing module can perform the corresponding function in any possible design example of the first aspect, specifically:
  • the processing module is configured to receive the initially transmitted first data in the first cell according to the correspondence between the first cell and the first hybrid automatic repeat request HARQ entity, and according to the second cell and the first data Correspondence of a HARQ entity, receiving the retransmitted first data in the second cell;
  • the transceiver module is configured to receive first indication information, where the first indication information is used to indicate the correspondence between the second cell and the first HARQ entity.
  • a communication device in a fourth aspect, includes a processor for implementing the method described in the first aspect.
  • the device may also include a memory for storing instructions and data.
  • the memory is coupled with the processor, and when the processor executes the program instructions stored in the memory, the method described in the first aspect can be implemented.
  • the device may also include a communication interface, which is used for the device to communicate with other devices.
  • the communication interface may be a transceiver, circuit, bus, module, or other type of communication interface, and other devices may be Network equipment, etc.
  • the device includes:
  • Memory used to store program instructions
  • the processor is configured to receive the initially transmitted first data in the first cell according to the correspondence between the first cell and the first hybrid automatic repeat request HARQ entity, and according to the second cell and the first data Correspondence of a HARQ entity, receiving the retransmitted first data in the second cell;
  • the communication interface is configured to receive first indication information, where the first indication information is used to indicate the correspondence between the second cell and the first HARQ entity.
  • a communication device may be a network device, a device in a network device, or a device that can be matched with a terminal device.
  • the device may include a transceiver module, and the transceiver module may perform the above-mentioned
  • the corresponding function in any possible design example in two aspects, specifically:
  • the processing module is configured to initially transmit the first data in the first cell according to the correspondence between the first cell and the first hybrid automatic repeat request HARQ entity, and according to the second cell and the first HARQ The correspondence of entities, retransmit the first data in the second cell;
  • the transceiver module is configured to send first indication information, where the first indication information is used to indicate the correspondence between the second cell and the first HARQ entity.
  • a communication device in a sixth aspect, includes a communication interface for implementing the method described in the second aspect.
  • the communication interface is used for the device to communicate with other devices.
  • the communication interface may be a transceiver, circuit, bus, module or other type of communication interface, and other devices may be terminal devices.
  • the device also includes a processor, configured to control the communication interface to implement the method described in the first aspect when executing the program instructions stored in the memory.
  • the device may also include a memory for storing instructions and data. In a possible design, the device includes:
  • Memory used to store program instructions
  • the processor is configured to initially transmit the first data in the first cell according to the corresponding relationship between the first cell and the first hybrid automatic repeat request HARQ entity, and according to the second cell and the first HARQ Correspondence between entities, retransmit the first data in the second cell.
  • the communication interface is configured to send first indication information, where the first indication information is used to indicate the correspondence between the second cell and the first HARQ entity.
  • an embodiment of the present application also provides a computer-readable storage medium, including instructions, which when run on a computer, cause the computer to execute any one of the possible design methods of the first aspect or the second aspect.
  • an embodiment of the present application further provides a chip system, which includes a processor and may also include a memory, for implementing the method of the first aspect or the second aspect.
  • the chip system can be composed of chips, or can include chips and other discrete devices.
  • the embodiments of the present application also provide a computer program product, including instructions, which when run on a computer, cause the computer to execute the method of the first aspect or the second aspect.
  • an embodiment of the present application provides a system that includes the device described in the third aspect and the device described in the fifth aspect, or the system includes the device described in the fourth aspect and the sixth aspect The device described.
  • FIG. 1 is a schematic diagram of a protocol stack architecture for data transmission provided by an embodiment of the application
  • FIG. 2 is a schematic diagram of the relationship between the MAC entity, HARQ entity, HARQ process, and HARQ buffer under carrier aggregation provided by an embodiment of this application;
  • FIG. 3 is a schematic diagram of beam failure detection and beam failure recovery provided by an embodiment of the application.
  • FIG. 4 is an architecture diagram of a communication system provided by an embodiment of this application.
  • FIG. 5 is a flowchart of a communication method provided by an embodiment of this application.
  • FIG. 6 is a schematic diagram of RRC provided by an embodiment of this application.
  • FIG. 7 is another schematic diagram of RRC provided by an embodiment of this application.
  • FIG. 8 is a schematic diagram of TB1 and TB2 transmission provided by an embodiment of this application.
  • FIG. 9 is a schematic diagram of TB2 retransmission provided by an embodiment of this application.
  • FIG. 10 is a schematic diagram of a BWP configuration provided by an embodiment of the application.
  • FIG. 11 is a schematic diagram of TB2 retransmission provided by an embodiment of this application.
  • Figures 12 and 13 are schematic diagrams of TB2 retransmission provided by an embodiment of this application.
  • FIG. 14 is a schematic diagram of TB1 retransmission provided by an embodiment of this application.
  • 15 and 16 are schematic diagrams of ARQ retransmission provided by an embodiment of this application.
  • Figure 17 is a schematic diagram of a cell configuration provided by an embodiment of the application.
  • FIG. 18 is a schematic structural diagram of a communication device provided by an embodiment of the application.
  • FIG. 19 is a schematic structural diagram of a communication device provided by an embodiment of this application.
  • the network device may be an access network device, and the access network device may also be called a radio access network (RAN) device, which is a device that provides wireless communication functions for terminal devices.
  • the access network equipment includes, for example, but is not limited to: the next generation base station (gNB), evolved node B (evolved node B, eNB), radio network controller (RNC), node B ( node B, NB), base station controller (BSC), base transceiver station (BTS), home base station (for example, home evolved nodeB, or home node B, HNB), baseband unit (baseband unit) , BBU), transmitting and receiving point (TRP), transmitting point (TP), mobile switching center, etc.
  • gNB next generation base station
  • eNB evolved node B
  • RNC radio network controller
  • node B node B
  • BSC base station controller
  • BTS base transceiver station
  • home base station for example, home evolved nodeB, or home node B, HNB
  • baseband unit
  • the access network equipment can also be a wireless controller, a centralized unit (CU), and/or a distributed unit (DU) in a cloud radio access network (cloud radio access network, CRAN) scenario, or a network
  • the equipment can be a relay station, an access point, a vehicle-mounted device, a terminal device, a wearable device, and a network device in a future 5G network or a network device in a future evolved PLMN network.
  • the terminal device can communicate with multiple access network devices of different technologies.
  • the terminal device can communicate with an access network device that supports long term evolution (LTE), or can communicate with an access network device that supports 5G. , It can also be dual-connected with LTE-enabled access network equipment and 5G-enabled access network equipment.
  • LTE long term evolution
  • 5G 5G-enabled access network equipment
  • the device used to implement the function of the network device may be a network device; it may also be a device capable of supporting the network device to implement the function, such as a chip system, and the device may be installed in the network device.
  • the device used to implement the functions of the network equipment is the network equipment, and the network equipment is a base station as an example to describe the technical solutions provided in the embodiments of the present application.
  • a terminal device can be referred to as a terminal for short. It is a device with wireless transceiver function.
  • the terminal device can be deployed on land, including indoor or outdoor, handheld or vehicle-mounted; it can also be deployed on the water (such as ships, etc.); it can also be deployed on In the air (such as airplanes, balloons, satellites, etc.).
  • the terminal device may be a mobile phone (mobile phone), a tablet computer (pad), a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, an industrial control ( Wireless terminal equipment in industrial control, wireless terminal equipment in unmanned driving (self-driving), wireless terminal equipment in remote medical (remote medical), wireless terminal equipment in smart grid (smart grid), transportation safety (transportation) Wireless terminal equipment in safety), wireless terminal equipment in a smart city (smart city), wireless terminal equipment in a smart home (smart home), and may also include user equipment (UE), etc.
  • UE user equipment
  • the terminal device can also be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), and a wireless communication Functional handheld devices, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminal devices in the 5th generation (5G) network in the future, or public land mobile communication networks that will evolve in the future (Public land mobile network (PLMN) terminal equipment, etc.
  • SIP session initiation protocol
  • WLL wireless local loop
  • PDA personal digital assistant
  • PLMN Public land mobile network
  • Terminal equipment can sometimes be called terminal equipment, user equipment (UE), access terminal equipment, vehicle-mounted terminal equipment, industrial control terminal equipment, UE unit, UE station, mobile station, mobile station, remote station, and remote terminal Equipment, mobile equipment, UE terminal equipment, terminal equipment, wireless communication equipment, UE agent or UE device, etc.
  • the terminal device can also be fixed or mobile. The embodiment of the application does not limit this.
  • the device used to implement the function of the terminal may be a terminal; it may also be a device capable of supporting the terminal to implement the function, such as a chip system, and the device may be installed in the terminal.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • the device used to implement the functions of the terminal is a terminal, and the terminal is a UE as an example to describe the technical solutions provided in the embodiments of the present application.
  • CA Carrier Aggregation
  • Carrier aggregation is a technology that aggregates at least two component carriers (CC) to support a larger transmission bandwidth.
  • carrier aggregation supports the aggregation of different carrier units, such as the aggregation of carrier units in the same or different bandwidths, or the aggregation of adjacent or non-adjacent carrier units in the same frequency band, or different Aggregation between carrier units in the frequency band, etc.
  • the terminal device side includes the application protocol (application protocol, APP) layer and the transmission control protocol (transmission control protocol, TCP) from top to bottom.
  • Layer Internet Protocol (IP) layer, Service Data Adaptation Protocol (SDAP) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (radio link control, RLC) layer, medium access control (MAC) layer, physical (PHY) layer, etc.
  • the access network side (for example, gNB) includes SDAP layer, PDCP layer, RLC layer, MAC layer, and PHY layer from top to bottom.
  • the core network side may include an IP layer and the like.
  • the server side includes the APP layer, the TCP layer, and the IP layer in turn from top to bottom.
  • the black arrow shown in Figure 1 indicates the main flow of data in each protocol stack during the data download process.
  • the above-mentioned SDAP layer to the PHY layer are the air interface protocol stacks on the RAN side, and are not a limitation of this application.
  • the access network side may also include protocol stacks of other wired transmission parts.
  • HARQ retransmission is a data retransmission mechanism of the MAC layer, and is a technology that combines forward error correction (FEC) and automatic repeat reQuest (ARQ) methods.
  • FEC forward error correction
  • ARQ automatic repeat reQuest
  • the receiving end can use the error detection code to detect whether the received data packet is wrong.
  • the error detection code can be a cyclic redundancy check (cyclic redundancy check, CRC) codes, etc.
  • the receiving end sends an acknowledgement (ACK) to the sending end.
  • ACK acknowledgement
  • the receiver first uses forward error correction (FEC) to correct the error. If the FEC can correct the error, the receiver can send an ACK to the sender. If the FEC cannot correct the error, then the receiver The end can send a negative acknowledgement (NACK) to the sender.
  • FEC forward error correction
  • the receiving end can discard the above-mentioned wrong data packet or save the above-mentioned wrong data packet, so that after the data is retransmitted, it can Transfer data to merge.
  • ACK can be represented by '1'
  • NACK can be represented by '0'; the transceiver can increase system reliability and improve system transmission efficiency through HARQ mechanism.
  • ARQ retransmission is a data retransmission mechanism of the RLC layer, and the retransmitted data is an RLC service data unit (SDU), or the retransmitted data is a segment of the RLC SDU.
  • the sending end can trigger the ARQ retransmission of the RLC layer based on the NACK sent by the receiving end. Or, when the RLC sending timer of the sending end expires, the ARQ retransmission of the RLC layer is triggered.
  • HARQ HARQ
  • ARQ technology if the receiving end finds that the data packet is transmitted incorrectly, it will discard the original data packet, and then apply for retransmission of the data packet.
  • HARQ technology if the receiving end finds that the data packet is transmitted incorrectly, it will retain the original data packet that was transmitted incorrectly, and then apply for retransmission of the data packet. Finally, the receiving end combines the retransmitted data packet with the original data packet to obtain a diversity gain, which may also be referred to as soft combining gain. And combined with the encoding method, the encoded redundant bits can be reserved differently for different times of retransmission to obtain diversity gain.
  • the ARQ mechanism adopts a method of discarding data packets and requesting retransmission.
  • the HARQ mechanism uses a method of combining the original data packet with the retransmitted data packet to obtain diversity gain. It is understandable that, for a data packet with a transmission error, although the original original data packet cannot be decoded correctly, it still contains useful information. If it is discarded, the corresponding useful information is also lost.
  • the HARQ mechanism may use the HARQ (HARQ with soft combining) mechanism.
  • the soft merging process may be: after receiving the wrong data packet, the receiving end can save the wrong data packet in a HARQ buffer register (buffer), and merge it with the subsequent received retransmitted data packet, This results in a more reliable data packet than decoding alone. Then decode the merged data packet, if it still fails, repeat the process of "request for retransmission and then perform soft merge".
  • the HARQ of soft combining may include two types of chase combining and incremental redundancy.
  • the bit information of the retransmitted data packet is the same as that of the original data packet; in incremental redundancy, the bit information of the retransmitted data packet and the original data packet can be different.
  • the sending end may generate multiple sets of coded bits, and each set of coded bits may carry the same information, that is, the same coded input information.
  • the sender can select a different set of coded bits from the previous one.
  • the receiving end can combine the retransmitted data with the previously transmitted data.
  • the set of coded bits for each retransmission may be referred to as a redundancy version (RV).
  • CA is only visible to the MAC layer.
  • the MAC layer has only one MAC entity.
  • the MAC layer has two MAC entities.
  • Each cell in the carrier aggregation corresponds to one HARQ entity.
  • n serving cells may correspond to n HARQ entities in total.
  • One HARQ entity corresponds to a set of HARQ processes, and each HARQ process corresponds to one HARQ buffer register (buffer).
  • the HARQ buffer register is used to store the transmitted transport block (TB). For example, a TB that has not received correct feedback.
  • the HARQ buffer register is used to store TB decoding soft information, etc.
  • each HARQ process can only process one TB, and one HARQ corresponds to one TB.
  • the unit of the time unit may be a subframe, a time slot, or a symbol, and a time unit may include one subframe, or a time slot, or one or more symbols, etc.
  • each HARQ process has an independent HARQ buffer register, so as to softly combine the received data.
  • space division multiplexing a time unit will transmit 2 TBs in parallel, and each TB has its own independent HARQ confirmation information and uses different HARQ processes to process.
  • one HARQ entity may include two HARQ process sets.
  • the HARQ entity is used to control the HARQ process, and the association between the cell and the HARQ entity can also be described as the association between the cell and the HARQ process.
  • the MAC layer of a network device or terminal device includes a MAC entity.
  • the MAC entity of a network device or terminal device is used to process one or more of the following transmission channels: broadcast channel (BCH), downlink shared channel (DL-SCH), paging channel (paging channel, PCH), uplink shared channel (UL-SCH), random access channel (RACH).
  • BCH broadcast channel
  • DL-SCH downlink shared channel
  • paging channel paging channel
  • PCH uplink shared channel
  • RACH random access channel
  • the MAC entity is responsible for mapping the logical channel to the transmission channel.
  • Logical channels are channels that support specific types of information transmission.
  • Each logical channel is defined by the type of information it transmits, including broadcast control channel (BCCH), paging control channel (PCCH), and common control Channel (common control channel, CCCH), dedicated control channel (DCCH), dedicated traffic channel (dedicated traffic channel, DTCH), used to transmit cell broadcast information, paging information, common control information, and dedicated control information And dedicated business data.
  • the MAC entity includes a HARQ entity.
  • the HARQ entity is used to maintain multiple parallel HARQ processes.
  • the HARQ entity of the terminal points the HARQ information received on the DL-SCH and the associated TB to the corresponding HARQ process.
  • one HARQ process supports one TB.
  • the HARQ information used for DL-SCH or UL-SCH transmission includes new data indication (NDI), transport block size (TBS), redundancy version (RV), HARQ process number, and so on.
  • the primary cell may be the cell where the terminal device performs the initial connection establishment, or the primary cell may be the cell where the terminal device performs radio resource control (Radio Resource Control, RRC) connection reestablishment, or the primary cell may be in the handover process.
  • the primary cell is mainly used for RRC communication with terminal equipment.
  • the carrier unit corresponding to the primary cell is called the primary component carrier (PCC)
  • the downlink carrier of the primary component carrier is called the downlink primary carrier unit (downlink PCC, DL PCC)
  • the uplink carrier of the primary carrier unit is called the uplink primary carrier.
  • Carrier unit uplink PCC, UL PCC).
  • the secondary cell may be a cell in which there is no RRC communication with the terminal device, and is mainly used to provide additional radio resources.
  • the secondary cell may be added during RRC reconfiguration.
  • the carrier unit corresponding to the secondary cell becomes a secondary component carrier (SCC).
  • the downlink carrier of the secondary carrier unit is called a downlink secondary carrier unit (down link SCC, DL SCC), and the uplink carrier of the secondary carrier unit is called an uplink secondary carrier unit (uplink SCC, UL SCC).
  • the primary cell may be determined when the connection is established, and the secondary cell may be added, modified or released through the RRC connection reconfiguration message after the initial access is completed.
  • the serving cell may be a cell that provides uplink and downlink transmission services for terminal equipment. If the terminal device is in the RRC connected (RRC_CONNECTED) state but CA is not configured, the terminal device has only one serving cell, and this serving cell can be the primary cell; if the terminal device is in the RRC connected (RRC_CONNECTED) state and CA is configured, this
  • the terminal device may include a serving cell set, and the serving cell set includes a primary cell and a secondary cell. It can be understood that in the embodiments of the present application, the serving cell may refer to the primary cell, or the serving cell may also refer to the secondary cell, or the serving cell may refer to the primary cell and the secondary cell at the same time.
  • bandwidth part bandwidth part (bandwidth part, BWP)
  • BWP is a group of continuous RB resources on the carrier.
  • a serving cell can be configured with a maximum of 4 BWPs unique to the terminal.
  • 4 BWPs can be configured for the uplink and downlink
  • 4 BWPs can be configured for the uplink and downlink under time division duplexing (TDD).
  • TDD time division duplexing
  • the terminal may only support one BWP, the bandwidth of the BWP is smaller than or equal to the UE bandwidth capability, and the UE bandwidth capability is smaller than or equal to the carrier bandwidth (carrier BW).
  • the terminal may support two BWPs, namely BWP1 and BWP2, and the bandwidths of BWP1 and BWP2 overlap each other.
  • two BWPs can be supported, namely BWP1 and BWP2, and BWP1 and BWP2 do not overlap.
  • Frequency range 1 frequency range 1, FR1
  • frequency range 2 frequency range 2, FR2
  • the frequency used for 5G communication is divided into FR1 and FR2 according to its range.
  • the frequency range corresponding to FR1 is 450MHz to 6000MHz, corresponding to the low frequency band.
  • the frequency range corresponding to FR2 is 24250MHz to 52600MHz, corresponding to the high frequency band.
  • the channel bandwidth can be different. Due to the abundant resources of the high frequency band, its channel bandwidth is generally relatively large.
  • the maximum channel bandwidth is 50MHz, and when the SCS is 30kHz or 60kHz, the maximum channel bandwidth is 100MHz.
  • the maximum channel bandwidth is 200MHz, and when the SCS is 120kHz, the maximum channel bandwidth is 400MHz.
  • TB can be expressed as a bit sequence a 0 , a 1 , a 2 , a 3 ,..., a A-1 , where A is the load size, that is, the number of bits contained in the TB, It can also be called the size of TB.
  • A is the load size, that is, the number of bits contained in the TB. It can also be called the size of TB.
  • a 0 , a 1 , a 2 , a 3 ,..., a A-1 to represent TB as an example, and introduce the encoding process of TB in detail.
  • the base picture selection of low-density parity-check can be performed according to the size of the coding rates R and A.
  • the result of LDPC base picture selection can be LDPC base picture 1 or LDPC base picture 2.
  • the generated CRC can represent p 0 ,p 1 ,p 2 ,p 3 ,...,p L-1 .
  • CBG is the result of grouping the coded blocks CB of the TB. Assume that the transport block (TB) includes C code blocks (CB). The number M of CBGs is jointly determined according to the RRC configuration value N and the number C of CBs contained in one TB.
  • the number of CBGs M is equal to C, and when N is less than C, the number of CBGs M is equal to N.
  • N is determined according to the number of CBGs configured by RRC in the existing protocol, and the value of N can be 2, 4, 6, 8, etc.
  • C is the number of CBs contained in 1 TB, and its size is determined according to the size B of TB plus CRC.
  • B A+L
  • A represents the size of TB
  • B represents the size of TB after adding CRC
  • L represents the size of CRC.
  • C CBs can be divided into M CBGs.
  • the sending end sends data
  • the receiving end can perform HARQ feedback with CBG granularity
  • the sending end can perform CBG data retransmission according to the HARQ feedback information of CBG granularity.
  • DCI Downlink control information
  • the information field of the DCI for downlink or uplink data scheduling may include CBGTI or CBGFI.
  • the number of CBGTI bits is determined according to the N value configured by RRC, and each bit represents the transmission status of each CBG. For example, “1” indicates that the corresponding CBG is transmitted, and “0" indicates that the corresponding CBG is not transmitted.
  • CBGFI indicates whether the currently transmitted CBG can be soft merged with the previously transmitted CBG. For example, “1” means it can be merged, "0” means it cannot be merged, etc.
  • TCP congestion control is a mechanism for handling network congestion through a congestion window.
  • the mainstream TCP congestion control algorithm divides the entire process of TCP connection into four stages: slow start, congestion avoidance, congestion control, and fast retransmission/recovery.
  • the sender will adjust the amount of data sent by the TCP data packet according to whether the feedback of the TCP data packet is overtime or whether the TCP data packet is lost.
  • the amount of data sent by the TCP packet can be greatly reduced, thereby reducing the amount of data sent by the upper layer to the RAN side.
  • Beam failure detection beam failure detection
  • beam failure recovery beam failure recovery
  • the process of beam failure detection and beam failure recovery may include: 1) The physical layer PHY of the terminal device reports a beam failure indication to the MAC layer of the terminal device. 2) The MAC layer of the terminal device reports upon receiving the beam failure indication and performs beam detection. If it is determined that the beam fails, random access is initiated and beam failure recovery is initiated. 3) The access network device responds to the random access of the terminal device to complete the beam failure recovery process. It should be noted that, in the example shown in FIG. 3, the detection of the beam of the PCell in FR1 is taken as an example for description, and the detection of beams of other cells is similar to the foregoing process, and will not be described here.
  • the so-called beam mismatch refers to a situation where the beam direction of the data transmitting end and the beam direction of the data receiving end do not match, which results in the incorrect transmission or reception of data.
  • the use of multiple antennas and high-frequency channels makes beamforming an important means to improve the quality of data transmission and reception.
  • beamforming can direct the beam of the signal to a specific direction, and similarly, the beam of the received signal can also be directed to a specific direction.
  • the direction of the transmitting beam and the direction of the receiving beam are the same, the maximum signal strength can be obtained, thereby improving the quality of signal reception.
  • the transmitting and receiving beams with the same direction may be called beam matching or beam alignment, and the transmitting and receiving beams with different directions may be called beam mismatch or beam (alignment) failure.
  • the signal is blocked by obstacles or the rotation or movement of the terminal direction can easily cause beam mismatch.
  • FIG. 4 a schematic diagram of a possible network architecture to which this embodiment of the application is applicable, including a terminal device 601 and an access network device 602.
  • the terminal device 601 may transmit uplink information to the access network device 602 through the Uu air interface, and the uplink information may include uplink data information and/or uplink control information.
  • the Uu air interface can be understood as a universal UE to network interface (universal UE to network interface).
  • Uu air interface transmission can include uplink transmission and downlink transmission.
  • the uplink transmission may refer to the terminal device 601 sending a signal to the access network device 602, and the downlink transmission may refer to the access network device 602 sending a signal to the terminal device 601.
  • the signal transmitted in uplink transmission may be referred to as uplink information or uplink signal, and the signal transmitted in downlink transmission may be referred to as downlink information or downlink signal.
  • a network management system 603 may also be included.
  • the terminal device 601 may communicate with the network management system 603 through a wired interface or a wireless interface.
  • the terminal device 601 may communicate with the network management system 603 through an access network device 602.
  • the network management system 603 may be a network management system of an operator.
  • the network management system 603 can also communicate with the terminal device 601 through a wired interface or a wireless interface.
  • the network management system 603 may communicate with the terminal 601 through the access network device 602.
  • a flow of a communication method is provided.
  • the flow can be applied to the initial transmission and retransmission process of uplink data, and can also be applied to the initial transmission and retransmission process of downlink data.
  • an example is used for description in the process of initial transmission and retransmission of downlink data.
  • the network device in this process may be the access network device 602 in FIG. 4, and the terminal device may be the terminal device 601 in FIG. 4, and the process is specifically:
  • the network device initially transmits first data in the first cell according to the correspondence between the first cell and the first HARQ entity.
  • the first data may specifically be first downlink data.
  • the terminal device receives the initially transmitted first data in the first cell according to the correspondence between the first cell and the first HARQ entity.
  • the network device sends first indication information to the terminal device, where the first indication information is used to indicate the correspondence between the second cell and the first HARQ entity.
  • the network device sends the retransmitted first data in the second cell according to the correspondence between the second cell and the first HARQ entity.
  • the terminal receives the retransmitted first data in the second cell according to the correspondence between the second cell and the first HARQ entity.
  • the network device may establish a correspondence between the second cell and the first HARQ entity.
  • the network device sends the first indication information to the terminal device to notify the terminal device of the correspondence between the second cell and the first HARQ entity.
  • the first indication is used to indicate the correspondence between the second cell and the first HARQ entity.
  • the network device may first establish the corresponding relationship between the first cell and the first HARQ entity, and then establish the second cell and the first HARQ entity under conditions such as the link interruption of the first cell or the beam mismatch of the first cell. Correspondence between HARQ entities. It is understandable that the foregoing scenario of establishing the corresponding relationship between the second cell and the first HARQ entity is only an exemplary description, and is not intended as a limitation to the embodiment of the present application.
  • the correspondence between the first cell and the first HARQ entity may be established first.
  • the second cell may include multiple BWPs, such as a first BWP and a second BWP.
  • the established correspondence between the second cell and the first HARQ entity may be specifically the correspondence between the first BWP and the first HARQ entity.
  • the network device may send the identification of the first BWP to the terminal device to notify the terminal device of the correspondence between the first BWP and the first HARQ entity.
  • the terminal device side may obtain the correspondence between different BWPs and HARQ entities, and according to the identity of the first BWP and the correspondence between different BWPs and HARQ entities, the correspondence between the first BWP and the first HARQ entity may be determined.
  • the correspondence between different BWPs and HARQ entities may be configured by the network device through high-level signaling, or may be pre-configured, or may be predefined by the protocol, etc.
  • the terminal device can detect the first cell. And when an abnormal situation such as a link interruption or beam mismatch of the first cell is detected, the second indication information is sent to notify the network device.
  • the second indication information may include the identifier of the first cell, the identifier of beam mismatch, and/or the identifier of beam recovery, etc.
  • the second indication information may specifically be RRC signaling, media access control control element (medium access control control element, MAC CE) signaling, uplink control information (uplink control information, UCI), etc.
  • the specific format of the RRC signaling may be as follows:
  • the specific format of the RRC signaling may be as follows:
  • the MAC CE may include the index of the first cell and the identifier of the beam failure.
  • the number of index bits of the first cell may be 4, 5, or 6 bits, etc.
  • the description is made by taking the index of the first cell of 6 bits as an example.
  • F is used to indicate the identifier of beam failure
  • Cell index indicates the index of the first cell
  • R indicates reserved bits.
  • the location information of F is 1, it may indicate that the cell indicated by the following Cell index has detected a beam failure.
  • the location information of F is 0, it can indicate that the beam of the cell indicated by the cell index has failed to recover.
  • the MAC CE may include the index of the first cell, the identifier of beam failure, and the identifier of beam recovery.
  • the number of index bits of the first cell may be 4, 5, or 6 bits, etc.
  • the description is made by taking the index of the first cell of 6 bits as an example.
  • F is used to represent the identifier of beam failure
  • Re represents the identifier of beam recovery
  • Cell index represents the index of the first cell.
  • the location information of F it may indicate that the cell indicated by the following Cell index has detected a beam failure.
  • the location information of Re is 1, it can indicate that the beam of the cell indicated by the following Cell index fails to recover.
  • the UCI may be carried in a physical uplink control channel (PUCCH) for transmission, or the UCI may be carried in a physical uplink shared channel (physical uplink shared channel, PUSCH).
  • PUCCH physical uplink control channel
  • PUSCH physical uplink shared channel
  • the first transmission of the first data is in the first cell
  • the retransmission of the first data is in the second cell.
  • the channel bandwidth of the first cell is greater than the channel bandwidth of the second cell (for example, the first cell may correspond to the cell in FR2, the channel bandwidth may be 400MHz, the second cell may correspond to the cell in FR1, and the channel bandwidth may be 100MHz)
  • the first data can be split into multiple data blocks and transmitted multiple times.
  • the data blocks transmitted multiple times may be in the same cell or in different cells.
  • the splitting of the first data into the first data block and the second data block is taken as an example for description.
  • the cell is the second cell as an example:
  • the network device may send the first DCI to the terminal device, where the first DCI is used to schedule retransmission of the first data block.
  • the first DCI is also used to indicate at least one of an index, a start identifier, or an end identifier of the first data block, and the start identifier indicates that in the retransmitted first data, the first retransmission
  • the end identifier indicates the last retransmitted data block among the retransmitted first data.
  • the network device may retransmit the first data block in the second cell according to the correspondence between the second cell and the first HARQ entity.
  • the terminal device may receive the retransmitted first data block in the second cell according to the correspondence between the second cell and the first HARQ entity.
  • the network device may send the second DCI to the terminal device, and the second DCI is used to schedule the retransmission of the second data block.
  • the second DCI is also used to indicate at least one of an index, a start identifier, or an end identifier of the second data block, and the start identifier indicates that in the retransmitted first data, the first retransmission
  • the end identifier indicates the last retransmitted data block among the retransmitted first data.
  • the network device may receive the retransmitted second data block in the second cell according to the correspondence between the second cell and the first HARQ entity.
  • the terminal device may receive the retransmitted second data block in the second cell according to the correspondence between the second cell and the first HARQ entity.
  • the first data block and the second data block in different cells, and the first data block is transmitted in the second cell, and the second data block is transmitted in the third cell as an example.
  • the third cell is different:
  • the network device may send the third DCI to the terminal device, and the third DCI is used to schedule the retransmission of the third data block.
  • the third DCI is also used to indicate at least one of an index, a start identifier, or an end identifier of the second data block, and the start identifier indicates that in the retransmitted first data, the first retransmission
  • the end identifier indicates the last retransmitted data block among the retransmitted first data.
  • the network device may send the retransmitted second data block in the third cell according to the correspondence between the third cell and the first HARQ entity.
  • the terminal device may receive the retransmitted second data block in the third cell according to the correspondence between the third cell and the first HARQ entity.
  • the above method can ensure that the transmission block size of the initial transmission and retransmission is the same.
  • the splitting of the first data into the first data block and the second data block is taken as an example for description, which is not a limitation of the present application.
  • the first data can be divided into N data blocks, the value of N can be other values except 2, and the N data blocks can be transmitted in the same cell or in different Transmission in the cell.
  • the first data can correspond to TB2
  • the first data block can correspond to CBG1
  • the second data block can correspond to CBG2.
  • TB please refer to the description of the fourteenth part of the above-mentioned term explanation, and for the introduction of CBG, refer to the description of the fifteenth part of the above-mentioned terminology.
  • the first cell may correspond to cell 2
  • the second cell may correspond to cell 1
  • the third cell may correspond to cell 3.
  • the first HARQ entity may correspond to HARQ entity 2
  • the second HARQ entity may correspond to HARQ entity 1.
  • the MAC layer on the network device side includes two data to be transmitted, TB1 and TB2.
  • TB1 transmits through cell 1
  • the data of TB1 is stored in the buffer of HARQ entity 1.
  • TB2 is transmitted through cell 2, and the data of TB2 is stored in the buffer of HARQ entity 2.
  • the corresponding relationship between HARQ entity 1 and cell 1 and the corresponding relationship between HARQ entity 2 and cell 2 can be established, and the same corresponding relationship can be maintained during initial data transmission and retransmission.
  • This correspondence between the cell and the HARQ entity can be regarded as a default correspondence between the cell and the HARQ entity.
  • the initial transmission and retransmission of TB1 are transmitted through HARQ process 0 of HARQ entity 1 in cell 1
  • the initial transmission and retransmission of TB2 are transmitted through HARQ entity 2 in cell 2.
  • the HARQ process N-1 for transmission.
  • the initial transmission and retransmission of TB1 can only be in cell 1, and the initial transmission and retransmission of TB2 can only be in cell 2.
  • the initial transmission and retransmission of TB1 can only be in cell 1
  • the initial transmission and retransmission of TB2 can only be in cell 2.
  • For data that has been initially transmitted in order to support cross-carrier data retransmission, only high-level data retransmission can change the data retransmission cell. The gain of soft information combination cannot be used, and the process time is long, causing retransmission. low efficiency.
  • the terminal device if cell 2 is blocked due to obstacles or the rotation or movement of the terminal device, the terminal device must re-align the transmit beam and/or receive beam.
  • the above beam alignment process It can be called beam recovery.
  • beam recovery please refer to the description in the eighteenth part of the above term explanation.
  • the congestion control process of the TCP layer of the sending device may enter the congestion control stage, and the data sending end actively reduces the data throughput input to the radio access network side, which reduces the data throughput performance of the entire radio access network side.
  • TCP congestion control please refer to the seventeenth part of the above term explanation.
  • this application provides the following solutions, which are the first solution and the second solution respectively.
  • the first solution may correspond to the process shown in FIG. 5 and the solution corresponding to the second embodiment.
  • the first solution is to establish a corresponding relationship between HARQ entity 2 and cell 1, and the network equipment side performs TB2 retransmission through cell 1.
  • the terminal equipment side receives the retransmitted TB2 through cell 1.
  • the MAC layer on the network device side can establish the correspondence between HARQ entity 2 and cell 1, and the MAC layer can notify the PHY layer of the correspondence between HARQ entity 2 and cell 1.
  • the PHY layer on the network device side can notify the terminal device of the corresponding relationship between HARQ entity 2 and cell 1 through the air interface. Specifically, for example:
  • cell 1 includes BWP1 and BWP2, and the correspondence between different BWPs and HARQ entities can be established in advance.
  • a corresponding relationship between BWP1 and HARQ entity 1 can be established, and BWP1 is used to transmit data in HARQ entity 1.
  • the corresponding relationship between BWP2 and HARQ entity 2 can be established, and BWP2 is used to transmit data in HARQ entity 2.
  • the configuration of BWP1 and BWP2 may be the same or different.
  • the physical resources and other related parameters configured by BWP1 and BWP2 may be the same or different.
  • BWP1 and BWP2 have the same configuration except for BWP ID, it can be considered that only the source of HARQ data sent or received by BWP is changed.
  • the source of HARQ data of BWP1 is HARQ entity 1, BWP2.
  • the source of HARQ data is HARQ entity 2, or it can be described as: changing the mapping relationship between BWP and HARQ entity.
  • the HARQ entity mapped by BWP1 is HARQ entity 1
  • the HARQ entity mapped by BWP2 is HARQ entity 2.
  • the time for the activated BWP to switch from BWP1 to BWP2 is very short, which does not affect the efficiency of data transmission.
  • BWP1 and BWP2 have different configurations except BWP ID, it can be considered that while changing the HARQ data source of BWP, it also changes the configuration of transmission resources or transmission parameters, or it can be described as: changing the BWP and HARQ entity
  • the radio frequency parameters or baseband parameters of the BWP are changed, and it takes a certain time for the activated BWP to switch from BWP1 to BWP2.
  • BWP switching can be controlled by means of RRC signaling, timer, PDCCH indication, MAC entity, etc.
  • the network side can change the correspondence between the cell and the HARQ entity by switching the activated BWP.
  • the BWP can be represented by the BWP ID
  • the HARQ entity can be represented by the HARQ entity ID
  • the HARQ entity can be represented by the cell ID corresponding to the HARQ entity by default.
  • the cell identity may be an index value configured by the cell or a cell ID.
  • the cell identifier is taken as the cell index value for illustration.
  • BWP1 corresponds to HARQ entity 1
  • BWP2 corresponds to HARQ entity 2.
  • the ID of BWP1 is 1, the ID of BWP2 is 2, the ID of HARQ entity 1 is 1, the ID of HARQ entity 2 is 2, the index of the cell corresponding to HARQ entity 1 by default is 1, and the index of cell corresponding to HRQ entity 2 by default is 2.
  • the correspondence between BWP1 and HARQ entity 1 can be expressed as: BWP ID1 corresponds to HARQ entity ID1, or BWP ID1 corresponds to cell index 1.
  • BWP2 and HARQ entity 2 can be expressed as: BWP ID2 corresponds to HARQ entity ID2, or BWP ID2 corresponds to cell index 2.
  • the first way is to add an information element (information element, IE) to the configuration of the BWP, where the IE is used to indicate the corresponding relationship between the configured BWP and the HARQ entity.
  • the IE may indicate the ID of the HARQ entity or the index of the cell.
  • BWP 1 corresponds to HARQ entity 1
  • an IE can be added to the configuration of BWP1
  • the HARQ entity ID 1 can be indicated in the IE
  • the cell index 1 can be indicated in the IE
  • BWP 2 corresponds to HARQ entity 2
  • an IE may be added to the configuration of BWP 2
  • the HARQ entity ID 2 may be indicated in the IE, or the cell index 2 may be stored in the IE.
  • the newly added IE may be called HARQ buffer mapping (HARQ buffer mapping).
  • the optional following BWP configuration is taken as an example.
  • the BWP configuration information may also include BWP ID, public downlink BWP (BWP DL common) configuration, and dedicated downlink BWP (BWP DL dedicated) configuration.
  • the public downlink BWP configuration may include a public PDCCH configuration (PDCCH-Config Comm) and a public PDSCH configuration (PDSCH-Config Comm).
  • the dedicated downlink BWP configuration can include PDCCH configuration (PDCCH Config), PDSCH configuration (PDSCH-Config), semi-persistent scheduling configuration (semi-persistent scheduling config, SPS config), radio link configuration (radiolink config), and buffer register mapping ( HARQ buffer mapping) etc.
  • the format of the downlink BWP configuration can also be expressed as:
  • the name of the newly added IE may be HARQ buffer mapping, which can refer to the bolded fields in the above example.
  • HARQ buffer mapping may include the HARQ entity ID (HARQ Entity Id). For example, if BWP 1 corresponds to HARQ entity 1, HARQ entity ID1 is included in the HARQ buffer mapping, that is, the HARQ entity ID is included in HARQ entity ID1.
  • the format of the downlink BWP configuration can also be expressed as:
  • the name of the newly added IE may be HARQ buffer mapping, which can be referred to the bolded field in the above example.
  • the HARQ buffer mapping may include a serving cell index (servCell Index).
  • serving cell index For example, if BWP1 corresponds to serving cell 1, the cell index 1 is included in the HARQ buffer mapping, that is, the cell index 1 is included in the ServCell Index.
  • BWP ID1 the identity of BWP 1 can be added to the configuration of cell 1, for example, BWP ID1.
  • a BWP2 identifier can be added in the configuration of cell 2, for example, BWP ID2.
  • the newly added IE may be called downlink BWPHARQ mapping (DL BWP HARQ mapping), and/or uplink BWPHARQ mapping (UL BWP HARQ mapping) ).
  • the cell configuration may also include downlink BWP configuration (DL BWP config) and uplink BWP configuration (UL BWP config).
  • the downlink BWP configuration may include the release and increase of the downlink BWP list
  • the uplink BWP configuration may include the release and increase of the uplink BWP list.
  • the format of the cell configuration can be expressed as:
  • the format of the cell configuration includes DL BWP HARQ mapping and UL BWP HARQ mapping.
  • DL BWP HARQ mapping and UL BWP HARQ mapping please refer to the bold part in the above cell configuration.
  • IE format of DL BWP HARQ Mapping, or UL BWP HARQ Mapping can be expressed as:
  • the correspondence between BWP ID and HARQ entity ID can be added, or the correspondence between BWP ID and serving cell index can be added.
  • the correspondence between the BWP ID and the HARQ entity ID or the correspondence between the BWP ID and the serving cell index please refer to the above-mentioned bolded part.
  • cell 1 when the activated BWP on cell 1 is BWP1, cell 1 sends the data in HARQ entity 1. It can also be said that cell 1 corresponds to HARQ entity 1. When the activated BWP on cell 1 is switched to BWP2, cell 1 sends HARQ The data in entity 2 can also be said that cell 1 corresponds to HARQ entity 2.
  • BWP1 and BWP2 are configured on cell 1, and the corresponding relationship between BWP1 and HARQ entity 2 and the corresponding relationship between BWP2 and HARQ entity 1 can be specifically configured.
  • BWP1 is used to transmit data in HARQ entity 2 on cell 2, the physical resources corresponding to BWP2 are still on cell 1.
  • the terminal device after receiving the retransmitted TB2, can determine the HARQ entity corresponding to the current BWP according to the corresponding relationship between the BWP and the HARQ entity. Then, according to the above-identified HARQ entity, it finds the buffer for storing the soft information of the TB2 that was first transmitted, merges the soft information of the first TB2 and the retransmitted soft information of TB2, and decodes, which improves the data receiving performance.
  • the second solution the MAC layer only sets one HARQ entity, and this HARQ entity corresponds to all cells.
  • the MAC layer only one HARQ entity is set in the MAC layer, and the HARQ entity corresponds to cell 1 and cell 2, that is, the HARQ entity has a corresponding relationship with both cell 1 and cell 2.
  • the retransmission of TB2 can be transferred to cell 1.
  • the MAC layer on the network device side notifies the PHY layer of the correspondence between the HARQ process and the cell.
  • the PHY layer of the network device notifies the terminal device of the correspondence between the HARQ process and the cell.
  • the network equipment side can notify the terminal equipment of the correspondence between the HARQ process and the cell by means of RRC signaling, MAC CE signaling, and DCI.
  • the HARQ process field may be included in the DCI, and the number of bits in the HARQ process field may be expanded according to the number of HARQ processes. For example, when one HARQ entity originally corresponds to one cell, and one HARQ entity includes 16 HARQ processes, the number of bits in the HARQ process field is 4 bits, and 4 bits can support the information indication of the maximum number of 16 HARQ processes. When one HARQ entity corresponds to two cells, and one HARQ entity includes 32 HARQ processes, the number of bits in the HARQ process domain needs to be expanded from 4 bits to 5 bits to support the maximum number of information indications of 32 HARQ processes.
  • the terminal device after receiving the retransmitted TB2, the terminal device needs to determine the HARQ process for transmitting TB2 according to the corresponding relationship between the HARQ process and the cell, that is, the HARQ process 2N-1 shown in FIG. 11. Then, in the buffer corresponding to HARQ process 2N-1, find the first transmission TB2. The terminal equipment softly merges and decodes the first transmitted TB2 soft information and the retransmitted TB2 soft information to improve the data receiving performance.
  • the soft information of the initial transmission and retransmission can be combined to obtain performance gains. Therefore, it is necessary to ensure the transport block size (TBS) of the initial transmission and retransmission. equal.
  • TBS transport block size
  • the channel bandwidth and quality of cell 1 and cell 2 differ greatly, or, it can be described as how to ensure the initial transmission when the channel bandwidth and quality of the initial transmission and retransmission of TB2 are greatly different It is the same as the retransmitted TBS, which is a problem to be solved in the embodiment of this application.
  • one scheduling time unit transmits one TB as an example for description, and the scheduling time unit may also be referred to as a time unit.
  • the number of bits of TB2 allocated by the network device to the terminal device can be referred to as the transmission block size of the initial transmission TB2 (TB2_TBS_initial).
  • the transmission block size of the first transmission TB2 is determined according to the number of RBs allocated by the network device to the terminal device and the MCS indication.
  • the number of RBs allocated by the network device to the terminal device may also be referred to as the number of RBs initially allocated to cell 2 (Cell 2_RBNum_initial)
  • the MCS indication may also be referred to as the MCS index initially allocated to cell 2 (Cell 2_MCS_initial index).
  • the number of RBs allocated by the network equipment to the terminal equipment is determined according to the CQI of cell 2 reported by the terminal equipment.
  • the network equipment When the retransmission of TB2 is in cell 1, the network equipment will determine the MCS of cell 1 retransmission according to the CQI information of cell 1 reported by the terminal equipment.
  • the MCS retransmitted by cell 1 may also be referred to as Cell1_MCS_ReTx. Since the transmission block size of the retransmitted TB2 on cell 1 needs to be equal to the transmission block size of the initial transmission TB2, the number of RBs required for the retransmission of TB2 in cell 1 can be transmitted by the MCS retransmitted in cell 1 and the transmission of the initial transmission TB2 The block size is determined.
  • the network equipment can allocate RBs according to normal RB resource allocation. Retransmission for TB2.
  • the number of available RBs in cell 1 may also be referred to as cell 1_RBNum_available.
  • the network device can split the retransmitted TB2 into multiple CBGs for retransmission. As shown in Figure 12, the retransmitted CBG can be transmitted on the same cell. Or, as shown in Figure 13, the retransmitted CBG can be transmitted on a different cell.
  • a network device sends a TB, and the TB includes 14 CBs, numbered 1 to 14 respectively.
  • the number of configured CBGs is 4, according to the existing CBG division rules, CB1 to CB4 belong to CBG#1,
  • CB5 to CB8 belong to CBG#2
  • CB9 to CB11 belong to CBG#3
  • CB12 to CB14 belong to CBG#4.
  • the terminal device when the terminal device receives the TB, it sends CBG1 and CBG3 transmission errors that are uncorrectable, sends a NACK to the network device side, and CBG#2 and CBG#4 are transmitted correctly, and sends an ACK to the network device side.
  • the network device After the network device receives the feedback from the terminal device, it can retransmit for CBG#1 and CBG#3.
  • the network device may send DCI to the terminal device, and the DCI is used to schedule the retransmission of CBG#1 or the retransmission of CBG#3.
  • the DCI needs to include a CBGTI field, a start indicator field, and an end indicator field.
  • the 4-bit CBGTI field can be specifically 1000, 1 means that CBG#1 is scheduled for retransmission, and 0 means that CBG#2, CBG#3, and CBG#4 are not scheduled for retransmission.
  • Retransmission Regarding the retransmission of CBG#3, the CBGTI field can be specifically 0010, 1 generation indicates that CBG#3 is scheduled for retransmission, and 0 indicates that CBG#1, CBG#2, and CBG#4 are not scheduled for retransmission.
  • the start indication field can be expressed as "start”, and the end indication field can be expressed as "end”.
  • start indicator field is 1 and the end indicator field is 0.
  • end indicator field is 1.
  • CBG#1 and CBG#3 are in different cells, that is, cell 1 and cell. 3
  • the process of retransmission is similar.
  • CBG#1 and CBG#3 can be transmitted in cell 1 at different times.
  • CBG#1 can be transmitted in cell 1 at time T1.
  • CBG#3 is transmitted in cell 1.
  • CBG#1 and CBG#3 can be simultaneously transmitted in cell 1 and cell 3. Compared with the method shown in FIG. 12, the transmission efficiency can be improved.
  • the data that was incorrectly transmitted on the second cell can be transferred to the first cell for retransmission.
  • the network device may send the fourth DCI, and the fourth DCI is used to schedule the retransmission of the second data and the third data.
  • the network device can simultaneously retransmit the second data and the third data in the first cell.
  • the terminal device can receive the second data and the third data that are retransmitted at the same time in the first cell.
  • data that is not correctly transmitted on the second cell can be transferred to the third cell for retransmission.
  • the network device may send the fourth DCI, and the fourth DCI is used to schedule the retransmission of the second data and the third data.
  • the network device can simultaneously retransmit the second data and the third data in the third cell.
  • the terminal device can receive the second data and the third data that are simultaneously transmitted in the third cell.
  • cell 1 can correspond to the second cell
  • cell 2 can correspond to the first cell or the third cell
  • TB1_0 can correspond to the second data
  • TB1_1 can correspond to the first cell.
  • Three data when the cell 2 recovers abnormally, the TB1_0 and TB1_1 initially transmitted in the cell 1 can be transferred to the cell 2 for retransmission.
  • the initial transmission of TB1_0 and TB1_1 is set in cell 1.
  • the network device can send DCI to the terminal device.
  • the DCI is used to schedule the retransmission of TB1_0 and TB1_1.
  • the device retransmits TB1_0 and TB1_1 in the second cell.
  • the DCI may include the frequency domain dynamic resource allocation of each TB, the time domain dynamic resource allocation of each TB, the number of TB indication information, the modulation and coding indication of each TB, and the new data indication of each TB. , The redundancy version indication of each TB, the HARQ process number indication information and TBS index included in each TB, etc. specific:
  • the frequency domain dynamic resource allocation of each TB indicates the frequency resources occupied by each TB transmission. This embodiment can support that each TB occupies different frequency resources. In addition, considering the saving of DCI load, multiple TBs can be transmitted through a joint frequency resource, and only one frequency domain resource allocation domain is required.
  • the time domain dynamic resource allocation of each TB indicates the time domain resources occupied by each TB transmission. This embodiment can support that each TB occupies different time domain resources. In addition, considering the saving of DCI load, multiple TBs can be sent through a joint time domain resource, and only one time domain resource allocation domain is needed.
  • the TB number indication information can indicate the number of TBs transmitted in a time unit, the total number of TBs, or the number of additional TBs in a time unit. Without considering spatial reuse, a cell can only transmit one TB in a time unit. In the embodiment of the present application, a cell can transmit N TBs in a time unit, and N>1.
  • the TB number indication information can be N or N-1. For example, in the embodiment of the present application, when the number of TBs indicates the total number of TBs, the number of TBs indicated by the TB number indication information may be 2, which are TB1_0 and TB1_1 respectively. When the number of TBs indicates the number of additional TBs, the number of TBs indicated by the TB number indication information may be 1, which means that 1 TB is transmitted on the basis of the original 1 TB.
  • Modulation and coding indication per TB can support the indication of modulation coding, new data indication and redundancy version indication for each TB.
  • This embodiment can support the indication of modulation coding, new data indication and redundancy version indication for each TB.
  • the total number of TBs is 2, there are MCS1, NDI1, RV1 and MCS2, NDI2, RV2.
  • the HARQ process number indication information included in the TB may specifically include the number indication information corresponding to the HARQ process 0 corresponding to TB1_0 and the number indication information corresponding to the HARQ process N-1.
  • the TBS index can indicate the size of a TBS, such as the size of TB1_0, or the size of TB1_1.
  • the DCI indicates that the TBS index of TB1_0 is 1, which means that the TBS size of TB1_0 is 24 bits.
  • the terminal device can determine the total TBS size of multiple TBs according to the information indication in the DCI and the system parameters through the TBS determination method in the prior art.
  • the terminal device can obtain the TBS size of another TB by subtracting the TBS size of one TB from the total TBS size.
  • the total number of TBs is N and N>1, N-1 TBS indexes need to be indicated.
  • the DCI format 1_1 for downlink scheduling is taken as an example, and the DCI indication may include the following content:
  • the terminal device can determine the total TBS size in the following ways:
  • the terminal device can obtain the n PRB parameters and the time domain resource allocation information sent by the network device parameter. According to n PRB parameters and The parameter determines the number of REs in a scheduling time unit. For example, the number of REs in a scheduling time unit can satisfy the following formula:
  • N RE min(156,N' RE ) ⁇ n PRB ;
  • N RE represents the number of REs in a scheduling time unit
  • N info N RE ⁇ R ⁇ Q m ⁇
  • N RE represents the number of REs in a scheduling time unit
  • R represents the code rate indicated in the MCS index
  • Qm is the modulation order indicated in the MCS index.
  • the intermediate number of information bits N info find a TBS value close to and not less than the number of information bits of the intermediate variable from the table shown in Table 5 below to determine the total TBS. For example, when the number of information bits of the intermediate variable is 100, the TBS is 104.
  • the total TBS can also be calculated by the number of information bits of the intermediate variable and a certain calculation rule. For example, first will pass Obtain the quantized intermediate number of information bits N′ info , where When the coding rate is less than 1/4,
  • Method 1 The terminal device notifies the network device of beam mismatch or link interruption through the air interface, and the network device initiates ARQ retransmission.
  • the specific notification method of the terminal device through the air interface refer to the record in the second embodiment above.
  • ARQ retransmission please refer to the introduction in Part 6 of the above-mentioned terminology explanation.
  • beam failure detection and beam failure recovery please refer to the introduction in Part 18 of the above-mentioned term explanation.
  • the terminal device detects cell 2 as an example for description.
  • the physical layer PHY of the terminal device reports a beam failure indication to the MAC layer of the terminal device.
  • the MAC layer of the terminal device reports upon receiving the beam failure indication and performs beam detection. And if the beam failure is detected, the MAC layer of the network device is notified through the air interface.
  • the MAC layer of the network device informs the RLC layer.
  • the RLC layer of the network device initiates ARQ retransmission. Through cell 1, the PCell or PSCell can send the retransmitted RLC SDU or RLC SDU segmented to the terminal device side.
  • Manner 2 The terminal device notifies the network device of beam failure or link failure through the status report of the RLC layer, and the network device starts ARQ retransmission.
  • the terminal device detects cell 2 as an example for description.
  • the physical layer PHY of the terminal device reports a beam failure indication to the MAC layer of the terminal device.
  • the MAC layer of the terminal device reports upon receiving the beam failure indication and performs beam detection.
  • the MAC layer on the terminal side transmits the beam failure information to the RLC layer.
  • the RLC layer of the terminal device sends an RLC status report (status report) to the network device.
  • the RLC status report contains information about the RLC SDU or RLC SDU segment not correctly received by the terminal side.
  • the RLC layer of the network device starts ARQ retransmission after receiving the RLC status report sent by the terminal. Through cell 1, the PCell or PSCell may send the incorrectly received RLC SDU or RLC SDU segment to the terminal device side.
  • the HARQ transmission framework does not need to be changed, and the initial transmission and retransmission data are not required to have the same TBS, which is simpler to implement.
  • an embodiment of the present application further provides an apparatus 1800, including a processing module 1801 and a transceiver module 1802.
  • the apparatus 1800 may be used to implement the function of the terminal device in the foregoing method.
  • the apparatus may be a terminal device or a device in a terminal device.
  • the device may be a chip system, and the chip system may be composed of a chip, or may include a chip and other discrete devices.
  • the processing module 1801 is configured to receive the initially transmitted first data in the first cell according to the correspondence between the first cell and the first hybrid automatic repeat request HARQ entity; the transceiver module 1802 is configured to receive the first data Indication information, the first indication information is used to indicate the corresponding relationship between the second cell and the first HARQ entity; the processing module 1801 is also used to set the corresponding relationship between the second cell and the first HARQ entity The retransmitted first data is received in the second cell.
  • the processing module 1801 and the transceiver module 1802 please refer to the description on the terminal device side in the foregoing method embodiment, which is not described here.
  • the apparatus 1800 may be used to implement the function of the network device in the foregoing method.
  • the apparatus may be a network device or a device in a network device.
  • the device may be a chip system, and the chip system may be composed of a chip, or may include a chip and other discrete devices.
  • the processing module 1801 is configured to initially transmit the first data in the first cell according to the correspondence between the first cell and the first hybrid automatic repeat request HARQ entity; the transceiver module 1802 is configured to send the first indication information , The first indication information is used to indicate the corresponding relationship between the second cell and the first HARQ entity; the processing module 1801 is also used to set the corresponding relationship between the second cell and the first HARQ entity The first data is retransmitted in the second cell.
  • the processing module 1801 and the transceiver module 1802 please refer to the description on the network device side in the foregoing method embodiment, which is not described here.
  • transceiver module 1802 and the processing module 1801 reference may be made to the record in the foregoing method embodiment.
  • the division of modules in the embodiments of the present application is illustrative, and is only a logical function division. In actual implementation, there may be other division methods.
  • the functional modules in the various embodiments of the present application may be integrated into one process. In the device, it can also exist alone physically, or two or more modules can be integrated into one module.
  • the above-mentioned integrated modules can be implemented in the form of hardware or software functional modules.
  • an embodiment of the present application further provides an apparatus 1900.
  • the device 1900 is used to implement the function of the terminal device in the foregoing method, and the device may be a terminal device or a device in a terminal device.
  • the apparatus 1900 includes at least one processor 1901, configured to implement the function of the terminal device in the foregoing method.
  • the processor 1901 may receive the initially transmitted first data in the first cell according to the correspondence between the first cell and the first HARQ entity.
  • the apparatus 1900 may further include at least one memory 1902 for storing program instructions and/or data.
  • the memory 1902 and the processor 1901 are coupled.
  • the coupling in the embodiments of the present application is an interval coupling or a communication connection between devices, units or modules, and may be in electrical, mechanical or other forms, and is used for information exchange between devices, units or modules.
  • the processor 1901 and the memory 1902 operate in cooperation.
  • the processor 1901 can execute program instructions stored in the memory 1902.
  • At least one of the at least one memory may be included in the processor 1901.
  • the apparatus 1901 may further include a communication interface 1903, which uses a communication transmission medium to communicate with other devices, so that the apparatus used in the apparatus 1900 can communicate with other devices.
  • the communication interface 1903 may be a transceiver, circuit, bus, module or other type of communication interface, and the other device may be a network device.
  • the processor 1901 uses the communication interface 1903 to send and receive data, and is used to implement the method in the foregoing embodiment.
  • the communication interface 1903 may receive first indication information and the like.
  • the device 1900 is used to implement the function of the network device in the above method, and the device may be a network device or a device in the network device.
  • the apparatus 1900 includes at least one processor 1901, configured to implement the function of the network device in the foregoing method.
  • the processor 1901 may initially transmit the first data in the first cell according to the correspondence between the first cell and the first HARQ entity.
  • the device 1900 may further include at least one memory 1902 for storing program instructions and/or data.
  • the memory 1902 and the processor 1901 are coupled.
  • the coupling in the embodiments of the present application is an interval coupling or a communication connection between devices, units or modules, and may be in electrical, mechanical or other forms, and is used for information exchange between devices, units or modules.
  • the processor 1901 and the memory 1902 operate in cooperation.
  • the processor 1901 can execute program instructions stored in the memory 1902.
  • At least one of the at least one memory may be included in the processor 1901.
  • the apparatus 1900 may further include a communication interface 1903 for communicating with other devices using a communication transmission medium, so that the apparatus used in the apparatus 1900 can communicate with other devices.
  • the communication interface 1903 may be a transceiver, circuit, bus, module, or other type of communication interface, and the other device may be a terminal device.
  • the processor 1901 uses the communication interface 1903 to send and receive data, and is used to implement the method in the foregoing embodiment.
  • the communication interface 1903 may send first indication information and the like.
  • the embodiment of the present application does not limit the connection medium between the communication interface 1903, the processor 1901, and the memory 1902.
  • the memory 1902, the processor 1901, and the communication interface 1903 are connected by a bus 1904 in FIG. 19, and the bus is represented by a thick line in FIG. 19.
  • the connection mode between other components is only for schematic illustration. , Is not limited.
  • the bus can be divided into address bus, data bus, control bus, etc. For ease of representation, only one thick line is used to represent in FIG. 19, but it does not mean that there is only one bus or one type of bus.
  • the processor may be a general-purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, and may implement or Perform the methods, steps, and logic block diagrams disclosed in the embodiments of the present application.
  • the general-purpose processor may be a microprocessor or any conventional processor. The steps of the method disclosed in the embodiments of the present application may be directly embodied as being executed and completed by a hardware processor, or executed and completed by a combination of hardware and software modules in the processor.
  • the memory may be a non-volatile memory, such as a hard disk drive (HDD) or a solid-state drive (SSD), etc., or a volatile memory (volatile memory), for example Random-access memory (random-access memory, RAM).
  • the memory is any other medium that can be used to carry or store desired program codes in the form of instructions or data structures and that can be accessed by a computer, but is not limited thereto.
  • the memory in the embodiments of the present application may also be a circuit or any other device capable of realizing a storage function, for storing program instructions and/or data.
  • the methods provided in the embodiments of the present application may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • software When implemented by software, it can be implemented in the form of a computer program product in whole or in part.
  • the computer program product includes one or more computer instructions.
  • the computer may be a general-purpose computer, a dedicated computer, a computer network, network equipment, user equipment, or other programmable devices.
  • the computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website, computer, server, or data center.
  • the computer-readable storage medium may 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 usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, and a magnetic tape), an optical medium (for example, a digital video disc (digital video disc, DVD for short)), or a semiconductor medium (for example, SSD).
  • “at least one” refers to one or more, and “multiple” refers to two or more.
  • “And/or” describes the association relationship of the associated objects, indicating that there can be three relationships, for example, A and/or B, which can mean: A alone exists, A and B exist at the same time, and B exists alone, where A, B can be singular or plural.
  • the character “/” generally indicates that the associated objects are in an "or” relationship.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

一种通信方法及装置，该方法包括：根据第一小区与第一混合自动重传请求HARQ实体的对应关系，在所述第一小区中接收初传的第一数据；接收第一指示信息，所述第一指示信息用于指示第二小区与所述第一HARQ实体的对应关系；根据所述第二小区与所述第一HARQ实体的对应关系，在所述第二小区中接收重传的所述第一数据。采用本申请实施例的方法及装置，可实现利用不同的小区进行数据的初传和重传。

Description

一种通信方法及装置
相关申请的交叉引用
本申请要求在2019年06月06日提交中国专利局、申请号为201910491679.1、申请名称为“一种通信方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种通信方法及装置。
背景技术
在无线通信系统中，基于混合式自动重传请求(hybrid automatic repeat request，HARQ)机制进行数据传输。其中，HARQ机制，是一种结合前向纠错(forward error correction，FEC)与自动重传请求(automatic repeat reQuest，ARQ)方法的技术。采用HARQ机制，进行数据的初传和重传，可以增加系统可靠性，提高系统传输效率。如何基于HARQ机制进行数据的初传和重传，是当前的研究热点。
发明内容
本申请提供一种通信方法及装置，以实现利用不同的小区进行数据的初传和重传。
第一方面，提供一种通信方法，包括：根据第一小区与第一混合自动重传请求HARQ实体的对应关系，在所述第一小区中接收初传的第一数据；接收第一指示信息，所述第一指示信息用于指示第二小区与所述第一HARQ实体的对应关系；根据所述第二小区与所述第一HARQ实体的对应关系，在所述第二小区中接收重传的所述第一数据。
在本申请实施例中，利用第一指示信息，指示第一HARQ实体与第二小区的对应关系，从而利用第二小区，重传第一HARQ实体所对应的第一数据；相对于，等待第一小区恢复正常，再进行第一数据的重传的方式，可提高数据的吞吐量。
在一种可能的设计中，所述第二小区中包括第一带宽部分BWP，所述第二小区与所述第一HARQ实体的对应关系，包括：所述第一BWP与所述第一HARQ实体的对应关系。
在一种可能的设计中，所述第一指示信息为所述第一BWP的标识，所述方法还包括：根据所述第一BWP的标识，确定所述第一BWP与所述第一HARQ实体的对应关系。
在一种可能的设计中，所述方法还包括：发送第二指示信息，所述第二指示信息用于指示所述第一小区的链路中断，或所述第一小区的波束失配。
在一种可能的设计中，所述第一数据中包括第一数据块，所述方法还包括：接收第一下行控制信息DCI，所述第一DCI用于调度所述第一数据块的重传；
所述根据所述第二小区与所述第一HARQ实体的对应关系，在所述第二小区中接收重传的第一数据，包括：根据所述第二小区与所述第一HARQ实体的对应关系，在所述第二小区中接收重传的所述第一数据块。
在一种可能的设计中，所述第一数据中包括第二数据块，所述方法还包括：接收第二DCI，所述第二DCI用于调度所述第二数据块的重传；
所述根据所述第二小区与所述第一HARQ实体的对应关系，接收重传的所述第一数据， 包括：根据所述第二小区与所述第一HARQ实体的对应关系，在所述第二小区中接收重传的所述第二数据块。
由上可见，在本申请实施例中，第一数据包括第一数据块和第二数据块，第一数据块和第二数据块的重传都在第二小区内，提高第二小区的利用率。
在一种可能的设计中，所述方法还包括：根据第三小区与所述第一HARQ实体的对应关系，在所述第三小区中接收重传的所述第一数据。
在一种可能的设计中，所述第一数据中包括第二数据块，所述方法还包括：接收第三DCI，所述第三DCI用于调度所述第二数据块的重传；
所述根据第三小区与所述第一HARQ实体的对应关系，在所述第三小区中接收重传的所述第一数据，包括：根据所述第三小区与所述第一HARQ实体的对应关系，在所述第三小区中接收重传的所述第二数据块。
由上可见，在本申请实施例中，第一数据包括第一数据块和第三数据块，第一数据块的重传在第二小区内，第二数据块的重传在第三小区内，可提高数据的传输效率。
在一种可能的设计中，所述第一DCI还用于指示所述第一数据块的索引、开始标识或结束标识中的至少一个，所述第二DCI或所述第三DCI还用于指示所述第二数据块的索引、开始标识或结束标识中的至少一个；其中，所述开始标识表示在重传的第一数据中，第一个重传的数据块，所述结束标识表示在重传的第一数据中，最后一个重传的数据块。
在一种可能的设计中，所述方法还包括：发送第四DCI，所述第四DCI用于调度第二数据和第三数据的重传，所述第二数据和所述第三数据的初传在所述第二小区中；在所述第一小区中重传所述第二数据和第三数据；或者，在第四小区中重传所述第二数据和第三数据。
在本申请实施例中，提供一种应用场景，第一小区或第四小区的传输带宽大于第二小区的传输带宽；第二数据和第三数据的初传在第二小区中，当第一小区异常恢复后，可在第一小区中，重传第二数据和第三数据；或者，在第四小区中重传第二数据和第三数据，提高数据的传输效率。
第二方面，提供一种通信方法，包括：根据第一小区与第一混合自动重传请求HARQ实体的对应关系，在所述第一小区中初传第一数据；发送第一指示信息，所述第一指示信息用于指示第二小区与所述第一HARQ实体的对应关系；根据所述第二小区与所述第一HARQ实体的对应关系，在所述第二小区中重传所述第一数据。
在一种可能的设计中，所述第二小区包括第一带宽部分BWP，所述第二小区与所述第一HARQ实体的对应关系包括所述第一BWP与所述第一HARQ实体的对应关系。
在一种可能的设计中，所述第一指示信息为所述第一BWP的标识。
在一种可能的设计中，所述方法还包括：接收第二指示信息，所述第二指示信息用于指示所述第一小区的链路中断，或所述第一小区的波束失配。
在一种可能的设计中，所述第一数据中包括第一数据块，所述方法还包括：发送第一下行控制信息DCI，所述第一DCI用于调度所述第一数据块的重传；
所述根据所述第二小区与所述第一HARQ实体的对应关系，在所述第二小区中重传所述第一数据，包括：根据所述第二小区与所述第一HARQ实体的对应关系，在所述第二小区中重传所述第一数据块。
在一种可能的设计中，所述第一数据中包括第二数据块，所述方法还包括：发送第二 DCI，所述第二DCI用于调度所述第二数据块的重传；
所述根据所述第二小区与所述第一HARQ实体的对应关系，在所述第二小区中重传所述第一数据，包括：根据所述第二小区与所述第一HARQ实体的对应关系，在所述第二小区中重传所述第二数据块。
在一种可能的设计中，所述方法还包括：根据第三小区与所述第一HARQ实体的对应关系，在所述第三小区中重传所述第一数据。
在一种可能的设计中，所述第一数据中包括第二数据块，所述方法还包括：发送第三DCI，所述第三DCI用于调度所述第二数据块的重传；
所述根据第三小区与所述第一HARQ实体的对应关系，在所述第三小区中重传所述第一数据，包括：根据所述第三小区与所述第一HARQ实体的对应关系，在所述第三小区中重传所述第二数据块。
在一种可能的设计中，所述第一DCI还用于指示所述第一数据块的索引、开始标识或结束标识中的至少一个，所述第二DCI或所述第三DCI还用于指示所述第二数据块的索引、开始标识或结束标识中的至少一个；其中，所述开始标识表示在重传的第一数据中，第一个重传的数据块，所述结束标识表示在重传的第一数据中，最后一个重传的数据块。
在一种可能的设计中，所述方法还包括：发送第四DCI，所述第四DCI用于调度第二数据和第三数据的重传，所述第二数据和所述第三数据的初传在所述第二小区中；在所述第一小区中重传所述第二数据和第三数据；或者，在第四小区中重传所述第二数据和第三数据。
第三方面，提供一种通信装置，该装置可以是终端设备，也可以是终端设备中的装置，或者是能够和终端设备匹配使用的装置，该装置可以包括收发模块和处理模块，且收发模块和处理模块可以执行上述第一方面任一种可能设计示例中的相应功能，具体的：
处理模块，用于根据第一小区与第一混合自动重传请求HARQ实体的对应关系，在所述第一小区中接收初传的第一数据，以及，根据所述第二小区与所述第一HARQ实体的对应关系，在所述第二小区中接收重传的所述第一数据；
收发模块，用于接收第一指示信息，所述第一指示信息用于指示第二小区与所述第一HARQ实体的对应关系。
关于收发模块和处理模块的具体功能，可参见上述第一方面实施例中的记载，在此不再说明。
第四方面，提供一种通信装置，所述装置包括处理器，用于实现上述第一方面描述的方法。所述装置还可以包括存储器，用于存储指令和数据。所述存储器与所述处理器耦合，所述处理器执行所述存储器中存储的程序指令时，可以实现上述第一方面描述的方法。所述装置还可以包括通信接口，所述通信接口用于该装置与其它设备进行通信，示例性的，通信接口可以是收发器、电路、总线、模块或其它类型的通信接口，其它设备可以为网络设备等。在一种可能的设计中，该装置包括：
存储器，用于存储程序指令；
处理器，用于根据第一小区与第一混合自动重传请求HARQ实体的对应关系，在所述第一小区中接收初传的第一数据，以及，根据所述第二小区与所述第一HARQ实体的对应关系，在所述第二小区中接收重传的所述第一数据；
通信接口，用于接收第一指示信息，所述第一指示信息用于指示第二小区与所述第一 HARQ实体的对应关系。
关于通信接口和处理器的具体功能，可参见上述第一方面实施例中的记载，在此不再说明。
第五方面，提供一种通信装置，该装置可以是网络设备，也可以网络设备中的装置，或者是能够和终端设备匹配使用的装置，该装置可以包括收发模块，且收发模块可以执行上述第二方面任一种可能设计示例中的相应功能，具体的：
处理模块，用于根据第一小区与第一混合自动重传请求HARQ实体的对应关系，在所述第一小区中初传第一数据，以及，根据所述第二小区与所述第一HARQ实体的对应关系，在所述第二小区中重传所述第一数据；
收发模块，用于发送第一指示信息，所述第一指示信息用于指示第二小区与所述第一HARQ实体的对应关系。
关于收发模块和处理模块的具体功能，可参见上述第二方面的记载，在此不再说明。
第六方面，提供一种通信装置，所述装置包括通信接口，用于实现上述第二方面描述的方法。所述通信接口用于该装置与其它设备进行通信，示例性的，通信接口可以是收发器、电路、总线、模块或其它类型的通信接口，其它设备可以为终端设备等。所述装置还包括处理器，用于执行所述存储器中存储的程序指令时，可以控制所述通信接口实现上述第一方面描述的方法。所述装置还可以包括存储器，用于存储指令和数据，在一种可能的设计中，该装置包括：
存储器，用于存储程序指令；
处理器，用于根据第一小区与第一混合自动重传请求HARQ实体的对应关系，在所述第一小区中初传第一数据，以及，根据所述第二小区与所述第一HARQ实体的对应关系，在所述第二小区中重传所述第一数据。
通信接口，用于发送第一指示信息，所述第一指示信息用于指示第二小区与所述第一HARQ实体的对应关系。
关于通信接口以及处理器的具体功能，可参见上述第二方面的记载，在此不再说明。
第七方面，本申请实施例还提供一种计算机可读存储介质，包括指令，当其在计算机上运行时，使得计算机执行第一方面或第二方面任一种可能设计的方法。
第八方面，本申请实施例还提供一种芯片系统，该芯片系统包括处理器，还可以包括存储器，用于实现第一方面或第二方面的方法。该芯片系统可以由芯片构成，也可以包含芯片和其他分立器件。
第九方面，本申请实施例中还提供一种计算机程序产品，包括指令，当其在计算机上运行时，使得计算机执行第一方面或第二方面的方法。
第十方面，本申请实施例提供一种系统，所述系统包括第三方面所述的装置和第五方面所述的装置，或者，所述系统包括第四方面所述的装置和第六方面所述的装置。
附图说明
图1为本申请实施例提供的数据传输的协议栈架构示意图；
图2为本申请实施例提供的载波聚合下MAC实体、HARQ实体、HARQ进程和HARQ buffer关系示意图；
图3为本申请实施例提供的波束失败检测和波束失败恢复的示意图；
图4为本申请实施例提供的通信系统的一架构图；
图5为本申请实施例提供的通信方法的一流程图；
图6为本申请实施例提供的RRC的一示意图；
图7为本申请实施例提供的RRC的另一示意图；
图8为本申请实施例提供的TB1和TB2传输的一示意图；
图9为本申请实施例提供的TB2重传的一示意图；
图10为本申请实施例提供的BWP配置的一示意图；
图11为本申请实施例提供的TB2重传的一示意图；
图12和图13为本申请实施例提供的TB2重传的一示意图；
图14为本申请实施例提供的TB1重传的一示意图；
图15和图16为本申请实施例提供的ARQ重传的示意图；
图17为本申请实施例提供的小区配置的示意图；
图18为本申请实施例提供的通信装置的一结构示意图；
图19为本申请实施例提供的通信装置的一结构示意图。
具体实施方式
为了便于理解，示例性的给出了与本申请相关概念的说明以供参考，可以理解的是，相关概念的说明也作为本申请实施例的一部分内容，具体如下：
一、网络设备
网络设备可以是接入网设备，接入网设备也可以称为无线接入网(radio access network，RAN)设备，是一种为终端设备提供无线通信功能的设备。接入网设备例如包括但不限于：5G中的下一代基站(generation nodeB，gNB)、演进型节点B(evolved node B，eNB)、无线网络控制器(radio network controller，RNC)、节点B(node B，NB)、基站控制器(base station controller，BSC)、基站收发台(base transceiver station，BTS)、家庭基站(例如，home evolved nodeB，或home node B，HNB)、基带单元(baseband unit，BBU)、收发点(transmitting and receiving point，TRP)、发射点(transmitting point，TP)、移动交换中心等。接入网设备还可以是云无线接入网络(cloud radio access network，CRAN)场景下的无线控制器、集中单元(centralized unit，CU)，和/或分布单元(distributed unit,DU)，或者网络设备可以为中继站、接入点、车载设备、终端设备、可穿戴设备以及未来5G网络中的网络设备或者未来演进的PLMN网络中的网络设备等。终端设备可以与不同技术的多个接入网设备进行通信，例如，终端设备可以与支持长期演进(long term evolution，LTE)的接入网设备通信，也可以与支持5G的接入网设备通信，还可以与支持LTE的接入网设备以及支持5G的接入网设备的双连接。本申请实施例并不限定。
本申请实施例中，用于实现网络设备的功能的装置可以是网络设备；也可以是能够支持网络设备实现该功能的装置，例如芯片系统，该装置可以被安装在网络设备中。在本申请实施例提供的技术方案中，以用于实现网络设备的功能的装置是网络设备，以网络设备是基站为例，描述本申请实施例提供的技术方案。
二、终端设备
终端设备可以简称为终端，是一种具有无线收发功能的设备，终端设备可以部署在陆地上，包括室内或室外、手持或车载；也可以部署在水面上(如轮船等)；还可以部署在 空中(例如飞机、气球和卫星上等)。所述终端设备可以是手机(mobile phone)、平板电脑(pad)、带无线收发功能的电脑、虚拟现实(virtual reality，VR)终端设备、增强现实(augmented reality，AR)终端设备、工业控制(industrial control)中的无线终端设备、无人驾驶(self driving)中的无线终端设备、远程医疗(remote medical)中的无线终端设备、智能电网(smart grid)中的无线终端设备、运输安全(transportation safety)中的无线终端设备、智慧城市(smart city)中的无线终端设备、智慧家庭(smart home)中的无线终端设备，以及还可以包括用户设备(user equipment，UE)等。终端设备还可以是蜂窝电话、无绳电话、会话启动协议(session initiation protocol，SIP)电话、无线本地环路(wireless local loop，WLL)站、个人数字助理(personal digital assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备，未来第五代(the 5th generation，5G)网络中的终端设备或者未来演进的公用陆地移动通信网络(public land mobile network，PLMN)中的终端设备等。终端设备有时也可以称为终端设备、用户设备(user equipment，UE)、接入终端设备、车载终端设备、工业控制终端设备、UE单元、UE站、移动站、移动台、远方站、远程终端设备、移动设备、UE终端设备、终端设备、无线通信设备、UE代理或UE装置等。终端设备也可以是固定的或者移动的。本申请实施例对此并不限定。
本申请实施例中，用于实现终端的功能的装置可以是终端；也可以是能够支持终端实现该功能的装置，例如芯片系统，该装置可以被安装在终端中。本申请实施例中，芯片系统可以由芯片构成，也可以包括芯片和其他分立器件。本申请实施例提供的技术方案中，以用于实现终端的功能的装置是终端，以终端是UE为例，描述本申请实施例提供的技术方案。
三、载波聚合(carrier aggregation，CA)
载波聚合是将至少2个载波单元(component carrier，CC)聚合在一起，以支持更大传输带宽的技术。为了高效地利用零碎的频谱，载波聚合支持不同载波单元之间的聚合，比如，相同或不同带宽内载波单元的聚合，或者，同一频带内，邻接或非邻接载波单元间的聚合，或者，不同频带内载波单元间的聚合等。
四、数据传输的协议栈
如图1所示，在用户面数据传输的协议栈中，终端设备侧(例如UE)从上至下，依次包括应用协议(application protocol，APP)层、传输控制协议(transmission control protocol，TCP)层、网络协议(internet protocol，IP)层、服务数据适配协议(service data adaptation protocol，SDAP)层、分组数据汇聚协议(packet data convergence protocol，PDCP)层、无线链路控制(radio link control，RLC)层、媒体接入控制(medium access control，MAC)层和物理(physical，PHY)层等。接入网侧(例如gNB)从上至下，依次包括SDAP层、PDCP层、RLC层、MAC层和PHY层等。核心网侧(例如core)可包括IP层等。服务器侧(例如server)从上至下，依次包括APP层、TCP层和IP层等。
以终端设备从服务器下载数据为例，图1所示的黑色箭头表示在数据下载过程中，数据在各个协议栈中的主要流向。需要说明的是，在接入网侧，上述SDAP层至PHY层是RAN侧的空口协议栈，并不作为对本申请的限定。比如，在一些示例中，所述接入网侧，还可包括其他有线传输部分的协议栈等。
五、混合式自动重传请求(hybrid automatic repeat request，HARQ)
HARQ重传是MAC层的数据重传机制，是一种结合前向纠错(forward error correction，FEC)与自动重传请求(automatic repeat reQuest，ARQ)方法的技术。
示例的，接收端在接收到发送端发送的数据包后，可使用检错码，来检测接收的数据包是否出错，比如，所述检错码可为循环冗余校验(cyclic redundancy check,CRC)码等。如果数据包无错，则接收端发送肯定确定(acknowledge，ACK)至发送端。如果数据包有错，则接收端首先使用前向纠错((forward error correction，FEC)纠正错误。若FEC可纠正错误，则接收端可发送ACK至发送端。若FEC无法纠正错误，则接收端可发送否定确认(negative acknowledgement，NACK)至发送端。
其中，针对接收端发送NACK的情况，即针对上述FEC无法纠正错误的数据包，接收端可丢弃上述错误的数据包或者把上述错误的数据包保存下来，以待重传数据后，可以与重传数据进行合并。示例的，对于ACK可用‘1’表示，对于NACK可用‘0’来表示；收发端通过HARQ机制可以增加系统可靠性，提高系统传输效率。
六、自动重传请求(automatic repeat request，ARQ)
ARQ重传是RLC层的数据重传机制，重传的数据为RLC服务数据单元(service data unit，SDU)，或者，重传的数据为RLC SDU的分段。发送端可基于接收端发送的NACK，触发RLC层的ARQ重传。或者，当发送端的RLC发送定时器超时时，触发RLC层的ARQ重传。
HARQ与ARQ的最大不同之处在于：采用ARQ技术，如果接收端发现数据包传错了，将丢弃原数据包，然后申请数据包的重传。而采用HARQ技术，如果接收端发现数据包传错了，将保留传错的原数据包，然后申请数据包的重传。最后，接收端将重传的数据包与原数据包进行合并，以获得分集增益，所述分集增益，也可称为软合并增益。并且结合编码方式，可针对不同次的重传将编码的冗余位进行不同的保留，以获得分集增益。
通过以上记载，可以看出，ARQ机制采用丢弃数据包并请求重传的方式。而HARQ机制采用将原数据包与重传数据包合并，以获得分集增益的方法。可以理解的是，针对传输错误的数据包，虽然初始的原数据包无法被正确解码，但其中还是包含了有用的信息，如果丢弃了，相应的，有用的信息也丢失了。
在本申请实施例中，HARQ机制可使用带软合并的HARQ(HARQ with soft combining)机制。所述软合并的过程可为：接收端在接收到错误的数据包后，可将错误的数据包保存在一个HARQ缓存寄存器(buffer)中，并与后续接收到的重传数据包进行合并，从而得到一个比单独解码更可靠的数据包。然后对合并后的数据包进行解码，如果还是失败，则重复“请求重传，再进行软合并”的过程。
在本申请实施例中，根据重传的比特信息与原始传输是否相同，软合并的HARQ可包括追赶合并(chase combining)和增量冗余(incremental redundancy)两类。在追随合并中，重传数据包与原始数据包的比特信息相同；在增量冗余中，重传数据包与原始数据包的比特信息可不同。
比如，在增量冗余中，发送端可生成多个编码比特(coded bit)的集合，每个编码比特集合可携带相同的信息，即编码输入信息相同。当发送端需要进行数据重传时，发送端可选择与前一次不同的编码比特集合。相应的，接收端可把重传的数据与前一次传输的数据进行合并。每次重传的编码比特集合可称为一个冗余版本(redundancy version，RV)。
七、HARQ实体
在接入网的高层协议框架中，CA仅对MAC层可见，关于接入网的高层协议框架可参 见图1中的记载，在此不再说明。如图2所示，终端设备在未配置为双连接(dual-connectivity，DC)的情况下，MAC层只有一个MAC实体。终端设备在配置为DC的情况下，MAC层有两个MAC实体。载波聚合中的每个小区对应一个HARQ实体，比如，在图2所示的示例中，n个服务小区可共对应于n个HARQ实体。一个HARQ实体对应一组HARQ进程(process)，每个HARQ进程对应一个HARQ缓存寄存器(buffer)。
针对发送端，HARQ缓存寄存器用于存放发送的传输块(transport block,TB)。比如，未收到正确反馈的TB。针对接收端，HARQ缓存寄存器用来存放TB的译码软信息等。
需要注意的是，在一个时间单元内，每个HARQ进程只能处理一个TB，一个HARQ和一个TB相对应。所述时间单元的单位可以是子帧、时隙、或符号等，一个时间单元可包括一个子帧、或一个时隙，或一个或多个符号等。相应的，在接收端，每个HARQ进程都有独立的HARQ缓存寄存器，以便对接收到的数据进行软合并。在空分复用中，一个时间单元会并行传输2个TB，每个TB有各自独立的HARQ确认信息，并使用不同的HARQ进程来处理。此时1个HARQ实体可包含2个HARQ进程集合。
需要说明的是，在本申请实施例中，HARQ实体用于控制HARQ进程，小区与HARQ实体的关联，还可以描述为小区与HARQ进程的关联等。网络设备或终端设备的MAC层包括MAC实体。网络设备或终端设备的MAC实体用来处理下述一种或多种传输信道：广播信道(broadcast channel,BCH)、下行共享信道(downlink shared channel,DL-SCH)、寻呼信道(paging channel,PCH)、上行共享信道(uplink shared channel,UL-SCH)、随机接入信道(random access channel,RACH)。对于上行链路和下行链路，MAC实体负责将逻辑信道映射到传输信道上。逻辑信道即支持特定类型信息传输的通道，每种逻辑信道由其传输的信息类型所定义，包括广播控制信道(broadcast control channel，BCCH)、寻呼控制信道(paging control channel，PCCH)、公共控制信道(common control channel，CCCH)、专用控制信道(dedicated control channel，DCCH)、专用业务信道(dedicated traffic channel，DTCH)，用于传输小区的广播信息、寻呼信息、公共控制信息、专用控制信息和专用业务数据。MAC实体包括HARQ实体，HARQ实体用于维护多个并行HARQ进程，下行数据传输时终端的HARQ实体将DL-SCH上接收的HARQ信息和关联的TB指向对应的HARQ进程。当物理层没有配置空间复用时，一个HARQ进程支持一个TB。其中用于DL-SCH或UL-SCH传输的HARQ信息包括新数据指示(NDI)、传输块大小(TBS)、冗余版本(RV)和HARQ进程号等。
八、主小区(primary cell，Pcell)
主小区可以是终端设备进行初始连接建立的小区，或者，主小区可以是终端设备进行无线资源控制(radio resource control，RRC)连接重建的小区，或者，主小区可以是在切换(handover)过程中指定的主小区等。主小区，主要用于与终端设备之间的RRC通信。主小区对应的载波单元称为主载波单元(primary component carrier，PCC)，主载波单元的下行载波称为下行主载波单元(down link PCC，DL PCC)，主载波单元的上行载波称为上行主载波单元(up link PCC，UL PCC)。
九、辅小区(secondary cell，Scell)
辅小区可以是与终端设备之间不存在RRC通信的小区，主要用于提供额外的无线资源。所述辅小区可以是在RRC重配置时添加的。辅小区对应的载波单元成为辅载波单元(secondary component carrier，SCC)。辅载波单元的下行载波称为下行辅载波单元(down  link SCC,DL SCC)，辅载波单元的上行载波称为上行辅载波单元(uplink SCC，UL SCC)。
示例的，主小区可以是在连接建立时确定的，辅小区可以是在初始接入完成之后，通过RRC连接重配置消息添加、修改或释放的。
十、服务小区(serving cell)
服务小区可以是为终端设备提供上下行传输服务的小区。如果终端设备处于RRC连接(RRC_CONNECTED)态但并未配置CA，则该终端设备只有一个服务小区，该服务小区可为主小区；如果终端设备处于RRC连接(RRC_CONNECTED)态且配置了CA，则该终端设备可包括一个服务小区集合，且该服务小区集合中包括主小区和辅小区。可以理解的是，在本申请实施例中，服务小区可以指代主小区，或者，服务小区也可以指代辅小区，或者，服务小区可以同时指代主小区和辅小区等。
十一、带宽部分(bandwidth part，BWP)
BWP是载波上一组连续的RB资源。在新无线接入技术(new radio access technique，NR)的版本(release)15中规定，对于一个终端设备，一个服务小区最多可以配置4个该终端特有的BWP，其中，在频分双工(frequency division duplexing，FDD)下，上下行可各配置4个BWP，在时分双工(time division duplexing，TDD)下，上下行可各配置4个BWP。在任一时刻，仅能激活一个BWP，终端设备和网络设备在激活的BWP上进行数据的收发。在载波宽带(carrier BW)内，终端可仅支持一个BWP，所述BWP的带宽小于或等于UE带宽能力(UE bandwidth capability)，UE带宽能力小于或等于载波带宽(carrier BW)。或者，在载波带宽中，终端可支持两个BWP，分别为BWP1和BWP2，且BWP1和BWP2的带宽相互重叠。或者，在载波带宽中，可支持两个BWP，分别为BWP1和BWP2，且BWP1和BWP2不重叠。
十二、频率范围1(frequency range 1，FR1)和频率范围2(frequency range 2，FR2)
如表1所示，在NR协议中，将用于5G通信的频率，按照其范围分为FR1和FR2。FR1对应的频率范围为450MHz至6000MHz，对应低频频段。FR2对应的频率范围为24250MHz至52600MHz，对应高频频段。位于不同FR，信道带宽可以不同。由于高频段的资源丰富，其信道带宽一般比较大。
表1频率范围的定义
Figure PCTCN2020094750-appb-000001
如表2所示，针对FR1，当子载波间隔SCS为15kHz时，最大支持50MHz的信道带宽，当SCS为30kHz或60kHz时，最大支持100MHz的信道带宽。如表3所示，针对FR2，当SCS为60kHz时，最大支持200MHz的信道带宽，当SCS为120kHz时，最大支持400MHz的信道带宽。
表2 FR1中不同系统参数下信道带宽、传输带宽配置NRB对应表
Figure PCTCN2020094750-appb-000002
表3 FR2中不同系统参数下信道带宽、传输带宽配置NRB对应表
Figure PCTCN2020094750-appb-000003
十三、传输块(transport block，TB)的编码过程
在本申请实施例中，可将TB表示为比特序列a 0,a 1,a 2,a 3,...,a A-1，其中A是负载大小，也就是TB所包含的比特数，也可以称为TB的大小。在以下示例中，将用a 0,a 1,a 2,a 3,...,a A-1表示TB为例，详细介绍TB的编码过程。
在本申请实施例中可根据编码率R和A的大小，进行低密度奇偶校验(low-density parity-check，LDPC)的基图选择。其中，LDPC基图选择的结果可为LDPC基图1或LDPC基图2。根据a 0,a 1,a 2,a 3,...,a A-1，产生CRC，产生的CRC可表示p 0,p 1,p 2,p 3,...,p L-1。对TB添加CRC。其中，添加CRC后的TB大小可表示为：B＝A+L，L表示添加的CRC的大小，B表示添加CRC后TB的大小。进一步的，对TB进行CB分段，以及对分段后的CB加CRC，然后对CB进行信道编码、速率匹配以及CB串接等。
十四、编码块组(code block group，CBG)传输
CBG是将TB的编码块CB进行分组的结果。假设传输块(transport block，TB)包括C个编码块(code block，CB)。所述CBG的个数M是根据RRC的配置值N以及1个TB所包含的CB个数C共同决定的。
在一个时间单元只有一个码字(codeword)传输的前提下，当N大于或等于C时，CBG的个数M等于C，当N小于C时，CBG的个数M等于N。或者，关于CBG的个数M，也可采用以下公式描述：M＝min(N,C)。
其中，N是根据现有协议中RRC配置的CBG个数所确定的，N的取值可为2,4,6,8等。C是1个TB所包含的CB个数，其大小是根据TB加CRC后的大小B来确定的。示例的，B＝A+L，A代表TB的大小，B代表TB增加CRC后的大小，L代表CRC的大小。
根据确定后的CBG个数M，和一定的映射准则，可以将C个CB分到M个CBG中。当发送端进行数据发送时，接收端可以以CBG为粒度进行HARQ反馈，发送端可以根据CBG粒度的HARQ反馈信息进行CBG的数据重传。
十五、CBG传输的下行控制信息(down control information，DCI)指示
为了支持CBG粒度的数据传输，在下行或上行数据调度的DCI的信息域中可包括CBGTI或CBGFI。其中，CBGTI的位数是根据RRC配置的N值确定的，每个比特表示各个 CBG的传输情况。比如，“1”表示对应CBG被传输了，“0”表示对应CBG没有被传输。CBGFI表示当前传输的CBG是否可以和之前传输的CBG进行软合并。比如，“1”表示可以合并，“0”表示不能合并等。
十六、TCP的拥塞控制
TCP拥塞控制是通过拥塞窗口处理网络拥塞现象的一种机制。主流的TCP拥塞控制算法将TCP连接的整个过程分为慢启动、拥塞避免、拥塞控制和快速重传/恢复四个阶段。其中，在拥塞控制阶段，发送端会根据TCP数据包的反馈是否超时或TCP数据包是否丢失的检测，调整TCP数据包发送的数据量。当检测到TCP数据包的反馈超时或数据包丢失时，可大幅降低TCP数据包发送的数据量，从而减少了上层发送到RAN侧的数据量。
十七、波束失败检测(beam failure detection)和波束失败恢复(beam failure recovery)
如图3所示，波束失败检测和波束失败恢复的过程可包括：1)终端设备的物理层PHY进行波束失败指示上报(beam failure indication)至终端设备MAC层。2)终端设备的MAC层在接收到所述波束失败指示上报，进行波束检测。如果确定波束失败，则发起随机接入，启动波束失败恢复。3)接入网设备响应终端设备的随机接入，完成波束失败恢复的过程。需要说明的是，在图3所示的示例中，是以检测FR1中的PCell的波束为例进行说明，检测其它小区的波束与上述过程相似，在此不再说明。
十八、波束失配
所谓波束失配，是指数据发送端的波束方向和数据接收端的波束方向不匹配而导致数据无法正确发送或接收的情况。在5G通信系统中，多天线和高频信道的使用使得波束赋形成为提高数据收发质量的重要手段。通过用于发送信号的多天线上信号的相位和/或幅度的调整，波束赋形可以使信号发送的波束指向特定的方向，同理也可以使接收信号的波束指向特定的方向。当发送波束的方向和接收波束的方向一致时，可以获得最大的信号强度，从而提高信号接收的质量。相反如果发送波束的方向和接收波束的方向相差较大时会导致信号无法正确接收。方向一致的发送和接收波束可以称为波束匹配，或波束对准，方向不一致的发送和接收波束可以称为波束失配，或波束(对准)失败。在高频信道下，信号受到障碍物阻挡或终端方向的转动或移动容易导致波束失配。
可以理解的是，在本申请的描述中，“第一”、“第二”等词汇，仅用于区分描述的目的，而不能理解为指示或暗示相对重要性，也不能理解为指示或暗示顺序。由于一个小区只包含一个下行载波，因此本申请实施例中的“小区”和“载波”可以等价使用。如无特别说明，本申请实施例中以小区为例进行说明。
如图4所示，为本申请实施例适用的一种可能的网络架构示意图，包括终端设备601和接入网设备602。
终端设备601可以通过Uu空口向接入网设备602传输上行信息，所述上行信息可包括上行数据信息和/或上行控制信息。其中，Uu空口可以理解为通用的UE和网络之间的接口(universal UE to network interface)。Uu空口的传输可以包括上行传输和下行传输。其中上行传输可以是指终端设备601向接入网设备602发送信号，下行传输可以是指接入网设备602向终端设备601发送信号。上行传输中所传输的信号可以称为上行信息或上行信号，下行传输中所传输的信号可以称为下行信息或下行信号。
可选的，在图4所示的网络架构下，还可包括网管系统603。终端设备601可以通过有线接口或无线接口与网管系统603通信，比如在一种实现方式中，终端设备601可以通 过接入网设备602与网管系统603进行通信。在具体实现中，该网管系统603可以是运营商的网管系统。同理，网管系统603也可以通过有线接口或无线接口与终端设备601进行通信。比如，在一种实现方式中，网管系统603可以通过接入网设备602与终端601进行通信。
如图5所示，提供一种通信方法的流程，该流程可应用于上行数据的初传和重传过程，也可应用于下行数据的初传和重传过程中。在本申请实施例中，以应用于下行数据的初传和重传过程中为例进行说明。该流程中的网络设备可为上述图4中的接入网设备602，终端设备可为上述图4中的终端设备601，该流程具体为：
S701.网络设备根据第一小区与第一HARQ实体的对应关系，在所述第一小区中初传第一数据。可选的，第一数据可具体为第一下行数据。
S702.终端设备根据第一小区与第一HARQ实体的对应关系，在所述第一小区中接收初传的第一数据。
S703.网络设备向终端设备发送第一指示信息，所述第一指示信息用于指示第二小区与所述第一HARQ实体的对应关系。
S704.网络设备根据第二小区与第一HARQ实体的对应关系，在第二小区中发送重传的第一数据。
S705.终端根据第二小区与第一HARQ实体的对应关系，在第二小区中接收重传的第一数据。
在一示例中，网络设备可建立第二小区与第一HARQ实体的对应关系。网络设备向终端设备发送第一指示信息，以通知终端设备第二小区与第一HARQ实体的对应关系。所述第一指示用于指示第二小区与第一HARQ实体的对应关系。可选的，网络设备可首先建立第一小区与第一HARQ实体的对应关系，在第一小区的链路中断，或第一小区的波束失配等条件下，再建立第二小区与第一HARQ实体的对应关系。可以理解的是，上述建立第二小区与第一HARQ实体对应关系的场景仅为示例性说明，并不作为对本申请实施例的限定。
在另一示例中，可首先建立第一小区与第一HARQ实体的对应关系。在第一小区的链路中断，或第一小区的波束失配等条件时，可建立第二小区与第一HARQ实体的对应关系。第二小区中可包括多个BWP，比如第一BWP和第二BWP等。上述所建立的第二小区与第一HARQ实体的对应关系，可具体为第一BWP与第一HARQ实体的对应关系。此时，网络设备可向终端设备发送第一BWP的标识，以通知终端设备第一BWP和第一HARQ实体的对应关系。终端设备侧可获取不同BWP与HARQ实体的对应关系，根据第一BWP的标识，以及不同BWP与HARQ实体的对应关系，可确定第一BWP与第一HARQ实体的对应关系。示例的，不同BWP与HARQ实体的对应关系，可为网络设备通过高层信令配置的，或者可为预先配置的，或者可为协议预定义的等。
在本申请实施例中，终端设备可对第一小区进行检测。且当检测到第一小区的链路中断或波束失配等异常情况时，发送第二指示信息，以通知网络设备。所述第二指示信息中可包括第一小区的标识，波束失配的标识，和/或波束恢复的标识等。可选的，所述第二指示信息可具体为RRC信令、媒体接入控制控制元素(medium access control control element，MAC CE)信令或上行控制信息(uplink control information，UCI)等。
示例的，当第二指示信息为RRC信令，且当该RRC信令中包括第一小区的标识，以及波束失配的标识时，该RRC信令的具体格式可如下：
Figure PCTCN2020094750-appb-000004
示例的，当第二指示信息为RRC信令，且该RRC信令中包括第一小区的标识、波束失配的标识或波束恢复的标识时，该RRC信令的具体格式可如下：
Figure PCTCN2020094750-appb-000005
示例的，如图6所示，当第二指示信息为MAC CE信令时，所述MAC CE中可包括第一小区的索引，波束失败的标识。其中，第一小区的索引位数可以为4位、5位或6位等，在图6所示的示例中，是以第一小区的索引为6位为例进行说明的。可以理解的是，在图6所示的示例中，F用于表示波束失败的标识，Cell index表示第一小区的索引，R表示保留比特。示例的，当F所在的位置信息为1时，可以表示后面Cell index所指示的小区检测到了波束失败。当F所在的位置信息为0时，可以表示后面Cell index所指示的小区波束失败恢复。
示例的，如图7所示，当第二指示信息为MAC CE信令时，所述MAC CE中可包括第一小区的索引、波束失败的标识和波束恢复的标识。其中，第一小区的索引位数可以为4位、5位或6位等，在图7所示的示例中，是以第一小区的索引为6位为例进行说明的。可以理解的是，在图7所示的示例中，F用于表示波束失败的标识，Re表示波束恢复的标识，Cell index表示第一小区的索引。示例的，当F所在的位置信息为1时，可以表示后面Cell index所指示的小区检测到了波束失败。Re所在的位置信息为1时，可以表示后面Cell index所指示的小区波束失败恢复。
示例的，当第二指示信息为UCI时，所述UCI可携带在物理上行控制信道(physical uplink control channel，PUCCH)中传输，或所述UCI可以携带在物理上行共享信道(physical uplink shared channel，PUSCH)中传输。
通过上述记载可知，第一数据的初传在第一小区中，第一数据的重传在第二小区中。当第一小区的信道带宽大于第二小区的信道带宽时(比如，第一小区可对应于FR2中的小区，信道带宽可为400MHz，第二小区可对应于FR1中的小区，信道带宽可为100MHz)，为了保证初传和重传数据对应的原始信息数据相同，可在重传第一数据时，将第一数据拆分成多个数据块，分多次传输。所述多次传输的数据块可在同一个小区中，也可在不同的小区中。在本申请实施例中，以将第一数据拆分为第一数据块和第二数据块为例进行说明。
示例的，以第一数据块和第二数据块在同一个小区中，且该小区为第二小区为例进行说明：
网络设备可向终端设备发送第一DCI，所述第一DCI用于调度第一数据块的重传。可选的，所述第一DCI还用于指示所述第一数据块的索引、开始标识或结束标识中的至少一个， 所述开始标识表示在重传的第一数据中，第一个重传的数据块，所述结束标识表示在重传的第一数据中，最后一个重传的数据块。网络设备可根据第二小区与第一HARQ实体的对应关系，在第二小区中重传第一数据块。相应的，终端设备可根据第二小区与第一HARQ实体的对应关系，在第二小区中接收重传的第一数据块。
网络设备可向终端设备发送第二DCI，第二DCI用于调度第二数据块的重传。可选的，所述第二DCI还用于指示所述第二数据块的索引、开始标识或结束标识中的至少一个，所述开始标识表示在重传的第一数据中，第一个重传的数据块，所述结束标识表示在重传的第一数据中，最后一个重传的数据块。网络设备可根据第二小区与第一HARQ实体的对应关系，在第二小区中接收重传的第二数据块。相应的，终端设备可根据第二小区与第一HARQ实体的对应关系，在第二小区中接收重传的第二数据块。
示例的，以第一数据块和第二数据块在不同小区中，且第一数据块在第二小区中传输，第二数据块在第三小区中传输为例进行说明，且第二小区与第三小区不同：
关于网络设备重传第一数据块的过程，可参见上述示例的记载，在此不再说明。
网络设备可向终端设备发送第三DCI，第三DCI用于调度第三数据块的重传。可选的，所述第三DCI还用于指示所述第二数据块的索引、开始标识或结束标识中的至少一个，所述开始标识表示在重传的第一数据中，第一个重传的数据块，所述结束标识表示在重传的第一数据中，最后一个重传的数据块。网络设备可根据第三小区与第一HARQ实体的对应关系，在第三小区中发送重传的第二数据块。相应的，终端设备可根据第三小区与第一HARQ实体的对应关系，在第三小区中接收重传的第二数据块。
当初传和重传信道带宽和质量有较大差异时，采用上述方法可保证初传和重传的传输块大小相同。可以理解的是，在本申请实施例中，以将第一数据拆分为第一数据块和第二数据块为例进行说明，并不作为对本申请的限定。比如，可将第一数据拆分为N个数据块，所述N的取值，可为除2外的其它取值，所述N个数据块可在同一个小区中传输，也可在不同的小区中传输。
在本申请实施例中，提供以下应用场景，在该应用场景中：第一数据可对应于TB2，第一数据块可对应于CBG1，第二数据块可对应于CBG2。关于TB的解释可参见上述术语解释第十四部分的说明，关于CBG的介绍可参见上述术语解释第十五部分的说明。第一小区可对应于小区2，第二小区可对应于小区1，第三小区可对应于小区3。第一HARQ实体可对应于HARQ实体2，第二HARQ实体可对应于HARQ实体1。
在一示例中，如图8所示，网络设备侧的MAC层包括TB1和TB2两个数据待传输。其中，初次传输时，TB1通过小区1进行传输，则TB1的数据存放在HARQ实体1的缓冲区内。TB2通过小区2进行传输，则TB2的数据存放在HARQ实体2的缓冲区内。
在本申请实施例中，可建立HARQ实体1与小区1的对应关系，以及HARQ实体2与小区2的对应关系，在数据初传和重传时维持相同的对应关系。这种小区和HARQ实体的对应关系，可以看作是一种默认的小区和HARQ实体的对应关系。针对上述示例，如图8所示,TB1的初传和重传都通过小区1中的HARQ实体1的HARQ进程0进行传输，TB2的初传和重传都通过小区2中的HARQ实体2中的HARQ进程N-1进行传输。可见，在该示例的小区和HARQ实体的映射架构中，TB1的初传和重传仅能在小区1中，TB2的初传和重传仅能在小区2中。一个已进行初传过的数据，为支持跨载波的数据重传，只能通过高层数据的重传才能改变 数据重传的小区，不能利用软信息合并的增益，流程时间较长，造成重传效率低下。
针对该示例中，如果小区2由于障碍物阻挡或终端设备的转动或移动等因素发生了阻塞(blockage)，此时终端设备要重新进行发送波束和/或接收波束的对齐，上述波束对齐的过程可称为波束恢复，关于波束恢复可参见上述术语解释十八部分的说明。在上述波束恢复过程中，在小区2上，网络设备和终端设备无法进行正常的数据收发，会导至数据发送设备的上层(比如TCP层)无法在一定的条件要求下接收到数据包的正确接收反馈，从而发送设备的TCP层的拥塞控制流程可能进入拥塞控制阶段，数据发送端主动降低输入到无线接入网侧的数据吞吐量，降低了整个无线接入网侧的数据吞吐量性能。关于TCP的拥塞控制可参见上述术语解释的第十七部分的说明。
针对上述过程，本申请提供以下解决方案，分别为第一种解决方案和第二种解决方案。其中，第一种解决方案可对应于上述图5所示的流程以及上述实施例二所对应的方案。
示例的，第一种解决方案：建立HARQ实体2与小区1的对应关系，网络设备侧通过小区1进行TB2的重传。相应的，终端设备侧通过小区1接收重传的TB2。
如图9所示，网络设备侧的MAC层可建立HARQ实体2与小区1的对应关系，且MAC层可将HARQ实体2与小区1的对应关系通知给PHY层。网络设备侧的PHY层可通过空口将HARQ实体2与小区1的对应关系，通知终端设备，具体的，比如：
比如，小区1中包括BWP1和BWP2，可预先建立不同BWP与HARQ实体的对应关系。比如，可建立BWP1与HARQ实体1的对应关系，BWP1用于传输HARQ实体1中的数据。可建立BWP2与HARQ实体2的对应关系，BWP2用于传输HARQ实体2中的数据。其中，BWP1与BWP2的配置可相同或不同，比如，BWP1与BWP2所配置的物理资源以及其它相关参数等可相同或不同。可以理解的是，当BWP1与BWP2，除了BWP ID外，其他配置相同时，可认为仅改变BWP所发送或接收的HARQ数据的来源，比如，BWP1的HARQ数据的来源为HARQ实体1，BWP2的HARQ数据的来源为HARQ实体2，或者，可以描述为：改变BWP与HARQ实体的映射关系。比如，BWP1所映射的HARQ实体为HARQ实体1，BWP2所映射的HARQ实体为HARQ实体2。或者，可以描述为：不改变BWP相关的射频参数以及基带参数等。此时激活的BWP由BWP1切换至BWP2的时间很短，不影响数据发送的效率。当BWP1与BWP2，除BWP ID外，其他配置不同时，可认为在改变BWP的HARQ数据来源的同时，还改变发送资源或发送参数的配置等，或者可以描述为：在改变BWP与HARQ实体的映射关系的同时，改变BWP的射频参数或基带参数等，此时激活的BWP由BWP1切换至BWP2需要一定的时间。其中BWP切换可以通过RRC信令、定时器、PDCCH指示、MAC实体等方式来控制。网络侧可以通过切换激活的BWP来改变小区和HARQ实体的对应关系。
示例的，在上述BWP与HARQ实体的对应关系中，所述BWP可用BWP ID表示，所述HARQ实体可用HARQ实体ID表示，或者，所述HARQ实体可用所述HARQ实体默认所对应的小区标识来表示。小区标识可以是小区配置的索引值或小区ID等。在以下示例中，以小区标识为小区索引值为例进行说明，比如，BWP1对应HARQ实体1，BWP2对应HARQ实体2。BWP1的ID为1，BWP2的ID为2，HARQ实体1的ID为1，HARQ实体2的ID为2，HARQ实体1默认所对应小区的索引为1，HRQ实体2默认所对应小区的索引为2。BWP1与HARQ实体1的对应关系可表示为：BWP ID1对应HARQ实体ID1，或者，BWP ID1对应小区索引1。BWP2与HARQ实体2的对应关系可表示为：BWP ID2对应HARQ实体ID2，或者，BWP ID2对应小区索引2。
关于所建立的BWP与HARQ实体的对应关系，可采用以方式进行表示：
第一种方式：在BWP的配置中增加一个信息元素(information element，IE)，所述IE用于表示所配置的BWP与HARQ实体的对应关系。示例的，所述IE可指示HARQ实体的ID，或者小区的索引。比如，沿用上述举例，BWP 1对应HARQ实体1，在BWP1的配置中可新增IE，所述IE中可指示HARQ实体ID1，或者，所述IE中可指示小区索引1。同理，BWP 2对应HARQ实体2，在BWP 2的配置中可新增IE，所述IE中可指示HARQ实体ID2，或者，所述IE中可存储小区索引2。
示例的，如图10所示，所述新增的IE可称为HARQ缓存寄存器映射(HARQ buffer mapping)。可选的以下行BWP配置为例，如图10所示，所述BWP的配置信息中还可包括BWP ID、公共下行BWP(BWP DL common)配置和专用下行BWP(BWP DL dedicated)配置。其中，公共下行BWP配置中可包括公共PDCCH配置(PDCCH-Config Comm)和公共PDSCH配置(PDSCH-Config Comm)。专用下行BWP配置中可包括PDCCH配置(PDCCH Config)、PDSCH配置(PDSCH-Config)、半持续调度配置(semi-persistent scheduling config，SPS config)、无线链路配置(radiolink config)和缓存寄存器映射(HARQ buffer mapping)等。
示例的，下行BWP配置的格式还可以表示为：
Figure PCTCN2020094750-appb-000006
其中，在上述下行BWP配置的格式中，新增IE的名称可为HARQ buffer mapping，可参见上述示例中加粗的字段。其中，HARQ buffer mapping中可包括HARQ实体的ID(HARQ Entity Id)。比如，若BWP 1对应HARQ实体1，则在上述HARQ buffer mapping中包括HARQ实体ID1，即上述HARQ Entity ID中包括HARQ实体ID1。
进一步的，所述HARQ Entiey Id可为大于或等于0，小于或等于N的正整数，所述N表示最大HARQ实体的个数；或者，可以描述为HARQEntityId::＝INTEGER(0..maxNrofHARQEntitys-1)，所述“maxNrofHARQEntitys”表示最大HARQ实体的个数。
示例的，下行BWP配置的格式还可以表示为：
Figure PCTCN2020094750-appb-000007
Figure PCTCN2020094750-appb-000008
其中，在上述下行BWP配置的格式下，新增IE的名称可为HARQ buffer mapping，可参见上述示例中加粗的字段。所述HARQ buffer mapping中可包括服务小区索引(servCell Index)。比如，若BWP1对应服务小区1，则在上述HARQ buffer mapping中包括小区索引1，即上述ServCell Index中包括小区索引1。所述servCell Index可为大于或等于0，小于或等于M的正整数，所述M表示最大小区的个数。或者，可以描述为ServCellIndex::＝INTEGER(0..maxNrofServingCells-1)，所述“maxNrofServingCells”表示最大小区的个数。
第二种方式：在小区级的配置时，新增BWP与HARQ实体的对应关系。比如，仍沿用上述举例，可在小区1的配置中新增BWP 1的标识，比如，BWP ID1。在小区2的配置中可新增BWP2的标识，比如，BWP ID2等。
示例的，如图17所示，在小区配置(Serving Cell Config)的格式中，新增的IE可称为下行BWPHARQ映射(DL BWP HARQ mapping)，和/或，上行BWPHARQ映射(UL BWP HARQ mapping)。可选的，如图17所示，在小区配置中，还可包括下行BWP配置(DL BWP config)和上行BWP配置(UL BWP config)。所述下行BWP配置中可包括下行BWP列表的释放和增加，上行BWP配置中可包括上行BWP列表的释放和增加等。
示例性，小区配置的格式可以表示为：
Figure PCTCN2020094750-appb-000009
Figure PCTCN2020094750-appb-000010
通过上述示例可以看出，在小区配置的格式中包括DL BWP HARQ mapping和UL BWP HARQ mapping，关于DL BWP HARQ mapping和UL BWP HARQ mapping可具体参见上述小区配置中的加粗部分。
进一步的，DL BWP HARQ Mapping，或者，UL BWP HARQ Mapping的IE格式可以表示为：
Figure PCTCN2020094750-appb-000011
通上述可以看出，在DL BWP HARQ Mapping，或者，UL BWP HARQ Mapping中可新增BWP ID与HARQ实体ID的对应关系，或者，新增BWP ID与服务小区索引的对应关系。关于BWP ID与HARQ实体ID的对应关系或BWP ID与服务小区索引的对应关系，可参见上述加粗部分的记载。
示例的，当小区1上的激活BWP是BWP1时，小区1发送HARQ实体1中的数据，也可以说小区1对应HARQ实体1；当小区1上的激活BWP切换到BWP2后，小区1发送HARQ实体2中的数据，也可以说小区1对应HARQ实体2。
可以理解的是，在本申请实施例中，当在一个小区中配置不同的BWP ID时，在进行数据传输时，这些BWP ID所对应的物理资源还在该小区上。例如，小区1上配置了BWP1与BWP2，具体可配置BWP1与HARQ实体2的对应关系，BWP2与HARQ实体1的对应关系。虽然BWP1用于传输小区2上的HARQ实体2内的数据，但BWP2所对应的物理资源还在小区1上。
在本申请实施例中，终端设备在接收到重传的TB2后，可根据BWP与HARQ实体的对应关系，确定当前BWP所对应的HARQ实体。然后根据上述确定的HARQ实体找到初传的TB2的译码软信息存放的缓冲区，将初传的TB2软信息与重传的TB2的软信息进行合并，译码，提高了数据的接收性能。
示例的，第二种解决方案：MAC层仅设置一个HARQ实体，该HARQ实体，对应于所有小区。比如，如图11所示，MAC层仅设置一个HARQ实体，该HARQ实体对应于小区1和小区2，即该HARQ实体与小区1和小区2均存在对应关系。当小区2发送了链路中断或波 束失配等情况下，可将TB2的重传转移到小区1中。
可以理解的是，在第二种解决方案中，需要注意以下问题：
1)对网络设备侧MAC层HARQ实体中HARQ进程的个数按照小区的个数进行扩展。比如，仍可参照图11所示，在一个HARQ实体对应于一个小区的情况下，一个HARQ实体中包括N-1个HARQ进程。在一个HARQ实体对应于两个小区的情况下，一个HARQ实体中包括2N-1个HARQ进程。
2)网络设备侧的MAC层将HARQ进程与小区的对应关系，通知PHY层。网络设备的PHY层将HARQ进程与小区的对应关系通知终端设备。比如，网络设备侧可通过RRC信令、MAC CE信令和DCI等方式，将HARQ进程与小区的对应关系通知终端设备。
在本申请实施例中，DCI中可包括HARQ进程域，HARQ进程域的比特数可以按照HARQ进程的个数进行扩展。比如，原来一个HARQ实体对应于一个小区时，一个HARQ实体中包括16个HARQ进程，那么HARQ进程域的比特数为4比特，4比特即可支持最大16个HARQ进程个数的信息指示。当一个HARQ实体对应于两个小区时，一个HARQ实体中包括32个HARQ进程，那么HARQ进程域的比特数需要4比特扩展为5比特，才可最大支持32个HARQ进程个数的信息指示。
在本申请实施例中，终端设备在接收到重传的TB2后，需要根据HARQ进程与小区的对应关系，确定传输TB2的HARQ进程，即图11所示的HARQ进程2N-1。然后，在HARQ进程2N-1所对应的缓存寄存器(buffer)中，查找到初传的TB2。终端设备对初传的TB2的软信息和重传的TB2的软信息进行软合并，译码，提高数据的接收性能。
示例的，在本申请实施例中，由于HARQ重传，可以利用初传和重传的软信息合并获得性能的增益，因此需要保证初传和重传的传输块大小(transport block size，TBS)相等。在本申请实施例中，当小区1与小区2的信道带宽与质量差异较大时，或者，可以描述为当TB2的初传与重传信道带宽和质量有较大差异时，如何保证初传和重传的TBS相同，是本申请实施例所要解决的一个问题。解决该问题的原理为：TB2重传的信道带宽小于TB2初传的信道带宽时，或者，可以描述为：当小区1的信道带宽小于小区2的信道带宽时，此时可将重传的TB2，拆分为多个CBG，关于CBG的介绍可参见上述术语解释第十五部分的说明。且在本申请实施例中，以一个调度时间单元传输一个TB为例进行说明，所述调度时间单元还可称为时间单元。
如图8所示，当TB2的初传在小区2中时，网络设备分配给终端设备的TB2的比特数可称为初传TB2的传输块大小(TB2_TBS_initial)。所述初传TB2的传输块大小是根据网络设备分配给终端设备的RB个数以及MCS指示所确定的。可选的，所述网络设备分配给终端设备的RB个数也可称为初始分配给小区2的RB个数(Cell 2_RBNum_initial)，MCS指示也可称为始分配给小区2的MCS索引(Cell 2_MCS_initial index)。所述网络设备分配给终端设备的RB个数是根据终端设备上报的小区2的CQI所确定的。
当TB2的重传在小区1中时，网络设备会根据终端设备小报的小区1的CQI信息，确定小区1重传的MCS。可选的，小区1重传的MCS也可称为Cell1_MCS_ReTx。由于小区1上重传的TB2的传输块大小需要等于初传TB2的传输块大小，因此TB2在小区1重传时所需要的RB个数可以通过小区1重传的MCS和初传TB2的传输块大小来确定。
示例的，在本申请实施例中，当TB2在小区1重传时所需要的RB个数小于或等于小区1可利用RB个数时，网络设备可按照正常的RB资源的分配，分配RB用于TB2的重传。可选 的，小区1可利用RB个数还可称为小区1_RBNum_available。
当TB2重传时所需要的RB个数大于小区1可利用RB个数时，网络设备可以将重传的TB2，拆分为多个CBG进行重传。如图12所示，重传的CBG可在同一个小区上传输。或者，如图13所示，重传的CBG可以在不同的小区上传输。
示例的，如图12所示，网络设备发送一个TB，该TB中包括14个CB，编号分别为1至14。其中，当配置的CBG个数为4个时，按照现有CBG划分的规则，CB1至CB4属于CBG#1，
CB5至CB8属于CBG#2，CB9至CB11属于CBG#3，CB12至CB14属于CBG#4。
在本申请实施例中，终端设备在接收到TB时，发送CBG1和CBG3传输错误，且不可纠正，发送NACK至网络设备侧，CBG#2和CBG#4传输正确，发送ACK至网络设备侧。网络设备接收到终端设备的反馈后，可针对CBG#1和CBG#3进行重传。其中，网络设备可发送DCI向终端设备，该DCI用于调度CBG#1的重传或CBG#3的重传。
比如，如图12或图13所示，该DCI中需要包括CBGTI域、开始指示域和结束指示域。如图12所示，针对CBG#1的重传，4比特的CBGTI域可具体为1000，1代表调度CBG#1进行重传，0代表未调度CBG#2、CBG#3和CBG#4进行重传。针对CBG#3的重传，CBGTI域可具体为0010，1代表示调度CBG#3进行重传，0代表未调度CBG#1、CBG#2和CBG#4进行重传。如图12所示，开始指示域可表示为“start”，结束指示域可表示为“end”。针对CBG1的重传，开始指示域为1，结束指示域为0。针对CBG3的重传，开始指示域为0，结束指示域为1。
图12所示的将CBG#1和CBG#3在同一个小区，即小区1中重传的过程，与图13所示的将CBG#1和CBG#3在不同小区,即小区1和小区3分别重传的过程相似。不同之处在于，在图12所示的示例中，可在不同的时间，在小区1中分别传输CBG#1和CBG#3，示例的，可在T1时间，在小区1传输CBG#1，在T2时间，在小区1传输CBG#3。在图13所示的示例中，可在小区1和小区3中同时传输CBG#1和CBG#3，相对于上述图12所示的方式，可提高传输效率。另外，可以理解的是，设定TB2是HARQ实体2中的数据，那么在上述第一种解决方案中，除了建立小区1与HARQ实体2的对应关系外，还需要建立小区3与HARQ实体2的对应关系，且将小区3与HARQ实体的对应关系，通过空口通知终端设备。
当第一小区恢复正常后，在第二小区上未正确传输的数据可转移到第一小区上重传。比如，设定第二数据和第三数据的初传在第二小区中，那么可将第二数据和第三数据的重传转移到第一小区上。比如，在本申请实施例中，网络设备可发送第四DCI，第四DCI用于调度第二数据和第三数据的重传。网络设备可在第一小区中，同时重传第二数据和第三数据。相应的，终端设备可在第一小区中，接收同时重传的第二数据和第三数据。
或者，在第二小区上未正确传输的数据可转移到第三小区上重传。比如，设定第二数据和第三数据的初传在第二小区中，那么可将第二数据和第三数据的重传转移到第三小区上。比如，在本申请实施例中，网络设备可发送第四DCI，第四DCI用于调度第二数据和第三数据的重传。网络设备可在第三小区中，同时重传第二数据和第三数据。相应的，终端设备可在第三小区中，接收同时传输的第二数据和第三数据。
提供一种应用场景，在该应用场景中，小区1可对于上述第二小区，小区2可对应于上述第一小区或第三小区，TB1_0可对应于上述第二数据，TB1_1可对应于上述第三数据。在本申请实施例中，当小区2异常恢复后，可将初传在小区1中的TB1_0和TB1_1转移到小区2中进生重传。
如图14所示，设定TB1_0和TB1_1的初传在小区1中，当小区2异常恢复后，所述网络设备可向终端设备发送DCI，该DCI用于调度TB1_0和TB1_1的重传，网络设备在第二小区中重传TB1_0和TB1_1。
示例的，所述DCI中可包括每个TB的频域动态资源分配、每个TB的时域动态资源分配、TB个数指示信息、每个TB的调制编码指示、每个TB的新数据指示、每个TB的冗余版本指示、每个TB包括的HARQ进程编号指示信息和TBS索引等。具体的：
每个TB的频域动态资源分配，表示每个TB发送所占用的频率资源。本实施例可以支持每个TB占用不同的频率资源。另外，考虑到DCI负载的节省，可以将多个TB通过一个联合的频率资源进行发送，只需要一个频域资源分配域。
每个TB的时域动态资源分配，表示每个TB发送所占用的时域资源。本实施例可以支持每个TB占用不同的时域资源。另外，考虑到DCI负载的节省，可以将多个TB通过一个联合的时域资源进行发送，只需要一个时域资源分配域。
TB个数指示信息，可指示一个时间单元内传输的TB数量、总TB个数，也可以是一个时间单元内额外增加的TB个数。在不考虑空间复用的情况下，在一个时间单元内，一个小区只能传输一个TB，在本申请实施例中，在一个时间单元内，一个小区可以传输N个TB，N>1。TB个数指示信息可以是N，或N-1。比如，在本申请实施例中，当TB个数指示总TB个数时，所述TB个数指示信息所指示的TB个数可为2，分别为TB1_0和TB1_1等。当TB个数指示额外增加的TB个数时，所述TB个数指示信息所指示的TB个数可为1，表示在原有1个TB的基础上再传输1个TB。
每TB的调制编码指示、每TB的新数据指示、每TB的冗余版本指示，本实施例可以支持指示每个TB的调制编码、新数据指示和冗余版本指示。当TB总个数为2时，有MCS1、NDI1、RV1和MCS2、NDI2、RV2。
TB包括的HARQ进程编号指示信息，可具体包括TB1_0所对应的HARQ进程0所对应的编号指示信息以及HARQ进程N-1所对应的编号指示信息等。
TBS索引，可指示一个TBS大小，比如TB1_0的大小，或者TB1_1的大小等。比如，在本申请实施例中，如表4所示，通过DCI指示TB1_0的TBS索引为1，表示TB1_0的TBS大小为24比特。终端设备通过现有技术中TBS的确定方法，根据DCI中的信息指示和系统参数可以确定多个TB的总TBS大小。终端设备通过总的TBS大小减去其中一个TB的TBS大小可以得到另一个TB的TBS大小。示例的，终端设备通过现有技术确定总TBS大小为80比特时，那么，终端设备可通过80-24＝56计算获得TB1_1大小为56比特。当TB的总个数为N且N>1时，需要指示N-1个TBS索引。
在本申请的一示例中，如表4所示，下行调度的DCI格式1_1为例，所述DCI指示中可包括以下内容：
表4
Figure PCTCN2020094750-appb-000012
Figure PCTCN2020094750-appb-000013
示例的，终端设备可通过以下方式，确定总的TBS大小：
1)终端设备可根据网络设备发送的频率资源分配和时域资源分配信息，获取n PRB参数和
Figure PCTCN2020094750-appb-000014
参数。根据n PRB参数和
Figure PCTCN2020094750-appb-000015
参数，确定一个调度时间单元内的RE个数。示例的，一个调度时间单元内的RE个数，可满足以下公式：
N RE＝min(156,N' RE)·n PRB；
Figure PCTCN2020094750-appb-000016
其中，N RE表示一个调度时间单元内的RE个数，
Figure PCTCN2020094750-appb-000017
表示在调度时间单元内，每个PRBR的DM-RS的RE数量，所述
Figure PCTCN2020094750-appb-000018
中包括没有数据的DM-RS CDM组的开销，所述
Figure PCTCN2020094750-appb-000019
是RRC配置的overhead参数，即
Figure PCTCN2020094750-appb-000020
2)根据以下公式，计算中间变量的信息比特个数。
N info＝N RE·R·Q m·υ
其中，N RE表示一个调度时间单元内的RE个数，R表示MCS index中指示的码率，Qm是MCS index中指示的调制阶数。
3)根据中间数量的信息比特个数N info，从下述表5所示的表格中找到一个接近且不小于中间变量的信息比特个数的TBS值，从而确定总的TBS。示例的，当中间变量的信息比特个数为100时，TBS为104。另外，还可以通过中间变量的信息比特个数和一定的计算规则计算得到总的TBS。示例的，先将通过
Figure PCTCN2020094750-appb-000021
获得量化的中间数量的信息比特N′ info，其中
Figure PCTCN2020094750-appb-000022
当编码率小于1/4时，
Figure PCTCN2020094750-appb-000023
其中
Figure PCTCN2020094750-appb-000024
当编码率大于等于1/4时，如果N′ info＞8424，则
Figure PCTCN2020094750-appb-000025
否则
Figure PCTCN2020094750-appb-000026
其中
Figure PCTCN2020094750-appb-000027
表5 TBS for N info≤3824
Index TBS Index TBS Index TBS Index TBS
1 24 31 336 61 1288 91 3624
2 32 32 352 62 1320 92 3752
3 40 33 368 63 1352 93 3824
4 48 34 384 64 1416    
5 56 35 408 65 1480    
6 64 36 432 66 1544    
7 72 37 456 67 1608    
8 80 38 480 68 1672    
9 88 39 504 69 1736    
10 96 40 528 70 1800    
11 104 41 552 71 1864    
12 112 42 576 72 1928    
13 120 43 608 73 2024    
14 128 44 640 74 2088    
15 136 45 672 75 2152    
16 144 46 704 76 2216    
17 152 47 736 77 2280    
18 160 48 768 78 2408    
19 168 49 808 79 2472    
20 176 50 848 80 2536    
21 184 51 888 81 2600    
22 192 52 928 82 2664    
23 208 53 984 83 2728    
24 224 54 1032 84 2792    
25 240 55 1064 85 2856    
26 256 56 1128 86 2976    
27 272 57 1160 87 3104    
28 288 58 1192 88 3240    
29 304 59 1224 89 3368    
30 320 60 1256 90 3496    
方式一：终端设备通过空口通知网络设备波束失配或链路中断，网络设备启动ARQ重传。关于终端设备具体通过空口通知的方式，可参见上述实施例二中的记载。关于ARQ重传可具体参见上述术语解释六部分介绍，关于波束失败检测和波束失败恢复，可具体参见上述术语解释十八部分介绍。
如图15所示，以终端设备检测小区2为例进行说明。1)终端设备的物理层PHY进行波 束失败指示上报(beam failure indication)至终端设备MAC层。2)终端设备的MAC层在接收到所述波束失败指示上报，进行波束检测。且如果检测到波束失败后，通过空口通知网络设备的MAC层。3)网络设备的MAC层，通知RLC层。4)网络设备的RLC层启动ARQ的重传，通过小区1，可以是PCell或PSCell发送重传的RLC SDU或RLC SDU分段至终端设备侧。
方式二：终端设备通过RLC层的状态报告，通知网络设备波束失败或链路失败，网络设备启动ARQ重传。
如图16所示，以终端设备检测小区2为例进行说明。1)终端设备的物理层PHY进行波束失败指示上报(beam failure indication)至终端设备MAC层。2)终端设备的MAC层在接收到所述波束失败指示上报，进行波束检测。终端侧的MAC层将波束失败信息传递至RLC层。3)终端设备的RLC层接收到波束失败信息后发送RLC状态报告(status reporting)至网络设备。其中RLC状态报告中包含了终端侧未正确接收的RLC SDU或RLC SDU分段的信息。4)网络设备的RLC层接收到终端发送的RLC状态报告后启动ARQ重传，通过小区1，可以是PCell或PSCell发送未正确接收的RLC SDU或RLC SDU分段至终端设备侧。
在本申请实施例中，不用改变HARQ的传输框架，而且不要求初传和重传数据具有相同的TBS，实现起来更简单。
与上述构思相同，如图18所示，本申请实施例还提供一种装置1800，包括处理模块1801和收发模块1802。
一示例中，装置1800可以用于实现上述方法中终端设备的功能，该装置可以是终端设备，也可以是终端设备中的装置。其中，该装置可以为芯片系统，所述芯片系统可以由芯片构成，也可以包括芯片和其他分立器件。
其中，处理模块1801，用于根据第一小区与第一混合自动重传请求HARQ实体的对应关系，在所述第一小区中接收初传的第一数据；收发模块1802，用于接收第一指示信息，所述第一指示信息用于指示第二小区与所述第一HARQ实体的对应关系；处理模块1801，还用于根据第二小区与所述第一HARQ实体的对应关系，在所述第二小区中接收重传的第一数据。关于处理模块1801和收发模块1802的说明，可参见上述方法实施例中涉及终端设备侧的记载，在此不再说明。
另一示例中，装置1800可以用于实现上述方法中网络设备的功能，该装置可以是网络设备，也可是网络设备中的装置。其中，该装置可以为芯片系统，所述芯片系统可以由芯片构成，也可以包括芯片和其他分立器件。
其中，处理模块1801，用于根据第一小区与第一混合自动重传请求HARQ实体的对应关系，在所述第一小区中初传第一数据；收发模块1802，用于发送第一指示信息，所述第一指示信息用于指示第二小区与所述第一HARQ实体的对应关系；处理模块1801，还用于根据所述第二小区与所述第一HARQ实体的对应关系，在所述第二小区中重传所述第一数据。关于处理模块1801和收发模块1802的说明，可参见上述方法实施例中涉及网络设备侧的记载，在此不再说明。
可以理解的是，关于上述收发模块1802和处理模块1801的具体实现方式，可参见上述方法实施例中的记载。本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，另外，在本申请各个实施例中的各功能模块可 以集成在一个处理器中，也可以是单独物理存在，也可以两个或两个以上模块集成在一个模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。
与上述构思相同，如图19所示，本申请实施例还提供一种装置1900。
一示例中，该装置1900用于实现上述方法中终端设备的功能，该装置可以是终端设备，也可以是终端设备中的装置。装置1900包括至少一个处理器1901，用于实现上述方法中终端设备的功能。示例地，处理器1901，可根据第一小区与第一HARQ实体的对应关系，在第一小区中接收初传的第一数据。关于如何根据第一小区与第一HARQ实体的对应关系，在第一小区中接收初传的第一数据，可参见上述方法实施例中的记载，在此不再说明。装置1900还可以包括至少一个存储器1902，用于存储程序指令和/或数据。存储器1902和处理器1901耦合。本申请实施例中的耦合是装置、单元或模块之间的间隔耦合或通信连接，可以是电性，机械或其它的形式，用于装置、单元或模块之间的信息交互。处理器1901和存储器1902协同操作。处理器1901可执行存储器1902中存储的程序指令。所述至少一个存储器的至少一个可以包括于处理器1901中。装置1901还可以包括通信接口1903，利用通信传输介质和其它设备进行通信，从而用于装置1900中的装置可以和其它设备进行通信。示例的，通信接口1903可以是收发器、电路、总线、模块或其它类型的通信接口，该其它设备可以是网络设备。处理器1901利用通信接口1903收发数据，并用于实现上述实施例中的方法。示例的，通信接口1903可以接收第一指示信息等。
一示例中，装置1900用于实现上述方法中网络设备的功能，该装置可以是网络设备，也可以是网络设备中的装置。装置1900至少包括一个处理器1901，用于实现上述方法中网络设备的功能。示例的，处理器1901，可根据第一小区与第一HARQ实体的对应关系，在所述第一小区中初传第一数据。关于如何根据第一小区与第一HARQ实体的对应关系，在第一小区中初传第一数据，可参见上述方法实施例中的记载，在此不再说明。装置1900还可包括至少一个存储器1902，用于存储程序指令和/或数据。存储器1902和处理器1901耦合。本申请实施例中的耦合是装置、单元或模块之间的间隔耦合或通信连接，可以是电性，机械或其它的形式，用于装置、单元或模块之间的信息交互。处理器1901和存储器1902协同操作。处理器1901可执行存储器1902中存储的程序指令。所述至少一个存储器中的至少一个可以包括于处理器1901中。装置1900还可以包括通信接口1903，用于利用通信传输介质和其它设备进行通信，从而用于装置1900中的装置可以和其它设备进行通信。示例的，通信接口1903可以是收发器、电路、总线、模块或其它类型的通信接口，该其它设备可以是终端设备。处理器1901利用通信接口1903收发数据，并用于实现上述实施例中的方法。示例性的，通信接口1903可以发送第一指示信息等。
本申请实施例中不限定上述通信接口1903、处理器1901以及存储器1902之间的连接介质。本申请实施例在图19中以存储器1902、处理器1901以及通信接口1903之间通过总线1904连接，总线在图19中以粗线表示，其它部件之间的连接方式，仅是进行示意性说明，并不引以为限。所述总线可以分为地址总线、数据总线、控制总线等。为了便于表示，图19中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
在本申请实施例中，处理器可以是通用处理器、数字信号处理器、专用集成电路、现场可编程门阵列或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件， 可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。
在本申请实施例中，存储器可以是非易失性存储器，比如硬盘(hard disk drive，HDD)或固态硬盘(solid-state drive，SSD)等，还可以是易失性存储器(volatile memory)，例如随机存取存储器(random-access memory，RAM)。存储器是能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。本申请实施例中的存储器还可以是电路或者其它任意能够实现存储功能的装置，用于存储程序指令和/或数据。
本申请实施例提供的方法中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本发明实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、网络设备、用户设备或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，简称DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机可以存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，数字视频光盘(digital video disc，简称DVD))、或者半导体介质(例如,SSD)等。
显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。
本申请实施例中，“至少一个”是指一个或者多个，“多个”是指两个或两个以上。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B的情况，其中A,B可以是单数或者复数。字符“/”一般表示前后关联对象是一种“或”的关系。
需要说明的是，在本申请实施例中，不同实施例之间可以单独使用，也可相互结合使用，本申请实施例并不作限定。且在无逻辑矛盾的前提下，各实施例之间可以相互引用，例如方法实施例之间的方法和/或术语可以相互引用，例如装置实施例之间的功能和/或术语可以相互引用，例如装置实施例和方法实施例之间的功能和/或术语可以相互引用。

Claims (45)

  1. 一种通信方法，其特征在于，包括：
    根据第一小区与第一混合自动重传请求HARQ实体的对应关系，在所述第一小区中接收初传的第一数据；
    接收第一指示信息，所述第一指示信息用于指示第二小区与所述第一HARQ实体的对应关系；
    根据所述第二小区与所述第一HARQ实体的对应关系，在所述第二小区中接收重传的所述第一数据。
  2. 如权利要求1所述的方法，其特征在于，所述第二小区中包括第一带宽部分BWP，所述第二小区与所述第一HARQ实体的对应关系，包括：所述第一BWP与所述第一HARQ实体的对应关系。
  3. 如权利要求2所述的方法，其特征在于，所述第一指示信息为所述第一BWP的标识，所述方法还包括：
    根据所述第一BWP的标识，确定所述第一BWP与所述第一HARQ实体的对应关系。
  4. 如权利要求1至3任一项所述的方法，其特征在于，所述方法还包括：
    发送第二指示信息，所述第二指示信息用于指示所述第一小区的链路中断，或所述第一小区的波束失配。
  5. 如权利要求1至4任一项所述的方法，其特征在于，所述第一数据中包括第一数据块，所述方法还包括：
    接收第一下行控制信息DCI，所述第一DCI用于调度所述第一数据块的重传；
    所述根据所述第二小区与所述第一HARQ实体的对应关系，在所述第二小区中接收重传的第一数据，包括：
    根据所述第二小区与所述第一HARQ实体的对应关系，在所述第二小区中接收重传的所述第一数据块。
  6. 如权利要求5所述的方法，其特征在于，所述第一数据中包括第二数据块，所述方法还包括：
    接收第二DCI，所述第二DCI用于调度所述第二数据块的重传；
    所述根据所述第二小区与所述第一HARQ实体的对应关系，接收重传的所述第一数据，包括：
    根据所述第二小区与所述第一HARQ实体的对应关系，在所述第二小区中接收重传的所述第二数据块。
  7. 如权利要求5所述的方法，其特征在于，所述方法还包括：
    根据第三小区与所述第一HARQ实体的对应关系，在所述第三小区中接收重传的所述第一数据。
  8. 如权利要求7所述的方法，其特征在于，所述第一数据中包括第二数据块，所述方法还包括：
    接收第三DCI，所述第三DCI用于调度所述第二数据块的重传；
    所述根据第三小区与所述第一HARQ实体的对应关系，在所述第三小区中接收重传的所述第一数据，包括：
    根据所述第三小区与所述第一HARQ实体的对应关系，在所述第三小区中接收重传的所述第二数据块。
  9. 如权利要求5、6、8任一项所述的方法，其特征在于，所述第一DCI还用于指示所述第一数据块的索引、开始标识或结束标识中的至少一个，所述第二DCI或所述第三DCI还用于指示所述第二数据块的索引、开始标识或结束标识中的至少一个；
    其中，所述开始标识表示在重传的第一数据中，第一个重传的数据块，所述结束标识表示在重传的第一数据中，最后一个重传的数据块。
  10. 如权利要求1至9任一项所述的方法，其特征在于，所述方法还包括：
    发送第四DCI，所述第四DCI用于调度第二数据和第三数据的重传，所述第二数据和所述第三数据的初传在所述第二小区中；
    在所述第一小区中重传所述第二数据和第三数据；或者，在第四小区中重传所述第二数据和第三数据。
  11. 一种通信方法，其特征在于，包括：
    根据第一小区与第一混合自动重传请求HARQ实体的对应关系，在所述第一小区中初传第一数据；
    发送第一指示信息，所述第一指示信息用于指示第二小区与所述第一HARQ实体的对应关系；
    根据所述第二小区与所述第一HARQ实体的对应关系，在所述第二小区中重传所述第一数据。
  12. 如权利要求11所述的方法，其特征在于，所述第二小区包括第一带宽部分BWP，所述第二小区与所述第一HARQ实体的对应关系包括所述第一BWP与所述第一HARQ实体的对应关系。
  13. 如权利要求12所述的方法，其特征在于，所述第一指示信息为所述第一BWP的标识。
  14. 如权利要求11至13任一项所述的方法，其特征在于，所述方法还包括：
    接收第二指示信息，所述第二指示信息用于指示所述第一小区的链路中断，或所述第一小区的波束失配。
  15. 如权利要求11至14任一项所述的方法，其特征在于，所述第一数据中包括第一数据块，所述方法还包括：
    发送第一下行控制信息DCI，所述第一DCI用于调度所述第一数据块的重传；
    所述根据所述第二小区与所述第一HARQ实体的对应关系，在所述第二小区中重传所述第一数据，包括：
    根据所述第二小区与所述第一HARQ实体的对应关系，在所述第二小区中重传所述第一数据块。
  16. 如权利要求15所述的方法，其特征在于，所述第一数据中包括第二数据块，所述方法还包括：
    发送第二DCI，所述第二DCI用于调度所述第二数据块的重传；
    所述根据所述第二小区与所述第一HARQ实体的对应关系，在所述第二小区中重传所述第一数据，包括：
    根据所述第二小区与所述第一HARQ实体的对应关系，在所述第二小区中重传所述第 二数据块。
  17. 如权利要求15所述的方法，其特征在于，所述方法还包括：
    根据第三小区与所述第一HARQ实体的对应关系，在所述第三小区中重传所述第一数据。
  18. 如权利要求17所述的方法，其特征在于，所述第一数据中包括第二数据块，所述方法还包括：
    发送第三DCI，所述第三DCI用于调度所述第二数据块的重传；
    所述根据第三小区与所述第一HARQ实体的对应关系，在所述第三小区中重传所述第一数据，包括：
    根据所述第三小区与所述第一HARQ实体的对应关系，在所述第三小区中重传所述第二数据块。
  19. 如权利要求15、16、18任一项所述的方法，其特征在于，所述第一DCI还用于指示所述第一数据块的索引、开始标识或结束标识中的至少一个，所述第二DCI或所述第三DCI还用于指示所述第二数据块的索引、开始标识或结束标识中的至少一个；
    其中，所述开始标识表示在重传的第一数据中，第一个重传的数据块，所述结束标识表示在重传的第一数据中，最后一个重传的数据块。
  20. 如权利要求11至19任一项所述的方法，其特征在于，所述方法还包括：
    发送第四DCI，所述第四DCI用于调度第二数据和第三数据的重传，所述第二数据和所述第三数据的初传在所述第二小区中；
    在所述第一小区中重传所述第二数据和第三数据；或者，在第四小区中重传所述第二数据和第三数据。
  21. 一种通信装置，其特征在于，包括：
    处理器，用于根据第一小区与第一混合自动重传请求HARQ实体的对应关系，在所述第一小区中接收初传的第一数据，以及，根据所述第二小区与所述第一HARQ实体的对应关系，在所述第二小区中接收重传的所述第一数据；
    通信接口，用于接收第一指示信息，所述第一指示信息用于指示第二小区与所述第一HARQ实体的对应关系。
  22. 如权利要求21所述的装置，其特征在于，所述第二小区中包括第一带宽部分BWP，所述第二小区与所述第一HARQ实体的对应关系，包括：所述第一BWP与所述第一HARQ实体的对应关系。
  23. 如权利要求22所述的装置，其特征在于，所述第一指示信息为所述第一BWP的标识，所述处理器还用于：
    根据所述第一BWP的标识，确定所述第一BWP与所述第一HARQ实体的对应关系。
  24. 如权利要求21至23任一项所述的装置，其特征在于，所述通信接口，还用于：
    发送第二指示信息，所述第二指示信息用于指示所述第一小区的链路中断，或所述第一小区的波束失配。
  25. 如权利要求21至24任一项所述的装置，其特征在于，所述第一数据中包括第一数据块，所述通信接口，还用于：接收第一下行控制信息DCI，所述第一DCI用于调度所述第一数据块的重传；
    所述处理器在根据所述第二小区与所述第一HARQ实体的对应关系，在所述第二小区 中接收重传的第一数据时，包括：
    根据所述第二小区与所述第一HARQ实体的对应关系，在所述第二小区中接收重传的所述第一数据块。
  26. 如权利要求25所述的装置，其特征在于，所述第一数据中包括第二数据块，所述通信接口，还用于：接收第二DCI，所述第二DCI用于调度所述第二数据块的重传；
    所述处理器在根据所述第二小区与所述第一HARQ实体的对应关系，接收重传的所述第一数据时，包括：
    根据所述第二小区与所述第一HARQ实体的对应关系，在所述第二小区中接收重传的所述第二数据块。
  27. 如权利要求25所述的装置，其特征在于，所述处理器，还用于：
    根据第三小区与所述第一HARQ实体的对应关系，在所述第三小区中接收重传的所述第一数据。
  28. 如权利要求27所述的装置，其特征在于，所述第一数据中包括第二数据块，所述通信接口，还用于接收第三DCI，所述第三DCI用于调度所述第二数据块的重传；
    所述处理器在根据第三小区与所述第一HARQ实体的对应关系，在所述第三小区中接收重传的所述第一数据时，包括：
    根据所述第三小区与所述第一HARQ实体的对应关系，在所述第三小区中接收重传的所述第二数据块。
  29. 如权利要求25、26、28任一项所述的装置，其特征在于，所述第一DCI还用于指示所述第一数据块的索引、开始标识或结束标识中的至少一个，所述第二DCI或所述第三DCI还用于指示所述第二数据块的索引、开始标识或结束标识中的至少一个；
    其中，所述开始标识表示在重传的第一数据中，第一个重传的数据块，所述结束标识表示在重传的第一数据中，最后一个重传的数据块。
  30. 如权利要求21至29任一项所述的装置，其特征在于，所述通信接口，还用于：发送第四DCI，所述第四DCI用于调度第二数据和第三数据的重传，所述第二数据和所述第三数据的初传在所述第二小区中；
    所述处理器，还用于：在所述第一小区中重传所述第二数据和第三数据；或者，在第四小区中重传所述第二数据和第三数据。
  31. 一种通信装置，其特征在于，包括：
    处理器，用于根据第一小区与第一混合自动重传请求HARQ实体的对应关系，在所述第一小区中初传第一数据，以及，根据所述第二小区与所述第一HARQ实体的对应关系，在所述第二小区中重传所述第一数据；
    通信接口，用于发送第一指示信息，所述第一指示信息用于指示第二小区与所述第一HARQ实体的对应关系。
  32. 如权利要求31所述的装置，其特征在于，所述第二小区包括第一带宽部分BWP，所述第二小区与所述第一HARQ实体的对应关系包括所述第一BWP与所述第一HARQ实体的对应关系。
  33. 如权利要求32所述的装置，其特征在于，所述第一指示信息为所述第一BWP的标识。
  34. 如权利要求31至33任一项所述的装置，其特征在于，所述通信接口，还用于： 接收第二指示信息，所述第二指示信息用于指示所述第一小区的链路中断，或所述第一小区的波束失配。
  35. 如权利要求31至34任一项所述的装置，其特征在于，所述第一数据中包括第一数据块，所述通信接口，还用于发送第一控制信息DCI，所述第一DCI用于调度所述第一数据块的重传；所述处理器在根据所述第二小区与所述第一HARQ实体的对应关系，在所述第二小区中重传所述第一数据时，包括：
    根据所述第二小区与所述第一HARQ实体的对应关系，在所述第二小区中重传所述第一数据块。
  36. 如权利要求35所述的装置，其特征在于，所述第一数据中包括第二数据块，所述通信接口，还用于发送第二DCI，所述第二DCI用于调度所述第二数据块的重传；所述处理器在根据所述第二小区与所述第一HARQ实体的对应关系，重传所述第一数据时，包括：
    根据所述第二小区与所述第一HARQ实体的对应关系，在所述第二小区中重传所述第二数据块。
  37. 如权利要求35所述的装置，其特征在于，所述处理器还用于：
    根据第三小区与所述第一HARQ实体的对应关系，在所述第三小区中重传所述第一数据。
  38. 如权利要求37所述的装置，其特征在于，所述第一数据中包括第二数据块，所述通信接口，还用于发送第三DCI，所述第三DCI用于调度所述第二数据块的重传；
    所述处理器在根据第三小区与所述第一HARQ实体的对应关系，在所述第三小区中重传所述第一数据时，包括：根据所述第三小区与所述第一HARQ实体的对应关系，在所述第三小区中重传所述第二数据块。
  39. 如权利要求35、36、38任一项所述的装置，其特征在于，所述第一DCI还用于指示所述第一数据块的索引、开始标识或结束标识中的至少一个，所述第二DCI或所述第三DCI还用于指示所述第二数据块的索引、开始标识或结束标识中的至少一个；
    其中，所述开始标识表示在重传的第一数据中，第一个重传的数据块，所述结束标识表示在重传的第一数据中，最后一个重传的数据块。
  40. 如权利要求31至39任一项所述的装置，其特征在于，所述通信接口，还用于发送第四DCI，所述第四DCI用于调度第二数据和第三数据的重传，所述第二数据和所述第三数据的初传在所述第二小区中；
    所述处理器，还用于在所述第一小区中重传所述第二数据和第三数据，或者，在第四小区中重传所述第二数据和第三数据。
  41. 一种装置，其特征在于，用于执行权利要求1至20任一项所述的方法。
  42. 一种装置，其特征在于，所述装置包括处理器、存储器以及存储在所述存储器上并可在所述处理器上运行的指令，当所述指令被运行时，使得所述装置执行如权利要求1至20任一项所述的方法。
  43. 一种装置，其特征在于，包括如权利要求21至40任一项所述的装置。
  44. 一种计算机程序产品，其特征在于，当其在计算机上运行时，使得所述计算机执行如权利要求1至20任一项所述的方法。
  45. 一种计算机可读存储介质，其特征在于，包括指令，当其在计算机上运行时，使 得计算机执行权利要求1至20任一项所述的方法。
PCT/CN2020/094750 2019-06-06 2020-06-05 一种通信方法及装置 Ceased WO2020244645A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP20818653.6A EP3982578A4 (en) 2019-06-06 2020-06-05 COMMUNICATION METHOD AND APPARATUS
US17/532,798 US12041598B2 (en) 2019-06-06 2021-11-22 Communication method and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910491679.1 2019-06-06
CN201910491679.1A CN112054880B (zh) 2019-06-06 2019-06-06 一种通信方法及装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/532,798 Continuation US12041598B2 (en) 2019-06-06 2021-11-22 Communication method and apparatus

Publications (1)

Publication Number Publication Date
WO2020244645A1 true WO2020244645A1 (zh) 2020-12-10

Family

ID=73608697

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/094750 Ceased WO2020244645A1 (zh) 2019-06-06 2020-06-05 一种通信方法及装置

Country Status (4)

Country Link
US (1) US12041598B2 (zh)
EP (1) EP3982578A4 (zh)
CN (1) CN112054880B (zh)
WO (1) WO2020244645A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022207772A1 (en) * 2021-03-31 2022-10-06 Sony Group Corporation Bandwidth parts for retransmissions

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111294141B (zh) * 2018-12-10 2021-09-07 华为技术有限公司 无线通信方法及装置
US20220124713A1 (en) * 2020-10-21 2022-04-21 Qualcomm Incorporated Resource allocation and hybrid automatic repeat request (harq) acknowledgement (ack) feedback for multi-cell scheduling
WO2023000141A1 (zh) * 2021-07-19 2023-01-26 Oppo广东移动通信有限公司 一种跨载波重传的方法及装置、终端设备、网络设备
CN117769817A (zh) 2021-08-06 2024-03-26 中兴通讯股份有限公司 传输调度技术
US20230073219A1 (en) * 2021-08-18 2023-03-09 Alireza Babaei Enhanced Cross-carrier Processes
KR20230109998A (ko) * 2022-01-14 2023-07-21 삼성전자주식회사 통신 시스템에서 제어 정보 및 데이터를 송수신하기 위한 장치 및 방법
CN116961858A (zh) * 2022-04-27 2023-10-27 北京三星通信技术研究有限公司 通信方法、用户设备及存储介质
WO2025010743A1 (zh) * 2023-07-13 2025-01-16 北京小米移动软件有限公司 通信处理方法及装置
CN116760512B (zh) * 2023-08-17 2023-11-17 上海朗力半导体有限公司 用于Multi-Link的HARQ重传控制方法及装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105634687A (zh) * 2014-11-04 2016-06-01 夏普株式会社 非授权频谱通信的重传方法以及基站和用户设备
WO2016116030A1 (zh) * 2015-01-21 2016-07-28 夏普株式会社 混合自动重传请求实体管理的方法和用户设备
CN109391379A (zh) * 2017-08-11 2019-02-26 维沃移动通信有限公司 一种harq指示方法、装置及系统

Family Cites Families (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101350708B (zh) * 2007-07-18 2011-01-26 大唐移动通信设备有限公司 多载波高速上行分组接入系统中混合自动重传方法与装置
KR101648775B1 (ko) * 2008-10-30 2016-08-17 엘지전자 주식회사 무선 통신 시스템에서 ｈａｒｑ 확인 응답 전송 및 전송 블록 재전송 방법
US8402334B2 (en) * 2008-12-17 2013-03-19 Research In Motion Limited System and method for hybrid automatic repeat request (HARQ) functionality in a relay node
CN102098152A (zh) * 2010-12-30 2011-06-15 电子科技大学 载波聚合下harq的跨载波重传方法
CN113938947A (zh) * 2016-01-20 2022-01-14 华为技术有限公司 一种数据发送方法、数据接收方法和装置
CN105589506B (zh) 2016-02-29 2017-10-17 华为技术有限公司 功率跟踪方法、装置及光伏发电系统
US20180176937A1 (en) * 2016-12-16 2018-06-21 Asustek Computer Inc. Method and apparatus of handling multiple uplink resource collisions in a wireless communication system
CN108512632B (zh) * 2017-02-28 2021-06-01 华为技术有限公司 数据处理方法及装置
US10716094B2 (en) * 2017-03-23 2020-07-14 Ofinno, Llc Packet duplication in a wireless device and wireless network
CN108633070A (zh) * 2017-03-24 2018-10-09 北京三星通信技术研究有限公司 半静态资源调度方法、功率控制方法及相应用户设备
US11139941B2 (en) * 2017-09-11 2021-10-05 Qualcomm Incorporated Uplink acknowledgment mapping and resource allocation
CN109586866B (zh) * 2017-09-28 2024-06-28 华为技术有限公司 通信方法、装置和设备
WO2019066587A1 (en) * 2017-09-28 2019-04-04 Intel IP Corporation COMMUNICATION NETWORK APPARATUS FOR UPLINK PLANNING
US11277862B2 (en) * 2017-10-26 2022-03-15 Comcast Cable Communications, Llc Activation and deactivation of configured grant
US10879985B2 (en) * 2017-11-16 2020-12-29 Ofinno, Llc Channel state information report on bandwidth part
EP3711427A1 (en) * 2017-11-18 2020-09-23 Lenovo (Singapore) Pte. Ltd. Random access configuration

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105634687A (zh) * 2014-11-04 2016-06-01 夏普株式会社 非授权频谱通信的重传方法以及基站和用户设备
WO2016116030A1 (zh) * 2015-01-21 2016-07-28 夏普株式会社 混合自动重传请求实体管理的方法和用户设备
CN109391379A (zh) * 2017-08-11 2019-02-26 维沃移动通信有限公司 一种harq指示方法、装置及系统

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
CMCC: "NR MAC for URLLC", 3GPP TSG-RAN WG2 MEETING #97 R2-1701920, 17 February 2017 (2017-02-17), XP051212458, DOI: 20200824165201X *
ERICSSON: "MAC Impact with Multiple Active BWPs", 3GPP TSG-RAN WG2 #104 R2-1817970, 16 November 2018 (2018-11-16), XP05155747, DOI: 20200824165357A *
PANASONIC: "Remaining Issues on Bandwidth Part Operation", 3GPP TSG-RAN WG1 MEETING 91 R1-1720505, 1 December 2017 (2017-12-01), XP051369012, DOI: 20200824165306A *
See also references of EP3982578A4 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022207772A1 (en) * 2021-03-31 2022-10-06 Sony Group Corporation Bandwidth parts for retransmissions

Also Published As

Publication number Publication date
US12041598B2 (en) 2024-07-16
EP3982578A4 (en) 2023-05-24
US20220086853A1 (en) 2022-03-17
EP3982578A1 (en) 2022-04-13
CN112054880A (zh) 2020-12-08
CN112054880B (zh) 2022-09-09

Similar Documents

Publication Publication Date Title
US12041598B2 (en) Communication method and apparatus
US11838130B2 (en) Method for partial retransmission
KR102356204B1 (ko) 통신 방법 및 통신 장치
EP3764575B1 (en) Method, device, and storage medium for transmitting data
TWI530144B (zh) 處理通訊運作的方法及其通訊裝置
TWI466557B (zh) 處理用於載波集成之軟性緩衝器的方法及其通訊裝置
JP6257759B2 (ja) マルチキャリア環境内における無線リンク性能を向上させるためのシステム及び方法
US10673699B2 (en) Methods and apparatus in a wireless communications network
US20230199766A1 (en) Hybrid automatic repeat request harq codebook generation method and apparatus
EP3416325B1 (en) Device and method of handling code block group-based communication operation
WO2021088991A1 (zh) 一种混合自动重传请求的处理方法及通信装置
US12580691B2 (en) NTN-based data transmission method and apparatus and storage medium
JP2023537184A (ja) ラプターコードのための情報表示
EP4097886A1 (en) Acknowledgment reporting for multi-link transmissions
WO2022237424A1 (zh) 通信方法及装置
CN115968538A (zh) 信息处理设备和信息处理方法
WO2021068693A1 (zh) 通信方法及装置
JP6571213B6 (ja) データ記憶方法、端末装置及び基地局
WO2022151964A1 (zh) 一种数据传输方法及装置
CN116033574A (zh) 通信方法及装置
US20250337534A1 (en) Methods, architectures, apparatuses and systems for downlink hybrid automatic repeat request (harq) operations with network coding
WO2026002105A1 (zh) 通信方法和通信装置
WO2026064917A1 (zh) 信息反馈方法、装置、设备、介质和程序产品
WO2025036226A1 (zh) Harq-ack信息反馈方法、接收方法及装置
KR20120122903A (ko) 캐리어 집적을 위한 소프트 버퍼 처리 방법 및 관련 통신 디바이스

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: 20818653

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2020818653

Country of ref document: EP