Data transmission methods, apparatuses and storage medium

Abstract

The embodiments of the present disclosure provide data transmission methods, apparatuses, and a storage medium. A method comprises: receiving unidirectional link data radio bearer (DRB) configuration information from a second network element, the unidirectional link DRB configuration information being used for configuring a DRB dedicated to an unidirectional link; and, on the basis of the unidirectional link DRB configuration information, configuring a DRB dedicated to an unidirectional link.

Description

Data transmission method, device and storage medium

[0001] This disclosure claims priority to Chinese patent application No. 202410083064.6, filed on January 19, 2024, the entire contents of which are incorporated herein by reference. Technical Field

[0002] The present disclosure relates to the field of communication technologies, and in particular to a data transmission method, device, and storage medium. Background Art

[0003] With the development of fifth-generation mobile networks (5G), communication services are becoming increasingly diverse, and significant differences in service requirements have emerged between uplink and downlink data transmission. For example, traditional video services have high bandwidth and throughput requirements for downlink data transmission, but relatively low requirements for uplink data transmission. Another example is gaming and live streaming services, which have high uplink throughput and latency requirements but may not have high downlink throughput requirements. Summary of the Invention

[0004] In a first aspect, a data transmission method is provided, applied to a first network element. The method includes:

[0005] receiving unidirectional link data radio bearer (DRB) configuration information from the second network element, where the unidirectional link DRB configuration information is used to configure a DRB dedicated to the unidirectional link;

[0006] Based on the unidirectional link DRB configuration information, a DRB dedicated to the unidirectional link is configured.

[0007] In a second aspect, a data transmission method is provided, which is applied to a second network element. The method includes:

[0008] Unidirectional link DRB configuration information is sent to the first network element, where the unidirectional link DRB configuration information is used to configure a DRB dedicated to the unidirectional link.

[0009] In a third aspect, a communication device is provided, applied to a first network element. The device includes:

[0010] A receiving unit, configured to receive unidirectional link DRB configuration information from a second network element, where the unidirectional link DRB configuration information is used to configure a DRB dedicated to the unidirectional link;

[0011] The processing unit is used to configure a DRB dedicated to the unidirectional link based on the unidirectional link DRB configuration information.

[0012] In a fourth aspect, a communication device is provided, which is applied to a second network element. The device includes:

[0013] The sending unit is used to send unidirectional link DRB configuration information to the first network element, where the unidirectional link DRB configuration information is used to configure a DRB dedicated to the unidirectional link.

[0014] In a fifth aspect, a communication device is provided, comprising: a processor and a memory; the memory and the processor are coupled; the memory is used to store instructions executable by the processor; when the processor is configured to execute the instructions, the communication device implements the method provided in any one of the first or second aspects above.

[0015] In a sixth aspect, a computer-readable storage medium is provided, which stores computer instructions. When the computer instructions are executed on a computer, the computer executes the method provided in either the first aspect or the second aspect.

[0016] In a seventh aspect, a computer program product comprising computer instructions is provided, which, when executed on a computer, enables the computer to execute the method provided in either the first aspect or the second aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] The accompanying drawings are used to provide a further understanding of the technical solution of the present disclosure and constitute a part of the specification. Together with the embodiments of the present disclosure, they are used to explain the technical solution of the present disclosure and do not constitute a limitation to the technical solution of the present disclosure.

[0018] FIG1 is a schematic structural diagram of a communication system provided by an embodiment of the present disclosure.

[0019] FIG2 is a flow chart of a data transmission method provided by an embodiment of the present disclosure.

[0020] FIG3 is a schematic diagram of an association relationship provided by an embodiment of the present disclosure.

[0021] FIG4 is another schematic diagram of an association relationship provided by an embodiment of the present disclosure.

[0022] FIG5 is another schematic diagram of an association relationship provided by an embodiment of the present disclosure.

[0023] FIG6 is another schematic diagram of an association relationship provided by an embodiment of the present disclosure.

[0024] FIG. 7 is another schematic diagram of an association relationship provided by an embodiment of the present disclosure.

[0025] FIG8 is another schematic diagram of an association relationship provided by an embodiment of the present disclosure.

[0026] FIG9 is a schematic diagram of using uplink and downlink DRBs for data transmission in a DC scenario provided by an embodiment of the present disclosure.

[0027] FIG10 is a schematic diagram of using uplink and downlink DRBs for data transmission in a mobile scenario provided by an embodiment of the present disclosure.

[0028] FIG11 is a flow chart of another data transmission method provided by an embodiment of the present disclosure.

[0029] FIG12 is a schematic diagram showing the composition of a communication device provided in an embodiment of the present disclosure.

[0030] FIG13 is a schematic diagram showing the composition of another communication device provided in an embodiment of the present disclosure.

[0031] FIG14 is a schematic structural diagram of a communication device provided in an embodiment of the present disclosure. DETAILED DESCRIPTION

[0032] The following will be combined with the accompanying drawings in the embodiments of the present disclosure to clearly and completely describe the technical solutions in the embodiments of the present disclosure. Obviously, the embodiments described are only part of the embodiments of the present disclosure, not all of the embodiments. Based on the embodiments of the present disclosure, all other embodiments obtained by ordinary technicians in this field without making any creative efforts are within the scope of protection of the present disclosure.

[0033] Unless the context requires otherwise, throughout the specification and claims, the term "comprise" and its other forms, such as the third person singular form "comprises" and the present participle form "comprising", are to be interpreted as open and inclusive, that is, "including, but not limited to". In the description of the specification, the terms "one embodiment", "some embodiments", "exemplary embodiments", "example", "specific example" or "some examples" are intended to indicate that the particular features, structures, materials or characteristics associated with the embodiment or example are included in at least one embodiment or example of the present disclosure. The schematic representation of the above terms does not necessarily refer to the same embodiment or example. In addition, the particular features, structures, materials or characteristics may be included in any one or more embodiments or examples in any appropriate manner.

[0034] The terms "first," "second," etc., are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of the technical features being referred to. Thus, a feature identified with "first," "second," etc., may explicitly or implicitly include one or more of such features. Throughout this disclosure, unless otherwise specified, "plurality" means two or more.

[0035] In the embodiments of the present disclosure, words such as "exemplarily" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as "exemplarily" or "for example" in the embodiments of the present disclosure should not be construed as being preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplarily" or "for example" is intended to present the relevant concepts in an illustrative manner.

[0036] Additionally, the use of “based on” is meant to be open and inclusive, as a process, step, calculation, or other action “based on” one or more stated conditions or values ​​may, in practice, be based on additional conditions or values ​​beyond those stated.

[0037] A radio bearer (RB) is a general term for the different layer protocol entities and configurations allocated by a base station to user equipment (UE). These include the service data adaptation protocol (SDAP), packet data convergence protocol (PDCP) protocol entities, radio link control layer (RLC) protocol entities, medium access control (MAC) protocol entities, and a series of resources allocated by the physical layer (PHY). In 5G New Radio (NR) wireless networks, DRBs are used to carry user data packets, and signaling radio bearers (SRBs) are used to carry user signaling messages. For data transmission, multiple DRBs can be established simultaneously between the UE and the base station node, each providing the same forwarding processing for data packets. A protocol data unit session (PDU session) can have multiple quality of service (QoS) flows. At the SDAP layer, one or more QoS flows are mapped to a DRB. Data from different DRBs is multiplexed at the MAC layer after being processed by the PDCP and RLC layers. At the MAC layer, the MAC entity transmits transport blocks (TBs) across multiple HARQ processes using a hybrid automatic repeat request (HARQ) entity.

