Data processing method and device, equipment and storage medium

Abstract

The invention provides a data processing method and device, equipment and a storage medium, and relates to the field of communication, and the data processing method comprises the steps that first equipment packages first data plane data through a first DSAP entity in a data service adaptation protocol DSAP layer, and obtains a first data service adaptation protocol sub protocol data unit DSAP sub PDU; a first device receives a first DSAPPDU from a DSAP layer through a media access control (MAC) layer, wherein the first DSAPPDU comprises a first DSAP sub PDU; the method comprises the steps that a first device packages a first DSAP PDU through an MAC layer to obtain a first MAC sub PDU, and the first MAC sub PDU comprises a first logical channel identifier (LCID) corresponding to a first DSAP entity; according to the data processing method, the end-to-end time delay of the data can be reduced, so that the communication performance can be improved.

Description

Technical Field

[0001] The present application relates to the field of communications, and more particularly, to a data processing method, apparatus, device, and storage medium. Background Art

[0002] The services on the data plane of the sixth-generation (6G) mobile communication technology have the characteristic of a large variety of service types.

[0003] However, the large variety of service types leads to a complex objective situation in end-to-end transmission. Therefore, in terms of transmission, the Radio Link Control (RLC) in the layer 2 (L2) wireless link layer, the Packet Data Convergence Protocol (PDCP), and the Service Data Adaptation Protocol (SDAP) can no longer cover various requirements. For example, they cannot meet the data transmission requirements with high latency requirements, thus affecting the communication performance.

[0004] Therefore, there is an urgent need in the art for a data transmission method to reduce the end-to-end latency of data and thus improve the communication performance. Summary of the Invention

[0005] Embodiments of the present application provide a data processing method, apparatus, device, and storage medium, which can reduce the end-to-end latency of data and thus improve the communication performance.

[0006] In a first aspect, a data processing method is provided, including:

[0007] A first device packets first data plane data through a first DSAP entity in a Data Service Adaptation Protocol (DSAP) layer to obtain a first Data Service Adaptation Protocol sub-protocol data unit (DSAP sub PDU).

[0008] The first device receives a first DSAP PDU from the DSAP layer through a Media Access Control (MAC) layer, and the first DSAP PDU includes the first DSAP sub PDU.

[0009] The first device packets the first DSAP PDU through the MAC layer to obtain a first MAC sub PDU, and the first MAC sub PDU includes a first Logical Channel ID (LCID) corresponding to the first DSAP entity.

[0010] In a second aspect, a data processing method is provided, including:

[0011] The second device unpacks the first Media Access Control sub - Protocol Data Unit (MAC subPDU) through the Media Access Control (MAC) layer to obtain the first Data Service Adaptation Protocol Protocol Data Unit (DSAP PDU). The first DSAP PDU includes the first DSAP sub PDU, and the first MAC sub PDU includes a first Logical Channel ID (LCID).

[0012] The second device receives the first DSAP sub PDU from the MAC layer through a first DSAP entity corresponding to the first LCID in the DSAP layer.

[0013] The second device unpacks the first DSAP sub PDU through the first DSAP entity to obtain first data plane data.

[0014] In a third aspect, a data processing apparatus is provided, including:

[0015] A processing unit, configured to packetize first data plane data through a first DSAP entity in a Data Service Adaptation Protocol (DSAP) layer to obtain a first Data Service Adaptation Protocol sub - Protocol Data Unit (DSAP sub PDU).

[0016] A communication unit, configured to receive a first DSAP PDU from the DSAP layer through the MAC layer, where the first DSAP PDU includes the first DSAP sub PDU.

[0017] The processing unit is further configured to: packetize the first DSAP PDU through the MAC layer to obtain a first MAC sub PDU, where the first MAC sub PDU includes a first Logical Channel ID (LCID) corresponding to the first DSAP entity.

[0018] In a fourth aspect, a data processing apparatus is provided, including:

[0019] A processing unit, configured to unpack a first Media Access Control sub - Protocol Data Unit (MAC subPDU) through the Media Access Control (MAC) layer to obtain a first Data Service Adaptation Protocol Protocol Data Unit (DSAP PDU). The first DSAP PDU includes the first DSAP sub PDU, and the first MAC sub PDU includes a first Logical Channel ID (LCID).

[0020] A communication unit, configured to receive the first DSAP sub PDU from the MAC layer through a first DSAP entity corresponding to the first LCID in the DSAP layer.

[0021] The processing unit is further configured to: unpack the first DSAP sub PDU through the first DSAP entity to obtain first data plane data.

[0022] In a fifth aspect, a first device is provided, where the first device includes a processor and a memory, and the memory stores a program or instruction that can run on the processor. When the program or instruction is executed by the processor, the steps of the method described in the first aspect are implemented.

[0023] In a sixth aspect, a first device is provided, including a processor and a communication interface. The processor is configured to packetize first data plane data through a first DSAP entity in a data service adaptation protocol (DSAP) layer to obtain a first data service adaptation protocol sub-protocol data unit (DSAP sub PDU).

[0024] The communication interface is configured to receive a first DSAP PDU from the DSAP layer through a media access control (MAC) layer, where the first DSAP PDU includes the first DSAP sub PDU.

[0025] The processor is further configured to: packetize the first DSAP PDU through the MAC layer to obtain a first MAC sub PDU, and the first MAC sub PDU includes a first logical channel identifier (LCID) corresponding to the first DSAP entity.

[0026] In a seventh aspect, a second device is provided, where the second device includes a processor and a memory, and the memory stores a program or instruction that can run on the processor. When the program or instruction is executed by the processor, the steps of the method described in the second aspect are implemented.

[0027] In an eighth aspect, a second device is provided, including a processor and a communication interface. The processor is configured to unpack a first media access control sub-protocol data unit (MAC sub PDU) through a media access control (MAC) layer to obtain a first data service adaptation protocol protocol data unit (DSAP PDU), where the first DSAP PDU includes the first DSAP sub PDU, and the first MAC sub PDU includes a first logical channel identifier (LCID).

[0028] The communication interface is configured to receive the first DSAP sub PDU from the MAC layer through a first DSAP entity corresponding to the first LCID in the DSAP layer.

[0029] The processor is further configured to: unpack the first DSAP sub PDU through the first DSAP entity to obtain first data plane data.

[0030] In a ninth aspect, a readable storage medium is provided, on which a program or instructions are stored. When the program or instructions are executed by a processor, the steps of the method described in the first aspect or the steps of the method described in the second aspect are implemented.

[0031] In a tenth aspect, a wireless communication system is provided, including: a first device and a second device. The first device can be used to execute the steps of the method described in the first aspect, and the second device can be used to execute the steps of the method described in the second aspect.

[0032] In an eleventh aspect, a chip is provided. The chip includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run a program or instructions to implement the method described in the first aspect or the method described in the second aspect.

[0033] In a twelfth aspect, a computer program / program product is provided. The computer program / program product is stored in a storage medium. The program / program product is executed by at least one processor to implement the steps of the method described in the first aspect or the steps of the method described in the second aspect.

[0034] In an embodiment of the present application, the first device packets the first data plane data through the first DSAP entity in the DSAP layer to obtain a first DSAP sub PDU; the first device receives the first DSAP PDU from the DSAP layer through the MAC layer, and the first DSAP PDU includes the first DSAP sub PDU; the first device packets the first DSAP PDU through the MAC layer to obtain a first MAC sub PDU, and the first MAC sub PDU includes the first LCID corresponding to the first DSAP entity. Equivalently, the first data plane data is directly packeted through the first DSAP entity, and the first MAC sub PDU obtained after packeting the first DSAP PDU through the MAC layer includes the first LCID corresponding to the first DSAP entity. Thus, direct communication between the DSAP layer and the MAC layer can be enabled, which can reduce the end-to-end data delay, such as reducing the transmission delay and processing delay, and further improving the communication performance. Description of the Drawings

[0035] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for the description of the embodiments of the present application will be briefly introduced below. Obviously, the drawings in the following description are only some embodiments of the present application. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts.

[0036] Figure 1 Block diagram of a wireless communication system to which embodiments of the present application can be applied.

[0037] Figure 2 Schematic diagram of a user plane protocol architecture.

[0038] Figure 3 Schematic diagram of a control plane protocol architecture.

[0039] Figure 4 Schematic flowchart of a data processing method provided by an embodiment of the present application.

[0040] Figure 5 Schematic diagram of a data plane protocol stack architecture provided by an embodiment of the present application.

[0041] Figure 6 Example of a mapping relationship between a service identifier, an identifier of a DSAP entity, and an LCID provided by an embodiment of the present application.

[0042] Figure 7 Example of another mapping relationship between a service identifier, an identifier of a DSAP entity, and an LCID provided by an embodiment of the present application.

[0043] Figure 8 Example of the format of a DSAP PDU provided by an embodiment of the present application.

[0044] Figure 9 Example of the data format of a DSAP subPDU obtained by packetizing data plane data without segmentation provided by an embodiment of the present application.

[0045] Figure 10 Example of the data format of a DSAP sub PDU obtained by packetizing data plane data without segmentation according to a fixed size provided by an embodiment of the present application.

[0046] Figure 11 Example of the data format of a DSAP sub PDU obtained by packetizing data plane data without segmentation or segmentation according to a fixed size under UM provided by an embodiment of the present application.

[0047] Figure 12 Example of the data format of a DSAP sub PDU obtained by packetizing data plane data without segmentation or segmentation according to a fixed size under AM or UM-A provided by an embodiment of the present application.

[0048] Figure 13It is an example of the data format of the DSAP sub PDU obtained by packetizing the data plane data without segmentation or after segmentation according to a semi-static size under UM in the embodiments of the present application.

[0049] Figure 14 It is an example of the data format of the DSAP sub PDU obtained by packetizing the data plane data without segmentation or after segmentation according to a semi-static size under AM or UM-A in the embodiments of the present application.

[0050] Figure 15 It is an example of the data format of the status report in the embodiments of the present application.

[0051] Figure 16 It is an example of the type provided in the embodiments of the present application.

[0052] Figure 17 It is an example of the configuration process provided in the embodiments of the present application.

[0053] Figure 18 It is an example of the position of the DSAP BSR provided in the embodiments of the present application.

[0054] Figure 19 It is an example of the format of the BSR provided in the embodiments of the present application.

[0055] Figure 20 It is a schematic flowchart of another data processing method provided in the embodiments of the present application.

[0056] Figure 21 It shows a schematic block diagram of a data processing device according to an embodiment of the present application.

[0057] Figure 22 It shows a schematic block diagram of another data processing device according to an embodiment of the present application.

[0058] Figure 23 It is an example of the communication device provided in the embodiments of the present application.

[0059] Figure 24 It is a schematic diagram of the hardware structure of a terminal for implementing an embodiment of the present application.

[0060] Figure 25 It is an example of the network side device provided in the embodiments of the present application. Detailed implementation manners

[0061] Next, the technical solutions in the embodiments of the present application will be clearly described with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are some, but not all, of the embodiments of the present application. All other embodiments obtained by those of ordinary skill in the art based on the embodiments in the present application belong to the scope of protection of the present application.

[0062] The terms "first", "second", etc. in this application are used to distinguish similar objects, rather than to describe a specific order or sequence. It should be understood that the terms used in this way can be interchanged under appropriate circumstances, so that the embodiments of this application can be implemented in an order other than those illustrated or described here, and the objects distinguished by "first" and "second" are usually of the same type, and the number of objects is not limited. For example, the first object can be one or more. In addition, "or" in this application means at least one of the connected objects. For example, "A or B" covers three scenarios, namely, Scenario 1: including A and not including B; Scenario 2: including B and not including A; Scenario 3: including both A and B. The character " / " generally indicates that the associated objects before and after are in an "or" relationship.

[0063] The term "indicate" in this application can be either a direct indication (or an explicit indication) or an indirect indication (or an implicit indication). Among them, a direct indication can be understood as that the sender clearly informs the receiver of specific information, operations to be performed, or request results, etc. in the sent indication; an indirect indication can be understood as that the receiver determines the corresponding information according to the indication sent by the sender, or makes a judgment and determines the operations to be performed or request results, etc. according to the judgment result.

[0064] It should be noted that the technology described in the embodiments of this application is not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, and can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA), or other systems. The terms "system" and "network" in the embodiments of this application are often used interchangeably, and the described technology can be used in the above-mentioned systems and radio technologies, as well as in other systems and radio technologies. The following description describes the New Radio (NR) system for example purposes, and the NR terms are used in most of the following descriptions, but these technologies can also be applied to systems other than the NR system, such as the 6th Generation (6G) communication system.

[0065] Figure 1 The block diagram of a wireless communication system to which the embodiments of this application can be applied is shown.

[0066] As Figure 1 shown, the wireless communication system includes a terminal 11 and a network-side device 12.

[0067] Among them, the terminal 11 can be a mobile phone, a tablet personal computer, a laptop computer, a notebook computer, a personal digital assistant (PDA), a handheld computer, a netbook, an ultra-mobile personal computer (UMPC), a mobile Internet device (MID), an augmented reality (AR), a virtual reality (VR) device, a robot, a wearable device, a flight vehicle, a vehicle user equipment (VUE), a shipborne device, a pedestrian user equipment (PUE), a smart home (home devices with wireless communication functions, such as refrigerators, TVs, washing machines or furniture, etc.), a game console, a personal computer (PC), a teller machine or a self-service machine, etc. Wearable devices include: smart watches, smart bracelets, smart earphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets, smart ankle chains, etc.), smart wristbands, smart clothing, etc. Among them, the vehicle user equipment can also be referred to as a vehicle terminal, a vehicle controller, a vehicle module, a vehicle component, a vehicle chip or a vehicle unit, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiments of the present application.

[0068] The network-side device 12 may include an access network device.

[0069] Among them, the access network device may also be referred to as a Radio Access Network (RAN) device, a radio access network function, or a radio access network unit. The access network device may include a base station, a Wireless Local Area Network (WLAN) Access Point (AP), or a Wireless Fidelity (WiFi) node, etc. Among them, the base station may be referred to as Node B (NB), Evolved Node B (eNB), the next generation Node B (gNB), New Radio Node B (NR Node B), access point, Relay Base Station (RBS), Serving Base Station (SBS), Base Transceiver Station (BTS), radio base station, radio transceiver, Basic Service Set (BSS), Extended Service Set (ESS), home Node B (HNB), home evolved Node B, Transmission Reception Point (TRP), or some other suitable term in the art. As long as the same technical effect is achieved, the base station is not limited to specific technical terms. It should be noted that in the embodiments of this application, only the base station in the NR system is taken as an example for introduction, and the specific type of the base station is not limited.

[0070] The core network device can also be referred to as a core network function or a core network node. Exemplarily, the core network device may include, but is not limited to, at least one of the following: Mobility Management Entity (MME), Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Policy Control Function (PCF), Policy and Charging Rules Function (PCRF), Edge Application Server Discovery Function (EASDF), Unified Data Management (UDM), Unified Data Repository (UDR), Home Subscriber Server (HSS), Centralized network configuration (CNC), Network Repository Function (NRF), Network Exposure Function (NEF), Local NEF (L-NEF), Binding Support Function (BSF), Application Function (AF), Location Management Function (LMF), location server, etc. It should be noted that in the embodiments of this application, only the core network functions in the NR system are taken as examples for introduction, and the specific types of core network functions are not limited.

[0071] To facilitate a better understanding of the embodiments of this application, the related technologies of this application are described.

[0072] Figure 2 It is a schematic diagram of a user plane protocol architecture.

[0073] As Figure 2 shown, the user plane of the UE and the access network device (such as gNB) may include the following protocol layers:

[0074] Physical Layer (PHY);

[0075] Media Access Control (MAC) layer;

[0076] Radio Link Control (RLC) layer;

[0077] Packet Data Convergence Protocol (PDCP) layer;

[0078] Service Data Adaptation Protocol (SDAP) layer.

[0079] Figure 3 It is a schematic diagram of a control plane protocol architecture.

[0080] Such as Figure 3 As shown, the control plane of the UE may include the following protocol layers:

[0081] PHY layer;

[0082] MAC layer;

[0083] RLC layer;

[0084] PDCP layer;

[0085] Radio Resource Control (RRC) layer;

[0086] Non-Access Stratum (NAS).

[0087] Among them, the control plane of the access network device (such as gNB) may include the following protocol layers:

[0088] PHY layer;

[0089] MAC layer;

[0090] RLC layer;

[0091] PDCP layer;

[0092] Radio Resource Control (RRC) layer.

[0093] Among them, the control plane of the core network function (such as AMF) includes the NAS layer. The NAS layer of the UE and the NAS layer of the core network function can communicate directly.

[0094] It can be seen that both the user plane and the signaling plane will pass through the PDCP and RLC protocol layers for L2 transmission.

[0095] PDCP layer: Its main functions include data transmission, compression and decompression (RoHC or EHC), security processing (encryption and decryption, integrity protection and verification), PDCP duplication, and in-order (or out-of-order) delivery. A PDCP entity can correspond to one or more RLC UM entities and AM entities, but there is no TM entity, that is, when RLC uses TM transmission, it does not go through PDCP processing.

[0096] RLC layer: It supports three transmission modes: Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM). TM is a transparent transmission mode and does not support segmentation. UM can segment but does not provide retransmission. AM can segment and retransmit, providing reliable transmission through status reports, but does not allow packet loss.

[0097] However, the variety of service types leads to a complex objective situation in end-to-end transmission. Therefore, in terms of transmission, the RLC layer, PDCP layer, and SDAP layer of layer 2 (L2) can no longer cover various requirements. For example, they cannot meet the data transmission requirements with high latency requirements, thus affecting the communication performance.

