Reflective Quality of Service for Encapsulating Security Payload Packets

Abstract

In a wireless network, a user equipment (UE) may support reflective quality of service (QoS) in which the QoS applied to an uplink packet is implicitly derived from a downlink packet. For example, when the UE receives a downlink packet including a reflective QoS (RQoS) indicator and a QoS flow identifier (QFI), the UE may apply the same QoS associated with the downlink packet to an uplink packet having one or more attributes that match the downlink packet. However, for a received downlink encapsulating security payload (ESP) packet including an RQoS indicator and a QFI, the modem cannot determine the uplink security parameter index (SPI) and downlink SPI pairing required to implement RQoS because only upper layers know the uplink / downlink SPI pairing. Therefore, some aspects described herein enable the modem to learn the uplink / downlink SPI pairing for ESP packets, thereby implementing RQoS for ESP packets.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to U.S. non-provisional patent application No. 17 / 451,976, filed on October 22, 2021, entitled “REFLECTIVE QUALITY OF SERVICE FOR ENCAPSULATING SECURITY PAYLOAD PACKETS,” which is hereby expressly incorporated herein by reference. Technical Field

[0003] Aspects of the present disclosure relate generally to wireless communications, and techniques and apparatus associated with Reflective Quality of Service (RQoS) for Encapsulated Security Payload (ESP) packets. Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasting. Typical wireless communication systems may utilize multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).

[0005] A wireless network may include one or more base stations that support communications for a user equipment (UE) or multiple UEs. A UE may communicate with a base station via downlink communications and uplink communications. A "downlink" (or "DL") refers to a communication link from a base station to a UE, and an "uplink" (or "UL") refers to a communication link from a UE to a base station.

[0006] The above-mentioned multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate at a city, country, region and / or global level. 5G (which may be referred to as New Radio (NR)) is an enhancement set to the LTE mobile standard promulgated by 3GPP. 5G is designed to better support mobile broadband Internet access by improving spectrum efficiency, reducing costs, improving services, utilizing new spectrum, and using orthogonal frequency division multiplexing (OFDM) (CP-OFDM) with cyclic prefix (CP) on the downlink, using CP-OFDM and / or single carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink to better integrate with other open standards, and supporting beamforming, multiple input multiple output (MIMO) antenna technology and carrier aggregation. As the demand for mobile broadband access continues to increase, further improvements to 4G, 5G and other radio access technologies remain useful. Summary of the invention

[0007] In a wireless network, a user equipment (UE) may support reflective quality of service (QoS), in which the QoS applied to an uplink packet is implicitly derived from a downlink packet. For example, when the UE receives a downlink packet including a reflective QoS (RQoS) indicator and a QoS flow identifier (QFI), the UE may apply the same QoS associated with the downlink packet to the uplink packet having one or more attributes that match the downlink packet (e.g., an uplink source Internet Protocol (IP) address that matches the downlink destination IP address, an uplink destination IP address that matches the downlink source IP address, an uplink source port number that matches the downlink destination port number, an uplink destination port number that matches the downlink source port number, and / or an uplink protocol that matches the downlink protocol). However, for a received downlink Encapsulating Security Payload (ESP) packet including an RQoS indicator and a QFI, the modem cannot determine the uplink security parameter index (SPI) and downlink SPI pairing required to implement RQoS because only the upper layers (e.g., the IP security (IPsec) layer) know the uplink / downlink SPI pairing. For example, the uplink ESP packet is typically generated by the IPsec layer (above the IP layer) after a security association is established (e.g., in an application processor). The security association may be separate for uplink packets and downlink packets, whereby different SPI values ​​may be used for uplink ESP packets and downlink ESP packets for bidirectional data flows. Therefore, because there is no predefined correlation between the uplink SPI value and the downlink SPI value, only the upper layers know explicitly the uplink SPI and downlink SPI pairing. In such a case, because the modem does not have the uplink SPI parameters required to create or otherwise derive a non-access stratum (NAS) RQoS uplink packet filter, the UE may not be able to utilize RQoS to determine which QoS to apply to the uplink ESP packet without specific signaling.

[0008] Some aspects described herein relate to techniques and apparatuses that enable a modem to learn an uplink / downlink SPI pairing for an ESP packet and thereby implement RQoS for the ESP packet. For example, in some aspects, a modem may monitor ESP packets on a protocol data unit (PDU) session with NAS RQoS enabled, and may store a record for each ESP packet associated with a unique attribute combination (e.g., a unique 3-tuple including a local IP address, a remote IP address, and an uplink SPI value). The record may also include a downlink SPI field and a flag or indication that the uplink SPI is not mapped to a downlink SPI value. Thus, when a modem receives a downlink ESP packet and there is only one stored record that satisfies a set of mapping conditions for the downlink ESP packet (e.g., there is one record that includes a local IP address and a remote IP address that match the local IP address and the remote IP address included in the downlink packet and / or a flag indicating that the uplink SPI is not mapped to a downlink SPI value, etc.), the modem may update the one matching record to include the downlink SPI value included in the downlink ESP packet, and change the value of the flag to indicate that the uplink SPI is mapped to the downlink SPI value. Additionally or alternatively, in the case where the modem and the upper layer generating the uplink ESP packet are able to exchange control information, the modem can query the upper layer to request an uplink SPI paired with an unmapped downlink SPI included in the header of the downlink ESP packet. In this way, the UE can create an uplink packet filter to indicate that uplink ESP packets with the same local IP address, remote IP address, and uplink SPI are associated with a QFI included in a downlink ESP packet, and the downlink ESP packet is associated with a downlink SPI paired with the uplink SPI. In this way, by learning the uplink and downlink SPI pairings, the UE can implement RQoS for ESP packets.

[0009] Some aspects described herein relate to a UE for wireless communication. The UE may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to store a record including a first attribute set associated with an uplink ESP packet sent by an upper layer of the UE, wherein the first attribute set includes an uplink SPI included in a header of the uplink ESP packet and a flag indicating that the uplink SPI is not mapped to a downlink SPI. The one or more processors may be configured to receive a downlink ESP packet associated with a second attribute set, wherein the second attribute set includes a downlink SPI included in a header of the downlink ESP packet. The one or more processors may be configured to map the uplink SPI associated with the uplink ESP packet and the downlink SPI associated with the downlink ESP packet based at least in part on the record including the uplink SPI satisfying one or more conditions.

[0010] Some aspects described herein relate to a UE for wireless communication. The UE may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive a downlink ESP packet, wherein the downlink ESP packet is associated with a local IP address, a remote IP address, and a downlink SPI that is not mapped to an uplink SPI. The one or more processors may be configured to provide a query including the local IP address, the remote IP address, and the downlink SPI to an upper layer. The one or more processors may be configured to receive a reply to the query from the upper layer, wherein the reply indicates an uplink SPI paired with the local IP address, the remote IP address, and the downlink SPI associated with the downlink ESP packet. The one or more processors may be configured to map the downlink SPI associated with the downlink ESP packet with the uplink SPI indicated in the reply to the query.

[0011] Some aspects described herein relate to a UE for wireless communication. The UE may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to determine that a DRB mapping rule associated with a QoS flow identifier (QFI) has changed based at least in part on receiving a configuration message or deriving a new QoS flow to data radio bearer (DRB) mapping rule. The one or more processors may be configured to avoid sending an end-marker service data adaptation protocol (SDAP) control PDU on a current DRB associated with the QFI based at least in part on determining that the QFI is not associated with an uplink packet filter.

[0012] Some aspects described herein relate to a method of wireless communication performed by a UE. The method may include storing a record including a first set of attributes associated with an uplink ESP packet sent by an upper layer of the UE, wherein the first set of attributes includes an uplink SPI included in a header of the uplink ESP packet and a flag indicating that the uplink SPI is not mapped to a downlink SPI. The method may include receiving a downlink ESP packet associated with a second set of attributes, wherein the second set of attributes includes a downlink SPI included in a header of the downlink ESP packet. The method may include mapping the uplink SPI associated with the uplink ESP packet and the downlink SPI associated with the downlink ESP packet based at least in part on the record including the uplink SPI satisfying one or more conditions.

[0013] Some aspects described herein relate to a method of wireless communication performed by a UE. The method may include receiving a downlink ESP packet, wherein the downlink ESP packet is associated with a local IP address, a remote IP address, and a downlink SPI that is not mapped to an uplink SPI. The method may include providing a query to an upper layer including the local IP address, the remote IP address, and the downlink SPI. The method may include receiving a reply to the query from the upper layer, wherein the reply indicates an uplink SPI paired with the local IP address, the remote IP address, and the downlink SPI associated with the downlink ESP packet. The method may include mapping the downlink SPI associated with the downlink ESP packet with the uplink SPI indicated in the reply to the query.

[0014] Some aspects described herein relate to a method of wireless communication performed by a UE. The method may include determining that a DRB mapping rule associated with a QFI has changed based at least in part on receiving a configuration message or deriving a new QoS flow to DRB mapping rule. The method may include avoiding sending an end marker SDAP control PDU on a current DRB associated with the QFI based at least in part on determining that the QFI is not associated with an uplink packet filter.

[0015] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a UE. The set of instructions, when executed by one or more processors of the UE, may cause the UE to: store a record including a first set of attributes associated with an uplink ESP packet sent by an upper layer of the UE, wherein the first set of attributes includes an uplink SPI included in a header of the uplink ESP packet and a flag indicating that the uplink SPI is not mapped to a downlink SPI. The set of instructions, when executed by one or more processors of the UE, may cause the UE to: receive a downlink ESP packet associated with a second set of attributes, wherein the second set of attributes includes a downlink SPI included in a header of the downlink ESP packet. The set of instructions, when executed by one or more processors of the UE, may cause the UE to: map the uplink SPI associated with the uplink ESP packet and the downlink SPI associated with the downlink ESP packet based at least in part on the record including the uplink SPI satisfying one or more conditions.

[0016] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication. The instruction set, when executed by one or more processors of the UE, may cause the UE to: receive a downlink ESP packet, wherein the downlink ESP packet is associated with a local IP address, a remote IP address, and a downlink SPI that is not mapped to an uplink SPI. The instruction set, when executed by one or more processors of the UE, may cause the UE to: provide a query including the local IP address, the remote IP address, and the downlink SPI to an upper layer. The instruction set, when executed by one or more processors of the UE, may cause the UE to: receive a reply to the query from the upper layer, wherein the reply indicates an uplink SPI paired with the local IP address, the remote IP address, and the downlink SPI associated with the downlink ESP packet. The instruction set, when executed by one or more processors of the UE, may cause the UE to: map the downlink SPI associated with the downlink ESP packet with the uplink SPI indicated in the reply to the query.

[0017] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication. The instruction set, when executed by one or more processors of the UE, may cause the UE to: determine that the DRB mapping rules associated with the QFI have changed based at least in part on receiving a configuration message or deriving a new QoS flow to DRB mapping rule. The instruction set, when executed by one or more processors of the UE, may cause the UE to: avoid sending an end marker SDAP control PDU on a current DRB associated with the QFI based at least in part on determining that the QFI is not associated with an uplink packet filter.

[0018] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include: a unit for storing a record including a first set of attributes associated with an uplink ESP packet sent by an upper layer of the apparatus, wherein the first set of attributes includes an uplink SPI included in a header of the uplink ESP packet and a flag indicating that the uplink SPI is not mapped to a downlink SPI. The apparatus may include: a unit for receiving a downlink ESP packet associated with a second set of attributes, wherein the second set of attributes includes a downlink SPI included in a header of the downlink ESP packet. The apparatus may include: a unit for mapping the uplink SPI associated with the uplink ESP packet and the downlink SPI associated with the downlink ESP packet based at least in part on the record including the uplink SPI satisfying one or more conditions.

[0019] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include: a unit for receiving a downlink ESP packet, wherein the downlink ESP packet is associated with a local IP address, a remote IP address, and a downlink SPI that is not mapped to an uplink SPI. The apparatus may include: a unit for providing a query including the local IP address, the remote IP address, and the downlink SPI. The apparatus may include: a unit for receiving a reply to the query, wherein the reply indicates an uplink SPI paired with the local IP address, the remote IP address, and the downlink SPI associated with the downlink ESP packet. The apparatus may include: a unit for mapping the downlink SPI associated with the downlink ESP packet with the uplink SPI indicated in the reply to the query.

[0020] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include: means for determining that a DRB mapping rule associated with a QFI has changed based at least in part on receiving a configuration message or deriving a new QoS flow to DRB mapping rule. The apparatus may include: means for avoiding sending an end marker SDAP control PDU on a current DRB associated with the QFI based at least in part on determining that the QFI is not associated with an uplink packet filter.

[0021] Aspects generally include methods, apparatuses, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, wireless communication devices, and / or processing systems as fully described with reference to and as illustrated by the drawings and description.

[0022] The features and technical advantages of the examples according to the present disclosure have been outlined quite extensively above so that the following detailed description may be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples may be easily used as the basis for modifying or designing other structures for the same purpose of achieving the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. When considered in conjunction with the accompanying drawings, the features of the concepts disclosed herein (both their organization and methods of operation) and the associated advantages will be better understood from the description below. Each of the figures in the accompanying drawings is provided for the purpose of illustration and description and not as a limitation on the limits of the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] Figure 1 is a schematic diagram illustrating an example of a wireless network.

[0024] Figure 2 is a schematic diagram showing an example of communication between a base station and a user equipment (UE) in a wireless network.

[0025] Figure 3 is a diagram illustrating an example of a Quality of Service (QoS) architecture that can be used in a wireless network.

[0026] Figure 4A-4B is a diagram illustrating an example associated with remapping a QoS flow based on a Service Data Adaptation Protocol (SDAP) end marker.

[0027] Figure 5A-5B is a diagram illustrating an example of non-access stratum (NAS) reflective QoS (RQoS).

[0028] Figure 6 is a diagram illustrating an example of access stratum (AS) RQoS.

[0029] Figure 7A-7B is a diagram showing an example in which a UE applies NAS RQoS technology to derive an uplink packet filter based on information in a downlink packet.

[0030] Figure 8-Figure 9 is a diagram illustrating an example associated with RQoS for Encapsulating Security Payload (ESP) packets.

[0031] Figure 10-12 is a flow chart of an example method of wireless communication.

[0032] Fig.13 is a schematic diagram of an example apparatus for wireless communications.

[0033] Fig.14 is a schematic diagram illustrating an example of a hardware implementation for an apparatus using a processing system. DETAILED DESCRIPTION

