Patent Description:
In a long term evolution (Long Term Evolution, LTE) or <NUM> new radio (New RAT, NR) system, uplink/downlink data transmission is implemented by using the hybrid automatic repeat request (Hybrid Automatic Repeat Request, HARQ). As shown in <FIG>, a terminal or user equipment (User Equipment, UE) may have a plurality of medium access control (Medium Access Control, MAC) entities (for example, master cell group (Master Cell Group, MCG) MAC and secondary cell group (Secondary Cell Group, SCG) MAC), where each MAC entity has its separate HARQ entity (Entity). Each HARQ entity is configured to control data transmission and reception of one cell or frequency channel (for example, a component carrier CC <NUM> in <FIG>), that is, data transmission and retransmission of one CC are implemented by using a same HARQ entity. Each HARQ entity has a plurality of HARQ processes (process), and different data is transmitted or received by using different HARQ processes. A quantity of HARQ processes on each CC is determined by a HARQ round trip time (Round Trip Time, RTT) (which is a time from transmission of data to reception of feedback about the data; if the round trip time is <NUM> milliseconds, and transmission of each piece of data takes <NUM> millisecond, a quantity of HARQ processes is <NUM> in order that data can be transmitted at each time point). A data interface between a MAC entity and an upper-layer entity is a logical channel (Logical Channel, LCH), for example, an LCH <NUM> in <FIG>. Data on a plurality of logical channels may be transmitted as one MAC protocol data unit (Protocol Data Unit, PDU) in a HARQ process by using a multiplexing (multiplexing) function.

In a <NUM> (<NUM> Generation, 5th Generation) mobile communications system, to achieve a <NUM> Gbps downlink transmission rate and a <NUM> Gbps uplink transmission rate, high-frequency communications and massive antenna technologies are introduced. In high-frequency communication, a wider system bandwidth can be provided and an antenna size can be smaller, to facilitate deployment of massive antennas in base stations and UEs. Multi-beam (multi-beam) or multi-TRP transmission point (multiple transmission and reception points) data transmission and reception are applied on a base station side, and multi-beam or multi-TRP transmission point transmission and reception will be extensively applied on a UE side.

However, when different beams or transmission points are used for data transmission and reception for the UE, no method is yet available for determining what HARQ transmission mode is to be used.

D1 (<CIT>) discloses an apparatus configured to be employed within an Evolved NodeB (eNB), including: a processor configured to generate one or more downlink control information (DCI) messages, where each of the one or more DCI messages is associated with a distinct transmit beam of a multiple beam transmission to a user equipment (UE), where the multiple beam transmission includes Nb transmit beams, where Nb is at least <NUM>; assign each of the one or more DCI messages to an associated search space of one or more search spaces; and output the one or more DCI messages for subsequent transmission via transmitter circuitry during a common subframe, where the processor is configured to output each of the one or more DCI messages for subsequent transmission via a distinct transmit beam of the Nb transmit beams.

D2 (<CIT>) discloses an information transmission method. The method is applicable to a wireless communication system including a plurality of beams, and at least one hybrid automatic repeat request HARQ entity is configured in the wireless communication system, and each HARQ entity includes multiple HARQ processes. The method includes: the first communication device determines N beams required for information transmission between the second communication device, where N is greater than <NUM>; the first communication device and the second communication device perform information transmission through the HARQ processes corresponding to the N beams and the N beams, and at least two beams among the N beams share a HARQ process; if the N beams are used by the first communications device to transmit information to the second communications device, and the first communications device determines that information sent to the second communications device needs to be retransmitted, the communication device retransmits using at least one of the N beams.

An objective of this disclosure is to provide a data transmission method, a terminal, and a network device, to resolve a problem that no method is yet available for determining what HARQ transmission mode is to be used when different beams are used for data transmission and reception for UE.

According to a first aspect, an embodiment of this disclosure provides a data transmission method, which is defined in claim <NUM>.

According to a second aspect, an embodiment of this disclosure further provides a data transmission method, which is defined in claim <NUM>.

According to a third aspect, an embodiment of this disclosure further provides a network device, which is defined in claim <NUM>.

To describe the technical solutions in the embodiments of this disclosure more clearly, the following briefly describes the accompanying drawings required for describing the embodiments of this disclosure. Apparently, the accompanying drawings in the following description show merely some embodiments of this disclosure, and a person of ordinary skill in the art may still derive other drawings from these accompanying drawings.

The following describes exemplary embodiments of this disclosure in more detail with reference to the accompanying drawings. Although the exemplary embodiments of this disclosure are shown in the accompanying drawings, it should be understood that this disclosure may be implemented in various forms and should not be limited by the embodiments set forth herein. On the contrary, the embodiments are provided to enable a more thorough understanding of this disclosure and convey the scope of this disclosure to a person skilled in the art.

The terms "first", "second", and the like in this specification and claims of this application are used to distinguish between similar objects instead of describing a specific order or sequence. It should be understood that the numbers used in this way are interchangeable in appropriate circumstances so that the embodiments of this application described herein can be implemented in other orders than the order illustrated or described herein. In addition, the terms "include", "have", and any other variant thereof are intended to cover a non-exclusive inclusion. For example, a process, method, system, product, or device that includes a list of steps or units is not necessarily limited to those steps or units that are expressly listed, but may include other steps or units that are not expressly listed or are inherent to the process, method, system, product, or device. The term "and/or" in this specification and claims indicates at least one of connected objects.

Examples provided in the following description are not intended to limit the scope, applicability, or configuration described in the claims. Functions and arrangements of discussed elements may be changed without departing from the scope of this disclosure. Various procedures or components may be properly omitted, replaced, or added in various examples. For example, the described method may be performed in an order different from the described order, and steps may be added, omitted, or combined. In addition, features described with reference to some examples may be combined in other examples.

