Data transmission method, data reception method and devices

Abstract

A data sending method, a data receiving method and equipment, the method comprising: a first device generating a first service data adaptation protocol (SDAP) protocol data unit (PDU) based on the same format of uplink and downlink SDAP PDUs; and the first device sending the first SDAP PDU to a second device; wherein the same format of uplink and downlink SDAP PDUs comprises a header unit and an SDAP SDU, and the SDAP SDU comprises at least one of an SDAP control SDU and an SDAP data SDU. The application can realize flexible and on-demand activation of service functions at the SDAP protocol level, based on a unified SDAP PDU format, the SDAP PDU carrying indication information of PDU structures or various information or formats contained therein, and a receiving end only needing to parse the SDAP PDU according to the same format to avoid data loss when different function services are switched.

Description

Technical Field

[0001] This application relates to the field of data communication technology, specifically to a data transmission method, a data reception method, and a device. Background Technology

[0002] The design goals of Lite Networks and Soft / Resilient Networks for next-generation mobile communications require service-oriented (SO) design of protocol stack functions.

[0003] In the prior art, the Service Data Adaptation Protocol (SDAP) functions as follows: Figure 1 As shown, SDAP is responsible for mapping and demapping QoS flows and Data Radio Bearers (DRBs), as well as the optional reflective QoS flow to DRB mapping function. In existing technologies, each protocol layer strictly adheres to the upper / lower layer constraints of L3 / L2 / L1 for data transmission, specifically as follows... Figure 2 and Figure 3 The 5G protocol stack scheme shown.

[0004] 6G networks are inherently intelligent networks, requiring them to generate measurement information based on their own operation. In 6G systems, with the increasing variety of information to be transmitted, in addition to service data and RRC signaling, there is a significant amount of information exchange between the peer access layer (AS) on the terminal and network sides, as well as within the AS layer itself. This includes interactions such as the configuration or update of artificial intelligence (AI) models, protocol sublayer state interaction, and the selection of appropriate protocol sublayer functions based on service characteristics. All of this necessitates that the 6G protocol stack possess the flexibility to select functions on demand, maintain a unified Protocol Data Unit (PDU) format with low redundancy overhead, and allow for connectionless or lightweight connections between protocol layers. Summary of the Invention

[0005] At least one embodiment of this application provides a data transmission method, a data reception method, and an apparatus for implementing data transmission based on the service-oriented unified SDAP PDU format.

[0006] To solve the above-mentioned technical problems, this application is implemented as follows:

[0007] In a first aspect, embodiments of this application provide a data transmission method, including:

[0008] The first device generates a first SDAP PDU based on the same format of the uplink and downlink service data adaptation protocol SDAP protocol data unit PDU; wherein, the same format of the uplink and downlink SDAP PDU includes: header unit and SDAP service data unit SDU;

[0009] The first device sends a first SDAP PDU to the second device.

[0010] Optionally, the SDAP SDU includes at least one of the SDAP control SDU and the SDAP data SDU.

[0011] Optionally, the header unit includes at least one of the following fields:

[0012] The type field (D / C / H) is used to indicate the type of SDAP PDU, which includes SDAP control PDU, SDAP data PDU and SDAP hybrid PDU, wherein the SDAP hybrid PDU includes SDAP control SDU and SDAP data SDU;

[0013] The QoS Flow Identifier (QFI) field is used to indicate the QoS flow identifier of the SDAP data PDU when the type field indicates an SDAP data PDU.

[0014] The first control identifier field (CF1) is used to indicate the service target range of the SDAP control SDU when the type field indicates an SDAP control PDU or an SDAP hybrid PDU.

[0015] The second control identifier field (CF2) is used to indicate the service correspondence of the SDAP control SDU when the service object range indicated by the first control identifier field is the target QoS flow listed in the SDAPPDU. The service correspondence includes: a first correspondence where all target QoS flows correspond to the same service in the SDAP control SDU, and a second correspondence where the target QoS flows correspond one-to-one with the services in the SDAP control SDU.

[0016] The data identifier field (DF1) is used to indicate whether the SDAP data SDU carries a sequence number and the length of the sequence number when the type field indicates an SDAP control PDU or an SDAP hybrid PDU.

[0017] Optionally, when the type field indicates an SDAP hybrid PDU, the SDAP SDU includes at least one SDAP control SDU; the header unit further includes an extension field (E) and a first length field corresponding to each SDAP control SDU; wherein,

[0018] The extended field (E) is used to indicate whether there is another SDAP control SDU after the SDAP control SDU corresponding to this extended field (E);

[0019] The first length field (CL) is used to indicate the length of the SDAP control SDU corresponding to this first length field (CL).

[0020] Optionally, the head unit further includes:

[0021] The RQI field is used to indicate whether to instruct the non-access tier NAS to update the NAS mapping rules.

[0022] Optionally, the SDAP control SDU includes at least one of the following fields:

[0023] The Service Identifier (SID) field is used to indicate the identifier of the service to which the SDAP control SDU requests, configures, or responds.

[0024] The third control identifier field (CF3) is used to indicate whether the service is a fixed format or a non-fixed format;

[0025] The fourth control identifier field (CF4) is used to indicate the length of the second length field when the third control identifier field indicates a non-fixed format.

[0026] The second length field (L) is used to indicate the length of the service context field;

[0027] The service context field is used to indicate the context information of the service.

[0028] Optionally, if the second control identifier field indicates that the service correspondence of the SDAP control SDU is the first correspondence:

[0029] If the service object range indicated by the first control identifier field is the target QoS flow listed in the SDAP control PDU, then the SDAP control SDU includes: at least one service identifier field, and a service context field corresponding to the at least one service identifier field;

[0030] If the service target range indicated by the first control identifier field is the QoS flow established by the first device or the second device, then the SDAP control SDU includes one of the service context fields.

[0031] Optionally, if the first control identifier field indicates that the service correspondence of the SDAP control SDU is the second correspondence:

[0032] The SDAP control SDU includes: at least one service identifier field, and a service context field corresponding to each service identifier field.

[0033] Optionally, when the data identifier field indicates that the SDAP data SDU carries a sequence number, the SDAP data SDU includes a sequence number field and a data field;

[0034] When the data identifier field indicates that the SDAP data SDU does not carry a sequence number, the SDAP data SDU includes a data field.

[0035] Secondly, embodiments of this application provide a data receiving method, including:

[0036] The second device receives the first SDAP PDU sent by the first device, wherein the first SDAP PDU is an SDAP PDU generated based on the same format of uplink and downlink SDAP PDUs, and the same format of uplink and downlink SDAP PDUs includes: header unit and SDAP PDU;

