Registering a user equipment with a core network via non-3GPP access network in a wireless communication system

The mechanism of using distinct protocols for request/response messages over non-3GPP access networks addresses the challenge of seamless UE connectivity in 6G systems, enhancing service utilization and deployment efficiency.

WO2026233591A1PCT designated stage Publication Date: 2026-11-12LENOVO INT COÖPERATIEF U A
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/EP2026/055405
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2026-01-27
Filing Date
2026-02-27
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

Existing wireless communication systems face challenges in enabling seamless connectivity between User Equipment (UE) and a core network via non-3GPP access networks, particularly in minimizing signaling overhead and facilitating easy deployment of 6G services while supporting both Internet services and 6GS services simultaneously.

Method used

A mechanism is introduced where a first request and response message for UE registration with a core network are transmitted via a non-3GPP access network using a first protocol, while the secure connection employs a second protocol, thereby reducing the need for synchronization of Non-Access Stratum (NAS) protocol state machines.

Benefits of technology

This approach minimizes signaling overhead and simplifies the registration process, allowing UEs to utilize both Internet services and 6GS services efficiently with reduced complexity and easy deployment.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure EP2026055405_12112026_PF_FP_ABST
    Figure EP2026055405_12112026_PF_FP_ABST
Patent Text Reader

Abstract

Various aspects of the present disclosure relate to a first network entity for wireless communication. The first network entity may be configured to, capable of, or operable to receive, via a non-3GPP access network, a first request message for registering a UE with a core network over a secure connection; and transmit, via the non-3GPP access network, a first response message indicating successful registration of the UE with the core network, wherein the first request message and the first response message comprise a first protocol, and wherein the secure connection comprises a second protocol different from the first protocol.
Need to check novelty before this filing date? Find Prior Art

Description

REGISTERING A USER EQUIPMENT WITH A CORE NETWORK VIA NON-3GPP ACCESS NETWORK IN A WIRELESS COMMUNICATION SYSTEMTECHNICAL FIELD

[0001] The present disclosure relates generally to wireless communication, including registering a User Equipment (UE) with a core network via a non-3GPP access network.BACKGROUND

[0002] A wireless communications system may include one or multiple network communication devices, which may be otherwise knowns as network equipment (NE) supporting wireless communications for one or multiple user communication devices, which may be otherwise known as a 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] As used herein, including the claims, 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 andDocket No. SMM920250239-GR-NPC). 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 B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed 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] The methods, apparatuses, processors, and systems of the present disclosure each have several innovative aspects, no single one of which is solely responsible for the desirable features disclosed herein.

[0005] A first network entity for wireless communication is described. The first network entity may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the first network entity may include at least one memory, and at least one processor coupled with the at least one memory and configured to cause the first network entity to: receive, via a non-3GPP access network, a first request message for registering a UE with a core network over a secure connection; and transmit, via the non-3GPP access network, a first response message indicating successful registration of the UE with the core network, wherein the first request message and the first response message comprise a first protocol, and wherein the secure connection comprises a second protocol different from the first protocol.

[0006] A method performed or performable by the first network entity is described herein. The method may comprise: receiving, via a non-3GPP access network, a first request message for registering a UE with a core network over a secure connection; and transmitting, via the non-3GPP access network, a first response message indicating successful registration of the UE with the core network, wherein the first request message and the first response message comprise a first protocol, and wherein the secure connection comprises a second protocol different from the first protocol.

[0007] A processor for wireless communication is described. The processor may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the processor may comprise at least one controller coupled with at least one memory and configured to cause the processor to: receive, via a non-3GPP access Docket No. SMM920250239-GR-NPnetwork, a first request message for registering a UE with a core network over a secure connection; and transmit, via the non-3GPP access network, a first response message indicating successful registration of the UE with the core network, wherein the first request message and the first response message comprise a first protocol, and wherein the secure connection comprises a second protocol different from the first protocol.

[0008] A UE for wireless communication is described. The UE may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the UE may include at least one memory, and at least one processor coupled with the at least one memory and configured to cause the UE to: transmit, via a non-3GPP access network, a first request message for registering the UE with a core network over a secure connection; and receive, via the non-3GPP access network, a first response message indicating successful registration of the UE with the core network, wherein the first request message and the first response message comprise a first protocol, and wherein the secure connection comprises a second protocol different from the first protocol.

[0009] A method performed or performable by the UE is described herein. The method may comprise: transmitting, via a non-3GPP access network, a first request message for registering the UE with a core network over a secure connection; and receiving, via the non-3GPP access network, a first response message indicating successful registration of the UE with the core network, wherein the first request message and the first response message comprise a first protocol, and wherein the secure connection comprises a second protocol different from the first protocol.

[0010] A processor for wireless communication is described. The processor may be configured to, capable of, or operable to perform one or more operations as described herein. For example, the processor may comprise at least one controller coupled with at least one memory and configured to cause the processor to: transmit, via a non-3GPP access network, a first request message for registering the UE with a core network over a secure connection; and receive, via the non-3GPP access network, a first response message indicating successful registration of the UE with the core network, wherein the first request message and the first response message comprise a first protocol, and wherein the secure connection comprises a second protocol different from the first protocol.Docket No. SMM920250239-GR-NPBRIEF DESCRIPTION OF THE DRAWINGS

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

[0012] Figure 2 illustrates an example architecture 200 for a wireless communication system comprising a 5G and 6G network with a common SBI Bus in accordance with aspects of the present disclosure.

[0013] Figure 3 illustrates an example of a non-roaming architecture for 5G Core Network with untrusted non-3GPP access in accordance with aspects of the present disclosure.

[0014] Figure 4 illustrates an example of non-roaming 6G architecture using servicebased representation for integration of the non-3GPP access in accordance with aspects of the present disclosure.

[0015] Figure 5 illustrates an example of a non-roaming 6G architecture using interface representation for integration of the non-3GPP access in accordance with aspects of the present disclosure.

[0016] Figure 6 illustrates an example of a control plane protocol stack for signalling between a UE and a 6thGeneration Core (6GC) via non-3GPP access in accordance with aspects of the present disclosure.

[0017] Figure 7 illustrates an example of a process flow for a registration and session establishment procedure via Untrusted Non-3GPP Access Node (UNAN) in accordance with aspects of the present disclosure.

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

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

[0020] Figure 10 illustrates an example of an NE 1000 in accordance with aspects of the present disclosure.Docket No. SMM920250239-GR-NP

[0021] Figure 11 illustrates a flowchart of a method 1100 performed by a UE in accordance with aspects of the present disclosure.

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

[0023] A wireless communication system may include at least one Network Function (NF) that contains a set of one or more NF services offered to NF service consumers. Such an NF may communicate with other NFs and NF services directly or indirectly. By way of example, a 5G communication system (5GS) has a 5G Core (5GC). The 5GC may include a Control Plane NF which exposes its capabilities as services via a Service-Based Interface (SB I). NF service discovery enables an NF to discover one or more NF instances which provide NF services.

[0024] It is expected that, similar to the 5GS, future communication networks such as 6G communication systems (6GS) will be based on a Service-Based Architecture (SBA), and that a service-based interface (SB I) will be used between NFs in the 6G core network.

[0025] However, there will be required a mechanism to enable the connectivity of a UE with the 6GC in order to use 6GS provided services when the UE uses non-3GPP access. A goal of such a mechanism would be to allow the UE to simultaneously use both: Internet services directly via the non-3GPP access; and 6GS offered services via the 6GC. Such a mechanism needs to be simple in order to minimize signalling load and to facilitate easy deployment.

[0026] The present disclosure describes how an NF may receive, over a secure connection and via a non-3GPP access network, a first request message for registering a UE with a core network. In reply to the UE, the NF transmits, via the non-3GPP access network, a first response message indicating successful registration of the UE with the core network. As described herein, the first request message and the first response message are sent and / or received in accordance with a first protocol, whereas the secure connection uses a second protocol different to than the first protocol.Docket No. SMM920250239-GR-NP

[0027] A benefit of such an arrangement is that connectivity between the UE and NF is enabled with minimal signalling overhead. For example, without the signalling required for synchronization of the Non Access Stratum (NAS) protocol state machines.

[0028] Aspects of the present disclosure are described in the context of a wireless communications system. Aspects of the present disclosure are further set forth in the accompanying drawings and the description below. The description set forth herein, in connection with the accompanying drawings, describes example implementations and does not represent all the implementations that may be implemented or that are within the scope of the claims. The detailed description includes specific details for the purpose of providing an understanding of the implementations described. These implementations, however, may be practiced without these specific details. Additionally, the description set forth herein, in connection with the accompanying drawings is provided to enable a person having ordinary skill in the art to make or use the present 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 present disclosure. Although aspects of a New Radio (NR) system may be described for purposes of example, and NR terminology may be used in much of the description, the techniques described herein are applicable beyond NR networks. Thus, the present disclosure is not limited to the examples and implementations described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.

[0029] Figure 1 illustrates an example of a wireless communications system 100 in accordance with aspects of the present disclosure. The wireless communications system 100 may include one or more NE 102, one or more UE 104, and a core network (CN) 106. The wireless communications system 100 may support various radio access technologies. In some implementations, the wireless communications system 100 may be a 4G network, such as a Long Term Evolution (LTE) network or an LTE- Advanced (LTE-A) network. In some other implementations, the wireless communications system 100 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 100Docket No. SMM920250239-GR-NPmay 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 (WiFi), IEEE 802.16 (WiMAX), IEEE 802.20. The wireless communications system 100 may support radio access technologies beyond 5G, for example, 6G. Additionally, the wireless communications system 100 may support technologies, such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA), etc.

[0030] The one or more NE 102 may be dispersed throughout a geographic region to form the wireless communications system 100. 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 signalling, transmit signalling) over a Uu interface.

[0031] 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 associated with the same or different radio access technologies may overlap, but the different geographic coverage areas may be associated with different NE 102.

[0032] The one or more UE 104 may be dispersed throughout a geographic region of the wireless communications system 100. 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 anDocket No. SMM920250239-GR-NPInternet-of-Things (loT) device, an Internet-of-Everything (loE) device, or machine-type communication (MTC) device, among other examples.

[0033] 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 may be referred to as a sidelink. For example, a UE 104 may support wireless communication directly with another UE 104 over a PC5 interface.

[0034] 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 access network 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).

[0035] 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 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.Docket No. SMM920250239-GR-NP

[0036] 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).

