Method and device for header compression in wireless communication

Abstract

The invention discloses a method and equipment used for header compression in wireless communication. The method comprises the following steps: performing header compression on a first data SDU (Service Data Unit) in a first protocol layer; submitting a first data PDU to a second protocol layer, wherein the first data PDU is generated by the first data SDU subjected to header compression; performing encryption processing on a second data SDU on the second protocol layer, the second data SDU being the first data PDU received by the second protocol layer; submitting a second data PDU to a lower layer, the second data PDU being generated by the encrypted second data SDU; wherein the first protocol layer is a higher layer of the second protocol layer; the second protocol layer is a higher layer of the MAC layer; the first protocol layer and the second protocol layer are both protocol layers of an access layer; the service provided by the second protocol layer to the first protocol layer is a radio bearer. According to the invention, future wireless communication can be better supported.

Description

Technical Field

[0001] This application relates to a method for processing header compression in a wireless communication system, and particularly relates to a 6G or evolved NR network. Background Art

[0002] The application scenarios of future wireless communication systems are becoming increasingly diversified, and different application scenarios have different performance requirements for the system. To meet the different performance requirements of various application scenarios, it was decided at the 72nd plenary session of 3GPP (3rd Generation Partner Project) RAN (Radio Access Network) to conduct research on the new radio access technology (NR, New Radio) (or Fifth Generation, 5G). At the 75th plenary session of 3GPP RAN, the WI (Work Item) of NR was adopted, and the standardization work of NR began.

[0003] In communication, whether it is LTE (Long Term Evolution) or 5G NR, it involves the accurate reception of reliable information, optimized energy efficiency ratio, determination of information effectiveness, flexible resource allocation, scalable system architecture, efficient non-access stratum information processing, low service interruption and disconnection rates, support for low power consumption, which is of great significance for the normal communication between base stations and user equipment, for the reasonable scheduling of resources, and for the balance of system load. It can be said to be the cornerstone of high throughput, meeting the communication needs of various services, improving spectrum utilization, and improving service quality. It is indispensable for eMBB (enhanced Mobile BroadBand), URLLC (Ultra Reliable Low Latency Communication), or eMTC (enhanced Machine Type Communication). At the same time, in the IIoT (Industrial Internet of Things in the industrial field), in V2X (Vehicular to X), in device-to-device communication, in communication on unlicensed spectrum, in user communication quality monitoring, in network planning and optimization, in TN (Territerial Network), in dual connectivity systems, in radio resource management and multi-antenna codebook selection, in signaling design, neighbor cell management, service management, and in beamforming, there are extensive demands. The information sending methods are divided into broadcast and unicast, and both sending methods are essential for the 5G system because they are very helpful for meeting the above demands.

[0004] With the continuous increase in the scenarios and complexity of the system, higher requirements are put forward for reducing the interruption rate, reducing latency, enhancing reliability, enhancing system stability, business flexibility, and power saving. At the same time, compatibility between different system versions also needs to be considered during system design.

[0005] The meanings of the concepts, terms, and abbreviations in this application can be referred to the 3GPP standards, including but not limited to:

[0006] https: / / www.3gpp.org / ftp / Specs / archive / 21_series / 21.905 / 21905-h10.zip

[0007] https: / / www.3gpp.org / ftp / Specs / archive / 38_series / 38.300 / 38300-h10.zip

[0008] https: / / www.3gpp.org / ftp / Specs / archive / 38_series / 38.331 / 38331-h10.zip

[0009] https: / / www.3gpp.org / ftp / Specs / archive / 38_series / 38.323 / 38323-h10.zip

[0010] https: / / www.3gpp.org / ftp / Specs / archive / 38_series / 38.322 / 38322-h10.zip

[0011] https: / / www.3gpp.org / ftp / Specs / archive / 37_series / 37.324 / 37324-h10.zip

[0012] https: / / www.3gpp.org / ftp / Specs / archive / 33_series / 33.501 / 333501- h10.zip Summary of the Invention

[0013] Researchers have found that in scenarios where header compression and encryption are supported in the AS (Access Stratum), it is a problem to be solved how to implement header compression in which protocol layers among multiple protocol layers above the MAC layer and which protocol layers implement encryption.

[0014] In view of the above problems, the present application provides a solution.

[0015] It should be noted that, without conflict, the embodiments and features in any node of the present application can be applied to any other node. Without conflict, the embodiments and features in the embodiments of the present application can be combined with each other arbitrarily. At the same time, the method proposed in the present application can also be used to solve other problems in communication, such as NR evolution (further evolved NR), especially problems in the 6G system.

[0016] As an embodiment, the interpretation of the terms in the present application refers to the definitions in the 3GPP specification protocol series TS38.

[0017] As an embodiment, the interpretation of the terms in the present application refers to the definitions in the 3GPP specification protocol series TS37.

[0018] The present application discloses a method in a first node for wireless communication, including:

[0019] Performing header compression on a first data SDU (Service Data Unit) in a first protocol layer; submitting a first data PDU (Protocol Data Unit) to a second protocol layer, where the first data PDU is generated from the first data SDU after the header compression; performing encryption processing on a second data SDU in the second protocol layer, where the second data SDU is the first data PDU received by the second protocol layer; submitting a second data PDU to a lower layer, where the second data PDU is generated from the second data SDU after the encryption processing;

[0020] Among them, the first protocol layer is a higher layer of the second protocol layer; the second protocol layer is a higher layer of the MAC layer; both the first protocol layer and the second protocol layer are protocol layers of the access layer; the service provided by the second protocol layer to the first protocol layer is a radio bearer.

[0021] As an embodiment, the problems to be solved by this application include: which protocol layers among the multiple protocol layers above the MAC layer in the access layer implement header compression and which protocol layers implement encryption are problems that need to be solved.

[0022] As an embodiment, the benefits of the above method include: higher efficiency, better support for 6G services, network architectures, and user plane requirements; more flexibility, better support for richer services, better support for multi-model services, better compatibility, and provision of more flexible QoS.

[0023] Specifically, according to one aspect of this application, header compression is performed on the third data SDU at the first protocol layer; the third data PDU is submitted to the second protocol layer, where the third data PDU is generated from the third data SDU that has undergone the header compression.

[0024] Among them, submitting the first data PDU to the second protocol layer includes: submitting the first data PDU to the first protocol entity of the second protocol layer; submitting the third data PDU to the second protocol layer includes: submitting the third data PDU to the first protocol entity of the second protocol layer; the header compression performed on the first data SDU at the first protocol layer and the header compression performed on the third data SDU at the first protocol layer use different header compression profiles.

[0025] Specifically, according to one aspect of this application, the first data SDU and the third data SDU use different IP (Internet Protocol) addresses; the first data SDU and the third data SDU correspond to different QoS flows or different QoS (Quality of Service) sub-flows.

[0026] Specifically, according to one aspect of this application, header compression is performed on the third data SDU at the first protocol layer; the third data PDU is submitted to the second protocol layer, where the third data PDU is generated from the third data SDU that has undergone the header compression.

[0027] Among them, submitting the first data PDU to the second protocol layer includes: submitting the first data PDU to the first protocol entity of the second protocol layer; submitting the third data PDU to the second protocol layer includes: submitting the third data PDU to the second protocol entity of the second protocol layer; the first data SDU and the third data SDU correspond to the same QoS flow.

[0028] Specifically, according to one aspect of the present application, at the second protocol layer, segment the second data SDU;

[0029] Among them, the second protocol layer is the PDCP layer.

[0030] Specifically, according to one aspect of the present application, perform second header compression on the second data SDU at the second protocol layer, where the second header compression is header compression other than RoHC;

[0031] Among them, the header compression performed on the first data SDU at the first protocol layer is the first header compression based on RoHC.

[0032] Specifically, according to one aspect of the present application, the first protocol layer is the SDAP layer.

[0033] Specifically, according to one aspect of the present application, the second protocol layer is the PDCP layer.

[0034] Specifically, according to one aspect of the present application, the first protocol layer supports the mapping between QoS flows and radio bearers, and supports marking QoS flow identifiers.

[0035] Specifically, according to one aspect of the present application, the second protocol layer supports sequence numbers, supports integrity protection, supports duplication, and supports packet discarding.

[0036] Specifically, according to one aspect of the present application, both the first protocol layer and the second protocol layer are protocol layers above RLC.

[0037] Specifically, according to one aspect of the present application, the first node is an Internet of Things terminal.

[0038] Specifically, according to one aspect of the present application, the first node is a user equipment.

[0039] Specifically, according to one aspect of the present application, the first node is an access network device.

[0040] Specifically, according to one aspect of the present application, the first node is a vehicle-mounted terminal.

[0041] Specifically, according to one aspect of the present application, the first node is a mobile phone.

[0042] The present application discloses a first node for use in wireless communication, including:

[0043] A first transmitter that performs header compression on a first data SDU at a first protocol layer; submits a first data PDU to a second protocol layer, where the first data PDU is generated from the first data SDU that has undergone the header compression; performs encryption processing on a second data SDU at the second protocol layer, where the second data SDU is the first data PDU received by the second protocol layer; submits a second data PDU to a lower layer, where the second data PDU is generated from the second data SDU that has undergone the encryption processing;

[0044] Wherein, the first protocol layer is a higher layer of the second protocol layer; the second protocol layer is a higher layer of the MAC layer; both the first protocol layer and the second protocol layer are protocol layers of the access layer; the service provided by the second protocol layer to the first protocol layer is a radio bearer.

[0045] As an embodiment, compared with the traditional solution, the present application has the following advantages:

[0046] The 6G network will support more and richer service forms, which poses challenges to both the network architecture and the user plane. The method proposed in the present application is beneficial to enhancing the flexibility of the first protocol layer and the second protocol layer, and at the same time can better support the transmission of complex services, such as multi-model services, especially complex services using different TCP / IP headers.

[0047] It is beneficial to simplify the design of the second protocol layer, reduce complexity, and shorten the processing delay.

[0048] It can better support the transmission of services based on PDU sets, such as XR (Extended Reality).

[0049] Maintains the relative independence of each layer of protocol, which is beneficial to implementation, deployment, debugging and standardization.

[0050] It can better support the application of AI (Artificial Intelligence) in access. BRIEF DESCRIPTION OF THE DRAWINGS

[0051] By reading the detailed description of the non-limiting embodiments with reference to the following drawings, other features, objects and advantages of the present application will become more apparent:

[0052] Figure 1Shows a flowchart of header compression of the first data SDU at the first protocol layer according to an embodiment of the present application, submitting the first data PDU to the second protocol layer, encrypting the second data SDU at the second protocol layer, and submitting the second data PDU to a lower layer;

[0053] Figure 2 Shows a schematic diagram of a network architecture according to an embodiment of the present application;

[0054] Figure 3 Shows a schematic diagram of an embodiment of the radio protocol architecture of the user plane and the control plane of an NR network according to an embodiment of the present application;

[0055] Figure 4 Shows a schematic diagram of a first communication device and a second communication device according to an embodiment of the present application;

[0056] Figure 5 Shows a flowchart of wireless signal transmission according to an embodiment of the present application;

[0057] Figure 6 Shows a schematic diagram of a user plane processing procedure according to an embodiment of the present application;

[0058] Figure 7 Shows a schematic diagram of the first protocol layer and the second protocol layer according to an embodiment of the present application;

[0059] Figure 8 Shows a schematic diagram of the first protocol layer and the second protocol layer according to an embodiment of the present application;

[0060] Figure 9 Shows a schematic diagram of the first protocol layer and the second protocol layer according to an embodiment of the present application;

[0061] Figure 10 Illustrates a schematic diagram of a processing device in a first node according to an embodiment of the present application. Embodiment

[0063] The technical solutions of the present application will be further described in detail below with reference to the accompanying drawings. It should be noted that, without conflict, the embodiments and features in the embodiments of the present application can be combined with each other arbitrarily.

[0064] Example 1

[0065] Embodiment 1 illustrates a flowchart of header compression of the first data SDU at the first protocol layer according to an embodiment of the present application, submitting the first data PDU to the second protocol layer, encrypting the second data SDU at the second protocol layer, and submitting the second data PDU to a lower layer, as shown in the attachedFigure 1 as shown. Attached Figure 1 In the figure, each box represents a step. It should be particularly emphasized that the order of the boxes in the figure does not represent the chronological relationship between the represented steps in terms of time.

