Multimedia priority services over wireless local area networks

Abstract

The invention relates to multimedia priority services over a wireless local area network. Apparatuses and components are disclosed, including apparatuses, systems, and methods for providing multimedia priority service (MPS) prioritization for a network via wireless local area network (WLAN) access.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to U.S. Provisional Application No. 63 / 513,774, filed on July 14, 2023, and entitled “Multimedia Priority Service over Wireless Local Area Network,” and priority to U.S. Non-Provisional Application No. 18 / 744,474, filed on June 14, 2024, and entitled “Multimedia Priority Service over Wireless Local Area Network,” the disclosures of both of which are incorporated herein by reference in their entirety for all purposes. Technical Field

[0003] The present application relates to the field of wireless technology, and in particular to multimedia priority services on wireless local area networks. Background Art

[0004] The 3rd Generation Partnership Project (3GPP) network uses a core network to provide services to users. As 3GPP networks develop, additional ways to access the core network to provide services to users have been developed. One of the ways that users can access the core network is through a wireless local area network (WLAN). WLAN can be hosted in multiple locations and can provide an alternative means of accessing the core network and, in some instances, provide improved services from the core network. BRIEF DESCRIPTION OF THE DRAWINGS

[0005] Figure 1 An example system arrangement with untrusted wireless local area network (WLAN) integration is illustrated in accordance with some embodiments.

[0006] Figure 2 An example system arrangement with trusted WLAN integration according to some embodiments is illustrated.

[0007] Figure 3 A table illustrating example parameters that may be included in a fifth generation quality of service information (5G_QOS_INFO) notification payload according to some embodiments.

[0008] Figure 4 An example signaling diagram of a registration procedure according to some embodiments is illustrated.

[0009] Figure 5 An example system arrangement is illustrated that may provide end-to-end prioritization for Multimedia Priority Service (MPS) via WLAN according to some embodiments.

[0010] Figure 6 A table showing example quality of service (QoS) information to differentiated services code point (DSCP) value mappings is illustrated in accordance with some embodiments.

[0011] Figure 7 A table showing example DSCP to QoS information mappings according to some embodiments is illustrated.

[0012] Figure 8 A first portion of a table showing example quality of service class identifier (QCI) to DSCP marking recommendations is illustrated in accordance with some embodiments.

[0013] Fig. 9 Illustrated according to some embodiments Figure 8 The second part of the table.

[0014] Fig.10 A table showing example DSCP to WLAN protocol mappings according to some embodiments is illustrated.

[0015] Fig.11 A first portion of an example signaling diagram of a device-centric QoS management method according to some embodiments is illustrated.

[0016] Fig.12 Illustrated according to some embodiments Fig.11 The second part of the example signaling diagram.

[0017] Fig.13 A first portion of an example signaling diagram of a network-centric QoS management method according to some embodiments is illustrated.

[0018] Fig.14 Illustrated according to some embodiments Fig.13 The second part of the example signaling diagram.

[0019] Fig.15 Example procedures to be performed by a user equipment (UE) according to some embodiments are illustrated.

[0020] Fig.16 Example procedures to be performed by a network structure according to some embodiments are illustrated.

[0021] Fig.17 Example procedures to be performed by a UE according to some embodiments are illustrated.

[0022] Fig.18 An example UE according to some embodiments is illustrated.

[0023] Fig.19 An example next generation NodeB (gNB) according to some embodiments is illustrated. DETAILED DESCRIPTION

[0024] The following specific embodiments relate to the accompanying drawings. The same figure numbers may be used to identify the same or similar elements in different drawings. In the following description, specific details, such as specific structures, architectures, interfaces, technologies, etc., are set forth for the purpose of illustration rather than limitation, so as to provide a thorough understanding of various aspects of various embodiments. However, it is obvious to those skilled in the art who benefit from the present disclosure that various aspects of various embodiments can be practiced in other examples that deviate from these specific details. In some instances, descriptions of well-known devices, circuits, and methods are omitted so as not to obscure the descriptions of various embodiments due to unnecessary details. For the purposes of this document, the phrase "A or B" refers to (A), (B), or (A and B); and the phrase "based on A" refers to "based at least in part on A", for example, it can be "based only on A" or it can be "based in part on A".

[0025] The following is a glossary of terms that may be used in this disclosure.

[0026] As used herein, the term "circuit" refers to, is part of, or includes a hardware component such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) or a memory (shared, dedicated, or group) configured to provide the described functions, an application specific integrated circuit (ASIC), a field programmable device (FPD) (e.g., a field programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high capacity PLD (HCPLD), a structured ASIC, or a programmable system on chip (SoC)), a digital signal processor (DSP), etc. In some embodiments, the circuit may execute one or more software or firmware programs to provide at least some of the described functions. The term "circuit" may also refer to a combination of one or more hardware elements and a program code for performing the functions of the program code (or a combination of circuits used in an electrical or electronic system). In these embodiments, the combination of hardware elements and program code may be referred to as a specific type of circuit.

[0027] As used herein, the term "processor circuit" refers to, is part of, or includes a circuit capable of sequentially and automatically performing a series of arithmetic or logical operations or recording, storing, or transmitting digital data. The term "processor circuit" may refer to an application processor, a baseband processor, a central processing unit (CPU), a graphics processing unit, a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, or any other device capable of executing or otherwise operating computer-executable instructions (such as program code, software modules, and / or functional processes).

[0028] As used herein, the term "interface circuit" refers to a circuit that enables, is a part of, or includes information exchange between two or more components or devices. The term "interface circuit" may refer to one or more hardware interfaces, such as a bus, an I / O interface, a peripheral component interface, a network interface card, etc.

[0029] As used herein, the term "user equipment" or "UE" refers to a device that has radio communication capabilities and can describe a remote user of network resources in a communication network. In addition, the terms "user equipment" or "UE" may be considered synonymous and may be referred to as a client, mobile phone, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc. In addition, the term "user equipment" or "UE" may include any type of wireless / wired device or any computing device that includes a wireless communication interface.

[0030] As used herein, the term "computer system" refers to any type of interconnected electronic devices, computer devices, or components thereof. Additionally, the term "computer system" or "system" may refer to various components of a computer that are communicatively coupled to one another. Furthermore, the term "computer system" or "system" may refer to multiple computer devices or multiple computing systems that are communicatively coupled to one another and configured to share computing resources or networked resources.

[0031] As used herein, the term "resource" refers to a physical or virtual device, a physical or virtual component within a computing environment, or a physical or virtual component within a specific device, such as a computer device, a mechanical device, a memory space, a processor / CPU time, a processor / CPU usage, a processor and accelerator load, a hardware time or usage, a power supply, an input / output operation, a port or a network socket, a channel / link allocation, throughput, memory usage, storage, a network, a database and an application, a unit of work, etc. "Hardware resources" may refer to computing, storage or network resources provided by physical hardware elements. "Virtualized resources" may refer to computing, storage or network resources provided by a virtualized infrastructure to an application, a device, a system, etc. The term "network resources" or "communication resources" may refer to resources that a computer device / system can access via a communication network. The term "system resources" may refer to any kind of shared entity that provides a service, and may include computing resources or network resources. System resources may be considered as a set of coherent functions, network data objects or services that can be accessed through a server, wherein such system resources reside on a single host or multiple hosts and can be clearly identified.

[0032] As used herein, the term "channel" refers to any tangible or intangible transmission medium for transmitting data or data streams. The term "channel" may be synonymous or equivalent to "communication channel", "data communication channel", "transmission channel", "data transmission channel", "access channel", "data access channel", "link", "data link", "carrier", "radio frequency carrier" or any other similar term representing a path or medium through which data is transmitted. In addition, as used herein, the term "link" refers to a connection made between two devices for transmitting and receiving information.

[0033] As used herein, the terms "instantiate," "instantiate," and the like refer to the creation of an instance. "Instance" also refers to a specific occurrence of an object, which may occur, for example, during the execution of program code.

[0034] The term "connected" may mean that two or more elements at a common communication protocol layer have an established signaling relationship with each other through a communication channel, link, interface, or reference point.

[0035] As used herein, the term "network element" refers to physical or virtualized equipment or infrastructure for providing wired or wireless communication network services. The term "network element" may be considered synonymous with or referred to as a networked computer, networking hardware, network equipment, network node, virtualized network function, etc.

[0036] The term "information element" refers to a structural element that contains one or more fields. The term "field" refers to the individual contents of an information element, or a data element that contains the contents. An information element may include one or more additional information elements.

[0037] When the access to the Evolved Packet Core (EPC) / Fifth Generation Core (5GC) is a wireless local area network (WLAN), it is necessary to support multimedia priority service (MPS) communications. For example, a user equipment (UE) may be able to access the EPC and / or 5GC. It may be beneficial to support MPS for UEs accessing the EPC and / or 5GC. A UE with MPE prioritization can prioritize services (including transmissions and / or signals associated with the service) over other UEs without MPE prioritization. Therefore, if the service becomes limited for some reason (such as in a disaster scenario), the network including the EPC and / or 5GC can prioritize the services of the UE with MPE prioritization to ensure and / or increase the opportunity to provide services to the UE with MPE prioritization. In some instances, the services prioritized for the UE with MPE prioritization may be limited to certain services, such as multimedia services, voice services, video call services, and / or data transmission sessions, and / or any communications initiated by the UE.

[0038] Support for MPS when the UE has WLAN access may be important during disaster scenarios, such as when the 3rd Generation Partnership Project (3GPP) access network (Long Term Evolution (LTE) and New Radio (NR)) is unavailable or degraded. In some cases, WLAN may be the only available access (e.g., inside buildings, hotels, airports, shopping malls, and stadiums), and therefore may be critical for MPS communications. For example, for disaster scenarios, providing prioritized services to UEs with MPS prioritization may be beneficial. Providing priority to UEs with MPS prioritization during disaster scenarios may ensure that services are provided to UEs with MPS prioritization during disaster scenarios.

[0039] 3GPP enables support for MPS for multimedia telephony (MMTEL) voice / video calls, and supports MPS for data transmission service sessions when accessing EPC / 5GC via a trusted or untrusted WLAN. For example, it has been proposed to provide support for MPS to EPC and / or 5GC via WLAN. MPS can be applied to voice and / or video call services, and / or data transmission service sessions. In some embodiments, other services of the UE (including multimedia services, voice services, video call services, and / or data transmission services) can support MPS.

[0040] The new work items were agreed upon in the Core Network and Terminal (CT) Working Group (WG) C1-234365 with certain objectives. The first objective may be to provide an indication of MPS authorization from the UE to the Trusted WLAN Access Network (TWAN), Evolved Packet Data Gateway (ePDG), and Non-3GPP Interconnect Function (N3IWF) for prioritization processing of the UE. The second objective may be to support transport level (e.g., Differentiated Services Code Point (DSCP)) MPS priority for signaling, MPS for Data Transport Service (DTS) sessions, and MPS MMTEL voice / video sessions. The third objective may be to support congestion control and retry timer exemption (if applicable) for 3GPP core network access via non-3GPP access networks for MPS subscribed UEs attached via WLAN.

[0041] WLAN Integration in Fifth Generation Systems (5GS)

[0042] 3GPP defines support for integrating untrusted and trusted WLAN networks with 5GS through N3IWF and Trusted Non-3GPP Gateway Function (TNGF), respectively. For example, some 5GS may allow UEs to connect to the core network of 5GS through N3IWF and / or TNGF. Figure 1 An example system arrangement 100 with untrusted WLAN integration is illustrated in accordance with some embodiments. Figure 2An example system arrangement 200 with trusted WLAN integration according to some embodiments is illustrated. It should be appreciated that in some examples, features of system arrangement 100 and system arrangement 200 may be implemented by a single system, where the system may provide both untrusted WLAN integration and trusted WLAN integration.

[0043] For the integration of untrusted and trusted WLAN networks, the transmission of non-access stratum (NAS) signaling and user plane data can be completed through an Internet Protocol Security (IPsec) tunnel established on WLAN-NWu between N3IWF and UE and / or on NWt between TNGF and UE. For example, the system arrangement 100 may include UE 102 and N3IWF 104. UE 102 may include UE1800 ( Fig.18 ) features. UE 102 may be part of a non-3GPP network, and NW3IWF 104 may be part of a home public land mobile network (HPLMN). NWu interface 106 may extend between UE 102 and N3IWF 104. One or more IPsec tunnels may be established on NWu interface 106 between UE 102 and N3IWF 104 for transmission of NAS signaling and / or user plane data.