[0037] In the wireless communications system 100, the NEs 102 and the UEs 104 may use resources of the wireless communications system 100 (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 other implementations, 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.

[0038] One or more numerologies may be supported in the wireless communications system 100, and a numerology may include a subcarrier spacing and a cyclic prefix. A first numerology (e.g., / t=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., / t=0) associated with the first subcarrier spacing (e.g., 15 kHz) may utilize one slot per subframe. A second numerology (e.g., / / =1) may be associated with a second subcarrier spacing (e.g., 30 kHz) and a normal cyclic prefix. A third numerology (e.g., g=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., / t=3) may be associated with a fourth subcarrier spacingDocket No. SMM920250239-GR-NP(e.g., 120 kHz) and a normal cyclic prefix. A fifth numerology (e.g., / t=4) may be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a normal cyclic prefix.

[0039] 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.

[0040] 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 100. For instance, the first, second, third, fourth, and fifth numerologies (i.e., / t=0, / t=l, =2, jtz=3, =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 may include 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., / t=0) associated with a first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframes and slots.

[0041] In the wireless communications system 100, 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 100 may support one or multiple operating frequency bands, such as frequency range designationsDocket No. SMM920250239-GR-NPFR1 (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.

[0042] 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., / t=0), which includes 15 kHz subcarrier spacing; a second numerology (e.g., / / =1), which includes 30 kHz subcarrier spacing; and a third numerology (e.g., / / =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., / z=2), which includes 60 kHz subcarrier spacing; and a fourth numerology (e.g., / t=3), which includes 120 kHz subcarrier spacing.

[0043] A wireless communication system (e.g.,, wireless network, wireless communication network) may be composed of various technologies which all together form a generation of mobile network technology. For example, a 4G wireless communication system may comprise an Evolved Packet System (EPS) and a 5G wireless communication system may comprise a 5GS. A future 6G wireless communication system may comprise a 6GS. Each new generation of wireless communication system may support greater network flexibility compared to older generation wireless communication systems. For example, the 5GS introduces the concept of a NF that contains a set of one or more NF services offered to NF service consumers. The NF may be deployed as a software package on the network operator’s platform. Each NF can communicate with other NFs and its NF services directly or indirectly. The term “communication system” is meant as a common term for any of the EPS, 5GS, 6GS or other networks including core network and access network.

[0044] A Control Plane NF in the 5GC may expose its capabilities as services via its SBI. The NF service discovery enables a NF to discover one or more NF instances whichDocket No. SMM920250239-GR-NPprovide the expected requested NF services. The NF service discovery is implemented by requesting the Network Repository Function (NRF) and utilizing the NF discovery functionality. It may be assumed that similarly to the 5GS also a future communication networks, e.g., 6GS, may be based on an SBA. The SBA may comprise the SBI between the NFs in the core network.

[0045] Figure 2 illustrates an example architecture 200 for a wireless communication system comprising a 5G and 6G network with a common SBI Bus in accordance with aspects of the present disclosure. The architecture 200 comprises a 5G / 6G UE 210, a 5GC + 6GC 204 (indicated by a box with a dashed line), a 5G RAN 217, a 5G Cell 257, a 6G RAN 215, and a 6G Cell 255. The 5GC + 6GC 204 comprises a common SBI bus 206, a Unified Data Management (UDM) / Unified Data Repository (UDR) 235 (comprising a 5G UDM interface 234 and a 6GUDM interface 236), an NRF 230 (comprising a 5GNRF interface 229 and a 6G NRF interface 231), a first 6G NF 267, a second 6G NF 268, an Session Management Function (SMF) 252, a 6G SMF 250, an AMF 222, a 6G AMF 220, a 5G UPF 262 and a 6G UPF 260.

[0046] Architecture 200 shows a possible representation of a combined 5GS and 6GS (e.g.„ combined 5GC and 6GC 204, 5GC + 6GC 204). The common SBI bus 206 is used for 5GS and 6GS. The CN comprises the 5GC and the 6GC 204. The combined 5GC and 6GC 204 may comprise an “evolved 5GC” or “Combined 5GC and 6GC”.

[0047] The 5GC + 6GC 204 represents a common CN with a common SBI bus 206 connecting the 5GC NFs, 6GC NFs and the combined “5GC + 6GC” NFs. The NRF 230 and UDM / UDR 235 are combined “5GC + 6GC” NFs. The 5G NRF interface 229 and 5G UDM interface 234 represent the 5G service interface. The 6G NRF interface 231 and 6G UDM interface 236 represent the 6G service interface. The 6G SMF 250, 6G AMF 220, 6G UPF 260 and 6G RAN are 6G NFs which are considered to be 6G specific NFs. The 6G NFs use the 6G services exposed by the hybrid NFs. For example, the 6G AMF 220 may use the 6G SBI services offered by the UDM / UDR 235, LMF or SMF + 6G SMF. e.g., The NRF 230 and UDM / UDR 235 may be referred to as eNRF or eUDM / UDR, respectively to denote that they are enhanced entities compared to 5G NRF or UDM / UDR.Docket No. SMM920250239-GR-NP

[0048] The communication between the end device (e.g.„ 5G / 6G UE 210) and the CN for the control plane signalling is performed with a NAS protocol. One end of the NAS protocol is terminated at the 5G / 6G UE 210 and the other end of the NAS protocol is terminated at the mobility management entity in the CN. The mobility management entity may be an MME in case of EPS or the AMF 222 in case of 5GS. The 6GS may introduce a new generation of NAS protocol, e.g., a 6GS NAS. The NAS protocol used in 5GS is 5GS NAS. The NAS protocol used in EPS is EPS NAS.

[0049] The EPS NAS is used for the signalling exchange over the 3GPP access (e.g.„ LTE or E-UTRAN) between the UE and 5GC (e.g.„ MME) for registration and session management procedures. The signalling exchange over the non-3GPP access network (e.g.„ WLAN or WiFi) between the UE and EPC (e.g.„ via evolved Packet Data Gateway (ePDG)) does not use the NAS protocol. IKEv2 signalling may be used to exchange control plane signalling between the UE and the ePDG. In 5GS, the NAS protocol is used for the signalling exchange between the 5G / 6GUE 210 and 5GC (e.g.„ AMF 222) for registration and session management procedures for both 3 GPP and non-3GPP access.

[0050] Figure 3 illustrates an example of a non-roaming architecture 300 for 5G Core Network with untrusted non-3GPP access in accordance with aspects of the present disclosure. The non-roaming architecture 300 comprises non-3GPP networks (indicated by the entities below the dashed line) and Home Public Land Mobile Network (HPLMN) (indicated by the entities above the dashed line). The non-3GPP networks comprise a UE 310 and an untrusted non-3GPP access 342. The HPLMN comprises a 3GPP access 340, an AMF 322, an N3IWF 344, an SMF 352, a UPF 360 and a Data Network 308.

[0051] Non-roaming architecture 300 shows the non-roaming architecture for 5G Core Network when untrusted non-3GPP access 342 is used by the UE 310 to access the 5GS services. The N3IWF 344 terminates the signalling from the UE 310 and the N3IWF 344 interfaces to the AMF 322 via N2 interface which is unified with the same N2 interface between the 3GPP access 340 and AMF 322. The interface between the UE 310 and the N3IWF 344 is called NWu. In EPS, the ePDG is defined as part of the EPS architecture and it is widely deployed by operators, primarily to support Voice over Wi-Fi (VoWiFi).Docket No. SMM920250239-GR-NP

[0052] The interworking architecture between ePDGZEPC and 5GS is defined so that the EPC interfaces (Diameter protocol based interfaces SWm, SWd, SWx) and network entities (3GPP Authentication, Authorization, and Accounting (AAA) Server (and 3GPP AAA proxy for roaming) and HSS) are used to connect the ePDG to an EPC / 5GS interworking architecture. To support the interworking architecture between untrusted access via ePDG and interworking with 5GC with SWm / SWx interface, it is required to support 3 GPP AAA Server (and a 3 GPP AAA proxy for roaming scenarios with SWd). The Interworking (IWK) has already been improved in previous releases to reduce the need for a 3 GPP AAA Server and move to service based interfaces.

[0053] The terms “data connection”, “data connectivity”, “data session”, “PDU Session”, or PDN connection may be used interchangeably hereinafter and refer to a connection for user data established in any of the different communication systems (e.g., 4G, 5G, 6G) and using any of the access technologies. Further, the terms “PDU Session ID”, “PDUS-ID”, “session ID” or “connection ID” have the same meaning. Similarly, the terms “data traffic”, “application traffic” or “user data” may be used interchangeably hereinafter. The terminologies “network slice”, “slice”, “NS-ID” or “Single Network Slice Selection Assistance Information (S-NSSAI)” may be used interchangeably hereinafter and have similar or same meaning. In particular, the “S-NSSAI” or “NS-ID” may be considered as an identification for the network slice.

[0054] Some examples described herein relate to how to enable the connectivity of a UE 310 with the 6GC in order to use 6GS provided services when the UE 310 uses (e.g., untrusted) non-3GPP access 342. Some examples described herein tend to enable a flexible solution which allows the UE 310 to use simultaneously 1) use Internet services directly via non-3GPP access 342 and 2) use 6GS offered services. In some examples described herein, the UE registration procedure via untrusted non-3GPP access 342 tends to be simple in order to minimize signalling load and to allow easy deployment in 6GS.

[0055] The use of NAS protocol via the non-3GPP access 342 via N3IWF 344 requires synchronization of the NAS protocol state machines between the 3GPP access 340 and the non-3GPP access 342. In the EPS, the UE 310 uses the IKEv2 protocol to establish IPsec tunnel with the ePDG. The UE 310 uses the IKEv2 protocol to exchange signalling with theDocket No. SMM920250239-GR-NPePDG. The ePDG supports Diameter-based protocol to entities in the CN. The ePDG is does not support SBI-based interfaces to NFs in the CN. In 5GS, the UE 310 uses the 5GS NAS protocol to perform registration procedure and session management procedure via N3IWF 344. The UE may be required to support the NAS protocol over the non-3GPP access 342 and maintain simultaneously multiple NAS state machines in the UE 310. Some examples described herein tend to overcome this drawback.

