User equipment registration

The adoption of the QUIC protocol for user equipment registration in 5G networks over non-3GPP access networks addresses inefficiencies in existing protocols by establishing secure and efficient connections, reducing latency and enhancing performance through simplified and secure communication.

WO2024235491A1PCT designated stage expired Publication Date: 2024-11-21LENOVO (SINGAPORE) PTE LTD

Patent Information

Application Number
PCT/EP2024/051992
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2024-01-12
Filing Date
2024-01-26
Publication Date
2024-11-21

AI Technical Summary

Technical Problem

Current wireless communication systems, particularly in 5G networks, face inefficiencies and complexities due to the reliance on outdated protocols like IKEv2/IPsec for secure connections over non-3GPP access networks, leading to increased latency, processing overhead, and potential points of failure.

Method used

Implementing the QUIC protocol for user equipment (UE) registration with a mobile communication network via an untrusted non-3GPP access network, which establishes two QUIC connections using an authentication key generated during the registration procedure, simplifying the protocol stack and enhancing security and performance.

Benefits of technology

This approach reduces latency, simplifies the protocol stack, provides strong security without complexity, and improves overall performance by leveraging QUIC's built-in encryption and streamlined handshake mechanisms, aligning with modern 5G network requirements.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure EP2024051992_21112024_PF_FP_ABST
    Figure EP2024051992_21112024_PF_FP_ABST
Patent Text Reader

Abstract

Various aspects of the present disclosure relate to a user equipment (UE), comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the UE to: perform a discovery of a non-3GPP interworking function that supports a connectivity with a mobile communication network using a QUIC protocol; in response to the discovery of the non-3GPP interworking function, establish a first QUIC connection with the non-3GPP interworking function via a non-3GPP access network; initiate a registration procedure with the mobile communication network via the first QUIC connection; terminate the first QUIC connection and establish a second QUIC connection with the non-3GPP interworking function via the non-3GPP access network using an authentication key generated during the registration procedure; and resume the registration procedure via the second QUIC connection.
Need to check novelty before this filing date? Find Prior Art

Description

USER EQUIPMENT REGISTRATIONTECHNICAL FIELD

[0001] The present disclosure relates to wireless communications, and more specifically to registering a user equipment (UE) with a network via an access network (e.g., an untrusted non-3GPP access network).BACKGROUND

[0002] A wireless communications system may include one or multiple network communication devices, such as base stations, which may support wireless communications for one or multiple user communication devices, which may be otherwise known as user equipment (UE), or other suitable terminology. The wireless communications system may support wireless communications with one or multiple user communication devices by utilizing resources of the wireless communication system (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers, or the like). Additionally, the wireless communications system may support wireless communications across various radio access technologies including third generation (3G) radio access technology, fourth generation (4G) radio access technology, fifth generation (5G) radio access technology, among other suitable radio access technologies beyond 5G (e.g., sixth generation (6G)).SUMMARY

[0003] An article “a” before an element is unrestricted and understood to refer to “at least one” of those elements or “one or more” of those elements. The terms “a,” “at least one,” “one or more,” and “at least one of one or more” may be interchangeable. As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of’ or “one or more of’ or “one or both of’) indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Also, as used herein, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a condition Bwithout departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be constmed in the same manner as the phrase “based at least in part on. Further, as used herein, including in the claims, a “set” may include one or more elements.

[0004] Some implementations of the method and apparatuses described herein may include a UE, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the UE to: perform a discovery of a non-3GPP interworking function that supports a connectivity with a mobile communication network using a QUIC protocol; in response to the discovery of the non-3GPP interworking function, establish a first QUIC connection with the non-3GPP interworking function via a non-3GPP access network; initiate a registration procedure with the mobile communication network via the first QUIC connection; terminate the first QUIC connection and establish a second QUIC connection with the non-3GPP interworking function via the non-3 GPP access network using an authentication key generated during the registration procedure; and resume the registration procedure via the second QUIC connection.

[0005] The discovery of the non-3 GPP interworking function that supports the connectivity with the mobile communication network using the QUIC protocol may be based on a network identifier associated with the non-3 GPP interworking function.

[0006] The at least one processor may be configured to cause the UE to: transmit a domain name system (DNS) query request message comprising one or more fully qualified domain name (FQDN) parameters, wherein at least one FQDN parameter indicates a requirement that the non-3 GPP interworking function supports the connectivity with the mobile communication network using the QUIC protocol; and receive a DNS query response message comprising the identifier associated with the non-3 GPP interworking function.

[0007] The at least one processor may be configured to cause the UE to: transmit a DNS service record query; receive a DNS service record based on the DNS service record query, the DNS service record comprising a host name and a port number; and obtain the network identifier using the host name and port number.

[0008] The at least one processor may be configured to cause the UE to establish the first QUIC connection with the non-3GPP interworking function via the non-3GPP access network based on the identifier associated with the non-3GPP interworking function.

[0009] To initiate the registration procedure the at least one processor may be configured to cause the UE to: transmit, to the non-3GPP interworking function via the first QUIC connection, a first QUIC message comprising a registration request and a first identifier of the UE.

[0010] To establish the second QUIC connection with the non-3GPP interworking function the at least one processor may be configured to cause the UE to: transmit a request for establishment of the second QUIC connection, via the non-3GPP access network, to the non-3GPP interworking function; the request comprising a second identifier, that is based on the first identifier of the UE, to indicate that the authentication key is to be used to authenticate the UE.

[0011] The second identifier of the UE may be the same as the first identifier of the UE.

[0012] The at least one processor may be configured to cause the UE to derive the second identifier from the first identifier.

[0013] The at least one processor may be configured to cause the UE to: perform an authentication procedure with at least one network entity via the first QUIC connection to derive the authentication key.

[0014] The at least one processor may be configured to cause the UE to: receive an indication that the first QUIC connection is terminated and to establish the second QUIC connection with the non-3GPP interworking function via the non-3 GPP access network using the authentication key.

[0015] To resume the registration procedure the at least one processor may be configured to cause the UE to: receive a registration accept message via the second QUIC connection.

[0016] The at least one processor may be configured to cause the UE to: transmit one or more non-access stratum (NAS) messages via the second QUIC connection, or receive the one or more NAS messages via the second QUIC connection, or a combination thereof.

[0017] Some implementations of the method and apparatuses described herein may further include a processor comprising: at least one controller coupled with at least one memory and configured to cause the processor to: perform a discovery of a non-3GPP interworking function that supports a connectivity with a mobile communication network using a QUIC protocol; in response to the discovery of the non-3GPP interworking function, establish a first QUIC connection with the non-3GPP interworking function via a non-3GPP access network, initiate a registration procedure with the mobile communication network via the first QUIC connection; terminate the first QUIC connection and establish a second QUIC connection with the non-3GPP interworking function via the non-3 GPP access network using an authentication key generated during the registration procedure; and resume the registration procedure via the second QUIC connection.

[0018] Some implementations of the method and apparatuses described herein may further include a method comprising: performing a discovery of a non-3 GPP interworking function that supports a connectivity with a mobile communication network using a QUIC protocol; in response to the discovery of the non-3 GPP interworking function, establishing a first QUIC connection with the non-3 GPP interworking function via a non-3 GPP access network, initiating a registration procedure with the mobile communication network via the first QUIC connection; terminating the first QUIC connection and establishing a second QUIC connection with the non-3 GPP interworking function via the non-3 GPP access network using an authentication key generated during the registration procedure; and resuming the registration procedure via the second QUIC connection.

