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

Abstract

Provided in the embodiments of the present disclosure are a data transmission method and apparatus, and a storage medium and an electronic apparatus. The method is applied to a first network element, and comprises: acquiring data radio bearer (DRB) and hybrid automatic repeat request (HARQ)-entity configuration information, wherein the DRB and HARQ-entity configuration information is used for configuring an HARQ entity for a DRB; configuring the HARQ entity for the DRB on the basis of the DRB and HARQ-entity configuration information; and submitting data received by the HARQ entity to an upper layer by means of the DRB corresponding to the HARQ entity.

Description

Data transmission method, device, storage medium and electronic device

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

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

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

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

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

[0006] Summary of the Invention

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

[0008] According to one embodiment of the present disclosure, a data transmission method is provided, which is applied to a first network element, including: obtaining configuration information of a data radio bearer DRB and a hybrid automatic repeat request HARQ entity, wherein the configuration information of the DRB and the HARQ entity is used to configure a HARQ entity for a DRB; configuring the HARQ entity to the DRB based on the configuration information of the DRB and the HARQ entity; and delivering the data received by the HARQ entity to an upper layer through the DRB corresponding to the HARQ entity.

[0009] According to another embodiment of the present disclosure, a data transmission method is also provided, which is applied to a second network element, including: obtaining configuration information of a data radio bearer DRB and a hybrid automatic repeat request HARQ entity, wherein the configuration information of the DRB and the HARQ entity is used to configure a HARQ entity for a DRB; configuring the HARQ entity for the DRB based on the configuration information of the DRB and the HARQ entity; and handing over the data stream to the HARQ entity corresponding to the DRB for sending through the DRB.

[0010] According to another embodiment of the present disclosure, a data transmission method is also provided, which is applied to a third network element, including: generating configuration information of a data radio bearer DRB and a hybrid automatic repeat request HARQ entity, wherein the configuration information of the DRB and the HARQ entity is used to configure one DRB to correspond to one HARQ entity; and sending the configuration information of the DRB and the HARQ entity.

[0011] According to another embodiment of the present disclosure, a data transmission device is provided, which is applied to a first network element, including: a first acquisition module, configured to obtain configuration information of a data radio bearer DRB and a hybrid automatic repeat request HARQ entity, wherein the configuration information of the DRB and the HARQ entity is used to configure one HARQ entity to correspond to one DRB; a first configuration module, configured to configure the HARQ entity to the DRB based on the configuration information of the DRB and the HARQ entity; and a first sending module, configured to deliver the data received by the HARQ entity to an upper layer through the DRB corresponding to the HARQ entity.

[0012] According to another embodiment of the present disclosure, a data transmission device is provided, which is applied to a second network element, including: a second acquisition module, configured to obtain configuration information of a data radio bearer DRB and a hybrid automatic repeat request HARQ entity, wherein the configuration information of the DRB and the HARQ entity is used to configure a HARQ entity for a DRB; a second configuration module, configured to configure the HARQ entity for the DRB based on the configuration information of the DRB and the HARQ entity; and a second sending module, configured to hand over the data stream to the HARQ entity corresponding to the DRB for sending through the DRB.

[0013] According to another embodiment of the present disclosure, a data transmission device is provided, which is applied to a third network element, including: a first generation module, configured to generate configuration information of a data radio bearer DRB and a hybrid automatic repeat request HARQ entity, wherein the configuration information of the DRB and the HARQ entity is used to configure one DRB to correspond to one HARQ entity; and a third sending module, configured to send the configuration information of the DRB and the HARQ entity.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0028] FIG13 is a schematic diagram of a data configuration method according to an embodiment of the present disclosure;

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

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

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

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

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

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

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

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

[0037] In the 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 the user data packet. One or more QoS flows are mapped to one DRB. Since the wireless resources in the wireless communication network are limited, different DRB data are multiplexed at the MAC layer after being processed by the PDCP layer and the RLC layer, and transmitted through the HARQ entity on multiple HARQ processes. TB transmission. Figure 4 is a schematic diagram of the data mapping method in the related art. As shown in Figure 4, this data transmission method multiplexing through the MAC layer may cause the data of DRB1 and the data of DRB2 to be simultaneously mapped to the same TB of the same HARQ process of HARQ entity 1 for transmission. Since TB is the basic unit of physical layer data scheduling and transmission, in this case, the data of DRB1 and DRB2 cannot be differentiated at the physical layer because they are multiplexed on one TB.

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

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

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

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

[0042] In an embodiment of the present disclosure, a network element may include one or more network nodes, one or more network functions, one or more network layers, one or more network devices, and / or one or more network entities. For example, a network element may be a RAN node, an RRC (Radio Resource Control) layer of the RAN, a MAC layer of the RAN, a MAC entity of the RAN, a Central Unit (CU), a Distributed Unit (DU), a UE, or an Integrated Access and Backhaul (IAB) Node. The RAN node may be a base station device, such as a 4G base station eNodeB, a 5G base station gNodeB, or a next-generation new base station. In an embodiment of the present disclosure, a DRB may be at least one of the following: a communication-related radio bearer, a perception-related radio bearer, an AI (Artificial Intelligence)-related radio bearer, a data service-related radio bearer, a computing-related radio bearer, or a security / trust-related radio bearer.

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

[0044] Step S602: The first network element obtains configuration information of a data radio bearer (DRB) and a hybrid automatic repeat request (HARQ) entity, wherein the configuration information of the DRB and the HARQ entity is used to configure one HARQ entity for one DRB.

[0045] Step S604: The first network element configures the HARQ entity to the DRB based on the configuration information of the DRB and the HARQ entity;

[0046] Step S606: The first network element delivers the data received by the HARQ entity to an upper layer through the DRB corresponding to the HARQ entity.

[0047] In the above steps, the first network element includes but is not limited to: RAN, UE, CU, DU, relay node or IAB node. The configuration information of the DRB and the HARQ entity may include information of one-to-one configuration of multiple groups of DRBs and HARQ entities. For example, the configuration information of the DRB and the HARQ entity includes information of one-to-one configuration between two groups of DRBs and HARQ entities: one group includes the first DRB and the first HARQ entity, indicating that the first HARQ entity is configured for the first DRB; the other group includes the second DRB and the second HARQ entity, indicating that the second HARQ entity is configured for the second DRB. The first HARQ entity and the second HARQ entity are different HARQ entities, the first DRB and the second DRB are different DRBs, the first DRB and the first HARQ entity are configured one-to-one, and the second HARQ entity and the second DRB are configured one-to-one. The first network element delivers the data received by the HARQ entities included in each group to the upper layer through the DRB configured one-to-one with the HARQ entities based on the information of one-to-one configuration of multiple groups of DRBs and HARQ entities. For example, the data received on the first HARQ entity is delivered to the upper layer through the first DRB, and the data received on the second HARQ entity is delivered to the upper layer through the second DRB.

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

[0049] In an optional embodiment, the configuration information of the DRB and HARQ entity includes at least one of the following: a DRB identifier of the DRB, a HARQ entity identifier of the HARQ entity, and a group identifier of the DRB and HARQ entity configuration.

[0050] In an optional embodiment, the first network element configures a HARQ entity for a DRB based on the configuration information of the DRB and the HARQ entity, which may be: the HARQ entity uses the same life cycle as the DRB. For example, when the DRB is established, the HARQ entity is generated accordingly, and when the DRB is removed, the HARQ entity is also deleted accordingly.