[0056] Figure 4 illustrates an example of non-roaming 6G architecture 400 using service-based representation for integration of the non-3GPP access in accordance with aspects of the present disclosure. The non-roaming 6G architecture 400 comprises a 5G / 6G UE 410, a 5GC + 6GC 404 (indicated by a box with a dashed line), a 5G RAN 417, a 5G Cell 457, a 6GRAN 415, and a 6G Cell 455. The 5GC + 6GC 404 comprises a common SBI bus 406, a UDM / UDR 435 (comprising a 5G UDM interface 434 and a 6G UDM interface 436), an NRF 430 (comprising a 5GNRF interface 429 and a 6GNRF interface 431), a first 6G NF 467, a second 6G NF 468, an SMF 452, a 6G SMF 450, an AMF 422, a 6G AMF 420, a 5G UPF 462 and a 6G UPF 460. The non-roaming 6G architecture 400 further comprises a UNAN 424 and aNon-3GPP Access 458 (e.g., WiFi).

[0057] The 5G / 6G UE 410 registers with the 6GS by using the 3GPP credentials (e.g., security keys) stored on the 5G / 6G UE 410. The 3GPP credentials are also used authenticate / authorize the 5G / 6G UE 410 over the 3GPP access. The 5G / 6G UE 410 may not use 6GS NAS to communicate with the 6GC., The 5G / 6G UE 410 and the 6GC may use a protocol over a secure connection (e.g., QUIC connection or Internet Protocol (IP) sec connection) to exchange signalling for registration and data connect! on / sessi on establishment.

[0058] The non-roaming 6G architecture 400 shows the SBI model of representation of the 6GS and a possible integration of the (untrusted) non-3GPP access 458 (e.g., WiFi). The UN AN 424 may comprise an Untrusted N3GPP Packet Gateway (UNPG) and / or an Untrusted N3GPP InterWorking Function (UNIWF).

[0059] The UNAN 424 may perform the following functionalities: 1) towards the 5G / 6G UE 410, the UNAN 424 may terminate the signalling connection and all data connections (e.g., using multiple QUIC connections and a QUIC payload (or QUIC Docket No. SMM920250239-GR-NPprotocol) for 3 GPP-specific information); 2) in the control plane towards the 6GC, the UNAN 424 may use (e.g.,, consume, offer) SBI interfaces towards other NFs; and 3) in the user plane towards the 6GC, the UNAN 424 may use N3’ tunnelling (or forwarding) towards the UPF.

[0060] The 5G AMF, 5G SMF or 5G UPF refer to functionality supported by the corresponding AMF 422, SMF 452 or UPF 462 in the 5GS specifications. The notation “5G” in front is used to show the difference to corresponding 6G NFs which might be introduced in the 6GS. The notation “AMF” and “5G AMF” may be used interchangeably herein but may represent the same functionality. The notation “6G AMF” represents a mobility and management NF that may be introduced in 6G and may have different functionality (or support different NF services) from the 5G AMF. EPS entities are not shown since EPS does not support an SBI interface.

[0061] Figure 5 illustrates an example of a non-roaming 6G architecture 500 using interface representation for integration of the non-3GPP access in accordance with aspects of the present disclosure. The non-roaming 6G architecture 500 comprises a 5G / 6GUE 510, a 6G / Radio Access Technology (RAT) 515, 6G AMF 520, a UNAN 525, aNon-3GPP Access 558 (e.g.,, WiFi, WLAN), an NRF 530, a UDM 535, an Authentication Server Function (AUSF) / AAA server / AAA proxy 537, a Compute NF 567, a 6G SMF 550, a 6G UPF 560 and an internet 509.

[0062] The non-roaming 6G architecture 500 represents the non-roaming architecture using interface representation for integration of the non-3GPP access 558. The 5G / 6G UE 510 may simultaneously use direct access to the Internet 509 from the Non-3GPP access 558 (indicated using a dashed line) and / or access to the 6GC via UNAN 524 (e.g., indicated by the dashed double dot line). The dashed double dot line shows the user plane data. The dashed single dot lines between the UE 510 and UN AN 524, as well as the solid lines between the UNAN 525 and other entities in the 6GC show the control plane (C-plane) signalling. The dotted line between the UNAN 524 and the 6G AMF 520 shows a C-plane interface for signalling exchange for mobility procedure when the 5G / 6GUE 510 moves between non-3GPP access 558 and 6G / RAT 515. The non-roaming 6G architecture 500 illustrates the role of the UNAN 524 to terminate both the control plane signalling and userDocket No. SMM920250239-GR-NPplane data from the UE 510. On the network side, the UNAN 524 acts as C-plane NF towards other 6GC C-plane NFs, e.g., the UNAN 524 is a producer of SBI services and consumer of SBI services towards the rother NFs. On the network side, the UNAN 524 terminates the user plane connection with one or more 6G UPFs.

[0063] The 5G / 6G UE 510 maintains policy for selecting whether to transmit traffic from the application layer directly from the non-3GPP access 558 to the Internet 509 (dashed line) or whether to use a data session (e.g., PDU Session, dashed double dot) with the 6GC via UNAN 524. In order to use the services offered by the 6GC (or 6GS), the UE 510 registers with the 6GC via UNAN 524 and the UE 510 may establish one or more data sessions with the 6GC via the UNAN 524.

[0064] There may be one or more secure connections between the UE 510 and the UNAN 524. The UNAN 524 may receive and transmit (e.g., via non-3GPP access 558 to or from the UE 510) a request and response messages to establish a new secure connection and / or modify an existing secure connection with the UE 510. Upon successful establishment of a secure connection, the UE 510 is assumed to be authenticated and authorized by the 6GC.

[0065] The signalling exchange between the UE 510 and the UNAN 524 in the control plane may use a 6g-n3gpp protocol message or data unit (e.g., PDU).

[0066] The 6g-n3gpp protocol message may comprise a registration request PDU type that may comprise at least one of: information for configuring the secure connection between the UE 510 and UNAN 524: an indication about the security mechanisms supported by the UE 510 (e.g., AKA’, 5G-AKA); or an indication about a supported transport mechanism capability (e.g., QUIC or IPsec).

[0067] The registration request PDU may comprise an indication of at least one of the following parameters to be used by the UNAN 524 for the registration procedure: a type of registration (e.g.,, initial registration or mobility from 3GPP access); a 6G / 5G, Globally Unique Temporary Identifier (GUTI) or Globally Unique Access and Mobility Management Function Identifier (GUAMI) (of an existing or last registration with theDocket No. SMM920250239-GR-NPPublic Land Mobile Network (PLMN)); a requested or supported capability; or a list of requested 3GPP services overN3GPP access.

[0068] The registration response PDU type may comprise an indication of at least one of: an allowed S-NSSAI; an allowed DNN; or a list of allowed service IDs over non-3GPP access. The deregistration request PDU type may comprise an indication of at least one of: a UE ID, a request to deregister the UE 510 from the 6GC. The deregistration response PDU type may indicate a result of the deregistration request message, e.g., positive or negative result. The connectivity establishment (or modification) request PDU type may include an indication of at least one of: a PDU Session ID, an S-NSSAI, a DNN, an SSC mode, or a type of connectivity (e.g., IPv4, IPv6 or Ethernet). The connectivity establishment (or modification) response PDU type may include the result (e.g.,, ack or Nack) of the connectivity establishment (or modification) request type. The connectivity establishment (or modification) establishment response type may result in the establishment of a new sub-connection (e.g.,, tunnel, stream) between the UE 510 and the UNAN 524.

[0069] The UNAN 524 acts similar to AMF towards a) the UDM 535 and AUSF 537 during the registration procedure, b) the Policy Control Function (PCF) for AM related or UE related policies and c) the 6G SMF 550 during session management procedure.

[0070] The UNAN 524 may indicate to the target NFs that non-3GPP access is used by the UE. The UE 510 may not support NAS Session Management (SM) over non-3GPP access. The UNAN 524 may create an N1 container (e.g., an N1 SM container or N1 policy container) on behalf of the UE 510 in order to avoid change to the service producer NF. The UNAN 524 may use a new container type in the SBI service messages (e.g., Nsmf or Npcf) to indicate UE specific parameters to the target NFs. On the user plane, the UNAN 524 behaves like an N3IWF towards the UE 510 and towards the 6G UPF 560 (e.g., N3 tunnel establishment and management). The UE subscription data may be created in the UDM 535 and provided by the UDM 535 to the UNAN 524.

[0071] The UDM / UDR 535 may create and store 6G non-3GPP related subscription data for a UE 510. The 6G non-3GPP related subscription data may be provided to the corresponding UNAN 524.Docket No. SMM920250239-GR-NP

[0072] The 6G non-3GPP related subscription may comprise AM / MM subscription data for non-3GPP access type. The AM / MM subscription data may comprise an indication of at least one of: a list of allowed DNNs for the non-3GPP access, a list of allowed S-NSSAIs (and associated DNNs) for the non-3GPP access, a list of allowed services for the non-3GPP access (e.g., Al service, compute service, list of one or more IP Multimedia Subsystem (IMS) services, etc.). The AM / MM subscription data is provided to the UNAN 524. The UDM / UDR 535 may further provide SM subscription data for non-3GPP access type. The SM subscription data may comprise authorized DNNs and an S-NSSAI, one or more session QoS profiles or parameters, charging characteristics, and / or security policies for the user plane specific for the non-3GPP access. The SM subscription data is provided to the 6G SMF 550 indicating non-3GPP access type.

[0073] The UDM 535 may discriminate, based on a discrimination factor, the request for 6G Access Management (AM) 3GPP-related subscription data and 6G AM non-3GPP related subscription data. The discrimination factor may comprise the type of the source NF requesting the subscription data (e.g., 6G AMF 550 or UNAN 524). The discrimination factor may comprise an explicit indication from the source NF (e.g. UNAN 524 or 6G AMF 520) indicating whether AM subscription data for 3GPP access or for non-3GPP access is requested. The UDM 535 receives a request message from the UNAN 524 indicating that the UNAN 524 is the serving node for the UE 510 for the non-3GPP access type.

[0074] Figure 6 illustrates an example of a control plane protocol stack 600 for signalling between a UE and a 6GC via non-3GPP access in accordance with aspects of the present disclosure. The control plane protocol stack 600 comprises a UE 610, a UNAN 624 and 6GNFs 667 (e.g., UDM, SMF, PCF). The UE 610 comprises Upper Layer modules, e.g., Connection manager with URSP rules, a 6g-n3gpp protocol, QUIC or IKEv2, User Datagram Protocol (UDP) / IPv4 / IPv6, and Layer 1 and Layer 2 (L2 / L1). The UN AN 624 comprises 6g-n3gpp protocol entity to the UE 610, QUIC or IKEv2 protocol entity to the UE 610, UDP / IPv4 / IPv6 protocol entity to the UE 610, L2 / L1 to the UE 610, SBI (Nsmf, Nudm, Npcf) services entity to the 6GNFs 667, transport connection to the 6GNFs 667, and lower layers to the 6GNFs 667. The 6GNFs 667 comprise an SBI services entity toDocket No. SMM920250239-GR-NPthe UNAN 624, a transport connection to the UNAN 624 and lower layers to the UNAN 624.