[0037] The second device parses the first SDAP PDU according to the same format of the uplink and downlink SDAP PDUs.

[0038] Optionally, the SDAP SDU includes at least one of the SDAP control SDU and the SDAP data SDU.

[0039] Optionally, the header unit includes at least one of the following fields:

[0040] The type field (D / CH) is used to indicate the type of SDAP PDU, which includes SDAP control PDU, SDAP data PDU and SDAP hybrid PDU, wherein the SDAP hybrid PDU includes SDAP control SDU and SDAP data SDU;

[0041] The QoS Flow Identifier (QFI) field is used to indicate the QoS flow identifier of the SDAP data PDU when the type field indicates an SDAP data PDU.

[0042] The first control identifier field (CF1) is used to indicate the service target range of the SDAP control PDU when the type field indicates an SDAP control PDU or an SDAP hybrid PDU. The service target range is: the target QoS flow listed in the SDAP PDU, or the QoS flow established by the first device or the second device.

[0043] The second control identifier field (CF2) is used to indicate the service correspondence of the SDAP control SDU when the service object range indicated by the first control identifier field is the target QoS flow listed in the SDAPPDU. The service correspondence includes: a first correspondence where all target QoS flows correspond to the same service in the SDAP control SDU, and a second correspondence where the target QoS flows correspond one-to-one with the services in the SDAP control SDU.

[0044] The data identifier field (DF1) is used to indicate whether the SDAP data SDU carries a sequence number and the length of the sequence number when the type field indicates an SDAP control PDU or an SDAP hybrid PDU.

[0045] Optionally, when the type field indicates an SDAP hybrid PDU, the SDAP SDU includes at least one SDAP control SDU; the header unit further includes an extension field (E) and a first length field corresponding to each SDAP control SDU; wherein,

[0046] The extended field (E) is used to indicate whether there is another SDAP control SDU after the SDAP control SDU corresponding to this extended field (E);

[0047] The first length field (CL) is used to indicate the length of the SDAP control SDU corresponding to this first length field (CL).

[0048] Optionally, the head unit further includes:

[0049] The RQI field is used to indicate whether to instruct the non-access tier NAS to update the NAS mapping rules.

[0050] Optionally, the SDAP control SDU includes at least one of the following fields:

[0051] The Service Identifier (SID) field is used to indicate the identifier of the service to which the SDAP control SDU requests, configures, or responds.

[0052] The third control identifier field (CF3) is used to indicate whether the service is a fixed format or a non-fixed format;

[0053] The fourth control identifier field (CF4) is used to indicate the length of the second length field when the third control identifier field indicates a non-fixed format.

[0054] The second length field is used to indicate the length of the service context field;

[0055] The service context field is used to indicate the context information of the service.

[0056] Optionally, if the second control identifier field indicates that the service correspondence of the SDAP control SDU is the first correspondence:

[0057] If the service object range indicated by the first control identifier field is the target QoS flow listed in the SDAP control PDU, then the SDAP control SDU includes: at least one service identifier field, and a service context field corresponding to the at least one service identifier field;

[0058] If the service target range indicated by the first control identifier field is the QoS flow established by the first device or the second device, then the SDAP control SDU includes one of the service context fields.

[0059] Optionally, if the first control identifier field indicates that the service correspondence of the SDAP control SDU is the second correspondence:

[0060] The SDAP control SDU includes: at least one service identifier field, and a service context field corresponding to each service identifier field.

[0061] Optionally, when the data identifier field indicates that the SDAP data SDU carries a sequence number, the SDAP data SDU includes a sequence number field and a data field;

[0062] When the data identifier field indicates that the SDAP data SDU does not carry a sequence number, the SDAP data SDU includes a data field.

[0063] Optionally, the second device parses the first SDAPPDU according to the same format of the uplink and downlink SDAP PDUs, including:

[0064] The second device determines the type of the first SDAP PDU according to the type field, and obtains the SDAP control SDU and / or SDAP data SDU in the first SDAP PDU according to the first control identifier field (CF1), the second control identifier field (CF2), and the data identifier field (DF1).

[0065] Based on the fields included in the SDAP control SDU, the SDAP control SDU in the first SDAP PDU is parsed, and / or, based on the fields included in the SDAP data SDU, the SDAP data SDU in the first SDAP PDU is parsed to obtain the SDAP data SDU.

[0066] Thirdly, embodiments of this application provide a first device, including a transceiver and a processor, wherein...

[0067] The processor is used to generate a first SDAP PDU based on the same format of the uplink and downlink service data adaptation protocol protocol data unit (PDU).

[0068] The transceiver is used to send a first SDAP PDU to the second device; wherein...

[0069] The same format for uplink and downlink SDAP PDUs includes: header unit and SDAP SDU.

[0070] Fourthly, embodiments of this application provide a first device, including: a processor, a memory, and a program stored in the memory and executable on the processor, wherein the program, when executed by the processor, implements the steps of the method described in the first aspect.

[0071] Fifthly, embodiments of this application provide a second device, including a transceiver and a processor, wherein...

[0072] The transceiver is used to receive a first SDAP PDU sent by a first device, wherein the first SDAP PDU is an SDAP PDU generated based on the same format of uplink and downlink SDAP PDUs, and the same format of uplink and downlink SDAP PDUs includes: a header unit and an SDAP PDU;

[0073] The processor is configured to parse the first SDAP PDU according to the same format of the uplink and downlink SDAP PDUs.

[0074] In a sixth aspect, embodiments of this application provide a second device, comprising: a processor, a memory, and a program stored in the memory and executable on the processor, wherein the program, when executed by the processor, implements the steps of the method described in the second aspect.

[0075] In a seventh aspect, embodiments of this application provide a computer-readable storage medium storing a program that, when executed by a processor, implements the steps of the method described above.

[0076] Compared with the prior art, the data sending method, data receiving method and device provided in this application embodiment can realize flexible on-demand activation of SDAP protocol-level service functions. Based on the unified SDAP PDU format, the SDAP PDU carries the PDU structure or various information or format indication information contained therein. The receiving end only needs to parse the SDAP PDU according to the same format, so as to avoid data loss when switching between different functional services. Attached Figure Description

[0077] Various other advantages and benefits will become apparent to those skilled in the art upon reading the following detailed description of preferred embodiments. The accompanying drawings are for illustrative purposes only and are not intended to limit the scope of this application. Furthermore, the same reference numerals denote the same parts throughout the drawings. In the drawings:

[0078] Figures 1-3 A schematic diagram of the protocol architecture of existing 5G technologies;

[0079] Figure 4 This is a schematic diagram illustrating an application scenario according to an embodiment of this application;

[0080] Figure 5-8 This is a schematic diagram of the format of an existing SDAP PDU;