[0019] Some implementations of the method and apparatuses described herein may further include a network entity comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the network entity to: establish, via a non-3 GPP access network, a first QUIC connection to a UE; facilitate a registration procedure between the UE and a mobile communication network via the first QUIC connection; terminate the first QUIC connection; establish, via the non-3 GPP access network, a second QUIC connection to the UE, using an authentication key generated during the registration procedure; and resume the registration procedure via the second QUIC connection.

[0020] The at least one processor may be configured to cause the network entity to: receive via the first QUIC connection, a first QUIC message from the UE, the first QUIC message comprising a registration request and a first identifier of the UE.

[0021] The at least one processor may be configured to cause the network entity to: receive, from the UE, a request for establishment of the second QUIC connection, via the non-3GPP access network, wherein the request comprises a second identifier of the UE, wherein the second identifier is based on the first identifier of the UE, wherein the second identifier indicates the authentication key for authenticating the UE; and establish the second QUIC connection based on a successful authentication of the UE using the authentication key.

[0022] The second identifier of the UE may be the same as the first identifier of the UE, and wherein the at least one processor may be configured to cause the network entity to: store the authentication key in the at least one memory in association with the first identifier of the UE; and retrieve the authentication key from the at least one memory based on the first identifier of the UE.

[0023] The second identifier of the UE may be derived from the first identifier of the UE, and the at least one processor may be configured to cause the network entity to: derive the second identifier of the UE from the first identifier of the UE; store the authentication key in the at least one memory in association with the second identifier of the UE; and retrieve the authentication key from the at least one memory using the second identifier of the UE.BRIEF DESCRIPTION OF THE DRAWINGS

[0024] Figure 1 illustrates an example of a network architecture.

[0025] Figure 2a illustrates an example of a control plane stack before a IPsec Security Association is established between a UE and a non-3GPP interworking.

[0026] Figure 2b illustrates an example of a control plane stack after a IPsec Security Association is established between a UE and a non-3GPP interworking function.

[0027] Figure 3 illustrates an example of a wireless communications system in accordance with aspects of the present disclosure.

[0028] Figure 4 illustrates a network architecture in accordance with aspects of the present disclosure.

[0029] Figure 5 illustrates an example of a process to register a user equipment with a network via an untrusted non-3GPP access network in accordance with aspects of the present disclosure.

[0030] Figure 6 illustrates a control plane stack in accordance with aspects of the present disclosure.

[0031] Figure 7 illustrates an example of a UE 700 in accordance with aspects of the present disclosure.

[0032] Figure 8 illustrates an example of a processor 800 in accordance with aspects of the present disclosure.

[0033] Figure 9 illustrates an example of a NE 900 in accordance with aspects of the present disclosure.

[0034] Figure 10 illustrates a flowchart of a method performed by a UE in accordance with aspects of the present disclosure.

[0035] Figure 11 illustrates a flowchart of method performed by a NE in accordance with aspects of the present disclosure.DETAILED DESCRIPTION

[0036] Figure 1 illustrates an example of a network architecture 100 which may include one or more of an un-trusted non-3GPP access network 103, a UE 104, an N3IWF 105, or a 5G CN 106. The UE 104 may connect to (e.g., establish a connection with) the 5G CN 106 via the untrusted non-3GPP access network 103, which may be, for example, Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), Wireless Local Area Network(WLAN), and the like. The UE 104 may connect to (e.g., establish a connection with) the 5G CN 106 to access one or more services or applications for the UE 104.

[0037] In the example of Figure 1, the UE 104 may connect to (e.g., establish a connection with) the 5G CN 106 via the N3IWF 105. For example, the N3IWF 105 may exchange signaling (e.g., transmit, receive) with the UE 104 via an NWu interface. Additionally, or alternatively, the N3IWF 106 may exchange signaling (e.g., transmit, receive) with the 5G CN 106 via a network interface (e.g., N2, N3). Additionally, or alternatively, the UE 104 may connect to (e.g., establish a connection with) the 5G CN 106 via a trusted non-3GPP access network (not shown). For example, the UE 104 may connect to (e.g., establish a connection with) the 5G CN 106 via an interworking function that is a Trusted Non-3GPP Gateway Function (TNGF) (not shown).

[0038] Figure 2a illustrates an example of a control plane stack before an IPsec Security Association is established between a UE and a non-3GPP interworking function.

[0039] Figure 2b illustrates an example of a control plane after a IPsec Security Association is established between a UE and a non-3GPP interworking function.

[0040] The protocol stack on the NWu interface, as depicted in Figures 2a and 2b is complicated and outdated. It involves multiple layers including IPsec, IKEv2 for establishing IPsec Security Associations (SAs), and the EAP-5G protocol for transporting NAS messages before the establishment of a signaling IPsec AS, etc. It applies IPsec in tunnel mode, which brings a lot of overhead as the UE is assigned an “inner IP” address and all data created by the UE is encapsulated in an inner IP packet, which subsequently is encapsulated in the outer IP packet. This stack was designed for an era when the latency and the transport efficiency requirements over non-3GPP access were less stringent.

[0041] The IKEv2 protocol is used between the UE and the N3IWF to establish IPsec security associations that support secure exchange of NAS signalling messages. The reliance on IKEv2 and the subsequent establishment of IPsec SAs adds complexity and overhead due to the multiple exchanges required to set up a secure connection. This increases latency, consumes more processing power, and can potentially introduce more points of failure. Furthermore, as UE devices and network functions evolve with more advanced capabilities,continuing to use IKEv2 / IPsec may hinder the exploitation of these capabilities to their fullest potential.

[0042] In contrast, the QUIC protocol, a modern transport layer network protocol designed by the Internet Engineering Task Force (IETF), presents a compelling alternative. QUIC integrates security and transport functionalities into a single protocol layer, effectively streamlining the stack. It also offers reduced connection and transport latency through fewer round trips and zero round trip times (0-RTT) for subsequent connections, which is particularly advantageous for mobile networks where latency can significantly impact user experience.

[0043] Additionally, QUIC operates over the User Datagram Protocol (UDP), which is simpler and more efficient than Transmission Control Protocol (TCP), particularly in handling packet loss — a common issue in wireless networks. This efficiency, coupled with QUIC's built-in encryption and streamlined handshake mechanisms, makes it a robust choice for the NWu interface, ensuring end-to-end security that aligns with the requirements of modern 5G networks.

[0044] Embodiment of the present disclosure relate to updating the NWu interface to use the QUIC protocol. This enables modernization of the 5G network architecture, improve efficiency, and provide a more seamless and secure user experience, leveraging the full potential of 5G connectivity. Employing QUIC over the NWu interface provides several advantages, including:• Reduced Latency: By minimizing the number of handshakes required to establish a secure connection, QUIC can significantly reduce the time it takes for a UE to connect to the 5G Core Network.• Simplified Protocol Stack: QUIC's combined approach to transport and security protocols simplifies the protocol stack, making it easier to implement and maintain. Modem UEs already support the QUIC protocol for enabling web browsing using HTTP / 3 and reusing the QUIC protocol over NWu presents a compelling choice.• Reduced complexity: QUIC provides strong security guarantees with built-in encryption, similar to what is achieved with IKEv2 / IPsec, but without the associated complexity.• Enhanced Performance: QUIC's improved congestion control and avoidance of head- of-line blocking over UDP can lead to better overall performance, particularly in environments with packet loss and variable network conditions.• Future-Proofing: As a protocol under active development, QUIC is better suited to adapt to future changes and requirements in the 5G ecosystem.