[0075] The control plane protocol stack 600 is a protocol stack in the control plane for the signalling between 1) the UE 610 and UNAN 624 via non-3GPP access and 2) UNAN 624 and other control plane (C -plane) entities. The L1 / L2 and Lower Layer indicate physical and data link layer communications. The network or transport layer above L1 / L2 is the IP layer. The IP layer may include IPv4 or IPv6 protocol and also use UDP as transport datagram protocol.

[0076] On top of the UDP, between the UE 610 and the UNAN 624, there may be different communication protocols used for the establishment of a secure (e.g.„ encrypted) signalling connection, e.g., IKEv2 or QUIC protocol. The UE 610 may use IKEv2 or QUIC protocol related signalling to initiate a secure connection establishment with the UNAN 624. If IKEv2 is used, an IPsec tunnel between the UE 610 and the UNAN 624 is established. If QUIC protocol is used, the UE 610 may act as a QUIC client and initiate the establishment of secure QUIC connection (e.g., using Transport Layer Security (TLS)1.3 or another version of TLS). The UNAN 624 acts as a QUIC server. The QUIC protocol or the HyperText Transfer Protocol version 3 (HTTPv3 or HTTP / 3) protocol within the QUIC packet may introduce a new payload type for the specific control signalling between the UE 610 and UNAN 624, e.g., called “6g-n3gpp protocol”. The “6g-n3gpp protocol” message may be carried as payload of the HTTP / 3 protocol payload. The “6g-n3gpp protocol” layer may indicate to the upper layer that a secure connection is established. In the Figure 6, the upper layer is shown as a connection manager layer (or module) of the UE 610 which may maintain the User Equipment Route Selection Policy (URSP) rules that area used to select an appropriate data session for the application traffic. The process in the UE 610 is described in 775a in Figure 7.

[0077] The UE 610 may determine to establish a new PDU Session, or an existing PDU Session may be handed over from 3GPP to non-3GPP access. The connection manager module may create a request for the PDU session and send the request over the “6g-n3gpp protocol” layer. The “6g-n3gpp protocol” layer creates a connectivity establishment requestDocket No. SMM920250239-GR-NPmessage and sends this message via a transport functionality of the 6g-n3gpp protocol to the UNAN 624.

[0078] Figure 7 illustrates an example of a process flow 700 for a registration and session establishment procedure via UNAN in accordance with aspects of the present disclosure. The process flow 700 may implement or be implemented by aspects of the wireless communication system 100. For example, the process flow 700 may include a 5G / 6G UE 710, a UNAN / UNPG 724, a UPF 760, an SMF 750, a UDM 735 and an AUSF 737 which may be one or more examples of devices described herein with reference to Figure 1.

[0079] The process flow 700 may be referred to as a procedure, including one or more operations performed by one or more of the 5G / 6G UE 710, UNAN / UNPG 724, UPF 760, SMF 750, UDM 735 and AUSF 737.

[0080] In the following description of the process flow 700, the operations or signalling performed between one or more of the 5G / 6G UE 710, UNAN / UNPG 724, UPF 760, SMF 750, UDM 735 and AUSF 737may be performed or signalled (e.g.„ transmitted, received) in a different order than the example order shown, or the operations or signalling performed by one or more of the 5G / 6G UE 710, UNAN / UNPG 724, UPF 760, SMF 750, UDM 735 and AUSF 737may be performed or signalled (e.g.„ transmitted, received) in different orders or at different times. Some operations or signalling may also be omitted from the process flow 700. Additionally, although some operations or signalling may be shown to occur at different times, these operations or signalling may occur at the same time or in overlapping time periods.

[0081] Process flow 700 shows the detailed signalling flow for the procedures for registration, and data connectivity (e.g., data session) establishment via UNAN.

[0082] Process flow starts at 771a, the 5G / 6G UE 710 uses its non-3GPP interface (e.g., WLAN or Wi-Fi) and selects an available WLAN network, e.g., a residential WLAN network, a public hotspot. The 5G / 6G UE 710 connects to the non-3GPP access network and obtains a local IP address from the WLAN network. The UE 710 may use a password or another mechanism to obtain access to the WLAN networkDocket No. SMM920250239-GR-NP

[0083] If the UE 710 has a subscription with a network operator deploying 6GS and the UE 710 wants to use 3 GPP specific services, e.g., IMS for voice, video or message communication, Al service, Compute service or any other service provided by the 6GS, the UE 710 may establish a connection to the 6GS. The UE 710 may have local configuration or stored policy configuration to discover and connect to a UNAN 724 in the 6GS via the untrusted non-3GPP network. The UE 710 may have a Fully Qualified Domain Name (FQDN) of the UNAN 724 and start a Domain Name System (DNS) procedure to resolve the IP address of the UNAN 724 that is offered for access via non-3GPP access.

[0084] The UE 710 initiates the connection establishment by transmitting a request message to the UNAN 724 including its UE identity and an indication about the desired secure transport protocol for communication, e.g., IPsec or QUIC protocol. Alternatively, the UE 710 may use a decorated FQDN or Uniform Resource Locator (URL) which includes the capability to support a specific communication protocol, e.g., IPsec or QUIC protocol. For example, the UE 710 may discover a first UNAN 724 that supports IPsec protocol and a second UNAN 724 that supports QUIC protocol. The UE 710 may select the UNAN 724 that supports the preferred communication protocol.

[0085] During the QUIC connection establishment, the UE 710 may indicate the support of the “6g-n3gpp protocol” and if the UNAN 724 also supports the “6g-n3gpp protocol”, the UNAN 724 proceeds with the authentication procedure. If the UNAN 724 doesn’t support the “6g-n3gpp protocol”, the UNAN 724 may send a message to the UE 710 indicating that the “6g-n3gpp protocol” is not supported. In such case, the UE 710 may start using IKEv2 protocol for secure connection establishment.

[0086] In 771b, the UNAN 724 performs authentication of the UE identity using the 3 GPP 6G entity for non-3GPP access authentication. For example, the UNAN 724 may use the AUSF 737 services (or AAA server) to perform the UE 710 authentication. A mutual authentication and authorization procedure may be performed where the UE 710 also authenticates the 6GS network. A two-step procedure may be performed In a first step of the two step procedure, an authentication procedure (e.g., EAP-AKA or EAP-AKA’ authentication method) is performed. In a second step of the two step procedure, a secure connection is established. The secure connection may be based on IPsec or QUICDocket No. SMM920250239-GR-NPconnection. During this step the UNAN 724 may receive the UE subscription identity (e.g., Subscription Permanent Identifier (SUPI)) from the AUSF 737. The UE 710 may indicate to the UNAN 724 its capability to support shared key derivation, e.g., for QUIC connection. The UE 710 and the UNAN 724 may derive a common shared key, e.g., called "Non-3GPP Access" key or pre-shared key (PSK). The UNAN 724 may provide to the UE 710 an address to be used for the QUIC connection with the PSK, e.g., the parameter containing the address may be called ‘UNAN C-plane ADDRESS’. The UNAN 724 may use EAP-AKA' authentication message to include the ‘UNAN C-plane ADDRESS’.

[0087] In 771c, after a successful authentication procedure in 771b, the UE 710 may use the shared key with the UN AN 724 and the UE 710 may initiate towards the UNAN 724 the establishment of a new secure connection (e.g., a new QUIC connection) for the transmission of the control plane signalling between the UE 710 and the UNAN 724. The UE 710 may use the UNAN C-plane address received during 771b. The secure connection (e.g., a new QUIC connection) may be for the transmission of the control plane signalling between the UE 710 and the UNAN 724. This same secure connection may be also used for the signalling exchange in the steps 772b, 774a, 775b and 779. The UE 710 and the UNAN 724 may support a specific protocol different from NAS protocol for the exchange of control plane information, e.g., a 6g-n3gpp protocol as described in 772b. The UE 710 and UNAN 724 may use a QUIC stream via a second Websocket to exchange the 6g-n3gpp protocol messages.

[0088] In 772a, the UNAN 724 may be internally configured to trigger the UE 710 registration procedure with the 6GC based on the successful establishment of the secure connection is 771c. The UNAN 724 may proceed with the 772c to request the UE subscription data from the UDM 735. The UNAN 724 may use the UE identity which was authenticated during 771b.

[0089] 772b is optional or conditional to 772a (e.g., depending on the UE supported capabilities). There may be a specific protocol (e.g., 6g-n3gpp protocol) supported between the UE 710 and UNAN 724 for the exchange of 3 GPP -related information over the secure connection. For example, the information carried by the 6g-n3gpp protocol can comprise any information relevant for MM or SM procedures between the UE 710 and 6GC. Where aDocket No. SMM920250239-GR-NPQUIC secure connection is used, the 6g-n3gpp protocol message may be included in a QUIC PDU payload as direct QUIC payload or as a HTTP / 3 payload. The UE 710 may have indicated to the UNAN 724 in any of steps 771a, 771b or 771c that the UE 710 supports the capability of the 6g-n3gpp protocol exchange. The UE 710 may transmit (e.g., send) a QUIC PDU including a 6g-n3gpp protocol request message to the UNAN 724. The 6g-n3gpp protocol request message may be of type registration request and may include at least one of: an indication about the type of registration (initial registration or mobility from 3GPP access), a 6G / 5G GUTI, a GUAMI (of an existing or last registration with this PLMN), a requested or supported capability, or a list of requested 3GPP services over N3GPP access. If the UE 710 indicates 6G GUTI or 5G GUTI (or GUAMI), the UNAN 724 determines that the UE 710 has been registered with the 6GC or 5GC correspondingly. The UNAN 724 discovers the 6G AMF or 5G AMF based on the 6G GUTI or 5G GUTI and the UNAN sends a request message to the selected 6G / 5G AMF to retrieve the UE Mobility Management (MM) context.

