CN116097727A

CN116097727A - Data transmission method, device and readable storage medium

Info

Publication number: CN116097727A
Application number: CN202280003672.0A
Authority: CN
Inventors: 李艳华; 吴昱民
Original assignee: Beijing Xiaomi Mobile Software Co Ltd
Current assignee: Beijing Xiaomi Mobile Software Co Ltd
Priority date: 2022-09-27
Filing date: 2022-09-27
Publication date: 2023-05-09
Also published as: WO2024065207A1

Abstract

The present disclosure provides a data transmission method, apparatus, and readable storage medium. The method comprises the following steps: when the service type is the first service, the PDCP entity transmits a data packet to at least one type of Radio Link Control (RLC) entity. In the embodiment of the disclosure, in a scene of transmitting XR service data, the split transmission of the XR service data is realized through the PDCP layer, so that the efficiency of transmitting the data is improved.

Description

Data transmission method, device and readable storage medium

Technical Field

The present disclosure relates to the field of wireless communications technologies, and in particular, to a data transmission method, apparatus, and readable storage medium.

Background

In a fifth Generation (5 th-Generation, 5G) wireless communication system, support for eXtended Reality (XR) service types is required. In XR traffic, quality of service (Quality of Service, qoS) streaming may be employed for packet transmission. During transmission, a Non-access Stratum (NAS) may not split packets, and different data may be contained in the same QoS flow. Therefore, the problem of data offloading in this XR service scenario needs to be solved.

Disclosure of Invention

The present disclosure provides a data transmission method, apparatus, and readable storage medium.

In a first aspect, the present disclosure provides a data transmission method, the method including:

when the service type is the first service, the PDCP entity transmits a data packet to at least one type of Radio Link Control (RLC) entity.

In the embodiment of the disclosure, in a scene of transmitting XR service data, the split transmission of the XR service data is realized through the PDCP layer, so that the efficiency of transmitting the data is improved.

In some possible embodiments, the PDCP entity sends data packets to at least one type of radio link control RLC entity, including:

and if the data packet is a PDCP data protocol data unit PDU, the PDCP entity sends the data packet to at least one type of RLC entity according to the attribute information of the data packet of the first service.

In some possible embodiments, the PDCP entity sends the data packet of the first service to at least one type of RLC entity according to attribute information of the data packet, including:

the PDCP entity determines attribute information of the data packet according to a first field in the data packet;

the PDCP entity transmits the data packet to the RLC entity associated with attribute information of the data packet.

In some possible embodiments, the first field is a service data unit SDU type field.

and if the PDCP packet copying function of the Radio Bearer (RB) of the first service is activated, the PDCP entity copies and sends the data packet to the RLC entity corresponding to the attribute information of the data packet.

In some possible implementations, the PDCP packet duplication function of the radio bearer RB of the first service is activated, including:

and the PDCP packet copying function corresponding to any attribute information in the first service is activated.

In some possible embodiments, the attribute information of the data packet includes one of the following:

the type of the data packet;

priority of the data packet;

processing level of the data packet.

In a second aspect, the present disclosure provides a communication device comprising: PDCP entity.

The PDCP entity is configured to send data packets to at least one type of radio link control RLC entity when the service type is a first service.

In a third aspect, the present disclosure provides a communication device comprising a processor and a memory; the memory is used for storing a computer program; the processor is configured to execute the computer program to implement the first aspect or any one of the possible designs of the first aspect.

In a fourth aspect, the present disclosure provides a computer readable storage medium having stored therein instructions (or computer programs, programs) which when invoked for execution on a computer, cause the computer to perform any one of the possible designs of the first aspect or the first aspect.

Drawings

The accompanying drawings, which are included to provide a further understanding of embodiments of the disclosure and are incorporated in and constitute a part of this application, illustrate embodiments of the disclosure and together with the description serve to explain the embodiments of the disclosure and not to limit the embodiments of the disclosure unduly. In the drawings:

the accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the disclosure and together with the description, serve to explain the principles of the embodiments of the disclosure.

Fig. 1 is a schematic diagram of a communication system architecture according to an embodiment of the disclosure;

fig. 2 is a schematic diagram of a protocol layer structure provided in an embodiment of the disclosure;

FIG. 3 is a flow chart illustrating a method of data transmission according to an exemplary embodiment;

FIG. 4 is a flow chart illustrating another data transmission method according to an exemplary embodiment;

FIG. 5 is a flow chart illustrating another data transmission method according to an exemplary embodiment;

fig. 6 is a block diagram of a data transmission apparatus according to an exemplary embodiment;

fig. 7 is a block diagram of a user device shown in accordance with an exemplary embodiment;

fig. 8 is a block diagram of a network device according to an exemplary embodiment.

Detailed Description

Embodiments of the present disclosure will now be further described with reference to the drawings and detailed description.

Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the embodiments of the present disclosure. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present disclosure as detailed in the accompanying claims.