[0044] The system arrangement 200 may include a UE 202 and a TNGF 204. The UE 202 may include a UE 1800 ( Fig.18 ) features. TNGF 204 may be part of the HPLMN, while UE 202 may be outside the HPLMN. NWt interface 206 may extend between UE 202 and TNGF 204. One or more IPsec tunnels may be established on the NWt interface 206 between UE 202 and TNGF 204 for transmission of NAS signaling and / or user plane data.

[0045] A signaling IPsec security association (SA) is established over the WLAN to carry NAS messaging. For example, a signaling IPsec SA may be established to carry NAS messaging via the NWu interface 106 and / or the NWt interface 206. One or more IPsec sub-SAs are established over the WLAN to carry user plane traffic. For example, one or more IPsec sub-SAs may be established to carry user plane traffic via the NWu interface 106 and / or the NWt interface 206.

[0046] The N3IWF or TNGF may decide to associate one or more fifth generation (5G) quality of service (QoS) flows for a packet data unit (PDU) session with an IPsec sub-SA. Mapping of 5G QoS flows to IPsec sub-SAs may be implemented. QoS flows may be assigned after the IP Sec sub-SA is created. The 5G QoS model on 3GPP access may also be followed on non-3GPP access. QoS flows identified by QoS flow identifiers (QFIs) may also define the finest granularity of QoS differentiation on non-3GPP access.

[0047] For a multiple access (MA) PDU session, a QoS flow can be access agnostic and can support the same QoS when the traffic is distributed over 3GPP access and / or non-3GPP access. Both guaranteed bit rate (GBR) QoS flows and non-GBR QoS flows can be carried over non-3GPP access. A 5G QoS flow can have the following related information.

[0048] For example, a 5G QoS flow may have a QoS profile. The QoS profile may specify 5G QoS parameters and QoS characteristics for the flow. The QoS profile may be provided to a 3GPP access and / or N3IWF / TNGF. For example, the QoS profile may be provided to the 3GPP access point 108 of the system arrangement 100, the 3GPP access point 208 of the system arrangement 200, the N3IWF 104, and / or the TNGF 204. For non-GBR flows, if the UE is registered on a 3GPP access and a non-3GPP access, the QoS profile may be sent to both accesses. For example, when the UE is registered for both a 3GPP access and a non-3GPP access, for non-GBR flows, the QoS profile may be provided to the 3GPP access point 108 of the system arrangement 100 and the untrusted non-3GPP access point 110, and / or to the 3GPP access point 208 and the trusted non-3GPP access point 210 of the system arrangement 200. For GBR flows, the QoS profile may be sent to only one access based on a policy and charging control (PCC) rule. For example, based on the PCC rules, for GBR flows, a QoS profile may be provided to the 3GPP access point 108 or the untrusted non-3GPP access point 110 of the system arrangement 100, and / or to the 3GPP access point 208 or the trusted non-3GPP access point 210 of the system arrangement 200. GBR flows may not support traffic splitting.

[0049] A 5G QoS flow may have one or more QoS rules. These rules may specify packet filters to map uplink (UL) traffic to QoS flows within a PDU session. QoS rules may be explicitly signaled to the UE, derived by the UE by applying reflective QoS control, or pre-configured in the UE. For example, QoS rules may be explicitly signaled to UE 102 and / or UE 202, derived by UE 102 and / or UE 202 via applying reflective QoS control, or pre-configured in UE 102 and / or UE 202.

[0050] A 5G QoS flow may have a QoS flow description. The QoS flow description may be optional. The QoS flow description may specify QoS parameters for the flow. The QoS flow description may be sent to the UE to provide QoS differentiation for the flow. For example, the QoS flow description may be sent to UE 102 and / or UE 202.

[0051] A 5G QoS flow may have one or more packet detection rules (PDRs). These rules may specify packet filters to map incoming packets at a user plane function (UPF) to an N3 / N9 tunnel established with an N3IWF / TNGF. For example, the system arrangement 100 may have an N3 tunnel 112 established between an N3IWF 104 and an UPF 114 of the system arrangement 100. The system arrangement 200 may have an N3 tunnel 212 established between a TNGF 204 and an UPF 214 of the system arrangement 200. The PDR may specify packet filters for mapping incoming packets to the N3 tunnel 112 and / or the N3 tunnel 212. The PDR may include a multiple access rule (MAR) for an MA PDU session, which indicates an access service steering, switching, and splitting (ATSSS) steering mode and steering functionality.

[0052] QoS signaling at N3IWF / TNGF for WLAN

[0053] During PDU session establishment, the N3IWF / TNGF may determine the number of user plane IPsec sub-SAs to be established with the UE and the QoS profile associated with each sub-SA. For example, the N3IWF 104 may determine the number of user plane IPsec sub-SAs to be established with the UE 102, and / or the TNGF 204 may determine the number of user plane IPsec sub-SAs to be established with the UE 202. One IPsec sub-SA may be associated with one or more QoS flows of a PDU session.

[0054] An Internet Key Exchange (IKE) Create_Child_SA request may be sent to a UE to establish a child SA, and may include a 5G_QOS_INFO notification payload specifying QoS specific parameters. For example, an IKE Create_Child_SA request may be sent to UE 102 and / or UE 202 to establish a child SA. The IKE Create_Child_SA request may include a 5G_QOS_INFO notification payload. Figure 3 Table 300 illustrates example parameters that may be included in a 5G_QOS_INFO notification payload according to some embodiments. Specifically, an IKE Create_Child_SA request sent to a UE may include a 5G_QOS_INFO notification payload that may have one or more of the parameters illustrated by Table 300.

[0055] The N3IWF or TNGF may implement a specific method to associate the DSCP value with the IPsec sub-SA. For example, N3IWF104( Figure 1 ) and / or TNGF 204( Figure 2 ) may associate a DSCP value with an IPsec sub-SA. The UE and N3IWF / TNGF may mark all Internet Protocol (IP) packets sent over the sub-SA with the associated DSCP value (if any). For example, UE 102 ( Figure 1 ), UE 202( Figure 2 ), N3IWF 104 and / or TNGF 204 may mark IP packets sent via the sub-SA using the associated DSCP value.

[0056] If multiple QoS flows are aggregated into the same IPsec sub-SA, the TNGF may derive QoS characteristics and / or GBR QoS flow information of the aggregated flows based on the QoS profiles of the individual flows. For example, if multiple QoS flows are aggregated into the same IPsec sub-SA, the TNGF 204 may derive QoS characteristics and / or GBR QoS flow information, wherein the QoS characteristics and / or GBR QoS flow information of the aggregated flows may be derived based on the QoS profiles of the individual flows.

[0057] Multimedia Priority Service (MPS) over 3GPP access in Evolved Packet System (EPS) / 5GS

[0058] MPS support for 3GPP access may be available in EPS / 5GS and Internet Protocol Multimedia Subsystem (IMS) Core Network (CN) as follows. A UE with MPS subscription may send a priority Radio Resource Control (RRC) establishment cause based on the MPS subscription information stored in the Universal Subscriber Identity Module (USIM) during the attach / initial registration procedure. Upon reception, the Evolved NodeB (eNB) / Radio Access Network (RAN) and Mobility Management Entity (MME) / Access and Mobility Management Function (AMF) may prioritize the UE.

[0059] MME / AMF may receive MPS subscription information from the Home Subscriber Service (HSS) / Unified Data Management (UDM) of the MPS-subscribed UE during the attach / initial registration procedure. Priority may be provided to user plane resources under the control of the 3GPP system based on the (HSS / UDM) subscription-based MPS-specific QoS parameters assigned to the default bearer / QoS flow carrying the MPS service, or the MPS-specific QoS parameters selected by the Policy and Charging Rules Function (PCRF) / Policy Control Function (PCF) and provided to the EPC / 5GC.

[0060] Features of MPS over WLAN

[0061] Updates to support MPS over WLAN in EPS / 5GS may include the following. For example, a UE with MPS subscription may indicate its MPS capability during the attach / initial registration procedure. This enables TWAN / Trusted Non-3GPP Access Network (TNAN) (e.g., trusted WLAN) and ePDG / N3IWF (e.g., untrusted WLAN) to prioritize MPS-subscribed UEs based on operator policy during authentication or after the network has successfully authenticated the UE. Updates to allow 3GPP networks to send the UE's MPS subscription information (from HSS / UDM) to trusted WLAN, untrusted WLAN, and ePDG / N3IWF may support MPS over WLAN in EPS and / or 5GS.

