Data transmission method and device, storage medium and electronic device

Abstract

The embodiment of the invention provides a data transmission method and device, a storage medium and an electronic device, and the method comprises the steps that a first network element uses data radio bearer (DRB) and hybrid automatic repeat request (HARQ) entity mapping information to configure at least one group of mapping between DRB and HARQ entities, the mapping information of the DRB and the HARQ entity indicates the mapping relation between the DRB and the HARQ entity in the at least one group, and each group in the at least one group comprises at least one DRB and at least one HARQ entity; and the first network element submits data received by the HARQ entity included in each group to an upper layer through the DRB mapped with the HARQ entity according to the mapping relationship between the DRB and the HARQ entity in at least one group indicated by the DRB and HARQ entity mapping information. Through the data transmission method and device, the problem that differential transmission cannot be carried out on a physical layer in data transmission in related technologies is solved.

Description

Technical Field

[0001] Embodiments of the present invention relate to the field of communications, and in particular, to a data transmission method, apparatus, storage medium, and electronic device. Background Art

[0002] With the increasing richness of wireless communication technology services, the requirements for service differentiation performance guarantee are also getting higher and higher.

[0003] In the data transmission method in the related art, insufficient consideration is given to the differences in service performance. Although at the SDAP (Service Data Adaptation Protocol) layer, data streams with different QoS (Quality of Service) requirements are distinguished by mapping to different DRBs (Data Radio Bearers), at the MAC (Medium Access Control) layer, the data of different DRBs are multiplexed together, and then HARQ (Hybrid Automatic Repeat reQuest) is used to perform physical layer data transmission on the data. Such a data transmission mapping method is too rigid to ensure differential transmission of different data at the physical layer. Summary of the Invention

[0004] Embodiments of the present invention provide a data transmission method, apparatus, storage medium, and electronic device to at least solve the problem that data transmission in the related art cannot perform differential transmission at the physical layer.

[0005] According to an embodiment of the present invention, a data transmission method is provided, including: a first network element configures a mapping between at least one group of DRBs (Data Radio Bearers) and HARQ (Hybrid Automatic Repeat reQuest) entities using DRB and 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 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 at least one group of DRBs and HARQ entities indicated by the DRB and HARQ entity mapping information.

[0006] According to another embodiment of the present invention, there is also provided a data transmission method, including: a second network element configures a mapping between at least one group of data radio bearers (DRBs) and hybrid automatic repeat request (HARQ) entities by using DRB-HARQ entity mapping information, where the DRB-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 to the HARQ entity mapped to the DRB in the group through one group of DRBs according to the mapping relationship between the DRBs and HARQ entities indicated by the DRB-HARQ entity mapping information.

[0007] According to another embodiment of the present invention, there is also provided a data transmission method, including: a third network element configures a mapping between at least one group of data radio bearers (DRBs) and hybrid automatic repeat request (HARQ) entities by using DRB-HARQ entity mapping information, where the DRB-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-HARQ entity mapping information.

[0008] According to another embodiment of the present invention, there is provided a data transmission apparatus applied to a first network element, including: a first configuration module configured to configure a mapping between at least one group of data radio bearers (DRBs) and hybrid automatic repeat request (HARQ) entities by using DRB-HARQ entity mapping information, where the DRB-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; a first sending module configured to hand over 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 indicated by the DRB-HARQ entity mapping information.

[0009] According to another embodiment of the present invention, there is provided a data transmission device, which is applied to a second network element and includes: a second configuration module, configured to configure the mapping between at least one group of data radio bearers (DRBs) and hybrid automatic repeat request (HARQ) entities by using DRB-HARQ entity mapping information, where the DRB-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; a second sending module, configured to send the 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 relationship between the at least one group of DRBs and HARQ entities indicated by the DRB-HARQ entity mapping information.

[0010] According to another embodiment of the present invention, there is provided a data transmission device, which is applied to a third network element and includes: a third configuration module, configured to configure the mapping between at least one group of data radio bearers (DRBs) and hybrid automatic repeat request (HARQ) entities by using DRB-HARQ entity mapping information, where the DRB-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; a third sending module, configured to send the DRB-HARQ entity mapping information.

[0011] According to still another embodiment of the present invention, there is further provided a computer-readable storage medium, in which a computer program is stored, and the computer program is configured to execute the steps in any one of the above method embodiments when running.

[0012] According to still another embodiment of the present invention, there is further provided an electronic device, including a memory and a processor, where a computer program is stored in the memory, and the processor is configured to run the computer program to execute the steps in any one of the above method embodiments.

[0013] Through the present invention, the mapping between DRBs and HARQ entities is configured based on the DRB-HARQ entity mapping information, so that data that needs to be transmitted differentially can be transmitted separately at the physical layer, thereby ensuring the embodiment of the difference in service performance, effectively solving the problem that data transmission in the related art cannot be differentially transmitted 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 capacity and service performance experience. Description of the Drawings

[0014] Figure 1 It is a schematic diagram of the transmission and processing process of a data stream in each layer in the related art;

[0015] Figure 2 It is a schematic structural diagram of the downlink with CA configured in the related art;

[0016] Figure 3 It is a schematic structural diagram of the uplink with CA configured in the related art;

[0017] Figure 4 It is a schematic diagram of the data mapping method in the related art;

[0018] Figure 5 It is a hardware structure block diagram of a mobile terminal for the data transmission method according to an embodiment of the present invention;

[0019] Figure 6 It is the flow of the data transmission method according to an embodiment of the present invention Figure 1 ;

[0020] Figure 7 It is a schematic diagram of mapping one DRB to one HARQ entity in data mapping according to an embodiment of the present invention;

[0021] Figure 8 It is a schematic diagram of the transmission of data packet grouping when mapping one DRB to one HARQ entity according to an embodiment of the present invention;

[0022] Figure 9 It is a schematic diagram of mapping multiple DRBs to one HARQ entity in data mapping according to an embodiment of the present invention;

[0023] Figure 10 It is a schematic diagram of the transmission of data packet grouping when mapping multiple DRBs to one HARQ entity according to an embodiment of the present invention;

[0024] Figure 11 It is a schematic diagram of mapping one DRB to multiple HARQ entities in data mapping according to an embodiment of the present invention;

[0025] Figure 12 It is a schematic diagram of the transmission of data packet grouping when mapping one DRB to multiple HARQ entities according to an embodiment of the present invention;

[0026] Figure 13 It is a schematic diagram of the mapping information of three groups of DRBs and HARQ entities according to an embodiment of the present invention;

[0027] Figure 14 It is the flow of the data transmission method according to an embodiment of the present invention Figure 2 ;

[0028] Figure 15 It is the flow of the data transmission method according to an embodiment of the present invention Figure 3 ;

[0029] Figure 16 Schematic of the RRC message transmission method according to an embodiment of the present invention Figure 1 ;

[0030] Figure 17 Schematic of the RRC message transmission method according to an embodiment of the present invention Figure 2 ;

[0031] Figure 18 Flow chart of the data transmission method according to an embodiment of the present invention Figure 4 ;

[0032] Figure 19 Flow chart of the data transmission method according to an embodiment of the present invention Figure 5 ;

[0033] Figure 20 Structural block diagram of the data transmission device according to an embodiment of the present invention Figure 1 ;

[0034] Figure 21 Structural block diagram of the data transmission device according to an embodiment of the present invention Figure 2 ;

[0035] Figure 22 Structural block diagram of the data transmission device according to an embodiment of the present invention Figure 3 . Detailed implementation manners

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

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

[0038] First, the related technologies involved in the present invention will be described:

[0039] With the development of wireless communication technology, services have become increasingly rich. Currently, the three classic 5G scenarios have presented significantly different service characteristics. The eMBB (Enhanced Mobile Broadband) service features high-speed data transmission with large data packets and high throughput. The URLLC (Ultra-reliable and Low Latency Communications) service requires low service latency and high reliability. The mMTC (Massive Machine Type Communication) service emphasizes the transmission of small data packets with low cost and low energy consumption. In the future, there will also be multi-modal services that integrate multiple service types, such as immersive cloud XR (Extended Reality), multi-dimensional holography, autonomous driving, and industrial Internet, which have higher requirements for ensuring differentiated service performance.