[0045] Aspects of the present disclosure are described in the context of a wireless communications system.

[0046] Figure 3 illustrates an example of a wireless communications system 300 in accordance with aspects of the present disclosure. The wireless communications system 300 may include one or more NE 102, one or more UE 104, and a CN 106. The wireless communications system 300 may support various radio access technologies. In some implementations, the wireless communications system 300 may be a 4G network, such as an LTE network or an LIE -Advanced (LTE-A) network. In some other implementations, the wireless communications system 300 may be a NR network, such as a 5G network, a 5G- Advanced (5G-A) network, or a 5G ultrawideband (5G-UWB) network. In other implementations, the wireless communications system 300 may be a combination of a 4G network and a 5G network, or other suitable radio access technology including Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20. The wireless communications system 300 may support radio access technologies beyond 5G, for example, 6G. Additionally, the wireless communications system 300 may support technologies, such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA), etc.

[0047] The one or more NE 102 may be dispersed throughout a geographic region to form the wireless communications system 300. One or more of the NE 102 described herein may be or include or may be referred to as a network node, a base station, a network element, a network function, a network entity, a radio access network (RAN), a NodeB, an eNodeB (eNB), a next-generation NodeB (gNB), or other suitable terminology. An NE 102 and a UE 104 may communicate via a communication link, which may be a wireless or wired connection. For example, an NE 102 and a UE 104 may perform wireless communication (e.g., receive signaling, transmit signaling) over a Uu interface.

[0048] An NE 102 may provide a geographic coverage area for which the NE 102 may support services for one or more UEs 104 within the geographic coverage area. For example, an NE 102 and a UE 104 may support wireless communication of signals related to services (e.g., voice, video, packet data, messaging, broadcast, etc.) according to one or multiple radio access technologies. In some implementations, an NE 102 may be moveable, for example, a satellite associated with a non-terrestrial network (NTN). In some implementations, different geographic coverage areas 112 associated with the same or different radio access technologies may overlap, but the different geographic coverage areas may be associated with different NE 102.

[0049] The one or more UE 104 may be dispersed throughout a geographic region of the wireless communications system 300. A UE 104 may include or may be referred to as a remote unit, a mobile device, a wireless device, a remote device, a subscriber device, a transmitter device, a receiver device, or some other suitable terminology. In some implementations, the UE 104 may be referred to as a unit, a station, a terminal, or a client, among other examples. Additionally, or alternatively, the UE 104 may be referred to as an Internet-of- Things (loT) device, an Internet-of-Everything (loE) device, or machine-type communication (MTC) device, among other examples.

[0050] A UE 104 may be able to support wireless communication directly with other UEs 104 over a communication link. For example, a UE 104 may support wireless communication directly with another UE 104 over a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular-V2X deployments, the communication link 114 may be referred to as a sidelink. F or example, a UE 104 may support wireless communication directly with another UE 104 over a PC5 interface.

[0051] An NE 102 may support communications with the CN 106, or with another NE 102, or both. For example, an NE 102 may interface with other NE 102 or the CN 106 through one or more backhaul links (e.g., SI, N2, N2, or network interface). In some implementations, the NE 102 may communicate with each other directly. In some other implementations, the NE 102 may communicate with each other or indirectly (e.g., via the CN 106. In some implementations, one or more NE 102 may include subcomponents, such as an accessnetwork entity, which may be an example of an access node controller (ANC). An ANC may communicate with the one or more UEs 104 through one or more other access network transmission entities, which may be referred to as a radio heads, smart radio heads, or transmission-reception points (TRPs).

[0052] The CN 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. The CN 106 may be an evolved packet core (EPC), or a 5G core (5GC), which may include a control plane entity that manages access and mobility (e.g., a mobility management entity (MME), an access and mobility management functions (AMF)) and a user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW), a Packet Data Network (PDN) gateway (P-GW), or a user plane function (UPF)). In some implementations, the control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signal bearers, etc.) for the one or more UEs 104 served by the one or more NE 102 associated with the CN 106.

[0053] The CN 106 may communicate with a packet data network over one or more backhaul links (e.g., via an SI, N2, N2, or another network interface). The packet data network may include an application server. In some implementations, one or more UEs 104 may communicate with the application server. A UE 104 may establish a session (e.g., a protocol data unit (PDU) session, or the like) with the CN 106 via an NE 102. The CN 106 may route traffic (e.g., control information, data, and the like) between the UE 104 and the application server using the established session (e.g., the established PDU session). The PDU session may be an example of a logical connection between the UE 104 and the CN 106 (e.g., one or more network functions of the CN 106).

[0054] In the wireless communications system 300, the NEs 102 and the UEs 104 may use resources of the wireless communications system 300 (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communications). In some implementations, the NEs 102 and the UEs 104 may support different resource structures. For example, the NEs 102 and the UEs 104 may support different frame structures. In some implementations, such as in 4G, the NEs 102 and the UEs 104 may support a single frame structure. In some otherimplementations, such as in 5G and among other suitable radio access technologies, the NEs 102 and the UEs 104 may support various frame structures (i.e., multiple frame structures). The NEs 102 and the UEs 104 may support various frame structures based on one or more numerologies.

[0055] One or more numerologies may be supported in the wireless communications system 300, and a numerology may include a subcarrier spacing and a cyclic prefix. A first numerology (e.g., / r=0) may be associated with a first subcarrier spacing (e.g., 15 kHz) and a normal cyclic prefix. In some implementations, the first numerology (e.g., / r=0) associated with the first subcarrier spacing (e.g., 15 kHz) may utilize one slot per subframe. A second numerology (e.g., / r=l) may be associated with a second subcarrier spacing (e.g., 30 kHz) and a normal cyclic prefix. A third numerology (e.g., / r=2) may be associated with a third subcarrier spacing (e.g., 60 kHz) and a normal cyclic prefix or an extended cyclic prefix. A fourth numerology (e.g., / r=3) may be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a normal cyclic prefix. A fifth numerology (e.g., / r=4) may be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a normal cyclic prefix.

[0056] A time interval of a resource (e.g., a communication resource) may be organized according to frames (also referred to as radio frames). Each frame may have a duration, for example, a 10 millisecond (ms) duration. In some implementations, each frame may include multiple subframes. For example, each frame may include 10 subframes, and each subframe may have a duration, for example, a 1 ms duration. In some implementations, each frame may have the same duration. In some implementations, each subframe of a frame may have the same duration.

[0057] Additionally or alternatively, a time interval of a resource (e.g., a communication resource) may be organized according to slots. For example, a subframe may include a number (e.g., quantity) of slots. The number of slots in each subframe may also depend on the one or more numerologies supported in the wireless communications system 300. For instance, the first, second, third, fourth, and fifth numerologies (i.e., / r=0, jU=l , / r=2, jU=3, / r=4) associated with respective subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz may utilize a single slot per subframe, two slots per subframe, four slots per subframe, eight slots per subframe, and 16 slots per subframe, respectively. Each slot mayinclude a number (e.g., quantity) of symbols (e.g., OFDM symbols). In some implementations, the number (e.g., quantity) of slots for a subframe may depend on a numerology. For a normal cyclic prefix, a slot may include 14 symbols. For an extended cyclic prefix (e.g., applicable for 60 kHz subcarrier spacing), a slot may include 12 symbols. The relationship between the number of symbols per slot, the number of slots per subframe, and the number of slots per frame for a normal cyclic prefix and an extended cyclic prefix may depend on a numerology. It should be understood that reference to a first numerology (e.g., / i =0) associated with a first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframes and slots.