[0051] In an optional embodiment, the first network element configures a HARQ entity for a DRB based on the configuration information of the DRB and the HARQ entity, which may be: the configuration of a HARQ entity for a DRB may be that in the data transmission of multiple DRBs, the HARQ entity only delivers data to the upper layer through the DRB.

[0052] In an optional embodiment, the first network element configures a HARQ entity for a DRB based on the configuration information of the DRB and the HARQ entity, which may be: the configuration of a HARQ entity for a DRB may be that in the data transmission with multiple DRBs, the HARQ entity is only bound, corresponds or associated with the DRB.

[0053] In an optional embodiment, the first network element configures a HARQ entity for a DRB based on the configuration information of the DRB and the HARQ entity, which may be: the configuration of the HARQ entity is included in the configuration of the DRB. For example, the DRB configuration parameters include parameter configuration of the HARQ entity.

[0054] In an optional embodiment, the first network element configures a HARQ entity for a DRB based on the configuration information of the DRB and the HARQ entity, which may be: the configuration of the DRB includes a HARQ entity identifier of the HARQ entity. For example, the configuration message of the DRB configuration includes the identifier of the HARQ entity (e.g., HARQ entity Identity).

[0055] In an optional embodiment, the first network element obtains the configuration information of the DRB and HARQ entity, including at least one of the following: the first network element generates the configuration information of the DRB and HARQ entity; the first network element receives a first configuration message including the configuration information of the DRB and HARQ entity; the first network element first sends a first request message, and then receives the first configuration message including the configuration information of the DRB and HARQ entity, wherein the first request message is used to request the second network element to send the first configuration message including the configuration information of the DRB and HARQ entity, and the second network element is a network element that sends data to the first network element according to the configuration information of the DRB and HARQ entity.

[0056] In an optional embodiment, after the first network element obtains the configuration information of the DRB and HARQ entity, the method further includes: sending a second configuration message including the configuration information of the DRB and HARQ entity to the second network element, so that the second network element sends data to the first network element according to the configuration information of the DRB and HARQ entity.

[0057] In an optional embodiment, the method for the first network element to receive the first configuration message including the configuration information of the DRB and HARQ entity includes at least one of the following: the first network element receives the first configuration message from the second network element, wherein the second network element is a network element that sends data to the first network element according to the configuration information of the DRB and HARQ entity; the first network element receives the first configuration message from the third network element, wherein the third network element is a network element that does not directly send data to the first network element according to the configuration information of the DRB and HARQ entity; the first network element receives the first configuration message from the third network element via the second network element, wherein the third network element is a network element that does not directly send data to the first network element according to the configuration information of the DRB and HARQ entity, and the second network element is a network element that directly sends data to the first network element according to the configuration information of the DRB and HARQ entity.

[0058] In the above steps, the first network element receives the configuration 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 configuration message is an RRC message sent by the base station, such as an RRC connection establishment message and an RRC reconfiguration message. When the first network element is a base station and the second network element is a UE, uplink transmission is performed between the second network element and the first network element, wherein the base station itself knows the configuration relationship because it can send RRC messages. Therefore, the base station can deliver the data received on the HARQ entity upward through the DRB corresponding to the HARQ entity configuration according to the configuration information in the RRC message previously sent to the UE. For example, the UE receives the RRC reconfiguration message sent by the base station, and the RRC reconfiguration message includes a DRB and the HARQ entity corresponding to the DRB. The UE delivers all data on the HARQ entity upward through the DRB according to the RRC reconfiguration message. Optionally, the UE side establishes the DRB and generates the HARQ entity according to the RRC reconfiguration message.

[0059] In the above steps, the first network element receives the configuration 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 configuration message (no user plane data transmission), the target control signaling comes from an RRC message of the base station, such as an RRC connection establishment message, an RRC reconfiguration message, etc., and the second network element is a base station that only sends data transmission (no control signaling). In this case, the first network element can configure the configuration relationship between the DRB and the HARQ entity of the received second network element data according to the RRC message from the third network element, and deliver the data upward based on the configured configuration relationship.

[0060] In the above steps, the first network element receives the configuration 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 interact directly with the UE, the RRC message generated by the CU needs to be sent to the UE via the DU.

[0061] In an optional embodiment, the first configuration message includes at least one of the following: an RRC message, a DRB configuration message.

[0062] In an optional embodiment, the second configuration message includes at least one of the following: an RRC message, a DRB configuration message.

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

[0064] In an optional embodiment, the first request message includes at least one of the following: an RRC request message, a radio bearer configuration request message.

[0065] In the above embodiment, the configuration message may also be a DRB configuration message included in an RRC message. The request message for the configuration information may also be a DRB configuration request message included in an RRC request message. The following takes the first network element as the UE as an example for explanation: that is, the RRC message is a radio resource control message, which is a control signaling message exchanged between the base station and the UE. In the current 4G / 5G system, the RRC message is generated by the base station RRC layer. Among them, the RRC establishment message is used to establish an RRC connection when the UE is in a non-connected state (such as the UE is in the RRC idle state RRC_IDLE), and the RRC establishment message includes an RRC establishment request message (for example, RRCSetupRequest message, RRCReestablishmentRequest message) sent by the UE to the base station and an RRC establishment message (for example, RRCSetup message) sent by the base station to the UE. After the RRC connection is established, the UE will send an RRC establishment completion message (for example, RRCSetupComplete message). The UE may use an RRC setup request message to send a DRB and HARQ entity configuration information request (corresponding to the configuration information request message mentioned in the present disclosure), and the base station may use an RRC setup message to send one-to-one configuration information of DRB and HARQ entity (i.e., the above-mentioned configuration information of DRB and HARQ entity) to instruct the UE to perform radio bearer configuration. Optionally, the UE may also use an RRC setup completion message to send the configuration information of DRB and HARQ entity. The RRC reconfiguration message (RRCReconfiguration message) is used to configure the RRC connection when the UE is in a connected state (e.g., RRC_CONNECTED). The UE receives the RRC reconfiguration message (e.g., RRCReconfiguration message) and performs radio bearer configuration according to the radio bearer configuration information contained in the RRCReconfiguration message. In an embodiment of the present disclosure, the base station may include the configuration information of DRB and HARQ entity in the RRC reconfiguration message and send it to the UE. After receiving the RRC reconfiguration message including the configuration information of DRB and HARQ entity, the UE performs radio bearer configuration according to the configuration information. In addition, for the scenario where CU (Central Unit) and DU (Distributed Unit) are deployed separately, after the UE sends an RRC connection establishment request, the DU sends a forwarding message of the UE RRC establishment request message to the CU (for example, Initial UL RRC Message Transfer) to forward the initial uplink RRC message from the DU to the control plane (CU-CP) of the CU.The CU allocates radio resources to the UE by sending a downlink RRC message forwarding message (DL RRC Message Transfer) to the DU. Figure 7 is a schematic diagram of an RRC message transmission method according to an embodiment of the present disclosure. As shown in Figure 7, the DU plays the role of RRC message forwarding between the CU and the UE. In the present disclosure, the CU can configure an RRC message containing configuration information for DRBs and HARQ entities and forward it to the UE via the DU. The UE can also send an RRC message containing a configuration information request for DRBs and HARQ entities to the CU via the DU.