[0034] The detailed description set forth below in conjunction with the accompanying drawings is intended as a description of various configurations and is not intended to represent a configuration in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts may be implemented without these specific details. In some instances, in order to avoid obscuring such concepts, known structures and components are shown in block diagram form.

[0035] Several aspects of telecommunication systems will now be described with reference to various devices and methods. These devices and methods will be described in the following detailed description by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements") and illustrated in the accompanying drawings. These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0036] For example, an element or any part of an element or any combination of elements can be implemented with a "processing system" including one or more processors. Examples of processors include microprocessors, microcontrollers, digital signal processors (DSPs), field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform various functions described throughout the present disclosure. One or more processors in a processing system can execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other terms, software should be widely interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, processes, functions, etc.

[0037] Therefore, in one or more exemplary embodiments, the described functions can be implemented by hardware, software, firmware or any combination thereof. If implemented by software, the function can be stored on a computer-readable medium as one or more instructions or codes or encoded as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media. Storage media can be any available media that can be accessed by a computer. By way of example and not limitation, such computer-readable media can include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), compact disk ROM (CD-ROM), or other optical disk storage, disk storage, or other magnetic storage devices, or a combination of computer-readable media of the above type, or can be used to store any other medium of computer executable code in the form of instructions or data structures that can be accessed by a computer.

[0038] Although aspects may be described herein using terminology generally associated with 5G or New Radio (NR) radio access technologies (RATs), aspects of the present disclosure may be applied to other RATs, such as 3G RATs, 4G RATs, and / or post-5G RATs (e.g., 6G).

[0039] Figure 1 1 is a schematic diagram showing a wireless network 100 in which aspects of the present disclosure may be practiced. The wireless network 100 may be a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, etc., or may include elements of a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, etc. The wireless network 100 may include one or more base stations 110 (shown as BS110a, BS110b, BS110c, and BS110d), a user equipment (UE) 120 or multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), and / or other network entities. The base station 110 is an entity that communicates with the UE 120. The base station 110 (sometimes referred to as a BS) may include, for example, an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, and / or a transmit receive point (TRP). Each base station 110 may provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP), the term "cell" may refer to the coverage area of ​​a base station 110 and / or a base station subsystem serving the coverage area, depending on the context in which the term is used.

[0040] The base station 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by a UE 120 with a service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by a UE 120 with a service subscription. A femto cell may cover a relatively small geographic area (e.g., a residence) and may allow restricted access by a UE 120 that has an association with the femto cell (e.g., a UE 120 in a closed subscriber group (CSG)). A base station 110 for a macro cell may be referred to as a macro base station. A base station 110 for a pico cell may be referred to as a pico base station. A base station 110 for a femto cell may be referred to as a femto base station or an intra-home base station. In Figure 1 In the example shown, BS 110a may be a macro base station for macro cell 102a, BS 110b may be a pico base station for pico cell 102b, and BS 110c may be a femto base station for femto cell 102c. A base station may support one or more (eg, three) cells.

[0041] In some examples, the cells may not necessarily be stationary, and the geographic area of ​​the cells may move according to the location of the mobile base station 110 (e.g., a mobile base station). In some examples, the base stations 110 may be interconnected with each other and / or to one or more other base stations 110 or network nodes (not shown) in the wireless network 100 through various types of backhaul interfaces (such as direct physical connections or virtual networks) using any suitable transport network.

[0042] The wireless network 100 may include one or more relay stations. A relay station is an entity that can receive data transmissions from an upstream station (e.g., a base station 110 or a UE 120) and send data transmissions to a downstream station (e.g., a UE 120 or a base station 110). A relay station may be a UE 120 that can relay transmissions for other UEs 120. Figure 1 In the example shown, BS 110d (eg, a relay base station) may communicate with BS 110a (eg, a macro base station) and UE 120d to facilitate communications between BS 110a and UE 120d. Base station 110 that relays communications may be referred to as a relay station, relay base station, relay, or the like.

[0043] The wireless network 100 may be a heterogeneous network including different types of base stations 110, such as macro base stations, pico base stations, femto base stations, relay base stations, etc. These different types of base stations 110 may have different transmit power levels, different coverage areas, and / or different impacts on interference in the wireless network 100. For example, a macro base station may have a high transmit power level (e.g., 5 to 40 watts), while a pico base station, a femto base station, and a relay base station may have a lower transmit power level (e.g., 0.1 to 2 watts).

[0044] A network controller 130 may be coupled to or in communication with a set of base stations 110 and may provide coordination and control for the base stations 110. The network controller 130 may communicate with the base stations 110 via backhaul communication links. The base stations 110 may communicate with each other directly or indirectly via wireless or wired backhaul communication links.

[0045] UE 120 can be dispersed throughout the wireless network 100, and each UE 120 can be stationary or mobile. UE 120 can include, for example, access terminals, terminals, mobile stations, and / or user units. UE 120 can be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or a smart bracelet)), an entertainment device (e.g., a music device, a video device, and / or a satellite radio unit), a vehicle component or sensor, a smart meter / sensor, an industrial manufacturing equipment, a global positioning system device, and / or any other suitable device configured to communicate via a wireless medium.

[0046] Some UEs 120 may be considered as machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UEs. MTC UEs and / or eMTC UEs may include, for example, robots, drones, remote devices, sensors, meters, monitors, and / or location tags, which may communicate with a base station, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered as Internet of Things (IoT) devices, and / or may be implemented as NB-IoT (narrowband IoT) devices. Some UEs 120 may be considered as user premises equipment. UE 120 may be included in a housing that houses components of UE 120 (such as processor components and / or memory components). In some examples, the processor component and the memory component may be coupled together. For example, a processor component (e.g., one or more processors) and a memory component (e.g., a memory) may be operationally coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0047] In general, any number of wireless networks 100 may be deployed in a given geographic area. Each wireless network 100 may support a specific RAT and may operate on one or more frequencies. RAT may be referred to as a radio technology, an air interface, etc. A frequency may be referred to as a carrier, a frequency channel, etc. Each frequency may support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, a 5G RAT network may be deployed.

[0048] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) can communicate directly using one or more sidelink channels (e.g., without using base station 110 as an intermediary for communicating with each other). For example, UE 120 can communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocol (e.g., which may include vehicle-to-vehicle (V2V) protocol, vehicle-to-infrastructure (V2I) protocol, or vehicle-to-pedestrian (V2P) protocol), and / or mesh network. In such examples, UE 120 can perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by base station 110.

[0049] The devices of the wireless network 100 can communicate using an electromagnetic spectrum, which can be subdivided into various categories, bands, channels, etc. by frequency or wavelength. For example, the devices of the wireless network 100 can communicate using one or more operating bands. In 5G, two initial operating bands have been identified as frequency range names FR1 (410MHz-7.125GHz) and FR2 (24.25GHz-52.6GHz). It should be understood that although a portion of FR1 is greater than 6GHz, FR1 is generally (interchangeably) referred to as the "Sub-6 GHz" band in various documents and articles. Similar naming issues sometimes occur with respect to FR2, although unlike the extremely high frequency (EHF) band (30GHz-300GHz) identified as the "millimeter wave" band by the International Telecommunication Union (ITU), FR2 is generally (interchangeably) referred to as the "millimeter wave" band in literature and articles.

[0050] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G research has identified the operating bands for these mid-band frequencies as frequency range names FR3 (7.125GHz-24.25GHz). The frequency bands falling into FR3 can inherit FR1 characteristics and / or FR2 characteristics, and therefore the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G operations beyond 52.6GHz. For example, three higher operating bands have been identified as frequency range names FR4a or FR4-1 (52.6GHz-71GHz), FR4 (52.6GHz-114.25GHz) and FR5 (114.25GHz-300GHz). Each of these higher frequency bands falls within the EHF band.

[0051] In view of the above examples, unless otherwise expressly stated, it should be understood that the term "sub-6 GHz" or the like (if used herein) can broadly represent frequencies that can be less than 6 GHz, frequencies that can be within FR1, or can include mid-band frequencies. In addition, unless otherwise expressly stated, it should be understood that the term "millimeter wave" or similar terms (if used herein) can broadly represent frequencies that can include mid-band frequencies, frequencies that can be within FR2, FR4, FR4-a or FR4-1 and / or FR5, or frequencies that can be within the EHF band. It is expected that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) can be modified, and the techniques described herein can be applicable to those modified frequency ranges.

[0052] In some aspects, UE 120 may include a communications manager 140. As described in more detail elsewhere herein, communications manager 140 may: store a record including a first set of attributes associated with an uplink Encapsulating Security Payload (ESP) packet sent by upper layers of UE 120, wherein the first set of attributes includes an uplink Security Parameter Index (SPI) included in a header of the uplink ESP packet and a flag indicating that the uplink SPI is not mapped to a downlink SPI; receive a downlink ESP packet associated with a second set of attributes, wherein the second set of attributes includes a downlink SPI included in a header of the downlink ESP packet; and map an uplink SPI associated with the uplink ESP packet and a downlink SPI associated with the downlink ESP packet based at least in part on the record including the uplink SPI satisfying one or more conditions.

[0053] Additionally or alternatively, in some aspects, and as described in more detail elsewhere herein, the communications manager 140 may: receive a downlink ESP packet, wherein the downlink ESP packet is associated with a local Internet Protocol (IP) address, a remote IP address, and a downlink SPI that is not mapped to an uplink SPI; provide a query to an upper layer that includes the local IP address, the remote IP address, and the downlink SPI; receive a reply to the query from the upper layer, wherein the reply indicates an uplink SPI paired with the local IP address, the remote IP address, and the downlink SPI associated with the downlink ESP packet; and map the downlink SPI associated with the downlink ESP packet with the uplink SPI indicated in the reply to the query.

[0054] Additionally or alternatively, in some aspects, and as described in greater detail elsewhere herein, the communications manager 140 may: determine that a DRB mapping rule associated with a QoS flow identifier (QFI) has changed based at least in part on receiving a configuration message or deriving a new QoS flow to data radio bearer (DRB) mapping rule; and avoid sending an end marker service data adaptation protocol (SDAP) control PDU on a current DRB associated with the QFI based at least in part on determining that the QFI is not associated with an uplink packet filter. Additionally or alternatively, the communications manager 140 may perform one or more other operations described herein.

[0055] As noted above, Figure 1 is provided as an example. Other examples may differ from those described above. Figure 1 Examples described.

[0056] Figure 22 is a schematic diagram showing an example 200 of base station 110 communicating with UE 120 in wireless network 100 according to the present disclosure. Base station 110 may be equipped with a set of antennas 234a to 234t, such as T antennas (T≥1). UE 120 may be equipped with a set of antennas 252a to 252r, such as R antennas (R≥1).

[0057] At the base station 110, the transmit processor 220 may receive data intended for the UE 120 (or a set of UEs 120) from the data source 212. The transmit processor 220 may select one or more modulation and coding schemes (MCS) for the UE 120 based at least in part on one or more channel quality indicators (CQIs) received from the UE 120. The base station 110 may process (e.g., encode and modulate) the data for the UE 120 based at least in part on the MCS selected for the UE 120, and may provide data symbols for the UE 120. The transmit processor 220 may process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper layer signaling), and provide overhead symbols and control symbols. The transmit processor 220 may generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signals (PSS) and secondary synchronization signals (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, if applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems), shown as modems 232a to 232t. For example, each output symbol stream may be provided to a modulator component (shown as MOD) of the modem 232. Each modem 232 may process a corresponding output symbol stream (e.g., for OFDM) using a corresponding modulator component to obtain an output sample stream. Each modem 232 may also process (e.g., convert to analog, amplify, filter, and / or upconvert) the output sample stream using a corresponding modulator component to obtain a downlink signal. The modems 232a to 232t may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas) (shown as antennas 234a to 234t).

[0058] At the UE 120, a set of antennas 252 (shown as antennas 252a to 252r) may receive downlink signals from the base station 110 and / or other base stations 110, and may provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems) (shown as modems 254a to 254r). For example, each received signal may be provided to a demodulator component (shown as DEMOD) of the modem 254. Each modem 254 may use a corresponding demodulator component to condition (e.g., filter, amplify, downconvert, and / or digitize) the received signal to obtain input samples. Each modem 254 may further process the input samples (e.g., for OFDM) using the demodulator component to obtain received symbols. The MIMO detector 256 may obtain received symbols from the modem 254, may perform MIMO detection on the received symbols (if applicable), and may provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) detected symbols, may provide decoded data for the UE 120 to a data sink 260, and may provide decoded control information and system information to a controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. A channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and / or a CQI parameter, among other things. In some examples, one or more components of the UE 120 may be included in a housing 284.

[0059] The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 may include, for example, one or more devices in a core network. The network controller 130 may communicate with the base station 110 via the communication unit 294.

[0060] One or more antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include or be included in one or more antenna panels, one or more antenna groups, one or more antenna element sets, and / or one or more antenna arrays, etc. Antenna panels, antenna groups, antenna element sets, and / or antenna arrays may include one or more antenna elements (in a single housing or multiple housings), coplanar antenna element sets, non-coplanar antenna element sets, and / or may be coupled to one or more transmit components and / or receive components (such as, Figure 2 One or more antenna elements of one or more components in.

[0061] On the uplink, at the UE 120, a transmit processor 264 may receive and process data from a data source 262 and control information from a controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI). The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be precoded by a TX MIMO processor 266 (if applicable), further processed by a modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to the base station 110. In some examples, the modem 254 of the UE 120 may include a modulator and a demodulator. In some examples, the UE 120 includes a transceiver. The transceiver may include any combination of an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, and / or a TX MIMO processor 266. The transceiver may be used by a processor (eg, controller / processor 280) and memory 282 to perform aspects of any of the methods described herein.

[0062] At the base station 110, uplink signals from the UE 120 and / or other UEs may be received by the antenna 234, processed by the modem 232 (e.g., a demodulator component of the modem 232, shown as DEMOD), detected by the MIMO detector 236 (if applicable), and further processed by the receive processor 238 to obtain decoded data and control information sent by the UE 120. The receive processor 238 may provide the decoded data to the data sink 239 and the decoded control information to the controller / processor 240. The base station 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The base station 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink and / or uplink communications. In some examples, the modem 232 of the base station 110 may include a modulator and a demodulator. In some examples, the base station 110 includes a transceiver. The transceiver may include any combination of antenna 234, modem 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to perform aspects of any of the methods described herein.