[0040] RB (Radio Bearer) is the general term for a series of protocol entities allocated by the base station for the UE (User Equipment), including a series of resources of each protocol entity. The 5G access network uses the data mapping method of DRB to provide service guarantee, and DRB is the actual transmission channel for user data. From the services provided from the lower layer to the upper layer: The physical layer provides services for the MAC sublayer through the transport channel; the MAC sublayer provides services for the RLC (Radio Link Control) sublayer through the logical channel; the RLC sublayer provides services for the PDCP (Packet Data Convergence Protocol) sublayer through the RLC channel; the PDCP sublayer provides services for the SDAP sublayer through the radio bearer RB, and the SDAP layer provides services for the upper layer through the QoS flow. From the data mapping from the upper layer to the lower layer: The SDAP layer is responsible for the mapping of the QoS flow to the DRB (data radio bearer). QoS flows with different packet forwarding requirements are mapped to different DRBs as a guarantee for differentiating service differences; the PDCP layer is responsible for sorting, header compression, encryption, and integrity protection processing of the upper layer data; the RLC layer performs data segmentation and executes 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 re-segmentation according to the actual resource situation; the MAC layer multiplexes multiple MAC SDUs into a MAC PDU as the physical layer transport block TB (Transport Block) and uses the HARQ mechanism for fast retransmission of data packets. One HARQ entity manages multiple parallel HARQ processes, and the data of different HARQ processes cannot be merged. The TB is the basic unit of HARQ transmission. When there is no spatial multiplexing, one HARQ process can transmit one TB. When there is spatial multiplexing, one HARQ process can transmit at most two TBs. Figure 1 It is a schematic diagram of the data flow transmission and processing process in each layer in the related technology. Figure 2 It is a schematic diagram of the structure of the downlink with configured CA (Carrier Aggregation) in the related technology. Figure 3 It is a schematic diagram of the structure of the uplink with configured CA in the related technology, such as Figure 1As shown in the figure, after multiple layers of processing, the data of RBx and RBy in the radio bearer (RB) are multiplexed into a MAC PDU at the MAC layer and finally mapped to a transport block (TB). When the radio bearer data passes from the PDCP and RLC layers to the MAC layer, a corresponding sub-header of each layer is added. For example, Figure 2 , Figure 3 As shown, the radio bearer data is first mapped to the RLC channel, then from the RLC channel to the logical channel, and then multiplexed and mapped to the HARQ entity through the logical channel scheduling. 5G RAN (Radio Access Network) pays more attention to service provision based on full utilization of resources in data transmission processing, and insufficiently considers the differences in service performance experience. Although data flows with different QoS requirements are distinguished by mapping to different DRBs at the SDAP layer, at the MAC layer, data from different DRBs are multiplexed together again. After the data is multiplexed at the MAC layer, the differences in services cannot be distinguished at the lower layer. The data transmission mapping method of the related technology is too rigid, and it is difficult to improve the performance by ensuring service differentiation at the lower layer, and it is difficult to meet the demand for flexible guarantee of service performance differences.

[0041] In a 5G (NR) wireless network, DRBs are 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 user data packets. One or more QoS flows are mapped to one DRB. Since the radio resources in the wireless communication network are limited, the data of different DRBs are multiplexed at the MAC layer after passing through 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 technology. As Figure 4 shown, in 5G, after being multiplexed at the MAC layer, the DRB is mapped to the HARQ entity. Since the DRB and the HARQ entity cannot be directly mapped, there will be a problem that the mapping relationship between the DRB and the HARQ entity is not clear. Therefore, the network side cannot confirm whether the data transmitted on the same TB comes from one service or multiple services.

[0042] In view of the above problems existing in the related technology, corresponding solutions are proposed in the embodiments of the present invention. The present invention will be described below in conjunction with the embodiments:

[0043] The method embodiments provided in the embodiments of the present application can be executed on a mobile terminal, a computer terminal or a similar computing device. Taking running on a mobile terminal as an example, Figure 5 is a hardware structure block diagram of a mobile terminal for the data transmission method of the embodiments of the present invention. As Figure 5As shown, the mobile terminal may include one or more ( Figure 5 only one is shown in the figure) processors 502 (the processor 502 may include, but is not limited to, a processing device such as a microprocessor MCU or a field programmable gate array FPGA) and a memory 504 for storing data. Among them, the above-mentioned mobile terminal may further include a transmission device 506 for communication functions and an input / output device 508. Those of ordinary skill in the art can understand that Figure 5 the structure shown in the figure is only schematic and does not limit the structure of the above-mentioned mobile terminal. For example, the mobile terminal may further include more or fewer components than Figure 5 shown in the figure, or have a different configuration from Figure 5 shown in the figure.

[0044] The memory 504 can be used 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 embodiments of the present invention. The processor 502 executes various functional applications and data processing by running the computer program stored in the memory 504, that is, implements 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 memories, or other non-volatile solid-state memories. In some instances, the memory 504 may further include a memory remotely set relative to the processor 502, and these remote memories can be connected to the mobile terminal through a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an enterprise intranet, a local area network, a mobile communication network, and their combinations.

[0045] The transmission device 506 is used to receive or send data via a network. Specific examples of the above-mentioned network may include a wireless network provided by a communication provider of the mobile terminal. In one instance, the transmission device 506 includes a network adapter (abbreviated as NIC), which can be connected to other network devices through a base station and thus communicate with the Internet. In one instance, the transmission device 506 may be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

[0046] In an embodiment of the present invention, 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, the network element may be a RAN node (RANNode), the RRC (Radio Resource Control) layer of the RAN, the MAC layer of the RAN, the 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 may include a radio 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), etc. In an embodiment of the present invention, the DRB includes at least one of the following: a communication-related radio bearer, a sensing-related radio bearer, an AI (Artificial Intelligence)-related radio bearer, a data service-related radio bearer, a computing-related radio bearer, and a security / trust-related radio bearer.

[0047] A data transmission method is provided in this embodiment. Figure 6 It is a flowchart of the data transmission method according to an embodiment of the present invention. Figure 1 , as Figure 6 shown, the flowchart includes the following steps:

[0048] Step S602, a first network element configures the mapping between at least one group of DRBs and HARQ entities using data DRB and 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;

[0049] Step S604, the first network element delivers the data received by the HARQ entities included in each group to the upper layer through the DRBs mapped to the HARQ entities 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.

[0050] 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 multiple groups of information on the mapping between HARQ entities and DRBs. For example, the DRB and HARQ entity mapping information includes three groups of information on the mapping between DRBs and HARQ entities: Group1 includes DRB1 and HARQ entity 1, indicating the mapping between DRB1 and HARQ entity 1; Group2 includes DRB2, DRB3, and HARQ entity 2, indicating the mapping between DRB2, DRB3, and HARQ entity 2; Group3 includes DRB4, HARQ entity 3, and HARQ entity 4, indicating the mapping between DRB4 and HARQ entity 3, HARQ entity 4. The first network element delivers the data received by each HARQ entity included in each group to the upper layer through the DRB mapped to the HARQ entity. For example, the data received on HARQ entity 1 is delivered to the upper layer through DRB1, the data received on HARQ entity 2 is delivered to the upper layer through DRB2 and DRB3, and the data received on HARQ entities 3 and 4 is delivered to the upper layer through DRB4.

[0051] Through the above steps, the mapping between the DRB and the HARQ entity is configured based on the DRB and HARQ entity mapping information, so that the data that needs to be transmitted differentially can be transmitted separately at the physical layer and delivered independently to the upper layer at the receiving end, thus ensuring the differentiation of service performance, effectively solving the problem that data transmission in the related art cannot be differentially transmitted 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 enhancing the service transmission capacity and service performance experience.

[0052] In an optional embodiment, the mapping relationship between the DRB and the 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.

[0053] In an optional embodiment, there is no fixed coupling relationship between the DRB and the HARQ entity, and the connection is established through the mapping information of the DRB and the HARQ entity. The DRB and the HARQ entity are generated independently, and flexible mapping is performed through RRC messages or DCI messages. When the network sends changes or the service requirements change, the mapping relationship between the DRB and the HARQ entity allows for flexible changes.