[0066] In an optional embodiment, the UE receives an RRC reconfiguration message, and the RRC reconfiguration message IE (Information Element) carries the configuration information of the DRB and HARQ entity. For example, the configuration information of the DRB and HARQ entity is carried in the radio bearer configuration IE. For example, the configuration information of the DRB and HARQ entity is carried in the MAC configuration IE. For example, the configuration information of the DRB and HARQ entity is carried in the RLC configuration IE. For example, the configuration information of the DRB and HARQ entity is carried in the PDCP configuration IE. For example, the UE receives the RadioBearerConfig IE carrying the configuration information of the DRB and HARQ entity, and configures a HARQ entity for a DRB on the UE side according to the configuration information of the DRB and HARQ entity. For example, the UE receives the RLC-BearerConfig IE carrying the configuration information of the DRB and HARQ entity, and configures the UE-side DRB to the HARQ entity according to the configuration information of the DRB and HARQ entity.

[0067] In an optional embodiment, the UE receives a radio bearer configuration message, and the radio bearer configuration message carries configuration information of the DRB and the HARQ entity. Optionally, the configuration information can be used to generate a HARQ entity for the DRB when the DRB is established. Optionally, when the DRB is removed, the configuration information can be used to delete the HARQ entity corresponding to the DRB. Optionally, when the DRB is modified, the configuration information can be used to modify the HARQ entity corresponding to the DRB.

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

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

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

[0071] Step S802: The second network element obtains configuration information of a DRB and a HARQ entity, wherein the configuration information of the DRB and the HARQ entity is used to configure a HARQ entity for one DRB, and the configuration information may include a DRB identifier and a HARQ entity identifier, or the configuration information may include multiple groups of DRB identifiers and HARQ entity identifiers, wherein each group includes a DRB identifier and a HARQ entity identifier;

[0072] Step S804: The second network element configures the HARQ entity for the DRB based on the configuration information of the DRB and the HARQ entity;

[0073] Step S806: The second network element hands over the data stream to the HARQ entity corresponding to the DRB through the DRB.

[0074] In step S804, when the second network element configures the HARQ entity for the DRB, it clearly indicates how each DRB and each HARQ entity are configured. For example, there are two groups of configuration information: DRB1 (DRB ID=1) is configured with HARQ entity 1 (HARQ entity ID=1), and DRB2 (DRB ID=2) is configured with HARQ entity 2 (HARQ entity ID=2). Data flow1 and data flow2 are data with different service characteristics. When sending data streams, the second network element sends data flow1 to the transmitting end HARQ entity 1 through DRB1 for transmission and sends data flow2 to the transmitting end HARQ entity 2 through DRB2 for transmission according to the configured configuration relationship. At the MAC layer, the data of the HARQ entity is placed in the HARQ process of the HARQ entity in the form of TB for physical layer transmission. There are multiple parallel HARQ processes in each HARQ entity to support TB transmission under the same DRB. However, since different HARQ entities correspond to different TBs and different HARQ entities correspond to data streams with different service domain characteristics and different DRBs, there will be no situation where different DRB data are multiplexed and transmitted on the same TB.

[0075] Through the above steps, a one-to-one configuration between DRB and HARQ entity can be configured based on the configuration information of DRB and HARQ entity to finely distinguish and independently configure the data required for different business characteristics, so that the data that needs differentiated transmission can be transmitted separately at the physical layer, thereby ensuring the difference in business performance, and effectively solving the problem that the data transmission method in the related technology multiplexes the data of different DRBs together at the MAC layer and cannot perform differentiated transmission of the data at the physical layer, thereby achieving the effect of improving the flexibility of physical layer data transmission so that the underlying transmission requirements of different businesses can be flexibly met, and greatly improving the business transmission capability and business performance experience.

[0076] In an optional embodiment, the configuration information of the DRB and HARQ entity includes at least one of the following: a DRB identifier of the DRB, a HARQ entity identifier of the HARQ entity, and a group identifier configured for the DRB and HARQ entity. For example, the RadioBearerConfig IE includes DRB Identify and HARQ entity Identify. For example, the RadioBearerConfig IE includes Group ID, DRB Identify, and HARQ entity Identify information, indicating the HARQ entity Identify configured for each DRB Identify in the group of the Group ID.

[0077] In an optional embodiment, the second network element configures a HARQ entity for a DRB based on the configuration information of the DRB and the HARQ entity, which may be: the HARQ entity uses the same life cycle as the DRB. For example, when the DRB is established, the HARQ entity is generated accordingly, and when the DRB is removed, the HARQ entity is also deleted accordingly.

[0078] In an optional embodiment, the second network element configures a HARQ entity for a DRB based on the configuration information of the DRB and the HARQ entity, which may be: the configuration of a HARQ entity for a DRB may be that in the data transmission of multiple DRBs, the HARQ entity only delivers data to the upper layer through the DRB.

[0079] In an optional embodiment, the second network element configures a HARQ entity for a DRB based on the configuration information of the DRB and the HARQ entity, which may be: the configuration of a HARQ entity for a DRB may be that in the data transmission with multiple DRBs, the HARQ entity is only bound, corresponds or associated with the DRB.

[0080] In an optional embodiment, the second network element configures a HARQ entity for a DRB based on the configuration information of the DRB and the HARQ entity, which may be: the configuration of the HARQ entity is included in the configuration of the DRB. For example, the DRB configuration parameters include parameter configuration of the HARQ entity.

[0081] In an optional embodiment, the second network element configures a HARQ entity for a DRB based on the configuration information of the DRB and the HARQ entity, which may be: the configuration of the DRB includes a HARQ entity identifier of the HARQ entity. For example, the configuration message of the DRB configuration includes the identifier of the HARQ entity (HARQ entity ID).

[0082] In an optional embodiment, the second network element obtains the configuration information of the DRB and HARQ entity, including at least one of the following: the second network element generates the configuration information of the DRB and HARQ entity; the second network element receives a third configuration message including the configuration information of the DRB and HARQ entity; the second network element first sends a second request message, and then receives a third configuration message including the configuration information of the DRB and HARQ entity, wherein the second request message is used to request the first network element to send the third configuration message including the configuration information of the DRB and HARQ entity.

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

[0084] In an optional embodiment, the method also includes: the second network element sends a fourth configuration message including the configuration information of the DRB and HARQ entity to the first network element so that the first network element receives data according to the configuration information of the DRB and HARQ entity, wherein the first network element is a network element that receives data from the second network element according to the configuration information of the DRB and HARQ entity.

[0085] In an optional embodiment, before the second network element sends the fourth configuration message including the configuration information of the DRB and HARQ entity to the first network element, the method further includes: the second network element receives the third request message sent by the first network element for requesting the configuration information of the DRB and HARQ entity. For example, the UE first sends a request message for the configuration information of the DRB and HARQ entity to the base station (such as the request message for the configuration information is an RRC request message), and after receiving the request message, the base station sends the configuration message for the configuration information of the DRB and HARQ entity to the UE (such as the configuration message is an RRC reconfiguration message).

[0086] In an optional embodiment, the third configuration message includes at least one of the following: an RRC message, a radio bearer configuration message.

[0087] In an optional embodiment, the fourth configuration message includes at least one of the following: an RRC message, a radio bearer configuration message.

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

[0089] In an optional embodiment, the second request message includes at least one of the following: an RRC request message, a radio bearer configuration request message.

[0090] In an optional embodiment, the third request message includes at least one of the following: an RRC request message, a radio bearer configuration request message.

