Data processing method and apparatus, device, and storage medium

Abstract

The present application relates to the field of communications, and provides a data processing method and apparatus, a device, and a storage medium. The data processing method comprises: by means of a first data service adaptation protocol (DSAP) entity in a DSAP layer, a first device packages first data plane data, to obtain a first data service adaptation protocol sub-protocol data unit (DSAP sub PDU); by means of a media access control (MAC) layer, the first device receives a first DSAP PDU from the DSAP layer, the first DSAP PDU comprising the first DSAP sub PDU; by means of the MAC layer, the first device packages the first DSAP PDU, to obtain a first MAC sub PDU, the first MAC sub PDU comprising a first logical channel identifier (LCID) corresponding to the first DSAP entity.

Description

Data processing method, device, equipment and storage medium

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to the Chinese patent application filed with the China Patent Office on December 21, 2023, with application number 202311782754.2 and invention name “Data processing method, device, equipment and storage medium”, the entire contents of which are incorporated by reference into this application. Technical Field

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

[0004] The data plane services of the sixth generation (6-Generation, 6G) mobile communication technology are characterized by a wide variety of services.

[0005] However, the wide variety of services leads to complex end-to-end transmission. Therefore, Layer 2 (L2) radio link control (RLC), packet data convergence protocol (PDCP), and service data adaptation protocol (SDAP) are no longer able to meet various requirements. For example, they cannot meet data transmission requirements with high latency requirements, which in turn affects communication performance.

[0006] Therefore, there is an urgent need in this field for a data transmission method to reduce the end-to-end data delay and thereby improve communication performance. Summary of the Invention

[0007] The embodiments of the present application provide a data processing method, apparatus, device, and storage medium that can reduce end-to-end data latency and thereby improve communication performance.

[0008] In a first aspect, a data processing method is provided, comprising:

[0009] The first device packages 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;

[0010] The first device receives 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;

[0011] The first device packages the first DSAPPDU 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.

[0012] In a second aspect, a data processing method is provided, comprising:

[0013] The second device decapsulates the 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;

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

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

[0016] According to a third aspect, a data processing device is provided, comprising:

[0017] a processing unit, configured to packetize 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;

[0018] a communication unit, 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;

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

[0020] In a fourth aspect, a data processing device is provided, comprising:

[0021] a processing unit, configured to decapsulate, through a media access control MAC layer, a first media access control sub-protocol data unit (MAC sub PDU) to obtain a first data service adaptation protocol (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);

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

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

[0024] In a fifth aspect, a first device is provided, comprising a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the program or instructions are executed by the processor, the steps of the method described in the first aspect are implemented.

[0025] In a sixth aspect, a first device is provided, comprising a processor and a communication interface, wherein 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 (DSAP) sub-PDU;

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

[0027] The processor 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.

[0028] In the seventh aspect, a second device is provided, which includes a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the program or instructions are executed by the processor, the steps of the method described in the second aspect are implemented.

[0029] In an eighth aspect, a second device is provided, including a processor and a communication interface, wherein the processor is configured to depacketize 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 (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);

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

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

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

[0033] In the tenth aspect, a wireless communication system is provided, comprising: a first device and a second device, wherein 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.

[0034] In the eleventh aspect, a chip is provided, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the method as described in the first aspect, or to implement the method as described in the second aspect.

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

[0036] In an embodiment of the present application, the first device packages 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 packages the first DSAPPDU 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. This is equivalent to directly packaging the first data plane data through the first DSAP entity, and the first MAC sub PDU obtained after packaging the first DSAPPDU through the MAC layer includes the first LCID corresponding to the first DSAP entity. As a result, the DSAP layer and the MAC layer can communicate directly, which can reduce the end-to-end data delay, for example, it can reduce the transmission delay and processing delay, and thus improve the communication performance. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following briefly introduces the drawings required for use in the description of the embodiments of the present application. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0038] FIG1 shows a block diagram of a wireless communication system applicable to an embodiment of the present application.

[0039] FIG2 is a schematic diagram of a user plane protocol architecture.

[0040] FIG3 is a schematic diagram of a control plane protocol architecture.

[0041] FIG4 is a schematic flow chart of a data processing method provided in an embodiment of the present application.

[0042] FIG5 is a schematic diagram of a data plane protocol stack architecture provided in an embodiment of the present application.

[0043] Figure 6 is an example of a mapping relationship between a service identifier, a DSAP entity identifier, and an LCID provided in an embodiment of the present application.

[0044] Figure 7 is an example of another mapping relationship between the service identifier, DSAP entity identifier and LCID provided in an embodiment of the present application.

[0045] FIG8 is an example of the format of the DSAP PDU provided in an embodiment of the present application.

[0046] FIG9 is an example of the data format of a DSAP sub PDU obtained by unsegmenting data plane data, as provided in an embodiment of the present application.

[0047] FIG10 is an example of the data format of a DSAP sub PDU obtained by unsegmenting and packetizing data plane data in a fixed size according to an embodiment of the present application.

[0048] FIG11 is an example of the data format of a DSAP sub PDU obtained by packetizing data plane data in a fixed size without segmentation or after segmentation under UM, provided by an embodiment of the present application.

[0049] FIG12 is an example of the data format of a DSAP sub PDU obtained by packetizing data plane data in a fixed size without segmentation or in a segmented manner under AM or UM-A, according to an embodiment of the present application.

[0050] FIG13 is an example of the data format of a DSAP sub PDU obtained by packetizing data plane data in a non-segmented or segmented manner according to a semi-static size under UM, provided by an embodiment of the present application.

[0051] FIG14 is an example of the data format of a DSAP sub PDU obtained by packetizing data plane data in an unsegmented or segmented manner according to a semi-static size under AM or UM-A, provided in an embodiment of the present application.

[0052] FIG15 is an example of the data format of a status report in an embodiment of the present application.

[0053] FIG16 is an example of the type provided by an embodiment of the present application.

[0054] FIG17 is an example of a configuration process provided in an embodiment of the present application.

[0055] FIG18 is an example of the location of the DSAP BSR provided in an embodiment of the present application.

[0056] FIG19 is an example of the format of the BSR provided in an embodiment of the present application.

[0057] Figure 20 is a schematic flowchart of another data processing method provided in an embodiment of the present application.

[0058] FIG21 shows a schematic block diagram of a data processing device according to an embodiment of the present application.

[0059] FIG22 shows a schematic block diagram of another data processing device according to an embodiment of the present application.

[0060] Figure 23 is an example of a communication device provided in an embodiment of the present application.

[0061] FIG24 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of the present application.

[0062] Figure 25 is an example of a network-side device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0063] The following will be combined with the accompanying drawings in the embodiments of this application to clearly describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field are within the scope of protection of this application.

[0064] The terms "first", "second", etc. in this application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way are interchangeable where appropriate, so that the embodiments of the present application can be implemented in an order other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same type, and do not limit the number of objects, for example, the first object can be one or more. In addition, "or" in this application represents at least one of the connected objects. For example, "A or B" covers three options, namely, Option 1: including A but not including B; Option 2: including B but not including A; Option 3: including both A and B. The character " / " generally indicates that the objects associated before and after are in an "or" relationship.

[0065] The term "indication" in this application can be either a direct indication (or explicit indication) or an indirect indication (or implicit indication). A direct indication can be understood as the sender explicitly informing the receiver of specific information, the operation to be performed, or the requested result, etc. in the instruction sent; an indirect indication can be understood as the receiver determining the corresponding information based on the instruction sent by the sender, or making a judgment and determining the operation to be performed or the requested result, etc. based on the judgment result.

[0066] It is worth noting that the technology described in the embodiments of the present application is not limited to the Long Term Evolution (LTE) / LTE-Advanced (LTE-A) system, but 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 the present application are often used interchangeably, and the described technology can be used for the systems and radio technologies mentioned above, as well as for other systems and radio technologies. The following description describes a New Radio (NR) system for example purposes, and NR terminology is used in most of the following description, but these technologies can also be applied to systems other than NR systems, such as 6th Generation (6G) communication systems.

[0067] FIG1 shows a block diagram of a wireless communication system applicable to an embodiment of the present application.

[0068] As shown in FIG1 , the wireless communication system includes a terminal 11 and a network-side device 12 .

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

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

[0071] Access network equipment may also be referred to as radio access network (RAN) equipment, radio access network functions, or radio access network units. Access network equipment may include base stations, wireless local area network (WLAN) access points (AS), or wireless fidelity (WiFi) nodes. Among them, the base station can 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 (home evolved Node B), Transmission Reception Point (TRP) or other appropriate terms in the field. As long as the same technical effect is achieved, the base station is not limited to specific technical vocabulary. It should be noted that in the embodiment of the present application, only the base station in the NR system is used as an example for introduction, and the specific type of the base station is not limited.

[0072] Core network equipment can also be called core network functions or core network nodes. Exemplarily, the core network equipment 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 ( Function, AF), Location Management Function (LMF), positioning server, etc. It should be noted that in the embodiment of the present application, only the core network function in the NR system is introduced as an example, and the specific type of the core network function is not limited.

[0073] In order to facilitate a better understanding of the embodiments of the present application, the technologies related to the present application are explained.

[0074] FIG2 is a schematic diagram of a user plane protocol architecture.

[0075] As shown in Figure 2, the user plane between the UE and the access network device (e.g., gNB) may include the following protocol layers:

[0076] Physical Layer (PHY);

[0077] Media Access Control (MAC) layer;

[0078] Radio Link Control (RLC) layer;

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

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

[0081] FIG3 is a schematic diagram of a control plane protocol architecture.

[0082] As shown in Figure 3, the control plane of the UE may include the following protocol layers:

[0083] PHY layer;

[0084] MAC layer;

[0085] RLC layer;

[0086] PDCP layer;

[0087] Radio Resource Control (RRC) layer;

[0088] Non-Access Stratum (NAS).

[0089] The control plane of an access network device (e.g., gNB) may include the following protocol layers:

[0090] PHY layer;

[0091] MAC layer;

[0092] RLC layer;

[0093] PDCP layer;

[0094] Radio Resource Control (RRC) layer.

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

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

[0097] PDCP layer: The main functions include data transmission, compression and decompression (RoHC or EHC), security processing (encryption and decryption, integrity protection and verification), PDCP replication, and in-order (or out-of-order) delivery. The 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.

[0098] RLC layer: Supports three transmission modes: Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM). TM is a transparent transmission mode that does not support segmentation. UM allows segmentation but does not provide retransmission. AM allows segmentation and retransmission, provides reliable transmission through status reporting, and does not tolerate packet loss.

[0099] However, the wide variety of services leads to complex end-to-end transmission. Therefore, in terms of transmission, the RLC layer, PDCP layer, and SDAP layer of Layer 2 (L2) can no longer meet various requirements. For example, they cannot meet the data transmission requirements with high latency requirements, which in turn affects communication performance.

[0100] For example, for the RLC layer, UM does not support reliable transmission, and AM does not allow packet loss. They may not be suitable for certain business scenarios on the data plane, such as the need to report 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, adding additional overhead.

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

[0102] FIG4 is a schematic flow chart of a data processing method 200 provided in an embodiment of the present application.

[0103] As shown in FIG4 , the method 200 may include:

[0104] S210: The first device packages 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 (PDU, DSAP sub PDU).

[0105] S220: The first device receives a first DSAPPDU from the DSAP layer through the MAC layer, where the first DSAPPDU includes the first DSAP sub PDU.