[0066] In Embodiment 1, the first node in the present application performs header compression on the first data SDU at the first protocol layer in step 101; submits the first data PDU to the second protocol layer in step 102; performs encryption processing on the second data SDU at the second protocol layer in step 103, and submits the second data PDU to a lower layer in step 104;

[0067] Among them, the first data PDU is generated from the first data SDU that has undergone the header compression; the second data SDU is the first data PDU received by the second protocol layer; the second data PDU is generated from the second data SDU that has undergone the encryption processing; the first protocol layer is a higher layer of the second protocol layer; the second protocol layer is a higher layer of the MAC layer; both the first protocol layer and the second protocol layer are protocol layers of the access layer; the service provided by the second protocol layer to the first protocol layer is a radio bearer.

[0068] As an embodiment, the first node is a UE (User Equipment).

[0069] As an embodiment, the first node is in the RRC connected state.

[0070] As an embodiment, the first node is in the RRC inactive state.

[0071] As an embodiment, the PDU of the higher layer received from the higher layer is the SDU of the current protocol layer.

[0072] As an embodiment, the PDU of the higher layer is the SDU of the current protocol layer.

[0073] As a sub - embodiment of this embodiment, the higher layer is the upper layer of the current protocol layer.

[0074] As a sub - embodiment of this embodiment, there are no other protocol layers between the higher layer and the current protocol layer.

[0075] As an embodiment, the first protocol layer processes the received SDU to generate the PDU of the first protocol layer.

[0076] As an embodiment, the second protocol layer processes the received SDU to generate the PDU of the second protocol layer.

[0077] As an example, the Access Stratum is a well-known term in the art.

[0078] As an example, in NR, the protocol layers or protocol sub-layers included in the Access Stratum correspond to Figure 3 , but in a 6G system, the names of the protocol layers or protocol sub-layers included in the Access Stratum may be different.

[0079] As an example, the Access Stratum is a functional combination, including parts belonging to the infrastructure and user equipment, and includes the protocols between these parts, which are particularly related to access technologies.

[0080] As an example, the protocols included in the Access Stratum terminate at the interruption and the radio access network.

[0081] As an example, the protocols included in the Access Stratum terminate at the interruption and the serving cell.

[0082] As an example, the protocols included in the Access Stratum terminate at the interruption and the base station.

[0083] As an example, different from the Access Stratum, the protocols included in the non-Access Stratum terminate at the user terminal and the core network.

[0084] As an example, different from the Access Stratum, the protocols included in the application layer terminate at the user terminal and the external application server.

[0085] As a sub-example of this example, the external application server includes servers on the Internet.

[0086] As an example, the protocol layers in this application can also be referred to as protocol sub-layers.

[0087] As an example, any parameter in this application is either configured by the network or can be generated by the first node according to an internal algorithm, such as randomly.

[0088] As an example, the values of any parameter in this application, including but not limited to the values of timers and counters, are finite unless otherwise stated.

[0089] As a sub-example of this example, the upper limit of the value of any parameter in this application is 1024 times 65536.

[0090] As a sub-example of this example, the upper limit of the value of any parameter in this application is 65536 or 65535.

[0091] As a sub - embodiment of this embodiment, the upper limit of the value of any parameter in this application is 1024.

[0092] As a sub - embodiment of this embodiment, the upper limit of the value of any parameter in this application is 640 or 320.

[0093] As an embodiment, this application is directed to a wireless communication network for NR evolution.

[0094] As an embodiment, this application is directed to a 6G wireless communication network.

[0095] As an embodiment, the NR evolution can also be referred to as 6G.

[0096] As an embodiment, the NR evolution is the next - generation wireless communication technology of NR.

[0097] As an embodiment, the serving cell refers to the cell where the UE camps. Performing cell search includes the UE searching for a suitable cell of the selected PLMN (Public Land Mobile Network) or SNPN (Stand - alone Non - Public Network), selecting the suitable cell to provide available services, and monitoring the control channel of the suitable cell. This process is defined as camping on the cell; that is, a camped - on cell, relative to this UE, is the serving cell of this UE. Camping on a cell in the RRC idle state or RRC inactive state has the following benefits: enabling the UE to receive system messages from the PLMN or SNPN; when registered, if the UE wishes to establish an RRC connection or resume a suspended RRC connection, the UE can achieve this by performing initial access on the control channel of the camped - on cell; the network can page the UE; enabling the UE to receive ETWS (Earthquake and Tsunami Warning System) and CMAS (Commercial Mobile Alert System) notifications.

[0098] As an example, for a UE in the RRC connected state without CA / DC (carrier aggregation / dual connectivity) configured, there is only one serving cell, which includes the primary cell. For a UE in the RRC connected state with CA / DC (carrier aggregation / dual connectivity) configured, the serving cell is used to indicate the cell set including the special cell (SpCell, Special Cell) and all secondary cells. The primary cell is the MCG (Master Cell Group) cell, which operates on the primary frequency, and the UE performs the initial connection establishment procedure or initiates connection reestablishment on the primary cell. For dual connectivity operation, the special cell refers to the PCell (Primary Cell) of the MCG or the PSCell (Primary SCGCell) of the SCG (Secondary Cell Group); if it is not dual connectivity operation, the special cell refers to the PCell.

[0099] As an example, the frequency on which the SCell (Secondary Cell) operates is the secondary frequency.

[0100] As an example, the individual content of an information element is called a field.

[0101] As an example, MR-DC (Multi-Radio Dual Connectivity) refers to the dual connectivity between an E-UTRA and an NR node, or the dual connectivity between two NR nodes.

[0102] As an example, in MR-DC, the radio access node that provides the control plane connection to the core network is the master node, and the master node can be the master eNB, the master ng-eNB, or the master gNB.

[0103] As an example, MCG refers to a set of serving cells associated with the master node in MR-DC, including the SpCell, and optionally, can also include one or more SCell.

[0104] As an example, the PCell is the SpCell of the MCG.

[0105] As an example, the PSCell is the SpCell of the SCG.

[0106] As an example, in MR-DC, a control plane connection to the core network is not provided, and the radio access node that provides additional resources to the UE is a secondary node. The secondary node can be an en-gNB, a secondary ng-eNB, or a secondary gNB.

[0107] As an example, in MR-DC, a set of serving cells associated with the secondary node is an SCG (secondary cell group), including a SpCell and, optionally, one or more SCell.

[0108] As an example, the SpCell is a PCell or the SpCell is a PSCell.

[0109] As an example, in the RRC inactive state, DC is not used.

[0110] As an example, in the RRC inactive state, CA is typically not used.

[0111] As an example, an RRC information block refers to an information element in an RRC message.

[0112] As an example, an SSB can be referred to as SS\PBCH, or an SS block.

[0113] As an example, L1 is Layer-1 or the physical layer.

[0114] As an example, the network targeted by this application for NR evolution, such as a 6G network.

[0115] As an example, an RRC information block can include one or more RRC information blocks.

[0116] As an example, an RRC information block can not include any RRC information blocks, but only include at least one parameter.

[0117] As an example, a radio bearer includes at least a signaling radio bearer and a data radio bearer.

[0118] As an example, a radio bearer is a service or an interface of a service provided by the second protocol layer to a higher layer of the second protocol layer.

[0119] As an example, a signaling radio bearer is a service or an interface of a service provided by the second protocol layer to a higher layer of the second protocol layer.

[0120] As a sub-example of this example, the higher layer of the second protocol layer includes at least the RRC layer and NAS.

[0121] As an embodiment, the data radio bearer is a service or an interface of a service provided by the second protocol layer to a higher layer of the second protocol layer.

[0122] As a sub - embodiment of this embodiment, the higher layer of the second protocol layer includes the first protocol layer.

[0123] As an embodiment, when the first node establishes an RRC connection with the network, the first node enters the RRC connected state.

[0124] As a sub - embodiment of this embodiment, the network is a radio access network (RAN).

[0125] As an embodiment, when the first node does not establish an RRC connection with the network, the first node is in the RRC idle state.

[0126] As a sub - embodiment of this embodiment, the network is a radio access network (RAN).

[0127] As an embodiment, when the RRC connection established by the first node with the network is suspended, the first node enters the RRC inactive state.

[0128] As a sub - embodiment of this embodiment, the network is a radio access network (RAN).

[0129] As an embodiment, different functions are supported in different RRC states.

[0130] As an embodiment, only very limited functions are supported in the non - RRC connected state.

[0131] As an embodiment, the non - RRC connected state is or includes the RRC idle state.

[0132] As an embodiment, the non - RRC connected state is or includes the RRC inactive state.

[0133] As an embodiment, this application is applicable to the RRC connected state.

[0134] As an embodiment, this application is not targeted at the RRC idle state.

[0135] As an embodiment, the first protocol layer supports the mapping between QoS flows and radio bearers.

[0136] As an embodiment, the first protocol layer supports marking the QoS flow identifier.

[0137] As an example, the meaning that the first protocol layer supports the mapping between QoS flows and radio bearers is that the first protocol layer uses the mapping function between QoS flows and radio bearers.

[0138] As an example, the meaning that the first protocol layer supports the mapping between QoS flows and radio bearers is that the functions of the first protocol layer include the mapping between QoS flows and radio bearers.

[0139] As an example, the meaning that the first protocol layer supports the mapping between QoS flows and radio bearers is that along with the header compression of the first data SDU at the first protocol layer, the QoS flow to which the first data SDU belongs is mapped to the first radio bearer at the first protocol layer.

[0140] As an example, the meaning that the first protocol layer supports marking the QoS flow identifier includes that the first protocol layer uses the function of marking the QoS flow identifier.

[0141] As an example, the meaning that the first protocol layer supports marking the QoS flow identifier includes that the functions of the first protocol layer include marking the QoS flow identifier.

[0142] As an example, the meaning that the first protocol layer supports marking the QoS flow identifier includes that along with the header compression of the first data SDU at the first protocol layer, the first node marks the QoS flow identifier at the first protocol layer.

[0143] As an example, the first protocol layer is an adaptation protocol layer.

[0144] As an example, the first protocol layer is an adaptation protocol related to service data.

[0145] As an example, the first protocol layer is the SDAP (Service Data Adaptation Protocol) layer.

[0146] As an example, there is no other protocol layer between the first protocol layer and the second protocol layer.

[0147] As an example, there is no other protocol sub-layer between the first protocol layer and the second protocol layer.

[0148] As an example, there is a direct interface between the first protocol layer and the second protocol layer.

[0149] As an example, the PDU generated by the first protocol layer is the SDU of the second protocol layer.

[0150] As an example, the first data SDU is a data SDU.

[0151] As an example, the first data SDU is not generated by RRC.

[0152] As an example, the first data SDU is not NAS (non access stratum) signaling.

[0153] As an example, the first data SDU is generated by the application layer of the first node.

[0154] As an example, the first data SDU is generated by the IP layer of the first node.

[0155] As an example, the header of the first data SDU carries an IP address.

[0156] As an example, the first data SDU belongs to a QoS flow.

[0157] As an example, the first data SDU belongs to a QoS sub - flow.

[0158] As an example, the first data SDU is uplink data.

[0159] As an example, the first data SDU is sent to the second protocol layer through a first data radio bearer.

[0160] As an example, those skilled in the art should understand at least one header compression protocol.

[0161] As an example, those skilled in the art should understand at least one method of performing header compression using a header compression protocol.

[0162] As an example, the header compression is used to compress the header of the first data SDU.

[0163] As an example, the header compression is used to save transmission resources.

[0164] As an example, the header compression performed on the first data SDU at the first protocol layer includes performing header compression using RoHC (RObust Header Compression).

[0165] As an example, the protocols related to RoHC can refer to IETF RFC 5795, IETF RFC 3095, IETF RFC 4815, IETF RFC 6846, and IETF RFC 5225.

[0166] As an example, RoHC is prior art.