[0091] In an optional embodiment, handing over the data stream to the HARQ entity corresponding to the DRB for sending through the DRB includes: the second network element sending the data stream according to the service characteristics of the data stream that needs to be sent, wherein data streams with different service characteristics are handed over to their corresponding configured HARQ entities for sending through different DRBs.

[0092] In the above steps, a specific DRB can be configured for data flows with specific business characteristics. The configuration method includes but is not limited to: configuring data flows with the same business characteristic information to the same DRB, and configuring data flows with different business characteristic information to different DRBs, for example, dataflow1, dataflow2, dataflow3, and dataflow4, the business characteristic information of these four data flows are respectively that data packets have order preservation requirements, data packets do not need order preservation, data packets have high reliability transmission requirements, and data packets have low reliability requirements. The second network element can configure data flow dataflow1 with order preservation requirements to DRB1; configure data flow dataflow2 without order preservation to DRB2, configure data flow dataflow3 with high reliability requirements to DRB3, and configure data flow dataflow4 with low reliability requirements to DRB4.

[0093] In an optional embodiment, the service characteristics include at least one of the following: a data packet sequence-preserving transmission service indication, a data packet non-sequence-preserving transmission service indication, a high-reliability transmission service indication, a low-reliability transmission service indication, a low-latency transmission service indication, a service no-low-latency transmission service indication, a service type indication, a service ID, and a service name identifier.

[0094] In an optional embodiment, the method also includes: the second network element obtains the service characteristics through at least one of the following methods: receiving service feature information from the core network, parsing NAS signaling to obtain service feature information, parsing QoS parameter information to obtain service feature information, parsing service feature information transmitted along the data stream to obtain service feature information, obtaining service feature information through DPI (Deep Packet Inspection) deep packet parsing, obtaining service feature information through AI (Artificial Intelligence) reasoning, and obtaining service feature information through big data analysis.

[0095] In the above embodiment, the first network element includes but is not limited to at least one of the following: RAN, UE, CU, DU, relay node, IAB node. Optionally, the second network element includes but is not limited to at least one of the following: RAN, UE, CU, DU, relay node, IAB node. In the case where 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 configuration information (i.e., the configuration information of the DRB and HARQ entity) and downlink data to the UE. The downlink data can be sent through the HARQ entity bound to the DRB (i.e., one-to-one configuration). After receiving this configuration information, the UE can know how to use the HARQ entity and DRB to receive data and submit it upward.

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

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

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

[0099] When the base station sends data to the UE, the base station configures the HARQ entity for the DRB according to the configuration information of the DRB and HARQ entity and sends the data according to the configuration information. The base station also informs the UE of the configuration information of the DRB and HARQ entity through RRC messages (such as RRC connection establishment message and RRC reconfiguration message).

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

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

[0102] For example, consider four data flows: dataflow1, dataflow2, dataflow3, and dataflow4. The service characteristics of these four data flows are: data packets require order preservation, data packets do not require order preservation, data packets require high-reliability transmission, and data packets require low reliability. The base station maps dataflow1, which requires order preservation, to DRB1; dataflow2, which does not require order preservation, to DRB2; dataflow3, which requires high reliability, to DRB3; and dataflow4, which requires low reliability, to DRB4.

[0103] Step 2: The base station sends the configuration information of the DRB and HARQ entity to the UE via an RRC message.

[0104] When configuring DRBs and HARQ entities, the base station explicitly indicates how each DRB and each HARQ entity is configured. For example, DRB1 is configured with HARQ entity 1, and DRB2 is configured with HARQ entity 2. The base station sends the configuration information to the UE via an RRC connection establishment message or an RRC reconfiguration message, so that the UE understands how the DRBs and HARQ entities are configured.

[0105] Step 3: The base station configures a corresponding HARQ entity for each DRB on the base station side according to the configuration information of the DRB and the HARQ entity, and hands over the data to be sent to the HARQ entity through the DRB.

[0106] Among them, when sending data, the base station can send data flow1 to the transmitting end HARQ entity 1 through DRB1 for transmission and send data flow2 to the transmitting end HARQ entity 2 for transmission through DRB2 according to the configuration information. The MAC layer entity transmits the data configured to the HARQ entity through the physical layer in the form of TB. There are multiple parallel HARQ processes in each HARQ entity. Different HARQ entities correspond to data streams with different service domain characteristics and different DRBs. Data of different data streams will not be configured to the same HARQ entity, thus avoiding the situation where different data streams are configured to the same TB in physical layer transmission. Since the data of different services can be distinguished at the physical layer, different physical layer transmission methods can be adopted for different service data. For example, the MCS level is reduced for TB transmission of highly reliable data streams, and the transmission power is increased for time slots of highly reliable data stream transmission.

[0107] As can be seen, in this embodiment, data streams with different service characteristics can be mapped to different DRBs through classification, and then different DRBs are configured to different HARQ entities to achieve the association between services and HARQ entities. Finally, different data streams are distinguished on the TB through the HARQ entity. Through this embodiment, differentiated transmission of service data is achieved, especially in physical link transmission, which clearly distinguishes and personalizes service differentiation.

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

[0109] When a base station sends data to a UE, it configures the DRB and HARQ entity and informs the UE of the relevant DRB and HARQ entity configuration information through an RRC message (such as an RRC connection establishment message or an RRC reconfiguration message). After receiving the configuration information, the UE can determine which DRB the HARQ entity configuration corresponds to. The UE delivers the downlink data received on the HARQ entity to the upper layer via the DRB corresponding to the HARQ entity configuration.

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

[0111] Step 1 (it should be noted that this step is optional and in actual applications, step 1 can be skipped and subsequent steps can be directly executed): the UE sends a request message, which carries a request for DRB and HARQ entity configuration information.

[0112] The request message sent by the UE may be an RRC setup request (RRC Setup Request) message or an RRC configuration request message.

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

[0114] By receiving information including DRB and HARQ entity configuration, the UE can determine which DRB corresponds to each HARQ entity and then deliver downlink data to the upper layer via the DRB configured for the HARQ entity. The base station sends the DRB and HARQ entity configuration information to the UE in an RRC Setup message or an RRC Reconfiguration message. The UE obtains the configuration information by receiving the above RRC message.

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

[0116] The configuration information of the DRB and HARQ entity may include multiple groups of DRB and HARQ entity configuration information, such as the first DRB configured with the first HARQ entity and the second DRB configured with the second HARQ entity. Based on the one-to-one configuration information of the multiple groups of DRBs and HARQ entities, the UE delivers the data received on the first HARQ entity to the upper layer through the first DRB, and delivers the data received on the second HARQ entity to the upper layer through the second DRB; the first HARQ entity and the second HARQ entity are different HARQ entities, and the first DRB and the second DRB are different DRBs.

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

[0118] Specific embodiment three: UE-side data configuration process during uplink transmission

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

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

[0121] Step 1: The UE sends an RRC request message for DRB and HARQ entity configuration information, such as the UE requests to configure a HARQ entity for DRBs of four uplink data streams.