[0098] For example, for the RLC layer, UM does not support reliable transmission, and AM does not allow packet loss, which may not be applicable to some service scenarios on the data plane. For example, in the case of reporting measurement results in a weak signal field, the measurement results may be lost in UM, and signaling processes such as reconstruction may be triggered in AM, increasing additional overhead.

[0099] In view of this, the embodiments of the present application provide a data processing method, device, equipment, and storage medium, which can reduce the end-to-end latency of data and thus improve the communication performance.

[0100] Figure 4 It is a schematic flowchart of the data processing method 200 provided by the embodiments of the present application.

[0101] As Figure 4 shown, the method 200 may include:

[0102] S210, The first device packets the first data plane data through the first DSAP entity in the Data Service Adaptation Protocol (DSAP) layer to obtain the first Data Service Adaptation Protocol sub - Protocol Data Unit (DSAP sub PDU).

[0103] S220, The first device receives the first DSAP PDU from the DSAP layer through the MAC layer, and the first DSAP PDU includes the first DSAP sub PDU.

[0104] S230, The first device packets the first DSAP PDU through the MAC layer to obtain the first MAC sub PDU, and the first MAC sub PDU includes the first Logical Channel ID (LCID) corresponding to the first DSAP entity.

[0105] It should be understood that the first device can be a terminal or an access network device.

[0106] Taking the first device as a terminal device as an example, the first DSAP entity receives the first data plane data. The first data plane data can be the original data of the data plane to be sent uplink. The first DSAP entity processes the first data plane data to obtain the first DSAP sub PDU and sends it to the MAC layer. In other words, after receiving the first DSAP PDU including the first DSAP sub PDU, the MAC layer obtains a complete uplink transmission block (TB) based on the first DSAP PDU and sends it.

[0107] In this embodiment, the first DSAP entity directly packets the first data plane data, and the first MAC sub PDU obtained after the MAC layer packets the first DSAP PDU includes the first LCID corresponding to the first DSAP entity. Thus, it can enable direct communication between the DSAP layer and the MAC layer, reduce the data end - to - end delay, such as reducing the transmission delay and processing delay, and further improve the communication performance.

[0108] In some embodiments, the first DSAP entity is the DSAP entity in the DSAP layer corresponding to the service identifier of the first data plane data.

[0109] Exemplarily, the service identifier of the first data is used to uniquely identify the service of the first data plane.

[0110] In some embodiments, the MAC layer is configured with at least one LCID dedicated to data plane data, and the at least one LCID includes the first LCID.

[0111] Exemplarily, the MAC layer is configured with one LCID dedicated to data plane data. That is to say, a common LCID can be used for the data plane.

[0112] In this embodiment, at least one LCID dedicated to the data plane is defined in the MAC, which can be used to identify data plane data, and thus data transparent transmission from the MAC layer to the DSAP layer can be achieved.

[0113] In some embodiments, the at least one LCID is multiple LCIDs corresponding to multiple types, and the multiple types include at least one of the following: at least one service type, at least one end-to-end type.

[0114] Exemplarily, the MAC layer is configured with multiple LCIDs dedicated to data plane data, and the multiple LCIDs can correspond to multiple types.

[0115] Exemplarily, the at least one service type may include types such as Artificial Intelligence (AI), communication and sensing, etc. For the at least one end-to-end type, it may include types such as UE<->RAN or UE<->CN. Exemplarily, the multiple types may also be multiple combined types, and the combined types can be formed by combining different types, such as service types and end-to-end types. That is to say, they can be defined respectively according to the service types (such as AI or communication and sensing), end-to-end types (UE<->RAN or UE<->CN), or their combinations of different data planes.

[0116] Exemplarily, the at least one LCID can be predefined or defined using RRC signaling.

[0117] For example, the LCID dedicated to the data plane can be defined by the following signaling:

[0118]

[0119]

[0120] In some embodiments, the S220 includes:

[0121] The first device receives the first DSAP PDU from the DSAP layer through the MAC layer and at least one of the following:

[0122] PDCP layer, RLC layer;

[0123] Among them, the PDCP layer is configured not to process data plane data, and the transmission mode of the RLC layer is configured in transparent mode.

[0124] Figure 5 It is a schematic diagram of the data plane protocol stack architecture provided by an embodiment of the present application.

[0125] As Figure 5 shown, for the protocol architecture of the data plane, the difference from the user plane is that there is no PDCP and RLC protocol layers, or the PDCP layer and the RLC layer can be retained, but the functions are simplified. When the PDCP layer and the RLC layer are retained, the RLC can be transparently transmitted using TM. As the data plane radio bearer (DPRB) carrying data on the data plane, there is no original PDCP-config, that is, no operation is performed, so there is no need for a PDCP header either.

[0126] For example, the RRC signaling is configured as follows:

[0127]

[0128]

[0129] In this embodiment, by deleting the PDCP and RLC protocol layers, or by simplifying their functions on the basis of retaining the PDCP layer and the RLC layer, the L2 on the data plane can be isolated from the processing of the RLC, PDCP, and even SDAP in the protocol stack, ensuring the independence of the data plane protocol stack. In addition, by simplifying the processing of the data plane protocol stack, the delay can be reduced, such as no ARQ, no sorting, etc., thereby ensuring that the data plane protocol stack better conforms to the data plane characteristics and improving the communication performance.

[0130] In some embodiments, the method 200 further includes:

[0131] The first device obtains DSAP configuration information, and the DSAP configuration information is used to configure at least one of the following:

[0132] At least one DSAP entity ID;

[0133] At least one service ID (Data Plane Traffic ID);

[0134] At least one LCID; for example, when the RLC layer is not retained, the DSAP configuration information includes the at least one LCID; for another example, when the RLC layer is retained, the DSAP configuration information does not include the at least one LCID, and in this case, the configuration information of the RLC layer may include the at least one LCID;

[0135] The first mapping relationship between the at least one DSAP entity identifier and the at least one service identifier;

[0136] The second mapping relationship between the at least one DSAP entity identifier and the at least one LCID;

[0137] The priority of the DSAP entity;

[0138] The uplink data source;

[0139] The downlink data destination;

[0140] The indication of whether to encrypt or decrypt;

[0141] The security algorithm for encryption;

[0142] The indication of whether integrity protection is performed;

[0143] The security algorithm for integrity protection;

[0144] The indication of whether to decrypt;

[0145] The transmission mode; for example, TM, UM, AM, UM-A;

[0146] The first indication information indicating whether segmentation is allowed;

[0147] The packet assembly parameters;

[0148] The segmentation allowance parameters; for example, set when limited to UM, AM, and UM-A;

[0149] The segmentation allowance multiple; for example, set when limited to UM, AM, and UM-A, and effective when the segmentation allowance parameters are set;

[0150] The indication of whether to deliver in sequence;

[0151] The indication of whether to compress;

[0152] The compression algorithm;

[0153] The indication of whether to perform retransmission;

[0154] The identifier of the BSR group; for example, the Logical Channel Group (LCG).

[0155] It should be understood that the present application does not limit the specific parameters and order included in the DSAP configuration information.

[0156] In this embodiment, through the DSAP configuration information, the processing of the DSAP layer can aggregate the functions of the RLC layer and the PDCP layer, and there are differences from the functions of the RLC layer and the PDCP layer.

[0157] Specifically, the differences from the RLC function:

[0158] 1. When the RLC layer packs data for uplink transmission, if the resources are insufficient, it will perform segmentation processing according to the packet size (size) indicated by the MAC. In this embodiment, the segmentation of the DSAP layer is within the packet size (size) indicated by the MAC, and the packets can be divided into non-segmented packets (such as packets with no fixed size or fixed-size packets) and segmented packets according to the transmission mode and configuration of the DSAP. When segmenting, it can be segmented according to a fixed size (such as segmentation allowable parameters or packet parameters), a semi-static size (such as segmentation allowable parameters), or a segmentation allowable multiple.

[0159] 2. The RLC supports three transmission modes: TM, UM, and AM. TM is the transparent transmission mode, UM does not provide retransmission, and AM provides reliable transmission through status reports but does not allow packet loss. In this embodiment, the DSAP layer on the data plane adds a transmission mode UM-A on the basis of TM, UM, and AM. Compared with UM, it can provide retransmission, and compared with AM, it allows packet loss within a certain range, that is, when the number of times the receiving end requests the retransmission of a certain PDU from the peer device reaches the threshold and the PDU is still not completely received, it accepts the fact that the PDU is lost and updates the receiving window status. This is to adapt to various QoS situations of the data plane services. In addition, although the AM and UM-A processing of the DSAP layer supports retransmission, it will not re-segment the segmented data to simplify the processing.

[0160] Differences from the PDCP function:

[0161] 1. The PDCP function is managed on a per-RB basis. Its functions include security, decompression, in-sequence delivery, PDCP duplication, etc. Each RB corresponds to one PDU SESSION. In this embodiment, the DSAP layer may not have the concept of RB and directly uses DSAP entities (each DSAP entity is assigned a different ID) as the unit, which corresponds to a type of service, or an end-to-end type, or a combination thereof, and can be flexibly configured according to different situations. Taking the following figure as an example, for instance, the data transmitted by DSAP entity 1 is used between the UE and the RAN, and the data transmitted by DSAP entity 2 is used between the UE and the CN. When the RAN only performs transparent transmission (or forwarding), different security algorithms (because the algorithm priorities supported by the RAN and the CN may be inconsistent) or even different keys can be set for DSAP entity 1 and DSAP entity 2.

[0162] In addition to the above, the RLC layer and the PDCP layer manage their respective SNs, and each DSAP entity in the data-plane DSAP layer has a unique SN to implement all functions.

[0163] If the TM is configured in the RLC protocol layer to pursue transmission and processing speed, there is no PDCP-related processing, such as security and in-sequence delivery. Therefore, data security and orderliness are not guaranteed. In this embodiment, through parameters such as the indication of in-sequence delivery, the indication of compression, and the compression algorithm in the DSAP configuration information, the functions of the PDCP layer can be aggregated at the DSAP layer, thereby ensuring data security and orderliness.

[0164] Figure 6 It is an example of a mapping relationship among the service identifier, the identifier of the DSAP entity, and the LCID provided by the embodiment of the present application.

[0165] As Figure 6 shown, a service identifier on the data plane can only belong to one DSAP entity, and one DSAP entity can correspond to multiple service identifiers on the data plane. When all service identifiers on the data plane use the same LCID, then all DSAP entities are mapped to the logical channel corresponding to the same LCID.

[0166] Figure 7 It is another example of a mapping relationship among the service identifier, the identifier of the DSAP entity, and the LCID provided by the embodiment of the present application.

[0167] As Figure 7As shown, when the services on the data plane manage LCIDs with a finer granularity, the LCIDs may be defined separately according to different service types on the data plane (such as AI, communication sensing), end-to-end types (UE <-> RAN, UE <-> CN), or a combination thereof. At this time, each DSAP entity corresponds to one or more logical channels, and each logical channel corresponds to one or more DSAP entities. For example, when the DSAP entity configures repeated PDU transmissions, there will be a situation where one DSAP entity corresponds to multiple logical channels.

[0168] In some embodiments, the transmission mode is any one of the following:

[0169] Transparent mode TM, unacknowledged mode UM, acknowledged mode AM, or unacknowledged mode - enhanced UM-A;

[0170] Among them, at least one of the UM, the AM, and the UM-A supports segmentation, and at least one of the AM and the UM-A supports non-segmentation.

[0171] The following points need to be explained for the DSAP configuration information:

[0172] 1. If each DSAP entity in the DSAP layer only corresponds to one service identifier (Data Plane Traffic ID), then at least one service identifier or the first mapping relationship in the DSAP configuration information can be omitted, and the corresponding field will not appear in the DSAP sub-header either. For ease of description, it is assumed that there is a one-to-many situation in the following embodiments by default.

[0173] 2. Non-segmentation is only allowed in the AM and UM-A modes. The reason is that TM itself does not support segmentation; if UM does not allow segmentation, there is no difference in processing and format from TM, and the advantages of UM cannot be reflected; non-segmentation in AM and UM-A can simplify processing and improve reliability by taking advantage of status reports and other features.

[0174] 3. The packet assembly parameter is an optional parameter. If it exists, the DSAP assembles the PDU according to this packet assembly parameter when assembling packets; if it does not exist, the DSAP assembles packets flexibly. In the former case, after the MAC obtains the uplink grant (ul grant), it can notify the DSAP according to an integer multiple N of this packet assembly parameter, and obtain at most N DSAP sub-PDUs to form a MAC sub-PDU for transmission processing. For example, when the number of DSAP sub-PDUs to be sent by the DSAP is less than or equal to N, all DSAP sub-PDUs can be sent. When the number of DSAP sub-PDUs to be sent by the DSAP is greater than N, the data sent is N - 1 DSAP sub-PDUs, and the BSR on the data plane is sent.

[0175] 4. The segment allowance parameter and the segment allowance multiple are optional parameters. The segment allowance multiple takes effect only when the segment allowance parameter is set, indicating that when packet assembly occurs and segmentation occurs, the maximum size of the segmented packet can be the segment allowance parameter × the segment allowance multiple. For example, if the segment allowance parameter is 50 and the segment allowance multiple is 3, then when segmentation occurs, the size of the segmented packet can be any value among 50, 100, and 150. Specifically, it can be determined by the DSAP according to the SDU size based on the packet assembly size indicated by the MAC layer.

[0176] In some embodiments, the DSAP configuration information satisfies at least one of the following:

[0177] In the case where the first mapping relationship is not a one-to-one mapping relationship, the DSAP configuration information includes the at least one service identifier and the first mapping relationship;

[0178] In the case where the first indication information indicates that segmentation is not allowed, the DSAP configuration information includes or does not include the packet assembly parameter;

[0179] In the case where the first indication information indicates that segmentation is allowed, the DSAP configuration information includes the segment allowance parameter;

[0180] In the case where the DSAP configuration information does not include the first indication information, the DSAP configuration information includes the packet assembly parameter and does not include the segment allowance parameter, or the DSAP configuration information does not include the packet assembly parameter and includes the segment allowance parameter;

[0181] In the case where the DSAP configuration information includes the segment allowance parameter, the DSAP configuration information includes or does not include the segment allowance multiple.

[0182] Figure 8 It is an example of the format of the DSAP PDU provided by the embodiments of the present application.

[0183] As Figure 8 shown, the DSAP PDU may include one or more DSAP sub PDUs, and each DSAP sub PDU may have a corresponding DSAP sub-header. For example, the DSAP PDU may include DSAP sub-header 1, DSAP sub PDU1 corresponding to DSAP sub-header 1, DSAP sub-header 2, DSAP sub PDU2 corresponding to DSAP sub-header 2, DSAP sub-header 3, and DSAP sub PDU3 corresponding to DSAP sub-header 3.

[0184] Of course, in other alternative embodiments, the number of DSAP sub PDUs or DSAP sub - headers included in the DSAP PDU may also be a value other than 3, and the present application does not make specific limitations thereon.

[0185] In some embodiments, S210 includes:

[0186] The first device, through the first DSAP entity, based on the first indication information in the DSAP configuration information, indicates packet assembly without segmentation or packet assembly after segmentation of the first data plane data, to obtain the first DSAP sub PDU;

[0187] Wherein, the DSAP sub - header of the first DSAP sub PDU includes a field carrying information for indicating the length of the payload in the first DSAP sub PDU.

[0188] In some embodiments, S210 includes:

[0189] The first device, through the first DSAP entity, based on the packet - assembly parameters in the DSAP configuration information, performs packet assembly without segmentation on the first data plane data, to obtain the first DSAP sub PDU.

[0190] In some embodiments, S210 includes:

[0191] The first device, through the first DSAP entity, based on the segmentation - allowed parameter in the DSAP configuration information, performs packet assembly without segmentation or packet assembly after segmentation on the first data plane data, to obtain the first DSAP sub PDU; or

[0192] The first device, through the first DSAP entity, based on the segmentation - allowed parameter and the segmentation - allowed multiple in the DSAP configuration information, performs packet assembly without segmentation or packet assembly after segmentation on the first data plane data, to obtain the first DSAP sub PDU.

[0193] In some embodiments, the value of the segmentation - allowed parameter is a unique value; wherein, the first DSAP sub PDU satisfies any one of the following:

[0194] In the case where the first device performs packet assembly without segmentation on the first data plane data, the DSAP sub - header of the first DSAP sub PDU includes a field for carrying segmentation information and a field carrying information for indicating the length of the payload in the first DSAP sub PDU;

[0195] When the first device performs packet assembly by segmenting the first data plane data and the payload in the first DSAP subPDU is a data packet other than the last data packet, a field for carrying segmentation information is included in the DSAP sub-header;

[0196] When the first device performs packet assembly by segmenting the first data plane data and the payload in the first DSAP subPDU is the last data packet, a field for carrying segmentation information and a field for indicating the length of the payload in the first DSAP sub PDU are included in the DSAP sub-header.

[0197] In some embodiments, the value of the segmentation permission parameter is a value list; wherein, the first DSAP subPDU satisfies any one of the following:

[0198] When the first device performs packet assembly without segmenting the first data plane data, a field for carrying segmentation information and a field for indicating the length of the payload in the first DSAP sub PDU are included in the DSAP sub-header of the first DSAP subPDU;

