User plane data transmission method and apparatus, communication device, and readable storage medium

Abstract

This application discloses a user plane data transmission method, apparatus, communication device, and readable storage medium, belonging to the field of wireless communication technology. The user plane data transmission method of this application includes: when the SDAP entity of a first device receives an SDAP PDU of a QoS flow indicated by a QFI or a new service task indicated by a task identifier from a lower layer, performing a first operation, the first operation including: retrieving an SDAP SDU from the SDAP PDU and transmitting the retrieved SDAP SDU to an upper layer; or, when the SDAP entity of the first device receives an SDAP SDU of a QoS flow indicated by a QFI or a new service task indicated by a task identifier from an upper layer, performing a second operation, the second operation including: constructing an SDAP PDU and submitting the constructed SDAP PDU to a lower layer; wherein the SDAP PDU is an SDAP PDU in a format supporting the new service.

Description

Technical Field

[0001] This application belongs to the field of wireless communication technology, and specifically relates to a user plane data transmission method, apparatus, communication device, and readable storage medium. Background Technology

[0002] Existing user plane protocols are primarily used to transmit application functions of user equipment (UE, also known as a terminal) and existing user plane data between the data network (DN). During existing user plane data transmission, transparently transmitted data is mapped to appropriate QoS streams and data radio bearers (DRBs) according to Quality of Service (QoS) rules. However, the new services of the sixth-generation mobile communication standard (6G) cause 6G networks to generate and transmit a large amount of new service data, which is different from the aforementioned existing user plane data. The requirements of the new service data (e.g., priority, endpoint, etc.) differ from those of existing user plane data, making it difficult for existing user plane protocols to support the transmission of this new service data. Summary of the Invention

[0003] This application provides a user plane data transmission method, apparatus, communication device, and readable storage medium, which can solve the problem that existing user plane protocols are unable to support new service data transmission.

[0004] Firstly, a user plane data transmission method is provided, including:

[0005] When the SDAP entity of the first device receives an SDAP PDU for a QoS flow indicated by a QFI or a new service task indicated by a task identifier from the lower layer, a first operation is performed, the first operation including: retrieving an SDAP SDU from the SDAP PDU and transmitting the retrieved SDAP SDU to the upper layer;

[0006] or,

[0007] When the SDAP entity of the first device receives an SDAP SDU for a QoS flow indicated by a QFI or a new service task indicated by a task identifier from the upper layer, a second operation is performed, the second operation including: constructing an SDAP PDU and submitting the constructed SDAP PDU to the lower layer;

[0008] The SDAP PDU is an SDAP PDU in a format that supports the new service.

[0009] Secondly, a user plane data transmission device is provided, comprising:

[0010] The processing module is configured to perform a first operation upon receiving an SDAP PDU for a QoS flow indicated by a QFI or a new service task indicated by a task identifier from a lower layer, the first operation comprising: retrieving an SDAPSDU from the SDAP PDU and transmitting the retrieved SDAP SDU to the upper layer; or, upon receiving an SDAP SDU for a QoS flow indicated by a QFI or a new service task indicated by a task identifier from an upper layer, performing a second operation comprising: constructing an SDAPPDU and submitting the constructed SDAP PDU to the lower layer;

[0011] The SDAP PDU is an SDAP PDU in a format that supports the new service.

[0012] Thirdly, a user plane data transmission apparatus is provided, the apparatus being configured to perform the steps of the user plane data transmission method as described in the first aspect.

[0013] Fourthly, a communication device is provided, the terminal including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the user plane data transmission method as described in the first aspect.

[0014] Fifthly, a communication device is provided, including a processor and a communication interface, wherein the processor is configured to perform a first operation upon receiving an SDAP PDU of a QoS stream indicated by a QFI or a new service task indicated by a task identifier from a lower layer, the first operation including: retrieving an SDAP SDU from the SDAP PDU and transmitting the retrieved SDAP SDU to an upper layer; or, upon receiving an SDAP SDU of a QoS stream indicated by a QFI or a new service task indicated by a task identifier from an upper layer, performing a second operation including: constructing an SDAP PDU and submitting the constructed SDAP PDU to the lower layer; wherein the SDAP PDU is an SDAP PDU in a format supporting new services.

[0015] In a sixth aspect, a readable storage medium is provided, on which a program or instructions are stored, which, when executed by a processor, implement the steps of the user plane data transmission method as described in the first aspect.

[0016] In a seventh aspect, a chip is provided, the chip including a processor and a communication interface, the communication interface being coupled to the processor, the processor being used to run programs or instructions to implement the steps of the user plane data transmission method as described in the first aspect.

[0017] Eighthly, 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 user plane data transmission method as described in the first aspect.

[0018] In this application embodiment, the processing method of new service data in the SDAP entity is clarified to meet the transmission requirements of new service data. Attached Figure Description

[0019] Figure 1 This is a block diagram of a wireless communication system applicable to embodiments of this application;

[0020] Figure 2 A schematic diagram of the user plane protocol stack between the UE and gNB;

[0021] Figure 3 A schematic diagram of the user plane protocol stack between the UE and UPF;

[0022] Figure 4 This is a schematic diagram of the data plane protocol stack between the UE and the network.

[0023] Figure 5 This is one of the flowcharts illustrating the user plane data transmission method according to an embodiment of this application;

[0024] Figure 6 This is a schematic diagram of a user plane protocol sublayer according to an embodiment of this application;

[0025] Figure 7 This is a second schematic flowchart of the user plane data transmission method according to an embodiment of this application;

[0026] Figure 8 This is a schematic diagram of Example 1 of the downlink SDAP data PDU in Embodiment 1 of this application;

[0027] Figure 9 This is a schematic diagram of Example 2 of the downlink SDAP data PDU in Embodiment 1 of this application;

[0028] Figure 10 This is a schematic diagram of Example 3 of the downlink SDAP data PDU in Embodiment 1 of this application;

[0029] Figure 11 This is a schematic diagram of Example 4 of the downlink SDAP data PDU in Embodiment 1 of this application;

[0030] Figure 12 This is a schematic diagram of Example 5 of the downlink SDAP data PDU in Embodiment 1 of this application;

[0031] Figure 13This is a schematic diagram of Example 6 of the downlink SDAP data PDU in Embodiment 1 of this application;

[0032] Figure 14 This is a schematic diagram of Example 1 of the uplink SDAP data PDU in Embodiment 2 of this application;

[0033] Figure 15 This is a schematic diagram of Example 2 of the uplink SDAP data PDU in Embodiment 2 of this application;

[0034] Figure 16 This is a schematic diagram of Example 3 of the uplink SDAP data PDU in Embodiment 2 of this application;

[0035] Figure 17 This is a schematic diagram of Example 4 of the uplink SDAP data PDU in Embodiment 2 of this application;

[0036] Figure 18 This is a schematic diagram of Example 5 of the uplink SDAP data PDU in Embodiment 2 of this application;

[0037] Figure 19 This is a schematic diagram of example 6 of the uplink SDAP data PDU in Embodiment 2 of this application;

[0038] Figure 20 This is a schematic diagram of example 7 of the uplink SDAP data PDU in Embodiment 2 of this application;

[0039] Figure 21 This is a schematic diagram of Example 1 of the downlink SDAP data PDU in Embodiment 3 of this application;

[0040] Figure 22 This is a schematic diagram of Example 2 of the downlink SDAP data PDU in Embodiment 3 of this application;

[0041] Figure 23 This is a schematic diagram of Example 3 of the downlink SDAP data PDU in Embodiment 3 of this application;

[0042] Figure 24 This is one of the structural schematic diagrams of a user plane data transmission device according to an embodiment of this application;

[0043] Figure 25 This is a second schematic diagram of the user plane data transmission device according to an embodiment of this application;

[0044] Figure 26 This is a schematic diagram of the structure of a communication device according to an embodiment of this application;

[0045] Figure 27 This is a schematic diagram of the hardware structure of a terminal according to an embodiment of this application;

[0046] Figure 28This is a schematic diagram of the hardware structure of a network-side device according to an embodiment of this application;

[0047] Figure 29 This is a schematic diagram of the hardware structure of a network-side device according to an embodiment of this application. Detailed Implementation

[0048] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0049] The terms "first," "second," etc., used in this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same class, not limited in number; for example, the first object can be one or more. Furthermore, "or" in this application indicates at least one of the connected objects. For example, the scope of protection for "A or B" covers at least three scenarios: Scenario 1: including A but not B; Scenario 2: including B but not A; Scenario 3: including both A and B. In addition, the terms "A and / or B," "at least one of A and B," and "at least one of A or B" also cover at least the above three scenarios. The character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0050] The term "instruction" in this application can be either a direct instruction (or explicit instruction) or an indirect instruction (or implicit instruction). A direct instruction can be understood as the sender explicitly informing the receiver of specific information, the required operation, or the requested result in the instruction sent. An indirect instruction 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 required operation or requested result based on the judgment result.

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

[0052] Figure 1This diagram illustrates a block diagram of a wireless communication system applicable to embodiments of this application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 can also be referred to as User Equipment (UE), and can 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), shipboard equipment, pedestrian user equipment (PUE), smart home devices (home appliances with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), game consoles, personal computers (PCs), ATMs, or self-service machines, etc. Wearable devices include: smartwatches, smart bracelets, smart earphones, smart glasses, smart jewelry (smart bracelets, smart chains, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among these, in-vehicle devices can also be referred to as in-vehicle terminals, in-vehicle controllers, in-vehicle modules, in-vehicle components, in-vehicle chips, or in-vehicle units, etc. It should be noted that the specific type of terminal 11 is not limited in this application embodiment. Network-side equipment 12 may include access network equipment or core network equipment, wherein access network equipment may also be referred to as Radio Access Network (RAN) equipment, radio access network function, or radio access network unit. Access network equipment may include base stations, Wireless Local Area Network (WLAN) access points (APs), or Wireless Fidelity (WiFi) nodes, etc.Among them, base stations can be referred to as Node B (NB), Evolved Node B (eNB), 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, Transmit / Receive Point (TRP), Non-Terrestrial Network (NTN) equipment (such as satellite or high altitude platform stations). The term "base station" can be any suitable term in the field, such as "station" or any other appropriate term in the relevant field, as long as the same technical effect is achieved. The term "base station" is not limited to specific technical terms. It should be noted that the embodiments of this application only use the base station in the NR system as an example for introduction, and do not limit the specific type of base station.

[0053] Core network equipment, also known as core network nodes, core network functions, or core network elements, includes, 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), and Binding Support. Functions include BSF, Application Function (AF), Location Management Function (LMF), Gateway Mobile Location Centre (GMLC), Network Data Analytics Function (NWDAF), and Non-Terrestrial Network (NTN) equipment (such as satellite or high altitude platform station).It should be noted that the embodiments of this application only use the core network equipment in the NR system as an example for introduction, and do not limit the specific type of core network equipment. If the name of the core network equipment mentioned in the embodiments of this application changes in subsequent protocol versions (e.g., 6G), it is also within the scope of protection of this application.

[0054] Optionally, the core network equipment can be implemented by one or more functional modules in a single device, or by multiple devices working together; this application does not specifically limit this. It is understood that the aforementioned functional modules can be network elements in hardware devices, software functional modules running on dedicated hardware, or virtualized functional modules instantiated on a platform (e.g., a cloud platform).

[0055] The following is a brief explanation of the technical terms used in this application.

[0056] 1. New Services

[0057] The convergence of communication and sensing, along with 6G applications such as Artificial Intelligence (AI) and communication, enables 6G networks to provide new services (such as sensing services, AI services, and computing services). These new services can be further categorized into external services and service networks based on their target audience. Taking sensing as an example, sensing services provided by 6G to external network functions such as application functions are called external sensing services; sensing services provided by 6G to core network functions, radio access network nodes, or user equipment (UE, also known as terminals) are called service networks.

[0058] The new services will generate a large amount of internal network data. This internal network data is typically transmitted not to external functions, but to core network functions, radio access network nodes, or UEs for use. Therefore, this type of data service is called a service network data service, also known as an internal data service. Regarding network exposure, data generated by the 6G network may also be sent to external network functions such as application functions; this is called an external data service.

[0059] 2. User Interface

[0060] 5G User Plane (UP) protocol stack such as Figure 2As shown, the air interface protocols between the UE and the Radio Access Network (RAN) include the Service Data Adaptation Protocol (SDAP), the Packet Data Convergence Protocol (PDCP), Radio Link Control (RLC), Media Access Control (MAC), and the Physical Layer (PHY). The SDAP sublayer is configured by Radio Resource Control (RRC) (TS38.331[3]), such as the uplink (UL) Quality of Service (QoS) flow to Data Radio Bearer (DRB) mapping rules. The SDAP sublayer maps QoS flows to DRBs. One or more QoS flows can be mapped to one DRB. In the UL, a QoS flow can only be mapped to one DRB at a time. Among them, SDAP provides the service of transmitting user plane data to the upper layer of the user plane, and SDAP expects the lower layer to provide the following services:

[0061] -User plane data transmission service;

[0062] - Deliver in order unless RRC is configured to deliver out of order (TS 38.331[3]).

[0063] The SDAP Protocol Data Unit (PDU) includes data PDUs and control PDUs. Its format and parameters are detailed in TS 37.324.

[0064] Please refer to Figure 3 The core network UPF's main function is to respond to SMF requests. As the connection point between the RAN and the data network (DN), the PDU session anchor is responsible for handling network user plane processing such as encapsulation and decapsulation of the GPRS Tunneling Protocol User Plane (GTP-U) protocol, packet routing and forwarding, packet inspection, and QoS flow mapping. It also implements user plane gating, redirection, and traffic redirection policies and rules. Simultaneously, it provides user traffic collection interfaces and traffic usage reports for billing and legitimate interception.

[0065] 3. Data plane

[0066] Because sensing / AI data is characterized by large volume, flexible endpoints, and flexible priorities, and because multi-UE data and UE and base station data can have their volume reduced or their quality improved through preprocessing at the base station, a data plane can be introduced in 6G networks to collect, transmit, and process the aforementioned internal network data. The data plane is a protocol stack used for data collection and transmission within the mobile network. Introducing a data plane function (DPF) in the core network, the underlying transport protocol between the RAN and the core network in 5G is either Stream Control Transmission Protocol (SCTP) / Internet Protocol (IP), GTP-U / User Datagram Protocol (UDP) / IP, or a UDP-based transport layer protocol (Quick UDP Internet Connections, QUIC) / UDP / IP, etc.

[0067] A data plane protocol stack between a UE and the network, such as Figure 4 As shown, data plane data is forwarded via the core network DPF and other functions.

[0068] 4. Sensing Data

[0069] Sensing data is generated by the UE or base station and can also be called sensing measurement data or sensing result.

[0070] Regarding sensing measurement data, one possible classification method is to divide the sensing measurements into the following four categories (this description focuses on the measurement quantities; it can also be divided into three categories or no classification, etc.; the four categories are for illustrative purposes only). Based on the relationship between sensing measurements and sensing services, the third and fourth level measurements below are often also referred to as sensing results. The measurement results of the second level measurements and / or the first level measurements are also referred to as sensing measurement data.

[0071] a) First-level measurement quantities (received signal / raw channel information), including at least one of the following: complex result of received signal / channel response, amplitude / phase, I-channel / Q-channel and its operation results (operations include: addition, subtraction, multiplication, division, matrix addition, subtraction, multiplication, matrix transpose, trigonometric operations, square root operations and power operations, etc., as well as threshold detection results, maximum / minimum value extraction results, etc. of the above operation results; operations also include Fast Fourier Transform (FFT) / Inverse Fast Fourier Transform (IFFT), Discrete Fourier Transform (DFT) / Inverse Discrete Fourier Transform (IDFT), 2D-FFT, 3D-FFT, matched filtering, autocorrelation operation, wavelet transform and digital filtering, etc., as well as threshold detection results, maximum / minimum value extraction results, etc. of the above operation results);

[0072] b) Second-level measurements (basic measurements), including at least one of the following: time delay, Doppler, angle, signal strength, and their multidimensional combined representations;

[0073] c) Third-level measurements (basic attributes / states), including at least one of the following: distance, velocity, angle / orientation, radar cross section (RCS), and acceleration;

[0074] d) Level 4 measurement quantities (advanced attributes / states), including at least one of the following: spatial location, presence of target, trajectory, action, expression, vital signs, quantity, imaging results, weather, air quality, shape, material, and composition.

[0075] The user plane data transmission method, apparatus, communication device, and readable storage medium provided in this application will be described in detail below with reference to the accompanying drawings and through some embodiments and application scenarios.