[0081] Figure 9-14 The following are schematic diagrams illustrating several formats of the SDAP PDU in embodiments of this application;

[0082] Figure 15 This is a schematic flowchart of a data transmission method according to an embodiment of this application;

[0083] Figure 16 This is a schematic flowchart of a data receiving method according to an embodiment of this application;

[0084] Figure 17 This is a schematic diagram of the structure of a first device according to an embodiment of this application;

[0085] Figure 18 This is a schematic diagram of the structure of the first device according to another embodiment of this application;

[0086] Figure 19 This is a schematic diagram of the structure of a second device according to an embodiment of this application;

[0087] Figure 20 This is a schematic diagram of the structure of a second device according to another embodiment of this application;

[0088] Figure 21 This is a schematic diagram of the structure of the first device according to yet another embodiment of this application;

[0089] Figure 22 This is a schematic diagram of the structure of a second device according to yet another embodiment of this application. Detailed Implementation

[0090] Exemplary embodiments of the present application will now be described in more detail with reference to the accompanying drawings. While exemplary embodiments of the present application are shown in the drawings, it should be understood that the present application may be implemented in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this application will be thorough and complete, and will fully convey the scope of the present application to those skilled in the art.

[0091] The terms “first,” “second,” etc., used in the specification and claims of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented, for example, in orders other than those illustrated or described herein. Furthermore, the terms “comprising” and “having,” and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus. The terms “and / or” in the specification and claims indicate at least one of the connected objects.

[0092] The technologies described in this document are not limited to NR systems and Long Time Evolution (LTE) / LTE-Advanced (LTE-A) systems, but can also be used in various 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), and other systems. The terms "system" and "network" are often used interchangeably. CDMA systems can implement radio technologies such as CDMA2000 and Universal Terrestrial Radio Access (UTRA). UTRA includes Wideband Code Division Multiple Access (WCDMA) and other CDMA variants. TDMA systems can implement radio technologies such as the Global System for Mobile Communication (GSM). OFDMA systems can implement radio technologies such as Ultra Mobile Broadband (UMB), Evolution-UTRA (E-UTRA), IEEE 802.21 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, and Flash-OFDM. UTRA and E-UTRA are part of the Universal Mobile Telecommunications System (UMTS). LTE and more advanced versions of LTE (such as LTE-A) are newer versions of UMTS that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents from an organization called the 3rd Generation Partnership Project (3GPP). CDMA2000 and UMB are described in documents from an organization called 3rd Generation Partnership Project 2 (3GPP2).The techniques described herein can be used with the systems and radio technologies mentioned above, as well as with other systems and radio technologies. However, the following description describes NR systems for illustrative purposes, and NR terminology is used in most of the following description, although these techniques can also be applied to applications beyond NR systems.

[0093] The following description provides examples and is not intended to limit the scope, applicability, or configuration set forth in the claims. Changes may be made to the function and arrangement of the elements discussed without departing from the spirit and scope of this disclosure. Various procedures or components may be appropriately omitted, substituted, or added to the examples. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Furthermore, features described with reference to certain examples may be combined in other examples.

[0094] Please see Figure 4 , Figure 4 This 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 device 12. The terminal 11 can also be referred to as a user terminal or user equipment (UE). The terminal 11 can be a mobile phone, tablet computer, laptop computer, personal digital assistant (PDA), mobile internet device (MID), wearable device, or in-vehicle device, etc. It should be noted that the specific type of terminal 11 is not limited in this embodiment. Network device 12 can be a base station and / or a core network element. The base station can be a 5G or later version base station (e.g., gNB, 5G NR NB, etc.), or a base station in other communication systems (e.g., eNB, WLAN access point, or other access point, etc.). The base station can be referred to as a node B, evolved node B, access point, base transceiver station (BTS), radio base station, radio transceiver, basic service set (BSS), extended service set (ESS), B node, evolved B node (eNB), home B node, home evolved B node, WLAN access point, WiFi node, or any other suitable term in the field. As long as the same technical effect is achieved, the base station is not limited to specific technical terms. It should be noted that in this embodiment of the application, only a base station in an NR system is used as an example, but the specific type of base station is not limited.

[0095] The base station can communicate with terminal 11 under the control of a base station controller, which in various examples may be part of the core network or some base stations. Some base stations may communicate control information or user data with the core network via backhaul. In some examples, some of these base stations may communicate with each other directly or indirectly via backhaul links, which may be wired or wireless communication links. The wireless communication system may support operation on multiple carriers (waveform signals of different frequencies). A multi-carrier transmitter can transmit modulated signals on multiple carriers simultaneously. For example, each communication link may be a multi-carrier signal modulated according to various radio technologies. Each modulated signal may be transmitted on a different carrier and may carry control information (e.g., reference signals, control channels, etc.), overhead information, data, etc.

[0096] The base station can wirelessly communicate with terminal 11 via one or more access point antennas. Each base station can provide communication coverage for its respective coverage area. The coverage area of ​​an access point can be divided into sectors that constitute only a part of that coverage area. The wireless communication system may include different types of base stations (e.g., macro base stations, micro base stations, or pico base stations). Base stations may also utilize different radio technologies, such as cellular or WLAN radio access technologies. Base stations may be associated with the same or different access networks or operator deployments. The coverage areas of different base stations (including coverage areas of the same or different types of base stations, coverage areas using the same or different radio technologies, or coverage areas belonging to the same or different access networks) may overlap.

[0097] Communication links in a wireless communication system may include an uplink for carrying uplink (UL) transmissions (e.g., from terminal 11 to network device 12) or a downlink for carrying downlink (DL) transmissions (e.g., from network device 12 to terminal 11). UL transmissions may also be referred to as reverse link transmissions, and DL transmissions may also be referred to as forward link transmissions. Downlink transmissions may be carried out using licensed frequency bands, unlicensed frequency bands, or both. Similarly, uplink transmissions may be carried out using licensed frequency bands, unlicensed frequency bands, or both.

[0098] The format of existing SDAP PDUs is as follows: Figures 5-8 As shown, Figure 5 The format of SDAP data PDU without SDAP header. Figure 6 The format of downlink SDAP data PDUs with SDAP headers. Figure 7 The format of uplink SDAP data PDUs with SDAP headers. Figure 8This describes the format of the end-marker for the SDAP PDU. It can be seen that various data PDUs and control PDUs in the prior art have different formats.