[0199] When the first device performs packet assembly by segmenting the first data plane data and the payload in the first DSAP subPDU is a data packet other than the last data packet, a field for carrying segmentation information and a field for indicating the length of the payload in the first DSAP sub PDU or a value used in the value list are included in the DSAP sub-header;

[0200] When the first device performs packet assembly by segmenting the first data plane data and the payload in the first DSAP subPDU is the last data packet, a field for carrying segmentation information and a field for indicating the length of the payload in the first DSAP sub PDU are included in the DSAP sub-header.

[0201] In some embodiments, when the first DSAP entity performs packet assembly by segmenting the first data plane data based on the segmentation permission parameter and the payload in the first DSAP sub PDU is a data packet other than the last data packet, a field for indicating the length of the payload in the first DSAP sub PDU or a value used in the value list is included in the DSAP sub-header; or

[0202] When the first DSAP entity packets the first data plane data based on the segmentation permission parameter and the segmentation permission multiple, and the payload in the first DSAP sub PDU is a data packet other than the last data packet, a field for indicating the length of the payload in the first DSAP sub PDU is included in the DSAP sub-header.

[0203] In some embodiments, when the first data plane data is packeted after segmentation and the payload in the first DSAP sub PDU is a data packet other than the last data packet and the first data packet, a field for indicating the sub-sequence number of the first DSAP sub PDU is included in the DSAP sub-header; or

[0204] When the first data plane data is packeted after segmentation and the payload in the first DSAP sub PDU is the first data packet or the last data packet, a field for indicating the sub-sequence number of the first DSAP sub PDU may or may not be included in the DSAP sub-header.

[0205] In some embodiments, when the transmission mode of the DSAP layer is AM or UM-A, a field for indicating whether information feedback is performed is included in the DSAP sub-header of the first DSAP sub PDU.

[0206] In some embodiments, the DSAP sub-header of the first DSAP sub PDU includes at least one of the following:

[0207] A field carrying the identifier of the first DSAP entity;

[0208] A field carrying the service identifier of the first data plane data;

[0209] A field carrying a flag indicating whether the first DSAP sub PDU is a control packet or a data packet;

[0210] A field carrying the sequence number of the first DSAP sub PDU;

[0211] A field for integrity protection and verification of the first DSAP sub PDU.

[0212] In some embodiments, S210 includes:

[0213] The first device receives packet indication information from the MAC layer through the DSAP layer;

[0214] Within the size indicated by the packet assembly indication information, the first device assembles the first data plane data through the first DSAP entity to obtain the first DSAP sub PDU.

[0215] When the DSAP layer receives the packet assembly indication information from the MAC, within the size indicated by the packet assembly indication information, it processes according to the priorities of the DSAP entities in the DSAP layer. For example, after processing the first data plane data according to the priority of the first DSAP entity, the first DSAP sub PDU can be obtained. Another example is that after processing the first data plane data according to the priority of the first DSAP entity, it is also possible to obtain multiple first DSAP sub PDUs.

[0216] In other words, when the MAC layer obtains uplink authorization and determines that the data plane data can be packet assembled according to the logical channel priority, it can send the packet assembly indication information to the DSAP layer. After the first DSAP entity in the DSAP layer completes the packet assembly processing of the first data plane data within the size indicated by the packet assembly indication information, the first DSAP sub PDU is obtained.

[0217] In some embodiments, the method 200 further includes:

[0218] In the case where the first DSAP entity cannot complete the packet assembly of the data plane data to be sent within the size indicated by the packet assembly indication information, the first device sends a buffer size report BSR indication to the MAC layer through the DSAP layer. The BSR indication includes the identifier of the BSR group and the buffer size of the BSR group.

[0219] The first device assembles packets based on the BSR indication through the MAC layer to obtain a second MAC sub PDU. The second MAC sub PDU includes a MAC control element CE. The MAC CE includes a field carrying the identifier of the buffer status report BSR group and a field carrying the buffer size of the BSR group.

[0220] Exemplarily, the identifier of the BSR group may be the LCG to which the first LCID belongs.

[0221] Exemplarily, the buffer size of the BSR group may be referred to as the data volume of the data plane data to be sent in the BSR group.

[0222] In some embodiments, the method 200 further includes:

[0223] When the first DSAP entity fails to packetize the first data plane data within the size indicated by the packet indication information, the first device packetizes the first buffer size report (BSR) through the first DSAP entity to obtain a second DSAP sub PDU:

[0224] Wherein, the first BSR is the BSR of the first LCID, the BSR of the first DSAP entity, or the BSR of the service identifier of the first data plane data, and the first DSAP PDU includes the second DSAP sub PDU.

[0225] In some embodiments, the second DSAP sub PDU satisfies any one of the following:

[0226] When the first BSR is the BSR of the first LCID, the second DSAP sub PDU includes a DSAP control element (CE), and the DSAP CE includes a field carrying a domain for identifying the second DSAP sub PDU as a DSAP BSR and a field carrying the buffer size of the first LCID;

[0227] Exemplarily, the buffer size of the first LCID can be referred to as the data volume of the data to be sent on the data plane of the first LCID.

[0228] When the second DSAP sub PDU includes the DSAP CE, the second DSAP sub PDU is the first DSAP sub PDU or the last DSAP sub PDU in the first DSAP PDU;

[0229] When the first BSR is the BSR of the first DSAP entity, the second DSAP sub PDU includes a field carrying the identifier of the first DSAP entity;

[0230] When the first BSR is the BSR of the service identifier of the first data plane data, the second DSAP sub PDU includes a field carrying the identifier of the first DSAP entity and a field carrying the service identifier of the first data plane data.

[0231] In some embodiments, when the first BSR is the BSR of the first DSAP entity or the BSR of the service identifier of the first data plane data, the second DSAP sub PDU further includes at least one of the following:

[0232] A field carrying a domain for indicating that the second DSAP sub PDU is a control packet or a data packet;

[0233] It carries a field for indicating the type of the second DSAP sub PDU.

[0234] In some embodiments, the S210 includes:

[0235] The first device packetizes the first data plane data through the first DSAP entity and performs at least one of the following to obtain the first DSAP sub PDU: desensitization, encryption, notifying the MAC layer of the amount of data to be sent existing in the DSAP layer, and integrity protection.

[0236] In some embodiments, the first DSAP PDU includes a third DSAP sub PDU, and the third DSAP sub PDU includes a field carrying the type of the status report and a field carrying the status report, and the type of the status report includes at least one of the following:

[0237] Unacknowledged sequence number;

[0238] Unacknowledged start sequence number and unacknowledged end sequence number;

[0239] Unacknowledged sequence number and unacknowledged sub-sequence number in the unacknowledged sequence number;

[0240] Unacknowledged first sequence number, unacknowledged start sub-sequence number in the first sequence number, unacknowledged second sequence number, and unacknowledged end sub-sequence number in the second sequence number.

[0241] In some embodiments, the third DSAP sub PDU further includes at least one of the following:

[0242] A field carrying the identifier of the first DSAP entity;

[0243] A field carrying the service identifier of the first data plane data;

[0244] A field carrying a field for indicating whether the third DSAP sub PDU is a control packet or a data packet;

[0245] A field carrying a field for indicating the type of the third DSAP sub PDU;

[0246] A field carrying the length of the field carrying the status report;

[0247] A field carrying acknowledgment information;

[0248] A field carrying a field for indicating the type of the status report and a field for indicating the content corresponding to the type of the status report.

[0249] The solution of the present application will be described below in conjunction with specific embodiments.

[0250] Embodiment 1:

[0251] Considering that the transmission data size and period of some data-plane services are relatively fixed, therefore, when configuring the DSAP entity, the base station can simplify the processing by not segmenting, saving processing time, and because the base station knows which data-plane services are enabled, it can reserve resources during resource allocation to achieve the purpose of not segmenting and being able to report completely.

[0252] In this embodiment, the DSAP entity supports packetizing without segmentation according to the size of the data-plane data.

[0253] Figure 9 It is an example of the data format of the DSAP subPDU obtained by packetizing the data-plane data without segmentation provided by the embodiment of the present application.

[0254] As Figure 9 shown in (a) of [], the DSAP sub PDU obtained by packetizing the data-plane data without segmentation under TM or UM may include a DSAP sub-header and a Payload. Among them, the DSAP sub-header may include at least one of the following:

[0255] DSAP entity ID: Used to represent the DSAP entity, which can be the DSAP entity ID for packetizing the data-plane data;

[0256] Service identifier: Used to identify the service to which the data-plane data belongs;

[0257] D / C: Indicates that the obtained DSAP sub PDU is a control packet or a data packet. The control packet generated under TM may be a feedback data packet generated due to functions such as compression being configured;

[0258] SN: Indicates the sequence number of the obtained DSAP sub PDU;

[0259] MAC-I: Used for integrity protection and verification, which can be placed inside the DSAP sub-header or behind the Payload. If the integrity protection is not configured for this DSAP entity, the DSAP sub-header can be without MAC-I, that is, it may not include MAC-I.

[0260] data_len: Length field, which is used to indicate the length of the subsequent Payload.

[0261] As Figure 9As shown in (b) therein, the DSAP sub PDU obtained by packetizing the data plane data without segmentation under AM or UM-A, compared with the DSAP sub PDU obtained by packetizing the data plane data without segmentation under TM or UM, its DSAP sub-header may further include:

[0262] P: The value of P is used to indicate whether to perform information feedback or status report feedback, that is, to indicate whether the receiving end performs information feedback or status report feedback.

[0263] Embodiment 2:

[0264] In this embodiment, the DSAP entity can perform packetization without segmentation according to a fixed size (size).

[0265] For example, when the packetization parameters in the DSAP configuration information are set, the DSAP entity can perform packetization without segmentation according to the packetization parameters in the DSAP configuration information.

[0266] Figure 10 It is an example of the data format of the DSAP sub PDU obtained by packetizing the data plane data without segmentation according to a fixed size provided by the embodiments of the present application.

[0267] Such as Figure 10 As shown in (a) therein, the DSAP sub PDU obtained by packetizing the data plane data without segmentation according to a fixed size under TM or UM may include a DSAP sub-header and a payload, where the DSAP sub-header may include at least one of the following:

[0268] DSAP entity ID: Used to represent the DSAP entity, which may be the DSAP entity ID for packetizing the data plane data;

[0269] Service identifier: Used to identify the service to which the data plane data belongs;

[0270] D / C: Indicates that the obtained DSAP sub PDU is a control packet or a data packet. The control packet generated under TM may be a feedback data packet generated due to functions such as compression being configured;

[0271] SN: Represents the sequence number of the obtained DSAP sub PDU;

[0272] MAC-I: Used for integrity protection and verification, which can be placed inside the DSAP sub-header or behind the payload. If the DSAP entity is not configured with integrity protection, the DSAP sub-header may not have MAC-I, that is, it may not include MAC-I.

[0273] Such as Figure 10As shown in (b) of , the DSAP sub PDU obtained by packetizing the data plane data without segmentation under AM or UM-A, compared with the DSAP sub PDU obtained by packetizing the data plane data without segmentation in fixed size under TM or UM, the DSAP sub-header may further include:

[0274] P: The value of P is used to indicate whether to perform information feedback or status report feedback, that is, to indicate whether the receiving end performs information feedback or status report feedback.

[0275] In this embodiment, since the DSAP entity packetizes according to a fixed size (size), the data_len field is no longer required in the DSAP sub-header.

[0276] Embodiment 3:

[0277] In this embodiment, the DSAP entity packetizes without segmentation or after segmentation according to a fixed size.

[0278] For example, when the segmentation allowable parameter in the DSAP configuration information is set to a unique value and the segmentation allowable multiple is not set, the DSAP entity can packetize without segmentation or after segmentation according to the segmentation allowable parameter in the DSAP configuration information.

[0279] When the service of the data plane is used to collect the measurement results of the serving cell and neighboring cells of the terminal, it is more suitable for the DSAP entity to packetize after segmentation according to a fixed size. For example, if the measurement results are all required to be reported in the following format, the length of each reported data group is 8 bytes (byte). Because neighboring cell measurement involves operations such as frequency point handover, the measurement results for different frequency points may be obtained in batches in DSAP. In this case, if the segmentation allowable parameter is configured as 8 bytes when configuring the DSAP entity, DSAP can packetize after segmentation in the smallest unit of 8 bytes when the obtained uplink grant (UL grant) is not sufficient to report all the measurement results, that is, report a complete group of measurement results.

[0280] frame: 2byte, slot: 1byte, PCI: 2byte, rsrp: 1byte, rsrq: 1byte, serving_cell_flag: 1byte

[0281] When the segmentation allowable parameter is set to a unique value when configuring the DSAP entity, it means that segmentation is allowed, but the data_len is a fixed value except for the last packet during segmentation.

[0282] It should be noted that the segmentation allowable parameter is not applicable to TM.

[0283] Figure 11This is an example of the data format of the DSAP sub PDU obtained by packetizing the data plane data without segmentation or after segmentation in fixed size under UM.

[0284] As Figure 11 shown in (a) of [], the DSAP sub PDU obtained by packetizing the data plane data without segmentation in fixed size under UM may include a DSAP sub header and a Payload. Among them, the DSAP sub header may include at least one of the following:

[0285] DSAP entity ID: used to represent the DSAP entity, which may be the DSAP entity ID for packetizing the data plane data;

[0286] Service identifier: used to identify the service to which the data plane data belongs;

[0287] D / C: indicates that the obtained DSAP sub PDU is a control packet or a data packet;

[0288] Segmentation information (SI): its value can be used to indicate segmentation information. For example, its value of 0b00 indicates no segmentation; its value of 0b01 indicates the first segment; its value of 0b11 indicates the middle segment packet; its value of 0b10 indicates the last segment;

[0289] SN: indicates the sequence number of the obtained DSAP sub PDU;

[0290] MAC-I: used for integrity protection and verification, which can be placed inside the DSAP sub header or behind the Payload. If the DSAP entity is not configured with integrity protection, the DSAP sub header can be without MAC-I, that is, it may not include MAC-I;

[0291] data_len: length field, which is used to indicate the length of the subsequent Payload.

[0292] As Figure 11 shown in (b) of [], when packetizing the segmented data plane data in fixed size under UM, the DSAP sub PDU obtained by packetizing the data packets except the last data packet after segmentation may include a DSAP sub header and a Payload. Among them, the DSAP sub header may include at least one of the following:

[0293] DSAP entity ID: used to represent the DSAP entity, which may be the DSAP entity ID for packetizing the data plane data;

[0294] Service identifier: used to identify the service to which the data plane data belongs;

[0295] D / C: Indicates that the obtained DSAPsub PDU is a control packet or a data packet;

[0296] Segmentation Information (SI): Its value can be used to indicate segmentation information. For example, a value of 0b00 indicates no segmentation; a value of 0b01 indicates the first segment; a value of 0b11 indicates an intermediate segment packet; a value of 0b10 indicates the last segment;

[0297] SN: Represents the sequence number of the obtained DSAPsub PDU;

[0298] MAC-I: Used for integrity protection and verification, can be placed inside the DSAP sub-header or after the payload. If the DSAP entity is not configured with integrity protection, the DSAP sub-header can be without MAC-I, that is, it can not include MAC-I;

[0299] Sub-SN: Its value can be used to indicate the sub-sequence number of the DSAP sub PDU. For example, its value can be used to indicate which data packet the DSAP sub PDU of the data plane data is after segmentation of the data plane data. Or rather, the DSAP sub PDUs generated by segmentation use Sub-SN to represent the position or sequence number of this DSAP sub PDU among all DSAP sub PDUs.

[0300] As Figure 11 shown in (c) below, when packetizing the data plane data segmented by a fixed size under UM, the DSAP sub PDU obtained after packetizing the last data packet after segmentation may include a DSAP sub-header and a payload. Among them, the DSAP sub-header may include at least one of the following:

[0301] DSAP Entity ID: Used to represent the DSAP entity, which can be the DSAP entity ID for packetizing the data plane data;

[0302] Service Identifier: Used to identify the service to which the data plane data belongs;

[0303] D / C: Indicates that the obtained DSAPsub PDU is a control packet or a data packet. The control packet generated in TM mode may be a feedback data packet generated due to functions such as compression being configured;

[0304] Segmentation Information (SI): Its value can be used to indicate segmentation information. For example, a value of 0b00 indicates no segmentation; a value of 0b01 indicates the first segment; a value of 0b11 indicates an intermediate segment packet; a value of 0b10 indicates the last segment;

[0305] SN: Represents the sequence number of the obtained DSAPsub PDU;

[0306] MAC-I: For integrity protection and verification, it can be placed within the DSAP sub-header or after the payload. If the DSAP entity is not configured with integrity protection, the DSAP sub-header may not have MAC-I, that is, it may not include MAC-I.

[0307] data_len: The length field, which is used to indicate the length of the subsequent payload.

[0308] Figure 12 It is an example of the data format of the DSAP sub PDU obtained by packetizing the data plane data without segmentation or after segmentation according to a fixed size under AM or UM-A in the embodiments of the present application.

[0309] Such as Figure 12 shown in (a), (b), and (c) in [reference], the DSAP sub PDU obtained by packetizing the data plane data without segmentation or after segmentation according to a fixed size under AM or UM-A, compared with the DSAP sub PDU obtained by packetizing the data plane data without segmentation or after segmentation according to a fixed size under UM, its DSAP sub-header may further include:

[0310] P: The value of P is used to indicate whether to perform information feedback or status report feedback, that is, it is used to indicate whether the receiving end performs information feedback or status report feedback.