[0076] To address the challenges of transmitting new service data within the network, including but not limited to the inability to terminate at radio access network nodes, the inability to support higher or lower priorities compared to existing user plane data, the inability to map new service QoS flows or tasks to multiple DRBs, and the additional latency caused by UPF processing and forwarding, improvements to existing user plane protocols are needed to meet the following requirements of new service data: transmission of data packets encapsulated using IP protocols, transmission of data packets encapsulated using non-IP protocols, new service data flow identification and flow mapping, flexible prioritization, and flexible endpoints. Simultaneously, since new service data is intra-network data, unnecessary forwarding nodes or protocol functions within the network should be reduced to improve the efficiency of new service data transmission.

[0077] Please refer to Figure 5 This application provides a user plane data transmission method, including:

[0078] Step S11: When the SDAP entity of the first device receives from the lower layer an SDAP PDU indicating a QoS flow ID (QFI) or a new service task indicating a task ID, a first operation is performed, the first operation including: retrieving an SDAP SDU from the SDAP PDU and delivering the retrieved SDAP SDU to the upper layer; wherein the SDAP PDU is an SDAP PDU in a format that supports the new service.

[0079] Wherein, the SDAP PDU of the QoS flow indicated by the QFI or the new service task indicated by the task identifier is either the SDAP PDU of the QoS flow indicated by the QFI or the SDAP PDU of the new service task indicated by the task identifier, wherein the QFI is the identifier of the QoS flow and the task identifier is the identifier of the new service task.

[0080] In some embodiments, the first device may be a terminal, a RAN device, or a new service function.

[0081] In some embodiments, the lower layer of the SDAP entity may be a PDCP entity.

[0082] In some embodiments, if the first device is a terminal, the SDAP PDU is downlink data, i.e., data sent to the terminal by the new service function. In this application embodiment, the data sent to the terminal by the new service function is called downlink data or downlink data packet (DL packet), and the data sent by the terminal to the new service function is called uplink data or uplink data packet (UL packet). In this application embodiment, both downlink SDAP PDU and downlink SDAP SDU can be called downlink data or downlink data packet.

[0083] In some embodiments, the SDAP PDU may include at least one of an SDAP control PDU and an SDAP data PDU.

[0084] In some embodiments, the DRB that receives the SDAP PDU refers to a DRB that has a mapping relationship with the QoS flow indicated by the QFI or the new service task indicated by the task identifier.

[0085] In this application embodiment, the processing method of new service data in the SDAP entity is clarified to meet the transmission requirements of new service data.

[0086] In some embodiments, optionally, the SDAP PDU supporting the new service format includes at least one of: new service data, SDAP control PDU supporting the new service, and user plane data with the SDAP header, wherein the SDAP header supports the transmission of the new service data.

[0087] In some embodiments, optionally, the user plane data includes at least one of new service data and non-new service data, wherein the non-new service data is other user plane data besides the new service data. That is, the user plane data with the SDAP header can be the SDAP header plus existing user plane data, or the SDAP header plus new service data.

[0088] The non-new service data can also be referred to as existing user plane data or external network user data. This existing user plane data can be voice service data or short messages from the IP Multimedia Subsystem (IMS), or application data from over-the-top (OTT) services (such as WeChat data, short video application data, etc.). In this embodiment, the first operation described above is compatible with both new service data and existing user plane data, thus supporting the transmission of both simultaneously.

[0089] The new service data, also known as network internal user data, may include at least one of the following: perception data, AI data, or computational data. Perception data includes at least the perception data obtained by the UE or base station through perception measurements. AI data may include at least one of the following: AI models, AI training data, AI inference data, etc. AI model data includes parameters of known model structures or new models and parameters. Regarding AI data or computational data, when the mobile communication network provides AI services or computational services for application functions deployed on terminals or application servers, we refer to it as NETforAI or NETforComputing data, or external AI or external computational service data. The main difference between external AI service data or external computational service data and existing cloud computing is that the AI ​​nodes or computational nodes providing the service are located within the mobile network. Regarding AI data or computational data, when the mobile communication network provides AI services or computational services to the UE or network (such as base stations, core network function nodes, or network management functions), we refer to it as AIforNET or ComputingforNET data, or internal AI or internal computational service data. Internal AI service data or internal computational service data is typically generated by the aforementioned internal nodes of the mobile communication network, and the data is transmitted to the internal nodes of the mobile network.

[0090] In some embodiments, optionally, retrieving an SDAP SDU from the SDAP PDU and transmitting the retrieved SDAP SDU to the upper layer includes at least one of the following:

[0091] If the SDAP PDU is an SDAP data PDU, and the DRB receiving the SDAP PDU has configured an SDAP header, the SDAP SDU is retrieved from the SDAP PDU according to the SDAP header, and the retrieved SDAP SDU is transmitted to the upper layer.

[0092] If the SDAP PDU is an SDAP data PDU and the DRB receiving the SDAP PDU is not configured with an SDAP header, the SDAP SDU is retrieved from the SDAP PDU according to the format of the SDAP PDU without an SDAP header, and the retrieved SDAPSDU is transmitted to the upper layer.

[0093] If the SDAP PDU is an SDAP control PDU, retrieve the SDAP SDU from the SDAP PDU associated with the SDAP control PDU and transmit the retrieved SDAP SDU to the upper layer.

[0094] The SDAP PDU associated with the SDAP control PDU refers to an SDAP data PDU that follows the SDAP PDU that sends the start marker and belongs to the same OoS stream or the same new service task as the SDAP PDU that sends the start marker. The start marker will be described in detail below.

[0095] In some embodiments, retrieving the SDAP SDU from the SDAP PDU based on the SDAP header can be done by removing the SDAP header from the SDAP PDU to obtain the SDAP SDU. If there is no SDAP header, the SDAP PDU can be directly used as the SDAP SDU.

[0096] In some embodiments, optionally, retrieving the SDAP SDU from the SDAP PDU according to the SDAP header and transmitting the retrieved SDAP SDU to the upper layer includes at least one of the following:

[0097] The SDAP SDU is retrieved from the SDAP PDU according to the SDAP header. If the SDAP header contains a new service data indication and the new service data indication indicates that the SDAP PDU is new service data, the retrieved SDAP SDU is transmitted to the modem; that is, the upper layer is the modem at this time.

[0098] The SDAP SDU is retrieved from the SDAP PDU according to the SDAP header. If the SDAP header contains a next-hop address, the retrieved SDAP SDU is transmitted to the next-hop address. That is, the upper layer is the node corresponding to the next-hop address at this time.

[0099] If the SDAP header contains a priority indicator, the SDAP SDU is retrieved from the SDAP PDU according to the priority indicator and transmitted to the upper layer. For example, if the priority indicator in the SDAP header of a flow or task's data is the highest priority indicator, the flow or task's data can be processed first (i.e., the above retrieval and transmission are performed first). If the priority indicator of a flow or task's data is the lowest priority indicator, it is necessary to wait for the data of other QoS flows to be processed before processing the data of that flow or task.

[0100] In some embodiments, optionally, the control PDU supporting the new service or the SDAP header includes at least one of the following information elements:

[0101] New Service Indication (NSI) is used to indicate whether the SDAP PDU is new service data;

[0102] New Service Type (NST) is used to indicate the type of new service;

[0103] User plane data type, used to indicate the user plane data type of the SDAP PDU;

[0104] Next hop node type (NHNT) indicates the type of the next hop node after the SDAP PDU is transmitted to the RAN device;

[0105] Priority indicator, used to indicate the priority information of the SDAP PDU; if there is no priority indicator in SDAP, the priority in the corresponding QoS parameters can be applied by default, just like the existing user plane data;

[0106] A task identifier is used to identify a new service task; the task identifier can also be a new service flow identifier. Existing QoS flows belong to a traditional user plane service and are QoS flows for a single UE, meaning one QoS flow is mapped to at most one DRB or multiple QoS flows are mapped to one DRB. New service tasks may sometimes be associated with multiple UEs, meaning one new service task is mapped to one DRB or one new service task is mapped to multiple DRBs. When mapping to multiple DRBs, if multiple DRBs of multiple UEs are involved, then the task identifier is a single task identifier shared by all UEs.

[0107] The RAN termination indication is used to indicate whether the SDAP PDU is parsed by the RAN device. For example, when the SDAP PDU is internal sensing service (SensingforNET) data or internal AI service (AIforNET) data, the sensing data or AI data may be sent to the base station. After parsing, the base station uses it for auxiliary channel estimation, beam management, or fine-tuning of AI models, etc. In this case, it is necessary to indicate in the SDAP header that the SDAP PDU is parsed by the RAN device. As another example, when the SDAP PDU is external sensing service (NETforSensing) data, the UE's external sensing service data is processed by the base station before being sent to the core network sensing function. In this case, it is necessary to indicate in the SDAP header that the SDAP PDU is parsed by the RAN device.

[0108] The extended header indicator is used to indicate whether the information unit following the extended header indicator needs to be parsed; for example, when set to 0, it means that the information unit following the extended header indicator does not exist, and if it exists, it will not be parsed; when set to 1, the information unit following the extended header indicator should be parsed.

[0109] The next-hop node address is used to indicate the next-hop node address of the SDAP PDU. When the new service does not use the IP protocol to encapsulate the data packet, but uses a 3GPP-defined protocol (such as the location protocol) to encapsulate the data packet, then the next-hop node address is needed to indicate which node to send the SDAP PDU to.

[0110] The destination address indicates the destination address of the SDAP PDU. When the new service does not encapsulate data packets using the IP protocol, but instead uses a 3GPP-defined protocol (such as a location protocol), the destination address is needed to resolve the routing issue for sending the SDAP PDU. The base station can determine the next-hop node based on the destination address.

[0111] A start-marker is used to indicate that a first data PDU following a first control PDU containing the start-marker will be processed according to the information element in the first control PDU, and that the SDU corresponding to the first data PDU will be mapped to the DRB of the first control PDU, wherein the first control PDU and the first data PDU belong to the same QoS flow or the same new service task; or, it is used to indicate that a third data PDU following a second data PDU containing the start-marker will be processed according to the information element in the second data PDU, wherein the second data PDU and the third data PDU belong to the same QoS flow or the same new service task;

[0112] The first quantity is used to indicate the number of data PDUs that need to be processed according to the information unit in the first control PDU or the information unit in the second data PDU;

[0113] An end-marker is used to indicate that a third data PDU following a second control PDU containing the end-marker will no longer be processed according to the information element in the first control PDU, and that the SDU corresponding to the third data PDU will no longer be mapped to the DRB of the first control PDU, wherein the first control PDU and the second control PDU belong to the same QoS flow or the same new service task; or, it is used to indicate that a fifth data PDU following a fourth data PDU containing the end-marker will no longer be processed according to the information element in the second data PDU, wherein the second data PDU and the fourth data PDU belong to the same QoS flow or the same new service task.

[0114] In one embodiment, a start marker can be used, but an end marker is not used. Data PDUs that belong to the same QoS flow or new service task as the SDAP PDU containing the start marker and are located after the SDAP PDU containing the start marker are processed according to the information units in the SDAP PDU containing the start marker. If the data PDUs of the QoS flow or new service task are no longer sent, it means that the data PDUs of the QoS flow or new service task have been sent.

[0115] In one embodiment, only a start marker may be used, without an end marker. Data PDUs belonging to the same QoS flow or new service task as the SDAP PDU containing the start marker, located after the SDAP PDU containing the start marker, are processed according to the information elements in the SDAP PDU containing the start marker. If an SDAP PDU containing the start marker for the QoS flow or new service task is retransmitted, then data PDUs belonging to the QoS flow or new service task that are located after the newly transmitted SDAP PDU containing the start marker are processed according to the information elements in the newly transmitted SDAP PDU containing the start marker.

[0116] In one embodiment, a start marker and an end marker can be used simultaneously. It should be noted that the start marker and the end marker generally do not appear in the same SDAP PDU. For example, the start marker is in the first control PDU, and the end marker is in the second control PDU. In this case, the data PDU located between the SDAP PDU containing the start marker and the SDAP PDU containing the end marker, and belonging to the same QoS flow or new service task as the SDAP PDU containing the start marker, is processed according to the information unit in the SDAP PDU containing the start marker.

[0117] In one embodiment, a start marker and a first quantity can be used simultaneously. For example, both the start marker and the first quantity are in the first control PDU. The first quantity of data PDUs, which are located after the first control PDU and belong to the same QoS flow or new service task as the first control PDU, are processed according to the information units in the first control PDU.

[0118] In some embodiments, optionally, the first control PDU of a QoS flow or new service task includes a start marker and other information elements (at least one of the information elements other than the start marker and end marker). The SDAP data PDU following the first control PDU of the QoS flow or new service task may not include an SDAP header (if there is only one QoS flow or new service task at present). By default, the information elements in the SDAP header of the SDAP data PDU following the first control PDU are the same as the other information elements of the first control PDU, thereby saving network overhead.

[0119] In some embodiments, optionally, the start marker and other information elements in the SDAP header can be sent in the same SDAP control PDU, or they can be sent in different SDAP control PDUs. For example, one SDAP control PDU can be used to send the other information elements in the SDAP header first, and then another SDAP control PDU can be used to send the start marker. In this embodiment, the SDAP control PDUs that send the start marker and the other information elements are combined into a first control PDU.

[0120] In some embodiments, optionally, the first SDAP data PDU of a QoS flow or new service task (i.e., the second data PDU mentioned above) includes a start marker and other information elements (at least one of the information elements other than the start marker and end marker). Subsequent SDAP data PDUs of the QoS flow or new service task following the second data PDU may not include an SDAP header (if there is only one QoS flow or new service task at present). By default, the information elements in the SDAP header of subsequent SDAP data PDUs are the same as the other information elements of the second data PDU, thereby saving network overhead.

[0121] In some embodiments, optionally, the SDAP control PDU supporting the new service or the SDAP header may further include at least one of a PDU type indicator and a QoS flow identifier, wherein the PDU type indicator is used to indicate whether the SDAP PDU is an SDAP control PDU or an SDAP data PDU.

[0122] In some embodiments, optionally, the user plane data type may also be referred to as a service flow type, including at least one of the following: non-new service data, new service data, sensing service data, AI service data, computing service data, external sensing service (NET for Sensing) data, internal sensing service (Sensing for NET) data, external AI service (NET for AI) data, internal AI service (AI for NET) data, external computing service (NET for Computing) data, internal computing service (Computing for NET) data, AI model data, AI training data, and AI inference data.

[0123] In some embodiments, if the SDAP control PDU supporting the new service or the SDAP header includes the user plane data type, the aforementioned new service data indication and the type of the new service may be omitted.

[0124] In some embodiments, optionally, the type of the new service includes at least one of the following: perception service, AI service, computing service, external perception service, internal perception service, external AI service, internal AI service, external computing service, internal computing service, AI model, AI training, and AI inference.

[0125] In some embodiments, optionally, the next-hop node type is a user plane function (UPF), a data plane function (DPF), or a new service function, wherein the new service function is a sensing function, an AI function, or a computing function.

[0126] Different new services have different priority requirements. Some new services may bring operators greater benefits than existing user plane data, thus they can have a higher priority. Conversely, some new services may only supplement the operator's existing user plane data, therefore they have a lower priority. Alternatively, if the new service data does not have short-term latency requirements, it can also be given a lower priority to better meet the data transmission needs of services with higher service quality requirements under high load. These priority indicators allow for matching the different priority requirements of different new services.

[0127] In some embodiments, the priority indication optionally includes a high-priority indication. The high-priority indication is used to indicate whether the priority of the new service data is higher than that of the non-new service data. In one case, the high-priority indication is used to indicate whether the priority of the new service data is the highest. If the high-priority indication indicates that the new service data has the highest priority, it means that the new service data has a higher priority than existing user plane data. For example, external AI services or computing services are geared towards low-latency scenarios, therefore the corresponding AI services or computing services should have a higher priority to ensure that the AI ​​services or computing services provided by 6G have a higher service quality. One example is that when data from the lower layer is received, the indicated higher-priority data is processed first and sent to the corresponding node. When there is no indicated higher-priority data, other service data is processed and sent to the corresponding node.

[0128] In some embodiments, optionally, the priority indication includes a low-priority indication, which indicates whether the priority of the new service data is lower than that of the non-new service data. In one case, the low-priority indication indicates whether the priority of the new service data is the lowest. If the low-priority indication indicates that the new service data has the lowest priority, it means that the new service data has a lower priority than existing user plane data. For example, in scenarios such as external AI training data or non-real-time perception data (e.g., perception measurement data required for long-term environmental reconstruction), these data do not have short-term transmission requirements and can be transmitted when network resources are idle, facilitating more reasonable scheduling and use of 6G transmission resources. One example is that when data is received from the lower layer, it can be cached first, and then the indicated lower-priority data can be sent to the corresponding node when there is no other service data.