[0099] In 6G and similar scenarios, the types of information that need to be transmitted are numerous. This requires the 6G protocol stack to have the flexibility to select functions on demand, maintain a unified Protocol Data Unit (PDU) format with low redundancy overhead, and allow for connectionless or lightweight connections between protocol layers. This can lead to data caching issues throughout the transmission process. For example, the stop-and-wait buffer of the HARQ process, the MAC buffer, and the SDAP sent buffer. When the SDAP function serving a UE is adjusted on demand, if the SDAP PDU format changes, the sender may have to lose all data being transmitted, and the receiver may have to discard all data that has not been processed correctly. This results in data loss or increased complexity in the data processing flow (such as data packet rollback).

[0100] To address the aforementioned issues, this application proposes an SDAP PDU scheme with the same format for both uplink and downlink. This scheme defines a unified SDAP PDU format for both uplink and downlink, enabling adjustments to various functional services to be transmitted along with the path via this unified SDAP PDU, thereby ensuring that the SDAP PDU before adjustment can be correctly received by the receiving end.

[0101] This application defines the header of an SDAP PDU and the accompanying control information, achieving unified uplink and downlink PDU formats and enabling the carrying of information on various service changes along the route. Specifically, the header of the SDP PDU carries overall format information for the entire PDU, allowing the receiving end to quickly obtain the overall PDU format by reading the header.

[0102] Specifically, the same format of the uplink and downlink SDAP PDU in this application embodiment includes: a header unit and an SDAP Service Data Unit (SDU) portion. The SDAP SDU includes at least one of SDAP Control SDU and SDAP Data SDU.

[0103] The head unit includes:

[0104] Indication information used to indicate the constituent units of uplink and downlink SDAP PDUs;

[0105] SDAP controls the header information corresponding to the SDU and / or SDAP data SDU.

[0106] like Figure 9 As shown in the embodiments of this application, the header unit may include at least one of the following fields:

[0107] (1) The type field (D / C / H) indicates the type of the SDAP PDU, specifically the type of SDAP PDU to which this type field belongs. This type includes SDAP control PDUs, SDAP data PDUs, and SDAP hybrid PDUs. The SDAP hybrid PDU includes both SDAP control and SDAP data PDUs. Here, D can represent an SDAP data PDU, C can represent an SDAP control PDU, and H can represent an SDAP hybrid PDU. The type field can be 2 bits long.

[0108] Table 1 provides an example of a type field. When D / C / H takes the value of Data PDU (0 in Table 1), Figure 9 The QFI identifier in the table is the QoS flow ID of the SDAP data PDU. When D / C / H is a Control PDU (value 1 in Table 1), Figure 9 The QFI field is missing. When D / C / H takes the value of Control PDU and Data PDU (value 2 in Table 1), Figure 9 The QFI field in the control PDU must exist and be identified as the QoS Flow ID of the data PDU. The QoS flow identifier (if present) in the control PDU is included in... Figure 9 The Control SDU section.

[0109] Table 1

[0110] 0 SDAP Data PDU 1 SDAP Control PDU 2 SDAP hybrid PDU (Control PDU and Data PDU)

[0111] (2) QoS Flow Identifier (QFI) field, used to indicate the QoS flow identifier of the SDAP data PDU when the type field indicates the SDAP data PDU. The length of the QFI can be 6 bits.

[0112] (3) The first control flag field (Control Flag 1, CF1) is used to indicate the service scope of the SDAP control SDU when the type field indicates an SDAP control PDU or an SDAP hybrid PDU. The service scope is either the target QoS flow listed in the SDAP PDU or the QoS flow already established by the terminal. That is, when the type field indicates an SDAP control PDU or an SDAP hybrid PDU, the SDAP SDU to which CF1 belongs includes an SDAP control SDU. In this case, CF1 is used to determine whether the service indicated by the SDAP control SDU applies to all QoS flows already established by the terminal or to the target QoS flow listed in the SDAP control PDU. Here, the terminal refers to the first terminal corresponding to the SDAP PDU to which CF1 belongs. For example, when the SDAP PDU to which CF1 belongs is a downlink SDAP PDU, the terminal is the terminal that receives the downlink SDAP PDU; when the SDAP PDU to which CF1 belongs is an uplink SDAP PDU, the terminal is the terminal that sends the downlink SDAP PDU. The length of CF1 can be 1 bit.