[0063] The controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2Any other components of the controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or the like may perform one or more techniques associated with reflective quality of service (RQoS) for encapsulated security payload (ESP) packets as described in more detail elsewhere herein. Figure 2 Any other component in may perform or direct e.g. Fig.10 Method 1000, Fig.11 Method 1100, Fig.12 Operations of method 1200 and / or other methods as described herein. Memory 242 and memory 282 may store data and program codes for base station 110 and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, the one or more instructions, when executed by one or more processors of base station 110 and / or UE 120 (e.g., directly, or after compilation, conversion, and / or interpretation), may cause the one or more processors, UE 120, and / or base station 110 to perform or direct, for example Fig.10 Method 1000, Fig.11 Method 1100, Fig.12 Method 1200 and / or other methods as described herein. In some examples, executing instructions may include: running instructions, converting instructions, compiling instructions, and / or interpreting instructions, etc.

[0064] In some aspects, the UE 120 includes: means for storing a record including a first set of attributes associated with an uplink ESP packet sent by an upper layer of the UE 120, wherein the first set of attributes includes an uplink security parameter index (SPI) included in a header of the uplink ESP packet and a flag indicating that the uplink SPI is not mapped to the downlink SPI; means for receiving a downlink ESP packet associated with a second set of attributes, wherein the second set of attributes includes the downlink SPI included in a header of the downlink ESP packet; and / or means for mapping the uplink SPI associated with the uplink ESP packet and the downlink SPI associated with the downlink ESP packet based at least in part on the record including the uplink SPI satisfying one or more conditions. The means for the UE 120 to perform the operations described herein may include, for example, one or more of the communication manager 140, the antenna 252, the modem 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, the TX MIMO processor 266, the controller / processor 280, or the memory 282.

[0065] Additionally or alternatively, in some aspects, the UE 120 includes: means for receiving a downlink ESP packet, wherein the downlink ESP packet is associated with a local IP address, a remote IP address, and a downlink SPI that is not mapped to an uplink SPI; means for providing a query to an upper layer including the local IP address, the remote IP address, and the downlink SPI; means for receiving a reply to the query from the upper layer, wherein the reply indicates an uplink SPI paired with the local IP address, the remote IP address, and the downlink SPI associated with the downlink ESP packet; and / or means for mapping the downlink SPI associated with the downlink ESP packet with the uplink SPI indicated in the reply to the query. Means for the UE 120 to perform operations described herein may include, for example, one or more of the communications manager 140, the antenna 252, the modem 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, the TX MIMO processor 266, the controller / processor 280, or the memory 282.

[0066] Additionally or alternatively, in some aspects, UE 120 includes: a unit for determining that a DRB mapping rule associated with a QFI has changed based at least in part on receiving a configuration message or deriving a new QoS flow to DRB mapping rule; and / or a unit for avoiding sending an end marker SDAP control PDU on a current DRB associated with the QFI based at least in part on determining that the QFI is not associated with an uplink packet filter. The unit for UE 120 to perform the operations described herein may include, for example, one or more of the communication manager 140, the antenna 252, the modem 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, the TX MIMO processor 266, the controller / processor 280, or the memory 282.

[0067] Although Figure 2 The blocks in the 200 and 210 are shown as distinct components, but the functionality described above with respect to these blocks may be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functionality described with respect to the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be performed by or under the control of the controller / processor 280.

[0068] As pointed out above, Figure 2 is provided as an example. Other examples may differ from those described above. Figure 2 Examples described.

[0069] Figure 33 is a schematic diagram illustrating an example 300 of a quality of service (QoS) architecture that can be used in a wireless network (e.g., a 5G network). For example, as described herein, different communications can be associated with different QoS requirements, such as latency requirements, delay requirements, jitter requirements, block error rate (BLER) requirements, and / or packet error rate requirements, etc. For example, voice communications may have more stringent QoS requirements than data communications, or ultra-reliable low-latency communication (URLLC) services may have more stringent QoS requirements than enhanced mobile broadband (eMBB) services.

[0070] like Figure 3 As shown, the QoS architecture used in wireless networks can be based on QoS flows, and can support QoS flows that require guaranteed bit rates (GBR QoS flows) and QoS flows that do not require GBR (non-GBR QoS flows). Therefore, at the non-access stratum (NAS) level, QoS flows are the finest granularity of QoS differentiation in a protocol data unit (PDU) session. Figure 3 As shown, the user plane function (UPF) can use a QoS flow identifier (QFI) to identify a QoS flow within a PDU session, and the QFI can be carried in an encapsulation header sent from the UPF to the base station via the NG-U interface. Figure 3 As shown, the QoS architecture may include a next generation radio access network (NG-RAN) connected to a 5G core network (5GC), wherein the 5GC may establish one or more PDU sessions for each UE communicating with a base station in the NG-RAN. In addition, the NG-RAN may establish one or more data radio bearers (DRBs) for each PDU session for each UE, and the NG-RAN may map packets belonging to different PDU sessions to different DRBs. Therefore, the NG-RAN may establish at least one default DRB for each PDU session. Non-access stratum (NAS) level packet filters may be used in the UE and the 5GC to associate uplink packets and downlink packets with QoS flows, and access stratum (AS) level packet filters may be used in the UE and the NG-RAN to associate uplink QoS flows and downlink QoS flows with DRBs.

[0071] exist Figure 3 In the QoS architecture shown in , NG-RAN and 5GC can ensure QoS (e.g., reliability and target latency) by mapping packets to appropriate QoS flows and DRBs. Therefore, there is usually a two-step mapping of Internet Protocol (IP) flows to QoS flows at the NAS level and from QoS flows to DRBs at the AS level.

[0072] For example, at the NAS level, a QoS flow may be associated with a QoS profile provided from the 5GC to the NG-RAN (e.g., from the UPF to the base station) and one or more QoS rules provided from the 5GC to the UE. The NG-RAN may use the QoS profile to determine the processing of packets to be applied to the radio interface between the base station and the UE, while the QoS rule specifies the mapping between the uplink user plane service and the QoS flow to the UE. Typically, depending on the QoS profile associated with the QoS flow, the QoS flow may be a GBR QoS flow or a non-GBR QoS flow. The QoS profile associated with the QoS flow may include various QoS parameters, which may include a 5G QoS identifier (5QI) and an allocation and retention priority (ARP). In addition, the QoS profile associated with the GBR QoS flow may include: a guaranteed flow bit rate (GFBR) for both uplink and downlink, a maximum flow bit rate (MFBR) for both uplink and downlink, and a maximum packet loss rate for both uplink and downlink. Alternatively, a QoS profile associated with a non-GBR QoS flow may include a reflective QoS attribute (RQA), which may indicate that when the RQA parameter is included in the QoS profile, at least some (but not necessarily all) traffic carried on the QoS flow is subject to reflective QoS (RQoS) at the NAS level.

[0073] In addition, an aggregate maximum bit rate can be associated with each PDU session (session-AMBR) and with each UE (UE-AMBR). The session-AMBR can generally limit the aggregate bit rate that is expected to be provided across all non-GBR QoS flows for a particular PDU session, and the UE-AMBR can limit the aggregate bit rate that is expected to be provided across all non-GBR QoS flows for the UE. 5QI can be associated with QoS characteristics, which indicate criteria for setting node-specific parameters for each QoS flow, where standardized or preconfigured 5G QoS characteristics can be derived from the 5QI value and are not explicitly signaled. The signaled QoS characteristics can be included in the QoS profile. For example, the QoS characteristics associated with the 5QI may include: resource type (e.g., GBR, delay-critical GBR, or non-GBR), priority level, packet delay budget, packet error rate, average window, and / or maximum data burst, etc.

[0074] At the AS level, the DRB defines the packet processing on the radio interface (Uu). For example, the DRB can serve packets using the same packet forwarding processing. The mapping between QoS flows and DRBs at the NG-RAN can be based on the QFI and one or more associated QoS profiles (e.g., QoS parameters and / or QoS characteristics). Separate DRBs can be established for QoS flows that require different packet forwarding processing, or several QoS flows belonging to the same PDU session can be multiplexed in the same DRB. On the uplink, the NG-RAN can use reflective mapping or explicit configuration to control the mapping between QoS flows and DRBs. For example, in reflective mapping, the UE can monitor the QFI associated with the downlink packet for each DRB, and the same mapping can be applied on the uplink. In other words, for a DRB, the UE can map uplink packets belonging to one or more QoS flows corresponding to the QFI and PDU session observed in the downlink packet for the DRB. In order to implement reflective mapping, the NG-RAN can mark the downlink packets sent to the UE on the Uu interface with the QFI. Alternatively, for explicit configuration, NG-RAN can use Radio Resource Control (RRC) signaling to configure uplink QoS flow to DRB mapping. The UE can generally apply the latest update of the mapping rules, regardless of whether the mapping is based on reflective mapping or explicit configuration.

[0075] On the downlink, the QFI may be signaled by the NG-RAN over the Uu interface to achieve RQoS on the uplink. Alternatively, if neither the NG-RAN nor the NAS (e.g. as indicated by the RQA) intends to use reflective mapping for one or more QoS flows carried in a DRB, the QFI for that DRB is not signaled over the Uu interface. On the uplink, the NG-RAN may configure the UE to signal the QFI over the Uu interface.

[0076] exist Figure 3 In the QoS architecture shown, a default DRB may be configured for each PDU session. In the event that an incoming uplink packet to be sent by the UE does not match the RRC configured mapping between QFI and DRB and / or the reflected mapping between QFI and DRB, the UE may map the packet to the default DRB.

[0077] Within each PDU Session, the NG-RAN may determine how to map multiple QoS flows to DRBs. The NG-RAN may map a GBR flow and a non-GBR flow or more than one GBR flow to the same DRB. The time at which one or more non-default DRBs are established between the NG-RAN and the UE for configured QoS flows during PDU Session establishment may be different from the time of PDU Session establishment, wherein the NG-RAN may determine when to establish the non-default DRBs.

[0078] As described above, Figure 3 are provided as examples. Other examples may differ from those regarding Figure 3 Examples described.

[0079] Figure 4A-4B 4 is a schematic diagram illustrating an example 400 associated with remapping a QoS flow based on a Service Data Adaptation Protocol (SDAP) end marker. Figure 4A As shown, example 400 includes communication between a UE including an application layer (e.g., upper layer) and a modem, a RAN that may include one or more base stations, one or more core network devices (e.g., access and mobility management function (AMF), UPF, session management function (SMF) and / or policy control function (PCF) and / or unified data management function (UDM), etc.), and a data network. As described herein, Figure 4A A call flow is shown in which the RAN can configure the UE to change the AS-level mapping of an existing QoS flow from a first DRB to a second DRB via RRC signaling. In addition, as described herein, the UE can use an end-marker SDAP control protocol data unit (PDU) to apply the configuration change without releasing the first DRB. As further described in detail herein, Figure 4B An example PDU session 450 is shown in which the UE may use an end-marker SDP control PDU to apply configuration changes.

[0080] In some aspects, Figure 4A The call flow shown in may start from a state where the UE is registered with the core network and the UE is camped on a cell in the RAN. For example, the UE may be in RRC connected mode and a PDU session associated with a PDU session type (e.g., IPv4, IPv6, IPv4v6, or Ethernet) has been established. For example, in Figure 4B In the example PDU session 450, an IP or Ethernet PDU session may be associated with one or more service data flows (SDFs), where the SDF may include data, packets, and / or frames from a set of applications on the UE. In general, a UE may have one or more PDU sessions, each PDU session may have one or more DRBs, and each DRB may have one or more QoS flows, where each QoS flow is identified by a QFI that may contain one or more SDFs.

[0081] like Figure 4AAs shown, at 410, the UE can establish a QoS flow with a specific QFI (e.g., QFI=1) during PDU establishment, and RRC signaling can configure the mapping between QFI and DRB (e.g., mapping QFI1 to DRB1). In the examples described herein, the UE can transmit uplink application data and downlink application data via QFI1 and DRB1.

[0082] like Figure 4A As further shown in , at 412, the RAN may send an RRC reconfiguration message to the UE containing a mapping between QFIs and DRBs (e.g., in an sdap-Config information element (IE) included in DRB-ToAddMod of RadioBearerConfig parameters). In this example, the existing QFI1 is mapped to DRB2. Thus, the RRC reconfiguration message may act as a trigger to instruct the UE to change the mapping for the existing QFI1 from DRB1 to DRB2.

[0083] like Figure 4A As further shown in FIG. 4 , at 414, the UE may send an RRC reconfiguration complete message to the RAN to confirm the RRC reconfiguration message.

[0084] like Figure 4A As further shown in FIG. 4 , at 416, the UE may map all new uplink data associated with QFI1 to DRB2 at the SDAP layer. Figure 4B , before the UE receives the RRC reconfiguration message that changes the mapping for QFI1 from DRB1 to DRB2, the first uplink packet and the second uplink packet (shown as Pkt1 and Pkt2) are sent, whereby the first uplink packet and the second uplink packet are mapped to DRB1. In addition, after the UE receives the RRC reconfiguration message that changes the mapping for QFI1 to DRB2, the third uplink packet and the fourth uplink packet (shown as shaded packets Pkt 3 and Pkt 4) are sent, whereby the third uplink packet and the fourth uplink packet are mapped to DRB2.

[0085] like Figure 4A As further shown in FIG. 4 , at 418, the UE may create an SDAP control PDU for QFI1 and place the SDAP control PDU in a layer 2 (L2) transmission buffer associated with DRB1 after the UE has confirmed that no new QFI1 uplink data is mapped to DRB1. Typically, the SDAP control PDU is the last packet data convergence protocol (PDCP) PDU in DRB1. For example, Figure 4BAs shown, the UE may place the SDAP control PDU in the L2 transmission buffer associated with DRB1 after the second uplink packet. Typically, the PDCP entity may not be able to distinguish the SDAP control PDU from the SDAP data PDU, whereby the SDAP data PDU and the SDAP control PDU are processed by the PDCP in the same manner, and the PDCP layer preserves the order of the SDAP data PDU and the SDAP control PDU (e.g., the PDCP layer ensures that the SDAP control PDU is the last PDCP PDU for QFI1 in DRB1). Therefore, the SDAP control PDU is used as an end marker in QFI remapping.

[0086] like Figure 4A As further shown in FIG. 4 , at 420, the UE may have mapped some QFI1 uplink data to DRB1 and placed the QFI uplink data in the L2 transmission buffer associated with DRB1. Therefore, at 420, the UE may send all QFI1 uplink data that is already in the L2 transmission buffer associated with DRB1 via DRB1. For example, Figure 4B In the example, when the SDAP control PDU is placed in the L2 transmission buffer associated with DRB1, the first uplink packet and the second uplink packet associated with QFI1 have been mapped to DRB1, so that the UE can send the first uplink packet and the second uplink packet via DRB1.