[0106] S230: The first device assembles the first DSAPPDU 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.

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

[0108] Taking the first device as a terminal device as an example, the first DSAP entity receives first data plane data, which may be original data plane data 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 DSAPPDU including the first DSAP sub PDU, the MAC layer obtains a complete uplink transmission block (TB) based on the first DSAPPDU and sends it.

[0109] In this embodiment, the first data plane data is directly packetized by the first DSAP entity, and the first MAC sub PDU obtained after the first DSAPPDU is packetized by the MAC layer includes the first LCID corresponding to the first DSAP entity. As a result, the DSAP layer and the MAC layer can communicate directly, which can reduce the end-to-end data delay, for example, it can reduce the transmission delay and processing delay, and thus improve the communication performance.

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

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

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

[0113] Exemplarily, the MAC layer is configured with an LCID dedicated to data plane data, that is, the data plane can use a common LCID.

[0114] In this embodiment, at least one LCID dedicated to the data plane is defined in the MAC, which can be used to identify data on the data plane, thereby enabling transparent transmission of data from the MAC layer to the DSAP layer.

[0115] In some embodiments, the at least one LCID is a plurality of LCIDs corresponding to a plurality of types, and the plurality of types include at least one of the following: at least one business type, and at least one end-to-end type.

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

[0117] Exemplarily, the at least one service type includes at least one service type that may include artificial intelligence (AI), synaesthesia, and other types. For the at least one end-to-end type, it may include a terminal-to-radio access network type (UE<->RAN) or a terminal-to-core network type (UE<->CN), etc. Exemplarily, the multiple types may also be multiple combination types, and the combination type may be formed by combining different types, such as service types and end-to-end types. That is to say, it may be defined separately according to the service type (such as AI or synaesthesia) of different data planes, the end-to-end type (UE<->RAN or UE<->CN), or a combination thereof.

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

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

[0120] In some embodiments, the S220 includes:

[0121] The first device receives the first DSAPPDU from the DSAP layer via the MAC layer and at least one of:

[0122] PDCP layer, RLC layer;

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

[0124] FIG5 is a schematic diagram of a data plane protocol stack architecture provided in an embodiment of the present application.

[0125] As shown in Figure 5, the data plane protocol architecture differs from the user plane in that it does not have the PDCP and RLC protocol layers. Alternatively, the PDCP and RLC layers can be retained but simplified in functionality. With the PDCP and RLC layers retained, the RLC can use TM for transparent transmission. The data plane radio bearer (DPRB), which carries the data plane, does not have the original PDCP configuration and therefore does not require a PDCP header.

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

[0127] In this embodiment, by removing the PDCP and RLC protocol layers, or by simplifying their functionality while retaining them, the data plane's Layer 2 (L2) layer is isolated from the RLC, PDCP, and even SDAP processing within the protocol stack, ensuring the independence of the data plane protocol stack. Furthermore, by simplifying the data plane protocol stack, such as by eliminating ARQ and queuing, latency can be reduced, ensuring that the data plane protocol stack is more consistent with data plane characteristics and improving communication performance.

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

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

[0130] At least one DSAP entity ID;

[0131] At least one data plane traffic ID;

[0132] At least one LCID; for example, in the case where the RLC layer is not retained, the DSAP configuration information includes the at least one LCID; for another example, in the case where the RLC layer is retained, the DSAP configuration information does not include the at least one LCID, in which case the configuration information at the RLC layer may include the at least one LCID;

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

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

[0135] Priority of DSAP entity;

[0136] Uplink data source;

[0137] Downlink data purpose;

[0138] Instruction on whether to encrypt or decrypt;

[0139] security algorithms used for encryption;

[0140] Indication of whether integrity protection is enabled;

[0141] Security algorithms for integrity protection;

[0142] Instruction on whether to decrypt;

[0143] Transmission mode; for example, TM, UM, AM, UM-A;

[0144] First indication information indicating whether segmentation is allowed;

[0145] Package parameters;

[0146] Segment permission parameters; for example, set when limited to UM, AM and UM-A;

[0147] Segment allowable multiples; for example, it is limited to UM, AM and UM-A and is valid when the segment allowable parameter is set;

[0148] Instructions on whether submission is in order;

[0149] An indication of whether to compress;

[0150] Compression algorithm;

[0151] an indication of whether to repeat the transmission;

[0152] The identifier of the BSR group; for example, the logical channel group (LCG).

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

[0154] In this embodiment, the DSAP configuration information enables the processing of the DSAP layer to aggregate the functions of the RLC layer and the PDCP layer, and the processing of the DSAP layer is different from the functions of the RLC layer and the PDCP layer.

[0155] Specifically, the difference from RLC function is:

[0156] 1. When the RLC layer is packetizing for uplink transmission, if resources are insufficient, it will perform segmentation according to the packetization size indicated by the MAC. In this embodiment, the DSAP layer performs segmentation within the packetization size indicated by the MAC. Depending on the DSAP transmission mode and configuration, the packetization can be divided into unsegmented packetization (e.g., packetization with no fixed size or packetization with a fixed size) and segmented packetization. Segmentation can be performed according to a fixed size (e.g., a segmentation permission parameter or a packetization parameter), a semi-static size (e.g., a segmentation permission parameter), or a segmentation permission multiple.

[0157] 2. RLC supports three transmission modes: TM, UM, and AM. TM is a transparent transmission mode. UM does not provide retransmission. AM provides reliable transmission through status reports, but does not allow packet loss. In this embodiment, the DSAP layer of 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 opposite end device to retransmit a certain PDU reaches a threshold and is still not completely received, the receiving end accepts the fact that the PDU is lost and updates the receiving window status. This adapts to various QoS situations of data plane services. In addition, although the AM and UM-A processing of the DSAP layer support retransmission, it will not re-segment the segmented data, which is used to simplify processing.

[0158] Differences from PDCP functions:

[0159] 1. PDCP functions are managed on a RB basis, including security, decompression, in-order delivery, PDCP replication, etc. Each RB corresponds to a PDU SESSION. In this embodiment, the DSAP layer may not have the concept of RBs, but directly uses DSAP entities (each DSAP entity is assigned a different ID) as units, corresponding to a service type, end-to-end type, or a combination thereof, which can be flexibly configured according to different situations. For example, the following figure shows that 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 CN may be inconsistent) and even different keys can be set for DSAP entity 1 and DSAP entity 2.

[0160] In addition to the above, the RLC layer and the PDCP layer manage their own SNs, and each DSAP entity in the DSAP layer of the data plane has a unique SN for implementing all functions.

[0161] If TM is configured in the RLC protocol layer in order to pursue transmission and processing speed, there will be no PDCP-related processing, such as security and in-order delivery, so data security and orderliness are not guaranteed. In this embodiment, through the indication of whether to deliver in order, the indication of whether to compress, the compression algorithm and other parameters in the DSAP configuration information, the function of aggregating the PDCP layer at the DSAP layer can be achieved, thereby ensuring data security and orderliness.

[0162] Figure 6 is an example of a mapping relationship between a service identifier, a DSAP entity identifier, and an LCID provided in an embodiment of the present application.

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

[0164] Figure 7 is an example of another mapping relationship between the service identifier, DSAP entity identifier and LCID provided in an embodiment of the present application.

[0165] As shown in Figure 7, when data plane services use finer granularity to manage LCIDs, LCIDs may be defined based on different data plane service types (such as AI, synaesthesia), end-to-end types (UE<->RAN, UE<->CN), or a combination thereof. In this case, each DSAP entity corresponds to one or more logical channels, and each logical channel corresponds to one or more DSAP entities. For example, when a DSAP entity is configured for repeated PDU transmission, there may be a situation where one DSAP entity corresponds to multiple logical channels.

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

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

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

[0169] The following points need to be explained regarding the DSAP configuration information:

[0170] 1. If each DSAP entity in the DSAP layer corresponds to only 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. Similarly, the corresponding domain will not appear in the DSAP subheader. For ease of description, a one-to-many situation is assumed in the following embodiments.

[0171] 2. Disallowing segmentation is limited to AM and UM-A modes because TM itself does not support segmentation. If UM does not allow segmentation, there will be no difference in processing and format between them and TM, and the advantages of UM will not be reflected. Disallowing segmentation in AM and UM-A can simplify processing and improve reliability by leveraging advantages such as status reporting.

[0172] 3. The packetization parameter is optional. If present, the DSAP will assemble the PDUs according to this packetization parameter. If not present, the DSAP will assemble the packets flexibly. After the MAC obtains an uplink authorization (UL grant), the MAC can notify the DSAP according to an integer multiple N of the packetization parameter, and obtain up to N DSAP sub PDUs to form a MAC sub PDU for transmission. 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 to be sent is N-1 DSAP sub PDUs, and the BSR of the data plane is sent.

[0173] 4. The segmentation permission parameter and the segmentation permission multiple are optional parameters. The segmentation permission multiple is effective only when the segmentation permission parameter is set. It means that when packet assembly and segmentation occur, the maximum size of the segmented packet can be the segmentation permission parameter × the segmentation permission multiple. For example, if the segmentation permission parameter is 50 and the segmentation permission 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 DSAP based on the SDU size based on the packet size indicated by the MAC layer.

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

[0175] In a 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;

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

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

[0178] In a case where the DSAP configuration information does not include the first indication information, the DSAP configuration information includes the packetization parameter but does not include the fragmentation permission parameter, or the DSAP configuration information does not include the packetization parameter but includes the fragmentation permission parameter;

[0179] In the case where the DSAP configuration information includes the fragmentation permission parameter, the DSAP configuration information includes or does not include the fragmentation permission multiple.

[0180] FIG8 is an example of the format of the DSAP PDU provided in an embodiment of the present application.

[0181] As shown in Figure 8, a DSAP PDU may include one or more DSAP sub PDUs, each of which may have a corresponding DSAP sub-header. For example, a DSAP PDU may include DSAP sub-header 1, DSAP sub PDU 1 corresponding to DSAP sub-header 1, DSAP sub-header 2, DSAP sub PDU 2 corresponding to DSAP sub-header 2, DSAP sub-header 3, and DSAP sub PDU 3 corresponding to DSAP sub-header 3.

[0182] 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 this application does not make any specific limitation on this.

[0183] In some embodiments, the S210 includes:

[0184] The first device, through the first DSAP entity, performs unsegmented packetization or segmented packetization on the first data plane data based on the first indication information in the DSAP configuration information to obtain the first DSAP sub PDU;

[0185] The DSAP subheader of the first DSAP sub PDU includes a field carrying a length for indicating a payload in the first DSAP sub PDU.

[0186] In some embodiments, the S210 includes:

[0187] The first device, through the first DSAP entity, non-segmentally packages the first data plane data based on the package parameters in the DSAP configuration information to obtain the first DSAP sub PDU.

[0188] In some embodiments, the S210 includes:

[0189] The first device, through the first DSAP entity, performs unsegmented packetization or segmented packetization on the first data plane data based on the segmentation permission parameter in the DSAP configuration information to obtain the first DSAP sub PDU; or

[0190] The first device, through the first DSAP entity, performs unsegmented or segmented packetization on the first data plane data based on the segmentation permission parameter and the segmentation permission multiple in the DSAP configuration information to obtain the first DSAP sub PDU.

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