[0054] 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 It is a schematic diagram of the mapping from a DRB to a HARQ entity in the data mapping according to an embodiment of the present invention. As Figure 7 shown, the data flow dataf low1 has an in-sequence delivery requirement, and the data flow dataf low2 has no in-sequence delivery requirement. The one-to-one mapping between the DRB and the HARQ entity maps the data flow dataf low1 with the in-sequence delivery requirement to DRB1; the data flow dataf low2 without the in-sequence delivery requirement is mapped to DRB2. Since DRB1 and DRB2 are respectively mapped one-to-one with HARQ entities 1 and 2, the data flow 1 is transmitted on the HARQ process of HARQ entity 1, and the data flow 2 is transmitted on the HARQ process of HARQ entity 2. There will be no situation where different data flows are mapped to the same HARQ entity, let alone the situation where different data flows are mapped to the same transport block (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 the data with different service requirements can be distinguished in the physical layer transmission, different transmission optimization measures can be taken in the physical layer. For example, for the data flow with the in-sequence delivery requirement, the MCS level can be specifically reduced during physical layer scheduling, and the power can be increased during power control, so as to ensure that the data can be transmitted correctly and in sequence as soon as possible in a short time. Figure 8 It is an example of the transmission schematic diagram of data packet assembly when mapping from a DRB to a HARQ entity according to an embodiment of the present invention. As Figure 8 shown, in the case of the existence of SDAP, PDCP, RLC, and MAC sub-layers, since the DRB can be directly mapped to the MAC layer data, in some cases, there may be no need to add a MAC sub-header even at the MAC layer. Among them, the service characteristics include but are not limited to: data packet in-sequence delivery service indication, data packet non-in-sequence delivery 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, service name identifier.

[0055] In an optional embodiment, the mapping relationship between multiple DRBs and one HARQ entity indicates the mapping of multiple DRBs to one HARQ entity. In a multi-modal service scenario, there are multiple parallel service transmissions between the base station and the UE, and there are association or constraint relationships between these parallel services. For example, in a holographic communication scenario, services such as video service, time-frequency service, tactile service, and taste service need to cooperate and synchronize. Each service corresponds to one DRB, and multiple services use one HARQ entity for transmission, so that the service data of each service 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 TBs of the HARQ process under the same HARQ entity, and 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 only be mapped to different HARQ processes, so that the 2 TBs multiplexed in space 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 multiplexed in space 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 the data with different service requirements can be distinguished in the physical layer transmission, different transmission measures can be taken in the physical layer to ensure service differentiation. Figure 9 It is a schematic diagram of the mapping of multiple DRBs to one HARQ entity in the data mapping according to the embodiment of the present invention. Figure 10 It is a schematic diagram of the transmission of data packet grouping when multiple DRBs are mapped to one HARQ entity according to the embodiment of the present invention. As Figure 10 shown, in the case where there are SDAP, PDCP, RLC, and MAC sublayers, since the DRB can be directly mapped to the MAC layer data, in some cases, there is no need to add a MAC sub-header even at the MAC layer.

[0056] 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 for transmitting a TB, under the same time slot scheduling transmission unit (e.g., slot time slot), the number of TBs that can be transmitted and the TB size are very limited. Without spatial multiplexing, only one TB is transmitted in one slot. With spatial multiplexing, at most two TBs are transmitted in one slot. Considering issues such as coding and interleaving gain and the error rate / retransmission delay caused by an overly large TB size (TBS), the bit size (TB size) of a TB is restricted (e.g., in LTE, it is specified that it cannot be greater than 6144 bits). That is to say, in the related art, only a limited-size TB data of one HARQ process of one HARQ entity can be transmitted in one slot, and it is impossible to simultaneously meet the requirements of low latency, high reliability, and high throughput. In the embodiment of the present invention, multiple HARQ entities are used to transmit the data of a DRB. For services that need to simultaneously meet the requirements of low latency, high reliability, and high throughput, it is allowed to simultaneously transmit data on multiple HARQ entities within one time domain transmission unit. Since the number of HARQ entities available for a DRB increases, it means that the number of TBs that can be transmitted simultaneously increases, and it also means an increase 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, then under spatial multiplexing, at most 2m TBs can be transmitted simultaneously. The more HARQ entities a DRB is mapped to, the more TBs can be transmitted at the same time, thus enabling the data of a service data stream to be transmitted quickly and in large quantities in a very short time. Moreover, when a certain TB transmission fails, it can be retransmitted separately without affecting the transmission of other TB data in the same DRB. Figure 11 It is a schematic diagram of the mapping of a DRB to multiple HARQ entities in the data mapping according to the embodiment of the present invention. Figure 12 It is a schematic diagram of the transmission of data packet grouping when a DRB is mapped to multiple HARQ entities according to the embodiment of the present invention. As Figure 12 shown, in the case where there are SDAP, PDCP, RLC, and MAC sublayers, since the DRB can be directly mapped to the MAC layer data, in some cases, there is no need to add a MAC sub-header at the MAC layer.

[0057] In an optional embodiment, the DRB and HARQ entity mapping information includes at least one of the following: a 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 mapped DRB ID in each group; the HARQ process ID corresponding to the mapped DRB ID in each group; the transport block TB ID corresponding to the mapped DRB ID in each group; the DRB priority corresponding to the DRB ID in each group; a data mapping rule for indicating that the data of each DRB in each group is allocated to each HARQ entity.

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

[0059] For example, the DRB and HARQ entity mapping information may include three groups (it should be noted that only three groups are taken as an example here for illustration. In actual applications, there may be more or fewer groups), corresponding to GroupID1, Group ID2, and Group ID3 respectively. Among them, in the group of Group ID1, it is indicated that DRB1 and HARQ entity 1 are mapped one by one; in the group of Group ID2, it is indicated that both DRB2 and DRB3 are mapped to HARQ entity 2; in the group of Group ID3, it is indicated that DRB4 is mapped to HARQ entity 3 and HARQ entity 4. Optionally, for the HARQ process ID corresponding to the mapped DRB ID in each group, in the case where multiple DRBs are mapped to one HARQ entity, the HARQ process ID can indicate that the data of different DRBs is mapped to different HARQs under the same HARQ entity. Figure 13 It is a schematic diagram of the mapping information of three groups of DRBs and HARQ entities in an embodiment of the present invention, as Figure 13As shown in the figure, for Group ID2, the HARQ process ID information can be increased to indicate that DRB2 is mapped to HARQ processes 1 and 2 of HARQ entity 2, and DRB3 is mapped to HARQ processes 3 and 4 of HARQ entity 2. Optionally, the DRB and HARQ entity mapping information further includes the TB IDs corresponding to the DRB ID mappings within each group to distinguish different DRB data by TB. For example, when the TBs are globally numbered, different TBs correspond to different TB sequence numbers. Only the absolute TB IDs can be used to distinguish different DRB data. Optionally, the DRB and HARQ entity mapping information further includes the HARQ process IDs corresponding to the DRB ID mappings within each group and the TB IDs within the HARQ process IDs for distinction. In spatial multiplexing, one HARQ process can correspond to 2 TBs, and the HARQ process IDs and the TB IDs within the HARQ process IDs can ensure that different DRB data can also be distinguished by TB under spatial multiplexing. Optionally, the DRB and HARQ entity mapping information further includes the DRB priority. Through the indication of the DRB priority corresponding to the data stream, the data streams with high priority can be preferentially scheduled for transmission. 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 DRB with high priority. The B-frame (bi-directional interpolated prediction frame) and P-frame (predictive-frame) are secondary video frames, and the data streams of the B-frame and P-frame are mapped to a DRB with low priority. Then the data stream of the I-frame can be preferentially scheduled during MAC scheduling, and the network can specifically guarantee the physical layer transmission performance for the I-frame data. For example, 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 the data mapping rule, which specifies the method of allocating the data of each DRB to each HARQ entity. For example, for Figure 13 Group ID2, the data mapping rule indicates that DRB2 is mapped to the HARQ processes with odd HARQ Process IDs under HARQ entity 2, and DRB3 is mapped to the HARQ processes with even HARQ Process IDs under HARQ entity 2.

[0060] In an optional embodiment, 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 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 the respective TB IDs under the HARQ entity.

[0061] In the above step, multiple DRBs can be mapped to different processes of the same HARQ entity. In this case, different DRBs can be distinguished by the respective HARQ process IDs under the HARQ entity; in the case of no spatial multiplexing, one HARQ process corresponds to one TB. Since different TBs correspond to different TB sequence numbers when global numbering is performed on the TBs, different DRBs can be distinguished by the respective TB IDs of the HARQ entity. In the case 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 the TB ID.

[0062] 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 a data mapping rule, where the data mapping rule is used to indicate the allocation of the DRB data in each group to each HARQ entity.

[0063] The method for the data mapping rule to indicate the allocation of the DRB data in each group to each HARQ entity is exemplarily described below: For example, for Figure 13 Group ID2, the data mapping rule indicates that DRB2 is mapped to the HARQ processes with odd HARQ Process IDs of HARQ entity 2, and DRB3 is mapped to the HARQ processes with even HARQ Process IDs of HARQ entity 2.

[0064] In an optional embodiment, the first network element configures the mapping between the at least one set of DRBs and HARQ entities using the DRB and HARQ entity mapping information, 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 configures the mapping relationship between the DRB 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 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 HARQ entities; the first network element modifies the mapping relationship between the DRB and HARQ entities using the most recently received target control signaling message, where the target control signaling message includes the most recent DRB and HARQ entity mapping information; the first network element updates the mapping relationship between the DRB and HARQ entities using the most recently received target control signaling message, where the target control signaling message includes the most recent DRB and HARQ entity mapping information; the first network element releases the original mapping relationship between the DRB and HARQ entities of the first network element using the most recently received target control signaling message, where the target control signaling message includes the most recent DRB and HARQ entity mapping information; the first network element sends the mapping information of the DRB and HARQ entities to a second network element using a second control signaling message including the mapping information of the DRB and HARQ entities, so that the second network element sends data according to the mapping information of the DRB and HARQ entities, where the second control signaling information includes at least one of the following: radio resource control (RRC) message, downlink control information (DCI).

[0065] 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), UCI (Uplink Control Information). The first control signaling message includes, but is not limited to, RRC message, NAS message, DCI, UCI.