[0311] It should be noted that in this embodiment, when SI is set to 0b01, that is, the first data packet in the segmentation, or when SI is set to 0b10, that is, the last data packet in the segmentation, the Sub-SN field may not exist.

[0312] Example 4:

[0313] In this embodiment, the DSAP entity packetizes without segmentation or after segmentation according to a semi-static size.

[0314] For example, when the segmentation allowance parameter in the DSAP configuration information is set to a value list and the segmentation allowance multiple is not set, the DSAP entity can packetize without segmentation or after segmentation according to the value selected from the value list of the segmentation allowance parameter in the DSAP configuration information (i.e., the semi-static size).

[0315] When configuring the DSAP entity, when the segmentation allow parameter is set to a list, it means that segmentation is allowed, and the value adopted during segmentation can be adaptively set according to the size indicated by the packet assembly indication notified by the MAC. For example: when the value of the segmentation allow parameter = {5, 10, 25}, it means that the value adopted during the packet assembly of the packets in the segmented data packet except the last packet can be selected from 5, 10, 25. If the size indicated by the packet assembly indication is 30 and all the data to be sent by the DSAP entity is 13, the terminal can perform packet assembly without segmentation; if the size indicated by the packet assembly indication is 8 and all the data to be sent by the DSAP entity is 13, then the value adopted by the DSAP entity during packet assembly is 5.

[0316] It should be noted that the segmentation allow parameter does not apply to TM.

[0317] Figure 13 This is an example of the data format of the DSAP sub PDU obtained by packet assembling the data plane data without segmentation or after segmentation according to a semi-static size under UM provided by the embodiments of the present application.

[0318] Such as Figure 13 As shown in (a) of , the DSAP sub PDU obtained by packet assembling the data plane data without segmentation according to a semi-static size under UM may include a DSAP sub-header and a payload. Among them, the DSAP sub-header may include at least one of the following:

[0319] DSAP entity ID: used to represent the DSAP entity, which may be the DSAP entity ID for packet assembling the data plane data;

[0320] Service identifier: used to identify the service to which the data plane data belongs;

[0321] D / C: indicates that the obtained DSAP sub PDU is a control packet or a data packet;

[0322] Segmentation information (SI): its value can be used to indicate segmentation information. For example, its value of 0b00 indicates no segmentation; its value of 0b01 indicates the first segment; its value of 0b11 indicates the middle segment packet; its value of 0b10 indicates the last segment;

[0323] SN: indicates the sequence number of the obtained DSAP sub PDU;

[0324] MAC-I: used for integrity protection and verification, which can be placed inside the DSAP sub-header or behind the payload. If the DSAP entity is not configured with integrity protection, the DSAP sub-header can be without MAC-I, that is, it can not include MAC-I;

[0325] data_len: Length field, which is used to indicate the length of the subsequent payload.

[0326] As Figure 13 As shown in (b) of , when packetizing the data plane data in segments according to a semi-static size under UM, the DSAP sub PDU obtained after packetizing the packets except the last packet after segmentation may include a DSAP sub-header and a payload. Among them, the DSAP sub-header may include at least one of the following:

[0327] DSAP entity ID: Used to represent the DSAP entity, which may be the DSAP entity ID for packetizing the data plane data;

[0328] Service identifier: Used to identify the service to which the data plane data belongs;

[0329] D / C: Indicates that the obtained DSAP sub PDU is a control packet or a data packet;

[0330] Segmentation information (SI): Its value can be used to indicate the segmentation information. For example, its value of 0b00 indicates no segmentation; its value of 0b01 indicates the first segment; its value of 0b11 indicates the intermediate segment packet; its value of 0b10 indicates the last segment;

[0331] SN: Represents the sequence number of the obtained DSAP sub PDU;

[0332] MAC-I: Used for integrity protection and verification, which can be placed inside the DSAP sub-header or behind the payload. If the integrity protection is not configured for this DSAP entity, the DSAP sub-header may not have MAC-I, that is, it may not include MAC-I;

[0333] Sub-SN: Its value can be used to indicate the sub-sequence number of the DSAP sub PDU. For example, its value can be used to indicate which packet of the segmented data plane data the DSAP sub PDU of the data packet is. Or rather, the DSAP sub PDU generated by segmentation uses Sub-SN to represent the position or sequence number of this DSAP sub PDU among all DSAP sub PDUs;

[0334] data_len: Length field, which is used to indicate the length of the subsequent payload.

[0335] As Figure 13 As shown in (c) of , when packetizing the last packet after segmentation of the data plane data in segments according to a semi-static size under UM, the DSAP sub PDU obtained after packetizing the last packet after segmentation may include a DSAP sub-header and a payload. Among them, the DSAP sub-header may include at least one of the following:

[0336] DSAP entity ID: It is used to represent a DSAP entity, which can be the DSAP entity ID for packetizing data plane data;

[0337] Service identifier: It is used to identify the service to which the data plane data belongs;

[0338] D / C: It indicates that the obtained DSAP sub PDU is a control packet or a data packet. The control packet generated in TM mode may be a feedback packet due to functions such as compression being configured;

[0339] Segmentation information (SI): Its value can be used to indicate segmentation information. For example, when its value is 0b00, it indicates no segmentation; when its value is 0b01, it indicates the first segment; when its value is 0b11, it indicates an intermediate segment packet; when its value is 0b10, it indicates the last segment;

[0340] SN: It represents the sequence number of the obtained DSAP sub PDU;

[0341] MAC-I: It is used for integrity protection and verification. It can be placed inside the DSAP sub-header or behind the payload. If integrity protection is not configured for this DSAP entity, the DSAP sub-header can be without MAC-I, that is, it can not include MAC-I;

[0342] data_len: The length field, which is used to indicate the length of the subsequent payload.

[0343] Figure 14 This is an example of the data format of the DSAP sub PDU obtained by packetizing data plane data without segmentation or after segmentation according to a semi-static size under AM or UM-A provided by an embodiment of the present application.

[0344] Such as Figure 14 As shown in (a), (b), and (c) therein, for the DSAP sub PDU obtained by packetizing data plane data without segmentation or after segmentation according to a semi-static size under AM or UM-A, compared with the DSAP sub PDU obtained by packetizing data plane data without segmentation or after segmentation according to a semi-static size under UM, its DSAP sub-header can also include:

[0345] P: The value of P is used to indicate whether to perform feedback on information or status report, that is, it is used to indicate whether the receiving end performs feedback on information or status report.

[0346] It should be noted that in this embodiment, the value of data_len can use the actual length value or can be set as the index of the value selected from the value list parameters of the segmentation allowable parameters. The present application does not make specific limitations on this.

[0347] Example 5:

[0348] In this example, the DSAP entity packets data without segmentation or after segmentation according to the segmentation allowable multiple.

[0349] For example, when the segmentation allowable parameter in the DSAP configuration information is set (for example, set to a unique value or a value list) and the segmentation allowable multiple is set, the DSAP entity can packet data without segmentation or after segmentation according to the unique value of the segmentation allowable parameter in the DSAP configuration information (or the value selected from the value list (i.e., the semi-static size)) and the segmentation allowable multiple.

[0350] It should be understood that in this example, the data format of the DSAP sub PDU obtained after the DSAP entity packets the data plane data without segmentation or after segmentation is the same as that in Embodiment 4 of the invention. The only difference is that when segmenting, the data_len in the format of the last packet needs to indicate the explicit size.

[0351] Example 6:

[0352] In this example, the DSAP entity generates status reports both when using AM and UM-A transmissions, thereby triggering the other party to retransmit. The packet priority of the status report is higher than that of the data.

[0353] Figure 15 It is an example of the data format of the status report in the embodiments of the present application.

[0354] As Figure 15 shown, the status report may include at least one of the following:

[0355] DSAP entity ID: used to represent the DSAP entity, which may be the DSAP entity ID for packetizing the data plane data;

[0356] Service identifier: used to identify the service to which the data plane data belongs;

[0357] D / C: indicates that the obtained DSAP sub PDU is a control packet or a data packet;

[0358] Control PDU type: used to indicate the control type of the DSAP sub PDU;

[0359] data_len: length field, which is used to indicate the length of the subsequent data, including the length from ACK_SN to content N.

[0360] ACK_SN: used to indicate the sequence number of the acknowledgment, such as the sequence number of the data packet that has been completely received or the sequence number of the completely received data packet.

[0361] Type (E_type) 1 to Type N: used to indicate N non-acknowledgment types;

[0362] Content (E_content) 1 to Content N: used to indicate the content corresponding to the type, such as the sequence number of the data packet to be received or the sequence number of the data packet that has not been completely received.

[0363] It should be noted that when E_type is set to different situations, the format of E_content can be different.

[0364] Figure 16 is an example of the type provided by the embodiments of the present application.

[0365] Such as Figure 16 as shown in (a) of , E_type = NACK_SN, all data packets with this SN are lost, and this SN is isolated.

[0366] Such as Figure 16 as shown in (b) of , E_type = continuous NACK_SN, all data packets from Start NACK_SN to End NACK_SN are lost.

[0367] Such as Figure 16 as shown in (c) of , E_type = NACK_sub-SN, the data packet with NACK_sub_SN of NACK_SN is lost.

[0368] Such as Figure 16 as shown in (d) of , E_type = continuous NACK_sub-SN, all data packets from Start NACK_sub_SN of Start NACK_SN to End NACK_sub_SN of End NACK_SN are lost.

[0369] Embodiment 7:

[0370] Figure 17 is an example of the configuration process provided by the embodiments of the present application.

[0371] Such as Figure 17 as shown in , when the service on the data plane is triggered by the UE side, a request message is sent to the RAN, which may carry service-related information for the network side to configure appropriate parameters to establish a transmission link based on this information. When the service on the data plane is triggered by the network side, the network side decides how to configure according to the information for initiating the service.

[0372] For example, when the network needs to establish a data plane transmission link, the rrcReconfiguration message can be used for configuration. If the LCID = 6, the specific content is as follows.

[0373] Solution 1:

[0374]

[0375] Solution 2:

[0376]

[0377]

[0378] It should be noted that the configuration parameters related to DSAP operations can be the DSAP configuration information mentioned above, such as including priority, whether to encrypt / decrypt, security algorithms, whether to perform integrity protection, etc.

[0379] Embodiment 8:

[0380] In this embodiment, when all the data to be sent at the DSAP layer cannot be fully packetized in the current uplink grant, a data plane status buffer report (buffer size report, BSR) is sent to the base station to report the amount of remaining data to be sent.

[0381] Specifically, the BSR can be sent by any one of the following methods:

[0382] Method 1:

[0383] Normally, the BSR is included in the MACCE of the MAC layer, and the remaining data volume to be sent is reported in units of LCG. In this embodiment, for data plane processing, if the LCG to which the data plane belongs is separated from the LCGs of the signaling plane and the user plane, the reporting function of the data volume to be sent on the data plane can be implemented through MACCE to achieve the expected effect.

[0384] Method 2:

[0385] Packetize in the form of a DSAP Control Element.

[0386] The DSAP control element (CE) is similar to the MAC CE of the MAC. At this time, the packetized DSAP BSR reports the amount of remaining data to be sent for each corresponding DSAP entity in units of LCID. After receiving the DSAP BSR, the DSAP on the base station side notifies the MAC layer through an interface message to complete the resource allocation process. At this time, the DSAP BSR can be distinguished from the DSAP sub-header by setting the identification ID of the DSAP BSR to a value outside the range of the DSAP entity ID.

[0387] Figure 18 This is an example of the position of the DSAP BSR provided by the embodiments of the present application.

[0388] Such as Figure 18 As shown in (a) of Figure 18 This DSAP BSR can also be placed at the end of the DSAP PDU, as shown in (b) of

[0389] Method 3:

[0390] Packetize in the form of a DSAP Control PDU.

[0391] Figure 19 This is an example of the format of the BSR provided by the embodiments of the present application.

[0392] Such as Figure 19 As shown, the BSR may include at least one of the following:

[0393] DSAP entity ID: used to represent the DSAP entity, which can be the DSAP entity ID for packetizing data plane data;

[0394] Service identifier: used to identify the service to which the data plane data belongs;

[0395] D / C: indicates whether the obtained DSAP sub-PDU is a control packet or a data packet;

[0396] Control PDU type: used to indicate the control type of the DSAP sub-PDU;

[0397] Content: used to indicate the amount of data to be sent.

[0398] In this embodiment, the BSR may report the amount of data to be sent in units of DSAP entities or in units of service identifiers, so as to improve the management unit fineness and flexibility. If in units of DSAP entities, the service identifier may not be included; if in units of service identifiers, the DSAP entity ID and the service identifier may be included at the same time.

[0399] It should be understood that the accompanying drawings involved in Embodiments 1 to 8 are only exemplary and should not be construed as a limitation to this application. For example, only the types of domains included are exemplified in the accompanying drawings, and should not be construed as a limitation to the actual lengths of the respective domains. Again, the data_len involved in the accompanying drawings may also contain auxiliary domains, which are used to represent the length of the data_len. This application does not make specific limitations thereto.

[0400] The data processing method provided by this application is described above from the perspective of the first device (i.e., the perspective of the sender or the perspective of packet assembly), and below from the perspective of the second device (i.e., the perspective of the receiver or the perspective of packet disassembly).

[0401] Figure 20 It is a schematic flowchart of the data processing method 300 provided by an embodiment of this application.

[0402] As Figure 20 shown, the data processing method 300 may include:

[0403] S310, the second device unpacks the first media access control sub-protocol data unit MAC sub PDU through the media access control MAC layer to obtain the first data service adaptation protocol data unit DSAP PDU. The first DSAP PDU includes the first DSAP sub PDU, and the first MAC sub PDU includes the first logical channel identifier LCID;

[0404] S320, the second device receives the first DSAP sub PDU from the MAC layer through the first DSAP entity corresponding to the first LCID in the DSAP layer;

[0405] S330, the second device unpacks the first DSAP sub PDU through the first DSAP entity to obtain the first data plane data.

[0406] It should be understood that the second device may be a terminal or an access network device.

[0407] Taking the second device as an example of a terminal device, when the MAC receives the first MAC sub PDU, it unpacks it to obtain the first LCID. Thus, the first DSAP sub PDU in the first DSAP PDU can be transparently transmitted to the first DSAP entity corresponding to the first LCID in the DSAP layer, so that the first DSAP entity can perform subsequent processing on the first DSAP sub PDU. Or, after receiving the first DSAP sub PDU sent by the MAC layer, the first DSAP entity processes it according to the configuration of the DSAP layer, unpacks the first DSAP sub PDU to obtain the first data plane data, and delivers the first data plane data to its service target.

[0408] In some embodiments, the first DSAP entity is the DSAP entity in the DSAP layer corresponding to the service identifier of the first data plane data.

[0409] In some embodiments, the MAC layer is configured with at least one LCID dedicated to data plane data, and the at least one LCID includes the first LCID.

[0410] In some embodiments, the at least one LCID is multiple LCIDs corresponding to multiple types, and the multiple types include at least one of the following: at least one service type, at least one end-to-end type.

[0411] In some embodiments, the S320 includes:

[0412] The second device receives the first DSAP sub PDU from the MAC layer through the first DSAP entity and at least one of the following:

[0413] Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer;

[0414] Wherein, the PDCP layer is configured not to process data plane data, and the transmission mode of the RLC layer is configured as the transparent mode.

[0415] In some embodiments, the method 300 further includes:

[0416] The second device obtains DSAP configuration information, and the DSAP configuration information is used to configure at least one of the following:

[0417] At least one DSAP entity identifier;

[0418] At least one service identifier;

[0419] At least one LCID;

[0420] The first mapping relationship between the at least one DSAP entity identifier and the at least one service identifier;

[0421] The second mapping relationship between the at least one DSAP entity identifier and the at least one LCID;

[0422] The priority of the DSAP entity;

[0423] The uplink data source;

[0424] The downlink data destination;

[0425] The indication of whether encryption and decryption are performed;

[0426] The security algorithm for encryption;

[0427] The indication of whether integrity protection is performed;

[0428] The security algorithm for integrity protection;

[0429] The indication of whether decryption is performed;

[0430] The transmission mode;

[0431] The first indication information indicating whether segmentation is allowed;

[0432] The packet assembly parameters;

[0433] The segmentation allowance parameters;

[0434] The segmentation allowance multiple;

[0435] The indication of whether delivery is in order;

[0436] The indication of whether compression is performed;

[0437] The compression algorithm;

[0438] The indication of whether retransmission is performed;

[0439] The identifier of the buffer status report BSR group.

[0440] In some embodiments, the transmission mode is any one of the following:

[0441] Transparent mode TM, unacknowledged mode UM, acknowledged mode AM, or unacknowledged mode - enhanced UM - A;

[0442] Wherein, at least one of the UM, the AM, and the UM - A supports segmentation, and at least one of the AM and the UM - A supports non - segmentation.

[0443] In some embodiments, the DSAP configuration information satisfies at least one of the following:

[0444] In the case where the first mapping relationship is not a one-to-one mapping relationship, the DSAP configuration information includes the at least one service identifier and the first mapping relationship;

[0445] In the case where the first indication information indicates that segmentation is not allowed, the DSAP configuration information includes or does not include the packet assembly parameters;

[0446] In the case where the first indication information indicates that segmentation is allowed, the DSAP configuration information includes the segmentation allowance parameter;

[0447] In the case where the DSAP configuration information does not include the first indication information, the DSAP configuration information includes the packet assembly parameters and does not include the segmentation allowance parameter, or the DSAP configuration information does not include the packet assembly parameters and includes the segmentation allowance parameter;