[0038] In 5G, the parameter configuration of each layer protocol entity for uplink data transmission and downlink data transmission is implemented through the configuration of a bearer by the RRC layer. The uplink and downlink parameter configurations are included in the configuration of a DRB. Since the data under the same DRB uses the same forwarding process, the use of the same DRB for uplink and downlink will also make the forwarding process of uplink data and downlink data the same. In a dual-connection scenario, whether it is uplink data transmission or downlink data transmission, it corresponds to the same master node (MN), secondary node, master cell group (MCG) and secondary cell group (SCG). Accordingly, the MCG bearer and SCG bearer cannot distinguish between uplink data transmission and downlink data transmission. In addition, when multiple carriers are used for data transmission, the uplink and downlink data transmission use the same primary carrier component (PCC) and each carrier corresponds to a HARQ entity.

[0039] As communication services become increasingly diverse, there are large differences in service requirements between uplink and downlink data transmission. For example, traditional video services have large demands on bandwidth and throughput for downlink data transmission, but small demands on uplink data transmission. For another example, gaming services and live broadcast services have high requirements for uplink throughput and also have large demands on latency. However, the current 5G configuration of DRB, HARQ entity and resources is highly coupled, which makes the correlation between uplink data transmission and downlink data transmission very high. In other words, the relevant technology is a design with tight uplink and downlink coupling. Regardless of uplink or downlink data transmission, the same HARQ entity, DRB, service cell and physical resources are configured in the base station and UE. When the uplink and downlink services are very different, it is difficult for the same configuration to adapt to both uplink and downlink data transmission, resulting in high transmission complexity.

[0040] Based on this, the embodiments of the present disclosure provide a data transmission method, device and storage medium. The first network element configures a DRB dedicated to the unidirectional link based on the unidirectional link DRB configuration information from the second network element. In this way, each unidirectional link has a dedicated DRB, so that data transmission is carried out based on the DRB dedicated to each unidirectional link, reducing the complexity of data transmission.

[0041] The following describes the solutions of the embodiments of the present disclosure in conjunction with the accompanying drawings.

[0042] The technical solutions provided in the embodiments of the present disclosure can be applied to 5G or the sixth-generation mobile communication network (the sixth-generation, 6G), etc., and the embodiments of the present disclosure are not limited to this. The technical solutions provided in the embodiments of the present disclosure can be used in various mobile communication network scenarios, including traditional cellular scenarios, sidelink (SL) communication scenarios, integrated access backhaul (IAB) scenarios, etc., and the embodiments of the present disclosure are not limited to this.

[0043] In the embodiment of the present disclosure, the first network element includes, but is not limited to, at least one of the following: RAN (radio access network), UE, CU, DU, relay node, IAB node, on-board unit (OBU), and roadside unit (RSU). The second network element includes, but is not limited to, at least one of the following: RAN, UE, CU, DU, relay node, IAB node, OBU, and RSU.

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

[0045] FIG1 is a schematic diagram of the structure of a communication system provided by an embodiment of the present disclosure. As shown in FIG1 , the communication system 10 includes multiple base stations (e.g., base station 21 and base station 22) and multiple terminals (e.g., terminal 31, terminal 32, terminal 33, and terminal 34). The multiple base stations and the multiple terminals can be connected via a wired network or a wireless network. The wired network or wireless network may include routers, switches, or other devices that facilitate communication between the multiple base stations and the multiple terminals, which is not limited by the embodiment of the present disclosure.

[0046] In some embodiments, a base station is used to provide wireless access services to multiple terminals. For example, a base station provides a service coverage area (also called a cell). Terminals within this area can communicate with the base station via wireless signals to receive the wireless access services provided by the base station. The service coverage areas of base stations may overlap, and terminals within the overlapping areas can receive wireless signals from multiple base stations.

[0047] In some embodiments, each of the multiple base stations can be connected to multiple terminals. For example, base station 21 is connected to terminal 31 and terminal 32. Terminal 31 and terminal 32 can be located in the same cell or in different cells. In other words, a base station can provide network services to terminals in one cell or to terminals in multiple cells simultaneously.

[0048] In some embodiments, each of the multiple base stations (e.g., base station 21) can be an evolution nodeB (eNB), a next-generation nodeB (gNB), a transmission receive point (TRP), a transmission point (TP), an access point (AP), or any other access node. Based on the size of the service coverage area provided, base stations can be further divided into macro base stations for providing macro cells, micro base stations for providing pico cells, and femto base stations for providing femto cells. With the continuous evolution of wireless communication technology, future base stations may also adopt other names.

[0049] In some embodiments, each of the multiple terminals (e.g., terminal 31) may be a device with wireless transceiver capabilities, such as a mobile phone, a tablet computer, a wearable device, an in-vehicle device, an augmented reality (AR) / virtual reality (VR) device, a laptop computer, an ultra-mobile personal computer (UMPC), a netbook, a personal digital assistant (PDA), etc. The embodiments of the present disclosure do not limit the specific type of the terminal.

[0050] In some embodiments, terminals can communicate with each other, for example, terminal 31 and terminal 32 in Figure 1 perform SL communication, and terminal 33 and terminal 34 perform SL communication. Terminal-to-terminal communication refers to direct communication between two terminals. Taking device-to-device (D2D) communication as an example, terminals performing D2D communication can be called D2D terminals, and the link between two terminals performing D2D communication can be called a pair of D2D links. The two terminals in a pair of D2D links can serve as receivers and transmitters to each other. In a transmission, one terminal can be a transmitter and the other terminal can be a receiver. If both terminals support simultaneous transmission and reception, each D2D terminal can serve as both a transmitter and a receiver.

[0051] It should be understood that Figure 1 is an exemplary structural diagram, and the number of devices included in the communication system shown in Figure 1 is not limited, for example, the number of base stations is not limited, and the number of terminals is not limited. Furthermore, in addition to the devices shown in Figure 1, the communication system shown in Figure 1 may also include other devices, which is not limited.

[0052] Next, as shown in FIG2 , an embodiment of the present disclosure provides a data transmission method. The method is applied to a first network element. The first network element may be any terminal shown in FIG1 , such as terminal 31. The method may include the following steps:

[0053] S101. Receive unidirectional link DRB configuration information from a second network element.

[0054] In some embodiments, in order to reduce the complexity of data transmission, after configuring the unidirectional link DRB configuration information, the second network element may send the unidirectional link DRB configuration information to the first network element. Accordingly, the first network element receives the unidirectional link DRB configuration information from the second network element. The unidirectional link DRB configuration information is used to configure a DRB dedicated to the unidirectional link. In the case of distinguishing between uplink and downlink scenarios, the second network element may be the base station 21 shown in FIG1 above. In scenarios such as D2D, vehicle to X communication (V2X), IAB, SL, and intelligent interaction that do not distinguish between uplink and downlink, taking the first network element as the terminal 31 shown in FIG1 above as an example, the second network element may be the terminal 32 connected to the terminal 31 shown in FIG1 above, or the base station 21 shown in FIG1 above. The embodiments of the present disclosure do not limit the specific implementation of the second network element. Moreover, in the above-mentioned scenario where uplink and downlink are not distinguished, the first network element can also be other devices to act as a transmitter or receiver for data transmission. For example, the first network element can be an IAB node to act as a transmitter or receiver for data transmission. For another example, the first network element can be an intelligent robot to act as a transmitter or receiver for data transmission.