[0192] When the first device performs unsegmented packetization on the first data plane data, the DSAP subheader of the first DSAP sub PDU includes a field for carrying segmentation information and a field for indicating the length of the payload in the first DSAP sub PDU;

[0193] In a case where the first device segments 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 subheader includes a field for carrying segmentation information;

[0194] When the first device segments and packages the first data plane data, and the payload in the first DSAP sub PDU is the last data packet, the DSAP subheader includes a field for carrying segmentation information and a field for indicating the length of the payload in the first DSAP sub PDU.

[0195] 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:

[0196] When the first device performs unsegmented packetization on the first data plane data, the DSAP subheader of the first DSAP sub PDU includes a field for carrying segmentation information and a field for indicating the length of the payload in the first DSAP sub PDU;

[0197] When the first device segments 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 subheader includes 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;

[0198] When the first device segments and packages the first data plane data, and the payload in the first DSAP sub PDU is the last data packet, the DSAP subheader includes a field for carrying segmentation information and a field for indicating the length of the payload in the first DSAP sub PDU.

[0199] In some embodiments, when the first DSAP entity segments 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 subheader includes a field carrying a length of the payload in the first DSAP sub PDU or a value used in the value list; or

[0200] When the first DSAP entity segments 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 subheader includes a field carrying a length for indicating the length of the payload in the first DSAP sub PDU.

[0201] In some embodiments, when the first data plane data is segmented 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 subheader includes a field carrying a subsequence number for indicating the first DSAP sub PDU; or

[0202] When the first data plane data is segmented and the payload in the first DSAP sub PDU is the first data packet or the last data packet, the DSAP subheader includes or does not include a field carrying a subsequence number for indicating the first DSAP sub PDU.

[0203] In some embodiments, when the transmission mode of the DSAP layer is AM or UM-A, the DSAP subheader of the first DSAP sub PDU includes a field carrying a signal for indicating whether to perform information feedback.

[0204] In some embodiments, the DSAP subheader of the first DSAP sub PDU includes at least one of the following:

[0205] a domain carrying the identifier of the first DSAP entity;

[0206] a field carrying a service identifier of the first data plane data;

[0207] Carrying a field for indicating whether the first DSAP sub PDU is a control packet or a data packet;

[0208] a field carrying a sequence number indicating the first DSAP sub PDU;

[0209] The DSAP sub PDU carries a field for integrity protection and verification of the first DSAP sub PDU.

[0210] In some embodiments, the S210 includes:

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

[0212] Within the size indicated by the packetization indication information, the first device packets the first data plane data through the first DSAP entity to obtain the first DSAP sub PDU.

[0213] When the DSAP layer receives the packet assembly instruction information from the MAC, it processes the data according to the priority of each DSAP entity in the DSAP layer within the size indicated by the packet assembly instruction information. For example, after processing the first data plane data according to the priority of the first DSAP entity, the first DSAP sub PDU may be obtained. For another example, after processing the first data plane data according to the priority of the first DSAP entity, multiple first DSAP sub PDUs may be obtained.

[0214] In other words, after the MAC layer obtains the uplink authorization, when it determines that the data plane data can be packetized according to the logical channel priority, it can send the packetization indication information to the DSAP layer. The first DSAP entity in the DSAP layer completes the packetization processing of the first data plane data within the size indicated by the packetization indication information, and obtains the first DSAP sub PDU.

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

[0216] When the first DSAP entity cannot 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, where the BSR indication includes a BSR group identifier and a buffer size of the BSR group;

[0217] The first device performs packetization based on the BSR indication through the MAC layer 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 an identifier of a buffer status report BSR group and a field carrying a buffer size of the BSR group.

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

[0219] Exemplarily, the buffer size of the BSR group may be referred to as the amount of data plane data to be sent by the BSR group.

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

[0221] If the first DSAP entity cannot complete packetization of the first data plane data within the size indicated by the packetization indication information, the first device packetizes the first buffer size report BSR through the first DSAP entity to obtain a second DSAP sub PDU:

[0222] 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 DSAPPDU includes the second DSAP sub PDU.

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

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

[0225] Exemplarily, the buffer size of the first LCID may be referred to as the data volume of the data plane data to be sent of the first LCID.

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

[0227] In a case where 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;

[0228] In the case where the first BSR is a 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.

[0229] 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:

[0230] Carrying a field for indicating that the second DSAP sub PDU is a control packet or a data packet;

[0231] The field carries a field for indicating the type of the second DSAP sub PDU.

[0232] In some embodiments, the S210 includes:

[0233] The first device obtains the first DSAP sub PDU by packetizing the first data plane data through the first DSAP entity and performing at least one of the following: desensitizing, encrypting, notifying the MAC layer of the amount of data to be sent at the DSAP layer, and integrity protection.

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

[0235] Unconfirmed serial number;

[0236] Unconfirmed start sequence number and unconfirmed end sequence number;

[0237] an unconfirmed sequence number and an unconfirmed subsequence number within the unconfirmed sequence number;

[0238] An unconfirmed first sequence number, an unconfirmed starting subsequence number in the first sequence number, an unconfirmed second sequence number, and an unconfirmed ending subsequence number in the second sequence number.

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

[0240] a domain carrying the identifier of the first DSAP entity;

[0241] a field carrying a service identifier of the first data plane data;

[0242] Carrying a field for indicating that the third DSAP sub PDU is a control packet or a data packet;

[0243] A field carrying a type of the third DSAP sub PDU;

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

[0245] A field that carries confirmation information;

[0246] The data frame carries 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.

[0247] The solution of this application is described below with reference to specific embodiments.

[0248] Example 1:

[0249] Taking into account that the transmission data size and period of some data plane services are relatively fixed, the base station can use non-segmentation when configuring the DSAP entity to simplify processing and save processing time. Moreover, because the base station knows which data plane services are enabled, it can reserve them when allocating resources to achieve the purpose of non-segmentation and complete reporting.

[0250] In this embodiment, the DSAP entity supports non-segmented packetization according to the size of the data plane data.

[0251] FIG9 is an example of the data format of a DSAP sub PDU obtained by unsegmenting data plane data, as provided in an embodiment of the present application.

[0252] As shown in (a) of FIG9 , a DSAP sub PDU obtained by unsegmenting data plane data under TM or UM may include a DSAP subheader and a payload. The DSAP subheader may include at least one of the following:

[0253] DSAP entity ID: used to represent a DSAP entity, which may be the DSAP entity ID used to package data plane data;

[0254] Business ID: used to identify the business to which the data plane data belongs;

[0255] D / C: Indicates that the obtained DSAPsub PDU is a control packet or a data packet. The control packet generated in TM may be a feedback packet generated by functions such as compression.

[0256] SN: indicates the sequence number of the obtained DSAPsub PDU;

[0257] MAC-I: used for integrity protection and verification, can be placed in the DSAP subheader or after the payload. If the DSAP entity is not configured with integrity protection, the DSAP subheader may not have a MAC-I, that is, it may not include a MAC-I.

[0258] data_len: length field, which is used to indicate the length of the following payload.

[0259] As shown in (b) of FIG9 , the DSAP sub PDU obtained by unsegmenting the data plane data under AM or UM-A may further include the following DSAP sub-header, compared to the DSAP sub PDU obtained by unsegmenting the data plane data under TM or UM:

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

[0261] Example 2:

[0262] In this embodiment, the DSAP entity may perform non-segmented packet assembly according to a fixed size.

[0263] For example, when the packetization parameters are set in the DSAP configuration information, the DSAP entity can perform non-segmented packetization according to the packetization parameters in the DSAP configuration information.

[0264] FIG10 is an example of the data format of a DSAP sub PDU obtained by unsegmenting and packetizing data plane data in a fixed size according to an embodiment of the present application.

[0265] As shown in (a) of FIG10 , a DSAP sub PDU obtained by unsegmenting data plane data in a fixed size under TM or UM may include a DSAP subheader and a payload. The DSAP subheader may include at least one of the following:

[0266] DSAP entity ID: used to represent a DSAP entity, which may be the DSAP entity ID used to package data plane data;

[0267] Business ID: used to identify the business to which the data plane data belongs;

[0268] D / C: Indicates that the obtained DSAPsub PDU is a control packet or a data packet. The control packet generated in TM may be a feedback packet generated by functions such as compression.

[0269] SN: indicates the sequence number of the obtained DSAPsub PDU;

[0270] MAC-I: used for integrity protection and verification, can be placed in the DSAP subheader or after the payload. If the DSAP entity is not configured with integrity protection, the DSAP subheader may not have a MAC-I, that is, it may not include a MAC-I.

[0271] As shown in (b) of Figure 10, the DSAP sub PDU obtained by unsegmenting the data plane data under AM or UM-A is compared to the DSAP sub PDU obtained by unsegmenting the data plane data according to a fixed size under TM or UM. The DSAP subheader may further include:

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

[0273] In this embodiment, since the DSAP entity is packaged according to a fixed size, the data_len field is no longer required in the DSAP subheader.

[0274] Example 3:

[0275] In this embodiment, the DSAP entity performs packetization without segmentation or after segmentation according to a fixed size.

[0276] For example, when the segmentation permission parameter in the DSAP configuration information is set to a unique value and the segmentation permission multiple is not set, the DSAP entity can perform unsegmented or segmented packet assembly according to the segmentation permission parameter in the DSAP configuration information.

[0277] When the data plane service is used to collect the terminal's serving cell and neighboring cell measurement results, it is more suitable for the DSAP entity to segment and package them according to a fixed size. For example, if the measurement results are required to be reported in the following format, the length of each group of reported data is 8 bytes. Because neighboring cell measurements involve operations such as frequency switching, the measurement results of different frequencies may be obtained in batches in the DSAP. In this case, if the segmentation permission parameter is configured to 8 bytes when configuring the DSAP entity, the DSAP can segment and package them in the minimum unit of 8 bytes when the obtained uplink authorization (UL grant) is insufficient to report all the measurement results, that is, report a complete set of measurement results.

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

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

[0280] It is worth noting that the segmentation permission parameter does not apply to TM.

[0281] FIG11 is an example of the data format of a DSAP sub PDU obtained by packetizing data plane data in a fixed size without segmentation or after segmentation under UM, provided by an embodiment of the present application.

[0282] As shown in (a) of FIG11 , a DSAP sub PDU obtained by unsegmenting data plane data according to a fixed size under UM may include a DSAP subheader and a payload. The DSAP subheader may include at least one of the following:

[0283] DSAP entity ID: used to represent a DSAP entity, which may be the DSAP entity ID used to package data plane data;

[0284] Business ID: used to identify the business to which the data plane data belongs;

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

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

[0287] SN: indicates the sequence number of the obtained DSAPsub PDU;

[0288] MAC-I: used for integrity protection and verification. It can be placed in the DSAP subheader or after the payload. If the DSAP entity is not configured with integrity protection, the DSAP subheader may not have a MAC-I, that is, it may not include a MAC-I.

[0289] data_len: length field, which is used to indicate the length of the following payload.

[0290] As shown in (b) of FIG11 , when data plane data is segmented and packetized according to a fixed size under UM, the DSAP sub PDU obtained after packetizing data packets other than the last data packet after the segmentation may include a DSAP subheader and a payload, where the DSAP subheader may include at least one of the following:

[0291] DSAP entity ID: used to represent a DSAP entity, which may be the DSAP entity ID used to package data plane data;