The terminology used in the embodiments of the disclosure is for the purpose of describing particular embodiments only and is not intended to be limiting of the embodiments of the disclosure. As used in this disclosure of embodiments and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any or all possible combinations of one or more of the associated listed items.

It should be understood that although the terms first, second, third, etc. may be used in embodiments of the present disclosure to describe various information, these information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, the first information may also be referred to as second information, and similarly, the second information may also be referred to as first information, without departing from the scope of embodiments of the present disclosure. The words "if" and "if" as used herein may be interpreted as "at … …" or "at … …" or "in response to a determination", depending on the context.

Embodiments of the present disclosure are described in detail below, examples of which are illustrated in the accompanying drawings, wherein like or similar reference numerals refer to the like or similar elements throughout. The embodiments described below by referring to the drawings are exemplary and intended for the purpose of explaining the present disclosure and are not to be construed as limiting the present disclosure.

Fig. 1 is a schematic diagram of a wireless communication system 100 to which embodiments of the present application are applicable. The user device 101 may access a wireless network to obtain services of an external network (e.g., the internet) through the wireless network or communicate with other devices through the wireless network, such as may communicate with other user devices. As shown in fig. 1, the wireless network includes: a radio access Network (Radio Access Network, RAN) device 102, or Network device 102, and a Core Network (CN) device 103, wherein the RAN device 102 is for accessing the user device 101 to a wireless Network, and the CN device 103 is for managing the user device 101 and providing a gateway for communication with an external Network. It should be understood that the number of each device in the communication system shown in fig. 1 is merely illustrative, and the embodiments of the present application are not limited thereto, and more user devices, more RAN devices, and other devices may be further included in the communication system in practical applications.

The wireless communication system 100 includes a user equipment 101, a RAN equipment 102 and a CN equipment 103.

Where the network architecture shown in fig. 1 is applicable to a 5G communication system, the CN device 103 may include: access and mobility management function (Access and Mobility Management Function, AMF) entities, session management function (Session Management Function, SMF), user plane function (User Plane Function, UPF) entities, policy and charging function (Policy and charging function, PCF) devices, network opening function (Network Exposure Function, NEF) devices, application function (Application Function, AF) devices, and the like.

The communication between the RAN device 102 and the user device 101 follows a certain protocol layer structure. Fig. 2 is a schematic diagram of a protocol layer structure according to an embodiment of the disclosure. Referring to fig. 2, the control plane protocol Layer structure may include functions of protocol layers such as a radio resource control (Radio Resource Control, RRC) Layer, a packet data convergence protocol (Packet Data Convergence Protocol, PDCP) Layer, a radio link control (Radio Link Control, RLC) Layer, a medium access control (Media Access Control, MAC) Layer, and a Physical Layer (PHY). The user plane protocol layer structure may include the functions of protocol layers such as PDCP layer, RLC layer, MAC layer, and physical layer.

The RAN and the UPF are generally referred to as user layer network function entities, and Data traffic of the user equipment may be transmitted through a Packet Data Unit (PDU) Session (Session) established between the user equipment and the application layer equipment, where the transmission may pass through the two network function devices, namely, the RAN and the UPF; the other parts are called control layer network functions and entities, and are mainly responsible for authentication and authentication, registration management, session management, mobility management, policy control and other functions, so that reliable and stable transmission of user layer traffic is realized.

The embodiment of the disclosure provides a data transmission method. The method can be applied to the following scenes: the data transmitting terminal device transmits the data packet of the first service to the data receiving terminal device, and the PDCP layer of the data receiving terminal device receives the data packet transmitted by the data transmitting terminal device through the high layer.

Referring to fig. 3, fig. 3 is a data transmission method according to an exemplary embodiment, and as shown in fig. 3, the method includes step S301, specifically:

in step S301, when the service type is the first service, the PDCP entity sends a data packet to at least one type of radio link control RLC entity.

Wherein a radio bearer RB of the first service is associated with the PDCP entity. One or a class of RLC entities includes at least one RLC entity.

In the embodiment of the disclosure, the PDCP layer and the RLC entity are configured in the same message receiving end device or message transmitting end device. For example, the message transmitting end device is a RAN device 102 or a network device 102, and the message receiving end device is a user device 101.

The PDCP layer and RLC entity may be configured in the ue 101 to receive data sent by the network device 102, where the method of the embodiments of the present disclosure may be performed by the ue 101. While the PDCP layer and the RLC entity are configured in the network device 102, the interaction between the PDCP layer and the RLC entity may still be described with reference to the embodiments of the present disclosure, where the method of the embodiments of the present disclosure may be performed by the network device 102.

In some possible embodiments, the PDCP layer may be a packet that receives the first service from a higher layer and shunts the received packet to transmit to at least one type of RLC entity.

In some possible implementations, the first service is an XR service, which includes a real and virtual combined environment and human-machine interaction service generated by computer technology and wearable devices. XR includes augmented Reality (Augmented Reality, AR), virtual Reality (VR), cloud gaming (Cloud gaming), and the like.

