Data transmission method and device, storage medium and electronic device

Abstract

Provided in an embodiment of the present invention are a data transmission method and device, a storage medium and an electronic device, the method being applied to a first network element, the method comprising: acquiring configuration information of a data radio bearer (DRB) and a hybrid automatic repeat request (HARQ) entity, the configuration information of the DRB and the HARQ entity being used for configuring 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; and submitting the data received by the HARQ entity to an upper layer through the DRB corresponding to the HARQ entity. Through the data transmission method and device, the problem that differential transmission cannot be carried out on a physical layer in data transmission in related technologies is solved.

Description

Technical Field

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

[0002] As the services of wireless communication technology become increasingly rich, the requirements for ensuring service differentiation performance are also getting higher and higher.

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

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

[0005] According to an embodiment of the present invention, a data transmission method is provided, which is applied to a first network element and includes: obtaining 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, configuring the HARQ entity to the DRB; and delivering the data received by the HARQ entity to the upper layer through the DRB corresponding to the HARQ entity.

[0006] According to another embodiment of the present invention, there is also provided a data transmission method, which is applied to a second network element and includes: obtaining 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; configuring the HARQ entity for the DRB based on the configuration information of the DRB and the HARQ entity; and sending a data stream through the DRB to the HARQ entity corresponding to the DRB for transmission.

[0007] According to another embodiment of the present invention, there is also provided a data transmission method, which is applied to a third network element and includes: 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; and sending the configuration information of the DRB and the HARQ entity.

[0008] According to another embodiment of the present invention, there is provided a data transmission apparatus, which is applied to a first network element and includes: a first obtaining module, configured to 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; 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 send 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 invention, there is provided a data transmission apparatus, which is applied to a second network element and includes: a second obtaining module, configured to 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; 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 send a data stream through the DRB to the HARQ entity corresponding to the DRB for transmission.

[0010] According to another embodiment of the present invention, there is provided a data transmission apparatus, which is applied to a third network element and includes: a first generating module, configured to generate 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; and a third sending module, configured to send the configuration information of the DRB and the HARQ entity.

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

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

[0013] Through the present invention, a HARQ entity is configured for a DRB based on the configuration information of the DRB and the HARQ entity, so that data that needs to be transmitted differentially can be transmitted separately at the physical layer, thereby ensuring the embodiment of the difference in service performance, effectively solving the problem that data transmission in the related art cannot be differentially transmitted at the physical layer, achieving the effect of improving the flexibility of physical layer data transmission, flexibly meeting the underlying transmission requirements of different services, and greatly improving the service transmission ability and service performance experience. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

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

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

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

[0020] Figure 7 is a schematic diagram of the RRC message transmission method according to an embodiment of the present invention Figure 1 ;

[0021] Figure 8 is the flow of the data transmission method according to an embodiment of the present invention Figure 2 ;

[0022] Figure 9It is the flowchart of the data transmission method according to an embodiment of the present invention Figure 3 ;

[0023] Figure 10 It is a schematic diagram of the RRC message transmission method according to an embodiment of the present invention Figure 2 ;

[0024] Figure 11 It is the flowchart of the data transmission method according to an embodiment of the present invention Figure 4 ;

[0025] Figure 12 It is the flowchart of the data transmission method according to an embodiment of the present invention Figure 5 ;

[0026] Figure 13 It is a schematic diagram of the data configuration method according to an embodiment of the present invention;

[0027] Figure 14 It is the structural block diagram of the data transmission device according to an embodiment of the present invention Figure 1 ;

[0028] Figure 15 It is the structural block diagram of the data transmission device according to an embodiment of the present invention Figure 2 ;

[0029] Figure 16 It is the structural block diagram of the data transmission device according to an embodiment of the present invention Figure 3 . Detailed implementation manners

[0030] In the following, embodiments of the present invention will be described in detail with reference to the accompanying drawings and in conjunction with the embodiments

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

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

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