[0058] In the wireless communications system 300, an electromagnetic (EM) spectrum may be split, based on frequency or wavelength, into various classes, frequency bands, frequency channels, etc. By way of example, the wireless communications system 300 may support one or multiple operating frequency bands, such as frequency range designations FR1 (410 MHz - 7.125 GHz), FR2 (24.25 GHz - 52.6 GHz), FR3 (7.125 GHz - 24.25 GHz), FR4 (52.6 GHz - 114.25 GHz), FR4a or FR4-1 (52.6 GHz - 71 GHz), and FR5 (114.25 GHz - 300 GHz). In some implementations, the NEs 102 and the UEs 104 may perform wireless communications over one or more of the operating frequency bands. In some implementations, FR1 may be used by the NEs 102 and the UEs 104, among other equipment or devices for cellular communications traffic (e.g., control information, data). In some implementations, FR2 may be used by the NEs 102 and the UEs 104, among other equipment or devices for short-range, high data rate capabilities.

[0059] FR1 may be associated with one or multiple numerologies (e.g., at least three numerologies). For example, FR1 may be associated with a first numerology (e.g., / r=0), which includes 15 kHz subcarrier spacing; a second numerology (e.g., / r=l), which includes 30 kHz subcarrier spacing; and a third numerology (e.g., / r=2), which includes 60 kHz subcarrier spacing. FR2 may be associated with one or multiple numerologies (e.g., at least 2 numerologies). For example, FR2 may be associated with a third numerology (e.g., / r=2), which includes 60 kHz subcarrier spacing; and a fourth numerology (e.g., / r=3), which includes 120 kHz subcarrier spacing.

[0060] In the wireless communications system 300, a UE 104 may connect to (e.g., establish a connection with) a CN 106 (e.g., a 5G CN) via an untrusted non-3GPP access network, which may be, for example, IEEE 802.11 (Wi-Fi), WLAN, and the like. The UE 104 may connect to (e.g., establish a connection with) the CN 106 to access one or more services or applications for the UE 104. As described herein with reference to Figure 1, the UE 104 may connect to (e.g., establish a connection with) to the CN 106 via an N3IWF. For example, the N3IWF may exchange signaling (e.g., transmit, receive) with the UE 104 via an NWu interface. Additionally, or alternatively, the N3IWF may exchange signaling (e.g., transmit, receive) with the CN 106 via a network interface (e.g., N2, N3). Additionally, or alternatively, the UE 104 may connect to (e.g., establish a connection with) the CN 106 via a trusted non-3GPP access network. For example, the UE 104 may connect to (e.g., establish a connection with) the CN 106 via a TNGF. Figure 4 illustrates an example network architecture 400 in accordance with aspects of the present disclosure. In some implementations, the network architecture 400 may implement or be implemented by aspects of the network architecture 100 or the wireless communications system 300 as described herein with reference to Figures 1 and 3. For example, the network architecture 400 may include a UE 104, which may be an example of a UE 104 as described herein with reference to Figures 1 and 3. The network architecture 400 may include a cellular base unit 102a and an access point 102b, which may be examples of NE 102 as described herein with reference to Figures 1 and 3. The network architecture 400 may include anN3IWF 105, which may be an example of an N3IWF as described herein with reference to Figure 1. The network architecture 400 may include a CN 106 (e.g., a mobile core network), which may be an example of a CN as described herein with reference to Figures 1 and 3.

[0061] The UE104 may establish a connection (e.g., a session) with the CN 106 (e.g., a 5G CN) via at least one or more access networks, such as a 3GPP access network 120 (also referred to as a trusted 3 GPP access network) or a non-3GPP access network 103 (e.g. an untrusted non-3GPP access network, a trusted non-3GPP access network, or a wireline non- 3GPP access network). The 3GPP access network 120 may be associated with a first radio access technology (e.g., 4G, 5G), while the non-3GPP access network 103 may be associated with a second radio access technology (e.g., Wi-Fi, WLAN). For example, the 3GPP access network 120 may support cellular communications, for example, with the UE 104 via thecellular base unit 102a, while the non-3GPP access network may support non-cellular communication (e.g., Wi-Fi communication, WLAN communication) with the UE 104 via the access point 102b. The non-3GPP access network 103 may communicate with the CN 106 via an interworking function (e.g. the N3IWF 105) and over one or more network interfaces (e.g., N2, N3).

[0062] The CN 106 may include one or more network functions, which may include one or more of a user plane function (UPF) 141, an access and mobility management function (AMF) 143, a session management function (SMF) 145, a policy control function network entity (PCF) 147, an Authentication Server Function (AUSF) 148, or a Unified Data Management network entity (UDM) 149.

[0063] Aspects of the present disclosure relate to registering the UE 104 with the CN 106 (e.g., a mobile core network) via the non-3GPP access network 103 using a QUIC protocol. As an example, embodiments are described below with reference to the non-3GPP access network 103 being an untrusted non -3 GPP access network 103.

[0064] Figure 5 illustrates a process to register the UE 104 with the CN 106 via the untrusted non-3GPP access network 103 using the QUIC protocol.

[0065] At step S502, the UE 104 connects to an untrusted non-3GPP access network 103 and obtains IP connectivity, i.e., it receives IP configuration data including an IP address. That is, the UE 104 is allocated an IP address.

[0066] At step S504, the UE 104 discovers a N3IWF 105 that supports connectivity with the CN106 using the QUIC protocol. Step S502 can be performed in a number of different ways.

[0067] Currently, when the UE wants to discover a network identifier (e.g. the IP address) of an N3IWF in a PLMN, the UE performs a DNS query using either: a) an Operator identifier based FQDN, in the form: "n3iwf.5gc.mnc<MNC>.mcc<MCC>.pub.3gppnetwork.org"; or b) a Tracking Area Identity based FQDN, in the form: "tac-lb<TAC-low-byte>.tac-hb<TAC- high-byte>.tac.n3iwf.5gc.mnc<MNC>.mcc<MCC>.pub.3gppnetwork.org". An Operator identifier based FQDN is used when the UE wants to discover any N3IWF in a specific PLMN. The Tracking Area Identity based FQDN is used when the UE wants to discover aN3IWF in a specific PLMN that is located in a specific tracking area in this PLMN. The discovered N3IWF with this method is assumed to support the IKEv2 protocol.

[0068] In order for the UE to discover a N3IWF that supports connectivity with the CN 106 using the QUIC protocol, at step S504, the UE 104 may transmit a domain name system (DNS) query request message comprising one or more fully qualified domain name (FQDN) parameters, wherein at least one FQDN parameter indicates a requirement that the non-3GPP interworking function supports connectivity with the CN 106 using the QUIC protocol. For example, a service tag specific to QUIC, such as "quic-n3iwf", could be included in the FQDN to indicate that the N3IWF must support QUIC. This would make the DNS query for a QUIC -supporting N3IWF look like "quic- n3iwf.5gc.mnc012.mcc345.pub.3gppnetwork.org" (Operator identifier based FQDN for QUIC) or "tac-lb21.tac-hb0b.tac.quic-n3iwf.5gc.mnc012.mcc345.pub. 3gppnetwork.org" (Tracking Area Identity based FQDN for QUIC). The UE 104 may transmit the DNS query request message to a DNS server. The UE 104 may receive a DNS query response message comprising the network identifier (e.g. the IP address) of a N3IWF that supports connectivity with the CN 106 using the QUIC protocol.