[0122] Step 2: The UE receives an RRC configuration message sent by the base station containing DRB and HARQ entity configuration information. The RRC configuration message may be an RRC reconfiguration message or an RRC request response message. The DRB and HARQ entity configuration information sent by the base station indicates the configuration relationship between one or more groups of DRBs and HARQ entities. For example, there are 4 groups of DRB and HARQ entity configuration relationships: DRB1 configures HARQ entity 1, DRB2 configures HARQ entity 2, DRB3 configures HARQ entity 3, and DRB4 configures HARQ entity 4. Optionally, step 2 may also be that the UE receives the DRB and HARQ entity configuration information of the downlink data sent by the base station, and uses the DRB and HARQ entity configuration information of the downlink data as the DRB and HARQ entity configuration information sent by the UE uplink data.

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

[0124] For example, there are four data flows: dataflow1, dataflow2, dataflow3, and dataflow4. The service characteristics of these four data flows are: data packets with order preservation requirements, data packets without order preservation requirements, data packets with high reliability transmission requirements, and data packets with low reliability requirements. Based on the base station's indication of the mapping relationship, the UE maps dataflow1 with order preservation requirements to DRB1; dataflow2 without order preservation requirements to DRB2; dataflow3 with high reliability requirements to DRB3; and dataflow4 with low reliability requirements to DRB4.

[0125] Step 4: The UE hands over the data to be sent to the HARQ entity through the DRB according to the configuration relationship between each DRB and its corresponding HARQ entity.

[0126] Because the physical layer at the transmitter can distinguish between different services, different physical layer transmission methods can be used for different service data. For example, the MCS level can be lowered for TB transmission of highly reliable data streams, and the transmit power can be increased for time slots used for highly reliable data streams. For example, a dedicated DRB can be established for high-speed data streams, along with a dedicated HARQ entity. Targeted measures such as specialized optimization and dedicated hardware processing can be employed to ensure high-speed data transmission.

[0127] As can be seen, in this embodiment, data streams with different service characteristics can be mapped to different DRBs through classification, and then different DRBs can be assigned to different HARQ entities to achieve the association between services and HARQ entities. Because different HARQ entities have different TBs, the HARQ entities can ensure that different data streams are distinguished at the physical layer. Through this embodiment, differentiated transmission of service data is achieved, especially in the physical link transmission, which clearly distinguishes and personalizes service differentiation.

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

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

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

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

[0132] Step 2: The base station sends an RRC configuration message containing DRB and HARQ entity configuration information to the UE. The RRC configuration message can be an RRC reconfiguration message or an RRC request response message. The DRB and HARQ entity configuration information sent by the base station indicates the configuration relationship between one or more groups of DRBs and HARQ entities. For example, there are four groups of DRB and HARQ entity configuration relationships: HARQ entity 1 is configured for DRB1, HARQ entity 2 is configured for DRB2, HARQ entity 3 is configured for DRB3, and HARQ entity 4 is configured for DRB4.

[0133] Step 3: The base station configures the HARQ entity for the base station side DRB according to the RRC message sent containing the DRB and HARQ entity configuration information.

[0134] Step 4: Based on the configuration information of the DRB and HARQ entity, the base station delivers the data received by each HARQ entity to the upper layer through the DRB corresponding to each HARQ entity.

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

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

[0137] Step S902: The third network element generates configuration information of a data radio bearer (DRB) and a hybrid automatic repeat request (HARQ) entity, wherein the configuration information of the DRB and the HARQ entity is used to configure one HARQ entity corresponding to one DRB.

[0138] Step S904: The third network element sends the configuration information of the DRB and HARQ entity.

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

[0140] In an optional embodiment, the configuration information of the DRB and HARQ entity includes at least one of the following: a DRB identifier of the DRB, a HARQ entity identifier of the HARQ entity, and a group identifier of the DRB and HARQ entity configuration.

[0141] In an optional embodiment, the configuration information of the DRB and HARQ entity sent by the third network element includes at least one of the following: the third network element directly sends the configuration information of the DRB and HARQ entity to the first network element, so that the first network element submits the data received by the HARQ entity to the upper layer through the DRB corresponding to the HARQ entity when receiving data; the third network element directly sends the configuration information of the DRB and HARQ entity to the second network element, so that the second network element hands over the data from the DRB to the HARQ entity for sending when sending data; the third network element sends the configuration information of the DRB and HARQ entity to the first network element through the second network element, so that the first network element submits the data received by the HARQ entity to the upper layer through the DRB corresponding to the HARQ entity when receiving data; the third network element sends the configuration information of the DRB and HARQ entity to the second network element through the first network element, so that the second network element hands over the data from the DRB to the HARQ entity for sending when sending data.

[0142] In an optional embodiment, the third network element configures a HARQ entity for a DRB based on the configuration information of the DRB and the HARQ entity, which may be: the HARQ entity uses the same life cycle as the DRB. For example, when the DRB is established, the HARQ entity is generated accordingly, and when the DRB is removed, the HARQ entity is also deleted accordingly.

[0143] In an optional embodiment, the third network element configures a HARQ entity for a DRB based on the configuration information of the DRB and the HARQ entity, which may be: the configuration of a HARQ entity for a DRB may be that the HARQ entity only delivers data to the upper layer through the DRB during data transmission of multiple DRBs.

[0144] In an optional embodiment, the third network element configures a HARQ entity for a DRB based on the configuration information of the DRB and the HARQ entity, which may be: the configuration of a HARQ entity for a DRB may be that in the data transmission with multiple DRBs, the HARQ entity is only bound, corresponds or associated with the DRB.

[0145] In an optional embodiment, the third network element configures a HARQ entity for a DRB based on the configuration information of the DRB and the HARQ entity, which may be: the configuration of the HARQ entity is included in the configuration of the DRB. For example, the DRB configuration parameters include parameter configuration of the HARQ entity.

[0146] In an optional embodiment, the third network element configures a HARQ entity for a DRB based on the configuration information of the DRB and the HARQ entity, which may be: the configuration of the DRB includes a HARQ entity identifier of the HARQ entity. For example, the identifier of the HARQ entity (HARQ entity ID) is included in the configuration message of the DRB configuration.

[0147] In the above steps, in the scenario where control signaling and data transmission are separated, there are base stations that only send control signaling and base stations that only perform data transmission. The base station that only sends control signaling uses a low-frequency carrier to achieve wide coverage of control signaling, and the base station that only performs data transmission can use a high-frequency carrier to achieve short-distance high-speed data transmission. Figure 10 is a second schematic diagram of the RRC message transmission method according to an embodiment of the present disclosure. As shown in Figure 10, the base station that only sends control signaling is responsible for the transmission of RRC messages, and the configuration information of the DRB and HARQ entities of the base station that only performs data transmission is placed in the RRC message of the base station that only sends control signaling for transmission. The base station that only performs data transmission uses the configuration information in the RRC information sent by the base station that only sends control signaling to send downlink data or receive uplink data. Optionally, the base station that only sends control signaling and the base station that only performs data transmission can transmit the configuration information through an inter-base station interface (for example, an X2 interface, an Xn interface). The UE receives the RRC information sent by the base station that only sends control signaling, and receives downlink data or transmits uplink data with the base station that only transmits data according to the configuration information. Moreover, for the networking scenario of macro base stations and micro base stations, the coverage range of the macro base station is large. The macro base station can provide control signaling transmission for the micro base station. For example, 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 the micro base station and the UE connected to the micro base station with an indication of the DRB configuration HARQ entity by sending an RRC message containing the DRB and HARQ entity configuration information corresponding to the micro base station-micro base station service UE.