[0292] Business ID: used to identify the business to which the data plane data belongs;

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

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

[0295] SN: indicates the sequence number of the obtained DSAPsub PDU;

[0296] MAC-I: used for integrity protection and verification. It can be placed in the DSAP subheader or after the payload. If the DSAP entity is not configured with integrity protection, the DSAP subheader may not have a MAC-I, that is, it may not include a MAC-I.

[0297] Sub-SN: This value can be used to indicate the subsequence number of a DSAP sub PDU. For example, it can be used to indicate the number of packets after the data plane data is segmented. Alternatively, the DSAP sub PDU generated by the segmentation uses the Sub-SN to indicate the position or sequence number of the DSAP sub PDU among all DSAP sub PDUs.

[0298] As shown in (c) of Figure 11, when data plane data is segmented and packetized according to a fixed size under UM, the DSAP sub PDU obtained by packetizing the last data packet after the segmentation may include a DSAP subheader and a payload. The DSAP subheader may include at least one of the following:

[0299] DSAP entity ID: used to represent a DSAP entity, which may be the DSAP entity ID used to package data plane data;

[0300] Business ID: used to identify the business to which the data plane data belongs;

[0301] 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 packet generated by functions such as compression.

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

[0303] SN: indicates the sequence number of the obtained DSAPsub PDU;

[0304] MAC-I: used for integrity protection and verification. It can be placed in the DSAP subheader or after the payload. If the DSAP entity is not configured with integrity protection, the DSAP subheader may not have a MAC-I, that is, it may not include a MAC-I.

[0305] data_len: length field, which is used to indicate the length of the following payload.

[0306] FIG12 is an example of the data format of a DSAP sub PDU obtained by packetizing data plane data in a fixed size without segmentation or in a segmented manner under AM or UM-A, according to an embodiment of the present application.

[0307] As shown in (a), (b), and (c) of FIG12 , the DSAP sub-PDU obtained by packetizing data plane data in a fixed size without segmentation or after segmentation under AM or UM-A may further include the following DSAP sub-header, compared to the DSAP sub-PDU obtained by packetizing data plane data in a fixed size without segmentation or after segmentation under UM:

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

[0309] It is worth noting that, in this embodiment, when the SI is set to 0b01, that is, the first data packet in the segment, or when the SI is set to 0b10, that is, the last data packet in the segment, the Sub-SN field may not be present.

[0310] Example 4:

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

[0312] For example, when the segmentation permission parameter in the DSAP configuration information is set to a value list and the segmentation permission multiple is not set, the DSAP entity can perform unsegmented or segmented packet assembly according to the value selected from the value list of the segmentation permission parameter in the DSAP configuration information (i.e., a semi-static size).

[0313] When configuring the DSAP entity, if the segmentation permission parameter is set to a list, it means that segmentation is possible, and the value used for segmentation can be adaptively set according to the size indicated by the packetization indication notified by the MAC. For example: when the value of the segmentation permission parameter = {5, 10, 25}, it means that the value used for packetization of data packets other than the last data packet in the segmented data packet can be selected from 5, 10, and 25. If the size indicated by the packetization indication is 30 and the total amount of data to be sent by the DSAP entity is 13, the terminal can perform unsegmented packetization; if the size indicated by the packetization indication is 8 and the total amount of data to be sent by the DSAP entity is 13, then the value used by the DSAP entity when packetizing is 5.

[0314] It is worth noting that the segmentation permission parameter does not apply to TM.

[0315] FIG13 is an example of the data format of a DSAP sub PDU obtained by packetizing data plane data in a non-segmented or segmented manner according to a semi-static size under UM, provided by an embodiment of the present application.

[0316] As shown in (a) of FIG13 , a DSAP sub PDU obtained by unsegmenting data plane data according to a semi-static size under UM may include a DSAP subheader and a payload. The DSAP subheader may include at least one of the following:

[0317] DSAP entity ID: used to represent a DSAP entity, which may be the DSAP entity ID used to package data plane data;

[0318] Business ID: used to identify the business to which the data plane data belongs;

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

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

[0321] SN: indicates the sequence number of the obtained DSAPsub PDU;

[0322] MAC-I: used for integrity protection and verification. It can be placed in the DSAP subheader or after the payload. If the DSAP entity is not configured with integrity protection, the DSAP subheader may not have a MAC-I, that is, it may not include a MAC-I.

[0323] data_len: length field, which is used to indicate the length of the following payload.

[0324] As shown in (b) of FIG13 , when data plane data is segmented and packetized according to a semi-static size under UM, a DSAP sub PDU obtained by packetizing data packets other than the last data packet after segmentation may include a DSAP subheader and a payload, wherein the DSAP subheader may include at least one of the following:

[0325] DSAP entity ID: used to represent a DSAP entity, which may be the DSAP entity ID used to package data plane data;

[0326] Business ID: used to identify the business to which the data plane data belongs;

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

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

[0329] SN: indicates the sequence number of the obtained DSAPsub PDU;

[0330] MAC-I: used for integrity protection and verification. It can be placed in the DSAP subheader or after the payload. If the DSAP entity is not configured with integrity protection, the DSAP subheader may not have a MAC-I, that is, it may not include a MAC-I.

[0331] Sub-SN: Its value can be used to indicate the subsequence number of a DSAP sub PDU. For example, its value can be used to indicate the number of packets after the data plane data is segmented. In other words, the DSAP sub PDU generated by the segmentation uses Sub-SN to indicate the position or sequence number of the DSAP sub PDU among all DSAP sub PDUs.

[0332] data_len: length field, which is used to indicate the length of the following payload.

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

[0334] DSAP entity ID: used to represent a DSAP entity, which may be the DSAP entity ID used to package data plane data;

[0335] Business ID: used to identify the business to which the data plane data belongs;

[0336] 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 packet generated by functions such as compression.

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

[0338] SN: indicates the sequence number of the obtained DSAPsub PDU;

[0339] MAC-I: used for integrity protection and verification. It can be placed in the DSAP subheader or after the payload. If the DSAP entity is not configured with integrity protection, the DSAP subheader may not have a MAC-I, that is, it may not include a MAC-I.

[0340] data_len: length field, which is used to indicate the length of the following payload.

[0341] FIG14 is an example of the data format of a DSAP sub PDU obtained by packetizing data plane data in an unsegmented or segmented manner according to a semi-static size under AM or UM-A, provided in an embodiment of the present application.

[0342] As shown in (a), (b), and (c) of FIG14 , the DSAP sub-PDU obtained by packetizing data plane data in an unsegmented or segmented manner according to a semi-static size under AM or UM-A may further include the following DSAP sub-header, compared to the DSAP sub-PDU obtained by packetizing data plane data in an unsegmented or segmented manner according to a semi-static size under UM:

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

[0344] It is worth noting that in this embodiment, the value of data_len can use the actual length value, or it can be set to the index of the value selected in the value list parameter of the segmentation allowed parameter. This application does not make specific restrictions on this.

[0345] Example 5:

[0346] In this embodiment, the DSAP entity performs packet assembly without segmentation or after segmentation according to the segmentation allowed multiple.

[0347] For example, when the segmentation permission parameter in the DSAP configuration information is set (for example, set to a unique value or a value list) and the segmentation permission multiple is set, the DSAP entity can perform unsegmented or segmented packet assembly according to the unique value of the segmentation permission parameter in the DSAP configuration information (or the value selected in the value list (i.e., a semi-static size)) and the segmentation permission multiple.

[0348] It should be understood that in this embodiment, the data format of the DSAP sub PDU obtained by the DSAP entity after unsegmenting or segmenting the data plane data is the same as that in embodiment 4 of the invention. The only difference is that when segmenting, data_len in the format of the last packet needs to indicate a clear size.

[0349] Example 6:

[0350] In this embodiment, the DSAP entity generates a status report when using AM and UM-A transmission to trigger the other party to retransmit. The packetization priority of the status report is higher than the packetization priority of the data.

[0351] FIG15 is an example of the data format of a status report in an embodiment of the present application.

[0352] As shown in FIG15 , the status report may include at least one of the following:

[0353] DSAP entity ID: used to represent a DSAP entity, which may be the DSAP entity ID used to package data plane data;

[0354] Business ID: used to identify the business to which the data plane data belongs;

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

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

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

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

[0359] Type (E_type) 1 to type N: used to indicate N types of non-confirmed types;

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

[0361] It is worth noting that when E_type is set to different situations, the format of E_content can be different.

[0362] FIG16 is an example of the type provided by an embodiment of the present application.

[0363] As shown in (a) of FIG16 , E_type=NACK_SN, all data packets of the SN are lost, and the SN is isolated.

[0364] As shown in (b) of FIG16 , E_type=continuous NACK_SN, and all data packets from Start NACK_SN to End NACK_SN are lost.

[0365] As shown in (c) of FIG. 16 , E_type=NACK_sub-SN, and the data packet whose sub_SN of NACK_SN is NACK_sub_SN is lost.

[0366] As shown in (d) of FIG16 , E_type=continuous NACK_sub-SN, and all data packets from Start NACK_sub_SN of Start NACK_SN to End NACK_sub_SN of End NACK_SN are lost.

[0367] Example 7:

[0368] FIG17 is an example of a configuration process provided in an embodiment of the present application.

[0369] As shown in Figure 17, when a data plane service is triggered by the UE, a request message is sent to the RAN, which may contain service-related information. The network side uses this information to configure appropriate parameters to establish a transmission link. When a data plane service is triggered by the network side, the network side determines the configuration based on the information of the initiated service.

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

[0371] Option 1:

[0372] Option 2:

[0373] It should be noted that the configuration parameters related to DSAP operations may be the DSAP configuration information mentioned above, such as priority, whether encryption or decryption, security algorithm, whether integrity protection is required, etc.

[0374] Example 8:

[0375] In this embodiment, when all the data to be sent in the DSAP layer cannot be fully packaged in this uplink authorization, a data plane buffer size report (BSR) is sent to the base station to report the amount of remaining data to be sent.

[0376] Specifically, the BSR may be sent using any of the following methods:

[0377] Method 1:

[0378] Typically, the MAC CE of the MAC layer includes a BSR, which reports the remaining amount of data to be sent in LCG units. In this embodiment, for data plane processing, if the LCG to which the data plane belongs is distinguished from the LCGs of the signaling plane and the user plane, the function of reporting the amount of data to be sent on the data plane can be implemented through the MAC CE, achieving the expected effect.

[0379] Method 2:

[0380] Packaged in the form of DSAP Control Element.

[0381] The DSAP Control Element (CE) is similar to the MAC CE in the MAC. In this case, the DSAP BSR reports the remaining data to be sent for each DSAP entity, using LCID as the unit. Upon receiving the DSAP BSR, the base station's DSAP notifies the MAC layer via an interface message, allowing it to complete resource allocation. The DSAP BSR can be distinguished from the DSAP subheader by setting the identification ID in the DSAP BSR to a value outside the DSAP entity ID range.

[0382] FIG18 is an example of the location of the DSAP BSR provided in an embodiment of the present application.

[0383] As shown in (a) of Figure 18 , the DSAP BSR can be placed at the head of the DSAP PDU. As shown in (b) of Figure 18 , the DSAP BSR can also be placed at the tail of the DSAP PDU.

[0384] Method 3:

[0385] Packetized in DSAP Control PDU format.

[0386] FIG19 is an example of the format of the BSR provided in an embodiment of the present application.

