Data transmission method and apparatus, and storage medium and electronic apparatus

Abstract

Provided in the embodiments of the present disclosure are a data transmission method and apparatus, and a storage medium and an electronic apparatus. The method comprises: by using data radio bearer (DRB) and hybrid automatic repeat request (HARQ)-entity mapping information, a first network element configuring the mapping between at least one group of DRB and HARQ entities, wherein the DRB and HARQ-entity mapping information indicates the mapping relationship between the at least one group of DRB and HARQ entities, and each group among the at least one group of DRB and HARQ entities comprises at least one DRB and at least one HARQ entity; and on the basis of the mapping relationship between the at least one group of DRB and HARQ entities, which mapping relationship is indicated by the DRB and HARQ-entity mapping information, the first network element submitting data, which is received by the HARQ entity included in each group, to an upper layer by means of the DRB to which the HARQ entity is mapped.

Description

Data transmission method, device, storage medium and electronic device

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] The present disclosure is based on Chinese patent application CN 202410011761.0 filed on January 2, 2024, entitled “Data Transmission Method, Device, Storage Medium and Electronic Device”, and claims the priority of the patent application, and all the disclosed contents thereof are incorporated into the present disclosure by reference. Technical Field

[0003] The embodiments of the present disclosure relate to the field of communications, and in particular, to a data transmission method, device, storage medium, and electronic device. Background Art

[0004] As wireless communication technology services become more and more diverse, the requirements for differentiated service performance assurance are also becoming higher and higher.

[0005] The data transmission methods used in related technologies do not adequately consider differences in service performance. Although data streams with different QoS (Quality of Service) requirements are differentiated by mapping them to different DRBs (Data Radio Bearers) at the SDAP (Service Data Adaptation Protocol) layer, data from different DRBs is multiplexed at the MAC (Medium Access Control) layer and then transmitted at the physical layer using HARQ (Hybrid Automatic Repeat reQuest). This data transmission mapping method is too rigid and makes it difficult to ensure differentiated transmission of different data at the physical layer.

[0006] Summary of the Invention

[0007] The embodiments of the present disclosure provide a data transmission method, device, storage medium, and electronic device to at least solve the problem in the related art that data transmission cannot be differentiated at the physical layer.

[0008] According to one embodiment of the present disclosure, a data transmission method is provided, including: a first network element uses data radio bearer DRB and hybrid automatic repeat request HARQ entity mapping information to configure the mapping between at least one group of DRBs and HARQ entities, wherein the DRB and HARQ entity mapping information indicates the mapping relationship between the DRBs and HARQ entities of the at least one group, and each group in the at least one group includes at least one DRB and at least one HARQ entity; the first network element delivers the data received by the HARQ entity included in each group to the upper layer through the DRB mapped to the HARQ entity according to the mapping relationship between the DRBs and HARQ entities of the at least one group indicated by the DRB and HARQ entity mapping information.

[0009] According to another embodiment of the present disclosure, a data transmission method is also provided, including: a second network element uses data radio bearer DRB and hybrid automatic repeat request HARQ entity mapping information to configure the mapping between at least one group of DRBs and HARQ entities, wherein the DRB and HARQ entity mapping information indicates the mapping relationship between the DRBs and HARQ entities of the at least one group, and each group in the at least one group includes at least one DRB and at least one HARQ entity; the second network element delivers the data stream to be sent through one of the DRBs to the HARQ entity in the group mapped with the DRB according to the mapping relationship between the DRBs and HARQ entities of the at least one group indicated by the DRB and HARQ entity mapping information.

[0010] According to another embodiment of the present disclosure, a data transmission method is also provided, including: a third network element uses data radio bearer DRB and hybrid automatic repeat request HARQ entity mapping information to configure the mapping between at least one group of DRBs and HARQ entities, wherein the DRB and HARQ entity mapping information indicates the mapping relationship between the DRBs and HARQ entities of the at least one group, and each group in the at least one group includes at least one DRB and at least one HARQ entity; the third network element sends the DRB and HARQ entity mapping information.

[0011] According to another embodiment of the present disclosure, a data transmission device is provided, which is applied to a first network element and includes: a first configuration module, configured to use data radio bearer DRB and hybrid automatic repeat request HARQ entity mapping information to configure the mapping between at least one group of DRBs and HARQ entities, wherein the DRB and HARQ entity mapping information indicates the mapping relationship between the DRBs and HARQ entities of the at least one group, and each group in the at least one group includes at least one DRB and at least one HARQ entity; a first sending module, configured to deliver the data received by the HARQ entity included in each group to an upper layer through the DRB mapped to the HARQ entity according to the mapping relationship between the DRBs and HARQ entities of at least one group indicated by the DRB and HARQ entity mapping information.

[0012] According to another embodiment of the present disclosure, a data transmission device is provided, which is applied to a second network element, including: a second configuration module, configured to use data radio bearer DRB and hybrid automatic repeat request HARQ entity mapping information to configure the mapping between at least one group of DRBs and HARQ entities, wherein the DRB and HARQ entity mapping information indicates the mapping relationship between the DRBs and HARQ entities of the at least one group, and each group in the at least one group includes at least one DRB and at least one HARQ entity; a second sending module, configured to hand over the data stream to be sent through one of the DRBs to the HARQ entity in the group mapped with the DRB according to the mapping relationship between the DRBs and HARQ entities of the at least one group indicated by the DRB and HARQ entity mapping information.

[0013] According to another embodiment of the present disclosure, a data transmission device is provided, which is applied to a third network element, including: a third configuration module, configured to use data radio bearer DRB and hybrid automatic repeat request HARQ entity mapping information to configure the mapping between at least one group of DRBs and HARQ entities, wherein the DRB and HARQ entity mapping information indicates the mapping relationship between the DRBs and HARQ entities of the at least one group, and each group in the at least one group includes at least one DRB and at least one HARQ entity; a third sending module, configured to send the DRB and HARQ entity mapping information.

[0014] According to another embodiment of the present disclosure, a computer-readable storage medium is provided, in which a computer program is stored. The computer program is configured to execute the steps of any one of the above method embodiments when running.

[0015] According to another embodiment of the present disclosure, an electronic device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to perform the steps in any one of the above method embodiments. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] FIG1 is a schematic diagram of a data flow transmission process at each layer in the related art;

[0017] FIG2 is a schematic diagram of the structure of a downlink configured with CA in the related art;

[0018] FIG3 is a schematic diagram of the structure of an uplink configured with CA in the related art;

[0019] FIG4 is a schematic diagram of a data mapping method in the related art;

[0020] FIG5 is a hardware structure block diagram of a mobile terminal according to a data transmission method according to an embodiment of the present disclosure;

[0021] FIG6 is a flowchart of a data transmission method according to an embodiment of the present disclosure;

[0022] FIG7 is a schematic diagram of data mapping from one DRB to one HARQ entity according to an embodiment of the present disclosure;

[0023] FIG8 is a schematic diagram of transmission of a data packet when one DRB is mapped to one HARQ entity according to an embodiment of the present disclosure;

[0024] FIG9 is a schematic diagram of data mapping of multiple DRBs to one HARQ entity according to an embodiment of the present disclosure;

[0025] FIG10 is a schematic diagram of transmission of data packets when multiple DRBs are mapped to one HARQ entity according to an embodiment of the present disclosure;

[0026] FIG11 is a schematic diagram of data mapping from one DRB to multiple HARQ entities according to an embodiment of the present disclosure;

[0027] FIG12 is a schematic diagram of transmission of a data packet when one DRB is mapped to multiple HARQ entities according to an embodiment of the present disclosure;

[0028] FIG13 is a schematic diagram of mapping information between three groups of DRBs and HARQ entities according to an embodiment of the present disclosure;

[0029] FIG14 is a second flowchart of a data transmission method according to an embodiment of the present disclosure;

[0030] FIG15 is a third flowchart of a data transmission method according to an embodiment of the present disclosure;

[0031] FIG16 is a schematic diagram 1 of an RRC message transmission method according to an embodiment of the present disclosure;

[0032] FIG17 is a second schematic diagram of an RRC message transmission method according to an embodiment of the present disclosure;

[0033] FIG18 is a fourth flowchart of a data transmission method according to an embodiment of the present disclosure;

[0034] FIG19 is a fifth flowchart of a data transmission method according to an embodiment of the present disclosure;

[0035] FIG20 is a structural block diagram 1 of a data transmission device according to an embodiment of the present disclosure;

[0036] FIG21 is a second structural block diagram of a data transmission device according to an embodiment of the present disclosure;

[0037] FIG22 is a third structural block diagram of the data transmission device according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0038] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings and in conjunction with embodiments.

[0039] It should be noted that the terms "first", "second", etc. in the specification and claims of the present disclosure and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence.

[0040] First, the related technologies involved in this disclosure are described:

[0041] With the advancement of wireless communication technology, services are becoming increasingly diverse. Currently, the three classic 5G scenarios exhibit distinct service characteristics. eMBB (Enhanced Mobile Broadband) services are characterized by high-speed data transmission with large data packets and high throughput. URLLC (Ultra-reliable and Low Latency Communications) services require low latency and high reliability. mMTC (Massive Machine Type Communication) services prioritize the low-cost and low-energy transmission of small data packets. In the future, multimodal services, such as immersive cloud XR (Extended Reality), multi-dimensional holography, autonomous driving, and the Industrial Internet, will emerge, integrating diverse service types and placing even higher demands on differentiated performance assurance.

[0042] RB (Radio Bearer) is a general term for a series of protocol entities and configurations allocated by the base station to the UE (User Equipment), including a series of resources for each protocol entity. The 5G access network uses DRB data mapping to provide service guarantee. DRB is the channel for the actual transmission of user data. From the perspective of the services provided by the lower layer to the upper layer: the physical layer provides services to the MAC sublayer through the transport channel; the MAC sublayer provides services to the RLC (Radio Link Control) sublayer through the logical channel; the RLC sublayer provides services to the PDCP (Packet Data Convergence Protocol) sublayer through the RLC channel; the PDCP sublayer provides services to the SDAP sublayer through the radio bearer RB, and the SDAP layer provides services to the upper layer through the QoS flow. From the perspective of data mapping from upper layers to lower layers: the SDAP layer is responsible for mapping QoS flows to data radio bearers (DRBs). QoS flows with different packet forwarding requirements are mapped to different DRBs to ensure service differentiation. The PDCP layer is responsible for sorting, header compression, encryption, and integrity protection of upper-layer data. The RLC layer segmented data and performed ARQ (Automatic Repeat Request) slow retransmission. A complete RLC SDU (Service Data Unit) may be split into multiple RLC PDU (Protocol Data Unit) segments, and the RLC layer can also perform resegmentation based on actual resource availability. The MAC layer multiplexes multiple MAC SDUs into a single MAC PDU as a physical layer transport block (TB), and uses the HARQ mechanism for fast retransmission of data packets. A HARQ entity manages multiple parallel HARQ processes, and data from different HARQ processes cannot be combined. A TB is the basic unit of HARQ transmission. Without spatial multiplexing, one HARQ process can transmit one TB. When spatial multiplexing is enabled, a single HARQ process can transmit up to two TBs. Figure 1 illustrates the data stream transmission processing at each layer in the related art. Figure 2 illustrates the structure of a downlink with CA (Carrier Aggregation) configured in the related art. Figure 3 illustrates the structure of an uplink with CA configured in the related art. As shown in Figure 1, after multiple layers of processing, the data of RBx and RBy in the radio bearer (RB) is multiplexed into a MAC PDU at the MAC layer and ultimately mapped to a TB.As radio bearer data moves from the PDCP and RLC layers to the MAC layer, a subheader corresponding to that layer is added to each layer. As shown in Figures 2 and 3, radio bearer data is first mapped to the RLC channel, then from the RLC channel to the logical channel, and then mapped to the HARQ entity through logical channel scheduling and multiplexing. 5G RAN (Radio Access Network) focuses more on service provision based on full resource utilization in data transmission processing, and does not give enough consideration to differences in service performance experience. Although data streams with different QoS requirements are differentiated by mapping them to different DRBs at the SDAP layer, data from different DRBs is multiplexed together at the MAC layer. After data is multiplexed at the MAC layer, the differences in services cannot be distinguished at the bottom layer. The data transmission mapping method of related technologies is too rigid, making it difficult to ensure service differentiation and performance improvement at the bottom layer, and it is difficult to meet the demand for flexible assurance of service performance differences.

[0043] In the 5G (NR) wireless network, DRB is used to carry user data transmission. Multiple DRBs can be established simultaneously between the user and the base station node, and each DRB provides the same forwarding processing for the user data packet. One or more QoS flows are mapped to one DRB. Since the wireless resources in the wireless communication network are limited, different DRB data are multiplexed at the MAC layer after being processed by the PDCP layer and the RLC layer, and the TB transmission on multiple HARQ processes is carried out through the HARQ entity. Figure 4 is a schematic diagram of the data mapping method in the related art. As shown in Figure 4, the DRB in 5G is mapped to the HARQ entity after being multiplexed through the MAC layer. Since the DRB and the HARQ entity cannot be directly mapped, the mapping relationship between the DRB and the HARQ entity will be unclear, and the network side cannot confirm whether the data transmitted on the same TB is from one service or multiple services.

[0044] In view of the above problems existing in the related art, corresponding solutions are proposed in the embodiments of the present disclosure. The present disclosure is described below with reference to the embodiments:

[0045] The method embodiments provided in the embodiments of the present application can be executed in a mobile terminal, a computer terminal or a similar computing device. Taking operation on a mobile terminal as an example, Figure 5 is a hardware structure block diagram of a mobile terminal of the data transmission method of the embodiment of the present disclosure. As shown in Figure 5, the mobile terminal may include one or more (only one is shown in Figure 5) processors 502 (the processor 502 may include but is not limited to a processing device such as a microprocessor MCU or a programmable logic device FPGA) and a memory 504 configured to store data, wherein the above-mentioned mobile terminal may also include a transmission device 506 and an input and output device 508 configured to have a communication function. It can be understood by those skilled in the art that the structure shown in Figure 5 is only for illustration and does not limit the structure of the above-mentioned mobile terminal. For example, the mobile terminal may also include more or fewer components than those shown in Figure 5, or have a configuration different from that shown in Figure 5.