In some possible embodiments, one XR service RB corresponds to one PDCP entity. The one PDCP entity is associated with at least one type of RLC entity. It is understood that the PDCP layer may be preconfigured with the association relationship, which will be described in detail in the following embodiments.

In some possible embodiments, at least one type of RLC entity may be one or two types of RLC entities. The class of RLC entities is related to the type of service and the configuration, e.g., data of one type of service may correspond to RLC entities configured with one or two classes. The configuration can be seen in the examples described below. Wherein each category of RLC entity comprises at least one RLC entity. The RLC includes three transmission modes: transparent Transmission Mode (TM), unacknowledged transmission mode (UM), acknowledged transmission mode (AM). Accordingly, the RLC entity included in each category of RLC entities may be a TM RLC entity, a UM RLC entity, or an AM RLC entity.

In an example, in a non-duplicate (duplicate) configured scenario, one category of RLC entity contains one RLC entity. In UM bidirectional (uplink and downlink) transmission mode, the one RLC entity refers to one UM RLC entity. In the UM unidirectional (uplink or downlink only) transmission mode, the one RLC entity refers to one uplink UM RLC entity and one downlink UM RLC entity (one for each transmission direction). In the AM mode, the one RLC entity refers to one AM RLC entity.

In another example, in a configuration duplication scenario, one category of RLC entity may include multiple RLC entities. For example, in combination with the foregoing example of unconfigured duplication, in the case of configured duplication, UM is transmitted bi-directionally corresponding to two UM RLC entities, UM is transmitted uni-directionally corresponding to four UM RLC entities, and AM is transmitted bi-directionally corresponding to two AM RLC entities.

In some possible embodiments, when there is only one type of PDCP associated RLC entity (RLC entity), the PDCP layer transmits a data packet to the RLC entity of that type.

In some possible embodiments, when the RLC entity associated with the PDCP has more than one class, the PDCP layer shunts data to the RLC entity of the more than one class, which may be performed according to the importance of the packet. For example, the data packets are classified according to their importance, and then the PDCP layer sends the data packet stream to RLC entities of different categories.

In some possible embodiments, when the RLC entity associated with the PDCP has more than one category, the PDCP layer shunts data to the RLC entity of the more than one category, which may be performed according to attribute information of the data packet. For example, the data packets are classified according to their attribute information, and then the PDCP layer transmits the data packet streams to RLC entities of different categories.

In one example, the attribute information of the data packet may be a type, priority level, or processing level of the data packet.

As an example: the packets may be categorized by flow or sub-flow, such as a first sub-flow packet (sub-flow 1) and a second sub-flow packet (sub-flow 2).

In an example, if the attribute information of the data packet includes a type of the data packet, the PDCP layer may shunt the data packet according to the type of the data packet and deliver the data packet to at least one RLC entity or at least one type of RLC entity.

In an example, if the diverted target class RLC entity contains only one RLC entity, e.g., one UM RLC entity for UM bi-directional transmission, one UM RLC entity for UM uni-directional transmission for each transmission direction (uplink and downlink), or one AM RLC entity for AM mode, PDCP submits a packet to the one RLC entity.

In some possible embodiments, the types of data packets include, for example: intra-coded frames (I frames) and forward Predictive-coded frames (P frames), i.e., I frames and P frames. Wherein the I-frames are key frames.

In some possible implementations, the PDCP layer may include a shunt in a duplicate (duplication) scenario during the shunt of XR service data.

The embodiment of the disclosure provides a data transmission method. Referring to fig. 4, fig. 4 is a data transmission method according to an exemplary embodiment, and as shown in fig. 4, the method includes step S401, specifically:

in step S401, if the data packet is PDCP control data, the PDCP entity sends the data packet to the first RLC entity.

In an example, the first RLC entity is the primary RLC (primary RLC entity) or a particular RLC entity designated for the network.

In some possible embodiments, the first service is an XR service, and the data packet is data transmitted in an XR service scenario.

In some possible embodiments, PDCP Control data (PDCP Control PDU) is data generated by the PDCP layer.

In the embodiment of the disclosure, in an XR service scenario, the PDCP layer delivers PDCP control data to the first RLC entity.

The embodiment of the disclosure provides a data transmission method. Referring to fig. 5, fig. 5 is a data transmission method according to an exemplary embodiment, and as shown in fig. 5, the method includes step S501, specifically:

In step S501, if the data packet is a PDCP data protocol data unit PDU, the PDCP entity sends the data packet to at least one RLC entity according to attribute information of the data packet of the first service.

In some possible implementations, a PDCP Data protocol Data unit (PDCP Data PDU) is a Data packet received by the PDCP layer from a higher layer.

In some possible embodiments, the attribute information of the data packet includes one of:

the type of the data packet;

priority of the data packet;

processing level of the data packet.

In some possible embodiments, the types of data packets include, for example: i-frames and P-frames. Wherein the I-frames are key frames.