[0090] In 772c, the UNAN 724 may retrieve the UE subscription data. Based on the UE Identity (ID) (e.g., SUPI) from the 771b, the UNAN 724 may discover a UDM 735. The UNAN 724 sends (e.g., transmits) a request message to the UNAN 724 including at least one of the parameters: a UE subscription ID (e.g., SUPI), an indication for requesting UE subscription data, an indication that the UE 710 is accessing the 6GC via non-3GPP access type, or a location of the non-3GPP access (e.g., country ID of the non-3GPP / WLAN location).

[0091] In 772d, the UDM 735 may store 6G non-3GPP related subscription data for the AM / MM procedure for the UE 710. The UDM 735 may provide some limited UE subscription data to the UNAN 724 compared with the UE subscription data provided to the AMF. For example, some parameters like forbidden areas may be expressed in a different way (e.g., WLAN Access Point (AP) location restriction) or the Subscribed slices / DNNs may be different / less than compared to 3GPP access. Some 3GPP-access specific parameters may not apply to non-3GPP access and may be omitted in the UE subscription data to the UNAN for example: RAT / Frequency Selection Priority (ID / Index) (RFSP), Closed Access Group (CAG) information, UE- Aggregate Maximum Bit Rate (AMBR),Docket No. SMM920250239-GR-NPLocal Area Data Network (LADN), Registration / extended Discontinuous Reception (eDRX) timers, Active timer, Mobile Initiated Connection Only (MICO) mode, Multicast and Broadcast Services (MBS), Vehicle-to-Everything (V2X), ALto-Everything (A2X), Proximity Services (ProSe). The UE subscription data may be referred to as AM / MM subscription data for non-3GPP access type. The AM / MM subscription data for non-3GPP access type may comprise at least one of: a list of allowed DNNs for the non-3GPP access, a list of allowed S-NSSAIs for the non-3GPP access, or a list of allowed services for the non-3GPP access (e.g., Al service, compute service, list of one or more IMS services, etc.).

[0092] The UDM 735 may transmit the AM / MM subscription data for non-3GPP access type to the UNAN 724 in a response message to 772c. If the UE 710 is not subscribed or allowed to use 6GS services via the non-3GPP access (or depending on the location of the non-3GPP access), the UDM 735 may send an indication to the UN AN 724 that the UE 710 is not subscribed or not allowed to access the 6GS services via the non-3GPP access. As a result, the UNAN 724 may reject the registration of the UE 710 to the 6GS in 774a.

[0093] In 773, the UNAN 724 may create and store UE’s 710 AM / MM context for non-3GPP access which may include at least one of the parameters: UE subscription ID; allowed S-NSSAIs for the non-3GPP access; allowed DNNs for the non-3GPP access; or an indication of whether for some of the DNNs interworking with 3GPP access is supported. The allowed S-NSSAIs and / or allowed DNNs for the non-3GPP access may also depend on the location of the non-3GPP access node (e.g., WLAN access point).

[0094] In 774a, the UNAN 724 transmits a response message to the UE 710, e.g., QUIC PDU including a 6g-n3gpp protocol registration response message. The 6g-n3gpp protocol registration response message may include at least one of: a UE temporary ID associated with the UNAN 724 (e.g., similar to GUTI associated with the AMF); a list of allowed S-NSSAIs; a list of allowed DNNs per S-NSSAI; a list of allowed services for the non-3GPP access; or other access specific configuration parameters. The parameters sent to the UE 710 are valid for the non-3GPP access type.

[0095] The UNAN 724 may determine that the UE 710 is not allowed (e.g,, not permitted) to register for the 6GC services. There may be one or more reasons for not Docket No. SMM920250239-GR-NPallowing the UE registration, e.g., the UE’s currently used non-3GPP access is not allowed (e.g., the provider of the non-3GPP access is not allowed), the location of the non-3GPP access is not allowed (e.g., the non-3GPP access is located is a forbidden country), the UE subscription data (e.g., as received in 772d) indicate that the UE 710 is not allowed to use 6GC services via non-3GPP access, or there is some temporary limit of not using the non-3GPP access (e.g., there is a forbidden and allowed period of using this access type). If the UNAN 724 determines that the UE 710 cannot register with the 6GC, the UNAN 710 sends (e.g., transmits) a failure indication in the 6g-n3gpp protocol registration response message and the UN AN 710 may indicate the reason of failure as described above in the reasons for not allowing the UE registration. The UNAN 724 may also send (e.g., transmit) a 6g-n3gpp protocol registration reject message. The UNAN 724 may also indicate to the UE 710 a timer value or other conditions when and how the UE 710 may initiate a new registration request from the non-3GPP access. In response to congestion at the UNAN 724, the UNAN 724 may indicate to the UE 710 a reject cause of congestion situation and the further indication when the UE 710 may re-initiate the registration via the non-3GPP access.

[0096] In response to rejection of the registration procedure, the UE 710 and UNAN 724 may release the security connection (e.g., QUIC connection) established in 771c. If there was an indication about the a timer value or other conditions when and how the UE 710 may initiate a new registration request via a non-3GPP access, the UE 710 should store this information internally (e.g., even without a secure connection with the UNAN 724), so that the UE 710 may initiate either 771a (to re-start the procedure) or 771c (when keeping the derived PSK, e.g., if the live-time of the PSK is long enough). When starting with 771c, the UNAN 724 may keep (e.g., store) a context (e.g., state) for the UE 710 and the corresponding PSK. The UE 710 may send (e.g., transmit) a 6g-n3gpp protocol response message to acknowledge the successful reception and processing of the 6g-n3gpp protocol registration response message. This acknowledgment message may indicate to the UNAN 724 that the registration procedure of the UE 710 is finalized and the UE 710 has been configured successfully with the information provided in the registration response message.

[0097] In 474b, the UNAN 724 may register itself with the UDM 735 as a serving NF for the UE 710 via non-3GPP access type. For this purpose, the UNAN 724 may send (e.g.,Docket No. SMM920250239-GR-NPtransmit) a request message to the UDM 735 including at least the parameters: UE subscription ID (e.g., SUPI), UNAN ID, or indication of non-3GPP access type. The UDM 735 stores the association of the SUPI registered at the serving UNAN ID.

[0098] In 775a, when an application requests a connectivity service, the UE 710 may use policies, e.g., URSP rules, to determine how the application traffic should be routed. The UE 710 determines whether to send (e.g., transmit) the application traffic directly from the non-3GPP access to the Internet or whether to use a data session (e.g., PDU Session) with the 6GC via UNAN 724. If the UE 710 determines to use a data session (e.g., PDU Session) with the 6GC via UNAN 724, the UE 710 may either 1) initiate the establishment of a data session with the 6GC via the secure connection with the UNAN 724; or 2) use an existing data session over the non-3GPP access; or 3) decide to hand over a data session from the 3GPP access to the non-3GPP access. The UE 710 may establish one or more data sessions with the 6GC via the UNAN 724.

[0099] A URSP rule contains a Traffic Descriptor (TD) and Route Selection Descriptor (RSD). The TD is used to determine when information (e.g., request) provided from an application matches the URSP rule. For example, the TD helps the UE 710 to identify traffic which has to be routed via a specific PDU Session. The traffic identification may be based on different criteria e.g., destination address, source application client, destination network identity (e.g., data network name, DNN) and others. The RSD is used to determine the parameters to be used for the PDU Session, e.g., the RSD may contain at least one of the types of information: Network Slice Selection (e.g., S-NSSAI), DNN Selection (e.g., DNN, APN), Session and Service Continuity (SSC) Mode, PDU Session Type Selection (e.g., IP type like IPv6 or IPv4 or Ethernet type), etc. The UE 710 determines the parameter for the data session based on the RSD parameters of the matched URSP rule. For example, the UE 710 (e.g., connection manager with URSP rules) determines to use at least one of the following parameters and provides them to the 6g-n3gpp protocol: S-NSSAI, DNN, SSC mode, PDU session type, UP security to be used for the data session, etc. There may be multiple RSDs for an URSP rule. The UE 710 may use the Allowed NSSAI received in 774a to determine which RSD in the URSP rules is valid. The UE 710 may also determine which services are allowed to be used via the non-3GPP access based on the combinationDocket No. SMM920250239-GR-NPof S-NSSAI and / or DNN. The UE 710 may internally configure allowed services that can be used over the N3GPP access.

[0100] In 775b, the UE 710 creates and sends (e.g., transmits) a 6g-n3gpp protocol message of type indicating a request for establishing a data session with the 6GC. The 6g-n3gpp protocol message is transmitted over the secure connection with the UNAN 724 (e.g., QUIC connection). The 6g-n3gpp protocol data session request message may include the information that is provided by the upper layer (e.g., connection manager module with the help of the URSP rules) and may comprise one or more RSD parameters of the matching URSP rule as described in 775a. The 6g-n3gpp protocol data session request message may include at least one of: PDU Session ID, S-NSSAI, DNN, SSC mode; data session type (e.g., IPv4, IPv6 or Ethernet), indication for new data session or indication for handover on an existing data session (e.g., from 3GPP access to non-3GPP access), indication for non-3GPP access type, or other protocol configuration options. The UE 710 may create a unique PDU Session ID, which is not used for other data sessions, in coordination with the NAS SM sublayer used via the 3 GPP access.

[0101] In 776a, the UNAN 724 performs an SMF selection procedure based on a) local configuration at UN AN 724, 2) SMF selection information received from the UDM 735 in 774b, and / or 3) or 3) using the NRF services. As the SMF 750 functionality may be specific for the operation for non-3GPP access as described in 777a, the UNAN 724 may use NRF services to discover and select SMF 750 by using an indication that the SMF 750 should be capable for establishing data sessions over non-3GPP access. The UNAN 724 may send a request message to NRF to request an SMF ID (or address) and include in indication that the SMF 750 is required to support data sessions establishment over non-3GPP access. If the UE 710 has indicated that this is an existing data session in 775b, the UNAN 724 may send (e.g., transmit) a request to the UDM 735 to resolve the currently serving SMF 750 for the data session (e.g., PDU Session).

[0102] In 776b, the UNAN 724 sends (e.g., transmits) a request message for data session establishment. The UNAN 724 may use the SBI serviceNsmf PDUSession CreateSMContext and include a request message. The request message may include at least one of: PDU Session ID, S-NSSAI, DNN, SSC mode; indication forDocket No. SMM920250239-GR-NPnew data session or indication for handover for an existing data session (e.g., from 3GPP access to non-3GPP access), or indication for using non-3GPP access type.