[0055] In some embodiments, a unidirectional link includes any one of the following: an uplink, a downlink, a transmit link, and a receive link. For example, taking the first network element as a terminal and the second network element as a base station, the uplink refers to the data transmission path for the terminal to send data to the base station, and the downlink refers to the data transmission path for the base station to send data to the terminal. For example, taking the first network element as a first terminal and the second network element as a second terminal, the transmit link refers to the data transmission path for the first terminal to send data to the second terminal, and the receive link refers to the data transmission path for the first terminal to receive data sent by the second terminal.

[0056] In some embodiments, a unidirectional link-specific DRB includes any one of the following: an uplink-specific DRB, a downlink-specific DRB, a transmission link-specific DRB, and a reception link-specific DRB. The transmission link may also be referred to by other names, such as a sending link, which is not limited in the present disclosure.

[0057] In some embodiments, the unidirectional link DRB configuration information only includes information related to the unidirectional link. Taking the unidirectional link as an uplink as an example, the uplink DRB configuration information may only include information related to the uplink, and not include information related to the downlink. Taking the unidirectional link as a downlink as an example, the downlink DRB configuration information may only include information related to the downlink, and not include information related to the uplink. In this way, the uplink DRB configuration is decoupled from the downlink DRB configuration, so that the first network element can perform independent uplink and downlink data transmission according to the differences between the uplink and downlink services, thereby reducing the complexity of data transmission.

[0058] In some embodiments, the unidirectional link DRB configuration information includes at least one of the following: an identifier of a DRB dedicated to the unidirectional link, an identifier of a HARQ entity dedicated to the unidirectional link, a set of physical resources corresponding to the unidirectional link, SDAP configuration information of the unidirectional link, PDCP configuration information of the unidirectional link, RLC configuration information of the unidirectional link, MAC configuration information of the unidirectional link, a cell identifier of the unidirectional link, a primary cell identifier of the unidirectional link, and a cell group identifier of the unidirectional link.

[0059] For example, taking the unidirectional link as the uplink (UL) as an example, the uplink DRB configuration information includes at least one of the following: an identifier of an uplink-dedicated DRB, an identifier of an uplink-dedicated HARQ entity, a physical resource set corresponding to the uplink, SDAP configuration information of the uplink, PDCP configuration information of the uplink, RLC configuration information of the uplink, MAC configuration information of the uplink, a cell identifier of the uplink, a primary cell identifier of the uplink, and a cell group identifier of the uplink. In some embodiments, only the uplink-dedicated DRB is established, modified, or released in the uplink DRB configuration information.

[0060] For another example, taking the unidirectional link as the downlink (DL), the downlink DRB configuration information includes at least one of the following: an identifier of a downlink-specific DRB, an identifier of a downlink-specific HARQ entity, a physical resource set corresponding to the downlink, SDAP configuration information of the downlink, PDCP configuration information of the downlink, RLC configuration information of the downlink, MAC configuration information of the downlink, a cell identifier of the downlink, a primary cell identifier of the downlink, and a cell group identifier of the downlink. In some embodiments, only the downlink-specific DRB is established, modified, or released in the downlink DRB configuration information.

[0061] For another example, taking the unidirectional link as the transmission link, the transmission link DRB configuration information (e.g., txdrb-ToAddModList) includes at least one of the following: an identifier of a DRB dedicated to the transmission link (e.g., txdrb-Identity), an identifier of a HARQ entity dedicated to the transmission link, a physical resource set corresponding to the transmission link, SDAP configuration information of the transmission link (e.g., sdap-Config), PDCP configuration information of the transmission link (e.g., pdcp-Config), RLC configuration information of the transmission link, MAC configuration information of the transmission link, a cell identifier of the transmission link, a primary cell identifier of the transmission link, and a cell group identifier of the transmission link. In some embodiments, only the DRB dedicated to the transmission link is established, modified, or released in the transmission link DRB configuration information.

[0062] For another example, taking the unidirectional link as the receiving link, the receiving link DRB configuration information (e.g., rxdrb-ToAddModList) includes at least one of the following: an identifier of a DRB dedicated to the receiving link (e.g., dldrb-Identity), an identifier of a HARQ entity dedicated to the receiving link, a physical resource set corresponding to the receiving link, SDAP configuration information of the receiving link (e.g., dlsdap-Config), PDCP configuration information of the receiving link (e.g., dlpdcp-Config), RLC configuration information of the receiving link, MAC configuration information of the receiving link, a cell identifier of the receiving link, a primary cell identifier of the receiving link, and a cell group identifier of the receiving link. In some embodiments, only the DRB dedicated to the receiving link is established, modified, or released in the receiving link DRB configuration information.

[0063] In some embodiments, the uplink independently configures uplink DRBs so that data transmission has a dedicated uplink primary cell or cell group, and the downlink independently configures downlink DRBs so that data transmission has a dedicated downlink primary cell or cell group. The independent configuration of uplink and downlink DRBs allows the uplink and downlink to have different primary cells or cell groups.

[0064] In some embodiments, the above-mentioned physical resource set includes at least one of the following: a bandwidth part (BWP) identifier, a carrier identifier, and a cell identifier.

[0065] In some embodiments, the BWP is an activated BWP. A cell includes at least one of the following: a base station, a distributed unit (DU), and a transmission receive point (TRP).

[0066] In some embodiments, the physical resources included in the physical resource set include at least one of the following: BWP resources, carrier resources, frequency band resources, and cell resources. Frequency band resources are spectrum bandwidth resources associated with absolute frequencies. For example, the 4.9 GHz frequency band corresponds to a 100 MHz bandwidth between 4800 MHz and 4900 MHz. A physical resource set may include multiple different BWP resources, multiple different carrier resources, multiple different frequency band resources, and multiple different cell resources.

[0067] In some embodiments, a unidirectional link-specific DRB is associated with a unidirectional link-specific HARQ entity. For example, taking the unidirectional link as an uplink as an example, when the uplink DRB configuration information includes an identifier of an uplink-specific DRB (such as an uplink DRB identifier) ​​and an identifier of an uplink-specific HARQ entity (such as an uplink HARQ entity identifier), the uplink-specific DRB and the identifier of the uplink-specific HARQ entity are used to associate the uplink-specific DRB with the uplink-specific HARQ entity. For another example, taking the unidirectional link as a downlink as an example, when the downlink DRB configuration information includes an identifier of a downlink-specific DRB (such as a downlink DRB identifier) ​​and an identifier of a downlink-specific HARQ entity, the downlink-specific DRB and the identifier of the downlink-specific HARQ entity (such as a downlink HARQ entity identifier) ​​are used to associate the downlink-specific DRB with the downlink-specific HARQ entity.

[0068] In some embodiments, a HARQ entity dedicated to a unidirectional link is associated with a set of physical resources corresponding to the unidirectional link. The set of physical resources corresponding to the unidirectional link may be a set of physical resources dedicated to the unidirectional link, or may be the same set of physical resources as other unidirectional links. For example, the uplink physical resources and the downlink physical resources may be completely different, partially the same, or completely the same.

