User equipment registration
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-01-26
- Publication Date
- 2026-08-11
Smart Images
Figure CN122556149A_ABST
Abstract
Description
Technical Field
[0001] This disclosure relates to wireless communications, and more specifically, to registering user equipment (UE) with a network via an access network (e.g., an untrusted non-3GPP access network). Background Technology
[0002] A wireless communication system may include one or more network communication devices, such as base stations, that support wireless communication for one or more user communication devices, which may also be referred to as user equipment (UE) or other suitable terms. The wireless communication system may support wireless communication with one or more user communication devices by utilizing the resources of the wireless communication system (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers, etc.)). Furthermore, the wireless communication system may support wireless communication across various radio access technologies, including third-generation (3G), fourth-generation (4G), fifth-generation (5G), and other suitable radio access technologies beyond 5G (e.g., sixth-generation (6G)). Summary of the Invention
[0003] The article “a” preceding an element is unrestricted and should be understood to refer to “at least one” or “one or more” of those elements. The terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. As used herein, the word “or,” as used in a list of items (e.g., a list of items beginning with phrases such as “at least one,” “one or more,” or “one or two”) indicates an inclusive list, such that a list of at least one of, for example, 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). Furthermore, as used herein, the phrase “based on” should not be construed as referring to a closed set of conditions. For example, without departing from the scope of this disclosure, an example step described as “based on condition A” may be based on both condition A and condition B. In other words, as used herein, the phrase “based on” should be interpreted in the same manner as the phrase “at least partially based on.” Furthermore, as used herein, the term “set” may comprise one or more elements.
[0004] Some embodiments of the methods and apparatus described herein may include a UE comprising: at least one memory; and at least one processor coupled to the at least one memory and configured such that the UE: performs the discovery of a non-3GPP interoperability function supporting a connection to a mobile communication network using the QUIC protocol; in response to the discovery of the non-3GPP interoperability function, establishes a first QUIC connection with the non-3GPP interoperability function via a non-3GPP access network; initiates a registration process to the mobile communication network via the first QUIC connection; terminates the first QUIC connection and establishes a second QUIC connection with the non-3GPP interoperability function via the non-3GPP access network using an authentication key generated during the registration process; and resumes the registration process via the second QUIC connection.
[0005] The discovery of the non-3GPP interoperability function supporting the connection to the mobile communication network using the QUIC protocol can be based on the network identifier associated with the non-3GPP interoperability function.
[0006] The at least one processor may be configured to cause the UE to: transmit a Domain Name System (DNS) query request message including one or more fully qualified domain name (FQDN) parameters, wherein at least one FQDN parameter indicates that the non-3GPP interoperability function supports the requirement of the connection with the mobile communication network using the QUIC protocol; and receive a DNS query response message including an identifier associated with the non-3GPP interoperability 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 including a hostname and a port number; and obtain the network identifier using the hostname and port number.
[0008] The at least one processor may be configured to enable the UE to establish the first QUIC connection with the non-3GPP interoperability function via the non-3GPP access network based on the identifier associated with the non-3GPP interoperability function.
[0009] In order to initiate the registration process, the at least one processor may be configured to cause the UE to: transmit a first QUIC message including the UE's registration request and a first identifier to the non-3GPP interoperability function via the first QUIC connection.
[0010] In order 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 to the non-3GPP interworking function via the non-3GPP access network for establishing the second QUIC connection; the request includes a second identifier based on the first identifier of the UE to indicate that the authentication key will 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 allow 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 process 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 to terminate the first QUIC connection, and establish a second QUIC connection with the non-3GPP interoperability function via the non-3GPP access network using the authentication key.
[0015] In order to resume the registration process, the at least one processor may be configured to cause the UE to receive a registration acceptance 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 embodiments of the methods and apparatus described herein may further include a processor comprising: at least one controller coupled to at least one memory and configured to: perform the discovery of a non-3GPP interoperability function supporting a connection to a mobile communication network using the QUIC protocol; in response to the discovery of the non-3GPP interoperability function, establish a first QUIC connection with the non-3GPP interoperability function via a non-3GPP access network; initiate a registration process to the mobile communication network via the first QUIC connection; terminate the first QUIC connection and establish a second QUIC connection with the non-3GPP interoperability function via the non-3GPP access network using an authentication key generated during the registration process; and resume the registration process via the second QUIC connection.
[0018] Some embodiments of the methods and apparatus described herein may further include a method comprising: performing the discovery of a non-3GPP interworking function supporting a connection to a mobile communication network using the 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 process to 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-3GPP access network using an authentication key generated during the registration process; and resuming the registration process via the second QUIC connection.
[0019] Some embodiments of the methods and apparatus described herein may further include a network entity comprising: at least one memory; and at least one processor coupled to the at least one memory and configured such that the network entity: establishes a first QUIC connection to a UE via a non-3GPP access network; facilitates a registration process between the UE and a mobile communication network via the first QUIC connection; terminates the first QUIC connection; establishes a second QUIC connection to the UE via the non-3GPP access network using an authentication key generated during the registration process; and resumes the registration process via the second QUIC connection.
[0020] The at least one processor may be configured to cause the network entity to receive a first QUIC message from the UE via the first QUIC connection, the first QUIC message including the UE’s registration request and a first identifier.
[0021] The at least one processor may be configured to cause the network entity to: receive a request from the UE via the non-3GPP access network for establishing the second QUIC connection, wherein the request includes 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 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 association with the first identifier of the UE in the at least one memory; 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 can be derived from the first identifier of the UE, and the at least one processor can 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 association with the second identifier of the UE in the at least one memory; and retrieve the authentication key from the at least one memory using the second identifier of the UE. Attached Figure Description
[0024] Figure 1 Illustrate an example of a network architecture.
[0025] Figure 2a This describes an example of the control plane stack before establishing an IPsec security association between the UE and a non-3GPP interoperable device.
[0026] Figure 2b This describes an example of the control plane stack after establishing an IPsec security association between the UE and a non-3GPP interoperability function.
[0027] Figure 3 Examples of wireless communication systems according to aspects of this disclosure are described.
[0028] Figure 4 This describes the network architecture based on aspects of this disclosure.
[0029] Figure 5 This document describes an example of a process for registering user equipment with a network via an untrusted non-3GPP access network, in accordance with aspects of this disclosure.
[0030] Figure 6 This describes the control plane stack according to aspects of this disclosure.
[0031] Figure 7 An example of UE 700 is described according to aspects of this disclosure.
[0032] Figure 8 An example of a processor 800 according to aspects of this disclosure is described.
[0033] Figure 9 An example of NE 900 based on aspects of this disclosure is described.
[0034] Figure 10 A flowchart illustrating a method performed by a UE according to aspects of this disclosure.
[0035] Figure 11 A flowchart illustrating the method performed by NE according to aspects of this disclosure. Detailed Implementation
[0036] Figure 1An example of network architecture 100 is described, which may include one or more of an untrusted 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, an IEEE 802.11 (Wi-Fi), a wireless local area network (WLAN), etc. The UE 104 may connect to (e.g., establish a connection with) the 5G CN 106 to access one or more services or applications of the UE 104.
[0037] exist Figure 1 In this example, UE 104 can connect to 5G CN 106 via N3IWF 105 (e.g., establish a connection with it). For example, N3IWF 105 can exchange signaling (e.g., transmit, receive) with UE 104 via the NWu interface. Alternatively, N3IWF 106 can exchange signaling (e.g., transmit, receive) with 5G CN 106 via a network interface (e.g., N2, N3). Alternatively, UE 104 can connect to 5G CN 106 via a trusted non-3GPP access network (not shown) (e.g., establish a connection with it). For example, UE 104 can connect to 5G CN 106 via an interworking function, which is a trusted non-3GPP gateway function (TNGF) (not shown).
[0038] Figure 2a This example illustrates the control plane stack before establishing an IPsec security association between the UE and a non-3GPP interoperability function.
[0039] Figure 2b This describes an example of the control plane after establishing an IPsec security association between the UE and a non-3GPP interoperability function.
[0040] like Figure 2a and 2b As described, the protocol stack on the NWu interface is complex and outdated. It involves multiple layers, including IPsec, IKEv2 for establishing IPsec Security Associations (SAs), and the EAP-5G protocol for delivering NAS messages before establishing the signaling IPsec AS. It uses IPsec in tunnel mode, which incurs significant overhead because the UE is assigned an "internal IP" address, and all data created by the UE is encapsulated in internal IP packets, which are then encapsulated in external IP packets. This stack was designed for an era where latency and transmission efficiency requirements for non-3GPP access were less stringent.
[0041] The IKEv2 protocol is used between the UE and N3IWF to establish an IPsec secure association, which supports the secure exchange of NAS signaling messages. The reliance on IKEv2 and the subsequent establishment of the IPsec SA increase complexity and overhead due to the multiple exchanges required to set up the secure connection. This increases latency, consumes more processing power, and may potentially introduce more points of failure. Furthermore, as UE devices and network functions evolve with more advanced capabilities, continued use of IKEv2 / IPsec may prevent these capabilities from reaching their full potential.
[0042] In contrast, the QUIC protocol—a modern transport layer network protocol designed by the Internet Engineering Task Force (IETF)—offers an attractive alternative. QUIC integrates security and transport functions into a single protocol layer, effectively simplifying the stack. It also provides 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] Furthermore, QUIC operates on User Datagram Protocol (UDP), which is simpler and more efficient than Transmission Control Protocol (TCP), especially in handling packet loss—a common problem in wireless networks. This efficiency, along with QUIC's built-in encryption and simplified handshake mechanism, makes it a robust choice for the NWu interface, ensuring end-to-end security that meets the requirements of modern 5G networks.
[0044] Embodiments of this disclosure relate to updating the NWu interface to use the QUIC protocol. This modernizes the 5G network architecture, improves efficiency, and provides a more seamless and secure user experience, thereby leveraging the full potential of 5G connectivity. Adopting QUIC on the NWu interface offers several advantages, including:
[0045] • Reduced latency: By minimizing the number of handshakes required to establish a secure connection, QUIC can significantly reduce the time required for a UE to connect to the 5G core network.
[0046] • Simplified Protocol Stack: The combination method of QUIC for transport and security protocols simplifies the protocol stack, making it easier to implement and maintain. Modern UEs already support the QUIC protocol for web browsing using HTTP / 3, and reusing the QUIC protocol on NWu presents an attractive option.
[0047] • Reduced complexity: QUIC provides strong security guarantees using built-in encryption, similar to those achieved with IKEv2 / Ipsec, but without the associated complexity.
[0048] • Enhanced performance: QUIC’s improved congestion control and avoidance of head-of-line blocking on UDP result in better overall performance, especially in environments with packet loss and variable network conditions.
[0049] • Future Proof: As a protocol under active development, QUIC is better suited to adapt to future changes and requirements in the 5G ecosystem.
[0050] The aspects of this disclosure are described in the context of wireless communication systems.
[0051] Figure 3 This describes an example of a wireless communication system 300 according to aspects of this disclosure. The wireless communication system 300 may include one or more NEs 102, one or more UEs 104, and CNs 106. The wireless communication system 300 may support various radio access technologies. In some embodiments, the wireless communication system 300 may be a 4G network, such as an LTE network or an LTE-A network. In some other embodiments, the wireless communication system 300 may be an NR network, such as a 5G network, a 5G-A network, or a 5G Ultra Wideband (5G-UWB) network. In other embodiments, the wireless communication system 300 may be a combination of 4G and 5G networks, or other suitable radio access technologies, including IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20. The wireless communication system 300 may support radio access technologies beyond 5G, such as 6G. In addition, the wireless communication system 300 can support technologies such as Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), or Code Division Multiple Access (CDMA).
[0052] One or more NEs 102 may be distributed across a geographical area to form a wireless communication system 300. One or more of the NEs 102 described herein may be, include, or be referred to as a network node, base station, network element, network function, network entity, radio access network (RAN), NodeB, eNodeB (eNB), next-generation NodeB (gNB), or other suitable terms. NEs 102 and UEs 104 may communicate via a communication link, which may be a wireless or wired connection. For example, NEs 102 and UEs 104 may perform wireless communication (e.g., receive signaling, transmit signaling) via a Uu interface.
[0053] NE 102 can provide a geographic coverage area that supports services for one or more UEs 104 within that geographic coverage area. For example, NE 102 and UE 104 can support wireless communication of signals associated with services (e.g., voice, video, packet data, messaging, broadcasting, etc.) based on one or more radio access technologies. In some embodiments, NE 102 can be mobile, for example, a satellite associated with a non-terrestrial network (NTN). In some embodiments, different geographic coverage areas 112 associated with the same or different radio access technologies can overlap, but different geographic coverage areas can be associated with different NEs 102.
[0054] One or more UEs 104 may be distributed across a geographical area of the wireless communication system 300. UE 104 may include or be referred to as a remote unit, mobile device, wireless device, remote device, subscriber device, transmitter device, receiver device, or some other suitable term. In some implementations, UE 104 may be referred to as a unit, station, terminal, or client, and other instances thereof. Additionally or alternatively, UE 104 may be referred to as an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a Machine Type Communication (MTC) device, and other instances thereof.
[0055] UE 104 may be able to support direct wireless communication with other UE 104 via a communication link. For example, UE 104 may support direct wireless communication with another UE 104 via 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, communication link 114 may be referred to as a side link. For example, UE 104 may support direct wireless communication with another UE 104 via a PC5 interface.
[0056] NE 102 may support communication with CN 106 or with another NE 102 or both. For example, NE 102 may interface with other NE 102 or CN 106 via one or more backhaul links (e.g., S1, N2, N2, or network interfaces). In some embodiments, NE 102 may communicate directly with each other. In some other embodiments, NE 102 may communicate with each other or indirectly (e.g., via CN 106). In some embodiments, one or more NE 102 may include sub-components, such as access network entities, which may be instances of access node controllers (ANCs). The ANC may communicate with one or more UE 104s via one or more other access network transmitting entities (which may be referred to as radio headends, smart radio headends, or transmit-receive points (TRPs)).
[0057] CN 106 can support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. CN 106 can be an evolved packet core (EPC) or a 5G core (5GC), which may include control plane entities (e.g., Mobility Management Entity (MME), Access and Mobility Management Function (AMF)) that manage access and mobility, and user plane entities (e.g., Serving Gateway (S-GW), Packet Data Network (PDN) Gateway (P-GW), or User Plane Function (UPF)) that route packets or interconnect to external networks. In some implementations, the control plane entities may manage non-access stratum (NAS) functions of one or more UEs 104 served by one or more NEs 102 associated with CN 106, such as mobility, authentication, and bearer management (e.g., data bearers, signaling bearers, etc.).
[0058] CN 106 can communicate with the packet data network via one or more backhaul links (e.g., via S1, N2, N2, or another network interface). The packet data network may contain an application server. In some implementations, one or more UEs 104 can communicate with the application server. UE 104 can establish a session (e.g., a Protocol Data Unit (PDU) session, etc.) with CN 106 via NE 102. CN 106 can use the established session (e.g., an established PDU session) to route services (e.g., control information, data, etc.) between UE 104 and the application server. A PDU session may be an instance of a logical connection between UE 104 and CN 106 (e.g., one or more network functions of CN 106).
[0059] In the wireless communication system 300, NE 102 and UE 104 can use the resources of the wireless communication system 300 (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communication). In some embodiments, NE 102 and UE 104 may support different resource structures. For example, NE 102 and UE 104 may support different frame structures. In some embodiments, such as in 4G, NE 102 and UE 104 may support a single frame structure. In some other embodiments, such as in 5G and other suitable radio access technologies, NE 102 and UE 104 may support various frame structures (i.e., multiple frame structures). NE 102 and UE 104 may support various frame structures based on one or more parameter sets.
[0060] The wireless communication system 300 may support one or more parameter sets, and the parameter sets may include subcarrier spacing and cyclic prefixes. A first parameter set (e.g., μ=0) may be associated with a first subcarrier spacing (e.g., 15 kHz) and a regular cyclic prefix. In some embodiments, the first parameter set (e.g., μ=0) associated with the first subcarrier spacing (e.g., 15 kHz) may utilize one time slot per subframe. A second parameter set (e.g., μ=1) may be associated with a second subcarrier spacing (e.g., 30 kHz) and a regular cyclic prefix. A third parameter set (e.g., μ=2) may be associated with a third subcarrier spacing (e.g., 60 kHz) and a regular cyclic prefix or an extended cyclic prefix. A fourth parameter set (e.g., μ=3) may be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a regular cyclic prefix. A fifth parameter set (e.g., μ=4) may be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a regular cyclic prefix.
[0061] Time intervals for resources (e.g., communication resources) can be organized according to frames (also called radio frames). Each frame may have a duration, for example, 10 milliseconds (ms). In some embodiments, each frame may contain multiple subframes. For example, each frame may contain 10 subframes, and each subframe may have a duration, for example, 1 ms. In some embodiments, each frame may have the same duration. In some embodiments, each subframe of a frame may have the same duration.
[0062] Alternatively, the time intervals of resources (e.g., communication resources) can be organized according to time slots. For example, a subframe may contain a certain number (e.g., quantity) of time slots. The number of time slots in each subframe may also depend on one or more parameter sets supported in the wireless communication system 300. For example, the first, second, third, fourth, and fifth parameter sets (i.e., μ=0, μ=1, μ=2, μ=3, μ=4) associated with corresponding subcarrier intervals of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz may utilize one time slot per subframe, two time slots per subframe, four time slots per subframe, eight time slots per subframe, and 16 time slots per subframe, respectively. Each time slot may contain a certain number (e.g., quantity) of symbols (e.g., OFDM symbols). In some embodiments, the number (e.g., quantity) of time slots in a subframe may depend on the parameter set. For a conventional cyclic prefix, a time slot may contain 14 symbols. For an extended cyclic prefix (e.g., applicable to a 60 kHz subcarrier spacing), a time slot may contain 12 symbols. The relationship between the number of symbols per time slot for the regular cyclic prefix and the extended cyclic prefix, the number of time slots per subframe, and the number of time slots per frame may depend on the parameter set. It should be understood that references to the first parameter set (e.g., μ=0) associated with the first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframes and time slots.
[0063] In the wireless communication system 300, the electromagnetic (EM) spectrum can be divided into various categories, frequency bands, channels, etc., based on frequency or wavelength. For example, the wireless communication system 300 may support one or more operating frequency bands, such as frequency range names FR1 (410 MHz to 7.125 GHz), FR2 (24.25 GHz to 52.6 GHz), FR3 (7.125 GHz to 24.25 GHz), FR4 (52.6 GHz to 114.25 GHz), FR4a or FR4-1 (52.6 GHz to 71 GHz), and FR5 (114.25 GHz to 300 GHz). In some embodiments, NE 102 and UE 104 may perform wireless communication on one or more of the operating frequency bands. In some embodiments, FR1 may be used by NE 102 and UE 104, as well as other equipment or devices, for cellular communication services (e.g., control information, data). In some implementations, FR2 can be used by NE 102 and UE 104, as well as other equipment or devices, for short-range, high data rate capabilities.
[0064] FR1 may be associated with one or more parameter sets (e.g., at least three parameter sets). For example, FR1 may be associated with a first parameter set containing a 15 kHz subcarrier spacing (e.g., μ=0); a second parameter set containing a 30 kHz subcarrier spacing (e.g., μ=1); and a third parameter set containing a 60 kHz subcarrier spacing (e.g., μ=2). FR2 may be associated with one or more parameter sets (e.g., at least two parameter sets). For example, FR2 may be associated with a third parameter set (e.g., μ=2) containing a 60 kHz subcarrier spacing; and a fourth parameter set (e.g., μ=3) containing a 120 kHz subcarrier spacing.
[0065] In the wireless communication system 300, UE 104 can connect to 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, etc.) (e.g., establish a connection thereto). UE 104 can connect to CN 106 (e.g., establish a connection thereto) to access one or more services or applications of UE 104. (See references herein.) Figure 1 As described, UE 104 can connect to CN 106 via N3IWF (e.g., establish a connection therewith). For example, N3IWF can exchange signaling (e.g., transmit, receive) with UE 104 via the NWu interface. Alternatively, N3IWF can exchange signaling (e.g., transmit, receive) with CN 106 via a network interface (e.g., N2, N3). Alternatively, UE 104 can connect to CN 106 via a trusted non-3GPP access network (e.g., establish a connection therewith). For example, UE 104 can connect to CN 106 via TNGF (e.g., establish a connection therewith). Figure 4 This describes an example network architecture 400 based on aspects of this disclosure. In some implementations, network architecture 400 may be implemented as referenced herein. Figure 1 and 3 The aspects of the network architecture 100 or wireless communication system 300 described herein may be implemented by or related to the network architecture 100 or wireless communication system 300. For example, network architecture 400 may include UE 104, which may be as referenced herein. Figure 1 and 3 An example of UE 104 is described. Network architecture 400 may include cellular base station unit 102a and access point 102b, which may be as referenced herein. Figure 1 and 3 The described NE 102 instance. Network architecture 400 may include N3IWF105, which may be as referenced herein. Figure 1An example of the N3IWF described. Network architecture 400 may include CN 106 (e.g., a mobile core network), which may be as referenced herein. Figure 1 and 3 An instance of the CN described.
[0066] UE 104 can establish a connection (e.g., session) with CN 106 (e.g., 5G CN) via at least one or more access networks (e.g., 3GPP access network 120 (also known as a trusted 3GPP access network) or non-3GPP access network 103 (e.g., an untrusted non-3GPP access network, a trusted non-3GPP access network, or a wired non-3GPP access network)). 3GPP access network 120 may be associated with a first radio access technology (e.g., 4G, 5G), while non-3GPP access network 103 may be associated with a second radio access technology (e.g., Wi-Fi, WLAN). For example, 3GPP access network 120 may support cellular communication with UE 104 via cellular base station unit 102a, while non-3GPP access network may support non-cellular communication with UE 104 via access point 102b (e.g., Wi-Fi communication, WLAN communication). The non-3GPP access network 103 can communicate with CN 106 via an interoperability function (e.g., N3IWF105) and through one or more network interfaces (e.g., N2, N3).
[0067] CN 106 may include one or more network functions, which may include one or more of the following: User Plane Function (UPF) 141, Access and Mobility Management Function (AMF) 143, Session Management Function (SMF) 145, Policy Control Function Network Entity (PCF) 147, Authentication Server Function (AUSF) 148, or Unified Data Management Network Entity (UDM) 149.
[0068] This disclosure relates to registering UE 104 with CN 106 (e.g., a mobile core network) via a non-3GPP access network 103 using the QUIC protocol. As an example, an embodiment is described below with reference to a non-3GPP access network 103 that is not a trusted non-3GPP access network 103.
[0069] Figure 5 This describes the process of registering UE 104 with CN 106 via an untrusted non-3GPP access network 103 using the QUIC protocol.
[0070] At step S502, UE 104 connects to the untrusted non-3GPP access network 103 and obtains an IP connection, that is, it receives IP configuration data containing an IP address. In other words, UE 104 is assigned an IP address.
[0071] At step S504, UE 104 discovers N3IWF 105, which supports connection with CN 106 using the QUIC protocol. Step S502 can be performed in several different ways.
[0072] Currently, when a UE wants to discover the network identifier (e.g., IP address) of an N3IWF in a PLMN, the UE performs a DNS query using either of the following: a) an FQDN based on the operator identifier, in the form: "n3iwf.5gc.mnc <mnc>.mcc <mcc>.pub.3gppnetwork.org; or b) an FQDN based on the tracking region identifier, in the form of: "tac-lb <tac-low-byte>.tac-hb <tac-high-byte>.tac.n3iwf.5gc.mnc <mnc>.mcc <mcc>The website is .pub.3gppnetwork.org. When a UE wants to discover any N3IWF within a specific PLMN, it uses an FQDN based on the operator identifier. When a UE wants to discover an N3IWF within a specific PLMN located in a specific tracking area within this PLMN, it uses an FQDN based on the tracking area identifier. It is assumed that the N3IWF discovered using this method supports the IKEv2 protocol.
[0073] To enable the UE to discover an N3IWF that supports a connection to CN 106 using the QUIC protocol, at step S504, the UE 104 may transmit a Domain Name System (DNS) query request message including one or more Fully Qualified Domain Name (FQDN) parameters, wherein at least one FQDN parameter indicates the requirement that non-3GPP interoperability support a connection to CN 106 using the QUIC protocol. For example, a QUIC-specific service tag (e.g., "quic-n3iwf") may be included in the FQDN to indicate that the N3IWF must support QUIC. This will make a DNS query for a QUIC-enabled N3IWF look like "quic-n3iwf.5gc.mnc012.mcc345.pub.3gppnetwork.org" (QUIC's carrier-based FQDN) or "tac-lb21.tac-hb0b.tac.quic-n3iwf.5gc.mnc012.mcc345.pub.3gppnetwork.org" (QUIC's tracking area identifier-based FQDN). UE 104 can send a DNS query request message to the DNS server. UE 104 can receive a DNS query response message, which includes the network identifier (e.g., IP address) of the N3IWF that supports the QUIC protocol connection to CN 106.
[0074] To enable the UE to discover N3IWFs supporting connections to CN 106 using the QUIC protocol, in step S504, the UE 104 may alternatively initiate 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 the specified protocol. DNS SRV records allow service identification by hostname and port number, and can also be prioritized and weighted for load balancing. As an example only, the SRV record for a QUIC-enabled N3IWF might look like this:
[0075] _quic._udp.n3iwf.5gc.mnc012.mcc345.pub.3gppnetwork.org; or
[0076] _quic._udp.tac-lb21.tac-hb0b.tac.n3iwf.5gc.mnc012.mcc345.pub.3gppnetwork.org
[0077] In this case, _quic indicates the QUIC protocol, and _udp specifies the underlying transport layer protocol.
[0078] UE 104 can send a DNS service record query to the DNS server. UE 104 can receive a DNS SRV record including the hostname and port number. Then, UE 104 can resolve the hostname to an IP address that supports non-3GPP interoperability with CN 106 using the QUIC protocol. UE 104 can send a DNS query to the DNS server including the hostname. Then, UE 104 can receive a DNS query response message including the N3IWF network identifier (e.g., IP address) that supports connection to CN 106 using the QUIC protocol.
[0079] After the UE discovers the network identifier (e.g., IP address) of the N3IWF 105, in step S506, the UE 104 establishes a first QUIC connection with the N3IWF. Compared to known methods that use IKEv2 as the transport protocol, QUIC combines features of both TCP and TLS, thereby potentially reducing connection and transport latency.
[0080] The first QUIC connection is a temporary QUIC connection used to support the registration process until the N3IWF key (also referred to herein as the authentication key) is exported. During the connection establishment phase, N3IWF 105 can provide a certificate to UE 104 and establish security between UE 104 and N3IWF 105. At this phase, UE 104 has not yet been certified by CN 106. In the context of registration with 5G CN 106, the Application Layer Protocol Negotiation (ALPN) element exchanged during the connection establishment phase includes a special value (e.g., "5g-nas") indicating that the 5G-NAS protocol will operate on the QUIC connection and that 5G-NAS Protocol Data Units (PDUs) will be exchanged. UE 104 is not certified during the establishment of the first QUIC connection.
[0081] At step S508, UE 104 initiates the registration process with CN 106 via the first QUIC connection. Specifically, at step S508, UE 104 transmits a first QUIC message to N3IWF 105. UE 104 uses the first QUIC connection to transmit the first QUIC message to N3IWF 105. The first QUIC message includes a request to register the UE, wherein the first QUIC message contains the UE's identifier (UE Id), also referred to herein as the UE's "first identifier". The first QUIC message may be a QUIC STREAM frame containing access network parameters (AN-Params) and a NAS-PDU containing a registration request message.
[0082] AN-Params may contain information as specified in TS 23.502, and therefore include information used by N3IWF 105 to select AMF 143 in 5G CN 106. This information includes, for example, GUAMI, the selected PLMN ID (or PLMN ID and NID), the requested NSSAI, and the establishment reason. The establishment reason provides the reason for requesting NAS connection to 5G CN 106.
[0083] UE 104 may include the UE Id in the AN-Params. This may be a 5G identifier (e.g., 5G-GUTI) assigned to UE 104 from a previous registration to the same PLMN. In another instance, the UE Id may be a value generated by the UE, such as a random value. In yet another instance, the UE Id may be a unique identifier for UE 104, such as IMEI, SUPI (Subscription Permanent Identifier), SUCI (Subscription Hidden Identifier), etc. This UE Id is used later in procedure 500, as described below.
[0084] In step S508, a first QUIC message is sent to N3IWF 105 to trigger the registration process for untrusted non-3GPP access via the first QUIC connection. N3IWF 105 is configured to facilitate the registration process between UE 104 and CN 106 by acting as an intermediary for message exchange between UE 104 and AMF 143.
[0085] In step S510, N3IWF 105 selects AMF 143, and in step S512, it forwards the received registration request message to the selected AMF 143.
[0086] As part of the registration process, at step S514, the AMF may request the UE device identifier (e.g., IMEI) of the UE 104, and thus the AMF 143 may send an identifier request to the UE 104 and receive an identification response from the UE 104.
[0087] At step S516, a mutual authentication process is performed between the AUSF in UE 104 and CN 106. The mutual authentication process may be based on the EAP-AKA protocol.
[0088] If authentication is successful, the same anchor key (e.g., SEAF key) is generated in UE 104 and AUSF 148. Figure 5 During the authentication process illustrated, UE 104 generates an anchor key (e.g., a SEAF key) in response to receiving an authentication request transmitted from AMF 143 via N3IWF 105. The UE uses the anchor key to derive the N3IWF key. On the network side, AUSF 148 generates an anchor key (e.g., a SEAF key) in response to receiving a challenge from AMF 143. AUSF 148 transmits a response to the challenge, which includes the anchor key. AMF 143 uses the anchor key to derive the N3IWF key. The N3IWF key in the UE and the N3IWF key in the N3IWF should be the same; therefore, the N3IWF key can be referred to as a public or pre-shared key.
[0089] At step S518, NAS security mode command / complete messages can be exchanged to establish a NAS security context between UE 104 and AMF 143 via N3IWF 105.
[0090] Steps S510, S512, S514, S516, and S518 may correspond to the steps specified in Clause 4.12.2.2 of TS 23.502 (Registration Procedure for Untrusted Non-3GPP Access), except that in this invention, NAS messages (e.g., NAS PDUs) between UE 104 and N3IWF 105 are exchanged via the first QUIC connection rather than via IPsec secure association.
[0091] At step S520, N3IWF 105 receives the N3IWF key from AMF 143. At step S520, AMF 143 may transmit an Initial Context Establishment Request message including the N3IWF key. N3IWF 105 may store the N3IWF key in memory in association with the UE Id to link the N3IWF key to the UE Id. In this example, the UE Id is used as a pre-shared key (PSK) identifier (also referred to herein as a "second identifier"). Alternatively, 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 to the PSK identifier.
[0092] After receiving the N3IWF key, N3IWF 105 closes the first QUIC connection. That is, at step S522, N3IWF 105 transmits a connection termination message (e.g., a CONNECTION_CLOSE frame) to UE 104 via the first QUIC connection. This message indicates that the connection is being closed and provides a reason for the closure (which may be in the form of an error code or reason value), thus indicating that a new QUIC connection should be requested by the UE to resume the ongoing registration process. In this case, a reason can be provided to the UE instructing it to immediately attempt to establish a new QUIC connection using the derived N3IWF key as a pre-shared key for authentication. After N3IWF 105 transmits the connection termination message via the first QUIC connection, N3IWF 105 terminates the first QUIC connection, causing N3IWF 106 to no longer use the first QUIC connection for communication.
[0093] In response to receiving a connection termination message, at step S524, UE 104 terminates the first QUIC connection, causing UE 104 to no longer use the first QUIC connection for communication. UE 104 also establishes a second QUIC connection with N3IWF 105 via an untrusted non-3GPP access network 103 using the N3IWF key. At step S524, UE 104 sends a request to N3IWF 105 via the untrusted non-3GPP access network 103 to establish the second QUIC connection; the request includes a PSK identifier to indicate that the N3IWF key will be used for UE authentication when establishing the second QUIC connection. The PSK identifier is based on the UE Id because the PSK identifier can be the same as the UE Id, or can be derived from the UE Id by means of a derivation function. In embodiments where the PSK identifier is derived from the UE Id, UE 104 and N3IWF 105 apply the same function and derive the same PSK identifier from the UE Id.
[0094] During the TLS negotiation phase, UE 104 may send a TLS ClientHello message including a PSK extension element, indicating the UE's intention to authenticate using a pre-shared key (PSK). In this scenario, the PSK key is an N3IWF key previously derived from the anchor key. The PSK extension element includes a PSK identifier, which is used by N3IWF 105 to reference the correct pre-shared key (i.e., the correct N3IWF key) for authentication used when establishing a second QUIC connection.
[0095] In response to receiving a request to establish a second QUIC connection, N3IWF 105 obtains a PSK identifier and queries memory to obtain an N3IWF key stored in association with the PSK identifier. N3IWF 105 is configured to use the N3IWF key to authenticate UE 104 during the establishment of the second QUIC connection in step S524. This new second QUIC connection is established to carry all subsequent NAS messages. The second QUIC connection is established only if the UE and the mobile network (e.g., CN 106) authenticate each other using a pre-shared key.
[0096] After successfully establishing the second QUIC connection, at step S526, N3IWF 105 responds to AMF with an initial context establishment response, thereby indicating that a context for secure communication with UE 104 has been created.
[0097] At step S528, AMF 143 completes the registration process by sending an N2 message, which includes a NAS registration acceptance message, to N3IWF 105.
[0098] At step S530, N3IWF 105 transmits a registration accept message to UE 104 via the second QUIC connection. Specifically, N3IWF 105 may forward the NAS registration accept message to UE 104 within a QUIC stream frame transmitted via the second QUIC connection.
[0099] The second QUIC connection is then used to carry all subsequent NAS messages exchanged between UE 104 and AMF 143 via N3IWF 105. The second QUIC connection may be referred to as a "signaling QUIC connection" or a "NAS signaling QUIC connection" to indicate the fact that it is used to deliver NAS signaling messages.
[0100] As can be seen, process 500 involves using QUIC for the transmission protocol and establishing two different QUIC connections throughout the process.
[0101] By using the above process 500 based on the QUIC protocol, the protocol architecture on NWu can be simplified, such as... Figure 6 As shown in [the document]. Figure 6 In this context, the NWu' interface represents the interface between the untrusted non-3GPP access network 103 and CN 106, which uses the QUIC protocol.
[0102] Figure 7 An example of a UE 700 according to aspects of this disclosure is described. UE 700 may include a processor 702, a memory 704, a controller 706, and a transceiver 708. The processor 702, memory 704, controller 706, or transceiver 708, or various combinations thereof, or various components thereof, may be examples of components for performing the various aspects of this disclosure as described herein. These components may be coupled via one or more interfaces (e.g., operatively ground, communicatively ground, functional ground, electronic ground, electrical ground).
[0103] Processor 702, memory 704, controller 706, or transceiver 708, or various combinations or components thereof, may be implemented in hardware (e.g., a circuit system). The hardware may be a processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), or other programmable logic device, or any combination thereof configured or otherwise supporting components for performing the functions described in this disclosure.
[0104] Processor 702 may include intelligent hardware devices (e.g., a general-purpose processor, DSP, CPU, ASIC, FPGA, or any combination thereof). In some embodiments, processor 702 may be configured to operate memory 704. In some other embodiments, memory 704 may be integrated into processor 702. Processor 702 may be configured to execute computer-readable instructions stored in memory 704 to cause UE 700 to perform various functions of this disclosure.
[0105] Memory 704 may comprise volatile or non-volatile memory. Memory 704 may store computer-readable, computer-executable code containing instructions that, when executed by processor 702, cause UE 700 to perform the various functions described herein. The code may be stored in a non-transitory computer-readable medium, such as memory 704 or another type of memory. Computer-readable medium includes both non-transitory computer storage media and communication media, wherein the communication media includes any media that facilitates the transfer of a computer program from one place to another. Non-transitory storage media may be any available media accessible by a general-purpose or special-purpose computer.
[0106] In some implementations, processor 702 and memory 704 coupled to processor 702 may be configured to cause UE 700 to perform one or more of the functions described herein (e.g., processor 702 executing instructions stored in memory 704). For example, processor 702 may support wireless communication at UE 700 according to an example disclosed herein. UE 700 may be configured to support a component for: performing the discovery of a non-3GPP interoperability function supporting a connection to a mobile communication network using the QUIC protocol; establishing a first QUIC connection with the non-3GPP interoperability function via a non-3GPP access network in response to the discovery of the non-3GPP interoperability function; initiating a registration process to the mobile communication network via the first QUIC connection; terminating the first QUIC connection and establishing a second QUIC connection with the non-3GPP interoperability function via the non-3GPP access network using an authentication key generated during the registration process; and resuming the registration process via the second QUIC connection.
[0107] Controller 706 manages the input and output signals of UE 700. Controller 706 can also manage peripheral devices not integrated into UE 700. In some embodiments, controller 706 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some embodiments, controller 706 may be implemented as part of processor 702.
[0108] In some embodiments, UE 700 may include at least one transceiver 708. In other embodiments, UE 700 may have more than one transceiver 708. Transceiver 708 may represent a wireless transceiver. Transceiver 708 may include one or more receiver chains 710, one or more transmitter chains 712, or a combination thereof.
[0109] Receiver chain 710 may be configured to receive signals (e.g., control information, data, packets) via wireless media. For example, receiver chain 710 may include one or more antennas for receiving signals over the air or wireless media. Receiver chain 710 may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. Receiver chain 710 may include at least one demodulator configured to demodulate the received signal and obtain transmitted data by reversing the modulation technique applied during signal transmission. Receiver chain 710 may include at least one decoder for decoding the demodulated signal to receive transmitted data.
[0110] Transmitter chain 712 can be configured to generate and transmit signals (e.g., control information, data, packets). 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). 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 a wireless medium. Transmitter chain 712 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.
[0111] Figure 8 An example of a processor 800 according to aspects of this disclosure is described. Processor 800 may be an example of a processor configured to perform various operations according to the examples described herein. Processor 800 may include a controller 802 configured to perform various operations according to the examples described herein. Processor 800 may optionally include at least one memory 804, which may be, for example, an L1 / L2 / L3 cache. Additionally or alternatively, processor 800 may optionally include one or more arithmetic logic units (ALUs) 806. One or more of these components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).
[0112] Processor 800 may be a processor chipset and includes a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receive, acquire, retrieve, transmit, output, forward, store, determine, identify, access, write, read) according to the examples described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory native to the processor chipset (e.g., processor 800) or contained within the processor chipset) 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).
[0113] Controller 802 can be configured to manage and coordinate various operations of processor 800 (e.g., signaling, receiving, acquiring, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, and reading) to enable processor 800 to support various operations according to the examples described herein. For example, controller 802 can operate as a control unit of processor 800, generating control signals that manage the operation of various components of processor 800. These control signals include enabling or disabling functional units, selecting data paths, initiating memory accesses, and coordinating operation timing.
[0114] Controller 802 may be configured to fetch (e.g., fetch, retrieve, receive) instructions from memory 804 and determine subsequent instructions to be executed to enable processor 800 to support various operations according to the examples described herein. Controller 802 may be configured to track the memory addresses of instructions associated with memory 804. Controller 802 may be configured to decode instructions to determine the operations to be performed and the operands involved. For example, controller 802 may be configured to interpret instructions and determine control signals to be output to other components of processor 800 to enable processor 800 to support various operations according to the examples described herein. Alternatively or additionally, controller 802 may be configured to manage data flow within processor 800. Controller 802 may be configured to control data transfers between registers, arithmetic logic unit (ALU), and other functional units of processor 800.
[0115] Memory 804 may include one or more caches (e.g., memory local to processor 800 or included in processor 800) or other memories, such as RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some embodiments, memory 804 may reside within or on the processor chipset (e.g., local to processor 800). In some other embodiments, memory 804 may reside outside the processor chipset (e.g., remote from processor 800).
[0116] Memory 804 may store computer-readable, computer-executable code containing instructions that, when executed by processor 800, cause processor 800 to perform the 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. Controller 802 and / or processor 800 may be configured to execute computer-readable instructions stored in memory 804 to cause processor 800 to perform various functions. For example, processor 800 and / or controller 802 may be coupled to or coupled to memory 804, and processor 800, controller 802, and memory 804 may be configured to perform the various functions described herein. In some instances, processor 800 may include multiple processors, and memory 804 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be individually or collectively configured to perform the various functions described herein.
[0117] One or more ALU 806s may be configured to support various operations according to the examples described herein. In some embodiments, one or more ALU 806s may reside within or on a processor chipset (e.g., processor 800). In some other embodiments, one or more ALU 806s may reside outside the processor chipset (e.g., processor 800). One or more ALU 806s may perform one or more calculations on data, such as addition, subtraction, multiplication, and division. For example, one or more ALU 806s may receive input operands and an opcode that determines the operation to be performed. One or more ALU 806s may be configured with various logic and arithmetic circuitry, including adders, subtractors, shifters, and logic gates, to process and manipulate data according to the operation. Alternatively, one or more ALU 806s may support logical operations such as AND, OR, XOR, NOR, and NAND, enabling one or more ALU 806s to handle conditional operations, comparisons, and bitwise operations.
[0118] Processor 800 may support wireless communication according to examples disclosed herein. Processor 800 may be configured or operable to support a component for: performing the discovery of a non-3GPP interoperability function supporting a connection to a mobile communication network using the QUIC protocol; establishing a first QUIC connection with the non-3GPP interoperability function via a non-3GPP access network in response to the discovery of the non-3GPP interoperability function; requesting a registration process 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 interoperability function via the non-3GPP access network using an authentication key generated during the registration process; and resuming the registration process via the second QUIC connection.
[0119] Figure 9 An example of NE 900 according to aspects of this disclosure is described. NE 900 may correspond to the N3IWF105 described herein. NE 900 may include a processor 902, a memory 904, a controller 906, and a transceiver 908. The processor 902, memory 904, controller 906, or transceiver 908, or various combinations thereof, or various components thereof, may be examples of components for performing the various aspects of this disclosure as described herein. These components may be coupled via one or more interfaces (e.g., operatively, communicatively, functionally, electronically, electrically).
[0120] Processor 902, memory 904, controller 906, or transceiver 908, or various combinations or components thereof, may be implemented in hardware (e.g., a circuit system). The hardware may be a processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), or other programmable logic device, or any combination thereof configured or otherwise supporting components for performing the functions described in this disclosure.
[0121] Processor 902 may include intelligent hardware devices (e.g., a general-purpose processor, DSP, CPU, ASIC, FPGA, or any combination thereof). In some embodiments, processor 902 may be configured to operate memory 904. In some other embodiments, memory 904 may be integrated into processor 902. Processor 902 may be configured to execute computer-readable instructions stored in memory 904 to cause NE 900 to perform various functions of this disclosure.
[0122] Memory 904 may comprise volatile or non-volatile memory. Memory 904 may store computer-readable, computer-executable code containing instructions that, when executed by processor 902, cause NE 900 to perform the various functions described herein. The code may be stored in a non-transitory computer-readable medium, such as memory 904 or another type of memory. Computer-readable medium includes both non-transitory computer storage media and communication media, wherein the communication media includes any media that facilitates the transfer of a computer program from one place to another. Non-transitory storage media may be any available media accessible by a general-purpose or special-purpose computer.
[0123] In some implementations, processor 902 and memory 904 coupled to processor 902 may be configured to cause NE 900 to perform one or more of the functions described herein (e.g., processor 902 executing instructions stored in memory 904). For example, processor 902 may support wireless communication at NE 900 according to an example disclosed herein. NE 900 may be configured to support a component for: establishing a first QUIC connection to UE via a non-3GPP access network; facilitating a registration process between UE and mobile communication network via the first QUIC connection; terminating the first QUIC connection; establishing a second QUIC connection to UE via a non-3GPP access network using an authentication key generated during the registration process; and resuming the registration process via the second QUIC connection.
[0124] Controller 906 manages the input and output signals of NE 900. Controller 906 can also manage peripheral devices not integrated into NE 900. In some embodiments, controller 906 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some embodiments, controller 906 may be implemented as part of processor 902.
[0125] In some embodiments, the NE 900 may include at least one transceiver 908. In other embodiments, 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.
[0126] Receiver chain 910 may be configured to receive signals (e.g., control information, data, packets) via wireless media. For example, receiver chain 910 may include one or more antennas for receiving signals over the air or wireless media. Receiver chain 910 may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. Receiver chain 910 may include at least one demodulator configured to demodulate the received signal and obtain transmitted data by reversing the modulation technique applied during signal transmission. Receiver chain 910 may include at least one decoder for decoding the demodulated signal to receive transmitted data.
[0127] Transmitter chain 912 can be configured to generate and transmit signals (e.g., control information, data, packets). 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). 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 a wireless medium. Transmitter chain 912 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.
[0128] Figure 10 A flowchart illustrating a method according to an aspect of this disclosure is provided. The operation of the method can be implemented by a UE as described herein. In some embodiments, the UE can execute a set of instructions to control the functional elements of the UE to perform the described functions.
[0129] At point 1002, the method may include performing the discovery of non-3GPP interoperability functions supporting connections to mobile communication networks using the QUIC protocol. The operation of 1002 may be performed according to the examples described herein. In some implementations, aspects of the operation of 1002 may be as described in references... Figure 7 The UE execution described.
[0130] At 1004, the method may include establishing a first QUIC connection with the non-3GPP interoperability function via a non-3GPP access network in response to the discovery of the non-3GPP interoperability function. The operation of 1004 may be performed according to the examples described herein. In some implementations, aspects of the operation of 1004 may be as described in the references... Figure 7 The UE execution described.
[0131] At 1006, the method may include initiating a registration process with the mobile communication network via a first QUIC connection. The operation of 1006 may be performed according to the examples described herein. In some embodiments, aspects of the operation of 1006 may be as described in references... Figure 7 The UE execution described.
[0132] At 1008, the method may include terminating the first QUIC connection and establishing a second QUIC connection via a non-3GPP access network and a non-3GPP interoperability function using the authentication key generated during the registration process. The operation of 1008 may be performed according to the examples described herein. In some implementations, aspects of the operation of 1008 may be as described in the references... Figure 7 The UE execution described.
[0133] At 1010, the method may include resuming the registration process via a second QUIC connection. The operation of 1008 may be performed according to the examples described herein. In some implementations, aspects of the operation of 1010 may be as described in the references... Figure 7 The UE execution described.
[0134] It should be noted that the method described herein describes one possible implementation, and the operation and steps may be rearranged or otherwise modified, and other implementations are possible.
[0135] Figure 11 A flowchart illustrating a method according to an aspect of this disclosure is provided. The operation of the method may be implemented by an NE as described herein. In some embodiments, the NE may execute a set of instructions to control the functional elements of the NE to perform the described functions.
[0136] At 1102, the method may include establishing a first QUIC connection to the UE via a non-3GPP access network. The operation of 1102 may be performed according to the examples described herein. In some implementations, aspects of the operation of 1102 may be as described in references... Figure 9 The described NE execution.
[0137] At 1104, the method may include facilitating a registration process between the UE and the mobile communication network via a first QUIC connection. The operation of 1104 may be performed according to the examples described herein. In some embodiments, aspects of the operation of 1104 may be as described in references... Figure 9 The described NE execution.
[0138] At 1106, the method may include terminating the first QUIC connection. The operation of 1106 may be performed according to the examples described herein. In some implementations, aspects of the operation of 1106 may be as described in references... Figure 9 The described NE execution.
[0139] At 1108, the method may include establishing a second QUIC connection to the UE via a non-3GPP access network using an authentication key generated during the registration process. Operation of 1108 may be performed according to the examples described herein. In some implementations, aspects of operation of 1108 may be as described in references... Figure 9 The described NE execution.
[0140] At 1110, the method may include resuming the registration process via a second QUIC connection. The operation of 1110 may be performed according to the examples described herein. In some embodiments, aspects of the operation of 1110 may be as described in references... Figure 9 The described NE execution.
[0141] It should be noted that the method described herein describes one possible implementation, and the operations and steps may be rearranged or otherwise modified, and other implementations are possible. For example, although this document has described an embodiment with reference to a non-3GPP access network 103 as an untrusted non-3GPP access network 103, the embodiment can be extended to a non-3GPP access network 103 as a trusted non-3GPP access network or a wired non-3GPP access network.
[0142] The description herein is provided to enable those skilled in the art to make or use this disclosure. Various modifications to this disclosure will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of this disclosure. Therefore, this disclosure is not limited to the examples and designs described herein, but should be given the widest scope consistent with the principles and novel features disclosed herein.< / mcc> < / mnc> < / mcc> < / mnc>
Claims
1. A user equipment (UE) comprising: At least one memory; and At least one processor, coupled to and configured to enable the UE to: Discover non-3GPP interoperability functions that support connections to mobile communication networks using the QUIC protocol; In response to the discovery of the non-3GPP interworking function, a first QUIC connection is established with the non-3GPP interworking function via a non-3GPP access network; The registration process with the mobile communication network is initiated via the first QUIC connection; Terminate the first QUIC connection; A second QUIC connection is established via the non-3GPP access network and the non-3GPP interoperability function using the authentication key generated during the registration process; and The registration process is resumed via the second QUIC connection.
2. The UE of claim 1, wherein the discovery of the non-3GPP interoperability function supporting the connection to the mobile communication network using the QUIC protocol is based on a network identifier associated with the non-3GPP interoperability 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 including one or more Fully Qualified Domain Name (FQDN) parameters, wherein at least one FQDN parameter indicates that the non-3GPP interoperability function supports the requirement for connection to the mobile communication network using the QUIC protocol; and Receive a DNS query response message that includes the identifier associated with the non-3GPP interoperability function.
4. The UE of claim 2, wherein the at least one processor is configured to cause the UE to: Launch DNS service record lookup; Based on the DNS service record query, receive the DNS service record, which includes the hostname and port number; and The network identifier is obtained using the hostname and port number.
5. The UE according to any one of claims 2 to 4, wherein the at least one processor is configured to enable the UE to establish the first QUIC connection with the non-3GPP interoperability function via the non-3GPP access network based on the identifier associated with the non-3GPP interoperability function.
6. The UE of claim 1, wherein, in order to initiate the registration process, the at least one processor is configured to cause the UE to: A first QUIC message, including a UE registration request and a first identifier, is transmitted to the non-3GPP interoperability function via the first QUIC connection.
7. The UE of claim 6, wherein, in order to establish the second QUIC connection with the non-3GPP interoperability function, the at least one processor is configured to cause the UE to: A request for establishing the second QUIC connection is transmitted to the non-3GPP interworking function via the non-3GPP access network; the request includes a second identifier based on the first identifier of the UE, indicating that the authentication key will be used to authenticate the UE.
8. The UE according to 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: The second identifier is derived from the first identifier.
10. The UE according to any of the preceding claims, wherein the at least one processor is configured to cause the UE to: An authentication process with at least one network entity is performed via the first QUIC connection to derive the authentication key.
11. The UE according to any of the preceding claims, wherein the at least one processor is configured to cause the UE to: The system receives an instruction to terminate the first QUIC connection and uses the authentication key to establish the second QUIC connection with the non-3GPP interoperability function via the non-3GPP access network.
12. The UE according to any of the preceding claims, wherein, in order to resume the registration process, the at least one processor is configured to cause the UE to: The registration acceptance message is received via the second QUIC connection.
13. The UE according to any of the preceding claims, 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 one or more NAS messages via the second QUIC connection, or a combination thereof.
14. A processor comprising: At least one controller, coupled to at least one memory and configured to enable the processor to: Discover non-3GPP interoperability functions that support connections to mobile communication networks using the QUIC protocol; In response to the discovery of the non-3GPP interworking function, a first QUIC connection is established with the non-3GPP interworking function via a non-3GPP access network; The registration process with the mobile communication network is initiated via the first QUIC connection; Terminate the first QUIC connection; A second QUIC connection is established via the non-3GPP access network and the non-3GPP interoperability function using the authentication key generated during the registration process; and The registration process is resumed via the second QUIC connection.
15. A method comprising: Discover non-3GPP interoperability functions that support connections to mobile communication networks using the QUIC protocol; In response to the discovery of the non-3GPP interworking function, a first QUIC connection is established with the non-3GPP interworking function via a non-3GPP access network; The registration process with the mobile communication network is initiated via the first QUIC connection; Terminate the first QUIC connection; A second QUIC connection is established via the non-3GPP access network and the non-3GPP interoperability function using the authentication key generated during the registration process; and The registration process is resumed via the second QUIC connection.
16. A network entity comprising: At least one memory; and At least one processor, coupled to the at least one memory and configured to enable the network entity to: The first QUIC connection to the UE is established via a non-3GPP access network; The registration process between the UE and the mobile communication network is facilitated via the first QUIC connection; Terminate the first QUIC connection; A second QUIC connection to the UE is established via the non-3GPP access network using the authentication key generated during the registration process; and The registration process is resumed 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: A first QUIC message is received from the UE via the first QUIC connection. The first QUIC message includes the UE's registration request and a first identifier.
18. The network entity of claim 17, wherein the at least one processor is configured to cause the network entity to: Receives a request from the UE via the non-3GPP access network for establishing the second QUIC connection, wherein the request includes a second identifier of the UE, wherein the second identifier is based on the first identifier of the UE, and wherein the second identifier indicates the authentication key used to authenticate the UE; and The second QUIC connection is established based on the successful authentication of the UE using the authentication key.
19. The network entity of 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: The authentication key is stored in the at least one memory in association with the first identifier of the UE; and The authentication key is retrieved 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: The second identifier of the UE is derived from the first identifier of the UE; The authentication key is stored in the at least one memory in association with the second identifier of the UE; and The authentication key is retrieved from the at least one memory using the second identifier of the UE.