In some possible embodiments, the priority level of the data packet includes, for example: high priority and low priority.

In some possible embodiments, the processing level of the data packet includes, for example: a first processing level and a second processing level.

Wherein, there is correlation among attribute information of three data packets of the type, the priority level and the processing level of the data packet. For example, an I-frame in a type, corresponding to a high priority in priority levels, also corresponds to a first processing level in processing levels, indicating a higher data reliability, and a higher level of importance. And the P frame in the type corresponds to the low priority in the priority level and also corresponds to the second processing level in the processing level, and the importance degree is lower than that of the I frame.

In an example, taking the type of the data packet as an example, when the type of the data packet is an I frame, the associated RLC entity is a first type RLC entity; when the type of the data packet is a P frame, the associated RLC entity is a second type RLC entity. It should be noted that, this association relationship may be preconfigured, and the description of the following embodiments may be referred to.

In this example, the PDCP layer shunts PDCP Data PDUs according to the type of the packet, sends I frame packets to the RLC entity of the first class, and sends P frame packets to the RLC entity of the second class.

Referring to the present example, the PDCP layer may further shunt PDCP Data PDUs according to a priority level of the Data packet, and transmit Data to at least one class of RLC entities; or the PDCP Data PDU is shunted according to the processing level of the Data packet, and Data is sent to at least one class of RLC entity.

In an embodiment of the present disclosure, in an XR service scenario, a PDCP layer performs offloading according to attribute information of PDCP Data PDUs, and transmits Data to at least one class RLC entity.

The embodiment of the disclosure provides a data transmission method. The method comprises the steps of S501-11 to S501-12, and specifically:

in step S501-11, the pdcp entity determines attribute information of a data packet according to a first field in the data packet.

The pdcp entity transmits the data packet to the RLC entity associated with the attribute information of the data packet at step S501-12.

In some possible embodiments, the first field is a field added to a header portion of the PDCP Data PDU of the packet to indicate attribute information of the packet.

In some possible embodiments, the first field is a field newly added to a header portion of a GPRS tunneling protocol (GPRS Tunnelling Protocol for the user plane, GTP-U) at the user plane, to indicate attribute information of the data packet.

In some possible embodiments, the attribute information of the data packet includes one of: the type of the data packet; priority of the data packet; processing level of the data packet. For convenience of description and correlation among three items of attribute information, in the embodiment of the present disclosure, the attribute information of the data packet is described as an example of the type of the data packet, and the first field indicates that the type of the data packet is an I frame or a P frame.

In some possible embodiments, when the type of the data packet is an I frame, the RLC entity associated therewith is a first category RLC entity; when the type of the data packet is a P frame, the associated RLC entity is a second type RLC entity. It should be noted that, this association relationship may be preconfigured, and the description of the following embodiments may be referred to.

In one example: the PDCP layer determines the type of the Data packet as an I frame according to a first field of a packet header part in the PDCP Data PDU. The PDCP layer transmits the data packet to a first type RLC entity associated with the I frame.

In another example: the PDCP layer determines the type of the Data packet as a P frame according to a first field of a packet header part in the PDCP Data PDU. The PDCP layer transmits the data packet to a second type RLC entity associated with the P frame.

In the embodiment of the present disclosure, when the PDCP Data PDU is shunted, the PDCP layer may shunt through the attribute information indicated by the first field.

The embodiment of the disclosure provides a data transmission method. The method comprises steps S501-11 to S501-12, wherein,

the first field is a service data unit SDU type field.

In some possible implementations, the Type of the packet is indicated as I-frame or P-frame in the service data unit Type (Service Data Unit Type, SDU Type) field.

In some possible embodiments, when the first field is the first set value, it indicates that the type of the corresponding PDCP Data PDU is an I frame.

In some possible embodiments, when the first field is the second set value, it indicates that the type of the corresponding PDCP Data PDU is a P frame.

In one example:

as shown in table 1 below, the first set point is 101 and the second set point is 110. When the bit value of the first field is 101, it indicates that the type of the corresponding PDCP Data PDU is an I frame. When the bit value of the first field is 110, it indicates that the type of the corresponding PDCP Data PDU is a P frame. It will be appreciated that when the bit value of the first field is other values, other meanings are indicated.

TABLE 1SDU type

Bits	Category(s)
		000	IP
001	Non-IP
		010	Ethernet
011	Unstructured
		100	ARP
101	I frame
		110	P frame
111	Reserved

In the embodiment of the disclosure, the PDCP layer determines the type of the PDCP Data PDU according to the SDU type field of the PDCP Data PDU, so as to perform splitting according to the type of the Data packet.

The embodiment of the disclosure provides a data transmission method. The method comprises the following steps of S501-21, in particular:

step S501-21, if the PDCP packet copying function of the radio bearer RB of the first service is activated, the PDCP entity copies and sends the data packet to the RLC entity corresponding to the attribute information of the data packet;