<FIG> is a structural diagram of a network system to which an embodiment of this disclosure may be applied. As shown in <FIG>, the network system includes a user terminal <NUM> and a base station <NUM>. The user terminal <NUM> may be user equipment (User Equipment, UE), for example, may be a terminal device such as a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer), a personal digital assistant (personal digital assistant, PDA for short), a mobile Internet device (Mobile Internet Device, MID), or a wearable device (Wearable Device). It should be noted that a specific type of the user terminal <NUM> is not limited in the embodiments of this disclosure. The base station <NUM> may be a base station (for example, a gNB or a <NUM> NR NB) in <NUM> or a later release, or a base station in another communications system, or is referred to as a NodeB, an evolved NodeB, a transmission and reception point (transmitting receiving point, TRP), or another term in the field. As long as a same technical effect is achieved, the base station is not limited to a specific technical term. It should be noted that only a <NUM> base station is used as an example in the embodiments of this disclosure, but a specific type of the base station <NUM> is not limited.

<FIG> is a schematic flowchart of a data transmission method according to an embodiment of this disclosure. As shown in <FIG>, an embodiment of this disclosure provides a data transmission method, applied to a terminal and including the following steps.

Step <NUM>: obtain hybrid automatic repeat request HARQ entities and medium access control MAC entities corresponding to a plurality of transmission carriers, where the transmission carriers are beams.

In this embodiment of this disclosure, different transmission carriers may correspond to a same MAC entity and correspond to different HARQ entities. In this case, the HARQ entities may be used to distinguish between different transmission carriers. Alternatively, different transmission carriers may correspond to a same MAC entity and correspond to a same HARQ entity. In this case, HARQ process IDs may be used to distinguish between data of different transmission carriers. Further, different transmission carriers may correspond to different MAC entities and different HARQ entities. In this case, identifier information of the MAC entities may be used to distinguish between data of different transmission carriers.

In addition, in this embodiment of this disclosure, the hybrid automatic repeat request HARQ entities and medium access control MAC entities corresponding to the plurality of transmission carriers are obtained by the terminal or a network device based on mapping relationship information between hybrid automatic repeat request HARQ and transmission carriers.

The mapping relationship information between hybrid automatic repeat request HARQ and transmission carriers includes: information about a transmission carrier; and HARQ configuration information corresponding to the information about the transmission carrier.

The information about the transmission carrier includes at least one of a transmission carrier identifier, a cell identifier corresponding to the transmission carrier, a frequency identifier corresponding to the transmission carrier, a bandwidth part (Bandwidth Part, BWP) identifier corresponding to the transmission carrier, a control channel identifier corresponding to the transmission carrier, and a MAC entity identifier corresponding to the transmission carrier.

Step <NUM>: perform data transmission between the transmission carriers and the HARQ entities and MAC entities corresponding to the transmission carriers.

Specifically, step <NUM> includes: in a case of downlink data reception, transmitting data received by each transmission carrier to a MAC entity and a HARQ entity corresponding to the transmission carrier, for processing; and/or
in a case of uplink data transmission, transmitting data to be transmitted to each transmission carrier, to a MAC entity and a HARQ entity corresponding to the transmission carrier, for processing.

The transmitting data received by each transmission carrier to a MAC entity and a HARQ entity corresponding to the transmission carrier, for processing in a case of downlink data reception includes:
in the case of downlink data reception, obtaining information about a first target transmission carrier; and determining the first target transmission carrier based on the information about the first target transmission carrier, and transmitting data received by the first target transmission carrier to a MAC entity and a HARQ entity corresponding to the first target transmission carrier, for processing.

Herein, the first target transmission carrier is any transmission carrier that performs downlink data reception, in the plurality of transmission carriers. The data received by the first target transmission carrier is identified by using the information about the first target transmission carrier. Further, the first target transmission carrier is identified based on the information about the first target transmission carrier, and the data is transmitted based on the foregoing mapping relationship information to the corresponding MAC entity and HARQ entity for processing.

For example, UE obtains information about a first target transmission carrier based on downlink data in downlink resource allocation information of downlink control information (Downlink Control Information, DCI) on a physical downlink control channel (Physical Downlink Control Channel, PDCCH), and transmits data to a MAC entity and a HARQ entity corresponding to the first target transmission carrier, for processing; or UE obtains information about a first target transmission carrier based on downlink data in a reference signal (for example, a synchronization signal block (Synchronization Signal Block, SSB) and/or channel state information reference signal (Channel State Information Reference Signal, CSI-RS)) information on a physical downlink shared channel (Physical Downlink Shared Channel, PDSCH), and transmits data to a MAC entity and a HARQ entity corresponding to the first target transmission carrier, for processing.

The transmitting data to be transmitted to each transmission carrier, to a MAC entity and a HARQ entity corresponding to the transmission carrier, for processing in a case of uplink data transmission includes:
in the case of uplink data transmission, obtaining information about a second target transmission carrier; and determining the second target transmission carrier based on the information about the second target transmission carrier, and transmitting data to be transmitted to the second target transmission carrier, to a MAC entity and a HARQ entity corresponding to the second target transmission carrier, for processing.

When the terminal performs uplink data transmission, the information about the transmission carrier may be carried, so that the network device identifies the corresponding transmission carrier based on the information about the transmission carrier.

Herein, the second target transmission carrier is any transmission carrier that performs uplink data transmission, in the plurality of transmission carriers. The data to be transmitted by the second target transmission carrier is identified by using the information about the second target transmission carrier.

For example, the UE obtains information about a second target transmission carrier based on uplink data in uplink resource allocation information of the downlink control information DCI on the physical downlink control channel PDCCH, and transmits data to a MAC entity and a HARQ entity corresponding to the second target transmission carrier, for processing; or the UE obtains information about a second target transmission carrier based on uplink data in reference signal information on the physical downlink shared channel PDSCH, and transmits data to a MAC entity and a HARQ entity corresponding to the second target transmission carrier, for processing.

In the data transmission method in this embodiment of this disclosure, the hybrid automatic repeat request HARQ entities and medium access control MAC entities corresponding to the plurality of transmission carriers are obtained, where the transmission carriers are beams; in the case of downlink data reception, the data received by each transmission carrier is transmitted to the MAC entity and HARQ entity corresponding to the transmission carrier, for processing; and in the case of uplink data transmission, the data to be transmitted to each transmission carrier is transmitted to the MAC entity and HARQ entity corresponding to the transmission carrier, for processing. In this way, the terminal implements data transmission and reception by using a plurality of different transmission carriers and using different HARQ processes, a scheduling delay caused by insufficiency of HARQ processes is avoided, and reliability of data transmission is improved by supporting HARQ transmission of different transmission carriers.