[0087] like Figure 4A As further shown in , at 422, the RAN may receive uplink data mapped to DRB2 at 416 before or after receiving uplink data mapped to DRB1 at 420 (e.g., due to hybrid automatic repeat request (HARQ) and / or logical channel prioritization (LCP), where DRB2 may have a higher priority than DRB1 in medium access control (MAC) layer scheduling). However, in the event that the RAN receives uplink data mapped to DRB2 before receiving uplink data mapped to DRB1, the RAN typically delivers DRB2 data to the upper layer only after receiving the end marker SDAP control PDU. Therefore, the RAN may deliver DRB1 data to the upper layer before delivering DRB2 data for QFI1 in the uplink. For example, at Figure 4B In the embodiment, the RAN may receive the third and / or fourth uplink packets (from DRB2) earlier than the first and / or second uplink packets (from DRB1) or the SDAP control PDU. However, the RAN will deliver the third uplink packet to the upper layer only after receiving the SDAP control PDU.

[0088] like Figure 4AAs further shown in FIG. 4 , at 424, the RAN may remap the downlink QFI1 data from DRB1 to DRB2. Typically, the remapping may be performed by the RAN at Figure 4A Executed at any time during the call flow shown. Therefore, as described herein, the application layer of the UE can use the new QFI to DRB mapping rules configured by the RAN to transmit downlink and uplink data without discarding the uplink data, and the end marker SDAP control PDU ensures that the uplink data is not out of order at the receiver (e.g., RAN) side. For example, as described herein, whenever the mapping between the QoS flow and the DRB changes, the UE can generally send an end marker SDAP control PDU to achieve uplink packet reordering when the mapping between the QoS flow and the DRB changes. However, in the case where the QoS flow is only downlink (e.g., there is no uplink data), there is no need to send an end marker SDAP control PDU (the end marker SDAP control PDU wastes resources and increases the uplink control overhead). Therefore, in some aspects described herein, in the case where the RRC reconfiguration message indicates a change to a DRB for a QoS flow that is not associated with any uplink packet filter, the UE can avoid sending an end marker SDAP control PDU. For example, when the UE receives an RRC reconfiguration message indicating that the UE changes the DRB mapped to the QFI from the first DRB to the second DRB, in the case where the QFI is associated with zero (0) uplink packet filters, the UE does not need to send an end marker SDAP control PDU (e.g., a control signal from the UE for in-sequence delivery of uplink data during remapping). For example, in this case, the end marker SDAP control PDU may be unnecessary because the only purpose of the end marker SDAP control PDU is to ensure in-sequence delivery of uplink data during remapping, which is not required for a downlink-only QoS flow that is not associated with any uplink packet filter, thereby reducing the uplink overhead associated with the end marker SDAP control PDU.

[0089] As mentioned above, Figure 4A-4B are provided as examples. Other examples may differ from those regarding Figure 4A-4B Examples described.

[0090] Figure 5A-5B 5 is a schematic diagram illustrating an example 500 of NAS RQoS. Figure 5A-5B As shown, example 500 includes communication between a UE including an application layer (e.g., upper layer) and a modem, a RAN that may include one or more base stations, one or more core network devices (e.g., AMF, UPF, SMF and / or PCF / UDM, etc.), and a data network. As described herein, Figure 5A-5B A call flow is shown where the UE may request to establish a new PDU session and the RAN may decide to use NAS RQoS without AS RQoS for the new PDU session. Figure 5A-5B The call flow shown in may start from a state where the UE is registered with the core network and has zero or more PDU sessions established, and the UE has a subscription that allows IP or Ethernet PDU types.

[0091] like Figure 5A As shown, at 510, the UE may send a PDU session establishment request message to the SMF. Typically, the PDU session establishment request message may include an RQoS bit (e.g., in a UE capability IE) indicating that the UE supports RQoS. The UE may set the PDU session type in the PDU session establishment request message to "IPv4v6", "IPv4", "IPv6", or "Ethernet". Figure 5A-5B In the example 500 shown and described herein, the first application packet may be an uplink packet (not downlink), whereby the application triggers the UE to establish a new PDU session.

[0092] like Figure 5A As further shown in FIG. 5 , at 512, the core network device may create one or more QFIs and determine 5QI parameters based on the UE's subscription. For downlink traffic, the SMF may send an RQoS indication (RQI) to the UPF to activate RQoS per SDF for a given QFI. The SMF may then (via the AMF) send one or more QoS profiles to the RAN, the one or more QoS profiles containing the above combined Figure 3 Optional RQA parameter described. Each QoS profile sent from the SMF to the RAN may correspond to a QFI, and the presence of the RQA parameter indicates that certain services (not necessarily all services) carried on the associated QFI are subject to RQoS. The QoS profile may provide the RAN with a mapping between QoS parameters and QFIs.

[0093] like Figure 5A As further shown in FIG. 5 , at 514 , the RAN and the core network may establish an N3 tunnel for the PDU session.

[0094] like Figure 5AAs further shown in, at 516, the RAN may configure one or more new DRBs, QFI to DRB mapping rules, and a downlink SDAP header to the UE via RRC signaling. In the absence of AS RQoS, the RAN may configure a downlink SDAP header for the DRB based on the RQA received at 512 (e.g., when RQA is present in the QoS profile of at least one QoS flow within the DRB, the RAN configures the downlink SDAP header). In the example described herein, QFI=x1 may be mapped to DRB=y1, and QFI=x2 may be mapped to DRB=y2. At 516, the UE may receive a PDU session establishment accept message with an RQ timer value in the RQ timer IE from the SMF. In the case where the RQ timer value is neither deactivated nor zero, the RQoS timer value may indicate that the SMF is enabling NAS RQoS for the PDU session of the UE. The PDU session establishment accept message may contain a default QoS rule (e.g., {match-all filter, QFI=x1, precedence value=255}).

[0095] like Figure 5A As shown, at 518, the application layer of the UE may send a first uplink data burst with a Transmission Control Protocol (TCP) / IP 5-tuple, the IP 5-tuple including a source IP address, a destination IP address, a source port, a destination port, and a protocol. The UE may match the uplink data packet with one or more uplink packet filters in the existing QoS rules. At this point, in the call flow, the UE only has the QoS rules signaled by the network, and no UE-derived QoS rules. In this example, the 5-tuple associated with the uplink data packet matches the uplink packet filter associated with the default QoS rule QFI=x1, which is configured at 516 to map to DRB=y1. Therefore, as shown at 520, the first data burst may be sent via QFI=x1 (e.g., the default QoS flow) and DRB=y1 mapped to QFI=x1.

[0096] like Figure 5AAs shown, at 522, the data network may send a first downlink data burst to the application layer of the UE in reply to the first uplink data burst from the application layer of the UE. In this example, the downlink packet includes a TCP / IP 5-tuple, which is a source-destination switched version of the 5-tuple from the UE (e.g., the source IP address and source port of the downlink packet are the same as the destination IP address and destination port of the uplink packet, respectively). As further shown, the UPF matches the downlink packet with a downlink packet filter from one or more packet detection rules (PDRs). In this example, the 5-tuple associated with the downlink packet matches a downlink PDR with activated NAS RQoS and associated with QFI=x2. The UPF may set QFI=x2 and RQI=1 in the encapsulation header on the N3 reference point for each downlink packet corresponding to the SDF. As shown at 524, when the RAN receives a downlink packet with RQI=1 over the N3 reference point, the RAN may indicate the QFI and RQI of the downlink packet to the UE in the SDAP header, and the RAN may map the packet with QFI=x2 to DRB=y2.

[0097] like Figure 5B As shown, at 526, the modem of the UE may derive a new QoS rule including QFI=x and a new NAS packet filter that maps the 5-tuple associated with the first uplink data burst to QFI=x2 associated with the first downlink data burst based on the downlink SDAP PDU. The derived QoS rule may have a fixed priority value (e.g., 80) and may map the 5-tuple associated with the first uplink data to a QoS flow (e.g., a non-default QoS flow) with QFI=x2.

[0098] like Figure 5B As shown, at 528, the application layer of the UE may send a second uplink data burst having the same TCP / IP 5-tuple as the first uplink data burst.

[0099] like Figure 5B As shown, at 530, the UE's modem may apply both the UE-derived QoS rule and the network-configured QoS rule and may associate one (or more) uplink packets in the second uplink data burst with QFI=x2. Although both the network-signaled default QoS rule (e.g., priority value 255) and the UE-derived QoS rule (e.g., priority value 80) match the one (or more) uplink packets, the UE's modem may associate the one (or more) uplink packets with the UE-derived QoS rule based on the lower priority value.

[0100] like Figure 5B As shown, at 532, the UE's modem may apply the QFI-to-DRB mapping rule signaled at 516 to map the packet to DRB=y2.

[0101] like Figure 5B As shown, at 534, the UE's modem may place one (or more) uplink packets associated with the second uplink data burst in an uplink SDAP PDU and may send the uplink SDAP PDU via QFI=x2 and DRB=y2.

[0102] like Figure 5B As shown, at 536, the RAN may forward one (or more) uplink packets associated with the second uplink data burst to the UPF via the N3 tunnel, with QFI=x2 in the tunnel header, and the UPF may forward the one (or more) uplink packets to the data network.

[0103] As mentioned above, Figure 5A-5B are provided as examples. Other examples may differ from those regarding Figure 5A-5B Examples described.

[0104] Figure 6 6 is a schematic diagram illustrating an example 600 of AS RQoS. Figure 6 As shown, example 600 includes communication between a UE including an application layer (e.g., upper layer) and a modem, a RAN that may include one or more base stations, one or more core network devices (e.g., AMF, UPF, SMF and / or PCF / UDM, etc.), and a data network. As described herein, Figure 6 A call flow is shown in which the UE performs AS RQoS operations to derive a mapping between QoS flows and DRBs. Explicit NAS QoS signaling (as opposed to NAS RQoS) is used to configure uplink packet filters for the UE. In some aspects, Figure 6 The call flow shown in may start from a state where the UE has indicated to the RAN in RRC signaling indicating the UE's capabilities (e.g., via an as-ReflectiveQoS parameter) that the UE supports AS RQoS. The UE may be in RRC connected mode, and the UE has established at least one PDU session and any associated DRB(s). As described herein, the core network may add a new QoS flow associated with a QFI by sending signaling to the UE indicating the new QoS rules and sending a new QoS profile to the RAN.

[0105] like Figure 6As shown, at 610, the core network may initiate a call flow to add a new QoS flow associated with a QFI (e.g., QFI=x) by sending a PDU Session Modification Command message with new QoS rules to the UE and by sending one or more new QoS profiles to the RAN. The RAN may decide to use AS RQoS to map the new QFI=x to an existing DRB (e.g., DRB=y).

[0106] like Figure 6 As further shown in , at 612, the data network may send a downlink user packet to the UE. The downlink user packet may be received at the UPF, and the UPF may forward the packet to the RAN via the N3 tunnel with QFI=x in the tunnel header.

[0107] like Figure 6 As further shown in , at 614, the RAN may send a downlink user packet to the UE in a SDAP PDU including a SDAP header. For example, the SDAP header may include one or more fields indicating QFI=x, Reflective QoS Flow to DRB Mapping Indication (RDI)=1, and RQI=0.

[0108] like Figure 6 As further shown in FIG. 6 , at 616 , the UE's modem may derive a new mapping rule (eg, mapping QFI=x to DRB=y) based on the downlink SDAP PDU.

[0109] like Figure 6 As further shown in FIG. 6 , at 618, the application layer of the UE may transmit the uplink user packets received at the modem.

[0110] like Figure 6 As further shown in , at 620, the UE's modem may apply uplink packet filtering and associate uplink user packets with QFI=x.

[0111] like Figure 6 As further shown in , at 622, the UE's modem may apply the mapping rule derived at 616 to map the uplink user packets to the appropriate DRB (DRB=y).

[0112] like Figure 6 As further shown, at 624, the UE's modem may place the uplink user packet in an uplink SDAP PDU and may transmit the uplink SDAP PDU via QFI=x and associated DRB=y.

[0113] like Figure 6As further shown, at 626, the RAN may forward the uplink user packet to the UPF via the N3 tunnel with QFI=x in the tunnel header, and the UPF may forward the uplink user packet to the data network.

[0114] As described above, Figure 6 are provided as examples. Other examples may differ from those regarding Figure 6 Examples described.

[0115] Figure 7A-7B 7 is a schematic diagram showing an example 700 of a UE applying NAS RQoS techniques to derive uplink packet filters based on information in downlink packets. Fig. 7A As shown, example 700 includes communication between a UE and a RAN for use in conjunction with the above Figure 5A-5B NAS RQoS is implemented for one or more downlink packets in a similar manner as described above. For example, when a UE receives a downlink SDAP PDU with an SDAP header parameter including RQI=1 in a DRB, the UE may extract the QFI value from the SDAP header and derive an uplink packet filter based on the received downlink SDAP data PDU. For example, the UE may implement NAS RQoS for one or more downlink packets by applying the above combined Figure 5A-5B The NAS RQoS described in the present invention may be used to derive an uplink packet filter, which may include extracting a 5-tuple (e.g., source IP address, destination IP address, source port, destination port, and protocol) from a TCP, User Datagram Protocol (UDP), and / or IP header. The UE may then search for the derived packet filter in a stored derived QoS rule table (e.g., indicating a UE-derived uplink packet filter, a QFI value, a priority value, and a remaining validity time for one or more existing UE-derived rules). In the event that the packet filter matches a QoS rule in the stored derived QoS rule table, the UE may overwrite the QFI of the matching QoS rule with a QFI value of QFI0 and restart a timer associated with the rule. In other cases, the UE may add a new QoS rule (e.g., including a UE-derived uplink packet filter and associated QFI and priority values) and start a new timer associated with the new QoS rule.

