CN110365459B

CN110365459B - Uplink HARQ transmission method and communication device

Info

Publication number: CN110365459B
Application number: CN201910436238.1A
Authority: CN
Inventors: 张芳; 高全中; 胥恒
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2019-05-23
Filing date: 2019-05-23
Publication date: 2021-05-18
Anticipated expiration: 2039-05-23
Also published as: CN110365459A; WO2020233717A1

Abstract

The embodiment of the application discloses an uplink HARQ transmission method and a communication device, which relate to the field of communication and can shorten the waiting time of uplink transmission of a terminal and improve the network performance. The method comprises the following steps: on a first uplink carrier, sending a first transport block to access network equipment through a first HARQ process; on a second uplink carrier, sending a second transport block to the access network equipment through the first HARQ process; and the second transmission block and the first transmission block are transmitted in a Time Division Multiplexing (TDM) mode.

Description

Uplink HARQ transmission method and communication device

Technical Field

The embodiment of the present application relates to the field of communications, and in particular, to an uplink HARQ transmission method and a communication apparatus.

Background

Existing fourth generation (4)^thgeneration, 4G) communication system and (5)^thgeneration, 5G) communication system, Carrier Aggregation (CA) is supported, that is, by aggregating a plurality of continuous or discontinuous carriers (CCs) into a larger bandwidth, a network device and a terminal can simultaneously receive and transmit data on the plurality of carriers to obtain a higher traffic rate.

In a carrier aggregation scenario, only a hybrid automatic repeat request (HARQ) process corresponding to a carrier can be used for transmission on the certain carrier. For example, in a scenario of aggregating a 3.5GHz carrier and a 2.1GHz carrier, data initially transmitted on the 3.5GHz carrier through HARQ process 1 can only be retransmitted on the 3.5GHz carrier through HARQ process 1. Similarly, data originally transmitted on the 2.1GHz carrier by HARQ process 2 can only be retransmitted on the 2.1GHz carrier by HARQ process 2.

When a terminal performs new transmission or retransmission through an HARQ process corresponding to a certain carrier, if there is no uplink transmission opportunity for a long time on the carrier, the terminal needs to wait for a long time before performing new transmission or retransmission through the HARQ process, which causes an excessive time delay of an uplink service of the terminal and affects network performance.

Disclosure of Invention

The embodiment of the application provides an uplink HARQ transmission method and a communication device, which can shorten the waiting time of uplink transmission of a terminal and improve the network performance.

In order to achieve the above purpose, the embodiment of the present application adopts the following technical solutions:

in a first aspect, an uplink HARQ transmission method is disclosed, which may be performed by a terminal or a chip in the terminal. The method comprises the following steps: on a first uplink carrier, sending a first transport block to access network equipment through a first HARQ process; on a second uplink carrier, a second transmission block is sent to the access network equipment through the first HARQ process; the second transport block and the first transport block are transmitted in a Time Division Multiplexing (TDM) manner.

In the method provided by the embodiment of the application, the terminal can use the same HARQ process to transmit data on different carriers in a TDM manner, when the terminal performs new transmission or retransmission through a certain HARQ process, the terminal can perform new transmission or retransmission through the HARQ process on the carrier with the current uplink transmission opportunity, long-time waiting is not needed, the time delay of the uplink service of the terminal is reduced, and the network performance is improved.

With reference to the first aspect, in a first possible implementation manner of the first aspect, the first uplink carrier and the second uplink carrier perform uplink transmission in a TDM manner.

According to the method provided by the embodiment of the application, the uplink CA capability is not required, and the requirement on the terminal complexity is reduced. In addition, the performance of the single carrier is ensured not to be reduced by a multi-carrier time division transmission mode.

With reference to the first possible implementation manner of the first aspect, in a second possible implementation manner of the first aspect, a MIMO capability of the first uplink carrier when performing uplink transmission with the second uplink carrier in a TDM manner is the same as a MIMO capability of the first uplink carrier in a single carrier transmission mode; the MIMO capability of the second uplink carrier in TDM uplink transmission with the first uplink carrier is the same as the MIMO capability of the second uplink carrier in single carrier transmission.

In the embodiment of the application, when the multi-carrier is transmitted in a TDM manner, the MIMO capability of the single carrier is the same as that in a single carrier transmission mode, so that the transmission performance of the single carrier is not influenced, and the network performance is ensured.

With reference to the first aspect or the first or second possible implementation manner of the first aspect, in a third possible implementation manner of the first aspect, the first uplink carrier and the second uplink carrier support carrier aggregation CA; or, the first uplink carrier is a normal uplink NUL carrier, and the second uplink carrier is an auxiliary uplink SUL carrier; or, the first uplink carrier is a primary cell uplink carrier, and the second uplink carrier is a secondary cell uplink carrier.

The method provided by the embodiment of the application supports an uplink CA scene, an SUL scene and a DC scene.

With reference to the first aspect or any one of the first to third possible implementation manners of the first aspect, in a fourth possible implementation manner of the first aspect, the method further includes: and receiving first information sent by the access network equipment, wherein the first information is used for enabling the first uplink carrier and the second uplink carrier to share the first HARQ process.

In the method provided by the embodiment of the present application, the access network device may indicate the capability of the terminal to enable the multi-carrier sharing HARQ process. For example, the access network device indicates the terminal to start the capability of the multi-carrier sharing HARQ process, and the terminal supports the multi-carrier sharing of the same HARQ process, e.g., supports the first HARQ process shared by the first uplink carrier and the second uplink carrier, that is, the terminal may transmit data in the TDM manner on the first uplink carrier and the second uplink carrier through the first HARQ process.

With reference to the first aspect or any one of the first to fourth possible implementation manners of the first aspect, in a fifth possible implementation manner of the first aspect, second information is sent to an access network device, where the second information is used to indicate that a terminal supports sharing of a first HARQ process by a first uplink carrier and a second uplink carrier.

In the method provided by the embodiment of the application, the terminal may report its capability information to the access network, and indicate that the terminal has the capability of sharing the HARQ process by multiple carriers, for example, indicate, through the second information, that the terminal supports the first uplink carrier and the second uplink carrier to share the first HARQ process.

With reference to the first aspect or any one of the first to fifth possible implementation manners of the first aspect, in a sixth possible implementation manner of the first aspect, the first transport block is a new transport block; the second transport block is a retransmitted data block of the first transport block.

In the embodiment of the application, the terminal can transmit the newly transmitted data on different carriers in a TDM manner through the same HARQ process, so that the waiting time of the newly transmitted data of the terminal is prevented from being too long, and the time delay of the uplink service is reduced.

With reference to the first aspect or any one of the first to fifth possible implementation manners of the first aspect, in a sixth possible implementation manner of the first aspect, the first transport block is a new transport block; the second transmission block is a newly transmitted data block.

In the embodiment of the application, the terminal can transmit the newly transmitted data and the retransmission data of the newly transmitted data on different carriers in a TDM manner through the same HARQ process, so that the waiting time of the retransmission data of the terminal is prevented from being too long, and the time delay of the uplink service is reduced.

With reference to any one of the sixth possible implementation manners of the first aspect, in an eighth possible implementation manner of the first aspect, the second transport block includes N sub transport blocks, where N is an integer greater than or equal to 1, and N is R_iAnd i is an integer from 0 to N-1, the method further comprising: receiving a sub-transport block R from an access network device_iControl information of, sub transport block R_iIncludes an identification ID of the first HARQ process, a new data indication NDI and a sub-transport block R_iThe NDI is not flipped; on the second uplink carrier, the first HARQ process is used for sending a sub-transmission block R to the access network equipment_i。

In the embodiment of the application, when the retransmission data block is too large, the terminal can retransmit the sub-transmission block for multiple times. And the sub-transmission blocks are transmitted on different carriers by the same HARQ process in a TDM manner, so that the waiting time of retransmission data of the terminal is prevented from being overlong, and the time delay of uplink service is reduced.

In a second aspect, a communication device is disclosed, which may be a terminal or a chip in a terminal. The method comprises the following steps: a communication unit, configured to send a first transport block to an access network device through a first HARQ process on a first uplink carrier; on a second uplink carrier, a second transmission block is sent to the access network equipment through the first HARQ process; and the second transmission block and the first transmission block are transmitted in a Time Division Multiplexing (TDM) mode.

With reference to the first possible implementation manner of the second aspect, in a first possible implementation manner of the second aspect, the first uplink carrier and the second uplink carrier perform uplink transmission in a TDM manner.

With reference to the first possible implementation manner of the second aspect, in a second possible implementation manner of the second aspect, a MIMO capability of the first uplink carrier when performing uplink transmission with the second uplink carrier in a TDM manner is the same as a MIMO capability of the first uplink carrier in a single carrier transmission mode; the MIMO capability of the second uplink carrier in TDM uplink transmission with the first uplink carrier is the same as the MIMO capability of the second uplink carrier in single carrier transmission.

With reference to the second aspect or the first or second possible implementation manner of the second aspect, in a third possible implementation manner of the second aspect, the first uplink carrier and the second uplink carrier support carrier aggregation CA; or, the first uplink carrier is a normal uplink NUL carrier, and the second uplink carrier is an auxiliary uplink SUL carrier; or, the first uplink carrier is a primary cell uplink carrier, and the second uplink carrier is a secondary cell uplink carrier.

With reference to the second aspect or any one of the first to third possible implementation manners of the second aspect, in a fourth possible implementation manner of the second aspect, the communication unit is further configured to receive first information sent by the access network device, where the first information is used to enable the first uplink carrier and the second uplink carrier to share the first HARQ process.

With reference to the second aspect or any one of the first to fourth possible implementation manners of the second aspect, in a fifth possible implementation manner of the second aspect, the communication unit is further configured to send second information to the access network device, where the second information is used to indicate that the terminal supports sharing of the first HARQ process by the first uplink carrier and the second uplink carrier.

With reference to the second aspect or any one of the first to fourth possible implementation manners of the second aspect, in a sixth possible implementation manner of the second aspect, the first transport block is a new transport block; the second transport block is a retransmitted data block of the first transport block.

With reference to the second aspect or any one of the first to sixth possible implementation manners of the second aspect, in a seventh possible implementation manner of the second aspect, the first transport block is a new transport block; the second transmission block is a newly transmitted data block.

With reference to any one of the sixth possible implementation manners of the second aspect, in an eighth possible implementation manner of the second aspect, the second transport block includes N sub transport blocks, where N is an integer greater than or equal to 1, and N is R_iI is an integer from 0 to N-1,