Further, the obtaining hybrid automatic repeat request HARQ entities and medium access control MAC entities corresponding to a plurality of transmission carriers in step <NUM> includes:.

Specifically, the network device configures the HARQ entities and MAC entities for the plurality of transmission carriers based on the mapping relationship information between hybrid automatic repeat request HARQ and transmission carriers.

The mapping relationship information between HARQ and transmission carriers includes:.

For example, the cell identifier corresponding to the transmission carrier may be specifically a cell <NUM>, the frequency identifier corresponding to the transmission carrier may be specifically a frequency <NUM>, the bandwidth part BWP identifier corresponding to the transmission carrier may be specifically a BWP_1, and the MAC entity identifier corresponding to the transmission carrier may be specifically MAC_1.

The transmission carrier identifier includes at least one of a synchronization signal block SSB identifier, a channel state information reference signal CSI-RS identifier, and a port number identifier corresponding to a reference signal, and the reference signal includes an SSB and/or a CSI-RS.

The transmission carrier identifier may also be another signal identifier, in addition to the SSB identifier and/or the CSI-RS identifier. This is not specifically limited herein.

The port number identifier corresponding to the reference signal may be specifically a port_1, and the reference signal may also be another reference signal, in addition to the SSB and the CSI-RS. This is not specifically limited herein.

The control channel identifier corresponding to the transmission carrier includes at least one of a control channel type identifier, a resource position identifier of a control channel, a reference signal identifier of a control channel, and a port number identifier corresponding to a reference signal of a control channel.

The control channel type identifier may be specifically a PDCCH_1 of a primary cell PCell; the resource position identifier of the control channel may be a control resource set (CORESET) and/or a search space (search space) identifier; and the reference signal identifier of the control channel may be an SSB identifier and/or a CSI-RS identifier.

In a first optional implementation, the configuring the corresponding HARQ entities and MAC entities for the plurality of transmission carriers includes:
configuring different HARQ entities for different transmission carriers.

Optionally, the different HARQ entities configured above belong to a same MAC entity.

In this implementation, the HARQ configuration information corresponding to the information about the transmission carrier includes a quantity of HARQ processes, for example, a quantity of HARQ processes corresponding to uplink data transmission and/or downlink data reception.

As shown in <FIG>, a transmission carrier <NUM> of a component carrier <NUM> (TRP <NUM> of CC <NUM>) and a transmission carrier <NUM> of the component carrier <NUM> (TRP <NUM> of CC <NUM>) correspond to a same MAC entity (MCG MAC) and correspond to different HARQ entities.

In a second optional implementation,
the configuring the corresponding HARQ entities and MAC entities for the plurality of transmission carriers includes:
configuring a same HARQ entity for the plurality of transmission carriers, and configuring different HARQ process IDs for different transmission carriers.

In this implementation, the HARQ configuration information corresponding to the information about the transmission carrier includes at least one of an identifier of a HARQ entity corresponding to the transmission carrier, a HARQ process ID available to the transmission carrier, a total quantity of available HARQ processes of a HARQ entity corresponding to the transmission carrier, and a quantity of HARQ processes available to the transmission carrier.

Optionally, the HARQ configuration information corresponding to the information about the transmission carrier includes at least one of first information and second information, where the first information includes the HARQ process ID available to the transmission carrier; and the second information includes the total quantity of available HARQ processes of the HARQ entity corresponding to the transmission carrier and the quantity of HARQ processes available to the transmission carrier.

For example, HARQ process IDs available to the transmission carriers are: HARQ process IDs [<NUM>, <NUM>] available to a beam <NUM>; and HARQ process IDs [<NUM>, <NUM>] available to a beam <NUM>. Alternatively, a bitmap is used to identify HARQ process IDs available to the beam or the transmission point; and the quantity of HARQ processes available to the transmission carrier is a quantity of HARQ processes corresponding to uplink data transmission and/or downlink data reception.

As shown in <FIG>, a transmission carrier <NUM> and a transmission carrier <NUM> of a component carrier <NUM> (TRP <NUM> + TRP <NUM> of CC <NUM>) correspond to a same MAC entity (MCG MAC) and correspond to a same HARQ entity; and a transmission carrier <NUM> and a transmission carrier <NUM> of a component carrier <NUM> (TRP <NUM> + TRP <NUM> of CC <NUM>) correspond to a same MAC entity (MCG MAC) and correspond to a same HARQ entity.

In a third optional implementation,
the configuring the corresponding HARQ entities and MAC entities for the plurality of transmission carriers includes:
configuring different HARQ entities for different transmission carriers, and configuring different MAC entities for different transmission carriers.

In this implementation, the mapping relationship information between hybrid automatic repeat request HARQ and transmission carriers further includes MAC configuration information corresponding to the transmission carrier, and the HARQ configuration information corresponding to the information about the transmission carrier includes a quantity of HARQ processes.

As shown in <FIG>, a transmission carrier <NUM> of a component carrier <NUM> (TRP <NUM> of CC <NUM>) corresponds to one MAC entity; and a transmission carrier <NUM> of the component carrier <NUM> (TRP <NUM> of CC <NUM>) corresponds to another MAC entity, and the transmission carrier <NUM> and transmission carrier <NUM> of the component carrier <NUM> correspond to different HARQ entities.

The MAC configuration information corresponding to the transmission carrier includes at least one of:.

Optionally, the MAC configuration information corresponding to the transmission carrier includes identifier information of a MAC entity.

In the data transmission method in this embodiment of this disclosure, the terminal can implement data transmission and reception by using a plurality of different transmission carriers and using different HARQ processes, a scheduling delay caused by insufficiency of HARQ processes is avoided, and reliability of data transmission is improved by supporting HARQ transmission of different transmission carriers.