[0116] However, in the case of Encapsulating Security Payload (ESP) packets, where the uplink ESP packets and / or downlink ESP packets may be encapsulated within another packet (such as a User Datagram Protocol (UDP) packet in a UDP Network Address Translation Traversal (UDP NAT-T) use case), the UE's modem may be unable to determine the uplink security parameter index (SPI) required to derive a NAS RQoS uplink packet filter. As described herein, example 700 illustrates an example in which the UE may apply the above-described NAS RQoS process to derive an uplink packet filter based on an example downlink SDAP PDU having an SDAP header and an ESP header. For example, at 710, the UE may receive a first downlink SDAP PDU having an SDAP header from a first DRB from the RAN. For example, Figure 7B An example structure 750 for a downlink SDAP PDU is shown, which may include a one-byte downlink SDAP header including: a QFI (e.g., QFI=3), and an RQI set to one (1) to indicate that the downlink packet requires RQoS treatment. Figure 7B As further shown, the downlink SDAPPDU includes an IPv4 header indicating a protocol (e.g., 50 to indicate the ESP protocol), a source address and a destination address, etc. In addition, as Figure 7B As shown, the downlink SDAP PDU may include an ESP header including a downlink SPI value (eg, Figure 7B of ten (10)).

[0117] Reference again Fig. 7A At 712, the UE may extract the QFI and RQI from the downlink SDAP header of the downlink packet received from the RAN. Figure 7B In the example downlink SDAP PDU shown in , the QFI is three (3) and the RQI is set to one (1), whereby the UE will derive a new uplink packet filter for the QoS flow associated with the downlink packet (e.g., the QoS flow associated with QFI=3). In this example, the downlink packet is an IPv4 ESP packet, and the 5-tuple parameters indicated in the IPv4 and ESP headers include: source IP address (10.10.10.10), destination IP address (20.20.20.20), downlink SPI (10), and protocol (50=ESP).

[0118] like Fig. 7AAs shown, at 714, the UE may need to identify an uplink security association with an uplink SPI that corresponds to a downlink security association with a downlink SPI indicated in a downlink packet. However, determining an uplink SPI paired with a downlink SPI may present various challenges because an uplink ESP packet is generated by the IPsec layer (above the IP layer) after a security association is established (e.g., in an application processor). The security association may be separate for uplink and downlink packets, whereby a bidirectional data stream may include uplink ESP packets and downlink ESP packets using different SPI values. Therefore, because there is no predefined correlation between uplink SPI and downlink SPI values, and only the IPsec layer explicitly knows the uplink and downlink SPI pairing, the modem may need to employ one or more techniques to learn the uplink and downlink SPI pairing to determine the uplink SPI required to achieve RQoS.

[0119] For example, if the following combination Figure 8 As described in further detail, a modem of a UE may monitor ESP packets on a PDU session with NAS RQoS enabled, and may store a record for each ESP packet associated with a unique attribute combination (e.g., a unique 3-tuple including a local IP address, a remote IP address, and an uplink SPI value). The stored record may also include a downlink SPI field that is initially set to "none" or another suitable null value, and the record may include a flag that initially indicates that the uplink SPI is not mapped to the downlink SPI. Thus, when the modem receives a downlink ESP packet and there is only one stored record that satisfies a set of mapping conditions for the downlink ESP packet (e.g., there is one record that includes a local IP address and a remote IP address that match the local IP address and the remote IP address included in the downlink packet and / or a flag that indicates that the uplink SPI is not mapped to the downlink SPI value, etc.), the modem may update the one matching record to include the downlink SPI value included in the downlink ESP packet, and change the value of the flag to indicate that the uplink SPI is mapped to the downlink SPI value. Additionally or alternatively, as described below in conjunction with Fig. 9As described in further detail, upon receiving a downlink ESP packet, in the event that the modem and the upper layer are able to exchange control information, the modem may query the upper layer (e.g., the application layer or the IPsec layer) to request an uplink SPI paired with the unmapped downlink SPI. In this manner, the UE may create an uplink packet filter to indicate that uplink ESP packets having the same local IP address, remote IP address, and paired uplink SPI are associated with the QFI included in the received downlink ESP packet, and thereby implement RQoS for the ESP packet.

[0120] For example, at 716, the UE may create an uplink packet filter based on the uplink SPI and downlink SPI pairing. For example, the uplink packet filter may include: a destination IP address corresponding to the source IP address of the downlink packet received at 710 (e.g., 10.10.10.10), a source IP address corresponding to the destination IP address of the downlink packet received at 710 (e.g., 20.20.20.20), an uplink SPI paired with the downlink SPI of the downlink packet received at 710, and a protocol (e.g., 50) of the downlink packet received at 710. In addition, the UE may associate an identifier (e.g., PF0) of the uplink packet filter with a QFI (e.g., QFI=3) associated with the received downlink packet. For example, at 718, the UE may create a new derived QoS rule indicating the QFI and priority value (e.g., {QFI=3, priority value=80, PF0}) associated with the uplink packet filter. In this way, when the modem receives an uplink packet from the application layer that matches the uplink packet filter (e.g., the uplink packet has the same destination IP address, source IP address, uplink SPI, and protocol as the uplink packet filter associated with identifier PF0), the UE can associate the uplink packet with the QoS flow associated with the QFI of the derived QoS rule, thereby achieving RQoS.

[0121] As mentioned above, Figure 7A-7B are provided as examples. Other examples may differ from those regarding Figure 7A-7B Examples described.

[0122] Figure 8 8 is a schematic diagram illustrating an example 800 associated with RQoS for ESP packets. Figure 8 As shown, example 800 includes communications between a UE and a RAN to implement NAS RQoS for ESP packets. Figure 8As shown, the UE may include a modem and an upper layer (e.g., an application layer, such as an IPsec layer), wherein the upper layer generates an uplink ESP packet, and only the upper layer is explicitly aware of the pairing between the downlink SPI and the uplink SPI. For example, in some aspects, the upper layer may generate an uplink ESP packet in an IPsec tunnel mode, a transport mode, or another suitable mode.

[0123] In some aspects, as described herein, example 800 may be performed to enable a modem to learn one or more uplink and downlink SPI pairings in the event that an upper layer (e.g., an application processor that creates one or more security associations) is unable to exchange control information with the modem. For example, the modem may be connected to a computer via a suitable interface (such as a universal serial bus (USB) port or a peripheral component interconnect express (PCIe) interface), where the upper layer is in the application processor of the computer. In this example, the upper layer (e.g., IPsec) at the computer may not be able to exchange control information with the modem. In another example, the modem may be included in a wireless customer premises equipment (CPE) or a smart phone with a wireless local area network (WLAN) hotspot, where the CPE or WLAN hotspot is connected to the Internet using a wireless backhaul (e.g., over a 5G network instead of using a fixed line backhaul such as a digital subscriber line (DSL)) and is connected to one or more personal computers using an Ethernet or WLAN connection. In this case, the upper layer (e.g., IPsec) at the personal computer may not be able to exchange control information with the modem.

[0124] Additionally or alternatively, as described herein, example 800 may be performed to enable the modem to learn one or more uplink and downlink SPI pairings when the upper layer is able to exchange control information with the modem (e.g., in a smart phone). In other words, example 800 may enable the modem to learn one or more uplink and downlink SPI pairings, regardless of whether the upper layer and the modem are able to exchange control information. For example, as described herein, the upper layer may create security association pairs one at a time. Therefore, as described herein, if a first security association pair is created before any other security association pair for the same source IP address and destination IP pair, example 800 may enable the modem to obtain and store SPI pairing information (e.g., pairing between an uplink SPI and a downlink SPI) for the first security association pair.

[0125] For example, at 810, the modem may monitor ESP packets on one or more PDU sessions with NAS RQoS enabled, and may receive one or more uplink ESP packets from an upper layer. For each uplink ESP packet received at the modem, the modem may determine a set of attributes associated with the uplink ESP packet. For example, the attribute set may include a 3-tuple including a local IP address (e.g., a source IP address associated with the UE), a remote IP address (e.g., a destination IP address associated with a website server), and an uplink SPI value. In some aspects, the QoS may store one or more records corresponding to a set of attributes associated with a previously received uplink ESP packet (e.g., a 3-tuple including a local IP address, a remote IP address, and an uplink SPI value associated with a previously received uplink ESP packet). Therefore, in the case where the modem receives an uplink ESP packet including a local IP address, a remote IP address, and an uplink SPI value from an upper layer and there is no existing record with the same local IP address, remote IP address, and uplink SPI value, the modem may determine that the uplink SPI is not mapped.

[0126] In some aspects, as further shown at 812, the modem may store a new record including the local IP address, the remote IP address, and the uplink SPI carried in the uplink ESP packet based on determining that there is no existing record including the same set of attributes. In some aspects, the new record stored by the modem may include a flag that may be set to a first value to indicate that the uplink SPI is not mapped to the downlink SPI (e.g., IsMaped=false or IsMaped=0). In addition, the new record may include a downlink SPI field that is initially set to a null value because the modem has not yet found a downlink SPI that is paired with the uplink SPI (e.g., DLSPI=None). In some aspects, the modem may also start a timer associated with the new record, wherein the timer may be used to handle a failure scenario that occurs when the modem cannot find a downlink SPI pairing for an unmapped attribute set (e.g., an unmapped 5-tuple including local IP address, remote IP address, uplink SPI, downlink SPI=None, and IsMapped=false or 0) within a predefined or configurable duration. Thus, if the modem cannot derive a downlink SPI pairing before the timer expires, the modem may delete the record associated with the unmapped uplink SPI.

[0127] As further shown at 814, the modem may receive one or more downlink ESP packets from the RAN, wherein each downlink ESP packet may include a source IP address (e.g., a remote IP address relative to QoS), a destination IP address (e.g., a local IP address relative to QoS), and a downlink SPI. In some aspects, the modem may determine whether one or more stored records include a set of attributes that satisfies one or more conditions. For example, the modem may determine whether there are one or more stored records that satisfy a first condition, whereby one (or more) stored records include the same local IP address and remote IP address as the downlink ESP packet. In addition, in some aspects, the modem may determine whether any such record satisfies a second condition, whereby the flag is set to a value indicating that the associated uplink SPI is not mapped to the downlink SPI (e.g., IsMapped is "false" or "0"). In some aspects, the modem may optionally further determine whether a third condition is satisfied, whereby the third condition may be that the downlink SPI included in the downlink ESP packet has not been mapped to the uplink SPI. In some aspects, in the case where the modem determines that there is only one stored record that satisfies the first condition and the second condition, or alternatively, there is only one stored record that satisfies the first condition, the second condition, and the third condition, if the timer associated with the record has not expired, the modem may determine that the downlink SPI included in the downlink ESP packet is paired with the uplink SPI in the one stored record. In such a case, when all applicable mapping conditions and / or criteria are met, the modem may update the record to indicate that the uplink and downlink SPIs are paired, as shown at 816. For example, the modem may update the record to include the downlink SPI in the downlink ESP packet, and may set the flag to a value indicating that the uplink SPI is mapped to the downlink SPI (e.g., IsMapped=true or 1). Alternatively, if there is no stored record that satisfies the above conditions or there are two or more stored records that satisfy the above conditions, the modem may not be able to determine the correct uplink and downlink SPI pairing.

[0128] The logic used by the modem to derive uplink and downlink SPI pairings for ESP packets will now be explained with reference to an example sequence of uplink and downlink ESP packets. For example, an upper layer of QoS may send a first uplink ESP packet having a local IP address (e.g., IP_A), a remote IP address (e.g., IP_B), and an uplink SPI value (e.g., UL SPI=SPI_0). To derive a first security association pairing, based on determining that there is no stored record including the local IP address, the remote IP address, and the uplink SPI included in the uplink ESP packet, the modem may store a new record constructed as follows:

[0129]

[0130] In some aspects, the modem may then receive a first downlink ESP packet with a local IP address (e.g., IP_A), a remote IP address (e.g., IP_B), and a downlink SPI value (e.g., DL SPI=SPI_1). In this case, there is only one record with the same local IP address and remote IP address, and a flag indicating that the associated uplink SPI is not mapped. Therefore, the modem updates the record to map the downlink SPI in the downlink ESP packet with the uplink SPI of the first uplink ESP packet, as follows:

[0131] Local IP = IP_A Remote IP = IP_B UL SPI=SPI_0 DL SPI=SPI_1 IsMapped = True

[0132] In some aspects, the modem may then receive additional uplink ESP packets with the same local IP address (e.g., IP_A), remote IP address (e.g., IP_B), and uplink SPI value (e.g., UL SPI=SPI_0). In this case, the modem does not perform an update because the 3-tuple of the local IP address, remote IP address, and uplink SPI has been paired with the downlink SPI. In addition, in the case where the modem receives additional downlink ESP packets with the same local IP address (e.g., IP_A), remote IP address (e.g., IP_B), and downlink SPI value (e.g., DL SPI=SPI_1), no update occurs because the 3-tuple of the local IP address, remote IP address, and downlink SPI has been paired with the uplink SPI. However, when the modem receives an uplink ESP packet with a different 3-tuple (e.g., local IP address=IP_A, remote IP address=IP_B, and UL SPI=SPI_2), the modem may store a new record to attempt to derive a second security association pairing, as follows:

[0133] Local IP = IP_A Remote IP = IP_B UL SPI=SPI_0 DL SPI=SPI_1 IsMapped = True Local IP = IP_A Remote IP = IP_B UL SPI=SPI_2 DL SPI=None IsMapped = False

[0134] In some aspects, the modem may then receive a downlink ESP packet with a local IP address (e.g., IP_A), a remote IP address (e.g., IP_B), and a downlink SPI value (e.g., DL SPI=SPI_3). In this case, there is only one record with the same local IP address and remote IP address, and a flag indicating that the associated uplink SPI is not mapped. Accordingly, the modem updates the second record to map the downlink SPI in the downlink ESP packet with the unmapped uplink SPI, as follows:

[0135] Local IP = IP_A Remote IP = IP_B UL SPI=SPI_0 DL SPI=SPI_1 IsMapped = True Local IP = IP_A Remote IP = IP_B UL SPI=SPI_2 DL SPI=SPI_3 IsMapped = True