[0167] As an example, the header compression performed on the first data SDU at the first protocol layer includes using EHC (Ethernet Header Compression) for header compression.

[0168] As an example, the header compression performed on the first data SDU at the first protocol layer includes using UDC (Uplink Data Compression).

[0169] As an example, there is an interface between the first protocol layer and the second protocol layer.

[0170] As an example, there is a service access point between the first protocol layer and the second protocol layer.

[0171] As an example, the submission of the first data PDU to the second protocol layer is through the interface or service access point between the first protocol layer and the second protocol layer.

[0172] As an example, the first data PDU is a data PDU.

[0173] As an example, the first data PDU is not generated by RRC.

[0174] As an example, the first data PDU is not NAS (non access stratum) signaling.

[0175] As an example, the first data PDU carries an IP address.

[0176] As an example, the first data PDU belongs to a QoS flow.

[0177] As an example, the first data PDU belongs to a QoS sub - flow.

[0178] As an example, the first data PDU is uplink data.

[0179] As an example, the first data PDU uses the first data radio bearer.

[0180] As an example, the first data PDU is transmitted via a first data radio bearer.

[0181] As an example, the generation of the first data PDU from the first data SDU that has undergone header compression includes: the first data SDU that has undergone header compression is the first data PDU.

[0182] As an example, the generation of the first data PDU from the first data SDU that has undergone header compression includes: the first data SDU that has undergone header compression is encapsulated to become the first data PDU.

[0183] As an example, the generation of the first data PDU from the first data SDU that has undergone header compression includes: the first data SDU that has undergone header compression and the header of the first protocol layer become the first data PDU.

[0184] As an example, the generation of the first data PDU from the first data SDU that has undergone header compression includes: the first data SDU that has undergone header compression and the header of the first protocol layer are encapsulated together to become the first data PDU.

[0185] As an example, the generation of the first data PDU from the first data SDU that has undergone header compression includes: the first data PDU carries the first data SDU.

[0186] As an example, the meaning that the second data PDU is generated from the second data SDU that has undergone encryption processing includes: the second data SDU that has undergone encryption processing is the second data PDU.

[0187] As an example, the meaning that the second data PDU is generated from the second data SDU that has undergone encryption processing includes: the second data SDU that has undergone encryption processing and the protocol header of the second protocol layer become the second data PDU.

[0188] As an example, the meaning that the second data PDU is generated from the second data SDU that has undergone encryption processing includes: the second data SDU that has undergone encryption processing and the protocol header of the second protocol layer are encapsulated together to become the second data PDU.

[0189] As an example, the meaning that the second data PDU is generated from the second data SDU that has undergone encryption processing includes: the second data PDU carries the second data SDU.

[0190] As an example, the second data SDU is the first data PDU.

[0191] As an example, when the second protocol layer receives the first data PDU, the first data PDU is the second data SDU for the second protocol layer.

[0192] As an example, the meaning that the second data SDU is the first data PDU received by the second protocol layer includes: the second data SDU is the first data PDU received by the second protocol layer from the first protocol layer.

[0193] As an example, the meaning that the second data SDU is the first data PDU received by the second protocol layer includes: the reception by the second protocol layer corresponds to submitting the first data PDU to the second protocol layer.

[0194] As an example, the encryption process of the second data SDU at the second protocol layer includes encrypting the second data SDU.

[0195] As an example, those skilled in the art should master at least one encryption method.

[0196] As an example, the encryption process of the second data SDU at the second protocol layer does not limit the encryption algorithm.

[0197] As an example, the encryption algorithms used in the encryption process of the second data SDU at the second protocol layer include one of AES, SNOW, and ChaCha.

[0198] As an example, those skilled in the art should understand that before encrypting the second data SDU at the second protocol layer, the first node and the network may need to perform signaling interactions including handshakes.

[0199] As an example, submitting the second data PDU to a lower layer includes: submitting the second data PDU to a lower layer of the second protocol layer through an interface or service access point between the second protocol layer and the lower layer of the second protocol layer.

[0200] As an example, the lower layer in submitting the second data PDU to a lower layer is the lower layer of the second protocol layer.

[0201] As an example, there is no other protocol layer between the lower layer in submitting the second data PDU to a lower layer and the second protocol layer.

[0202] As an example, there is no other protocol sublayer between the lower layer to which the second data PDU is submitted and the second protocol layer in the lower layer.

[0203] As an example, the lower layer to which the second data PDU is submitted is the RLC layer.

[0204] As an example, the lower layer to which the second data PDU is submitted is the MAC layer.

[0205] As an example, the interface between the second protocol layer and the lower layer of the second protocol layer is a logical channel.

[0206] As an example, the protocol header of the second data PDU indicates that the second data PDU is a PDU of a data type.

[0207] As an example, the protocol header of the second data PDU does not indicate that the second data PDU is a PDU of a data type.

[0208] As an example, the second data PDU is sent to the lower layer of the second protocol layer through a traffic channel.

[0209] As a sub - example of this example, the PDUs sent to the lower layer of the second protocol layer through the traffic channel are all data PDUs.

[0210] As a sub - example of this example, the traffic channel is a DTCH (downlink traffic channel).

[0211] As an example, since the second data SDU is an SDU of a data type, the PDU generated from the second data SDU, that is, the second data PDU, is a data PDU.

[0212] As an example, the first data PDU uses a data radio bearer, so the first data PDU is a PDU of a data type.

[0213] As an example, the second data SDU uses a data radio bearer, so the second data SDU is a PDU of a data type.

[0214] As an example, the second data SDU is the first data PDU, and the first data PDU is a PDU of a data type, so the second data SDU is an SDU of a data type.

[0215] As an example, the meaning that the first protocol layer is a higher layer than the second protocol layer includes: the first protocol layer is higher than the second protocol layer.

[0216] As an example, the meaning that the first protocol layer is a higher layer than the second protocol layer includes: the first protocol layer is above the second protocol layer.

[0217] As an example, the meaning that the first protocol layer is a higher layer than the second protocol layer includes: when transmitting, data is submitted from the first protocol layer to the second protocol layer.

[0218] As an example, the meaning that the first protocol layer is a higher layer than the second protocol layer includes: when receiving, data is submitted from the second protocol layer to the first protocol layer.

[0219] As an example, the meaning that the second protocol layer is a higher layer than the MAC layer is: the second protocol layer is above the MAC layer.

[0220] As an example, there are no other protocol layers between the second protocol layer and the MAC layer.

[0221] As an example, there are other protocol layers between the second protocol layer and the MAC layer.

[0222] As a sub - example of this example, the other protocol layer is the RLC layer.

[0223] As an example, the service provided by the second protocol layer to the first protocol layer being a radio bearer means that the interface between the first protocol layer and the second protocol layer is a radio bearer.

[0224] As an example, the second protocol layer supports sequence numbers.

[0225] As an example, the protocol header of the data PDU generated by the second protocol layer includes a sequence number.

[0226] As an example, the header of the second data PDU includes a sequence number.

[0227] As an example, the header of the second data PDU includes a sequence number field.

[0228] As an example, the second protocol layer supports integrity protection.

[0229] As an example, the functions of the second protocol layer include integrity protection.

[0230] As an example, the second protocol layer supports integrity protection including performing integrity protection processing on the second data SDU.

[0231] As an example, accompanying the encryption processing of the second data SDU in the second protocol layer, the first node performs integrity protection processing on the second data SDU in the second protocol layer.

[0232] As an example, the second protocol layer supports duplication.

[0233] As an example, the functions of the second protocol layer include duplication.

[0234] As an example, the duplication supported by the second protocol layer is to duplicate the SDU of the second protocol layer and transmit it through multiple paths to improve performance, such as increasing reliability.

[0235] As an example, the second protocol layer supports packet discard.

[0236] As an example, when the SDU sent through one path is confirmed to be received by the peer, the protocol entity of the second protocol layer instructs to delete the SDU replicated and transmitted through other paths.

[0237] As an example, the second protocol layer is a protocol layer related to packet data.

[0238] As an example, the second protocol layer is a packet data convergence protocol layer.

[0239] As an example, the second protocol layer is the PDCP (Packet Data Convergence Protocol) layer.

[0240] As an example, when the access layer includes the RLC layer, the second protocol layer is a protocol layer above the RLC layer.

[0241] As a sub - example of this example, there is no other protocol layer between the second protocol layer and the RLC layer.

[0242] As a sub - example of this example, when the access layer does not include the RLC layer, there is no other protocol layer between the second protocol layer and the MAC layer.

[0243] As a sub - example of this example, the second protocol layer is the PDCP layer.

[0244] As an example, when the access layer does not include the RLC layer, there is no other protocol layer between the second protocol layer and the MAC layer.

[0245] As a sub - embodiment of this embodiment, the second protocol layer is the PDCP layer.

[0246] As an embodiment, the advantage of the above - mentioned method is that it can better support the requirements of the 6G system and reduce the processing delay.

[0247] As an embodiment, both the first protocol layer and the second protocol layer are protocol layers below the IP layer.

[0248] As an embodiment, the peer protocol layer of the first protocol layer is in the RAN.

[0249] As an embodiment, the peer protocol layer of the first protocol layer is in the cell.

[0250] As an embodiment, the peer protocol layer of the first protocol layer is in the base station.

[0251] As an embodiment, the peer protocol layer of the second protocol layer is in the RAN.

[0252] As an embodiment, the peer protocol layer of the second protocol layer is in the cell.

[0253] As an embodiment, the peer protocol layer of the second protocol layer is in the base station.

[0254] As an embodiment, the first node sends the second data PDU through the air interface at the lower layer.

[0255] As an embodiment, sending the second data PDU through the air interface is sending it to the serving cell.

[0256] Example 2

[0257] Embodiment 2 exemplifies a schematic diagram of a network architecture according to the present application, as shown in the appendix Figure 2 as follows.

[0258] Appendix Figure 2A diagram illustrating the network architecture 200 of 5G NR, LTE (Long-Term Evolution), and LTE-A (Long-Term Evolution Advanced) systems. The 5G NR or LTE network architecture 200 may be referred to as 5GS (5G System) / EPS (Evolved Packet System) 200 or some other suitable term. The 5GS / EPS 200 may include one or more UEs (User Equipment) 201, NG-RAN (Next Generation Radio Access Network) 202, 5GC (5G Core Network) / EPC (Evolved Packet Core) 210, HSS (Home Subscriber Server) / UDM (Unified Data Management) 220, and Internet services 230. The 5GS / EPS may be interconnected with other access networks, but these entities / interfaces are not shown for simplicity. As shown, the 5GS / EPS provides packet-switched services. However, those skilled in the art will readily understand that the various concepts presented throughout this application can be extended to networks providing circuit-switched services or other cellular networks. The NG-RAN includes NR Node B (gNB) 203 and other gNBs 204. The gNB 203 provides user and control plane protocol termination towards the UE 201. The gNB 203 may be connected to other gNBs 204 via the Xn interface (e.g., backhaul). The gNB 203 may also be referred to as a base station, base transceiver station, radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), TRP (Transmit Receive Point), or some other suitable term. The gNB 203 provides an access point to the 5GC / EPC 210 for the UE 201. Examples of the UE 201 include cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptop computers, personal digital assistants (PDAs), satellite radios, non-terrestrial base station communications, satellite mobile communications, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, drones, aircraft, narrowband Internet of Things devices, machine type communication devices, land vehicles, automobiles, wearable devices, or any other similar functional devices. Those skilled in the art may also refer to the UE 201 as a mobile station, subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable term.gNB203 is connected to 5GC / EPC210 via the S1 / NG interface. 5GC / EPC210 includes MME (Mobility Management Entity) / AMF (Authentication Management Field) / SMF (Session Management Function) 211, other MME / AMF / SMF 214, S-GW (Service Gateway) / UPF (User Plane Function) 212, and P-GW (Packet Date Network Gateway) / UPF 213. MME / AMF / SMF 211 is a control node that processes the signaling between UE201 and 5GC / EPC210. Generally, MME / AMF / SMF 211 provides bearer and connection management. All user IP (Internet Protocal) packets are transmitted through S-GW / UPF 212, and S-GW / UPF 212 itself is connected to P-GW / UPF 213. P-GW provides UE IP address allocation and other functions. P-GW / UPF 213 is connected to the Internet service 230. The Internet service 230 includes operator-corresponding Internet protocol services, specifically including the Internet, intranet, IMS (IP Multimedia Subsystem), and packet-switched streaming services.