[0448] In the case where the DSAP configuration information includes the segmentation allowance parameter, the DSAP configuration information includes or does not include the segmentation allowance multiple.

[0449] In some embodiments, the S330 includes:

[0450] The second device unpacks the first DSAP sub PDU through the first DSAP entity based on the first indication information in the DSAP configuration information to obtain the first data plane data;

[0451] Wherein, a field for indicating the length of the payload in the first DSAP sub PDU is included in the DSAP sub-header of the first DSAP sub PDU.

[0452] In some embodiments, the S330 includes:

[0453] The second device unpacks the first DSAP sub PDU through the first DSAP entity based on the packet assembly parameters in the DSAP configuration information to obtain the first data plane data.

[0454] In some embodiments, the S330 includes:

[0455] The second device unpacks the first DSAP sub PDU through the first DSAP entity based on the segmentation allowance parameter in the DSAP configuration information to obtain the first data plane data; or

[0456] The second device unpacks the first DSAP sub PDU through the first DSAP entity based on the segmentation allowance parameter and the segmentation allowance multiple in the DSAP configuration information to obtain the first data plane data.

[0457] In some embodiments, the value of the segmentation permission parameter is a unique value; wherein, the first DSAP subPDU satisfies any one of the following:

[0458] The DSAP sub-header of the first DSAP sub PDU includes a field for carrying segmentation information and a field carrying a field for indicating the length of the payload in the first DSAP sub PDU;

[0459] The DSAP sub-header includes a field for carrying segmentation information;

[0460] The DSAP sub-header includes a field for carrying segmentation information and a field carrying a field for indicating the length of the payload in the first DSAP subPDU.

[0461] In some embodiments, the value of the segmentation permission parameter is a list of values; wherein, the first DSAP subPDU satisfies any one of the following:

[0462] The DSAP sub-header of the first DSAP sub PDU includes a field for carrying segmentation information and a field carrying a field for indicating the length of the payload in the first DSAP sub PDU;

[0463] The DSAP sub-header includes a field for carrying segmentation information and a field carrying a field for indicating the length of the payload in the first DSAP subPDU or a value used in the list of values;

[0464] The DSAP sub-header includes a field for carrying segmentation information and a field carrying a field for indicating the length of the payload in the first DSAP sub PDU.

[0465] In some embodiments, when the first DSAP entity unpacks the first DSAP sub PDU based on the segmentation permission parameter, the DSAP sub-header includes a field carrying a field for indicating the length of the payload in the first DSAP sub PDU or a value used in the list of values; or

[0466] When the first DSAP entity unpacks the first DSAP sub PDU based on the segmentation permission parameter and the segmentation permission multiple, the DSAP sub-header includes a field carrying a field for indicating the length of the payload in the first DSAP subPDU.

[0467] In some embodiments, the DSAP sub-header includes or does not include a field carrying a sub-sequence number for indicating the first DSAP sub PDU.

[0468] In some embodiments, when the transmission mode of the DSAP layer is AM or UM-A, a field for indicating whether to perform information feedback is included in the DSAP sub-header of the first DSAP sub PDU.

[0469] In some embodiments, the DSAP sub-header of the first DSAP sub PDU includes at least one of the following:

[0470] A field carrying the identifier of the first DSAP entity;

[0471] A field carrying the service identifier of the first data plane data;

[0472] A field carrying a flag for indicating whether the first DSAP sub PDU is a control packet or a data packet;

[0473] A field carrying the sequence number of the first DSAP sub PDU;

[0474] A field for integrity protection and verification of the first DSAP sub PDU.

[0475] In some embodiments, the method 300 further includes:

[0476] The second device receives a second MAC sub PDU through the MAC layer, the second MAC sub PDU includes a MAC control element CE, and the MAC CE includes a field carrying the identifier of the buffer status report BSR group and a field carrying the buffer size of the BSR group.

[0477] In some embodiments, the method 300 further includes:

[0478] The second device receives a second DSAP sub PDU from the MAC layer through the first DSAP entity;

[0479] The second device unpacks the second DSAP sub PDU to obtain a first buffer status report BSR:

[0480] Wherein, the first BSR is the BSR of the first LCID, the BSR of the first DSAP entity, or the BSR of the service identifier of the first data plane data, and the first DSAP PDU includes the second DSAP sub PDU.

[0481] In some embodiments, the second DSAP sub PDU satisfies any one of the following:

[0482] In the case where the first BSR is the BSR of the first LCID, the second DSAP sub PDU includes a DSAP control element CE, and the DSAP CE includes a field carrying a domain for identifying the second DSAP sub PDU as a DSAP BSR and a field carrying the buffer size of the first LCID;

[0483] In the case where the second DSAP sub PDU includes the DSAP CE, the second DSAP sub PDU is the first DSAP sub PDU or the last DSAP sub PDU in the first DSAP PDU;

[0484] In the case where the first BSR is the BSR of the first DSAP entity, the second DSAP sub PDU includes a field carrying the identifier of the first DSAP entity;

[0485] In the case where the first BSR is the BSR of the service identifier of the first data plane data, the second DSAP sub PDU includes a field carrying the identifier of the first DSAP entity and a field carrying the service identifier of the first data plane data.

[0486] In some embodiments, in the case where the first BSR is the BSR of the first DSAP entity or the BSR of the service identifier of the first data plane data, the second DSAP sub PDU further includes at least one of the following:

[0487] A field carrying a domain for indicating that the second DSAP sub PDU is a control packet or a data packet;

[0488] A field carrying a domain for indicating the type of the second DSAP sub PDU.

[0489] In some embodiments, the S330 includes:

[0490] The second device unpacks the first DSAP sub PDU through the first DSAP entity and at least one of the following to obtain the first data plane data: decryption, data packet recombination, integrity check.

[0491] In some embodiments, the first DSAP PDU includes a third DSAP sub PDU, and the third DSAP sub PDU includes a field carrying the type of the status report and a field carrying the status report, and the type of the status report includes at least one of the following:

[0492] Unacknowledged sequence number;

[0493] Unacknowledged starting sequence number and unacknowledged ending sequence number;

[0494] Unacknowledged sequence number and unacknowledged sub-sequence number in the unacknowledged sequence number;

[0495] Unacknowledged first sequence number, unacknowledged starting sub-sequence number in the first sequence number, unacknowledged second sequence number, and unacknowledged ending sub-sequence number in the second sequence number.

[0496] In some embodiments, the third DSAP sub PDU further includes at least one of the following:

[0497] A field carrying the identifier of the first DSAP entity;

[0498] A field carrying the service identifier of the first data plane data;

[0499] A field carrying a field for indicating whether the third DSAP sub PDU is a control packet or a data packet;

[0500] A field carrying a field for indicating the type of the third DSAP sub PDU;

[0501] A field carrying the length of the field carrying the status report;

[0502] A field carrying the acknowledgement information;

[0503] A field carrying a field for indicating the type of the status report and a field for indicating the content corresponding to the type of the status report.

[0504] It should be understood that the descriptions of the related terms and solutions of the method 300 can refer to the descriptions in the method 200 and the above various embodiments. To avoid repetition, they will not be elaborated here.

[0505] For the data processing method provided by the embodiments of the present application, the execution subject may be a data processing device. In the embodiments of the present application, taking the data processing device executing the data processing method as an example, the data processing device provided by the embodiments of the present application is described.

[0506] Figure 21 A schematic block diagram of a data processing device 410 according to an embodiment of the present application is shown.

[0507] As Figure 21 shown, the data processing device 410 includes:

[0508] A processing unit 411, configured to packetize first data plane data through a first DSAP entity in a data service adaptation protocol (DSAP) layer to obtain a first data service adaptation protocol sub-protocol data unit (DSAP sub PDU);

[0509] A communication unit 412, configured to receive a first DSAP PDU from the DSAP layer through a Media Access Control (MAC) layer, where the first DSAP PDU includes the first DSAP sub PDU;

[0510] The processing unit 411 is further configured to: packetize the first DSAP PDU through the MAC layer to obtain a first MAC sub PDU, where the first MAC sub PDU includes a first Logical Channel ID (LCID) corresponding to the first DSAP entity.

[0511] In some embodiments, the first DSAP entity is a DSAP entity in the DSAP layer corresponding to a service ID of the first data plane data.

[0512] In some embodiments, the MAC layer is configured with at least one LCID dedicated to data plane data, and the at least one LCID includes the first LCID.

[0513] In some embodiments, the at least one LCID is multiple LCIDs corresponding to multiple types, and the multiple types include at least one of the following: at least one service type, at least one end-to-end type.

[0514] In some embodiments, the communication unit 412 is specifically configured to:

[0515] receive the first DSAP PDU from the DSAP layer through the MAC layer and at least one of the following:

[0516] Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer;

[0517] Wherein, the PDCP layer is configured not to process data plane data, and the transmission mode of the RLC layer is configured as a transparent mode.

[0518] In some embodiments, the communication unit 412 is further configured to:

[0519] obtain DSAP configuration information, where the DSAP configuration information is used to configure at least one of the following:

[0520] at least one DSAP entity identifier;

[0521] at least one service identifier;

[0522] at least one LCID;

[0523] a first mapping relationship between the at least one DSAP entity identifier and the at least one service identifier;

[0524] The second mapping relationship between the at least one DSAP entity identifier and the at least one LCID;

[0525] The priority of the DSAP entity;

[0526] The uplink data source;

[0527] The downlink data destination;

[0528] The indication of whether encryption and decryption are performed;

[0529] The security algorithm for encryption;

[0530] The indication of whether integrity protection is performed;

[0531] The security algorithm for integrity protection;

[0532] The indication of whether decryption is performed;

[0533] The transmission mode;

[0534] The first indication information indicating whether segmentation is allowed;

[0535] The packetization parameters;

[0536] The segmentation allowance parameters;

[0537] The segmentation allowance multiple;

[0538] The indication of whether in-sequence delivery is performed;

[0539] The indication of whether compression is performed;

[0540] The compression algorithm;

[0541] The indication of whether retransmission is performed;

[0542] The identifier of the buffer status report BSR group.

[0543] In some embodiments, the transmission mode is any one of the following:

[0544] Transparent mode TM, unacknowledged mode UM, acknowledged mode AM, or unacknowledged mode - enhanced UM-A;

[0545] Wherein, at least one of the UM, the AM, and the UM-A supports segmentation, and at least one of the AM and the UM-A supports non-segmentation.

[0546] In some embodiments, the DSAP configuration information satisfies at least one of the following:

[0547] In the case where the first mapping relationship is not a one-to-one mapping relationship, the DSAP configuration information includes the at least one service identifier and the first mapping relationship;

[0548] When the first indication information indicates that segmentation is not allowed, the DSAP configuration information includes or does not include the packet assembly parameters;

[0549] When the first indication information indicates that segmentation is allowed, the DSAP configuration information includes the segmentation allowed parameter;

[0550] When the DSAP configuration information does not include the first indication information, the DSAP configuration information includes the packet assembly parameters and does not include the segmentation allowed parameter, or the DSAP configuration information does not include the packet assembly parameters and includes the segmentation allowed parameter;

[0551] When the DSAP configuration information includes the segmentation allowed parameter, the DSAP configuration information includes or does not include the segmentation allowed multiple.

[0552] In some embodiments, the processing unit 411 is specifically configured to:

[0553] Through the first DSAP entity, based on the first indication information in the DSAP configuration information, perform non-segmented packet assembly or packet assembly after segmentation on the first data plane data to obtain the first DSAP sub PDU;

[0554] Wherein, a field for indicating the length of the payload in the first DSAP sub PDU is included in the DSAP sub-header of the first DSAP sub PDU.

[0555] In some embodiments, the processing unit 411 is specifically configured to:

[0556] Through the first DSAP entity, perform non-segmented packet assembly on the first data plane data based on the packet assembly parameters in the DSAP configuration information to obtain the first DSAP sub PDU.

[0557] In some embodiments, the processing unit 411 is specifically configured to:

[0558] Through the first DSAP entity, perform non-segmented packet assembly or packet assembly after segmentation on the first data plane data based on the segmentation allowed parameter in the DSAP configuration information to obtain the first DSAP sub PDU; or

[0559] Through the first DSAP entity, perform non-segmented packet assembly or packet assembly after segmentation on the first data plane data based on the segmentation allowed parameter and the segmentation allowed multiple in the DSAP configuration information to obtain the first DSAP sub PDU.

[0560] In some embodiments, the value of the segmentation permission parameter is a unique value; wherein, the first DSAP subPDU satisfies any one of the following:

[0561] In the case where the first device performs non-segmented packet assembly on the first data plane data, the DSAP sub-header of the first DSAP sub PDU includes a field for carrying segmentation information and a field carrying a length indicating the payload in the first DSAP sub PDU;

[0562] In the case where the first device performs segmented packet assembly on the first data plane data and the payload in the first DSAP subPDU is a data packet other than the last data packet, the DSAP sub-header includes a field for carrying segmentation information;

[0563] In the case where the first device performs segmented packet assembly on the first data plane data and the payload in the first DSAP subPDU is the last data packet, the DSAP sub-header includes a field for carrying segmentation information and a field carrying a length indicating the payload in the first DSAP sub PDU.

[0564] In some embodiments, the value of the segmentation permission parameter is a value list; wherein, the first DSAP subPDU satisfies any one of the following:

[0565] In the case where the first device performs non-segmented packet assembly on the first data plane data, the DSAP sub-header of the first DSAP sub PDU includes a field for carrying segmentation information and a field carrying a length indicating the payload in the first DSAP sub PDU;

[0566] In the case where the first device performs segmented packet assembly on the first data plane data and the payload in the first DSAP subPDU is a data packet other than the last data packet, the DSAP sub-header includes a field for carrying segmentation information and a field carrying a length indicating the payload in the first DSAP sub PDU or a value used in the value list;

[0567] In the case where the first device performs segmented packet assembly on the first data plane data and the payload in the first DSAP subPDU is the last data packet, the DSAP sub-header includes a field for carrying segmentation information and a field carrying a length indicating the payload in the first DSAP sub PDU.

[0568] In some embodiments, when the first DSAP entity performs packet assembly for segmenting the first data plane data based on the segmentation permission parameter, and the payload in the first DSAP sub PDU is a data packet other than the last data packet, the DSAP sub-header includes a field carrying a value for indicating the length of the payload in the first DSAP sub PDU or a value used in the value list; or

[0569] When the first DSAP entity performs packet assembly for segmenting the first data plane data based on the segmentation permission parameter and the segmentation permission multiple, and the payload in the first DSAP sub PDU is a data packet other than the last data packet, the DSAP sub-header includes a field carrying a value for indicating the length of the payload in the first DSAP sub PDU.

[0570] In some embodiments, when performing packet assembly for segmenting the first data plane data, and the payload in the first DSAP sub PDU is a data packet other than the last data packet and the first data packet, the DSAP sub-header includes a field carrying a value for indicating the sub-sequence number of the first DSAP sub PDU; or

[0571] When performing packet assembly for segmenting the first data plane data, and the payload in the first DSAP sub PDU is the first data packet or the last data packet, the DSAP sub-header may or may not include a field carrying a value for indicating the sub-sequence number of the first DSAP sub PDU.

[0572] In some embodiments, when the transmission mode of the DSAP layer is AM or UM-A, the DSAP sub-header of the first DSAP sub PDU includes a field carrying a value for indicating whether information feedback is performed.

[0573] In some embodiments, the DSAP sub-header of the first DSAP sub PDU includes at least one of the following:[[]]

[0574] A field carrying the identifier of the first DSAP entity;

[0575] A field carrying the service identifier of the first data plane data;

[0576] A field carrying a value for indicating that the first DSAP sub PDU is a control packet or a data packet;

[0577] A field carrying a value for indicating the sequence number of the first DSAP sub PDU;

[0578] Carries a field for integrity protection and verification of the first DSAP sub PDU.

[0579] In some embodiments, the processing unit 411 is specifically configured to:

[0580] Receive packet assembly indication information from the MAC layer through the DSAP layer;

[0581] Within the size indicated by the packet assembly indication information, packetize the first data plane data through the first DSAP entity to obtain the first DSAP sub PDU.

[0582] In some embodiments, the communication unit 412 is further configured to:

[0583] In the case where the first DSAP entity cannot complete packetizing the data plane data to be sent within the size indicated by the packet assembly indication information, send a buffer size report BSR indication to the MAC layer through the DSAP layer, where the BSR indication includes the identifier of the BSR group and the buffer size of the BSR group;

[0584] The processing unit 411 is further configured to: Through the MAC layer, perform packetization based on the BSR indication to obtain a second MAC sub PDU, where the second MAC sub PDU includes a MAC control element CE, and the MAC CE includes a field carrying the identifier of the buffer status report BSR group and a field carrying the buffer size of the BSR group.

[0585] In some embodiments, the processing unit 411 is further configured to:

[0586] In the case where the first DSAP entity cannot complete packetizing the first data plane data within the size indicated by the packet assembly indication information, packetize a first buffer size report BSR through the first DSAP entity to obtain a second DSAP sub PDU:

[0587] Wherein, the first BSR is the BSR of the first LCID, the BSR of the first DSAP entity, or the BSR of the service identifier of the first data plane data, and the first DSAP PDU includes the second DSAP sub PDU.

[0588] In some embodiments, the second DSAP sub PDU satisfies any one of the following:

[0589] When the first BSR is the BSR for the first LCID, the second DSAP sub PDU includes a DSAP control element CE, and the DSAP CE includes a field carrying a domain for identifying the second DSAP sub PDU as a DSAP BSR and a field carrying the buffer size of the first LCID;