[0113] Table 2 provides an example of CF1. When CF1 identifies all QoS flows of the terminal (UE) (value "0" in Table 2), the control information in the SDAP Control PDU (D / C / H = C) or Control SDU (D / C / H = H) does not carry any QoS flow ID. When CF1 identifies the QoS flow carried in the PDU (value "1" in Table 2), it only includes all QoS flows contained in the Control SDU. ((D / C / H = H, in which case the QFI field is used to identify the QoS flow described in the Data SDU).

[0114] Table 2

[0115] 0 All QoS flows of UE 1 QoS flows listing in the PDU

[0116] (4) The second control identifier field (CF2) is used to indicate the service correspondence of the SDAP control SDU when the service object range indicated by the first control identifier field (CF1) is the target QoS flow listed in the SDAP PDU. The service correspondence includes a first correspondence and a second correspondence, wherein the first correspondence is that all target QoS flows correspond to the same service in the SDAP control SDU, and the second correspondence is that there is a one-to-one correspondence between the target QoS flow and the service in the SDAP control SDU. That is, CF2 is used to identify the format of the SDAP Control PDU or Control SDU.

[0117] The length of CF2 can be 1 bit. Table 3 provides an example of CF2. When CF1 = (QoS flowslisting in the PDU) and D / C / H is C / H, it indicates whether the "service" in the control SDU corresponds to one "service" for each QoS flow carried in the SDAP Control PDU or Control SDU (as shown in Table 3, CF2 = 1), or whether all the carried QoS flows correspond to one "service" (as shown in Table 3, CF2 = 0). When CF1 = (All QoS flows of UE), CF2 is ignored, that is, CF2 is an invalid value.

[0118] Table 3

[0119]

[0120] (5) The Data Identifier Field (DF1) is used to indicate whether the SDAP Data SDU carries a Sequence Number (SN) when the Type Field (D / C / H) indicates an SDAP Control PDU or an SDAP Hybrid PDU, and, if so, to indicate the length of the sequence number. That is, DF1 is used to identify whether the SDAP Data PDU or Data SDU carries an SN (Sequence Number), and, if so, to indicate the length of the SN. The length of DF1 can be 2 bits.

[0121] Table 4 provides an example of DF1. As shown in Table 4, if DF1 = 0, it indicates that the SDAP Data PDU or Data SDU does not carry an SN number, meaning there is no sorting function. Other values ​​indicate the length of the SN number; for example, a value of 1 indicates that the SN number is 1 byte long.

[0122] Table 4

[0123] 0 0 Byte 1 1 Byte 2 2 Bytes 3 3 Bytes

[0124] In this embodiment of the application, when the type field indicates an SDAP hybrid PDU, the SDAP SDU includes at least one SDAP control SDU; the header unit further includes an extension field (E) and a first length field corresponding to each SDAP control SDU; wherein:

[0125] (6) The first length field (CL) is used to indicate the length of the SDAP control SDU corresponding to this extension field (E) when the type field (D / C / H) indicates an SDAP hybrid PDU. The length of CL can be 2 bytes. When D / C / H = D / C, the CL does not exist, that is, there is no CL field in the SDAP PDU. When D / C / H = H, it identifies the byte length of the Control SDU in the SDAP PDU.

[0126] Furthermore, the header unit may also include at least one of the following fields:

[0127] (7) Extension field (E): This field indicates whether there are any SDAP control SDUs following the SDAP control SDU corresponding to this extension field (E). The length of the E field can be 1 bit. Table 5 provides an example of the E field. In this example, a value of 0 indicates that the SDAP control SDU corresponding to this extension field (E) is the last SDAP control SDU in the SDAP PDU, and a value of 1 indicates that there are any SDAP control SDUs following the SDAP control SDU corresponding to this extension field (E), that is, the SDAP control SDU corresponding to this extension field (E) is not the last SDAP control SDU in the SDAP PDU.

[0128] Table 5

[0129]

[0130] (8) The RQI field is used to identify whether to instruct the Non-Access Stratum (NAS) to update the NAS mapping rules. The specific definition of this RQI field can be found in similar fields in existing technologies. This field may not exist in 6G systems.

[0131] (9) Reserved fields (R) are empty fields.

[0132] In this embodiment of the application, the SDAP control SDU includes at least one of the following fields:

[0133] (1) Service ID (SID) field, used to indicate the identifier (ID) of the service to which the SDAP control SDU requests, configures, or responds. The length of the SID can be an integer byte or a few bits. For example, the SID length is 6 bits.

[0134] (2) The third control identifier field (CF3) is used to indicate whether the service is in a fixed format or a non-fixed format. Fixed formats have a fixed length, while non-fixed formats have a variable length. That is, CF3 is used to determine whether the service indicated by the SID is in a fixed format. If it is, the L field mentioned below does not exist; otherwise, the L field exists to determine the length of the service context field, and then the service content is obtained by parsing the service context field. The length of CF3 can be 1 bit.

[0135] Table 6 provides an example of the CF3 field. A value of 0 for CF3 indicates a fixed format, and a value of 1 indicates a non-fixed format.

[0136] Table 6

[0137]

[0138]

[0139] (3) The fourth control identifier field (CF4) is used to indicate the length of the second length field when the third control identifier field indicates a non-fixed format. The length of CF3 can be 1 bit.

[0140] Table 7 provides an example of the CF4 field. As shown in Table 7, when CF3 takes the value 0 and 1, the length of the second length field is 8 bits and 16 bits, respectively. Of course, other values ​​can also be taken in this embodiment, such as 8 bits and 1 bit.

[0141] Table 7

[0142] 0 8 bits 1 16 bits

[0143] (4) The second length field (L field) is used to indicate the length of the service context field. That is, the value of the second length field is used to indicate the length of the service context field, such as the length in bytes. The length of the L field is determined by the value of CF4. For example, if the length of L is 8 bits, then the maximum length of the context information of a "service" is 255 bytes.

[0144] (5) Service Context Domain, which is used to indicate the context information of the service, that is, to indicate the content of the service.

[0145] Below are examples of SDAP SDU formats for certain situations.

[0146] For example, when the second control identifier field indicates that the service correspondence of the SDAP control SDU is the first correspondence (CF2 = 0 in Table 3, all QoS flows correspond to one "service"):

[0147] (A) If the service target range indicated by the first control identifier field is the target QoS flow listed in the SDAP control PDU (CF1 = 1 in Table 2, all QoS flows carried in the SDAP control SDU correspond to the same service format), then the SDAP control SDU includes: at least one service identifier field, and a service context field corresponding to the at least one service identifier field. A specific SDAP SDU format in this case is as follows: Figure 10 As shown.

[0148] (B) If the service scope indicated by the first control identifier field is the QoS flow already established by the first or second device (CF1 = 0 in Table 2, all QoS flows established by the UE correspond to the same service format), then the SDAP control SDU includes one of the service context fields. A specific SDAP SDU format in this case is as follows: Figure 11 As shown.

[0149] For example, when the first control identifier field indicates that the service correspondence of the SDAP control SDU is the second correspondence (CF1 = 1 in Table 2, and each QoS flow carried by the SDAP control SDU corresponds to a service): the SDAP control SDU includes: at least one service identifier field, and a service context field corresponding one-to-one with each service identifier field. For QoS flows that need to change the "service", each QoS flow can be assigned its corresponding "service" content. A specific SDAP SDU format in this case is as follows: Figure 12 As shown.

[0150] For example, in an embodiment of this application, when the data identifier field indicates that the SDAP data SDU carries a sequence number (DF1 is not equal to 0), the SDAP data SDU includes a sequence number field and a data field. A specific format of the SDAP data SDU in this case is as follows: Figure 13 As shown.

[0151] For example, when the data identifier field indicates that the SDAP data SDU does not carry a sequence number (DF1 equals 0), the SDAP data SDU includes a data field. A specific format of the SDAP data SDU in this case is as follows: Figure 14 As shown, the serial number (SN) is not carried at this time.

[0152] Based on the same format of uplink and downlink SDAP PDUs in the embodiments of this application, the embodiments of this application also provide a data transmission method applied to a first device, which may be a network device or a terminal, such as... Figure 15 As shown, the method includes:

[0153] Step 151: The first device generates a first SDAP PDU based on the same format of the uplink and downlink SDAP PDUs.

[0154] Here, the same format for the uplink and downlink SDAP PDUs includes: a header unit and an SDAP SDU, wherein the SDAP SDU includes at least one of an SDAP control SDU and an SDAP data SDU. For the specific structure, please refer to the description above.

[0155] Step 152: The first device sends a first SDAP PDU to the second device.

[0156] Through the above steps, the embodiments of this application can realize flexible on-demand activation of SDAP protocol-level service functions. Based on the unified SDAP PDU format, the SDAP PDU carries the PDU structure or various information or format indication information contained therein. The receiving end only needs to parse the SDAP PDU according to the same format, so as to avoid data loss when switching between different function services.

[0157] As can be seen, the embodiments of this application achieve flexible selection of protocol functions on demand, realizing a service-oriented RAN protocol stack scheme. Furthermore, because it uses the same format, compared to transmissions based on different formats, the embodiments of this application can reduce the overhead of RRC signaling used for format indication. The embodiments of this application can achieve zero handover and zero data loss during configuration information changes.

[0158] Furthermore, since the first device can be a network device or a terminal, the service scope of the SDAP control SDU indicated by the first control identifier field (CF1) is: the target QoS flow listed in the SDAP PDU to which the first control identifier field (CF1) belongs, or the QoS flow already established by the first device or the second device. Here, when the first device is a terminal, the QoS flow already established by the first device or the second device refers to the QoS flow already established by the first device; when the second device is a terminal, the QoS flow already established by the first device or the second device refers to the QoS flow already established by the second device.

[0159] This application also provides a data receiving method, applied to a second device, such as... Figure 16 As shown, the method includes:

[0160] Step 161: The second device receives the first SDAP PDU sent by the first device.

[0161] Here, the first SDAP PDU is an SDAP PDU generated based on the same format of the uplink and downlink SDAP PDUs. The same format of the uplink and downlink SDAP PDUs includes: a header unit and an SDAP SDU. The SDAP SDU includes at least one of SDAP control SDU and SDAP data SDU.

[0162] Step 162: The second device parses the first SDAPPDU according to the same format of the uplink and downlink SDAP PDUs.

[0163] Through the above steps, this application embodiment realizes flexible on-demand activation of SDAP protocol-level service functions. Based on the unified SDAP PDU format, the receiving device only needs to parse the SDAP PDU according to the same format to avoid data loss when switching between different function services.

[0164] In step 162 above, the second device determines the type of the first SDAP PDU according to the type field, and obtains the SDAP control SDU and / or SDAP data SDU in the first SDAP PDU according to the first control identifier field (CF1), the second control identifier field (CF2), and the data identifier field (DF1); then, it parses the SDAP control SDU in the first SDAP PDU according to the fields included in the SDAP control SDU, and / or parses the SDAP data SDU in the first SDAP PDU according to the fields included in the SDAP data SDU to obtain the SDAP data SDU.

[0165] In this embodiment, the SDAP PDU carries the PDU structure or various information or formatted indication information contained therein. This ensures that the receiving device can correctly parse the PDU when the function changes. During various "service" switching processes, the SDAP PDU is processed according to the accompanying information carried in the PDU, ensuring that no data packets are lost and that all data are processed correctly during the switching between old and new services.

[0166] When the "service" of a QoS flow is modified, the SDAP PDU is processed according to the in-band information carried in the PDU and the specific service is used. For example, if a new "sequencing" service is requested, there will also be Data SDUs without a serial number. When the second device receives such an SDU, it will deliver the data packet to the upper layer according to the processing before the "sequencing" service took effect.

[0167] The various methods of the embodiments of this application have been described above. Apparatus for implementing the above methods will now be provided.

[0168] Please refer to Figure 17 This application also provides a first device 1700, comprising:

[0169] The first generation module 1701 is used to generate the first SDAP PDU based on the same format of the uplink and downlink service data adaptation protocol SDAP protocol data unit PDU.

[0170] The first transmitting module 1702 is used to transmit a first SDAP PDU to the second device; wherein...

[0171] The same format for uplink and downlink SDAP PDUs includes: header unit and SDAP SDU.

[0172] Here, SDAP SDU includes at least one of SDAP control SDU and SDAP data SDU.

[0173] The same format for uplink and downlink SDAP PDUs can be found in the description above, and will not be repeated here.

[0174] It should be noted that the device in this embodiment corresponds to the method applied to the first device side described above. The implementation methods in each of the above embodiments are applicable to the embodiments of this device and can achieve the same technical effect. The device provided in this application embodiment can implement all the method steps implemented in the above method embodiments and can achieve the same technical effect. Therefore, the parts that are the same as those in the method embodiments and the beneficial effects will not be described in detail here.

[0175] Please refer to Figure 18 This application also provides a first device 1800, including: a transceiver 1801 and a processor 1802;

[0176] The processor 1802 described above is used to generate a first SDAP PDU based on the same format of the uplink and downlink service data adaptation protocol protocol data unit PDU;

[0177] The transceiver 1801 is used to send a first SDAP PDU to the second device; wherein...

[0178] The same format for uplink and downlink SDAP PDUs includes: a header unit and an SDAP SDU, wherein the SDAP SDU includes at least one of an SDAP control SDU and an SDAP data SDU.

[0179] The same format for uplink and downlink SDAP PDUs can be found in the description above, and will not be repeated here.

[0180] It should be noted that the device in this embodiment corresponds to the method applied to the first device side described above. The implementation methods in each of the above embodiments are applicable to the embodiments of this device and can achieve the same technical effect. The device provided in this application embodiment can implement all the method steps implemented in the above method embodiments and can achieve the same technical effect. Therefore, the parts that are the same as those in the method embodiments and the beneficial effects will not be described in detail here.

[0181] Please refer to Figure 19 This application embodiment also provides a second device 1900, including:

[0182] The first receiving module 1901 is used to receive the first SDAP PDU sent by the first device, wherein the first SDAP PDU is an SDAP PDU generated based on the same format of the uplink and downlink SDAP PDUs, and the same format of the uplink and downlink SDAP PDUs includes: a header unit and an SDAP PDU.

[0183] Here, SDAP SDU includes at least one of SDAP control SDU and SDAP data SDU;

[0184] The first parsing module 1902 is used to parse the first SDAP PDU according to the same format of the uplink and downlink SDAP PDUs.

[0185] The same format for uplink and downlink SDAP PDUs can be found in the description above, and will not be repeated here.

[0186] Optionally, the first parsing module is further configured to determine the type of the first SDAP PDU based on the type field, and obtain the SDAP control SDU and / or SDAP data SDU in the first SDAP PDU based on the first control identifier field (CF1), the second control identifier field (CF2), and the data identifier field (DF1); parse the SDAP control SDU in the first SDAP PDU based on the fields included in the SDAP control SDU, and / or parse the SDAP data SDU in the first SDAP PDU based on the fields included in the SDAP data SDU to obtain the SDAP data SDU.

[0187] It should be noted that the device in this embodiment corresponds to the method applied to the second device side described above. The implementation methods in each of the above embodiments are applicable to the embodiments of this device and can achieve the same technical effect. The device provided in this application embodiment can implement all the method steps implemented in the above method embodiments and can achieve the same technical effect. Here, the parts that are the same as those in the method embodiments and the beneficial effects will not be described in detail.

[0188] Please refer to Figure 20 This application also provides a second device 2000, including: a transceiver 2001 and a processor 2002;

[0189] The transceiver 2001 is used to receive a first SDAP PDU sent by the first device, wherein the first SDAP PDU is an SDAP PDU generated based on the same format of uplink and downlink SDAP PDUs, and the same format of uplink and downlink SDAP PDUs includes: header unit and SDAP PDU;

[0190] The processor 2002 parses the first SDAP PDU according to the same format of the uplink and downlink SDAP PDUs.

[0191] The same format for uplink and downlink SDAP PDUs can be found in the description above, and will not be repeated here.

[0192] Optionally, the processor is further configured to determine the type of the first SDAP PDU according to the type field, and obtain the SDAP control SDU and / or SDAP data SDU in the first SDAP PDU according to the first control identifier field (CF1), the second control identifier field (CF2), and the data identifier field (DF1); parse the SDAP control SDU in the first SDAP PDU according to the fields included in the SDAP control SDU, and / or parse the SDAP data SDU in the first SDAP PDU according to the fields included in the SDAP data SDU to obtain the SDAP data SDU.

[0193] It should be noted that the device in this embodiment corresponds to the method applied to the second device side described above. The implementation methods in each of the above embodiments are applicable to the embodiments of this device and can achieve the same technical effect. The device provided in this application embodiment can implement all the method steps implemented in the above method embodiments and can achieve the same technical effect. Here, the parts that are the same as those in the method embodiments and the beneficial effects will not be described in detail.

[0194] Please refer to Figure 21 This application also provides a first device 2100, including a processor 2101, a memory 2102, and a computer program stored in the memory 2102 and executable on the processor 2101. When the computer program is executed by the processor 2101, it implements the various processes of the data transmission method embodiment executed by the first device described above and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0195] Please refer to Figure 22This application also provides a second device 2200, including a processor 2201, a memory 2202, and a computer program stored in the memory 2202 and executable on the processor 2201. When the computer program is executed by the processor 2201, it implements the various processes of the data receiving method embodiment executed by the second device described above and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0196] This application also provides a computer-readable storage medium storing a computer program. When executed by a processor, the computer program implements the various processes of the above-described data transmission or data reception method embodiments and achieves the same technical effects. To avoid repetition, it will not be described again here. The computer-readable storage medium may include, for example, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0197] 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. Unless otherwise specified, 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.