[0129] In some embodiments, optionally, the SDAP header further includes a QFI information element, which indicates the task identifier when the new service data indicates that the SDAP PDU is new service data. That is, the existing QFI information element used to indicate QoS flows can be used to indicate the task identifier. There is no need to set up a separate information element for the task identifier.

[0130] In some embodiments, optionally, the SDAP header includes: a Reflective QoS flow to DRB mapping indication (RDI) information element, a Reflective QoS Indication (RQI) information element, and a QFI information element. Existing SDAP headers include the aforementioned RDI, RQI, and QFI information elements; that is, the SDAP header in this embodiment is an extension of the existing SDAP header, thus making it suitable for both new service data and existing user plane data.

[0131] In some embodiments, optionally, the SDAP header does not include RDI information elements and RQI information elements. That is, the SDAP header in this application embodiment is not an extension of the existing SDAP header, but rather an SDAP header specifically set up for new service data.

[0132] In some embodiments, optionally, the SDAP entity is located in an SDAP sublayer that supports at least one of the following functionalities:

[0133] Mapping between uplink new service QoS streams and DRBs;

[0134] Mapping between downlink new service QoS flows and DRBs;

[0135] Mapping between uplink new service QoS flows and DRB sets; for example, a new service QoS flow can be mapped to DRBs of different UEs or multiple DRBs of the same UE;

[0136] Mapping between downlink new service QoS flows and DRB groups;

[0137] Mapping between new uplink service tasks and DRBs;

[0138] Mapping between new downlink service tasks and DRB;

[0139] Mapping between new uplink service tasks and DRB groups; for example, a new service task can be mapped to DRBs of different UEs or multiple DRBs of the same UE;

[0140] Mapping between new downlink service tasks and DRB groups;

[0141] Mark new service QoS flows in uplink packets (UL packets);

[0142] Mark new service QoS flows in downlink packets (DL packets);

[0143] Mark new service tasks in the uplink data packets;

[0144] New service tasks are marked in the downlink data packets.

[0145] The SDAP sublayer in this embodiment can also be called an enhanced user plane protocol sublayer, or an enhanced SDAP sublayer, which is used for user plane data transmission. Please refer to... Figure 6 , Figure 6 This is a schematic diagram of a user plane protocol sublayer according to an embodiment of this application. It should be noted that... Figure 6 This is just one example and does not limit the structure of the user plane protocol sublayer.

[0146] In some embodiments, optionally, the first device is a terminal, and the method further includes:

[0147] The first device receives first configuration information, which is used to indicate the addition of a DRB. The first configuration information includes SDAP header configuration information; the SDAP header includes at least one of an uplink SDAP header and a downlink SDAP header.

[0148] The first device establishes the SDAP entity based on the configuration information.

[0149] In some embodiments, the configuration information may optionally be carried in an RRC reconfiguration message.

[0150] In some embodiments, optionally, the SDAP header configuration information includes one of the following:

[0151] Does an SDAP header exist?

[0152] The number of bits in the SDAP header;

[0153] The format name of the SDAP header.

[0154] In some embodiments, optionally, the first device is a network-side device, and the method includes:

[0155] If there are multiple SDAP control PDU formats, the first device sends second configuration information, which includes the configured SDAP control PDU format; the control PDU format includes at least one of uplink control PDU and downlink control PDU; the configured SDAP control PDU format is one of the multiple SDAP control PDU formats;

[0156] or

[0157] The first device is a terminal, and the method further includes:

[0158] The first device receives second configuration information, which includes a configured SDAP control PDU format; the control PDU format includes at least one of uplink control PDU and downlink control PDU.

[0159] In some embodiments, optionally, the method further includes:

[0160] The first device reports terminal capability information, which includes at least one of the following:

[0161] Does the terminal support the new service?

[0162] Does the terminal support the SDAP PDU format with the SDAP header?

[0163] Does the terminal support the SDAP control PDU that supports the new service?

[0164] Please refer to Figure 7 This application provides a user plane data transmission method, including:

[0165] Step S21: When the SDAP entity of the first device receives the SDAP SDU of the QoS flow indicated by the QFI or the new service task indicated by the task identifier from the upper layer, the second operation is performed, the second operation includes: constructing SDAPPDU and submitting the constructed SDAP PDU to the lower layer; wherein the SDAP PDU is an SDAP PDU in a format that supports the new service.

[0166] In some embodiments, the first device may be a terminal, a RAN device, or a new service function.

[0167] In some embodiments, the upper layer of the SDAP entity may be an application function or a modem.

[0168] In some embodiments, if the first device is a terminal, the SDAP PDU is uplink data, that is, data sent by the terminal to the new service function.

[0169] In this application embodiment, the processing method of new service data in the SDAP entity is clarified to meet the transmission requirements of new service data.

[0170] In some embodiments, optionally, the SDAP PDU supporting the new service format includes at least one of: new service data, SDAP control PDU supporting the new service, and user plane data with the SDAP header, wherein the SDAP header supports the transmission of the new service data.

[0171] In some embodiments, optionally, the user plane data includes at least one of new service data and non-new service data (or existing user plane data), wherein the non-new service data is other user plane data besides the new service data. That is, the user plane data with the SDAP header can be the SDAP header + existing user plane data, or the SDAP header + new service data.

[0172] In this embodiment of the application, the second operation described above is compatible with existing user plane data in addition to being applicable to new service data, thereby enabling the simultaneous transmission of both new service data and existing user plane data.

[0173] In some embodiments, optionally, the construction of the SDAP PDU and the submission of the constructed SDAP PDU to the lower layer includes at least one of the following:

[0174] If the SDAP SDU is an SDAP data SDU, and the DRB mapped by the SDAP SDU has been configured with an SDAP header, an SDAP PDU is constructed based on the SDAP header, and the constructed SDAP PDU is submitted to the lower layer.

[0175] If the SDAP SDU is an SDAP data SDU and the DRB mapped by the SDAP SDU is not configured with an SDAP header, an SDAP PDU is constructed according to the SDAP PDU format without an SDAP header, and the constructed SDAP PDU is submitted to the lower layer.

[0176] If the SDAP SDU is an SDAP control SDU, construct an SDAP PDU and submit the constructed SDAP PDU to the lower layer.

[0177] In some embodiments, the DRB mapped by the SDAP SDU refers to a DRB that has a mapping relationship with the QoS flow indicated by the QFI or the new service task indicated by the task identifier.

[0178] In some embodiments, an SDAP PDU is constructed based on the SDAP header, that is, an SDAP SDU is obtained by adding an SDAP header to it. An SDAP PDU is also constructed based on the format of an SDAP PDU without an SDAP header, that is, an SDAPPDU is obtained directly from the SDAP SDU.

[0179] In some embodiments, optionally, the second operation further includes at least one of the following:

[0180] If there is no mapping rule for storing the QoS flow to the DRB, map the SDAP SDU to the default DRB;

[0181] If the mapping rules from the QoS flow to the DRB are stored, map the SDAP SDU to the DRB corresponding to the mapping rules from the QoS flow to the DRB.

[0182] If there is no mapping rule for storing the new service task to the DRB, map the SDAP SDU to the default DRB;

[0183] If the mapping rule from the new service task to the DRB is stored, the SDAP SDU is mapped to the DRB corresponding to the mapping rule from the new service task to the DRB.

[0184] In some embodiments, optionally, the control PDU supporting the new service or the SDAP header includes at least one of the following information elements:

[0185] New service data indication is used to indicate whether the SDAP PDU is new service data;

[0186] New service type, used to indicate the type of new service;

[0187] User plane data type, used to indicate the user plane data type of the SDAP PDU;

[0188] Next-hop node type, used to indicate the type of the next-hop node after the SDAP PDU is transmitted to the RAN device;

[0189] Priority indicator, used to indicate the priority information of the SDAP PDU; if there is no priority indicator in SDAP, the priority in the corresponding QoS parameters can be applied by default, just like the existing user plane data;

[0190] A task identifier is used to identify a new service task; the task identifier can also be a new service flow identifier. Existing QoS flows belong to a traditional user plane service and are QoS flows for a single UE, meaning one QoS flow is mapped to at most one DRB or multiple QoS flows are mapped to one DRB. New service tasks may sometimes be associated with multiple UEs, meaning one new service task is mapped to one DRB or one new service task is mapped to multiple DRBs. When mapping to multiple DRBs, if multiple DRBs of multiple UEs are involved, then the task identifier is a single task identifier shared by all UEs.

[0191] The RAN termination indication is used to indicate whether the SDAP PDU is parsed by the RAN device. For example, when the SDAP PDU is internal sensing service (SensingforNET) data or internal AI service (AIforNET) data, the sensing data or AI data may be sent to the base station. After parsing, the base station uses it for auxiliary channel estimation, beam management, or fine-tuning of AI models, etc. In this case, it is necessary to indicate in the SDAP header that the SDAP PDU is parsed by the RAN device. As another example, when the SDAP PDU is external sensing service (NETforSensing) data, the UE's external sensing service data is processed by the base station before being sent to the core network sensing function. In this case, it is necessary to indicate in the SDAP header that the SDAP PDU is parsed by the RAN device.

[0192] The extended header indicator is used to indicate whether the information unit following the extended header indicator needs to be parsed; for example, when set to 0, it means that the information unit following the extended header indicator does not exist, and if it exists, it will not be parsed; when set to 1, the information unit following the extended header indicator should be parsed.

[0193] The next-hop node address is used to indicate the next-hop node address of the SDAP PDU. When the new service does not use the IP protocol to encapsulate the data packet, but uses a 3GPP-defined protocol (such as the location protocol) to encapsulate the data packet, then the next-hop node address is needed to indicate which node to send the SDAP PDU to.

[0194] The destination address indicates the destination address of the SDAP PDU. When the new service does not encapsulate data packets using the IP protocol, but instead uses a 3GPP-defined protocol (such as a location protocol), the destination address is needed to resolve the routing issue for sending the SDAP PDU. The base station can determine the next-hop node based on the destination address.

[0195] A start-marker is used to indicate that a first data PDU following a first control PDU containing the start-marker will be processed according to the information element in the first control PDU, and that the SDU corresponding to the first data PDU will be mapped to the DRB of the first control PDU, wherein the first control PDU and the first data PDU belong to the same QoS flow or the same new service task; or, it is used to indicate that a third data PDU following a second data PDU containing the start-marker will be processed according to the information element in the second data PDU, wherein the second data PDU and the third data PDU belong to the same QoS flow or the same new service task;

[0196] The first quantity is used to indicate the number of data PDUs that need to be processed according to the information unit in the first control PDU or the information unit in the second data PDU;

[0197] An end-marker is used to indicate that a third data PDU following a second control PDU containing the end-marker will no longer be processed according to the information element in the first control PDU, and that the SDU corresponding to the third data PDU will no longer be mapped to the DRB of the first control PDU, wherein the first control PDU and the second control PDU belong to the same QoS flow or the same new service task; or, it is used to indicate that a fifth data PDU following a fourth data PDU containing the end-marker will no longer be processed according to the information element in the second data PDU, wherein the second data PDU and the fourth data PDU belong to the same QoS flow or the same new service task.

[0198] In some embodiments, optionally, the SDAP control PDU supporting the new service or the SDAP header may further include at least one of a PDU type indicator and a QoS flow identifier, wherein the PDU type indicator is used to indicate whether the SDAP PDU is an SDAP control PDU or an SDAP data PDU.

[0199] In some embodiments, optionally, the user plane data type includes at least one of the following: non-new service data, new service data, perception service data, AI service data, computing service data, external perception service data, internal perception service data, external AI service data, internal AI service data, external computing service data, internal computing service data, AI model data, AI training data, and AI inference data.

[0200] In some embodiments, if the SDAP control PDU supporting the new service or the SDAP header includes the user plane data type, the aforementioned new service data indication and the type of the new service may be omitted.

[0201] In some embodiments, optionally, the type of the new service includes at least one of the following: perception service, AI service, computing service, external perception service, internal perception service, external AI service, internal AI service, external computing service, internal computing service, AI model, AI training, and AI inference.

[0202] In some embodiments, optionally, the next-hop node type is a user plane function, a data plane function, or a new service function, wherein the new service function is a sensing function, an AI function, or a computing function.

[0203] In some embodiments, the priority indication optionally includes a high-priority indication. The high-priority indication is used to indicate whether the priority of the new service data is higher than that of the non-new service data. In one case, the high-priority indication is used to indicate whether the priority of the new service data is the highest. If the high-priority indication indicates that the new service data has the highest priority, it means that the new service data has a higher priority than existing user plane data. For example, external AI services or computing services are geared towards low-latency scenarios, therefore the corresponding AI services or computing services should have a higher priority to ensure that the AI ​​services or computing services provided by 6G have a higher service quality. One example is that when an SDAP PDU is received from the upper layer, the indicated higher-priority SDAP PDU is processed first and then submitted to the lower layer for processing. When there is no indicated higher-priority data, other service data is processed and submitted to the lower layer for processing.

[0204] In some embodiments, optionally, the priority indication includes a low-priority indication, which indicates whether the priority of the new service data is lower than that of the non-new service data. In one case, the low-priority indication indicates whether the priority of the new service data is the lowest. If the low-priority indication indicates that the new service data has the lowest priority, it means that the new service data has a lower priority than existing user plane data. For example, in scenarios such as external AI training data or non-real-time perception data (e.g., perception measurement data required for long-term environmental reconstruction), these data do not have short-term transmission requirements and can be transmitted when network resources are idle, facilitating more reasonable scheduling and use of 6G transmission resources. One example is that when data is received from the upper layer, it can be cached first, and when there is no other service data, the indicated lower-priority data can be submitted to the lower layer for processing.

[0205] In some embodiments, optionally, the SDAP header further includes a QFI information element, which indicates the task identifier when the new service data indicates that the SDAP PDU is new service data. That is, the existing QFI information element used to indicate QoS flows can be used to indicate the task identifier. There is no need to set up a separate information element for the task identifier.

[0206] In some embodiments, optionally, the SDAP header includes: an RDI information element, an RQI information element, and a QFI information element. Existing SDAP headers include the aforementioned RDI information element, RQI information element, and QFI information element; that is, the SDAP header in this embodiment is an extension of the existing SDAP header, thus making it suitable for both new service data and existing user plane data.

[0207] In some embodiments, optionally, the SDAP header does not include RDI information elements and RQI information elements. That is, the SDAP header in this application embodiment is not an extension of the existing SDAP header, but rather an SDAP header specifically set up for new service data.

[0208] In some embodiments, optionally, the SDAP entity is located in an SDAP sublayer that supports at least one of the following functionalities:

[0209] Mapping between uplink new service QoS streams and DRBs;

[0210] Mapping between downlink new service QoS flows and DRBs;

[0211] Mapping between uplink new service QoS flows and DRB groups;

[0212] Mapping between downlink new service QoS flows and DRB groups;

[0213] Mapping between new uplink service tasks and DRBs;

[0214] Mapping between new downlink service tasks and DRB;

[0215] Mapping between new service tasks and DRB groups;

[0216] Mapping between new downlink service tasks and DRB groups;

[0217] Mark new service QoS flows in uplink packets (UL packets);

[0218] Mark new service QoS flows in downlink packets (DL packets);

[0219] Mark new service tasks in the uplink data packets;

[0220] New service tasks are marked in the downlink data packets.

[0221] In some embodiments, optionally, the first device is a terminal, and the method further includes:

[0222] The first device receives first configuration information, which is used to indicate the addition of a DRB. The first configuration information includes SDAP header configuration information; the SDAP header includes at least one of an uplink SDAP header and a downlink SDAP header.

[0223] The first device establishes the SDAP entity based on the configuration information.

[0224] In some embodiments, the configuration information may optionally be carried in an RRC reconfiguration message.

[0225] In some embodiments, optionally, the SDAP header configuration information includes one of the following:

[0226] Does an SDAP header exist?

[0227] The number of bits in the SDAP header;

[0228] The format name of the SDAP header.

[0229] In some embodiments, optionally, the first device is a network-side device, and the method includes:

[0230] If there are multiple SDAP control PDU formats, the first device sends second configuration information, which includes the configured SDAP control PDU format; the control PDU format includes at least one of uplink control PDU and downlink control PDU; the configured SDAP control PDU format is one of the multiple SDAP control PDU formats;

[0231] or

[0232] The first device is a terminal, and the method further includes:

[0233] The first device receives second configuration information, which includes a configured SDAP control PDU format; the control PDU format includes at least one of uplink control PDU and downlink control PDU.

[0234] In some embodiments, optionally, the method further includes:

[0235] The first device reports terminal capability information, which includes at least one of the following:

[0236] Does the terminal support the new service?

[0237] Does the terminal support the SDAP PDU format with the SDAP header?

[0238] Does the terminal support the SDAP control PDU that supports the new service?

[0239] The user plane data transmission method of this application will be explained below with specific examples.

[0240] Embodiment 1 of this application: Downlink SDAP data PDU format based on existing SDAP sublayer enhancement

[0241] The solution in this embodiment is to enhance the existing SDAP data PDU 37.324 to support the transmission of new service data, thereby supporting both existing user plane data transmission and new service data transmission, and flexibly processing the new service data according to its priority.

[0242] In this embodiment, the format of a potential SDAP data PDU is as follows.

[0243] Example 1:

[0244] Please refer to Figure 8 , Figure 8 This is a schematic diagram of Example 1 of the downlink SDAP data PDU in Embodiment 1 of this application. The SDAP header of the downlink SDAP data PDU includes: RDI, RQI, NSI (New Service Indicator), and QFI. Among them, RDI, RQI, and QFI are information elements in the existing SDAP header, and NSI is a newly added information element. NSI is used to indicate whether the downlink SDAP data PDU is new service data.

[0245] In this embodiment of the application, when the SDAP entity of the first device receives SDAP data PDU of a QoS flow indicated by a QFI or a new service task indicated by a task identifier from the lower layer, a first operation is performed, the first operation including:

[0246] If the DRB receiving the SDAP data PDU has an SDAP header configured, the SDAP header contains a New Service Data Indicator, which processes existing user plane data or new service data. For example, the New Service Data Indicator indicates that the SDAP SDU is new service data, and the retrieved SDAP SDU is transmitted to the modem. Optionally, when the NSI indicates that the SDAP data PDU is new service data, the QFI information element shown is a Task Identifier (TI).

[0247] If the DRB receiving the SDAP PDU does not have an SDAP header configured, the SDAP SDU is retrieved from the SDAP PDU according to the format of the SDAP PDU without an SDAP header, and the retrieved SDAP SDU is transmitted to the upper layer.

[0248] Example 2:

[0249] Please refer to Figure 9 , Figure 9This is a schematic diagram of Example 2 of the downlink SDAP data PDU in Embodiment 1 of this application. The SDAP header of this downlink SDAP data PDU includes: RDI, RQI, QFI, NSI (New Service Indicator), and NST (New Service Type). RDI, RQI, and QFI are information units in the existing SDAP header, while NSI and NST are newly added information units. NSI indicates whether the downlink SDAP data PDU is new service data, and NST indicates the type of the new service. The type of the new service includes at least one of the following: perception service, AI service, computing service, external perception service, internal perception service, external AI service, internal AI service, external computing service, internal computing service, AI model, AI training, and AI inference.

[0250] In this embodiment of the application, when the SDAP entity of the first device receives SDAP data PDU of a QoS flow indicated by a QFI or a new service task indicated by a task identifier from the lower layer, a first operation is performed, the first operation including:

[0251] If the DRB receiving the SDAP data PDU has configured the SDAP header, it retrieves the SDAP SDU from the SDAP data PDU according to the SDAP header (NSI (New Service Indicator) and NST (New Service Type)) and transmits the retrieved SDAP SDU to the upper layer.

[0252] If the DRB receiving the SDAP PDU does not have an SDAP header configured, the SDAP SDU is retrieved from the SDAP PDU according to the format of the SDAP PDU without an SDAP header, and the retrieved SDAP SDU is transmitted to the upper layer.

[0253] In some other embodiments, optionally, the above-mentioned NSI (New Service Indication) and NST (New Service Type) can also be combined into a "User-plane Data Type" or "Service Flow Type". Optionally, the User-plane Data Type / Service Flow Type includes at least one of the following: non-new service data, new service data, sensing service data, AI service data, computing service data, external sensing service (NET for Sensing) data, internal sensing service (Sensing for NET) data, external AI service (NET for AI) data, internal AI service (AI for NET) data, external computing service (NET for Computing) data, internal computing service (Computing for NET) data, AI model data, AI training data, and AI inference data.

[0254] Example 3:

[0255] Please refer to Figure 10 , Figure 10 This is a schematic diagram of Example 3 of the downlink SDAP data PDU in Embodiment 1 of this application. The SDAP header of the downlink SDAP data PDU includes: RDI, RQI, QFI, and HPI. Among them, RDI, RQI, and QFI are information elements in the existing SDAP header, and HPI is a newly added information element used to indicate whether the priority of the downlink SDAP data PDU is higher than that of non-new service data.

[0256] In this embodiment of the application, when the SDAP entity of the first device receives SDAP data PDU of a QoS flow indicated by a QFI or a new service task indicated by a task identifier from the lower layer, a first operation is performed, the first operation including:

[0257] If the DRB receiving the SDAP data PDU has configured an SDAP header, the SDAP header contains a high priority indication. Based on the high priority indication, the SDAP SDU is retrieved from the SDAP PDU and the retrieved SDAPSDU is transmitted to the upper layer.

[0258] Example 4:

[0259] Please refer to Figure 11 , Figure 11 This is a schematic diagram of Example 4 of a downlink SDAP data PDU in Embodiment 1 of this application. The SDAP header of this downlink SDAP data PDU includes: RDI, RQI, QFI, and LPI. Among them, RDI, RQI, and QFI are information elements in the existing SDAP header, and LPI is a newly added information element used to indicate whether the priority of this downlink SDAP data PDU is lower than that of non-new service data.

[0260] In this embodiment of the application, when the SDAP entity of the first device receives SDAP data PDU of a QoS flow indicated by a QFI or a new service task indicated by a task identifier from the lower layer, a first operation is performed, the first operation including:

[0261] If the DRB receiving the SDAP data PDU has configured an SDAP header, the SDAP header contains a low priority indication. Based on the low priority indication, the SDAP SDU is retrieved from the SDAP PDU and the retrieved SDAPSDU is transmitted to the upper layer.

[0262] Example 5:

[0263] Please refer to Figure 12 , Figure 12This is a schematic diagram of Example 5 of the downlink SDAP data PDU in Embodiment 1 of this application. The SDAP header of the downlink SDAP data PDU includes: RDI, RQI, QFI, LPI, and HPI. Among them, RDI, RQI, and QFI are information elements in the existing SDAP header, while HPI and LPI are newly added information elements. LPI is used to indicate whether the priority of the downlink SDAP data PDU is lower than that of non-new service data, and HPI is used to indicate whether the priority of the downlink SDAP data PDU is higher than that of non-new service data.

[0264] In this embodiment of the application, when the SDAP entity of the first device receives SDAP data PDU of a QoS flow indicated by a QFI or a new service task indicated by a task identifier from the lower layer, a first operation is performed, the first operation including:

[0265] If the DRB receiving the SDAP data PDU has configured an SDAP header, the SDAP header contains high priority and low priority indications. Based on the high priority and low priority indications, the SDAP SDU is retrieved from the SDAP PDU and transmitted to the upper layer.

[0266] Example 6:

[0267] Please refer to Figure 13 , Figure 13 This is a schematic diagram of Example 6 of a downlink SDAP data PDU according to Embodiment 1 of this application. The SDAP header of this downlink SDAP data PDU includes: RDI, RQI, QFI, EI (Extended Header Indicator), NST (New Type of Service Indicator), PI (Priority Indicator), Next Hop Address, and Destination Address. Among them, RDI, RQI, and QFI are information elements in the existing SDAP header, while EI (Extended Header Indicator), NST (New Type of Service Indicator), PI (Priority Indicator), Next Hop Address, and Destination Address are newly added information elements. NST (New Type of Service Indicator) is used to indicate the type of new service; PI (Priority Indicator) is used to indicate the priority information of the downlink SDAP data PDU; and EI (Extended Header Indicator) is used to indicate whether it is necessary to parse the information elements after the extended header indication.

[0268] In this embodiment of the application, when the SDAP entity of the first device receives SDAP data PDU of a QoS flow indicated by a QFI or a new service task indicated by a task identifier from the lower layer, a first operation is performed, the first operation including:

[0269] If the DRB receiving the SDAP data PDU has an SDAP header configured, and the SDAP header contains an Extension Indicator (EI), the decision is made based on the EI to determine whether to parse the information elements following the extension header indication. If the first EI is 1, then the NST and priority indication (PI) are parsed. If the next EI is also 1, then the next-hop address and destination address are parsed.

[0270] It should be noted that, in the embodiments of this application, the existence of a certain information unit in the SDAP header, the abbreviation of the information unit, the number of bits of the information unit, or the order of the information units are merely examples and are not intended to limit the SDAP header of this application.

[0271] Embodiment 2 of this application: Uplink SDAP data PDU format enhanced based on existing SDAP sublayer.

[0272] Example 1 illustrates the SDAP header of a downlink SDAP data PDU. This example will introduce the uplink SDAP data PDU header.

[0273] The solution in this embodiment is to enhance the existing SDAP data PDU (37.324) to support the transmission of new service data. This solves the problem that SDAP can support both existing user plane data transmission and new service data transmission, and allows for flexible processing of new service data based on its priority.

[0274] In this embodiment, the format of a potential SDAP data PDU can be as follows:

[0275] Example 1:

[0276] Please refer to Figure 14 , Figure 14 This is a schematic diagram of Example 1 of the uplink SDAP data PDU in Embodiment 2 of this application. The SDAP header of the uplink SDAP data PDU includes: D / C (Data / Control), NSI (New Service Indication), and QFI. D / C and QFI are information elements in the existing SDAP header, while NSI is a newly added information element used to indicate whether the uplink SDAP data PDU is new service data.

[0277] In this embodiment of the application, when the SDAP entity of the first device receives an SDAP SDU of a QoS flow indicated by a QFI or a new service task indicated by a task identifier from the upper layer, a second operation is performed, the second operation including:

[0278] If no mapping rule for the QoS flow to DRB is stored, the SDAP SDU is mapped to the default DRB; if a mapping rule for the QoS flow to DRB is stored, the SDAP SDU is mapped to the DRB corresponding to the mapping rule for the QoS flow to DRB; or, if no mapping rule for the new service task to DRB is stored, the SDAP SDU is mapped to the default DRB; if a mapping rule for the new service task to DRB is stored, the SDAP SDU is mapped to the DRB corresponding to the mapping rule for the new service task to DRB.

[0279] If the DRB mapped by the SDAP SDU has an SDAP header configured, an SDAP PDU is constructed based on the SDAP header, and the constructed SDAP PDU is submitted to the lower layer.

[0280] Optionally, when NSI indicates that the SDAP data PDU is new service data, the QFI information unit is a Task Identifier (TI).

[0281] Example 2:

[0282] Please refer to Figure 15 , Figure 15 This is a schematic diagram of Example 2 of the uplink SDAP data PDU in Embodiment 2 of this application. The SDAP header of the uplink SDAP data PDU includes: D / C (Data / Control), R (Reserved), QFI, NSI (New Service Indicator), and NST (New Service Type). Among them, D / C and QFI are information units in the existing SDAP header, while NSI and NST are newly added information units. NSI is used to indicate whether the uplink SDAP data PDU is new service data, and NST is used to indicate the new service type. Optionally, the new service type includes at least one of the following: perception service, AI service, computing service, external perception service, internal perception service, external AI service, internal AI service, external computing service, internal computing service, AI model, AI training, and AI inference.

[0283] In this embodiment of the application, when the SDAP entity of the first device receives an SDAP SDU of a QoS flow indicated by a QFI or a new service task indicated by a task identifier from the upper layer, a second operation is performed, the second operation including:

[0284] If no mapping rule for the QoS flow to DRB is stored, the SDAP SDU is mapped to the default DRB; if a mapping rule for the QoS flow to DRB is stored, the SDAP SDU is mapped to the DRB corresponding to the mapping rule for the QoS flow to DRB; or, if no mapping rule for the new service task to DRB is stored, the SDAP SDU is mapped to the default DRB; if a mapping rule for the new service task to DRB is stored, the SDAP SDU is mapped to the DRB corresponding to the mapping rule for the new service task to DRB.

[0285] If the DRB mapped by the SDAP SDU has an SDAP header configured, an SDAP PDU is constructed based on the SDAP header, and the constructed SDAP PDU is submitted to the lower layer.

[0286] In some other embodiments, optionally, the above-mentioned NSI (New Service Indication) and NST (New Service Type) can also be combined into a "User-plane Data Type" or "Service Flow Type". Optionally, the User-plane Data Type / Service Flow Type includes at least one of the following: non-new service data, new service data, sensing service data, AI service data, computing service data, external sensing service (NET for Sensing) data, internal sensing service (Sensing for NET) data, external AI service (NET for AI) data, internal AI service (AI for NET) data, external computing service (NET for Computing) data, internal computing service (Computing for NET) data, AI model data, AI training data, and AI inference data.

[0287] Example 3:

[0288] Please refer to Figure 16 , Figure 16 This is a schematic diagram of Example 3 of the uplink SDAP data PDU in Embodiment 2 of this application. The SDAP header of the uplink SDAP data PDU includes: D / C (Data / Control), HPI (High Priority Indicator), and QFI. D / C and QFI are information elements in the existing SDAP header, while HPI is a newly added information element. HPI is used to indicate whether the priority of the uplink SDAP data PDU is higher than that of non-new service data.

[0289] In this embodiment of the application, when the SDAP entity of the first device receives an SDAP SDU of a QoS flow indicated by a QFI or a new service task indicated by a task identifier from the upper layer, a second operation is performed, the second operation including:

[0290] If the DRB mapped to the SDAP SDU has an SDAP header configured, an SDAP PDU is constructed according to the high priority indication in the SDAP header, and the constructed SDAP PDU is submitted to the lower layer.

[0291] Example 4:

[0292] Please refer to Figure 17 , Figure 17 This is a schematic diagram of Example 4 of the uplink SDAP data PDU in Embodiment 2 of this application. The SDAP header of the uplink SDAP data PDU includes: D / C (Data / Control), LPI (Priority Indicator), and QFI. D / C and QFI are information elements in the existing SDAP header, while LPI is a newly added information element. LPI is used to indicate whether the priority of the uplink SDAP data PDU is lower than that of non-new service data.

[0293] In this embodiment of the application, when the SDAP entity of the first device receives an SDAP SDU of a QoS flow indicated by a QFI or a new service task indicated by a task identifier from the upper layer, a second operation is performed, the second operation including:

[0294] If the DRB mapped to the SDAP SDU has an SDAP header configured, an SDAP PDU is constructed according to the low priority indication in the SDAP header, and the constructed SDAP PDU is submitted to the lower layer.

[0295] Example 5:

[0296] Please refer to Figure 18 , Figure 18 This is a schematic diagram of Example 5 of the uplink SDAP data PDU in Embodiment 2 of this application. The SDAP header of the uplink SDAP data PDU includes: D / C (Data / Control), QFI, LPI, and HPI. D / C and QFI are information elements in the existing SDAP header, while HPI and LPI are newly added information elements. LPI is used to indicate whether the priority of the uplink SDAP data PDU is lower than that of non-new service data, and HPI is used to indicate whether the priority of the uplink SDAP data PDU is higher than that of non-new service data.

[0297] In this embodiment of the application, when the SDAP entity of the first device receives an SDAP SDU of a QoS flow indicated by a QFI or a new service task indicated by a task identifier from the upper layer, a second operation is performed, the second operation including:

[0298] If the DRB mapped to the SDAP SDU has an SDAP header configured, an SDAP PDU is constructed based on the high priority indication and low priority indication in the SDAP header, and the constructed SDAP PDU is submitted to the lower layer.

[0299] Example 6:

[0300] Please refer to Figure 19 , Figure 19 This is a schematic diagram of Example 6 of the uplink SDAP data PDU in Embodiment 2 of this application. The SDAP header of this uplink SDAP data PDU includes: D / C (Data / Control), QFI, and RTI (RAN Termination Indication). D / C and QFI are information elements in the existing SDAP header, while RTI is a newly added information element, namely RAN Termination Indication, used to indicate whether the SDAP PDU is parsed by the RAN device.

[0301] In this embodiment of the application, when the SDAP entity of the first device receives an SDAP SDU of a QoS flow indicated by a QFI or a new service task indicated by a task identifier from the upper layer, a second operation is performed, the second operation including:

[0302] If the DRB mapped to the SDAP SDU has an SDAP header configured, an SDAP PDU is constructed based on the SDAP header, and the constructed SDAP PDU is submitted to the lower layer. The SDAP header includes RTI.

[0303] Optionally, when NSI (New Service Indicator) is 1, QFI can be used as TI (Task Identifier).

[0304] Optionally, when the RTI (RAN Termination Indication) is 1, the base station will perform fusion processing on the data corresponding to the same TI for the same UE, or the base station will perform fusion processing on the data corresponding to the same TI for different UEs.

[0305] Example 7:

[0306] Please refer to Figure 20 , Figure 20This is a schematic diagram of Example 7 of the uplink SDAP data PDU in Embodiment 2 of this application. The SDAP header of this uplink SDAP data PDU includes: D / C (Data / Control), NSI (New Service Indicator), QFI, NST (New Service Type Indicator), PI (Priority Indicator), NHNT (Next Hop Node Type), EI (Extended Header Indicator), Next Hop Address, and Destination Address. Among them, D / C and QFI are information elements in the existing SDAP header, while NSI, EI, NST, PI, NHNT, Next Hop Address, and Destination Address are newly added information elements. NSI is used to indicate whether the uplink SDAP data PDU is new service data; NST (New Service Type Indicator) is used to indicate the type of new service; PI (Priority Indicator) is used to indicate the priority information of the uplink SDAP data PDU; NHNT is used to indicate the next hop node type after the uplink SDAP data PDU is transmitted to the RAN device; and EI (Extended Header Indicator) is used to indicate whether it is necessary to parse the information elements after the extended header indication. The Next Hop Address indicates the address of the next hop node of the SDAP PDU; the Destination Address indicates the destination address of the SDAP PDU.

[0307] In this embodiment of the application, when the SDAP entity of the first device receives an SDAP SDU of a QoS flow indicated by a QFI or a new service task indicated by a task identifier from the upper layer, a second operation is performed, the second operation including:

[0308] If the DRB mapped by the SDAP SDU has an SDAP header configured, an SDAP PDU is constructed based on the SDAP header, and the constructed SDAP PDU is submitted to the lower layer.

[0309] Optionally, the next-hop node type is a user plane function, a data plane function, or a new service function, wherein the new service function is a perception function, an AI function, or a computing function.

[0310] Optionally, if the EI (Extended Header Indicator) is 1, the Next Hop Address or Destination Address is parsed, and the uplink SDAP data PDU is sent to the corresponding node address or destination address.

[0311] It should be noted that, in the embodiments of this application, the existence of a certain information unit in the SDAP header, the abbreviation of the information unit, the number of bits of the information unit, or the order of the information units are merely examples and are not intended to limit the SDAP header of this application.

[0312] Embodiment 3 of this application: Adding a new SDAP-enhanced downlink SDAP data PDU format

[0313] Examples 1 and 2 extend and enhance the SDAP header of existing SDAP data PDUs. The approach in this example is that the RDI (Reflected QoS Flow to DRB Mapping Indicator) and RQI (Reflected QoS Flow Indicator) in the downlink SDAP data PDU header may not be needed in new services, and even QFI (Qos Flow Identifier) ​​may not be required. Therefore, the SDAP header of the downlink SDAP data PDU in this example uses a newly defined format. This newly defined format may have lower header overhead when used for new services, or it can carry more information about new services while maintaining the same overhead. The newly added downlink SDAP data PDU can also support both existing user plane data transmission and new service data transmission, and can flexibly process new service data according to its priority.

[0314] In this embodiment, a potential downlink SDAP data PDU format example is shown below.

[0315] Example 1:

[0316] Please refer to Figure 21 , Figure 21 This is a schematic diagram of Example 1 of the downlink SDAP data PDU in Embodiment 3 of this application. The SDAP header of the downlink SDAP data PDU includes: NSI (New Service Indicator), R (Reserved), and QFI. NSI is used to indicate whether the downlink SDAP data PDU is new service data.

[0317] In this embodiment of the application, when the SDAP entity of the first device receives SDAP data PDU of a QoS flow indicated by a QFI or a new service task indicated by a task identifier from the lower layer, a first operation is performed, the first operation including:

[0318] If the DRB receiving the SDAP data PDU has an SDAP header configured, the SDAP header contains a New Service Data Indicator, which processes existing user plane data or new service data. For example, the New Service Data Indicator indicates that the SDAP SDU is new service data, and the retrieved SDAP SDU is transmitted to the modem. Optionally, when the NSI indicates that the SDAP data PDU is new service data, the QFI information element shown is a Task Identifier (TI).

[0319] If the DRB receiving the SDAP PDU does not have an SDAP header configured, the SDAP SDU is retrieved from the SDAP PDU according to the format of the SDAP PDU without an SDAP header, and the retrieved SDAP SDU is transmitted to the upper layer.

[0320] The advantage of this new SDAP data PDU is that it maintains the same number of QFI bits and can also indicate new service data. Even reserving (R) 1 bit to account for the needs of new services can be used as a QFI bit, thus satisfying more QoS flow classification requirements by adding 1 bit to the QFI, such as supporting longer task identifiers.

[0321] Example 2:

[0322] Please refer to Figure 22 , Figure 22 This is a schematic diagram of Example 2 of the downlink SDAP data PDU in Embodiment 3 of this application. The SDAP header of the downlink SDAP data PDU includes: QFI, LPI, and HPI, wherein LPI is used to indicate whether the priority of the downlink SDAP data PDU is lower than that of non-new service data, and HPI is used to indicate whether the priority of the downlink SDAP data PDU is higher than that of non-new service data.

[0323] In this embodiment of the application, when the SDAP entity of the first device receives SDAP data PDU of a QoS flow indicated by a QFI or a new service task indicated by a task identifier from the lower layer, a first operation is performed, the first operation including:

[0324] If the DRB receiving the SDAP data PDU has configured an SDAP header, the SDAP header contains high priority and low priority indications. Based on the high priority and low priority indications, the SDAP SDU is retrieved from the SDAP PDU and transmitted to the upper layer.

[0325] In this embodiment, the addition of SDAP data PDUs also supports higher or lower priority indications for new services while keeping the QFI bit count unchanged.

[0326] Example 3:

[0327] Please refer to Figure 23 , Figure 23 This is a schematic diagram of Example 3 of the downlink SDAP data PDU in Embodiment 3 of this application. The SDAP header of the downlink SDAP data PDU includes: SFT, HPI, LPI, and TI. Among them, LPI is used to indicate whether the priority of the downlink SDAP data PDU is lower than that of non-new service data, HPI is used to indicate whether the priority of the downlink SDAP data PDU is higher than that of non-new service data, Service flow Type (SFT) is used to indicate the type of user plane data, and TI indicates the task identifier of the new service.

[0328] In this embodiment of the application, when the SDAP entity of the first device receives SDAP data PDU of a QoS flow indicated by a QFI or a new service task indicated by a task identifier from the lower layer, a first operation is performed, the first operation including:

[0329] If the DRB receiving the SDAP data PDU has configured an SDAP header, it retrieves the SDAP SDU from the SDAP PDU according to the SDAP header and transmits the retrieved SDAP SDU to the upper layer.

[0330] Embodiment 4 of this application: An SDAP control PDU format

[0331] Example 1 extends and enhances the SDAP header of existing downlink SDAP data PDUs. Example 3 adds a new downlink SDAP data PDU. Example 2 extends and enhances the SDAP header of existing uplink SDAP data PDUs. The solution in this example is: currently, downlink only has SDAP data PDUs, while uplink SDAP control PDUs support end-markers. This example provides an SDAP control PDU format that can be used for indicating downlink and / or uplink SDAP control information.

[0332] In this embodiment, the SDAP control PDU can be an uplink SDAP control PDU with added information elements, or it can be a newly added uplink SDAP control PDU format and / or a newly added downlink SDAP control PDU format.

[0333] The SDAP control PDU format includes at least one of the following:

[0334] A start-marker is used to indicate that a first data PDU following a first control PDU containing the start-marker will be processed according to the information element in the first control PDU, and that the SDU corresponding to the first data PDU will be mapped to the DRB of the first control PDU, wherein the first control PDU and the first data PDU belong to the same QoS flow or the same new service task; or, it is used to indicate that a third data PDU following a second data PDU containing the start-marker will be processed according to the information element in the second data PDU, wherein the second data PDU and the third data PDU belong to the same QoS flow or the same new service task;

[0335] The first quantity is used to indicate the number of data PDUs that need to be processed according to the information unit in the first control PDU or the information unit in the second data PDU;

[0336] An end-marker is used to indicate that a third data PDU following a second control PDU containing the end-marker will no longer be processed according to the information element in the first control PDU, and that the SDU corresponding to the third data PDU will no longer be mapped to the DRB of the first control PDU, wherein the first control PDU and the second control PDU belong to the same QoS flow or the same new service task; or, it is used to indicate that a fifth data PDU following a fourth data PDU containing the end-marker will no longer be processed according to the information element in the second data PDU, wherein the second data PDU and the fourth data PDU belong to the same QoS flow or the same new service task;

[0337] New Service Indication (NSI) is used to indicate whether the SDAP PDU is new service data;

[0338] New Service Type (NST) is used to indicate the type of new service; optionally, the type of new service includes at least one of the following: perception service, AI service, computing service, external perception service, internal perception service, external AI service, internal AI service, external computing service, internal computing service, AI model, AI training, AI inference;

[0339] The next hop node type (NHNT) indicates the type of the next hop node after the SDAP PDU is transmitted to the RAN device. Optionally, the next hop node type is a user plane function (UPF), a data plane function (DPF), or a new service function, where the new service function is a sensing function, an AI function, or a computing function.

[0340] Priority indicator, used to indicate the priority information of the SDAP PDU; if there is no priority indicator in SDAP, the priority in the corresponding QoS parameters can be applied by default, just like the existing user plane data;

[0341] A task identifier is used to identify a new service task; the task identifier can also be a new service flow identifier. Existing QoS flows belong to a traditional user plane service and are QoS flows for a single UE, meaning one QoS flow is mapped to at most one DRB or multiple QoS flows are mapped to one DRB. New service tasks may sometimes be associated with multiple UEs, meaning one new service task is mapped to one DRB or one new service task is mapped to multiple DRBs. When mapping to multiple DRBs, if multiple DRBs of multiple UEs are involved, then the task identifier is a single task identifier shared by all UEs.

[0342] The RAN termination indication is used to indicate whether the SDAP PDU is parsed by the RAN device. For example, when the SDAP PDU is internal sensing service (SensingforNET) data or internal AI service (AIforNET) data, the sensing data or AI data may be sent to the base station. After parsing, the base station uses it for auxiliary channel estimation, beam management, or fine-tuning of AI models, etc. In this case, it is necessary to indicate in the SDAP header that the SDAP PDU is parsed by the RAN device. As another example, when the SDAP PDU is external sensing service (NETforSensing) data, the UE's external sensing service data is processed by the base station before being sent to the core network sensing function. In this case, it is necessary to indicate in the SDAP header that the SDAP PDU is parsed by the RAN device.

[0343] The extended header indicator is used to indicate whether the information unit following the extended header indicator needs to be parsed; for example, when set to 0, it means that the information unit following the extended header indicator does not exist, and if it exists, it will not be parsed; when set to 1, the information unit following the extended header indicator should be parsed.

[0344] The next-hop node address is used to indicate the next-hop node address of the SDAP PDU. When the new service does not use the IP protocol to encapsulate the data packet, but uses a 3GPP-defined protocol (such as the location protocol) to encapsulate the data packet, then the next-hop node address is needed to indicate which node to send the SDAP PDU to.

[0345] The destination address indicates the destination address of the SDAP PDU. When the new service does not encapsulate data packets using the IP protocol, but instead uses a 3GPP-defined protocol (such as a location protocol), the destination address is needed to resolve the routing issue for sending the SDAP PDU. The base station can determine the next-hop node based on the destination address.

[0346] Optionally, the SDAP control PDU format may further include a QoS flow identifier (QFI), a task identifier, or a PDU type indicator. The PDU type indicator is used to indicate whether the SDAP PDU is an SDAP data PDU or an SDAP control PDU.

[0347] For example, when the SDAP control PDU includes a start marker, and the SDAP control PDU also includes at least one of the following: new service indication, new service type, next-hop node type, priority indication, task identifier, RAN termination indication, extension header indication, next-hop node address, and destination address, then the SDAP entity processes the SDAP data PDU located after the SDAP control PDU including the start marker, which belongs to the same QoS flow or new service task as the SDAP control PDU including the start marker, according to at least one of the following in the SDAP control PDU including the start marker: new service indication, new service type, next-hop node type, priority indication, task identifier, RAN termination indication, extension header indication, next-hop node address, and destination address. If the SDAP control PDU including the start marker includes a QoS flow identifier (QFI) or a task identifier, then the SDAP entity processes the SDAP data PDU following the SDAP control PDU including the start marker, which has the same QFI or task identifier, according to at least one of the following in the SDAP control PDU including the start marker: new service indication, new service type, next-hop node type, priority indication, task identifier, RAN termination indication, extended header indication, next-hop node address, and destination address. The processing includes at least one of the following:

[0348] Retrieve the SDAP SDU from the SDAP PDU and transmit the retrieved SDAP SDU (if it contains an SDAP control PDU with a start marker) to the upper layer;

[0349] The SDAP PDU is constructed based on the SDAP control PDU, and the constructed SDAP PDU is submitted to the lower layer.

[0350] In the example above, the SDAP data PDUs following the SDAP control PDU containing the start marker may not carry an SDAP header. These SDAP data PDUs implicitly indicate that the information units of the aforementioned SDAP control PDU containing the start marker should be used for processing. Sending information once via the SDAP control PDU containing the start marker saves overhead compared to including an SDAP header in every SDAP data PDU.

[0351] Similarly, the SDAP PDU formats of the aforementioned Embodiment 1, Embodiment 2, or Embodiment 3 may also include a start marker or an end marker. When the SDAP PDU formats of the aforementioned Embodiment 1, Embodiment 2, or Embodiment 3 also include a start marker or an end marker, this means that the SDAP data PDU may include a start marker or an end marker. One example is that an SDAP entity processes the SDAP data PDU containing the start marker and subsequent SDAP PDUs with the same QFI or task identifier, based on at least one of the following in the SDAP data PDU containing the start marker: new service indication, new service type, next-hop node type, priority indication, task identifier, RAN termination indication, extended header indication, next-hop node address, and destination address. When the SDAP PDU format of the aforementioned Embodiment 1, Embodiment 2, or Embodiment 3 further includes a start marker or an end marker, another example is that the SDAP entity processes SDAP data PDUs including a start marker, SDAP data PDUs including an end marker, and SDAP PDUs with the same QFI or task identifier located between SDAP data PDUs including a start marker and SDAP data PDUs including an end marker, based on at least one of the following in the SDAP data PDU including the start marker: new service indication, new service type, next-hop node type, priority indication, task identifier, RAN termination indication, extended header indication, next-hop node address, and destination address. The processing includes at least one of the following:

[0352] Retrieve the SDAP SDU from the SDAP PDU and transmit the retrieved SDAP SDU (if it contains a control PDU with a start marker) to the upper layer;

[0353] An SDAP PDU is constructed based on the SDAP header, and the constructed SDAP PDU is submitted to the lower layer.

[0354] Embodiment 5 of this application: A method for establishing SDAP entities

[0355] The solution in this embodiment is to establish an SDAP entity based on an RRC request, thereby solving the problem of RRC configuration in the SDAP header branch of the aforementioned embodiments one to three.

[0356] The SDAP entity creation method in this embodiment includes:

[0357] Step 1: Optionally, the UE sends a message to report terminal capability information, which includes at least one of the following:

[0358] Does the UE support the new service? If the UE supports the new service, then the aforementioned user plane protocol sublayer header should be used as needed.

[0359] Does the UE support the SDAP PDU format with the SDAP header?

[0360] Step 2: The base station sends DRB addition information (i.e., the first configuration information mentioned above) to the UE as needed, for example, via an RRC reconfiguration message. The DRB addition message includes downlink SDAP header (sdap-HeaderDL) indication information and / or uplink SDAP header (sdap-HeaderUL) indication information. The downlink SDAP header (sdap-HeaderDL) indication information is used to indicate the downlink SDAP header configuration information. The uplink SDAP header (sdap-HeaderDL) indication information is used to indicate the uplink SDAP header configuration information.

[0361] One example is indicating whether the configuration information is included by whether or not the above indication information is present or absent.