[0103] The UNAN 724 may create N1 -specific container message (e.g., N1 SM container) on behalf of the UE 710. The UNAN 724 may use the information sent from the UE 710 in 775b and creates the N1 SM container. For example, the UNAN 724 creates a NAS SM PDU Session establishment request message and sends (e.g., transmits) the NAS SM message to the SMF 750 together with the PDU Session ID, S-NSSAI and DNN that may be outside of the NAS SM message. The SMF 750 may not be required to differentiate between data session establishment via non-3GPP access and via 3GPP access. The SMF 750 behaviour may be the same for data session establishment independent of the Access Network (AN) access type.

[0104] The UNAN 724 sends (e.g., transmits) a request message to the SMF 750 using the same or similar information as received in 775b. The request message to the SMF 750 may not include an N1 SM container. The SMF 750 may differentiate that this is a request from UNAN 724 for data session over non-3GPP access different from the request for data session over 3 GPP access from AMF.

[0105] In 777a, the SMF 750 functionality may be modified compared to 5G SMF in order to allow the reception of requests messages for PDU Session establishment / modification from the UNAN 724 without a NAS SM container, e.g., as described in 776b . If the SMF 750 supports such capability, the SMF 750 may register this capability with the NRF. During the NF registration process with the NRF, the SMF 750 may indicate at least one of: capability to support PDU Session establishment / modification without NAS SM container or capability to support PDU Session establishment / modification via non-3GPP access. The SMF 750 may receive (e.g., retrieve) the SM subscription data from the UDM 735. The SMF 750 may indicate non-3GPP access type to the UDM 735. The UDM 735 may store SM subscription data for non-3GPP access type that may comprise QoS parameters specific for the non-3GPP access. This data is provided to the SMF 750 indicating non-3GPP access type. If the establishment of the data session is successful, the SMF creates and stores SM context for the PDU Session of the UE. The SM context may include QoS rules for one or more QoS flows.Docket No. SMM920250239-GR-NP

[0106] In 777b, the SMF 750 selects a UPF 760 for the data session. The SMF 750 sends (e.g., transmits) configuration information to the UPF 760 for the data session. The UPF 760 may respond to the SMF 750 with the IP address to be used for the N3’ tunnel towards the AN.

[0107] In 778a, the SMF 750 sends (e.g., transmits) a response message to the UNAN 724 as a response to 776b. The response message may include at least one of: UE ID (e.g., SUPI), PDU Session ID, result indication of the data session establishment, AN SM information, or SM information for the UE. The AN SM information indicates one or more QoS flows and the corresponding QoS parameters to be used for the user data. The AN SM parameters may include at least one of: a tunnel endpoint address (e.g., UPF IP address) to which the RAN node establishes a N3’ tunnel; one or more QoS profiles corresponding to one or more QoS flows within the PDU Session. The UNAN 724 uses the AN SM parameters to determine how many sub-connections (e.g., QUIC connections or streams) should be established towards the UE 710 and corresponding N3 tunnels towards the UPF 760. The SM information for the UE 710 is signalling data that is targeted to the UE 710. The UNAN 724 may forward the SM information transparently to the UE 710, e.g., via the 6g-n3gpp protocol. The QoS information for the UE 710 may include QoS rules for one or more QoS flows similar to the QoS flow information specified in the 5GS.

[0108] In 778b, the SMF 750 may register the successfully established (or handed over) data session with the UDM.

[0109] In 779, the UNAN 724 sends (e.g., transmits) a 6g-n3gpp protocol message indicating data session response message over the QUIC connection. The 6g-n3gpp protocol data session response message may indicate at least one of the following parameters: PDU Session ID, result of the data session establishment (e.g., success or failure), or SM information for the UE. The PDU Session ID may be used by the UE 710 to correlate that the response message is related to the request message transmitted in 774a. The SM information for the UE 710 is the same as information as received by the SMF 750 in 778a.

[0110] Based on the QoS profile received in 778a, the UNAN 724 may determine that the user data for the data session requires a QoS handling different from the QoS handling Docket No. SMM920250239-GR-NPof the control signalling (e.g., 6G-n3gpp protocol, as per the already used blue-coloured QUIC connection). The UNAN 724 may determine to indicate to the UE 710 that a new secure connection (e.g., a new QUIC connection) for the use data transmission should be established. A separate QUIC connection may allow a QoS packet marking (e.g., using Differentiated Services Code Point (DSCP) in case of Differentiated Services (DiffServ) markings) of the outer IP packets. The network entities between the UE 710 and the UN AN 724 (e.g., WLAN AP, routers) may apply expedited forwarding for the packets of one QUIC connection compared to other QUIC connection.[OHl] In 780a, if the UE 710 has received an indication in 779 that a new secure connection (e.g., a new QUIC connection) for the use data transmission is to be established, the UE 710 initiates the establishment of a new QUIC connection. For example, the UE 710 may use the same shared key (e.g., PSK) as used in 771c. If the SM information for the UE 710 as received in 779 indicates multiple QoS flows to be established within the data session, the UE 710 may initiate the establishment of a separate QUIC connection per QoS flow in order to differentiate the data handling in the user plane. The network between UE 710 and UNAN 724 may then apply different traffic engineering policies (e.g., different DSCP handling, queuing behaviour) to the separate QUIC connections based on their respective 5-tuples. If a single (e.g., default) QoS flow is setup for the PDU Session, then a single new QUIC connection is established to transmit the data packets belonging to the PDU Session.

[0112] On the N3’ interface between the UNAN 724 and UPF 710, the UNAN 724 may multiplex the QoS flows on the same N3’ tunnel and tagging the QoS flows with different QoS flow identifier (QFI). The network may apply different traffic engineering policies (e.g., different DSCP handling, queuing behaviour) to the separate connections based on their respective 5-tuples.

[0113] In 780b, the UNAN 724 may establish an N3’ tunnel towards the UPF 760 according to the UPF tunnel endpoint address received in the AN SM parameters in 778a. The UNAN 724 may establish a single N3 tunnel to the UPF 760 even if there are multiple QUIC connections established by the UE 710 in 780a for the same data session.Docket No. SMM920250239-GR-NP

[0114] In some examples described herein, the UNAN 724 terminates the signalling connection and all data connections (e.g., using multiple QUIC connection) towards the UE 710. In the control plane towards the 6GC, the UNAN 724 may use (e.g., consumes and offers) SBI interfaces towards other NFs. In the user plane towards the 6GC, the UNAN 724 may use N3’ tunnelling (or forwarding) towards the UPF 760. The use of a single NF (e.g., UNAN 724) tends to offer scalable and efficient integration of the (untrusted) non-3GPP access in the 6GS. Some examples described herein may be applied for public networks, e.g., PLMN, or for private network, e.g., Non-Public Network (NPN) or Standalone NPN (SNPN).

[0115] Figure 8 illustrates an example of a UE 800 in accordance with aspects of the present disclosure. The UE 800 may include a processor 802, a memory 804, a controller 806, and a transceiver 808. The processor 802, the memory 804, the controller 806, or the transceiver 808, 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.

[0116] The processor 802, the memory 804, the controller 806, or the transceiver 808, 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.

[0117] The processor 802 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 802 may be configured to operate the memory 804. In some other implementations, the memory 804 may be integrated into the processor 802. The processor 802 may be configured to execute computer-readable instructions stored in the memory 804 to cause the UE 800 to perform various functions of the present disclosure.

[0118] The memory 804 may include volatile or non-volatile memory. The memory 804 may store computer-readable, computer-executable code including instructions when Docket No. SMM920250239-GR-NPexecuted by the processor 802 cause the UE 800 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such the memory 804 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 special-purpose computer.

[0119] In some implementations, the processor 802 and the memory 804 coupled with the processor 802 may be configured to cause the UE 800 to perform one or more of the functions described herein (e.g., executing, by the processor 802, instructions stored in the memory 804). For example, the processor 802 may support wireless communication at the UE 800 in accordance with examples as disclosed herein. The UE 800 may be configured to support a means for transmitting, via a non-3GPP access network, a first request message for registering the UE with a core network over a secure connection; and receiving, via the non-3GPP access network, a first response message indicating successful registration of the UE with the core network, wherein the first request message and the first response message comprise a first protocol, and wherein the secure connection comprises a second protocol different from the first protocol.

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

[0121] In some implementations, the UE 800 may include at least one transceiver 808. In some other implementations, the UE 800 may have more than one transceiver 808. The transceiver 808 may represent a wireless transceiver. The transceiver 808 may include one or more receiver chains 810, one or more transmitter chains 812, or a combination thereof.

[0122] A receiver chain 810 may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain 810 may include one or more antennas for receive the signal over the air or wireless medium. Docket No. SMM920250239-GR-NPThe receiver chain 810 may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiver chain 810 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 810 may include at least one decoder for decoding the processing the demodulated signal to receive the transmitted data.

[0123] A transmitter chain 812 may be configured to generate and transmit signals (e.g., control information, data, packets). The transmitter chain 812 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 812 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 812 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.

[0124] Figure 9 illustrates an example of a processor 900 in accordance with aspects of the present disclosure. The processor 900 may be an example of a processor configured to perform various operations in accordance with examples as described herein. The processor 900 may include a controller 902 configured to perform various operations in accordance with examples as described herein. The processor 900 may optionally include at least one memory 904, which may be, for example, an L1 / L2 / L3 cache. Additionally, or alternatively, the processor 900 may optionally include one or more arithmetic-logic units (ALUs) 906. 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).

[0125] The processor 900 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.Docket No. SMM920250239-GR-NPThe 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 900) 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).

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

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