the communication unit is further adapted to receive a sub-transport block R from the access network device_iControl information of, sub transport block R_iIncludes an identification ID of the first HARQ process, a new data indication NDI and a sub-transport block R_iThe NDI is not flipped;

the communication unit is further configured to send the sub-transport block R to the access network device on the second uplink carrier using the first HARQ process_i。

In a third aspect, a communication apparatus is disclosed, comprising: a communication interface, configured to send a first transport block to an access network device through a first HARQ process on a first uplink carrier; on a second uplink carrier, a second transmission block is sent to the access network equipment through the first HARQ process; and the second transmission block and the first transmission block are transmitted in a Time Division Multiplexing (TDM) mode.

With reference to the first possible implementation manner of the third aspect, in a first possible implementation manner of the third aspect, the first uplink carrier and the second uplink carrier perform uplink transmission in a TDM manner.

With reference to the first possible implementation manner of the third aspect, in a second possible implementation manner of the third aspect, a MIMO capability of the first uplink carrier when performing uplink transmission with the second uplink carrier in a TDM manner is the same as a MIMO capability of the first uplink carrier in a single carrier transmission mode; the MIMO capability of the second uplink carrier in TDM uplink transmission with the first uplink carrier is the same as the MIMO capability of the second uplink carrier in single carrier transmission.

With reference to the third aspect or the first or second possible implementation manner of the third aspect, in a third possible implementation manner of the third aspect, the first uplink carrier and the second uplink carrier support carrier aggregation CA; or, the first uplink carrier is a normal uplink NUL carrier, and the second uplink carrier is an auxiliary uplink SUL carrier; or, the first uplink carrier is a primary cell uplink carrier, and the second uplink carrier is a secondary cell uplink carrier.

With reference to the third aspect or any one of the first to third possible implementation manners of the third aspect, in a fourth possible implementation manner of the third aspect, the communication interface is further configured to receive first information sent by the access network device, where the first information is used to enable the first uplink carrier and the second uplink carrier to share the first HARQ process.

With reference to the third aspect or any one of the first to fourth possible implementation manners of the third aspect, in a fifth possible implementation manner of the third aspect, the communication interface is further configured to send second information to the access network device, where the second information is used to indicate that the terminal supports the first uplink carrier and the second uplink carrier to share the first HARQ process.

With reference to the third aspect or any one of the first to fourth possible implementation manners of the third aspect, in a sixth possible implementation manner of the third aspect, the first transport block is a new transport block; the second transport block is a retransmitted data block of the first transport block.

With reference to the third aspect or any one of the first to sixth possible implementation manners of the third aspect, in a seventh possible implementation manner of the third aspect, the first transport block is a new transport block; the second transmission block is a newly transmitted data block.

Bonding ofIn an eighth possible implementation manner of the third aspect, the second transport block includes N sub transport blocks, N is an integer greater than or equal to 1, and N is R_iI is an integer from 0 to N-1,

the communication interface is further adapted to receive a sub-transport block R from the access network device_iControl information of, sub transport block R_iIncludes an identification ID of the first HARQ process, a new data indication NDI and a sub-transport block R_iThe NDI is not flipped;

the communication interface is further configured to send the sub-transport block R to the access network device on the second uplink carrier using the first HARQ process_i。

In a fourth aspect, an uplink HARQ transmission method is disclosed, which may be executed by an access network device or a chip in the access network device. The method comprises the following steps: on a first uplink carrier, receiving a first transport block sent by a terminal through a first HARQ process; on a second uplink carrier, receiving a second transmission block sent by the terminal through the first HARQ process; and the second transmission block and the first transmission block are transmitted in a Time Division Multiplexing (TDM) mode.

With reference to the fourth aspect, in a first possible implementation manner of the fourth aspect, the first uplink carrier and the second uplink carrier perform uplink transmission in a TDM manner.

With reference to the fourth aspect or the first possible implementation manner of the fourth aspect, in a second possible implementation manner of the fourth aspect, a MIMO capability of the first uplink carrier when performing uplink transmission with the second uplink carrier in a TDM manner is the same as a MIMO capability of the first uplink carrier in a single carrier transmission mode; the MIMO capability of the second uplink carrier in TDM uplink transmission with the first uplink carrier is the same as the MIMO capability of the second uplink carrier in single carrier transmission.

With reference to the fourth aspect or the first or second possible implementation manner of the fourth aspect, in a third possible implementation manner of the fourth aspect, the first uplink carrier is a primary cell uplink carrier and the second uplink carrier is a secondary cell uplink carrier; or, the first uplink carrier is a normal uplink NUL carrier, and the second uplink carrier is an auxiliary uplink SUL carrier; or the first uplink carrier is a main cell group uplink carrier, and the second uplink carrier is a secondary cell group uplink carrier.

With reference to the fourth aspect or any one of the first to third possible implementation manners of the fourth aspect, in a fourth possible implementation manner of the fourth aspect, the method further includes: and sending first information to the terminal, wherein the first information is used for enabling the first uplink carrier and the second uplink carrier to share the first HARQ process.

With reference to the fourth aspect or any one of the first to fourth possible implementation manners of the fourth aspect, in a fifth possible implementation manner of the fourth aspect, the method further includes: and sending second information to the terminal, wherein the second information is used for indicating that the terminal supports the first uplink carrier and the second uplink carrier to share the first HARQ process.

With reference to the fourth aspect or any one of the first to fifth possible implementation manners of the fourth aspect, in a sixth possible implementation manner of the fourth aspect, the first transport block is a new transport block; the second transport block is a retransmitted data block of the first transport block.

With reference to the fourth aspect or any one of the first to sixth possible implementation manners of the fourth aspect, in a seventh possible implementation manner of the fourth aspect, the first transport block is a new transport block; the second transmission block is a newly transmitted data block.

With reference to the fourth aspect or any one of the first to seventh possible implementation manners of the fourth aspect, in an eighth possible implementation manner of the fourth aspect, the second transport block includes N sub transport blocks, N is an integer greater than or equal to 1, and N sub transport blocks are R_iAnd i is an integer from 0 to N-1, the method further comprising:

transmitting a sub-transport block R to a terminal_iControl information of, sub transport block R_iIncludes an identification ID of the first HARQ process, a new data indication NDI and a sub-transport block R_iThe NDI is not flipped; on the second upstream lineOn the carrier, the receiving terminal uses the sub-transmission block R sent by the first HARQ process_i。

In a fifth aspect, a communication apparatus is disclosed, which may be an access network device or a chip in the access network device. The method comprises the following steps: a communication unit, configured to receive, on a first uplink carrier, a first transport block sent by a terminal through a first HARQ process; the communication unit is further configured to receive, on a second uplink carrier, a second transport block sent by the terminal through the first HARQ process; and the second transmission block and the first transmission block are transmitted in a TDM mode.

With reference to the fifth aspect, in a first possible implementation manner of the fifth aspect, the first uplink carrier and the second uplink carrier perform uplink transmission in a TDM manner.

With reference to the fifth aspect or the first possible implementation manner of the fifth aspect, in a second possible implementation manner of the fifth aspect, the MIMO capability of the first uplink carrier when performing uplink transmission with the second uplink carrier in a TDM manner is the same as the MIMO capability of the first uplink carrier in a single carrier transmission mode; the MIMO capability of the second uplink carrier in TDM uplink transmission with the first uplink carrier is the same as the MIMO capability of the second uplink carrier in single carrier transmission.

With reference to the fifth aspect or the first or second possible implementation manner of the fifth aspect, in a third possible implementation manner of the fifth aspect, the first uplink carrier is a primary cell uplink carrier and the second uplink carrier is a secondary cell uplink carrier; or, the first uplink carrier is a normal uplink NUL carrier, and the second uplink carrier is an auxiliary uplink SUL carrier; or the first uplink carrier is a main cell group uplink carrier, and the second uplink carrier is a secondary cell group uplink carrier.

With reference to the fifth aspect or any one of the first to third possible implementation manners of the fifth aspect, in a fourth possible implementation manner of the fifth aspect, the communication unit is further configured to send, to the terminal, first information, where the first information is used to enable the first uplink carrier and the second uplink carrier to share the first HARQ process.

With reference to the fifth aspect or any one of the first to fourth possible implementation manners of the fifth aspect, in a fifth possible implementation manner of the fifth aspect, the communication unit is further configured to send second information to the terminal, where the second information is used to indicate that the terminal supports the first uplink carrier and the second uplink carrier to share the first HARQ process.

With reference to the fifth aspect or any one of the first to fifth possible implementation manners of the fifth aspect, in a sixth possible implementation manner of the fifth aspect, the first transport block is a new transport block; the second transport block is a retransmitted data block of the first transport block.

With reference to the fifth aspect or any one of the first to sixth possible implementation manners of the fifth aspect, in a seventh possible implementation manner of the fifth aspect, the first transport block is a new transport block; the second transmission block is a newly transmitted data block.

With reference to the fifth aspect or any one of the first to seventh possible implementation manners of the fifth aspect, in an eighth possible implementation manner of the fifth aspect, the second transport block includes N sub transport blocks, N is an integer greater than or equal to 1, and N sub transport blocks are R_iAnd i is an integer from 0 to N-1. The communication unit is further adapted to send the sub-transport blocks R to the terminal_iControl information of, sub transport block R_iIncludes an identification ID of the first HARQ process, a new data indication NDI and a sub-transport block R_iThe NDI is not flipped; on the second uplink carrier, the receiving terminal uses the sub-transmission block R sent by the first HARQ process_i。

In a sixth aspect, a communication apparatus is disclosed, which may be an access network device or a chip in the access network device. The method comprises the following steps: a communication unit, configured to receive, on a first uplink carrier, a first transport block sent by a terminal through a first HARQ process; the communication unit is further configured to receive, on a second uplink carrier, a second transport block sent by the terminal through the first HARQ process; and the second transmission block and the first transmission block are transmitted in a TDM mode.

With reference to the sixth aspect, in a first possible implementation manner of the sixth aspect, the first uplink carrier and the second uplink carrier perform uplink transmission in a TDM manner.

With reference to the sixth aspect or the first possible implementation manner of the sixth aspect, in a second possible implementation manner of the sixth aspect, the MIMO capability of the first uplink carrier when performing uplink transmission with the second uplink carrier in a TDM manner is the same as the MIMO capability of the first uplink carrier in a single carrier transmission mode; the MIMO capability of the second uplink carrier in TDM uplink transmission with the first uplink carrier is the same as the MIMO capability of the second uplink carrier in single carrier transmission.