[0198] Through 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 software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0199] 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 forms under the guidance of this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.

Claims

1. A data transmission method, characterized in that, include: The first device generates a first SDAP PDU based on the same format of the uplink and downlink service data adaptation protocol SDAP protocol data unit PDU; wherein, the same format of the uplink and downlink SDAP PDU includes: header unit and SDAP service data unit SDU; The first device sends a first SDAP PDU to the second device; The SDAP SDU includes at least one of SDAP control SDU and SDAP data SDU; the header unit includes at least one of the following fields: The type field is used to indicate the type of SDAP PDU, which includes SDAP control PDU, SDAP data PDU and SDAP hybrid PDU, wherein the SDAP SDU of the SDAP hybrid PDU includes SDAP control SDU and SDAP data SDU; The QoS flow identifier field is used to indicate the QoS flow identifier of the SDAP data PDU when the type field indicates an SDAP data PDU. The first control identifier field is used to indicate the service target range of the SDAP control SDU when the type field indicates an SDAP control PDU or an SDAP hybrid PDU. The second control identifier field is used to indicate the service correspondence of the SDAP control SDU when the service object range indicated by the first control identifier field is the target QoS flow listed in the SDAP PDU. The service correspondence includes: a first correspondence in which all target QoS flows correspond to the same service in the SDAP control SDU, and a second correspondence in which the target QoS flows correspond one-to-one with the services in the SDAP control SDU. The data identifier field is used to indicate whether the SDAP data SDU carries a sequence number and the length of the sequence number, when the type field indicates an SDAP control PDU or an SDAP hybrid PDU.