[0069] In some embodiments, there is an association relationship between the unidirectional link-specific DRB, the unidirectional link-specific HARQ entity, and the physical resource set corresponding to the unidirectional link. For example, taking the unidirectional link as an uplink as an example, when the uplink DRB configuration information includes the identifier of the uplink-specific DRB, the identifier of the uplink-specific HARQ entity, and the physical resource set corresponding to the uplink, exemplarily, as shown in FIG3 , a schematic diagram of an association relationship provided by an embodiment of the present disclosure is provided. Referring to FIG3 , the data of the uplink-specific DRB can use the uplink-specific HARQ entity and the physical resources in the physical resource set corresponding to the uplink for uplink data transmission. For another example, taking the unidirectional link as a downlink as an example, when the downlink DRB configuration information includes the identifier of the downlink-specific DRB, the identifier of the downlink-specific HARQ entity, and the physical resource set corresponding to the downlink, exemplarily, as shown in FIG4 , another schematic diagram of an association relationship provided by an embodiment of the present disclosure is provided. Referring to FIG4 , the data of the downlink-specific DRB can use the downlink-specific HARQ entity and the physical resources in the physical resource set corresponding to the downlink for downlink data transmission.

[0070] In some embodiments, when the unidirectional link DRB configuration information includes an identifier of a HARQ entity dedicated to the unidirectional link and a physical resource set corresponding to the unidirectional link, and the physical resource set includes a carrier identifier, it means that the HARQ entity dedicated to the unidirectional link can use the carrier resources corresponding to the carrier identifier for data transmission.

[0071] For example, taking the unidirectional link as the uplink as an example, when the uplink DRB configuration information includes the identifier of the uplink-specific HARQ entity and two uplink carrier identifiers (for example, one uplink carrier identifier at 800MHz and one uplink carrier identifier at 3.5GHz), it means that the uplink-specific HARQ entity uses the two uplink carrier resources corresponding to the two uplink carrier identifiers for uplink data transmission. In this way, the uplink-specific HARQ entity uses low-frequency uplink carrier resources for uplink data transmission to improve the reliability of uplink data transmission, and uses high-frequency uplink carrier resources for uplink data transmission to improve the throughput of uplink data transmission. In addition, uplink transmission data that is erroneously transmitted on high-frequency uplink carrier resources can be retransmitted on low-frequency uplink transmission resources. For example, as shown in Figure 5, another association relationship diagram is provided for an embodiment of the present disclosure. Referring to Figure 5, assuming that the uplink DRB configuration information includes the identifier of the uplink-dedicated HARQ entity as an uplink HARQ entity, and the two uplink carrier identifiers are uplink carrier 1 and uplink carrier 2, then the uplink HARQ entity can perform uplink data transmission on uplink carrier 1 and uplink carrier 2.

[0072] For another example, taking the unidirectional link as the downlink as an example, when the downlink DRB configuration information includes the identifier of the downlink-specific HARQ entity and two downlink carrier identifiers (for example, one downlink carrier identifier at 3.5 GHz and one downlink carrier identifier at 6 GHz), it indicates that the downlink-specific HARQ entity uses two downlink carrier resources corresponding to the two downlink carrier identifiers for downlink data transmission. For example, as shown in FIG6 , another association relationship diagram provided for an embodiment of the present disclosure is shown. Referring to FIG6 , assuming that the downlink DRB configuration information includes the identifier of the downlink-specific HARQ entity as a downlink HARQ entity, and the two downlink carrier identifiers are downlink carrier 1 and downlink carrier 2, the downlink HARQ entity can perform downlink data transmission on downlink carrier 1 and downlink carrier 2.

[0073] In some embodiments, uplink and downlink data transmission are decoupled on the carrier by configuring their own DRBs. In some embodiments, uplink and downlink data can be transmitted using carriers of different frequency bands.

[0074] It should be understood that the transmit power of a terminal is typically lower than that of a base station. The terminal uses low-frequency carrier resources, while the base station uses high-frequency carrier resources to ensure uplink and downlink data transmission performance. By configuring separate dedicated HARQ entities and carrier resources for the uplink and downlink, respectively, uplink and downlink decoupling is achieved, ensuring differentiated uplink and downlink performance.

[0075] In some embodiments, the DRB dedicated to the unidirectional link is associated with a set of physical resources corresponding to the unidirectional link. When the unidirectional link DRB configuration information includes an identifier of the DRB dedicated to the unidirectional link and a set of physical resources corresponding to the unidirectional link, data representing the DRB dedicated to the unidirectional link can be transmitted using the set of physical resources corresponding to the unidirectional link.

[0076] For example, taking the unidirectional link as the uplink as an example, when the uplink DRB configuration information includes the identifier of the uplink-dedicated DRB and the physical resource set corresponding to the uplink, it means that the uplink-dedicated DRB can use the physical resource set corresponding to the uplink for data transmission. For example, as shown in FIG7 , which is another association relationship diagram provided in an embodiment of the present disclosure, referring to FIG7 , the uplink-dedicated DRB corresponds to the physical resource set corresponding to the uplink.

[0077] For another example, taking the unidirectional link as the downlink as an example, when the downlink DRB configuration information includes the identifier of the downlink-specific DRB and the physical resource set corresponding to the downlink, it means that the downlink-specific DRB can use the physical resource set corresponding to the downlink for data transmission. Taking the above-mentioned physical resource set including the carrier identifier as an example, the uplink-specific DRB can use the uplink-specific uplink carrier resources for data transmission, and the downlink-specific DRB can use the downlink-specific downlink carrier resources for data transmission. For example, as shown in Figure 8, another association relationship diagram provided for an embodiment of the present disclosure is shown. Referring to Figure 8, the downlink-specific DRB corresponds to the physical resource set corresponding to the downlink.

[0078] As a possible example, taking the unidirectional link as the downlink, when the downlink DRB configuration information includes the identifier of the downlink-specific DRB and two BWP identifiers, the data of the downlink-specific DRB can be transmitted downlink using the two BWPs corresponding to the two BWP identifiers. The two BWPs can be from different frequency bands. The two BWPs can be activated BWPs, that is, the data of the downlink-specific DRB can be transmitted downlink using the two activated BWPs. In some embodiments, receiving the unidirectional link DRB configuration information from the second network element can be receiving the unidirectional link DRB configuration information from the second network element through a first control message. That is, receiving the first control message sent by the second network element, the first control message including the unidirectional link DRB configuration information. In some embodiments, the first control message includes at least one of the following: a radio resource control (RRC) message, a DRB configuration message. The RRC message is a control message sent by the base station to the UE, and the RRC message includes multiple information elements (IEs) related to the bearer. The first control information can also be called by other names, for example, first control signaling.

[0079] In some embodiments, the first control message may include one unidirectional link DRB configuration information, or may include multiple unidirectional link DRB configuration information. Taking the case where the first control message includes uplink DRB configuration information and downlink DRB configuration information as an example, when the uplink DRB configuration information includes an uplink-specific DRB identifier and an uplink cell identifier (e.g., base station 1), and the downlink DRB configuration information includes a downlink-specific DRB identifier and a downlink cell identifier (e.g., base station 2), it indicates that the uplink of the first network element is connected to base station 1 and transmits uplink data with base station 1 through the uplink-specific DRB, and that the downlink of the first network element is connected to base station 2 and transmits downlink data with base station 2 through the downlink-specific DRB.