[0066] In an optional embodiment, the first network element directly receives a target control signaling message including the DRB and HARQ entity mapping information, which 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 that the first network element processes according to the DRB and HARQ entity mapping information after receiving it; 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 that the first network element processes according to the DRB and HARQ entity mapping information after receiving it; 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 that the first network element processes according to the DRB and HARQ entity mapping information after receiving it.

[0067] 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. Among them, the base station sends the mapping information of the DRB and the HARQ entity to the UE (for example, the mapping information is sent to the UE in the RRC message or the DCI message). Since the base station itself can send the mapping information of the DRB and the HARQ entity, it knows the mapping relationship itself. Therefore, the base station can deliver the data received on the HARQ entity to the upper layer 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 (without user plane data transmission), the target control signaling comes from an RRC message or a DCI message of the base station, and the second network element is a base station that only performs data transmission (without 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 to the upper layer 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, 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 does not directly interact with the UE, the RRC message generated by the CU needs to be sent to the UE via the DU.

[0068] In an alternative embodiment, the UE obtains the static mapping information of the DRB and the HARQ entity for data transmission between the UE and the base station B by receiving an RRC message from the base station A. The RRC message contains the mapping information of the DRB and the HARQ entity of the base station B. Then the UE obtains the real-time dynamic mapping information of the DRB and the HARQ entity for data transmission between the UE and the base station B by receiving a DCI message from the base station B. The DCI message contains the real-time mapping information of the DRB and the HARQ entity of the base station B.

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

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

[0071] In an optional embodiment, 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.

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

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

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

[0075] Figure 14 is the flow of the data transmission method according to the embodiments of the present invention Figure 2 , as Figure 14 shown, the flow includes the following steps:

[0076] Step S1402, the second network element configures the mapping between at least one group of DRBs and HARQ entities using the 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;

[0077] Step S1404, 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 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.

[0078] In the above steps, when the second network element configures the mapping relationship between DRBs and HARQ entities, it clearly indicates how each DRB is mapped to each HARQ entity. Suppose there are 3 sets of mapping information (of course, there can be more or fewer sets of mapping information, and here only 3 sets of mapping information are taken as an example for illustration): DRB1 is mapped to HARQ entity 1, DRBs 2 and 3 are mapped to HARQ entity 2, and DRB4 is mapped to HARQ entities 3 and 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. Among them, the services of data flow3 and data flow4 are interrelated. When the second network element sends data flows, according to the configured mapping relationship, it sends data flow1 and data flow2 through DRB1 to the second network element's HARQ entity 1 for transmission, sends data flow3 and data flow4 through DRBs 2 and 3 to the sender's HARQ entity 2 for transmission, and sends data flow5 through DRB4 to the second network element's HARQ entities 3 and 4 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 TBs. There are multiple parallel HARQ processes in each HARQ entity to support the TB transmission under the DRB.

[0079] Through the above steps, the mapping between DRBs and HARQ entities can be configured based on the DRB and HARQ entity mapping information, and data with different service characteristics can be transmitted according to requirements, so that the data transmission can flexibly meet the underlying transmission requirements of different services, and has a great effect on improving the service transmission capacity and service performance experience.

[0080] In an optional embodiment, the mapping relationship between each group of DRBs and HARQ entities 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.

[0081] In an optional embodiment, the DRB-HARQ entity mapping information includes at least one of the following: a 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 mapped DRB ID in each group; the HARQ process ID corresponding to the mapped DRB ID in each group; the transport block TB ID corresponding to the mapped DRB ID in each group; the DRB priority corresponding to the DRB ID in each group; a data mapping rule for indicating that the data of each DRB in each group is allocated to each HARQ entity.

[0082] In an optional embodiment, 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.

[0083] 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 a data mapping rule, where the data mapping rule is used to indicate the allocation of the data of each DRB in each group to each HARQ entity.

[0084] In an optional embodiment, the second network element configures the mapping between the at least one set of DRBs and HARQ entities 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 the HARQ entity 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 the HARQ entity; the second network element modifies the mapping relationship between the DRB and the HARQ entity using the latest received third control signaling message, where the third control signaling message includes the latest DRB and HARQ entity mapping information; the second network element updates the mapping relationship between the DRB and the HARQ entity using the latest received third control signaling message, where the third control signaling message includes the latest DRB and HARQ entity mapping information; the second network element releases the original mapping relationship between the DRB and the HARQ entity of the second network element using the latest received third control signaling message, where the third control signaling message includes the latest DRB and HARQ entity mapping information.

[0085] In an optional embodiment, the second network element receiving the third control signaling message including the DRB and HARQ entity mapping information includes 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 a first network element, where 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 a third network element, where 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, where 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.

[0086] In an optional embodiment, the method further 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, where the first network element is the network element that receives the data of the second network element.

[0087] In the above step, 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, and 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 the DRB for data reception and upward delivery.

[0088] 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 (for example, the sixth control signaling message is an RRC request message, a UCI message) to the base station. 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, a DCI message).

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

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

[0091] 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, an RRC request response message.

[0092] In an optional embodiment, the second network element hands over a data stream to be sent through a set of DRBs to the HARQ entity mapped to the DRB in the set, 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 through different DRBs for sending.

[0093] In the above steps, data flows with different service characteristics can be sent by different DRBs to the corresponding mapped HARQ entities. The following is an example of this sending method: Assume that data flow1 and data flow2 have the same service characteristics, and data flow3 and data flow4 have different service characteristics. Transmit data flow1 and data flow2 through DRB1, and transmit data flow3 and data flow4 through DRB2 and DRB3 respectively. The methods for the second network element to obtain the service characteristics include but are 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 carried along with the data flow to obtain service characteristic information, obtaining service characteristic information through DPI (Deep Packet Inspection), obtaining service characteristic information through AI (Artificial Intelligence) inference, and obtaining service characteristic information through big data analysis.

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

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

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

[0097] Figure 15 is the flow of the data transmission method according to the embodiment of the present invention Figure 3 , as Figure 15 shown, this flow includes the following steps:

[0098] Step S1502, the third network element configures the mapping between at least one group of DRBs and HARQ entities using the DRB and 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;

[0099] Step S1504, the third network element sends the DRB and HARQ entity mapping information.

[0100] Through the above steps, the mapping between the DRB and the HARQ entity can be configured based on the DRB and HARQ entity mapping information, so that the data that needs to be transmitted differentially can be transmitted separately at the physical layer, thus ensuring the differentiation of service performance, effectively solving the problem that in the related art, the data of different DRBs cannot be differentially transmitted at the physical layer when the data of different DRBs are multiplexed together at the MAC 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 capacity and service performance experience.