[0148] In the above steps, the third network element sends the configuration information of the DRB and HARQ entity to the first network element through 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, the CU and the UE do not interact directly, and the RRC message generated by the CU is sent to the UE via the DU. The CU and the DU interact through the F1 interface. The physical upper 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 deployed in an integrated manner, the DU first receives information from the UE and then sends it to the CU through the F1 interface. When downlink data arrives, the CU first processes it and then transmits it to the DU through the F1 interface, and then passes it to the UE through the air interface. In the present disclosure, the CU sends an RRC message containing the configuration information of the DRB and HARQ entity to the DU, and the DU forwards the configuration information to the UE. The DU and the UE configure uplink and downlink data transmission according to the configuration relationship. For downlink transmission, based on the DRB and HARQ entity configuration information of the CU in the RRC message, the DU puts the data on a DRB on the HARQ entity configured with the DRB and sends it. For uplink transmission, based on the DRB and HARQ entity configuration information of the CU in the RRC message, the DU puts the data received on a HARQ entity on the configured DRB and delivers it to the upper layer.

[0149] In an optional embodiment, the third network element sends the configuration information of the DRB and HARQ entity, including: the third network element sends the configuration information of the DRB and HARQ entity through a fifth configuration message, wherein the fifth configuration message includes at least one of the following: RRC message, DRB configuration message.

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

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

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

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

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

[0155] The present disclosure provides a data transmission configuration process for binding a DRB with a HARQ entity, wherein the DRB and HARQ entity binding is a one-to-one configuration of the DRB and the HARQ entity or a configuration of one HARQ entity for each DRB.

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

[0157] Step S1102: The receiving end obtains configuration information of the DRB and the HARQ entity, for example, by receiving control signaling (such as an RRC message) containing the configuration information, where the control signaling includes a fixed configuration indication of the DRB for the HARQ entity.

[0158] Step S1104: configuring each HARQ entity to be associated with each DRB according to the configuration information of the DRB and the HARQ entity;

[0159] Step S1106: Each HARQ entity at the receiving end receives the TB data of the multi-process and performs physical layer decoding;

[0160] Step S1108: The data of each HARQ entity at the receiving end is delivered to the upper layer via the corresponding DRB configured by the HARQ entity.

[0161] FIG12 is a fifth flowchart of a data transmission method according to an embodiment of the present disclosure. FIG13 is a schematic diagram of a data configuration method according to an embodiment of the present disclosure. The processing steps at the transmitting end are as follows:

[0162] Step S1202: The transmitter obtains service characteristic information of the data stream;

[0163] Step S1204: The transmitter maps data streams with different or the same service feature requirements to different DRBs according to the service feature information;

[0164] Step S1206: The transmitting end obtains configuration information of the DRB and HARQ entity;

[0165] Step S1208: The transmitting end configures each HARQ entity for each DRB according to the configuration information of the DRB and the HARQ entity;

[0166] Step S1210: The transmitting end delivers the data to be sent to the HARQ entity through the DRB according to the configuration information of the DRB and the HARQ entity for transmission;

[0167] Step S1212: Each HARQ entity configures multi-process TB transmission.

[0168] In the above steps, after obtaining the configuration information for the DRB and HARQ entities, the transmitter also sends this configuration information to the receiver. Existing mechanisms cannot meet the requirements for personalized transmission at the underlying layer (e.g., the physical layer), and lack flexibility in providing personalized service guarantees. Through the refined differentiation, independent configuration, and personalized resource allocation of different service feature demand data in the above steps, the underlying transmission requirements of different services are flexibly met, significantly improving service transmission capabilities and service performance experience.

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

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

[0171] Figure 14 is a structural block diagram 1 of a data transmission device according to an embodiment of the present disclosure. As shown in Figure 14, the device is applied to a first network element, including: a first acquisition module 142, configured to obtain configuration information of a data radio bearer DRB and a hybrid automatic repeat request HARQ entity, wherein the configuration information of the DRB and the HARQ entity is used to configure one HARQ entity to correspond to one DRB; a first configuration module 144, configured to configure the HARQ entity to the DRB based on the configuration information of the DRB and the HARQ entity; a first sending module 146, configured to deliver the data received by the HARQ entity to an upper layer through the DRB corresponding to the HARQ entity.

[0172] In an optional embodiment, the configuration information of the DRB and HARQ entity includes at least one of the following: a DRB identifier of the DRB, a HARQ entity identifier of the HARQ entity, and a group identifier of the DRB and HARQ entity configuration.

[0173] In an optional embodiment, the first configuration module 144 includes at least one of the following: a first periodic unit, configured so that the HARQ entity uses the same life cycle as the DRB; a first delivery unit, configured so that the HARQ entity delivers data to the upper layer only through the DRB in data transmission with multiple DRBs; a first binding unit, configured so that the HARQ entity is only bound to the DRB in data transmission with multiple DRBs; a first corresponding unit, configured so that the HARQ entity only corresponds to the DRB in data transmission with multiple DRBs; a first association unit, configured so that the HARQ entity is only associated with the DRB in data transmission with multiple DRBs; a first configuration unit, configured so that the configuration of the DRB includes the configuration of the HARQ entity; and a second configuration unit, configured so that the configuration of the DRB includes the HARQ entity identifier of the HARQ entity.

[0174] In an optional embodiment, the first acquisition module 142 includes at least one of the following: a first generation unit, configured to generate configuration information of the DRB and HARQ entity; a first receiving unit, configured to enable the first network element to receive a first configuration message including the configuration information of the DRB and HARQ entity; a first sending unit, configured to enable the first network element to first send a first request message and then receive the first configuration message including the configuration information of the DRB and HARQ entity, wherein the first request message is used to request the second network element to send the first configuration message including the configuration information of the DRB and HARQ entity, and the second network element is a network element that sends data to the first network element according to the configuration information of the DRB and HARQ entity.

[0175] In an optional embodiment, the device also includes: a fourth sending module, which is configured to send a second configuration message including the configuration information of the DRB and HARQ entity to the second network element after obtaining the configuration information of the DRB and HARQ entity, so that the second network element sends data to the first network element according to the configuration information of the DRB and HARQ entity, wherein the second configuration message includes at least one of the following: radio resource control RRC message, radio bearer configuration message.

[0176] In an optional embodiment, the first receiving unit includes at least one of the following: a first receiving subunit, configured to receive the first configuration message from a second network element, wherein the second network element is a network element that sends data to the first network element according to the configuration information of the DRB and HARQ entity; a second receiving subunit, configured to receive the first configuration message from a third network element, wherein the third network element is a network element that does not directly send data to the first network element according to the configuration information of the DRB and HARQ entity; a third receiving subunit, configured to receive the first configuration message from the third network element via the second network element, wherein the third network element is a network element that does not directly send data to the first network element according to the configuration information of the DRB and HARQ entity, and the second network element is a network element that directly sends data to the first network element according to the configuration information of the DRB and HARQ entity.

[0177] In an optional embodiment, the first configuration message includes at least one of the following: an RRC message, a radio bearer configuration message.

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

[0179] In an optional embodiment, the first request message includes at least one of the following: an RRC request message, a radio bearer configuration request message.

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

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

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

[0183] Figure 15 is a second structural block diagram of a data transmission device according to an embodiment of the present disclosure. As shown in Figure 15, the device is applied to a second network element, and includes: a second acquisition module 152, configured to obtain configuration information of a data radio bearer DRB and a hybrid automatic repeat request HARQ entity, wherein the configuration information of the DRB and the HARQ entity is used to configure a HARQ entity for a DRB; a second configuration module 154, configured to configure the HARQ entity for the DRB based on the configuration information of the DRB and the HARQ entity; a second sending module 156, configured to hand over the data stream through the DRB to the HARQ entity corresponding to the DRB for sending.