As shown in <FIG>, an embodiment of this disclosure further provides a data transmission method, applied to a network device and including the following steps.

In addition, in this embodiment of this disclosure, the hybrid automatic repeat request HARQ entities and medium access control MAC entities corresponding to the plurality of transmission carriers are obtained by a terminal or the network device based on mapping relationship information between hybrid automatic repeat request HARQ and transmission carriers.

The information about the transmission carrier includes at least one of a transmission carrier identifier, a cell identifier corresponding to the transmission carrier, a frequency identifier corresponding to the transmission carrier, a bandwidth part BWP identifier corresponding to the transmission carrier, a control channel identifier corresponding to the transmission carrier, and a MAC entity identifier corresponding to the transmission carrier.

Step <NUM> specifically includes: in a case of downlink data transmission, transmitting data to be transmitted to each transmission carrier, to a MAC entity and a HARQ entity corresponding to the transmission carrier, for processing; and/or
in a case of uplink data reception, transmitting data received by each transmission carrier to a MAC entity and a HARQ entity corresponding to the transmission carrier, for processing.

The transmitting data to be transmitted to each transmission carrier, to a MAC entity and a HARQ entity corresponding to the transmission carrier, for processing in a case of downlink data transmission includes:
specifically, in the case of downlink data transmission, obtaining information about a third target transmission carrier; and determining the third target transmission carrier based on the information about the third target transmission carrier, and transmitting data to be transmitted to the third target transmission carrier, to a MAC entity and a HARQ entity corresponding to the third target transmission carrier, for processing.

Herein, the third target transmission carrier is any transmission carrier that performs downlink data transmission, in the plurality of transmission carriers. The data to be transmitted by the third target transmission carrier is identified by using the information about the third target transmission carrier.

When the network device performs downlink data transmission, the information about the transmission carrier may be carried, so that the terminal identifies the corresponding transmission carrier based on the information about the transmission carrier.

The transmitting data received by each transmission carrier to a MAC entity and a HARQ entity corresponding to the transmission carrier, for processing in a case of uplink data reception includes:
in the case of uplink data reception, obtaining information about a fourth target transmission carrier; and determining the fourth target transmission carrier based on the information about the fourth target transmission carrier, and transmitting data received by the fourth target transmission carrier to a MAC entity and a HARQ entity corresponding to the fourth target transmission carrier, for processing.

Herein, the fourth target transmission carrier is any transmission carrier that performs uplink data reception, in the plurality of transmission carriers. The data received by the fourth target transmission carrier is identified by using the information about the fourth target transmission carrier. Further, the fourth target transmission carrier is identified based on the information about the fourth target transmission carrier, and the data is transmitted based on the foregoing mapping relationship information to the corresponding MAC entity and HARQ entity for processing.

In the data transmission method in this embodiment of this disclosure, the hybrid automatic repeat request HARQ entities and medium access control MAC entities corresponding to the plurality of transmission carriers are obtained, where the transmission carriers are beams; in the case of downlink data transmission, the data to be transmitted to each transmission carrier is transmitted to the MAC entity and HARQ entity corresponding to the transmission carrier, for processing; and in the case of uplink data reception, the data received by each transmission carrier is transmitted to the MAC entity and HARQ entity corresponding to the transmission carrier, for processing. In this way, data transmission and reception are implemented by using a plurality of different transmission carriers and using different HARQ processes, a scheduling delay caused by insufficiency of HARQ processes is avoided, and reliability of data transmission is improved by supporting HARQ transmission of different transmission carriers.

Specifically, the terminal configures the HARQ entities and MAC entities for the plurality of transmission carriers based on the mapping relationship information between hybrid automatic repeat request HARQ and transmission carriers.

In this implementation, the HARQ configuration information corresponding to the information about the transmission carrier includes a quantity of HARQ processes, for example, a quantity of HARQ processes corresponding to uplink data reception and/or downlink data transmission.

In a third optional implementation, the configuring the corresponding HARQ entities and MAC entities for the plurality of transmission carriers includes:
configuring different HARQ entities for different transmission carriers, and configuring different MAC entities for different transmission carriers.

In the data transmission method in this embodiment of this disclosure, terminal can implement data transmission and reception by using a plurality of different transmission carriers and using different HARQ processes, a scheduling delay caused by insufficiency of HARQ processes is avoided, and reliability of data transmission is improved by supporting HARQ transmission of different transmission carriers.

<FIG> is a schematic modular diagram of a terminal according to an embodiment of this disclosure. As shown in <FIG>, an embodiment of this disclosure further provides a terminal <NUM>, including:.

In the terminal in this embodiment of this disclosure, the first transmission module is configured to: in a case of downlink data reception, transmit data received by each transmission carrier to a MAC entity and a HARQ entity corresponding to the transmission carrier, for processing; and/or
in a case of uplink data transmission, transmit data to be transmitted to each transmission carrier, to a MAC entity and a HARQ entity corresponding to the transmission carrier, for processing.

In the terminal in this embodiment of this disclosure, the first obtaining module is configured to: configure the corresponding HARQ entities and MAC entities for the plurality of transmission carriers based on mapping relationship information between hybrid automatic repeat request HARQ and transmission carriers, where the mapping relationship information is configured by a network device or prescribed by a protocol; or
obtain HARQ entities and MAC entities configured by a network device for the plurality of transmission carriers.

In the terminal in this embodiment of this disclosure, the mapping relationship information between hybrid automatic repeat request HARQ and transmission carriers includes: information about a transmission carrier; and.

In the terminal in this embodiment of this disclosure,
the first obtaining module is configured to configure different HARQ entities for different transmission carriers.

In the terminal in this embodiment of this disclosure, the HARQ configuration information corresponding to the information about the transmission carrier includes a quantity of HARQ processes.

In the terminal in this embodiment of this disclosure, the first obtaining module is configured to configure a same HARQ entity for the plurality of transmission carriers, and configure different HARQ process IDs for different transmission carriers.