[0136] Thus, at 818, QoS may create an uplink packet filter based on the uplink SPI and downlink SPI pairing found using the above logic. For example, for a first record, a first uplink packet filter (denoted as PF0) may include a destination IP address corresponding to a remote IP address (e.g., IP_B), a source IP address corresponding to a local IP address (e.g., IP_A), an uplink SPI (e.g., SPI_0), and an identifier of the ESP protocol (e.g., 50). In addition, QoS may associate the first uplink packet filter with a QFI associated with a downlink packet including a downlink SPI paired with the uplink SPI, and may create a first derived QoS rule indicating the QFI and priority value associated with the first uplink packet filter PF0 (e.g., the first derived QoS rule may be {QFI=3, priority value=80, PF0}). Similarly, for the second record, the second uplink packet filter (denoted as PF1) may include a destination IP address corresponding to a remote IP address (e.g., IP_B), a source IP address corresponding to a local IP address (e.g., IP_A), an uplink SPI (e.g., SPI_2), and an identifier of the ESP protocol (e.g., 50). In addition, the UE may associate the second uplink packet filter PF1 with a QFI associated with a downlink packet including a downlink SPI paired with the uplink SPI, and may create a second derived QoS rule indicating the QFI and priority value associated with the second uplink packet filter PF1 (e.g., the second derived QoS rule may be {QFI=2, priority value=80, PF1}). In this way, when the modem receives an uplink ESP packet from the application layer that matches the uplink packet filter in the derived QoS rule (for example, the uplink ESP packet has the same destination IP address, source IP address, uplink SPI, and protocol as the uplink packet filter), the UE can associate the uplink ESP packet with the QoS flow corresponding to the QFI of the derived QoS rule to achieve RQoS.

[0137] As described above, Figure 8 are provided as examples. Other examples may differ from those regarding Figure 8 Examples described.

[0138] Fig. 9 is a schematic diagram illustrating an example 900 associated with RQoS for ESP packets. Fig. 9 As shown, example 900 includes communications between a UE and a RAN to implement NAS RQoS for ESP packets. Fig. 9As shown, the UE may include a modem and an upper layer (e.g., an application layer, such as an IPsec layer), wherein the upper layer generates an uplink ESP packet and only the upper layer is explicitly aware of the pairing between the downlink SPI and the uplink SPI. For example, in some aspects, the upper layer may generate the uplink ESP packet in IPsec tunnel mode, transport mode, or another suitable mode. In some aspects, as described herein, example 900 may be performed to enable the modem to learn one or more uplink and downlink SPI pairings when the upper layer (e.g., an application processor that creates one or more security associations) is able to exchange control information with the modem (e.g., in a smartphone).

[0139] For example, at 910, the modem may receive one or more downlink ESP packets from the RAN. For each downlink ESP packet received at the modem, the modem may determine a set of attributes associated with the downlink ESP packet. For example, the attribute set may include a 3-tuple including a destination IP address (e.g., a local IP address associated with the UE), a source IP address (e.g., a remote IP address associated with a remote website server), and a downlink SPI value. In some aspects, the UE may determine that the downlink ESP packet is not mapped or associated with the uplink SPI based on determining that there is no existing uplink packet filter including the same attribute set as the received downlink ESP packet. Therefore, in the case where the modem receives a downlink ESP packet including a local IP address, a remote IP address, and a downlink SPI value from the RAN and there is no existing uplink packet filter with the same local IP address, the same remote IP address, and an uplink SPI value mapped to the downlink SPI value, the modem may determine that the downlink SPI is not mapped to the uplink SPI.

[0140] For example, in some aspects, the modem may monitor downlink ESP packets on one or more PDU sessions with NAS RQoS enabled, and the modem may determine, for each observed downlink ESP packet, whether the header of the downlink ESP packet includes an indicator for deriving one or more QoS rules. In the case where the header includes an indicator for deriving one or more QoS rules, the modem may check whether there is a local record (e.g., including a local IP address, a remote IP address, an uplink SPI, and / or a downlink SPI) that matches a set of attributes associated with the downlink ESP packet (e.g., the local IP address of the record matches the local IP address included in the downlink ESP packet, the remote IP address of the record matches the remote IP address included in the downlink ESP packet, and the downlink SPI of the record matches the SPI included in the downlink ESP packet). In the case where no match is found, the modem may determine that the downlink SPI is not mapped to the uplink SPI. Otherwise, in the case where a match is found, the modem may use the uplink SPI included in the matching local record for RQoS processing.

[0141] In some aspects, at 912, the modem can query an upper layer (e.g., an IPsec layer) to request an uplink SPI associated with a given 3-tuple including a local IP address, a remote IP address, and a downlink SPI based on determining that the downlink SPI in a given downlink ESP packet is not mapped to an uplink SPI. For example, as described above, the upper layer can create a security association and therefore can explicitly know that the uplink and downlink SPIs are paired. Therefore, in the case where the modem and the upper layer are able to exchange control information through a suitable interface, the modem can query the upper layer to request an uplink SPI paired with a given local IP address, a remote IP address, and a downlink SPI value included in the downlink ESP packet, and at 914, the upper layer can reply to the query to indicate an uplink SPI paired with a downlink SPI that is not mapped.

[0142] Thus, at 916, the UE may create an uplink packet filter based on the uplink SPI and downlink SPI pairing determined by querying the upper layer. For example, the uplink packet filter may include a destination IP address corresponding to a remote IP address of the downlink ESP packet (e.g., an IP address of a remote website server), a source IP address corresponding to a local IP address of the downlink ESP packet (e.g., an IP address of the UE), an uplink SPI paired with the downlink SPI of the downlink ESP packet, and an identifier of the ESP protocol. In addition, the UE may associate the uplink packet filter with a QFI included in the downlink ESP packet, and the UE may create a derived QoS rule indicating the QFI, the uplink packet filter, and a priority value associated with the QoS rule. In this way, when the modem receives an uplink ESP packet matching the derived QoS rule from the application layer (e.g., the uplink packet has the same destination IP address, source IP address, uplink SPI, and protocol as the uplink packet filter of the derived QoS rule), the UE can apply the matching QoS rule to associate the uplink ESP packet with the QoS flow corresponding to the QFI of the derived QoS rule, thereby implementing RQoS. In addition, in response to the uplink SPI provided by the upper layer, the modem can create a new local record including a local IP address, a remote IP address, an uplink SPI, and a downlink SPI, wherein the local IP address of the record is set to the local IP address included in the downlink ESP packet, the remote IP address of the record is set to the remote IP address included in the downlink ESP packet, the uplink SPI of the record is set to the uplink SPI provided by the upper layer query response and paired with the downlink SPI included in the downlink ESP packet, and the downlink SPI of the record is set to the SPI included in the downlink ESP packet. In this way, the local record can be matched with subsequent downlink ESP packets to implement RQoS processing.

[0143] In an example implementation of logic for learning one or more uplink and downlink SPI pairings when an upper layer may exchange control information with a modem, a UE may receive a first downlink ESP packet with a first local IP address (IP_A), a first remote IP address (IP_B), and a downlink SPI (SPI_1). The UE may not be able to find a matching local record, whereupon the modem may query the upper layer, which may know that the downlink SPI (SPI_1) is paired with the uplink SPI (SPI_0). The modem may then create or update a local record using the first local IP address (IP_A), the first remote IP address (IP_B), the uplink SPI (SPI_0) paired with the downlink SPI of the first downlink ESP packet, and the downlink SPI (SPI_1) of the downlink ESP packet. The UE may then receive one or more additional downlink ESP packets with the first local IP address, the first remote IP address, and the downlink SPI. In this case, a match is found in the local record, and the modem may use the uplink SPI included in the matching local record for RQoS processing. In the event that the UE then receives a downlink ESP packet with a first local IP address (IP_A), a first remote IP address (IP_B), and a second downlink SPI (e.g., SPI_3), no match will be found in the local record, so the modem can query the upper layer again, which knows that the second downlink SPI (SPI_3) is paired with the second uplink SPI (e.g., SPI_2). Therefore, the modem can update the local record, which may include a first record associating the first local IP address and the first remote IP address with the first downlink SPI and the first uplink SPI, and a second record associating the first local IP address and the first remote IP address with the second downlink SPI and the second uplink SPI.

[0144] As described above, Fig. 9 are provided as examples. Other examples may differ from those regarding Fig. 9 Examples described.

[0145] Fig.10 1 is a flow chart of an example method 1000 of wireless communication. Method 1000 may be performed by, for example, a UE (eg, a modem of UE 120).