[0046] The memory 504 can be configured to store computer programs, for example, software programs and modules of application software, such as the computer program corresponding to the data transmission method in the embodiment of the present disclosure. The processor 502 executes various functional applications and data processing by running the computer program stored in the memory 504, that is, implementing the above-mentioned method. The memory 504 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 504 may further include a memory remotely located relative to the processor 502, and these remote memories may be connected to the mobile terminal via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0047] The transmission device 506 is configured to receive or transmit data via a network. A specific example of the aforementioned network may include a wireless network provided by the mobile terminal's communications provider. In one embodiment, the transmission device 506 includes a network interface controller (NIC), which can be connected to other network devices via a base station to enable communication with the Internet. In one embodiment, the transmission device 506 may be a radio frequency (RF) module configured to communicate with the Internet wirelessly.

[0048] In the embodiments of the present disclosure, a network element may include one or more network nodes, one or more network functions, one or more network layers, one or more network devices, and / or one or more network entities. For example, a network element may be a RAN node, an RRC (Radio Resource Control) layer of the RAN, a MAC layer of the RAN, a MAC entity of the RAN, a Central Unit (CU), a Distributed Unit (DU), a UE, or an Integrated Access and Backhaul (IAB) Node. Optionally, the RAN node may include an access network device. In some embodiments, the access network device may include a 4G base station eNodeB, a 5G base station gNodeB, or a next-generation new base station (such as a 6G base station), or a wireless controller in a Cloud Radio Access Network (CRAN), or the access network device may include a relay station, an access point, a vehicle-mounted device, a wearable device, or a network device in a future evolved Public Land Mobile Network (PLMN). In an embodiment of the present disclosure, the DRB includes at least one of the following: a communication-related wireless bearer, a perception-related wireless bearer, an AI (Artificial Intelligence)-related wireless bearer, a data service-related wireless bearer, a computing-related wireless bearer, and a security / trust-related wireless bearer.

[0049] In this embodiment, a data transmission method is provided. FIG6 is a flowchart of the data transmission method according to an embodiment of the present disclosure. As shown in FIG6 , the flow includes the following steps:

[0050] Step S602: The first network element configures mapping between at least one group of DRBs and HARQ entities using data DRB-to-HARQ entity mapping information, wherein the DRB-to-HARQ entity mapping information indicates a mapping relationship between the at least one group of DRBs and HARQ entities, and each of the at least one group includes at least one DRB and at least one HARQ entity.

[0051] In step S604, the first network element delivers the data received by the HARQ entity included in each group to the upper layer through the DRB mapped to the HARQ entity according to the mapping relationship between at least one group of DRBs and HARQ entities indicated by the DRB and HARQ entity mapping information.

[0052] In the above steps, the first network element includes but is not limited to: RAN, UE, CU, DU, relay node or IAB node. The DRB and HARQ entity mapping information may include information on multiple groups of HARQ entity and DRB mappings. For example, the DRB and HARQ entity mapping information includes three groups of mapping information between DRBs and HARQ entities: Group 1 includes DRB 1 and HARQ entity 1, indicating that DRB 1 is mapped to HARQ entity 1; Group 2 includes DRB 2, DRB 3, and HARQ entity 2, indicating that DRB 2 and DRB 3 are mapped to HARQ entity 2; Group 3 includes DRB 4, HARQ entity 3, and HARQ entity 4, indicating that DRB 4 is mapped to HARQ entity 3 and HARQ entity 4. The first network element submits the data received by the HARQ entities included in each group to the upper layer through the DRB mapped to the HARQ entity based on the information of mapping multiple groups of HARQ entities to the DRB. For example, the data received on HARQ entity 1 is submitted to the upper layer through DRB1, the data received on HARQ entity 2 is submitted to the upper layer through DRB2 and DRB3, and the data received on HARQ entity 3 and HARQ entity 4 is submitted to the upper layer through DRB4.

[0053] Through the above steps, the mapping between DRB and HARQ entity will be configured based on the DRB and HARQ entity mapping information, so that the data that needs to be differentially transmitted can be transmitted separately at the physical layer and independently submitted to the upper layer at the receiving end, thereby ensuring the difference in service performance, effectively solving the problem that data transmission in related technologies cannot be differentiated at the physical layer, achieving the effect of improving the flexibility of physical layer data transmission, flexibly meeting the underlying transmission requirements of different services, and greatly improving the service transmission capability and service performance experience.

[0054] In an optional embodiment, the mapping relationship between the DRB of each group and the HARQ entity includes at least one of the following: the mapping relationship between one DRB and one HARQ entity; the mapping relationship between one DRB and multiple HARQ entities; the mapping relationship between multiple DRBs and one HARQ entity.

[0055] In an optional embodiment, the DRB and HARQ entity do not have a fixed coupling relationship. Instead, the connection is established through mapping information between the DRB and HARQ entity. The DRB and HARQ entity are generated independently and flexibly mapped via RRC messages or DCI messages. The mapping relationship between the DRB and HARQ entity can be flexibly changed when network transmission or service requirements change.

[0056] In an optional embodiment, the mapping relationship between a DRB and a HARQ entity indicates a one-to-one mapping between a DRB and a HARQ entity. Figure 7 is a schematic diagram of a DRB to a HARQ entity in data mapping according to an embodiment of the present disclosure. As shown in Figure 7, the data stream dataflow1 has an order preservation requirement, and the data stream dataflow2 has no order preservation requirement. The one-to-one mapping of DRBs and HARQ entities maps the data stream dataflow1 with an order preservation requirement to DRB1; and maps the data stream dataflow2 that does not require order preservation to DRB2. Since DRB1 and DRB2 are mapped one-to-one with HARQ entities 1 and 2 respectively, data stream 1 is transmitted on the HARQ process of HARQ entity 1, and data stream 2 is transmitted on the HARQ process of HARQ entity 2. There will be no situation where different data streams are mapped to the same HARQ entity, and there will be no situation where different data streams are mapped to the same TB of the same HARQ process. Since the DRB is directly mapped to the HARQ entity, the data of each DRB can be directly mapped to the TB of the HARQ process under the corresponding HARQ entity. Since data with different service requirements can be distinguished during physical layer transmission, different transmission optimization measures can be taken at the physical layer. For example, for data streams with order preservation requirements, the MCS level can be specifically lowered during physical layer scheduling, and the power can be increased during power control. This can ensure that the data can be transmitted correctly and delivered in sequence as quickly as possible in a short time. Figure 8 is an example of a transmission diagram of a data packet when a DRB is mapped to a HARQ entity according to an embodiment of the present disclosure. As shown in Figure 8, in the presence of SDAP, PDCP, RLC, and MAC sublayers, since the DRB can be directly mapped to the MAC layer data, in some cases it may not even be necessary to add a MAC subheader at the MAC layer. The service characteristics include, but are not limited to: data packet order preservation transmission service indication, data packet non-order preservation transmission service indication, high reliability transmission service indication, low reliability transmission service indication, low latency transmission service indication, no low latency transmission service indication, service type indication, service ID, and service name identification.

[0057] In an optional embodiment, the mapping relationship between multiple DRBs and a HARQ entity indicates the mapping of multiple DRBs to a HARQ entity. In a multimodal service scenario, there will be multiple parallel service transmissions between the base station and the UE, and there is an association or constraint relationship between these parallel services. For example, in a holographic communication scenario, video services, time-frequency services, tactile services, taste services and other services need to be coordinated and synchronized. Each service corresponds to a DRB, and multiple services use one HARQ entity to transmit, so that each service data can be received in a timely manner at the receiving end and cooperate to achieve a high-quality integrated service experience. When mapping data, different DRBs are mapped to the TB of the HARQ process under the same HARQ entity. Different DRBs can be distinguished by different HARQ processes or different TBs under the same HARQ process. For the case without spatial multiplexing, one HARQ process corresponds to one TB. Mapping different DRBs to different HARQ processes of the same HARQ entity makes the same TB correspond to the same service data, and different DRB data can be distinguished by the HARQ process ID. When there is spatial multiplexing, one HARQ process can transmit 2 TBs through spatial multiplexing. When there is spatial multiplexing, different DRBs can be mapped only to different HARQ processes, so that the 2 TBs spatially multiplexed under one HARQ process correspond to the data of the same DRB, and different DRB data can be distinguished only by the HARQ process ID. When there is spatial multiplexing, different DRBs can also be mapped to different TBs under one HARQ process, so that the 2 TBs spatially multiplexed under one HARQ process correspond to the data of different DRBs, and different DRB data can be distinguished by the HARQ process ID and the TB ID. Since data with different business requirements can be distinguished in physical layer transmission, different transmission measures can be taken at the physical layer to ensure business differences. Figure 9 is a schematic diagram of multiple DRBs in data mapping to one HARQ entity according to an embodiment of the present disclosure. Figure 10 is a schematic diagram of the transmission of data packets when multiple DRBs are mapped to one HARQ entity according to an embodiment of the present disclosure. As shown in Figure 10, in the presence of SDAP, PDCP, RLC, and MAC sublayers, since DRBs can be directly mapped to MAC layer data, in some cases there is no need to add a MAC subheader at the MAC layer.

[0058] In an optional embodiment, the mapping relationship between a DRB and multiple HARQ entities indicates the mapping of a DRB to multiple HARQ entities. In the related art, even if a HARQ entity has multiple parallel HARQ processes to transmit TBs, the number of TBs that can be transmitted and the size of TBs are very limited under the same time slot scheduling transmission unit (for example, slot time slot). When there is no spatial multiplexing, a slot only transmits one TB, and when there is spatial multiplexing, a slot can transmit a maximum of two TBs. Taking into account the coding and interleaving gain and the error rate / retransmission delay caused by the excessive TB size (TBS), the bit size of a TB (TB size) is limited (for example, it cannot be greater than 6144 bits in LTE). In other words, the related art can only transmit a limited size of TB data of a HARQ process of a HARQ entity in a slot, and cannot meet the requirements of low latency, high reliability and high throughput at the same time. In the embodiment of the present disclosure, multiple HARQ entities are used to transmit the data of one DRB. For services that need to meet the requirements of low latency, high reliability and high throughput at the same time, multiple HARQ entities in one time domain transmission unit are allowed to transmit data at the same time. Since the number of HARQ entities available for one DRB increases, it means that the number of TBs that can be transmitted at the same time increases, which also means an improvement in data throughput in a short period of time. For example, if one DRB is mapped to m (m is an integer greater than 1) HARQ entities, a maximum of 2m TBs can be transmitted simultaneously under spatial multiplexing. The more HARQ entities a DRB is mapped to, the more TBs can be transmitted at the same time, thereby achieving rapid and large-scale transmission of data of a service data stream in a very short time, and when a TB fails to be transmitted, it can be retransmitted separately without affecting the transmission of other TB data in the same DRB. Figure 11 is a schematic diagram of data mapping from one DRB to multiple HARQ entities according to an embodiment of the present disclosure, and Figure 12 is a schematic diagram of transmission of data packets when one DRB is mapped to multiple HARQ entities according to an embodiment of the present disclosure. As shown in Figure 12, in the presence of SDAP, PDCP, RLC, and MAC sublayers, since the DRB can be directly mapped to MAC layer data, in some cases there is no need to add a MAC subheader in the MAC layer.

[0059] In an optional embodiment, the DRB and HARQ entity mapping information includes at least one of the following: a group identifier ID indicating the mapping relationship between at least one DRB and at least one HARQ entity in each group; the DRB ID of the DRB in each group; the HARQ entity ID mapped corresponding to the DRB ID in each group; the HARQ process ID mapped corresponding to the DRB ID in each group; the transport block TB ID mapped corresponding to the DRB ID in each group; the DRB priority corresponding to the DRB ID in each group; and a data mapping rule for indicating the allocation of data of each DRB in each group to each HARQ entity.

[0060] The following is an example of the DRB and HARQ entity mapping information in the above steps:

[0061] For example, the DRB and HARQ entity mapping information may include three groups (it should be noted that only three groups are used as an example for explanation here, and in actual applications, more or fewer groups may be included), corresponding to Group ID1, Group ID2, and Group ID3 respectively. The group of Group ID1 indicates that DRB1 and HARQ entity 1 are mapped one to one; the group of Group ID2 indicates that DRB2 and DRB3 are both mapped to HARQ entity 2; the group of Group ID3 indicates that DRB4 is mapped to HARQ entity 3 and HARQ entity 4. Optionally, the DRB ID in each group is mapped to the corresponding HARQ process ID. When multiple DRBs are mapped to one HARQ entity, the HARQ process ID may indicate that different DRB data is mapped to different HARQs under the same HARQ entity. Figure 13 is a schematic diagram of three groups of DRB and HARQ entity mapping information in an embodiment of the present disclosure. As shown in Figure 13 , for Group ID 2, HARQ process ID information may be added, indicating that DRB 2 is mapped to HARQ process 1 and HARQ process 2 of HARQ entity 2, and that DRB 3 is mapped to HARQ process 3 and HARQ process 4 of HARQ entity 2. Optionally, the DRB and HARQ entity mapping information also includes the TB IDs mapped to the DRB IDs within each group, distinguishing different DRB data by TB. For example, when TBs are globally numbered, different TB numbers correspond to different TBs. Using only the absolute TB IDs can distinguish different DRB data. Optionally, the DRB and HARQ entity mapping information also includes the HARQ process ID corresponding to the DRB ID within each group and the TB ID within the HARQ process ID for distinction. In spatial multiplexing, one HARQ process can correspond to two TBs. Using the HARQ process ID and the TB ID within the HARQ process ID ensures that different DRB data can be distinguished by TB even in spatial multiplexing. Optionally, the DRB and HARQ entity mapping information also includes a DRB priority. Through the DRB priority indication corresponding to the data stream, the high-priority data stream can be scheduled for transmission first. Taking the XR service as an example, the I frame (Intra-coded picture frame) is an important video frame, and the data stream of the I frame is mapped to a high-priority DRB. The B frame (bi-directional interpolated prediction frame) and the P frame (predictive-frame) are secondary video frames, and the data streams of the B frame and the P frame are mapped to a low-priority DRB. The data stream of the I frame can be scheduled first during MAC scheduling, and the network can provide performance guarantees for the physical layer transmission of the I frame data, such as the physical layer transmission of the I frame data can use better time-frequency resources, higher transmission power, etc.Optionally, the DRB and HARQ entity mapping information further includes data mapping rules, which specify a method for allocating data of each DRB to each HARQ entity. For example, for Group ID 2 in FIG13 , the data mapping rules indicate that DRB 2 is mapped to an odd-numbered HARQ process under HARQ entity 2, and that DRB 3 is mapped to an even-numbered HARQ process under HARQ entity 2.