[0259] As an embodiment, the first node in this application is UE201.

[0260] As an embodiment, the base station of the second node in this application is gNB203.

[0261] As an embodiment, the radio link from the UE201 to the NR node B is an uplink.

[0262] As an embodiment, the radio link from the NR node B to the UE201 is a downlink.

[0263] As an embodiment, the UE201 includes a mobile phone.

[0264] As an embodiment, the UE201 is a vehicle including an automobile.

[0265] As an embodiment, the gNB203 is a macrocellular base station.

[0266] As an example, the gNB 203 is a Micro Cell base station.

[0267] As an example, the gNB 203 is a Pico Cell base station.

[0268] As an example, the gNB 203 is an aerial platform device.

[0269] As an example, the gNB 203 is a satellite device.

[0270] Example 3

[0271] Embodiment 3 shows a schematic diagram of an embodiment of the radio protocol architecture of a user plane and a control plane of an NR network, as shown in the appendix Figure 3 as follows. Figure 3 It is a schematic diagram illustrating an embodiment of the radio protocol architecture for the user plane 350 and the control plane 300, Figure 3The radio protocol architecture of the control plane 300 for the first node (UE, gNB) and the second node (gNB, UE), or between two UEs, is shown in three layers: layer 1, layer 2, and layer 3. Layer 1 (L1 layer) is the lowest layer and implements various PHY (Physical Layer) signal processing functions. Layer 1 will be referred to as PHY 301 in this document. Layer 2 (L2 layer) 305 is above PHY 301 and is responsible for the link between the first node and the second node, and between two UEs through PHY 301. Layer 2 305 includes a MAC (Medium Access Control) sublayer 302, an RLC (Radio Link Control) sublayer 303, and a PDCP (Packet Data Convergence Protocol) sublayer 304, and these sublayers terminate at the second node. The PDCP sublayer 304 provides multiplexing between different radio bearers and logical channels. The PDCP sublayer 304 also provides security by encrypting data packets, and provides handover support for the first node between the second nodes. The RLC sublayer 303 provides segmentation and reassembly of upper layer data packets, retransmission of lost data packets, and reordering of data packets to compensate for out-of-order reception due to HARQ. The MAC sublayer 302 provides multiplexing between logical and transport channels. The MAC sublayer 302 is also responsible for allocating various radio resources (e.g., resource blocks) in a cell between the first nodes. The MAC sublayer 302 is also responsible for HARQ operations. The RRC (Radio Resource Control) sublayer 306 in layer 3 (L3 layer) of the control plane 300 is responsible for obtaining radio resources (i.e., radio bearers) and configuring the lower layers using the RRC signaling between the second node and the first node. The PC5-S (PC5 Signaling Protocol) sublayer 307 is responsible for handling the signaling protocol of the PC5 interface. The radio protocol architecture of the user plane 350 includes layer 1 (L1 layer) and layer 2 (L2 layer). The radio protocol architecture for the first node and the second node in the user plane 350 is generally the same as the corresponding layers and sublayers in the control plane 300 for the physical layer 351, the PDCP sublayer 354 in the L2 layer 355, the RLC sublayer 353 in the L2 layer 355, and the MAC sublayer 352 in the L2 layer 355, but the PDCP sublayer 354 also provides header compression for upper layer data packets to reduce radio transmission overhead.The L2 layer 355 in the user plane 350 further includes an SDAP (Service Data Adaptation Protocol) sub-layer 356. The SDAP sub-layer 356 is responsible for the mapping between QoS flows and data radio bearers (DRBs) to support the diversity of services. The SRB can be regarded as a service or interface provided by the PDCP layer to higher layers, such as the RRC layer. In the NR system, the SRB includes SRB1, SRB2, and SRB3, which are used to transmit different types of control signaling respectively. The SRB is a bearer between the UE and the access network and is used to transmit control signaling including RRC signaling between the UE and the access network. SRB1 is of particular significance to the UE. After each UE establishes an RRC connection, there will be an SRB1 for transmitting RRC signaling. Most signaling is transmitted through SRB1. If SRB1 is interrupted or unavailable, the UE must perform RRC reconstruction. SRB2 is generally only used to transmit NAS signaling or signaling related to security. The UE may not be configured with SRB3. Except for emergency services, the UE must establish an RRC connection with the network to perform subsequent communications. Although not shown, the first node may have several upper layers above the L2 layer 355. In addition, it also includes a network layer (e.g., IP layer) terminated at the P-GW on the network side and an application layer terminated at the other end of the connection (e.g., a remote UE, a server, etc.).

[0272] As an example, the Figure 3 radio protocol architecture in is applicable to the first node in the present application.

[0273] As an example, the Figure 3 radio protocol architecture in is applicable to the second node in the present application.

[0274] As an example, the first data SDU in the present application is generated in a protocol layer above SDAP356.

[0275] As an example, the first data PDU in the present application is generated in the first protocol layer.

[0276] As an example, the second data SDU in the present application is generated in the first protocol layer.

[0277] As an example, the second data PDU in the present application is generated in the second protocol layer.

[0278] As an example, the first signaling in the present application is generated in RRC306.

[0279] As an example, the first data packet in the present application is generated in MAC352 or PHY351.

[0280] As an embodiment, the second data packet in the present application is generated at the MAC 352 or the PHY 351.

[0281] As an embodiment, the third data SDU in the present application is generated at a protocol layer above the SDAP 356.

[0282] As an embodiment, the third data PDU in the present application is generated at the first protocol layer.

[0283] As an embodiment, the fourth data SDU in the present application is generated at the first protocol layer.

[0284] As an embodiment, the fourth data PDU in the present application is generated at the second protocol layer.

[0285] Example 4

[0286] Embodiment 4 shows a schematic diagram of a first communication device and a second communication device according to an embodiment of the present application, as shown in the appendix Figure 4 as shown. Figure 4 is a block diagram of a first communication device 450 and a second communication device 410 that communicate with each other in an access network.

[0287] The first communication device 450 includes a controller / processor 459, a memory 460, a data source 467, a transmitting processor 468, a receiving processor 456, and optionally, a multi-antenna transmitting processor 457, a multi-antenna receiving processor 458, a transmitter / receiver 454, and an antenna 452.

[0288] The second communication device 410 includes a controller / processor 475, a memory 476, a receiving processor 470, a transmitting processor 416, and optionally, a multi-antenna receiving processor 472, a multi-antenna transmitting processor 471, a transmitter / receiver 418, and an antenna 420.

[0289] In the transmission from the second communication device 410 to the first communication device 450, at the second communication device 410, upper layer data packets from the core network are provided to the controller / processor 475. The controller / processor 475 implements the functionality of the L2 (Layer-2) layer. In the transmission from the second communication device 410 to the first communication device 450, the controller / processor 475 provides header compression, encryption, packet segmentation and reordering, multiplexing between logical and transport channels, and radio resource allocation for the first communication device 450 based on various priority metrics. The controller / processor 475 is also responsible for retransmission of lost packets and signaling to the first communication device 450. The transmit processor 416 and the multi-antenna transmit processor 471 implement various signal processing functions for the L1 layer (i.e., the physical layer). The transmit processor 416 implements encoding and interleaving to facilitate forward error correction (FEC) at the second communication device 410, and mapping of signal constellations based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The multi-antenna transmit processor 471 performs digital space precoding on the encoded and modulated symbols, including codebook-based precoding and non-codebook-based precoding, and beamforming processing, to generate one or more spatial streams. The transmit processor 416 then maps each spatial stream to subcarriers, multiplexes with reference signals (e.g., pilots) in the time domain and / or frequency domain, and then uses the inverse fast Fourier transform (IFFT) to generate a physical channel carrying a time-domain multi-carrier symbol stream. Subsequently, the multi-antenna transmit processor 471 performs transmit analog precoding / beamforming operations on the time-domain multi-carrier symbol stream. Each transmitter 418 converts the baseband multi-carrier symbol stream provided by the multi-antenna transmit processor 471 into a radio frequency stream and then provides it to different antennas 420.

[0290] In the transmission from the second communication device 410 to the first communication device 450, at the first communication device 450, each receiver 454 receives signals via its respective antenna 452. Each receiver 454 recovers the information modulated onto the radio frequency carrier and converts the radio frequency stream into a baseband multi-carrier symbol stream provided to the receive processor 456. The receive processor 456 and the multi-antenna receive processor 458 perform various signal processing functions of the L1 layer. The multi-antenna receive processor 458 performs receive analog precoding / beamforming operations on the baseband multi-carrier symbol stream from the receivers 454. The receive processor 456 uses the fast Fourier transform (FFT) to convert the baseband multi-carrier symbol stream after the receive analog precoding / beamforming operations from the time domain to the frequency domain. In the frequency domain, the physical layer data signal and the reference signal are demultiplexed by the receive processor 456, where the reference signal will be used for channel estimation, and the data signal recovers any spatial streams destined for the first communication device 450 after multi-antenna detection in the multi-antenna receive processor 458. The symbols on each spatial stream are demodulated and recovered in the receive processor 456, and soft decisions are generated. Subsequently, the receive processor 456 decodes and deinterleaves the soft decisions to recover the upper layer data and control signals transmitted by the second communication device 410 on the physical channel. Subsequently, the upper layer data and control signals are provided to the controller / processor 459. The controller / processor 459 performs the functions of the L2 layer. The controller / processor 459 may be associated with a memory 460 that stores program code and data. The memory 460 may be referred to as a computer-readable medium. In the transmission from the second communication device 410 to the second communication device 450, the controller / processor 459 provides demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover upper layer data packets from the core network. Subsequently, the upper layer data packets are provided to all protocol layers above the L2 layer. Various control signals may also be provided to the L3 for L3 processing.

[0291] In the transmission from the first communication device 450 to the second communication device 410, at the first communication device 450, a data source 467 is used to provide upper layer data packets to a controller / processor 459. The data source 467 represents all protocol layers above the L2 layer. Similar to the transmit function described at the second communication device 410 in the transmission from the second communication device 410 to the first communication device 450, the controller / processor 459 implements header compression, encryption, packet segmentation and reordering, and multiplexing between logical and transport channels based on radio resource allocation, and implements L2 layer functions for the user plane and the control plane. The controller / processor 459 is also responsible for retransmission of lost packets and signaling to the second communication device 410. A transmit processor 468 performs modulation mapping and channel coding processing, and a multi-antenna transmit processor 457 performs digital multi-antenna spatial precoding, including codebook-based precoding and non-codebook-based precoding, and beamforming processing. Subsequently, the transmit processor 468 modulates the generated spatial streams into multi-carrier / single-carrier symbol streams, and after passing through an analog precoding / beamforming operation in the multi-antenna transmit processor 457, provides them to different antennas 452 via a transmitter 454. Each transmitter 454 first converts the baseband symbol stream provided by the multi-antenna transmit processor 457 into a radio frequency symbol stream and then provides it to the antenna 452.

[0292] In the transmission from the first communication device 450 to the second communication device 410, the functions at the second communication device 410 are similar to the receive functions described at the first communication device 450 in the transmission from the second communication device 410 to the first communication device 450. Each receiver 418 receives radio frequency signals through its corresponding antenna 420, converts the received radio frequency signals into baseband signals, and provides the baseband signals to a multi-antenna receive processor 472 and a receive processor 470. The receive processor 470 and the multi-antenna receive processor 472 jointly implement the functions of the L1 layer. A controller / processor 475 implements the L2 layer functions. The controller / processor 475 may be associated with a memory 476 that stores program code and data. The memory 476 may be referred to as a computer-readable medium. In the transmission from the first communication device 450 to the second communication device 410, the controller / processor 475 provides demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover upper layer data packets from the UE 450. The upper layer data packets from the controller / processor 475 may be provided to the core network.