[0387] As shown in FIG19 , the BSR may include at least one of the following:

[0388] DSAP entity ID: used to represent a DSAP entity, which may be the DSAP entity ID used to package data plane data;

[0389] Business ID: used to identify the business to which the data plane data belongs;

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

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

[0392] Content: Used to indicate the amount of data to be sent.

[0393] In this embodiment, the BSR may report the amount of data to be sent in units of DSAP entities or service identifiers, thereby increasing the precision and flexibility of management units. If the unit is DSAP entities, the service identifier may not be included; if the unit is service identifiers, both the DSAP entity ID and the service identifier may be included.

[0394] It should be understood that the figures in Examples 1 to 8 are for illustrative purposes only and should not be construed as limiting the present application. For example, the figures merely illustrate the types of fields included and should not be construed as limiting the actual lengths of each field. For another example, the data_len field in the figures may also include an auxiliary field to indicate the length of data_len. This application does not impose specific limitations on this.

[0395] The above describes the data processing method provided in this application from the perspective of the first device (i.e., the perspective of the sending end or the perspective of packet assembly). The following describes the data processing method provided in this application from the perspective of the second device (i.e., the perspective of the receiving end or the perspective of unpacking).

[0396] FIG20 is a schematic flowchart of a data processing method 300 provided in an embodiment of the present application.

[0397] As shown in FIG. 20 , the data processing method 300 may include:

[0398] S310: The second device decapsulates the first media access control sub-protocol data unit (MAC sub PDU) through the media access control (MAC) layer to obtain a first data service adaptation protocol (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).

[0399] S320: 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;

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

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

[0402] Taking the second device as a terminal device as an example, after 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 DSAPPDU 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 subsequently process the first DSAP sub PDU. In other words, after the first DSAP entity receives the first DSAP sub PDU sent by the MAC layer, it processes it according to the configuration of the DSAP layer, unpacks the first DSAP sub PDU to obtain first data plane data, and delivers the first data plane data to its service target.

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

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

[0405] In some embodiments, the at least one LCID is a plurality of LCIDs corresponding to a plurality of types, and the plurality of types include at least one of the following: at least one business type, and at least one end-to-end type.

[0406] In some embodiments, the S320 includes:

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

[0408] Packet Data Convergence Protocol PDCP layer, Radio Link Control RLC layer;

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

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

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

[0412] At least one DSAP entity identifier;

[0413] At least one business identifier;

[0414] At least one LCID;

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

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

[0417] Priority of DSAP entity;

[0418] Uplink data source;

[0419] Downlink data purpose;

[0420] Instruction on whether to encrypt or decrypt;

[0421] security algorithms used for encryption;

[0422] Indication of whether integrity protection is enabled;

[0423] Security algorithms for integrity protection;

[0424] Instruction on whether to decrypt;

[0425] Transmission mode;

[0426] First indication information indicating whether segmentation is allowed;

[0427] Package parameters;

[0428] Segmentation allowed parameters;

[0429] Multiples are allowed for segments;

[0430] Instructions on whether submission is in order;

[0431] An indication of whether to compress;

[0432] Compression algorithm;

[0433] an indication of whether to repeat the transmission;

[0434] Buffer Status Report (BSR) group identifier.

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

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

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

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

[0439] In a 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;

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

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

[0442] In a case where the DSAP configuration information does not include the first indication information, the DSAP configuration information includes the packetization parameter but does not include the fragmentation permission parameter, or the DSAP configuration information does not include the packetization parameter but includes the fragmentation permission parameter;

[0443] In the case where the DSAP configuration information includes the fragmentation permission parameter, the DSAP configuration information includes or does not include the fragmentation permission multiple.

[0444] In some embodiments, the S330 includes:

[0445] The second device depackets 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;

[0446] The DSAP subheader of the first DSAP sub PDU includes a field carrying a length for indicating a payload in the first DSAP sub PDU.

[0447] In some embodiments, the S330 includes:

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

[0449] In some embodiments, the S330 includes:

[0450] The second device depackets the first DSAP sub PDU based on the fragmentation permission parameter in the DSAP configuration information through the first DSAP entity to obtain the first data plane data; or

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

[0452] 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:

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

[0454] The DSAP subheader includes a field for carrying segmentation information;

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

[0456] 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:

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

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

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

[0460] In some embodiments, when the first DSAP entity unpacks the first DSAP sub PDU based on the fragmentation permission parameter, the DSAP subheader includes a field carrying a length of a payload in the first DSAP sub PDU or a value used in the value list; or

[0461] When the first DSAP entity decapsulates the first DSAP sub PDU based on the fragmentation permission parameter and the fragmentation permission multiple, the DSAP subheader includes a field carrying a length for indicating the length of the payload in the first DSAP sub PDU.

[0462] In some embodiments, the DSAP subheader includes or does not include a field carrying a subsequence number for indicating the first DSAP sub PDU.

[0463] In some embodiments, when the transmission mode of the DSAP layer is AM or UM-A, the DSAP subheader of the first DSAP sub PDU includes a field carrying a signal for indicating whether to perform information feedback.

[0464] In some embodiments, the DSAP subheader of the first DSAP sub PDU includes at least one of the following:

[0465] a domain carrying the identifier of the first DSAP entity;

[0466] a field carrying a service identifier of the first data plane data;

[0467] Carrying a field for indicating whether the first DSAP sub PDU is a control packet or a data packet;

[0468] a field carrying a sequence number indicating the first DSAP sub PDU;

[0469] The DSAP sub PDU carries a field for integrity protection and verification of the first DSAP sub PDU.

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

[0471] 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 a buffer size of the BSR group.

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

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

[0474] The second device obtains a first buffer size report BSR by unpacking the second DSAP sub PDU:

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

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

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

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

[0479] In a case where 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;

[0480] In the case where the first BSR is a 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.

[0481] 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:

[0482] Carrying a field for indicating that the second DSAP sub PDU is a control packet or a data packet;

[0483] The field carries a field for indicating the type of the second DSAP sub PDU.

[0484] In some embodiments, the S330 includes:

[0485] The second device obtains the first data plane data by unpacking the first DSAP sub PDU through the first DSAP entity and performing at least one of the following: decryption, data packet reassembly, and integrity verification.

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

[0487] Unconfirmed serial number;

[0488] Unconfirmed start sequence number and unconfirmed end sequence number;

[0489] an unconfirmed sequence number and an unconfirmed subsequence number within the unconfirmed sequence number;

[0490] An unconfirmed first sequence number, an unconfirmed starting subsequence number in the first sequence number, an unconfirmed second sequence number, and an unconfirmed ending subsequence number in the second sequence number.

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

[0492] a domain carrying the identifier of the first DSAP entity;

[0493] a field carrying a service identifier of the first data plane data;

[0494] Carrying a field for indicating that the third DSAP sub PDU is a control packet or a data packet;

[0495] A field carrying a type of the third DSAP sub PDU;

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

[0497] A field that carries confirmation information;

[0498] The data frame carries 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.

[0499] It should be understood that the description of the relevant terms and schemes of the method 300 can refer to the description of the method 200 and the above-mentioned embodiments. To avoid repetition, they will not be repeated here.

[0500] The data processing method provided in the embodiment of the present application can be executed by a data processing device. In the embodiment of the present application, the data processing device provided in the embodiment of the present application is described by taking the data processing method executed by the data processing device as an example.

[0501] FIG21 shows a schematic block diagram of a data processing device 410 according to an embodiment of the present application.

[0502] As shown in FIG21 , the data processing device 410 includes:

[0503] The processing unit 411 is configured to packetize 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;

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

[0505] 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 identifier LCID corresponding to the first DSAP entity.

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

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

[0508] In some embodiments, the at least one LCID is a plurality of LCIDs corresponding to a plurality of types, and the plurality of types include at least one of the following: at least one business type, and at least one end-to-end type.

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

[0510] receiving the first DSAPPDU from the DSAP layer via the MAC layer and at least one of:

[0511] Packet Data Convergence Protocol PDCP layer, Radio Link Control RLC layer;

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

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

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

[0515] At least one DSAP entity identifier;

[0516] At least one business identifier;

[0517] At least one LCID;

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

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

[0520] Priority of DSAP entity;

[0521] Uplink data source;

[0522] Downlink data purpose;

[0523] Instruction on whether to encrypt or decrypt;

[0524] security algorithms used for encryption;

[0525] Indication of whether integrity protection is enabled;

[0526] Security algorithms for integrity protection;

[0527] Instruction on whether to decrypt;

[0528] Transmission mode;

[0529] First indication information indicating whether segmentation is allowed;

[0530] Package parameters;

[0531] Segmentation allowed parameters;

[0532] Multiples are allowed for segments;

[0533] Instructions on whether submission is in order;

[0534] An indication of whether to compress;

[0535] Compression algorithm;

[0536] an indication of whether to repeat the transmission;

[0537] Buffer Status Report (BSR) group identifier.

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

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

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

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

[0542] In a 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;

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

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

[0545] In a case where the DSAP configuration information does not include the first indication information, the DSAP configuration information includes the packetization parameter but does not include the fragmentation permission parameter, or the DSAP configuration information does not include the packetization parameter but includes the fragmentation permission parameter;

[0546] In the case where the DSAP configuration information includes the fragmentation permission parameter, the DSAP configuration information includes or does not include the fragmentation permission multiple.

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

[0548] performing, by the first DSAP entity, unsegmented packetization or segmented packetization on the first data plane data based on the first indication information in the DSAP configuration information, to obtain the first DSAP sub PDU;

[0549] The DSAP subheader of the first DSAP sub PDU includes a field carrying a length for indicating a payload in the first DSAP sub PDU.

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

[0551] The first data plane data is non-segmentedly packetized through the first DSAP entity based on the packetization parameters in the DSAP configuration information to obtain the first DSAP sub PDU.

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

[0553] performing, by the first DSAP entity, unsegmented packetization or segmented packetization on the first data plane data based on a segmentation permission parameter in the DSAP configuration information to obtain the first DSAP sub PDU; or

[0554] The first DSAP sub PDU is obtained by performing unsegmented or segmented packetization on the first data plane data based on the segmentation permission parameter and the segmentation permission multiple in the DSAP configuration information through the first DSAP entity.

[0555] 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:

[0556] When the first device performs unsegmented packetization on the first data plane data, the DSAP subheader of the first DSAP sub PDU includes a field for carrying segmentation information and a field for indicating the length of the payload in the first DSAP sub PDU;

[0557] In a case where the first device segments 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 subheader includes a field for carrying segmentation information;

[0558] When the first device segments and packages the first data plane data, and the payload in the first DSAP sub PDU is the last data packet, the DSAP subheader includes a field for carrying segmentation information and a field for indicating the length of the payload in the first DSAP sub PDU.

[0559] 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:

[0560] When the first device performs unsegmented packetization on the first data plane data, the DSAP subheader of the first DSAP sub PDU includes a field for carrying segmentation information and a field for indicating the length of the payload in the first DSAP sub PDU;

[0561] When the first device segments 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 subheader includes 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;

[0562] When the first device segments and packages the first data plane data, and the payload in the first DSAP sub PDU is the last data packet, the DSAP subheader includes a field for carrying segmentation information and a field for indicating the length of the payload in the first DSAP sub PDU.

[0563] In some embodiments, when the first DSAP entity segments 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 subheader includes a field carrying a length of the payload in the first DSAP sub PDU or a value used in the value list; or