[0080] As an example, a data transmission method provided by an embodiment of the present disclosure is applicable to a dual connectivity (DC) scenario. In some embodiments, in a DC scenario, the uplink and downlink may be connected to the same cell or different cells. For example, the first control message may also be used to indicate the uplink master cell corresponding to the uplink-dedicated DRB and the downlink master cell corresponding to the downlink-dedicated DRB. The uplink master cell and the downlink master cell may be the same or different. For example, the first control message includes an uplink-dedicated DRB identifier, an uplink master cell identifier, a downlink-dedicated DRB identifier, and a downlink master cell identifier. For another example, the first control message also includes uplink master cell group (MCG) bearer information and downlink MCG bearer information. The uplink MCG bearer information and the downlink MCG bearer information may be the same or different. In a DC scenario, it is assumed that the UE is connected to base station 1 and base station 2 at the same time, and transmits data with the two base stations at the same time. If the uplink and downlink transmissions of each base station of the dual connection use the same DRB, if the connection between the UE and base station 1 is interrupted in the uplink, the downlink transmission of the UE and base station 1 will be affected. Through the technical solution of the present disclosure, as shown in Figure 9, a schematic diagram of using uplink and downlink DRBs for data transmission in a DC scenario provided by an embodiment of the present disclosure is provided. Referring to Figure 9, the UE and base station 1 use an uplink DRB (the uplink data of the UE can be sent using a low frequency), and the UE and base station 1 use a downlink DRB (the downlink data of the UE can be sent using a high frequency). Through the separation / decoupling of the uplink and downlink DRBs, the data transmission between the UE and the base station 1 can support the use of a low frequency for the uplink to improve the reliability of data transmission, and can also support the use of a high frequency for the downlink to improve the throughput. The bidirectional link between the UE and the base station 2 can also use the uplink DRB and downlink DRB method. In this way, the downlink data transmission of the UE can use the downlink DRB of base station 1 and the downlink DRB of base station 2, and the uplink data transmission of the UE can use the uplink DRB of base station 1 and the uplink DRB of base station 2. Uplink DRB1, downlink DRB1, uplink DRB2, and downlink DRB2 can be DRBs that are independently configured through different unidirectional link DRB configuration information.

[0081] As another example, a data transmission method provided by an embodiment of the present disclosure is also applicable to mobility scenarios. For example, as shown in Figure 10, a schematic diagram of using uplink and downlink DRBs for data transmission in a mobile scenario provided by an embodiment of the present disclosure is shown. Referring to Figure 10, during the movement of the UE, the downlink DRB data transmission between the UE and the source base station can be migrated to the target base station. At the same time, the uplink DRB between the UE and the source base station remains unchanged. For another example, there are two distributed units (DU) under a centralized unit (CU). The uplink uses DU1 to connect to the UE and uses uplink DRB for uplink transmission. The downlink data is migrated to DU2 and downlink DRB is used between DU2 and the UE for downlink transmission. In some embodiments, the downlink DRB can be migrated through a first control message.

[0082] As another example, a data transmission method provided by an embodiment of the present disclosure is also applicable to scenarios that do not distinguish between uplink and downlink, such as D2D, V2X, IAB, and other scenarios. For the above-mentioned scenarios that do not distinguish between uplink and downlink, an embodiment of the present disclosure provides a data transmission method that configures a unidirectional link-specific DRB for a unidirectional link, for example, a transmission link-specific DRB is configured for a transmission link, and a reception link-specific DRB is configured for a reception link, so that the first network element can independently transmit service data in different link directions.

[0083] For example, taking the first network element as the transmitting end and the receiving end as an example, the first control message may include two types of DRB configuration information of the transmitting link used by the first network element as the transmitting end and DRB configuration information of the receiving link used by the first network element as the receiving end.

[0084] S102: Configure a DRB dedicated to the unidirectional link based on the unidirectional link DRB configuration information.

[0085] As an example, configuring a DRB dedicated to a unidirectional link includes at least one of the following:

[0086] Establish a DRB dedicated to unidirectional links;

[0087] Modify the DRB dedicated to unidirectional links;

[0088] Release the DRB dedicated to the unidirectional link. Here, the release of the DRB can also be represented by other names, such as deletion, removal, etc., which is not limited in the embodiment of the present disclosure.

[0089] It should be noted that in the related prior art, the uplink and downlink, or the bidirectional links of the transmitting link and the receiving link use the same DRB configuration, without distinguishing between the uplink and downlink or the transmitting end and the receiving end. The DRB configuration is highly coupled, and the uplink and downlink or the transmitting end and the receiving end cannot independently configure the DRB, for example, they cannot independently establish, modify or release the DRB. For example, in the RRC protocol of 5G TS38.331, the information element Radio Bearer Configuration (IE RadioBearerConfig) contains information on DRB establishment, modification and release. As follows:

[0090] As can be seen from the above content, the related art uses the same DRB configuration for the uplink and downlink bidirectional links, without distinguishing between uplink and downlink. The technical solution of the embodiment of the present disclosure is to configure a unidirectional link-specific DRB for each unidirectional link. For example, an uplink-specific DRB is configured for the uplink for uplink data transmission, and a downlink-specific DRB is configured for the downlink for downlink data transmission. Taking IE RadioBearerConfig as an example, the embodiment of the present disclosure configures dedicated establishment, modification, and deletion messages for the uplink-specific DRB and the downlink-specific DRB in IE RadioBearerConfig respectively. Exemplarily, the relevant content is as follows:

[0091] In some embodiments, only uplink-dedicated DRBs are established, modified, or released in the uplink DRB configuration information.

[0092] In some embodiments, only downlink-dedicated DRBs are established, modified, or released in the downlink DRB configuration information.

[0093] As an example, the control signaling IE for adding and modifying uplink DRB is uldrb-ToAddModList. As an example, the control signaling IE for releasing uplink DRB is uldrb-ToReleaseList.

[0094] As an example, the control signaling IE for adding and modifying downlink DRB is dldrb-ToAddModList. As an example, the control signaling IE for releasing downlink DRB is dldrb-ToReleaseList).

[0095] As another example, the relevant signaling for configuring uplink-specific DRBs and downlink-specific DRBs may also be: ULRadioBearerConfig, DLRadioBearerConfig. All uplink bearer information is configured in ULRadioBearerConfig, and all downlink bearer information is configured in DLRadioBearerConfig.

[0096] As another example, the relevant signaling for configuring uplink-specific DRBs and downlink-specific DRBs may also be: ULDataRadioBearerConfig, DLDataRadioBearerConfig. All uplink data bearer information is configured in ULDataRadioBearerConfig, and all downlink data bearer information is configured in DLDataRadioBearerConfig.

[0097] As a possible example, the control signaling IE of the uplink DRB configuration includes at least one of the following: an uplink-dedicated DRB identifier (e.g., uldrb-Identity), an uplink-dedicated HARQ entity identifier (e.g., UL HARQ entity ID), an uplink corresponding physical resource set, uplink SDAP configuration information (e.g., ulsdap-Config), uplink PDCP configuration information (e.g., ulpdcp-Config), uplink RLC configuration information, uplink MAC configuration information, uplink cell identifier, uplink primary cell identifier, and uplink cell group identifier.