[0184] In an optional embodiment, the configuration information of the DRB and HARQ entity includes at least one of the following: a DRB identifier of the DRB, a HARQ entity identifier of the HARQ entity, and a group identifier of the DRB and HARQ entity configuration.

[0185] In an optional embodiment, the second configuration module 154 includes at least one of the following: a second period unit, configured so that the HARQ entity uses the same life cycle as the DRB; a second delivery unit, configured so that the HARQ entity delivers data to the upper layer only through the DRB in data transmission with multiple DRBs; a second binding unit, configured so that the HARQ entity is only bound to the DRB in data transmission with multiple DRBs; a second corresponding unit, configured so that the HARQ entity only corresponds to the DRB in data transmission with multiple DRBs; a second association unit, configured so that the HARQ entity is only associated with the DRB in data transmission with multiple DRBs; a third configuration unit, configured so that the configuration of the DRB includes the configuration of the HARQ entity; and a fourth configuration unit, configured so that the configuration of the DRB includes the HARQ entity identifier of the HARQ entity.

[0186] In an optional embodiment, the second acquisition module 152 includes at least one of the following: a second generation unit, configured to generate configuration information of the DRB and HARQ entity; a second receiving unit, configured to receive a third configuration message including the configuration information of the DRB and HARQ entity; a second sending unit, configured to first send a second request message, and then receive a third configuration message including the configuration information of the DRB and HARQ entity, wherein the second request message is used to request the first network element to send the third configuration message including the configuration information of the DRB and HARQ entity.

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

[0188] In an optional embodiment, the device also includes: a fifth sending module, configured to send a fourth configuration message including the configuration information of the DRB and HARQ entity to the first network element, so that the first network element receives data according to the configuration information of the DRB and HARQ entity, wherein the first network element is a network element that receives data from the second network element according to the configuration information of the DRB and HARQ entity.

[0189] In an optional embodiment, the device also includes: a receiving module, configured to receive a third request message sent by the first network element before sending the fourth configuration message including the configuration information of the DRB and HARQ entity to the first network element, wherein the third request message is used to request the second network element to send a fourth configuration message including the configuration information of the DRB and HARQ entity.

[0190] In an optional embodiment, the third configuration message includes at least one of the following: an RRC message, a radio bearer configuration message.

[0191] In an optional embodiment, the fourth configuration message includes at least one of the following: an RRC message, a radio bearer configuration message.

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

[0193] In an optional embodiment, the second request message includes at least one of the following: an RRC request message, a radio bearer configuration request message.

[0194] In an optional embodiment, the third request message includes at least one of the following: an RRC request message, a radio bearer configuration request message.

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

[0196] In an optional embodiment, the service characteristics include at least one of the following: a data packet sequence-preserving transmission service indication, a data packet non-sequence-preserving transmission service indication, a high-reliability transmission service indication, a low-reliability transmission service indication, a low-latency transmission service indication, a service no-low-latency transmission service indication, a service type indication, a service ID, and a service name identifier.

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

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

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

[0200] Figure 16 is a third structural block diagram of the data transmission device according to an embodiment of the present disclosure. As shown in Figure 16, the device is applied to a third network element, including: a first generation module 162, configured to generate configuration information of a data radio bearer DRB and a hybrid automatic repeat request HARQ entity, wherein the configuration information of the DRB and the HARQ entity is used to configure one DRB to correspond to one HARQ entity; a third sending module 164, configured to send the configuration information of the DRB and the HARQ entity.

[0201] In an optional embodiment, the configuration information of the DRB and HARQ entity includes at least one of the following: a DRB identifier of the DRB, a HARQ entity identifier of the HARQ entity, and a group identifier of the DRB and HARQ entity configuration.

[0202] In an optional embodiment, the third sending module 164 includes at least one of the following: a fourth sending unit, configured to directly send the configuration information of the DRB and the HARQ entity to the first network element, so that the first network element, when receiving data, submits the data received by the HARQ entity to the upper layer through the DRB corresponding to the HARQ entity; a fifth sending unit, configured to directly send the configuration information of the DRB and the HARQ entity to the second network element, so that when the second network element sends data, the data from the DRB is handed over to the HARQ entity for sending; a sixth sending unit, configured to send the configuration information of the DRB and the HARQ entity to the first network element through the second network element, so that when the first network element receives data, the data received by the HARQ entity is handed over to the upper layer through the DRB corresponding to the HARQ entity; a seventh sending unit, configured to send the configuration information of the DRB and the HARQ entity to the second network element through the first network element, so that when the second network element sends data, the data from the DRB is handed over to the HARQ entity for sending.

[0203] In an optional embodiment, the third sending module 164 includes: an eighth sending unit, configured to send the configuration information of the DRB and HARQ entity through a fifth configuration message.

[0204] In an optional embodiment, the fifth configuration message includes at least one of the following: an RRC message, a radio bearer configuration message.

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

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

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

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

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

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

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

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

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

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

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

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

Claims

1. A data transmission method, applied to a first network element, the method comprising: Obtaining configuration information of a data radio bearer (DRB) and a hybrid automatic repeat request (HARQ) entity, wherein the configuration information of the DRB and the HARQ entity is used to configure one HARQ entity for one DRB; Based on the configuration information of the DRB and the HARQ entity, configuring the HARQ entity to the DRB; Delivering the data received by the HARQ entity to an upper layer through the DRB corresponding to the HARQ entity.

2. The method according to claim 1, wherein, The configuration information of the DRB and the HARQ entity includes at least one of the following: the DRB identifier of the DRB, the HARQ entity identifier of the HARQ entity, and the group identifier of the DRB and HARQ entity configuration.

3. The method according to claim 1 or 2, wherein Configuring the HARQ entity to the DRB includes at least one of the following: The HARQ entity uses the same lifecycle as the DRB; In data transmission of multiple DRBs, the HARQ entity only delivers data to the upper layer through the DRB; In data transmission of multiple DRBs, the HARQ entity is only bound to the DRB; In data transmission of multiple DRBs, the HARQ entity only corresponds to the DRB; In data transmission of multiple DRBs, the HARQ entity is only associated with the DRB; Configuring the DRB includes configuring the HARQ entity; Configuring the DRB includes the HARQ entity identifier of the HARQ entity.

4. The method according to claim 1, wherein The first network element obtaining the configuration information of the DRB and the HARQ entity includes at least one of the following: The first network element generates the configuration information of the DRB and the HARQ entity; The first network element receives a first configuration message including the configuration information of the DRB and the HARQ entity; The first network element first sends a first request message and then receives the first configuration message including the configuration information of the DRB and the HARQ entity, wherein the first request message is used to request the second network element to send the first configuration message including the configuration information of the DRB and the HARQ entity, and the second network element is the network element that sends data to the first network element according to the configuration information of the DRB and the HARQ entity.

5. The method according to any one of claims 1 to 4, wherein After the first network element obtains the configuration information of the DRB and the HARQ entity, the method further comprises: sending a second configuration message including the configuration information of the DRB and the HARQ entity to the second network element, so that the second network element sends data to the first network element according to the configuration information of the DRB and the HARQ entity, wherein the second configuration message includes at least one of the following: a radio resource control (RRC) message, a radio bearer configuration message.