[0062] In an optional embodiment, the mapping relationship between the multiple DRBs and a HARQ entity includes at least one of the following: different DRBs are mapped to different HARQ processes of a HARQ entity, wherein the different DRBs are distinguished by the HARQ process IDs under the HARQ entity; different DRBs are mapped to different TBs of a HARQ entity, wherein the different DRBs are distinguished by the TB IDs in the HARQ entity; different DRBs are mapped to different TBs of a HARQ entity, wherein the different DRBs are distinguished by the HARQ process IDs and TB IDs under the HARQ entity.

[0063] In the above steps, multiple DRBs can be mapped to different processes of the same HARQ entity. In this case, different DRBs can be distinguished by the HARQ process IDs under the HARQ entity; in the absence of spatial multiplexing, one HARQ process corresponds to one TB. Since different TBs correspond to different TB serial numbers when TBs are globally numbered, different DRBs can be distinguished by the TB IDs of the HARQ entity. In the presence of spatial multiplexing, one HARQ process corresponds to two TBs. At this time, different DRBs can also be placed on different TBs of the same HARQ process and distinguished by the HARQ process ID and TB ID.

[0064] In an optional embodiment, the mapping relationship between one DRB and multiple HARQ entities includes: allocating the data on the one DRB to the multiple HARQ entities according to the data mapping rules, wherein the data mapping rules are used to indicate the allocation of each DRB data in each group to each HARQ entity.

[0065] The following is an exemplary description of the method by which the data mapping rule indicates the allocation of each DRB data in each group to each HARQ entity: for example, for Group ID2 in Figure 13, the data mapping rule indicates that DRB2 is mapped to the HARQ process with an odd-numbered HARQ Process ID of HARQ entity 2, and indicates that DRB3 is mapped to the HARQ process with an even-numbered HARQ Process ID of HARQ entity 2.

[0066] In an optional embodiment, the first network element uses the DRB and HARQ entity mapping information to configure the mapping between the at least one group of DRBs and HARQ entities, including at least one of the following: the first network element directly receives a target control signaling message including the DRB and HARQ entity mapping information, and uses the target control signaling message to configure the mapping relationship between the DRB and the HARQ entity; the first network element first sends a first control signaling message including a request for the DRB and HARQ entity mapping information, and then receives a target control signaling message including the DRB and HARQ entity mapping information to configure the mapping relationship between the DRB and the HARQ entity; the first network element uses the latest received target control signaling message to modify the mapping relationship between the DRB and the HARQ entity, wherein the target control signaling message includes the latest DRB and HARQ entity mapping information; The first network element uses the latest received target control signaling message to update the mapping relationship between the DRB and the HARQ entity, wherein the target control signaling message includes the latest DRB and HARQ entity mapping information; the first network element uses the latest received target control signaling message to release the original mapping relationship between the DRB and the HARQ entity of the first network element, wherein the target control signaling message includes the latest DRB and HARQ entity mapping information; the first network element uses a second control signaling message containing the mapping information between the DRB and the HARQ entity to send the mapping information between the DRB and the HARQ entity to the second network element, so that the second network element sends data according to the mapping information between the DRB and the HARQ entity, wherein the second control signaling information includes at least one of the following: radio resource control RRC message, downlink control information DCI.

[0067] In the above steps, the target control signaling message includes but is not limited to: RRC message, NAS (Non-Access-Stratum) message, DCI (Downlink Control Information), and UCI (Uplink Control Information). The first control signaling message includes but is not limited to RRC message, NAS message, DCI, and UCI.

[0068] In an optional embodiment, the first network element directly receives the target control signaling message including the DRB and HARQ entity mapping information, including at least one of the following: the first network element receives the target control signaling message from the second network element, wherein the second network element is a network element that directly sends data to the first network element, and the data is data processed by the first network element according to the DRB and HARQ entity mapping information after being received; the first network element receives the target control signaling message from the third network element, wherein the third network element is a network element that does not directly send data to the first network element, and the data is data processed by the first network element according to the DRB and HARQ entity mapping information after being received; the first network element receives the target control signaling message from the third network element via the second network element, wherein the third network element is a network element that does not directly send data to the first network element, and the second network element is a network element that directly sends data to the first network element, and the data is data processed by the first network element according to the DRB and HARQ entity mapping information after being received.

[0069] In the above steps, the first network element receives the target control signaling message from the second network element, including but not limited to: when the first network element is a UE and the second network element is a base station, downlink transmission is performed between the second network element and the first network element, and the target control signaling message is an RRC message (such as an RRC reconfiguration message) or a DCI message sent by the base station. When the first network element is a base station and the second network element is a UE, uplink transmission is performed between the second network element and the first network element, wherein the base station sends mapping information containing DRBs and HARQ entities to the UE (for example, the mapping information is placed in an RRC message or a DCI message and sent to the UE). Since the base station itself can send mapping information containing DRBs and HARQ entities, it itself knows the mapping relationship. Therefore, the base station can deliver the data received on the HARQ entity upward through the DRB mapped to the HARQ entity according to the mapping information previously sent to the UE. The first network element receives the target control signaling message from the third network element, including but not limited to: when the first network element is a UE and the third network element is a base station that only sends the target control signaling message (no user plane data transmission), the target control signaling comes from the RRC message or DCI message of the base station, and the second network element is a base station that only sends data transmission (no control signaling). In this case, the first network element can configure the mapping relationship between the HARQ entity and the DRB of the received second network element data according to the RRC message from the third network element, and deliver the data upward based on the configured mapping relationship. The first network element receives the target control signaling message from the third network element via the second network element, including but not limited to: when the first network element is a UE and the second network element is a DU (which can directly interact with the UE for control signaling messages and data transmission messages), and the third network element is a CU, since the CU and the UE do not interact directly, the RRC message generated by the CU needs to be sent to the UE via the DU.

[0070] In an optional embodiment, the UE obtains static mapping information between DRBs and HARQ entities for data transmission between the UE and base station B by receiving an RRC message from base station A. The RRC message includes mapping information between DRBs and HARQ entities of base station B. The UE then obtains real-time dynamic mapping information between DRBs and HARQ entities for data transmission between the UE and base station B by receiving a DCI message from base station B. The DCI message includes real-time mapping information between DRBs and HARQ entities of base station B.

[0071] In an optional embodiment, the target control signaling message includes but is not limited to: RRC message, NAS message, DCI, and UCI.

[0072] In an optional embodiment, the first control signaling message includes but is not limited to: RRC message, NAS message, DCI, and UCI.

[0073] In an optional embodiment, the RRC message includes at least one of the following: an RRC connection establishment message, an RRC configuration message, an RRC reconfiguration message, an RRC forwarding message, an RRC request message, and an RRC request response message.

[0074] In an optional embodiment, the first network element includes at least one of the following: RAN, UE, CU, DU, relay node, and IAB node.

[0075] In an optional embodiment, the second network element includes at least one of the following: RAN, UE, CU, DU, relay node, and IAB node.

[0076] In an optional embodiment, the third network element includes at least one of the following: RAN, UE, CU, DU, relay node, and IAB node.

[0077] FIG14 is a second flowchart of a data transmission method according to an embodiment of the present disclosure. As shown in FIG14 , the process includes the following steps:

[0078] Step S1402: The second network element configures mapping between at least one group of DRBs and HARQ entities using data radio bearer (DRB) and hybrid automatic repeat request (HARQ) entity mapping information, wherein the DRB and HARQ entity mapping information indicates a mapping relationship between the DRBs and HARQ entities of the at least one group, and each of the at least one group includes at least one DRB and at least one HARQ entity.

[0079] In step S1404, the second network element transmits the data stream to be sent through one of the DRBs to the HARQ entity in the group mapped with the DRB according to the mapping relationship between the DRB and HARQ entity of at least one group indicated by the DRB and HARQ entity mapping information.

[0080] In the above steps, when configuring the relationship between DRB and HARQ entity mapping, the second network element clearly indicates how each DRB is mapped to each HARQ entity. Assume that there are 3 groups of mapping information (of course, there can also be more or fewer groups of mapping information. Here, only 3 groups of mapping information are used as an example): DRB1 is mapped to HARQ entity 1, DRB2 and 3 are mapped to HARQ entity 2, and DRB4 is mapped to HARQ entity 3 and HARQ entity 4. Data flow1 and data flow2 are data with the same service characteristics, and data flow3, data flow4, and data flow5 are data with different service characteristics. The services of data flow3 and data flow4 are interrelated. When the second network element sends the data stream, it sends data flow1 and data flow2 to the second network element HARQ entity 1 through DRB1 according to the configured mapping relationship, sends data flow3 and data flow4 to the transmitting end HARQ entity 2 through DRB2 and DRB3 for transmission, and sends data flow5 to the second network element HARQ entity 3 and HARQ entity 4 through DRB4 for transmission. At the MAC layer, the data mapped to the HARQ entity is placed in the HARQ process of the HARQ entity for physical layer transmission in the form of TB. Each HARQ entity has multiple parallel HARQ processes that support TB transmission under DRB.

[0081] Through the above steps, the mapping between DRB and HARQ entities can be configured based on the DRB and HARQ entity mapping information, and data with different business characteristics can be transmitted according to demand, so that data transmission can flexibly meet the underlying transmission requirements of different services, and greatly improve the business transmission capability and business performance experience.

[0082] In an optional embodiment, the mapping relationship between the DRB of each group and the HARQ entity includes at least one of the following: the mapping relationship between one DRB and one HARQ entity; the mapping relationship between one DRB and multiple HARQ entities; the mapping relationship between multiple DRBs and one HARQ entity.

[0083] In an optional embodiment, the DRB and HARQ entity mapping information includes at least one of the following: a group identifier ID indicating the mapping relationship between at least one DRB and at least one HARQ entity in each group; the DRB ID of the DRB in each group; the HARQ entity ID mapped corresponding to the DRB ID in each group; the HARQ process ID mapped corresponding to the DRB ID in each group; the transport block TB ID mapped corresponding to the DRB ID in each group; the DRB priority corresponding to the DRB ID in each group; and a data mapping rule for indicating the allocation of data of each DRB in each group to each HARQ entity.

[0084] In an optional embodiment, the mapping relationship between the multiple DRBs and a HARQ entity includes at least one of the following: different DRBs are mapped to different HARQ processes of a HARQ entity, wherein the different DRBs are distinguished by the HARQ process IDs under the HARQ entity; different DRBs are mapped to different TBs of a HARQ entity, wherein the different DRBs are distinguished by the TB IDs in the HARQ entity; different DRBs are mapped to different TBs of a HARQ entity, wherein the different DRBs are distinguished by the HARQ process IDs and TB IDs under the HARQ entity.

[0085] In an optional embodiment, the mapping relationship between one DRB and multiple HARQ entities includes: allocating the data on the one DRB to the multiple HARQ entities according to the data mapping rules, wherein the data mapping rules are used to indicate the allocation of data of each DRB in each group to each HARQ entity.

[0086] In an optional embodiment, the second network element uses the DRB and HARQ entity mapping information to configure the mapping between the at least one group of DRBs and HARQ entities, including at least one of the following: the second network element receives a third control signaling message including the DRB and HARQ entity mapping information, and uses the third control signaling message to configure the mapping relationship between the DRB and the HARQ entity; the second network element first sends a fourth control signaling message including a request for the DRB and HARQ entity mapping information, and then receives a third control signaling message including the DRB and HARQ entity mapping information to configure the mapping relationship between the DRB and the HARQ entity; the third control signaling message includes the DRB and HARQ entity mapping information. The second network element uses the latest received third control signaling message to modify the mapping relationship between DRB and HARQ entity, wherein the third control signaling message includes the latest DRB and HARQ entity mapping information; the second network element uses the latest received third control signaling message to update the mapping relationship between DRB and HARQ entity, wherein the third control signaling message includes the latest DRB and HARQ entity mapping information; the second network element uses the latest received third control signaling message to cancel the original mapping relationship between DRB and HARQ entity of the second network element, wherein the third control signaling message includes the latest DRB and HARQ entity mapping information.

[0087] In an optional embodiment, the second network element receives the third control signaling message including the DRB and HARQ entity mapping information, including at least one of the following: the second network element receives the third control signaling message including the DRB and HARQ entity mapping information from the first network element, wherein the first network element is a network element that directly receives data from the second network element, and the data is data sent by the second network element according to the DRB and HARQ entity mapping information; the second network element receives the third control signaling message including the DRB and HARQ entity mapping information from the third network element, wherein the third network element is a network element that does not directly receive data from the second network element, and the data is data sent by the second network element according to the DRB and HARQ entity mapping information; the second network element receives the third control signaling message including the DRB and HARQ entity mapping information from the third network element via the first network element, wherein the first network element is a network element that directly receives data from the second network element, and the third network element is a network element that does not directly receive data from the second network element, and the data is data sent by the second network element according to the DRB and HARQ entity mapping information.