[0098] As a possible example, the control signaling IE of the downlink DRB configuration includes at least one of the following: an identifier of a downlink-specific DRB (e.g., dldrb-Identity), an identifier of a downlink-specific HARQ entity (e.g., DL HARQ entity ID), a physical resource set corresponding to the downlink, SDAP configuration information of the downlink (e.g., dlsdap-Config), PDCP configuration information of the downlink (e.g., dlpdcp-Config), RLC configuration information of the downlink, MAC configuration information of the downlink, cell identifier of the downlink, primary cell identifier of the downlink, and cell group identifier of the downlink.

[0099] As an example, taking the configuration of a DRB dedicated to a transmission link and a DRB dedicated to a reception link as an example, the configuration of a DRB dedicated to a unidirectional link based on the unidirectional link DRB configuration information is illustrated. For example, the relevant signaling content is as follows:

[0100] In the above content, txdrb is the DRB dedicated to the transmit link, and rxdrb is the DRB dedicated to the receive link.

[0101] As another example, the relevant signaling for configuring the DRB dedicated to the transmit link and the DRB dedicated to the receive link may also be: TXRadioBearerConfig, RXRadioBearerConfig. All transmit link bearer information is configured in TXRadioBearerConfig, and all receive link bearer information is configured in RXRadioBearerConfig.

[0102] As another example, the relevant signaling for configuring the DRB dedicated to the transmit link and the DRB dedicated to the receive link can also be: TXDataRadioBearerConfig, RXDataRadioBearerConfig. All transmit link data bearer information is configured in TXDataRadioBearerConfig, and all receive link data bearer information is configured in RXDataRadioBearerConfig.

[0103] As a possible example, the control signaling IE of the transmission link DRB configuration includes at least one of the following: an identifier of the DRB dedicated to the transmission link (for example, txdrb-Identity), an identifier of the HARQ entity dedicated to the transmission link (such as TX HARQ entity ID), a physical resource set corresponding to the transmission link, SDAP configuration information of the transmission link (for example, txsdap-Config), PDCP configuration information of the transmission link (for example, txpdcp-Config), RLC configuration information of the transmission link, MAC configuration information of the transmission link, cell identifier of the transmission link, primary cell identifier of the transmission link, and cell group identifier of the transmission link.

[0104] As a possible example, the control signaling IE of the receiving link DRB configuration includes at least one of the following: an identifier of a DRB dedicated to the receiving link (e.g., rxdrb-Identity), an identifier of a HARQ entity dedicated to the receiving link (e.g., RX HARQ entity ID), a physical resource set corresponding to the receiving link, SDAP configuration information of the receiving link (e.g., rxsdap-Config), PDCP configuration information of the receiving link (e.g., rxpdcp-Config), RLC configuration information of the receiving link, MAC configuration information of the receiving link, cell identifier of the receiving link, primary cell identifier of the receiving link, and cell group identifier of the receiving link.

[0105] In some embodiments, after the first network element configures a DRB dedicated to the unidirectional link based on the unidirectional link DRB configuration information, the first network element can perform data transmission based on the DRB dedicated to the unidirectional link, for example, performing uplink data transmission based on the DRB dedicated to the uplink, performing downlink data transmission based on the DRB dedicated to the downlink, etc.

[0106] Based on the embodiment shown in Figure 2, the first network element configures a DRB dedicated to the unidirectional link based on the unidirectional link DRB configuration information from the second network element, so as to facilitate data transmission based on the DRB dedicated to the unidirectional link. In this way, each unidirectional link is configured with its own corresponding dedicated DRB for data transmission, so that the DRB configuration of the uplink is decoupled from the DRB configuration of the downlink, or the DRB configuration of the transmitting link is decoupled from the DRB configuration of the receiving link, thereby reducing the complexity of data transmission.

[0107] In some embodiments, as shown in FIG11 , an embodiment of the present disclosure further provides a data transmission method, which is applied to a second network element. The second network element may be the base station 21 shown in FIG1 . The method may include the following steps:

[0108] S201. Send unidirectional link DRB configuration information to a first network element.

[0109] In some embodiments, to reduce the complexity of data transmission, after configuring the unidirectional link DRB configuration information, the second network element may send the unidirectional link DRB configuration information to the first network element. The unidirectional link DRB configuration information is used to configure a DRB dedicated to the unidirectional link.

[0110] For the description of the unidirectional link DRB configuration information, reference may be made to the relevant description in the embodiment shown in FIG2 above, which will not be repeated here.

[0111] In some embodiments, sending the unidirectional link DRB configuration information to the first network element may be the second network element sending the unidirectional link DRB configuration information to the first network element via a first control message. That is, sending the unidirectional link DRB configuration information to the first network element may be the second network element sending a first control message to the first network element, the first control message including the unidirectional link DRB configuration information. The first control message includes at least one of the following: an RRC message, a DRB configuration message.

[0112] In some embodiments, after configuring the unidirectional link DRB configuration information, the second network element may configure a DRB dedicated to the unidirectional link based on the unidirectional link DRB configuration information. In this way, the second network element and the first network element have consistent configuration (recognition) of the DRB dedicated to the unidirectional link, thereby helping to reduce the complexity of data transmission and improve data transmission performance. For the description of configuring a DRB dedicated to the unidirectional link based on the unidirectional link DRB configuration information, please refer to the relevant description in the embodiment shown in Figure 2 above, and will not be repeated here.

[0113] The above mainly introduces the solution provided by the present disclosure from the perspective of the interaction between various network elements. It can be understood that, in order to implement the above functions, each network element, such as the first network element or the second network element, includes a hardware structure and / or software module corresponding to the execution of each function. It should be easy for those skilled in the art to realize that, in combination with the algorithm steps of each example described in the embodiments disclosed herein, the present disclosure can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in a hardware or computer software-driven hardware manner depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the present disclosure.

[0114] FIG12 is a schematic diagram showing the composition of a communication device provided by an embodiment of the present disclosure. As shown in FIG12 , the communication device 30 includes a receiving unit 301 and a processing unit 302 .

[0115] The communication device 30 may be the first network element or a chip in the first network element. When the communication device 30 is used to implement the functions of the first network element in the above embodiment, each unit may be used to implement the following functions.

[0116] The receiving unit 301 is configured to receive unidirectional link data radio bearer (DRB) configuration information from a second network element, where the unidirectional link DRB configuration information is used to configure a DRB dedicated to the unidirectional link;

[0117] The processing unit 302 is configured to configure a DRB dedicated to the unidirectional link based on the unidirectional link DRB configuration information.

[0118] In some embodiments, the unidirectional link includes any one of the following: uplink, downlink, transmit link, receive link.

[0119] In some embodiments, the unidirectional link-dedicated DRB includes any one of the following: an uplink-dedicated DRB, a downlink-dedicated DRB, a transmission link-dedicated DRB, and a reception link-dedicated DRB.

[0120] In some embodiments, the unidirectional link DRB configuration information only includes information related to the unidirectional link.

[0121] In some embodiments, a unidirectional link-specific DRB is associated with a unidirectional link-specific hybrid automatic repeat request HARQ entity.