or if the PDCP packet duplication function of the RLC entity associated with the PDCP of the radio bearer RB of the first service is activated, the PDCP entity duplicates and sends the data packet to the RLC entity corresponding to the attribute information of the data packet.

In some possible implementations, the first service is an XR service, and this embodiment configures a PDCP packet duplication (PDCP multiplexing) function for an RB corresponding to the XR service. When the PDCP packet duplication function corresponding to the RB is activated, the PDCP layer duplicates and transmits a data packet to an associated RLC entity.

In some possible implementations, the first service is an XR service, and this embodiment configures a PDCP Packet Duplication (PDCP) function for a RLC entity associated with PDCP of the RB corresponding to the XR service. And when the PDCP packet copying function corresponding to the RLC entity is activated, the PDCP layer copies and sends the data packet to the associated RLC entity. The benefit of this function is to refine the packet duplication function of PDCP to RLC entity granularity instead of RB granularity.

In some possible embodiments, the attribute information of the data packet may be one of the following: the type of the data packet; priority of the data packet; processing level of the data packet. For convenience of description, three items of attribute information have correlation, so in the embodiment of the present disclosure, description will be given by taking attribute information of a data packet as a type of the data packet as an example.

In some possible embodiments, when the type of the data packet is an I frame, the RLC entity associated therewith is a first category RLC entity; when the type of the data packet is a P frame, the associated RLC entity is a second type RLC entity. The PDCP delivers the data packet to a different type of RLC entity.

In an example, if the diverted target class RLC entity contains only one RLC entity, for example, one UM RLC entity for UM bidirectional transmission, one UM RLC entity for UM unidirectional transmission for each transmission direction (uplink and downlink), or one AM RLC entity for AM mode, PDCP delivers the data packet to the one RLC entity.

In an example, if the target class RLC entity that is shunted includes more than one RLC entity, for example, for two UM RLC entities in UM bidirectional transmission, four UM RLC entities in UM unidirectional transmission, and two AM RLC entities in AM mode, PDCP packet duplication may be activated for the target class RLC entity that is shunted, and a data packet is duplicated and sent for the relevant RLC entity that is duplicated.

In this example, the PDCP packet duplication function corresponding to any attribute information in the first service may be activated, for example, the PDCP packet duplication function corresponding to the I frame data packet.

For example, when the PDCP packet duplication function corresponding to the RB of the XR service is activated and the type of the data packet is an I frame, the I frame is associated with a first class RLC entity, where the first class RLC entity includes two RLC entities, denoted as a first RLC entity and a second RLC entity. At this time, if PDCP packet duplication is activated for the first RLC entity, the data packet is transmitted to the first RLC entity and the data packet is duplicated and transmitted to the second RLC entity. The first RLC entity may be referred to herein as a primary RLC entity and the second RLC entity as a secondary RLC entity; alternatively, the first RLC entity may be referred to as a duplicate RLC entity, and the second RLC entity may be referred to as a duplicate RLC entity.

In an embodiment, the first RLC entity and the second RLC entity may be protocol contracted or network indicated. For example, the RLC entities are distinguished according to the configuration sequence, and the RLC entity configured first is the first RLC entity; and the second RLC entity is configured subsequently.

In an embodiment, the first RLC entity may default to transmission of PDCP layer control PDUs.

In an example, the secondary RLC entity or duplicate RLC entity may be greater than 1. I.e., multiple PDCP packet duplicate transmissions are made.

In the above embodiments, only the PDCP copy transmission of the I frame data packet is illustrated, and in other examples of the present disclosure, alternative PDCP copy packet transmission may be performed for other types of data packets. By the method, the PDCP duplicate transmission can be flexibly selected for the data types with high reliability requirements, and the PDCP duplicate transmission is not performed for the data types with low reliability requirements, so that the reliability can be met, and meanwhile, the transmission cost is reduced.

In the embodiment of the disclosure, the PDCP packet duplication function of the associated RLC entity can be activated in combination with the attribute information of the data packet to realize shunting in the duplication scenario.

The embodiment of the disclosure provides a data transmission method. The method comprises step S301, or step S401, or step S501. The method further comprises the following step S300:

Step S300, configuring PDCP entity to be associated with N categories of RLC entity, wherein N categories correspond to attribute information of N data packets.

Wherein the PDCP entity is a PDCP entity corresponding to or associated with a radio bearer RB of the first service.

In some possible implementations, the PDCP layer may be preconfigured: association between PDCP entities corresponding to Radio Bearers (RBs) of the XR service and N RLC entities.

In some possible embodiments, the attribute information of the data packet includes one of: the type of the data packet; priority of the data packet; processing level of the data packet. The types of the data packet include, for example: both I-frames and P-frames. The priority level of the data packet includes, for example: both high and low priority. The processing level of the data packet includes, for example: the first processing level and the second processing level.

For each item of attribute information, n=2.