[0128] The memory 904 may include one or more caches (e.g., memory local to or included in the processor 900 or other memory, such RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementations, the memory 904 may resideDocket No. SMM920250239-GR-NPwithin or on a processor chipset (e.g., local to the processor 900). In some other implementations, the memory 904 may reside external to the processor chipset (e.g., remote to the processor 900).

[0129] The memory 904 may store computer-readable, computer-executable code including instructions that, when executed by the processor 900, cause the processor 900 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 902 and / or the processor 900 may be configured to execute computer-readable instructions stored in the memory 904 to cause the processor 900 to perform various functions. For example, the processor 900 and / or the controller 902 may be coupled with or to the memory 904, the processor 900, the controller 902, and the memory 904 may be configured to perform various functions described herein. In some examples, the processor 900 may include multiple processors and the memory 904 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.

[0130] The one or more ALUs 906 may be configured to support various operations in accordance with examples as described herein. In some implementations, the one or more ALUs 906 may reside within or on a processor chipset (e.g., the processor 900). In some other implementations, the one or more ALUs 906 may reside external to the processor chipset (e.g., the processor 900). One or more ALUs 906 may perform one or more computations such as addition, subtraction, multiplication, and division on data. For example, one or more ALUs 906 may receive input operands and an operation code, which determines an operation to be executed. One or more ALUs 906 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 906 may support logical operations such as AND, OR, exclusive-OR (XOR), not-OR (NOR), and not- AND (NAND), enabling the one or more ALUs 906 to handle conditional operations, comparisons, and bitwise operations.Docket No. SMM920250239-GR-NP

[0131] The processor 900 may support wireless communication in accordance with examples as disclosed herein. The processor 900 may be configured to support a means for transmitting, via a non-3GPP access network, a first request message for registering the UE with a core network over a secure connection; and receiving, via the non-3GPP access network, a first response message indicating successful registration of the UE with the core network, wherein the first request message and the first response message comprise a first protocol, and wherein the secure connection comprises a second protocol different from the first protocol. The processor 900 may be configured to or operable to support a means for receiving, via a non-3GPP access network, a first request message for registering a UE with a core network over a secure connection; and transmitting, via the non-3GPP access network, a first response message indicating successful registration of the UE with the core network, wherein the first request message and the first response message comprise a first protocol, and wherein the secure connection comprises a second protocol different from the first protocol.

[0132] Figure 10 illustrates an example of a NE 1000 in accordance with aspects of the present disclosure. The NE 1000 may include a processor 1002, a memory 1004, a controller 1006, and a transceiver 1008. The processor 1002, the memory 1004, the controller 1006, or the transceiver 1008, 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.

[0133] The processor 1002, the memory 1004, the controller 1006, or the transceiver 1008, 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.

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

[0135] The memory 1004 may include volatile or non-volatile memory. The memory 1004 may store computer-readable, computer-executable code including instructions when executed by the processor 1002 cause the NE 1000 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such the memory 1004 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 special-purpose computer.

[0136] In some implementations, the processor 1002 and the memory 1004 coupled with the processor 1002 may be configured to cause the NE 1000 to perform one or more of the functions described herein (e.g., executing, by the processor 1002, instructions stored in the memory 1004). For example, the processor 1002 may support wireless communication at the NE 1000 in accordance with examples as disclosed herein. The NE 1000 may be configured to support a means for receiving, via a non-3GPP access network, a first request message for registering a UE with a core network over a secure connection; and transmitting, via the non-3GPP access network, a first response message indicating successful registration of the UE with the core network, wherein the first request message and the first response message comprise a first protocol, and wherein the secure connection comprises a second protocol different from the first protocol.

[0137] The controller 1006 may manage input and output signals for the NE 1000. The controller 1006 may also manage peripherals not integrated into the NE 1000. In some implementations, the controller 1006 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some implementations, the controller 1006 may be implemented as part of the processor 1002.Docket No. SMM920250239-GR-NP

[0138] In some implementations, the NE 1000 may include at least one transceiver 1008. In some other implementations, the NE 1000 may have more than one transceiver 1008. The transceiver 1008 may represent a wireless transceiver. The transceiver 1008 may include one or more receiver chains 1010, one or more transmitter chains 1012, or a combination thereof.

[0139] A receiver chain 1010 may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain 1010 may include one or more antennas for receive the signal over the air or wireless medium. The receiver chain 1010 may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiver chain 1010 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 1010 may include at least one decoder for decoding the processing the demodulated signal to receive the transmitted data.

[0140] A transmitter chain 1012 may be configured to generate and transmit signals (e.g., control information, data, packets). The transmitter chain 1012 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 1012 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 1012 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.

[0141] Figure 11 illustrates a flowchart of a method 1100 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.

[0142] At 1102, the method 1100 may include transmitting, via a non-3GPP access network, a first request message for registering the UE with a core network over a secure Docket No. SMM920250239-GR-NPconnection. 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 UE as described with reference to Figure 8.

[0143] At 1104, the method 1100 may include receiving, via the non-3GPP access network, a first response message indicating successful registration of the UE with the core network, wherein the first request message and the first response message comprise a first protocol, and wherein the secure connection comprises a second protocol different from the first protocol. 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 UE as described with reference to Figure 8.

[0144] It should be noted that the method 1100 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.

[0145] Figure 12 illustrates a flowchart of a method 1200 in accordance with aspects of the present disclosure. The operations of the method 1200 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.

[0146] At 1202, the method 1200 may include receiving, via a non-3GPP access network, a first request message for registering a UE with a core network over a secure connection. The operations of 1202 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1202 may be performed by a NE as described with reference to Figure 10.

[0147] At 1204, the method 1200 may include transmitting, via the non-3GPP access network, a first response message indicating successful registration of the UE with the core network, wherein the first request message and the first response message comprise a first protocol, and wherein the secure connection comprises a second protocol different from the first protocol. The operations of 1204 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1204 may be performed by a NE as described with reference to Figure 10.Docket No. SMM920250239-GR-NP

[0148] There is provided herein a first network entity for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the first network entity to: receive, via a non-3GPP access network, a first request message for registering a UE with a core network over a secure connection; and transmit, via the non-3GPP access network, a first response message indicating successful registration of the UE with the core network, wherein the first request message and the first response message comprise a first protocol, and wherein the secure connection comprises a second protocol different from the first protocol. Such a first network entity tends to enable connectivity between the UE and first network entity without synchronization of the NAS protocol state machines.

[0149] The first request message and the first response message may be associated with the first protocol. The secure connection may be associated with the second protocol. The second protocol may be different than the first protocol. The first network entity may comprise a UNAN. The first network entity may comprise a UNPG. The first network entity may comprise an enhanced N3IWF. The first network entity may comprise an interworking function. The first network entity may comprise an interworking function for UE signaling and data to a 6G core network via the non-3GPP access network. The core network may comprise a 6GC. The non-3GPP access network may be an access network that provides IP connectivity to a UE. The non-3GPP access network may comprise an access network that is not specified or controlled by 3GPP radio access technologies. The non-3GPP access network may comprise a Wi-Fi or Wireless LAN (WLAN).

[0150] The first request message is terminated and processed at the first network entity. The processing of the first request message may result in further action performed by the first network entity. The first response message may comprise a connection establishment response message or registration response message. The second protocol may be at least one of: a QUIC protocol; or an IPsec protocol. The first protocol may comprise a 6G-N3GPP protocol. The first request message may comprise a registration request PDU type. The first response message may comprise a registration response PDU type.

[0151] The at least one processor may be further configured to cause the first network entity to: receive, via the non-3GPP access network, a second request message; andDocket No. SMM920250239-GR-NPtransmit, via the non-3GPP access network, a second response message, wherein the second request message and the second response message comprise the first protocol. The second request message may be transmitted over the secure connection. The second request message may be a request for data session establishment or data session modification. The second response message may be transmitted over the secure connection. The second request message and the second response message may be associated with the first protocol.

[0152] The second request message may comprise at least one of a deregistration request PDU type; a data session establishment request PDU type; or a data session modification request PDU type. In response to the received second request message comprising a data session establishment request PDU type, the method may further comprise: generating a NAS SM container to be transmitted to an SMF.

[0153] The second response message may comprise at least one of a deregistration response PDU type; a data session establishment response PDU type; or a data session modification response PDU type. The data session establishment request PDU type may comprise a PDU session establishment request PDU type. The data session modification request PDU type may comprise a PDU session modification request PDU type. The data session establishment response PDU type may comprise a PDU session establishment response PDU type. The data session modification response PDU type may comprise a PDU session modification response PDU type. The at least one processor may be further configured to cause the first network entity to: perform an authentication procedure with an authentication entity for successful establishment of the secure connection, wherein performing the authentication procedure comprises: receive, from the authentication entity, a UE subscription ID. The authentication entity may comprise an AUSF.

[0154] The at least one processor may be further configured to cause the first network entity to: transmit, to a UDM entity, a third request message for subscription data for registering the UE with the core network over the secure connection via the non-3GPP access network; and receive, from the UDM entity, a third response message comprising the subscription data. The third request message may comprise an indication of at least one of: a UE subscription ID; a request for the subscription data; the UE accessing a 6GC via the non-3GPP access network; or a location of the non-3GPP access network. The thirdDocket No. SMM920250239-GR-NPrequest message may comprise a request for subscription data. The UE accessing the 6GC via the non-3GPP access network may comprise the UE connecting to the 6GC via the non-3 GPP access network. The UE accessing the 6GC via the non-3GPP access network may comprise the UE registering with the 6GC via the non-3GPP access network. The subscription data may comprise an indication of at least one of: a subscribed network slice; a subscribed DNN; or a subscribed service. The subscribed service may comprise a compute service or an Al service.

[0155] The first request message may comprise an indication of at least one of: a type of registration; a GUTI; a GUAMI; a requested capability of the UE; a supported capability by the UE; or a request for a 3 GPP service over the non-3GPP access network. The 3 GPP service may comprise a 5G service. The 3GPP service may comprise a 5G service using a 5G SBI. The 3GPP service may comprise a 6G service. The 3GPP service may comprise a 6G service using a 6G SBI. The 3GPP service may comprise an Al service, a compute service, or an IMS service. The 3GPP service may comprise a 3GPP specific service.

[0156] There is further provided herein a method performed or performable by a first network entity, the method comprising: receiving, via a non-3GPP access network, a first request message for registering a UE with a core network over a secure connection; and transmitting, via the non-3GPP access network, a first response message indicating successful registration of the UE with the core network, wherein the first request message and the first response message comprise a first protocol, and wherein the secure connection comprises a second protocol different from the first protocol Such a method performed or performable by the first network entity tends to enable connectivity between the UE and first network entity without synchronization of the NAS protocol state machines.

[0157] The second protocol may be at least one of a QUIC protocol; or an IPsec protocol. The first protocol may comprise a 6G-N3GPP protocol. The first request message may comprise a registration request PDU type. The first response message may comprise a registration response PDU type. The method may further comprise receiving, via the non-3 GPP access network, a second request message; and transmitting, via the non-3GPP access network, a second response message, wherein the second request message and the second response message comprise the first protocol. The second request message mayDocket No. SMM920250239-GR-NPcomprise at least one of: a deregistration request PDU type; a data session establishment request PDU type; or a data session modification request PDU type. In response to the received second request message comprising a data session establishment request PDU type, the method may further comprise generating an NAS SM container to be transmitted to an SMF. The second response message may comprise at least one of: a deregistration response PDU type; a data session establishment response PDU type; or a data session modification response PDU type.

[0158] The method may further comprise performing an authentication procedure with an authentication entity for successful establishment of the secure connection, wherein performing the authentication procedure may comprise receiving, from the authentication entity, a UE subscription ID. The method may further comprise transmitting, to a UDM, entity a third request message for subscription data for registering the UE with the core network over the secure connection via the non-3GPP access network; and receiving, from the UDM entity, a third response message comprising the subscription data. The third request message may comprise an indication of at least one of: a UE subscription ID; a request for the subscription data; the UE accessing a 6GC via the non-3GPP access network; or a location of the non-3GPP access network. The subscription data may comprise an indication of at least one of: a subscribed network slice; a subscribed DNN; or a subscribed service. The first request message may comprise an indication of at least one of: a type of registration; a GUTI; a GUAMI; a requested capability of the UE; a supported capability by the UE; or a request for a 3 GPP service over the non-3GPP access network.

[0159] There is further provided herein a UE for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the UE to: transmit, via a non-3GPP access network, a first request message for registering the UE with a core network over a secure connection; and receive, via the non-3GPP access network, a first response message indicating successful registration of the UE with the core network, wherein the first request message and the first response message comprise a first protocol, and wherein the secure connection comprises a second protocol different from the first protocol. Such a UE tends to enable connectivityDocket No. SMM920250239-GR-NPbetween the UE and first network entity without synchronization of the NAS protocol state machines.

[0160] The second protocol may be at least one of a QUIC protocol; or an IPsec protocol. The first protocol may comprise a 6G-N3GPP protocol. The first request message may comprise a registration request PDU type. The first response message may comprise a registration response PDU type.

[0161] The at least one processor may be configured to cause the UE to transmit, via the non-3GPP access network, a second request message; and receive, via the non-3GPP access network, a second response message, wherein the second request message and the second response message comprise the first protocol. The second request message may comprise at least one of a deregistration request PDU type; a data session establishment request PDU type; or a data session modification request PDU type. The second response message may comprise at least one of a deregistration response PDU type; a data session establishment response PDU type; or a data session modification response PDU type. The first request message may comprise an indication of at least one of a type of registration; a GUTI; a GUAMI; a requested capability of the UE; a supported capability of the UE; or a request for a 3 GPP service over the non-3GPP access network.

[0162] There is further provided herein a method performed or performable by a UE, the method comprising: transmitting, via a non-3GPP access network, a first request message for registering the UE with a core network over a secure connection; and receiving, via the non-3GPP access network, a first response message indicating successful registration of the UE with the core network, wherein the first request message and the first response message comprise a first protocol, and wherein the secure connection comprises a second protocol different from the first protocol. Such a method performed or performable by the UE tends to enable connectivity between the UE and first network entity without synchronization of the NAS protocol state machines.

[0163] Some examples described herein relate to a UE that, in the control plane, supports and manages 6g-n3gpp protocol data units over a secure connection with the UNAN.Docket No. SMM920250239-GR-NP

[0164] Some examples described herein relate to a UNAN configured to support control plane signalling exchange between the UE and the UNAN. The UNAN may be configured to use of a 6g-n3gpp protocol for the registration of the UE with the 6GC and data session establishment between the UE and SMF / UPF. The UNAN may act similar to an AMF towards a) the UDM and AUSF during registration procedure, b) the PCF for AM related policies and c) the SMF during session management procedure. The UNAN may indicate to the target NFs that non-3GPP access is used by the UE. The UE may not support NAS SM over non-3GPP access. The UNAN may be configured to create an N1 container (e.g., an N1 SM container or an N1 policy container) on behalf of the UE in order to avoid change to the service producer NF. The UN AN may be configured to use a container type in the SBI service messages (e.g., Nsmf or Npcf) to indicate UE specific parameters to the target NFs.