In the terminal in this embodiment of this disclosure, the HARQ configuration information corresponding to the information about the transmission carrier includes at least one of an identifier of a HARQ entity corresponding to the transmission carrier, a HARQ process ID available to the transmission carrier, a total quantity of available HARQ processes of a HARQ entity corresponding to the transmission carrier, and a quantity of HARQ processes available to the transmission carrier.

In the terminal in this embodiment of this disclosure,
the first obtaining module is configured to configure different HARQ entities for different transmission carriers, and configure different MAC entities for different transmission carriers.

In the terminal in this embodiment of this disclosure, the mapping relationship information between hybrid automatic repeat request HARQ and transmission carriers further includes MAC configuration information corresponding to the transmission carrier, and the HARQ configuration information corresponding to the information about the transmission carrier includes a quantity of HARQ processes.

In the terminal in this embodiment of this disclosure, the MAC configuration information corresponding to the transmission carrier includes at least one of:.

In the terminal in this embodiment of this disclosure, the transmission carrier identifier includes at least one of a synchronization signal block SSB identifier, a channel state information reference signal CSI-RS identifier, and a port number identifier corresponding to a reference signal, and the reference signal includes an SSB and/or a CSI-RS.

In the terminal in this embodiment of this disclosure, the control channel identifier corresponding to the transmission carrier includes at least one of a control channel type identifier, a resource position identifier of a control channel, a reference signal identifier of a control channel, and a port number identifier corresponding to a reference signal of a control channel.

In the terminal in this embodiment of this disclosure, the first transmission module is configured to: in the case of downlink data reception, obtain information about a first target transmission carrier; and determine the first target transmission carrier based on the information about the first target transmission carrier, and transmit data received by the first target transmission carrier to a MAC entity and a HARQ entity corresponding to the first target transmission carrier, for processing; and/or
in the case of uplink data transmission, obtain information about a second target transmission carrier; and determine the second target transmission carrier based on the information about the second target transmission carrier, and transmit data to be transmitted to the second target transmission carrier, to a MAC entity and a HARQ entity corresponding to the second target transmission carrier, for processing.

An embodiment of this disclosure further provides a terminal, including a memory, a processor, and a computer program stored in the memory and capable of running on the processor. When the computer program is executed by the processor, each process of the foregoing data transmission method embodiment applied to the terminal is implemented, with the same technical effect achieved. To avoid repetition, details are not described again herein.

An embodiment of this disclosure further provides a computer-readable storage medium, where the computer-readable storage medium stores a computer program. When the computer program is executed by a processor, each process of the foregoing data transmission method embodiment applied to the terminal is implemented, with the same technical effect achieved. To avoid repetition, details are not described again herein. The computer-readable storage medium is, for example, a read-only memory (Read-Only Memory, ROM for short), a random access memory (Random Access Memory, RAM for short), a magnetic disk, or an optical disc.

To better achieve the foregoing objective, as shown in <FIG>, an embodiment of this disclosure further provides a terminal, including a memory <NUM>, a processor <NUM>, a transceiver <NUM>, a user interface <NUM>, a bus interface, and a computer program stored in the memory <NUM> and capable of running on the processor <NUM>, where the processor <NUM> is configured to read the program in the memory <NUM> to perform the following process:.

In <FIG>, a bus architecture may include any quantity of interconnect buses and bridges, specifically for interconnecting various circuits of one or more processors represented by the processor <NUM> and a memory represented by the memory <NUM>. The bus architecture may further interconnect various other circuits such as a peripheral device, a voltage regulator, and a power management circuit. These are all well known in the art, and therefore are not further described in this specification. The bus interface provides an interface. The transceiver <NUM> may be a plurality of components, that is, the transceiver <NUM> includes a transmitter and a receiver, and provides a unit for communicating with various other apparatuses on a transmission medium. For different user equipment, the user interface <NUM> may also be an interface for externally or internally connecting a required device, and the connected device includes but is not limited to a mini keyboard, a display, a speaker, a microphone, a joystick, or the like.

The processor <NUM> is responsible for bus architecture management and general processing. The memory <NUM> may store data used when the processor <NUM> performs an operation.

Optionally, by reading the program in the memory <NUM>, the processor <NUM> is further configured to perform the following:.

Optionally, the mapping relationship information between hybrid automatic repeat request HARQ and transmission carriers includes:.

Optionally, by reading the program in the memory <NUM>, the processor <NUM> is further configured to perform the following:
configuring different HARQ entities for different transmission carriers.

Optionally, the HARQ configuration information corresponding to the information about the transmission carrier includes a quantity of HARQ processes.

Optionally, by reading the program in the memory <NUM>, the processor <NUM> is further configured to perform the following:
configuring a same HARQ entity for the plurality of transmission carriers, and configuring different HARQ process IDs for different transmission carriers.

Optionally, the HARQ configuration information corresponding to the information about the transmission carrier includes at least one of an identifier of a HARQ entity corresponding to the transmission carrier, a HARQ process ID available to the transmission carrier, a total quantity of available HARQ processes of a HARQ entity corresponding to the transmission carrier, and a quantity of HARQ processes available to the transmission carrier.

Optionally, by reading the program in the memory <NUM>, the processor <NUM> is further configured to perform the following:
configuring different HARQ entities for different transmission carriers, and configuring different MAC entities for different transmission carriers.

Optionally, the mapping relationship information between hybrid automatic repeat request HARQ and transmission carriers further includes MAC configuration information corresponding to the transmission carrier, and the HARQ configuration information corresponding to the information about the transmission carrier includes a quantity of HARQ processes.

Optionally, the MAC configuration information corresponding to the transmission carrier includes at least one of:.

Optionally, the transmission carrier identifier includes at least one of a synchronization signal block SSB identifier, a channel state information reference signal CSI-RS identifier, and a port number identifier corresponding to a reference signal, and the reference signal includes an SSB and/or a CSI-RS.

Optionally, the control channel identifier corresponding to the transmission carrier includes at least one of a control channel type identifier, a resource position identifier of a control channel, a reference signal identifier of a control channel, and a port number identifier corresponding to a reference signal of a control channel.