For the type of data packet, PDCP entities corresponding to the XR service RB are associated with two RLC entities, for example, an I frame is associated with a first class RLC and a P frame is associated with a second class RLC.

For the priority level of the data packet, the PDCP entity corresponding to the RB is associated with two RLC entities, for example, a high priority is associated with a first class RLC and a low priority is associated with a second class RLC.

For the processing level of the data packet, the PDCP entity corresponding to the RB is associated with two RLC entities, for example, a first processing level is associated with a first class RLC and a second processing level is associated with a second class RLC.

It can be appreciated that step S300 in the embodiments of the present disclosure may be preconfigured to facilitate determining the RLC entity class associated with the service, and the PDCP layer transmits data to the associated RLC entity class after determining the associated RLC entity class.

In some possible implementations, the RLC entities of each category include at least one unacknowledged mode UM RLC entity (associated with unidirectional or bidirectional transmissions), or include acknowledged mode AM RLC entities.

In an example, each category of RLC entity contains one RLC entity.

For example, in a scenario where duplication is not configured, one class of RLC entity contains one RLC entity. In the UM bidirectional transmission mode, the one RLC entity refers to one UM RLC entity. In the UM unidirectional transmission mode, the one RLC entity refers to an uplink UM RLC entity and a downlink UM RLC entity (one for each transmission direction). In the AM mode, the one RLC entity refers to one AM RLC entity.

In another example, the RLC entity of one category includes a plurality of RLC entities.

For example, in the configuration copy scenario, UM is transmitted bi-directionally to two UM RLC entities, UM is transmitted uni-directionally to four UM RLC entities, and AM is transmitted bi-directionally to two AM RLC entities.

In some possible embodiments, when one class of RLC entity includes one RLC entity, for N classes of RLC entities, N UM RLC entities (bi-directional), or 2N UM RLC entities (one for each transmission direction in unidirectional), or N AM RLC entities are corresponding.

In an example, the RLC entity associated with the I-frame data packet is a first category RLC entity, which may be a RLC entity comprising: one UM RLC entity (bi-directional), two UM RLC entities (corresponding to both uplink and downlink directions, respectively), or one AM RLC entity.

In some possible embodiments, when one class of RLC entity contains multiple RLC entities, the radio bearer RB of the first service is configured with a PDCP packet duplication function. For N categories of RLC entities, (n×m) RLC entities are corresponding. Wherein the (n×m) RLC entities may be: (n×m) UM RLC entities (bidirectional), or (2×n×m) UM RLC entities (one for each transmission direction in unidirectional), or (n×m) AM RLC entities.

In some possible implementations, the number of duplicates M is also considered when configuring the associated RLC entity. Wherein M is more than or equal to 2 and less than or equal to 4.

To facilitate an understanding of the disclosed embodiments, a few specific examples are set forth below.

Example one:

for an RB of XR service, configuring PDCP entities of each of the RBs to associate RLC entities of N categories.

When the RB is not configured with a PDCP packet duplication function or PDCP packet duplication is not configured for the PDCP-associated RLC entity of the RB, the N categories of RLC entities may be corresponding to: n UM RLC entities (bidirectional transmission), or 2N UM RLC entities (corresponding to both uplink and downlink directions, respectively), or N AM RLC entities. That is, one RLC entity class includes one RLC entity, which is 1 UM RLC entity for UM bidirectional transmission, one UM RLC entity for UM unidirectional transmission, one UM RLC entity for each of two directions, and one AM RLC entity for AM mode.

Example two:

for the RBs of XR service, configuring the PDCP entity of each RB to be associated with N categories of RLC entities for shunting according to service attributes.

When the RB is not configured with a PDCP packet duplication function or PDCP packet duplication is not configured for the PDCP-associated RLC entity of the RB, each PDCP entity is associated with N categories of RLC entities. However, a certain class of the N classes of RLC entities may be configured with multiple RLC entities, so as to perform RLC entity level splitting.

Such as: configuring a category RLC entity for the first service data type, the category RLC entity comprising an RLC entity; for the second traffic data type, one class RLC entity is configured, which contains two RLC entities for the primary base station (MCG) and the secondary base Station (SCG), respectively.

In this way, a plurality of split bearers (split bearers) can be used to transmit traffic with a large traffic volume. And for the service with small service volume, no separate bearing transmission is needed.

Example three:

for the RB of XR service, when the RB is configured with a PDCP packet duplication function or PDCP packet duplication is configured for the PDCP associated RLC entity of the RB, the PDCP entity of the RB is configured to be associated with N categories of RLC entities, the N categories of RLC entities correspond to (N.times.M) RLC entities, and M is duplication times.

For example, the N categories of RLC entities may be corresponding to: (n×m) UM RLC entities (bidirectional transmission), or (2×n×m) UM RLC entities (corresponding to both uplink and downlink directions, respectively), or (n×m) AM RLC entities. Wherein M is more than or equal to 2 and less than or equal to 4. I.e. M duplicate RLC entity configurations are made for each type of RLC entity.