[0122] In some embodiments, a HARQ entity dedicated to a unidirectional link is associated with a set of physical resources corresponding to the unidirectional link.

[0123] In some embodiments, the unidirectional link DRB configuration information includes at least one of the following: an identifier of a DRB dedicated to the unidirectional link, an identifier of a HARQ entity dedicated to the unidirectional link, a set of physical resources corresponding to the unidirectional link, SDAP configuration information of the unidirectional link, PDCP configuration information of the unidirectional link, RLC configuration information of the unidirectional link, MAC configuration information of the unidirectional link, a cell identifier of the unidirectional link, a primary cell identifier of the unidirectional link, and a cell group identifier of the unidirectional link.

[0124] In some embodiments, the physical resource set includes at least one of the following: a partial bandwidth BWP identifier, a carrier identifier, and a cell identifier.

[0125] In some embodiments, the BWP is an activated BWP.

[0126] In some embodiments, the processing unit 302 may be configured to perform at least one of the following: establishing a DRB dedicated to a unidirectional link; modifying a DRB dedicated to a unidirectional link; and releasing a DRB dedicated to a unidirectional link.

[0127] In some embodiments, the receiving unit 301 can be used to receive unidirectional link DRB configuration information from the second network element through a first control message, where the first control message includes at least one of the following: a radio resource control RRC message, and a DRB configuration message.

[0128] FIG13 is a schematic diagram showing the composition of another communication device provided by an embodiment of the present disclosure. As shown in FIG13 , the communication device 40 includes a sending unit 401. In some embodiments, the communication device 40 further includes a processing unit 402.

[0129] The communication device 40 may be the second network element or a chip in the second network element. When the communication device 40 is used to implement the functions of the second network element in the above embodiment, each unit may be used to implement the following functions.

[0130] The sending unit 401 is configured to send unidirectional link DRB configuration information to the first network element, where the unidirectional link DRB configuration information is used to configure a DRB dedicated to the unidirectional link.

[0131] In some embodiments, the processing unit 402 is configured to configure a DRB dedicated to the unidirectional link based on the unidirectional link DRB configuration information.

[0132] In some embodiments, the unidirectional link includes any one of the following: uplink, downlink, transmit link, receive link.

[0133] In some embodiments, the unidirectional link-dedicated DRB includes any one of the following: an uplink-dedicated DRB, a downlink-dedicated DRB, a transmission link-dedicated DRB, and a reception link-dedicated DRB.

[0134] In some embodiments, the unidirectional link DRB configuration information only includes information related to the unidirectional link.

[0135] In some embodiments, a unidirectional link-specific DRB is associated with a unidirectional link-specific hybrid automatic repeat request HARQ entity.

[0136] In some embodiments, a HARQ entity dedicated to a unidirectional link is associated with a set of physical resources corresponding to the unidirectional link.

[0137] In some embodiments, the unidirectional link DRB configuration information includes at least one of the following: an identifier of a DRB dedicated to the unidirectional link, an identifier of a HARQ entity dedicated to the unidirectional link, a set of physical resources corresponding to the unidirectional link, SDAP configuration information of the unidirectional link, PDCP configuration information of the unidirectional link, RLC configuration information of the unidirectional link, MAC configuration information of the unidirectional link, a cell identifier of the unidirectional link, a primary cell identifier of the unidirectional link, and a cell group identifier of the unidirectional link.

[0138] In some embodiments, the physical resource set includes at least one of the following: a partial bandwidth BWP identifier, a carrier identifier, and a cell identifier.

[0139] In some embodiments, the BWP is an activated BWP.

[0140] In some embodiments, the processing unit 402 may be configured to perform at least one of the following: establishing a DRB dedicated to a unidirectional link; modifying a DRB dedicated to a unidirectional link; and releasing a DRB dedicated to a unidirectional link.

[0141] In some embodiments, the sending unit 401 may be configured to send unidirectional link DRB configuration information via a first control message, where the first control message includes at least one of the following: an RRC message, a DRB configuration message.

[0142] It should be noted that the units in Figures 12 and 13 may also be referred to as modules. For example, the sending unit may be referred to as a sending module. In addition, in the embodiments shown in Figures 12 and 13, the names of the units may not be those shown in the figures. For example, the sending unit may be referred to as a communication unit, and the receiving unit may be referred to as a communication unit.

[0143] If the various units in Figures 12 and 13 are implemented in the form of software function modules and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiment of the present disclosure is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor (processor) to execute all or part of the steps of the various embodiments of the present disclosure. The storage medium for storing computer software products includes various media that can store program codes, such as a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0144] When the communication device 30 or 40 implements the functions of the integrated modules in hardware, the present disclosure provides a schematic structural diagram of the communication device. As shown in Figure 14, the communication device 50 includes: a processor 502, a communication interface 503, and a bus 504. In some embodiments, the communication device 50 may also include a memory 501.

[0145] The processor 502 can implement or execute the various exemplary logic blocks, modules, and circuits described in conjunction with the present disclosure. The processor 502 can be a central processing unit, a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field-programmable gate array or other programmable logic device, a transistor logic device, a hardware component, or any combination thereof, and can implement or execute the various exemplary logic blocks, modules, and circuits described in conjunction with the present disclosure. The processor 502 can also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, etc.

[0146] The communication interface 503 is used to connect to other devices via a communication network, such as Ethernet, wireless access network, wireless local area network (WLAN), etc.

[0147] The memory 501 may be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM) or other type of dynamic storage device that can store information and instructions, or an electrically erasable programmable read-only memory (EEPROM), a disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto.

[0148] As a possible implementation, the memory 501 can exist independently of the processor 502. The memory 501 can be connected to the processor 502 via a bus 504 to store instructions or program codes. When the processor 502 calls and executes the instructions or program codes stored in the memory 501, the data transmission method provided in the embodiment of the present disclosure can be implemented.

[0149] In another possible implementation, the memory 501 may also be integrated with the processor 502 .

[0150] Bus 504 can be an Extended Industry Standard Architecture (EISA) bus, etc. Bus 504 can be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, FIG14 shows only one thick line, but this does not mean that there is only one bus or only one type of bus.

[0151] Through the description of the above implementation methods, technical personnel in the relevant field can clearly understand that for the convenience and conciseness of the description, only the division of the above-mentioned functional modules is used as an example. In actual applications, the above-mentioned functions can be assigned to different functional modules as needed, that is, the internal structure of the base station or terminal is divided into different functional modules to complete all or part of the functions described above.

[0152] The embodiments of the present disclosure also provide a computer-readable storage medium (e.g., a non-transitory computer-readable storage medium). All or part of the processes in the above-mentioned method embodiments can be completed by computer instructions to the relevant hardware. The program can be stored in the above-mentioned computer-readable storage medium. When the program is executed, it can include the processes of the above-mentioned method embodiments. The computer-readable storage medium can be an internal storage unit or memory of any of the above-mentioned embodiments. The above-mentioned computer-readable storage medium can also be an external storage device of the above-mentioned first network element or second network element, such as a plug-in hard disk, a smart media card (SMC), a secure digital (SD) card, a flash card, etc. equipped on the above-mentioned first network element or second network element. Furthermore, the above-mentioned computer-readable storage medium can also include both the internal storage unit of the above-mentioned first network element or second network element and an external storage device. The above-mentioned computer-readable storage medium is used to store the above-mentioned computer program and other programs and data required by the above-mentioned first network element or second network element. The above-mentioned computer-readable storage medium can also be used to temporarily store data that has been output or is to be output.