[0165] Some examples described herein relate to a UDM / UDR configured to create and store 6G non-3GPP related subscription data for a UE. This data may be provided to the corresponding UNAN. The subscription data may comprise AM / MM subscription data for non-3GPP access type. The AM / MM subscription data for non-3GPP access type may comprise at least one of a list of allowed DNNs for the non-3GPP access, a list of allowed S-NSSAIs for the non-3GPP access, or a list of allowed services for the non-3GPP access (e.g., Al service, compute service, list of one or more IMS services, etc.). This data may be provided to the UNAN. The SM subscription data for non-3GPP access type may comprise QoS parameters specific for the non-3GPP access. This data may be provided to the SMF for indicating non-3GPP access type. The UDM may be configured to discriminate the request for 6G AM 3GPP-related subscription data and 6G AM non-3GPP related subscription data. The discrimination factors may comprise at least one of the type of the source NF requesting the subscription data (e.g., 6G AMF or UNAN); or an explicit indication from the source NF indicating whether AM subscription data for 3GPP access or for non-3GPP access is requested. The UDM may be configured to receive a request message from UNAN indicating that the UNAN is the serving node for the UE for the non-3 GPP access type.Docket No. SMM920250239-GR-NP

[0166] There is further provided herein a method for a first Network Function (e.g., a UNAN) part of a first communication system and second communication system, the method comprising: receiving a first request message for the establishment of a secure connection with a UE; discovering an authentication entity (e.g., AUSF) for 3GPP based authentication of the UE and performing an authentication procedure with the authentication entity to authenticate the UE (e.g., using the 3GPP based credentials), wherein as a result of the authentication procedure a secure connection with the UE is established; determining to trigger a registration procedure for the UE, wherein a request for UE subscription data is transmitted (e.g., to the UDM) including an indication for non-3 GPP access; and transmitting a first response message to the UE to acknowledge successful registration with the 6GC.

[0167] The method may further comprise receiving a second request message (e.g.,, sent by the UE) to request registration with the core network after the successful establishment of the secure connection with the UE. The method may further comprise receiving a third request message (e.g., from the UE) indicating the establishment of a data session. The third message may comprise at least one of a network slice identity (e.g., S-NSSAI), data network name (e.g., DNN) or a NAS container.

[0168] The method may further comprise selecting a session management function (e.g., 6G SMF) to serve the data session and transmitting a request message for data session establishment. The method may further comprise transmitting a second response message (e.g., to the UE) indicating the result of the establishment of a data session. The UE subscription data may comprise at least one of: a list of allowed network slice identities, a list of allowed data network names (e.g., DNNs); or a list of allowed service identifiers (e.g., compute service, Al service, etc.).

[0169] 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.

[0170] 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 Docket No. SMM920250239-GR-NPapplied 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.Docket No. SMM920250239-GR-NP

Claims

CLAIMSWhat is claimed is:

1. A first network entity for wireless communication, comprising:at least one memory; andat least one processor coupled with the at least one memory and configured to cause the first network entity to:receive, via a non-3GPP access network, a first request message for registering a user equipment, UE, with a core network over a secure connection; andtransmit, via the non-3GPP access network, a first response message indicating successful registration of the UE with the core network, wherein the first request message and the first response message comprise a first protocol, and wherein the secure connection comprises a second protocol different from the first protocol.

2. The first network entity of claim 1, wherein the second protocol is at least one of:a quick user datagram protocol internet connections, QUIC, protocol; or an internet protocol security, IPsec, protocol.

3. The first network entity of claim 1 or claim 2, wherein the first protocol comprises a 6G-N3GPP protocol.

4. The first network entity of any one of claims 1 to 3, wherein the first request message comprises a registration request protocol data unit, PDU, type and wherein the first response message comprises a registration response PDU type.

5. The first network entity of any one of claims 1 to 4, wherein the at least one processor is further configured to cause the first network entity to:receive, via the non-3GPP access network, a second request message; and transmit, via the non-3GPP access network, a second response message, wherein the second request message and the second response message comprise the first protocol.Docket No. SMM920250239-GR-NP6. The first network entity of claim 5, wherein the second request message comprises at least one ofa deregistration request PDU type;a data session establishment request PDU type; ora data session modification request PDU type.

7. The first network entity of claim 6, wherein in response to the received second request message comprising a data session establishment request PDU type, the method further comprises:generating a non access stratum, NAS, session management, SM, container to be transmitted to a session management function, SMF.

8. The first network entity of any one of claims 5 to 7, wherein the second response message comprises at least one ofa deregistration response PDU type;a data session establishment response PDU type; ora data session modification response PDU type.

9. The first network entity of any one of claims 1 to 8, wherein the at least one processor is further configured to cause the first network entity to:perform an authentication procedure with an authentication entity for successful establishment of the secure connection, wherein performing the authentication procedure comprises:receive, from the authentication entity, a UE subscription identifier, ID.

10. The first network entity of any one of claims 1 to 9, wherein the at least one processor is further configured to cause the first network entity to:transmit, to a unified data management, UDM, entity, a third request message for subscription data for registering the UE with the core network over the secure connection via the non-3GPP access network; andDocket No. SMM920250239-GR-NPreceive, from the UDM entity, a third response message comprising the subscription data.

11. The first network entity of claim 10, wherein the third request message comprises an indication of at least one of:a UE subscription identifier, ID;a request for the subscription data;the UE accessing a sixth generation core, 6GC, via the non-3GPP access network; ora location of the non-3GPP access network.

12. The first network entity of claim 10 or claim 11, wherein the subscription data comprises an indication of at least one of:a subscribed network slice;a subscribed data network name, DNN; ora subscribed service.

13. The first network entity of any one of claims 1 to 12: wherein the first request message comprises an indication of at least one of:a type of registration;a globally unique temporary identifier GUTI;a globally unique access and mobility management function identifier, GUAMI; a requested capability of the UE;a supported capability by the UE; ora request for a 3 GPP service over the non-3GPP access network.

14. A method performed or performable by a first network entity, the method comprising:receiving, via a non-3GPP access network, a first request message for registering a user equipment, UE, with a core network over a secure connection; andDocket No. SMM920250239-GR-NPtransmitting, via the non-3GPP access network, a first response message indicating successful registration of the UE with the core network, wherein the first request message and the first response message comprise a first protocol, and wherein the secure connection comprises a second protocol different from the first protocol.

15. A user equipment, UE, for wireless communication, comprising:at least one memory; andat least one processor coupled with the at least one memory and configured to cause the UE to:transmit, via a non-3GPP access network, a first request message for registering the UE with a core network over a secure connection; andreceive, via the non-3GPP access network, a first response message indicating successful registration of the UE with the core network, wherein the first request message and the first response message comprise a first protocol, and wherein the secure connection comprises a second protocol different from the first protocol.Docket No. SMM920250239-GR-NP