<FIG> is a schematic diagram of a hardware structure of a terminal for implementing each embodiment of this disclosure. The terminal <NUM> includes but is not limited to components such as a radio frequency unit <NUM>, a network module <NUM>, an audio output unit <NUM>, an input unit <NUM>, a sensor <NUM>, a display unit <NUM>, a user input unit <NUM>, an interface unit <NUM>, a memory <NUM>, a processor <NUM>, and a power supply <NUM>. A person skilled in the art may understand that the structure of the terminal shown in <FIG> does not constitute a limitation on the terminal. A quantity of components included in the terminal may be greater or less than that shown in the figure, or some components are combined, or component arrangements are different. In this embodiment of this disclosure, the terminal includes but is not limited to a mobile phone, a tablet computer, a notebook computer, a palmtop computer, an in-vehicle terminal, a wearable device, a pedometer, or the like.

The processor <NUM> is configured to: obtain hybrid automatic repeat request HARQ entities and medium access control MAC entities corresponding to a plurality of transmission carriers, where the transmission carriers are beams; and
perform data transmission between the transmission carriers and the HARQ entities and MAC entities corresponding to the transmission carriers.

In the foregoing technical solution in this embodiment of this disclosure, the hybrid automatic repeat request HARQ entities and medium access control MAC entities corresponding to the plurality of transmission carriers are obtained, where the transmission carriers are beams; in the case of downlink data reception, the data received by each transmission carrier is transmitted to the MAC entity and HARQ entity corresponding to the transmission carrier, for processing; and in the case of uplink data transmission, the data to be transmitted to each transmission carrier is transmitted to the MAC entity and HARQ entity corresponding to the transmission carrier, for processing. In this way, the terminal implements data transmission and reception by using a plurality of different transmission carriers and using different HARQ processes, a scheduling delay caused by insufficiency of HARQ processes is avoided, and reliability of data transmission is improved by supporting HARQ transmission of different transmission carriers.

It should be understood that in this embodiment of this disclosure, the radio frequency unit <NUM> may be configured to receive and send signals in an information reception or transmission or call process. Specifically, after receiving downlink data from a network device, the radio frequency unit <NUM> sends the downlink data to the processor <NUM> for processing, and in addition, sends uplink data to the network device. Generally, the radio frequency unit <NUM> includes but is not limited to an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like. In addition, the radio frequency unit <NUM> may further communicate with a network and another device through a wireless communications system.

The terminal provides wireless broadband Internet access for a user by using the network module <NUM>, for example, helps the user send and receive e-mails, browse web pages, and access streaming media.

The audio output unit <NUM> may convert audio data received by the radio frequency unit <NUM> or the network module <NUM> or stored in the memory <NUM> into an audio signal, and output the audio signal as a sound. In addition, the audio output unit <NUM> may further provide an audio output (for example, a call signal reception sound or a message reception sound) related to a specific function performed by the terminal <NUM>. The audio output unit <NUM> includes a speaker, a buzzer, a telephone receiver, and the like.

The input unit <NUM> is configured to receive an audio or video signal. The input unit <NUM> may include a graphics processing unit (Graphics Processing Unit, GPU) <NUM> and a microphone <NUM>. The graphics processing unit <NUM> processes image data of a still picture or a video obtained by an image capture apparatus (for example, a camera) in an image capture mode or a video capture mode. A processed image frame may be displayed on the display unit <NUM>. An image frame processed by the graphics processing unit <NUM> may be stored in the memory <NUM> (or another storage medium) or sent by the radio frequency unit <NUM> or the network module <NUM>. The microphone <NUM> can receive a sound and can process the sound into audio data. The processed audio data may be converted in a telephone call mode into a format that can be sent to a mobile communications network device through the radio frequency unit <NUM>, for outputting.

The terminal <NUM> further includes at least one sensor <NUM>, for example, an optical sensor, a motion sensor, and another sensor. Specifically, the optical sensor includes an ambient light sensor and a proximity sensor. The ambient light sensor may adjust luminance of a display panel <NUM> based on brightness of ambient light. The proximity sensor may turn off the display panel <NUM> and/or backlight when the terminal <NUM> moves to an ear. As a type of motion sensor, an accelerometer sensor can detect magnitudes of acceleration in all directions (usually three axes), can detect a magnitude and a direction of gravity when the terminal is in a stationary state, and can be applied to terminal posture recognition (such as screen switching between portrait and landscape, related games, and magnetometer posture calibration), functions related to vibration recognition (such as pedometer and tapping), and the like. The sensor <NUM> may further include a fingerprint sensor, a pressure sensor, an iris sensor, a molecular sensor, a gyroscope, a barometer, a hygrometer, a thermometer, an infrared sensor, and the like.

The user input unit <NUM> may be configured to receive input digit or character information, and generate a key signal input related to a user setting and function control of the terminal. Specifically, the user input unit <NUM> includes a touch panel <NUM> and other input devices <NUM>. The touch panel <NUM>, also referred to as a touchscreen, may capture a touch operation performed by the user on or near the touch panel (for example, an operation performed by the user on the touch panel <NUM> or near the touch panel <NUM> by using any appropriate object or accessory such as a finger or a stylus). The touch panel <NUM> may include two parts: a touch detection apparatus and a touch controller. The touch detection apparatus detects a touch direction of the user, detects a signal carried by a touch operation, and transmits the signal to the touch controller. The touch controller receives touch information from the touch detection apparatus, converts the touch information into point coordinates, sends the point coordinates to the processor <NUM>, and receives and executes a command sent by the processor <NUM>. In addition, the touch panel <NUM> may be implemented in a plurality of forms, for example, a resistive, capacitive, infrared, or surface acoustic wave touch panel. The user input unit <NUM> may further include the other input devices <NUM> in addition to the touch panel <NUM>. Specifically, the other input devices <NUM> may include but are not limited to a physical keyboard, a function key (such as a volume control key or a power on/off key), a trackball, a mouse, a joystick, and the like.