[0069] In order for the UE to discover a N3IWF that supports connectivity with the CN 106 using the QUIC protocol, at step S504, the UE 104 may alternatively transmit a DNS service record query for one or more DNS System Service (SRV) records. DNS SRV records can be used to specify the location of services for specified protocols. DNS SRV records allow a service to be identified by a hostname and port number, and they can also be prioritized and weighted for load balancing. As a mere example, the SRV record for an N3IWF supporting QUIC could look like:_quic._udp.n3iwf.5gc. mnc012.mcc345.pub.3gppnetwork.org; or_quic._udp.tac-lb21.tac-hb0b.tac.n3iwf.5gc.mnc012.mcc345.pub.3gppnetwork.orgIn this case, quic indicates the QUIC protocol, and _udp specifies the underlying transport layer protocol.

[0070] The UE 104 may transmit the DNS service record query to a DNS server. The UE 104 may receive a DNS SRV record comprising a host name and a port number. The UE 104 is then able to resolve the host name to the IP address of a non-3GPP interworking functionthat supports connectivity with the CN 106 using the QUIC protocol. The UE 104 may transmit a DNS query comprising the host name to a DNS server. The UE 104 may then receive a DNS query response message comprising the network identifier (e.g. the IP address) of a N3IWF that supports connectivity with the CN 106 using the QUIC protocol.

[0071] After the UE discovers the network identifier (e.g. the IP address) for the N3IWF105, at step S506 the UE 104 establishes a first QUIC connection with the N3IWF. Compared to the known approaches of using IKEv2 as the transport protocol, QUIC incorporates features of both TCP and TLS, potentially reducing connection and transport latencies.

[0072] The first QUIC connection is a temporary QUIC connection used to support the registration procedure until a N3IWF key (otherwise referred to herein as an authentication key) is derived. During the connection establishment phase, the N3IWF 105 may provide a certificate to the UE 104 and security is established between the UE 104 and N3IWF 105. At this stage, the UE 104 is not yet authenticated by the CN 106. In the context of registration to a 5G CN 106, the Application-Layer Protocol Negotiation (ALPN) element exchanged during the connection establishment phase comprises a special value (e.g., “5g-nas”), which indicates that the 5G-NAS protocol will operate over the QUIC connection and 5G-NAS protocol data units (PDUs) will be exchanged. The UE 104 is not authenticated during the establishment of the first QUIC connection.

[0073] At step S508, the UE 104 initiates a registration procedure with the CN 106 via the first QUIC connection. In particular, at step S508, the UE 104 transmits a first QUIC message to the N3IWF 105. The UE 104 transmits the first QUIC message to the N3IWF 105 using the first QUIC connection. The first QUIC message comprising a request to register the UE, wherein the first QUIC message includes an identifier of the UE (UE Id) otherwise referred to herein as a “first identifier” of the UE. The first QUIC message may be a QUIC STREAM frame that contains Access Network parameters (AN-Params) and a NAS-PDU containing a registration request message.

[0074] The AN-Params may contain information as specified in TS 23.502 and therefore include information that is used by the N3IWF 105 for selecting an AMF 143 in the 5G CN106. This information includes e.g., the GUAMI, the Selected PLMN ID (or PLMN ID andNID), the requested NSSAI and the establishment cause. The establishment cause provides the reason for requesting a NAS connection with the 5G CN 106.

[0075] The UE 104 may include the UE Id in the AN-Params. This could be a 5G identity (e.g., 5G-GUTI) allocated to the UE 104 from a prior registration to the same PLMN. In another example, the UE Id may be a value generated by the UE, e.g., a random value. In yet another example, the UE Id may be a unique identifier of the UE 104, such as an IMEI, a SUPI (subscription permanent identifier), a SUCI (subscription concealed identifier), etc. This UE Id is used later on in the process 500 as described below.

[0076] The transmission of the first QUIC message to the N3IWF 105 at step S508 triggers a registration procedure for untrusted non-3GPP access that is performed via the first QUIC connection. The N3IWF 105 is configured to facilitate the registration procedure between the UE 104 and the CN 106 by acting as an intermediary for the exchange of messages between the UE 104 and the AMF 143.

[0077] At step S510 the N3IWF 105 selects an AMF 143 and at step S512 forwards the received registration request message to the selected AMF 143.

[0078] As part of the registration procedure, at step S514 the AMF may request a UE device identity (e.g., an IMEI) of the UE 104, hence, the AMF 143 may transmit an identity request to the UE 104 and receive an identify response from the UE 104.

[0079] At step S516, a mutual authentication procedure is executed between the UE 104 and the AUSF in the CN 106. The mutual authentication procedure may be based on the EAP-AKA’ protocol.

[0080] If the authentication is successful, the same anchor key (e.g. a SEAF key) is generated in the UE 104 and in the AUSF 148. During the authentication procedure shown in Figure 5, the UE 104 generates the anchor key (e.g. a SEAF key) in response to receiving an authentication request transmitted from the AMF 143 via the N3IWF 105. The UE uses the anchor key to derive an N3IWF key. On the network side, the AUSF 148 generates the anchor key (e.g. a SEAF key) in response to receiving a challenge from the AMF 143. The AUSF 148 transmits a response to the challenge, the response comprising the anchor key. The AMF 143 uses the anchor key to derive a N3IWF key. The N3IWF key in the UE andthe N3IWF key in the N3IWF should be the same, hence, the N3IWF key may be referred to as a common or pre-shared key.

[0081] At step S518, the NAS Security Mode Command / Complete messages may be exchanged to establish a NAS security context between the UE 104 and the AMF 143 via the N3IWF 105.

[0082] Steps S510, S512, S514, S516 and S518 may correspond to steps specified in TS 23.502, clause 4.12.2.2 (Registration procedure for untrusted non-3GPP access), with the difference being that in the present invention the NAS messages (e.g. NAS PDUs) between the UE 104 and the N3IWF 105 are exchanged over the first QUIC connection, not over an IPsec security association.

[0083] At step S520, the N3IWF 105 receives the N3IWF key from the AMF 143. At step S520 the AMF 143 may transmit an Initial Context Setup Request message comprising the N3IWF key. The N3IWF 105 may store the N3IWF key in memory in association with the UE Id to link the N3IWF key with the UE Id. In this example, the UE Id is used as a Pre- Shared Key (PSK) identifier (otherwise referred to herein as a “second identifier”). Alternatively, the N3IWF 105 may derive the Pre-Shared Key (PSK) identifier from the UE Id and store the N3IWF key in memory in association with the PSK identifier to link the N3IWF key with the PSK identifier.

[0084] After reception of the N3IWF key the N3IWF 105 closes the first QUIC connection. That is, at step S522 the N3IWF 105 transmits a connection termination message (e.g. a CONNECTION CLOSE frame) to the UE 104 via the first QUIC connection. This message indicates that the connection is being closed and provides a reason for the closure (this may be in the form of an error code or cause value) indicating that a new QUIC connection should be requested by the UE to resume the ongoing registration procedure. In this case, a reason may be provided indicating to the UE that it should immediately attempt to establish a new QUIC connection using the derived N3IWF key as a pre-shared key for authentication. After the N3IWF 105 transmits the connection termination message via the first QUIC connection, the N3IWF 105 terminates the first QUIC connection such that the N3IWF 105 no longer uses the first QUIC connection for communication.