Example four:

in a scenario where the PDCP entity is associated with a radio bearer RB of XR service, for example, in a scenario where the PDCP entity is transmitted in association with an RB of XR service. The PDCP layer may perform a shunt transmission after receiving the data packet.

When the packet is a PDCP Data PDU, the splitting can be performed in two ways:

mode one: determining the type according to SDU fields in PDCP Data PDU, and sending Data packet to the RLC entity associated with the type;

mode two: determining the type according to SDU fields in PDCP Data PDU, and copying and sending Data packet to the associated RLC entity of the type if the PDCP packet copying function of XR service RB is activated or the PDCP packet copying function of the associated RLC entity of XR service RB is activated.

Otherwise, the data packet is sent to the first RLC entity. For example, when the data packet is control data, the data packet is transmitted to the first RLC entity. Wherein the first RLC entity designates an RLC entity for the primary RLC entity or the network.

Based on the same concept as the above-described method, the embodiments of the present disclosure also provide a communication apparatus that can be used to perform the data transmission method in the above-described embodiments.

In one possible implementation, as shown in fig. 6, the communication device 600 includes a PDCP entity 601.

The PDCP entity 601 is configured to send data packets to at least one type of radio link control RLC entity when the service type is a first service.

In some possible embodiments, the PDCP entity 601 is further configured to send the data packet to at least one type of RLC entity according to attribute information of the data packet of the first service if the data packet is a PDCP data protocol data unit PDU.

In some possible embodiments, the PDCP entity 601 is further configured to determine attribute information of the data packet based on a first field in the data packet; and sending the data packet to the RLC entity associated with the attribute information of the data packet.

In some possible embodiments, the PDCP entity 601 is further configured to duplicate and send the data packet to an RLC entity corresponding to the attribute information of the data packet if a PDCP packet duplication function of a radio bearer RB of the first service is activated.

and under the first service, the PDCP packet copying function corresponding to any attribute information is activated.

the type of the data packet;

priority of the data packet;

processing level of the data packet.

In some possible implementations, the communication device may be the user device 101 or the network device 102.

When the communication device is a user equipment 101, its structure may be as shown in fig. 7. Referring to fig. 7, an apparatus 700 may include one or more of the following components: a processing component 702, a memory 704, a power component 706, a multimedia component 708, an audio component 710, an input/output (I/O) interface 712, a sensor component 714, and a communication component 716.

The processing component 702 generally controls overall operation of the apparatus 700, such as operations associated with display, telephone calls, data communications, camera operations, and recording operations. The processing component 702 may include one or more processors 720 to execute instructions to perform all or part of the steps of the methods described above. Further, the processing component 702 can include one or more modules that facilitate interaction between the processing component 702 and other components. For example, the processing component 702 may include a multimedia module to facilitate interaction between the multimedia component 708 and the processing component 702.

Memory 704 is configured to store various types of data to support operations at device 700. Examples of such data include instructions for any application or method operating on the apparatus 700, contact data, phonebook data, messages, pictures, videos, and the like. The memory 704 may be implemented by any type or combination of volatile or nonvolatile memory devices such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disk.

The power supply component 706 provides power to the various components of the device 700. The power components 706 may include a power management system, one or more power sources, and other components associated with generating, managing, and distributing power for the device 700.

The multimedia component 708 includes a screen between the device 700 and the user that provides an output interface. In some embodiments, the screen may include a Liquid Crystal Display (LCD) and a Touch Panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from a user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensor may sense not only the boundary of a touch or sliding action, but also the duration and pressure associated with the touch or sliding operation. In some embodiments, the multimedia component 708 includes a front-facing camera and/or a rear-facing camera. The front-facing camera and/or the rear-facing camera may receive external multimedia data when the device 700 is in an operational mode, such as a shooting mode or a video mode. Each front camera and rear camera may be a fixed optical lens system or have focal length and optical zoom capabilities.

The audio component 710 is configured to output and/or input audio signals. For example, the audio component 710 includes a Microphone (MIC) configured to receive external audio signals when the device 700 is in an operational mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signals may be further stored in the memory 704 or transmitted via the communication component 716. In some embodiments, the audio component 710 further includes a speaker for outputting audio signals.

The I/O interface 712 provides an interface between the processing component 702 and peripheral interface modules, which may be a keyboard, click wheel, buttons, etc. These buttons may include, but are not limited to: homepage button, volume button, start button, and lock button.

The sensor assembly 714 includes one or more sensors for providing status assessment of various aspects of the apparatus 700. For example, the sensor assembly 714 may detect an on/off state of the device 700, a relative positioning of the assemblies, such as a display and keypad of the apparatus 700, the sensor assembly 714 may also detect a change in position of the apparatus 700 or one of the assemblies of the apparatus 700, the presence or absence of user contact with the apparatus 700, an orientation or acceleration/deceleration of the apparatus 700, and a change in temperature of the apparatus 700. The sensor assembly 714 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. The sensor assembly 714 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly 714 may also include an acceleration sensor, a gyroscopic sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.