With reference to the sixth aspect or the first or second possible implementation manner of the sixth aspect, in a third possible implementation manner of the sixth aspect, the first uplink carrier is a primary cell uplink carrier and the second uplink carrier is a secondary cell uplink carrier; or, the first uplink carrier is a normal uplink NUL carrier, and the second uplink carrier is an auxiliary uplink SUL carrier; or the first uplink carrier is a main cell group uplink carrier, and the second uplink carrier is a secondary cell group uplink carrier.

With reference to the sixth aspect or any one of the first to third possible implementation manners of the sixth aspect, in a fourth possible implementation manner of the sixth aspect, the communication unit is further configured to send, to the terminal, first information, where the first information is used to enable the first uplink carrier and the second uplink carrier to share the first HARQ process.

With reference to the sixth aspect or any one of the first to fourth possible implementation manners of the sixth aspect, in a fifth possible implementation manner of the sixth aspect, the communication unit is further configured to send second information to the terminal, where the second information is used to indicate that the terminal supports the first uplink carrier and the second uplink carrier to share the first HARQ process.

With reference to the sixth aspect or any one of the first to fifth possible implementation manners of the sixth aspect, in a sixth possible implementation manner of the sixth aspect, the first transport block is a new transport block; the second transport block is a retransmitted data block of the first transport block.

With reference to the sixth aspect or any one of the first to sixth possible implementation manners of the sixth aspect, in a seventh possible implementation manner of the sixth aspect, the first transport block is a new transport block; the second transmission block is a newly transmitted data block.

With reference to the sixth aspect or any one of the first to seventh possible implementation manners of the sixth aspect, in an eighth possible implementation manner of the sixth aspect, the second transport block includes N sub transport blocks, N is an integer greater than or equal to 1, and N sub transport blocks are R_iAnd i is an integer from 0 to N-1. The communication unit is further adapted to send the sub-transport blocks R to the terminal_iControl information of, sub transport block R_iIncludes an identification ID of the first HARQ process, a new data indication NDI and a sub-transport block R_iThe NDI is not flipped; on the second uplink carrier, the receiving terminal uses the sub-transmission block R sent by the first HARQ process_i。

In a seventh aspect, a communication method is disclosed, including: the terminal reports the capability information to the access network equipment, wherein the capability information is used for indicating an uplink carrier frequency band supported by the terminal; the access network equipment selects a first uplink carrier and a second uplink carrier according to the capability information reported by the terminal; the first uplink carrier and the second uplink carrier are transmitted in a TDM mode; further, the access network device may also send the information of the first uplink carrier and the information of the second uplink carrier to the terminal, and indicate that the first uplink carrier and the second uplink carrier may be transmitted in a TDM manner.

In the uplink CA scenario, the MIMO capability and maximum transmit power of each aggregated CC (carrier) are reduced compared to that in single carrier transmission mode. Taking the aggregation of the n 773.5 GHz uplink carrier and the n 31.8 GHz uplink carrier as an example, the terminal needs to have the capability of sending uplink data at the 3.5GHz uplink carrier and the 1.8GHz uplink carrier simultaneously, and has large power consumption and short standby time. Secondly, 3.5GHz uplink carriers and 1.8GHz uplink carriers can only be transmitted by using 1 antenna, the maximum transmitting power is also reduced to 23dBm from 26dBm of the original single carrier, the performance on each carrier is reduced relative to the single carrier transmission mode, and the overall performance improvement of uplink communication is not obvious. In addition, the uplink carrier concurrency has a high requirement on the complexity of the terminal, and many terminals do not support uplink CA.

The embodiment of the application also provides a communication method, which does not require the terminal to have the uplink CA capability and reduces the requirement on the complexity of the terminal. In addition, the multi-carrier can be transmitted in a TDM manner, the performance of the single carrier is not reduced, the uplink wireless resources can be effectively utilized, and the performance of uplink communication is improved.

In an eighth aspect, a communication device is disclosed, which includes a memory, a processor, and a program stored in the memory and executable on the processor, and when the program is executed by the processor, the processor implements the first aspect and any one of the possible implementations of the first aspect, the method described in any one of the possible implementations of the fourth aspect and the fourth aspect, or the method described in the seventh aspect.

In a ninth aspect, embodiments of the present application provide a chip, where the chip includes a processor and an interface circuit, where the interface circuit is coupled to the processor, and the processor is configured to execute a computer program or instructions to implement the method according to the first aspect and any one of the possible implementations of the first aspect, the fourth aspect and any one of the possible implementations of the fourth aspect, or the method according to the seventh aspect, and the interface circuit is configured to communicate with other modules outside the chip.

In a tenth aspect, a computer-readable storage medium is disclosed, which comprises instructions that, when executed on a computer, cause the computer to perform the method described above for implementing the first aspect and any one of the possible implementations of the first aspect, the method described above for implementing any one of the possible implementations of the fourth aspect and the fourth aspect, or the communication method described above for the fourth aspect.

In an eleventh aspect, a computer program product is disclosed, comprising instructions which, when run on a computer, cause the computer to perform the method according to the first aspect as well as any one of the possible implementations of the first aspect, the fourth aspect as well as any one of the possible implementations of the fourth aspect, or the method according to the seventh aspect.

In a twelfth aspect, a wireless communications apparatus is disclosed that includes: instructions are stored in the wireless communication device; when the wireless communication apparatus is operated on the apparatus according to the above sixth aspect to the eighth aspect, so that the apparatus performs the method according to the above first aspect and any one of the possible implementation manners of the first aspect, the fourth aspect and any one of the possible implementation manners of the fourth aspect, or the method according to the above seventh aspect, the wireless communication apparatus may be a chip.

In a thirteenth aspect, a system is disclosed that includes an access network device and a terminal. Illustratively, the terminal is configured to send a first transport block to the access network device through a first HARQ process on a first uplink carrier; on a second uplink carrier, a second transmission block is sent to the access network equipment through the first HARQ process; and the second transmission block and the first transmission block are transmitted in a Time Division Multiplexing (TDM) mode.

The access network equipment is used for receiving the first transmission block and the second transmission block sent by the terminal.

Drawings

Fig. 1 is an architecture diagram of a communication system provided in an embodiment of the present application;

fig. 2 is a schematic diagram of a CA scenario provided in an embodiment of the present application;

fig. 3 is a schematic diagram of an SUL scene provided in an embodiment of the present application;

fig. 4 is an architecture diagram of another communication system provided by an embodiment of the present application;

fig. 5 is a schematic diagram of a HARQ entity managing a HARQ process according to an embodiment of the present application;

fig. 6A is a block diagram of a terminal according to an embodiment of the present disclosure;

fig. 6B is a block diagram of an access network device according to an embodiment of the present application;

fig. 7A is a schematic flowchart of uplink HARQ transmission according to an embodiment of the present application;

fig. 7B is a schematic diagram of an rf channel provided in an embodiment of the present application;

fig. 8 is a schematic diagram of HARQ process sharing provided in an embodiment of the present application;

fig. 9 is a flowchart illustrating a communication method according to an embodiment of the present application;

fig. 10 is another block diagram of a communication device according to an embodiment of the present application;

fig. 11 is another block diagram of a communication device according to an embodiment of the present disclosure;

fig. 12 is another block diagram of a communication device according to an embodiment of the present disclosure;

fig. 13 is another block diagram of a communication device according to an embodiment of the present disclosure.

Detailed Description

The technical solution in the present application will be described below with reference to the accompanying drawings.

Fig. 1 shows a schematic diagram of a communication system to which the technical solution provided in the present application is applicable, which may include one or more access network devices 100 and one or more terminals 200 (only one terminal 200 is shown in fig. 1) connected to each access network device 100 of the one or more access network devices 100. Fig. 1 illustrates an access network device and a terminal, and it should be noted that fig. 1 is only a schematic diagram and does not constitute a limitation to an application scenario of the technical solution provided in the present application.

The access network device 100 may be a transmission reception node (TRP), a base station, a relay station, a node, an access point, or the like. The access network device 100 may be an access network device in a 5G communication system or an access network device in a future evolution network; but also wearable devices or vehicle-mounted devices, etc. In addition, the method can also comprise the following steps: a Base Transceiver Station (BTS) in a global system for mobile communication (GSM) or Code Division Multiple Access (CDMA) network, or an nb (nodeb) in Wideband Code Division Multiple Access (WCDMA), or an eNB or enodeb (evolved nodeb) in Long Term Evolution (LTE). The access network device 100 may also be a wireless controller in a Cloud Radio Access Network (CRAN) scenario. The present application will be described below with reference to a base station as an example.

The terminal 200 may be a User Equipment (UE), an access terminal, a UE unit, a UE station, a mobile station, a remote terminal, a mobile device, a UE terminal, a wireless communication device, a UE agent, or a UE device, etc. An access terminal may be a cellular telephone, a cordless telephone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, a vehicle mounted device, a wearable device, a terminal in a 5G network or a terminal in a future evolved Public Land Mobile Network (PLMN) network, etc.

The communication system shown in fig. 1 supports a CA scenario, a Dual Connectivity (DC) scenario, and a Supplemental Uplink (SUL) scenario.

Fig. 2 is a schematic diagram of a CA scenario. As shown in fig. 2, the access network device 100 provides a primary cell uplink carrier and a secondary cell uplink carrier for the terminal 200, the primary cell uplink carrier provides a primary cell, the secondary cell uplink carrier provides a secondary cell, the terminal 200 may be located in a coverage of the primary cell and a coverage of the secondary cell, the terminal 200 may send data to the access network device 100 through the primary cell uplink carrier and the secondary cell uplink carrier, and the access network device 100 may also send data to the terminal 200 through the primary cell uplink carrier and the secondary cell uplink carrier. It should be noted that, in the embodiment of the present application, there is no limitation on the sizes of the coverage areas of the primary cell and the secondary cell, and for convenience of description, one cell is referred to as a primary cell, and another cell is referred to as a secondary cell, where the primary cell and the secondary cell may be interchanged, and the names of the primary cell and the secondary cell do not play a limiting role.