[0362] Alternatively, another example is to represent configuration information by size, such as 0 bits indicating no SDAP header, 8 bits indicating a SDAP header of a certain format, 16 bits indicating a SDAP header of a certain format, etc. Another example is to identify configuration information by the SDAP header format name, such as Format0, format1, etc.

[0363] When an SDAP header is present, it contains at least one of the following pieces of information:

[0364] New Service Indication (NSI) is used to indicate whether the SDAP PDU is new service data;

[0365] New Service Type (NST) is used to indicate the type of new service;

[0366] User plane data type, used to indicate the user plane data type of the SDAP PDU;

[0367] Next hop node type (NHNT) indicates the type of the next hop node after the SDAP PDU is transmitted to the RAN device;

[0368] Priority indicator, used to indicate the priority information of the SDAP PDU; if there is no priority indicator in SDAP, the priority in the corresponding QoS parameters can be applied by default, just like the existing user plane data;

[0369] A task identifier is used to identify a new service task; the task identifier can also be a new service flow identifier. Existing QoS flows belong to a traditional user plane service and are QoS flows for a single UE, meaning one QoS flow is mapped to at most one DRB or multiple QoS flows are mapped to one DRB. New service tasks may sometimes be associated with multiple UEs, meaning one new service task is mapped to one DRB or one new service task is mapped to multiple DRBs. When mapping to multiple DRBs, if multiple DRBs of multiple UEs are involved, then the task identifier is a single task identifier shared by all UEs.

[0370] The RAN termination indication is used to indicate whether the SDAP PDU is parsed by the RAN device. For example, when the SDAP PDU is internal sensing service (SensingforNET) data or internal AI service (AIforNET) data, the sensing data or AI data may be sent to the base station. After parsing, the base station uses it for auxiliary channel estimation, beam management, or fine-tuning of AI models, etc. In this case, it is necessary to indicate in the SDAP header that the SDAP PDU is parsed by the RAN device. As another example, when the SDAP PDU is external sensing service (NETforSensing) data, the UE's external sensing service data is processed by the base station before being sent to the core network sensing function. In this case, it is necessary to indicate in the SDAP header that the SDAP PDU is parsed by the RAN device.

[0371] The extended header indicator is used to indicate whether the information unit following the extended header indicator needs to be parsed; for example, when set to 0, it means that the information unit following the extended header indicator does not exist, and if it exists, it will not be parsed; when set to 1, the information unit following the extended header indicator should be parsed.

[0372] The next-hop node address is used to indicate the next-hop node address of the SDAP PDU. When the new service does not use the IP protocol to encapsulate the data packet, but uses a 3GPP-defined protocol (such as the location protocol) to encapsulate the data packet, then the next-hop node address is needed to indicate which node to send the SDAP PDU to.

[0373] The destination address indicates the destination address of the SDAP PDU. When the new service does not encapsulate data packets using the IP protocol, but instead uses a 3GPP-defined protocol (such as a location protocol), the destination address is needed to resolve the routing issue for sending the SDAP PDU. The base station can determine the next-hop node based on the destination address.

[0374] A start-marker is used to indicate that a first data PDU following a first control PDU containing the start-marker will be processed according to the information element in the first control PDU, and that the SDU corresponding to the first data PDU will be mapped to the DRB of the first control PDU, wherein the first control PDU and the first data PDU belong to the same QoS flow or the same new service task; or, it is used to indicate that a third data PDU following a second data PDU containing the start-marker will be processed according to the information element in the second data PDU, wherein the second data PDU and the third data PDU belong to the same QoS flow or the same new service task;

[0375] The first quantity is used to indicate the number of data PDUs that need to be processed according to the information unit in the first control PDU or the information unit in the second data PDU;

[0376] An end-marker is used to indicate that a third data PDU following a second control PDU containing the end-marker will no longer be processed according to the information element in the first control PDU, and that the SDU corresponding to the third data PDU will no longer be mapped to the DRB of the first control PDU, wherein the first control PDU and the second control PDU belong to the same QoS flow or the same new service task; or, it is used to indicate that a fifth data PDU following a fourth data PDU containing the end-marker will no longer be processed according to the information element in the second data PDU, wherein the second data PDU and the fourth data PDU belong to the same QoS flow or the same new service task.

[0377] Step 3: The UE receives the DRB add information and establishes an SDAP entity.

[0378] In this embodiment, enhancements to the user plane protocol enable it to support not only existing user plane data transmission but also new 6G service data transmission. By designing the user plane protocol sublayer header, the requirements of new service data are met with minimal header overhead, thus resolving issues encountered when transmitting new service data through the existing user plane. These issues include, but are not limited to, the inability to terminate at radio access network nodes, the inability to support higher or lower priorities than existing user plane data, the inability to map new service QoS flows or tasks to multiple DRBs, and the additional latency caused by UPF processing and forwarding. The introduction of a new SDAP header further reduces overhead, or allows for the carrying of more new service information with the same overhead. This embodiment enables flexible mapping of new service QoS flows or tasks at the protocol data unit granularity to DRBs or DRB groups, making it more suitable for situations where individual protocol data units are long.

[0379] The user plane data transmission method provided in this application can be executed by a user plane data transmission device. This application uses the execution of the user plane data transmission method by a user plane data transmission device as an example to illustrate the user plane data transmission device provided in this application.

[0380] This application provides a user plane data transmission device. As an example, the user plane data transmission device can be a communication device or a component within a communication device, such as a chip. The communication device can be a terminal, a network-side device, or a server, etc. Exemplarily, the terminal can be, but is not limited to, the type of terminal 11 listed above, and the network-side device can be, but is not limited to, the type of network-side device 12 listed above. This application does not impose specific limitations.

[0381] The user plane data transmission device includes a receiving module, a transmitting module, and a processing module. These modules can be implemented in software or hardware. When implemented in hardware, the processing module can be implemented by a processor. For example, the processor can include general-purpose processors, special-purpose processors, etc., such as central processing units (CPUs), microprocessors, digital signal processors (DSPs), artificial intelligence (AI) processors, graphics processing units (GPUs), application-specific integrated circuits (ASICs), network processors (NPs), field-programmable gate arrays (FPGAs), or other programmable logic devices, gate circuits, transistors, discrete hardware components, etc. The receiving and transmitting modules can be implemented by a communication interface, which can include one or more of the following: transceivers, pins, circuits, buses, radio frequency units, etc.

[0382] For details, see Figure 24 When the user plane data transmission device is a terminal or a component within a terminal, the user plane data transmission device 10 includes:

[0383] Processing module 11 is configured to perform a first operation upon receiving an SDAP PDU for a new service task indicated by a QoS flow indicated by a QFI or a task identifier indicated by a task identifier from a lower layer. The first operation includes retrieving an SDAPSDU from the SDAP PDU and transmitting the retrieved SDAP SDU to the upper layer. Alternatively, upon receiving an SDAP SDU for a new service task indicated by a QoS flow indicated by a QFI or a task identifier indicated by a task identifier from an upper layer, the second operation includes constructing an SDAPPDU and submitting the constructed SDAP PDU to the lower layer. The SDAP PDU is an SDAPPDU in a format that supports new services.

[0384] Optionally, the SDAP PDU supporting the new service format includes at least one of: new service data, SDAP control PDU supporting the new service, and user plane data with the SDAP header, wherein the SDAP header supports the transmission of the new service data.

[0385] Optionally, retrieving an SDAP SDU from the SDAP PDU and transmitting the retrieved SDAP SDU to the upper layer includes at least one of the following:

[0386] If the SDAP PDU is an SDAP data PDU, and the DRB receiving the SDAP PDU has configured an SDAP header, the SDAP SDU is retrieved from the SDAP PDU according to the SDAP header, and the retrieved SDAP SDU is transmitted to the upper layer.

[0387] If the SDAP PDU is an SDAP data PDU and the DRB receiving the SDAP PDU is not configured with an SDAP header, the SDAP SDU is retrieved from the SDAP PDU according to the format of the SDAP PDU without an SDAP header, and the retrieved SDAPSDU is transmitted to the upper layer.

[0388] If the SDAP PDU is an SDAP control PDU, retrieve the SDAP SDU from the SDAP PDU associated with the SDAP control PDU and transmit the retrieved SDAP SDU to the upper layer.

[0389] Optionally, retrieving the SDAP SDU from the SDAP PDU according to the SDAP header and transmitting the retrieved SDAP SDU to the upper layer includes at least one of the following:

[0390] The SDAP SDU is retrieved from the SDAP PDU according to the SDAP header. If the SDAP header contains a new service data indication and the new service data indication indicates that the SDAP PDU is new service data, the retrieved SDAP SDU is transmitted to the modem.

[0391] The SDAP SDU is retrieved from the SDAP PDU according to the SDAP header. If the SDAP header contains a next-hop address, the retrieved SDAP SDU is transmitted to the next-hop address.

[0392] If the SDAP header contains a priority indication, the SDAP SDU is retrieved from the SDAP PDU according to the priority indication, and the retrieved SDAP SDU is transmitted to the upper layer.

[0393] Optionally, the construction of the SDAP PDU and the submission of the constructed SDAP PDU to the lower layer includes at least one of the following:

[0394] If the SDAP SDU is an SDAP data SDU, and the DRB mapped by the SDAP SDU has been configured with an SDAP header, an SDAP PDU is constructed based on the SDAP header, and the constructed SDAP PDU is submitted to the lower layer.

[0395] If the SDAP SDU is an SDAP data SDU and the DRB mapped by the SDAP SDU is not configured with an SDAP header, an SDAP PDU is constructed according to the SDAP PDU format without an SDAP header, and the constructed SDAP PDU is submitted to the lower layer.

[0396] If the SDAP SDU is an SDAP control SDU, construct an SDAP PDU and submit the constructed SDAP PDU to the lower layer.

[0397] Optionally, the second operation further includes at least one of the following:

[0398] If there is no mapping rule for storing the QoS flow to the DRB, map the SDAP SDU to the default DRB;

[0399] If the mapping rules from the QoS flow to the DRB are stored, map the SDAP SDU to the DRB corresponding to the mapping rules from the QoS flow to the DRB.

[0400] If there is no mapping rule for storing the new service task to the DRB, map the SDAP SDU to the default DRB;

[0401] If the mapping rule from the new service task to the DRB is stored, the SDAP SDU is mapped to the DRB corresponding to the mapping rule from the new service task to the DRB.

[0402] Optionally, the control PDU supporting the new service or the SDAP header includes at least one of the following information elements:

[0403] New service data indication is used to indicate whether the SDAP PDU is new service data;

[0404] New service type, used to indicate the type of new service;

[0405] User plane data type, used to indicate the user plane data type of the SDAP PDU;

[0406] Next-hop node type, used to indicate the type of the next-hop node after the SDAP PDU is transmitted to the RAN device;

[0407] Priority indicator, used to indicate the priority information of the SDAP PDU;

[0408] Task identifier, used to identify new service tasks;

[0409] RAN termination indication is used to indicate whether the SDAP PDU has been resolved by the RAN device;

[0410] An extension header indicator is used to indicate whether the information unit following the extension header indicator needs to be parsed.

[0411] The next-hop node address is used to indicate the next-hop node address of the SDAP PDU;

[0412] Destination address, used to indicate the destination address of the SDAP PDU;

[0413] A start-marker is used to indicate that a first data PDU following a first control PDU containing the start-marker will be processed according to the information element in the first control PDU, and that the SDU corresponding to the first data PDU will be mapped to the DRB of the first control PDU, wherein the first control PDU and the first data PDU belong to the same QoS flow or the same new service task; or, it is used to indicate that a third data PDU following a second data PDU containing the start-marker will be processed according to the information element in the second data PDU, wherein the second data PDU and the third data PDU belong to the same QoS flow or the same new service task;

[0414] The first quantity is used to indicate the number of data PDUs that need to be processed according to the information unit in the first control PDU or the information unit in the second data PDU;

[0415] An end-marker is used to indicate that a third data PDU following a second control PDU containing the end-marker will no longer be processed according to the information element in the first control PDU, and that the SDU corresponding to the third data PDU will no longer be mapped to the DRB of the first control PDU, wherein the first control PDU and the second control PDU belong to the same QoS flow or the same new service task; or, it is used to indicate that a fifth data PDU following a fourth data PDU containing the end-marker will no longer be processed according to the information element in the second data PDU, wherein the second data PDU and the fourth data PDU belong to the same QoS flow or the same new service task.

[0416] Optionally, the SDAP control PDU supporting the new service or the SDAP header may further include at least one of a PDU type indicator and a QoS flow identifier, wherein the PDU type indicator is used to indicate whether the SDAP PDU is an SDAP control PDU or an SDAP data PDU.

[0417] Optionally, the user plane data types include at least one of the following: non-new service data, new service data, perception service data, AI service data, computing service data, external perception service data, internal perception service data, external AI service data, internal AI service data, external computing service data, internal computing service data, AI model data, AI training data, and AI inference data.

[0418] Optionally, the new service type includes at least one of the following: perception service, AI service, computing service, external perception service, internal perception service, external AI service, internal AI service, external computing service, internal computing service, AI model, AI training, and AI inference.

[0419] Optionally, the next-hop node type is a user plane function, a data plane function, or a new service function, wherein the new service function is a perception function, an AI function, or a computing function.

[0420] Optionally, the priority indication includes at least one of the following: a high priority indication and a low priority indication, wherein the high priority indication is used to indicate whether the priority of the new service data is higher than that of the non-new service data, and the low priority indication is used to indicate whether the priority of the new service data is lower than that of the non-new service data.

[0421] Optionally, the SDAP header further includes a QFI information element, which indicates the task identifier when the new service data indicates that the SDAP PDU is new service data.

[0422] Optionally, the SDAP entity is located in an SDAP sublayer, which supports at least one of the following functions:

[0423] Mapping between uplink new service QoS streams and DRBs;

[0424] Mapping between downlink new service QoS flows and DRBs;

[0425] Mapping between uplink new service QoS flows and DRB groups;

[0426] Mapping between downlink new service QoS flows and DRB groups;

[0427] Mapping between new uplink service tasks and DRBs;

[0428] Mapping between new downlink service tasks and DRB;

[0429] Mapping between new service tasks and DRB groups;

[0430] Mapping between new downlink service tasks and DRB groups;

[0431] New service QoS flows are marked in uplink UL packets;

[0432] New service QoS flows are marked in downlink DL packets;

[0433] Mark new service tasks in the uplink data packets;

[0434] New service tasks are marked in the downlink data packets.

[0435] Optional, also includes:

[0436] A receiving module is configured to receive first configuration information, which is used to indicate the addition of a DRB. The first configuration information includes SDAP header configuration information; the SDAP header includes at least one of an uplink SDAP header and a downlink SDAP header.

[0437] The processing module 11 is used to establish the SDAP entity based on the first configuration information.

[0438] Optionally, the SDAP header configuration information includes one of the following:

[0439] Does an SDAP header exist?

[0440] The number of bits in the SDAP header;

[0441] The format name of the SDAP header.

[0442] Optional, also includes:

[0443] A sending module is configured to send second configuration information if multiple SDAP control PDU formats are available, wherein the second configuration information includes a configured SDAP control PDU format; the control PDU format includes at least one of uplink control PDU and downlink control PDU; and the configured SDAP control PDU format is one of the multiple SDAP control PDU formats.

[0444] or

[0445] The receiving module is configured to receive second configuration information, which includes a configured SDAP control PDU format; the control PDU format includes at least one of uplink control PDU and downlink control PDU.

[0446] Optional, also includes:

[0447] The sending module is used to report terminal capability information, which includes at least one of the following:

[0448] Does the terminal support the new service?

[0449] Does the terminal support the SDAP PDU format with the SDAP header?

[0450] Does the terminal support the SDAP control PDU that supports the new service?

[0451] In this application embodiment, the processing method of new service data in the SDAP entity is clarified to meet the transmission requirements of new service data.

[0452] The user plane data transmission device provided in this application embodiment can achieve... Figure 5 or Figure 7 The various processes implemented in the method embodiments achieve the same technical effect, and will not be described again here to avoid repetition.

[0453] See Figure 25 When the user plane data transmission device is a network-side device or a component of a network-side device, the user plane data transmission device 20 includes...

[0454] Processing module 21 is configured to perform a first operation upon receiving an SDAP PDU for a QoS flow indicated by a QFI or a new service task indicated by a task identifier from a lower layer. The first operation includes retrieving an SDAPSDU from the SDAP PDU and transmitting the retrieved SDAP SDU to the upper layer. Alternatively, upon receiving an SDAP SDU for a QoS flow indicated by a QFI or a new service task indicated by a task identifier from an upper layer, the second operation includes constructing an SDAPPDU and submitting the constructed SDAP PDU to the lower layer. The SDAP PDU is an SDAPPDU in a format that supports new services.