The communication component 716 is configured to facilitate communication between the apparatus 700 and other devices in a wired or wireless manner. The apparatus 700 may access a wireless network based on a communication standard, such as WiFi,2G or 3G, or a combination thereof. In one exemplary embodiment, the communication component 716 receives broadcast signals or broadcast related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, the communication component 716 further includes a Near Field Communication (NFC) module to facilitate short range communications. For example, the NFC module may be implemented based on Radio Frequency Identification (RFID) technology, infrared data association (IrDA) technology, ultra Wideband (UWB) technology, bluetooth (BT) technology, and other technologies.

In an exemplary embodiment, the apparatus 700 may be implemented by one or more Application Specific Integrated Circuits (ASICs), digital Signal Processors (DSPs), digital Signal Processing Devices (DSPDs), programmable Logic Devices (PLDs), field Programmable Gate Arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic elements for executing the methods described above.

In an exemplary embodiment, a non-transitory computer readable storage medium is also provided, such as memory 704, including instructions executable by processor 720 of apparatus 700 to perform the above-described method. For example, the non-transitory computer readable storage medium may be ROM, random Access Memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, etc.

When the communication device is a network device 102, its structure may be as shown in fig. 8. Referring to fig. 8, a configuration of a communication apparatus is described with a base station as an example. As shown in fig. 8, the apparatus 800 includes a memory 801, a processor 802, a transceiver component 803, and a power supply component 806. The memory 801 is coupled to the processor 802 and can be used to store programs and data necessary for the communication device 800 to perform various functions. The processor 802 is configured to support the communication device 800 to perform the corresponding functions of the above-described method, which functions may be implemented by calling a program stored in the memory 801. The transceiver component 803 may be a wireless transceiver that can be utilized to support the communication device 800 in receiving signaling and/or data over a wireless air interface and transmitting signaling and/or data. The transceiver component 803 may also be referred to as a transceiver unit or a communication unit, and the transceiver component 803 may include a radio frequency component 804 and one or more antennas 805, where the radio frequency component 804 may be a remote radio frequency unit (remote radio unit, RRU), and may be specifically used for transmitting radio frequency signals and converting radio frequency signals to baseband signals, and the one or more antennas 805 may be specifically used for radiating and receiving radio frequency signals.

When the communication device 800 needs to transmit data, the processor 802 may perform baseband processing on the data to be transmitted, and then output a baseband signal to the radio frequency unit, where the radio frequency unit performs radio frequency processing on the baseband signal and then transmits the radio frequency signal in the form of electromagnetic wave through the antenna. When data is transmitted to the communication device 800, the radio frequency unit receives a radio frequency signal through the antenna, converts the radio frequency signal into a baseband signal, and outputs the baseband signal to the processor 802, and the processor 802 converts the baseband signal into data and processes the data.

The disclosed embodiments also provide a communication device comprising a processor and a memory, wherein,

the memory is used for storing a computer program;

the processor is configured to execute the computer program to implement the foregoing data transmission method.

Embodiments of the present disclosure also provide a computer-readable storage medium having instructions stored therein, which when invoked for execution on a computer, cause the computer to perform the foregoing data transmission method.

Other implementations of the disclosed embodiments will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any adaptations, uses, or adaptations of the disclosed embodiments following, in general, the principles of the disclosed embodiments and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosed embodiments being indicated by the following claims.

It is to be understood that the disclosed embodiments are not limited to the precise arrangements and instrumentalities shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the embodiments of the present disclosure is limited only by the appended claims.

Industrial applicability

Claims

1. A data transmission method, the method comprising:

2. The method of claim 1, wherein the PDCP entity transmitting data packets to at least one type of radio link control RLC entity comprises:

3. The method as claimed in claim 2, wherein the PDCP entity transmits the data packet to at least one type of the RLC entity according to attribute information of the data packet of the first service, comprising:

4. The method of claim 3, wherein the first field is a service data unit SDU type field.

5. The method as claimed in claim 2, wherein the PDCP entity transmits the data packet to at least one type of the RLC entity according to attribute information of the data packet of the first service, comprising:

6. The method of claim 5, wherein the PDCP packet copy function of the radio bearer RB of the first service is activated, comprising:

7. The method of any of claims 2 to 6, wherein the attribute information of the data packet comprises one of:

the type of the data packet;

priority of the data packet;

processing level of the data packet.

8. A communication device, the communication device comprising:

and the PDCP entity is used for sending data packets to at least one type of Radio Link Control (RLC) entity when the service type is the first service.

9. A communication device includes a processor and a memory, wherein,

the memory is used for storing a computer program;

the processor is configured to execute the computer program to implement the method of any one of claims 1-7.

10. A computer readable storage medium having instructions stored therein which, when invoked for execution on a computer, cause the computer to perform the method of any of claims 1-7.