[0564] When the first DSAP entity segments 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 subheader includes a field carrying a length for indicating the length of the payload in the first DSAP sub PDU.

[0565] In some embodiments, when the first data plane data is segmented 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 subheader includes a field carrying a subsequence number for indicating the first DSAP sub PDU; or

[0566] When the first data plane data is segmented and the payload in the first DSAP sub PDU is the first data packet or the last data packet, the DSAP subheader includes or does not include a field carrying a subsequence number for indicating the first DSAP sub PDU.

[0567] In some embodiments, when the transmission mode of the DSAP layer is AM or UM-A, the DSAP subheader of the first DSAP sub PDU includes a field carrying a signal for indicating whether to perform information feedback.

[0568] In some embodiments, the DSAP subheader of the first DSAP sub PDU includes at least one of the following:

[0569] a domain carrying the identifier of the first DSAP entity;

[0570] a field carrying a service identifier of the first data plane data;

[0571] Carrying a field for indicating whether the first DSAP sub PDU is a control packet or a data packet;

[0572] a field carrying a sequence number indicating the first DSAP sub PDU;

[0573] The DSAP sub PDU carries a field for integrity protection and verification of the first DSAP sub PDU.

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

[0575] receiving packet assembly indication information from the MAC layer through the DSAP layer;

[0576] The first data plane data is packetized by the first DSAP entity within the size indicated by the packetization indication information to obtain the first DSAP sub PDU.

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

[0578] When the first DSAP entity cannot complete packetization of the data plane data to be sent within the size indicated by the packetization indication information, sending a buffer size report (BSR) indication to the MAC layer through the DSAP layer, where the BSR indication includes a BSR group identifier and a buffer size of the BSR group;

[0579] The processing unit 411 is further configured to: perform packetization based on the BSR indication through the MAC layer 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 an identifier of a buffer status report BSR group and a field carrying a buffer size of the BSR group.

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

[0581] If the first DSAP entity cannot complete packetization of the first data plane data within the size indicated by the packetization indication information, the first DSAP entity packets the first buffer size report BSR to obtain a second DSAP sub PDU:

[0582] 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 DSAPPDU includes the second DSAP sub PDU.

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

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

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

[0586] In a case where 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;

[0587] In the case where the first BSR is a 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.

[0588] 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:

[0589] Carrying a field for indicating that the second DSAP sub PDU is a control packet or a data packet;

[0590] The field carries a field for indicating the type of the second DSAP sub PDU.

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

[0592] The first DSAP sub PDU is obtained by packetizing the first data plane data through the first DSAP entity and performing at least one of the following: desensitization, encryption, notifying the MAC layer of the amount of data to be sent by the DSAP layer, and integrity protection.

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

[0594] Unconfirmed serial number;

[0595] Unconfirmed start sequence number and unconfirmed end sequence number;

[0596] an unconfirmed sequence number and an unconfirmed subsequence number within the unconfirmed sequence number;

[0597] An unconfirmed first sequence number, an unconfirmed starting subsequence number in the first sequence number, an unconfirmed second sequence number, and an unconfirmed ending subsequence number in the second sequence number.

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

[0599] a domain carrying the identifier of the first DSAP entity;

[0600] a field carrying a service identifier of the first data plane data;

[0601] Carrying a field for indicating that the third DSAP sub PDU is a control packet or a data packet;

[0602] A field carrying a type of the third DSAP sub PDU;

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

[0604] A field that carries confirmation information;

[0605] The data frame carries 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.

[0606] It should be understood that the data processing device 410 provided in the embodiment of the present application may correspond to the first device in the method embodiment of the present application, and the above-mentioned (or other) operations or functions of each unit in the data processing device 410 are respectively for implementing the corresponding processes executed by the first device in the method embodiment shown in Figure 4. In order to avoid repetition, they will not be described here.

[0607] FIG22 shows a schematic block diagram of a data processing device 420 according to an embodiment of the present application.

[0608] As shown in FIG22 , the data processing device 420 includes:

[0609] a processing unit 421 configured to decapsulate, through a media access control (MAC) layer, a first media access control sub-protocol data unit (MAC sub PDU) to obtain a first data service adaptation protocol (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);

[0610] a communication unit 422 configured to receive the first DSAP sub PDU from the MAC layer via a first DSAP entity corresponding to the first LCID in the DSAP layer;

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

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

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

[0614] In some embodiments, the at least one LCID is a plurality of LCIDs corresponding to a plurality of types, and the plurality of types include at least one of the following: at least one business type, and at least one end-to-end type.

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

[0616] receiving the first DSAP sub PDU from the MAC layer via the first DSAP entity and at least one of:

[0617] Packet Data Convergence Protocol PDCP layer, Radio Link Control RLC layer;

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

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

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

[0621] At least one DSAP entity identifier;

[0622] At least one business identifier;

[0623] At least one LCID;

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

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

[0626] Priority of DSAP entity;

[0627] Uplink data source;

[0628] Downlink data purpose;

[0629] Instruction on whether to encrypt or decrypt;

[0630] security algorithms used for encryption;

[0631] Indication of whether integrity protection is enabled;

[0632] Security algorithms for integrity protection;

[0633] Instruction on whether to decrypt;

[0634] Transmission mode;

[0635] First indication information indicating whether segmentation is allowed;

[0636] Package parameters;

[0637] Segmentation allowed parameters;

[0638] Multiples are allowed for segments;

[0639] Instructions on whether submission is in order;

[0640] An indication of whether to compress;

[0641] Compression algorithm;

[0642] an indication of whether to repeat the transmission;

[0643] Buffer Status Report (BSR) group identifier.

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

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

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

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

[0648] In a 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;

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

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

[0651] In a case where the DSAP configuration information does not include the first indication information, the DSAP configuration information includes the packetization parameter but does not include the fragmentation permission parameter, or the DSAP configuration information does not include the packetization parameter but includes the fragmentation permission parameter;

[0652] In the case where the DSAP configuration information includes the fragmentation permission parameter, the DSAP configuration information includes or does not include the fragmentation permission multiple.

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

[0654] unpacking the first DSAP sub PDU based on the first indication information in the DSAP configuration information through the first DSAP entity to obtain the first data plane data;

[0655] The DSAP subheader of the first DSAP sub PDU includes a field carrying a length for indicating a payload in the first DSAP sub PDU.

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

[0657] The first DSAP sub PDU is unpacked through the first DSAP entity based on the packetization parameters in the DSAP configuration information to obtain the first data plane data.

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

[0659] Unpacking the first DSAP sub PDU based on the fragmentation permission parameter in the DSAP configuration information through the first DSAP entity to obtain the first data plane data; or

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

[0661] 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:

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

[0663] The DSAP subheader includes a field for carrying segmentation information;

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

[0665] 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:

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

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

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

[0669] In some embodiments, when the first DSAP entity unpacks the first DSAP sub PDU based on the fragmentation permission parameter, the DSAP subheader includes a field carrying a length of a payload in the first DSAP sub PDU or a value used in the value list; or

[0670] When the first DSAP entity decapsulates the first DSAP sub PDU based on the fragmentation permission parameter and the fragmentation permission multiple, the DSAP subheader includes a field carrying a length for indicating the length of the payload in the first DSAP sub PDU.

[0671] In some embodiments, the DSAP subheader includes or does not include a field carrying a subsequence number for indicating the first DSAP sub PDU.

[0672] In some embodiments, when the transmission mode of the DSAP layer is AM or UM-A, the DSAP subheader of the first DSAP sub PDU includes a field carrying a signal for indicating whether to perform information feedback.

[0673] In some embodiments, the DSAP subheader of the first DSAP sub PDU includes at least one of the following:

[0674] a domain carrying the identifier of the first DSAP entity;

[0675] a field carrying a service identifier of the first data plane data;

[0676] Carrying a field for indicating whether the first DSAP sub PDU is a control packet or a data packet;

[0677] a field carrying a sequence number indicating the first DSAP sub PDU;

[0678] The DSAP sub PDU carries a field for integrity protection and verification of the first DSAP sub PDU.

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

[0680] A second MAC sub PDU is received 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 a buffer size of the BSR group.

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

[0682] receiving, through the first DSAP entity, a second DSAP sub PDU from the MAC layer;

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

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

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

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

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

[0688] In a case where 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;

[0689] In the case where the first BSR is a 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.

[0690] 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:

[0691] Carrying a field for indicating that the second DSAP sub PDU is a control packet or a data packet;

[0692] The field carries a field for indicating the type of the second DSAP sub PDU.

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

[0694] The first data plane data is obtained by unpacking the first DSAP sub PDU through the first DSAP entity and performing at least one of the following: decryption, data packet reassembly, and integrity verification.

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

[0696] Unconfirmed serial number;

[0697] Unconfirmed start sequence number and unconfirmed end sequence number;

[0698] an unconfirmed sequence number and an unconfirmed subsequence number within the unconfirmed sequence number;

[0699] An unconfirmed first sequence number, an unconfirmed starting subsequence number in the first sequence number, an unconfirmed second sequence number, and an unconfirmed ending subsequence number in the second sequence number.

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

[0701] a domain carrying the identifier of the first DSAP entity;

[0702] a field carrying a service identifier of the first data plane data;

[0703] Carrying a field for indicating that the third DSAP sub PDU is a control packet or a data packet;

[0704] A field carrying a type of the third DSAP sub PDU;

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

[0706] A field that carries confirmation information;

[0707] The data frame carries 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.

[0708] It should be understood that the data processing device 420 provided in the embodiment of the present application may correspond to the second device in the method embodiment of the present application, and the above-mentioned (or other) operations or functions of each unit in the data processing device 420 are respectively for realizing the corresponding process of the second device in the method embodiment shown in Figure 20. In order to avoid repetition, they will not be described here.

[0709] The data processing device in the embodiment of the present application can 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 can be a first device or a second device, or a device other than a terminal. The first device can be a terminal or a network-side device, and the second device can be a network-side device or a terminal. For example, the terminal can include but is not limited to the types of terminals 11 listed above, the network-side device can include but is not limited to the types of network-side devices 12 listed above, and the other devices can be servers, network attached storage (NAS), etc., which are not specifically limited in the embodiment of the present application.

[0710] The data processing device provided in the embodiment of the present application can implement the various processes involved in the method embodiment shown in Figure 4 or Figure 20 and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0711] FIG23 is an example of a communication device 500 provided in an embodiment of the present application.

[0712] As shown in Figure 23, the communication device 500 includes a processor 501 and a memory 502. The memory 502 stores a program or instruction that can be run on the processor 501. When the program or instruction is executed by the processor 501, the various steps of the above-mentioned data processing method embodiment are implemented. For example, when the communication device 500 is a first device, when the program or instruction is executed by the processor 501, the various steps of the above-mentioned data processing method embodiment performed by the first device are implemented, and the same technical effect can be achieved. When the communication device 500 is a second device, when the program or instruction is executed by the processor 501, the various steps of the above-mentioned data processing method embodiment performed by the second device are implemented, and the same technical effect can be achieved. To avoid repetition, they are not described here.

[0713] The present application also provides a first device, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is configured to execute a program or instruction to implement the steps in the method embodiment shown in FIG4 . The embodiment of the first device corresponds to the method embodiment of the first device, and each implementation process and implementation method of the aforementioned method embodiment are applicable to the embodiment of the first device and can achieve the same technical effects.