[0590] When the second DSAP sub PDU includes the DSAP CE, the second DSAP sub PDU is the first DSAP sub PDU or the last DSAP sub PDU in the first DSAP PDU;

[0591] When the first BSR is the BSR for the first DSAP entity, the second DSAP sub PDU includes a field carrying the identifier of the first DSAP entity;

[0592] When the first BSR is the BSR for the service identifier of the first data plane data, the second DSAP sub PDU includes a field carrying the identifier of the first DSAP entity and a field carrying the service identifier of the first data plane data.

[0593] In some embodiments, when the first BSR is the BSR for the first DSAP entity or the BSR for the service identifier of the first data plane data, the second DSAP sub PDU further includes at least one of the following:

[0594] A field carrying a domain for indicating that the second DSAP sub PDU is a control packet or a data packet;

[0595] A field carrying a domain for indicating the type of the second DSAP sub PDU.

[0596] In some embodiments, the processing unit 411 is specifically configured to:

[0597] Packetize the first data plane data through the first DSAP entity and at least one of the following to obtain the first DSAP sub PDU: desensitization, encryption, notifying the MAC layer of the data volume to be sent in the DSAP layer, and integrity protection.

[0598] In some embodiments, the first DSAP PDU includes a third DSAP sub PDU, and the third DSAP sub PDU includes a field carrying the type of the status report and a field carrying the status report, and the type of the status report includes at least one of the following:

[0599] Unacknowledged sequence number;

[0600] Unacknowledged start sequence number and unacknowledged end sequence number;

[0601] Unacknowledged sequence number and unacknowledged sub-sequence number in the unacknowledged sequence number;

[0602] Unacknowledged first sequence number, unacknowledged start sub-sequence number in the first sequence number, unacknowledged second sequence number, unacknowledged end sub-sequence number in the second sequence number.

[0603] In some embodiments, the third DSAP sub PDU further includes at least one of the following:

[0604] A field carrying the identifier of the first DSAP entity;

[0605] A field carrying the service identifier of the first data plane data;

[0606] A field carrying a domain for indicating whether the third DSAP sub PDU is a control packet or a data packet;

[0607] A field carrying a domain for indicating the type of the third DSAP sub PDU;

[0608] A field carrying the length of the field carrying the status report;

[0609] A field carrying acknowledgment information;

[0610] A field carrying a domain for indicating the type of the status report and a domain for indicating the content corresponding to the type of the status report.

[0611] It should be understood that the data processing device 410 provided in the embodiments of the present application may correspond to the first device in the method embodiments of the present application, and the above (or other) operations or functions of each unit in the data processing device 410 are respectively for implementing Figure 4 the corresponding processes executed by the first device in the illustrated method embodiments. For the sake of avoiding repetition, details are not described herein again.

[0612] Figure 22 A schematic block diagram of a data processing device 420 according to an embodiment of the present application is shown.

[0613] As Figure 22 shown, the data processing device 420 includes:

[0614] A processing unit 421 is configured to unpack a first Media Access Control sub - Protocol Data Unit (MAC sub PDU) through a Media Access Control (MAC) layer to obtain a first Data Service Adaptation Protocol Protocol Data Unit (DSAP PDU), where the first DSAP PDU includes the first DSAP sub PDU, and the first MAC sub PDU includes a first Logical Channel ID (LCID).

[0615] A communication unit 422 is configured to receive the first DSAP sub PDU from the MAC layer through a first DSAP entity corresponding to the first LCID in the DSAP layer.

[0616] The processing unit 421 is further configured to: unpack the first DSAP sub PDU through the first DSAP entity to obtain first data plane data.

[0617] In some embodiments, the first DSAP entity is a DSAP entity in the DSAP layer corresponding to the service ID of the first data plane data.

[0618] In some embodiments, the MAC layer is configured with at least one LCID dedicated to data plane data, and the at least one LCID includes the first LCID.

[0619] In some embodiments, the at least one LCID is multiple LCIDs corresponding to multiple types, and the multiple types include at least one of the following: at least one service type, at least one end - to - end type.

[0620] In some embodiments, the communication unit 422 is specifically configured to:

[0621] receive the first DSAP sub PDU from the MAC layer through the first DSAP entity and at least one of the following:

[0622] Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer;

[0623] wherein, the PDCP layer is configured not to process data plane data, and the transmission mode of the RLC layer is configured as the transparent mode.

[0624] In some embodiments, the communication unit 422 is further configured to:

[0625] The second device obtains DSAP configuration information, and the DSAP configuration information is used to configure at least one of the following:

[0626] at least one DSAP entity identifier;

[0627] at least one service identifier;

[0628] At least one LCID;

[0629] The first mapping relationship between the at least one DSAP entity identifier and the at least one service identifier;

[0630] The second mapping relationship between the at least one DSAP entity identifier and the at least one LCID;

[0631] The priority of the DSAP entity;

[0632] The uplink data source;

[0633] The downlink data destination;

[0634] An indication of whether encryption and decryption are performed;

[0635] The security algorithm for encryption;

[0636] An indication of whether integrity protection is performed;

[0637] The security algorithm for integrity protection;

[0638] An indication of whether decryption is performed;

[0639] The transmission mode;

[0640] The first indication information indicating whether segmentation is allowed;

[0641] The packet assembly parameters;

[0642] The segmentation allowance parameter;

[0643] The segmentation allowance multiple;

[0644] An indication of whether in-sequence delivery is performed;

[0645] An indication of whether compression is performed;

[0646] The compression algorithm;

[0647] An indication of whether retransmission is performed;

[0648] The identifier of the buffer status report BSR group.

[0649] In some embodiments, the transmission mode is any one of the following:

[0650] Transparent mode TM, unacknowledged mode UM, acknowledged mode AM, or unacknowledged mode - enhanced UM-A;

[0651] Wherein, at least one of the UM, the AM, and the UM-A supports segmentation, and at least one of the AM and the UM-A supports non-segmentation.

[0652] In some embodiments, the DSAP configuration information satisfies at least one of the following:

[0653] In the case where the first mapping relationship is not a one-to-one mapping relationship, the DSAP configuration information includes the at least one service identifier and the first mapping relationship;

[0654] In the case where the first indication information indicates that segmentation is not allowed, the DSAP configuration information includes or does not include the packet assembly parameters;

[0655] In the case where the first indication information indicates that segmentation is allowed, the DSAP configuration information includes the segmentation allowance parameter;

[0656] In the case where the DSAP configuration information does not include the first indication information, the DSAP configuration information includes the packet assembly parameters and does not include the segmentation allowance parameter, or the DSAP configuration information does not include the packet assembly parameters and includes the segmentation allowance parameter;

[0657] In the case where the DSAP configuration information includes the segmentation allowance parameter, the DSAP configuration information includes or does not include the segmentation allowance multiple.

[0658] In some embodiments, the processing unit 421 is specifically configured to:

[0659] Through the first DSAP entity, based on the first indication information in the DSAP configuration information, unpack the first DSAP sub PDU to obtain the first data plane data;

[0660] Wherein, a field for indicating the length of the payload in the first DSAP sub PDU is included in the DSAP sub-header of the first DSAP sub PDU.

[0661] In some embodiments, the processing unit 421 is specifically configured to:

[0662] Through the first DSAP entity, based on the packet assembly parameters in the DSAP configuration information, unpack the first DSAP sub PDU to obtain the first data plane data.

[0663] In some embodiments, the processing unit 421 is specifically configured to:

[0664] Through the first DSAP entity, based on the segmentation allowance parameter in the DSAP configuration information, unpack the first DSAP sub PDU to obtain the first data plane data; or

[0665] Through the first DSAP entity, the first DSAP sub PDU is unpacked based on the segmentation permission parameter and the segmentation permission multiple in the DSAP configuration information to obtain the first data plane data.

[0666] In some embodiments, the value of the segmentation permission parameter is a unique value; wherein, the first DSAP sub PDU satisfies any one of the following:

[0667] The DSAP sub-header of the first DSAP sub PDU includes a field for carrying segmentation information and a field for carrying the length of the payload in the first DSAP sub PDU;

[0668] The DSAP sub-header includes a field for carrying segmentation information;

[0669] The DSAP sub-header includes a field for carrying segmentation information and a field for carrying the length of the payload in the first DSAP sub PDU.

[0670] In some embodiments, the value of the segmentation permission parameter is a value list; wherein, the first DSAP sub PDU satisfies any one of the following:

[0671] The DSAP sub-header of the first DSAP sub PDU includes a field for carrying segmentation information and a field for carrying the length of the payload in the first DSAP sub PDU;

[0672] The DSAP sub-header includes a field for carrying segmentation information and a field for carrying the length of the payload in the first DSAP sub PDU or the value used in the value list;

[0673] The DSAP sub-header includes a field for carrying segmentation information and a field for carrying the length of the payload in the first DSAP sub PDU.

[0674] In some embodiments, when the first DSAP entity unpacks the first DSAP sub PDU based on the segmentation permission parameter, the DSAP sub-header includes a field for carrying the length of the payload in the first DSAP sub PDU or the value used in the value list; or

[0675] When the first DSAP entity unpacks the first DSAP sub PDU based on the segmentation permission parameter and the segmentation permission multiple, the DSAP sub-header includes a field for carrying the length of the payload in the first DSAP sub PDU.

[0676] In some embodiments, the DSAP sub - header includes or does not include a field carrying a sub - sequence number for indicating the first DSAP sub PDU.

[0677] In some embodiments, when the transmission mode of the DSAP layer is AM or UM - A, the DSAP sub - header of the first DSAP sub PDU includes a field carrying an indication of whether information feedback is performed.

[0678] In some embodiments, the DSAP sub - header of the first DSAP sub PDU includes at least one of the following:

[0679] A field carrying the identifier of the first DSAP entity;

[0680] A field carrying the service identifier of the first data plane data;

[0681] A field carrying an indication of whether the first DSAP sub PDU is a control packet or a data packet;

[0682] A field carrying the sequence number of the first DSAP sub PDU;

[0683] A field carrying integrity protection and verification for the first DSAP sub PDU.

[0684] In some embodiments, the communication unit 421 is further configured to:

[0685] Receive a second MAC sub PDU through the MAC layer, where the second MAC sub PDU includes a MAC control element CE, and the MAC CE includes a field carrying the identifier of a buffer status report BSR group and a field carrying the buffer size of the BSR group.

[0686] In some embodiments, the communication unit 421 is further configured to:

[0687] Receive a second DSAP sub PDU from the MAC layer through the first DSAP entity;

[0688] The processing unit 421 is further configured to: obtain a first buffer size report BSR by unpacking the second DSAP sub PDU:

[0689] Wherein, the first BSR is the BSR of the first LCID, the BSR of the first DSAP entity, or the BSR of the service identifier of the first data plane data, and the first DSAP PDU includes the second DSAP sub PDU.

[0690] In some embodiments, the second DSAP sub PDU satisfies any one of the following:

[0691] When the first BSR is the BSR of the first LCID, the second DSAP sub PDU includes a DSAP control element CE, and the DSAP CE includes a field carrying a domain for identifying the second DSAP sub PDU as a DSAP BSR and a field carrying the buffer size of the first LCID;

[0692] When the second DSAP sub PDU includes the DSAP CE, the second DSAP sub PDU is the first DSAP sub PDU or the last DSAP sub PDU in the first DSAP PDU;

[0693] When the first BSR is the BSR of the first DSAP entity, the second DSAP sub PDU includes a field carrying the identifier of the first DSAP entity;

[0694] When the first BSR is the BSR of the service identifier of the first data plane data, the second DSAP sub PDU includes a field carrying the identifier of the first DSAP entity and a field carrying the service identifier of the first data plane data.

[0695] In some embodiments, when the first BSR is the BSR of the first DSAP entity or the BSR of the service identifier of the first data plane data, the second DSAP sub PDU further includes at least one of the following:

[0696] A field carrying a domain for indicating that the second DSAP sub PDU is a control packet or a data packet;

[0697] A field carrying a domain for indicating the type of the second DSAP sub PDU.

[0698] In some embodiments, the processing unit 421 is specifically configured to:

[0699] Unpack the first DSAP sub PDU through the first DSAP entity and at least one of the following to obtain the first data plane data: decryption, data packet recombination, integrity check.

[0700] In some embodiments, the first DSAP PDU includes a third DSAP sub PDU, and the third DSAP sub PDU includes a field carrying the type of the status report and a field carrying the status report, and the type of the status report includes at least one of the following:

[0701] Unacknowledged serial number

[0702] Unacknowledged starting serial number and unacknowledged ending serial number

[0703] Unacknowledged serial number and unacknowledged sub - serial number in the unacknowledged serial number

[0704] Unacknowledged first serial number, unacknowledged starting sub - serial number in the first serial number, unacknowledged second serial number, unacknowledged ending sub - serial number in the second serial number

[0705] In some embodiments, the third DSAP sub PDU further includes at least one of the following:

[0706] Field carrying the identifier of the first DSAP entity

[0707] Field carrying the service identifier of the first data plane data

[0708] Field carrying a field for indicating whether the third DSAP sub PDU is a control packet or a data packet

[0709] Field carrying a field for indicating the type of the third DSAP sub PDU

[0710] Field carrying the length of the field carrying the status report

[0711] Field carrying acknowledgment information

[0712] Field carrying a field for indicating the type of the status report and a field for indicating the content corresponding to the type of the status report

[0713] It should be understood that the data processing device 420 provided in the embodiments of the present application may correspond to the second device in the method embodiments of the present application, and the above (or other) operations or functions of each unit in the data processing device 420 are respectively for implementing Figure 20 the corresponding processes of the second device in the method embodiments shown. To avoid repetition, details are not described herein again.

[0714] The data processing device in the embodiments of the present application may be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or a chip. The electronic device may be a first device or a second device, or other devices other than terminals. The first device may be a terminal or a network-side device, and the second device may be a network-side device or a terminal. Exemplarily, the terminal may include, but is not limited to, the types of the above-listed terminal 11, and the network-side device may include, but is not limited to, the types of the above-listed network-side device 12. The other devices may be servers, Network Attached Storage (NAS), etc., and the embodiments of the present application do not make specific limitations.

[0715] The data processing device provided in the embodiments of the present application can implement Figure 4 or Figure 20 each process involved in the method embodiments shown, and achieve the same technical effects. To avoid repetition, it will not be elaborated here.

[0716] Figure 23 is an example of the communication device 500 provided in the embodiments of the present application.

[0717] As Figure 23 shown, the communication device 500 includes a processor 501 and a memory 502. A program or instruction that can run on the processor 501 is stored on the memory 502. When the program or instruction is executed by the processor 501, each step of the above data processing method embodiment is implemented. For example, when the communication device 500 is a first device, when the program or instruction is executed by the processor 501, each step executed by the first device in the above data processing method embodiment is implemented, and the same technical effects can be achieved. When the communication device 500 is a second device, when the program or instruction is executed by the processor 501, each step executed by the second device in the above data processing method embodiment is implemented, and the same technical effects can be achieved. To avoid repetition, it will not be elaborated here.

[0718] The embodiments of the present application further provide a first device, including a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run a program or instruction to implement the steps in the method embodiment as Figure 4 shown. The embodiment of the first device corresponds to the method embodiment of the first device. Each implementation process and implementation manner of the above method embodiment can be applied to the embodiment of the first device, and the same technical effects can be achieved.

[0719] The embodiments of the present application further provide a second device, including a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run a program or instruction to implement the steps in the method embodiment as Figure 20Steps of the method embodiments shown. Embodiments of the second device correspond to method embodiments of the second device. Each implementation process and implementation manner of the above method embodiments can be applied to embodiments of the second device and can achieve the same technical effects.

[0720] Figure 24 It is a schematic diagram of the hardware structure of a terminal for implementing an embodiment of the present application.

[0721] As Figure 24 shown, the terminal 600 includes, but is not limited to, at least some components such as a radio frequency unit 601, a network module 602, an audio output unit 603, an input unit 604, a sensor 605, a display unit 606, a user input unit 607, an interface unit 606, a memory 609, and a processor 610.

[0722] Those skilled in the art can understand that the terminal 600 may further include a power source (such as a battery) for supplying power to each component. The power source can be logically connected to the processor 610 through a power management system, so as to implement functions such as management of charging, discharging, and power consumption management through the power management system. Figure 24 The terminal structure shown in does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown in the figure, or combine certain components, or have different component arrangements, which will not be elaborated here.

[0723] It should be understood that in embodiments of the present application, the input unit 604 may include a graphics processing unit (GPU) 6041 and a microphone 6042. The graphics processor 6041 processes image data of still pictures or videos obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. The display unit 606 may include a display panel 6061, and the display panel 6061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 607 includes at least one of a touch panel 6071 and other input devices 6072. The touch panel 6071 is also called a touch screen. The touch panel 6071 may include a touch detection device and a touch controller. The other input devices 6072 may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, a joystick, which will not be elaborated here.

[0724] In embodiments of the present application, after the radio frequency unit 601 receives downlink data from a network-side device, it can be transmitted to the processor 610 for processing; in addition, the radio frequency unit 601 can send uplink data to the network-side device. Generally, the radio frequency unit 601 includes, but is not limited to, an antenna, an amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, etc.