Further, the touch panel <NUM> may cover the display panel <NUM>. After the touch panel <NUM> detects a touch operation on or near the touch panel, the touch panel <NUM> transmits the touch operation to the processor <NUM> to determine a type of a touch event. Then the processor <NUM> provides a corresponding visual output on the display panel <NUM> based on the type of the touch event. Although the touch panel <NUM> and the display panel <NUM> are used as two independent components to implement input and output functions of the terminal in <FIG>, the touch panel <NUM> and the display panel <NUM> may be integrated to implement the input and output functions of the terminal in some embodiments. This is not specifically limited herein.

The interface unit <NUM> is an interface for connecting an external apparatus to the terminal <NUM>. For example, the external apparatus may include a wired or wireless headphone port, an external power (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting an apparatus having an identification module, an audio input/output (Input/Output, I/O) port, a video I/O port, an earphone port, and the like. The interface unit <NUM> may be configured to receive an input (for example, data information or power) from an external apparatus, and transmit the received input to one or more components in the terminal <NUM>, or may be configured to transmit data between the terminal <NUM> and an external apparatus.

The memory <NUM> may be configured to store software programs and various data. The memory <NUM> may primarily include a program storage area and a data storage area. The program storage area may store an operating system, an application program required for at least one function (such as a sound play function and an image play function), and the like. The data storage area may store data created based on use of the mobile phone (such as audio data and a phone book), and the like. In addition, the memory <NUM> may include a high-speed random access memory, or may further include a non-volatile memory, for example, at least one magnetic disk storage device, a flash memory, or may include another volatile solid-state storage device.

The processor <NUM> is a control center of the terminal. The processor <NUM> uses various interfaces and lines to connect all parts of the entire terminal, and performs various functions and data processing of the terminal by running or executing the software program and/or module stored in the memory <NUM> and invoking data stored in the memory <NUM>, thereby performing overall monitoring on the terminal. The processor <NUM> may include one or more processing units. Optionally, the processor <NUM> may integrate an application processor and a modem processor. The application processor mainly processes the operating system, a user interface, an application program, and the like. The modem processor mainly processes wireless communication. It may be understood that the modem processor may alternatively not be integrated into the processor <NUM>.

The terminal <NUM> may further include the power supply <NUM> (for example, a battery) supplying power to all components. Optionally, the power supply <NUM> may be logically connected to the processor <NUM> through a power management system. In this way, functions such as charge management, discharge management, and power consumption management are implemented by using the power management system.

In addition, the terminal <NUM> includes some functional modules that are not illustrated.

As shown in <FIG>, an embodiment of this disclosure further provides a network device <NUM>, including:.

In the network device in this embodiment of this disclosure, the second obtaining module is configured to: configure the corresponding HARQ entities and MAC entities for the plurality of transmission carriers based on mapping relationship information between hybrid automatic repeat request HARQ and transmission carriers; or
obtain HARQ entities and MAC entities configured by a terminal for the plurality of transmission carriers.

In the network device in this embodiment of this disclosure, the mapping relationship information between hybrid automatic repeat request HARQ and transmission carriers includes: information about a transmission carrier; and.

In the network device in this embodiment of this disclosure, the second obtaining module is configured to configure different HARQ entities for different transmission carriers.

In the network device in this embodiment of this disclosure, the HARQ configuration information corresponding to the information about the transmission carrier includes a quantity of HARQ processes.

In the network device in this embodiment of this disclosure, the second obtaining module is configured to configure a same HARQ entity for the plurality of transmission carriers, and configure different HARQ process IDs for different transmission carriers.

In the network device in this embodiment of this disclosure, the HARQ configuration information corresponding to the information about the transmission carrier includes at least one of an identifier of a HARQ entity corresponding to the transmission carrier, a HARQ process ID available to the transmission carrier, a total quantity of available HARQ processes of a HARQ entity corresponding to the transmission carrier, and a quantity of HARQ processes available to the transmission carrier.

In the network device in this embodiment of this disclosure, the second obtaining module is configured to configure different HARQ entities for different transmission carriers, and configure different MAC entities for different transmission carriers.

The mapping relationship information between hybrid automatic repeat request HARQ and transmission carriers further includes MAC configuration information corresponding to the transmission carrier, and the HARQ configuration information corresponding to the information about the transmission carrier includes a quantity of HARQ processes.

In the network device in this embodiment of this disclosure, the MAC configuration information corresponding to the transmission carrier includes at least one of:.

In the network device in this embodiment of this disclosure, the transmission carrier identifier includes at least one of a synchronization signal block SSB identifier, a channel state information reference signal CSI-RS identifier, and a port number identifier corresponding to a reference signal, and the reference signal includes an SSB and/or a CSI-RS.

In the network device in this embodiment of this disclosure, the control channel identifier corresponding to the transmission carrier includes at least one of a control channel type identifier, a resource position identifier of a control channel, a reference signal identifier of a control channel, and a port number identifier corresponding to a reference signal of a control channel.

In the network device in this embodiment of this disclosure, the second transmission module is configured to: in a case of downlink data transmission, transmit data to be transmitted to each transmission carrier, to a MAC entity and a HARQ entity corresponding to the transmission carrier, for processing; and/or
in a case of uplink data reception, transmit data received by each transmission carrier to a MAC entity and a HARQ entity corresponding to the transmission carrier, for processing.

In the network device in this embodiment of this disclosure, the second transmission module is configured to: in the case of downlink data transmission, obtain information about a third target transmission carrier; and determine the third target transmission carrier based on the information about the third target transmission carrier, and transmit data to be transmitted to the third target transmission carrier, to a MAC entity and a HARQ entity corresponding to the third target transmission carrier, for processing; and/or
in the case of uplink data reception, obtain information about a fourth target transmission carrier; and determine the fourth target transmission carrier based on the information about the fourth target transmission carrier, and transmit data received by the fourth target transmission carrier to a MAC entity and a HARQ entity corresponding to the fourth target transmission carrier, for processing.

An embodiment of this disclosure further provides a network device, including a memory, a processor, and a computer program stored in the memory and capable of running on the processor. When the computer program is executed by the processor, each process of the foregoing data transmission method embodiment applied to the network device is implemented, with the same technical effect achieved. To avoid repetition, details are not described again herein.

An embodiment of this disclosure further provides a computer-readable storage medium, where the computer-readable storage medium stores a computer program. When the computer program is executed by a processor, each process of the foregoing data transmission method embodiment applied to the network device is implemented, with the same technical effect achieved. To avoid repetition, details are not described again herein. The computer-readable storage medium is, for example, a ROM, a RAM, a magnetic disk, or an optical disc.

As shown in <FIG>, an embodiment of this disclosure further provides a network device <NUM>, including a processor <NUM>, a transceiver <NUM>, a memory <NUM>, and a bus interface, where
the processor <NUM> is configured to read a program in the memory <NUM> to perform the following process:.

In <FIG>, a bus architecture may include any quantity of interconnect buses and bridges, specifically for interconnecting various circuits of one or more processors represented by the processor <NUM> and a memory represented by the memory <NUM>. The bus architecture may further interconnect various other circuits such as a peripheral device, a voltage regulator, and a power management circuit. These are all well known in the art, and therefore are not further described in this specification. The bus interface provides an interface. The transceiver <NUM> may be a plurality of components, that is, the transceiver <NUM> includes a transmitter and a receiver, and provides a unit for communicating with various other apparatuses on a transmission medium.

The HARQ configuration information corresponding to the information about the transmission carrier includes at least one of an identifier of a HARQ entity corresponding to the transmission carrier, a HARQ process ID available to the transmission carrier, a total quantity of available HARQ processes of a HARQ entity corresponding to the transmission carrier, and a quantity of HARQ processes available to the transmission carrier.

It should be noted that the terms "comprise", "include", or any of their variants in this specification are intended to cover a non-exclusive inclusion, so that a process, a method, an article, or an apparatus that includes a list of elements not only includes those elements but also includes other elements that are not expressly listed, or further includes elements inherent to such process, method, article, or apparatus. In absence of more constraints, an element preceded by "includes a. " does not preclude existence of other identical elements in the process, method, article, or apparatus that includes the element.

According to the description of the foregoing implementations, a person skilled in the art can clearly understand that the method in the foregoing embodiments may be implemented by software in addition to a necessary universal hardware platform or by hardware only. In most cases, the former is a preferred implementation. Based on such an understanding, the technical solutions of this disclosure essentially, or the part contributing to the related art may be implemented in a form of a software product. The computer software product is stored in a storage medium (for example, a ROM/RAM, a magnetic disk, or an optical disc), and includes several instructions for instructing a terminal (which may be a mobile phone, a computer, a server, an air conditioner, a network device, or the like) to perform the method described in the embodiments of this disclosure.

A person of ordinary skill in the art may be aware that the units and algorithm steps in the examples described with reference to the embodiments disclosed in this specification can be implemented by electronic hardware or a combination of computer software and electronic hardware. A person skilled in the art may use different methods to implement the described functions for each particular application, but it should not be considered that the implementation goes beyond the scope of this disclosure.

It may be clearly understood by a person skilled in the art that, for the purpose of convenient and brief description, for a detailed working process of the foregoing system, apparatus, and unit, reference may be made to a corresponding process in the foregoing method embodiments, and details are not described again herein.

In the embodiments provided in this disclosure, it should be understood that the disclosed apparatus and method may be implemented in other manners. For example, a plurality of units or components may be combined or integrated into another system, or some features may be ignored or may not be performed. The indirect couplings or communication connections between the apparatuses or units may be implemented in electrical, mechanical, or other forms.

When the functions are implemented in a form of a software functional unit and sold or used as an independent product, the functions may be stored in a computer-readable storage medium. Based on such an understanding, the technical solutions of this disclosure essentially, or the part contributing to the prior art, or some of the technical solutions may be implemented in a form of a software product. The software product is stored in a storage medium, and includes several instructions for instructing a computer device (which may be a personal computer, a server, a network device, or the like) to perform all or some of the steps of the method described in the embodiments of this disclosure. The foregoing storage medium includes: any medium that can store program code, such as a USB flash drive, a removable hard disk, a ROM, a RAM, a magnetic disk, or an optical disc.

It may be understood that the embodiments described in the embodiments of this disclosure may be implemented by hardware, software, firmware, middleware, microcode, or a combination thereof. For hardware implementation, the processing unit may be implemented in one or more application specific integrated circuits (Application Specific Integrated Circuit, ASIC), digital signal processors (Digital Signal Processing, DSP), digital signal processing devices (DSP Device, DSPD), programmable logic devices (Programmable Logic Device, PLD), field-programmable gate arrays (Field-Programmable Gate Array, FPGA), general purpose processors, controllers, microcontrollers, microprocessors, and other electronic units for performing the functions described in this disclosure, or a combination thereof.

For software implementation, the technologies described in the embodiments of this disclosure may be implemented by modules (for example, processes or functions) that perform the functions described in the embodiments of this disclosure. Software code may be stored in the memory and executed by the processor. The memory may be implemented in or outside the processor.

Claim 1:
A data transmission method, applied to a terminal (<NUM>), the method comprising:
obtaining (<NUM>) hybrid automatic repeat request, HARQ, entities and medium access control, MAC, entities corresponding to a plurality of transmission carriers, wherein the transmission carriers are beams; and
performing (<NUM>) data transmission between the transmission carriers and the HARQ entities and MAC entities corresponding to the transmission carriers; wherein
the HARQ entities and MAC entities corresponding to the plurality of transmission carriers are obtained based on mapping relationship information between HARQ and transmission carriers; a same HARQ entity is configured for the plurality of transmission carriers, and different HARQ process identifiers, IDs, are configured for different transmission carriers;
the mapping relationship information between HARQ and transmission carriers comprises information about a transmission carrier, and HARQ configuration information corresponding to the information about the transmission carrier;
the information about the transmission carrier comprises a cell identifier corresponding to the transmission carrier; and
the HARQ configuration information corresponding to the information about the transmission carrier comprises at least one of a HARQ process ID available to the transmission carrier, a total quantity of available HARQ processes of a HARQ entity corresponding to the transmission carrier, and a quantity of HARQ processes available to the transmission carrier.