2. The method according to claim 1, characterized in that, When the type field indicates an SDAP hybrid PDU, the SDAP SDU includes at least one SDAP control SDU; the header unit further includes an extension field and a first length field corresponding to each SDAP control SDU; wherein, The extended field is used to indicate whether there is another SDAP control SDU after the SDAP control SDU corresponding to this extended field; The first length field is used to indicate the length of the SDAP control SDU corresponding to this first length field.

3. The method according to claim 1, characterized in that, The head unit also includes: The RQI field is used to indicate whether to instruct the non-access tier NAS to update the NAS mapping rules.

4. The method according to claim 1, characterized in that, The SDAP control SDU includes at least one of the following fields: The service identifier field is used to indicate the identifier of the service to which the SDAP control SDU requests, configures, or responds; The third control identifier field is used to indicate whether the service is a fixed format or a non-fixed format; The fourth control identifier field is used to indicate the length of the second length field when the third control identifier field indicates a non-fixed format. The second length field is used to indicate the length of the service context field; The service context field is used to indicate the context information of the service.

5. The method according to claim 4, characterized in that, When the second control identifier field indicates that the service correspondence of the SDAP control SDU is the first correspondence: If the service target range indicated by the first control identifier field is the target QoS flow listed in the SDAP control PDU, then the SDAP control PDU includes: at least one service identifier field, and a service context field corresponding to the at least one service identifier field; If the service target range indicated by the first control identifier field is the QoS flow established by the first device or the second device, then the SDAP control SDU includes one of the service context fields.

6. The method according to claim 4, characterized in that, When the first control identifier field indicates that the service correspondence of the SDAP control SDU is the second correspondence: The SDAP control SDU includes: at least one service identifier field, and a service context field corresponding to each service identifier field.

7. The method according to claim 4, characterized in that, When the data identifier field indicates that the SDAP data SDU carries a sequence number, the SDAP data SDU includes a sequence number field and a data field; When the data identifier field indicates that the SDAP data SDU does not carry a sequence number, the SDAP data SDU includes a data field.

8. A data receiving method, characterized in that, include: The second device receives the first SDAP PDU sent by the first device, wherein the first SDAP PDU is an SDAP PDU generated based on the same format of uplink and downlink SDAP PDUs, and the same format of uplink and downlink SDAP PDUs includes: header unit and SDAP PDU; The second device parses the first SDAP PDU according to the same format of the uplink and downlink SDAP PDUs; The SDAP SDU includes at least one of SDAP control SDU and SDAP data SDU; the header unit includes at least one of the following fields: The type field is used to indicate the type of SDAP PDU, which includes SDAP control PDU, SDAP data PDU and SDAP hybrid PDU, wherein the SDAP SDU of the SDAP hybrid PDU includes SDAP control SDU and SDAP data SDU; The QoS flow identifier field is used to indicate the QoS flow identifier of the SDAP data PDU when the type field indicates an SDAP data PDU. The first control identifier field is used to indicate the service target range of the SDAP control SDU when the type field indicates an SDAP control PDU or an SDAP hybrid PDU. The second control identifier field is used to indicate the service correspondence of the SDAP control SDU when the service object range indicated by the first control identifier field is the target QoS flow listed in the SDAP PDU. The service correspondence includes: a first correspondence in which all target QoS flows correspond to the same service in the SDAP control SDU, and a second correspondence in which the target QoS flows correspond one-to-one with the services in the SDAP control SDU. The data identifier field is used to indicate whether the SDAP data SDU carries a sequence number and the length of the sequence number, when the type field indicates an SDAP control PDU or an SDAP hybrid PDU.