[0725] The memory 609 can be used to store software programs or instructions and various data. The memory 609 may mainly include a first storage area for storing programs or instructions and a second storage area for storing data. Among them, the first storage area may store an operating system, application programs or instructions required for at least one function (such as a sound playback function, an image playback function, etc.). In addition, the memory 609 may include volatile memory or non-volatile memory. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), a static random access memory (SRAM), a dynamic random access memory (DRAM), a synchronous dynamic random access memory (SDRAM), a double data rate synchronous dynamic random access memory (DDR SDRAM), an enhanced synchronous dynamic random access memory (ESDRAM), a synchronous link dynamic random access memory (SLDRAM), and a direct rambus random access memory (DRRAM). The memory 609 in the embodiments of the present application includes, but is not limited to, these and any other suitable types of memory.

[0726] The processor 610 may include one or at least two processing units; optionally, the processor 610 integrates an application processor and a modem processor. Among them, the application processor mainly processes operations related to the operating system, user interface, and application programs, etc., and the modem processor mainly processes wireless communication signals, such as a baseband processor. It can be understood that the above modem processor may not be integrated into the processor 610.

[0727] In one implementation, the terminal 600 is a first device. In this case, the processor 610 is configured to packetize the first data plane data through a first DSAP entity in the data service adaptation protocol (DSAP) layer to obtain a first data service adaptation protocol sub-protocol data unit (DSAP sub PDU); the interface unit 608 is configured to receive the first DSAP PDU from the DSAP layer through the media access control (MAC) layer, where the first DSAP PDU includes the first DSAP sub PDU; the processor 610 is further configured to packetize the first DSAP PDU through the MAC layer to obtain a first MAC sub PDU, where the first MAC sub PDU includes a first logical channel identifier (LCID) corresponding to the first DSAP entity.

[0728] In another implementation, the terminal 600 is a second device. In this case, the processor 610 is configured to unpack a first media access control sub-protocol data unit (MAC sub PDU) through the MAC layer to obtain a first data service adaptation protocol protocol data unit (DSAP PDU), where the first DSAP PDU includes the first DSAP sub PDU, and the first MAC sub PDU includes a first LCID; the interface unit 608 is configured to receive the first DSAP sub PDU from the MAC layer through a first DSAP entity corresponding to the first LCID in the DSAP layer; the processor 610 is further configured to unpack the first DSAP sub PDU through the first DSAP entity to obtain first data plane data. For example, the radio frequency unit 601 is configured to receive a physical downlink shared channel (PDSCH) to obtain a MAC PDU, which includes the first MAC sub PDU.

[0729] In this embodiment, the first DSAP entity directly packetizes the first data plane data, and the first MAC sub PDU obtained after packetizing the first DSAP PDU through the MAC layer includes the first LCID corresponding to the first DSAP entity. Thus, direct communication between the DSAP layer and the MAC layer can be enabled, and the end-to-end data delay can be reduced, for example, the transmission delay and the processing delay can be reduced, thereby improving the communication performance.

[0730] It can be understood that the implementation processes of the various implementations mentioned in this embodiment can refer to the relevant descriptions of the method embodiment and achieve the same or corresponding technical effects. To avoid repetition, details are not described herein again.

[0731] Figure 25 This is an example of the network-side device 700 provided by the embodiment of the present application.

[0732] Such asFigure 25 As shown in the figure, the network-side device 700 includes: an antenna 71, a radio frequency device 72, a baseband device 73, a processor 74, and a memory 75. The antenna 71 is connected to the radio frequency device 72. In the uplink direction, the radio frequency device 72 receives information through the antenna 71 and sends the received information to the baseband device 73 for processing. In the downlink direction, the baseband device 73 processes the information to be sent and sends it to the radio frequency device 72. After processing the received information, the radio frequency device 72 sends it out through the antenna 71.

[0733] In the above embodiments, the method executed by the network-side device can be implemented in the baseband device 73, and the baseband device 73 includes a baseband processor.

[0734] The baseband device 73 may include, for example, at least one baseband board, and at least two chips are provided on the baseband board. As Figure 15 shown, one of the chips is, for example, a baseband processor, which is connected to the memory 75 through a bus interface to call the program in the memory 75 and execute the corresponding processes of the network-side device in the above method embodiments.

[0735] The network-side device may further include a network interface 76, and the interface is, for example, a Common Public Radio Interface (CPRI).

[0736] Specifically, the network-side device 700 in the embodiments of the present application further includes: instructions or programs stored on the memory 75 and executable on the processor 74. The processor 74 calls the instructions or programs in the memory 75 to execute Figure 21 the steps executed by each unit in the data processing device shown in FIGS. 17 or 22 and achieves the same technical effects. To avoid repetition, it will not be elaborated here.

[0737] The embodiments of the present application further provide a readable storage medium. Programs or instructions are stored on the readable storage medium. When the programs or instructions are executed by a processor, the various processes of the above data processing method embodiments are implemented, and the same technical effects can be achieved. To avoid repetition, it will not be elaborated here.

[0738] Wherein, the processor is the processor in the terminal described in the above embodiments. The readable storage medium includes a computer-readable storage medium, such as a computer read-only memory ROM, a random access memory RAM, a magnetic disk, or an optical disc, etc. In some examples, the readable storage medium may be a non-transitory readable storage medium.

[0739] An embodiment of the present application further provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is configured to run programs or instructions to implement each process of the above data processing method embodiment and can achieve the same technical effect. To avoid repetition, details are not described herein again.

[0740] It should be understood that the chip mentioned in the embodiment of the present application may also be referred to as a system-on-chip, system chip, chip system, or system-on-chip.

[0741] An embodiment of the present application further provides a computer program / program product, which is stored in a storage medium. The computer program / program product is executed by at least one processor to implement each process of the above data processing method embodiment and can achieve the same technical effect. To avoid repetition, details are not described herein again.

[0742] An embodiment of the present application further provides a communication system, including: a first device and a second device. The first device can be used to execute the steps performed by the first device in the data processing method described above, and the second device can be used to execute the steps performed by the second device in the data processing method described above.

[0743] It should be noted that in this article, the terms "include", "comprise" or any other variant thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements not only includes those elements, but also includes other elements not expressly listed, or further includes elements inherent to such process, method, article or device. Without further limitation, an element defined by the statement "including a..." does not exclude the existence of another identical element in the process, method, article or device including the element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in a reverse order according to the functions involved. For example, the described methods may be performed in an order different from that described, and various steps may be added, omitted or combined. Additionally, the features described with reference to certain examples may be combined in other examples.

[0744] Through the description of the above embodiments, those skilled in the art can clearly understand that the above method-related embodiments can be implemented by means of a computer software product plus a necessary general hardware platform, and of course, can also be implemented by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disc, etc.) and includes several instructions for causing a terminal or a network-side device to execute the methods described in various embodiments of the present application.

[0745] The embodiments of the present application have been described above in conjunction with the accompanying drawings. However, the present application is not limited to the above specific embodiments. The above specific embodiments are merely illustrative and not restrictive. Under the inspiration of the present application, those of ordinary skill in the art can also make many forms of embodiments without departing from the purpose of the present application and the scope protected by the claims. These embodiments are all within the protection scope of the present application.

Claims

1. A data processing method, characterized in that, including: The first device packets the first data plane data through the first DSAP entity in the Data Service Adaptation Protocol DSAP layer to obtain the first Data Service Adaptation Protocol sub - protocol data unit DSAP sub PDU; The first device receives the first DSAP PDU from the DSAP layer through the Media Access Control MAC layer, and the first DSAP PDU includes the first DSAP sub PDU; The first device packets the first DSAP PDU through the MAC layer to obtain the first MAC sub PDU, and the first MAC sub PDU includes the first Logical Channel ID LCID corresponding to the first DSAP entity.

2. The method according to claim 1, characterized in that, The first DSAP entity is the DSAP entity in the DSAP layer corresponding to the service ID of the first data plane data.

3. The method according to claim 1 or 2, characterized in that, The MAC layer is configured with at least one LCID dedicated to data plane data, and the at least one LCID includes the first LCID.

4. The method according to claim 3, characterized in that The at least one LCID is multiple LCIDs corresponding to multiple types, and the multiple types include at least one of the following: at least one service type, at least one end - to - end type.

5. The method according to any one of claims 1 to 4, characterized in that The first device receives the first DSAP PDU from the DSAP layer through the Media Access Control MAC layer, including: The first device receives the first DSAP PDU from the DSAP layer through the MAC layer and at least one of the following: Packet Data Convergence Protocol PDCP layer, Radio Link Control RLC layer; Wherein, the PDCP layer is configured not to process data plane data, and the transmission mode of the RLC layer is configured as the transparent mode.

6. The method according to any one of claims 1 to 5, characterized in that, The method further includes: The first device obtains DSAP configuration information, and the DSAP configuration information is used to configure at least one of the following: At least one DSAP entity identifier; At least one service identifier; At least one LCID; The first mapping relationship between the at least one DSAP entity identifier and the at least one service identifier; The second mapping relationship between the at least one DSAP entity identifier and the at least one LCID; The priority of the DSAP entity; The uplink data source; The downlink data destination; The indication of whether to encrypt or decrypt; The security algorithm for encryption; The indication of whether to perform integrity protection; The security algorithm for integrity protection; The indication of whether to decrypt; The transmission mode; The first indication information indicating whether segmentation is allowed; The packetization parameters; The segmentation allowance parameters; The segmentation allowance multiple; The indication of whether to deliver in order; The indication of whether to compress; The compression algorithm; The indication of whether to perform re - transmission; The identifier of the Buffer Status Report BSR group.

7. The method according to claim 6, characterized in that, The transmission mode is any one of the following: Transparent Mode TM, Unacknowledged Mode UM, Acknowledged Mode AM or Unacknowledged Mode - Enhanced UM - A; Wherein, at least one of the UM, the AM and the UM - A supports segmentation, and at least one of the AM and the UM - A supports non - segmentation.

8. The method according to claim 6 or 7, characterized in that, The DSAP configuration information satisfies at least one of the following: When the first mapping relationship is not a one-to-one mapping relationship, the DSAP configuration information includes the at least one service identifier and the first mapping relationship; When the first indication information indicates that segmentation is not allowed, the DSAP configuration information includes or does not include the packet assembly parameters; When the first indication information indicates that segmentation is allowed, the DSAP configuration information includes the segmentation allowance parameter; When the DSAP configuration information does not include the first indication information, the DSAP configuration information includes the packet assembly parameters and does not include the segmentation allowance parameter, or the DSAP configuration information does not include the packet assembly parameters and includes the segmentation allowance parameter; When the DSAP configuration information includes the segmentation allowance parameter, the DSAP configuration information includes or does not include the segmentation allowance multiple.

9. The method according to any one of claims 1 to 8, characterized in that The first device assembles the first data plane data through a first DSAP entity in the data service adaptation protocol DSAP layer to obtain a first data service adaptation protocol sub-protocol data unit DSAP sub PDU, including: The first device, through the first DSAP entity, assembles the first data plane data without segmentation or after segmentation based on the first indication information in the DSAP configuration information to obtain the first DSAP sub PDU; Among them, a field for indicating the length of the payload in the first DSAP sub PDU is included in the DSAP sub-header of the first DSAP sub PDU.

10. The method according to any one of claims 1 to 8, characterized in that The first device assembles the first data plane data through a first DSAP entity in the data service adaptation protocol DSAP layer to obtain a first data service adaptation protocol sub-protocol data unit DSAP sub PDU, including: The first device, through the first DSAP entity, assembles the first data plane data without segmentation based on the packet assembly parameters in the DSAP configuration information to obtain the first DSAP sub PDU.

11. The method according to any one of claims 1 to 8, characterized in that The first device assembles the first data plane data through a first DSAP entity in the data service adaptation protocol DSAP layer to obtain a first data service adaptation protocol sub-protocol data unit DSAP sub PDU, including: The first device, through the first DSAP entity, assembles the first data plane data without segmentation or after segmentation based on the segmentation allowance parameter in the DSAP configuration information to obtain the first DSAP sub PDU; or The first device, through the first DSAP entity, assembles the first data plane data without segmentation or after segmentation based on the segmentation allowance parameter and the segmentation allowance multiple in the DSAP configuration information to obtain the first DSAP sub PDU.

12. The method according to claim 11, wherein The value of the segmentation allowance parameter is a unique value; among them, the first DSAP sub PDU satisfies any one of the following: When the first device performs non-segmented packet assembly on the first data plane data, the DSAP sub-header of the first DSAP sub PDU includes a field for carrying segmentation information and a field carrying a value for indicating the length of the payload in the first DSAP sub PDU; When the first device performs segmented packet assembly on the first data plane data and the payload in the first DSAP sub PDU is a data packet other than the last data packet, the DSAP sub-header includes a field for carrying segmentation information; When the first device performs segmented packet assembly on the first data plane data and the payload in the first DSAP sub PDU is the last data packet, the DSAP sub-header includes a field for carrying segmentation information and a field carrying a value for indicating the length of the payload in the first DSAP sub PDU.

13. The method according to claim 11, characterized in that The value of the segmentation permission parameter is a value list; wherein, the first DSAP sub PDU satisfies any one of the following: When the first device performs non-segmented packet assembly on the first data plane data, the DSAP sub-header of the first DSAP sub PDU includes a field for carrying segmentation information and a field carrying a value for indicating the length of the payload in the first DSAP sub PDU; When the first device performs segmented packet assembly on the first data plane data and the payload in the first DSAP sub PDU is a data packet other than the last data packet, the DSAP sub-header includes a field for carrying segmentation information and a field carrying a value for indicating the length of the payload in the first DSAP sub PDU or a value used in the value list; When the first device performs segmented packet assembly on the first data plane data and the payload in the first DSAP sub PDU is the last data packet, the DSAP sub-header includes a field for carrying segmentation information and a field carrying a value for indicating the length of the payload in the first DSAP sub PDU.

14. The method according to claim 13, wherein When the first DSAP entity performs segmented packet assembly on the first data plane data based on the segmentation permission parameter and the payload in the first DSAP sub PDU is a data packet other than the last data packet, the DSAP sub-header includes a field carrying a value for indicating the length of the payload in the first DSAP sub PDU or a value used in the value list; Or When the first DSAP entity performs segmented packet assembly on the first data plane data based on the segmentation permission parameter and the segmentation permission multiple, and the payload in the first DSAP sub PDU is a data packet other than the last data packet, the DSAP sub-header includes a field carrying a value for indicating the length of the payload in the first DSAP sub PDU.

15. The method according to any one of claims 12 to 14, characterized in that When segmenting and packetizing the first data plane data and the payload in the first DSAP sub PDU is a data packet other than the last and the first data packets, a field carrying a sub-sequence number for indicating the first DSAP sub PDU is included in the DSAP sub-header; Or When segmenting and packetizing the first data plane data and the payload in the first DSAP sub PDU is the first or the last data packet, a field carrying a sub-sequence number for indicating the first DSAP sub PDU may or may not be included in the DSAP sub-header.

16. The method according to any one of claims 9 to 15, characterized in that, When the transmission mode of the DSAP layer is AM or UM-A, a field carrying an indication of whether information feedback is to be performed is included in the DSAP sub-header of the first DSAP sub PDU.

17. The method according to any one of claims 9 to 16, characterized in that, The DSAP sub-header of the first DSAP sub PDU includes at least one of the following: A field carrying the identifier of the first DSAP entity; A field carrying the service identifier of the first data plane data; A field carrying an indication of whether the first DSAP sub PDU is a control packet or a data packet; A field carrying the sequence number of the first DSAP sub PDU; A field for integrity protection and verification of the first DSAP sub PDU.

18. The method according to any one of claims 1 to 17, characterized in that, The first device packetizes the first data plane data through a first DSAP entity in a data service adaptation protocol DSAP layer to obtain a first data service adaptation protocol sub-protocol data unit DSAP sub PDU, including: The first device receives packetization indication information from the MAC layer through the DSAP layer; Within the size indicated by the packetization indication information, the first device packetizes the first data plane data through the first DSAP entity to obtain the first DSAP sub PDU.

19. The method according to claim 18, wherein The method further includes: When the first DSAP entity fails to complete packetization of the data plane data to be sent within the size indicated by the packetization indication information, the first device sends a buffer size report BSR indication to the MAC layer through the DSAP layer, and the BSR indication includes the identifier of the BSR group and the buffer size of the BSR group; The first device packetizes based on the BSR indication through the MAC layer to obtain a second MAC sub PDU, and the second MAC sub PDU includes a MAC control element CE, and the MAC CE includes a field carrying the identifier of the buffer status report BSR group and a field carrying the buffer size of the BSR group.

20. The method according to claim 18, characterized in that The method further includes: When the first DSAP entity fails to complete packetization of the first data plane data within the size indicated by the packetization indication information, the first device packetizes a first buffer size report BSR through the first DSAP entity to obtain a second DSAP sub PDU: Wherein, the first BSR is the BSR of the first LCID, the BSR of the first DSAP entity, or the BSR of the service identifier of the first data plane data, and the first DSAP PDU includes the second DSAP sub PDU.

21. The method according to claim 20, wherein The second DSAP sub PDU satisfies any one of the following: When the first BSR is the BSR of the first LCID, the second DSAP sub PDU includes a DSAP control element CE, and the DSAP CE includes a field carrying a domain for identifying the second DSAP sub PDU as a DSAP BSR and a field carrying the buffer size of the first LCID; When the second DSAP sub PDU includes the DSAP CE, the second DSAP sub PDU is the first DSAP sub PDU or the last DSAP sub PDU in the first DSAP PDU; When the first BSR is the BSR of the first DSAP entity, the second DSAP sub PDU includes a field carrying the identifier of the first DSAP entity; When the first BSR is the BSR of the service identifier of the first data plane data, the second DSAP sub PDU includes a field carrying the identifier of the first DSAP entity and a field carrying the service identifier of the first data plane data.