[0062] Additionally, updates to the 3GPP capability to communicate per-packet data network (PDN) connection / PDU session and per-bearer / QoS flow QoS treatment to WLAN may support MPS on WLAN in EPS and / or 5GS. This may include QoS treatment of media associated with all authorized MPS sessions (e.g., regardless of the UE's subscription to MPS). DSCP may be a mechanism for QoS differentiation by which WLAN may apply any WLAN QoS mechanism. Application of DSCP between UE, WLAN, and 3GPP network may also be implemented.

[0063] Methods for MPS over WLAN - General Concepts

[0064] Updates to N3IWF may include the following. If the network supports MPS, MPS subscription may allow users to receive priority services. The same MPS subscription may apply to access via 3GPP access and non-3GPP access via WLAN. Service users using UEs that support connection via trusted or untrusted non-3GPP access via WLAN may support MPS.

[0065] For WLAN access, the UE may inform the TNAN / N3IWF of its MPS subscription before the NAS Registration Request. Based on operator policy, the TNAN / N3IWF may use this indication to provide priority treatment to the UE in case of congestion / overload before receiving a NAS Registration Request with MPS Priority Establishment Cause.

[0066] Further updates to the N3IWF may include implementing QoS corresponding to N3 packet markings (e.g., DSCP), thereby taking into account QoS requirements associated with such markings received via N2. The QoS may include a 5G QoS identifier (5QI), a priority level (if explicitly signaled), and optionally an Assigned and Reservation Priority (ARP) priority level. Based on operator policy and / or regional / national regulations, the N3IWF may apply a different DSCP value to the outer Encapsulating Security Payload (ESP) tunnel packet than the DSCP value of the inner IP packet.

[0067] Another update may include packet marking in the downlink and uplink on N2 and N3, for example, setting the DSCP value based on the establishment cause on N2 and based on the 5QI, priority level (if explicitly signaled), and optionally the ARP priority level on N3.

[0068] Other updates may include the following. For example, the UE may be made aware of the WLAN MPS capabilities as shared in the Registration Accept in 3GPP to know whether it can use MPS in the next access. Similar to the Configuration Update Command (CUC) in 3GPP, there is no mechanism (notification) to dynamically update the MPS in the WLAN. In addition, authentication and authorization may be updated, such as if the MPS-specific authentication / authorization fails, there may be an explicit indication returned to the UE. The MPS priority may be shared with the N3IWF from the UDM / Authentication Service Function (AUSF).

[0069] Method for MPS over WLAN - Registration Procedure

[0070] Figure 4An example signaling diagram 400 of a registration procedure according to some embodiments is illustrated. For example, according to some embodiments, the registration procedure may be performed as a UE (such as UE 102 ( Figure 1 ) and / or UE 202( Figure 1 )) is performed as part of registering to the EPC and / or 5GC network via WLAN access. Signaling diagram 400 illustrates operations and / or signals that may be exchanged between elements of the EPC and / or 5GC network as part of a registration procedure.

[0071] Signaling diagram 400 may include UE 402. UE 402 may include UE 102 ( Figure 1 ), UE 202( Figure 2 ) and / or UE 1800( Fig.18 ) features. The registration procedure illustrated by the signaling diagram 400 may be performed to register the UE 402 to the EPC and / or 5GC network via WLAN access.

[0072] The signaling diagram 400 may include an untrusted WLAN access point 404. The untrusted WLAN access point 404 may include an untrusted non-3GPP access point 110 ( Figure 1 ) features. The untrusted WLAN access point 404 may not be controlled by the same operator as the operator of the EPC and / or 5GC network. The untrusted WLAN access point 404 may provide access to the EPC and / or 5GC network via WLAN. Since the untrusted WLAN access point 404 is not trusted by the EPC and / or 5GC network, the untrusted WLAN access point 404 may be located outside the HPLMN including the EPC and / or 5GC network, and may have a higher security standard for accessing the EPC and / or 5GC network than a trusted WLAN access point.

[0073] The signaling diagram 400 may include an N3IWF 406. The N3IWF 406 may include an N3IWF 104 ( Figure 1 The N3IWF 406 may act as a gateway for the EPC and / or 5GC network and may provide an N3 interface (such as an N3 tunnel 112 ( Figure 1 )) and N2 interfaces. N3IWF 406 can facilitate authentication and / or registration of UEs connected to the EPC and / or 5GC network via the untrusted WLAN access point 404. In addition, services from the EPC and / or 5GC network can be provided to the UE connected via the untrusted WLAN access point 404 through N3IWF 406.

[0074] In other embodiments, UE 402 may access the WLAN through a trusted WLAN access point, such as trusted non-3GPP access point 210 ( Figure 2 )) is connected to the EPC and / or 5GC network. In these embodiments, the untrusted WLAN access point 404 may be replaced by a trusted WLAN access point. The trusted WLAN access point may be controlled by the same operator as the operator of the EPC and / or 5GC network. The trusted WLAN access point may be located within the HPLMN and may provide one or more of the services of the untrusted WLAN access point 404 to the UE. The trusted WLAN access point may perform one or more of the operations and / or receive one or more of the signals / messages, which are described as being implemented by the untrusted WLAN access point 404.

[0075] In addition, in an embodiment where the UE is connected to the EPC and / or 5GC network through a trusted WLAN access point, the N3IWF 406 may be provided by a TNGF (such as TNGF 204 ( Figure 2 )) instead. TNGF can act as a gateway for the EPC and / or 5GC network and can provide an N3 interface (such as N3 tunnel 212 ( Figure 2 )) and N2 interface. The TNGF may perform one or more of the operations and / or receive one or more of the signals / messages, which are described as being implemented by the N3IWF 406.

[0076] The signaling diagram 400 may include an AMF 408. The AMF 408 may be a control plane function that may provide one or more services, such as registration management, reachability management, connection management, and / or mobility management. The AMF 408 may facilitate registration of the UE with the EPC and / or 5GC network.

[0077] The signaling diagram 400 may include an AUSF 410. The AUSF 410 may facilitate authentication of a UE connected to an EPC and / or 5GC network.

[0078] In 412, UE 402 may connect to untrusted WLAN access point 404. For example, UE 402 may establish a connection with untrusted WLAN access point 404 through signal exchange. UE 402 may obtain an IP address from untrusted WLAN access point 404, and UE 402 may use the IP address to exchange signals with untrusted WLAN access point 404.

[0079] When the UE decides to attach to the 5GC network, a N3IWF in the 5G public land mobile network (PLMN) is selected. For example, UE 402 may determine that UE 402 will attach to the EPC and / or 5GC network for service. Based on UE 402's determination that UE 402 will attach to the EPC and / or 5GC network, UE 402 may select an N3IWF to connect to in 414. The N3IWF that UE 402 selects to connect to may be predefined, may be based on the characteristics of UE 402, and / or may be based on the service that UE 402 is attaching to the EPC and / or 5GC network. In the illustrated embodiment, UE 402 may choose to attach to N3IWF 406. UE 402 may obtain an IP address from N3IWF 406, and UE 402 may use the IP address to exchange signals with N3IWF 406.

[0080] The UE may proceed to establish an IPsec security association (SA) with the selected N3IWF by initiating an IKE initial exchange in accordance with RFC 7296. For example, UE 402 may initiate an IKE exchange in 416. The UE may initiate an IKE_AUTH exchange by sending an IKE_AUTH request message. For example, as part of the IKE exchange in 416, UE 402 may transmit an IKE authentication (IKE_AUTH) request message to N3IWF 406. If the UE has an MPS subscription, the UE may include a notification payload indicating its MPS subscription in the IKE_AUTH request. For example, UE 402 may include an indication in the IKE_AUTH request message that UE 402 has MPS prioritization. In some embodiments, UE 402 may have MPS prioritization based on UE 402 subscribing to MPS. UE 402 may include an indication that UE 402 has MPS prioritization in the notification payload of the IKE_AUTH request message.

[0081] The N3IWF may respond with an IKE_AUTH response message, which may include an EAP-Request / 5G-Start packet. For example, the N3IWF 406 may provide an IKE_AUTH response message to the UE 402. The IKE_AUTH response message may be provided in response to the IKE_AUTH request message. The IKE_AUTH response message may include an Extensible Authentication Protocol Request (EAP-Request) / 5G-Start packet. For example, the EAP-Request / 5G-Start packet may notify the UE to initiate an EAP-5G session to start sending NAS messages encapsulated within the EAP-5G packet.

[0082] In the case of trusted WLAN access, if the UE has an MPS subscription, the UE may also include an indication of its MPS subscription in the username portion of the network access identifier (NAI). For example, as part of 416, UE 402 may provide the NAI to N3IWF 406. In an embodiment where UE 402 is utilizing a trusted WLAN access point to access an EPC / 5GC network, UE 402 may include an indication that UE 402 has MPS prioritization within the username portion of the NAI. Based on operator policy, after receiving an indication of MPS subscription from the UE, the TNAN may prioritize the UE. For example, a trusted WLAN access point and a TNGF may be part of the TNAN. After the WLAN access point receives an indication that the UE has MPS prioritization, the TNAN may prioritize the UE based on operator policy (such as prioritizing signals related to the UE).

[0083] The UE may send an IKE_AUTH request including an EAP-Response / 5G-NAS packet including access network (AN) parameters (AN parameters) and a registration request message. For example, UE 402 may send a registration request message to N3IWF 406 in 418. The registration request message may be included in an EAP-Response / 5G-NAS packet, where the EAP-Response / 5G-NAS packet may include the AN parameters and the registration request message. In some embodiments, the EAP-Response / 5G-NAS packet may be included in an IKE_AUTH request (such as an IKE_AUTH request message).

[0084] The AN parameters may include information used by the N3IWF to select an AMF in the 5GC. The information may include, for example, a globally unique AMF identifier (GUAMI), a selected PLMN ID, a requested NSSAI, and / or an establishment cause associated with the UE 402. The establishment cause may provide a reason for requesting a signaling connection with the EPC and / or 5GC, and the N3IWF may use the establishment cause to determine the DSCP value on the N2. For example, the N3IWF 406 may receive the AN parameters from the UE 402. The N3IWF 406 may identify an indication of the establishment cause based on the AN parameters and determine a DSCP value for the N2 interface to be used for the EPC and / or 5GC network.

[0085] The N3IWF may select an AMF based on the received AN parameters and local policies, and forward the registration request message to the selected AMF. For example, in 420, the N3IWF 406 may select an AMF based on the AN parameters received from the UE 402 and / or the local policies associated with the N3IWF 406. In the illustrated embodiment, the N3IWF 406 may select an AMF 408 based on the AN parameters and / or the local policies. The N3IWF 406 may provide the registration request received from the UE 402 in 418 to the AMF 408.

[0086] The selected AMF may decide to request a Subscription Hidden Identifier (SUCI) by sending a NAS Identity Request message to the UE. For example, as part of 422, the AMF 408 may send a NAS Identity Request message to the UE 402. The NAS Identity Request message may include and / or indicate a request for a SUCI. The AMF may use the establishment cause to determine a message priority header and then determine a DSCP value for subsequent signaling. For example, the AMF 408 may utilize the establishment cause received from the UE 402 to determine a message priority header and / or a DSCP value for subsequent signaling related to the UE 402.

[0087] The AMF may decide to authenticate the UE by invoking an authentication server function (AUSF). In this case, the AMF may select the AUSF based on a subscription permanent identifier (SUPI) or a SUCI. For example, the AMF 408 may determine that the UE 402 is to be authenticated. The AMF 408 may select the AUSF 410 for authentication based on the SUPI or SUCI associated with the UE 402. The AMF 408 may invoke the AUSF 410 to authenticate the UE 402. The AUSF 410 may perform authentication of the UE as specified in Technical Specification (TS) 33.501 (3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Security Architecture and Procedures for 5G Systems (Release 18). (2023). 3GPP TS33.501, 18.2.0). The AUSF may select the UDM and may obtain authentication data from the UDM. For example, the AUSF 410 may select the UDM and may retrieve authentication information from the selected UDF.

[0088] AMF 408 may send a NAS security mode command to UE 402 to activate NAS security. UE 402 may complete an improved extensible authentication protocol method for third generation authentication and key agreement (EAP-AKA') authentication, create a NAS security context, and / or send a NAS security mode complete message to AMF 408 relayed by N3IWF 406. Upon receiving NAS security mode complete, AMF 408 may send an NGAP initial context establishment request message including an N3IWF key. This may trigger N3IWF 406 to send EAP-Success to UE 402, which completes the EAP-5G session.

[0089] In 424, an IPsec SA may be established between the UE 402 and the N3IWF 406. For example, an IPsec SA may be established between the UE 402 and the N3IWF 406. The N3IWF 406 may apply a DSCP value to the signaling IPsec SA, in which case all IP packets exchanged between the UE 402 and the N3IWF 406 via the "signaling IPsec SA" may be marked with the DSCP value. The DSCP value may be determined by an operator policy and may be based on a DSCP value on N2, for example.

[0090] In 426, the AMF 408 may determine a subscribed single network slice selection assistance information (S-NSSAI) or a subset of the requested network slice selection assistance information (NSSAI) allowed by the S-NSSAI. A slice may be selected based on the subset of the requested NSSAI. The AMF 408 may determine whether the N3IWF 406 is suitable for the selected slice.

[0091] In 428, the AMF 408 may send a NAS Registration Accept message in an N2 message sent to the N3IWF. For example, the AMF 408 may send an N2 message to the N3IWF 428 via an N2 interface between the AMF 408 and the N3IWF 428. The N2 message may include a NAS Registration Accept message. The N2 message may include an allowed NSSAI for the access type of the UE 402. The allowed NSSAI may be a subset of the slices supported by the selected N3IWF 406. The N3IWF 406 may forward the NAS Registration Accept message to the UE 402 via the established signaling IPsec SA.

[0092] Method 1 for MPS over WLAN: E2E QoS model based on DSCP signaling

[0093] For end-to-end QoS on 5G and WLAN, it may be beneficial to enable QoS differentiation across all network segments. Figure 5An example system arrangement 500 is illustrated that may provide end-to-end prioritization for MPS via WLAN according to some embodiments.

[0094] The system arrangement 500 can implement in-band DSCP signaling. For in-band DSCP signaling, 5G QoS can be mapped to DSCP markings, which are mapped to WLAN user plane (UP) / access category (AC) within the WLAN domain. For example, the elements of the system arrangement 500 can map QoS flows to DSCP markings. In turn, the DSCP markings can map signals with DSCP markings to corresponding WLAN UP / AC within the WLAN domain.

[0095] System arrangement 500 may include UE 502. UE 502 may include UE 102 ( Figure 1 ), UE 202( Figure 2 )、UE 402( Figure 4 ) and / or UE 1800( Fig.18 ) features. UE 502 may include a 3GPP stack 504 and a WLAN station (STA) 506. The 3GPP stack 504 may facilitate communication between UE 502 and a 3GPP network (such as an EPC and / or a 5GC network). WLAN STA 506 may facilitate communication between UE 502 and a WLAN network.

[0096] The system arrangement 500 may include a 3GPP RAN node 508. The 3GPP RAN node 508 may provide access to a core network and corresponding services via 3GPP technology. For example, the UE 502 may establish a connection with the 3GPP RAN node 508 via 3GPP technology. The 3GPP RAN node 508 may include a base station, such as a nodeB, an evolved nodeB (eNB), a next generation nodeB (gNB), or some combination thereof. The 3GPP RAN node 508 may include a 3GPP access point 108 ( Figure 1 )、3GPP access point 208( Figure 2 ) and / or gNB1900( Fig.19 )'s features.

[0097] The system arrangement 500 may include a WLAN access point 510. The WLAN access point 510 may be an untrusted WLAN access point or a trusted WLAN access point. The WLAN access point 510 may include an untrusted non-3GPP access point 110 ( Figure 1 )、trusted non-3GPP access point 210( Figure 2 ) and / or untrusted WLAN access point 404 ( Figure 4) features. The WLAN access point 510 may provide access to the core network and corresponding services via WLAN technology. For example, the UE 502 may establish a connection with the WLAN access point 510 via WLAN technology.

[0098] The system arrangement 500 may include a gateway function 512. The gateway function 512 may include an N3IWF or a TNGF. The gateway function 512 may include an N3IWF 104 ( Figure 1 )、TNGF 204( Figure 2 ) and / or N3IWF 406( Figure 4 ) features. The WLAN access point 510 may establish a connection with the gateway function 512 to access the core network.

[0099] The system arrangement 500 may include a core network 514. The core network 514 may include an EPC and / or a 5GC network. The core network 514 may include an AMF 516 and a UPF 518. The AMF 516 may include an AMF 408 ( Figure 4 ) features. UPF 518 may include UPF 114 ( Figure 1 ) and / or UPF 214( Figure 2 ) features. The 3GPP RAN node 508 and the gateway function 512 may establish a connection with the core network 514 or a component thereof. For example, the gateway function 512 may have an N2 interface extending between the gateway function 512 and the AMF 516, and an N3 interface extending between the gateway function 512 and the UPF 518. The N2 interface and the N3 interface may be dedicated backhauls.

[0100] In the downlink (DL), the N3IWF / TNGF may map the 5QI to a DSCP marking. For example, the gateway function 512 may map data and / or signals issued in the DL to a DSCP marking corresponding to the 5QI associated with the UE 502. Specifically, the gateway function 512 may map data received from the AMF 516 and / or the UPF 518 to an appropriate DSCP value for the UE 502.

[0101] In the uplink (UL), the 3GPP stack 504 can map the 5QI to a DSCP marking. For example, the 3GPP stack 504 of the UE 502 can map the data and / or signals published in the UL to a DSCP marking corresponding to the 5QI associated with the UE 502.

[0102] The IP path between the N3IWF / TNGF and the WLAN access can apply DSCP-based prioritization, assuming that it is part of a managed network. For example, an IP path 520 can be established between the gateway function 512 and the WLAN access point 510. The signals issued via the IP path 520 can be prioritized based on the DSCP values ​​corresponding to the signals. For example, certain DSCP values ​​can be assigned to signals corresponding to UEs with MPS prioritization. These DSCP values ​​can prioritize the transmission of these signals over other signals associated with DSCP values ​​corresponding to UEs without MPS prioritization.

[0103] WLAN APs and STAs may map DSCP markings to 802.11UP / AC as defined in the 802.11 specification (also in RFC 8325). For example, the WLAN access point 510 and / or the WLAN STA 506 may map DSCP markings to WLAN protocols, such as 802.11UP / AC. A wireless connection 522 may be established between the WLAN STA 506 and the WLAN access point 510. The mapping of DSCP markings to WLAN protocols may allow certain signals corresponding to UEs with MPS prioritization issued by the wireless connection 522 to take precedence over other signals corresponding to UEs without MPS prioritization. For example, the mapping of DSCP markings to WLAN protocols may allow certain DSCP values ​​to be mapped to certain WLAN protocol values ​​for the WiFi Multimedia (WMM) AC of the wireless connection 522 to prioritize transmissions across the wireless connection 522.

[0104] In the illustrated embodiment, UE 502 may have MPS prioritization. Therefore, the signal corresponding to UE 502 may be prioritized by 5QI to DSCP mapping and DSCP to WLAN protocol mapping. The signal corresponding to UE 502 may be prioritized across wireless connection 522 and IP path 520 based on these mappings. Therefore, end-to-end (E2E) prioritization for the signal may be provided for UE 502. This option of E2E QoS assumes that the backhaul between N3IWF / TNGF and 5G core is managed by a mobile network operator (MNO). For example, in the illustrated embodiment, the N2 interface between the gateway function 512 and AMF516 and the N3 interface between the gateway function 512 and UPF 518 may be managed by the MNO.

[0105] Figure 6Table 600 showing example QoS information to DSCP value mappings according to some embodiments is illustrated. For example, Table 600 shows second generation (2G) / third generation (3G) / EPS QoS information and corresponding mappings to class of service (CoS) and DSCP values. Table 600 corresponds to Table 3 in the official document IR.34-IPX Provider Network Guide (IPX Provider Network Guide (formerly Inter-Service Provider IP Backbone Guide. (2018-08). GSM Association official document IR.34, 14.0). System arrangement 500 ( Figure 5 ) may implement a QoS to DSCP value mapping as shown in Table 600, or a similar QoS to DSCP value mapping.

[0106] Figure 7 Table 700 showing an example DSCP to QoS information mapping according to some embodiments is illustrated. For example, Table 700 shows a mapping table of DSCP to 3GPP QoS information and Enhanced Distributed Channel Access (EDCA) AC. Table 700 corresponds to Table R-1 in Part 11 of the IEEE Information Technology Standard (IEEE Standard for Information Technology - Telecommunications and Information Exchange between Systems for Local and Metropolitan Area Networks - Specific Requirements; Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications. (2016-12). IEEE Std 802.11-2016). System Arrangement 500 ( Figure 5 ) may implement DSCP to 3GPP QoS information and EDCA AC mapping as shown in Table 700, or similar DSCP to 3GPP QoS information and EDCA AC mapping.

[0107] Figure 8 Illustrated is a first portion of a table 800 showing example quality of service class identifier (QCI) to DSCP marking recommendations according to some embodiments. Fig. 9 Illustrated according to some embodiments Figure 8 The second part of Table 800 of FIG. 800 shows, for example, a 3GPP QCI to DSCP marking recommendation. The data shown in Table 800 can be used for Diffserv to QCI mapping. System Arrangement 500 ( Figure 5 ) can implement the QCI to DSCP marking recommendations shown in table 800, or similar QCI to DSCP marking recommendations. For example, system arrangement 500 can implement QCI to DSCP marking recommendations for use across IP path 520 ( Figure 5 ) signal transmission.

[0108] Fig.10Table 1000 showing example DSCP to WLAN protocol mappings according to some embodiments is illustrated. For example, Table 1000 shows example enterprise DSCP to UP / AC mappings. Table 1000 corresponds to Table R-2 in IEEE Information Technology Standard Part 11 (IEEE Standard for Information Technology - Telecommunications and Information Exchange between Systems for Local and Metropolitan Area Networks - Specific Requirements; Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications. (2016-12). IEEE Std 802.11-2016). System Arrangement 500 ( Figure 5 ) may implement the DSCP to WLAN protocol mapping shown in table 1000, or a similar DSCP to WLAN protocol mapping. For example, system arrangement 500 may implement DSCP to WLAN protocol mapping for use across wireless connection 522 ( Figure 5 ) signal transmission.

[0109] Method 2 for MPS over WLAN: UE-centric E2E QoS model

[0110] Fig.11 A first portion of an example signaling diagram 1100 of a device-centric QoS management method according to some embodiments is illustrated. Fig.12 Illustrated according to some embodiments Fig.11 The second part of the example signaling diagram 1100. For example, the signaling diagram 1100 illustrates example signaling for a system for implementing device-centric QoS management using a WLAN during a multiple access protocol data unit (MA-PDU) session establishment.

[0111] This option can provide QoS prioritization within the WLAN for 5G flows for the case when the DSCP marking is not added by N3IWF / TNGF or is stripped by the network segment before reaching the WLAN AP. This option can provide additional QoS information (e.g., throughput, latency) for 5G QoS flows to the WLAN AP network that can be used for resource reservation. This option requires enhancements to support QoS management between STAs and APs for 5G flows.

[0112] The signaling diagram 1100 may include a UE 1102. The UE 1102 may include a UE 102 ( Figure 1 ), UE 202( Figure 2 )、UE 402( Figure 4 ), UE 502( Figure 5 ) and / or UE 1800( Fig.18 ) features. UE 1102 may include a cellular element 1104 and a WLAN element 1106. Cellular element 1104 may include a 3GPP stack 504 ( Figure 5) features. The WLAN element 1106 may include a WLAN STA 506 ( Figure 5 )'s features.

[0113] The signaling diagram 1100 may include a WLAN access point 1108. The WLAN access point 1108 may be a trusted WLAN access point or an untrusted WLAN access point. The WLAN access point 1108 may include an untrusted non-3GPP access point 110 ( Figure 1 )、trusted non-3GPP access point 210( Figure 2 )、Untrusted WLAN access point 404( Figure 4 ) and / or WLAN access point 510 ( Figure 5 )'s features.

[0114] The signaling diagram 1100 may include a gateway function 1110. The gateway function 1110 may be an N3IWF or a TNGF. The gateway function 1110 may include the N3IWF 104 ( Figure 1 )、TNGF 204( Figure 2 )、N3IWF 406( Figure 4 ) and / or gateway function 512 ( Figure 5 )'s features.

[0115] The signaling diagram 1100 may include a base station 1112. The base station 1112 may include a 3GPP access point 108 ( Figure 1 )、3GPP access point 208( Figure 2 )、3GPP RAN node 508( Figure 5 ) and / or gNB 1900( Fig.19 )'s features.

[0116] The signaling diagram 1100 may include a core network 1114. The core network 1114 may be an EPC and / or a 5GC network. The core network 1114 may include an AMF 1116, a session management function (SMF) 1118, and a UPF 1120. The AMF 1116 may include an AMF 408 ( Figure 4 ) and / or AMF 516( Figure 5 ) features. SMF 1118 may collect information related to PDU session management and / or control one or more of the elements of core network 1114. UPF 1120 may include UPF 114 ( Figure 1 )、UPF 214( Figure 2 ) and / or UPF 518( Figure 5 )'s features.

[0117] UE 1102 may establish a PDU session and / or an MA-PDU session with the core network 1114. For example, the cellular element 1104 may transmit a PDU session establishment request 1122 to the AMF 1116. The PDU session establishment request 1122 may include an MA-PDU request. The AMF 1116 may respond to the cellular element 1104 with a PDU session establishment acceptance 1124. During the establishment of a (MA-)PDU session involving WLAN access, the UE may initiate QoS management with the WLAN AP for 5G flows. For example, the UE 1102 may initiate QoS management with the WLAN for the IPsec sub-SA 1142 during the establishment of the PDU session and / or MA-PDU session.

[0118] At 1126, the core network 1114 may perform one or more operations for PDU session establishment. For example, the core network 1114 may perform the following steps in TS 23.502 (3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for 5G System (5GS); Stage 2 (Release 18). (2023-06). 3GPP TS 23.502, 18.2.0) Figure 4 .Steps 2 to 20 as shown in 3.2.1.1-1, with changes made to clause 4.22.2.1 of TS23.502 (supra).

[0119] The AMF 1116 may transmit an N2 PDU Session Request 1128 to the Gateway Function 1110. As part of the IKEv2 Child SA establishment, the Gateway Function 1110 may transmit an IKE Create Child SA Request (IKEv2 Create_Child_SA Req) 1130 to the cellular element 1104. During the IKEv2 Child SA establishment, 5G QoS characteristics may be sent to the UE. For example, the IKEv2 Create_Child_SA Req 1130 may include a 5G QoS information payload (5G_QOS_INFO payload). The 5G_QOS_INFO payload may include 5G QoS characteristics.

[0120] The UE 1102 may map the 5G QoS characteristics to the DSCP (if the DSCP is not received), and then map the DSCP to 802.11 UP / AC. For example, in 1132, the cellular element 1104 may map the 5QI to the DSCP. In 1134, the cellular element 1104 may provide the WLAN element 1106 with the DSCP value from the 5QI to DSCP mapping, an indication of the DSCP value to be prioritized, and / or an indication that the 5QI to DSCP mapping has been completed. In 1136, the WLAN element 1106 may map the DSCP to the WLAN protocol. In some embodiments, the WLAN protocol may be 802.11 UP / AC.

[0121] For DL ​​flows, the UE may use an enhanced protocol (R2) to negotiate QoS prioritization with a WLAN AP (e.g., AC_VO or AC_VI). The message may also provide 5G QoS information to the WLAN for resource reservation. For example, the WLAN element 1106 of the UE 1102 may transmit a QoS negotiation request 1138 to the WLAN access point 1108. The QoS negotiation request 1138 may include QoS information. For example, the QoS negotiation request 1138 may include a service identifier, a scheduling priority indicator (SPI) for IPsec, a request, and / or UP / AC information.

[0122] QoS prioritization on the WLAN AP may be based on the SPI value, the target address, and / or the security protocol Id (ESP). For example, the WLAN access point 1108 may determine whether to prioritize the signal and / or message sent by the WLAN access point 1108 based on the SPI value, the target address, and / or the security protocol Id. Therefore, the WLAN AP maps the DL traffic for the IPsec sub-SA to the negotiated appropriate 802.11UP / AC. For example, in 1140, the WLAN access point 1108 may map the DL IPsec SA traffic to the appropriate WLAN protocol. In some embodiments, the WLAN protocol may be 802.11UP / AC. The mapping of the DL IPsec SA traffic to the appropriate WLAN protocol may be based on the SPI value, the target address, and / or the security protocol Id.

[0123] The WLAN access point 1108 may transmit a QoS negotiation response 1202 to the WLAN element 1106 of the UE 1102. The QoS negotiation response may indicate whether the QoS negotiation request 1138 has been accepted or rejected. If the WLAN AP cannot grant flows for the requested AC, the WLAN AP may reject the QoS request from the UE, resulting in a failure to establish an IPsec sub-SA on the WLAN access. For example, if the WLAN access point 1108 cannot grant flows for the AC requested by the QoS negotiation request 1138, the QoS negotiation response 1202 transmitted by the WLAN access point 1108 may indicate that the QoS negotiation request 1138 has been rejected. The rejection may result in a failure to establish an IPsec sub-SA on the WLAN access point 1108.

[0124] In 1204, the WLAN element 1106 may provide an indication to the cellular element 1104 whether the QoS negotiation request 1138 has been accepted or rejected. If the QoS negotiation request 1138 has been accepted, the cellular element 1104 may transmit an IKE Create Child SA Response (IKEv2Create_Child_SA Resp) 1206 to the gateway function 1110 to establish the IPsec SA. The gateway function 1110 may transmit an N2 PDU Session Request Acknowledgement 1208 to the AMF 1116 of the core network 1114. In 1210, the core network 1114 may execute TS23.502 (3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for 5G System (5GS); Stage 2 (Release 18). (2023-06). 3GPP TS23.502, 18.2.0) Figure 4 .3.2.2.1-1. Steps 15 to 17 are performed to complete the IPsec SA establishment.

[0125] This model can also be applied to prioritize NAS over signaling IPsec SA within a WLAN. During signaling IPsec SA establishment, the DSCP value can be sent to the UE via IKE_AUTH messaging using a notification payload. For example, in some embodiments, the IKEv2Create_Child_SA request 1130 can include a notification payload indicating the DSCP value. In other embodiments, another message related to IKE messaging transmitted to the UE 1102 can include a notification payload with a DSCP value. The UE can map the DSCP to 802.11UP / AC. For example, the UE 1102 can map the DSCP value indicated in the notification payload to a WLAN protocol. In some embodiments, the WLAN protocol can be 802.11UP / AC.

[0126] Thus, the WLAN AP may map DL traffic for signaling IPsec SA traffic to the negotiated appropriate 802.11 UP / AC, resulting in priority transmission for NAS messaging. For example, the WLAN access point 1108 may map DL traffic for signaling IPsec SA traffic to an appropriate WLAN protocol. In some embodiments, the WLAN protocol may be 802.11 UP / AC. This may result in priority transmission for NAS messaging for the UE 1102.

[0127] Although the signals and operations of the signaling diagram 1100 are shown in a particular order in the illustrated embodiment, it should be understood that in other embodiments, one or more of these signals and / or operations may be performed in a different order and / or simultaneously. In addition, it should be understood that in other embodiments, one or more of these signals and / or operations may be omitted, and / or one or more additional signals and / or operations may be performed.

[0128] Approach 3 for MPS over WLAN: Network-centric E2E QoS model for trusted WLAN

[0129] Fig.13 A first portion of an example signaling diagram 1300 of a network-centric QoS management method according to some embodiments is illustrated. Fig.14 Illustrated according to some embodiments Fig.13 The second part of the example signaling diagram 1300. For example, the signaling diagram 1300 illustrates example signaling for a system for implementing network-centric QoS management using a WLAN during an MA-PDU session establishment.

[0130] For the case when the DSCP tag is not added by TNGF or is stripped by the network segment before reaching the WLAN AP, this option is applicable to trusted WLAN integrated deployment and can provide QoS prioritization within the WLAN for 5G flows. This method can provide additional QoS information (e.g., throughput, latency) for 5G QoS flows to the WLAN AP network that can be used for resource reservation, and requires enhancements to the EAP-5G protocol to carry 5G QoS information and other related parameters on the Ta interface based on authentication, authorization, and accounting (AAA).

[0131] Signaling diagram 1300 may include UE 1302. UE 302 may include UE 102 ( Figure 1 ), UE 202( Figure 2 )、UE 402( Figure 4 ), UE 502( Figure 5 )、UE 1102( Fig.11 ) and / or UE 1800( Fig.18) features. UE 1302 may include a cellular element 1304 and a WLAN element 1306. The cellular element 1304 may include a 3GPP stack 504 ( Figure 5 ) and / or honeycomb element 1104 ( Fig.11 ) features. The WLAN element 1306 may include a WLAN STA 506 ( Figure 5 ) and / or WLAN element 1106 ( Fig.11 )'s features.

[0132] The signaling diagram 1300 may be applicable to trusted WLAN integration. For example, the signaling diagram 1300 may include a WLAN access point 1308. The WLAN access point 1308 may be a trusted WLAN access point. The WLAN access point 1308 may include a trusted non-3GPP access point 210 ( Figure 2 )、WLAN access point 510( Figure 5 ) and / or WLAN access point 1108 ( Fig.11 )'s features.

[0133] The signaling diagram 1300 may include a TNGF 1310. The TNGF 1310 may include a TNGF 204 ( Figure 2 )、gateway function 512( Figure 5 ) and / or gateway function 1110( Fig.11 )'s features.

[0134] Signaling diagram 1300 may include base station 1312. Base station 1312 may include 3GPP access point 108 ( Figure 1 )、3GPP access point 208( Figure 2 )、3GPP RAN node 508( Figure 5 )、Base Station 1112( Fig.11 ) and / or gNB 1900( Fig.19 )'s features.

[0135] Signaling diagram 1300 may include core network 1314. Core network 1314 may be an EPC and / or 5GC network. Core network 1314 may include AMF 1316, SMF 1318, and UPF 1320. AMF 1316 may include AMF 408 ( Figure 4 )、AMF 516( Figure 5 ) and / or AMF 1116( Fig.11 ) features. SMF 1318 may include SMF 1118 ( Fig.11) features. UPF 1320 may include UPF 114 ( Figure 1 )、UPF 214( Figure 2 )、UPF 518( Figure 5 ) and / or UPF 1120( Fig.11 )'s features.

[0136] UE 1302 may establish a PDU session and / or an MA-PDU session with core network 1314. For example, cellular element 1304 may transmit a PDU session establishment request 1322 to AMF 1316. PDU session establishment request 1322 may include an MA-PDU request. AMF 1316 may respond to cellular element 1304 with PDU session establishment accept 1324. During MA-PDU session establishment, TNGF may initiate QoS management with WLAN AP for 5G flows sent over IPsec sub-SA. For example, TNGF 1310 may initiate QoS management with WLAN for IPsec sub-SA 1342 during establishment of PDU session and / or MA-PDU session.

[0137] In 1326, the core network 1314 may perform one or more operations for PDU session establishment. For example, the core network 1314 may perform the following steps in TS 23.502 (3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for 5G System (5GS); Stage 2 (Release 18). (2023-06). 3GPP TS 23.502, 18.2.0) Figure 4 .Steps 2 to 20 as shown in 3.2.1.1-1, with changes made to clause 4.22.2.1 of TS23.502 (supra).

[0138] The AMF 1316 may transmit an N2 PDU Session Request 1328 to the TNGF 1310. During signaling of the IPsec SA establishment, the DSCP value may be sent to the UE via IKE_AUTH messaging using a notification payload. For example, as part of the IKEv2 child SA establishment, the TNGF 1310 may transmit an IKE Create Child SA Request (IKEv2Create_Child_SA Req) 1330 to the cellular element 1304. The IKEv2 Create_Child_SA Req 1330 may include a 5G QoS information payload (5G_QOS_INFO payload). The 5G_QOS_INFO payload may include 5G QoS characteristics. In addition, the 5G QoS information payload may include a DSCP value, wherein the 5G QoS information payload may operate as a notification payload.

[0139] The cellular element 1304 may transmit an IKE Create Child SA Response (IKEv2Create_Child_SAResp) 1332 to the TNGF 1310 to establish the IPsec SA. The TNGF 1310 may transmit an N2 PDU Session Request Acknowledgement 1334 to the AMF 1316 of the core network 1314. In 1336, the core network 1314 may execute TS23.502 (3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for 5G System (5GS); Stage 2 (Release 18). (2023-06). 3GPP TS23.502, 18.2.0) Figure 4 .3.2.2.1-1. Steps 15 to 17 are performed to complete the IPsec SA establishment.

[0140] The UE 1302 may map the 5G QoS characteristics to the DSCP. For example, in 1338, the cellular element 1304 may map the 5QI to the DSCP. In 1340, the cellular element 1304 may provide the WLAN element 1306 with the DSCP value from the 5QI to DSCP mapping, an indication of the DSCP value to be prioritized, and / or an indication that the 5QI to DSCP mapping has been completed. For the UL, the UE may map the DSCP to 802.11 UP / A. For example, in 1344, the WLAN element 1306 may map the DSCP to the WLAN protocol. In some embodiments, the WLAN protocol may be 802.11 UP / AC.

[0141] The TNGF may use a new EAP-5G signaling message (TS24.502) to send 5G QoS information (such as a service identifier, SPI, and / or DSCP) to the WLAN AP through the AAA interface (Ta). For example, the TNGF 1310 may transmit an EAP-5G signaling message 1346 to the WLAN access point 1308. The EAP-5G signaling message 1346 may be based on EAP-5G signaling as defined by TS24.502 (3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Access to 3GPP 5G Core Network (5GCN via Non-3GPP Access Network (N3AN)); Stage 3 (Release 18). (2023-06). 3GPP TS24.502, 18.2.0). The EAP-5G signaling message 1346 may include QoS information such as a service identifier, SPI, DSCP value, and / or other 5G QoS information. The EAP-5G message may be carried over AAA using the already defined RADIUS EAP-message attributes. For example, the EAP-5G signaling message 1346 may be carried over the AAA interface using the RADIUS EAP-message attribute. In some embodiments, the N3IWF / TNGF may use the new EAP-5G signaling message to send 5G QoS information (such as service identifier, SPI, and DSCP) to the WLAN AP over the AAA interface (Ta).

[0142] The WLAN AP may map the DL IPsec SA service to the appropriate 802.11UP / AC based on the DSCP value. The received 5G QoS characteristics may be used for WLAN resource reservation. DL QoS prioritization on the WLAN AP may be based on a triple (SPI value, target address, security protocol identifier (ESP)). For example, in 1402, the WLAN access point 1308 may map the IPsec SA service in the DL direction to the WLAN protocol. In some embodiments, the WLAN protocol may be 802.11UP / AC. The mapping of the IPsec SA service to the WLAN protocol may be based on the DSCP value associated with the service. Therefore, the WLAN AP may map the DL signaling IPsec SA service to the appropriate 802.11UP / AC based on the DSCP value. For example, the WLAN access point 1308 may map the DL signaling IPsec SA service to the appropriate WLAN protocol. In some embodiments, the mapping of the IPsec SA service to the WLAN protocol may be based on 5G QoS. The QoS prioritization of the IPsec SA service to the WLAN protocol may be based on the SPI value associated with the service, the target address of the service, and / or the security protocol identifier associated with the service. The received 5G QoS characteristics may be used for WLAN resource reservation. For example, the SPI value, the target address and / or the security protocol identifier may be used to reserve WLAN resources for transmitting the service.

[0143] The WLAN access point 1308 may transmit an EAP-5G message response 1404 to the TNGF 1310. The EAP-5G message response 1404 may indicate an EAP-5G signaling message 1346. The model may also be applied to prioritize NAS over signaling IPsecSA within a WLAN. The EAP-5G message response 1404 may be in accordance with EAP-5G signaling as defined by TS24.502 (3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Access to 3GPP 5G Core Network (5GCN via Non-3GPP Access Network (N3AN)); Stage 3 (Release 18). (2023-06). 3GPP TS24.502, 18.2.0). The EAP-5G message may be carried on AAA using the already defined RADIUS EAP-message attributes. For example, the EAP-5G message response 1404 may be carried on the AAA interface using RADIUS EAP-message attributes.

[0144] This model can also be applied to prioritize NAS over signaling IPsec SA within a WLAN.For example, the signals and / or operations shown in signaling diagram 1300 can also be used to prioritize NAS over signaling IPsec SA within a WLAN.

[0145] Although the signals and operations of the signaling diagram 1300 are shown in a particular order in the illustrated embodiment, it should be understood that in other embodiments, one or more of these signals and / or operations may be performed in a different order and / or simultaneously. In addition, it should be understood that in other embodiments, one or more of these signals and / or operations may be omitted and / or one or more additional signals and / or operations may be performed.

[0146] Open perspective

[0147] There may be some points to address, including the following. The UE may not be aware of the WLAN MPS as shared in the Registration Accept in 3GPP to know whether it can use the MPS in the next access. Similar to CUC in 3GPP, there may not be a mechanism to dynamically update the MPS in WLAN. For authentication and authorization, what are the consequences of MPS-specific authentication / authorization failures? There may be an indication provided back to the UE.

[0148] Initial access and authorization to the network when the WLAN is congested, a UE that has not yet been authorized by the network may not be able to access the network even if it has valid user credentials associated with the UE (e.g., calling card number, PIN, or security token). For WLAN access, the UE may inform the TNAN / N3IWF of its MPS subscription prior to the NAS registration request. Based on operator policy, the TNAN / N3IWF may use this indication to provide priority treatment to the UE in case of congestion overload before accepting a NAS registration request with MPS priority establishment cause.

[0149] When the UE does not have a Universal Integrated Circuit Card (UICC), service user credentials not associated with the UE (e.g., calling card number, PIN, or security token) may be used. The AP may be able to define whether it is MPS in a standardized interface. Authentication and Authorization: For UEs with a 3GPP subscription for MPS and with WLAN access to EPC / 5GC, the system may support MPS for MMTEL voice / video authorization based on the UE subscription information. For UEs without a 3GPP subscription for MPS and with WLAN access to EPC / 5GC, the system may support MPS for MMTEL voice / video authorization based on service user credentials not associated with the UE (e.g., calling card number, PIN, or security token).

[0150] MPS for MMTEL voice and video and MPS for DTS (Data Transport Service) can be handled as separate features. MPS priority can be shared with N3IWF from UDM / AUSF. MPS priority can be shared with TNAN from UDM / AUSF.

[0151] Fig.15 An example procedure 1500 to be performed by a UE according to some embodiments is illustrated. For example, the procedure 1500 may be performed by a UE 102 ( Figure 1 ), UE 202( Figure 2 )、UE 402( Figure 4 ), UE 502( Figure 5 )、UE 1102( Fig.11 )、UE 1302( Fig.13 ) and / or UE 1800( Fig.18 The UE may perform procedure 1500 to facilitate prioritization of signals via a WLAN according to MPS prioritization.

[0152] Procedure 1500 may include establishing a connection with a WLAN access point at 1502. For example, the UE may establish a connection with a WLAN access point to access a network. The WLAN access point may include an untrusted non-3GPP access point 110 ( Figure 1 )、trusted non-3GPP access point 210( Figure 2 )、WLAN access point 510( Figure 5 )、WLAN access point 1108( Fig.11 ) and / or WLAN access point 1308 ( Fig.13 ) features. The network may include an EPC network and / or a 5G network. In addition, the network may include a core network (such as core network 514 ()) that can provide services to the UE via a WLAN access point. Figure 5 )、Core Network 1114( Fig.11 ) and / or core network 1314 ( Fig.13 )).

[0153] In some embodiments, the WLAN access point may be an untrusted WLAN access point or a trusted WLAN access point. For example, the WLAN access point may be an untrusted WLAN access point in some embodiments, or may be a trusted WLAN access point in other embodiments.

[0154] The procedure 1500 may include determining that the UE has MPS prioritization at 1504. For example, the UE may determine that the UE has MPS prioritization to indicate that services of the UE are to be prioritized.

[0155] The procedure 1500 may include transmitting an indication of MPS prioritization for the UE. For example, the UE may transmit an indication of MPS prioritization for the UE to a WLAN access point.

[0156] In some embodiments, an indication of MPS prioritization may be included in an Internet Key Exchange Authorization (IKE_AUTH) request. For example, an indication of MPS prioritization may be included in an IKE exchange (such as 416( Figure 4 ) in an IKE exchange of (i) an IKE request to transmit the indication of MPS prioritization. In some of these embodiments, the indication of MPS prioritization may be included in a notification payload of the IKE_AUTH request. Further, in some of these embodiments, the WLAN access point may include an untrusted WLAN access point, and the indication of MPS prioritization may be included in the IKE_AUTH request based at least in part on the WLAN access point including the untrusted WLAN access point.

[0157] In some embodiments, the indication of MPS prioritization may be included in the username portion of the NAI. In some of these embodiments, the WLAN access point may include a trusted WLAN access point, and the indication of MPS prioritization may be included in the username portion of the NAI based at least in part on the WLAN access point including a trusted WLAN access point.

[0158] In some embodiments, the procedure 1500 may include transmitting an indication of an establishment cause. For example, the UE may transmit an indication of an establishment cause to the WLAN access point. The establishment cause may be used to determine a DSCP value for subsequent signaling related to the UE.

[0159] In some implementations, procedure 1500 may include applying a QI to DSCP mapping to signaling.For example, the UE may apply a QI to DSCP mapping to signaling via the UE's 3GPP stack to prioritize signaling between the UE's 3GPP stack and the WLAN STA.

[0160] In some implementations, the procedure 1500 may include applying a DSCP to WLAN protocol mapping. For example, the UE may apply the DSCP to WLAN protocol mapping to the UE's signaling via the UE's WLAN STA to prioritize signaling between the UE and a WLAN access point.

[0161] Although Fig.15 The order of operations within the protocol 1500 is arguably implied, but it should be understood that in other embodiments, one or more of these operations may be performed in a different order and / or performed simultaneously. Furthermore, it should be understood that in other embodiments, one or more of these operations may be omitted from the protocol 1500 and / or one or more additional operations may be included in the protocol 1500.

[0162] Fig.16An example procedure 1600 to be performed by a network structure according to some embodiments is illustrated. For example, the network structure may include a WLAN access point (such as an untrusted non-3GPP access point 110 ( Figure 1 )、trusted non-3GPP access point 210( Figure 2 )、Untrusted WLAN access point 404( Figure 4 )、WLAN access point 510( Figure 5 )、WLAN access point 1108( Fig.11 ) and / or WLAN access point 1308 ( Fig.13 )), gateway functions (such as N3IWF 104 ( Figure 1 )、TNGF 204( Figure 2 )、N3IWF 406( Figure 4 )、gateway function 512( Figure 5 )、gateway function 1110( Fig.11 ) and / or TNGF 1310( Fig.13 )), core networks (such as core network 514 ( Figure 5 )、Core Network 1114( Fig.11 ) and / or core network 1314 ( Fig.13 )), AMF (such as AMF 408 ( Figure 4 )), AUSF (such as AUSF 410 ( Figure 4 )) or some combination thereof. In different embodiments, the elements included in the network structure may be different. The network structure may execute procedure 1600 to facilitate prioritization of signals via WLAN according to MPS prioritization.

[0163] Procedure 1600 may include receiving an indication that the UE has MPS prioritization at 1602. For example, the network structure may receive an indication that the UE has MPS prioritization from the UE via a WLAN access point of the network structure. For example, the network structure may receive the indication as 416( Figure 4 ) as part of the IKE exchange in the IKE.

[0164] In some embodiments, the indication that the UE has MPS prioritization may be received in an Internet Key Exchange Authorization (IKE_AUTH) request. In some of these embodiments, the indication that the UE has MPS prioritization may be received in a Notification payload of an IKE_AUTH request.

[0165] In some embodiments, an indication that the UE has MPS prioritization may be received in the username portion of the NAI.

[0166] In some embodiments, the procedure 1600 may include receiving an indication of an establishment cause. For example, the network structure may receive an indication of an establishment cause from the UE.

[0167] In some embodiments, procedure 1600 may include determining a DSCP value for subsequent signaling. For example, the network structure may determine a DSCP value for subsequent signaling of the UE.

[0168] The procedure 1600 may include configuring the network structure to prioritize subsequent signaling of the UE at 1604. For example, the network structure may configure the network structure to prioritize subsequent signaling of the UE via the WLAN access point based at least in part on the indication that the UE has MPS prioritization.

[0169] In some embodiments, configuring the network structure may include generating a QI to DSCP mapping for subsequent signaling of the UE based at least in part on an indication that the UE has MPS prioritization. In addition, in some embodiments, configuring the network structure may include applying the QI to DSCP mapping to subsequent signaling via the N3IWF or TNGF to prioritize subsequent signaling between the N3IWF or TNGF and the WLAN access point.

[0170] In some embodiments, configuring the network structure may include generating a DSCP to WLAN protocol mapping for subsequent signaling of the UE based at least in part on the indication that the UE has MPS prioritization. In addition, in some embodiments, configuring the network structure may include applying the DSCP to WLAN protocol mapping to the subsequent signaling via the WLAN access point to prioritize the subsequent signaling between the WLAN access point and the UE.

[0171] Although Fig.16 The order of operations within the protocol 1600 may be arguably implied, but it should be understood that in other embodiments, one or more of these operations may be performed in a different order and / or performed simultaneously. Furthermore, it should be understood that in other embodiments, one or more of these operations may be omitted from the protocol 1600 and / or one or more additional operations may be included in the protocol 1600.

[0172] Fig.17 An example procedure 1700 to be performed by a UE according to some embodiments is illustrated. For example, the procedure 1700 may be performed by a UE 102 ( Figure 1 ), UE 202( Figure 2 )、UE 402( Figure 4 ), UE 502( Figure 5 )、UE 1102( Fig.11 )、UE 1302( Fig.13) and / or UE 1800( Fig.18 The UE may perform procedure 1700 to facilitate prioritization of signals via a WLAN according to MPS prioritization.

[0173] Procedure 1700 may include establishing a connection with a WLAN access point at 1702. For example, the UE may establish a connection with a WLAN access point of a network. The WLAN access point may include an untrusted non-3GPP access point 110 ( Figure 1 )、trusted non-3GPP access point 210( Figure 2 )、WLAN access point 510( Figure 5 )、WLAN access point 1108( Fig.11 ) and / or WLAN access point 1308 ( Fig.13 ) features. The network may include an EPC network and / or a 5G network. In addition, the network may include a core network (such as core network 514 ()) that can provide services to the UE via a WLAN access point. Figure 5 )、Core Network 1114( Fig.11 ) and / or core network 1314 ( Fig.13 )).

[0174] In some embodiments, the WLAN access point may be part of an untrusted WLAN network or part of a trusted WLAN network. For example, the WLAN access point may be part of an untrusted WLAN network in some embodiments or part of a trusted WLAN network in other embodiments.

[0175] The procedure 1700 may include transmitting an indication of MPS prioritization at 1704. For example, the UE may transmit an indication of MPS prioritization to a WLAN access point to indicate that services of the UE are to be prioritized.

[0176] In some embodiments, the WLAN access point may be part of an untrusted WLAN network, and an indication of MPS prioritization may be transmitted in an Internet Key Exchange Authorization (IKE_AUTH) request based at least in part on the WLAN access point being part of the untrusted WLAN network. For example, IKE_AUTH may be 416( Figure 4 ) as part of an IKE exchange. In some of these embodiments, an indication of MPS prioritization may be included in a Notification payload of an IKE_AUTH request.

[0177] In some embodiments, the WLAN access point may be part of a trusted WLAN network, and the indication of MPS prioritization is transmitted in the username portion of the NAI based at least in part on the WLAN access point being part of the trusted WLAN network.

[0178] The procedure 1700 may include transmitting an indication of an establishment cause at 1706. For example, the UE may transmit an indication of the establishment cause to the WLAN access point. The establishment cause may be used to determine a DSCP value used to prioritize signaling related to the UE.

[0179] Although Fig.17 The order of operations within the protocol 1700 may be arguably implied, but it should be understood that in other embodiments, one or more of these operations may be performed in a different order and / or performed simultaneously. Furthermore, it should be understood that in other embodiments, one or more of these operations may be omitted from the protocol 1700 and / or one or more additional operations may be included in the protocol 1700.

[0180] Fig.18 An example UE 1800 according to some embodiments is illustrated. UE 1800 can be any mobile or non-mobile computing device, such as a mobile phone, a computer, a tablet, an industrial wireless sensor (e.g., a microphone, a carbon dioxide sensor, a pressure sensor, a humidity sensor, a thermometer, a motion sensor, an accelerometer, a laser scanner, a fluid level sensor, an inventory sensor, a voltage / current meter, an actuator, etc.), a video surveillance / monitoring device (e.g., a camera, a video camera, etc.), a wearable device (e.g., a smart watch), a loose IoT device. In some embodiments, UE 1800 can be a RedCap UE or an NR-Light UE.

[0181] UE 1800 may include a processor 1804, RF interface circuitry 1808, memory / storage 1812, a user interface 1816, a sensor 1820, a driver circuit 1822, a power management integrated circuit (PMIC) 1824, antenna structures 1826, and a battery 1828. The components of UE 1800 may be implemented as an integrated circuit (IC), a portion of an integrated circuit, a discrete electronic device or other module, logical component, hardware, software, firmware, or a combination thereof. Fig.18 The block diagram of UE 1800 is intended to show a high-level view of some of the components of UE 1800. However, some of the components shown may be omitted, additional components may be present, and different arrangements of the components shown may occur in other implementations.

[0182] Components of UE 1800 may be coupled to various other components via one or more interconnects 1832, which may represent any type of interface, input / output, bus (local, system, or extension), transmission line, trace, optical connection, etc., which allows various circuit components (on a common or different chip or chipset) to interact with each other.

[0183] The processor 1804 may include processor circuits such as a baseband processor circuit (BB) 1804A, a central processor unit circuit (CPU) 1804B, and a graphics processor unit circuit (GPU) 1804C. The processor 1804 may include any type of circuit or processor circuit that executes or otherwise operates computer-executable instructions (such as program codes, software modules, or functional processes from the memory / storage device 1812) to cause the UE 1800 to perform operations as described herein.

[0184] In some embodiments, the baseband processor circuit 1804A can access the communication protocol stack 1836 in the memory / storage device 1812 to communicate through a 3GPP compatible network. Generally speaking, the baseband processor circuit 1804A can access the communication protocol stack to: perform user plane functions at the PHY layer, MAC layer, RLC layer, PDCP layer, SDAP layer, and PDU layer; and perform control plane functions at the PHY layer, MAC layer, RLC layer, PDCP layer, RRC layer, and non-access layer. In some embodiments, the PHY layer operations can be additionally / alternatively performed by components of the RF interface circuit 1808.

[0185] The baseband processor circuit 1804A may generate or process baseband signals or waveforms that carry information in a 3GPP-compatible network. In some embodiments, the waveforms used for NR may be based on cyclic prefix OFDM (CP-OFDM) in the uplink or downlink, and discrete Fourier transform spread OFDM (DFT-S-OFDM) in the uplink.

[0186] The memory / storage 1812 may include one or more non-transitory computer-readable media including instructions (e.g., the communication protocol stack 1836) that may be executed by one or more processors in the processor 1804 to enable the UE 1800 to perform various operations described herein. The memory / storage 1812 includes any type of volatile or non-volatile memory that may be distributed throughout the UE 1800. In some embodiments, some of the memory / storage 1812 may be located on the processor 1804 itself (e.g., L1 cache and L2 cache), while other memory / storage 1812 is located external to the processor 1804 but accessible via a memory interface. The memory / storage 1812 may include any suitable volatile or non-volatile memory, such as, but not limited to, dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state memory, or any other type of memory device technology.

[0187] The RF interface circuit 1808 may include a transceiver circuit and a radio frequency front end module (RFEM), which allows the UE 1800 to communicate with other devices through a radio access network. The RF interface circuit 1808 may include various elements arranged in a transmit path or a receive path. These elements may include, for example, switches, mixers, amplifiers, filters, synthesizer circuits, control circuits, etc.

[0188] In the receive path, the RFEM may receive the radiated signal from the air interface via the antenna structure 1826 and proceed to filter and amplify the signal (using a low noise amplifier). The signal may be provided to the transceiver's receiver, which down-converts the RF signal to a baseband signal that is provided to the baseband processor of the processor 1804.

[0189] In the transmit path, the transmitter of the transceiver up-converts the baseband signal received from the baseband processor and provides an RF signal to the RFEM. The RFEM may amplify the RF signal through a power amplifier before the signal is radiated across the air interface via the antenna structure 1826.

[0190] In various embodiments, the RF interface circuit 1808 may be configured to transmit / receive signals in a manner compatible with NR access technology.

[0191] The antenna structure 1826 may include antenna elements to convert electrical signals into radio waves to travel through the air and convert received radio waves into electrical signals. These antenna elements may be arranged into one or more antenna panels. The antenna structure 1826 may have antenna panels that are omnidirectional, directional, or a combination thereof to achieve beamforming and multiple-input multiple-output communications. The antenna structure 1826 may include microstrip antennas, printed antennas manufactured on the surface of one or more printed circuit boards, patch antennas, phased array antennas, etc. The antenna structure 1826 may have one or more panels that are designed for specific frequency bands including frequency bands in FR1 or FR2.

[0192] The user interface 1816 includes various input / output (I / O) devices designed to enable a user to interact with the UE 1800. The user interface circuit 1816 includes an input device circuit and an output device circuit. The input device circuit includes any physical or virtual device for accepting input, and in particular includes one or more physical or virtual buttons (e.g., a reset button), a physical keyboard, a keypad, a mouse, a touchpad, a touch screen, a microphone, a scanner, a headset, etc. The output device circuit includes any physical or virtual device for displaying information or otherwise conveying information (such as sensor readings, (multiple) actuator positions, or other similar information). The output device circuit may include any number or combination of audio or visual displays, in particular including one or more simple visual outputs / indicators (e.g., binary state indicators, such as light emitting diodes (LEDs)) and multi-character visual outputs, or more complex outputs, such as display devices or touch screens (e.g., liquid crystal displays (LCDs), LED displays, quantum dot displays, projectors, etc.), where the output of characters, graphics, multimedia objects, etc. is generated or produced by the operation of the UE 1800.

[0193] Sensors 1820 may include devices, modules, or subsystems that are designed to detect events or changes in their environment and send information about the detected events (sensor data) to some other device, module, subsystem, etc. Examples of such sensors include, among others: an inertial measurement unit including an accelerometer, gyroscope, or magnetometer; a microelectromechanical system or nanoelectromechanical system including a three-axis accelerometer, three-axis gyroscope, or magnetometer; a level sensor; a flow sensor; a temperature sensor (e.g., a thermistor); a pressure sensor; a barometric pressure sensor; a gravity meter; an altimeter; an image capture device (e.g., a camera or a lensless aperture); a light detection and ranging sensor; a proximity sensor (e.g., an infrared radiation detector, etc.); a depth sensor; an ambient light sensor; an ultrasonic transceiver; a microphone or other similar audio capture device; and the like.

[0194] The driver circuit 1822 may include software and hardware elements for controlling specific devices embedded in, attached to, or otherwise communicatively coupled to the UE 1800. The driver circuit 1822 may include various drivers to allow other components to interact with or control various input / output (I / O) devices that may be present in or connected to the UE 1800. For example, the driver circuit 1822 may include: a display driver for controlling and allowing access to a display device, a touch screen driver for controlling and allowing access to a touch screen interface, a sensor driver for obtaining sensor readings of the sensor circuit 1820 and controlling and allowing access to the sensor circuit 1820, a driver for obtaining an actuator position of an electromechanical component or controlling and allowing access to an electromechanical component, a camera driver for controlling and allowing access to an embedded image capture device, and an audio driver for controlling and allowing access to one or more audio devices.

[0195] The PMIC 1824 may manage power provided to various components of the UE 1800. Specifically, with respect to the processor 1804, the PMIC 1824 may control power selection, voltage scaling, battery charging, or DC-DC conversion.

[0196] In some embodiments, the PMIC 1824 may control or otherwise be part of various power saving mechanisms of the UE 1800. For example, if the platform UE is in the RRC_Connected state, in which the platform is still connected to the RAN node because it expects to receive traffic soon, then after a period of inactivity, the platform may enter a state known as discontinuous reception mode (DRX). During this state, the UE 1800 may be powered off for short time intervals, thereby saving power. If there is no data traffic activity for an extended period of time, the UE 1800 may transition to the RRC_Idle state, in which the UE is disconnected from the network and no operations such as channel quality feedback, handover, etc. are performed. The UE 1800 enters a very low power state and performs paging, in which the platform again periodically wakes up to listen to the network and then powers off again. The UE 1800 may not receive data in this state; in order to receive data, the platform must transition back to the RRC_Connected state. Additional power saving modes may prevent the device from using the network for longer than the paging interval (ranging from a few seconds to several hours). During this time, the device is completely unable to connect to the network and can be completely powered off. Any data sent during this time will be significantly delayed, and it is assumed that the delay is acceptable.

[0197] The battery 1828 can power the UE 1800, but in some examples, the UE 1800 can be installed in a fixed location and can have a power source coupled to the power grid. The battery 1828 can be a lithium-ion battery, a metal-air battery such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, etc. In some specific implementations, such as in vehicle-based applications, the battery 1828 can be a typical lead-acid car battery.

[0198] Fig.19 An exemplary gNB 1900 is shown according to some embodiments. The gNB 1900 may include a processor 1904, an RF interface circuit 1908, a core network (CN) interface circuit 1912, a memory / storage circuit 1916, and an antenna structure 1926.

[0199] Components of gNB 1900 may be coupled to various other components via one or more interconnects 1928.

[0200] The processor 1904, RF interface circuit 1908, memory / storage circuit 1916 (including communication protocol stack 1910), antenna structure 1926 and interconnect 1928 may be similar to those described in detail in the accompanying drawings. Fig.18 Like named elements are shown and described.

[0201] The CN interface circuit 1912 may provide connectivity for a core network (e.g., a 5th Generation Core Network (5GC) using a 5th Generation Core Network (5GC) compatible network interface protocol such as a Carrier Ethernet protocol or some other suitable protocol). Network connectivity may be provided to / from the gNB 1900 via optical fiber or wireless backhaul. The CN interface circuit 1912 may include one or more dedicated processors or FPGAs for communicating using one or more of the aforementioned protocols. In some implementations, the CN interface circuit 1912 may include multiple controllers for providing connectivity to other networks using the same or different protocols.

[0202] It is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of the authorized use should be clearly stated to users.

[0203] For one or more embodiments, at least one of the components shown in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes, or methods described in the following example section. For example, the baseband circuit described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the following examples. For another example, the circuits associated with the UE, base station, network element, etc. described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples shown in the example section below.

[0204] Example

[0205] In the following sections, additional exemplary embodiments are provided.

[0206] Embodiment 1 may include a method of operating a user equipment (UE), the method comprising: establishing a connection with a wireless local area network (WLAN) access point to access a network; determining that the UE has multimedia priority service (MPS) prioritization to indicate that the UE's service is to be prioritized; and transmitting an indication of the MPS prioritization for the UE to the WLAN access point.

[0207] Embodiment 2 may include the method of embodiment 1, wherein the indication of the MPS prioritization is included in an Internet Key Exchange Authorization (IKE_AUTH) request.

[0208] Embodiment 3 may include the method of embodiment 2, wherein the indication of the MPS prioritization is included in a notification payload of the IKE_AUTH request.

[0209] Embodiment 4 may include the method of embodiment 2, wherein the WLAN access point comprises an untrusted WLAN access point, and wherein the indication of the MPS prioritization is included in the IKE_AUTH request based at least in part on the WLAN access point comprising the untrusted WLAN access point.

[0210] Embodiment 5 may include the method of embodiment 1, wherein the indication of the MPS prioritization is included in a username portion of a network access identifier (NAI).

[0211] Embodiment 6 may include the method of embodiment 5, wherein the WLAN access point comprises a trusted WLAN access point, and wherein the indication of the MPS prioritization is included in the username portion of the NAI based at least in part on the WLAN access point comprising the trusted WLAN access point.

[0212] Embodiment 7 may include the method of embodiment 1, comprising transmitting an indication of an establishment cause to the WLAN access point, the establishment cause to be used to determine a differentiated services code point (DSCP) value for subsequent signaling related to the UE.

[0213] Embodiment 8 may include a method according to embodiment 1, the method comprising applying a quality of service identifier (QI) to differentiated services code point (DSCP) mapping to signaling via a third generation partnership project (3GPP) stack of the UE to prioritize the signaling between the 3GPP stack of the UE and a WLAN station (STA).

[0214] Embodiment 9 may include the method according to embodiment 1, the method comprising applying a differentiated services code point (DSCP) to WLAN protocol mapping to the signaling of the UE via the WLAN station (STA) of the UE to prioritize the signaling between the UE and the WLAN access point.

[0215] Embodiment 10 may include a method of operating a network structure, the method comprising: receiving an indication from a user equipment (UE) via a wireless local area network (WLAN) access point of the network structure that the UE has multimedia priority service (MPS) prioritization; and configuring the network structure to prioritize subsequent signaling of the UE via the WLAN access point based at least in part on the indication that the UE has MPS prioritization.

[0216] Embodiment 11 may include the method of embodiment 10, wherein the indication that the UE has MPS prioritization is received in an Internet Key Exchange Authorization (IKE_AUTH) request.

[0217] Embodiment 12 may include the method of Embodiment 11, wherein the indication that the UE has MPS prioritization is received in a notification payload of the IKE_AUTH request.

[0218] Embodiment 13 may include the method of embodiment 10, wherein the indication that the UE has MPS prioritization is received in a username portion of a network access identifier (NAI).

[0219] Embodiment 14 may include the method of embodiment 10, the method comprising receiving an indication of an establishment cause from the UE, and determining a differentiated services code point (DSCP) value for the subsequent signaling to the UE.

[0220] Embodiment 15 may include a method according to embodiment 10, wherein configuring the network structure includes generating a quality of service identifier (QI) to differentiated services code point (DSCP) mapping for the subsequent signaling of the UE based at least in part on the indication that the UE has MPS prioritization, and applying the QI to DSCP mapping to the subsequent signaling via a non-3rd Generation Partnership Project Interconnect Function (N3IWF) or a trusted non-3rd Generation Partnership Project Gateway Function (TNGF) to prioritize the subsequent signaling between the N3IWF or the TNGF and the WLAN access point.

[0221] Embodiment 16 may include a method according to embodiment 10, wherein configuring the network structure includes generating a differentiated services code point (DSCP) to WLAN protocol mapping for the subsequent signaling of the UE based at least in part on the indication that the UE has MPS prioritization, and applying the DSCP to the WLAN protocol mapping to the subsequent signaling via the WLAN access point to prioritize the subsequent signaling between the WLAN access point and the UE.

[0222] Embodiment 17 may include a method of operating a user equipment (UE), the method comprising: establishing a connection with a wireless local area network (WLAN) access point of a network; transmitting an indication of multimedia priority service (MPS) prioritization to the WLAN access point to indicate that the service of the UE is to be prioritized; and transmitting an indication of an establishment cause to the WLAN access point, the establishment cause being used to determine a differentiated services code point (DSCP) value for prioritizing signaling related to the UE.

[0223] Embodiment 18 may include the method of Embodiment 17, wherein the WLAN access point is part of an untrusted WLAN network, and wherein the indication of the MPS prioritization is transmitted in an Internet Key Exchange Authorization (IKE_AUTH) request based at least in part on the WLAN access point being part of the untrusted WLAN network.

[0224] Embodiment 19 may include the method of Embodiment 18, wherein the indication of the MPS prioritization is included in a notification payload of the IKE_AUTH request.

[0225] Embodiment 20 may include the method of embodiment 17, wherein the WLAN access point is part of a trusted WLAN network, and wherein the indication of the MPS prioritization is transmitted in a username portion of a network access identifier (NAI) based at least in part on the WLAN access point being part of the trusted WLAN network.

[0226] Embodiment 21 may include an apparatus comprising means for performing one or more elements of the method described in or related to any of Embodiments 1 to 20, or any other method or process described herein.

[0227] Embodiment 22 may include one or more non-transitory computer-readable media, which include instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of a method described in or related to any of Embodiments 1 to 20 or any other method or process described herein.

[0228] Embodiment 23 may include an apparatus comprising logic components, modules, or circuits for performing one or more elements of the method described in or related to any of Embodiments 1 to 20, or any other method or process described herein.

[0229] Embodiment 24 may include methods, techniques or processes described or related to any one of Embodiments 1 to 20, or parts or components thereof.

[0230] Embodiment 25 may include a device comprising: one or more processors and one or more computer-readable media, wherein the one or more computer-readable media include instructions that, when executed by the one or more processors, cause the one or more processors to perform a method, technique, or process, or a portion thereof, described in or related to any one of Embodiments 1 to 20.

[0231] Embodiment 26 may include a signal as described or related to any one of Embodiments 1 to 20, or a portion or component thereof.

[0232] Embodiment 27 may include a datagram, information element, packet, frame, segment, PDU or message, or a portion or component thereof, as described or related to any one of Embodiments 1 to 20, or otherwise described in the present disclosure.

[0233] Embodiment 28 may include a signal encoded with data as described or associated with any one of Embodiments 1 to 20, or a portion or component thereof, or otherwise described in this disclosure.

[0234] Embodiment 29 may include a signal encoded with a datagram, IE, packet, frame, segment, PDU or message as described or associated with any one of Embodiments 1 to 20, or a portion or component thereof, or otherwise described in the present disclosure.

[0235] Embodiment 30 may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors will cause the one or more processors to perform a method, technique, or process, or a portion thereof, described in or related to any one of Embodiments 1 to 20.

[0236] Embodiment 31 may include a computer program comprising instructions, wherein execution of the program by a processing element causes the processing element to perform a method, technique, or process described in or related to any one of Embodiments 1 to 20, or a portion thereof.

[0237] Embodiment 32 may include signals in a wireless network as shown and described herein.

[0238] Embodiment 33 may include a method of communicating in a wireless network as shown and described herein.

[0239] Embodiment 34 may include a system for providing wireless communications as shown and described herein.

[0240] Embodiment 35 may include an apparatus for providing wireless communications as shown and described herein.

[0241] Unless explicitly stated otherwise, any of the above examples may be combined with any other example (or combination of examples). The foregoing description of one or more specific implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise form disclosed. In view of the above teachings, modifications and variations are possible or can be obtained from the practice of various embodiments.

[0242] Although the above embodiments have been described in considerable detail, numerous variations and modifications will become apparent to those skilled in the art once the above disclosure is fully appreciated. It is intended that the following claims be interpreted to include all such variations and modifications.

Claims

1. One or more computer-readable media having instructions that, when executed, cause a processing circuit to: determining that a Universal Subscriber Identity Module (USIM) of a user equipment (UE) indicates that the UE is configured for priority access; and A notification payload is generated for transmission, the notification payload indicating the prioritization of the UE.

2. The one or more computer-readable media of claim 1 , wherein the instructions, when executed, further cause the processing circuit to: An Internet Key Exchange authentication IKE_AUTH request is generated for transmission, wherein the IKE_AUTH request includes the notification payload.

3. The one or more computer-readable media of claim 2, wherein the IKE_AUTH request is to be transmitted to an untrusted wireless local area network (WLAN) access point, and wherein the notification payload is included in the IKE_AUTH request based at least in part on the transmission of the IKE_AUTH request to the untrusted WLAN access point.

4. One or more computer-readable media according to any one of claims 1 to 3, wherein the USIM indicates that the UE is configured for priority access based at least in part on multimedia priority service (MPS) subscription information stored in the USIM.

5. The one or more computer-readable media of claim 4, wherein the instructions, when executed, further cause the processing circuit to: An indication of an establishment cause for transmission is generated based on the MPS subscription information.

6. One or more computer-readable media according to any one of claims 1 to 3, wherein the instructions, when executed, further cause the processing circuit to: A wireless local area network (WLAN) station (STA) of the UE applies a mapping of a differentiated services code point (DSCP) to a WLAN protocol to signaling of the UE, so as to prioritize the signaling between the UE and a WLAN access point.

7. One or more computer-readable media according to any one of claims 1 to 3, wherein the instructions, when executed, further cause the processing circuit to: A network access identifier NAI is generated for transmission, wherein the NAI includes a prioritization indication for the UE.

8. The one or more computer-readable media of claim 7, wherein the prioritization indication for the UE is included in a username portion of the NAI.

9. A method comprising: identifying a notification payload received from a user equipment (UE), the notification payload indicating prioritization of the UE; as well as The UEs are prioritized based at least in part on the prioritization.

10. The method of claim 9, wherein the UE is prioritized after the UE is authenticated.

11. The method of any one of claims 9 or 10, wherein the notification payload is received in an Internet Key Exchange Authentication (IKE_AUTH) request.

12. The method according to any one of claims 9 or 10, further comprising: identifying an indication of an establishment cause received from the UE; as well as A Differentiated Services Code Point (DSCP) value for subsequent signaling to the UE is determined based at least in part on the establishment cause.

13. The method according to any one of claims 9 or 10, further comprising: generating a quality of service identifier (QI) to differentiated services code point (DSCP) mapping for subsequent signaling of the UE based at least in part on the notification payload indicating prioritization; as well as The QI to DSCP mapping is applied to the subsequent signaling via a non-3GPP interworking function N3IWF or a trusted non-3GPP gateway function TNGF to prioritize the subsequent signaling between the N3IWF or the TNGF and a wireless local area network WLAN access point.

14. The method according to any one of claims 9 or 10, further comprising: generating a differentiated services code point (DSCP) to wireless local area network (WLAN) protocol mapping for subsequent signaling of the UE based at least in part on the notification payload indicating prioritization; as well as The DSCP to WLAN protocol mapping is applied to the subsequent signaling via a WLAN access point to prioritize the subsequent signaling between the WLAN access point and the UE.

15. A device, wherein: identifying a Multimedia Priority Service MPS indication received from a user equipment UE and included in a Network Access Identifier NAI; and The UE is prioritized based at least in part on the MPS indication. The apparatus of claim 15 , wherein the UE is prioritized after the UE is authenticated.

17. The apparatus of claim 15, wherein the MPS indication is included in a username portion of the NAI.

18. The device according to any one of claims 15 to 17, wherein the device is further used for: identifying an indication of an establishment cause received from the UE; and A Differentiated Services Code Point (DSCP) value for subsequent signaling to the UE is determined based at least in part on the establishment cause.

19. The device according to any one of claims 15 to 17, wherein the device is further used for: generating a quality of service identifier (QI) to differentiated services code point (DSCP) mapping for subsequent signaling of the UE based at least in part on the MPS indication; and The QI to DSCP mapping is applied to the subsequent signaling via a non-3GPP interworking function N3IWF or a trusted non-3GPP gateway function TNGF to prioritize the subsequent signaling between the N3IWF or the TNGF and a wireless local area network WLAN access point.

20. The device according to any one of claims 15 to 17, wherein the device is further used for: generating a differentiated services code point (DSCP) to wireless local area network (WLAN) protocol mapping for subsequent signaling of the UE based at least in part on the MPS indication; and The DSCP to WLAN protocol mapping is applied to the subsequent signaling via a WLAN access point to prioritize the subsequent signaling between the WLAN access point and the UE.

Images