[0714] The present application also provides a second device, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is configured to execute a program or instruction to implement the steps of the method embodiment shown in FIG20 . The embodiment of the second device corresponds to the method embodiment of the second device, and each implementation process and implementation method of the aforementioned method embodiment are applicable to the embodiment of the second device and can achieve the same technical effects.

[0715] FIG24 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of the present application.

[0716] As shown in Figure 24, the terminal 600 includes but is not limited to: 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 at least some of the components of the processor 610.

[0717] Those skilled in the art will appreciate that the terminal 600 may also include a power supply (such as a battery) to power various components. The power supply may be logically connected to the processor 610 through a power management system, thereby implementing functions such as charging, discharging, and power consumption management through the power management system. The terminal structure shown in Figure 24 does not constitute a limitation of the terminal. The terminal may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be described in detail here.

[0718] It should be understood that in an embodiment of the present application, the input unit 604 may include a graphics processing unit (GPU) 6041 and a microphone 6042, and the graphics processor 6041 processes the image data of a static picture or video 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 a touch panel 6071 and at least one of other input devices 6072. The touch panel 6071 is also called a touch screen. The touch panel 6071 may include two parts: a touch detection device and a touch controller. 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, and a joystick, which will not be repeated here.

[0719] In the embodiment of the present application, after receiving downlink data from a network-side device, the radio frequency unit 601 may transmit the data to the processor 610 for processing. Furthermore, the radio frequency unit 601 may send uplink data to the network-side device. Typically, 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, and the like.

[0720] 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, wherein the first storage area may store an operating system, applications 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 a volatile memory or a 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 (DDRSDRAM), an enhanced synchronous dynamic random access memory (ESDRAM), a synchronous link dynamic random access memory (SLDRAM), and a direct memory bus random access memory (DRRAM). The memory 609 in the embodiment of the present application includes but is not limited to these and any other suitable types of memory.

[0721] Processor 610 may include one or at least two processing units. Optionally, processor 610 integrates an application processor and a modem processor. The application processor primarily handles operations related to the operating system, user interface, and application programs, while the modem processor primarily processes wireless communication signals, such as a baseband processor. It is understood that the modem processor may not be integrated into processor 610.

[0722] In one implementation, the terminal 600 is a first device. In this case, the processor 610 is used to packetize the first data plane data through the 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 used to receive 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 processor 610 is also used 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.

[0723] In another implementation, the terminal 600 is a second device. In this case, the processor 610 is configured to decapsulate 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 (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). 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 decapsulate 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 PDSCH to obtain a MAC PDU, which includes the first MAC sub PDU.

[0724] In this embodiment, the first data plane data is directly packetized by the first DSAP entity, and the first MAC sub PDU obtained after the first DSAPPDU is packetized by the MAC layer includes the first LCID corresponding to the first DSAP entity. As a result, the DSAP layer and the MAC layer can communicate directly, which can reduce the end-to-end data delay, for example, it can reduce the transmission delay and processing delay, and thus improve the communication performance.

[0725] It can be understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of the method embodiment and achieve the same or corresponding technical effects. To avoid repetition, it will not be described here.

[0726] FIG25 is an example of a network-side device 700 provided in an embodiment of the present application.

[0727] As shown in Figure 25, network-side device 700 includes an antenna 71, a radio frequency device 72, a baseband device 73, a processor 74, and a memory 75. Antenna 71 is connected to radio frequency device 72. In the uplink direction, radio frequency device 72 receives information via antenna 71 and sends the received information to baseband device 73 for processing. In the downlink direction, baseband device 73 processes the information to be transmitted and sends it to radio frequency device 72. Radio frequency device 72 processes the received information and then sends it through antenna 71.

[0728] The method executed by the network-side device in the above embodiment may be implemented in the baseband device 73 , which includes a baseband processor.

[0729] The baseband device 73 may include, for example, at least one baseband board, on which at least two chips are arranged, as shown in Figure 15, 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 process of the network side device in the above method embodiment.

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

[0731] Specifically, the network side device 700 of the embodiment of the present application also includes: instructions or programs stored in the memory 75 and can be run on the processor 74. The processor 74 calls the instructions or programs in the memory 75 to execute the steps performed by each unit in the data processing device shown in Figure 21 or 22, and achieves the same technical effect. To avoid repetition, it will not be repeated here.

[0732] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, the various processes of the above-mentioned data processing method embodiment are implemented and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0733] The processor is the processor in the terminal described in the above embodiment. 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 disk. In some examples, the readable storage medium may be a non-transitory readable storage medium.

[0734] An embodiment of the present application also provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned data processing method embodiment and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0735] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0736] An embodiment of the present application also 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 the various processes of the above-mentioned data processing method embodiment and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0737] An embodiment of the present application also provides a communication system, including: a first device and a second device, wherein 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.

[0738] It should be noted that, in this article, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device comprising a series of elements includes not only those elements, but also includes other elements that are not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a..." does not exclude the presence of other identical elements in the process, method, article or device comprising 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 the opposite order according to the functions involved. For example, the described method may be performed in an order different from that described, and various steps may also be added, omitted or combined. In addition, the features described with reference to certain examples may be combined in other examples.

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

[0740] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of this application, ordinary technicians in this field can also make many forms of implementation methods without departing from the purpose of this application and the scope of protection of the claims. These implementation methods are all within the protection of this application.

Claims

1. A data processing method, wherein: include: The first device packages 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; The first device receives 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 first device assembles the first DSAPPDU 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.

2. The method according to claim 1, wherein: The first DSAP entity is a DSAP entity in the DSAP layer corresponding to the service identifier of the first data plane data.

3. The method according to claim 1 or 2, wherein: 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, wherein: The at least one LCID is a plurality of LCIDs corresponding to a plurality of types, and the plurality of types include at least one of the following: at least one service type and at least one end-to-end type.

5. The method according to any one of claims 1 to 4, wherein: The first device receives a first DSAP PDU from the DSAP layer through a media access control MAC layer, including: The first device receives the first DSAP PDU from the DSAP layer via the MAC layer and at least one of: Packet Data Convergence Protocol PDCP layer, Radio Link Layer Control RLC layer; The PDCP layer is configured not to process data on the data plane, and the transmission mode of the RLC layer is configured as a transparent mode.

6. The method according to any one of claims 1 to 5, wherein: The method further comprises: The first device acquires 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 business 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; The priority of the DSAP entity; Uplink data source; Downlink data purpose; Instruction on whether to encrypt or decrypt; Security algorithms used for encryption; Indication of whether integrity protection is enabled; Security algorithms for integrity protection; Instruction on whether to decrypt; Transmission mode; First indication information indicating whether segmentation is allowed; Package parameters; Segmentation allowed parameters; Multiples are allowed for segmentation; Instructions on whether to submit in order; An indication of whether to compress; Compression algorithm; an indication of whether to repeat the transmission; The identifier of the buffer status report (BSR) group.

7. The method according to claim 6, 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; 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, wherein: The DSAP configuration information satisfies at least one of the following: In a 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 packetization parameter; In the case where the first indication information indicates that segmentation is allowed, the DSAP configuration information includes the segmentation permission parameter; In the case where the DSAP configuration information does not include the first indication information, the DSAP configuration information includes the packetization parameter and does not include the segmentation permission parameter, or the DSAP configuration information does not include the packetization parameter and includes the segmentation permission parameter; In the case where the DSAP configuration information includes the segmentation permission parameter, the DSAP configuration information includes or does not include the segmentation permission multiple.

9. The method according to any one of claims 1 to 8, wherein: The first device packages 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, through the first DSAP entity, performs unsegmented packetization or segmented packetization on the first data plane data based on the first indication information in the DSAP configuration information to obtain the first DSAP sub PDU; The DSAP subheader of the first DSAP sub PDU includes a field carrying a length for indicating a payload in the first DSAP sub PDU.

10. The method according to any one of claims 1 to 8, wherein: The first device packages 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, through the first DSAP entity, unsegmentally packages the first data plane data based on the package 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, wherein: The first device packages 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, through the first DSAP entity, performs unsegmented packetization or segmented packetization on the first data plane data based on the segmentation permission parameter in the DSAP configuration information to obtain the first DSAP sub PDU; or The first device, through the first DSAP entity, performs unsegmented or segmented packetization on the first data plane data based on the segmentation permission parameter and the segmentation permission 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 permission parameter is a unique value; wherein the first DSAP sub PDU satisfies any one of the following: In the case where the first device performs unsegmented packetization on the first data plane data, the DSAP subheader of the first DSAP sub PDU includes a field for carrying segmentation information and a field for indicating the length of the payload in the first DSAP sub PDU; In the case where the first device performs segmented packetization 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 subheader includes a field for carrying segmentation information; When the first device segments and packages the first data plane data, and the payload in the first DSAP sub PDU is the last data packet, the DSAP subheader includes a field for carrying segmentation information and a field for indicating the length of the payload in the first DSAP sub PDU.

13. The method according to claim 11, wherein: The value of the segmentation permission parameter is a value list; wherein the first DSAP sub PDU satisfies any one of the following: In the case where the first device performs unsegmented packetization on the first data plane data, the DSAP subheader of the first DSAP sub PDU includes a field for carrying segmentation information and a field for indicating the length of the payload in the first DSAP sub PDU; In a case where the first device performs segmented packetization 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 subheader includes a field for carrying segmentation information, and a field for carrying a length indicating the payload in the first DSAP sub PDU or a value used in the value list; When the first device segments and packages the first data plane data, and the payload in the first DSAP sub PDU is the last data packet, the DSAP subheader includes a field for carrying segmentation information and a field for indicating the length of the payload in the first DSAP sub PDU.

14. The method according to claim 13, wherein: In a case where the first DSAP entity segments 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 subheader includes a field carrying a length of the payload in the first DSAP sub PDU or a value used in the value list; or When the first DSAP entity segments 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 subheader includes a field carrying a length for indicating the payload in the first DSAP sub PDU.

15. The method according to any one of claims 12 to 14, wherein: In the case where the first data plane data is segmented 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 subheader includes a field carrying a subsequence number for indicating the first DSAP sub PDU; or In the case where the first data plane data is segmented and the payload in the first DSAP sub PDU is the first data packet or the last data packet, the DSAP subheader includes or does not include a field carrying a subsequence number for indicating the first DSAP sub PDU.

16. The method according to any one of claims 9 to 15, wherein: In the case where the transmission mode of the DSAP layer is AM or UM-A, the DSAP subheader of the first DSAP sub PDU includes a field carrying a signal for indicating whether to perform information feedback.

17. The method according to any one of claims 9 to 16, wherein: The DSAP subheader of the first DSAP sub PDU includes at least one of the following: a domain carrying an identifier of the first DSAP entity; a domain carrying a service identifier of the first data plane data; Carrying a field for indicating that the first DSAP sub PDU is a control packet or a data packet; A field carrying a sequence number indicating the first DSAP sub PDU; The carrier carries a field for performing integrity protection and verification on the first DSAP sub PDU.

18. The method according to any one of claims 1 to 17, wherein: The first device packages 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 packet assembly indication information from the MAC layer through the DSAP layer; Within the size indicated by the packetization indication information, the first device packets 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 comprises: In a case where the first DSAP entity cannot 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, where the BSR indication includes an identifier of a BSR group and a buffer size of the BSR group; The first device performs packetization through the MAC layer based on the BSR indication to obtain a second MAC sub PDU, wherein 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 a buffer size of the BSR group.