[0101] In an optional embodiment, the mapping relationship between the DRB and the 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.

[0102] In an optional embodiment, the DRB and HARQ entity mapping information 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 mapped DRB ID in each group; the HARQ process ID corresponding to the mapped DRB ID in each group; the transport block TB ID corresponding to the mapped DRB ID in each group; the DRB priority corresponding to the DRB ID in each group; the data mapping rule for indicating the allocation of the data of each DRB in each group to each HARQ entity.

[0103] In an optional embodiment, 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 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 TB IDs under the HARQ entity.

[0104] 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 rule, where the data mapping rule is used to indicate the allocation of the data of each DRB in each group to each HARQ entity.

[0105] In an optional embodiment, the third network element sending the DRB and HARQ entity mapping information includes 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 when the first network element receives data, it configures the mapping between at least one set of DRBs and HARQ entities and delivers the data received by each HARQ entity included in each set to the upper layer through the DRB mapped to the HARQ entity according to the mapping between the at least one set 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 when the second network element transmits data, it configures the mapping between at least one set of DRBs and HARQ entities and delivers a data stream to be transmitted through one set of DRBs in the set to the HARQ entity mapped to the DRB in the set for transmission according to the mapping between the at least one set 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 during data transmission.

[0106] In an optional embodiment, the third network element sending the DRB and HARQ entity mapping information 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: RRC message, NAS message, DCI, UCI.

[0107] In an optional embodiment, 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.

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

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

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