[0034] A radio bearer (RB) is a general term for a series of protocol entities and configurations allocated by a base station for a UE (User Equipment), including a series of resources for each protocol entity. The 5G access network uses the data mapping method of DRB to provide service guarantee, and DRB is the actual transmission channel for user data. From the perspective of the services provided from the lower layer to the upper layer: The physical layer provides services for the MAC sublayer through the transport channel; the MAC sublayer provides services for the RLC (Radio Link Control) sublayer through the logical channel; the RLC sublayer provides services for the PDCP (Packet Data Convergence Protocol) sublayer through the RLC channel; the PDCP sublayer provides services for the SDAP sublayer through the radio bearer RB, and the SDAP layer provides services for the upper layer through the QoS flow. From the perspective of data mapping from the upper layer to the lower layer: The SDAP layer is responsible for the mapping of QoS flow to DRB (data radio bearer). QoS flows with different packet forwarding requirements are mapped to different DRBs as a guarantee for differentiating service differences; the PDCP layer is responsible for sorting, header compression, encryption, and integrity protection processing of the upper layer data; the RLC layer performs data segmentation and executes ARQ (Automatic Repeat reQuest) slow retransmission. A complete RLC SDU (Service Data Unit) may be split into multiple RLC PDU (Protocol Data Unit) segments, and the RLC layer can also perform re-segmentation according to the actual resource situation; the MAC layer multiplexes multiple MAC SDUs into a MAC PDU as the transport block TB (Transport Block) of the physical layer and uses the HARQ mechanism for fast retransmission of data packets. There are multiple parallel HARQ processes under one HARQ entity, and the data of different HARQ processes cannot be merged. The TB is the basic unit of HARQ transmission. When there is no spatial multiplexing, one HARQ process can transmit one TB. When there is spatial multiplexing, one HARQ process can transmit at most two TBs. Figure 1 is a schematic diagram of the data flow transmission and processing process in the related technology, such as Figure 1As shown, after multiple layers of processing, the data of RBx and RBy in the radio bearer (RB) is multiplexed into a MAC PDU at the MAC layer and finally mapped to a transport block (TB). 5G Radio Access Network (RAN) pays more attention to service provision based on the full utilization of resources during data transmission processing, and insufficiently considers the differences in service performance experience. Although data streams with different QoS requirements are differentiated by mapping to different data radio bearers (DRBs) at the SDAP layer, at the MAC layer, data from different DRBs is multiplexed together again. After data is multiplexed at the MAC layer, the differences in services cannot be distinguished at the lower layer. The data transmission mapping method of the prior art is too rigid, making it difficult to improve performance while ensuring service differentiation at the lower layer and difficult to meet the demand for flexible guarantee of service performance differences. Figure 2 is a schematic structural diagram of a downlink with configured Carrier Aggregation (CA) in the related art. Figure 3 is a schematic structural diagram of an uplink with configured CA in the related art.

[0035] In a 5G (NR) wireless network, DRBs are used to carry user data transmission. Multiple DRBs can be established simultaneously between a user and a base station node, and each DRB provides the same forwarding processing for user data packets. One or more QoS flows are mapped to one DRB. Since radio resources in a wireless communication network are limited, data from different DRBs is multiplexed at the MAC layer after being processed by the PDCP layer and the RLC layer, and TB transmission on multiple HARQ processes is performed through a HARQ entity. Figure 4 is a schematic diagram of the data mapping method in the related art. As Figure 4 shown, in this data transmission method multiplexed at the MAC layer, it may occur that data of DRB1 and data of DRB2 are simultaneously mapped to the same TB of the same HARQ process of HARQ entity 1 for transmission. Since the TB is the basic unit of physical layer data scheduling and transmission, in this case, the data of DRB1 and DRB2 cannot be differentially transmitted at the physical layer because they are multiplexed on one TB.

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