22. The method according to claim 20 or 21, characterized in that, When the first BSR is the BSR of the first DSAP entity or the BSR of the service identifier of the first data plane data, the second DSAP sub PDU further includes at least one of the following: A field carrying a domain for indicating that the second DSAP sub PDU is a control packet or a data packet; A field carrying a domain for indicating the type of the second DSAP sub PDU.

23. The method according to any one of claims 1 to 22, characterized in that, The first device packetizes the first data plane data through a first DSAP entity in a data service adaptation protocol DSAP layer to obtain a first data service adaptation protocol sub-protocol data unit DSAP sub PDU, including: The first device packetizes the first data plane data through the first DSAP entity and at least one of the following to obtain the first DSAP sub PDU: desensitization, encryption, notifying the MAC layer of the data volume to be sent existing in the DSAP layer, and integrity protection.

24. The method according to any one of claims 1 to 23, characterized in that, The first DSAP PDU includes a third DSAP sub PDU, and the third DSAP sub PDU includes a field carrying the type of the status report and a field carrying the status report. The type of the status report includes at least one of the following: An unacknowledged sequence number; An unacknowledged start sequence number and an unacknowledged end sequence number; An unacknowledged sequence number and an unacknowledged sub-sequence number in the unacknowledged sequence number; An unacknowledged first sequence number, an unacknowledged start sub-sequence number in the first sequence number, an unacknowledged second sequence number, and an unacknowledged end sub-sequence number in the second sequence number.

25. The method according to claim 24, wherein The third DSAP sub PDU further includes at least one of the following: A field carrying the identifier of the first DSAP entity; A field carrying the service identifier of the first data plane data; A field carrying a field for indicating whether the third DSAP sub PDU is a control packet or a data packet; A field carrying a field for indicating the type of the third DSAP sub PDU; A field carrying the length of the field carrying the status report; A field carrying the acknowledgement information; A field carrying a field for indicating the type of the status report and a field for indicating the content corresponding to the type of the status report.

26. A data processing method, characterized in that, Including: The second device unpacks the first media access control sub-protocol data unit (MAC sub PDU) through the media access control (MAC) layer to obtain the first data service adaptation protocol protocol data unit (DSAP PDU). The first DSAP PDU includes the first DSAP sub PDU, and the first MAC sub PDU includes the first logical channel identifier (LCID); The second device receives the first DSAP sub PDU from the MAC layer through the first DSAP entity corresponding to the first LCID in the DSAP layer; The second device unpacks the first DSAP sub PDU through the first DSAP entity to obtain the first data plane data.

27. The method according to claim 26, wherein The first DSAP entity is the DSAP entity corresponding to the service identifier of the first data plane data in the DSAP layer.

28. The method according to claim 26 or 27, characterized in that The MAC layer is configured with at least one LCID dedicated to data plane data, and the at least one LCID includes the first LCID.

29. The method according to claim 28, wherein The at least one LCID is multiple LCIDs corresponding to multiple types, and the multiple types include at least one of the following: at least one service type, at least one end-to-end type.

30. The method according to any one of claims 26 to 29, characterized in that The second device receives the first DSAP sub PDU from the MAC layer through the first DSAP entity corresponding to the first LCID in the DSAP layer, including: The second device receives the first DSAP sub PDU from the MAC layer through the first DSAP entity and at least one of the following: The packet data convergence protocol (PDCP) layer, the radio link control (RLC) layer; Wherein, the PDCP layer is configured not to process data plane data, and the transmission mode of the RLC layer is configured as the transparent mode.

31. The method according to any one of claims 26 to 30, characterized in that, The method further includes: The second device obtains DSAP configuration information, and the DSAP configuration information is used to configure at least one of the following: At least one DSAP entity identifier; At least one service identifier; At least one LCID; The first mapping relationship between the at least one DSAP entity identifier and the at least one service identifier; The second mapping relationship between the at least one DSAP entity identifier and the at least one LCID; The priority of the DSAP entity; The uplink data source; The downlink data destination; The indication of whether to perform encryption and decryption; The security algorithm for encryption; The indication of whether to perform integrity protection; The security algorithm for integrity protection; The indication of whether to perform decryption; Transmission mode; First indication information indicating whether segmentation is allowed; Packet aggregation parameters; Segmentation allowance parameter; Segmentation allowance multiple; Indication of whether to deliver in sequence; Indication of whether to compress; Compression algorithm; Indication of whether to perform retransmission; Identifier of the buffer status report BSR group.

32. The method according to claim 31, wherein The transmission mode is any one of the following: Transparent mode TM, unacknowledged mode UM, acknowledged mode AM, or unacknowledged mode - enhanced UM-A; Among them, at least one of the UM, the AM, and the UM-A supports segmentation, and at least one of the AM and the UM-A supports non-segmentation.

33. The method according to claim 31 or 32, characterized in that, The DSAP configuration information satisfies at least one of the following: In the case where the first mapping relationship is not a one-to-one mapping relationship, the DSAP configuration information includes the at least one service identifier and the first mapping relationship; In the case where the first indication information indicates that segmentation is not allowed, the DSAP configuration information includes or does not include the packet aggregation parameters; In the case where the first indication information indicates that segmentation is allowed, the DSAP configuration information includes the segmentation allowance parameter; In the case where the DSAP configuration information does not include the first indication information, the DSAP configuration information includes the packet aggregation parameters and does not include the segmentation allowance parameter, or the DSAP configuration information does not include the packet aggregation parameters and includes the segmentation allowance parameter; In the case where the DSAP configuration information includes the segmentation allowance parameter, the DSAP configuration information includes or does not include the segmentation allowance multiple.

34. The method according to any one of claims 26 to 33, characterized in that, The second device unpacks the first DSAP sub PDU through the first DSAP entity to obtain first data plane data, including: The second device unpacks the first DSAP sub PDU through the first DSAP entity based on the first indication information in the DSAP configuration information to obtain the first data plane data; Among them, a field for indicating the length of the payload in the first DSAP sub PDU is carried in the DSAP sub-header of the first DSAP sub PDU.

35. The method according to any one of claims 26 to 33, characterized in that, The second device unpacks the first DSAP sub PDU through the first DSAP entity to obtain first data plane data, including: The second device unpacks the first DSAP sub PDU through the first DSAP entity based on the packet aggregation parameters in the DSAP configuration information to obtain the first data plane data.

36. The method according to any one of claims 26 to 33, characterized in that, The second device unpacks the first DSAP sub PDU through the first DSAP entity to obtain first data plane data, including: The second device unpacks the first DSAP sub PDU through the first DSAP entity based on the segmentation allowance parameter in the DSAP configuration information to obtain the first data plane data; or The second device unpacks the first DSAP sub PDU through the first DSAP entity based on the segmentation allowance parameter and the segmentation allowance multiple in the DSAP configuration information to obtain the first data plane data.

37. The method according to claim 36, characterized in that, The value of the segmentation permission parameter is a unique value; among them, the first DSAP sub PDU satisfies any one of the following: The DSAP sub-header of the first DSAP sub PDU includes a field for carrying segmentation information and a field for carrying the length of the payload in the first DSAP sub PDU; The DSAP sub-header includes a field for carrying segmentation information; The DSAP sub-header includes a field for carrying segmentation information and a field for carrying the length of the payload in the first DSAP sub PDU.

38. The method according to claim 36, wherein The value of the segmentation permission parameter is a value list; among them, the first DSAP sub PDU satisfies any one of the following: The DSAP sub-header of the first DSAP sub PDU includes a field for carrying segmentation information and a field for carrying the length of the payload in the first DSAP sub PDU; The DSAP sub-header includes a field for carrying segmentation information and a field for carrying the length of the payload in the first DSAP sub PDU or the value used in the value list; The DSAP sub-header includes a field for carrying segmentation information and a field for carrying the length of the payload in the first DSAP sub PDU.

39. The method according to claim 38, characterized in that, When the first DSAP entity unpacks the first DSAP sub PDU based on the segmentation permission parameter, the DSAP sub-header includes a field for carrying the length of the payload in the first DSAP sub PDU or the value used in the value list; or When the first DSAP entity unpacks the first DSAP sub PDU based on the segmentation permission parameter and the segmentation permission multiple, the DSAP sub-header includes a field for carrying the length of the payload in the first DSAP sub PDU.

40. The method according to any one of claims 37 to 39, characterized in that, The DSAP sub-header includes or does not include a field for carrying the sub-sequence number of the first DSAP sub PDU.

41. The method according to any one of claims 34 to 40, characterized in that, When the transmission mode of the DSAP layer is AM or UM-A, the DSAP sub-header of the first DSAP sub PDU includes a field for carrying an indication of whether information feedback is performed.

42. The method according to any one of claims 34 to 41, characterized in that, The DSAP sub-header of the first DSAP sub PDU includes at least one of the following: A field for carrying the identifier of the first DSAP entity; A field for carrying the service identifier of the first data plane data; A field for carrying an indication of whether the first DSAP sub PDU is a control packet or a data packet; A field for carrying the sequence number of the first DSAP sub PDU; A field for performing integrity protection and verification on the first DSAP sub PDU.

43. The method according to any one of claims 26 to 42, characterized in that, The method further includes: The second device receives a second MAC sub PDU through the MAC layer, where the second MAC sub PDU includes a MAC control element CE, and the MAC CE includes a field carrying an identifier of a buffer status report BSR group and a field carrying the buffer size of the BSR group.

44. The method according to any one of claims 26 to 42, characterized in that, The method further includes: The second device receives a second DSAP sub PDU from the MAC layer through the first DSAP entity; The second device unpacks the second DSAP sub PDU to obtain a first buffer size report BSR: Wherein, the first BSR is the BSR of the first LCID, the BSR of the first DSAP entity, or the BSR of the service identifier of the first data plane data, and the first DSAP PDU includes the second DSAP sub PDU.

45. The method according to claim 44, characterized in that, The second DSAP sub PDU satisfies any one of the following: When the first BSR is the BSR of the first LCID, the second DSAP sub PDU includes a DSAP control element CE, and the DSAP CE includes a field carrying an identifier for indicating that the second DSAP sub PDU is a DSAP BSR and a field carrying the buffer size of the first LCID; When the second DSAP sub PDU includes the DSAP CE, the second DSAP sub PDU is the first DSAP sub PDU or the last DSAP sub PDU in the first DSAP PDU; When the first BSR is the BSR of the first DSAP entity, the second DSAP sub PDU includes a field carrying an identifier of the first DSAP entity; When the first BSR is the BSR of the service identifier of the first data plane data, the second DSAP sub PDU includes a field carrying an identifier of the first DSAP entity and a field carrying the service identifier of the first data plane data.

46. The method according to claim 44 or 45, characterized in that, When the first BSR is the BSR of the first DSAP entity or the BSR of the service identifier of the first data plane data, the second DSAP sub PDU further includes at least one of the following: A field carrying an indication of whether the second DSAP sub PDU is a control packet or a data packet; A field carrying an indication of the type of the second DSAP sub PDU.

47. The method according to any one of claims 26 to 46, characterized in that, The second device unpacks the first DSAP sub PDU through the first DSAP entity to obtain first data plane data, including: The second device unpacks the first DSAP sub PDU through the first DSAP entity and at least one of the following to obtain the first data plane data: decryption, data packet recombination, integrity check.

48. The method according to any one of claims 26 to 47, characterized in that, The first DSAP PDU includes a third DSAP sub PDU, and the third DSAP sub PDU includes a field carrying a type of status report and a field carrying a status report. The type of the status report includes at least one of the following: Unacknowledged sequence number; Unacknowledged starting sequence number and unacknowledged ending sequence number; Unacknowledged sequence number and unacknowledged sub-sequence number in the unacknowledged sequence number; Unacknowledged first sequence number, unacknowledged starting sub-sequence number in the first sequence number, unacknowledged second sequence number, and unacknowledged ending sub-sequence number in the second sequence number.

49. The method according to claim 48, wherein The third DSAP sub PDU further includes at least one of the following: A field carrying an identifier of the first DSAP entity; A field carrying a service identifier of the first data plane data; A field carrying a field for indicating that the third DSAP sub PDU is a control packet or a data packet; A field carrying a field for indicating the type of the third DSAP sub PDU; A field carrying the length of the field carrying the status report; A field carrying acknowledgment information; A field carrying a field for indicating the type of the status report and a field for indicating the content corresponding to the type of the status report.

50. A data processing device, characterized in that, including: A processing unit for packetizing first data plane data through a first DSAP entity in a data service adaptation protocol (DSAP) layer to obtain a first data service adaptation protocol sub-protocol data unit (DSAP sub PDU); A communication unit for receiving a first DSAP PDU from the DSAP layer through a media access control (MAC) layer, where the first DSAP PDU includes the first DSAP sub PDU; The processing unit is further configured to: packetize the first DSAP PDU through the MAC layer to obtain a first MAC sub PDU, where the first MAC sub PDU includes a first logical channel identifier (LCID) corresponding to the first DSAP entity.

51. The device according to claim 50, characterized in that, The first DSAP entity is a DSAP entity in the DSAP layer corresponding to the service identifier of the first data plane data.

52. The device according to claim 50 or 51, characterized in that The MAC layer is configured with at least one LCID dedicated to data plane data, and the at least one LCID includes the first LCID.

53. The device according to any one of claims 50 to 52, characterized in that, The communication unit is specifically configured to: Receive the first DSAP PDU from the DSAP layer through the MAC layer and at least one of the following: Packet data convergence protocol (PDCP) layer, radio link control (RLC) layer; Wherein, the PDCP layer is configured not to process data plane data, and the transmission mode of the RLC layer is configured as a transparent mode.

54. The device according to any one of claims 50 to 53, characterized in that, The communication unit is further configured to: Obtain DSAP configuration information, where the DSAP configuration information is used to configure at least one of the following: At least one DSAP entity identifier; At least one service identifier; At least one LCID; A first mapping relationship between the at least one DSAP entity identifier and the at least one service identifier; A second mapping relationship between the at least one DSAP entity identifier and the at least one LCID; Priority of the DSAP entity; Uplink data source; Downlink data destination; Indication of whether encryption / decryption is performed; Security algorithm for encryption; Indication of whether integrity protection is performed; Security algorithm for integrity protection; Indication of whether decryption is performed; Transmission mode; First indication information indicating whether segmentation is allowed; Packet assembly parameters; Segmentation allowance parameters; Segmentation allowance multiple; Indication of whether in-sequence delivery is performed; Indication of whether compression is performed; Compression algorithm; Indication of whether retransmission is performed; Identification of the buffer status report BSR group.

55. A data processing device, characterized in that, Including: A processing unit, configured to unpack a first media access control sub-protocol data unit MAC subPDU through a media access control MAC layer to obtain a first data service adaptation protocol protocol data unit DSAP PDU, where the first DSAP PDU includes the first DSAP sub PDU, and the first MAC sub PDU includes a first logical channel identifier LCID; A communication unit, configured to receive the first DSAP sub PDU from the MAC layer through a first DSAP entity corresponding to the first LCID in the DSAP layer; The processing unit is further configured to: unpack the first DSAP sub PDU through the first DSAP entity to obtain first data plane data.

56. The device according to claim 55, characterized in that, The first DSAP entity is the DSAP entity corresponding to the service identifier of the first data plane data in the DSAP layer.

57. The device according to claim 55 or 56, characterized in that, The MAC layer is configured with at least one LCID dedicated to data plane data, and the at least one LCID includes the first LCID.

58. The device according to any one of claims 55 to 57, characterized in that, The communication unit is specifically configured to: Receive the first DSAP sub PDU from the MAC layer through the first DSAP entity and at least one of the following: Packet data convergence protocol PDCP layer, radio link control RLC layer; Wherein, the PDCP layer is configured not to process data plane data, and the transmission mode of the RLC layer is configured as the transparent mode.

59. The device according to any one of claims 55 to 58, characterized in that, The communication unit is further configured to: Obtain DSAP configuration information, where the DSAP configuration information is used to configure at least one of the following: At least one DSAP entity identifier; At least one service identifier; At least one LCID; The first mapping relationship between the at least one DSAP entity identifier and the at least one service identifier; The second mapping relationship between the at least one DSAP entity identifier and the at least one LCID; Priority of the DSAP entity; Uplink data source; Downlink data destination; Indication of whether encryption / decryption is performed; Security algorithm for encryption; Indication of whether integrity protection is performed; Security algorithm for integrity protection; Indication of whether decryption is performed; Transmission mode; First indication information indicating whether segmentation is allowed; Packet assembly parameters; Segmentation allowance parameters; Segmentation allowance multiple; Indication of whether in-sequence delivery is performed; Indication of whether compression is performed; Compression algorithm; Indication of whether retransmission is performed; Identification of the buffer status report BSR group.

60. A first device, characterized in that, It includes a transceiver, a processor, and a memory. The memory stores programs or instructions that can run on the processor. When the programs or instructions are executed by the processor, the data processing method according to any one of claims 1 to 25 is implemented.

61. A second device, characterized in that, It includes a transceiver, a processor, and a memory. The memory stores programs or instructions that can run on the processor. When the programs or instructions are executed by the processor, the data processing method according to any one of claims 26 to 49 is implemented.

62. A readable storage medium, characterized in that, Programs or instructions are stored on the readable storage medium. When the programs or instructions are executed by the processor, the data processing method according to any one of claims 1 to 25 is implemented, or the data processing method according to any one of claims 26 to 49 is implemented.

Images