20. The method according to claim 18, wherein: The method further comprises: In a case where the first DSAP entity cannot complete packetization of the first data plane data within the size indicated by the packetization indication information, the first device packets the first buffer size report BSR through the first DSAP entity to obtain a second DSAP sub PDU: 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 DSAPPDU 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: 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 field for identifying that the second DSAP sub PDU is a DSAP BSR and a field carrying a buffer size of the first LCID; 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; In the case where 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; In the case where the first BSR is a BSR of a 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 a service identifier of the first data plane data.

22. The method according to claim 20 or 21, wherein: In the case where the first BSR is a BSR of the first DSAP entity or a BSR of a service identifier of the first data plane data, the second DSAP sub PDU further includes at least one of the following: Carrying a field for indicating that the second DSAP sub PDU is a control packet or a data packet; The carrier carries a field used to indicate the type of the second DSAP sub PDU.

23. The method according to any one of claims 1 to 22, wherein: The first device packages 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 obtains the first DSAP sub PDU by packetizing the first data plane data through the first DSAP entity and performing at least one of the following: desensitizing, encryption, notifying the MAC layer of the amount of data to be sent at the DSAP layer, and integrity protection.

24. The method according to any one of claims 1 to 23, wherein: The first DSAP PDU includes a third DSAP sub PDU, the third DSAP sub PDU includes a field carrying a type of status report and a field carrying a status report, and the type of status report includes at least one of the following: Unconfirmed sequence number; Unconfirmed start sequence number and unconfirmed end sequence number; an unconfirmed sequence number and an unconfirmed subsequence number of the unconfirmed sequence number; An unconfirmed first sequence number, an unconfirmed starting subsequence number in the first sequence number, an unconfirmed second sequence number, and an unconfirmed ending subsequence 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 domain carrying an identifier of the first DSAP entity; a domain carrying a service identifier of the first data plane data; Carrying a field for indicating that the third DSAP sub PDU is a control packet or a data packet; A field carrying a type of the third DSAP sub PDU; A field carrying the length of the status report field; A field that carries confirmation information; The data frame carries 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, wherein: include: 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 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; 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; The second device unpacks the first DSAP sub PDU through the first DSAP entity to obtain first data plane data.

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

28. The method according to claim 26 or 27, wherein: 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 a plurality of LCIDs corresponding to a plurality of types, and the plurality of types include at least one of the following: at least one service type and at least one end-to-end type.

30. The method according to any one of claims 26 to 29, wherein: 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, including: The second device receives the first DSAP sub PDU from the MAC layer via the first DSAP entity and at least one of: Packet Data Convergence Protocol PDCP layer, Radio Link Layer Control RLC layer; The PDCP layer is configured not to process data on the data plane, and the transmission mode of the RLC layer is configured as a transparent mode.

31. The method according to any one of claims 26 to 30, wherein: The method further comprises: The second device obtains 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 business 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; The priority of the DSAP entity; Uplink data source; Downlink data purpose; Instruction on whether to encrypt or decrypt; Security algorithms used for encryption; Indication of whether integrity protection is enabled; Security algorithms for integrity protection; Instruction on whether to decrypt; Transmission mode; First indication information indicating whether segmentation is allowed; Package parameters; Segmentation allowed parameters; Multiples are allowed for segmentation; Instructions on whether to submit in order; An indication of whether to compress; Compression algorithm; an indication of whether to repeat the transmission; The 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; 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, wherein: The DSAP configuration information satisfies at least one of the following: In a 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 packetization parameter; In the case where the first indication information indicates that segmentation is allowed, the DSAP configuration information includes the segmentation permission parameter; In the case where the DSAP configuration information does not include the first indication information, the DSAP configuration information includes the packetization parameter and does not include the segmentation permission parameter, or the DSAP configuration information does not include the packetization parameter and includes the segmentation permission parameter; In the case where the DSAP configuration information includes the segmentation permission parameter, the DSAP configuration information includes or does not include the segmentation permission multiple.

34. A method according to any one of claims 26 to 33, wherein: 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; The DSAP subheader of the first DSAP sub PDU includes a field carrying a length for indicating a payload in the first DSAP sub PDU.

35. The method according to any one of claims 26 to 33, wherein: 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 packetization 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, wherein: 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 permission 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 permission parameter and the segmentation permission multiple in the DSAP configuration information to obtain the first data plane data.

37. The method of claim 36, wherein: The value of the segmentation permission parameter is a unique value; wherein the first DSAP sub PDU satisfies any one of the following: The DSAP subheader of the first DSAP sub PDU includes a field for carrying segmentation information and a field for indicating the length of the payload in the first DSAP sub PDU; The DSAP subheader includes a field for carrying segmentation information; The DSAP subheader includes a field for carrying segmentation information and a field for indicating the length of the payload in the first DSAP sub PDU.

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

39. The method of claim 38, wherein: In a case where the first DSAP entity unpacks the first DSAP sub PDU based on the segmentation permission parameter, the DSAP subheader includes a field carrying a length of a payload in the first DSAP sub PDU or a value used in the value list; or When the first DSAP entity unpacks the first DSAP sub PDU based on the fragmentation permission parameter and the fragmentation permission multiple, the DSAP subheader includes a field carrying a length for indicating the length of the payload in the first DSAP sub PDU.

40. The method according to any one of claims 37 to 39, wherein: The DSAP subheader includes or does not include a field carrying a subsequence number for indicating the first DSAP sub PDU.

41. A method according to any one of claims 34 to 40, wherein: In the case where the transmission mode of the DSAP layer is AM or UM-A, the DSAP subheader of the first DSAP sub PDU includes a field carrying a signal for indicating whether to perform information feedback.

42. The method according to any one of claims 34 to 41, wherein: The DSAP subheader of the first DSAP sub PDU includes at least one of the following: a domain carrying an identifier of the first DSAP entity; a domain carrying a service identifier of the first data plane data; Carrying a field for indicating that the first DSAP sub PDU is a control packet or a data packet; A field carrying a sequence number indicating the first DSAP sub PDU; The carrier carries 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, wherein: The method further comprises: 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 a buffer size of the BSR group.

44. The method according to any one of claims 26 to 42, wherein: The method further comprises: The second device receives a second DSAP sub PDU from the MAC layer through the first DSAP entity; The second device obtains a first buffer size report BSR by unpacking the second DSAP sub PDU: 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 of claim 44, wherein: The second DSAP sub PDU satisfies any one of the following: 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 field for identifying that the second DSAP sub PDU is a DSAP BSR and a field carrying a buffer size of the first LCID; 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; In the case where 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; In the case where the first BSR is a BSR of a 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 a service identifier of the first data plane data.

46. ​​The method according to claim 44 or 45, wherein: In the case where the first BSR is a BSR of the first DSAP entity or a BSR of a service identifier of the first data plane data, the second DSAP sub PDU further includes at least one of the following: Carrying a field for indicating that the second DSAP sub PDU is a control packet or a data packet; The carrier carries a field used to indicate the type of the second DSAP sub PDU.

47. The method according to any one of claims 26 to 46, wherein: The second device unpacks the first DSAP sub PDU through the first DSAP entity to obtain first data plane data, including: The second device obtains the first data plane data by unpacking the first DSAP sub PDU through the first DSAP entity and performing at least one of the following: decryption, data packet reassembly, and integrity verification.

48. The method according to any one of claims 26 to 47, wherein: The first DSAP PDU includes a third DSAP sub PDU, the third DSAP sub PDU includes a field carrying a type of status report and a field carrying a status report, and the type of status report includes at least one of the following: Unconfirmed sequence number; Unconfirmed start sequence number and unconfirmed end sequence number; an unconfirmed sequence number and an unconfirmed subsequence number of the unconfirmed sequence number; An unconfirmed first sequence number, an unconfirmed starting subsequence number in the first sequence number, an unconfirmed second sequence number, and an unconfirmed ending subsequence number in the second sequence number.

49. The method of claim 48, wherein: The third DSAP sub PDU further includes at least one of the following: a domain carrying an identifier of the first DSAP entity; a domain carrying a service identifier of the first data plane data; Carrying a field for indicating that the third DSAP sub PDU is a control packet or a data packet; A field carrying a type of the third DSAP sub PDU; A field carrying the length of the status report field; A field that carries confirmation information; The data frame carries 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, wherein: include: A processing unit, configured to packetize 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; a communication unit, configured to receive a first DSAP PDU from the DSAP layer through a media access control MAC layer, wherein the first DSAP PDU includes the first DSAP sub PDU; The processing unit is further used to: group 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 apparatus of claim 50, wherein: 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, wherein: 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, wherein: The communication unit is specifically used for: receiving the first DSAP PDU from the DSAP layer by the MAC layer and at least one of: Packet Data Convergence Protocol PDCP layer, Radio Link Layer Control RLC layer; The PDCP layer is configured not to process data on the data plane, 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, wherein: The communication unit is also used for: 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 business 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; The priority of the DSAP entity; Uplink data source; Downlink data purpose; Instruction on whether to encrypt or decrypt; Security algorithms used for encryption; Indication of whether integrity protection is enabled; Security algorithms for integrity protection; Instruction on whether to decrypt; Transmission mode; First indication information indicating whether segmentation is allowed; Package parameters; Segmentation allowed parameters; Multiples are allowed for segmentation; Instructions on whether to submit in order; An indication of whether to compress; Compression algorithm; an indication of whether to repeat the transmission; The identifier of the buffer status report (BSR) group.

55. A data processing device, wherein: include: a processing unit, 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, wherein 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 used to: unpack the first DSAP sub PDU through the first DSAP entity to obtain first data plane data.

56. The apparatus of claim 55, wherein: The first DSAP entity is a DSAP entity in the DSAP layer corresponding to the service identifier of the first data plane data.

57. The apparatus of claim 55 or 56, wherein: 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, wherein: The communication unit is specifically used for: receiving the first DSAP sub PDU from the MAC layer via the first DSAP entity and at least one of: Packet Data Convergence Protocol PDCP layer, Radio Link Layer Control RLC layer; The PDCP layer is configured not to process data on the data plane, and the transmission mode of the RLC layer is configured as a transparent mode.

59. The device according to any one of claims 55 to 58, wherein The communication unit is also used for: 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 business 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; The priority of the DSAP entity; Uplink data source; Downlink data purpose; Instruction on whether to encrypt or decrypt; Security algorithms used for encryption; Indication of whether integrity protection is enabled; Security algorithms for integrity protection; Instruction on whether to decrypt; Transmission mode; First indication information indicating whether segmentation is allowed; Package parameters; Segmentation allowed parameters; Multiples are allowed for segmentation; Instructions on whether to submit in order; An indication of whether to compress; Compression algorithm; an indication of whether to repeat the transmission; The identifier of the buffer status report (BSR) group.

60. A first device, wherein: The device comprises a transceiver, a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the data processing method according to any one of claims 1 to 25 is implemented.

61. A second device, wherein: It comprises a transceiver, a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the data processing method according to any one of claims 26 to 49 is implemented.

62. A readable storage medium, wherein: The readable storage medium stores programs or instructions, and when the programs or instructions are executed by the processor, they implement the data processing method according to any one of claims 1 to 25, or implement the data processing method according to any one of claims 26 to 49.

Images