The primary cell may adopt a TDD or FDD frequency band, and the secondary cell may adopt a TDD or FDD frequency band. For example, when the primary cell adopts a TDD band and the secondary cell adopts a TDD band, the CA scenario at this time may be referred to as a TDD + TDD CA scenario; for example, when the primary cell adopts a TDD frequency band and the secondary cell adopts an FDD frequency band, the CA scenario at this time may be referred to as a TDD + FDD CA scenario.

FIG. 3 is a schematic diagram of a SUL scene. As shown in fig. 2, the access network device 100 may provide two uplink carriers for the terminal 200, which are a Normal Uplink (NUL) carrier and a Supplementary Uplink (SUL) carrier, and the NUL and the SUL may be transmitted in a Time Division Multiplexing (TDM) manner. In addition, the SUL may adopt a frequency band lower than the NUL, and when the multi-band of the SUL is lower than the NUL, the coverage of the SUL is larger than the NUL coverage, as shown in fig. 3, the terminal 200 may be located in a near-midpoint region in the cell. When the terminal 200 is in the near-midpoint area, it may be understood that the terminal 200 may be in the NUL and SUL coverage simultaneously, or that the terminal 200 is in the NUL coverage, or that the distance from the terminal 200 to the access network device 11 does not exceed a threshold. The SUL may use a frequency band higher than the NUL, which is not limited in the embodiment of the present application.

Fig. 4 shows a schematic diagram of another communication system to which the technical solution provided by the present application is applicable, which may include two access network nodes (access network node 301, access network node 302) and one or more terminals 200 (only one terminal 200 is shown in fig. 4) connected to each access network node. Fig. 4 is a schematic diagram, and does not limit the application scenarios of the technical solutions provided in the present application. The communication system shown in fig. 4 supports a Dual Connectivity (DC) scenario, where the access network node 301 and the access network node 302 may be two nodes, both the access network node 301 and the access network node may be the above-mentioned access network device 100, and the access network node 301 and the access network node 302 may also be integrated in one access network device 100.

Referring to fig. 4, in a DC scenario, access network node 301 may provide terminal 200 with one uplink carrier (uplink carrier 1 shown in fig. 4) for uplink communication between terminal 200 and access network node 301. The access network node 302 may provide an uplink carrier (uplink carrier 2 shown in fig. 4) for the terminal 200, for uplink communication between the terminal 200 and the access network node 302. The access network node 301 may be a master node, the access network node 302 may be a slave node, the uplink carrier 1 may be referred to as a master cell group uplink carrier (or may be referred to as a master node uplink carrier), and the uplink carrier 2 may be referred to as a slave cell group uplink carrier (or may be referred to as a slave node uplink carrier); alternatively, the access network node 302 may be a primary node, the access network node 301 may be a secondary node, the uplink carrier 2 may be referred to as a primary cell group uplink carrier (or may be referred to as a primary node uplink carrier), and the uplink carrier 1 may be referred to as a secondary cell group uplink carrier (or may be referred to as a secondary node uplink carrier).

To facilitate understanding of the technical solution, terms related to the embodiments of the present application are explained as follows:

(1) HARQ process

In the embodiment of the application, the terminal maintains one HARQ entity, the HARQ entity is used for managing all HARQ processes and HARQ buffers of all HARQ processes, and the terminal can buffer data in the HARQ buffers of the HARQ processes. When a terminal transmits data through one HARQ process on a certain carrier, the terminal may obtain the data in the HARQ buffer of the HARQ process. For example, referring to fig. 5, assuming that there are N HARQ processes for uplink transmission, one HARQ entity of a terminal may manage the N HARQ processes, and when the terminal transmits data through a certain HARQ process on one carrier, the terminal reads data in a HARQ buffer of the HARQ process in the HARQ entity. It should be noted that one HARQ entity may maintain multiple parallel HARQ processes, each HARQ process has one HARQ Identity (ID), and different HARQ processes may be distinguished by the HARQ ID.

In addition, some HARQ processes need to maintain a state variable, namely HARQ FEEDBACK (HARQ _ FEEDBACK), and the terminal may set the HARQ FEEDBACK of the HARQ process to an Acknowledgement (ACK) or a Negative Acknowledgement (NACK) according to the HARQ FEEDBACK value received by the HARQ process.

(2) New Data Identifier (NDI)

Each HARQ process maintains an NDI. In a possible implementation manner, NDI is 1bit, and the value of this bit indicates whether the terminal uses the HARQ process for new transmission or retransmission. If the value of the NDI of the HARQ process is flipped more than the last time, it indicates that the terminal can use the HARQ process to transmit new data, and if the value of the NDI is not flipped, it indicates that the terminal can use the HARQ process to retransmit data.

For example, if the NDI of the HARQ process is flipped from "0" to "1", it indicates that the terminal can use the HARQ process for new transmission.

(3) TDM mode

When the first data (e.g., the first transport block) and the second data (e.g., the second transport block) are transmitted in the TDM manner, the time domain resource of the first data and the time domain resource of the second data do not overlap, or it can be understood that the time domain resource of the first data and the time domain resource of the second data are different, or the first data and the second data are not transmitted at the same time.

When the first uplink carrier and the second uplink carrier are transmitted in a TDM manner, it may be understood that a time domain resource of the first uplink carrier and a time domain resource of the second uplink carrier are not overlapped, or the time domain resource of the first uplink carrier and the time domain resource of the second uplink carrier are different, or the first uplink carrier and the second uplink carrier do not send data at the same time, or the first uplink carrier and the second uplink carrier send data singly, or only one uplink carrier is used for sending data at the same time. When the first uplink carrier and the second uplink carrier are transmitted in the TDM manner, the data on the first uplink carrier and the data on the second uplink carrier are also transmitted in the TDM manner.

The embodiment of the present application provides a scheme, where two uplink carriers are configured for a terminal 200, which are a first uplink carrier and a second uplink carrier, respectively, where the first uplink carrier and the second uplink carrier may be two uplink carriers in a CA scenario, for example, a primary cell uplink carrier and a secondary cell uplink carrier in fig. 2; alternatively, the first uplink carrier and the second uplink carrier may be two uplink carriers in an SUL scenario, for example, a NUL carrier and an SUL carrier in fig. 3; alternatively, the first uplink carrier and the second uplink carrier may be two uplink carriers in a DC scenario, such as uplink carrier 1 and uplink carrier 2 in fig. 4. The terminal 200 sends a first transport block to the access network device through a first HARQ process on a first uplink carrier; and sending a second transport block to the access network equipment through the first HARQ process on a second uplink carrier. Wherein the second transport block and the first transport block are transmitted in a Time Division Multiplexing (TDM) manner. It can be seen that, in the method provided in this embodiment of the present application, a terminal may use the same HARQ process to transmit data on different carriers in a TDM manner, and when the terminal performs new transmission or retransmission through a certain HARQ process, it may flexibly select a carrier currently having an uplink transmission opportunity to perform new transmission or retransmission through the HARQ process, so as to avoid that when each carrier maintains its HARQ process, the HARQ process on each carrier needs to wait for the uplink transmission opportunity on the carrier to perform new transmission or retransmission through the HARQ process, which results in long-time waiting, thereby reducing the time delay of the uplink service of the terminal and improving the network performance.

The terminal according to the embodiment of the present application can be implemented by the communication device 610 in fig. 6A. Fig. 6A is a schematic diagram illustrating a hardware structure of a communication device 610 according to an embodiment of the present disclosure. The communication device 610 includes a processor 6101, a communication link 6102, a memory 6103, and at least one communication interface (fig. 6A is only exemplary and is illustrated as including the communication interface 6104).

The processor 6101 may be a general purpose Central Processing Unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more ics for controlling the execution of programs in accordance with the present disclosure.

The communication link 6102 may include a path for communicating information between the aforementioned components.

Communication interface 6104 may be implemented using any transceiver or the like for communicating with other devices or communication networks, such as ethernet, Radio Access Network (RAN), Wireless Local Area Networks (WLAN), etc.