[0088] In an optional embodiment, the method also includes: the second network element sends a fifth control signaling message (such as an RRC reconfiguration message, a DCI message) including the DRB and HARQ entity mapping information to the first network element, wherein the first network element is the network element that receives the second network element data.

[0089] In the above steps, when the first network element is a UE and the second network element is a base station, downlink transmission is performed between the second network element and the first network element. In this case, the base station transmits the DRB and HARQ entity mapping information and downlink data to the UE. The downlink data can be sent through the HARQ entity corresponding to the DRB. After receiving the DRB and HARQ entity mapping information, the UE can know how to use the HARQ entity and DRB to receive data and submit it upward.

[0090] In an optional embodiment, before the second network element sends the fifth control signaling message including the DRB and HARQ entity mapping information to the first network element, the method further includes: the second network element receives a sixth control signaling message including a request for the DRB and HARQ entity mapping information from the first network element. For example, the UE first sends a sixth control signaling message including a request for the DRB and HARQ entity mapping information to the base station (for example, the sixth control signaling message is an RRC request message or a UCI message), and after receiving the request message, the base station sends the fifth control signaling message including the DRB and HARQ entity mapping information to the UE (for example, the fifth control signaling message is an RRC reconfiguration message or a DCI message).

[0091] In an optional embodiment, the third control signaling message includes at least one of the following: RRC message, NAS message, DCI, UCI.

[0092] In an optional embodiment, the fourth control signaling message includes at least one of the following: RRC message, NAS message, DCI, UCI.

[0093] In an optional embodiment, the RRC message includes at least one of the following: an RRC connection establishment message, an RRC configuration message, an RRC reconfiguration message, an RRC forwarding message, an RRC request message, and an RRC request response message.

[0094] In an optional embodiment, the second network element sends a data stream that needs to be sent through one group of DRBs to the HARQ entity mapped to the DRB in the group, including: the second network element sends the data stream according to the service characteristics of the data stream that needs to be sent, wherein data streams with different service characteristics are sent through different DRBs to the corresponding mapped HARQ entities.

[0095] In the above steps, data flows with different service characteristics can be sent by corresponding mapped HARQ entities through different DRBs. The following example illustrates the sending method: assuming that data flow1 and data flow2 are data with the same service characteristics, and data flow3 and data flow4 are data with different service characteristics, data flow1 and data flow2 are transmitted through DRB1, and data flow3 and data flow4 are transmitted through DRB2 and DRB3 respectively. The method for the second network element to obtain the service characteristics includes but is not limited to: receiving service characteristic information from the core network, parsing NAS signaling to obtain service characteristic information, parsing QoS parameter information to obtain service characteristic information, parsing service characteristic information transmitted along the data flow to obtain service characteristic information, obtaining service characteristic information through DPI (Deep Packet Inspection) deep packet parsing, obtaining service characteristic information through AI (Artificial Intelligence) reasoning, and obtaining service characteristic information through big data analysis.

[0096] In an optional embodiment, the second network element includes at least one of the following: RAN, UE, CU, DU, relay node, and IAB node.

[0097] In an optional embodiment, the first network element includes at least one of the following: RAN, UE, CU, DU, relay node, and IAB node.

[0098] In an optional embodiment, the third network element includes at least one of the following: RAN, UE, CU, DU, relay node, and IAB node.

[0099] FIG15 is a flowchart of a data transmission method according to an embodiment of the present disclosure. As shown in FIG15 , the process includes the following steps:

[0100] Step S1502: The third network element configures mapping between at least one group of DRBs and HARQ entities using DRB-to-HARQ entity mapping information, wherein the DRB-to-HARQ entity mapping information indicates a mapping relationship between the DRBs and HARQ entities of the at least one group, and each of the at least one group includes at least one DRB and at least one HARQ entity.

[0101] Step S1504: The third network element sends the DRB and HARQ entity mapping information.

[0102] Through the above steps, the mapping between DRB and HARQ entity can be configured based on the DRB and HARQ entity mapping information, so that data that needs to be transmitted differentially can be transmitted separately at the physical layer, thereby ensuring the difference in service performance. It effectively solves the problem that the data transmission method in the related technology multiplexes the data of different DRBs together at the MAC layer and cannot transmit the data differentially at the physical layer, achieves the effect of improving the flexibility of physical layer data transmission, flexibly meets the underlying transmission requirements of different services, and greatly improves the service transmission capability and service performance experience.

[0103] In an optional embodiment, the mapping relationship between the DRB of each group and the HARQ entity includes at least one of the following: the mapping relationship between one DRB and one HARQ entity; the mapping relationship between one DRB and multiple HARQ entities; the mapping relationship between multiple DRBs and one HARQ entity.

[0104] In an optional embodiment, the DRB and HARQ entity mapping information includes at least one of the following: a group identifier ID indicating the mapping relationship between at least one DRB and at least one HARQ entity in each group; the DRB ID of the DRB in each group; the HARQ entity ID mapped corresponding to the DRB ID in each group; the HARQ process ID mapped corresponding to the DRB ID in each group; the transport block TB ID mapped corresponding to the DRB ID in each group; the DRB priority corresponding to the DRB ID in each group; and a data mapping rule for indicating the allocation of data of each DRB in each group to each HARQ entity.

[0105] In an optional embodiment, the mapping relationship between the multiple DRBs and a HARQ entity includes at least one of the following: different DRBs are mapped to different HARQ processes of a HARQ entity, wherein the different DRBs are distinguished by the HARQ process IDs under the HARQ entity; different DRBs are mapped to different TBs of a HARQ entity, wherein the different DRBs are distinguished by the TB IDs in the HARQ entity; different DRBs are mapped to different TBs of a HARQ entity, wherein the different DRBs are distinguished by the HARQ process IDs and TB IDs under the HARQ entity.

[0106] In an optional embodiment, the mapping relationship between one DRB and multiple HARQ entities includes: allocating the data on the one DRB to the multiple HARQ entities according to the data mapping rules, wherein the data mapping rules are used to indicate the allocation of data of each DRB in each group to each HARQ entity.

[0107] In an optional embodiment, the third network element sends the DRB and HARQ entity mapping information, including at least one of the following: the third network element directly sends the DRB and HARQ entity mapping information to the first network element, so that the first network element configures at least one group of mappings between DRBs and HARQ entities when receiving data and delivers the data received by the HARQ entities included in each group to the upper layer through the DRB mapped to the HARQ entity according to the mapping between the at least one group of DRBs and HARQ entities; the third network element directly sends the DRB and HARQ entity mapping information to the second network element, so that the second network element configures at least one group of mappings between DRBs and HARQ entities when transmitting data and delivers a data stream to be sent through one of the DRBs to the HARQ entity mapped to the DRB in the group according to the mapping between the at least one group of DRBs and HARQ entities; the third network element sends the DRB and HARQ entity mapping information to the first network element through the second network element, so that the first network element performs data mapping processing according to the DRB and HARQ entity mapping information when transmitting data.

[0108] In an optional embodiment, the third network element sending the DRB and HARQ entity mapping information includes: the third network element sending the DRB and HARQ entity mapping information through a seventh control signaling message, wherein the seventh control signaling message includes at least one of the following: RRC message, NAS message, DCI, UCI.

[0109] In an optional embodiment, the RRC message includes at least one of the following: an RRC connection establishment message, an RRC configuration message, an RRC reconfiguration message, an RRC forwarding message, an RRC request message, and an RRC request response message.

[0110] In an optional embodiment, the third network element includes at least one of the following: RAN, UE, CU, DU, relay node, and IAB node.

[0111] In an optional embodiment, the first network element includes at least one of the following: RAN, UE, CU, DU, relay node, and IAB node.

[0112] In an optional embodiment, the second network element includes at least one of the following: RAN, UE, CU, DU, relay node, and IAB node.

[0113] Below, the application of the target control signaling message in the above steps is exemplified: The radio resource control message, namely the RRC (Radio Resource Control) message, is a control signaling message exchanged between the base station and the UE. In the 4G / 5G system, it is generated by the base station RRC layer. The RRC establishment message is used to establish an RRC connection when the UE is in a non-connected state (for example, the UE is in the RRC idle state RRC_IDLE). The RRC establishment message includes an RRC establishment request message sent by the UE to the base station (such as RRCSetupRequest message, RRCReestablishmentRequest message) and an RRC establishment message sent by the base station to the UE (for example, RRCSetup message). After the RRC connection is established, the UE will send an RRC establishment completion message (for example, RRCSetupComplete message). The UE can use the RRC establishment request message to send a DRB and HARQ entity mapping information request, and the base station can use the RRC establishment message to send DRB and HARQ entity mapping information to instruct the UE to perform radio bearer configuration. Optionally, the UE can also use the RRC establishment completion message to send DRB and HARQ entity mapping information. The RRC reconfiguration message (RRCReconfiguration message) is used to modify the RRC connection when the UE is in a connected state (for example, RRC_CONNECTED). The UE receives the RRC reconfiguration message (RRCReconfiguration message) and performs radio bearer configuration according to the radio bearer configuration information included in the RRCReconfiguration message. The base station may include DRB and HARQ entity mapping information in the RRC reconfiguration message and send it to the UE. After receiving the RRC reconfiguration message including the DRB and HARQ entity mapping information, the UE performs radio bearer configuration according to the mapping information. Optionally, the mapping information is carried in the IE (Information Element) of the RRC reconfiguration message. For example, the DRB and HARQ entity mapping information is carried in the radio bearer configuration IE. For example, the DRB and HARQ entity mapping information is carried in the MAC configuration IE. For example, the DRB and HARQ entity mapping information is carried in the RLC configuration IE. For example, the DRB and HARQ entity mapping information is carried in the PDCP configuration IE. For example, the UE receives the RadioBearerConfig IE carrying the DRB and HARQ entity mapping information, and performs mapping association between each DRB and each HARQ entity on the UE side according to the DRB and HARQ entity mapping information.For example, the UE receives the RLC-BearerConfig IE carrying the DRB and HARQ entity mapping information, and performs mapping association between each DRB and each HARQ entity on the UE side according to the DRB and HARQ entity mapping information.

[0114] A 5G base station can be divided into two parts, CU and DU. The CU is the centralized unit of the base station, and the DU is the distributed unit of the base station. The CU and DU interact through the F1 interface. The physical upper layer, MAC, and RLC layers with high real-time requirements are placed in the DU for processing, while the PDCP and RRC layers with low real-time requirements are placed in the CU for processing. When the CU and DU are not deployed in an integrated manner, the DU first receives information from the UE and then sends it to the CU through the F1 interface. When downlink data arrives, the CU processes it first, then transmits it to the DU through the F1 interface, and then passes it to the UE through the air interface. The CU sends an RRC message including DRB and HARQ entity mapping information to the DU, and the DU forwards the mapping information to the UE. The DU and UE perform mapping of uplink and downlink data transmission according to the mapping relationship. For downlink transmission, according to the DRB and HARQ entity mapping information of the CU in the RRC message, the DU puts the data on the DRB on the HARQ entity mapped by the DRB and sends it. For uplink transmission, according to the DRB and HARQ entity mapping information of the CU in the RRC message, the DU puts the data received on the HARQ entity into the mapped DRB and delivers it to the upper layer.

[0115] For the scenario where CU and DU are deployed separately, after the UE sends an RRC connection establishment request, the DU sends a forwarding message of the UE RRC establishment request message to the CU (for example, Initial UL RRC Message Transfer) to forward the initial uplink RRC message from the DU to the control plane (CU-CP) of the CU. The CU allocates wireless resources to the UE by sending a forwarding message of the downlink RRC message (DL RRC Message Transfer) to the DU. Figure 16 is a schematic diagram 1 of the RRC message transmission method according to an embodiment of the present disclosure. As shown in Figure 16, it can be seen that the DU plays the role of RRC message forwarding between the CU and the UE. In an embodiment of the present disclosure, the CU can configure an RRC message including DRB and HARQ entity mapping information, and forward it to the UE through the DU. The UE can also send an RRC message including a DRB and HARQ entity mapping information request to the CU through the DU.