[0111] Next, an exemplary description of the application of the target control signaling message in the above steps is given: The radio resource control message, i.e., the RRC (Radio Resource Control) message, is a control signaling message exchanged between the base station and the UE, and is generated by the base station RRC layer in both 4G / 5G systems. The RRC establishment message is used to establish an RRC connection when the UE is in the non-connected state (for example, when the UE is in the RRC idle state RRC_IDLE). The RRC establishment message includes the RRC establishment request message sent by the UE to the base station (such as the RRCSetupRequest message, the RRCReestablishmentRequest message) and the RRC establishment message sent by the base station to the UE (for example, the RRCSetup message). After the UE establishes an RRC connection, it will send an RRC establishment complete message (for example, the 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 complete 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 the 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 RRCReconfigurationmessage. The base station can include DRB and HARQ entity mapping information in the RRC reconfiguration message and send it to the UE. After the UE receives the RRC reconfiguration message including the DRB and HARQ entity mapping information, it 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 the mapping association of each DRB and each HARQ entity on the UE side according to the DRB and HARQ entity mapping information.For example, the UE receives an RLC-BearerConfig IE carrying 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.

[0112] The 5G base station can be split into two parts: CU and DU. CU is the centralized unit of the base station, and DU is the distributed part of the base station. The CU and DU interact through the F1 interface. The physical high layer, MAC, and RLC layers with high real-time requirements are processed in the DU, while the PDCP and RRC layers with low real-time requirements are processed in the CU. When the CU and DU are not integrated, 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 transmits 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 the 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 in the RRC message of the CU, the DU places 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 in the RRC message of the CU, the DU places the data received on the HARQ entity on the mapped DRB and submits it to the upper layer.

[0113] For the scenario of CU and DU separated deployment, after the UE sends an RRC connection establishment request, the DU sends a forwarding message of the UE RRC establishment request message (for example, Initial UL RRC Message Transfer) to the CU to forward the initial uplink RRC message from the DU to the control plane (CU-CP) of the CU. The CU allocates radio resources for the UE by sending a forwarding message of the downlink RRC message (DL RRC Message Transfer) to the DU. Figure 16 It is a schematic diagram of the RRC message transmission method according to an embodiment of the present invention Figure 1 as Figure 16 shown, it can be seen that the DU plays a role in forwarding RRC messages between the CU and the UE. In the embodiment of the present invention, 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.

[0114] In 5G, the base station uses Downlink Control Information (DCI) to provide the terminal with control information such as physical resource allocation, power control, and Hybrid Automatic Repeat reQuest (HARQ) for uplink and downlink scheduling. DCI can be transmitted to the User Equipment (UE) on the Physical Downlink Control Channel (PDCCH) or the Physical Downlink Shared Channel (PDSCH). In 5G, the UE uses Uplink Control Information (UCI) to provide the base station with control information such as uplink scheduling information, HARQ feedback, and channel measurement. UCI can be transmitted to the base station on the Physical Uplink Control Channel (PUCCH) or the Physical Uplink Shared Channel (PUSCH). The static or semi-static configuration between the base station and the UE is generally completed through Radio Resource Control (RRC) messages, and the dynamic configuration between the base station and the UE is generally completed through DCI and UCI. The static / semi-static configuration of the Data Radio Bearer (DRB) and HARQ entity mapping information can be first performed using RRC messages, and then the dynamic configuration of the DRB and HARQ entity mapping information can be performed using DCI and / or UCI according to the dynamic changes of the network and services. Optionally, the UE sends the requirements for the DRB and HARQ entity mapping information through UCI, and the base station sends the DRB and HARQ entity mapping information to the UE through DCI after receiving the requirements. For downlink transmission, the base station configures the DRB and HARQ entity mapping information and performs downlink data transmission according to the mapping information. The UE receives the relationship information of the DRB and HARQ entity mapping and performs downlink data reception and up-link delivery of downlink data according to the mapping relationship. For uplink transmission, the base station configures the relationship information of the DRB and HARQ entity mapping and sends it to the UE. The UE receives the relationship information of the DRB and HARQ entity mapping and performs uplink data transmission according to the mapping information, and the base station receives uplink data according to the mapping information. Regardless of downlink 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 entities. The base station sends the DRB and HARQ entity mapping information to the UE through messages such as 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 at the time of RRC establishment, or send the DRB and HARQ entity mapping information through the RRC reconfiguration message after RRC establishment. When the base station needs to change the mapping relationship of the DRB and HARQ entities in real time, the DRB and HARQ entity mapping information is sent through DCI.RRC messages are used for the configuration of static or semi-static mapping of DRB and HARQ entities in the network, and DCI messages are used for the configuration of dynamic and real-time mapping of DRB and HARQ entities in the network. After the UE receives the DRB and HARQ entity mapping information, it determines the DRB mapped to each HARQ entity on the receiving side according to the mapping information, and delivers the data upward through the DRB. When the UE is in the non-connected state, the DRB and HARQ entity mapping information is configured through the RRC connection establishment message. Optionally, the UE first sends an RRC connection request including a request for DRB and HARQ entity mapping information, and then receives an RRC connection establishment message including the DRB and HARQ entity mapping information to obtain the DRB and HARQ entity mapping information for mapping configuration. When the UE is in the connected state, the UE can use the 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 the DCI. Optionally, when the UE needs to change the mapping relationship between the DRB and the HARQ entity, the UE can also actively initiate a dynamic configuration request message of the DRB and HARQ entity mapping information through the UCI, and then the base station initiates the dynamic configuration information of the DRB and HARQ entity mapping information to the UE through the DCI. Optionally, the dynamic configuration request message of the DRB and HARQ entity mapping information actively initiated by the UE includes the UE's request and suggestion information for the mapping of one to multiple groups of DRB and HARQ entities. For example, 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 transfer the long-period DRB and HARQ entity mapping information, including: the group ID of the mapping relationship between the DRB and the HARQ entity, the DRB ID within each group, the HARQ entity ID corresponding to the DRB ID mapping within each group, the priority of each DRB within each group, and the data mapping rule for allocating the data of each DRB to each HARQ entity. The DCI message is used to transfer the short-period or dynamically changing DRB and HARQ entity mapping information based on the mapping relationship transferred by the RRC message, including: the HARQ process ID corresponding to the DRB ID mapping within each group; the TB ID corresponding to the DRB ID mapping within each group.

[0115] 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 perform mapping configuration on the DRB and HARQ entity on the UE side. After receiving the DCI message, the UE obtains the mapping information between DRB and HARQ entity from the DCI message and performs mapping configuration on each DRB and each HARQ entity on the UE side according to the mapping information between DRB and HARQ entity. Optionally, the mapping configuration actions include but are not limited to: establishing a mapping relationship between DRB and HARQ entity, modifying the mapping relationship between DRB and HARQ entity, releasing the mapping relationship between DRB and HARQ entity, and replacing the original mapping relationship between DRB and HARQ entity on the UE side with a new mapping relationship between DRB and HARQ entity.

[0116] In an optional embodiment, the base station uses a DCI message to send the latest mapping information between DRB and HARQ entity to the UE, instructing the UE to modify the mapping between DRB and HARQ entity on the UE side. After receiving the DCI message, the UE obtains the latest mapping information between DRB and HARQ entity 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 DRB and HARQ entity.

[0117] 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.

[0118] In an optional embodiment, the base station sends the latest mapping information between DRB and HARQ entity to the UE using a DCI message, instructing the UE to delete (or release) the original mapping relationship between DRB and HARQ entity on the UE side. After receiving the DCI message, the UE obtains the latest mapping information between DRB and HARQ entity 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 DRB and HARQ entity.

[0119] 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 of the DRB and the HARQ entity according to 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 of the DRB and the HARQ entity.

[0120] In an optional embodiment, the UE may request the mapping information of the DRB and the HARQ entity from the base station through the UCI. For example, request to establish a mapping relationship between DRB1, DRB2 and HARQ entity 1. For example, request to release the mapping relationship between DRB1, DRB2 and HARQ entity 1. For example, request to change the mapping relationship from the mapping of DRB1, DRB2 and HARQ entity 1 to the mapping of 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 DRB and HARQ entity.

[0121] The following is an example of the data mapping process of DRB and HARQ entity mapping information in the scenario of separation of control and forwarding: In the scenario of separation of control signaling and data transmission, 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 schematic diagram of an RRC message transmission method according to an embodiment of the present invention Figure 2 In this scenario, the control base station is responsible for the transmission of RRC messages, 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. For the networking scenario of macro base stations and micro base stations, the coverage of macro base stations is large. 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 the UE connected to the macro base station, but also provides RRC control signaling for the UE connected to the micro base station. The macro base station provides an indication of DRB and HARQ entity mapping to the micro base station and the UE connected to the micro base station by sending an RRC message including DRB and HARQ entity mapping information corresponding to the micro base station-micro base station serving UE.

[0122] Next, in combination with specific embodiments, the method of this solution will be described as a whole:

[0123] Figure 18 It is the flow of the data transmission method according to the embodiment of the present invention Figure 4 , and the processing steps of the data receiving end are as follows:

[0124] Step S1802, obtain the mapping information between the HARQ entity and the DRB;

[0125] Step S1804, configure the mapping of one to multiple HARQ entities and one to multiple DRBs according to the mapping information between the HARQ entity and the DRB;

[0126] Step S1806, each HARQ entity receives TB data of multiple processes and performs physical layer decoding;

[0127] Step S1808, the data of each HARQ entity is delivered to the upper layer through the DRB mapped by the HARQ entity.

[0128] In the above steps, the methods for obtaining the mapping information between the HARQ entity and the DRB include but are 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, the mapping information is sent through an RRC reconfiguration message, and the DCI information is dynamically indicated through a PDCCH to send the mapping information, etc.

[0129] Figure 19 It is the flow of the data transmission method according to the embodiment of the present invention Figure 5 , and the processing steps of the data transmitting end are as follows:

[0130] Step S1902, obtain the service characteristic information of the data stream;

[0131] Step S1904, map data streams with different same service characteristic requirements to different DRBs according to the service characteristic information;

[0132] Step S1906, obtain the mapping information between the HARQ entity and the DRB;

[0133] Step S1908, configure the mapping of one to multiple HARQ entities and one to multiple DRBs for each transmitting end according to the mapping information between the HARQ entity and the DRB;

[0134] Step S1910, map one to multiple DRBs to one to multiple HARQ entities according to the mapping information between the HARQ entity and the DRB;

[0135] Step S1912, configure multi-process TB transmission for each HARQ entity.

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

[0137] Taking the second network element as the base station and the first network element as the UE as an example, the processing operations on each network element side are exemplarily described below.

[0138] Specific Embodiment 1: Data Mapping Process on the Base Station Side during Downlink Transmission

[0139] When the base station sends data to the UE, the base station configures the relationship information of the mapping between the DRB and the HARQ entity and sends the data according to the mapping information. And the base station informs the UE of the relationship information of the mapping between the DRB and the HARQ entity through RRC messages (such as RRC connection establishment messages, RRC reconfiguration messages).

[0140] Among them, the specific steps on the base station side as the transmitting end during downlink transmission are exemplified as follows:

[0141] Step 1: The base station maps data streams with different service characteristic information to different DRBs.

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

[0143] Among them, when the base station configures the relationship of the mapping between the DRB and the HARQ entity, it clearly indicates how the DRB and the HARQ entity are mapped. 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 the HARQ entity are mapped. Optionally, the DRB and HARQ entity mapping information may have multiple sets of mapping relationship indications, and each set of DRB and HARQ entity mapping relationships may 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: 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 for indicating that the data of each DRB in each group is allocated to each HARQ entity.

[0144] Step 3: The base station delivers the data to be transmitted to the HARQ entity for transmission through the DRB according to the configured mapping relationship between the DRB and the HARQ entity. Optionally, in Step 3, when transmitting data, the base station may transmit different service data on different TBs according to the configured mapping relationship. For example, in the mapping from 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 to one TB will not occur. For example, in the mapping from 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 to one TB. Optionally, in spatial multiplexing, one HARQ process can transmit 2 TBs, and information on the HARQ process ID and the TB ID can also be added to the mapping relationship information when configuring the mapping relationship to clearly indicate that the data streams on different DRBs are mapped to different TBs of the same HARQ entity. For example, in the mapping from one DRB to multiple HARQ entities, the data stream on one DRB can be mapped to the TBs of different HARQ entities. Since different service data can be distinguished at the physical layer, the base station can adopt different physical layer transmission means for different service data during transmission. For example, reducing the MCS level for the TB transmission of high-reliability data streams and increasing the transmission power for the time slots of high-reliability data stream transmission, etc.

[0145] Step 4: The base station updates the mapping relationship between the DRB and the HARQ entity according to the change in service requirements and sends the update of the mapping relationship to the UE through DCI. For example, the mapping information of the changed DRB and HARQ entity is transmitted through DCI, enabling the UE to adapt to the change in service requirements in real time.

[0146] It can be seen from this that in this embodiment, data streams with different service characteristic requirements can be mapped to different DRBs through classification, and then the DRBs are mapped to the HARQ entity in a flexible mapping manner to realize the association between the service and the HARQ entity and the distinction of different data streams on the TB. Through this embodiment, differential transmission of service data is realized, especially the clear distinction and personalized guarantee of service differentiation in physical link transmission.

[0147] Specific Embodiment 2: Data Mapping Process on the UE Side during Downlink Transmission

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

[0149] The specific steps when the UE is the receiving end during downlink transmission are exemplified as follows:

[0150] Step 1 (It should be noted that this step is an optional step, and in actual applications, it is also possible to skip Step 1 and directly execute the subsequent steps): The UE sends a request message carrying a request for DRB and HARQ entity mapping information. The request message sent by the UE can be an RRC establishment request (RRC Setup Request) message, an RRC configuration request message, or UCI.

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

[0152] By receiving the message containing DRB and HARQ entity mapping information, the UE can know which DRB each TB corresponding to each HARQ process under each HARQ entity corresponds to, and then deliver the downlink data to the upper layer through the mapped DRB. Optionally, the DRB and HARQ entity mapping information can have multiple sets of mapping relationship indications, and each set of DRB and HARQ entity mapping relationships 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: 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 mapped by the DRB ID in each group; the HARQ process ID mapped by the DRB ID in each group; the transport block TB ID mapped by the DRB ID in each group; the DRB priority corresponding to the DRB ID in each group; the data mapping rule for allocating the data of each DRB in each group to each HARQ entity. Optionally, the base station sends the DRB and HARQ entity mapping information in an RRC connection establishment message (RRC Setup message) or an RRC reconfiguration message to the UE, and the UE obtains the mapping information by receiving the above RRC message. Optionally, the base station sends the DRB and HARQ entity mapping information in DCI to the UE, and the UE obtains the mapping information by receiving the above DCI message.

[0153] Step 3: According to the information on the mapping between the DRB and the HARQ entity in the DRB-HARQ entity mapping information, the UE delivers the TB data received by the HARQ entity to the upper layer through the DRB.

[0154] The DRB-HARQ entity mapping information may include multiple sets of information on the mapping between the HARQ entity and the DRB.

[0155] It can be seen that by receiving the DRB-HARQ entity mapping information, the UE can know how to independently deliver the received data to the upper layer.

[0156] Specific Embodiment 3: Data Mapping Process on the UE Side during Uplink Transmission

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

[0158] Among them, the specific steps on the UE side as the transmitting end during uplink transmission are exemplified as follows:

[0159] Step 1: The UE sends an RRC request message for the DRB-HARQ entity mapping information, such as the UE requests to configure the HARQ entity for the DRB of 4 uplink data streams. (It should be noted that this step is an optional step, and in actual execution, this step can be skipped to directly execute Step 2)

[0160] Step 2: The UE receives an RRC configuration message sent by the base station, which contains DRB and HARQ entity mapping information. The RRC configuration message can be an RRC reconfiguration message or an RRC request response message. The DRB and HARQ entity mapping information can have multiple sets of mapping relationship indications, and each set of DRB and HARQ entity mapping relationships can be one-to-one, one-to-many, or many-to-one. The DRB and HARQ entity mapping information can include 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 TBID 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 for indicating that the data of each DRB in each group is allocated to each HARQ entity. Optionally, Step 2 can 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 for the UE's uplink data transmission.

[0161] Step 3: The UE maps data streams with different service characteristic information to different DRBs.

[0162] Step 4: According to the configured mapping relationship between the DRB and the HARQ entity, the UE delivers the data to be sent to the HARQ entity through the DRB for transmission.

[0163] Step 5: The UE sends, through UCI, to the base station the recommended information on the change of the mapping relationship between the DRB and the HARQ entity according to the uplink service requirements. (It should be noted that this step is an optional step)

[0164] Since the physical layer at the transmitting end can distinguish data of different services, different physical layer transmission means can be adopted for different service data. For example, the MCS level is reduced for the TB transmission of high-reliability data streams, and the transmission power is increased for the time slots of high-reliability data stream transmissions.

[0165] It can be seen that in this embodiment, data streams with different service characteristic requirements can be mapped to different DRBs through classification, and then the DRBs are mapped to the HARQ entities in a flexible mapping manner to realize the association between the services and the HARQ entities and the differentiation of different data streams on the TB. Through this embodiment, the differential transmission of service data is realized, especially the clear differentiation and personalized guarantee of service differentiation in the physical link transmission.

[0166] Specific Embodiment 4: Data Mapping Process on the Base Station Side during Uplink Transmission

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

[0168] Among them, the specific steps when the base station side is the receiving end during uplink transmission are exemplified as follows:

[0169] Step 1: The base station receives the RRC request message of the DRB and HARQ entity mapping information sent by the UE. For example, the UE requests to configure the HARQ entity for the DRB of 4 uplink data streams.

[0170] Step 2: The base station sends an RRC configuration message containing the 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, in the RRC reconfiguration message sent by the base station containing the DRB and HARQ entity mapping information, the mapping relationship of one or more groups of DRBs and HARQ entities is indicated.

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

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

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

[0174] 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 by service. Through this embodiment, differential transmission of service data is achieved, especially in the physical link transmission, clear distinction and personalized guarantee of service differentiation are realized.

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

[0176] In this embodiment, a data transmission device is further provided. This device is used to implement the above embodiments and preferred implementation manners, and those that have been described will not be repeated. As used below, the term "module" can be a combination of software and / or hardware that can achieve a predetermined function. Although the devices described in the following embodiments are preferably implemented in software, implementation in hardware, or a combination of software and hardware is also possible and contemplated.

[0177] Figure 20 is the structural block diagram of the data transmission device according to the embodiment of the present invention Figure 1 , as Figure 20 shown, this device is applied to the first network element and includes: a first configuration module 202, configured to configure the mapping between at least one group of DRBs and HARQ entities by 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; a first sending module 204, configured to submit 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 at least one group of DRBs and HARQ entities indicated by the DRB and HARQ entity mapping information.

[0178] In an optional embodiment, the mapping relationship between the DRB and the 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.

[0179] In an optional embodiment, the DRB and HARQ entity mapping information includes at least one of the following: a 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 mapped DRB ID in each group; the HARQ process ID corresponding to the mapped DRB ID in each group; the transport block TB ID corresponding to the mapped DRB ID in each group; the DRB priority corresponding to the DRB ID in each group; a data mapping rule for indicating that the data of each DRB in each group is allocated to each HARQ entity.

[0180] In an optional embodiment, 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.

[0181] 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 a data mapping rule, where the data mapping rule is used to indicate the allocation of the data of each DRB in each group to each HARQ entity.

[0182] 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 mapping information of the DRB and the HARQ entity, and configure the mapping relationship between the DRB and the HARQ entity by using the target control signaling message; a first sending unit, configured to first send a first control signaling message including a request for the mapping information of the DRB and the HARQ entity, and then receive a target control signaling message including the mapping information of the DRB and the HARQ entity to configure the mapping relationship between the DRB and the HARQ entity; a first modifying unit, configured to modify the mapping relationship between the DRB and the HARQ entity by using the most recently received target control signaling message, where the target control signaling message includes the most recent mapping information of the DRB and the HARQ entity; a first updating unit, configured to update the mapping relationship between the DRB and the HARQ entity by using the most recently received target control signaling message, where the target control signaling message includes the most recent mapping information of the DRB and the HARQ entity; a first releasing unit, configured to release the original mapping relationship between the DRB and the HARQ entity of the first network element by using the most recently received target control signaling message, where the target control signaling message includes the most recent mapping information of the DRB and the HARQ entity; a second sending unit, configured to send the mapping information of the DRB and the HARQ entity to a second network element by using a second control signaling message including the mapping information of the DRB and the HARQ entity, so that the second network element sends data according to the mapping information of the DRB and the HARQ entity, where the second control signaling information includes at least one of the following: a radio resource control (RRC) message, a downlink control information (DCI).

[0183] 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, where the second network element is a network element that directly sends data to the first network element, and the data is data that is processed by the first network element according to the mapping information of the DRB and the HARQ entity after being received; a second sub-receiving unit, configured to receive 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 data that is processed by the first network element according to the mapping information of the DRB and the HARQ entity 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, 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 data that is processed by the first network element according to the mapping information of the DRB and the HARQ entity after being received.

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

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

[0186] In an optional embodiment, 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.

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

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

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

[0190] Figure 21 is the structural block diagram of the data transmission device according to the embodiment of the present invention Figure 2 , as Figure 21 shown, the device is applied to the second network element and includes: a second configuration module 212, configured to configure 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; a second sending module 214, configured to send the 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 relationship between the at least one group of DRBs and HARQ entities indicated by the DRB and HARQ entity mapping information.

[0191] In an optional embodiment, the mapping relationship between the DRB and the 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.

[0192] In an optional embodiment, the DRB and HARQ entity mapping information includes at least one of the following: a 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 mapped DRB ID in each group; the HARQ process ID corresponding to the mapped DRB ID in each group; the transport block TB ID corresponding to the mapped DRB ID in each group; the DRB priority corresponding to the DRB ID in each group; a data mapping rule for indicating the allocation of the data of each DRB in each group to each HARQ entity.

[0193] In an optional embodiment, 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.

[0194] 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 a data mapping rule, where the data mapping rule is used to indicate the allocation of the data of each DRB in each group to each HARQ entity.

[0195] 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 configure the mapping relationship between the DRB and the HARQ entity using the third control signaling message; 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 the 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 mapping relationship between the DRB and the HARQ entity using the latest received third control signaling message, where the third control signaling message includes the latest DRB and HARQ entity mapping information; a second updating unit, configured to update the mapping relationship between the DRB and the HARQ entity using the latest received third control signaling message, where the third control signaling message includes the latest DRB and HARQ entity mapping information; a second releasing unit, configured to release the original mapping relationship between the DRB and the HARQ entity of the second network element by using the latest received third control signaling message, where the third control signaling message includes the latest DRB and HARQ entity mapping information.

[0196] 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 a first network element, where 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 a third network element, where 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, where 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.

[0197] In an optional embodiment, the apparatus further comprises: a fourth sending module, configured to send a fifth control signaling message including the DRB and HARQ entity mapping information to a first network element, so that the first network element receives data of 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: an RRC message, a downlink control information DCI.

[0198] In an optional embodiment, the apparatus further comprises: 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: an RRC message, an uplink control information UCI.

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

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

[0201] 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, an RRC request response message.

[0202] In an optional embodiment, the second sending module 214 comprises: 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 different DRBs to the corresponding mapped HARQ entities.

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

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

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

[0206] Figure 22 is the structural block diagram of the data transmission apparatus according to the embodiment of the present invention Figure 3, such as Figure 22 As shown, the device is applied to a third network element and includes: a third configuration module 222, configured to configure the mapping between at least one set of data radio bearers (DRBs) and hybrid automatic repeat request (HARQ) entities using DRB and HARQ entity mapping information, where the DRB and 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; a third sending module 224, configured to send the DRB and HARQ entity mapping information.

[0207] In an optional embodiment, the mapping relationship between the DRBs and HARQ entities 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.

[0208] 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 each DRB in each group; the HARQ entity ID corresponding to the mapped DRB ID in each group; the HARQ process ID corresponding to the mapped DRB ID in each group; the transport block (TB) ID corresponding to the mapped DRB ID in each group; the DRB priority corresponding to the DRB ID in each group; a data mapping rule for indicating the distribution of the data of each DRB in each group to each HARQ entity.

[0209] In an optional embodiment, 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 TB IDs under the HARQ entity.

[0210] 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 a data mapping rule, where the data mapping rule is used to indicate the distribution of the data of each DRB in each group to each HARQ entity.

[0211] 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 a first network element, so that when the first network element receives data, it configures the mapping between at least one set of DRBs and HARQ entities and delivers the data received by each HARQ entity included in each set to the upper layer through the DRB mapped to the HARQ entity; a fifth sending unit, configured to directly send the DRB and HARQ entity mapping information to a second network element, so that when the second network element transmits data, it configures the mapping between at least one set of DRBs and HARQ entities and delivers a data stream to be sent through one set of DRBs to the HARQ entity mapped to the DRB in the set for sending; 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.

[0212] 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, where the seventh control signaling message includes at least one of the following: an RRC message, an NAS message, a DCI, a UCI.

[0213] 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, an RRC request response message.

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

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

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

[0217] It should be noted that the above-mentioned various modules can be implemented by software or hardware. For the latter, it can be implemented in the following ways, but not limited thereto: the above-mentioned modules are all located in the same processor; or, the above-mentioned various modules are separately located in different processors in any combination form.

[0218] An embodiment of the present invention also provides a computer-readable storage medium, in which a computer program is stored, and the computer program is configured to execute the steps in any one of the above method embodiments when running.

[0219] In an exemplary embodiment, the above computer-readable storage medium may include, but is not limited to: various media that can store computer programs such as USB flash drives, read-only memories (ROM for short), random access memories (RAM for short), mobile hard disks, magnetic disks, or optical discs.

[0220] An embodiment of the present invention also provides an electronic device, including a memory and a processor. A computer program is stored in the memory, and the processor is configured to run the computer program to execute the steps in any one of the above method embodiments.

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

[0222] Specific examples in this embodiment may refer to the examples described in the above embodiments and exemplary embodiments, and will not be repeated here.

[0223] Obviously, those skilled in the art should understand that the above modules or steps of the present invention can be implemented by a general-purpose computing device. They can be concentrated on a single computing device or distributed on a network composed of multiple computing devices. They can be implemented by program codes executable by the computing device, so that 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 executed in a different order from here, or they can be separately made into individual integrated circuit modules, or multiple modules or steps among them can be made into a single integrated circuit module to implement. In this way, the present invention is not limited to any specific combination of hardware and software.

[0224] The above is only the preferred embodiment of the present invention and is not used to limit the present invention. For those skilled in the art, the present invention can have various changes and modifications. Any modification, equivalent replacement, improvement, etc. made within the principle of the present invention shall be included in the protection scope of the present invention.

Claims

1. A data transmission method, characterized in that, Comprising: The first network element configures the mapping between at least one group of data radio bearers (DRBs) and hybrid automatic repeat request (HARQ) entities using 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 first network element delivers the data received by the HARQ entities included in each group 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 and HARQ entity mapping information.

2. The method according to claim 1, characterized in that, The mapping relationship between the DRBs and HARQ entities 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.

3. The method according to claim 1 or 2, characterized in that, 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 corresponding to the mapped DRB ID in each group; The HARQ process ID corresponding to the mapped DRB ID in each group; The transport block (TB) ID corresponding to the mapped DRB ID in each group; The DRB priority corresponding to the DRB ID in each group; The data mapping rule used to indicate 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 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 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, characterized in that, The first network element configures the mapping between the at least one group of DRBs and HARQ entities using the DRB and HARQ entity mapping information includes 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 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 of the DRB and the HARQ entity, and then receives a target control signaling message including the mapping information of 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 of 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 of 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 of the DRB and the HARQ entity; The first network element sends the mapping information of the DRB and the HARQ entity to the second network element using a second control signaling message including the mapping information of the DRB and the HARQ entity, so that the second network element sends data according to the mapping information of 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 of the DRB and the HARQ entity includes at least one of the following: The first network element receives the target control signaling message from the 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 of the DRB and the HARQ entity after receiving it; The first network element receives the target control signaling message from the 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 of the DRB and the HARQ entity after receiving it; 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 of the DRB and the HARQ entity after receiving it.

8. The method according to claim 6 or 7, characterized in that, 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, characterized in that, 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, characterized in that, 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, characterized in that, 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, characterized in that, Includes: 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, 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 second network element, 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, 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.

15. The method according to claim 14, characterized in that, 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, characterized in that 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 DRB in each group; The HARQ entity ID corresponding to the mapped DRB ID in each group; The HARQ process ID corresponding to the mapped DRB ID in each group; The transport block (TB) ID corresponding to the mapped 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, 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 TB IDs under the HARQ entity.

18. The method according to claim 15, characterized in that, The mapping relationship between 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, characterized in that, The second network element configures the mapping between the DRB and the HARQ entity of 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 the HARQ entity 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 the HARQ entity; The second network element modifies the mapping relationship between the DRB and the HARQ entity 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 the HARQ entity 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 the HARQ entity 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, characterized in that, The second network element receives a 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 a 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 a 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 a network element that directly receives the data from the second network element, the third network element is a 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.

21. The method according to any one of claims 14 to 20, characterized in that, The method further includes: The second network element sends a fifth control signaling message including the mapping information of the DRB and the HARQ entity to the first network element, so that the first network element receives the data of the second network element according to the mapping information of the DRB and the HARQ entity, 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 mapping information of the DRB and the HARQ entity to the first network element, the method further includes: The second network element receives a sixth control signaling message including a request for the mapping information of the DRB and the HARQ entity 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, characterized in that, 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, characterized in that, 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 set of DRBs to the HARQ entity mapped to the DRB in the set, 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, characterized in that, 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.

28. The method according to any one of claims 20 to 22, characterized in that, 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.

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 and Backhaul IAB Node.

30. A data transmission method, characterized in that, Including: The third network element configures the mapping between at least one set of DRBs and HARQ entities using the mapping information of the Data Radio Bearer DRB and the Hybrid Automatic Repeat Request HARQ entity, where the mapping information of the DRB and the HARQ entity 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 third network element sends the mapping information of the DRB and the HARQ entity.

31. The method according to claim 30, wherein The mapping relationship between the DRB and the 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, characterized in that, 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 group 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, characterized in that, 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, characterized in that, The third network element includes at least one of the following: Radio Access Network (RAN), User Equipment (UE), Central Unit (CU), Distribution Unit (DU), relay node, Integrated Access and Backhaul (IAB) node.

39. The method according to claim 35, characterized in that, The first network element includes at least one of the following: Radio Access Network (RAN), User Equipment (UE), Central Unit (CU), Distribution Unit (DU), relay node, Integrated Access and Backhaul (IAB) node.

40. The method according to claim 35, characterized in that, The second network element includes at least one of the following: Radio Access Network (RAN), User Equipment (UE), Central Unit (CU), Distribution Unit (DU), relay node, Integrated Access and Backhaul (IAB) node.

41. A computer-readable storage medium, characterized in that, A computer program is stored in the computer-readable storage medium, where 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, characterized in that, 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