[0455] Optionally, the SDAP PDU supporting the new service format includes at least one of: new service data, SDAP control PDU supporting the new service, and user plane data with the SDAP header, wherein the SDAP header supports the transmission of the new service data.

[0456] Optionally, retrieving an SDAP SDU from the SDAP PDU and transmitting the retrieved SDAP SDU to the upper layer includes at least one of the following:

[0457] If the SDAP PDU is an SDAP data PDU, and the DRB receiving the SDAP PDU has configured an SDAP header, the SDAP SDU is retrieved from the SDAP PDU according to the SDAP header, and the retrieved SDAP SDU is transmitted to the upper layer.

[0458] If the SDAP PDU is an SDAP data PDU and the DRB receiving the SDAP PDU is not configured with an SDAP header, the SDAP SDU is retrieved from the SDAP PDU according to the format of the SDAP PDU without an SDAP header, and the retrieved SDAPSDU is transmitted to the upper layer.

[0459] If the SDAP PDU is an SDAP control PDU, retrieve the SDAP SDU from the SDAP PDU associated with the SDAP control PDU and transmit the retrieved SDAP SDU to the upper layer.

[0460] Optionally, retrieving the SDAP SDU from the SDAP PDU according to the SDAP header and transmitting the retrieved SDAP SDU to the upper layer includes at least one of the following:

[0461] The SDAP SDU is retrieved from the SDAP PDU according to the SDAP header. If the SDAP header contains a new service data indication and the new service data indication indicates that the SDAP PDU is new service data, the retrieved SDAP SDU is transmitted to the modem.

[0462] The SDAP SDU is retrieved from the SDAP PDU according to the SDAP header. If the SDAP header contains a next-hop address, the retrieved SDAP SDU is transmitted to the next-hop address.

[0463] If the SDAP header contains a priority indication, the SDAP SDU is retrieved from the SDAP PDU according to the priority indication, and the retrieved SDAP SDU is transmitted to the upper layer.

[0464] Optionally, the construction of the SDAP PDU and the submission of the constructed SDAP PDU to the lower layer includes at least one of the following:

[0465] If the SDAP SDU is an SDAP data SDU, and the DRB mapped by the SDAP SDU has been configured with an SDAP header, an SDAP PDU is constructed based on the SDAP header, and the constructed SDAP PDU is submitted to the lower layer.

[0466] If the SDAP SDU is an SDAP data SDU and the DRB mapped by the SDAP SDU is not configured with an SDAP header, an SDAP PDU is constructed according to the SDAP PDU format without an SDAP header, and the constructed SDAP PDU is submitted to the lower layer.

[0467] If the SDAP SDU is an SDAP control SDU, construct an SDAP PDU and submit the constructed SDAP PDU to the lower layer.

[0468] Optionally, the second operation further includes at least one of the following:

[0469] If there is no mapping rule for storing the QoS flow to the DRB, map the SDAP SDU to the default DRB;

[0470] If the mapping rules from the QoS flow to the DRB are stored, map the SDAP SDU to the DRB corresponding to the mapping rules from the QoS flow to the DRB.

[0471] If there is no mapping rule for storing the new service task to the DRB, map the SDAP SDU to the default DRB;

[0472] If the mapping rule from the new service task to the DRB is stored, the SDAP SDU is mapped to the DRB corresponding to the mapping rule from the new service task to the DRB.

[0473] Optionally, the control PDU supporting the new service or the SDAP header includes at least one of the following information elements:

[0474] New service data indication is used to indicate whether the SDAP PDU is new service data;

[0475] New service type, used to indicate the type of new service;

[0476] User plane data type, used to indicate the user plane data type of the SDAP PDU;

[0477] Next-hop node type, used to indicate the type of the next-hop node after the SDAP PDU is transmitted to the RAN device;

[0478] Priority indicator, used to indicate the priority information of the SDAP PDU;

[0479] Task identifier, used to identify new service tasks;

[0480] RAN termination indication is used to indicate whether the SDAP PDU has been resolved by the RAN device;

[0481] An extension header indicator is used to indicate whether the information unit following the extension header indicator needs to be parsed.

[0482] The next-hop node address is used to indicate the next-hop node address of the SDAP PDU;

[0483] Destination address, used to indicate the destination address of the SDAP PDU;

[0484] A start-marker is used to indicate that a first data PDU following a first control PDU containing the start-marker will be processed according to the information element in the first control PDU, and that the SDU corresponding to the first data PDU will be mapped to the DRB of the first control PDU, wherein the first control PDU and the first data PDU belong to the same QoS flow or the same new service task; or, it is used to indicate that a third data PDU following a second data PDU containing the start-marker will be processed according to the information element in the second data PDU, wherein the second data PDU and the third data PDU belong to the same QoS flow or the same new service task;

[0485] The first quantity is used to indicate the number of data PDUs that need to be processed according to the information unit in the first control PDU or the information unit in the second data PDU;

[0486] An end-marker is used to indicate that a third data PDU following a second control PDU containing the end-marker will no longer be processed according to the information element in the first control PDU, and that the SDU corresponding to the third data PDU will no longer be mapped to the DRB of the first control PDU, wherein the first control PDU and the second control PDU belong to the same QoS flow or the same new service task; or, it is used to indicate that a fifth data PDU following a fourth data PDU containing the end-marker will no longer be processed according to the information element in the second data PDU, wherein the second data PDU and the fourth data PDU belong to the same QoS flow or the same new service task.

[0487] Optionally, the SDAP control PDU supporting the new service or the SDAP header may further include at least one of a PDU type indicator and a QoS flow identifier, wherein the PDU type indicator is used to indicate whether the SDAP PDU is an SDAP control PDU or an SDAP data PDU.

[0488] Optionally, the user plane data types include at least one of the following: non-new service data, new service data, perception service data, AI service data, computing service data, external perception service data, internal perception service data, external AI service data, internal AI service data, external computing service data, internal computing service data, AI model data, AI training data, and AI inference data.

[0489] Optionally, the new service type includes at least one of the following: perception service, AI service, computing service, external perception service, internal perception service, external AI service, internal AI service, external computing service, internal computing service, AI model, AI training, and AI inference.

[0490] Optionally, the next-hop node type is a user plane function, a data plane function, or a new service function, wherein the new service function is a perception function, an AI function, or a computing function.

[0491] Optionally, the priority indication includes at least one of the following: a high priority indication and a low priority indication, wherein the high priority indication is used to indicate whether the priority of the new service data is higher than that of the non-new service data, and the low priority indication is used to indicate whether the priority of the new service data is lower than that of the non-new service data.

[0492] Optionally, the SDAP header further includes a QFI information element, which indicates the task identifier when the new service data indicates that the SDAP PDU is new service data.

[0493] Optionally, the SDAP entity is located in an SDAP sublayer, which supports at least one of the following functions:

[0494] Mapping between uplink new service QoS streams and DRBs;

[0495] Mapping between downlink new service QoS flows and DRBs;

[0496] Mapping between uplink new service QoS flows and DRB groups;

[0497] Mapping between downlink new service QoS flows and DRB groups;

[0498] Mapping between new uplink service tasks and DRBs;

[0499] Mapping between new downlink service tasks and DRB;

[0500] Mapping between new service tasks and DRB groups;

[0501] Mapping between new downlink service tasks and DRB groups;

[0502] New service QoS flows are marked in uplink UL packets;

[0503] New service QoS flows are marked in downlink DL packets;

[0504] Mark new service tasks in the uplink data packets;

[0505] New service tasks are marked in the downlink data packets.

[0506] In this application embodiment, the processing method of new service data in the SDAP entity is clarified to meet the transmission requirements of new service data.

[0507] The user plane data transmission device provided in this application embodiment can achieve... Figure 5 or Figure 7 The various processes implemented in the method embodiments achieve the same technical effect, and will not be described again here to avoid repetition.

[0508] like Figure 26 As shown, this application embodiment also provides a communication device 30, including a processor 31 and a memory 32. The memory 32 stores a program or instructions that can run on the processor 31. For example, when the communication device 30 is a terminal, the program or instructions executed by the processor 31 implement the various steps of the above-described user plane data transmission method embodiment and achieve the same technical effect. When the communication device 30 is a network-side device, the program or instructions executed by the processor 31 implement the various steps of the above-described user plane data transmission method embodiment and achieve the same technical effect. To avoid repetition, this will not be described again here.

[0509] This application embodiment also provides a terminal, including 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, for example... Figure 5 or Figure 7 The steps in the method embodiment shown are illustrated. This terminal embodiment corresponds to the above-described terminal-side method embodiment. All implementation processes and methods of the above-described method embodiments can be applied to this terminal embodiment and achieve the same technical effect. The terminal can be... Figure 24 or Figure 25 The user plane data transmission device shown. Specifically, Figure 27 A schematic diagram of the hardware structure of a terminal to implement an embodiment of this application.

[0510] The terminal 40 includes, but is not limited to, at least some of the following components: radio frequency unit 41, network module 42, audio output unit 43, input unit 44, sensor 45, display unit 46, user input unit 47, interface unit 48, memory 49, and processor 410.

[0511] Those skilled in the art will understand that the terminal 40 may also include a power supply (such as a battery) for supplying power to various components. The power supply may be logically connected to the processor x 10 through a power management system, thereby enabling functions such as managing charging, discharging, and power consumption through the power management system. Figure 27The terminal structure shown does not constitute a limitation on 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 elaborated here.

[0512] It should be understood that, in this embodiment, the input unit 44 may include a graphics processor 441 and a microphone 442. The graphics processor 441 processes image data of still images or videos obtained by an image capture device (such as a camera) in video capture mode or image capture mode. The display unit 46 may include a display panel 461, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 47 includes at least one of a touch panel 471 and other input devices 472. The touch panel 471 is also called a touch screen. The touch panel 471 may include two parts: a touch detection device and a touch controller. Other input devices 472 may include, but are not limited to, a physical keyboard, function keys (such as volume control buttons, power buttons, etc.), a trackball, a mouse, and a joystick, which will not be described in detail here.

[0513] In this embodiment, after receiving downlink data from the network-side device, the radio frequency unit 41 can transmit it to the processor 410 for processing; in addition, the radio frequency unit 41 can send uplink data to the network-side device. Typically, the radio frequency unit 41 includes, but is not limited to, antennas, amplifiers, transceivers, couplers, low-noise amplifiers, duplexers, etc.

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

[0515] Processor 410 may include one or more processing units; optionally, processor 410 integrates an application processor and a modem processor, wherein the application processor mainly handles operations involving the operating system, user interface, and applications, and the modem processor mainly handles wireless communication signals, such as a baseband processor. It is understood that the aforementioned modem processor may also not be integrated into processor 410.

[0516] The processor 410 is configured to perform a first operation upon receiving an SDAP PDU for a new service task indicated by a QoS flow indicated by a QFI or a task identifier indicated by a task identifier from a lower layer. The first operation includes retrieving an SDAP SDU from the SDAP PDU and transmitting the retrieved SDAP SDU to an upper layer. Alternatively, upon receiving an SDAP SDU for a new service task indicated by a QoS flow indicated by a QFI or a task identifier indicated by a task identifier from an upper layer, the processor 410 is configured to perform a second operation upon receiving an SDAP PDU for a new service task indicated by a QoS flow indicated by a QFI or a task identifier from an upper layer. The second operation includes constructing an SDAP PDU and submitting the constructed SDAP PDU to a lower layer. The SDAP PDU is configured to be an SDAP PDU in a format that supports the new service.

[0517] In this application embodiment, the processing method of new service data in the SDAP entity is clarified to meet the transmission requirements of new service data.

[0518] It is understood that the implementation process of each implementation method mentioned in this embodiment can be referred to Figure 5 or Figure 7 The relevant descriptions of the method embodiments shown herein, which achieve the same or corresponding technical effects, will not be repeated here to avoid duplication.

[0519] This application embodiment also provides a network-side device, including 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, for example... Figure 5 or Figure 7 The steps of the method embodiment shown are illustrated. This network-side device embodiment corresponds to the above-described network-side device method embodiment. All implementation processes and methods of the above-described method embodiments can be applied to this network-side device embodiment and can achieve the same technical effect.

[0520] Specifically, embodiments of this application also provide a network-side device, which can be... Figure 24 or Figure 25 The user plane data transmission device shown is an example. Figure 28 As shown, the network-side device 50 includes: an antenna 51, a radio frequency (RF) device 52, a baseband device 53, a processor 54, and a memory 55. The antenna 51 is connected to the RF device 52. In the uplink direction, the RF device 52 receives information through the antenna 51 and sends the received information to the baseband device 53 for processing. In the downlink direction, the baseband device 53 processes the information to be transmitted and sends it to the RF device 52. The RF device 52 processes the received information and then transmits it through the antenna 51.

[0521] The method executed by the network-side device in the above embodiments can be implemented in the baseband device 53, which includes a baseband processor.

[0522] Baseband device 53 may include, for example, at least one baseband board on which multiple chips are disposed, such as Figure 5 As shown, one of the chips is, for example, a baseband processor, which is connected to the memory 55 via a bus interface to call the program or instructions in the memory 55 to execute the network-side device operations shown in the above method embodiment.

[0523] The network-side device may also include a network interface 56, such as a Common Public Radio Interface (CPRI).

[0524] The processor 54 is configured to perform a first operation upon receiving an SDAP PDU for a new service task indicated by a QoS flow indicated by a QFI or a task identifier indicated by a task identifier from the lower layer. The first operation includes retrieving an SDAP SDU from the SDAP PDU and transmitting the retrieved SDAP SDU to the upper layer. Alternatively, upon receiving an SDAP SDU for a new service task indicated by a QoS flow indicated by a QFI or a task identifier indicated by a task identifier from the upper layer, the processor 54 is configured to perform a second operation upon receiving an SDAP PDU for a new service task indicated by a QoS flow indicated by a QFI or a task identifier indicated by a task identifier from the upper layer. The second operation includes constructing an SDAP PDU and submitting the constructed SDAP PDU to the lower layer. The SDAP PDU is an SDAP PDU in a format that supports the new service.

[0525] Furthermore, the network-side device 50 in this embodiment of the application also includes: a program or instructions stored in the memory 55 and executable on the processor 54, wherein the processor 54 calls the program or instructions in the memory 55 to execute. Figure 24 or Figure 25 The methods executed by each module shown achieve the same technical effect, and to avoid repetition, they will not be described in detail here.

[0526] Specifically, embodiments of this application also provide a network-side device. For example... Figure 29 As shown, the network-side device 60 includes a processor 61, a network interface 62, and a memory 63. This network-side device can be the XX device shown in Figure m. The network interface 62 is, for example, a Common Public Radio Interface (CPRI).

[0527] The processor 61 is configured to perform a first operation upon receiving an SDAP PDU for a new service task indicated by a QoS flow indicated by a QFI or a task identifier indicated by a task identifier from a lower layer. The first operation includes retrieving an SDAP SDU from the SDAP PDU and transmitting the retrieved SDAP SDU to an upper layer. Alternatively, upon receiving an SDAP SDU for a new service task indicated by a QoS flow indicated by a QFI or a task identifier indicated by a task identifier from an upper layer, the processor 61 is configured to perform a second operation upon receiving an SDAP PDU for a new service task indicated by a QoS flow indicated by a QFI or a task identifier from an upper layer. The second operation includes constructing an SDAP PDU and submitting the constructed SDAP PDU to a lower layer. The SDAP PDU is an SDAP PDU in a format that supports the new service.

[0528] Furthermore, the network-side device 60 in this embodiment of the application also includes: a program or instructions stored in the memory 63 and executable on the processor 61, wherein the processor 61 calls the program or instructions in the memory 63 to execute. Figure X The methods executed by each module shown in X achieve the same technical effect, and will not be elaborated here to avoid repetition.

[0529] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the various processes of the above-described user plane data transmission method embodiments and achieve the same technical effects. To avoid repetition, they will not be described again here.

[0530] The processor mentioned above is either the processor in the terminal described in the above embodiments or the processor in the network-side device. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk. In some examples, the readable storage medium may be a non-transient readable storage medium.

[0531] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the various processes of the above-described user plane data transmission method embodiments and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0532] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0533] This application also provides a computer program / program product, which is stored in a storage medium and executed by at least one processor to implement the various processes of the above-described user plane data transmission method embodiments, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0534] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0535] From the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of computer software products plus necessary general-purpose hardware platforms, and of course, they can also be implemented by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.), and the computer software product includes several instructions to cause the terminal or network-side device to execute the methods described in the various embodiments of this application.