9. The method according to claim 8, characterized in that, When the type field indicates an SDAP hybrid PDU, the SDAP SDU includes at least one SDAP control SDU; the header unit further includes an extension field and a first length field corresponding to each SDAP control SDU; wherein, The extended field is used to indicate whether there is another SDAP control SDU after the SDAP control SDU corresponding to this extended field; The first length field is used to indicate the length of the SDAP control SDU corresponding to this first length field.

10. The method according to claim 8, characterized in that, The head unit also includes: The RQI field is used to indicate whether to instruct the non-access tier NAS to update the NAS mapping rules.

11. The method according to claim 8, characterized in that, The SDAP control SDU includes at least one of the following fields: The service identifier field is used to indicate the identifier of the service to which the SDAP control SDU requests, configures, or responds; The third control identifier field is used to indicate whether the service is a fixed format or a non-fixed format; The fourth control identifier field is used to indicate the length of the second length field when the third control identifier field indicates a non-fixed format. The second length field is used to indicate the length of the service context field; The service context field is used to indicate the context information of the service.

12. The method according to claim 11, characterized in that, When the second control identifier field indicates that the service correspondence of the SDAP control SDU is the first correspondence: If the service target range indicated by the first control identifier field is the target QoS flow listed in the SDAP control PDU, then the SDAP control PDU includes: at least one service identifier field, and a service context field corresponding to the at least one service identifier field; If the service target range indicated by the first control identifier field is the QoS flow established by the first device or the second device, then the SDAP control SDU includes one of the service context fields.

13. The method according to claim 11, characterized in that, When the first control identifier field indicates that the service correspondence of the SDAP control SDU is the second correspondence: The SDAP control SDU includes: at least one service identifier field, and a service context field corresponding to each service identifier field.

14. The method according to claim 11, characterized in that, When the data identifier field indicates that the SDAP data SDU carries a sequence number, the SDAP data SDU includes a sequence number field and a data field; When the data identifier field indicates that the SDAP data SDU does not carry a sequence number, the SDAP data SDU includes a data field.

15. The method according to claim 8, characterized in that, The second device parses the first SDAP PDU according to the same format of the uplink and downlink SDAP PDUs, including: The second device determines the type of the first SDAP PDU according to the type field, and obtains the SDAP control SDU and / or SDAP data SDU in the first SDAP PDU according to the first control identifier field, the second control identifier field, and the data identifier field; Based on the fields included in the SDAP control SDU, the SDAP control SDU in the first SDAP PDU is parsed, and / or, based on the fields included in the SDAP data SDU, the SDAP data SDU in the first SDAP PDU is parsed to obtain the SDAP data SDU.

16. A first device, characterized in that, Includes transceivers and processors, among which, The processor is used to generate a first SDAP PDU based on the same format of the uplink and downlink service data adaptation protocol protocol data unit (PDU). The transceiver is used to send a first SDAP PDU to the second device; wherein the uplink and downlink SDAP PDUs have the same format including: a header unit and an SDAP PDU; The SDAP SDU includes at least one of SDAP control SDU and SDAP data SDU; the header unit includes at least one of the following fields: The type field is used to indicate the type of SDAP PDU, which includes SDAP control PDU, SDAP data PDU and SDAP hybrid PDU, wherein the SDAP SDU of the SDAP hybrid PDU includes SDAP control SDU and SDAP data SDU; The QoS flow identifier field is used to indicate the QoS flow identifier of the SDAP data PDU when the type field indicates an SDAP data PDU. The first control identifier field is used to indicate the service target range of the SDAP control SDU when the type field indicates an SDAP control PDU or an SDAP hybrid PDU. The second control identifier field is used to indicate the service correspondence of the SDAP control SDU when the service object range indicated by the first control identifier field is the target QoS flow listed in the SDAP PDU. The service correspondence includes: a first correspondence in which all target QoS flows correspond to the same service in the SDAP control SDU, and a second correspondence in which the target QoS flows correspond one-to-one with the services in the SDAP control SDU. The data identifier field is used to indicate whether the SDAP data SDU carries a sequence number and the length of the sequence number, when the type field indicates an SDAP control PDU or an SDAP hybrid PDU.

17. A first device, characterized in that, include: A processor, a memory, and a program stored in the memory and executable on the processor, wherein the program, when executed by the processor, implements the steps of the method as described in any one of claims 1 to 7.

18. A second device, characterized in that, Includes transceivers and processors, among which, The transceiver is used to receive a first SDAP PDU sent by a first device, wherein the first SDAP PDU is an SDAP PDU generated based on the same format of uplink and downlink SDAP PDUs, and the same format of uplink and downlink SDAP PDUs includes: a header unit and an SDAP PDU; The processor is configured to parse the first SDAP PDU according to the same format of the uplink and downlink SDAP PDUs; The SDAP SDU includes at least one of SDAP control SDU and SDAP data SDU; the header unit includes at least one of the following fields: The type field is used to indicate the type of SDAP PDU, which includes SDAP control PDU, SDAP data PDU and SDAP hybrid PDU, wherein the SDAP SDU of the SDAP hybrid PDU includes SDAP control SDU and SDAP data SDU; The QoS flow identifier field is used to indicate the QoS flow identifier of the SDAP data PDU when the type field indicates an SDAP data PDU. The first control identifier field is used to indicate the service target range of the SDAP control SDU when the type field indicates an SDAP control PDU or an SDAP hybrid PDU. The second control identifier field is used to indicate the service correspondence of the SDAP control SDU when the service object range indicated by the first control identifier field is the target QoS flow listed in the SDAP PDU. The service correspondence includes: a first correspondence in which all target QoS flows correspond to the same service in the SDAP control SDU, and a second correspondence in which the target QoS flows correspond one-to-one with the services in the SDAP control SDU. The data identifier field is used to indicate whether the SDAP data SDU carries a sequence number and the length of the sequence number, when the type field indicates an SDAP control PDU or an SDAP hybrid PDU.

19. A second device, characterized in that, include: A processor, a memory, and a program stored in the memory and executable on the processor, wherein the program, when executed by the processor, implements the steps of the method as described in any one of claims 8 to 15.

20. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the steps of the method as described in any one of claims 1 to 15.

Images