[0293] As an embodiment, the first communication device 450 includes: at least one processor and at least one memory, the at least one memory including computer program code; the at least one memory and the computer program code are configured to be used together with the at least one processor, and the first communication device 450 is at least: performing header compression on a first data SDU at a first protocol layer; submitting a first data PDU to a second protocol layer, where the first data PDU is generated from the first data SDU that has undergone the header compression; performing encryption processing on a second data SDU at the second protocol layer, where the second data SDU is the first data PDU received by the second protocol layer; submitting a second data PDU to a lower layer, where the second data PDU is generated from the second data SDU that has undergone the encryption processing; where the first protocol layer is a higher layer of the second protocol layer; the second protocol layer is a higher layer of the MAC layer; the first protocol layer and the second protocol layer are both protocol layers of the access layer; and the service provided by the second protocol layer to the first protocol layer is a radio bearer.

[0294] As an embodiment, the first communication device 450 includes: a memory storing a computer-readable instruction program, the computer-readable instruction program generating actions when executed by at least one processor, the actions including: performing header compression on a first data SDU at a first protocol layer; submitting a first data PDU to a second protocol layer, where the first data PDU is generated from the first data SDU that has undergone the header compression; performing encryption processing on a second data SDU at the second protocol layer, where the second data SDU is the first data PDU received by the second protocol layer; submitting a second data PDU to a lower layer, where the second data PDU is generated from the second data SDU that has undergone the encryption processing; where the first protocol layer is a higher layer of the second protocol layer; the second protocol layer is a higher layer of the MAC layer; the first protocol layer and the second protocol layer are both protocol layers of the access layer; and the service provided by the second protocol layer to the first protocol layer is a radio bearer.

[0295] As an embodiment, the first communication device 450 corresponds to the first node in the present application.

[0296] As an embodiment, the second communication device 410 corresponds to the second node in the present application.

[0297] As an embodiment, the first communication device 450 is a UE.

[0298] As an embodiment, the first communication device 450 is a vehicle-mounted terminal.

[0299] As an example, the first communication device 450 is a mobile phone.

[0300] As an example, the second communication device 450 is a relay.

[0301] As an example, the second communication device 410 is a satellite.

[0302] As an example, the second communication device 410 is an aircraft.

[0303] As an example, the second communication device 410 is a base station.

[0304] As an example, the receiver 454 (including the antenna 452), the receiving processor 456, and the controller / processor 459 are used to receive the first signaling in this application.

[0305] As an example, the transmitter 454 (including the antenna 452), the transmitting processor 468, and the controller / processor 459 are used to send the first data SDU in this application.

[0306] As an example, the transmitter 454 (including the antenna 452), the transmitting processor 468, and the controller / processor 459 are used to send the first data PDU in this application.

[0307] As an example, the transmitter 454 (including the antenna 452), the transmitting processor 468, and the controller / processor 459 are used to send the second data SDU in this application.

[0308] As an example, the transmitter 454 (including the antenna 452), the transmitting processor 468, and the controller / processor 459 are used to send the second data PDU in this application.

[0309] As an example, the transmitter 454 (including the antenna 452), the transmitting processor 468, and the controller / processor 459 are used to send the third data SDU in this application.

[0310] As an example, the transmitter 454 (including the antenna 452), the transmitting processor 468, and the controller / processor 459 are used to send the third data PDU in this application.

[0311] As an example, the transmitter 454 (including the antenna 452), the transmitting processor 468, and the controller / processor 459 are used to send the fourth data SDU in this application.

[0312] As an example, the transmitter 454 (including the antenna 452), the transmitting processor 468, and the controller / processor 459 are used to transmit the fourth data PDU in this application.

[0313] As an example, the transmitter 454 (including the antenna 452), the transmitting processor 468, and the controller / processor 459 are used to transmit the first data packet in this application.

[0314] Example 5

[0315] Example 5 exemplifies a wireless signal transmission flowchart according to an embodiment of this application, as shown in the appendix Figure 5 shown. In the appendix Figure 5 U01 corresponds to the first node of this application. It should be specifically noted that the order in this example does not limit the signal transmission order and implementation order in this application, and the steps within F51 and F52 are optional.

[0316] For First Node U01 , in step S5101, the first signaling is received; in step S5102, header compression is performed on the first data SDU at the first protocol layer; in step S5103, the first data PDU is submitted to the second protocol layer; in step S5104, encryption processing is performed on the second data SDU at the second protocol layer; in step S5105, the second data PDU is submitted to a lower layer; in step S5106, the first data packet is transmitted; in step S5107, header compression is performed on the third data SDU at the first protocol layer; in step S5108, the third data PDU is submitted to the second protocol layer; in step S5109, encryption processing is performed on the fourth data SDU at the second protocol layer; in step S5110, the fourth data PDU is submitted to a lower layer; in step S5111, the second data packet is transmitted.

[0317] For Second Node U02 , in step S5201, the first signaling is transmitted; in step S5202, the first data packet is received; in step S5203, the second data packet is received.

[0318] In Example 5, the first data PDU is generated from the first data SDU that has undergone the header compression; the second data SDU is the first data PDU received by the second protocol layer; the second data PDU is generated from the second data SDU that has undergone the encryption processing; the first protocol layer is a higher layer than the second protocol layer; the second protocol layer is a higher layer than the MAC layer; both the first protocol layer and the second protocol layer are protocol layers of the access layer; the service provided by the second protocol layer to the first protocol layer is a radio bearer.

[0319] As an example, the first node U01 receives the first signaling in the RRC connected state.

[0320] As an example, the second node U02 is the base station corresponding to the PCell of the first node U01.

[0321] As an example, the second node U02 is the second cell or the base station to which the second cell belongs.

[0322] As an example, the second node U02 is a network device of a 6G network.

[0323] As an example, the first signaling includes RRC signaling.

[0324] As an example, the first signaling includes NAS signaling.

[0325] As an example, the first signaling configures at least one of header compression and encryption.

[0326] As an example, the first signaling configures integrity protection.

[0327] As an example, the first signaling establishes a first radio bearer, and the first data SDU uses the first radio bearer.

[0328] As an example, it is a prior art in the art for the network to configure header compression through signaling.

[0329] As an example, it is a prior art in the art for the network to configure encryption through signaling.

[0330] As an example, the first node U01 performs header compression and / or encryption processing through stored parameters.

[0331] As a sub - example of this example, the stored parameters are the parameters stored in the SIM card.

[0332] As a sub - example of this example, the stored parameters are the parameters received and stored in the RRC connected state.

[0333] As an example, step S5101 is before step S5102.

[0334] As an example, step S5102 is before step S5103.

[0335] As an example, step S5103 is before step S5104.

[0336] As an example, step S5104 is before step S5105.

[0337] As an example, step S5105 is before step S5106.

[0338] As an example, any one of steps S5107 to S5111 and any one of steps S5102 to S5106 have no requirement of temporal precedence.

[0339] As an example, steps S5107 to S5110 are all earlier than step S5106.

[0340] As a sub - example of this example, step S5111 is missing, and the fourth data PDU is transmitted through the first data packet.

[0341] As an example, steps S5107 to S5110 are later than step S5106.

[0342] As a sub - example of this example, step S5111 exists, and the fourth data PDU is transmitted through the second data packet.

[0343] As an example, step S5107 is before step S5108.

[0344] As an example, step S5108 is before step S5109.

[0345] As an example, step S5109 is before step S5110.

[0346] As an example, step S5110 is before step S5111.

[0347] As an example, step S5106 and step S5111 can be processed in parallel.

[0348] As an example, the first data packet and the second data packet can be multiplexed together.

[0349] As an example, the first data packet and the second data packet can be multiplexed in the same MAC PDU.

[0350] As an example, whether the first data packet and the second data packet can be multiplexed in the same MAC PDU is network - configured.

[0351] As an example, when there are sufficient resources, the first data packet and the second data packet are multiplexed in the same MAC PDU.

[0352] As an example, when the wireless resources are only sufficient to transmit the first data packet, the first data packet and the second data packet are not multiplexed in the same MAC PDU.

[0353] As an embodiment, step S5201 is before step S5202.

[0354] As an embodiment, step S5202 is before step S5203.

[0355] As an embodiment, the first data packet is a lower-layer data packet.

[0356] As an embodiment, the first data packet is a lower-layer data packet of the second protocol layer.

[0357] As an embodiment, the first data packet is a MAC PDU.

[0358] As an embodiment, the first data packet carries the second data PDU.

[0359] As an embodiment, sending data to a network through a lower-layer data packet is a prior art in the art.

[0360] As a sub-embodiment of this embodiment, the lower-layer data packet is the first data packet.

[0361] As an embodiment, the three data PDUs are generated from the third data SDU that has undergone header compression.

[0362] As a sub-embodiment of this embodiment, the third data PDU is the third data SDU that has undergone header compression.

[0363] As a sub-embodiment of this embodiment, the third data PDU is generated from the third data SDU that has undergone header compression and the header of the first protocol layer.

[0364] As a sub-embodiment of this embodiment, the third data SDU that has undergone header compression and the header of the first protocol layer are encapsulated together to form the third data PDU.

[0365] As a sub-embodiment of this embodiment, the third data PDU carries the third data SDU.

[0366] As an embodiment, submitting the first data PDU to the second protocol layer includes: submitting the first data PDU to the first protocol entity of the second protocol layer; submitting the third data PDU to the second protocol layer includes: submitting the third data PDU to the first protocol entity of the second protocol layer.

[0367] As a sub-embodiment of this embodiment, the first data PDU and the third data PDU use the same radio bearer.

[0368] As a sub - embodiment of this embodiment, the first data PDU and the third data PDU are submitted to the second protocol layer using the same service access point.

[0369] As a sub - embodiment of this embodiment, the first data PDU and the third data PDU are generated by different protocol entities of the first protocol layer respectively.

[0370] As a sub - embodiment of this embodiment, the first data PDU and the third data PDU are generated by the same protocol entity of the first protocol layer respectively.

[0371] As an embodiment, the header compression performed on the first data SDU at the first protocol layer and the header compression performed on the third data SDU at the first protocol layer use different header compression profiles.

[0372] As a sub - embodiment of this embodiment, the first signaling indicates the header compression profile for the header compression of the first data SDU at the first protocol layer.

[0373] As a sub - embodiment of this embodiment, the first signaling indicates the header compression profile for the header compression of the third data SDU at the first protocol layer.

[0374] As a sub - embodiment of this embodiment, the header compression performed on the first data SDU at the first protocol layer and the header compression performed on the third data SDU at the first protocol layer using different header compression profiles is beneficial to improving flexibility, is beneficial to supporting different, for example, IP addresses and higher - layer protocols for the first data SDU and the third data SDU, and is beneficial to better supporting multi - model services.

[0375] As an embodiment, it is allowed to configure multiple header compression profiles for the same radio bearer.

[0376] As an embodiment, those of ordinary skill in the art should understand what a header compression profile is.

[0377] As an embodiment, the first node U01 performs header compression on the third data SDU at the first protocol layer.

[0378] As a sub - embodiment of this embodiment, the first node U01 submits the third data PDU to the second protocol layer, where the third data PDU is generated from the third data SDU that has undergone the header compression.

[0379] As a sub - embodiment of this embodiment, the third data PDU is the third data SDU that has undergone header compression.

[0380] As a sub - embodiment of this embodiment, the third data PDU is generated from the header - compressed third data SDU and the header of the first protocol layer.

[0381] As a sub - embodiment of this embodiment, the header - compressed third data SDU and the header of the first protocol layer are encapsulated together to form the third data PDU.

[0382] As a sub - embodiment of this embodiment, the third data PDU carries the third data SDU.

[0383] As an embodiment, submitting the first data PDU to the second protocol layer includes: submitting the first data PDU to the first protocol entity of the second protocol layer; submitting the third data PDU to the second protocol layer includes: submitting the third data PDU to the second protocol entity of the second protocol layer.

[0384] As a sub - embodiment of this embodiment, the first data SDU and the third data SDU correspond to the same QoS flow.

[0385] As a sub - embodiment of this embodiment, the first data SDU and the third data SDU correspond to the same QoS sub - flow.

[0386] As a sub - embodiment of this embodiment, the first data PDU and the third data PDU use different radio bearers.