[0536] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other implementations under the guidance of this application without departing from the spirit and scope of the claims. All of these implementations are within the protection scope of this application.

Claims

1. A user plane data transmission method, characterized by, include: When the Service Data Adaptation Protocol (SDAP) entity of the first device receives from the lower layer an SDAP Protocol Data Unit (PDU) indicating a QoS flow indicated by a Quality of Service (QoS) Flow Identifier (QFI) or a new service task indicated by a Task Identifier (TOD), a first operation is performed, the first operation including: retrieving an SDAP SDU from the SDAP PDU and transmitting the retrieved SDAP SDU to the upper layer; or, When the SDAP entity of the first device receives an SDAP SDU for a QoS flow indicated by a QFI or a new service task indicated by a task identifier from the upper layer, a second operation is performed, the second operation including: constructing an SDAP PDU and submitting the constructed SDAP PDU to the lower layer; The SDAP PDU is an SDAP PDU in a format that supports the new service.

2. The method of claim 1, wherein, The SDAP PDU supporting the new service format includes at least one of the following: new service data, SDAP control PDU supporting the new service, and user plane data with an SDAP header, wherein the SDAP header supports the transmission of the new service data.

3. The method according to claim 1 or 2, characterized in that, Retrieving an SDAP SDU from the SDAP PDU and transmitting the retrieved SDAP SDU to the upper layer includes at least one of the following: If the SDAP PDU is an SDAP data PDU, and the DRB receiving the SDAP PDU has configured an SDAP header, the SDAP SDU is retrieved from the SDAP PDU according to the SDAP header, and the retrieved SDAP SDU is transmitted to the upper layer. If the SDAP PDU is an SDAP data PDU and the DRB receiving the SDAP PDU is not configured with an SDAP header, the SDAP SDU is retrieved from the SDAP PDU according to the format of the SDAP PDU without an SDAP header, and the retrieved SDAPSDU is transmitted to the upper layer. If the SDAP PDU is an SDAP control PDU, retrieve the SDAP SDU from the SDAP PDU associated with the SDAP control PDU and transmit the retrieved SDAP SDU to the upper layer.

4. The method of claim 3, wherein, The step of retrieving the SDAP SDU from the SDAP PDU according to the SDAP header and transmitting the retrieved SDAP SDU to the upper layer includes at least one of the following: The SDAP SDU is retrieved from the SDAP PDU according to the SDAP header. If the SDAP header contains a new service data indication and the new service data indication indicates that the SDAP PDU is new service data, the retrieved SDAP SDU is transmitted to the modem. The SDAP SDU is retrieved from the SDAP PDU according to the SDAP header. If the SDAP header contains a next-hop address, the retrieved SDAP SDU is transmitted to the next-hop address. If the SDAP header contains a priority indication, the SDAPSDU is retrieved from the SDAP PDU according to the priority indication, and the retrieved SDAP SDU is transmitted to the upper layer.

5. The method according to claim 1 or 2, characterized in that, The process of constructing an SDAP PDU and submitting the constructed SDAPPDU to the lower layer includes at least one of the following: If the SDAP SDU is an SDAP data SDU, and the DRB mapped by the SDAP SDU has been configured with an SDAP header, an SDAP PDU is constructed based on the SDAP header, and the constructed SDAP PDU is submitted to the lower layer. If the SDAP SDU is an SDAP data SDU and the DRB mapped by the SDAP SDU is not configured with an SDAP header, an SDAP PDU is constructed according to the SDAP PDU format without an SDAP header, and the constructed SDAP PDU is submitted to the lower layer. If the SDAP SDU is an SDAP control SDU, construct an SDAP PDU and submit the constructed SDAP PDU to the lower layer.

6. The method according to claim 1 or 2 or 5, characterized in that, The second operation also includes at least one of the following: If there is no mapping rule for storing the QoS flow to the DRB, map the SDAP SDU to the default DRB; If the mapping rules from the QoS flow to the DRB are stored, map the SDAP SDU to the DRB corresponding to the mapping rules from the QoS flow to the DRB. If there is no mapping rule for storing the new service task to the DRB, map the SDAP SDU to the default DRB; If the mapping rule from the new service task to the DRB is stored, the SDAP SDU is mapped to the DRB corresponding to the mapping rule from the new service task to the DRB.

7. The method according to any one of claims 2-5, characterized in that, The control PDU supporting the new service or the SDAP header includes at least one of the following information elements: New service data indication is used to indicate whether the SDAP PDU is new service data; New service type, used to indicate the type of new service; User plane data type, used to indicate the user plane data type of the SDAP PDU; Next-hop node type, used to indicate the type of the next-hop node after the SDAP PDU is transmitted to the RAN device; Priority indicator, used to indicate the priority information of the SDAP PDU; Task identifier, used to identify new service tasks; RAN termination indication is used to indicate whether the SDAP PDU has been resolved by the RAN device; An extension header indicator is used to indicate whether the information unit following the extension header indicator needs to be parsed. The next-hop node address is used to indicate the next-hop node address of the SDAP PDU; Destination address, used to indicate the destination address of the SDAP PDU; A start marker is used to indicate that the first data PDU following the first control PDU containing the start marker will be processed according to the information unit in the first control PDU, and to map the SDU corresponding to the first data PDU to the DRB of the first control PDU, wherein the first control PDU and the first data PDU belong to the same QoS flow or the same new service task. Alternatively, it can be used to indicate that a third data PDU following the second data PDU containing the start marker will be processed according to the information unit in the second data PDU, wherein the second data PDU and the third data PDU belong to the same QoS flow or the same new service task; The first quantity is used to indicate the number of data PDUs that need to be processed according to the information unit in the first control PDU or the information unit in the second data PDU; An end marker is used to indicate that the third data PDU following the second control PDU containing the end marker will no longer be processed according to the information unit in the first control PDU, and the SDU corresponding to the third data PDU will no longer be mapped to the DRB of the first control PDU. The first control PDU and the second control PDU belong to the same QoS flow or the same new service task. Alternatively, it can be used to indicate that the fifth data PDU following the fourth data PDU containing the end marker is no longer processed according to the information element in the second data PDU, and that the second data PDU and the fourth data PDU belong to the same QoS flow or the same new service task.

8. The method according to claim 7, characterized in that, The SDAP control PDU supporting the new service or the SDAP header also includes at least one of a PDU type indicator and a QoS flow identifier, wherein the PDU type indicator is used to indicate whether the SDAP PDU is an SDAP control PDU or an SDAP data PDU.

9. The method according to claim 7, characterized in that, The user plane data types include at least one of the following: non-new service data, new service data, perception service data, AI service data, computing service data, external perception service data, internal perception service data, external AI service data, internal AI service data, external computing service data, internal computing service data, AI model data, AI training data, and AI inference data.

10. The method according to claim 7, characterized in that, The new service types include at least one of the following: perception service, AI service, computing service, external perception service, internal perception service, external AI service, internal AI service, external computing service, internal computing service, AI model, AI training, and AI inference.

11. The method according to claim 7, characterized in that, The next-hop node type is a user plane function, a data plane function, or a new service function, and the new service function is a perception function, an AI function, or a computing function.

12. The method according to claim 7, characterized in that, The priority indication includes at least one of the following: a high priority indication and a low priority indication, wherein the high priority indication is used to indicate whether the priority of the new service data is higher than that of the non-new service data, and the low priority indication is used to indicate whether the priority of the new service data is lower than that of the non-new service data.

13. The method according to claim 7, characterized in that, The SDAP header also includes a QFI information element, which indicates the task identifier when the new service data indicates that the SDAP PDU is new service data.

14. The method according to any one of claims 1-13, characterized in that, The SDAP entity resides in an SDAP sublayer, which supports at least one of the following functionalities: Mapping between uplink new service QoS streams and DRBs; Mapping between downlink new service QoS flows and DRBs; Mapping between uplink new service QoS flows and DRB groups; Mapping between downlink new service QoS flows and DRB groups; Mapping between new uplink service tasks and DRBs; Mapping between new downlink service tasks and DRB; Mapping between new service tasks and DRB groups; Mapping between new downlink service tasks and DRB groups; New service QoS flows are marked in uplink UL packets; New service QoS flows are marked in downlink DL packets; Mark new service tasks in the uplink data packets; New service tasks are marked in the downlink data packets.

15. The method according to any one of claims 1-14, characterized in that, The first device is a terminal, and the method further includes: The first device receives first configuration information, which is used to indicate the addition of a DRB. The first configuration information includes SDAP header configuration information; the SDAP header includes at least one of an uplink SDAP header and a downlink SDAP header. The first device establishes the SDAP entity based on the first configuration information.

16. The method according to claim 15, characterized in that, The SDAP header configuration information includes one of the following: Does an SDAP header exist? The number of bits in the SDAP header; The format name of the SDAP header.

17. The method according to any one of claims 1-16, characterized in that, The first device is a network-side device, and the method includes: If there are multiple SDAP control PDU formats, the first device sends second configuration information, which includes the configured SDAP control PDU format; the control PDU format includes at least one of uplink control PDU and downlink control PDU; the configured SDAP control PDU format is one of the multiple SDAP control PDU formats; or The first device is a terminal, and the method further includes: The first device receives second configuration information, which includes a configured SDAP control PDU format; the control PDU format includes at least one of uplink control PDU and downlink control PDU.

18. The method according to any one of claims 15-17, characterized in that, Also includes: The first device reports terminal capability information, which includes at least one of the following: Does the terminal support the new service? Does the terminal support the SDAP PDU format with an SDAP header? Does the terminal support the SDAP control PDU that supports the new service? 19. A user plane data transmission device, characterized in that, include: The processing module is configured to perform a first operation upon receiving an SDAP PDU for a new service task indicated by a QoS flow indicated by a QFI or a task identifier indicated by a task identifier from a lower layer. The first operation includes retrieving an SDAP SDU from the SDAP PDU and transmitting the retrieved SDAP SDU to the upper layer. Alternatively, upon receiving an SDAP SDU for a new service task indicated by a QoS flow indicated by a QFI or a task identifier indicated by a task identifier from an upper layer, the module is configured to perform a second operation upon receiving an SDAPPDU for a new service task indicated by a QFI or a task identifier from an upper layer. The second operation includes constructing an SDAPPDU and submitting the constructed SDAP PDU to the lower layer. The SDAP PDU is an SDAPPDU in a format that supports new services.

20. The apparatus according to claim 19, characterized in that, Retrieving an SDAP SDU from the SDAP PDU and transmitting the retrieved SDAP SDU to the upper layer includes at least one of the following: If the SDAP PDU is an SDAP data PDU, and the DRB receiving the SDAP PDU has configured an SDAP header, the SDAP SDU is retrieved from the SDAP PDU according to the SDAP header, and the retrieved SDAP SDU is transmitted to the upper layer. If the SDAP PDU is an SDAP data PDU and the DRB receiving the SDAP PDU is not configured with an SDAP header, the SDAP SDU is retrieved from the SDAP PDU according to the format of the SDAP PDU without an SDAP header, and the retrieved SDAPSDU is transmitted to the upper layer. If the SDAP PDU is an SDAP control PDU, retrieve the SDAP SDU from the SDAP PDU associated with the SDAP control PDU and transmit the retrieved SDAP SDU to the upper layer.

21. The apparatus according to claim 20, characterized in that, The step of retrieving the SDAP SDU from the SDAP PDU according to the SDAP header and transmitting the retrieved SDAP SDU to the upper layer includes at least one of the following: If the SDAP header contains a new service data indication, and the new service data indication indicates that the SDAP PDU is new service data, the retrieved SDAP SDU is transmitted to the modem. If the SDAP header contains a next-hop address, the retrieved SDAP SDU is transmitted to the next-hop address; If the SDAP header contains a priority indication, the SDAPSDU is retrieved from the SDAP PDU according to the priority indication, and the retrieved SDAP SDU is transmitted to the upper layer.

22. The apparatus according to claim 19, characterized in that, The process of constructing an SDAP PDU and submitting the constructed SDAPPDU to the lower layer includes at least one of the following: If the SDAP SDU is an SDAP data SDU, and the DRB mapped by the SDAP SDU has been configured with an SDAP header, an SDAP PDU is constructed based on the SDAP header, and the constructed SDAP PDU is submitted to the lower layer. If the SDAP SDU is an SDAP data SDU and the DRB mapped by the SDAP SDU is not configured with an SDAP header, an SDAP PDU is constructed according to the SDAP PDU format without an SDAP header, and the constructed SDAP PDU is submitted to the lower layer. If the SDAP SDU is an SDAP control SDU, construct an SDAP PDU and submit the constructed SDAP PDU to the lower layer.

23. The apparatus according to claim 19 or 22, characterized in that, The second operation also includes at least one of the following: If there is no mapping rule for storing the QoS flow to the DRB, map the SDAP SDU to the default DRB; If the mapping rules from the QoS flow to the DRB are stored, map the SDAP SDU to the DRB corresponding to the mapping rules from the QoS flow to the DRB. If there is no mapping rule for storing the new service task to the DRB, map the SDAP SDU to the default DRB; If the mapping rule from the new service task to the DRB is stored, the SDAP SDU is mapped to the DRB corresponding to the mapping rule from the new service task to the DRB.

24. The apparatus according to any one of claims 20-22, characterized in that, The SDAP header includes at least one of the following information elements: New service data indication is used to indicate whether the SDAP PDU is new service data; New service type, used to indicate the type of new service; User plane data type, used to indicate the user plane data type of the SDAP PDU; Next-hop node type, used to indicate the type of the next-hop node after the SDAP PDU is transmitted to the RAN device; Priority indicator, used to indicate the priority information of the SDAP PDU; Task identifier, used to identify new service tasks; RAN termination indication is used to indicate whether the SDAP PDU has been resolved by the RAN device; An extension header indicator is used to indicate whether the information unit following the extension header indicator needs to be parsed. The next-hop node address is used to indicate the next-hop node address of the SDAP PDU; Destination address, used to indicate the destination address of the SDAP PDU; A start marker is used to indicate that the first data PDU following the first control PDU containing the start marker will be processed according to the information unit in the first control PDU, and to map the SDU corresponding to the first data PDU to the DRB of the first control PDU, wherein the first control PDU and the first data PDU belong to the same QoS flow or the same new service task. Alternatively, it can be used to indicate that a third data PDU following the second data PDU containing the start marker will be processed according to the information unit in the second data PDU, wherein the second data PDU and the third data PDU belong to the same QoS flow or the same new service task; The first quantity is used to indicate the number of data PDUs that need to be processed according to the information unit in the first control PDU or the information unit in the second data PDU; An end marker is used to indicate that the third data PDU following the second control PDU containing the end marker will no longer be processed according to the information unit in the first control PDU, and the SDU corresponding to the third data PDU will no longer be mapped to the DRB of the first control PDU. The first control PDU and the second control PDU belong to the same QoS flow or the same new service task. Alternatively, it can be used to indicate that the fifth data PDU following the fourth data PDU containing the end marker is no longer processed according to the information element in the second data PDU, and that the second data PDU and the fourth data PDU belong to the same QoS flow or the same new service task.

25. The apparatus according to any one of claims 19-24, characterized in that, Also includes: A receiving module is configured to receive first configuration information, which is used to indicate the addition of a DRB, and the first configuration information includes SDAP header configuration information. The SDAP header includes at least one of an uplink SDAP header and a downlink SDAP header; The processing module is used to establish an SDAP entity based on the first configuration information.

26. The apparatus according to any one of claims 19-25, characterized in that, Also includes: A sending module is configured to send second configuration information if multiple SDAP control PDU formats are available, wherein the second configuration information includes a configured SDAP control PDU format; the control PDU format includes at least one of uplink control PDU and downlink control PDU; and the configured SDAP control PDU format is one of the multiple SDAP control PDU formats. or The receiving module is configured to receive second configuration information, which includes a configured SDAP control PDU format; the control PDU format includes at least one of uplink control PDU and downlink control PDU.

27. The apparatus according to claim 25 or 26, characterized in that, Also includes: The sending module is used to report terminal capability information, which includes at least one of the following: Does the terminal support the new service? Does the terminal support the SDAP PDU format with an SDAP header? Does the terminal support the SDAP control PDU that supports the new service? 28. A communication device, characterized in that, It includes a processor and a memory, the memory storing a program or instructions that can run on the processor, the program or instructions being executed by the processor to implement the steps of the user plane data transmission method as described in any one of claims 1 to 18.

29. A readable storage medium, characterized in that, The readable storage medium stores a program or instructions that, when executed by a processor, implement the steps of the user plane data transmission method as described in any one of claims 1 to 18.

Images