The memory 6103 may be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a Random Access Memory (RAM) or other type of dynamic storage device that can store information and instructions, an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disk storage, optical disk storage (including compact disc, laser disc, optical disc, digital versatile disc, blu-ray disc, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited to these. The memory may be separate and coupled to the processor via communication link 6102. The memory may also be integral to the processor.

The memory 6103 is used for storing computer-executable instructions for executing the present invention, and is controlled by the processor 6101 to execute. The processor 6101 is configured to execute the computer executable instructions stored in the memory 6103, thereby implementing the intent processing method provided by the following embodiments of the present application.

Optionally, the computer-executable instructions in the embodiments of the present application may also be referred to as application program codes, which are not specifically limited in the embodiments of the present application.

In particular implementations, processor 6101 may include one or more CPUs, such as CPU0 and CPU1 in fig. 6A, as an example.

In a specific implementation, the communication device 610 may include multiple processors, such as the processor 6101 and the processor 6108 in fig. 6A, as an example. Each of these processors may be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor. A processor herein may refer to one or more devices, circuits, and/or processing cores for processing data (e.g., computer program instructions).

In a specific implementation, the communication apparatus 610 may further include an output device 6105 and an input device 6106 as an embodiment. An output device 6105 is in communication with the processor 6101 and may display information in a variety of ways. For example, the output device 6105 may be a Liquid Crystal Display (LCD), a Light Emitting Diode (LED) display device, a Cathode Ray Tube (CRT) display device, a projector (projector), or the like. The input device 6106 is in communication with the processor 6101 and can receive input from a user in a variety of ways. For example, the input device 6106 may be a mouse, keyboard, touch screen device, or sensing device, among others.

The communication device 610 may be a general-purpose device or a special-purpose device. In a specific implementation, the communication device 610 may be a desktop computer, a laptop computer, a web server, a Personal Digital Assistant (PDA), a mobile phone, a tablet computer, a wireless terminal device, an embedded device, or a device with a similar structure as in fig. 6A. The embodiment of the present application does not limit the type of the communication device 610.

Fig. 6B is a schematic structural diagram of an access network device. The structure of the access network device 620 may refer to the structure shown in fig. 6B.

The access network equipment includes at least one processor 6201, at least one memory 6202, at least one transceiver 6203, at least one network interface 6204, and one or more antennas 6205. The processor 6201, memory 6202, transceiver 6203, and network interface 6204 are connected, e.g., via a bus. Antenna 6205 is connected to transceiver 6203. Network interface 6204 is configured to enable the access network device to connect to other communication devices through a communication link, for example, the access network device connects to a network element of a core network through an S1 interface. In the embodiment of the present application, the connection may include various interfaces, transmission lines, buses, and the like, which is not limited in this embodiment.

The processor in this embodiment, for example, the processor 6201, may include at least one of the following types: a general-purpose Central Processing Unit (CPU), a Digital Signal Processor (DSP), a microprocessor, an Application-Specific Integrated Circuit (ASIC), a Microcontroller (MCU), a Field Programmable Gate Array (FPGA), or an Integrated Circuit for implementing logic operations. For example, the processor 6201 may be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor. The at least one processor 6201 may be integrated in one chip or located on multiple different chips.

The memory, for example, the memory 6202, in the embodiment of the present application may include at least one of the following types: read-only memory (ROM) or other types of static memory devices that may store static information and instructions, Random Access Memory (RAM) or other types of dynamic memory devices that may store information and instructions, and Electrically erasable programmable read-only memory (EEPROM). In some scenarios, the memory may also be, but is not limited to, a compact disk-read-only memory (CD-ROM) or other optical disk storage, optical disk storage (including compact disk, laser disk, optical disk, digital versatile disk, blu-ray disk, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer.

The memory 6202 may be separate and coupled to the processor 6201. Alternatively, the memory 6202 may be integrated with the processor 6201, for example, integrated in one chip. The memory 6202 can store program codes for executing the technical solution of the embodiment, and the processor 6201 controls the execution of the program codes, and various executed computer program codes can also be regarded as drivers of the processor 6201. For example, the processor 6201 is configured to execute computer program codes stored in the memory 6202, so as to implement the technical solution in the embodiment of the present application.

Transceiver 6203 may be configured to support receiving or transmitting radio frequency signals between the access network device and the terminal, and transceiver 6203 may be connected to antenna 6205. Specifically, one or more antennas 6205 may receive an rf signal, and the transceiver 6203 may be configured to receive the rf signal from the antennas, convert the rf signal into a digital baseband signal or a digital if signal, and provide the digital baseband signal or the digital if signal to the processor 6201, so that the processor 6201 performs further processing on the digital baseband signal or the digital if signal, such as demodulation processing and decoding processing. Additionally, transceiver 6203 may be configured to receive a modulated digital baseband signal or digital intermediate frequency signal from processor 6201, convert the modulated digital baseband signal or digital intermediate frequency signal to a radio frequency signal, and transmit the radio frequency signal via one or more antennas 6205. Specifically, the transceiver 6203 may selectively perform one or more stages of down-mixing processing and analog-to-digital conversion processing on the rf signal to obtain a digital baseband signal or a digital intermediate frequency signal, where a sequence of the down-mixing processing and the analog-to-digital conversion processing is adjustable. The transceiver 6203 may selectively perform one or more stages of up-mixing processing and digital-to-analog conversion processing on the modulated digital baseband signal or the digital intermediate frequency signal to obtain the radio frequency signal, where an order of the up-mixing processing and the digital-to-analog conversion processing is adjustable. The digital baseband signal and the digital intermediate frequency signal may be collectively referred to as a digital signal. A transceiver may be referred to as a transceiving circuit, a transceiving unit, a transceiving device, a transmitting circuit, a transmitting unit, a transmitting device, or the like.

An embodiment of the present application provides an uplink HARQ transmission method, which is applied to the communication systems shown in fig. 1 to 4, and as shown in fig. 7A, the method includes the following steps:

701. and the terminal sends second information to the access network equipment, wherein the second information is used for indicating that the terminal supports the first uplink carrier and the second uplink carrier to share the first HARQ process.

It should be noted that the first uplink carrier and the second uplink carrier are two uplink carriers configured between the access network devices, and the first HARQ process is any one of HARQ processes used for uplink transmission. The first uplink carrier and the second uplink carrier share one HARQ process, that is, the terminal may use the same HARQ process on two different carriers, for example, uplink transmission may be performed through the first HARQ process on the first uplink carrier, and uplink transmission may also be performed through the first HARQ process on the second uplink carrier.

In this embodiment of the application, when the first uplink carrier and the second uplink carrier share the first HARQ process, the first uplink carrier and the second uplink carrier may share the HARQ buffer of the first HARQ process. And when the terminal sends data through the first HARQ process on the first uplink carrier, acquiring the data in the HARQ buffer of the first HARQ process. And when the terminal sends data through the first HARQ process on the second uplink carrier, acquiring the data in the HARQ buffer of the first HARQ process.

In a specific implementation, the terminal may send the first uplink carrier and the second uplink carrier in the following two manners.

The first uplink carrier and the second uplink carrier support a TDM transmission scenario, that is, the terminal cannot simultaneously and concurrently transmit the first uplink carrier and the second uplink carrier, and transmit the first uplink carrier and the second uplink carrier in a TDM manner. For example, in an SUL scenario, a first uplink carrier is a NUL carrier, a second uplink carrier is a SUL carrier, and the NUL carrier and the SUL carrier are transmitted in a TDM manner; or the first uplink carrier and the second uplink carrier are uplink carriers in a CA scene or a DC scene.

It should be noted that, the first uplink carrier and the second uplink carrier are sent in a TDM manner, which may be understood that the first uplink carrier and the second uplink carrier are not sent at the same time, or an uplink time domain resource of the first uplink carrier and an uplink time domain resource of the second uplink carrier are not overlapped. In addition, in the embodiment of the present application, the uplink carrier transmission, or the uplink carrier transmission, may be understood as transmitting uplink data through the uplink carrier.

Optionally, in this implementation, when the first uplink carrier performs uplink transmission in a TDM manner with the second uplink carrier, a multiple-input multiple-output (MIMO) capability of the first uplink carrier is the same as a MIMO capability of the first uplink carrier in a single carrier transmission mode; the MIMO capability of the second uplink carrier in TDM uplink transmission with the first uplink carrier is the same as the MIMO capability of the second uplink carrier in single carrier transmission. The MIMO capability may be understood as the number of MIMO layers supported by a carrier, or the number of radio frequency channels supported by the carrier. Illustratively, when the terminal sends the first uplink carrier and the second uplink carrier in a TDM manner, the number of MIMO layers supported by the first uplink carrier is the same as the number of MIMO layers supported by the first uplink carrier when the terminal sends the first uplink carrier alone; the number of MIMO layers supported by the second uplink carrier is the same as the number of MIMO layers supported by the second uplink carrier when the terminal transmits the second uplink carrier alone.

For example, as shown in fig. 7B, the first uplink carrier and the second uplink carrier share the radio frequency channel 1 and the radio frequency channel 2, when the first uplink carrier operates in the single carrier transmission mode (or can be understood as a single transmission mode), the switch 1 operates in the state 1, the switch 2 operates in the state 1, and the radio frequency channel 1 and the radio frequency channel 2 provide the first uplink carrier 2T; when the second uplink carrier operates in a single carrier transmission mode (or may be understood as a single-shot mode), the switch 1 operates in the state 2, the switch 2 operates in the state 2, and the secondary cell uplink carrier 2T is provided through the radio frequency channel 1 and the radio frequency channel 2.

If the first uplink carrier and the second uplink carrier are sent in a TDM manner, the radio frequency channel 1 and the radio frequency channel 2 may be adopted when the first uplink carrier works; the first uplink carrier may also use the radio frequency channel 1 and the radio frequency channel 2 when operating.

Optionally, in a first implementation manner, because the first uplink carrier and the second uplink carrier are sent in a time-sharing manner, when the terminal transmits data on a certain uplink carrier through one HARQ process, the uplink carrier may use the MIMO capability of the uplink carrier in the single carrier transmission mode.

For example, in the example of fig. 7B, the first uplink carrier and the second uplink carrier are sent in a time-sharing manner, and when a terminal transmits data through one HARQ process on a certain uplink carrier, the terminal may occupy 2 radio frequency channels, that is, radio frequency channel 1 and radio frequency channel 2.

And in the second scenario, the first uplink carrier and the second uplink carrier support multi-carrier concurrence. For example, the first uplink carrier and the second uplink carrier support CA. Or, in a DC scenario, the first uplink carrier is a master cell group uplink carrier, and the second uplink carrier is a secondary cell group uplink carrier.

The first uplink carrier and the second uplink carrier are sent in a concurrent manner, which may be understood that at the same time, the first uplink carrier and the second uplink carrier may send simultaneously or have the capability of sending simultaneously, or an uplink time domain resource of the first uplink carrier and an uplink time domain resource of the second uplink carrier may overlap.

Optionally, in a second implementation manner, since the first uplink carrier and the second uplink carrier are sent simultaneously, both the first uplink carrier and the second uplink carrier may use MIMO capability in a concurrent manner.

For example, in the schematic diagram of fig. 7B, the first uplink carrier and the second uplink carrier are sent simultaneously, the first uplink carrier may adopt a radio frequency channel 1, and the second uplink carrier may adopt a radio frequency channel 2. When a terminal transmits data through one HARQ process on a certain uplink carrier, the terminal may occupy 1 radio frequency channel.

Optionally, in a second implementation manner, data in one HARQ process may be sent in a time-sharing manner, but multiple HARQ processes may be sent concurrently, for example, at the same time, a data block is sent on a first uplink carrier through HARQ process 1, and another data block is sent on a second uplink carrier through HARQ process 2.

In a specific implementation, the second information may be capability information reported by the terminal, where the capability information is used to indicate whether the terminal supports the multi-carrier shared HARQ process, and the terminal may notify the access network device through the second information, and the terminal supports the multi-carrier shared HARQ process, that is, the terminal may transmit data through the same HARQ process on different uplink carriers.

It should be noted that 701 is an optional step. For example, the access network device and the terminal may default that the terminal supports the multi-carrier sharing HARQ process without being reported by the terminal through 701.

702. The access network equipment sends first information to the terminal, and the first information is used for enabling the first uplink carrier and the second uplink carrier to share the first HARQ process.

In a specific implementation, the access network device may determine that the terminal has the capability of the multi-carrier shared HARQ process according to the capability information (i.e., the second information in the embodiment of the present application) reported by the terminal in step 701. The access network device may notify the terminal of the capability of starting the multi-carrier shared HARQ process through the first information. For example, the access network device may send the first information to the terminal, and after receiving the first information, the terminal starts the capability of the multi-carrier shared HARQ process, so as to support the first uplink carrier and the second uplink carrier to share the first HARQ process.

In one possible implementation, the access network device may send the first information to the terminal through Radio Resource Control (RRC) signaling, a control element for radio access control (MAC CE), or Downlink Control Information (DCI). The first information may be 1bit information added in the sending RRC signaling, the MAC CE, or the DCI. The 1bit information is used to indicate whether the terminal turns on the capability of the multi-carrier shared HARQ process. For example, the first information is "0" and is used to indicate that the terminal does not start the capability of the multi-carrier shared HARQ process, and the terminal does not support the first uplink carrier and the second uplink carrier to share the first HARQ process; the first information is "1" and is used to indicate the capability of the terminal to start the multi-carrier shared HARQ process, and the terminal supports the first uplink carrier and the second uplink carrier to share the first HARQ process.

S702 is optional. For example, the access network device and the terminal may enable the multicarrier sharing HARQ process by default without the access network device issuing the enabled information via 702.

703. The terminal sends a first transmission block to the access network equipment through a first HARQ process on a first uplink carrier; and sending a second transport block to the access network equipment through the first HARQ process on the second uplink carrier.

As a result of using the first HARQ process, the second Transport Block (TB) is transmitted in a TDM manner with the first transport block. For example, the time domain resources for the first transport block and the time domain resources for the second transport block do not overlap, or the time domain resources for the first transport block and the time domain resources for the second transport block are different.

In a possible implementation manner, the first transport block is a newly transmitted data block; the second transport block is a retransmission data block of the first transport block.

In another possible implementation manner, the first transport block is a newly transmitted data block; the second transmission block is a newly transmitted data block.

Optionally, in the method shown in fig. 7A, the access network device may schedule uplink data through an UL Grant (uplink Grant), for example, the first transport block or the second transport block. The UL Grant includes an ID and an NDI of the HARQ process.

Specifically, the HARQ process ID in the UL Grant indicates through which HARQ process the uplink data currently scheduled by the terminal is transmitted. For example, it is assumed that the ID of the first HARQ process is "1", and the HARQ process ID in the UL Grant is "1", which is used to indicate that the transport block in the HARQ buffer of the first HARQ process is transmitted through the first HARQ process.

In addition, the NDI indicates whether the access network device is newly transmitted data or retransmitted data in the current UL Grant scheduling. Specifically, if the NDI is turned over for the last time, it is determined that the UL Grant scheduling is new transmission data, and the terminal sends the new transmission data in the HARQ buffer of the HARQ process through the HARQ process indicated by the UL Grant on the uplink carrier with the current transmission opportunity (e.g., the first transport block in the embodiment of the present application).

In a possible implementation manner, if the UL Grant of the access network device schedules retransmission data and one retransmission cannot complete transmission of all the retransmission data, the terminal may retransmit the data for multiple times. After the access network device fails to demodulate the initial transmission data of the terminal, the terminal retransmits the data for multiple times, and the access network device can combine the data retransmitted by the terminal for multiple times and then combine the data with the initial transmission data to obtain a combined decoding gain.

For example, the first transport block is initial transport data, and the second transport block is retransmission data corresponding to the first transport block. The second transmission block comprises N sub-transmission blocks, N is an integer greater than or equal to 1, and the N sub-transmission blocks are R_iAnd i is an integer from 0 to N-1.

The access network equipment schedules a sub-transmission block R through one-time UL Grant_iThe terminal slave access network equipment UL Grant, the UL Grant comprises a sub-transmission block R_iThe control information comprises the identifier ID of the first HARQ process, the NDI and the sub-transport block R_iThe NDI is not flipped.

The terminal judges that the NDI is not overturned before, determines that the UL Grant scheduling is retransmission data, and then transmits the retransmission data according to the sub-transmission block R_iObtaining the sub-transport block R in the HARQ buffer of the first HARQ process_iAnd on a second uplink carrier (namely the uplink carrier with the current transmission opportunity), the sub-transport block R is sent to the access network equipment by using a first HARQ process_i。

It should be noted that, in the embodiment of the present application, an uplink carrier currently having a transmission opportunity, that is, a current transmission resource, may be used for an uplink carrier for uplink transmission.

The method described in the embodiment of the present application is explained below with reference to fig. 8 by taking an example that the first uplink carrier is a 3.5G uplink carrier and the second uplink carrier is a 2.1G uplink carrier.

Referring to fig. 8, 16 HARQ processes may be shared by the 3.5G uplink carrier and the 2.1G uplink carrier, where each HARQ process may be used for performing uplink transmission in a TDM manner on the 3.5G uplink carrier and the 2.1G uplink carrier. Illustratively, the access network device schedules a TB1 in the 1 st time Slot (Slot0) of a 2.6G uplink carrier, and the UL grant for uplink scheduling indicates ID, NDI, Modulation and Coding Scheme (MCS) 1 of the HARQ process, and the number of RBs M₁And transport block size. Wherein, it is assumed that the ID of the HARQ process indicates HARQ process 0 (i.e. HARQ process with ID 0), the transport block size is used to indicate the size of TB1, and the number of RBs M₁For indicating the number of RBs used by transmission TB1,MCS1 is used to indicate the strategy of modulating, coding TB 1.

After the access network device receives the TB1, the data demodulation fails, and the access network device calculates that retransmission data can be scheduled at the 3 rd time Slot (Slot2) of the 2.1GHz uplink carrier at the earliest. Referring to fig. 8, it can be seen that the 2.1GHz uplink carrier has no resource for uplink transmission at Slot 2. The terminal cannot retransmit the data at Slot2 of the 2.1GHz uplink carrier. However, the Slot4 of the 3.5GHz uplink carrier has uplink transmission resources, and the access network device may send retransmission data corresponding to the TB1 at the Slot4 of the 3.5GHz uplink carrier.

Specifically, the access network device may send the UL grant at Slot3 of the 3.5GHz uplink carrier, schedule uplink data of Slot4 of the 3.5GHz uplink carrier, where the UL grant sent at Slot3 of the 3.5GHz uplink carrier includes an ID of an HARQ process, MCS2, and number of allocated RBs M₂Transport block size, and NDI. Wherein the transport block size is the same as the size of TB 1; NDI is not flipped (e.g., NDI is originally 0, NDI in UL grant is also 0); the ID of the HARQ process is 0.

And the terminal judges that the NDI is not overturned, and determines that the Slot4 of the 3.5GHz uplink carrier retransmits data through the HARQ process 0. The terminal may obtain TB2 (i.e., retransmission data of TB 1) in the HARQ buffer of HARQ process 0, and send TB2 in Slot4 of the 3.5GHz uplink carrier through HARQ process 0. Specifically, the coded TB2 is modulated with MCS2 and is recorded at M₂TB2 is sent on one RB.

After receiving the TB2 sent on the Slot4 of the 3.5GHz uplink carrier, the access network equipment combines the TB1 and the TB2 to obtain a combined decoding gain.

It should be noted that, if the RB resource on Slot4 of the 3.5GHz uplink carrier is too small to finish sending TB2 at one time, TB2 may be sent multiple times, and the terminal sends one sub-transport block at one time, and each sending needs to be individually scheduled by the access network device through the UL grant. After receiving all the sub-transport blocks, the access network combines all the sub-transport blocks, and then combines and decodes the combined sub-transport blocks with TB 1.

In addition, the terminal subsequently transmits the sub-transport blocks on the uplink carriers with transmission opportunities. For example, the sub-transport block may be sent at a transmission opportunity of a 3.5GHz uplink carrier, or the sub-transport block may be sent at a transmission opportunity of a 2.6GHz uplink carrier.

In a possible implementation manner, the second information in 701 may further include carrier combination information. The carrier combination information is used for indicating the carrier combination supported by the terminal and used for HARQ process sharing. For example, the carrier combination information is 2.1GHz and 3.5GHz, and is used to indicate that the terminal supports the sharing of the same HARQ process by the 2.1GHz uplink carrier and the 3.5GHz uplink carrier.

Table 1 shows an example of different frequency divisions. As shown in table 1, in the 5G NR system, frequency bands are divided, and different frequency bands support different duplex modes. For FDD duplexing, the uplink and downlink carriers are transmitted on different frequency bands, respectively, while for TDD duplexing, the uplink and downlink carriers share the same spectrum resources and are transmitted by using different times. The 5G NR system also defines the SUL carrier frequency bands, which are used for uplink transmission, and frequency band decoupling, which supports uplink and downlink use.

TABLE 1

NR frequency band identification	Uplink carrier frequency band	Downlink carrier frequency band	Duplex mode
				n1	1920MHz–1980MHz	2110MHz–2170MHz	FDD
n2	1850MHz–1910MHz	1930MHz–1990MHz	FDD
				n3	1710MHz–1785MHz	1805MHz–1880MHz	FDD
n5	824MHz–849MHz	869MHz–894MHz	FDD
				n7	2500MHz–2570MHz	2620MHz–2690MHz	FDD
n38	2570MHz–2620MHz	2570MHz–2620MHz	TDD
				n77	3300MHz–4200MHz	3300MHz–4200MHz	TDD
n78	3300MHz–3800MHz	3300MHz–3800MHz	TDD
				n79	4400MHz–5000MHz	4400MHz–5000MHz	TDD
n80	1710MHz–1785MHz	N/A	SUL
				n84	1920MHz–1980MHz	N/A	SUL
n86	1710MHz–1780MHz	N/A	SUL

Specifically, the carrier combination information may include two frequency band identifiers shown in table 1, which are used to indicate two uplink carriers that are supported by the terminal and are transmitted in a TDM manner, and the two uplink carriers indicated by the two frequency band identifiers may share the same HARQ process. For example, the carrier combination information indicates the frequency band identifier indicators n3 and n7, that is, the 1710 MHz-1785 MHz uplink carrier and the 2500 MHz-2570 MHz uplink carrier support TDM transmission, and the 1710 MHz-1785 MHz uplink carrier and the 2500 MHz-2570 MHz uplink carrier may share the same HARQ process.

Fig. 7A is introduced by taking two uplink carriers as an example, and it should be noted that the above is also applicable to a plurality of carriers (e.g. 3, 4 or more) sharing the same HARQ process, and in the same HARQ process, transport blocks of the plurality of carriers are transmitted in a TDM manner.

In a CA scenario, the terminal may report a frequency band combination supporting CA to the access network device according to table 1. The terminal may receive downlink signals from multiple downlink carriers or may transmit uplink signals on multiple uplink carriers simultaneously. In the uplink CA scenario, the MIMO capability and maximum transmit power of each aggregated CC (carrier) are reduced compared to that in single carrier transmission mode. Taking the aggregation of the n 773.5 GHz uplink carrier and the n 31.8 GHz uplink carrier as an example, the terminal needs to have the capability of sending uplink data at the 3.5GHz uplink carrier and the 1.8GHz uplink carrier simultaneously, and has large power consumption and short standby time. Secondly, 3.5GHz uplink carriers and 1.8GHz uplink carriers can only be transmitted by using 1 antenna, the maximum transmitting power is also reduced to 23dBm from 26dBm of the original single carrier, the performance on each carrier is reduced relative to the single carrier transmission mode, and the overall performance improvement of uplink communication is not obvious. In addition, the uplink carrier concurrency has a high requirement on the complexity of the terminal, and many terminals do not support uplink CA.

The embodiment of the present application further provides a communication method, which does not require the capability of uplink CA, reduces the requirement on the complexity of the terminal, does not degrade the performance of a single carrier, can effectively utilize uplink wireless resources, and improves the performance of uplink communication. As shown in fig. 9, the method comprises the steps of:

901. and the terminal reports the capability information to the access network equipment, wherein the capability information is used for indicating the uplink carrier frequency band supported by the terminal.

In a possible implementation manner, the capability information may include identifications of all uplink carrier frequency bands supported by the terminal, for example, the terminal supports n3, n5, and n7 shown in table 1. The capability information may include n3, n5, and n7, indicating that the terminal supports 1710 MHz-1785 MHz uplink carriers, 824 MHz-849 MHz uplink carriers, and 2500 MHz-2570 MHz uplink carriers.

In another possible implementation manner, a specified field in the capability information indicates that the terminal supports a specified uplink carrier frequency band. For example, the terminal accesses the network on the 3.5GHz band, the freqbandlnformationnr field is reported in the capability information, the access network device is indicated through the freqbandlnformationnr field, and the terminal supports the carrier wave of the 3.5GHz band and the carrier wave of the 2.1GHz band.

Optionally, it should be noted that the capability information may also indicate other capability information of the terminal, such as: whether the terminal supports downlink CA, whether the terminal supports transceiving duplex, whether the terminal supports uplink CA and the time delay of switching between two carriers. Illustratively, the BandCombination field 1 in the capability information indicates that the terminal supports downlink CA for 3.5G downlink carriers and 2.1G downlink carriers; the simultaneoustxtxinterbandca in the CA-parameternr field in the capability information indicates that the terminal supports carrier transceiving duplexing on the 3.5G frequency band and the 2.1G frequency band, that is, the terminal can receive downlink data and can send uplink data at the same time. The BandCombination field 2 in the capability information is used to indicate that the terminal supports uplink CA of 3.5G downlink carriers and 2.1G downlink carriers.

The different positions of the BandCombination field 1 and the BandCombination field 2 in the capability information may be referred to as "BandCombination" fields, and the different positions of the "BandCombination" fields are used to indicate the capability of the terminal for uplink CA and the capability of the terminal for downlink CA, respectively.

Optionally, since the terminal does not have the capability of uplink CA, the capability information in 901 may indicate that the terminal does not support uplink CA.

In a first possible implementation manner, the capability information reported by the terminal indicates that the terminal supports multi-carrier TDM transmission. Optionally, the capability information may further indicate that the terminal supports a frequency band combination of the multi-carrier TDM transmission, for example, n3+ n5+ n 5.

In a second possible implementation manner, the capability information reported by the terminal may not indicate that the terminal supports multi-carrier TDM transmission.

902. The access network equipment selects a first uplink carrier and a second uplink carrier according to the capability information reported by the terminal; the first uplink carrier and the second uplink carrier are transmitted in a TDM manner.

In a specific implementation, the access network device determines, according to the capability information reported by the terminal, a plurality of uplink carriers supported by the terminal, and determines, among the plurality of carriers, two uplink carriers used by the terminal for TDM transmission, that is, a first uplink carrier and a second uplink carrier in an embodiment of the present application.

In a first possible implementation manner, the capability information reported by the terminal indicates that the terminal supports multi-carrier TDM transmission or the terminal supports frequency band combination of multi-carrier TDM transmission, and the access network device may determine two uplink carriers used for TDM transmission according to the capability information, that is, the first uplink carrier and the second uplink carrier described in this embodiment of the present application.

In a second possible implementation manner, the capability information reported by the terminal may not indicate that the terminal supports multi-carrier TDM transmission (or that the terminal supports frequency band combination of multi-carrier TDM transmission). The access network device may configure one or more of the uplink frequency bands supported by the terminal as TDM.

It should be noted that the first uplink carrier and the second uplink carrier may use the same duplexing mode, for example, the first uplink carrier and the second uplink carrier both use a TDD duplexing mode. The first uplink carrier and the second uplink carrier may also use different duplexing modes, for example, the first uplink carrier adopts an FDD duplexing mode, and the second uplink carrier adopts a TDD duplexing mode. The first carrier and the second carrier may use different subcarrier spacing (Numerology) or the same subcarrier pattern.

903. And the access network equipment sends the information of the first uplink carrier and the information of the second uplink carrier to the terminal.

In a specific implementation, the first uplink carrier may be a carrier currently accessed by the terminal, and the second uplink carrier is an uplink carrier that is determined by the access network device according to the capability information reported by the terminal and that can be transmitted in a TDM manner with the first uplink carrier.

The information of the first uplink carrier may be channel configuration information on a frequency band where the first uplink carrier is located and signal configuration information on a frequency band where the first uplink carrier is located. The channel configuration information on the frequency band where the first uplink carrier is located may be PUSCH information and PUCCH information, and the signal configuration information on the frequency band where the first uplink carrier is located may be SCS information and SRS information.

The information of the second uplink carrier may be channel configuration information on a frequency band where the second uplink carrier is located and signal configuration information on a frequency band where the second uplink carrier is located. The channel configuration information on the frequency band where the second uplink carrier is located may be PUSCH information and PUCCH information, and the signal configuration information on the frequency band where the second uplink carrier is located may be SCS information and SRS information.

In a possible implementation manner, the terminal accesses the cell of the first uplink carrier before step 801, where the access network device only needs to issue the information of the second uplink carrier to the terminal. For example, the terminal accesses a cell of a 3.5GHz uplink carrier, and determines that the terminal supports time-division transmission of the 3.5GHz uplink carrier and the 2.1GHz uplink carrier according to the capability information reported by the terminal, and configures information of the 2.1GHz uplink carrier, such as SCS information, PUSCH information, SRS information, and PUCCH information on a 2.1G frequency band, for the terminal in an RRC reconfiguration message.

Taking the example that the terminal supports 3.5GHz uplink carrier and 2.1GHz uplink carrier, the terminal does not support uplink CA. The access network equipment allocates a first uplink carrier for the terminal to be a 3.5GHz uplink carrier and a second uplink carrier to be a 2.1GHz uplink carrier according to the reporting capacity of the terminal, and schedules uplink data on the 3.5GHz uplink carrier and the 2.1GHz uplink carrier respectively in a time division manner, so that uplink concurrence is avoided, and the implementation complexity of the terminal is reduced. As the 3.5GHz frequency band is a TDD system, no data is transmitted in the uplink on TDD downlink time slot resources. After configuring a 2.1GHz uplink carrier for the terminal, the terminal can adopt the 2.1G uplink carrier to send uplink data on a 3.5GHz TDD downlink time slot, and does not schedule the uplink data on a 2.1GHz frequency band on the 3.5GHz TDD uplink time slot, so that the terminal is ensured to send the data on only one uplink carrier all the time. In addition, the frequency bands of the carriers are different, and the coverage areas of the carriers are different. Generally, the lower the frequency band, the greater its coverage. Because the coverage area of the 2.1GHz uplink carrier is larger than that of the 3.5GHz uplink carrier, for the users at the edge of the cell, the uplink data is scheduled only on the 2.1GHz uplink carrier, and the uplink coverage area is improved.

The content of fig. 9 describes how to configure the first uplink carrier and the second uplink carrier, which is merely an example, and the first uplink carrier and the second uplink carrier may also be configured in other ways, and this is not limited in this embodiment of the present application. After configuring the first uplink carrier and the second uplink carrier, the first uplink carrier and the second uplink carrier may be activated or deactivated, which is described below with the second uplink carrier as an example. The following activated or deactivated content may be performed in conjunction with fig. 9 or separately from fig. 9.

In an optional implementation manner, after the access network device configures the second uplink carrier, the terminal may be notified to activate or deactivate the second uplink carrier through the MAC CE or DCI signaling.

Specifically, the access network device determines whether the second uplink carrier meets an activation condition, and the base station may notify the terminal of activation of the second uplink carrier through an MAC CE or DCI message when the activation condition is met. Similarly, the access network device determines that the second uplink carrier does not satisfy the activation condition, and may notify the terminal to deactivate the second uplink carrier through the MAC CE or the DCI message.

As an implementation manner, the activation condition may be that Reference Signal Receiving Power (RSRP) of a downlink Synchronization Signal Block (SSB) or a channel State information-reference signal (CSI-RS) measured on the second uplink carrier satisfies a certain threshold.

In another possible implementation manner, after the access network device configures the second uplink carrier, the second uplink carrier is in an activated state by default.

How to activate or deactivate the uplink carrier is introduced above. The following describes how the source access network device and the target access network device transfer the configuration information of the uplink carrier in the terminal moving process. The following may be performed separately from or in combination with one or more of the above schemes of configuring uplink carriers and (de) activating uplink carriers.

In an optional implementation manner, during the terminal moving process, the terminal may perform cell handover. The access network device may send the capability information of the terminal in s901 to the target access network device through an interface between the access network devices in a cell handover process of the terminal, and then the target access network configures an uplink carrier according to the capability information and sends uplink configuration information to the source access network device, and the source access network device sends the uplink configuration information to the terminal, for example, the target access network device configures information of a second uplink carrier to the terminal through a Handover (HO) signaling. Or after the terminal completes cell switching, the access network device configures the information of the second uplink carrier to the terminal through the RRC reconfiguration message.

The information of the second uplink carrier may include radio resource configuration information of the second uplink carrier.

Fig. 10 shows a schematic diagram of a possible structure of the communication device according to the above-described embodiment, in a case where each functional module is divided according to each function. The communication device shown in fig. 10 may be the terminal described in the embodiment of the present application, a component in the terminal for implementing the method described above, or a chip applied to the terminal. The Chip may be a System-On-a-Chip (SOC) or a baseband Chip with a communication function. As shown in fig. 10, the communication apparatus includes a processing unit 1001 and a communication unit 1002. The processing unit may be one or more processors and the communication unit may be a transceiver.

A processing unit 1001 for supporting terminal generation of "second information" and "capability information", and/or other processes for the techniques described herein.

A communication unit 1002, configured to support communication between the communication device and other communication devices, for example, to support the terminal to perform steps 701-702, 502, 901, and 903, and/or other processes for the technology described herein.

It should be noted that all relevant contents of each step related to the above method embodiment may be referred to the functional description of the corresponding functional module, and are not described herein again.

For example, in the case of using an integrated unit, a schematic structural diagram of a communication device provided in an embodiment of the present application is shown in fig. 11. In fig. 11, the communication apparatus includes: a processing module 1101 and a communication module 1102. The processing module 1101 is used for controlling and managing the actions of the communication device, for example, performing the steps performed by the processing unit 1001 described above, and/or other processes for performing the techniques described herein. The communication module 1102 is configured to perform the steps performed by the communication unit 1002, and support interaction between the communication apparatus and other devices, such as interaction with other terminal apparatuses. As shown in fig. 11, the communication device may further include a storage module 1103, and the storage module 1103 is used for storing program codes and data of the communication device.

When the processing module 1101 is a processor, the communication module 1102 is a transceiver, and the storage module 1103 is a memory, the communication device is the communication device shown in fig. 6A.

Fig. 12 shows a schematic diagram of a possible structure of the communication device according to the above embodiment, in the case of dividing each functional module according to each function. The communication device shown in fig. 12 may be an access network device described in this embodiment, or may be a component in the access network device that implements the foregoing method, or may be a chip applied to the access network device. The Chip may be a System-On-a-Chip (SOC) or a baseband Chip with a communication function. As shown in fig. 12, the communication apparatus includes a processing unit 1201 and a communication unit 1202. The processing unit 1201 may be one or more processors and the communication unit 1202 may be a transceiver.

Processing unit 1201 is configured to support access network device generation of "first information", and/or other processes for the techniques described herein.

A communication unit 1202, configured to support communication between the communication apparatus and other communication apparatuses, for example, to support an access network device to perform steps 701 to 702, 502, 901, and 903, and/or other processes for the technology described herein.

For example, in the case of using an integrated unit, a schematic structural diagram of a communication device provided in an embodiment of the present application is shown in fig. 13. In fig. 13, the communication apparatus includes: a processing module 1301 and a communication module 1302. Processing module 1301 is used to control and manage the actions of the communication apparatus, e.g., to perform the steps performed by processing unit 1201 described above, and/or other processes for performing the techniques described herein. The communication module 1302 is configured to perform the steps performed by the communication unit 1202, and support interaction between the communication apparatus and other devices, such as interaction with other access network device apparatuses. As shown in fig. 13, the communication device may further include a storage module 1303, and the storage module 1303 is used for storing program codes and data of the communication device.

When the processing module 1301 is a processor, the communication module 1302 is a transceiver, and the storage module 1303 is a memory, the communication device is the communication device shown in fig. 6B.

The embodiment of the application provides a computer-readable storage medium, wherein instructions are stored in the computer-readable storage medium; the instructions are for performing a method as shown in fig. 7A or fig. 9.

Embodiments of the present application provide a computer program product comprising instructions, which when run on a communication apparatus, cause the communication apparatus to perform a method as shown in fig. 7A or fig. 9.

An embodiment of the present application provides a wireless communication apparatus, including: instructions are stored in the wireless communication device; when the wireless communication apparatus operates on the communication apparatus shown in fig. 6A, 6B, 10 to 13, the communication apparatus is caused to perform the method as shown in fig. 7A or 9. The wireless communication device may be a chip.

An embodiment of the present application further provides a communication system, including: a terminal and an access network device. Illustratively, the terminal may be the communication apparatus shown in fig. 6A, 6B, and 10 to 13, and the access network device may be the communication apparatus shown in fig. 6A, 6B, and 10 to 13.

For example, the terminal may send the first transport block to the access network device through the first HARQ process on the first uplink carrier; a second transport block may be sent to the access network device through the first HARQ process on the second uplink carrier; and the second transmission block and the first transmission block are transmitted in a Time Division Multiplexing (TDM) mode.

Through the description of the above embodiments, it is clear to those skilled in the art that, for convenience and simplicity of description, the foregoing division of the functional modules is merely used as an example, and in practical applications, the above functions may be distributed by different functional modules according to needs, that is, the internal structure of the database access apparatus may be divided into different functional modules to complete all or part of the above described functions.

The processor in the embodiment of the present application may include, but is not limited to, at least one of the following: various computing devices that run software, such as a Central Processing Unit (CPU), a microprocessor, a Digital Signal Processor (DSP), a Microcontroller (MCU), or an artificial intelligence processor, may each include one or more cores for executing software instructions to perform operations or processing. The processor may be a single semiconductor chip or integrated with other circuits to form a semiconductor chip, for example, an SoC (system on chip) with other circuits (such as a codec circuit, a hardware acceleration circuit, or various buses and interface circuits), or may be integrated in the ASIC as a built-in processor of the ASIC, which may be packaged separately or together with other circuits. The processor may further include necessary hardware accelerators such as Field Programmable Gate Arrays (FPGAs), PLDs (programmable logic devices), or logic circuits implementing dedicated logic operations, in addition to cores for executing software instructions to perform operations or processes.

The memory in the embodiment of the present application may include at least one of the following types: read-only memory (ROM) or other types of static memory devices that may store static information and instructions, Random Access Memory (RAM) or other types of dynamic memory devices that may store information and instructions, and Electrically erasable programmable read-only memory (EEPROM). In some scenarios, the memory may also be, but is not limited to, a compact disk-read-only memory (CD-ROM) or other optical disk storage, optical disk storage (including compact disk, laser disk, optical disk, digital versatile disk, blu-ray disk, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer.

In the present application, "at least one" means one or more. "plurality" means two or more. "and/or" describes the association relationship of the associated objects, meaning that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone, wherein A and B can be singular or plural. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship. "at least one of the following" or similar expressions refer to any combination of these items, including any combination of the singular or plural items. For example, at least one (one) of a, b, or c, may represent: a, b, c, a-b, a-c, b-c, or a-b-c, wherein a, b, c may be single or multiple. In addition, in order to facilitate clear description of technical solutions of the embodiments of the present application, in the embodiments of the present application, terms such as "first" and "second" are used to distinguish the same items or similar items having substantially the same functions and actions. Those skilled in the art will appreciate that the terms "first," "second," etc. do not denote any order or quantity, nor do the terms "first," "second," etc. denote any order or importance.

In the several embodiments provided in the present application, it should be understood that the disclosed database access apparatus and method may be implemented in other ways. For example, the above-described database access device embodiments are merely illustrative, and for example, the division of the modules or units is only one logical division, and there may be other divisions when actually implemented, for example, multiple units or components may be combined or integrated into another device, or some features may be omitted, or not executed. In addition, the shown or discussed coupling or direct coupling or communication connection between each other may be an indirect coupling or communication connection through some interfaces, database access devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may be one physical unit or a plurality of physical units, that is, may be located in one place, or may be distributed in a plurality of different places. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a readable storage medium. Based on such understanding, the technical solutions of the embodiments of the present application may be essentially or partially contributed to by the prior art, or all or part of the technical solutions may be embodied in the form of a software product, where the software product is stored in a storage medium and includes several instructions to enable a device (which may be a single chip microcomputer, a chip, or the like) or a processor to execute all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a U disk, a removable hard disk, a ROM, a RAM, a magnetic disk, or an optical disk.

The above description is only an embodiment of the present application, but the scope of the present application is not limited thereto, and any changes or substitutions within the technical scope of the present disclosure should be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. An uplink automatic hybrid repeat request (HARQ) transmission method is characterized by comprising the following steps:

receiving and sending a first transport block from a terminal through a first HARQ process on a first uplink carrier;

receiving a second transport block from the terminal through the first HARQ process on a second uplink carrier;

performing merging decoding according to the first transport block and the second transport block;

the second transmission block and the first transmission block are transmitted in a Time Division Multiplexing (TDM) mode;

the second transmission block comprises N sub-transmission blocks, N is an integer greater than or equal to 1, and the N sub-transmission blocks are R_iAnd i is an integer taken from 0 to N-1, the method further comprising:

transmitting a sub-transport block R to the terminal_iControl information of, the sub transport block R_iIncludes the identification ID of the first HARQ process, the new data indication NDI and the sub-transport block R_iThe NDI is not flipped;

receiving the sub-transport block R sent by the terminal by using the first HARQ process on the second uplink carrier_i。

2. The method of claim 1, wherein the first uplink carrier and the second uplink carrier are uplink transmitted in a TDM manner.

3. The method according to claim 2, wherein the MIMO capability of the first uplink carrier in uplink transmission with the second uplink carrier in TDM manner is the same as the MIMO capability of the first uplink carrier in single carrier transmission mode; the MIMO capability of the second uplink carrier in TDM uplink transmission with the first uplink carrier is the same as the MIMO capability of the second uplink carrier in single carrier transmission.

4. The method according to any of claims 1-3, wherein the first uplink carrier is a primary cell uplink carrier and the second uplink carrier is a secondary cell uplink carrier; or, the first uplink carrier is a normal uplink NUL carrier, and the second uplink carrier is an auxiliary uplink SUL carrier; or, the first uplink carrier is a primary base station uplink carrier, and the second uplink carrier is a secondary base station uplink carrier.

5. The method according to any one of claims 1-3, further comprising:

and sending first information to the terminal, wherein the first information is used for enabling the first uplink carrier and the second uplink carrier to share the first HARQ process.

6. The method according to any one of claims 1-3, further comprising:

and sending second information to the terminal, wherein the second information is used for indicating that the terminal supports the first uplink carrier and the second uplink carrier to share the first HARQ process.

7. The method according to any of claims 1-3, wherein the first transport block is a new transport block; the second transport block is a retransmission data block of the first transport block.

8. A communication device configured to perform the method of any one of claims 1-7.

9. A communications apparatus comprising a processor coupled with a memory;

a memory for storing a computer program;

a processor for executing a computer program stored in the memory to cause the apparatus to perform the method of any of claims 1 to 7.

10. A computer-readable storage medium comprising instructions which, when executed on a computer, cause the computer to perform the method of any one of claims 1-7.