[0387] As a sub - embodiment of this embodiment, the first data PDU and the third data PDU are submitted to the second protocol layer through different service access points respectively.

[0388] As an embodiment, the advantages of the above - mentioned method include: for the same service or the same PDU session, different radio bearers can be used for transmission, which is beneficial to providing different services for different data of the same service, saving resources, improving efficiency, being beneficial to supporting more complex services, and being beneficial to better supporting multi - modality services.

[0389] As an embodiment, the first data SDU and the third data SDU correspond to the same QoS flow.

[0390] As an embodiment, the first data SDU and the third data SDU correspond to the same QoS sub - flow.

[0391] As an embodiment, the first node U01 segments the second data SDU at the second protocol layer.

[0392] As a sub - embodiment of this embodiment, the first node U01 segments the second data SDU according to the indication of the lower layer of the second protocol layer.

[0393] As a sub - embodiment of this embodiment, the first node U01 segments the second data SDU according to the size of the radio resources.

[0394] As a sub - embodiment of this embodiment, the first node U01 segments the second data SDU according to the radio resources so that the second data SDU adapts to the radio resources after segmentation.

[0395] As a sub - embodiment of this embodiment, the first node U01 segments the second data SDU according to the indication of the network.

[0396] As a sub - embodiment of this embodiment, the header of the second data PDU includes some bits of the second data SDU.

[0397] As a sub - embodiment of this embodiment, the header of the second data PDU includes the number of segments of the second data SDU.

[0398] As a sub - embodiment of this embodiment, the number of segments of the second data SDU included in the header of the second data PDU is relative to the second data SDU.

[0399] As an embodiment, the first node U01 performs second header compression on the second data SDU at the second protocol layer, where the second header compression is based on header compression other than the first header compression protocol.

[0400] As an embodiment, the header compression performed by the first node U01 on the first data SDU at the first protocol layer is the first header compression based on the first header compression protocol.

[0401] As an embodiment, the header compression performed on the first data SDU at the first protocol layer is the first header compression.

[0402] As an embodiment, the first header compression is based on the first header compression protocol.

[0403] As an embodiment, the first header compression uses the first header compression protocol.

[0404] As an embodiment, the second header compression does not use the first header compression protocol.

[0405] As an embodiment, the second header compression uses a protocol other than the first header compression protocol.

[0406] As an example, the first header compression protocol is RoHC.

[0407] As an example, the first header compression protocol is EHC.

[0408] As an example, the first header compression protocol is UDC.

[0409] As an example, the header compression other than the first header compression protocol is RoHC-based header compression, and the first header compression protocol is EHC or the first header compression protocol is UDC.

[0410] As an example, the header compression other than the first header compression protocol is EHC-based header compression, and the first header compression protocol is RoHC or the first header compression protocol is UDC.

[0411] As an example, the header compression other than the first header compression protocol is UDC-based header compression, and the first header compression protocol is EHC or the first header compression protocol is RoHC.

[0412] As an example, for the first data SDU, performing first header compression at the first protocol layer and second header compression at the second protocol layer respectively is beneficial to improving compatibility and is beneficial to better supporting the simultaneous use of multiple header compression algorithms.

[0413] As an example, when the second data PDU and the fourth data PDU are multiplexed together, step S5111 is not necessary.

[0414] As an example, the second data PDU and the fourth data PDU are multiplexed in the first data packet.

[0415] As an example, the different header compression profiles used for the header compression of the first data SDU at the first protocol layer and the header compression of the third data SDU at the first protocol layer mean that: the profile of the header compression of the first data SDU at the first protocol layer and the profile of the header compression of the third data SDU at the first protocol layer are independently configured.

[0416] As an example, the different header compression profiles used for the header compression of the first data SDU at the first protocol layer and the header compression of the third data SDU at the first protocol layer mean that: the header compression of the first data SDU at the first protocol layer and the header compression of the third data SDU at the first protocol layer respectively correspond to their own header compression channels.

[0417] As an example, the different header compression profiles used for header compression of the first data SDU at the first protocol layer and for header compression of the third data SDU at the first protocol layer mean that: the header compression of the first data SDU at the first protocol layer and the header compression of the third data SDU at the first protocol layer respectively correspond to their own header compression entities.

[0418] As an example, the first protocol entity of the second protocol layer multiplexes the SDU of the second protocol layer carrying the first data PDU and the SDU of the second protocol layer carrying the third data PDU in the same PDU of the second protocol layer.

[0419] As an example, the different header compression profiles are used for header compression of the first data SDU at the first protocol layer and for header compression of the third data SDU at the first protocol layer.

[0420] Example 6

[0421] Embodiment 6 exemplifies a schematic diagram of a user plane processing procedure according to an embodiment of the present application, as shown in the appendix Figure 6 as follows.

[0422] The appendix Figure 6 shows the structure of the access layer user plane, where the ellipses represent the interfaces or service access points between two layers. The interfaces between adjacent layers are different, and different interfaces mean different functions. The appendix Figure 6 also shows the functions of each layer. In implementation, each layer may further include functions not shown in the appendix Figure 6 where the RLC layer is optional in some embodiments.

[0423] As an example, the interface between the first protocol layer and the higher layer of the first protocol layer is a flow, and the first protocol layer receives the flow from the higher layer.

[0424] As a sub - embodiment of this embodiment, the flow is a QoS flow.

[0425] As a sub - embodiment of this embodiment, the flow corresponds to a service.

[0426] As a sub - embodiment of this embodiment, the flow corresponds to a session.

[0427] As a sub - embodiment of this embodiment, the first data SDU is received by the first protocol layer through the flow.

[0428] As a sub - embodiment of this embodiment, the flow is an information flow or an IP flow.

[0429] As an embodiment, in the appendix Figure 6 There are 3 interfaces between the first protocol layer and the higher layer, which is to represent multiple, rather than being limited to 3.

[0430] As an embodiment, the first protocol layer supports mapping multiple flows to the same entity of the second protocol layer.

[0431] As an embodiment, the flow operation of the first protocol layer is to map the flow to the corresponding radio bearer.

[0432] As an embodiment, which flows the first protocol layer maps to which radio bearers is network - configured.

[0433] As an embodiment, which flows the first protocol layer maps to which radio bearers is predefined.

[0434] As an embodiment, which flows the first protocol layer maps to which radio bearers is fixed.

[0435] As an embodiment, multiple PDUs in the flows received by the first protocol layer use different IP addresses.

[0436] As an embodiment, multiple PDUs in the flows received by the first protocol layer use different TCP ports.

[0437] As an embodiment, multiple PDUs in the flows received by the first protocol layer use different TCP / IP addresses.

[0438] As an embodiment, there are multiple TCP / IP addresses used by multiple PDUs in the flows received by the first protocol layer.

[0439] As an embodiment, there are multiple IP addresses used by multiple PDUs in the flows received by the first protocol layer.

[0440] As an embodiment, there are multiple TCP ports used by multiple PDUs in the flows received by the first protocol layer.

[0441] As an embodiment, any one PDU in the flows received by the first protocol layer uses only one IP address.

[0442] As an embodiment, any one PDU in the flows received by the first protocol layer uses only one TCP port.

[0443] As an example, any PDU in the stream received by the first protocol layer uses only one TCP / IP address.

[0444] As an example, the first data SDU is a data PDU received by the first protocol layer from a higher layer.

[0445] As an example, the first data SDU is an IP packet received by the first protocol layer from a higher layer.

[0446] As an example, the first data SDU is non-3GPP data received by the first protocol layer from a higher layer.

[0447] As an example, the first data SDU is a PDU received by the first protocol layer from a higher layer that can be header-compressed by RoHC.

[0448] As an example, the first data SDU is a PDU received by the first protocol layer from a higher layer that can be supported by RoHC.

[0449] As an example, the second protocol layer may include one or more entities.

[0450] As an example, which entity of the second protocol layer the first data PDU is submitted to is network-indicated.

[0451] As a sub-example of this example, the network indicates via the first signaling which entity of the second protocol layer the first data PDU is submitted to.

[0452] As an example, which entity of the second protocol layer the first data PDU is submitted to is determined by the first node itself.

[0453] As an example, the first data PDU may be submitted to multiple entities of the second protocol layer.

[0454] As an example, the first data PDU is submitted to one entity of the second protocol layer.

[0455] As an example, one entity of the second protocol layer corresponds to one radio bearer.

[0456] As an example, which radio bearer the first data PDU uses is network-indicated.

[0457] As a sub-example of this example, the network indicates via the first signaling which radio bearer the first data PDU uses.

[0458] As an example, which radio bearer the first data PDU uses is determined by the first node itself.

[0459] As an example, the first data PDU can be submitted to multiple radio bearers.

[0460] As an example, the first data PDU is submitted to one radio bearer.

[0461] As an example, the interface between the first protocol layer and the second protocol layer is a radio bearer.

[0462] As an example, a radio bearer is a service provided by the second protocol layer to the first protocol layer.

[0463] As an example, the second protocol layer does not support header compression.

[0464] As an example, the second protocol layer only supports header compression different from that of the first protocol layer.

[0465] As an example, the second protocol layer only supports header compression using a different header compression protocol from that of the first protocol layer.

[0466] As an example, the functions of the second protocol layer, in addition to the security function, include at least one of in-sequence delivery, retransmission, discard, segmentation, discarding duplicate data, and calculating data capacity.

[0467] As an example, the second protocol layer uses a transmission window mechanism.

[0468] As an example, the security of the second protocol layer includes encryption.

[0469] As an example, the security of the second protocol layer includes at least the former of encryption and integrity protection.

[0470] As an example, submitting the second data PDU to a lower layer means submitting the second data PDU to the RLC layer.

[0471] As an example, submitting the second data PDU to a lower layer means submitting the second data PDU to the MAC layer.

[0472] As a sub-example of this example, the RLC layer is missing.

[0473] As a sub-example of this example, there is no other protocol layer between the second protocol layer and the MAC layer.

[0474] As an embodiment, the interface between the second protocol layer and the RLC layer is an RLC channel.

[0475] As an embodiment, the second data PDU is submitted to the RLC layer through the RLC channel.

[0476] As an embodiment, the second data PDU is received by an RLC entity of the RLC layer.

[0477] As an embodiment, the second protocol layer is not the RLC layer.

[0478] As an embodiment, the second protocol layer is a higher layer of the RLC layer.

[0479] As an embodiment, the functions of the RLC layer include segmentation.

[0480] As an embodiment, the functions of the RLC layer include ARQ (Automatic Repeat reQuest).

[0481] As an embodiment, the RLC layer includes a transparent mode, an unacknowledged mode, and an acknowledged mode.

[0482] As an embodiment, the functions of the RLC layer include using sequence numbers.

[0483] As an embodiment, the functions of the RLC layer include protocol error detection.

[0484] As an embodiment, the functions of the RLC layer include duplicate detection.

[0485] As an embodiment, the interface between the RLC layer and the MAC layer is a logical channel.

[0486] As an embodiment, when the access stratum does not include the RLC layer, the second data PDU is submitted to the MAC layer through the interface between the second protocol layer and the MAC layer.

[0487] As an embodiment, the functions of the MAC layer include scheduling.

[0488] As an embodiment, the scheduling algorithm is prior art in the art.

[0489] As an embodiment, the functions of the MAC layer include multiplexing. The MAC layer multiplexes the received MAC SDUs into one MAC PDU according to the size of the available radio resources.

[0490] As an embodiment, the functions of the MAC layer further include HARQ (Hybrid Automatic Repeat reQuest).

[0491] As an example, HARQ is a prior art in the field.

[0492] As an example, the interface between the MAC layer and the lower layer of the MAC layer is the transport channel.

[0493] As a sub - example of this example, the lower layer of the MAC layer is the physical layer.

[0494] As an example, the first data packet is a MAC PDU.

[0495] As an example, the first data packet is sent to the network through the physical layer.

[0496] As an example, the first data packet carries at least some bits of the second data PDU.

[0497] As an example, the first data packet carries at least one segment of the second data PDU.

[0498] As an example, the first data packet carries at least some bits of the fourth data PDU.