[0116] In 5G, base stations use downlink control information (DCI) to provide terminals with control information such as physical resource allocation, power control, and HARQ for uplink and downlink scheduling. DCI can be transmitted to the UE on the PDCCH (Physical Downlink Control Channel) or PDSCH (Physical Downlink Shared Channel). In 5G, UEs use UCI to provide base stations with control information such as uplink scheduling, HARQ feedback, and channel measurement. UCI can be transmitted to the base station on the PUCCH (Physical Uplink Control Channel) or PUSCH (Physical Uplink Shared Channel). Static or semi-static configuration between the base station and UE is generally accomplished through RRC messages, while dynamic configuration between the base station and UE is generally accomplished through DCI and UCI. RRC messages can be used to perform static or semi-static configuration of DRB and HARQ entity mapping information, and then DCI and / or UCI can be used to dynamically configure DRB and HARQ entity mapping information based on network and service dynamics. Optionally, the UE sends a request for DRB and HARQ entity mapping information through UCI, and after receiving the request, the base station sends DRB and HARQ entity mapping information to the UE through DCI. For downlink transmission, the base station configures the DRB and HARQ entity mapping information and sends downlink data according to the mapping information. The UE receives the relationship information between the DRB and HARQ entity mapping and receives the downlink data and submits the downlink data to the upper layer according to the mapping relationship. For uplink transmission, the base station configures the relationship information between the DRB and HARQ entity mapping and sends it to the UE. The UE receives the relationship information between the DRB and HARQ entity mapping and sends the uplink data according to the mapping information. The base station receives the uplink data according to the mapping information. Regardless of downlink transmission or uplink transmission, the UE needs to obtain the DRB and HARQ entity mapping information from the base station to know the mapping relationship between the DRB and HARQ entity. The base station will send the DRB and HARQ entity mapping information to the UE through RRC messages and DCI messages to inform the UE of the mapping relationship. The UE processes the received data according to the mapping relationship. The base station can send the DRB and HARQ entity mapping information through the RRC establishment message when the RRC is established, or send the DRB and HARQ entity mapping information through the RRC reconfiguration message after the RRC is established. When the base station needs to change the mapping relationship between the DRB and the HARQ entity in real time, the mapping information of the DRB and the HARQ entity is sent through DCI.RRC messages are used for static or semi-static DRB and HARQ entity mapping configuration in the network, and DCI messages are used for dynamic and real-time DRB and HARQ entity mapping configuration in the network. After the UE receives the DRB and HARQ entity mapping information, it determines the DRB corresponding to each HARQ entity mapped on the receiving side according to the mapping information, and delivers data upward through the DRB. When the UE is in a non-connected state, the DRB and HARQ entity mapping information is configured through an RRC connection establishment message. Optionally, the UE first sends an RRC connection request including a DRB and HARQ entity mapping information request, and then receives an RRC connection establishment message including DRB and HARQ entity mapping information to obtain the DRB and HARQ entity mapping information for mapping configuration. When the UE is in a connected state, the UE can use an RRC reconfiguration message to obtain the DRB and HARQ entity mapping information for mapping configuration. Optionally, when the UE needs to change the mapping relationship between the DRB and the HARQ entity, the base station can actively initiate a dynamic configuration message of the DRB and HARQ entity mapping information and send it to the UE through DCI. Optionally, when the UE needs to change the mapping relationship between DRB and HARQ entity, the UE may also actively initiate dynamic configuration request information of DRB and HARQ entity mapping information through UCI, and then the base station initiates dynamic configuration information of DRB and HARQ entity mapping information to the UE through DCI. Optionally, the dynamic configuration request information of DRB and HARQ entity mapping information actively initiated by the UE through UCI includes the UE's request suggestion information for one or more groups of DRB and HARQ entity mappings, such as the UE requests the following mapping information from the base station: DRB1 is mapped to HARQ entity 1, DRB2 is mapped to HARQ entity 2 and HARQ entity 3. Optionally, the RRC message is used to statically or semi-statically transmit long-period DRB and HARQ entity mapping information, including: the group ID of the mapping relationship between DRB and HARQ entity, the DRB ID in each group, the HARQ entity ID corresponding to the DRB ID mapping in each group, the priority corresponding to each DRB in each group, and the data mapping rules for allocating the data of each DRB to each HARQ entity. The DCI message is used to transmit short-cycle or dynamically changing DRB and HARQ entity mapping information based on the mapping relationship transmitted by the RRC message, including: the HARQ process ID corresponding to the DRB ID mapping in each group; the TB ID corresponding to the DRB ID mapping in each group.

[0117] In an optional embodiment, the base station uses a DCI message to send mapping information between DRB and HARQ entity to the UE, instructing the UE to configure the mapping between the DRB and HARQ entity on the UE side. After receiving the DCI message, the UE obtains the mapping information between the DRB and the HARQ entity from the DCI message and configures the mapping between each DRB and each HARQ entity on the UE side according to the mapping information between the DRB and the HARQ entity. Optionally, the mapping configuration actions include but are not limited to: establishing a mapping relationship between the DRB and the HARQ entity, modifying the mapping relationship between the DRB and the HARQ entity, releasing the mapping relationship between the DRB and the HARQ entity, and replacing the original mapping relationship between the DRB and the HARQ entity on the UE side with a new mapping relationship between the DRB and the HARQ entity.

[0118] In an optional embodiment, the base station uses a DCI message to send the latest mapping information between DRBs and HARQ entities to the UE, instructing the UE to modify the mapping between the DRBs and HARQ entities on the UE side. After receiving the DCI message, the UE obtains the latest mapping information between DRBs and HARQ entities from the DCI message and modifies the mapping relationship between each DRB and each HARQ entity on the UE side according to the mapping information between DRBs and HARQ entities.

[0119] In an optional embodiment, the base station first uses an RRC message to send the mapping information of the DRB and the HARQ entity to the UE, instructing the UE to map the DRB and the HARQ entity on the UE side. When the mapping relationship needs to be updated, the real-time mapping information of the DRB and the HARQ entity is sent to the UE using DCI, instructing the UE to update the mapping of the DRB and the HARQ entity on the UE side. After receiving the DCI message, the UE obtains the latest mapping information of the DRB and the HARQ entity from the DCI message and updates the mapping relationship between each DRB and each HARQ entity on the UE side according to the mapping information of the DRB and the HARQ entity.

[0120] In an optional embodiment, the base station uses a DCI message to send the latest mapping information between DRBs and HARQ entities to the UE, instructing the UE to delete (or release) the original mapping relationship between the DRBs and HARQ entities on the UE side. After receiving the DCI message, the UE obtains the latest mapping information between the DRBs and HARQ entities from the DCI message and deletes (or releases) the original mapping relationship between each DRB and each HARQ entity on the UE side according to the mapping information between the DRBs and HARQ entities.

[0121] In an optional embodiment, the base station may not use an RRC message to send the DRB and HARQ entity mapping information to the UE, but may directly send the DRB and HARQ entity mapping information to the UE through DCI. The UE only obtains the mapping information between the DRB and the HARQ entity based on the received DCI message, and configures the original mapping relationship between each DRB and each HARQ entity on the UE side according to the mapping information between the DRB and the HARQ entity.

[0122] In an optional embodiment, the UE may request the mapping information between DRBs and HARQ entities from the base station through UCI. For example, the UE may request to establish a mapping relationship between DRB1, DRB2 and HARQ entity 1. For example, the UE may request to release the mapping relationship between DRB1, DRB2 and HARQ entity 1. For example, the UE may request to change the mapping relationship from mapping DRB1, DRB2 and HARQ entity 1 to mapping DRB1 and HARQ entity 1. The base station receives the DRB and HARQ entity mapping information request contained in the UCI and determines the latest mapping information between DRBs and HARQ entities.

[0123] The following is an illustrative description of the data mapping process of DRB and HARQ entity mapping information in conjunction with the control and forwarding separation scenario: In the control signaling and data transmission separation scenario, there are base stations that only send control signaling and base stations that only send data. The base station that only sends control signaling (referred to as the control base station) uses a low-frequency carrier to achieve wide coverage of the control signaling, and the base station that only sends data (referred to as the data base station) can use a high-frequency carrier to achieve short-distance high-speed data transmission. Figure 17 is a second schematic diagram of the RRC message transmission method according to an embodiment of the present disclosure. In this scenario, the control base station is responsible for the transmission of the RRC message, and the DRB and HARQ entity mapping information of the data base station is placed in the RRC message of the control base station for transmission. The data base station uses the mapping information in the RRC information sent by the control base station to send downlink data or receive uplink data. Optionally, the control base station can transmit the mapping information to the data base station through an inter-base station interface (for example, an X2 interface, an Xn interface). The UE receives the RRC information sent by the control base station and receives downlink data from the data base station or transmits uplink data to the data base station according to the mapping information. In a macro-micro base station networking scenario, the macro base station has a larger coverage area. The macro base station can provide control signaling transmission for the micro base station. The macro base station not only provides RRC control signaling and data transmission for UEs connected to the macro base station, but also for UEs connected to the micro base station. The macro base station provides instructions for the micro base station and the UE connected to the micro base station on the mapping of DRBs and HARQ entities by sending RRC messages containing the mapping information of DRBs and HARQ entities corresponding to the micro base station-micro base station-served UE.

[0124] Below, the method of this solution is generally described in conjunction with specific embodiments:

[0125] FIG18 is a fourth flowchart of a data transmission method according to an embodiment of the present disclosure. The processing steps at the data receiving end are as follows:

[0126] Step S1802: Acquire mapping information between HARQ entities and DRBs;

[0127] Step S1804: configuring mapping between one or more HARQ entities and one or more DRBs according to the mapping information between the HARQ entities and the DRBs;

[0128] Step S1806: Each HARQ entity receives TB data of multiple processes and performs physical layer decoding;

[0129] Step S1808: The data of each HARQ entity is delivered to the upper layer via the DRB mapped by the HARQ entity.

[0130] In the above steps, the method for obtaining the mapping information of the HARQ entity and the DRB includes but is not limited to: receiving control signaling including the mapping information (corresponding to the aforementioned target control signaling), and the control signaling can be an RRC message, a DCI message, for example, sending the mapping information through an RRC reconfiguration message, sending DCI information through PDCCH to dynamically indicate the mapping information, etc.

[0131] FIG19 is a fifth flowchart of a data transmission method according to an embodiment of the present disclosure. The processing steps at the data transmitting end are as follows:

[0132] Step S1902, obtaining service feature information of the data stream;

[0133] Step S1904: Map data flows with different or the same service feature requirements to different DRBs according to the service feature information;

[0134] Step S1906: Acquire mapping information between HARQ entities and DRBs;

[0135] Step S1908: configuring mapping between one or more HARQ entities and one or more DRBs at each transmitting end according to the mapping information between the HARQ entities and the DRBs;

[0136] Step S1910: mapping one or more DRBs to one or more HARQ entities according to mapping information between HARQ entities and DRBs;

[0137] Step S1912: Each HARQ entity configures multi-process TB transmission.

[0138] In step S1906, after the transmitting end obtains the mapping information between the HARQ entity and the DRB, the method includes sending the mapping information to the receiving end.

[0139] The following takes the second network element as a base station and the first network element as a UE as an example to exemplify the processing operations on each network element side.

[0140] Specific embodiment 1: Data mapping process at the base station side during downlink transmission

[0141] When a base station sends data to a UE, it configures the relationship information between the DRB and HARQ entity mapping and sends data according to the mapping information. The base station also informs the UE of the relationship information between the DRB and HARQ entity mapping through an RRC message (such as an RRC connection establishment message or an RRC reconfiguration message).

[0142] The specific steps for the base station side as the transmitter during downlink transmission are as follows:

[0143] Step 1: The base station maps data streams of different service feature information to different DRBs.

[0144] Step 2: The base station configures the mapping relationship between DRB and HARQ entity and sends it to the UE via RRC message.

[0145] Among them, when the base station configures the relationship between DRB and HARQ entity mapping, it clearly indicates how to map between DRB and HARQ entity. For example, DRB1 is mapped to HARQ entity 1, DRB2 and DRB3 are mapped to different HARQ processes of HARQ entity 2, and DRB4 is mapped to HARQ entity 3 and HARQ entity 4. Optionally, the base station sends the mapping relationship to the UE through an RRC connection establishment message or an RRC reconfiguration message, so that the UE understands how the DRB and HARQ entity are mapped. Optionally, the DRB and HARQ entity mapping information can have multiple groups of mapping relationship indications, and each group of DRB and HARQ entity mapping relationship can be one-to-one, one-to-many or many-to-one. Optionally, the DRB and HARQ entity mapping information may include at least one of the following: a group identifier ID indicating the mapping relationship between at least one DRB and at least one HARQ entity in each group; the DRB ID of the DRB in each group; the HARQ entity ID mapped corresponding to the DRB ID in each group; the HARQ process ID mapped corresponding to the DRB ID in each group; the transport block TB ID mapped corresponding to the DRB ID in each group; the DRB priority corresponding to the DRB ID in each group; and a data mapping rule for indicating the allocation of data of each DRB in each group to each HARQ entity.

[0146] Step 3: The base station hands over the data to be sent to the HARQ entity through the DRB according to the configured mapping relationship between the DRB and the HARQ entity for transmission. Optionally, in step 3, when sending data, the base station can place different service data on different TBs for transmission according to the configured mapping relationship. For example, in the mapping of one DRB to one HARQ entity, since the data streams on different DRBs are mapped to the TBs of different HARQ entities, the situation where different DRBs are multiplexed into one TB will not occur. For example, in the mapping of multiple DRBs to one HARQ entity, the data streams on different DRBs are mapped to different HARQ processes of the same HARQ entity, avoiding the situation where different DRBs are multiplexed into one TB. Optionally, one HARQ process can transmit 2 TBs during spatial multiplexing, and the information of the HARQ process ID and TB ID can be added to the mapping relationship information when configuring the mapping relationship to explicitly indicate that the data streams on different DRBs are mapped to different TBs of the same HARQ entity. For example, in the mapping of one DRB to multiple HARQ entities, the data streams on one DRB can be mapped to TBs of different HARQ entities. Because data of different services can be distinguished at the physical layer, the base station can adopt different physical layer transmission methods for different service data during transmission. For example, the MCS level can be lowered for TB transmission of highly reliable data streams, and the transmission power can be increased for time slots of highly reliable data stream transmission.

[0147] Step 4: The base station updates the mapping relationship between DRBs and HARQ entities based on service demand changes and sends the updated mapping relationship to the UE via DCI. For example, the DCI transmits the changed mapping information between DRBs and HARQ entities, allowing the UE to adapt to service demand changes in real time.

[0148] Therefore, it can be seen that in this embodiment, data streams with different service feature requirements can be mapped to different DRBs by classification, and then the DRBs can be mapped to HARQ entities using a flexible mapping method to achieve the association between services and HARQ entities and the differentiation of different data streams on the TB. Through this embodiment, differentiated transmission of service data is achieved, especially in physical link transmission, which clearly distinguishes and personalizes service differentiation.

[0149] Specific embodiment 2: UE-side data mapping process during downlink transmission

[0150] When the base station sends data to the UE, the base station configures the relationship between the DRB and the HARQ entity mapping and informs the UE of the relevant DRB and HARQ entity mapping information through an RRC message (such as an RRC connection establishment message or an RRC reconfiguration message). After receiving the mapping information, the UE can know which DRB the TB data received by the HARQ entity corresponds to. The UE submits the downlink data received on the HARQ entity to the upper layer through the DRB mapped by the HARQ entity.

[0151] The specific steps for the UE as the receiving end during downlink transmission are as follows:

[0152] Step 1 (This step is optional and can be skipped in practice): The UE sends a request message that carries a request for DRB and HARQ entity mapping information. The request message sent by the UE may be an RRC Setup Request message, an RRC Configuration Request message, or UCI.

[0153] Step 2: The UE receives a message containing DRB and HARQ entity mapping information.

[0154] By receiving the mapping information including DRB and HARQ entity, the UE can know which DRB corresponds to each TB of each HARQ process under each HARQ entity, and then deliver the downlink data to the upper layer through the mapped DRB. Optionally, the DRB and HARQ entity mapping information can indicate multiple groups of mapping relationships, and each group of DRB and HARQ entity mapping relationship can be one-to-one, one-to-many or many-to-one. Optionally, the DRB and HARQ entity mapping information can include at least one of the following: a group identifier ID indicating the mapping relationship between at least one DRB and at least one HARQ entity in each group; the DRB ID of the DRB in each group; the HARQ entity ID mapped to the DRB ID in each group; the HARQ process ID mapped to the DRB ID in each group; the transport block TB ID mapped to the DRB ID in each group; the DRB priority corresponding to the DRB ID in each group; and a data mapping rule for indicating that the data of each DRB in each group is allocated to each HARQ entity. Optionally, the base station places the DRB and HARQ entity mapping information in an RRC connection establishment message (RRC Setup message) or an RRC reconfiguration message and sends it to the UE, and the UE obtains the mapping information by receiving the above RRC message. Optionally, the base station places the DRB and HARQ entity mapping information in a DCI and sends it to the UE, and the UE obtains the mapping information by receiving the above DCI message.

[0155] Step 3: According to the information of mapping the DRB and the HARQ entity in the DRB and HARQ entity mapping information, the UE submits the TB data received by the HARQ entity to the upper layer through the DRB.

[0156] The DRB and HARQ entity mapping information may include information on multiple groups of HARQ entities and DRB mappings.

[0157] It can be seen from this that by receiving the DRB and HARQ entity mapping information, the UE can know how to independently submit the received data to the upper layer.

[0158] Specific embodiment 3: UE-side data mapping process during uplink transmission

[0159] When the UE sends data to the base station, the UE configures the relationship information between the DRB and HARQ entity mapping and sends data according to the mapping information. Before the UE sends data, the base station informs the UE of the relationship information between the DRB and HARQ entity mapping through an RRC message (such as an RRC connection establishment message, an RRC reconfiguration message) to help the UE send data according to the mapping information. Optionally, the UE first sends a request for the DRB and HARQ entity mapping relationship information, and then the base station sends the DRB and HARQ entity mapping relationship information to the UE.

[0160] The specific steps for the UE side as the transmitter during uplink transmission are as follows:

[0161] Step 1: The UE sends an RRC request message with DRB and HARQ entity mapping information, e.g., the UE requests the configuration of HARQ entities for DRBs of four uplink data streams. (It should be noted that this step is optional and can be skipped to proceed directly to step 2.)

[0162] Step 2: The UE receives an RRC configuration message sent by the base station containing DRB and HARQ entity mapping information. The RRC configuration message may be an RRC reconfiguration message or an RRC request response message. The DRB and HARQ entity mapping information may have multiple groups of mapping relationship indications, and each group of DRB and HARQ entity mapping relationship may be one-to-one, one-to-many or many-to-one. The DRB and HARQ entity mapping information may include at least one of the following: a group identifier ID indicating a mapping relationship between at least one DRB and at least one HARQ entity in each group; the DRB ID of the DRB in each group; the HARQ entity ID mapped to the DRB ID in each group; the HARQ process ID mapped to the DRB ID in each group; the transport block TB ID mapped to the DRB ID in each group; the DRB priority corresponding to the DRB ID in each group; and a data mapping rule for indicating that the data of each DRB in each group is allocated to each HARQ entity. Optionally, step 2 may also be that the UE receives the DRB and HARQ entity mapping information of the downlink data sent by the base station, and uses the DRB and HARQ entity mapping information of the downlink data as the DRB and HARQ entity mapping information of the uplink data sent by the UE.

[0163] Step 3: The UE maps data streams of different service feature information to different DRBs.

[0164] Step 4: The UE delivers the data to be sent to the HARQ entity through the DRB according to the configured mapping relationship between the DRB and the HARQ entity.

[0165] Step 5: Based on uplink service requirements, the UE sends a suggestion message to the base station via the UCI regarding changes in the mapping relationship between DRBs and HARQ entities. (It should be noted that this step is optional.)

[0166] Since the physical layer at the transmitter can distinguish data from different services, different physical layer transmission methods can be used for different service data. For example, the MCS level is lowered for TB transmission of highly reliable data streams, and the transmission power is increased for time slots of highly reliable data stream transmission.

[0167] Therefore, it can be seen that in this embodiment, data streams with different service feature requirements can be mapped to different DRBs by classification, and then the DRBs can be mapped to HARQ entities using a flexible mapping method to achieve the association between services and HARQ entities and the differentiation of different data streams on the TB. Through this embodiment, differentiated transmission of service data is achieved, especially in physical link transmission, which clearly distinguishes and personalizes service differentiation.

[0168] Specific embodiment 4: Data mapping process at the base station side during uplink transmission

[0169] When the base station receives data sent from the UE, the base station configures the relationship information between the DRB and HARQ entity mapping and receives the data according to the mapping information. Before the base station receives the data, the base station informs the UE of the relationship information between the DRB and HARQ entity mapping through an RRC message (such as an RRC connection establishment message, an RRC reconfiguration message) to help the UE send data according to the mapping information. Optionally, the UE first sends a request for the DRB and HARQ entity mapping relationship information, and then the base station sends the DRB and HARQ entity mapping relationship information to the UE.

[0170] The specific steps for the base station side as the receiving end during uplink transmission are as follows:

[0171] Step 1: The base station receives an RRC request message for DRB and HARQ entity mapping information sent by the UE, such as the UE requests to configure a HARQ entity for the DRBs of four uplink data streams.

[0172] Step 2: The base station sends an RRC configuration message containing DRB and HARQ entity mapping information to the UE. The RRC configuration message can be an RRC reconfiguration message or an RRC request response message. For example, the RRC reconfiguration message containing DRB and HARQ entity mapping information sent by the base station indicates the mapping relationship between one or more groups of DRBs and HARQ entities.

[0173] Step 3: The base station configures the DRB and HARQ entity mapping relationship of the base station as the receiving end according to the RRC message containing the DRB and HARQ entity mapping information sent.

[0174] Step 4: The base station delivers the TB data received by each HARQ entity to the upper layer through the mapped DRB according to the configured mapping relationship between the DRB and the HARQ entity.

[0175] Step 5: The base station receives the suggestion information of the mapping relationship change between the UE's DRB and HARQ entity, and sends the latest mapping relationship information between the DRB and HARQ entity to the UE through DCI (it should be noted that this step is optional).

[0176] Since the physical layer at the receiving end can distinguish data of different services, the received data can be delivered to the upper layer independently according to the service. Through this embodiment, differentiated transmission of service data is achieved, especially clear differentiation and personalized guarantee of service differentiation in physical link transmission.

[0177] Through the description of the above implementation methods, those skilled in the art can clearly understand that the method according to the above embodiment can be implemented by means of software plus the necessary general hardware platform, and of course it can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present disclosure is essentially or the part that contributes to the prior art can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), including a number of instructions for enabling a terminal device (which can be a mobile phone, computer, server, or network device, etc.) to execute the methods described in each embodiment of the present disclosure.

[0178] This embodiment also provides a data transmission device for implementing the above-mentioned embodiments and preferred implementations. Details already described will not be repeated. As used below, the term "module" may refer to a combination of software and / or hardware that implements a predetermined function. Although the devices described in the following embodiments are preferably implemented in software, implementation using hardware, or a combination of software and hardware, is also possible and contemplated.

[0179] Figure 20 is a structural block diagram 1 of a data transmission device according to an embodiment of the present disclosure. As shown in Figure 20, the device is applied to a first network element, including: a first configuration module 202, configured to use data radio bearer DRB and hybrid automatic repeat request HARQ entity mapping information to configure at least one group of mappings between DRB and HARQ entities, wherein the DRB and HARQ entity mapping information indicates the mapping relationship between the DRB and HARQ entity of the at least one group, and each group in the at least one group includes at least one DRB and at least one HARQ entity; a first sending module 204, configured to deliver the data received by the HARQ entity included in each group to the upper layer through the DRB mapped to the HARQ entity according to the mapping relationship between the DRB and HARQ entity of at least one group indicated by the DRB and HARQ entity mapping information.

[0180] In an optional embodiment, the mapping relationship between the DRB of each group and the HARQ entity includes at least one of the following: the mapping relationship between one DRB and one HARQ entity; the mapping relationship between one DRB and multiple HARQ entities; the mapping relationship between multiple DRBs and one HARQ entity.

[0181] In an optional embodiment, the DRB and HARQ entity mapping information includes at least one of the following: a group identifier ID indicating the mapping relationship between at least one DRB and at least one HARQ entity in each group; the DRB ID of the DRB in each group; the HARQ entity ID mapped corresponding to the DRB ID in each group; the HARQ process ID mapped corresponding to the DRB ID in each group; the transport block TB ID mapped corresponding to the DRB ID in each group; the DRB priority corresponding to the DRB ID in each group; and a data mapping rule for indicating the allocation of data of each DRB in each group to each HARQ entity.

[0182] In an optional embodiment, the mapping relationship between the multiple DRBs and a HARQ entity includes at least one of the following: different DRBs are mapped to different HARQ processes of a HARQ entity, wherein the different DRBs are distinguished by the HARQ process IDs under the HARQ entity; different DRBs are mapped to different TBs of a HARQ entity, wherein the different DRBs are distinguished by the TB IDs in the HARQ entity; different DRBs are mapped to different TBs of a HARQ entity, wherein the different DRBs are distinguished by the HARQ process IDs and TB IDs under the HARQ entity.

[0183] In an optional embodiment, the mapping relationship between one DRB and multiple HARQ entities includes: allocating the data on the one DRB to the multiple HARQ entities according to the data mapping rules, wherein the data mapping rules are used to indicate the allocation of each DRB data in each group to each HARQ entity.

[0184] In an optional embodiment, the first configuration module 202 includes at least one of the following: a first receiving unit, configured to directly receive a target control signaling message including the DRB and HARQ entity mapping information, and use the target control signaling message to configure the mapping relationship between the DRB and the HARQ entity; a first sending unit, configured to first send a first control signaling message including a request for the DRB and HARQ entity mapping information, and then receive a target control signaling message including the DRB and HARQ entity mapping information to configure the mapping relationship between the DRB and the HARQ entity; a first modifying unit, configured to use the latest received target control signaling message to modify the mapping relationship between the DRB and the HARQ entity, wherein the target control signaling message includes the latest DRB and HARQ entity mapping information; a first updating unit, configured to use the latest received target control signaling message to modify the mapping relationship between the DRB and the HARQ entity A target control signaling message is used to update the mapping relationship between the DRB and the HARQ entity, wherein the target control signaling message includes the latest DRB and HARQ entity mapping information; a first releasing unit is configured to use the latest received target control signaling message to release the original mapping relationship between the DRB and the HARQ entity of the first network element, wherein the target control signaling message includes the latest DRB and HARQ entity mapping information; a second sending unit is configured to use a second control signaling message containing the mapping information between the DRB and the HARQ entity to send the mapping information between the DRB and the HARQ entity to the second network element, so that the second network element sends data according to the mapping information between the DRB and the HARQ entity, wherein the second control signaling information includes at least one of the following: radio resource control RRC message, downlink control information DCI.

[0185] In an optional embodiment, the first receiving unit includes at least one of the following: a first sub-receiving unit, configured to receive the target control signaling message from a second network element, wherein the second network element is a network element that directly sends data to the first network element, and the data is data processed by the first network element according to the DRB and HARQ entity mapping information after being received; a second sub-receiving unit, configured to receive the target control signaling message from a third network element, wherein the third network element is a network element that does not directly send data to the first network element, and the data is data processed by the first network element according to the DRB and HARQ entity mapping information after being received; a third sub-receiving unit, configured to receive the target control signaling message from the third network element via the second network element, wherein the third network element is a network element that does not directly send data to the first network element, and the second network element is a network element that directly sends data to the first network element, and the data is data processed by the first network element according to the DRB and HARQ entity mapping information after being received.

[0186] In an optional embodiment, the target control signaling message includes at least one of the following: RRC message, NAS message, DCI, and UCI.

[0187] In an optional embodiment, the first control signaling message includes at least one of the following: RRC message, NAS message, DCI, UCI.

[0188] In an optional embodiment, the RRC message includes at least one of the following: an RRC connection establishment message, an RRC configuration message, an RRC reconfiguration message, an RRC forwarding message, an RRC request message, and an RRC request response message.

[0189] In an optional embodiment, the first network element includes at least one of the following: RAN, UE, CU, DU, relay node, and IAB node.

[0190] In an optional embodiment, the second network element includes at least one of the following: RAN, UE, CU, DU, relay node, and IAB node.

[0191] In an optional embodiment, the third network element includes at least one of the following: RAN, UE, CU, DU, relay node, node.

[0192] Figure 21 is a second structural block diagram of a data transmission device according to an embodiment of the present disclosure. As shown in Figure 21, the device is applied to a second network element, and includes: a second configuration module 212, configured to use data radio bearer DRB and hybrid automatic repeat request HARQ entity mapping information to configure at least one group of mappings between DRB and HARQ entity, wherein the DRB and HARQ entity mapping information indicates the mapping relationship between the DRB and HARQ entity of the at least one group, and each group in the at least one group includes at least one DRB and at least one HARQ entity; a second sending module 214, configured to hand over the data stream to be sent through one of the DRBs to the HARQ entity in the group mapped with the DRB according to the mapping relationship between the DRB and HARQ entity of the at least one group indicated by the DRB and HARQ entity mapping information.