[0085] In response to receiving the connection termination message, at step S524 the UE 104 terminates the first QUIC connection such that the UE 104 no longer uses the first QUIC connection for communication. The UE 104 also establishes a second QUIC connection with the N3IWF 105 via the untrusted non-3GPP access network 103 using the N3IWF key. At step S524, theUE 104 transmits a request for establishment of the second QUIC connection, via the untrusted non-3GPP access network 103, to the N3IWF 105; the request comprising a PSK identifier to indicate that the N3IWF key is to be used to authenticate the UE when establishing the second QUIC connection. The PSK identifier is based on the UE Id in that the PSK identifier may be the same as the UE Id, or may be derived from the UE Id by way of a derivation function. In embodiments whereby the PSK identifier is derived from the UE Id, the UE 104 and N3IWF 105 apply the same function and derive the same PSK identity from the UE Id.

[0086] During the TLS negotiation phase, the UE 104 may send a TLS ClientHello message comprising a PSK Extension element, which indicates its intention to use a Pre- Shared Key (PSK) for authentication. In this scenario, the PSK key is the N3IWF key that was derived previously from the anchor key. The PSK Extension element comprises the PSK identifier, which is used by the N3IWF 105 to reference the correct pre-shared key (i.e., the correct N3IWF key) for the authentication used in establishment of the second QUIC connection.

[0087] In response to receiving the request for establishment of the second QUIC connection, the N3IWF 105 obtains the PSK identifier and queries memory to obtain the N3IWF key stored in association with the PSK identifier. The N3IWF 105 is configured to authenticate the UE 104 using the N3IWF key during the establishment of the second QUIC connection at step S524. This new second QUIC connection is established to carry all subsequent NAS messages. The second QUIC connection is established only when the UE and the mobile network (e.g. CN 106) are mutually authenticated using the pre-shared key.

[0088] After the successful establishment of the second QUIC connection, at step S526 the N3IWF 105 responds to AMF with an Initial Context Setup Response, indicating that a context has been created that enables secure communication with the UE 104.

[0089] At step S528, the AMF 143 completes the registration procedure by sending an N2 message to the N3IWF 105 comprising a NAS Registration Accept message.

[0090] At step S530, the N3IWF 105 transmits a registration accept message, via the second QUIC connection, to the UE 104. In particular, the N3IWF 105 may forward the NAS Registration Accept message to the UE 104 within a QUIC Stream frame transmitted over the second QUIC connection.

[0091] The second QUIC connection is then used to carry all subsequent NAS messages exchanged between the UE 104 and AMF 143 via the N3IWF 105. The second QUIC connection can be referred to as the “signalling QUIC connection”, or “QUIC connection for NAS signalling” signifying the fact that is used to transport NAS signalling messages.

[0092] It can be seen that the process 500 include the use of QUIC for the transport protocol and the establishment of two distinct QUIC connections throughout the process.

[0093] By using the above process 500 that based on the QUIC protocol, the protocol architecture over NWu can be simplified as shown in Figure 6. In Figure 6. The NWu’ interface represents the interface between the untrusted non -3 GPP access network 103 and the CN 106 that employs the QUIC protocol.

[0094] Figure 7 illustrates an example of a UE 700 in accordance with aspects of the present disclosure. The UE 700 may include a processor 702, a memory 704, a controller 706, and a transceiver 708. The processor 702, the memory 704, the controller 706, or the transceiver 708, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces.

[0095] The processor 702, the memory 704, the controller 706, or the transceiver 708, or various combinations or components thereof may be implemented in hardware (e.g., circuitry). The hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), or other programmable logic device, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.

[0096] The processor 702 may include an intelligent hardware device (e.g., a general- purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof). In some implementations, the processor 702 may be configured to operate the memory 704. In some other implementations, the memory 704 may be integrated into the processor 702. The processor 702 may be configured to execute computer-readable instructions stored in the memory 704 to cause the UE 700 to perform various functions of the present disclosure.

[0097] The memory 704 may include volatile or non-volatile memory. The memory 704 may store computer-readable, computer-executable code including instructions when executed by the processor 702 cause the UE 700 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such the memory 704 or another type of memory. Computer-readable media includes both non- transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or specialpurpose computer.

[0098] In some implementations, the processor 702 and the memory 704 coupled with the processor 702 may be configured to cause the UE 700 to perform one or more of the functions described herein (e.g., executing, by the processor 702, instructions stored in the memory 704). For example, the processor 702 may support wireless communication at the UE 700 in accordance with examples as disclosed herein. The UE 700 may be configured to support a means for performing a discovery of a non -3 GPP interworking function that supports a connectivity with a mobile communication network using a QUIC protocol; in response to the discovery of the non-3GPP interworking function, establishing a first QUIC connection with the non-3GPP interworking function via a non-3GPP access network; initiating a registration procedure with the mobile communication network via the first QUIC connection; terminating the first QUIC connection and establishing a second QUIC connection with the non-3GPP interworking function via the non-3 GPP access network using an authentication key generated during the registration procedure; and resuming the registration procedure via the second QUIC connection.

[0099] The controller 706 may manage input and output signals for the UE 700. The controller 706 may also manage peripherals not integrated into the UE 700. In some implementations, the controller 706 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some implementations, the controller 706 may be implemented as part of the processor 702.

[0100] In some implementations, the UE 700 may include at least one transceiver 708. In some other implementations, the UE 700 may have more than one transceiver 708. The transceiver 708 may represent a wireless transceiver. The transceiver 708 may include one or more receiver chains 710, one or more transmitter chains 712, or a combination thereof.

[0101] A receiver chain 710 may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain 710 may include one or more antennas for receive the signal over the air or wireless medium. The receiver chain 710 may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiver chain 710 may include at least one demodulator configured to demodulate the receive signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal. The receiver chain 710 may include at least one decoder for decoding the processing the demodulated signal to receive the transmitted data.

[0102] A transmitter chain 712 may be configured to generate and transmit signals (e.g., control information, data, packets). The transmitter chain 712 may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes like phase-shift keying (PSK) or quadrature amplitude modulation (QAM). The transmitter chain 712 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium. The transmitter chain 712 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.

[0103] Figure 8 illustrates an example of a processor 800 in accordance with aspects of the present disclosure. The processor 800 may be an example of a processor configured toperform various operations in accordance with examples as described herein. The processor 800 may include a controller 802 configured to perform various operations in accordance with examples as described herein. The processor 800 may optionally include at least one memory 804, which may be, for example, an L1 / L2 / L3 cache. Additionally, or alternatively, the processor 800 may optionally include one or more arithmetic-logic units (ALUs) 806. One or more of these components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).

[0104] The processor 800 may be a processor chipset and include a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) in accordance with examples as described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory local to or included in the processor chipset (e.g., the processor 800) or other memory (e.g., random access memory (RAM), read-only memory (ROM), dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM), static RAM (SRAM), ferroelectric RAM (FeRAM), magnetic RAM (MRAM), resistive RAM (RRAM), flash memory, phase change memory (PCM), and others).

[0105] The controller 802 may be configured to manage and coordinate various operations (e.g., signaling, receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) of the processor 800 to cause the processor 800 to support various operations in accordance with examples as described herein. For example, the controller 802 may operate as a control unit of the processor 800, generating control signals that manage the operation of various components of the processor 800. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating timing of operations.