[0499] As an example, the first data packet carries at least one segment of the fourth data PDU.

[0500] As an example, the second data PDU can be submitted to an RLC entity for processing or, after being replicated, can be submitted to multiple RLC entities for processing respectively.

[0501] As an example, the above - mentioned processing method for the user plane is beneficial to supporting richer services, increasing flexibility, reducing processing delay, and improving the performance of the user plane for a 6G network.

[0502] Example 7

[0503] Example 7 illustrates a schematic diagram of the first protocol layer and the second protocol layer according to an example of the present application, as shown in the appendix Figure 7 as follows.

[0504] As an example, the first data SDU is the first PDU of the higher layer of the first protocol layer.

[0505] As an example, the first PDU is an IP packet.

[0506] As an example, the first PDU is an application - layer data packet.

[0507] As an example, the first PDU is not an access - layer PDU.

[0508] As an example, the first PDU is submitted to the protocol entity of the first protocol layer through the service access point of the first protocol layer.

[0509] As an example, the first data SDU is the first PDU received by the first protocol layer entity from a higher layer.

[0510] As an example, the interface between the first protocol layer and the second protocol layer is a radio bearer.

[0511] As an example, the radio bearer is a service provided by the second protocol layer to the first protocol layer.

[0512] As an example, the first data PDU is submitted to the entity of the second protocol layer and is transmitted through the radio bearer.

[0513] As an example, the second data SDU is the first data PDU received by the second protocol layer.

[0514] As an example, any processing performed in the first protocol layer is any processing performed by at least one entity of the first protocol layer.

[0515] As an example, any processing performed in the second protocol layer is any processing performed by at least one entity of the second protocol layer.

[0516] As an example, a protocol layer exchanges signaling and / or data with other protocol layers through service access points.

[0517] As an example, entities of a protocol layer exchange signaling and / or data with entities of other protocol layers through service access points.

[0518] As an example, a protocol entity of the first protocol layer processes the first data SDU and the third data SDU.

[0519] As a sub - example of this example, the first data SDU and the third data SDU belong to different services.

[0520] As a sub - example of this example, the first data SDU and the third data SDU belong to the same service.

[0521] As a sub - example of this example, the advantages of the above method include: low implementation complexity and small memory footprint.

[0522] As a sub - embodiment of this embodiment, the second data PDU and the fourth data PDU are processed by the same protocol entity of the second protocol layer.

[0523] As a sub - embodiment of this embodiment, the advantages of the above - mentioned method include: low implementation complexity, only one protocol entity of the second protocol layer needs to be created.

[0524] As a sub - embodiment of this embodiment, the second data PDU and the fourth data PDU are processed by different protocol entities of the second protocol layer.

[0525] As a sub - embodiment of this embodiment, the advantages of the above - mentioned method include: better guarantee the processing of the second data PDU and the fourth data PDU without mutual interference.

[0526] As an embodiment, different protocol entities of the first protocol layer process the first data SDU and the third data SDU.

[0527] As a sub - embodiment of this embodiment, the first data SDU and the third data SDU belong to different services.

[0528] As a sub - embodiment of this embodiment, the first data SDU and the third data SDU belong to the same service.

[0529] As a sub - embodiment of this embodiment, the advantages of the above - mentioned method include: short processing time, which is beneficial to parallel processing.

[0530] As a sub - embodiment of this embodiment, the second data PDU and the fourth data PDU are processed by the same protocol entity of the second protocol layer.

[0531] As a sub - embodiment of this embodiment, the advantages of the above - mentioned method include: low implementation complexity, only one protocol entity of the second protocol layer needs to be created.

[0532] As a sub - embodiment of this embodiment, the second data PDU and the fourth data PDU are processed by different protocol entities of the second protocol layer.

[0533] As a sub - embodiment of this embodiment, the advantages of the above - mentioned method include: better guarantee the processing of the second data PDU and the fourth data PDU without mutual interference.

[0534] As an embodiment, the data PDU of the first protocol layer processed by the first protocol layer entity is dynamically submitted to multiple protocol entities of the second protocol layer.

[0535] As an example, the mapping relationship between the first protocol layer entity and the entity of the second protocol layer is dynamic.

[0536] As an example, the first node determines which entity of the second protocol layer the data PDU of the first protocol layer entity is submitted to according to one of the load, internal algorithm, indication of the lower layer, queuing delay, and network signaling.

[0537] As an example, the advantages of the above method include: facilitating load balancing, ensuring transmission quality, and reducing transmission delay.

[0538] Example 8

[0539] Embodiment 8 exemplifies a schematic diagram of the first protocol layer and the second protocol layer according to an embodiment of the present application, as shown in the appendix Figure 8 as shown.

[0540] As an example, the first data SDU is the first PDU of the higher layer of the first protocol layer.

[0541] As an example, the first PDU is an IP packet.

[0542] As an example, the first PDU is an application layer data packet.

[0543] As an example, the first PDU is not an access layer PDU.

[0544] As an example, the first PDU is submitted to the protocol entity of the first protocol layer through the service access point of the first protocol layer.

[0545] As an example, the first data SDU is the first PDU received by the first protocol layer entity from the higher layer.

[0546] As an example, the third data SDU is the third PDU of the higher layer of the first protocol layer.

[0547] As an example, the third PDU is an IP packet.

[0548] As an example, the third PDU is an application layer data packet.

[0549] As an example, the third PDU is not an access layer PDU.

[0550] As an example, the third PDU is submitted to the protocol entity of the first protocol layer through the service access point of the first protocol layer.

[0551] As an example, the third data SDU is the third PDU received by the first protocol layer entity from a higher layer.

[0552] As an example, the interface between the first protocol layer and the second protocol layer is a radio bearer.

[0553] As an example, a radio bearer is a service provided by the second protocol layer to the first protocol layer.

[0554] As an example, the third data PDU is submitted to an entity of the second protocol layer for transmission via a radio bearer.

[0555] As an example, the fourth data SDU is the third data PDU received by the second protocol layer.

[0556] As an example, the third data PDU is submitted to an entity of the second protocol layer for transmission via a radio bearer.

[0557] As an example, the fourth data SDU is the third data PDU received by the second protocol layer.

[0558] As an example, a protocol layer exchanges signaling and / or data with other protocol layers through service access points.

[0559] As an example, entities of a protocol layer exchange signaling and / or data with entities of other protocol layers through service access points.

[0560] As an example, the first data SDU and the third data SDU belong to the same service.

[0561] As an example, the first data SDU and the third data SDU belong to the same session.

[0562] As an example, the first data SDU and the third data SDU belong to the same PDU session.

[0563] As an example, the second data SDU and the fourth data SDU are processed by the same protocol entity of the second protocol layer.

[0564] As an example, the first data SDU is processed by a first entity of the first protocol layer to generate the first data PDU.

[0565] As an example, the third data SDU is processed by a second entity of the first protocol layer to generate the third data PDU.

[0566] As an embodiment, the first data SDU and the third data SDU carry different IP addresses.

[0567] As an embodiment, the first data SDU and the third data SDU carry different TCP ports.

[0568] As an embodiment, the first data SDU and the third data SDU carry different TCP / IP addresses.

[0569] As an embodiment, the first data SDU and the third data SDU belong to or correspond to different QoS flows.

[0570] As an embodiment, the first data SDU and the third data SDU belong to or correspond to different QoS sub-flows.

[0571] As an embodiment, the first data SDU and the third data SDU use different header compression profiles.

[0572] As an embodiment, the first data SDU and the third data SDU are header-compressed by different header compression entities respectively.

[0573] As a sub-embodiment of this embodiment, the different header compression entities belong to the first entity and the second entity of the first protocol layer respectively.

[0574] As an embodiment, the first data SDU and the third data SDU are header-compressed through different header compression channels respectively.

[0575] As a sub-embodiment of this embodiment, the different header compression channels correspond to the first entity and the second entity of the first protocol layer respectively.

[0576] As an embodiment, the advantages of the above method include: being conducive to supporting more complex service types, especially better supporting multi-modal services, improving the header compression efficiency, and avoiding header compression context reset caused by changes in the protocol headers of data packets, such as different IP addresses carried in the headers of different data packets; when the second protocol layer is the PDCP layer, simplifying the design of the PDCP layer, and the second protocol layer can better reuse the PDCP of the NR system.

[0577] As an embodiment, the number of entities in the first protocol layer depends on the network configuration.

[0578] As a sub-embodiment of this embodiment, the network can be configured according to internal algorithms or experience.

[0579] As a sub - embodiment of this embodiment, the network can be configured according to the multi - modal characteristics of the service or QoS flow to which the first data SDU belongs.

[0580] As a sub - embodiment of this embodiment, the network can fixedly configure two first protocol layer entities.

[0581] As a sub - embodiment of this embodiment, the network can be configured according to the number of IP addresses of the service or QoS flow to which the first data SDU belongs.

[0582] As an embodiment, the number of entities of the first protocol layer is determined by the first node.

[0583] As a sub - embodiment of this embodiment, the first node indicates to the network the number of entities established by the first protocol layer.

[0584] As a sub - embodiment of this embodiment, the number of entities of the first protocol layer is for the service / QoS flow / session of the first data SDU.

[0585] As a sub - embodiment of this embodiment, the first node can be configured according to an internal algorithm or experience.

[0586] As a sub - embodiment of this embodiment, the first node can be configured according to the multi - modal characteristics of the service or QoS flow to which the first data SDU belongs.

[0587] As a sub - embodiment of this embodiment, the first node can fixedly configure two first protocol layer entities.

[0588] As a sub - embodiment of this embodiment, the first node can be configured according to the number of IP addresses of the service or QoS flow to which the first data SDU belongs.

[0589] Example 9

[0590] Embodiment 9 exemplifies a schematic diagram of the first protocol layer and the second protocol layer according to an embodiment of the present application, as shown in the appendix Figure 9 as follows.

[0591] As an embodiment, the first data SDU is the first PDU of a higher layer of the first protocol layer.

[0592] As an embodiment, the first PDU is an IP packet.

[0593] As an embodiment, the first PDU is an application - layer data packet.

[0594] As an embodiment, the first PDU is not an access - layer PDU.

[0595] As an embodiment, the first PDU is submitted to the protocol entity of the first protocol layer through the service access point of the first protocol layer.

[0596] As an embodiment, the first data SDU is the first PDU received by the first protocol layer entity from a higher layer.

[0597] As an embodiment, the third data SDU is the third PDU of a higher layer of the first protocol layer.

[0598] As an embodiment, the third PDU is an IP packet.

[0599] As an embodiment, the third PDU is an application layer data packet.

[0600] As an embodiment, the third PDU is not an access layer PDU.

[0601] As an embodiment, the third PDU is submitted to the protocol entity of the first protocol layer through the service access point of the first protocol layer.

[0602] As an embodiment, the third data SDU is the third PDU received by the first protocol layer entity from a higher layer.

[0603] As an embodiment, the interface between the first protocol layer and the second protocol layer is a radio bearer.

[0604] As an embodiment, the radio bearer is a service provided by the second protocol layer to the first protocol layer.

[0605] As an embodiment, the third data PDU is submitted to the entity of the second protocol layer, i.e., transmitted through the radio bearer.

[0606] As an embodiment, the fourth data SDU is the third data PDU received by the second protocol layer.

[0607] As an embodiment, the third data PDU is submitted to the entity of the second protocol layer, i.e., transmitted through the radio bearer.

[0608] As an embodiment, the fourth data SDU is the third data PDU received by the second protocol layer.

[0609] As an embodiment, a protocol layer exchanges signaling and / or data with other protocol layers through service access points.

[0610] As an example, an entity of a protocol layer exchanges signaling and / or data with entities of other protocol layers through service access points.

[0611] As an example, the first data SDU and the third data SDU belong to the same service.

[0612] As an example, the first data SDU and the third data SDU belong to the same session.

[0613] As an example, the first data SDU and the third data SDU belong to the same PDU session.

[0614] As an example, the first data SDU and the third data SDU are processed by the same protocol entity of the first protocol layer.

[0615] As an example, the second data SDU and the fourth data SDU are processed by different protocol entities of the second protocol layer.