[0193] In an optional embodiment, the mapping relationship between the DRB of each group and the HARQ entity includes at least one of the following: the mapping relationship between one DRB and one HARQ entity; the mapping relationship between one DRB and multiple HARQ entities; the mapping relationship between multiple DRBs and one HARQ entity.

[0194] In an optional embodiment, the DRB and HARQ entity mapping information includes at least one of the following: a group identifier ID indicating the mapping relationship between at least one DRB and at least one HARQ entity in each group; the DRB ID of the DRB in each group; the HARQ entity ID mapped corresponding to the DRB ID in each group; the HARQ process ID mapped corresponding to the DRB ID in each group; the transport block TB ID mapped corresponding to the DRB ID in each group; the DRB priority corresponding to the DRB ID in each group; and a data mapping rule for indicating the allocation of data of each DRB in each group to each HARQ entity.

[0195] In an optional embodiment, the mapping relationship between the multiple DRBs and a HARQ entity includes at least one of the following: different DRBs are mapped to different HARQ processes of a HARQ entity, wherein the different DRBs are distinguished by the HARQ process IDs under the HARQ entity; different DRBs are mapped to different TBs of a HARQ entity, wherein the different DRBs are distinguished by the TB IDs in the HARQ entity; different DRBs are mapped to different TBs of a HARQ entity, wherein the different DRBs are distinguished by the HARQ process IDs and TB IDs under the HARQ entity.

[0196] In an optional embodiment, the mapping relationship between one DRB and multiple HARQ entities includes: allocating the data on the one DRB to the multiple HARQ entities according to the data mapping rules, wherein the data mapping rules are used to indicate the allocation of data of each DRB in each group to each HARQ entity.

[0197] In an optional embodiment, the second configuration module 212 includes: a second receiving unit, configured to receive a third control signaling message including the DRB and HARQ entity mapping information, and use the third control signaling message to configure the mapping relationship between the DRB and the HARQ entity; a third sending unit, configured to first send a fourth control signaling message including a request for the DRB and HARQ entity mapping information, and then receive a third control signaling message including the DRB and HARQ entity mapping information to configure the mapping relationship between the DRB and the HARQ entity; a second modifying unit, configured to modify the DRB using the most recently received third control signaling message The mapping relationship between RB and HARQ entity, wherein the third control signaling message includes the latest DRB and HARQ entity mapping information; a second updating unit is configured to use the latest received third control signaling message to update the mapping relationship between DRB and HARQ entity, wherein the third control signaling message includes the latest DRB and HARQ entity mapping information; a second releasing unit is configured so that the second network element uses the latest received third control signaling message to release the original mapping relationship between DRB and HARQ entity of the second network element, wherein the third control signaling message includes the latest DRB and HARQ entity mapping information.

[0198] In an optional embodiment, the second receiving unit includes at least one of the following: a fourth receiving subunit, configured to receive the third control signaling message including the DRB and HARQ entity mapping information from the first network element, wherein the first network element is a network element that directly receives data from the second network element, and the data is data sent by the second network element according to the DRB and HARQ entity mapping information; a fifth receiving subunit, configured to receive the third control signaling message including the DRB and HARQ entity mapping information from the third network element, wherein the third network element is a network element that does not directly receive data from the second network element, and the data is data sent by the second network element according to the DRB and HARQ entity mapping information; a sixth receiving subunit, configured to receive the third control signaling message including the DRB and HARQ entity mapping information from the third network element via the first network element, wherein the first network element is a network element that directly receives data from the second network element, the third network element is a network element that does not directly receive data from the second network element, and the data is data sent by the second network element according to the DRB and HARQ entity mapping information.

[0199] In an optional embodiment, the device also includes: a fourth sending module, configured to send a fifth control signaling message including the DRB and HARQ entity mapping information to the first network element, so that the first network element receives data from the second network element according to the DRB and HARQ entity mapping information, wherein the fifth control signaling includes at least one of the following: RRC message, downlink control information DCI.

[0200] In an optional embodiment, the device also includes: a receiving module, configured to receive a sixth control signaling message including a request for the DRB and HARQ entity mapping information from the first network element before sending the fifth control signaling message including the DRB and HARQ entity mapping information to the first network element, wherein the sixth control signaling includes at least one of the following: RRC message, uplink control information UCI.

[0201] In an optional embodiment, the third control signaling message includes at least one of the following: RRC message, NAS message, DCI, UCI.

[0202] In an optional embodiment, the fourth control signaling message includes at least one of the following: RRC message, NAS message, DCI, UCI.

[0203] In an optional embodiment, the RRC message includes at least one of the following: an RRC connection establishment message, an RRC configuration message, an RRC reconfiguration message, an RRC forwarding message, an RRC request message, and an RRC request response message.

[0204] In an optional embodiment, the second sending module 214 includes: a third sending unit, configured to send the data stream according to the service characteristics of the data stream to be sent, wherein data streams with different service characteristics are sent by corresponding mapped HARQ entities through different DRBs.

[0205] In an optional embodiment, the second network element includes at least one of the following: RAN, UE, CU, DU, relay node, and IAB node.

[0206] In an optional embodiment, the first network element includes at least one of the following: RAN, UE, CU, DU, relay node, and IAB node.

[0207] In an optional embodiment, the third network element includes at least one of the following: RAN, UE, CU, DU, relay node, and IAB node.

[0208] Figure 22 is a third structural block diagram of a data transmission device according to an embodiment of the present disclosure. As shown in Figure 22, the device is applied to a third network element, and includes: a third configuration module 222, configured to use data radio bearer DRB and hybrid automatic repeat request HARQ entity mapping information to configure at least one group of mappings between DRB and HARQ entities, wherein the DRB and HARQ entity mapping information indicates the mapping relationship between the DRB and HARQ entity of the at least one group, and each group in the at least one group includes at least one DRB and at least one HARQ entity; a third sending module 224, configured to send the DRB and HARQ entity mapping information.

[0209] In an optional embodiment, the mapping relationship between the DRB of each group and the HARQ entity includes at least one of the following: the mapping relationship between one DRB and one HARQ entity; the mapping relationship between one DRB and multiple HARQ entities; the mapping relationship between multiple DRBs and one HARQ entity.

[0210] In an optional embodiment, the DRB and HARQ entity mapping information includes at least one of the following: a group identifier ID indicating the mapping relationship between at least one DRB and at least one HARQ entity in each group; the DRB ID of the DRB in each group; the HARQ entity ID mapped corresponding to the DRB ID in each group; the HARQ process ID mapped corresponding to the DRB ID in each group; the transport block TB ID mapped corresponding to the DRB ID in each group; the DRB priority corresponding to the DRB ID in each group; and a data mapping rule for indicating the allocation of data of each DRB in each group to each HARQ entity.

[0211] In an optional embodiment, the mapping relationship between the multiple DRBs and a HARQ entity includes at least one of the following: different DRBs are mapped to different HARQ processes of a HARQ entity, wherein the different DRBs are distinguished by the HARQ process IDs under the HARQ entity; different DRBs are mapped to different TBs of a HARQ entity, wherein the different DRBs are distinguished by the TB IDs in the HARQ entity; different DRBs are mapped to different TBs of a HARQ entity, wherein the different DRBs are distinguished by the HARQ process IDs and TB IDs under the HARQ entity.

[0212] In an optional embodiment, the mapping relationship between one DRB and multiple HARQ entities includes: allocating the data on the one DRB to the multiple HARQ entities according to the data mapping rules, wherein the data mapping rules are used to indicate the allocation of data of each DRB in each group to each HARQ entity.

[0213] In an optional embodiment, the third sending module 224 includes at least one of the following: a fourth sending unit, configured to directly send the DRB and HARQ entity mapping information to the first network element, so that when the first network element receives data, it configures at least one group of mappings between DRBs and HARQ entities and delivers the data received by the HARQ entities included in each group to the upper layer through the DRB mapped to the HARQ entity according to the mapping between the at least one group of DRBs and HARQ entities; a fifth sending unit, configured to directly send the DRB and HARQ entity mapping information to the second network element, so that when the second network element transmits data, it configures at least one group of mappings between DRBs and HARQ entities and delivers a data stream to be sent through one group of DRBs to the HARQ entity mapped to the DRB in the group according to the mapping between the at least one group of DRBs and HARQ entities; a sixth sending unit, configured to send the DRB and HARQ entity mapping information to the first network element through the second network element, so that the first network element performs data mapping processing according to the DRB and HARQ entity mapping information during data transmission.

[0214] In an optional embodiment, the third sending module 224 includes: a seventh sending unit, configured to send the DRB and HARQ entity mapping information through a seventh control signaling message, wherein the seventh control signaling message includes at least one of the following: RRC message, NAS message, DCI, UCI.

[0215] In an optional embodiment, the RRC message includes at least one of the following: an RRC connection establishment message, an RRC configuration message, an RRC reconfiguration message, an RRC forwarding message, an RRC request message, and an RRC request response message.

[0216] In an optional embodiment, the third network element includes at least one of the following: RAN, UE, CU, DU, relay node, and IAB node.

[0217] In an optional embodiment, the first network element includes at least one of the following: RAN, UE, CU, DU, relay node, and IAB node.

[0218] In an optional embodiment, the second network element includes at least one of the following: RAN, UE, CU, DU, relay node, and IAB node.

[0219] It should be noted that the above modules can be implemented through software or hardware. For the latter, it can be implemented in the following ways, but not limited to: the above modules are all located in the same processor; or the above modules are located in different processors in any combination.

[0220] An embodiment of the present disclosure further provides a computer-readable storage medium, in which a computer program is stored. The computer program is configured to execute the steps of any one of the above method embodiments when run.

[0221] In an exemplary embodiment, the computer-readable storage medium may include, but is not limited to, various media that can store computer programs, such as a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk, or an optical disk.

[0222] An embodiment of the present disclosure further provides an electronic device, including a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to perform the steps in any of the above method embodiments.

[0223] In an exemplary embodiment, the electronic device may further include a transmission device and an input / output device, wherein the transmission device is connected to the processor, and the input / output device is connected to the processor.

[0224] For specific examples in this embodiment, reference may be made to the examples described in the above embodiments and exemplary implementation modes, and this embodiment will not be described in detail here.

[0225] Obviously, those skilled in the art should understand that the modules or steps of the present disclosure described above can be implemented using a general-purpose computing device, they can be concentrated on a single computing device, or distributed across a network composed of multiple computing devices, they can be implemented using program code executable by the computing device, and thus, they can be stored in a storage device and executed by the computing device, and in some cases, the steps shown or described can be performed in a different order than herein, or they can be fabricated into separate integrated circuit modules, or multiple modules or steps can be fabricated into a single integrated circuit module for implementation. Thus, the present disclosure is not limited to any particular combination of hardware and software.

[0226] The foregoing description is merely a preferred embodiment of the present disclosure and is not intended to limit the present disclosure. Those skilled in the art will readily appreciate that various modifications and variations of the present disclosure are possible. Any modifications, equivalent substitutions, or improvements made within the principles of the present disclosure shall be included within the scope of protection of the present disclosure.

Claims

1. A data transmission method, comprising: The first network element configures the mapping between at least one set of data radio bearers (DRBs) and hybrid automatic repeat request (HARQ) entities using the DRB-HARQ entity mapping information, where the DRB-HARQ entity mapping information indicates the mapping relationship between the at least one set of DRBs and HARQ entities, and each set in the at least one set includes at least one DRB and at least one HARQ entity; The first network element delivers the data received by the HARQ entities included in each set to the upper layer through the DRBs mapped to the HARQ entities according to the mapping relationship between the DRBs and HARQ entities indicated by the DRB-HARQ entity mapping information.

2. The method according to claim 1, wherein The mapping relationship between the DRBs and HARQ entities in each set includes at least one of the following: The mapping relationship between one DRB and one HARQ entity; The mapping relationship between one DRB and multiple HARQ entities; The mapping relationship between multiple DRBs and one HARQ entity.

3. The method according to claim 1 or 2, wherein The DRB-HARQ entity mapping information includes at least one of the following: The group identifier (ID) indicating the mapping relationship between at least one DRB and at least one HARQ entity in each group; The DRB ID of the DRBs in each group; The HARQ entity ID mapped corresponding to the DRB ID in each group; The HARQ process ID mapped corresponding to the DRB ID in each group; The transport block (TB) ID mapped corresponding to the DRB ID in each group; The DRB priority corresponding to the DRB ID in each group; The data mapping rule for indicating the distribution of the data of each DRB in each group to each HARQ entity.

4. The method according to claim 2, wherein, The mapping relationship between multiple DRBs and one HARQ entity includes at least one of the following: Different DRBs are mapped to different HARQ processes of one HARQ entity, where the different DRBs are distinguished by the respective HARQ process IDs under the HARQ entity; Different DRBs are mapped to different TBs of one HARQ entity, where the different DRBs are distinguished by the respective TB IDs in the HARQ entity; Different DRBs are mapped to different TBs of one HARQ entity, where the different DRBs are distinguished by the respective HARQ process IDs and respective TB IDs under the HARQ entity.

5. The method according to claim 2, wherein, The mapping relationship between one DRB and multiple HARQ entities includes: According to the data mapping rule, the data on the one DRB is distributed to the multiple HARQ entities, where the data mapping rule is used to indicate the distribution of the data of each DRB in each group to each HARQ entity.