[0106] The controller 802 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from the memory 804 and determine subsequent instruction(s) to be executed to cause the processor 800 to support various operations in accordance with examples as described herein. The controller 802 may be configured to track memory address ofinstructions associated with the memory 804. The controller 802 may be configured to decode instructions to determine the operation to be performed and the operands involved. For example, the controller 802 may be configured to interpret the instruction and determine control signals to be output to other components of the processor 800 to cause the processor 800 to support various operations in accordance with examples as described herein. Additionally, or alternatively, the controller 802 may be configured to manage flow of data within the processor 800. The controller 802 may be configured to control transfer of data between registers, arithmetic logic units (ALUs), and other functional units of the processor 800.

[0107] The memory 804 may include one or more caches (e.g., memory local to or included in the processor 800 or other memory, such RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementations, the memory 804 may reside within or on a processor chipset (e.g., local to the processor 800). In some other implementations, the memory 804 may reside external to the processor chipset (e.g., remote to the processor 800).

[0108] The memory 804 may store computer-readable, computer-executable code including instructions that, when executed by the processor 800, cause the processor 800 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. The controller 802 and / or the processor 800 may be configured to execute computer-readable instructions stored in the memory 804 to cause the processor 800 to perform various functions. For example, the processor 800 and / or the controller 802 may be coupled with or to the memory 804, the processor 800, the controller 802, and the memory 804 may be configured to perform various functions described herein. In some examples, the processor 800 may include multiple processors and the memory 804 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions herein.

[0109] The one or more ALUs 806 may be configured to support various operations in accordance with examples as described herein. In some implementations, the one or more ALUs 806 may reside within or on a processor chipset (e.g., the processor 800). In someother implementations, the one or more ALUs 806 may reside external to the processor chipset (e.g., the processor 800). One or more ALUs 806 may perform one or more computations such as addition, subtraction, multiplication, and division on data. For example, one or more ALUs 806 may receive input operands and an operation code, which determines an operation to be executed. One or more ALUs 806 be configured with a variety of logical and arithmetic circuits, including adders, subtractors, shifters, and logic gates, to process and manipulate the data according to the operation. Additionally, or alternatively, the one or more ALUs 806 may support logical operations such as AND, OR, exclusive-OR (XOR), not-OR (NOR), and not-AND (NAND), enabling the one or more ALUs 806 to handle conditional operations, comparisons, and bitwise operations.

[0110] The processor 800 may support wireless communication in accordance with examples as disclosed herein. The processor 800 may be configured to or operable to support a means for performing a discovery of a non-3GPP interworking function that supports a connectivity with a mobile communication network using a QUIC protocol; in response to the discovery of the non-3GPP interworking function, establishing a first QUIC connection with the non-3GPP interworking function via a non-3GPP access network, initiating a registration procedure with the mobile communication network via the first QUIC connection; terminating the first QUIC connection and establishing a second QUIC connection with the non-3GPP interworking function via the non-3 GPP access network using an authentication key generated during the registration procedure; and resuming the registration procedure via the second QUIC connection.

[0111] Figure 9 illustrates an example of a NE 900 in accordance with aspects of the present disclosure. The NE 900 may correspond to the N3IWF 105 described herein. The NE 900 may include a processor 902, a memory 904, a controller 906, and a transceiver 908. The processor 902, the memory 904, the controller 906, or the transceiver 908, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces.

[0112] The processor 902, the memory 904, the controller 906, or the transceiver 908, or various combinations or components thereof may be implemented in hardware (e.g., circuitry). The hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), or other programmable logic device, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.

[0113] The processor 902 may include an intelligent hardware device (e.g., a general- purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof). In some implementations, the processor 902 may be configured to operate the memory 904. In some other implementations, the memory 904 may be integrated into the processor 902. The processor 902 may be configured to execute computer-readable instructions stored in the memory 904 to cause the NE 900 to perform various functions of the present disclosure.

[0114] The memory 904 may include volatile or non-volatile memory. The memory 904 may store computer-readable, computer-executable code including instructions when executed by the processor 902 cause the NE 900 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such the memory 904 or another type of memory. Computer-readable media includes both non- transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or specialpurpose computer.

[0115] In some implementations, the processor 902 and the memory 904 coupled with the processor 902 may be configured to cause the NE 900 to perform one or more of the functions described herein (e.g., executing, by the processor 902, instructions stored in the memory 904). For example, the processor 902 may support wireless communication at the NE 900 in accordance with examples as disclosed herein. The NE 900 may be configured to support a means for establishing, via a non -3 GPP access network, a first QUIC connection to a UE; facilitating a registration procedure between the UE and a mobile communication network via the first QUIC connection; terminating the first QUIC connection; establishing, via the non-3GPP access network, a second QUIC connection to the UE using anauthentication key generated during the registration procedure; and resuming the registration procedure via the second QUIC connection.

[0116] The controller 906 may manage input and output signals for the NE 900. The controller 906 may also manage peripherals not integrated into the NE 900. In some implementations, the controller 906 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some implementations, the controller 906 may be implemented as part of the processor 902.

[0117] In some implementations, the NE 900 may include at least one transceiver 908. In some other implementations, the NE 900 may have more than one transceiver 908. The transceiver 908 may represent a wireless transceiver. The transceiver 908 may include one or more receiver chains 910, one or more transmitter chains 912, or a combination thereof.

[0118] A receiver chain 910 may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain 910 may include one or more antennas for receive the signal over the air or wireless medium. The receiver chain 910 may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiver chain 910 may include at least one demodulator configured to demodulate the receive signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal. The receiver chain 910 may include at least one decoder for decoding the processing the demodulated signal to receive the transmitted data.

[0119] A transmitter chain 912 may be configured to generate and transmit signals (e.g., control information, data, packets). The transmitter chain 912 may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes like phase-shift keying (PSK) or quadrature amplitude modulation (QAM). The transmitter chain 912 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium. The transmitter chain 912 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.

[0120] Figure 10 illustrates a flowchart of a method in accordance with aspects of the present disclosure. The operations of the method may be implemented by a UE as described herein. In some implementations, the UE may execute a set of instructions to control the function elements of the UE to perform the described functions.

[0121] At 1002, the method may include performing a discovery of a non-3GPP interworking function that supports connectivity with a mobile communication network using a QUIC protocol. The operations of 1002 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1002 may be performed by a UE as described with reference to Figure 7.

[0122] At 1004, the method may include in response to the discovery of the non-3GPP interworking function, establishing a first QUIC connection with the non -3 GPP interworking function via a non -3 GPP access network. The operations of 1004 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1004 may be performed by a UE as described with reference to Figure 7.

[0123] At 1006, the method may include initiating a registration procedure with the mobile communication network via the first QUIC connection. The operations of 1006 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1006 may be performed by a UE as described with reference to Figure 7.

[0124] At 1008, the method may include terminating the first QUIC connection and establishing a second QUIC connection with the non-3GPP interworking function via the non-3GPP access network using an authentication key generated during the registration procedure. The operations of 1008 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1008 may be performed by a UE as described with reference to Figure 7.

[0125] At 1010, the method may include resuming the registration procedure via the second QUIC connection. The operations of 1008 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1010 may be performed by a UE as described with reference to Figure 7.

[0126] It should be noted that the method described herein describes a possible implementation, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible.

[0127] Figure 11 illustrates a flowchart of a method in accordance with aspects of the present disclosure. The operations of the method may be implemented by a NE as described herein. In some implementations, the NE may execute a set of instructions to control the function elements of the NE to perform the described functions.

[0128] At 1102, the method may include establishing a first QUIC connection, via a non- 3 GPP access network, to a UE. The operations of 1102 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1102 may be performed by a NE as described with reference to Figure 9.