[0616] As an example, the second data SDU is processed by the first protocol entity of the second protocol layer.

[0617] As an example, the fourth data SDU is processed by the second protocol entity of the second protocol layer.

[0618] As an example, the values of the fields other than the sequence number in the protocol headers of the first PDU and the third PDU are the same.

[0619] As an example, the first data SDU and the third data SDU carry different IP addresses.

[0620] As an example, the first data SDU and the third data SDU carry different TCP ports.

[0621] As an example, the first data SDU and the third data SDU carry different TCP / IP addresses.

[0622] As an example, the first data SDU and the third data SDU use different header compression profiles.

[0623] As an example, the first data SDU and the third data SDU belong to or correspond to the same QoS flow.

[0624] As an example, the first data SDU and the third data SDU belong to or correspond to the same QoS sub-flow.

[0625] As an embodiment, the first data SDU and the third data SDU are header-compressed by the same header compression entity.

[0626] As an embodiment, the first data SDU and the third data SDU are respectively header-compressed by different header compression entities.

[0627] As an embodiment, the first data SDU and the third data SDU are header-compressed through the same header compression channel.

[0628] As an embodiment, the first data SDU and the third data SDU are respectively header-compressed through different header compression channels.

[0629] As an embodiment, the advantages of the above method include: using an entity of the first protocol layer to process the same service is beneficial to taking into account different data within the same service; processing through protocol entities of different second protocol layers is beneficial to providing different transmission services for different data of the same service, such as providing different qualities, which can better meet the services with complex service requirements, and at the same time is beneficial to reducing resource consumption.

[0630] As an embodiment, the first data PDU is dynamically submitted to at least one of multiple protocol entities of the second protocol layer.

[0631] As an embodiment, the mapping relationship between the first protocol layer entity and multiple protocol entities of the second protocol layer is dynamic.

[0632] As an embodiment, the first node determines which entity of the second protocol layer the first data PDU is submitted to according to one of load, internal algorithm, indication of a lower layer, queuing delay, and network signaling.

[0633] As an embodiment, the advantages of the above method include: being more flexible, being beneficial to balancing the load, ensuring the transmission quality, and reducing the transmission delay.

[0634] As an embodiment, the number of entities in the second protocol layer depends on the network configuration.

[0635] As a sub-embodiment of this embodiment, the number of entities in the first protocol layer is for the service / QoS flow / session of the first data SDU.

[0636] As a sub-embodiment of this embodiment, the network can be configured according to an internal algorithm or experience.

[0637] As a sub-embodiment of this embodiment, the network can be configured according to the multi-modal characteristics of the service to which the first data SDU belongs.

[0638] As a sub - embodiment of this embodiment, the network may fixedly configure two second protocol layer entities.

[0639] Example 10

[0640] Embodiment 10 exemplifies a structural block diagram of a processing device in a first node according to an embodiment of the present application; as shown in the appendix Figure 10 shown. In the appendix Figure 10 shown, the processing device 1000 in the first node includes a first receiver 1001 and a first transmitter 1002.

[0641] In Embodiment 10, the first transmitter 1002 performs header compression on the first data SDU at the first protocol layer; submits the first data PDU to the second protocol layer, where the first data PDU is generated from the first data SDU that has undergone the header compression; performs encryption processing on the second data SDU at the second protocol layer, where the second data SDU is the first data PDU received by the second protocol layer; submits the second data PDU to a lower layer, where the second data PDU is generated from the second data SDU that has undergone the encryption processing;

[0642] wherein, the first protocol layer is a higher layer of the second protocol layer; the second protocol layer is a higher layer of the MAC layer; both the first protocol layer and the second protocol layer are protocol layers of the access layer; the service provided by the second protocol layer to the first protocol layer is a radio bearer.

[0643] As an embodiment, the first transmitter 1002 performs header compression on the third data SDU at the first protocol layer; submits the third data PDU to the second protocol layer, where the third data PDU is generated from the third data SDU that has undergone the header compression;

[0644] wherein, submitting the first data PDU to the second protocol layer includes: submitting the first data PDU to the first protocol entity of the second protocol layer; submitting the third data PDU to the second protocol layer includes: submitting the third data PDU to the first protocol entity of the second protocol layer; the header compression performed on the first data SDU at the first protocol layer and the header compression performed on the third data SDU at the first protocol layer use different header compression profiles.

[0645] As an embodiment, the first data SDU and the third data SDU use different IP addresses; the first data SDU and the third data SDU correspond to different QoS flows or different QoS sub - flows.

[0646] As an example, the first transmitter 1002 performs header compression on the third data SDU at the first protocol layer; and submits the third data PDU to the second protocol layer, where the third data PDU is generated from the third data SDU that has undergone the header compression.

[0647] Among them, submitting the first data PDU to the second protocol layer includes: submitting the first data PDU to the first protocol entity of the second protocol layer; submitting the third data PDU to the second protocol layer includes: submitting the third data PDU to the second protocol entity of the second protocol layer; the first data SDU and the third data SDU correspond to the same QoS flow.

[0648] As an example, the first transmitter 1002 segments the second data SDU at the second protocol layer.

[0649] Among them, the second protocol layer is the PDCP layer.

[0650] As an example, the first transmitter 1002 performs second header compression on the second data SDU at the second protocol layer, where the second header compression is based on header compression other than RoHC.

[0651] Among them, the header compression performed on the first data SDU at the first protocol layer is the first header compression based on RoHC.

[0652] As an example, the first protocol layer is the SDAP layer.

[0653] As an example, the second protocol layer is the PDCP layer.

[0654] As an example, the first protocol layer supports the mapping between QoS flows and radio bearers and supports marking QoS flow identifiers.

[0655] As an example, the second protocol layer supports sequence numbers, integrity protection, duplication, and packet discarding.

[0656] As an example, the first node is a user equipment (UE).

[0657] As an example, the first node is a user equipment (UE) that supports a 6G network.

[0658] As an example, the first node is a terminal that supports large delay differences.

[0659] As an example, the first node is a terminal that supports NTN.

[0660] As an example, the first node is an aircraft or a vessel.

[0661] As an example, the first node is a mobile phone or a vehicle-mounted terminal.

[0662] As an example, the first node is a terminal supporting MUSIM.

[0663] As an example, the first node is an Internet of Things terminal or an industrial Internet of Things terminal.

[0664] As an example, the first node is a device supporting low-latency and high-reliability transmission.

[0665] As an example, the first receiver 1001 includes at least one of the antenna 452, the receiver 454, the receiving processor 456, the multi-antenna receiving processor 458, the controller / processor 459, the memory 460, or the data source 467 in Embodiment 4.

[0666] As an example, the first transmitter 1002 includes at least one of the antenna 452, the transmitter 454, the transmitting processor 468, the multi-antenna transmitting processor 457, the controller / processor 459, the memory 460, or the data source 467 in Embodiment 4.

[0667] Those of ordinary skill in the art can understand that all or part of the steps in the above methods can be completed by instructing relevant hardware through a program, and the program can be stored in a computer-readable storage medium, such as a read-only memory, a hard disk, or an optical disc, etc. Optionally, all or part of the steps of the above embodiments can also be implemented using one or more integrated circuits. Correspondingly, each module unit in the above embodiments can be implemented in a hardware form or in the form of a software function module. This application is not limited to any specific form of the combination of software and hardware. The user equipment, terminal, and UE in this application include, but are not limited to, drones, communication modules on drones, remote control airplanes, aircraft, small airplanes, mobile phones, tablet computers, notebooks, vehicle-mounted communication devices, wireless sensors, network cards, Internet of Things terminals, RFID terminals, NB-IoT terminals, MTC (Machine Type Communication) terminals, eMTC (enhanced MTC) terminals, data cards, network cards, vehicle-mounted communication devices, low-cost mobile phones, low-cost tablet computers, satellite communication devices, vessel communication devices, NTN user equipment and other wireless communication devices. The base station or system equipment in this application includes, but is not limited to, macrocell base stations, microcell base stations, home base stations, relay base stations, gNB (NR Node B) NR Node B, TRP (Transmitter Receiver Point), NTN base stations, satellite devices, flight platform devices and other wireless communication devices.

[0668] The present invention can be implemented in other specific forms without departing from its core or essential characteristics. Therefore, the presently disclosed embodiments should in any event be considered as illustrative rather than restrictive. The scope of the invention is determined by the appended claims rather than the foregoing description, and all changes within the meaning and range of their equivalents are considered to be included therein.

Claims

1. A first node used for header compression in wireless communication, wherein, Comprising: A first transmitter that performs header compression on a first data SDU at a first protocol layer; Submits a first data PDU to a second protocol layer, wherein the first data PDU is generated from the first data SDU that has undergone the header compression; Performs encryption processing on a second data SDU at the second protocol layer, wherein the second data SDU is the first data PDU received by the second protocol layer; submits a second data PDU to a lower layer, wherein the second data PDU is generated from the second data SDU that has undergone the encryption processing; Wherein the first protocol layer is a higher layer of the second protocol layer; the second protocol layer is a higher layer of the MAC layer; both the first protocol layer and the second protocol layer are protocol layers of the access layer; the service provided by the second protocol layer to the first protocol layer is a radio bearer.

2. The first node according to claim 1, wherein Comprising: The first transmitter that performs header compression on a third data SDU at a first protocol layer; Submits a third data PDU to the second protocol layer, wherein the third data PDU is generated from the third data SDU that has undergone the header compression; Wherein submitting the first data PDU to the second protocol layer includes: submitting the first data PDU to a first protocol entity of the second protocol layer; submitting the third data PDU to the second protocol layer includes: submitting the third data PDU to the first protocol entity of the second protocol layer; the header compression performed on the first data SDU at the first protocol layer and the header compression performed on the third data SDU at the first protocol layer use different header compression profiles.

3. The first node according to claim 2, wherein The first data SDU and the third data SDU use different IP addresses; the first data SDU and the third data SDU correspond to different QoS flows or different QoS sub-flows.

4. The first node according to claim 1, wherein Comprising: The first transmitter that performs header compression on a third data SDU at a first protocol layer; Submits a third data PDU to the second protocol layer, wherein the third data PDU is generated from the third data SDU that has undergone the header compression; Wherein submitting the first data PDU to the second protocol layer includes: submitting the first data PDU to a first protocol entity of the second protocol layer; submitting the third data PDU to the second protocol layer includes: submitting the third data PDU to a second protocol entity of the second protocol layer; the first data SDU and the third data SDU correspond to the same QoS flow.

5. The first node according to any one of claims 1 to 4, characterized in that Comprising: The first transmitter that segments the second data SDU at the second protocol layer; Wherein the second protocol layer is the PDCP layer.

6. The first node according to any one of claims 1 to 5, characterized in that, Comprising: The first transmitter that performs a second header compression on the second data SDU at the second protocol layer, wherein the second header compression is a header compression other than based on RoHC; Wherein the header compression performed on the first data SDU at the first protocol layer is a first header compression based on RoHC.

7. The first node according to any one of claims 1 to 6, wherein The first protocol layer is the SDAP layer.

8. The first node according to any one of claims 1 to 7, characterized in that The second protocol layer is the PDCP layer.

9. The first node according to any one of claims 1 to 8, characterized in that The first protocol layer supports the mapping between QoS flows and radio bearers and supports marking QoS flow identifiers.

10. The first node according to any one of claims 1 to 9, characterized in that The second protocol layer supports sequence numbers, integrity protection, duplication, and packet discard.

11. A method in a first node used for header compression in wireless communication, wherein, including: Performing header compression on the first data SDU at the first protocol layer; Submitting the first data PDU to the second protocol layer, where the first data PDU is generated from the first data SDU that has undergone the header compression; Performing encryption processing on the second data SDU at the second protocol layer, where the second data SDU is the first data PDU received by the second protocol layer; submitting the second data PDU to a lower layer, where the second data PDU is generated from the second data SDU that has undergone the encryption processing; wherein the first protocol layer is a higher layer of the second protocol layer; the second protocol layer is a higher layer of the MAC layer; both the first protocol layer and the second protocol layer are protocol layers of the access layer; the service provided by the second protocol layer to the first protocol layer is a radio bearer.

Images