6. The method according to claim 4, wherein The method for the first network element to receive the first configuration message including the configuration information of the DRB and the HARQ entity includes at least one of the following: The first network element receives the first configuration message from the second network element, wherein the second network element is the network element that sends data to the first network element according to the configuration information of the DRB and the HARQ entity; The first network element receives the first configuration 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 according to the configuration information of the DRB and the HARQ entity; The first network element receives the first configuration 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 according to the configuration information of the DRB and the HARQ entity, and the second network element is a network element that directly sends data to the first network element according to the configuration information of the DRB and the HARQ entity.

7. The method according to any one of claims 4 to 6, wherein, The first configuration message includes at least one of the following: Radio Resource Control (RRC) message, radio bearer configuration message.

8. The method according to claim 4, wherein The first request message includes at least one of the following: RRC request message, radio bearer configuration request message.

9. A data transmission method, applied to a second network element, the method includes: Obtain configuration information of a Data Radio Bearer (DRB) and a Hybrid Automatic Repeat reQuest (HARQ) entity, where the configuration information of the DRB and the HARQ entity is used to configure one HARQ entity for one DRB; Based on the configuration information of the DRB and the HARQ entity, configure the HARQ entity for the DRB; Send a data stream through the DRB to the HARQ entity corresponding to the DRB for transmission.

10. The method according to claim 9, wherein, The configuration information of the DRB and the HARQ entity includes at least one of the following: the DRB identifier of the DRB, the HARQ entity identifier of the HARQ entity, and the group identifier configured for the DRB and the HARQ entity.

11. The method according to claim 9 or 10, wherein, Configuring the HARQ entity for the DRB includes at least one of the following: The HARQ entity uses the same lifecycle as the DRB; In data transmission of multiple DRBs, the HARQ entity only delivers data to the upper layer through the DRB; In data transmission of multiple DRBs, the HARQ entity is only bound to the DRB; In data transmission of multiple DRBs, the HARQ entity only corresponds to the DRB; In data transmission of multiple DRBs, the HARQ entity is only associated with the DRB; Configuring the DRB includes configuring the HARQ entity; Configuring the DRB includes the HARQ entity identifier of the HARQ entity.

12. The method according to any one of claims 9 to 11, wherein, The second network element obtaining the configuration information of the DRB and the HARQ entity includes at least one of the following: The second network element generates the configuration information of the DRB and the HARQ entity; The second network element receives a third configuration message including the configuration information of the DRB and the HARQ entity; The second network element first sends a second request message and then receives a third configuration message including the configuration information of the DRB and the HARQ entity, where the second request message is used to request the first network element to send the third configuration message including the configuration information of the DRB and the HARQ entity.

13. The method according to claim 12, wherein, The second network element receiving the third configuration message including the configuration information of the DRB and the HARQ entity includes at least one of the following: The second network element receives the third configuration message from the first network element, where the first network element is a network element that receives data from the second network element according to the configuration information of the DRB and the HARQ entity; The second network element receives the third configuration message 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 according to the configuration information of the DRB and the HARQ entity; The second network element receives the third configuration message from the third network element via the first network element, where the third network element is a network element that does not directly send data to the first network element according to the configuration information of the DRB and the HARQ entity, and the first network element is a network element that sends data to the second network element according to the configuration information of the DRB and the HARQ entity.

14. The method according to any one of claims 9 to 13, wherein The method further includes: The second network element sends a fourth configuration message including the configuration information of the DRB and the HARQ entity to the first network element, so that the first network element receives data according to the configuration information of the DRB and the HARQ entity, where the first network element is a network element that receives data from the second network element according to the configuration information of the DRB and the HARQ entity.

15. The method according to claim 14, wherein, Before the second network element sends the fourth configuration message including the configuration information of the DRB and the HARQ entity to the first network element, the method further includes: The second network element receives a third request message sent by the first network element, where the third request message is used to request the second network element to send a fourth configuration message including the configuration information of the DRB and the HARQ entity.

16. The method according to any one of claims 12, 13, and 15, wherein, The third configuration message includes at least one of the following: a radio resource control (RRC) message, a radio bearer configuration message.

17. The method according to claim 14 or 15, wherein, The fourth configuration message includes at least one of the following: a radio resource control (RRC) message, a radio bearer configuration message.

18. The method according to claim 12, wherein, The second request message includes at least one of the following: An RRC request message, a radio bearer configuration request message.

19. The method according to claim 15, wherein, The third request message includes at least one of the following: An RRC request message, a radio bearer configuration request message.

20. The method according to claim 9, wherein Handing the data stream to the HARQ entity corresponding to the DRB for transmission via the DRB includes: The second network element sends the data stream according to the service characteristics of the data stream to be sent, where there are different Data streams with service characteristics are handed to the corresponding configured HARQ entities for transmission through different DRBs.

21. The method according to claim 20, wherein, The service characteristics include at least one of the following: Packet in-sequence transmission service indication, packet out-of-sequence transmission service indication, high-reliability transmission service indication, low-reliability transmission service indication, low-latency transmission service indication, no low-latency transmission service indication, service type indication, service identifier, service name identifier.

22. A data transmission method applied to a third network element, including: Generating configuration information of a data radio bearer (DRB) and a hybrid automatic repeat request (HARQ) entity, where the configuration information of the DRB and the HARQ entity is used to configure one HARQ entity for one DRB; Sending the configuration information of the DRB and the HARQ entity.

23. The method according to claim 22, wherein, The configuration information of the DRB and the HARQ entity includes at least one of the following: the DRB identifier of the DRB, the HARQ entity identifier of the HARQ entity, and the group identifier configured for the DRB and the HARQ entity.

24. The method according to claim 22, wherein, The third network element sending the configuration information of the DRB and the HARQ entity includes at least one of the following: The third network element directly sends the configuration information of the DRB and the HARQ entity to the first network element, so that when the first network element receives data, it delivers the data received by the HARQ entity to the upper layer through the DRB corresponding to the HARQ entity; The third network element directly sends the configuration information of the DRB and the HARQ entity to the second network element, so that when the second network element sends data, it hands over the data from the DRB to the HARQ entity for sending; The third network element sends the configuration information of the DRB and the HARQ entity to the first network element through the second network element, so that when the first network element receives data, it delivers the data received by the HARQ entity to the upper layer through the DRB corresponding to the HARQ entity; The third network element sends the configuration information of the DRB and the HARQ entity to the second network element through the first network element, so that when the second network element sends data, it hands over the data from the DRB to the HARQ entity for sending.

25. The method according to any one of claims 22 to 24, wherein, The third network element sending the configuration information of the DRB and the HARQ entity includes: The third network element sends the configuration information of the DRB and the HARQ entity through a fifth configuration message.

26. The method according to claim 25, wherein The fifth configuration message includes at least one of the following: a radio resource control (RRC) message, a radio bearer configuration message.

27. A computer-readable storage medium storing a computer program therein, wherein, When the computer program is executed by a processor, it implements the steps of the method described in any one of claims 1 to 8, or implements the steps of the method described in any one of claims 9 to 21, or implements the steps of the method described in any one of claims 22 to 26.

28. An electronic device, comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, wherein when the processor executes the computer program, it implements the steps of the method described in any one of claims 1 to 8, or implements the steps of the method described in any one of claims 9 to 21, or implements the steps of the method described in any one of claims 22 to 26.

Images