[0129] At 1104, the method may include facilitating a registration procedure between the UE and a mobile communication network via the first QUIC connection. The operations of 1104 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1104 may be performed by a NE as described with reference to Figure 9.

[0130] At 1106, the method may include terminating the first QUIC connection. The operations of 1106 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1106 may be performed by a NE as described with reference to Figure 9.

[0131] At 1108, the method may include establishing a second QUIC connection via the non-3GPP access network, to the UE, using an authentication key generated during the registration procedure. The operations of 1108 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1108 may be performed by a NE as described with reference to Figure 9.

[0132] At 1110, the method may include resuming the registration procedure via the second QUIC connection. The operations of 1110 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1110 may be performed by a NE as described with reference to Figure 9.

[0133] It should be noted that the method described herein describes a possible implementation, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible. For example, whilst embodiments have been described herein with reference to the non-3GPP access network 103 being an untrusted non-3GPP access network 103, embodiments may extend to the non-3GPP access network 103 being a trusted non-3GPP access network or a wireline non-3GPP access network.

[0134] The description herein is provided to enable a person having ordinary skill in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to a person having ordinary skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.

Claims

CLAIMS1. A user equipment (UE), comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the UE to: perform a discovery of a non -3 GPP interworking function that supports a connectivity with a mobile communication network using a QUIC protocol; in response to the discovery of the non-3GPP interworking function, establish a first QUIC connection with the non -3 GPP interworking function via a non-3GPP access network; initiate a registration procedure with the mobile communication network via the first QUIC connection; terminate the first QUIC connection; establish a second QUIC connection with the non-3GPP interworking function via the non-3GPP access network using an authentication key generated during the registration procedure; and resume the registration procedure via the second QUIC connection.

2. The UE of claim 1, wherein the discovery of the non-3GPP interworking function that supports the connectivity with the mobile communication network using the QUIC protocol is based on a network identifier associated with the non-3GPP interworking function.

3. The UE of claim 2, wherein the at least one processor is configured to cause the UE to: transmit a domain name system (DNS) query request message comprising one or more fully qualified domain name (FQDN) parameters, wherein at least one FQDN parameter indicates a requirement that the non-3GPP interworking function supports the connectivity with the mobile communication network using the QUIC protocol; andreceive a DNS query response message comprising the identifier associated with the non-3GPP interworking function.

4. The UE of claim 2, wherein the at least one processor is configured to cause the UE to: transmit a DNS service record query; receive a DNS service record based on the DNS service record query, the DNS service record comprising a host name and a port number; and obtain the network identifier using the host name and port number.

5. The UE of any of claims 2 to 4, wherein the at least one processor is configured to cause the UE to establish the first QUIC connection with the non-3GPP interworking function via the non-3GPP access network based on the identifier associated with the non-3GPP interworking function.

6. The UE of claim 1, wherein to initiate the registration procedure the at least one processor is configured to cause the UE to: transmit, to the non-3GPP interworking function via the first QUIC connection, a first QUIC message comprising a registration request and a first identifier of the UE.

7. The UE of claim 6, wherein to establish the second QUIC connection with the non- 3GPP interworking function the at least one processor is configured to cause the UE to: transmit a request for establishment of the second QUIC connection, via the non- 3 GPP access network, to the non-3GPP interworking function; the request comprising a second identifier, that is based on the first identifier of the UE, to indicate that the authentication key is to be used to authenticate the UE.

8. The UE of claim 7, wherein the second identifier of the UE is the same as the first identifier of the UE.

9. The UE of claim 7, wherein the at least one processor is configured to cause the UE to: derive the second identifier from the first identifier.

10. The UE of any preceding claim, wherein the at least one processor is configured to cause the UE to: perform an authentication procedure with at least one network entity via the first QUIC connection to derive the authentication key.

11. The UE of any preceding claim, wherein the at least one processor is configured to cause the UE to: receive an indication that the first QUIC connection is terminated and to establish the second QUIC connection with the non-3GPP interworking function via the non-3GPP access network using the authentication key.

12. The UE of any preceding claim, wherein to resume the registration procedure the at least one processor is configured to cause the UE to: receive a registration accept message via the second QUIC connection.

13. The UE of any preceding claim, wherein the at least one processor is configured to cause the UE to: transmit one or more non-access stratum (NAS) messages via the second QUIC connection, or receive the one or more NAS messages via the second QUIC connection, or a combination thereof.

14. A processor comprising: at least one controller coupled with at least one memory and configured to cause the processor to: perform a discovery of an non-3GPP interworking function that supports a connectivity with a mobile communication network using a QUIC protocol;in response to the discovery of the non-3GPP interworking function, establish a first QUIC connection with the non -3 GPP interworking function via a non-3GPP access network, initiate a registration procedure with the mobile communication network via the first QUIC connection; terminate the first QUIC connection; establish a second QUIC connection with the non-3GPP interworking function via the non-3GPP access network using an authentication key generated during the registration procedure; and resume the registration procedure via the second QUIC connection.

15. A method comprising: performing a discovery of a non -3 GPP interworking function that supports a connectivity with a mobile communication network using a QUIC protocol; in response to the discovery of the non-3GPP interworking function, establishing a first QUIC connection with the non-3GPP interworking function via a non-3GPP access network, initiating a registration procedure with the mobile communication network via the first QUIC connection; terminating the first QUIC connection; establishing a second QUIC connection with the non-3GPP interworking function via the non-3GPP access network using an authentication key generated during the registration procedure; and resuming the registration procedure via the second QUIC connection.

16. A network entity comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the network entity to: establish, via a non-3GPP access network, a first QUIC connection to a UE;facilitate a registration procedure between the UE and a mobile communication network via the first QUIC connection; terminate the first QUIC connection; establish, via the non-3GPP access network, a second QUIC connection to the UE using an authentication key generated during the registration procedure; and resume the registration procedure via the second QUIC connection.

17. The network entity of claim 16, wherein the at least one processor is configured to cause the network entity to: receive via the first QUIC connection, a first QUIC message from the UE, the first QUIC message comprising a registration request and a first identifier of the UE.

18. The network entity of claim 17, wherein the at least one processor is configured to cause the network entity to: receive, from the UE, a request for establishment of the second QUIC connection, via the non-3GPP access network, wherein the request comprises a second identifier of the UE, wherein the second identifier is based on the first identifier of the UE, wherein the second identifier indicates the authentication key for authenticating the UE; and establish the second QUIC connection based on a successful authentication of the UE using the authentication key.

19. The network entity according to claim 18, wherein the second identifier of the UE is the same as the first identifier of the UE, and wherein the at least one processor is configured to cause the network entity to: store the authentication key in the at least one memory in association with the first identifier of the UE; and retrieve the authentication key from the at least one memory based on the first identifier of the UE.

20. The network entity of claim 18, wherein the second identifier of the UE is derived from the first identifier of the UE, and the at least one processor is configured to cause the network entity to: derive the second identifier of the UE from the first identifier of the UE; store the authentication key in the at least one memory in association with the second identifier of the UE; and retrieve the authentication key from the at least one memory using the second identifier of the UE.

Citation Information

Patent Citations

  • Next gen zero trust network access (ZTNA) and virtual private network (VPN) including cloud secure access service edge (SASE)

    US20230079444A1

  • Establishing untrusted non-3GPP sessions without compromising security

    WO2021076407A1

Cited By

  • QUIC protocol link establishment process and 5G NAS flow fusion design

    CN120786732A