[0037] The method embodiments provided in the embodiments of the present application can be executed on a mobile terminal, a computer terminal, or a similar computing device. Taking the operation on a mobile terminal as an example, Figure 5 is a hardware structural block diagram of a mobile terminal according to the data transmission method of the embodiment of the present invention. As Figure 5 shown, the mobile terminal may include one or more (Figure 5 only one processor 502 is shown (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 for storing data. Among them, the above mobile terminal may further include a transmission device 506 for communication functions and an input / output device 508. Those of ordinary skill in the art can understand that Figure 5 the structure shown is only schematic and does not limit the structure of the above mobile terminal. For example, the mobile terminal may further include more or fewer components than Figure 5 shown, or have a different configuration from Figure 5 shown.

[0038] The memory 504 can be used to store computer programs. For example, software programs and modules of application software, such as the computer program corresponding to the data transmission method in the embodiment of the present invention. The processor 502 executes various functional applications and data processing by running the computer program stored in the memory 504, that is, implements the above 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 memories. In some instances, the memory 504 may further include a memory remotely located relative to the processor 502, and these remote memories can be connected to the mobile terminal through a network. Examples of the above network include, but are not limited to, the Internet, an enterprise intranet, a local area network, a mobile communication network, and combinations thereof.

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

[0040] In an embodiment of the present invention, a network element may include one or more network nodes, one or more network functions, one or more network layers, one or more network devices, and / or one or more network entities. For example, the network element may be a RAN node (RANNode), the RRC (Radio Resource Control) layer of the RAN, the MAC layer of the RAN, the MAC entity of the RAN, a Central Unit (CU), a Distributed Unit (DU), a UE, or an Integrated Access and Backhaul (IAB) Node. 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 invention, the DRB may be at least one of the following: a communication-related radio bearer, a sensing-related radio bearer, an AI (Artificial Intelligence)-related radio bearer, a data service-related radio bearer, a computing-related radio bearer, and a security / trust-related radio bearer.

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

[0042] Step S602, a first network element obtains 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;

[0043] 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;

[0044] Step S606, the first network element delivers the data received by the HARQ entity to the upper layer through the DRB corresponding to the HARQ entity.

[0045] 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 multiple sets of information on the one-to-one configuration of the DRB and the HARQ entity. For example, the configuration information of the DRB and the HARQ entity includes two sets of information on the one-to-one configuration between the DRB and the HARQ entity: one set includes a first DRB and a first HARQ entity, denoted as the first DRB configuring the first HARQ entity; the other set includes a second DRB and a second HARQ entity, denoted as the second DRB configuring the second HARQ entity. Among them, the first HARQ entity and the second HARQ entity are different HARQ entities, the first DRB and the second DRB are different DRBs, and the first DRB is configured one-to-one with the first HARQ entity, and the second HARQ entity is configured one-to-one with the second DRB. The first network element delivers the data received by the HARQ entity included in each group to the upper layer through the DRB configured one-to-one with the HARQ entity according to the multiple sets of information on the one-to-one configuration of the DRB and the HARQ entity. 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.

[0046] Through the above steps, a HARQ entity is 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 delivered independently to the upper layer at the receiving end, thus ensuring the manifestation of the difference in service performance, effectively solving the problem that data transmission in the related art cannot be differentially transmitted at the physical layer, achieving the effect of improving the flexibility of physical layer data transmission, flexibly meeting the underlying transmission requirements of different services, and greatly improving the service transmission ability and service performance experience.

[0047] In an alternative embodiment, 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.

[0048] In an alternative embodiment, the first network element configuring a HARQ entity for a DRB based on the configuration information of the DRB and the HARQ entity may be: the HARQ entity uses the same lifecycle as the DRB. For example, when the DRB is established, the HARQ entity is correspondingly generated, and when the DRB is removed, the HARQ entity is also correspondingly deleted.

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

[0050] In an optional embodiment, the first network element configuring one HARQ entity for one DRB based on the configuration information of the DRB and the HARQ entity may be: the one HARQ entity configured for the one DRB may be that in the data transmission of multiple DRBs, the HARQ entity is only bound, corresponding, or associated with the DRB.

[0051] In an optional embodiment, the first network element configuring one HARQ entity for one DRB based on the configuration information of the DRB and the HARQ entity may be: the configuration of the DRB includes the configuration of the HARQ entity. For example, the DRB configuration parameters include the parameter configuration of the HARQ entity.

[0052] In an optional embodiment, the first network element configuring one HARQ entity for one DRB based on the configuration information of the DRB and the HARQ entity may be: the configuration of the DRB includes the HARQ entity identifier of the HARQ entity. For example, the configuration message of the DRB configuration includes the identifier of the HARQ entity (such as, HARQ entity Identity).

[0053] In an optional embodiment, 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 a first configuration message including the configuration information of the DRB and the HARQ entity, where the first request message is used to request a 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.

[0054] In an optional embodiment, after the first network element obtains the configuration information of the DRB and the HARQ entity, the method further includes: sending a second configuration message including the configuration information of the DRB and the HARQ entity to a 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.

[0055] In an optional embodiment, the method for the first network element to receive a first configuration message including 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 a second network element, where 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 the HARQ entity; the first network element receives the first configuration message from a third network element, where the third network element is a network element that does not directly send data to the first network element 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.

[0056] In the above steps, the first network element receiving the configuration message from the second network element includes, but is not limited to: when the first network element is a UE and the second network element is a base station, a 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 or an RRC reconfiguration message. When the first network element is a base station and the second network element is a UE, an uplink transmission is performed between the second network element and the first network element. Since the base station itself can send RRC messages, it knows the configuration relationship itself. Therefore, the base station can, according to the configuration information in the RRC message previously sent to the UE, deliver the data received on the HARQ entity to the upper layer through the DRB configured corresponding to the HARQ entity. For example, the UE receives an 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 the data on the HARQ entity to the upper layer 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.

[0057] In the above steps, the first network element receiving the configuration message from the third network element includes, but is 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 (without user plane data transmission), the target control signaling is an RRC message from 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 performs data transmission (without control signaling). In this case, the first network element can configure the configuration relationship between the DRB for the data received from the second network element and the HARQ entity according to the RRC message from the third network element, and deliver the data to the upper layer based on the configured configuration relationship.

[0058] 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 directly interact with the UE, the RRC message generated by the CU needs to be sent to the UE via the DU.

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

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

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

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

[0063] In the above embodiments, 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. Here, taking the first network element as the UE as an example, an illustrative description is given as follows: The RRC message, that is, the radio resource control message, 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 RRC layer of the base station. 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 being in the RRC idle state RRC_IDLE). The RRC establishment message includes an RRC establishment request message sent by the UE to the base station (for example, RRCSetupRequest message, RRCReestablishmentRequest message) and an RRC establishment message sent by the base station to the UE (for example, RRCSetupmessage). After the UE establishes an RRC connection, it will send an RRC establishment complete message (for example, RRCSetupCompletemessage). The UE can use the RRC establishment request message to send a DRB and HARQ entity configuration information request (corresponding to the request message for the configuration information mentioned in the present invention). The base station can use the RRC establishment message to send DRB and HARQ entity one-to-one configuration information (that is, the above-mentioned DRB and HARQ entity configuration information) to instruct the UE to perform radio bearer configuration. Optionally, the UE can also use the RRC establishment complete message to send the DRB and HARQ entity configuration information. The RRC reconfiguration message (RRCReconfiguration message) is used to configure the RRC connection when the UE is in a connected state (for example, RRC_CONNECTED). The UE receives the RRC reconfiguration message (for example, RRCReconfiguration message) and performs radio bearer configuration according to the radio bearer configuration information included in the RRCReconfiguration message. In the embodiments of the present invention, the base station may include the DRB and HARQ entity configuration information in the RRC reconfiguration message and send it to the UE. After receiving the RRC reconfiguration message containing the DRB and HARQ entity configuration information, the UE performs radio bearer configuration according to the configuration information. In addition, for the scenario of separate deployment of the CU (Central Unit) and DU (Distributed Unit), after the UE sends an RRC connection establishment request, the DU sends a forwarding message of the UE RRC establishment request message (for example, Initial UL RRC Message Transfer) to the CU to forward the initial uplink RRC message from the DU to the control plane (CU-CP) of the CU.The CU allocates radio resources for the UE by sending a forwarding message (DL RRC Message Transfer) of the downlink RRC message to the DU. Figure 7 is a schematic diagram of the RRC message transmission method according to an embodiment of the present invention Figure 1 , such as Figure 7 shown, the DU plays a role in forwarding RRC messages between the CU and the UE. In the present invention, the CU can configure an RRC message containing the configuration information of the DRB and the HARQ entity, and forward it to the UE through the DU. The UE can also send an RRC message containing a request for the configuration information of the DRB and the HARQ entity to the CU through the DU.

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

[0065] In an optional embodiment, the UE receives a radio bearer configuration message, and the configuration information of the DRB and the HARQ entity is carried in the radio bearer configuration message. 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.

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

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

[0068] Figure 8 is the process of the data transmission method according to an embodiment of the present invention Figure 2 , such as Figure 8 shown, the process includes the following steps:

[0069] Step S802, the second network element obtains the configuration information of the DRB and the HARQ entity, wherein the configuration information of the DRB and the HARQ entity is used to configure one 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, and each group includes a DRB identifier and a HARQ entity identifier;

[0070] 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;

[0071] Step S806, the second network element sends the data stream through the DRB to the HARQ entity corresponding to the DRB for transmission.

[0072] In step S804, when the second network element configures the HARQ entity for the DRB, it clearly indicates how to configure between each DRB and each HARQ entity. For example, there are 2 sets of configuration information: DRB1 (DRB ID = 1) is configured with HARQ entity 1 (HARQ entity ID = 1), DRB2 (DRB ID = 2) is configured with HARQ entity 2 (HARQ entity ID = 2), and dataflow1 and data flow2 are data with different service characteristics. When the second network element sends the data stream, according to the configured configuration relationship, it sends data flow1 through DRB1 to the sending-end HARQ entity 1 for transmission and sends data flow2 through DRB2 to the sending-end HARQ entity 2 for transmission. At the MAC layer, the data of the HARQ entity is placed in the HARQ process of the HARQ entity for physical layer transmission in the form of a TB. There are multiple parallel HARQ processes in each HARQ entity to support the 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 data of different DRBs is multiplexed and transmitted on the same TB.

[0073] Through the above steps, based on the configuration information of the DRB and the HARQ entity, a one-to-one configuration between the DRB and the HARQ entity can be configured to finely distinguish and independently configure data with different service characteristic requirements, so that data that needs to be transmitted differently can be transmitted separately at the physical layer, thereby ensuring the manifestation of service performance differences, effectively solving the problem that in the related art, the data transmission method multiplexes the data of different DRBs together at the MAC layer and cannot perform differential transmission of data at the physical layer, achieving the effect of improving the flexibility of physical layer data transmission, enabling flexible satisfaction of different underlying transmission requirements of services, and greatly enhancing the service transmission capacity and service performance experience.

[0074] In an optional embodiment, 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. For example, in the RadioBearerConfig IE, the DRB Identify and the HARQ entity Identify are included. For example, the RadioBearerConfig IE includes the Group ID, the DRB Identify, and the HARQ entity Identify information, indicating the HARQ entity Identify configured for each DRB Identify within the group indicated by the Group ID.

[0075] In an optional embodiment, the second network element configuring a HARQ entity for a DRB based on the configuration information of the DRB and the HARQ entity may be: the HARQ entity uses the same lifecycle as the DRB. For example, when the DRB is established, the HARQ entity is correspondingly generated, and when the DRB is removed, the HARQ entity is also correspondingly deleted.

[0076] In an optional embodiment, the second network element configuring a HARQ entity for a DRB based on the configuration information of the DRB and the HARQ entity may be: configuring 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.

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

[0078] In an optional embodiment, the second network element configuring a HARQ entity for a DRB based on the configuration information of the DRB and the HARQ entity may be that the configuration of the DRB includes the configuration of the HARQ entity. For example, the DRB configuration parameters include the parameter configuration of the HARQ entity.

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

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

[0081] In an optional embodiment, 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 the 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 the 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 the 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 the network element that sends data to the second network element according to the configuration information of the DRB and the HARQ entity.

[0082] In an optional embodiment, 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 to enable the first network element to receive data according to the configuration information of the DRB and the HARQ entity, where the first network element is the network element that receives data from the second network element according to the configuration information of the DRB and the HARQ entity.

[0083] In an optional embodiment, 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 the third request message sent by the first network element for requesting the configuration information of the DRB and the HARQ entity. For example, the UE first sends a request message for the configuration information of the DRB and the 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 the HARQ entity to the UE (such as the configuration message is an RRC reconfiguration message).

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

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

[0086] 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 request response message.

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

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

[0089] In an optional embodiment, delivering the data stream through the DRB to the HARQ entity corresponding to the DRB for transmission includes: the second network element transmits the data stream according to the service characteristics of the data stream to be transmitted, wherein data streams with different service characteristics are delivered through different DRBs to the HARQ entities configured correspondingly for transmission.

[0090] In the above steps, a specific DRB can be configured for a data stream with specific service characteristics. The configuration method includes, but is not limited to: configuring data streams with the same service characteristic information to the same DRB, and configuring data streams with different service characteristic information to different DRBs. For example, for dataflow1, dataflow2, dataflow3, and dataflow4, the service characteristic information of these four data streams are that the data packets have an in-sequence delivery requirement, the data packets do not have an in-sequence delivery requirement, the data packets have a high-reliability transmission requirement, and the data packets have a low reliability requirement, respectively. The second network element can configure the data stream dataflow1 with an in-sequence delivery requirement to DRB1; configure the data stream dataflow2 without an in-sequence delivery requirement to DRB2, configure the data stream dataflow3 with a high-reliability requirement to DRB3, and configure the data stream dataflow4 with a low reliability requirement to DRB4.

[0091] In an optional embodiment, the service characteristics include at least one of the following: data packet in-sequence transmission service indication, data packet non-in-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 ID, service name identifier.

[0092] In an optional embodiment, the method further includes: the second network element obtains the service characteristics through at least one of the following methods: receiving service characteristic information from the core network, parsing NAS signaling to obtain service characteristic information, parsing QoS parameter information to obtain service characteristic information, parsing service characteristic information carried along with the data stream in the data stream to obtain service characteristic information, obtaining service characteristic information through DPI (Deep Packet Inspection), obtaining service characteristic information through AI (Artificial Intelligence) inference, and obtaining service characteristic information through big data analysis.

[0093] 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. When the first network element is a UE and the second network element is a base station, downlink transmission is performed between the second network element and the first network element. In this case, the base station transmits configuration information (i.e., the above configuration information of the DRB and the HARQ entity) and downlink data to the UE. This downlink data can be sent out 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 the DRB for data reception and upward delivery.

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

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

[0096] Specific Embodiment 1: Data transmission process on the base station side during downlink transmission

[0097] 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 the HARQ entity and sends the data according to the configuration information. The base station also notifies the UE of the configuration information of the DRB and the HARQ entity through RRC messages (such as RRC connection establishment message, RRC reconfiguration message).

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

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

[0100] For example, there are four data streams, dataflow1, dataflow2, dataflow3, and dataflow4. The service characteristic information of these four data streams is that the data packets have an in-sequence requirement, the data packets do not require in-sequence, the data packets have a high-reliability transmission requirement, and the reliability requirement of the data packets is low. The base station maps the data stream dataflow1 with an in-sequence requirement to DRB1; maps the data stream dataflow2 without in-sequence requirement to DRB2, maps the data stream dataflow3 with a high-reliability requirement to DRB3, and maps the data stream dataflow4 with a low-reliability requirement to DRB4.

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

[0102] Among them, when the base station configures the DRB and the HARQ entity, it clearly indicates how each DRB and each HARQ entity are 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 through an RRC connection establishment message or an RRC reconfiguration message, so that the UE knows how the DRB and the HARQ entity are configured.

[0103] Step 3: The base station configures the 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 the data to be sent to the HARQ entity through the DRB for sending.

[0104] Among them, when the base station sends data, according to the configuration information, it 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 through DRB2 for transmission. The MAC - layer entity physically transmits the data configured to the HARQ entity 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. The 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 different - service data can be distinguished at the physical layer, different physical - layer transmission means can be adopted for different - service data. For example, reducing the MCS level for the TB transmission of high - reliability data streams and increasing the transmission power of the time slots for high - reliability data - stream transmission, etc.

[0105] It can be seen from this that in this embodiment, different - service - characteristic - requirement data streams can be mapped to different DRBs through classification, and then different DRBs are configured to different HARQ entities to realize the association between services and HARQ entities. Finally, different data streams are distinguished on the TB through the HARQ entity. Through this embodiment, differential transmission of service data is realized, especially in the physical - link transmission, the service differentiation is clearly distinguished and personalized guaranteed.

[0106] Specific Embodiment 2: UE - side data - transmission process during downlink transmission

[0107] When the base station sends data to the UE, the base station will configure DRB and HARQ entities and inform the UE of the configuration information of the relevant DRB and HARQ entities through RRC messages (such as RRC connection - establishment messages, RRC re - configuration messages). After receiving the configuration information, the UE can know which DRB the HARQ - entity configuration corresponds to. The UE delivers the downlink data received on the HARQ entity to the upper layer through the DRB corresponding to the HARQ - entity configuration.

[0108] Specific steps of the UE as the receiving - end during downlink transmission are exemplified as follows:

[0109] Step 1 (it should be noted that this step is an optional step, and in actual applications, it can also skip Step 1 and directly execute subsequent steps): The UE sends a request message carrying a request for DRB and HARQ - entity configuration information.

[0110] The request message sent by the UE can be an RRC establishment - request (RRC Setup Request) message or an RRC configuration - request message.

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

[0112] By receiving the configuration information including DRB and HARQ entity configuration information, the UE can know which DRB each HARQ entity corresponds to, and then deliver the downlink data to the upper layer through the DRB configured corresponding to the HARQ entity. The base station sends the DRB and HARQ entity configuration information to the UE in the RRC connection establishment message (RRC Setup message) or the RRC reconfiguration message, and the UE obtains the configuration information by receiving the above RRC message.

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

[0114] The configuration information of the DRB and the HARQ entity may include multiple sets of DRB and HARQ entity configuration information. For example, the first DRB is configured with the first HARQ entity, and the second DRB is configured with the second HARQ entity. According to the one-to-one configuration information of multiple sets of DRB 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.

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

[0116] Specific Embodiment 3: UE-side data configuration process during uplink transmission

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

[0118] Among them, the specific steps of the UE side as the transmitter during uplink transmission are exemplified as follows:

[0119] Step 1: The UE sends an RRC request message for DRB and HARQ entity configuration information. For example, the UE requests to configure HARQ entities for DRBs of 4 uplink data streams.

[0120] Step 2: The UE receives an RRC configuration message sent by the base station and containing DRB and HARQ entity configuration information. The RRC configuration message may be an RRC reconfiguration message or an RRC request response message. Among the DRB and HARQ entity configuration information sent by the base station, the configuration relationships of one or more groups of DRBs and HARQ entities are indicated. 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 for the UE's uplink data transmission.

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

[0122] For example, there are four data streams: dataflow1, dataflow2, dataflow3, and dataflow4. The service characteristic information of these four data streams is that the data packets have an in-sequence requirement, the data packets do not have an in-sequence requirement, the data packets have a high-reliability transmission requirement, and the data packets have a low reliability requirement respectively. The UE maps the data stream dataflow1 with an in-sequence requirement to DRB1 according to the indication of the mapping relationship by the base station; maps the data stream dataflow2 without an in-sequence requirement to DRB2, maps the data stream dataflow3 with a high-reliability requirement to DRB3, and maps the data stream dataflow4 with a low reliability requirement to DRB4.

[0123] Step 4: The UE delivers 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 for transmission.

[0124] Since the physical layer at the transmitting end can distinguish data of different services, different physical layer transmission means can be adopted for different service data. For example, the MCS level is reduced for the TB transmission of high-reliability data streams, and the transmission power of the time slots for high-reliability data stream transmission is increased, etc. For example, a dedicated DRB is established for a high-speed transmission data stream, and a dedicated HARQ entity is configured. Targeted measures such as special optimization and dedicated hardware processing can be adopted to ensure high-speed data transmission.

[0125] It can be seen from this that in this embodiment, data streams with different service feature requirements can be mapped to different DRBs through classification, and then different DRBs are configured to different HARQ entities to realize the association between services and HARQ entities. Since the TBs of different HARQ entities are different, different data streams can be guaranteed to be separated at the physical layer through the HARQ entities. Through this embodiment, differential transmission of service data is realized, especially clear differentiation and personalized guarantee of service differentiation in physical link transmission.

[0126] Specific Embodiment Four: Data Transmission Process on the Base Station Side during Uplink Transmission

[0127] When the base station receives data sent by the UE, the base station 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 RRC messages (such as RRC connection establishment messages, RRC reconfiguration messages) 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.

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

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

[0130] Step 2: The base station sends an RRC configuration message containing the 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. In the DRB and HARQ entity configuration information sent by the base station, the configuration relationships of one to multiple groups of DRBs and HARQ entities are indicated. For example, there are 4 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.

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

[0132] 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 configured respectively.

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

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

[0135] 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 for one DRB;

[0136] Step S904, the third network element sends the configuration information of the DRB and the HARQ entity.

[0137] Through the above steps, a corresponding HARQ entity can be configured for each DRB based on the configuration information of the DRB and the HARQ entity, so that data that needs to be differentially transmitted can be transmitted separately at the physical layer, thus ensuring the embodiment of service performance differences, effectively solving the problem that in the related art, data of different DRBs are multiplexed together at the MAC layer and data cannot be differentially transmitted at the physical layer, achieving the effect of improving the flexibility of physical layer data transmission, flexibly meeting the underlying transmission requirements of different services, and greatly improving the service transmission capacity and service performance experience.

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

[0139] In an optional embodiment, the configuration information of the DRB and the 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 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 delivers 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 delivers the data from the DRB to the HARQ entity for sending.

[0140] In an optional embodiment, the third network element configuring one HARQ entity for one DRB based on the configuration information of the DRB and the HARQ entity may be: the HARQ entity uses the same lifecycle as the DRB. For example, when the DRB is established, the HARQ entity is correspondingly generated, and when the DRB is removed, the HARQ entity is also correspondingly deleted.

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

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

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

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

[0145] 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 stations that only send control signaling use low-frequency carriers to achieve wide coverage of control signaling, and the base stations that only perform data transmission can use high-frequency carriers to achieve short-distance high-speed data transmission. Figure 10 It is a schematic diagram of the RRC message transmission method according to an embodiment of the present invention Figure 2 , such as Figure 10 shown, 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 transmitted in the RRC messages of the base station that only sends control signaling. 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 may transmit the configuration information through an interface between base stations (for example, the X2 interface, the Xn interface). The UE receives the RRC information sent by the base station that only sends control signaling and performs downlink data reception or uplink data transmission with the base station that only performs data transmission according to the configuration information. Moreover, for the scenario of macro base station and micro base station networking, 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 an indication for the micro base station and the UE connected to the micro base station to configure the HARQ entity for the DRB by sending an RRC message including the configuration information of the DRB and HARQ entities corresponding to the micro base station - micro base station serving UE.

[0146] In the above steps, 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, 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 does not directly interact with the UE, and the RRC messages generated by the CU are sent to the UE via the DU. Among them, the CU and the DU interact through the F1 interface. The physical high layer, MAC, and RLC layers with high real-time requirements are processed in the DU, while the PDCP and RRC layers with low real-time requirements are placed in the CU for processing. When the CU and the DU are not integratedly deployed, the DU first receives information from the UE and then sends it to the CU through the F1 interface. When downlink data arrives, the CU processes it first, then transmits it to the DU through the F1 interface, and then passes it to the UE through the air interface. In the present invention, the CU sends an RRC message containing the configuration information of the DRB and the HARQ entity to the DU, and the DU forwards the configuration information to the UE, and the DU and the UE perform the configuration of uplink and downlink data transmission according to the configuration relationship. For downlink transmission, according to the DRB and HARQ entity configuration information in the RRC message of the CU, the DU places the data on one DRB on the HARQ entity configured for the DRB and sends it. For uplink transmission, according to the DRB and HARQ entity configuration information in the RRC message of the CU, the DU places the data received on one HARQ entity on the corresponding DRB configured and submits it to the upper layer.

[0147] In an optional embodiment, 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, where the fifth configuration message includes at least one of the following: an RRC message, a DRB configuration message.

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

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

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

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

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

[0153] The present invention provides a data transmission configuration process for binding a DRB to a HARQ entity. The binding of the DRB to the HARQ entity is a one-to-one configuration of the DRB and the HARQ entity or one HARQ entity is configured for each DRB.

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

[0155] Step S1102, the receiving end obtains the configuration information of the DRB and the HARQ entity. The obtaining method is, for example, receiving a control signal (such as an RRC message) containing the configuration information. The control signal contains a fixed configuration indication of the DRB for the HARQ entity;

[0156] Step S1104, configure each HARQ entity to be associated with each DRB according to the configuration information of the DRB and the HARQ entity;

[0157] Step S1106, each HARQ entity at the receiving end receives TB data of multiple processes and performs physical layer decoding;

[0158] Step S1108, the data of each HARQ entity at the receiving end is delivered to the upper layer through the DRB configured corresponding to the HARQ entity.

[0159] Figure 12 is the flow of the data transmission method according to the embodiment of the present invention Figure 5 , Figure 13 is a schematic diagram of the data configuration method according to the embodiment of the present invention. The processing steps at the transmitting end are as follows:

[0160] Step S1202, the transmitting end obtains the service characteristic information of the data stream;

[0161] Step S1204, the transmitting end maps data streams with different same service characteristic requirements to different DRBs according to the service characteristic information;

[0162] Step S1206, the transmitting end obtains the configuration information of the DRB and the HARQ entity;

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

[0164] Step S1210, according to the configuration information of the DRB and the HARQ entity, the transmitting end delivers the data to be sent to the HARQ entity through the DRB for sending;

[0165] Step S1212, each HARQ entity configures multi-process TB transmission.

[0166] In the above steps, after the transmitting end obtains the configuration information of the DRB and the HARQ entity, it also sends the configuration information to the receiving end. The existing mechanism cannot meet the requirements of personalized transmission at the underlying layer (such as the physical layer), and lacks flexibility in terms of personalized guarantee for services. Through the refined differentiation, independent configuration, and personalized resource configuration of data with different service characteristic requirements in the above steps, the underlying transmission requirements of different services are flexibly met, and there is a great improvement in service transmission capabilities and service performance experience.

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

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

[0169] Figure 14 is a structural block diagram of the data transmission device according to an embodiment of the present invention Figure 1 , as Figure 14 shown, this device is applied to the first network element and includes: a first acquisition module 142, configured to acquire 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; 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 the upper layer through the DRB corresponding to the HARQ entity.

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

[0171] In an optional embodiment, the first configuration module 144 includes at least one of the following: a first cycle unit for the HARQ entity to use the same lifecycle as the DRB; a first delivery unit for the HARQ entity to deliver data to the upper layer only through the DRB in data transmission involving multiple DRBs; a first binding unit for the HARQ entity to bind only to the DRB in data transmission involving multiple DRBs; a first correspondence unit for the HARQ entity to correspond only to the DRB in data transmission involving multiple DRBs; a first association unit for the HARQ entity to associate only with the DRB in data transmission involving multiple DRBs; a first configuration unit for the configuration of the DRB to include the configuration of the HARQ entity; and a second configuration unit for the configuration of the DRB to include the HARQ entity identifier of the HARQ entity.

[0172] In an optional embodiment, the first acquisition module 142 includes at least one of the following: a first generation unit for generating the configuration information of the DRB and the HARQ entity; a first reception unit for the first network element to receive a first configuration message including the configuration information of the DRB and the HARQ entity; and a first transmission unit for the first network element to first send a first request message and then receive a first configuration message including the configuration information of the DRB and the HARQ entity, where 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.

[0173] In an optional embodiment, the apparatus further includes: a fourth transmission module for, after acquiring the configuration information of the DRB and the HARQ entity, 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, where the second configuration message includes at least one of the following: a radio resource control (RRC) message and a radio bearer configuration message.

[0174] 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, where 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 the HARQ entity; a second receiving subunit, configured to receive the first configuration message from a third network element, where the third network element is a network element that does not directly send data to the first network element according to the configuration information of the DRB and the HARQ entity; a third receiving subunit, configured to receive 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.

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

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

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

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

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

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

[0181] Figure 15 is the structural block diagram of the data transmission device according to the embodiment of the present invention Figure 2 , such as Figure 15As shown, the device is applied to a second network element and includes: a second acquisition module 152, configured to acquire 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; 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; and a second transmission module 156, configured to hand over a data stream to the HARQ entity corresponding to the DRB for transmission through the DRB.

[0182] In an optional embodiment, the configuration information of the DRB and the 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 the HARQ entity.

[0183] In an optional embodiment, the second configuration module 154 includes at least one of the following: a second cycle unit, configured to enable the HARQ entity to use the same lifecycle as the DRB; a second submission unit, configured to enable the HARQ entity to submit data to an upper layer only through the DRB during data transmission of multiple DRBs; a second binding unit, configured to enable the HARQ entity to be bound only to the DRB during data transmission of multiple DRBs; a second correspondence unit, configured to enable the HARQ entity to correspond only to the DRB during data transmission of multiple DRBs; a second association unit, configured to enable the HARQ entity to be associated only with the DRB during data transmission of multiple DRBs; a third configuration unit, configured to configure the DRB to include configuring the HARQ entity; and a fourth configuration unit, configured to configure the DRB to include the HARQ entity identifier of the HARQ entity.

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

[0185] 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 a 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; a fifth receiving subunit, configured to receive the third configuration message from a 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; a sixth receiving subunit, configured to receive 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.

[0186] In an optional embodiment, the apparatus further includes: a fifth sending module, configured to send a fourth configuration message including the configuration information of the DRB and the HARQ entity to a 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.

[0187] In an optional embodiment, the apparatus further 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 the HARQ entity to 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.

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

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

[0190] 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 request response message.

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

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

[0193] 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 to be sent, where data streams with different service characteristics are sent by different DRBs to their corresponding configured HARQ entities.

[0194] In an optional embodiment, 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 ID, service name identifier.

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

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

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

[0198] Figure 16 is the structural block diagram of the data transmission device according to the embodiment of the present invention Figure 3 , as Figure 16 shown, the device is applied to a third network element and includes: a first generation module 162, configured to generate 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; a third sending module 164, configured to send the configuration information of the DRB and the HARQ entity.

[0199] In an optional embodiment, 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, the group identifier of the DRB and HARQ entity configuration.

[0200] 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 a first network element, so that when receiving data, the first network element delivers 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 a second network element, so that when sending data, the second network element delivers the data from the DRB 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 receiving data, the first network element delivers the data received by the HARQ entity 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 sending data, the second network element delivers the data from the DRB to the HARQ entity for sending.

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

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

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

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

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

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

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

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

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

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

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

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

[0213] Obviously, those skilled in the art should understand that the above modules or steps of the present invention can be implemented by a general-purpose computing device. They can be concentrated on a single computing device or distributed on a network composed of multiple computing devices. They can be implemented by program codes executable by the computing device, so that they can be stored in a storage device and executed by the computing device. And in some cases, the steps shown or described can be executed in a different order than here, or they can be separately made into individual integrated circuit modules, or multiple modules or steps among them can be made into a single integrated circuit module to implement. In this way, the present invention is not limited to any specific combination of hardware and software.

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

Claims

1. A data transmission method, characterized in that, Applied to a first 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 to the DRB; Deliver the data received by the HARQ entity to the 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, characterized in that 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 a first configuration message including the configuration information of the DRB and the HARQ entity, where the first request message is used to request a 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 a 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, characterized in that After the first network element obtains the configuration information of the DRB and the HARQ entity, the method further includes: sending a second configuration message including the configuration information of the DRB and the HARQ entity to a 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, where 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 a second network element, where 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 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, characterized in that, 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, characterized in that The first request message includes at least one of the following: RRC request message, radio bearer configuration request message.

9. A data transmission method, characterized in that, Applied to the second network element, the method includes: Obtain the configuration information of the Data Radio Bearer (DRB) and the 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; Deliver the 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, characterized in that, 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 the data transmission of multiple DRBs, the HARQ entity only delivers data to the upper layer through the DRB; In the data transmission of multiple DRBs, the HARQ entity is only bound to the DRB; In the data transmission of multiple DRBs, the HARQ entity only corresponds to the DRB; In the data transmission of multiple DRBs, the HARQ entity is only associated with the DRB; The configuration of the DRB includes the configuration of the HARQ entity; The configuration of the DRB includes the HARQ entity identifier of the HARQ entity.

12. The method according to any one of claims 9 to 11, characterized in that 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 the 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 the 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 the 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 the 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, characterized in that, 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 the 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, characterized in that, 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, characterized in that, 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, characterized in that, 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, characterized in that 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 sending 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 data streams with different service characteristics are handed to the corresponding configured HARQ entities for sending 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, characterized in that, Applied to the third network element, it includes: Generating the configuration information of the data radio bearer (DRB) and the 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, characterized in that, 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 receiving data, the first network element 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 delivers 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 receiving data, the first network element 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 delivers the data from the DRB to the HARQ entity for sending.

25. The method according to any one of claims 22 to 24, characterized in that 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, characterized in that, A computer program is stored in the computer-readable storage medium, 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, characterized in that, When the processor executes the computer program, it implements the steps of the method described in any one of claims 1 to 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