[0153] The embodiments of the present disclosure further provide a computer program product, which includes a computer program. When the computer program product runs on a computer, the computer is enabled to execute any one of the data transmission methods provided in the above embodiments.

[0154] Although the present disclosure is described herein in conjunction with various embodiments, in the process of implementing the disclosure for which protection is sought, those skilled in the art may understand and implement other variations of the disclosed embodiments by reviewing the drawings, the disclosure, and the appended claims. In the claims, the word "comprising" does not exclude other components or steps, and "one" or "an" does not exclude multiple components. A single processor or other unit may implement several functions listed in the claims. Certain measures are recorded in different dependent claims, but this does not mean that these measures cannot be combined to produce good results.

[0155] Although the present disclosure has been described in conjunction with example features and embodiments thereof, it will be apparent that various modifications and combinations may be made thereto without departing from the spirit and scope of the present disclosure. Accordingly, this specification and the drawings are merely illustrative of the present disclosure as defined by the appended claims and are deemed to cover any and all modifications, variations, combinations or equivalents within the scope of the present disclosure. It will be apparent that those skilled in the art may make various modifications and variations to the present disclosure without departing from the spirit and scope of the present disclosure. Thus, the present disclosure is intended to encompass such modifications and variations as would fall within the scope of the claims of the present disclosure and their equivalents.

[0156] The above are only specific embodiments of the present disclosure, but the scope of protection of the present disclosure is not limited thereto. Any changes or replacements within the technical scope disclosed in the present disclosure should be included in the scope of protection of the present disclosure. Therefore, the scope of protection of the present disclosure should be based on the scope of protection of the claims.

Claims

1. A data transmission method, applied to a first network element, the method comprising: Receiving unidirectional link data radio bearer (DRB) configuration information from a second network element, the unidirectional link DRB configuration information being used to configure a DRB dedicated to the unidirectional link; Configuring the DRB dedicated to the unidirectional link based on the unidirectional link DRB configuration information.

2. The method according to claim 1, wherein, The unidirectional link includes any one of the following: uplink, downlink, transmit link, receive link.

3. The method according to claim 1 or 2, wherein The DRB dedicated to the unidirectional link includes any one of the following: uplink-dedicated DRB, downlink-dedicated DRB, transmit-link-dedicated DRB, receive-link-dedicated DRB.

4. The method according to claim 1, wherein The unidirectional link DRB configuration information only contains information related to the unidirectional link.

5. The method according to claim 1, wherein, The DRB dedicated to the unidirectional link is associated with the unidirectional link dedicated hybrid automatic repeat request (HARQ) entity.

6. The method according to claim 5, wherein, The unidirectional link dedicated HARQ entity is associated with the physical resource set corresponding to the unidirectional link.

7. The method according to claim 1, wherein The unidirectional link DRB configuration information includes at least one of the following: the identifier of the DRB dedicated to the unidirectional link, the identifier of the HARQ entity dedicated to the unidirectional link, the physical resource set corresponding to the unidirectional link, the service data adaptation protocol (SDAP) configuration information of the unidirectional link, the packet data convergence protocol (PDCP) configuration information of the unidirectional link, the radio link control (RLC) configuration information of the unidirectional link, the media access control (MAC) configuration information of the unidirectional link, the cell identifier of the unidirectional link, the primary cell identifier of the unidirectional link, the cell group identifier of the unidirectional link.

8. The method according to claim 6 or 7, wherein The physical resource set includes at least one of the following: partial bandwidth (BWP) identifier, carrier identifier, cell identifier.

9. The method according to claim 8, wherein, The BWP is an active BWP.

10. The method according to claim 1, wherein, The configuring the DRB dedicated to the unidirectional link includes at least one of the following: Establishing the DRB dedicated to the unidirectional link; Modifying the DRB dedicated to the unidirectional link; Releasing the DRB dedicated to the unidirectional link.

11. The method according to claim 1, wherein The receiving unidirectional link data radio bearer DRB configuration information from the second network element includes: Receiving the unidirectional link DRB configuration information from the second network element through a first control message, the first control message including at least one of the following: radio resource control (RRC) message, DRB configuration message.

12. A data transmission method, applied to a second network element, the method comprising: Sending unidirectional link data radio bearer DRB configuration information to a first network element, the unidirectional link DRB configuration information being used to configure a DRB dedicated to the unidirectional link.

13. The method according to claim 12, further comprising: Configuring the DRB dedicated to the unidirectional link based on the unidirectional link DRB configuration information.

14. The method according to claim 12 or 13, wherein, The unidirectional link includes any one of the following: uplink, downlink, transmit link, receive link.

15. The method according to claim 12 or 13, wherein The DRB dedicated to the unidirectional link includes any one of the following: uplink-dedicated DRB, downlink-dedicated DRB, transmit-link-dedicated DRB, receive-link-dedicated DRB.

16. The method according to claim 12, wherein, The unidirectional link DRB configuration information only contains information related to the unidirectional link.

17. The method according to claim 12, wherein, The DRB dedicated to the unidirectional link is associated with the hybrid automatic repeat request (HARQ) entity dedicated to the unidirectional link.

18. The method according to claim 17, wherein, The HARQ entity dedicated to the unidirectional link is associated with the set of physical resources corresponding to the unidirectional link.

19. The method according to claim 12, wherein, The unidirectional link DRB configuration information includes at least one of the following: the identifier of the DRB dedicated to the unidirectional link, the identifier of the HARQ entity dedicated to the unidirectional link, the set of physical resources corresponding to the unidirectional link, the service data adaptation protocol (SDAP) configuration information of the unidirectional link, the packet data convergence protocol (PDCP) configuration information of the unidirectional link, the radio link control (RLC) configuration information of the unidirectional link, the media access control (MAC) configuration information of the unidirectional link, the cell identifier of the unidirectional link, the primary cell identifier of the unidirectional link, the cell group identifier of the unidirectional link.

20. The method according to claim 18 or 19, wherein, The set of physical resources includes at least one of the following: partial bandwidth (BWP) identifier, carrier identifier, cell identifier.

21. The method according to claim 20, wherein, The BWP is an active BWP.

22. The method according to claim 13, wherein, Configuring the DRB dedicated to the unidirectional link includes at least one of the following: Establishing the DRB dedicated to the unidirectional link; Modifying the DRB dedicated to the unidirectional link; Releasing the DRB dedicated to the unidirectional link.

23. The method according to claim 12, wherein Sending the unidirectional link DRB configuration information to the first network element includes: Sending the unidirectional link DRB configuration information to the first network element through a first control message, where the first control message includes at least one of the following: radio resource control (RRC) message, DRB configuration message.

24. A communication device, comprising: A memory and a processor; The memory is coupled to the processor; The memory is used to store instructions executable by the processor; When the processor executes the instructions, it executes the method according to any one of claims 1-11, or the method according to any one of claims 12-23.

25. A computer-readable storage medium, wherein, Computer instructions are stored on the computer-readable storage medium. When the computer instructions run on a computer, the computer is caused to execute the method according to any one of claims 1-11, or the method according to any one of claims 12-23.

Images