6. The method according to any one of claims 1 to 5, wherein, The first network element configures the mapping between the at least one set of DRBs and HARQ entities using the DRB-HARQ entity mapping information includes at least one of the following: The first network element directly receives the target control signaling message including the DRB-HARQ entity mapping information and configures the mapping relationship between the DRBs and HARQ entities using the target control signaling message; The first network element first sends a first control signaling message including a request for the mapping information between the DRB and the HARQ entity, and then receives a target control signaling message including the mapping information between the DRB and the HARQ entity to configure the mapping relationship between the DRB and the HARQ entity; The first network element modifies the mapping relationship between the DRB and the HARQ entity using the latest received target control signaling message, where the target control signaling message includes the latest mapping information between the DRB and the HARQ entity; The first network element updates the mapping relationship between the DRB and the HARQ entity using the latest received target control signaling message, where the target control signaling message includes the latest mapping information between the DRB and the HARQ entity; The first network element releases the original mapping relationship between the DRB and the HARQ entity of the first network element using the latest received target control signaling message, where the target control signaling message includes the latest mapping information between the DRB and the HARQ entity; The first network element sends the mapping information between the DRB and the HARQ entity to a second network element using a second control signaling message including the mapping information between the DRB and the HARQ entity, so that the second network element sends data according to the mapping information between the DRB and the HARQ entity, where the second control signaling information includes at least one of the following: radio resource control (RRC) message, downlink control information (DCI).

7. The method according to claim 6, wherein, The first network element directly receiving the target control signaling message including the mapping information between the DRB and the HARQ entity includes at least one of the following: The first network element receives the target control signaling message from a second network element, where the second network element is a network element that directly sends data to the first network element, and the data is the data processed by the first network element according to the mapping information between the DRB and the HARQ entity after being received; The first network element receives the target control signaling message from a third network element, where the third network element is a network element that does not directly send data to the first network element, and the data is the data processed by the first network element according to the mapping information between the DRB and the HARQ entity after being received; The first network element receives the target control signaling message from the third network element via the second network element, where the third network element is a network element that does not directly send data to the first network element, the second network element is a network element that directly sends data to the first network element, and the data is the data processed by the first network element according to the mapping information between the DRB and the HARQ entity after being received.

8. The method according to claim 6 or 7, wherein The target control signaling message includes at least one of the following: Radio resource control (RRC) message, non-access stratum (NAS) message, downlink control information (DCI), uplink control information (UCI).

9. The method according to claim 6, wherein The first control signaling message includes at least one of the following: Radio resource control (RRC) message, non-access stratum (NAS) message, downlink control information (DCI), uplink control information (UCI).

10. The method according to claim 8 or 9, wherein, The RRC message includes at least one of the following: RRC connection establishment message, RRC configuration message, RRC reconfiguration message, RRC forwarding message, RRC request message, RRC request response message.

11. The method according to any one of claims 1 to 10, wherein The first network element includes at least one of the following: Radio Access Network (RAN), User Equipment (UE), Central Unit (CU), Distributed Unit (DU), relay node, Integrated Access and Backhaul (IAB) node.

12. The method according to claim 7, wherein The second network element includes at least one of the following: Radio Access Network (RAN), User Equipment (UE), Central Unit (CU), Distributed Unit (DU), relay node, Integrated Access and Backhaul (IAB) node.

13. The method according to claim 7, wherein, The third network element includes at least one of the following: Radio Access Network (RAN), User Equipment (UE), Central Unit (CU), Distributed Unit (DU), relay node, Integrated Access and Backhaul (IAB) node.

14. A data transmission method, comprising: The second network element configures the mapping between at least one group of Data Radio Bearers (DRBs) and Hybrid Automatic Repeat reQuest (HARQ) entities using the DRB and HARQ entity mapping information, wherein the DRB and HARQ entity mapping information indicates the mapping relationship between the at least one group of DRBs and HARQ entities, and each group in the at least one group includes at least one DRB and at least one HARQ entity; The second network element hands over the data stream to be sent through one group of DRBs to the HARQ entity mapped to the DRB in the group for sending according to the mapping relationship between the at least one group of DRBs and HARQ entities indicated by the DRB and HARQ entity mapping information.

15. The method according to claim 14, wherein, The mapping relationship between the DRB and HARQ entity in each group includes at least one of the following: The mapping relationship between one DRB and one HARQ entity; The mapping relationship between one DRB and multiple HARQ entities; The mapping relationship between multiple DRBs and one HARQ entity.

16. The method according to claim 14 or 15, wherein, The DRB and HARQ entity mapping information includes at least one of the following: The group identifier (ID) indicating the mapping relationship between at least one DRB and at least one HARQ entity in each group; The DRB ID of the DRBs in each group; The HARQ entity ID mapped to the corresponding DRB ID in each group; The HARQ process ID mapped to the corresponding DRB ID in each group; The Transport Block (TB) ID mapped to the corresponding DRB ID in each group; The DRB priority corresponding to the DRB ID in each group; The data mapping rule for indicating that the data of each DRB in each group is allocated to each HARQ entity.

17. The method according to claim 15, wherein, The mapping relationship between multiple DRBs and one HARQ entity includes at least one of the following: Different DRBs are mapped to different HARQ processes of one HARQ entity, wherein the different DRBs are distinguished by the respective HARQ process IDs under the HARQ entity; Different DRBs are mapped to different TBs of one HARQ entity, wherein the different DRBs are distinguished by the respective TB IDs in the HARQ entity; Different DRBs are mapped to different TBs of one HARQ entity, wherein the different DRBs are distinguished by the respective HARQ process IDs and respective TB IDs under the HARQ entity.

18. The method according to claim 15, wherein The mapping relationship between the one DRB and multiple HARQ entities includes: According to the data mapping rule, allocate the data on the one DRB to the multiple HARQ entities, where the data mapping rule is used to indicate the allocation of the data of each DRB in each group to each HARQ entity.

19. The method according to any one of claims 14 to 18, wherein, The second network element configures the mapping between the DRB and HARQ entities of the at least one group by using the DRB and HARQ entity mapping information, including at least one of the following: The second network element receives a third control signaling message including the DRB and HARQ entity mapping information, and configures the mapping relationship between the DRB and HARQ entities by using the third control signaling message; The second network element first sends a fourth control signaling message including a request for the DRB and HARQ entity mapping information, and then receives a third control signaling message including the DRB and HARQ entity mapping information to configure the mapping relationship between the DRB and HARQ entities; The second network element modifies the mapping relationship between the DRB and HARQ entities by using the latest received third control signaling message, where the latest DRB and HARQ entity mapping information is included in the third control signaling message; The second network element updates the mapping relationship between the DRB and HARQ entities by using the latest received third control signaling message, where the latest DRB and HARQ entity mapping information is included in the third control signaling message; The second network element releases the original mapping relationship between the DRB and HARQ entities of the second network element by using the latest received third control signaling message, where the latest DRB and HARQ entity mapping information is included in the third control signaling message.

20. The method according to claim 19, wherein The second network element receives the third control signaling message including the DRB and HARQ entity mapping information, including at least one of the following: The second network element receives the third control signaling message including the DRB and HARQ entity mapping information from the first network element, where the first network element is the network element that directly receives the data from the second network element, and the data is the data sent by the second network element according to the DRB and HARQ entity mapping information; The second network element receives the third control signaling message including the DRB and HARQ entity mapping information from the third network element, where the third network element is the network element that does not directly receive the data of the second network element, and the data is the data sent by the second network element according to the DRB and HARQ entity mapping information; The second network element receives the third control signaling message including the DRB and HARQ entity mapping information from the third network element via the first network element, where the first network element is the network element that directly receives the data from the second network element, the third network element is the network element that does not directly receive the data of the second network element, and the data is the data sent by the second network element according to the DRB and HARQ entity mapping information. The method further includes:

21. The method according to any one of claims 14 to 20, wherein, ​ The second network element sends a fifth control signaling message including the DRB and HARQ entity mapping information to the first network element, so that the first network element receives the data of the second network element according to the DRB and HARQ entity mapping information, where the fifth control signaling includes at least one of the following: RRC message, downlink control information DCI.

22. The method according to claim 21, wherein Before the second network element sends the fifth control signaling message including the DRB and HARQ entity mapping information to the first network element, the method further includes: The second network element receives a sixth control signaling message including a request for the DRB and HARQ entity mapping information from the first network element, where the sixth control signaling includes at least one of the following: RRC message, uplink control information UCI.

23. The method according to claim 19 or 20, wherein The third control signaling message includes at least one of the following: Radio resource control RRC message, non-access stratum NAS message, downlink control information DCI, uplink control information UCI.

24. The method according to claim 19, wherein, The fourth control signaling message includes at least one of the following: Radio resource control RRC message, non-access stratum NAS message, downlink control information DCI, uplink control information UCI.

25. The method according to any one of claims 21 to 24, wherein, The RRC message includes at least one of the following: RRC connection establishment message, RRC configuration message, RRC reconfiguration message, RRC forwarding message, RRC request message, RRC request response message.

26. The method according to claim 14, wherein The second network element hands over a data stream to be sent through a group of DRBs to the HARQ entity mapped to the DRB in the group, including: The second network element sends the data stream according to the service characteristics of the data stream to be sent, where data streams with different service characteristics are handed over to the corresponding mapped HARQ entities for sending through different DRBs.

27. The method according to any one of claims 14 to 26, wherein, The second network element includes at least one of the following: Radio access network RAN, user equipment UE, central unit CU, distributed unit DU, relay node, integrated access backhaul IAB node.

28. The method according to any one of claims 20 to 22, wherein The first network element includes at least one of the following: Radio access network RAN, user equipment UE, central unit CU, distributed unit DU, relay node, integrated access backhaul IAB node.

29. The method according to claim 20, wherein, The third network element includes at least one of the following: Radio access network RAN, user equipment UE, central unit CU, distributed unit DU, relay node, integrated access backhaul IAB node.

30. A data transmission method, including: The third network element configures the mapping between at least one group of DRBs and HARQ entities using data radio bearer DRB and hybrid automatic repeat request HARQ entity mapping information, where the DRB and HARQ entity mapping information indicates the mapping relationship between the at least one group of DRBs and HARQ entities, and each group in the at least one group includes at least one DRB and at least one HARQ entity; The third network element sends the DRB and HARQ entity mapping information.

31. The method according to claim 30, wherein, The mapping relationship between the DRB and HARQ entity in each group includes at least one of the following: The mapping relationship between one DRB and one HARQ entity; The mapping relationship between one DRB and multiple HARQ entities; The mapping relationship between multiple DRBs and one HARQ entity.

32. The method according to claim 30 or 31, wherein, The mapping information of the DRB and the HARQ entity includes at least one of the following: The group identification ID indicating the mapping relationship between at least one DRB and at least one HARQ entity in each group; The DRB ID of the DRB in each group; The HARQ entity ID corresponding to the mapping of the DRB ID in each group; The HARQ process ID corresponding to the mapping of the DRB ID in each group; The transport block TB ID corresponding to the mapping of the DRB ID in each group; The DRB priority corresponding to the DRB ID in each group; The data mapping rule used to indicate the allocation of the data of each DRB in each group to each HARQ entity.

33. The method according to claim 31, wherein, The mapping relationship between the multiple DRBs and one HARQ entity includes at least one of the following: Different DRBs are mapped to different HARQ processes of one HARQ entity, where the different DRBs are distinguished by the HARQ process IDs under the HARQ entity; Different DRBs are mapped to different TBs of one HARQ entity, where the different DRBs are distinguished by the TB IDs in the HARQ entity; Different DRBs are mapped to different TBs of one HARQ entity, where the different DRBs are distinguished by the HARQ process IDs and the TB IDs under the HARQ entity.

34. The method according to claim 31, wherein, The mapping relationship between one DRB and multiple HARQ entities includes: According to the data mapping rule, the data on the one DRB is allocated to the multiple HARQ entities, where the data mapping rule is used to indicate the allocation of the data of each DRB in each group to each HARQ entity.

35. The method according to claim 30, wherein The third network element sending the mapping information of the DRB and the HARQ entity includes at least one of the following: The third network element directly sends the mapping information of the DRB and the HARQ entity to the first network element, so that when the first network element receives data, it configures the mapping between at least one group of DRBs and HARQ entities and delivers the data received by each HARQ entity included in each group to the upper layer through the DRB mapped to the HARQ entity; The third network element directly sends the mapping information of the DRB and the HARQ entity to the second network element, so that when the second network element transmits data, it configures the mapping between at least one group of DRBs and HARQ entities and delivers a data stream to be sent through one of the groups of DRBs to the HARQ entity mapped to the DRB in the group for sending; The third network element sends the mapping information of the DRB and the HARQ entity to the first network element through the second network element, so that the first network element performs data mapping processing according to the mapping information of the DRB and the HARQ entity during data transmission.

36. The method according to any one of claims 30 to 35, wherein The third network element sending the mapping information of the DRB and the HARQ entity includes: The third network element sends the DRB and HARQ entity mapping information through a seventh control signaling message, where the seventh control signaling message includes at least one of the following: radio resource control (RRC) message, non-access stratum (NAS) message, downlink control information (DCI), and uplink control information (UCI).

37. The method according to claim 36, wherein, The RRC message includes at least one of the following: RRC connection establishment message, RRC configuration message, RRC reconfiguration message, RRC forwarding message, RRC request message, and RRC request response message.

38. The method according to any one of claims 30 to 37, wherein The third network element includes at least one of the following: Radio access network (RAN), user equipment (UE), central unit (CU), distributed unit (DU), relay node, integrated access and backhaul (IAB) node.

39. The method according to claim 35, wherein, The first network element includes at least one of the following: Radio access network (RAN), user equipment (UE), central unit (CU), distributed unit (DU), relay node, integrated access and backhaul (IAB) node.

40. The method according to claim 35, wherein, The second network element includes at least one of the following: Radio access network (RAN), user equipment (UE), central unit (CU), distributed unit (DU), relay node, integrated access and backhaul (IAB) node.

41. A computer-readable storage medium storing a computer program therein, wherein, When the computer program is executed by a processor, it implements the steps of the method described in any one of claims 1 to 13, or implements the steps of the method described in any one of claims 14 to 29, or implements the steps of the method described in any one of claims 30 to 40.

42. An electronic device, comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, where when the processor executes the computer program, it implements the steps of the method described in any one of claims 1 to 13, or implements the steps of the method described in any one of claims 14 to 29, or implements the steps of the method described in any one of claims 30 to 40.

Images