[0146] At 1010, the UE may: store a record including a first set of attributes associated with an uplink ESP packet sent by an upper layer of the UE, wherein the first set of attributes includes an uplink SPI included in a header of the uplink ESP packet and a flag indicating that the uplink SPI is not mapped to a downlink SPI. For example, the UE (e.g., using Fig.12 The communication manager 140 and / or SPI mapping component 1208 depicted in the embodiment of the present invention may: store a record including a first set of attributes associated with an uplink ESP packet sent by an upper layer of the UE, wherein the first set of attributes includes an uplink SPI included in a header of the uplink ESP packet and a flag indicating that the uplink SPI is not mapped to a downlink SPI, as described above in conjunction with, for example Figure 8 Described at 810 and 812. In some aspects, one or more of the uplink ESP packet or the downlink ESP packet is encapsulated in another packet. In some aspects, the modem and the upper layer are associated with a configuration that does not permit the exchange of control information between the modem and the upper layer. In some aspects, the modem and the upper layer are associated with a configuration that allows the exchange of control information between the modem and the upper layer.

[0147] At 1020, the UE may receive a downlink ESP packet associated with a second attribute set, wherein the second attribute set includes a downlink SPI included in a header of the downlink ESP packet. Fig.12 The communication manager 140 and / or receiving component 1202 depicted in the embodiment may: receive a downlink ESP packet associated with a second attribute set, wherein the second attribute set includes a downlink SPI included in a header of the downlink ESP packet, as described above in conjunction with, for example Figure 8 As described at 814.

[0148] At 1030, the UE may map an uplink SPI associated with an uplink ESP packet and a downlink SPI associated with a downlink ESP packet based at least in part on the record including the uplink SPI satisfying one or more conditions. Fig.12 The communication manager 140 and / or SPI mapping component 1208 depicted in the embodiment may: map an uplink SPI associated with an uplink ESP packet and a downlink SPI associated with a downlink ESP packet based at least in part on the record including the uplink SPI satisfying one or more conditions, as described above in conjunction with, for example Figure 8Described at 816. In some aspects, mapping an uplink SPI associated with an uplink ESP packet and a downlink SPI associated with a downlink ESP packet includes: updating the first set of attributes to include a downlink SPI included in a second set of attributes associated with the downlink ESP packet; and updating the flag to indicate that the uplink SPI is mapped to the downlink SPI.

[0149] In some aspects, the one or more conditions include: a first attribute set associated with the record satisfies one or more mapping criteria, and no other record includes an attribute set that satisfies the one or more mapping criteria. In some aspects, the one or more mapping criteria include: the first attribute set has a first local IP address that matches a second local IP address included in a second attribute set associated with a downlink ESP packet, and the first attribute set has a first remote IP address that matches a second remote IP address included in a second attribute set associated with a downlink ESP packet. In some aspects, the one or more mapping criteria include: the flag has a value indicating that the uplink SPI is not mapped to the downlink SPI. In some aspects, the one or more mapping criteria include: the downlink SPI is not mapped to any uplink SPI. In some aspects, the one or more conditions include: the downlink ESP packet associated with the downlink SPI is received before the expiration of a timer associated with the record including the first attribute set.

[0150] In some aspects, method 1000 includes: creating an uplink packet filter based at least in part on a downlink ESP packet, the uplink packet filter including: an SPI value set to an uplink SPI mapped to a downlink SPI associated with the downlink ESP packet, a destination IP address set to a source IP address in a header of the downlink ESP packet, a source IP address set to a destination IP address in a header of the downlink ESP packet, and a protocol value set to a protocol parameter in a header of the downlink ESP packet; and creating a QoS rule including the uplink packet filter, a QFI set to a QFI parameter in an SDAP header of the downlink ESP packet, and a priority value set to a predefined value. In some aspects, method 1000 includes: receiving an uplink application packet; determining that the uplink application packet includes a parameter set that matches the uplink packet filter in the QoS rule; and associating the uplink application packet with the QFI in the QoS rule.

[0151] In some aspects, method 1000 includes: determining that DRB mapping rules associated with the QFI have changed based at least in part on receiving a configuration message or exporting new QoS flow to DRB mapping rules; and avoiding sending an end marker SDAP control PDU on a current DRB associated with the QFI based at least in part on determining that the QFI is not associated with an uplink packet filter.

[0152] although Fig.10 Example blocks of method 1000 are shown, but in some aspects, method 1000 may include Fig.10 Those blocks depicted in the method 1000 may be additional blocks, fewer blocks, different blocks, or differently arranged blocks. Additionally or alternatively, two or more blocks in the blocks of the method 1000 may be executed in parallel.

[0153] Fig.11 1 is a flow diagram of an example method 1100 of wireless communication. The method 1100 may be performed by, for example, a UE (eg, a modem of UE 120).

[0154] At 1110, the UE may receive a downlink ESP packet, wherein the downlink ESP packet is associated with a local IP address, a remote IP address, and a downlink SPI that is not mapped to an uplink SPI. Fig.12 The communication manager 140 and / or SPI mapping component 1208 depicted in the embodiment of the present invention may: receive a downlink ESP packet, wherein the downlink ESP packet is associated with a local IP address, a remote IP address, and a downlink SPI that is not mapped to an uplink SPI, as described above in conjunction with, for example Fig. 9 Described at 910. In some aspects, the modem and upper layers are associated with a configuration that allows control information to be exchanged between the modem and the upper layers.

[0155] At 1120, the UE may provide a query including a local IP address, a remote IP address, and a downlink SPI to an upper layer. For example, a UE (e.g., using Fig.12 The communication manager 140 and / or SPI mapping component 1208 depicted in FIG. 10 may: provide a query to the upper layer including the local IP address, the remote IP address, and the downlink SPI, as described above in conjunction with, for example, Fig. 9 As described at 912 .

[0156] At 1130, the UE may receive a reply to the query from an upper layer, wherein the reply indicates an uplink SPI paired with a local IP address, a remote IP address, and a downlink SPI associated with a downlink ESP packet. Fig.12The communication manager 140 and / or SPI mapping component 1208 depicted in the figure may: receive a reply to the query from an upper layer, wherein the reply indicates an uplink SPI paired with a local IP address, a remote IP address, and a downlink SPI associated with a downlink ESP packet, as described above in conjunction with, for example Fig. 9 As described at 914.

[0157] At 1140, the UE may map the downlink SPI associated with the downlink ESP packet with the uplink SPI indicated in the reply to the query. For example, the UE (e.g., using Fig.12 The communication manager 140 and / or SPI mapping component 1208 depicted in FIG. 1 may: map the downlink SPI associated with the downlink ESP packet with the uplink SPI indicated in the reply to the query, as described above in conjunction with, for example, Fig. 9 As described at 916.

[0158] In some aspects, the method 1100 includes: creating an uplink packet filter based at least in part on a downlink ESP packet, the uplink packet filter including: an SPI value set to an uplink SPI mapped to a downlink SPI associated with the downlink ESP packet, a destination IP address set to a source IP address in a header of the downlink ESP packet, a source IP address set to a destination IP address in a header of the downlink ESP packet, and a protocol value set to a protocol parameter in a header of the downlink ESP packet; and creating a QoS rule including the uplink packet filter, a QFI set to a QFI parameter in an SDAP header of the downlink ESP packet, and a priority value set to a predefined value. In some aspects, the method 1100 includes: receiving an uplink application packet; determining that the uplink application packet includes a parameter set that matches the uplink packet filter in the QoS rule; and associating the uplink application packet with the QFI in the QoS rule.

[0159] although Fig.11 Example blocks of method 1100 are shown, but in some aspects, method 1100 may include Fig.11 Those blocks depicted in the method 1100 may be additional blocks, fewer blocks, different blocks, or differently arranged blocks. Additionally or alternatively, two or more blocks in the blocks of the method 1100 may be executed in parallel.

[0160] Fig.121 is a schematic diagram of an example apparatus 1200 for wireless communication. Apparatus 1200 may be a UE, or a UE may include apparatus 1200. In some aspects, apparatus 1200 includes a receiving component 1202 and a transmitting component 1204, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1200 may communicate with another apparatus 1206 (such as a UE, a base station, or another wireless communication device) using receiving component 1202 and transmitting component 1204. As further shown, apparatus 1200 may include a communication manager 140. Communication manager 140 may include one or more of an SPI mapping component 1208 or an RQoS component 1210, etc.

[0161] In some aspects, the apparatus 1200 may be configured to perform one or more operations described herein in conjunction with FIGS. 7-9. Additionally or alternatively, the apparatus 1200 may be configured to perform one or more methods described herein, such as Fig.10 Method 1000, Fig.11 Method 1100, Fig.12 In some aspects, Fig.12 The apparatus 1200 and / or one or more components shown may include a combination of Figure 2 Additionally or alternatively, Fig.12 One or more of the components shown in the figure may be combined with Figure 2 In addition or alternatively, one or more components in the component set may be at least partially implemented as software stored in a memory. For example, a component (or a portion of a component) may be implemented as an instruction or code stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the function or operation of the component.

[0162] The receiving component 1202 may receive communications from the apparatus 1206, such as reference signals, control information, data communications, or a combination thereof. The receiving component 1202 may provide the received communications to one or more other components of the apparatus 1200. In some aspects, the receiving component 1202 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the apparatus 1200. In some aspects, the receiving component 1202 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of a UE are described.

[0163] The transmitting component 1204 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 1206. In some aspects, one or more other components of the device 1200 may generate communications and may provide the generated communications to the transmitting component 1204 for transmission to the device 1206. In some aspects, the transmitting component 1204 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 1206. In some aspects, the transmitting component 1204 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memory, or combinations thereof of the described UE. In some aspects, the transmit component 1204 can be collocated with the receive component 1202 in a transceiver.

[0164] The SPI mapping component 1208 may: store a record including a first set of attributes associated with an uplink ESP packet sent by an upper layer, wherein the first set of attributes includes an uplink SPI included in a header of the uplink ESP packet and a flag indicating that the uplink SPI is not mapped to a downlink SPI. The receiving component 1202 may: receive a downlink ESP packet associated with a second set of attributes, wherein the second set of attributes includes a downlink SPI included in a header of the downlink ESP packet. The SPI mapping component 1208 may: map the uplink SPI associated with the uplink ESP packet and the downlink SPI associated with the downlink ESP packet based at least in part on the record including the uplink SPI satisfying one or more conditions.

[0165] The RQoS component 1210 may: create an uplink packet filter based at least in part on the downlink ESP packet, the uplink packet filter comprising: an SPI value set to an uplink SPI mapped to a downlink SPI associated with the downlink ESP packet, a destination IP address set to a source IP address in a header of the downlink ESP packet, a source IP address set to a destination IP address in a header of the downlink ESP packet, and a protocol value set to a protocol parameter in a header of the downlink ESP packet. The RQoS component 1210 may: create a QoS rule comprising an uplink packet filter, a QFI set to a QFI parameter in a SDAP header of the downlink ESP packet, and a priority value set to a predefined value.

[0166] The RQoS 1208 may: receive an uplink application packet. The RQoS component 1208 may: determine that the uplink application packet includes a set of parameters that matches an uplink packet filter in a QoS rule. The RQoS component 1208 may: associate the uplink application packet with a QFI in the QoS rule.

[0167] The SPI mapping component 1208 may receive a downlink ESP packet, wherein the downlink ESP packet is associated with a local IP address, a remote IP address, and a downlink SPI that is not mapped to an uplink SPI. The SPI mapping component 1208 may provide a query including the local IP address, the remote IP address, and the downlink SPI to an upper layer. The SPI mapping component 1208 may receive a reply to the query, wherein the reply indicates an uplink SPI paired with the local IP address, the remote IP address, and the downlink SPI associated with the downlink ESP packet. The SPI mapping component 1208 may map the downlink SPI associated with the downlink ESP packet with the uplink SPI indicated in the reply to the query.

[0168] The communication manager 140 may determine that the DRB mapping rule associated with the QFI has changed based at least in part on receiving a configuration message or deriving a new QoS flow to DRB mapping rule. The sending component 1204 may avoid sending an end marker SDAP control PDU on a current DRB associated with the QFI based at least in part on determining that the QFI is not associated with an uplink packet filter.

[0169] Fig.12 The number and arrangement of components shown in are provided as examples. In practice, there may be Fig.12 Additional components, fewer components, different components, or components arranged differently than those shown in FIG. Fig.12 Two or more components shown in may be implemented in a single component, or in Fig.12 A single component shown in may be implemented as multiple distributed components. Additionally or alternatively, Fig.12 A set (one or more) of components shown in can perform the operations described in Fig.12 One or more functions performed by another set of components shown in FIG.

[0170] Fig.13 13 is a schematic diagram illustrating an example 1300 of a hardware implementation for an apparatus 1305 employing a processing system 1310. The apparatus 1305 may be a UE.

[0171] The processing system 1310 may be implemented using a bus architecture, represented generally by bus 1315. Bus 1315 may include any number of interconnecting buses and bridges, depending on the specific application and overall design constraints of the processing system 1310. Bus 1315 links together various circuits, including one or more processors and / or hardware components (represented by processor 1320), the components shown, and computer readable media / memory 1325. Bus 1315 may also link various other circuits such as timing sources, peripherals, voltage regulators, and / or power management circuits.

[0172] The processing system 1310 may be coupled to a transceiver 1330. The transceiver 1330 is coupled to one or more antennas 1335. The transceiver 1330 provides a means for communicating with various other devices over a transmission medium. The transceiver 1330 receives signals from the one or more antennas 1335, extracts information from the received signals, and provides the extracted information to the processing system 1310 (specifically, the receiving component 1202). In addition, the transceiver 1330 receives information from the processing system 1310 (specifically, the transmitting component 1204) and generates a signal to be applied to the one or more antennas 1335 based at least in part on the received information.

[0173] The processing system 1310 includes a processor 1320 coupled to a computer-readable medium / memory 1325. The processor 1320 is responsible for general processing, including executing software stored on the computer-readable medium / memory 1325. The software, when executed by the processor 1320, causes the processing system 1310 to perform various functions described herein for any particular device. The computer-readable medium / memory 1325 can also be used to store data that is manipulated by the processor 1320 when executing the software. The processing system also includes at least one of the components shown. A component can be a software module that runs in the processor 1320 and resides / is stored in the computer-readable medium / memory 1325, one or more hardware modules coupled to the processor 1320, or some combination thereof.

[0174] In some aspects, the processing system 1310 can be a component of the UE 120 and can include the memory 282, and / or at least one of the TX MIMO processor 266, the RX processor 258, and / or the controller / processor 280. In some aspects, the apparatus 1305 for wireless communication includes: means for storing a record including a first set of attributes associated with an uplink ESP packet sent by an upper layer of the UE 120, wherein the first set of attributes includes an uplink SPI included in a header of the uplink ESP packet and a flag indicating that the uplink SPI is not mapped to a downlink SPI; means for receiving a downlink ESP packet associated with a second set of attributes, wherein the second set of attributes includes a downlink SPI included in a header of the downlink ESP packet; and / or means for mapping an uplink SPI associated with the uplink ESP packet and a downlink SPI associated with the downlink ESP packet based at least in part on the record including the uplink SPI satisfying one or more conditions.

[0175] Additionally or alternatively, in some aspects, the apparatus 1305 for wireless communication includes: a unit for receiving a downlink ESP packet, wherein the downlink ESP packet is associated with a local IP address, a remote IP address, and a downlink SPI that is not mapped to an uplink SPI; a unit for providing a query to an upper layer including the local IP address, the remote IP address, and the downlink SPI; a unit for receiving a reply to the query from the upper layer, wherein the reply indicates an uplink SPI paired with the local IP address, the remote IP address, and the downlink SPI associated with the downlink ESP packet; and / or a unit for mapping the downlink SPI associated with the downlink ESP packet with the uplink SPI indicated in the reply to the query.

[0176] Additionally or alternatively, in some aspects, the apparatus 1305 for wireless communication includes: a unit for determining that a DRB mapping rule associated with a QFI has changed based at least in part on receiving a configuration message or deriving a new QoS flow to DRB mapping rule; and / or a unit for avoiding sending an end marker SDAP control PDU on a current DRB associated with the QFI based at least in part on determining that the QFI is not associated with an uplink packet filter.

[0177] The aforementioned means may be one or more of the aforementioned components of the processing system 1310 of the apparatus 1200 and / or the apparatus 1305 configured to perform the functions recited by the aforementioned means. As described elsewhere herein, the processing system 1310 may include the TX MIMO processor 266, the RX processor 258, and / or the controller / processor 280. In one configuration, the aforementioned means may be the TX MIMO processor 266, the RX processor 258, and / or the controller / processor 280 configured to perform the functions and / or operations recited herein.

[0178] Fig.13 is provided as an example. Other examples may differ from those described above. Fig.13 Examples described.

[0179] The following provides an overview of some aspects of the disclosure:

[0180] Aspect 1: A method of wireless communication performed by a UE, comprising: storing a record including a first set of attributes associated with an uplink ESP packet sent by an upper layer of the UE, wherein the first set of attributes includes an uplink SPI included in a header of the uplink ESP packet and a flag indicating that the uplink SPI is not mapped to a downlink SPI; receiving a downlink ESP packet associated with a second set of attributes, wherein the second set of attributes includes a downlink SPI included in a header of the downlink ESP packet; and mapping the uplink SPI associated with the uplink ESP packet and the downlink SPI associated with the downlink ESP packet based at least in part on the record including the uplink SPI satisfying one or more conditions.

[0181] Aspect 2: The method of Aspect 1, wherein mapping the uplink SPI associated with the uplink ESP packet and the downlink SPI associated with the downlink ESP packet comprises: updating a first attribute set to include the downlink SPI included in a second attribute set associated with the downlink ESP packet; and updating the flag to indicate that the uplink SPI is mapped to the downlink SPI.

[0182] Aspect 3: The method of any one of Aspects 1-2, wherein the one or more conditions include: a first set of attributes associated with the record satisfies one or more mapping criteria, and no other record includes a set of attributes that satisfies the one or more mapping criteria.

[0183] Aspect 4: The method of Aspect 3, wherein the one or more mapping criteria include: a first attribute set having a first local IP address that matches a second local IP address included in a second attribute set associated with the downlink ESP packet, and the first attribute set having a first remote IP address that matches a second remote IP address included in a second attribute set associated with the downlink ESP packet.

[0184] Aspect 5: The method of any one of Aspects 3-4, wherein the one or more mapping criteria include: the flag has a value indicating that the uplink SPI is not mapped to a downlink SPI.

[0185] Aspect 6: The method of any one of Aspects 3-5, wherein the one or more mapping criteria include: the downlink SPI is not mapped to any uplink SPI.

[0186] Aspect 7: The method of any one of Aspects 3-6, wherein the one or more conditions include: the downlink ESP packet associated with the downlink SPI is received before the expiration of a timer associated with the record including the first set of attributes.

[0187] Aspect 8: The method of any one of Aspects 1-7 further includes: creating an uplink packet filter based at least in part on the downlink ESP packet, the uplink packet filter including: an SPI value set to the uplink SPI mapped to the downlink SPI associated with the downlink ESP packet, a destination IP address set to the source IP address in the header of the downlink ESP packet, a source IP address set to the destination IP address in the header of the downlink ESP packet, and a protocol value set to a protocol parameter in the header of the downlink ESP packet; and creating a QoS rule, the QoS rule including the uplink packet filter, the QFI set to the QFI parameter in the SDAP header of the downlink ESP packet, and a priority value set to a predefined value.

[0188] Aspect 9: The method of Aspect 8 also includes: receiving an uplink application packet; determining that the uplink application packet includes a set of parameters that matches the uplink packet filter in the QoS rule; and associating the uplink application packet with the QFI in the QoS rule.

[0189] Aspect 10: The method of any one of Aspects 1-9 further includes: determining that the DRB mapping rules associated with the QFI have changed based at least in part on receiving a configuration message or exporting a new QoS flow to DRB mapping rule; and avoiding sending an end marker SDAP control PDU on the current DRB associated with the QFI based at least in part on determining that the QFI is not associated with an uplink packet filter.

[0190] Aspect 11: The method of any of Aspects 1-10, wherein the UE comprises a modem associated with a configuration that does not permit exchange of control information between the modem and the upper layer.

[0191] Aspect 12: The method of any one of Aspects 1-10, wherein the UE comprises a modem associated with a configuration permitting exchange of control information between the modem and the upper layer.

[0192] Aspect 13: The method of any of Aspects 1-12, wherein one or more of the uplink ESP packet or the downlink ESP packet are encapsulated in another packet.

[0193] Aspect 14: A method of wireless communication performed by a UE, comprising: receiving a downlink ESP packet, wherein the downlink ESP packet is associated with a local IP address, a remote IP address, and a downlink SPI that is not mapped to an uplink SPI; providing a query including the local IP address, the remote IP address, and the downlink SPI to an upper layer; receiving a reply to the query from the upper layer, wherein the reply indicates an uplink SPI paired with the local IP address, the remote IP address, and the downlink SPI associated with the downlink ESP packet; and mapping the downlink SPI associated with the downlink ESP packet with the uplink SPI indicated in the reply to the query.

[0194] Aspect 15: The method of Aspect 14 also includes: creating an uplink packet filter based at least in part on the downlink ESP packet, the uplink packet filter including: an SPI value set to the uplink SPI mapped to the downlink SPI associated with the downlink ESP packet, a destination IP address set to the source IP address in the header of the downlink ESP packet, a source IP address set to the destination IP address in the header of the downlink ESP packet, and a protocol value set to a protocol parameter in the header of the downlink ESP packet; and creating a QoS rule, the QoS rule including the uplink packet filter, the QFI set to the QFI parameter in the SDAP header of the downlink ESP packet, and a priority value set to a predefined value.

[0195] Aspect 16: The method of Aspect 15 also includes: receiving an uplink application packet; determining that the uplink application packet includes a parameter set that matches the uplink packet filter in the QoS rule; and associating the uplink application packet with the QFI in the QoS rule.

[0196] Aspect 17: The method of any one of Aspects 14-16, wherein the UE comprises a modem associated with a configuration permitting exchange of control information between the modem and the upper layer.

[0197] Aspect 18: A method of wireless communication performed by a UE, comprising: determining that a DRB mapping rule associated with a QFI has changed based at least in part on receiving a configuration message or exporting a new QoS flow to DRB mapping rule; and avoiding sending an end marker SDAP control PDU on a current DRB associated with the QFI based at least in part on determining that the QFI is not associated with an uplink packet filter.

[0198] Aspect 19: An apparatus for wireless communication at a device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods of Aspects 1-13.

[0199] Aspect 20: An apparatus for wireless communication, comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method of one or more of aspects 1-13.

[0200] Aspect 21: An apparatus for wireless communication, comprising at least one unit for performing one or more methods of aspects 1-13.

[0201] Aspect 22: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method of one or more of aspects 1-13.

[0202] Aspect 23: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform one or more of the methods of aspects 1-13.

[0203] Aspect 24: An apparatus for wireless communication at a device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods of Aspects 14-17.

[0204] Aspect 25: An apparatus for wireless communication, comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform one or more of the methods of aspects 14-17.

[0205] Aspect 26: An apparatus for wireless communication, comprising at least one unit for performing one or more of the methods of aspects 14-17.

[0206] Aspect 27: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method of one or more of aspects 14-17.

[0207] Aspect 28: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform one or more of the methods of aspects 14-17.

[0208] Aspect 29: An apparatus for wireless communication at a device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method of Aspect 18.

[0209] Aspect 30: An apparatus for wireless communication, comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method of Aspect 18.

[0210] Aspect 31: An apparatus for wireless communication, comprising at least one unit for performing the method of Aspect 18.

[0211] Aspect 32: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method of Aspect 18.

[0212] Aspect 33: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method according to Aspect 18.

[0213] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations are possible in light of the above disclosure or may be acquired from practice of the various aspects.

[0214] As used herein, the term "component" is intended to be interpreted broadly as a combination of hardware and / or hardware and software. "Software" should be interpreted broadly to mean instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads in execution, processes and / or functions, etc., regardless of whether they are referred to as software, firmware, middleware, microcode, hardware description languages ​​or other. As used herein, "processor" is implemented with a combination of hardware and / or hardware and software. It will be apparent that the system and / or method described herein can be implemented with a combination of hardware and / or hardware and software in different forms. The actual dedicated control hardware or software code for implementing these systems and / or methods is not limited to these aspects. Therefore, the operation and behavior of the system and / or method are described herein without citing a specific software code, because those skilled in the art will understand that software and hardware can be designed to implement the system and / or method based at least in part on the description herein.

[0215] As used herein, "satisfying a threshold" may mean, depending on the context, that a value is greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc.

[0216] Even if a specific combination of features is narrated in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features can be combined in a manner not specifically narrated in the claims and / or specifically disclosed in the specification. The disclosure of various aspects includes the combination of each dependent claim with each other claim in the claim set. As used herein, the phrase "at least one of" the item list refers to any combination of these items, including a single member. As an example, "at least one of a, b or c" is intended to cover a, b, c, a+b, a+c, b+c and a+b+c, and any combination with multiples of the same element (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c and c+c+c, or any other ordering of a, b and c).

[0217] Unless clearly described as such, otherwise the element, action or instruction used herein should not be interpreted as being key or necessary. In addition, as used herein, the article "a" and "an" are intended to include one or more items, and can be used interchangeably with "one or more". In addition, as used herein, the article "the" is intended to include one or more items mentioned in combination with the article "the", and can be used interchangeably with "one or more". In addition, as used herein, the term "set" and "group" are intended to include one or more items, and can be used interchangeably with "one or more". In the case of only being intended to a project, phrase "only one" or similar language is used. In addition, as used herein, the term "has", "have", "having" etc. are intended to be open terms, which do not limit the elements they modify (for example, "having" A elements can also have B). In addition, unless otherwise clearly stated, phrase "based on" is intended to mean "at least partially based on". Furthermore, as used herein, the term "or" when used in a series is intended to be inclusive and may be used interchangeably with "and / or" unless expressly stated otherwise (e.g., if used in conjunction with "either" or "only one of").

Claims

1. A user equipment (UE) for wireless communication, comprising: one or more memories; as well as One or more processors coupled to the one or more memories, the one or more processors being configured, individually or in combination, to: storing a record including a first set of attributes associated with an uplink Encapsulating Security Payload (ESP) packet sent by an upper layer of the UE, wherein the first set of attributes includes: an uplink Security Parameter Index (SPI) included in a header of the uplink ESP packet, and a flag including a value indicating that the uplink SPI is not mapped to a downlink SPI; receiving a downlink ESP packet associated with a second set of attributes and a downlink SPI, wherein the second set of attributes includes the downlink SPI included in a header of the downlink ESP packet; and Mapping the uplink SPI and the downlink SPI associated with the downlink ESP packet based at least in part on the record satisfying one or more conditions, wherein the one or more conditions include: the first set of attributes satisfying one or more mapping criteria and any additional records already stored by the UE do not satisfy the one or more mapping criteria.

2. The UE according to claim 1, wherein: To map the uplink SPI with the downlink SPI associated with the downlink ESP packet, the one or more processors are further configured to: updating the first set of attributes to include the downlink SPI included in a second set of attributes associated with the downlink ESP packet; and The flag is updated to indicate that the uplink SPI is mapped to a downlink SPI.

3. The UE according to claim 1, wherein: The one or more mapping criteria include: The first set of attributes has a first local Internet Protocol (IP) address that matches a second local IP address included in a second set of attributes associated with the downlink ESP packet, and The first set of attributes has a first remote IP address that matches a second remote IP address included in a second set of attributes associated with the downlink ESP packet.

4. The UE according to claim 1, wherein: The one or more mapping criteria include the flag having a value indicating that the uplink SPI is not mapped to a downlink SPI.

5. The UE according to claim 1, wherein: The one or more mapping criteria include that the downlink SPI is not mapped to any uplink SPI.

6. The UE according to claim 1, wherein: The one or more conditions also include: the downlink ESP packet associated with the downlink SPI is received before expiration of a timer associated with the record including a first set of attributes.

7. The UE according to claim 1, wherein: The one or more processors are further configured to: creating an uplink packet filter based at least in part on the downlink ESP packet, the uplink packet filter comprising: an SPI value set to the uplink SPI mapped to the downlink SPI associated with the downlink ESP packet, a destination Internet Protocol (IP) address set to a source IP address in a header of the downlink ESP packet, a source IP address set to the destination IP address in a header of the downlink ESP packet, and a protocol value set to a protocol parameter in a header of the downlink ESP packet; and A quality of service (QoS) rule is created, the QoS rule including the uplink packet filter, a QoS flow identifier (QFI) parameter set as a Service Data Adaptation Protocol (SDAP) QFI parameter in a header of the downlink ESP packet, and a priority value set to a predefined value.

8. The UE according to claim 7, wherein: The one or more processors are further configured to: receiving an uplink application packet; determining that the uplink application packet includes a set of parameters that matches the uplink packet filter in the QoS rule; as well as The uplink application packet is associated with the QFI in the QoS rule.

9. The UE according to claim 1, wherein: The one or more processors are further configured to: determining that a quality of service (QoS) flow to data radio bearer (DRB) mapping rule associated with a QoS flow identifier (QFI) has changed based at least in part on receiving a configuration message or deriving a new DRB mapping rule; as well as Based at least in part on determining that the QFI is not associated with an uplink packet filter, avoiding sending an end marker service data adaptation protocol (SDAP) control protocol data unit (PDU) on a current DRB associated with the QFI.

10. The UE according to claim 1, comprising: A modem is associated with a configuration that does not permit exchange of control information between the modem and the upper layer.

11. The UE according to claim 1, comprising: A modem is associated with a configuration that permits the exchange of control information between the modem and the upper layer.

12. The UE according to claim 1, wherein: One or more of the uplink ESP packet or the downlink ESP packet are encapsulated in another packet.

13. A method of wireless communication performed by a user equipment (UE), comprising: storing a record comprising a first set of attributes associated with an uplink Encapsulating Security Payload (ESP) packet sent by an upper layer of the UE, wherein the first set of attributes comprises an uplink Security Parameter Index (SPI) included in a header of the uplink ESP packet and a flag comprising a value indicating that the uplink SPI is not mapped to a downlink SPI; receiving a downlink ESP packet associated with a second set of attributes and a downlink SPI, wherein the second set of attributes includes the downlink SPI included in a header of the downlink ESP packet; and The uplink SPI and the downlink SPI associated with the downlink ESP packet are mapped based at least in part on the record satisfying one or more conditions, wherein the one or more conditions include: the first set of attributes satisfies one or more mapping criteria and any additional records already stored by the UE do not satisfy the one or more mapping criteria.

14. The method according to claim 13, wherein: Mapping the uplink SPI with the downlink SPI associated with the downlink ESP packet comprises: updating the first set of attributes to include the downlink SPI included in a second set of attributes associated with the downlink ESP packet; and The flag is updated to indicate that the uplink SPI is mapped to a downlink SPI.

15. The method according to claim 13, wherein: The one or more mapping criteria include: The first set of attributes has a first local Internet Protocol (IP) address that matches a second local IP address included in a second set of attributes associated with the downlink ESP packet, and The first set of attributes has a first remote IP address that matches a second remote IP address included in a second set of attributes associated with the downlink ESP packet.

16. The method according to claim 13, wherein: The one or more mapping criteria include the flag having a value indicating that the uplink SPI is not mapped to a downlink SPI.

17. The method according to claim 13, wherein: The one or more mapping criteria include that the downlink SPI is not mapped to any uplink SPI.

18. The method according to claim 13, wherein: The one or more conditions also include: the downlink ESP packet associated with the downlink SPI is received before expiration of a timer associated with the record including a first set of attributes.

19. The method according to claim 13, further comprising: creating an uplink packet filter based at least in part on the downlink ESP packet, the uplink packet filter comprising: an SPI value set to the uplink SPI mapped to the downlink SPI associated with the downlink ESP packet, a destination Internet Protocol (IP) address set to a source IP address in a header of the downlink ESP packet, a source IP address set to the destination IP address in a header of the downlink ESP packet, and a protocol value set to a protocol parameter in a header of the downlink ESP packet; and A quality of service (QoS) rule is created, the QoS rule including the uplink packet filter, a QoS flow identifier (QFI) parameter set as a Service Data Adaptation Protocol (SDAP) QFI parameter in a header of the downlink ESP packet, and a priority value set to a predefined value.

20. The method according to claim 19, further comprising: receiving an uplink application packet; determining that the uplink application packet includes a set of parameters that matches the uplink packet filter in the QoS rule; as well as The uplink application packet is associated with the QFI in the QoS rule.

21. The method of claim 13, further comprising: determining that a quality of service (QoS) flow to data radio bearer (DRB) mapping rule associated with a QoS flow identifier (QFI) has changed based at least in part on receiving a configuration message or deriving a new DRB mapping rule; as well as Based at least in part on determining that the QFI is not associated with an uplink packet filter, avoiding sending an end marker service data adaptation protocol (SDAP) control protocol data unit (PDU) on a current DRB associated with the QFI.

22. The method according to claim 13, wherein: The UE includes a modem that is associated with a configuration that does not permit exchange of control information between the modem and the upper layer.

23. The method according to claim 13, wherein: The UE includes a modem associated with a configuration permitting exchange of control information between the modem and the upper layers.

24. The method according to claim 13, wherein: The upper layer includes an application layer.

25. The method of claim 13, wherein: One or more of the uplink ESP packet or the downlink ESP packet are encapsulated in another packet.

26. The method according to claim 25, wherein: The another packet in which one or more of the uplink ESP packet or the downlink ESP packet is encapsulated comprises a User Datagram Protocol (UDP) packet.

27. An apparatus for wireless communication, the apparatus comprising: means for storing a record comprising a first set of attributes associated with an uplink Encapsulating Security Payload (ESP) packet sent by an upper layer of the apparatus, wherein an uplink Security Parameter Index (SPI) is associated with the uplink ESP packet and included in a header of the uplink ESP packet, and wherein the first set of attributes comprises: the uplink SPI, and a flag comprising a value indicating that the uplink SPI is not mapped to a downlink SPI; means for receiving a downlink ESP packet associated with a second set of attributes and a downlink SPI, wherein the second set of attributes includes the downlink SPI included in a header of the downlink ESP packet; and A unit for mapping the uplink SPI and the downlink SPI associated with the downlink ESP packet based at least in part on the record satisfying one or more conditions, wherein the one or more conditions include: the first set of attributes satisfies one or more mapping criteria and any additional records already stored by the device do not satisfy the one or more mapping criteria.

28. A non-transitory computer-readable medium storing an instruction set for wireless communication, wherein the instruction set, when executed by one or more processors of a user equipment (UE), causes the UE to at least perform the following operations: storing a record comprising a first set of attributes associated with an uplink Encapsulating Security Payload (ESP) packet sent by an upper layer of the UE, wherein: an uplink security parameter index (SPI) associated with the uplink ESP packet and included in a header of the uplink ESP packet, and wherein the first set of attributes includes: the uplink SPI, and a flag including a value indicating that the uplink SPI is not mapped to a downlink SPI; receiving a downlink ESP packet associated with a second set of attributes and a downlink SPI, wherein the second set of attributes includes the downlink SPI included in a header of the downlink ESP packet; and The uplink SPI and the downlink SPI associated with the downlink ESP packet are mapped based at least in part on the record satisfying one or more conditions, wherein the one or more conditions include: the first set of attributes satisfies one or more mapping criteria and any additional records already stored by the UE do not satisfy the one or more mapping criteria.

Images