Access to a second network

Abstract

A base station receives a configuration message from a first network. The configuration message includes an indication that the first network supports onboarding of a second network. The configuration message includes an identifier of the second network. The base station sends, to a mobility management function of the first network, a configuration onboarding request for a wireless device to be configured to onboard to the second network.

Description

[0001] Cross-references to related applications

[0002] This application claims the benefit of U.S. Provisional Application 63 / 062,976, filed August 7, 2020, which is incorporated herein by reference in its entirety. Technical Field

[0003] This disclosure generally relates to access to a second network. Background Technology

[0004] In the prior art, a wireless device can execute a configuration access procedure, in which it uses a configuration access network to access a providing server. The providing server can provide credentials for accessing a second network (e.g., a target network). When using the configuration access procedure, the wireless device can access the configuration access network and use it to obtain credentials. After obtaining the credentials, the UE can deregister from the configuration access network and connect to the target network.

[0005] Existing technology allows wireless devices to access a second network via a first network. The wireless device can access the second network (e.g., an overlay network) via an interconnecting node (e.g., an N3IWF) of the second network, using the first network (e.g., an underlying network). During initial access and registration on the first network, AMF selection can be performed by the RAN node. If the RAN node selects an AMF that does not support the underlying network capabilities of SNPN, the wireless device may fail to establish a PDU session for an IPSec connection to the N3IWF, and the process of connecting to and accessing the overlay network or the second network (via the N3IWF) may fail. Summary of the Invention

[0006] To address the aforementioned problems, a first aspect of this disclosure provides a method for accessing a second network, the method comprising: The first access and mobility management function (AMF) of the first network receives a forwarded registration request from the radio access network (RAN) node. The registration request is used for the radio device to configure network access to the second network. If the radio device is in connected mode or the RAN node cannot select an appropriate AMF, the RAN node forwards the registration request. The first AMF sends a discovery request to the Network Storage Function (NRF) of the first network. The discovery request is used to discover the AMF that supports the configuration for network access of the wireless device. The discovery request includes a configuration for network access support indication. The first AMF receives a discovery response message from the NRF, the discovery response message including information on AMF candidates that support configuration for network entry.

[0007] A second aspect of this disclosure provides a network node, the network node comprising: One or more processors; and A memory for storing instructions that, when executed by the one or more processors, cause the network node to perform the method described in the first aspect above.

[0008] A third aspect of this disclosure provides a method for accessing a second network, the method comprising: The network repository function (NRF) of the first network receives a discovery request from the first access and mobility management function (AMF) of the first network. The discovery request is used to discover an AMF that supports configuration access for wireless devices to the second network. The discovery request includes a configuration access support indication. The NRF sends a discovery response message to the first AMF, the discovery response message including information on AMF candidates that support configuration for network entry.

[0009] A fourth aspect of this disclosure provides a network repository function, including: One or more processors; and A memory for storing instructions that, when executed by the one or more processors, cause the network storage function to perform the method described in the third aspect above.

[0010] A fifth aspect of this disclosure provides a non-transitory computer-readable medium including instructions that, when executed by one or more processors, cause the one or more processors to perform the method described in the first or third aspect above. Attached Figure Description

[0011] Examples of several embodiments of the various implementations of the invention are described herein with reference to the figures.

[0012] Figure 1 A diagram illustrating an example 5G system architecture according to an embodiment of this disclosure.

[0013] Figure 2 A diagram illustrating an example 5G system architecture according to an embodiment of this disclosure.

[0014] Figure 3 This is a system diagram of an example wireless device and network node in a 5G system according to an embodiment of the present disclosure.

[0015] Figure 4 A system diagram of an example wireless device according to an embodiment of this disclosure.

[0016] Figure 5A and Figure 5BTwo registration management status models in UE 100 and AMF 155 are described, representing aspects of the embodiments according to this disclosure.

[0017] Figure 6A and Figure 6B Two connection management state models in UE 100 and AMF 155 are described, representing aspects of the embodiments according to this disclosure.

[0018] Figure 7 A graph for classifying and labeling traffic according to an embodiment of this disclosure.

[0019] Figure 8 This is an exemplary call flow for a registration procedure according to an embodiment of the present disclosure.

[0020] Figure 9 This is an exemplary call flow for a registration procedure according to an embodiment of the present disclosure.

[0021] Figure 10 This is an exemplary call flow for a service request procedure according to an embodiment of the present disclosure.

[0022] Figure 11 This is an exemplary call flow for a service request procedure according to an embodiment of the present disclosure.

[0023] Figure 12 An exemplary call flow for establishing a PDU session according to an embodiment of the present disclosure.

[0024] Figure 13 An exemplary call flow for establishing a PDU session according to an embodiment of the present disclosure.

[0025] Figure 14 An example of an exemplary mobile communication network according to an embodiment of the present disclosure is shown.

[0026] Figure 15 Exemplary embodiments of this disclosure are shown.

[0027] Figure 16 Exemplary embodiments of this disclosure are shown.

[0028] Figure 17 Exemplary embodiments of this disclosure are shown.

[0029] Figure 18 Exemplary embodiments of this disclosure are shown.

[0030] Figure 19 Exemplary embodiments of this disclosure are shown.

[0031] Figure 20Exemplary embodiments of this disclosure are shown.

[0032] Figure 21 Exemplary embodiments of this disclosure are shown.

[0033] Figure 22 An exemplary flowchart of this disclosure is shown.

[0034] Figure 23 An exemplary flowchart of this disclosure is shown.

[0035] Figure 24 An exemplary flowchart of this disclosure is shown.

[0036] Figure 25 An exemplary flowchart of this disclosure is shown.

[0037] Figure 26 An exemplary flowchart of this disclosure is shown.

[0038] Figure 27 An exemplary flowchart of this disclosure is shown.

[0039] Figure 28 An example of the message in this disclosure is shown.

[0040] Figure 29 Exemplary embodiments of this disclosure are shown.

[0041] Figure 30 Exemplary embodiments of this disclosure are shown.

[0042] Figure 31 Exemplary embodiments of this disclosure are shown.

[0043] Figure 32 An exemplary flowchart of this disclosure is shown.

[0044] Figure 33 An exemplary flowchart of this disclosure is shown.

[0045] Figure 34 An exemplary flowchart of this disclosure is shown.

[0046] Figure 35 An exemplary flowchart of this disclosure is shown. Detailed Implementation

[0047] Exemplary embodiments of the present invention enable the implementation of enhanced features and functions in 5G systems. More specifically, embodiments based on technology positioning via user plane transmission (e.g., for 5G or future communication systems). Throughout this disclosure, UE, wireless device, vehicle terminal, and mobile device are interchangeable. Throughout this disclosure, base station, (radio)access network ((R)AN), next-generation radio access network (NG-RAN), new radio node B (gNB), and next-generation eNodeB (ng-eNB) are interchangeable. Throughout this disclosure, base station, radio access network (RAN), and eNodeB are interchangeable.

[0048] Throughout this disclosure, AMF, LMC, LMF, UDM, OAM, GMLC, LCS client, NEF, and AF are exemplary network functions that can be implemented as network elements on dedicated hardware and / or as... Figure 4 The network nodes shown are either implemented as software instances running on (dedicated) hardware and / or shared hardware, or as virtualization functions instantiated on a suitable platform.

[0049] The following abbreviations are used throughout this disclosure: 5G (5th generation mobile network) 5GC 5G Core Network 5GS 5G System 5G-AN5G Access Network 5QI 5G QoS Indicator ACK confirmation AF application functions A-GNSS Assisted GNSS AMBR Aggregation Maximum Bit Rate AMF access and mobility management functions AN access network ANDSP Access Network Discovery and Selection Strategy APN Access Point Name ARP allocation and reservation priority BD Billing Domain BPS pressure sensor CCNF Public Control Network Functions CDR Fee Data Records CHF paid features CIoT Cellular IoT CN Core Network CP control plane C-V2X cellular vehicle-to-everything (V2X) DAB Digital Audio Broadcasting DDN downlink data notification DDoS Distributed Denial of Service DL downlink DN Data Network DN-AAA Data Network Authentication Authorization and Accounting DNN data network name DTMB Digital Terrestrial Multimedia Broadcasting ECGIE-UTRAN Cell Global Identifier ECID Enhanced Cell Identification E-CSCF Emergency Call Session Control Function eNodeB Evolution Node B EPS Evolution Package System E-UTRAN Evolution Universal Terrestrial Radio Access Network FDD Frequency Division Duplex FQDN (Fully Qualified Domain Name) F-TEID fully compliant TEID GAD Geographic Region Description GMLC Gateway Mobile Positioning Center gNB Next Generation Node B gNB-CU-CPgNB Central Unit Control Plane GNSS Global Navigation Satellite System GPSI General Public Subscription Identifier GTPGPRS tunneling protocol GUTI Globally Unique Temporary Identifier GW gateway HGMLC Homepage GMLC HTTP Hypertext Transfer Protocol ID identifier IMEI (International Mobile Equipment Identity) IMEI DBIMEI database IMSIP Multimedia Subsystem IMSI International Mobile Subscriber ID IP Internet Protocol IP-CANIP connection access network Layer 2 (Data Link Layer) Layer 3 (Network Layer) LADN Local Area Network Data Network LAN (Local Area Network) LCS location service LI legitimate interception LMC Location Management Component LMF location management function LPP LTE positioning protocol LRF orientation search function MAC Media Access Control MEI mobile device identifier MIB Master Information Block MICO only initiates connections via mobile. MME Mobility Management Entity MO Mobile Origin MO-LR Mobile Origin Location Request MSISDN Mobile Subscriber ISDN MT movement termination MT-LR moving termination location request N3IWF Non-3GPP Interoperability Function NAI Network Access Identifier NAS Non-Access Layer NAT (Network Address Translation) NB-IoT Narrowband IoT NCGINR Community Global Identifier NEF Network Exposure Function NF Network Functions NGAP Next Generation Application Protocol ng-eNB next-generation eNB NG-RANNR Radio Access Network NI-LR Network-Induced Localization Request NR New Radio NRF network storage function NRPPa New Radio Positioning Protocol A NSI network slicing example NSSAI Network Slice Selection Auxiliary Information NSSF Network Slice Selection Function NWDAF network data analysis function OAM Operation Supervision and Maintenance OCS Online Billing System OFCS Offline Billing System OTDOA observation arrival time difference PCC Strategy and Fee Control PCF strategy control function PCRF policy and charging rules functions PDN Packet Data Network PDU Packet Data Unit PEI Permanent Device Identifier PGWPDN Gateway PLMN Public Land Mobile Network ProSe is based on proximity services. QFI QoS Stream Identifier QoS (Quality of Service) RM Registration Management RA Random Access RAN Radio Access Network RAT radio access technology RRC Radio Resource Control RM Registration Management S1-APS1 Application Protocol SBA Service-Based Architecture SCM Security Context Management SEA Safety Anchor Function SETSUPL Enable Terminal SGW Service Gateway SIB System Information Block SLPSUPL Location Platform SM Session Management SMF Session Management Function SMS / FSMS function S-NSSAI Single Network Slice Selection Auxiliary Information SS Synchronization Signal SSC Session and Service Continuity SUCI Service User Relevance ID SUPI subscriber permanent identifier SUPL Safety User Plane Position TA tracking area TAI tracking area identifier TBS Ground Beacon System TCP Transmission Control Protocol TEID tunnel endpoint identifier TMSI Temporary Mobile Subscriber Identifier TNAN Trusted Non-3GPP Access Network TNGF Trusted Non-3GPP Gateway TRP Transmit and Receive Points UCMFUE Radio Capability Management Function UDR Unified Data Storage UDM Unified Data Management UDP User Datagram Protocol UE User Equipment UL uplink UL CL uplink classifier UPF User Plane Functions V2X vehicle-to-everything (V2X) WLAN wireless local area network XML Extensible Markup Language Example Figure 1 and Figure 2 A 5G system including an access network and a 5G core network is depicted. An example 5G access network may include an access network connected to the 5G core network. The access network may include NG-RAN 105 and / or non-3GPP AN 165. An example 5G core network may connect to one or more 5G access networks, 5G-AN and / or NG-RAN. The 5G core network may include, as shown in the example... Figure 1 and examples Figure 2 The functional elements or network functions in the system, wherein the interface can be used for communication between functional elements and / or network elements.

[0050] In the example, a network function can be a processing function within a network, which may have functional behaviors and / or interfaces. Network functions can be implemented as network elements on dedicated hardware and / or such as... Figure 3 and Figure 4 The network nodes depicted are either implemented as software instances running on dedicated hardware and / or shared hardware, or as virtual functions instantiated on a suitable platform.

[0051] In the example, the Access and Mobility Management (AMF) 155 may include the following functions (some of the functions of AMF 155 may be supported in a single instance of AMF 155): termination of the RAN 105 CP interface (N2), termination of NAS (N1), NAS encryption and integrity protection, registration management, connection management, reachability management, mobility management, lawful interception (for AMF155 events and interfaces with the LI system), providing transport for session management, SM messages between UE 100 and SMF 160, transparent proxy for routing SM messages, access authentication, access authorization, providing transport for SMS messages between UE 100 and SMSF, security anchor function, SEA, interaction with AMFF 150 and UE 100, receiving intermediate keys established as a result of the UE 100 authentication process, receiving security context management (SCM) keys from the SEA for deriving access network-specific keys, etc.

[0052] In the example, AMF 155 can support non-3GPP access networks through the N2 interface with N3IWF 170, support NAS signaling with UE 100 through N3IWF 170, support authentication, mobility management, and separate security context states for UE 100 connected via non-3GPP access 165 or simultaneously via 3GPP access 105 and non-3GPP access 165, support effective coordination of RM contexts via 3GPP access 105 and non-3GPP access 165, support CM management context for UE 100 for connections via non-3GPP access, and so on.

[0053] In the example, an AMF 155 area may include one or more AMF 155 sets. An AMF 155 set may include some AMF 155s serving a given area and / or network slice. In the example, multiple AMF 155 sets may be each AMF 155 area and / or network slice. An application identifier may be an identifier that can be mapped to a specific application traffic detection rule. A configured NSSAI may be an NSSAI that can be provided in UE 100. For DNN, the DN 115 Access Identifier (DNAI) may be an identifier for user plane access to DN 115. Initial registration may be related to UE 100 registration in RM-DEREGISTERED (RM-Deregister) states 500 and 520. An N2AP UE 100 association may be a logical association between a 5G AN node and an AMF 155 based on UE 100. An N2AP UE-TNLA combination may be a combination between an N2AP UE 100 association and a TNL association for a specific transport network layer, for a given UE 100.

[0054] In the example, the session management function SMF 160 may include one or more of the following functions (one or more of the SMF 160 functions may be supported in a single instance of SMF 160): session management (e.g., session establishment, modification, and release, including tunnel maintenance between UPF 110 and AN 105 nodes), UE 100 IP address allocation and management (including optional authorization), selection and control of UP functions, configuring traffic redirection at UPF 110 to route traffic to the appropriate destination, terminating the interface for policy control functions, controlling policy enforcement and a portion of QoS, lawful interception (for SM events and interfaces with LI systems), terminating the SM portion of NAS messages, downlink data notification, initiating AN-specific SM information, sending it to (R)AN 105 via N2 through AMF155, determining the SSC mode of the session, roaming functions, handling local execution to apply QoS SLA (VPLMN), charge data collection and charge interface (VPLMN), lawful interception (in VPLMN, for SM events and interfaces with LI systems), and support for external DN. The interaction of DN 115 is used to transmit signaling for PDU session authorization / authentication by external DN 115, etc.

[0055] In the example, the User Plane Function UPF 110 may include one or more of the following functions (some of the UPF 110 functions may be supported in a single instance of UPF 110): anchor points for movement within / between RATs (if applicable), external PDU session points interconnected to DN115, packet routing and forwarding, packet inspection and user plane portion of policy rule enforcement, lawful interception (UP collection), traffic usage reporting, uplink classifier for routed traffic flows supporting data networks, branch points for multihomed PDU sessions, QoS processing in the user plane, uplink traffic authentication (SDF to QoS flow mapping), transport level packet marking in uplink and downlink, downlink packet buffering, downlink data notification triggering, etc.

[0056] In the example, UE 100 IP address management may include the allocation and release of UE 100 IP addresses and / or the updating of allocated IP addresses. UE 100 may set the requested PDU type during the PDU session establishment procedure based on its IP stack capabilities and / or configuration. In the example, SMF 160 may select the PDU type for the PDU session. In the example, if SMF 160 receives a request to set the PDU type to IP, SMF 160 may select the PDU type as IPv4 or IPv6 based on DNN configuration and / or operator policies. In the example, SMF 160 may provide a reason value to UE 100 to indicate whether other IP versions are supported on the DNN. In the example, if SMF 160 receives a request for the PDU type to be IPv4 or IPv6, and the requested IP version is supported by the DNN, SMF 160 may select the requested PDU type.

[0057] In an exemplary implementation, the 5GC element and UE 100 may support the following mechanism: During the PDU session establishment procedure, the SMF 160 may send an IP address to the UE 100 via SM NAS signaling. Once the PDU session can be established, IPv4 address allocation and / or IPv4 parameter configuration can be used via DHCPv4. If IPv6 is supported, IPv6 prefix allocation can be supported via stateless IPv6 autoconfiguration. In the example, the 5GC network element may support IPv6 parameter configuration via stateless DHCPv6.

[0058] 5GC can support the allocation of static IPv4 addresses and / or static IPv6 prefixes based on subscription information in UDM 140 and / or on configurations on a per subscriber, per DNN basis.

[0059] The User Plane Function (UPF 110) can handle the user plane path of PDU sessions. The UPF 110, which provides an interface to the data network, can support the function of PDU session anchoring.

[0060] In the example, the policy control function PCF 135 can support a unified policy framework to control network behavior, provide policy rules for control plane functions to enforce policy rules, implement a front-end for accessing subscription information related to policy decisions in the User Data Repository (UDR), and so on.

[0061] The Network Exposure Function (NEF 125) can provide a means to securely expose services and capabilities provided by 3GPP network functions, switch between information exchanged with AF 145 and information exchanged with internal network functions, receive information from other network functions, and so on.

[0062] In the example, the Network Repository feature NRF 130 can support service discovery functionality that can receive NF discovery requests from NF instances, provide NF instances with information about discovered NF instances (to be discovered), and maintain information about available NF instances and the services they support, etc.

[0063] In the example, NSSF 120 can select a set of network slice instances serving UE 100 and determine the allowed NSSAI. In the example, NSSF 120 can determine the set of AMF 155 to be used to serve UE 100, and / or determine the list of candidate AMF 155 based on configuration by querying NRF 130.

[0064] In the example, the data stored in the UDR may include at least user subscription data, including at least subscription identifiers, security credentials, access and mobility-related subscription data, session-related subscription data, policy data, and so on.

[0065] In the example, AUSF 150 supports authentication server functionality (AUSF 150).

[0066] In the example, application function AF 145 can interact with the 3GPP core network to provide services. In the example, based on operator deployment, application functions can be trusted by the operator to interact directly with relevant network functions. Application functions that the operator does not allow to directly access network functions can interact with relevant network functions using an external exposure framework (e.g., via NEF 125).

[0067] In the example, the control plane interface between (R)AN 105 and the 5G core can support connecting various types of ANs (e.g., 3GPP RAN 105, N3IWF 170 for untrusted access 165) to the 5GC via control plane protocols. In the example, the N2 AP protocol can be used for both 3GPP access 105 and non-3GPP access 165. In the example, the control plane interface between (R)AN 105 and the 5G core can support decoupling between AMF 155 and other functions (such as SMF 160) that may require control over services supported by the AN (e.g., control over UP resources in 105 for PDU sessions).

[0068] In the example, 5GC can provide policy information from PCF 135 to UE 100. In this example, the policy information may include: access network discovery and selection policy, UE 100 routing policy (URSP), SSC mode selection policy (SSCMSP), network slice selection policy (NSSP), DNN selection policy, non-seamless offloading policy, and so on.

[0069] In the example, such as Figure 5A and Figure 5B As described, the Registration Management (RM) can be used to register or deregister UE / User 100 in the network and establish user contexts in the network. Connection Management can be used to establish and release signaling connections between UE 100 and AMF 155.

[0070] In the example, UE 100 can register on the network to receive services that require registration. In the example, UE 100 can periodically update its registration on the network to maintain reachability (periodic registration update), or update it while on the move (e.g., mobile registration update), or update its capabilities or renegotiate protocol parameters.

[0071] In the example, as shown in the example Figure 8 and Figure 9 The initial registration procedure described may involve performing network access control functions (e.g., user authentication and access authorization based on subscription profiles in UDM 140). Example Figure 9 yes Figure 8 The initial registration procedure described herein continues. Due to the initial registration procedure, the identity of service AMF 155 can be registered in UDM 140.

[0072] In the example, the registration management RM program can be applied to both 3GPP Access 105 and non-3GPP Access 165.

[0073] Example Figure 5A The RM state of UE 100 as observed by UE 100 and AMF 155 can be depicted. In an exemplary implementation, two RM states reflecting the registration status of UE 100 in the selected PLMN can be employed in UE 100 and AMF 155: RM-DEREGISTERED 500 and RM-REGISTERED (RM-registered) 510. In the example, in RM-DEREGISTERED state 500, UE 100 may not be registered in the network. The UE 100 context in AMF 155 may not maintain valid location or routing information for UE 100, therefore UE 100 may not be reachable via AMF 155. In the example, the UE 100 context may be stored in both UE 100 and AMF 155. In the example, in RM-registered state 510, UE 100 can register on the network. In RM-REGISTERED state 510, UE 100 can receive services that may require registration on the network.

[0074] In an exemplary implementation, two RM states that reflect the registration status of UE 100 in the selected PLMN can be adopted for UE 100 in AMF 155: RM-DEREGISTERED 520 and RM-REGISTERED 530.

[0075] As shown in the example Figure 6A and Figure 6B As depicted, the connection management CM may include establishing and releasing a signaling connection between UE 100 and AMF 155 via the N1 interface. This signaling connection can be used to enable NAS signaling exchange between UE 100 and the core network. The signaling connection between UE 100 and AMF 155 may include both a signaling connection between UE 100 and (R)AN 105 (e.g., an RRC connection via 3GPP access) and an N2 connection between UE 100 and AMF 155.

[0076] As exemplary Figure 6A and Figure 6B As described, the NAS signaling connection between UE 100 and AMF 155 can employ two CM states: CM-IDLE (600, 620) and CM-CONNECTED (610, 630). UE 100 in CM-IDLE (600) state can be in RM-REGISTERED (510) state and may not have a NAS signaling connection established with AMF 155 via N1. UE 100 can perform cell selection, cell reselection, PLMN selection, etc. UE 100 in CM-CONNECTED (610) state can have a NAS signaling connection with AMF 155 via N1.

[0077] In an exemplary implementation, for UE 100 at AMF 155, two CM states can be used, namely CM-IDLE 620 and CM-CONNECTED 630.

[0078] In the example, the RRC inactivity state can be applied to NG-RAN (e.g., it can be applied to NR and E-UTRA connected to a 5G CN). Based on network configuration, AMF 155 can provide auxiliary information to NG RAN 105 to assist NG RAN 105 in determining whether UE 100 can be sent to the RRC inactivity state. When UE 100 is in CM-CONNECTED 610 in the RRC inactivity state, UE 100 can continue the RRC connection as a response to RAN 105 paging due to uplink data pending, mobile-initiated signaling procedures, etc., to notify the network that it has left the RAN 105 notification area, etc.

[0079] In the example, NAS signaling connection management may include establishing and releasing NAS signaling connections. The NAS signaling connection establishment function can be provided by UE 100 and AMF155 to establish a NAS signaling connection for UE 100 in CM-IDLE 600 state. The procedure for releasing the NAS signaling connection can be initiated by the 5G(R)AN 105 node or AMF 155.

[0080] In the example, UE 100's reachability management can detect whether UE 100 is reachable and can provide UE 100's location (e.g., access node) to the network to reach UE 100. Reachability management can be accomplished by paging UE 100 and UE 100 location tracking. UE 100 location tracking can include both UE 100 registration area tracking and UE 100 reachability tracking. During registration and registration update procedures, UE 100 and AMF 155 can negotiate UE 100 reachability characteristics in CM-IDLE 600, 620 states.

[0081] In the example, for CM-IDLE 600 and 620 states, two UE100 reachability categories can be negotiated between UE 100 and AMF 155: 1) When UE 100 is in CM-IDLE 600 mode, UE 100 reachability allows the mobile device to terminate data. 2) Mobile-Initiated Connection Only (MICO) mode. 5GC can support PDU connection services, which provide PDU exchange between UE 100 and the data network identified by the DNN. PDU connection services can be supported via PDU sessions established at the request of UE 100.

[0082] In the example, a PDU session can support one or more PDU session types. A PDU session can be established, modified (e.g., based on a request from UE 100), and / or released (e.g., based on a request from UE 100 and 5GC) using NAS SM signaling exchanged via N1 between UE 100 and SMF160. Based on a request from the application server (AS), 5GC can trigger a specific application in UE 100. Upon receiving the trigger, UE 100 can send it to the identified application in UE 100. The identified application in UE 100 can establish a PDU session for a specific DNN.

[0083] In the example, the 5G QoS model can support, as shown in the example. Figure 7The framework described herein is based on QoS flows. The 5G QoS model can simultaneously support QoS flows that require guaranteed flow bit rates and QoS flows that do not require guaranteed flow bit rates. In the example, the 5G QoS model can support reflection QoS. The QoS model may include flow mapping or packet marking at UPF 110 (CN_UP) 110, AN 105, and / or UE 100. In the example, packets can arrive at and / or be assigned to the application / service layer 730 of UE 100, UPF 110 (CN_UP) 110, and / or AF 145.

[0084] In the example, a QoS flow can be a granularity of QoS differentiation within a PDU session. QoS flow IDs and QFIs can be used to identify QoS flows in a 5G system. In the example, user plane traffic with the same QFI within a PDU session can receive the same traffic forwarding processing. The QFI can be carried in the encapsulation header on N3 and / or N9 (e.g., without changing the end-to-end packet header). In the example, the QFI can be applied to PDUs with different types of payloads. The QFI can be unique within a PDU session.

[0085] In the example, the QoS parameters of the QoS flow can be provided as a QoS profile to (R)AN 105 via N2 during PDU session establishment, QoS flow establishment, or each time the user plane is activated using NG-RAN. In the example, each PDU session may require default QoS rules. SMF 160 can assign QFIs to the QoS flow and can derive QoS parameters from information provided by PCF 135. In the example, SMF 160 can provide the (R)AN 105 with the QFIs and a QoS profile containing the QoS parameters of the QoS flow.

[0086] In the example, a 5G QoS flow can be the granularity of QoS forwarding processing in a 5G system. Traffic mapped to the same 5G QoS flow can receive the same forwarding processing (e.g., scheduling policies, queue management policies, rate setting policies, RLC configuration, etc.). In the example, providing different QoS forwarding processing may require separate 5G QoS flows.

[0087] In the example, the 5G QoS indicator can be a scalar that can be used as a reference for specific QoS forwarding behaviors (e.g., packet loss rate, packet delay budget) to be provided to the 5G QoS flow. In the example, the 5G QoS indicator can be implemented in the access network by 5QI reference node-specific parameters (e.g., scheduling weights, admission thresholds, queue management thresholds, link layer protocol configurations, etc.) that control QoS forwarding processing.

[0088] In the example, 5GC supports edge computing and enables operators and third-party services to be hosted close to the UE's attached access point. The 5G core network can select a UPF 110 close to UE 100 and can perform traffic redirection from UPF 110 to the local data network via the N6 interface. In the example, selection and traffic redirection can be based on UE 100's subscription data, UE 100's location, information from application function AF 145, policies, other relevant traffic rules, etc. In the example, the 5G core network can expose network information and capabilities to edge computing application functions. Edge computing functionality support may include: local routing, where the 5G core network can select UPF 110 to route user traffic to the local data network; traffic redirection, where the 5G core network can select traffic to be routed to applications in the local data network; session and service continuity for UE100 and application mobility; user plane selection and reselection, for example, based on input from application functions; network capability openness, where the 5G core network and application functions can provide information to each other via NEf 125; QoS and charging, where PCF 135 can provide QoS control and charging rules for traffic routed to the local data network; support for LAN data networks, where the 5G core network can provide support for connectivity to LADN in specific areas where applications are deployed; and so on.

[0089] An example 5G system could be a 3GPP system including a 5G access network 105, a 5G core network, and a UE 100. The permitted NSSAI could be an NSSAI provided by the serving PLMN during, for example, the registration process, indicating the network-permitted NSSAI for UE 100 within the serving PLMN of the currently registered area.

[0090] In the example, the PDU connectivity service can provide PDU exchange between UE 100 and the data network. A PDU session can be an association between UE 100 and data network DN 115 that provides the PDU connectivity service. The association type can be IP, Ethernet, and / or unstructured.

[0091] The user plane connection to the data network established via the network slice instance may include the following: executing the RM procedure to select the AMF 155 that supports the required network slice, and the number of one or more PDU sessions established to the required data network via the network slice instance.

[0092] In the example, the network slice set of UE 100 can be changed at any time when UE 100 can register on the network, and can be initiated by the network or UE 100.

[0093] In the example, periodic registration updates could mean that UE 100 re-registers when the periodic registration timer expires. The requested NSSAI could be an NSSAI that UE 100 can provide to the network.

[0094] In the example, a service-based interface can represent a set of services that can be provided / exposed by a given NF.

[0095] In the example, service continuity can refer to an uninterrupted user experience of the service, including situations where the IP address and / or anchor point can change. In the example, session continuity can refer to the continuity of a PDU session. For IP-type PDU sessions, session continuity can imply that the IP address is retained throughout the lifetime of the PDU session. The uplink classifier can be a UPF 110 function, designed to redirect uplink traffic to the data network DN 115 based on filter rules provided by SMF 160.

[0096] In the example, the 5G system architecture can support data connectivity and services, enabling deployments using technologies such as network function virtualization and / or software-defined networking. The 5G system architecture can leverage service-based interactions between identified control plane (CP) network functions. In the 5G system architecture, the separation of user plane (UP) functions from control plane functions can be considered. If needed, the 5G system can enable network functions to interact directly with other NFs.

[0097] In this example, a 5G system can reduce the dependency between the access network (AN) and the core network (CN). The architecture could include an aggregated access-agnostic core network with a common AN-CN interface, which could integrate different 3GPP and non-3GPP access types.

[0098] In the example, the 5G system can support a unified authentication framework, stateless network nodes (NFs) with separate compute and storage resources, open capabilities, and simultaneous access to local and centralized services. To support low-latency services and access to local data networks, the UP (Upload and Activation) function can be deployed close to the access network.

[0099] In the example, the 5G system can support roaming within the visited PLMN using home routing traffic and / or local breakout traffic. The example 5G architecture can be service-based, and the interaction between network functions can be represented in two ways: (1) as a service-based representation (in the example...) Figure 1(2) As a reference point representation, it shows the interaction between NF services in the network functions described by the point-to-point reference point (e.g., N11) between any two network functions.

[0100] In the example, network slices may include core network control plane and user plane network functions, 5G radio access networks, N3IWF functions for non-3GPP access networks, and so on. Network slices can vary depending on the supported features and network function implementations. Operators can deploy multiple network slice instances that deliver the same features but are used for different groups of UEs, for example, when they deliver different committed services and / or because they can be dedicated to a customer. The NSSF 120 can store mapping information between slice instance IDs and NF IDs (or NF addresses).

[0101] In the example, UE 100 can be served simultaneously by one or more network slice instances via 5G-AN. In the example, UE 100 can be served by k network slices at a time (e.g., k=8, 16, etc.). Logically, the AMF 155 instance serving UE 100 can belong to the network slice instance serving UE 100.

[0102] In the example, each PLMN can have a PDU session belonging to a specific network slice instance. Different network slice instances may not share PDU sessions. Different slices can have slice-specific PDU sessions using the same DNN.

[0103] S-NSSAI (Single Network Slice Selection Auxiliary Information) identifies network slices. S-NSSAI may include: Slice / Service Type (SST), which may refer to the expected network slice behavior in terms of characteristics and services; and / or Slice Differentiator (SD). The Slice Differentiator may be optional information that supplements the Slice / Service Type to allow further differentiation to select a network slice instance from multiple potential network slice instances that conform to the indicated Slice / Service Type. In the example, the same network slice instance with different S-NSSAIs can be selected. The CN portion of the network slice instance serving UE 100 can be selected by the CN.

[0104] In the example, subscription data may include the S-NSSAI of the network slice subscribed by UE 100. One or more S-NSSAIs may be marked as the default S-NSSAI. In the example, k S-NSSAIs may be marked as the default S-NSSAI (e.g., k=8, 16, etc.). In the example, UE 100 may subscribe to more than 8 S-NSSAIs.

[0105] In the example, UE 100 can be configured by an HPLMN, each PLMN being configured with an NSSAI. After successfully completing the UE's registration procedure, UE 100 can obtain the allowed NSSAI for this PLMN from AMF 155, which may include one or more S-NSSAIs.

[0106] In the example, the allowed NSSAI of the PLMN can take precedence over the configured NSSAI. UE 100 can use the S-NSSAI corresponding to the network slice used in the serving PLMN for subsequent network slice selection procedures within the allowed NSSAI.

[0107] In the example, establishing a user plane connection to the data network via a network slice instance may include: executing the RM procedure to select an AMF 155 that supports the required network slice, the number of one or more PDU sessions established to the required data network via the network slice instance, and so on.

[0108] In the example, when UE 100 registers with the PLMN, if UE 100 has a configured NSSAI or an allowed NSSAI for the PLMN, UE 100 can provide the requested NSSAI (which includes the S-NSSAI corresponding to the slice UE 100 is attempting to register for), a temporary user ID (if a temporary user ID is assigned to the UE), etc., to the network and NAS layers in the RRC. The requested NSSAI can be a configured NSSAI, an allowed NSSAI, etc.

[0109] In the example, when UE 100 registers with the PLMN, if UE 100 does not have a configured NSSAI or an allowed NSSAI for the PLMN, then RAN 105 can route NAS signaling from UE 100 to the default AMF 155 / or route NAS signaling from the default AMF to the UE.

[0110] In the example, based on local policies, subscription changes, and / or UE 100 mobility, the network can change the set of permitted network slices to which UE 100 is registered. In the example, the network can perform the change during the registration process or use an RM procedure (which can trigger the registration process) to notify UE 100 of the change in supported network slices. The network can provide UE 100 with the new list of allowed NSSAI and tracking areas.

[0111] In the example, during the registration process in the PLMN, if the network determines that UE 100 should be served by a different AMF 155 based on network slicing, the AMF 155 that first receives the registration request can redirect the registration request to another AMF 155 via RAN 105 or via direct signaling between the initial AMF 155 and the target AMF 155.

[0112] In the example, the network operator can provide a network slice selection policy (NSSP) to UE 100. The NSSP may include one or more NSSP rules.

[0113] In the example, if UE 100 has a number of PDU sessions established corresponding to a specific S-NSSAI, UE 100 can route user data for an application within a single PDU session unless other conditions in UE 100 prevent the use of a PDU session. If the application provides a Data Navigate (DNN), UE 100 can consider the DNN to determine which PDU session to use. In the example, if UE 100 does not have a PDU session established with a specific S-NSSAI, UE 100 can request a new PDU session corresponding to the S-NSSAI and with a DNN that can be provided by the application. In the example, in order for RAN 105 to select appropriate resources to support network slices in RAN 105, RAN 105 can know the network slice used by UE 100.

[0114] In the example, when UE 100 triggers the establishment of a PDU session, AMF 155 can select SMF 160 from the network slice instance based on S-NSSAI, DNN, and / or other information (e.g., UE 100 subscriptions and local operator policies). The selected SMF160 can then establish a PDU session based on S-NSSAI and DNN.

[0115] In the example, to support network control privacy of slice information of slices accessible to UE 100, UE 100 may exclude NSSAI in NAS signaling when UE 100 is aware of or configured to allow privacy considerations to apply to NSSAI, unless UE 100 has a NAS security context and UE 100 may exclude NSSAI in unprotected RRC signaling.

[0116] In the example, for roaming scenarios, network slice-specific network functions (NFs) can be selected in both the VPLMN and HPLMN based on the S-NSSAI provided by the UE 100 during PDU connection establishment. If a standardized S-NSSAI is used, each PLMN can select slice-specific NF instances based on the provided S-NSSAI. In the example, the VPLMN can map the HPLMN's S-NSSAI to the VPLMN's S-NSSAI based on the roaming protocol (e.g., including the default S-NSSAI mapped to the VPLMN). In the example, slice-specific NF instances can be selected in the VPLMN based on the VPLMN's S-NSSAI. In the example, any slice-specific NF instance in the HPLMN can be selected based on the HPLMN's S-NSSAI.

[0117] As shown in the example Figure 8 and Figure 9 As described, the UE 100 can perform a registration procedure to obtain authorization for receiving services, to enable mobile tracking, to achieve accessibility, and so on.

[0118] In the example, UE 100 can send AN message 805 to (R)AN 105 (including AN parameters, RM-NAS registration request (registration type, SUCI or SUPI or 5G-GUTI, last accessed TAI (if available), security parameters, requested NSSAI, mapping of the requested NSSAI, UE 100 5GC capability, PDU session status, PDU session to be reactivated, follow-up requests, MICO mode preference, etc.) etc.). In the example, in the case of NG-RAN, parameters may include, for example, SUCI or SUPI or 5G-GUTI, the selected PLMN ID, and the requested NSSAI. In the example, parameters may include the establishment reason. The establishment reason can provide the reason for requesting to establish an RRC connection. In the example, the registration type can indicate whether UE 100 is to perform initial registration (i.e., UE 100 is in RM-DEREGISTERED state), mobile registration update (e.g., UE 100 is in RM-REGISTERED and the registration process is initiated due to mobility), periodic registration update (e.g., UE 100 is in RM-REGISTERED and the registration process can be initiated due to the expiration of the periodic registration update timer), or emergency registration (e.g., UE 100 is in a limited service state). In the example, if UE 100 performs initial registration to the PLMN (i.e., UE 100 is in RM-DEREGISTERED state) and UE 100 does not yet have a 5G-GUTI, UE 100 can include its SUCI or SUPI in the registration request. SUCI can be included if the home network has provided a public key to protect the SUPI in the UE. If UE 100 receives a UE 100 configuration update command indicating that UE 100 needs to re-register and that the 5G-GUTI is invalid, UE 100 can perform initial registration and may include a SUPI in the registration request message. For emergency registration, if UE 100 does not have a valid 5G-GUTI available, a SUPI may be included; when UE 100 has neither a SUPI nor a valid 5G-GUTI, a PEI may be included. In other cases, a 5G-GUTI may be included, and it may indicate the last serving AMF 155. If UE 100 has already registered via non-3GPP access in a new PLMN different from the 3GPP access (e.g., not the registered PLMN or an equivalent PLMN of the registered PLMN), UE 100 may not provide the 5G-GUTI assigned by AMF 155 via 3GPP access during the registration procedure via non-3GPP access.If UE 100 has already registered in a PLMN (e.g., a registered PLMN) that is different from a non-3GPP access PLMN (e.g., not a registered PLMN or an equivalent PLMN of a registered PLMN), then during the registration procedure via 3GPP access, UE 100 may not provide the 5G-GUTI assigned by AMF 155 via non-3GPP access. UE 100 may provide UE usage settings based on its configuration. In the case of initial registration or mobile registration update, UE 100 may include a mapping of requested NSSAIs, which may be a mapping of each S-NSSAI in the requested NSSAIs of the HPLMN to the S-NSSAIs in the configured NSSAIs, to ensure that the network can verify whether the S-NSSAIs in the requested NSSAIs are allowed based on the subscribed S-NSSAIs. If available, the previously accessed TAI may be included to help AMF 155 generate the UE's registration area. In the example, security parameters may be used for authentication and integrity protection. The requested NSSAIs may instruct network slice selection auxiliary information. The PDU session status can indicate previously established PDU sessions in the UE. When UE 100 is connected to two AMF 155s belonging to different PLMNs via 3GPP access and non-3GPP access, the PDU session status can indicate the PDU sessions already established in the UE for the current PLMN. It may include PDU sessions awaiting reactivation to indicate that UE 100 may intend to activate a PDU session for its UP connection. When UE 100 is outside the availability area of ​​the LADN, the PDU session corresponding to the LADN may not be included in the PDU sessions awaiting reactivation. When UE 100 may have pending uplink signaling, and UE 100 may not include PDU sessions awaiting reactivation, it may include follow-up requests, or the registration type may indicate that UE 100 may need to perform emergency registration.

[0119] In the example, if including SUPI or 5G-GUTI does not indicate a valid AMF 155, then (R)AN 105 may select AMF 155 808 based on (R)AT and the requested NSSAI (if available). If UE 100 is in CM-CONNECTED state, then (R)AN 105 may forward the registration request message to AMF 155 based on the UE's N2 connection. If (R)AN 105 can choose not to select an appropriate AMF 155, then it may forward the registration request to an AMF 155 that has been configured in (R)AN 105 to perform AMF 155 selection 808.

[0120] In the example, (R)AN 105 can send N2 message 810 to the new AMF 155 (including: N2 parameters, RM-NAS registration request (registration type, SUPI or 5G-GUTI, last accessed TAI (if available), security parameters, requested NSSAI, mapping of the requested NSSAI, UE 100 5GC capability, PDU session status, PDU session to be reactivated, follow-up requests, and MICO mode preferences), etc.). In the example, when using NG-RAN, the N2 parameters may include the selected PLMN ID, location information, cell identity, and RAT type related to the cell where UE 100 is located. In the example, when using NG-RAN, the N2 parameters may include the establishment reason.

[0121] In the example, the new AMF 155 can send Namf_Communication_UEContextTransfer (Full Registration Request) 815 to the old AMF 155. In the example, if the UE's 5G-GUTI is included in the registration request and the serving AMF 155 has changed since the last registration procedure, the new AMF 155 can invoke the Namf_Communication_UEContextTransfer service operation 815 (including the integrity-protected full registration request IE) on the old AMF 155 to request the UE's SUPI and MM context. The old AMF 155 can use the integrity-protected full registration request IE to verify that the context transfer service operation call corresponds to the requesting UE 100. In the example, the old AMF 155 can transfer event subscription information for the UE for each NF consumer to the new AMF 155. In the example, if UE 100 identifies itself with a PEI, the SUPI request can be skipped.

[0122] In the example, the old AMF 155 can send a Namf_Communication_UEContextTransfer response 815 (SUPI, MM context, SMF 160 information, PCF ID) to the new AMF 155. In the example, the old AMF 155 can respond to the Namf_Communication_UEContextTransfer call with the new AMF 155 including the UE's SUPI and MM context. In the example, if the old AMF 155 maintains information about the established PDU session, it can include SMF 160 information, including S-NSSAI, SMF 160 identity, and PDU session ID. In the example, if the old AMF 155 maintains information about the active NGAP UE-TNLA to the N3IWF, it can include information about the NGAP UE-TNLA binding.

[0123] In the example, if the SUCI is not provided by UE 100 or retrieved from the old AMF 155, the identity request procedure 820 can be initiated by the AMF 155 sending an identity request message to the UE 100 that requests the SUCI.

[0124] In the example, UE 100 can respond with an identity response message 820 that includes the SUCI. UE 100 can derive the SUCI using the public key of the provided HPLMN.

[0125] In the example, AMF 155 may decide to initiate UE 100 authentication 825 by calling AUSF 150. AMF 155 may select AUSF 150 based on SUPI or SUCI. In the example, if AMF 155 is configured to support emergency registration for unauthenticated SUPI and emergency registration of the registration type indicated by UE 100, AMF 155 may skip authentication and security settings, or AMF 155 may accept that authentication may fail and continue the registration procedure.

[0126] In the example, authentication 830 can be performed by the Nudm_UEAuthenticate_Get operation. AUSF 150 can discover UDM 140. If AMF 155 provides SUCI to AUSF 150, AUSF 150 can return SUPI to AMF 155 after successful authentication. In the example, if network slicing is used, AMF 155 can decide whether to reroute the registration request if the initial AMF 155 references AMF 155. In the example, AMF 155 can initiate NAS security functions. In the example, upon completing NAS security function settings, AMF 155 can initiate the NGAP procedure so that 5G-AN can use it to protect procedures with the UE. In the example, 5G-AN can store a security context and can acknowledge it to AMF 155. 5G-AN can use the security context to protect messages exchanged with the UE.

[0127] In the example, the new AMF 155 can send a Namf_Communication_RegistrationCompleteNotify 835 to the old AMF 155. If the AMF 155 has changed, the new AMF 155 can notify the old AMF 155 that UE100 can complete its registration in the new AMF 155 by calling the Namf_Communication_RegistrationCompleteNotify service operation. If the authentication / security procedure fails, registration can be refused, and the new AMF 155 can call the Namf_Communication_RegistrationCompleteNotify service operation, with the refusal indication reason code directed to the old AMF 155. The old AMF 155 can continue as if it never received the UE 100 context transport service operation. If one or more of the S-NSSAIs used in the old registration area cannot be served in the target registration area, the new AMF 155 can determine which PDU sessions may not be supported in the new registration area. The new AMF 155 can call the Namf_Communication_RegistrationCompleteNotify service operation to the old AMF 155, including the rejected PDU session ID and the reason for rejection (e.g., S-NSSAI becomes unavailable). The new AMF 155 can modify the PDU session state accordingly. The old AMF 155 can notify the corresponding SMF 160 to release the UE's SM context locally by calling the Nsmf_PDUSession_ReleaseSMContext service operation.

[0128] In the example, the new AMF 155 can send an Identity Request / Response 840 (e.g., PEI) to UE 100. If the PEI is not provided by UE 100 or retrieved from the old AMF 155, the Identity Request procedure can be initiated by sending an Identity Request message to UE 100 via AMF 155 to retrieve the PEI. Unless UE 100 performs emergency registration, the PEI may be transmitted encrypted and may not be authenticated. For emergency registration, UE 100 may have already included the PEI in the registration request.

[0129] In the example, the new AMF 155 can initiate an ME identity check 845 by calling the N5g-eir_EquipmentIdentityCheck_Get service operation 845.

[0130] In the example, based on SUPI, the new AMF 155 can select 905 UDM 140. UDM 140 can select a UDR instance. In the example, AMF 155 can select UDM 140.

[0131] In the example, if AMF 155 has changed since the last registration procedure, or if UE 100 provides a SUPI that may not reference a valid context in AMF 155, or if UE 100 is registered to the same AMF 155 but has already registered to a non-3GPP access (e.g., UE 100 registered via a non-3GPP access and can initiate a registration procedure to add 3GPP access), the new AMF 155 can register with UDM 140 using Nudm_UECM_Registration 910 and can subscribe to be notified by UDM 140 when AMF 155 registration can be cancelled. UDM 140 can store the AMF 155 identifier associated with the access type and may not delete the AMF 155 identifier associated with another access type. UDM 140 can store information provided by Nudr_UDM_Update during registration in the UDR. In the example, AMF 155 can retrieve access and mobile subscription data and SMF 160 select subscription data using Nudm_SDM_Get 915. UDM 140 can retrieve this information (access and mobile subscription data) from the UDR via Nudr_UDM_Query. After receiving a successful response, AMF 155 can subscribe to be notified when the requested data can be modified using Nudm_SDM_Subscribe 920. UDM 140 can subscribe to the UDR via Nudr_UDM_Subscribe. If the GPSI is available in the UE 100 subscription data, it can be provided from UDM 140 to AMF 155 in the subscription data. In the example, the new AMF 155 can provide the access type it serves for UE 100 to UDM 140, and this access type can be set to 3GPP access. UDM 140 can store the associated access type in the UDR along with the serving AMF 155 via Nudr_UDM_Update. The new AMF 155 can create an MM context for UE100 after obtaining mobile subscription data from UDM 140. In the example, when UDM 140 stores the associated access type along with the serving AMF 155, UDM 140 can initiate Nudm_UECM_DeregistrationNotification921 to the old AMF 155 corresponding to the 3GPP access. The old AMF 155 can then remove the UE's MM context. If the reason for service NF deletion indicated by UDM 140 is initial registration, the old AMF 155 can call the Namf_EventExposure_Notify service operation to all associated SMFs 160 of UE100 to notify UE100 to deregister from the old AMF 155. SMF 160 can release the PDU session upon receiving this notification.In the example, the old AMF 155 can use Nudm_SDM_unsubscribe 922 to unsubscribe from UDM 140 for subscription data.

[0132] In the example, if AMF 155 decides to initiate PCF 135 communication, for example, if AMF 155 has not yet obtained the access and mobility policy of UE 100, or if the access and mobility policy in AMF 155 is no longer valid, AMF 155 can choose 925PCF 135. If the new AMF 155 receives a PCF ID from the old AMF 155 and successfully contacts the PCF135 identified by the PCF ID, then AMF 155 can choose the (V-)PCF identified by the PCF ID. If the PCF 135 identified by the PCF ID may not be used (e.g., there is no response from PCF 135), or if no PCF ID is received from the old AMF 155, then AMF 155 can choose 925PCF 135.

[0133] In the example, the new AMF 155 can perform policy association establishment 930 during the registration procedure. If the new AMF 155 contacts the PCF 135 identified by the (V-)PCF ID received during movement between AMFs 155, the new AMF 155 can include the PCF-ID in the Npcf_AMPolicyControl Get operation. If the AMF 155 notifies the PCF 135 of movement restrictions (e.g., UE 100 orientation) for adjustment, or if the PCF 135 updates its own movement restrictions due to certain conditions (e.g., application in use, time and date), the PCF 135 can provide the updated movement restrictions to the AMF 155.

[0134] In the example, PCF 135 can invoke Namf_EventExposure_Subscribe service operation 935 for UE 100 event subscription.

[0135] In the example, AMF 155 can send Nsmf_PDUSession_UpdateSMContext 936 to SMF 160. In the example, if the PDU session to be reactivated is included in the registration request, AMF 155 can invoke Nsmf_PDUSession_UpdateSMContext. AMF 155 can send the Nsmf_PDUSession_UpdateSMContext request to the SMF 160 associated with the PDU session to activate the user plane connection of the PDU session. SMF 160 can decide to trigger, for example, intermediate UPF 110 insertion, removal, or PSA modification. In the case of performing intermediate UPF 110 insertion, removal, or relocation for a PDU session not included in the PDU session to be reactivated, this procedure can be executed without N11 and N2 interaction to update the N3 user plane between (R)AN 105 and 5GC. AMF 155 can invoke the Nsmf_PDUSession_ReleaseSMContext service operation to SMF 160 when any PDU session state indicates that it has been released at UE100. AMF 155 can invoke the Nsmf_PDUSession_ReleaseSMContext service operation to SMF 160 to release any network resources associated with the PDU session.

[0136] In the example, the new AMF 155 can send an N2 AMF 155 Mobility Request 940 to the N3IWF. If the AMF 155 has changed, the new AMF 155 can create an NGAP UE 100 association for the N3IWF connected to UE 100. In the example, the N3IWF can respond to the new AMF 155 with an N2 AMF 155 Mobility Response 940.

[0137] In the example, the new AMF 155 can send a Registration Acceptance 955 to UE 100 (including: 5G-GUTI, registration area, mobility restrictions, PDU session state, allowed NSSAI, [mapping of allowed NSSAI], periodic registration update timer, LADN information and accepted MICO mode, indication of IMS voice support via PS session, emergency service support indicator, etc.). In the example, AMF 155 can send a Registration Acceptance message to UE 100 indicating that the registration request has been accepted. If AMF 155 has assigned a new 5G-GUTI, it can include the 5G-GUTI. If AMF 155 has assigned a new registration area, it can send the registration area to UE 100 via the Registration Acceptance message 955. If the registration acceptance message does not include the registration area, UE 100 may consider the old registration area valid. In the example, mobility restrictions can be included if they apply to UE 100 and the registration type may not be emergency registration. AMF 155 can indicate the established PDU session to UE 100 in the PDU session state. UE 100 can locally remove any internal resources associated with a PDU session not marked as established in the received PDU session state. In the example, when UE 100 is connected to two AMF 155s belonging to different PLMNs via 3GPP access and non-3GPP access, UE 100 can locally remove any internal resources associated with the current PLMN's PDU session that are not marked as established in the received PDU session state. If the PDU session state information is in the registration request, AMF 155 can indicate the PDU session state to the UE. The mapping of allowed NSSAIs can be a mapping of each S-NSSAI in the allowed NSSAIs of the HPLMN to an S-NSSAI in the configured NSSAIs. AMF 155 can include LADN information of the LADN in the registration acceptance message 955, which is available in the registration area determined by AMF 155 for the UE. If UE 100 includes MICO mode in its request, AMF 155 can respond to whether MICO mode can be used. AMF 155 can set an indication to support IMS voice via PS session. In the example, to set the indication to support IMS voice via PS session, AMF 155 can execute a UE / RAN radio information and compatibility request procedure to check the compatibility of UE 100 and RAN radio capabilities related to IMS voice via PS. In the example, an emergency service support indicator can notify UE 100 to support emergency services; for example, UE 100 can request emergency services via a PDU session. In the example, the handover restriction list and UE-AMBR can be provided to the NG-RAN by AMF 155.

[0138] In the example, UE 100 can send a registration complete 960 message to the new AMF 155. In the example, UE 100 can send the registration complete message 960 to AMF 155 to confirm that a new 5G-GUTI can be assigned. In the example, when information about the PDU session to be reactivated is not included in the registration request, AMF 155 can release the signaling connection with UE 100. In the example, when a subsequent request is included in the registration request, AMF 155 may not release the signaling connection after the registration procedure is completed. In the example, if AMF 155 realizes that some signaling is pending in AMF 155 or between UE 100 and 5GC, AMF 155 may not release the signaling connection after the registration procedure is completed.

[0139] As exemplary Figure 10 and Figure 11 As described, a service request procedure (e.g., a service request procedure triggered by UE 100) can be used by UE 100 in CM-IDLE state to request the establishment of a secure connection to AMF 155. Figure 11 It describes the service request procedure. Figure 10 The following diagram continues. The service request procedure can be used to activate user plane connectivity for established PDU sessions. The service request procedure can be triggered by UE 100 or 5GC, and can be used when UE 100 is in CM-IDLE and / or CM-CONNECTED, and can allow selective activation of user plane connectivity for some established PDU sessions.

[0140] In the example, UE 100, in CM IDLE state, can initiate a service request procedure to send uplink signaling messages, user data, etc., in response to a network paging request, and so on. In the example, after receiving the service request message, AMF 155 can perform authentication. In the example, after establishing a signaling connection to AMF 155, UE 100 or the network can send signaling messages such as PDU session establishment messages from UE 100 to SMF 160 via AMF 155.

[0141] In the example, for any service request, the AMF 155 can respond with a service accept message to synchronize the PDU session state between UE100 and the network. If the service request may not be accepted by the network, the AMF 155 can respond to UE100 with a service deny message. The service deny message may include an instruction or reason code requesting UE100 to perform a registration update procedure. In the example, for a service request arising from user data, if user plane connection activation may fail, the network can take further action. In the example... Figure 10 and Figure 11In this context, more than one UPF may be involved, such as the old UPF110-2 and PDU session anchor PSA UPF 110-3.

[0142] In the example, UE 100 can send an AN message to (R)AN 105, which includes AN parameters, mobility management, MM NAS service request 1005 (e.g., a list of PDU sessions to be activated, a list of allowed PDU sessions, security parameters, PDU session status, etc.), and so on. In the example, when UE 100 can reactivate a PDU session, UE 100 can provide a list of PDU sessions to be activated. When the service request can be a response to a paging or NAS notification, the list of allowed PDU sessions can be provided by UE 100, and can identify the access that can be transmitted to or the PDU sessions that can be associated with that access. In the example, for the NG-RAN case, parameters may include the selected PLMN ID and establishment reason. The establishment reason can provide the reason for requesting to establish an RRC connection. UE 100 can send a NAS service request message to RAN 105 for AMF 155 encapsulated in an RRC message.

[0143] In the example, if a service request can be triggered for user data, UE 100 can use a list of PDU sessions to be activated to identify the PDU sessions for which an UP connection will be activated in the NAS service request message. If a service request can be triggered by signaling, UE 100 may not be able to identify any PDU sessions. If this procedure can be triggered by a paging response, and / or UE 100 can simultaneously have user data to be transmitted, UE 100 can use a list of PDU sessions to be activated to identify the PDU sessions for which its UP connection can be activated in the MM NAS service request message.

[0144] In the example, if a service request for 3GPP access can be triggered in response to a paging indicating non-3GPP access, the NAS service request message can identify a list of PDU sessions associated with non-3GPP access that can be reactivated through 3GPP in the list of allowed PDU sessions. In the example, the PDU session status can indicate the PDU sessions available in UE 100. In the example, when UE 100 is outside the availability area of ​​the LADN, UE 100 may not trigger a service request procedure for the PDU session corresponding to the LADN. If a service request can be triggered for other reasons, UE 100 may not be able to identify such PDU sessions in the list of PDU sessions to be activated.

[0145] In the example, (R)AN 105 can send an N2 message 1010 (e.g., a service request) to AMF 155, including N2 parameters, MM NAS service requests, etc. If AMF 155 may not be able to process the service request, it can reject the N2 message. In the example, if NG-RAN is available, the N2 parameters may include 5G-GUTI, the selected PLMN ID, location information, RAT type, establishment reason, etc. In the example, the 5G-GUTI can be obtained in the RRC procedure, and (R)AN 105 can select AMF 155 based on the 5G-GUTI. In the example, the location information and RAT type may relate to the cell where UE 100 can camp. In the example, based on the PDU session state, AMF 155 can initiate a PDU session release procedure in the network for PDU sessions whose PDU session IDs can be indicated as unavailable by UE 100.

[0146] In the example, if the service request is not sent with integrity protection or integrity protection verification fails, the AMF155 can initiate NAS authentication / security procedure 1015.

[0147] In the example, if UE 100 triggers a service request to establish a signaling connection, then after the signaling connection is successfully established, UE 100 and the network can exchange NAS signaling.

[0148] In the example, AMF 155 can send a PDU session update context request 1020 to SMF 160, such as an Nsmf_PDUSession_UpdateSMContext request including PDU session ID, reason, UE 100 location information, access type, etc.

[0149] In the example, if UE 100 can identify the PDU session to be activated in the NAS service request message, the Nsmf_PDUSession_UpdateSMContext request can be invoked by AMF 155. In the example, the Nsmf_PDUSession_UpdateSMContext request can be triggered by SMF 160, where the PDU session identified by UE 100 can be associated with a different PDU session ID than the one that triggered the procedure. In the example, the Nsmf_PDUSession_UpdateSMContext request can be triggered by SMF 160, where the current UE 100 location can be outside the valid area of ​​the N2 information provided by SMF 160 during the network-triggered service request procedure. AMF 155 may choose not to send the N2 information provided by SMF 160 during the network-triggered service request procedure.

[0150] In the example, AMF 155 can identify the PDU session to be activated and can send an Nsmf_PDUSession_UpdateSMContext request to the SMF 160 associated with the PDU session, where the reason is set to indicate the establishment of user plane resources for the PDU session.

[0151] In the example, if the procedure can be triggered in response to a paging indicating non-3GPP access, and the list of allowed PDU sessions provided by UE 100 may not include PDU sessions that have been paged for UE 100, then AMF 155 may notify SMF 160 that the user plane of the PDU session may not be reactivated. The service request procedure may succeed without reactivating the user plane of any PDU session, and AMF 155 may notify UE 100.

[0152] In the example, if the PDU session ID corresponds to the LADN, and SMF 160 determines that UE 100 may be outside the availability zone of the LADN based on the UE 100 location reported from AMF 155, then SMF 160 may decide (based on local policy) to maintain the PDU session, may refuse to activate the user plane connection for the PDU session, and may notify AMF 155. In the example, if this procedure can be triggered by a network-triggered service request, then SMF 160 may notify the UPF 110 that initiated the data notification to abandon downlink data for the PDU session and / or not provide additional data notification messages. SMF 160 may respond to AMF 155 with an appropriate rejection reason and may stop user plane activation of the PDU session.

[0153] In the example, if the PDU session ID corresponds to an LADN, and the SMF 160 can determine that UE 100 may be outside the availability zone of the LADN based on the UE 100 location reported from the AMF 155, then the SMF 160 can decide (based on local policy) to release the PDU session. The SMF 160 can release the PDU session locally and can notify the AMF 155 that the PDU session can be released. The SMF 160 can respond to the AMF 155 with an appropriate rejection reason and can stop user plane activation of the PDU session.

[0154] In the example, if SMF 160 can accept UP activation for a PDU session, then based on the orientation information received from AMF 155, SMF 160 can check the UPF 110 selection criteria (e.g., slice isolation requirements, slice coexistence requirements, UPF 110 dynamic load, relative static capacity of UPF 110 among UPFs supporting the same DNN, UPF 110 orientation available at SMF 160, UE 100 orientation information, UPF 110 capabilities, and the features required for a specific UE 100 session). In the example, the appropriate UPF 110 can be determined by matching the features and characteristics required by UE 100, DNN, PDU session type (e.g., IPv4, IPv6, Ethernet type, or unstructured type), and (if applicable) static IP address / prefix, SSC mode selected for the PDU session, UE 100 subscription profile in UDM 140, including DNAI in the PCC rules, local operator policy, S-NSSAI, and other factors by the UE. The UE 100 may select (the access technology used, the logical topology of UPF 110, etc.) and may determine to perform one or more of the following: continue using the current UPF; if the UE 100 has moved out of the service area of ​​UPF 110 previously connected to (R)AN 105, while maintaining the UPF acting as the PDU session anchor, a new intermediate UPF 110 may be selected (or an intermediate UPF 110 may be added / removed); a PDU session re-establishment may be triggered to perform the relocation / reassignment of UPF 110 acting as the PDU session anchor, for example, if the UE 100 has moved out of the service area of ​​UPF 110 connected to RAN 105.

[0155] In the example, SMF 160 can send an N4 session establishment request 1030 to UPF 110 (e.g., a new intermediate UPF 110). In this example, if SMF 160 can choose the new UPF 110 to act as the intermediate UPF 110-2 for a PDU session, or if SMF 160 can choose to insert an intermediate UPF 110 for a PDU session that may not have an intermediate UPF 110-2, it can send an N4 session establishment request 1030 message to the new UPF 110, thereby providing packet inspection, data forwarding, enforcement, and reporting rules to be installed on the new intermediate UPF. The PDU session anchor addressing information (on N9) for this PDU session can be provided to the intermediate UPF 110-2.

[0156] In the example, if SMF 160 selects the new UPF 110 to replace the old (intermediate) UPF 110-2, SMF 160 may include a data forwarding indication. The data forwarding indication may instruct UPF 110 to reserve a second tunnel endpoint for buffered DL data from the old I-UPF.

[0157] In the example, the new UPF 110 (intermediate) can send an N4 session establishment response message 1030 to the SMF 160. If the UPF 110 can allocate CN tunnel information, it can provide the SMF 160 with the DL CN tunnel information and UL CN tunnel information (e.g., CN N3 tunnel information) of the UPF 110 used as the PDU session anchor. If a data forwarding indication is received, the new (intermediate) UPF 110, acting as the N3 endpoint, can send the DL CN tunnel information of the old (intermediate) UPF 110-2 to the SMF 160. The SMF 160 can start a timer to release resources in the old intermediate UPF 110-2.

[0158] In the example, if SMF 160 can select a new intermediate UPF 110 for the PDU session, or can remove the old I-UPF 110-2, then SMF 160 can send an N4 session modification request message 1035 to the PDU session anchor PSA UPF 110-3, thereby providing data forwarding instructions and DL tunnel information from the new intermediate UPF 110.

[0159] In the example, if a new intermediate UPF 110 can be added to the PDU session, then (PSA)UPF 110-3 can begin sending DL data to the new I-UPF 110, as indicated by the DL tunnel information.

[0160] In the example, if the service request can be triggered by the network, and the SMF 160 can remove the old I-UPF 110-2 without replacing it with a new I-UPF 110, then the SMF 160 can include a data forwarding indication in the request. The data forwarding indication can tell the (PSA) UPF 110-3 that a second tunnel endpoint can be reserved for buffered DL data from the old I-UPF 110-2. In this case, the PSA UPF 110-3 can begin buffering DL data that it may simultaneously receive from the N6 interface.

[0161] In the example, PSA UPF 110-3 (PSA) can send an N4 session modification response 1035 to SMF 160. In this example, if a data forwarding indication is received, PSA UPF 110-3 can become an N3 endpoint and can send CN DL tunnel information for the old (intermediate) UPF 110-2 to SMF 160. SMF 160 can start a timer to release any resources in the old intermediate UPF 110-2.

[0162] In the example, SMF 160 can send an N4 session modification request 1045 to the old UPF 110-2 (e.g., it may include the new UPF 110 address, the new UPF 110 DL tunnel ID, etc.). In the example, if the service request can be triggered by the network, and / or SMF 160 can remove the old (intermediate) UPF 110-2, then SMF 160 can send an N4 session modification request message to the old (intermediate) UPF 110-2 and can provide DL tunnel information for buffered DL data. If SMF 160 can allocate a new I-UPF 110, the DL tunnel information comes from the new (intermediate) UPF 110 that can be used as the N3 endpoint. If SMF 160 does not allocate a new I-UPF 110, the DL tunnel information can come from the new UPF 110 (PSA) 110-3 used as the N3 endpoint. SMF 160 can start a timer to monitor the forwarding tunnel. In the example, the old (intermediate) UPF 110-2 can send an N4 session modification response message to the SMF 160.

[0163] In the example, if I-UPF 110-2 can be relocated and a forwarding tunnel is established to the new I-UPF 110, then the old (intermediate) UPF 110-2 can forward its buffered data to the new (intermediate) UPF 110, which will serve as the N3 endpoint. In the example, if the old I-UPF 110-2 may be removed, and the new I-UPF 110 may not be assigned to a PDU session, and a forwarding tunnel may be established to UPF 110(PSA)110-3, then the old (intermediate) UPF 110-2 can forward its buffered data to UPF 110(PSA)110-3, which will serve as the N3 endpoint.

[0164] In the example, upon receiving an Nsmf_PDUSession_UpdateSMContext request with a reason (including, for example, the establishment of user plane resources), SMF 160 can send an N11 message 1060 to AMF 155, such as an Nsmf_PDUSession_UpdateSMContext response (including N1 SM container (PDU session ID, PDU session re-establishment indication), N2 SM information (PDU session ID, QoS profile, CN N3 tunnel information, S-NSSAI), and reason). SMF 160 can determine whether UPF 110 reallocation can be performed based on UE 100 location information, UPF 110 service area, and operator policy. In the example, for a PDU session that can be determined to be served by the current UPF 110 (e.g., PDU session anchor or intermediate UPF) serving SMF 160, SMF 160 can generate N2 SM information and can send an Nsmf_PDUSession_UpdateSMContext response 1060 to AMF 155 to establish a user plane. The N2 SM information may contain information that AMF 155 can provide to RAN 105. In the example, for a PDU session that SMF 160 determines requires UPF 110 to relocate the PDU session anchor UPF, SMF 160 can refuse to activate the UP for the PDU session by sending an Nsmf_PDUSession_UpdateSMContext response containing an N1 SM container to UE 100 via AMF 155. The N1 SM container may include the corresponding PDU session ID and a PDU session re-establishment indication.

[0165] Upon receiving a Namf_EventExposure_Notify from AMF 155 to SMF 160 indicating that UE 100 is reachable, if SMF 160 may have pending DL data, SMF 160 may invoke the Namf_Communication_N1N2MessageTransfer service operation to AMF 155 to establish a user plane for a PDU session. In the example, in the case of DL data, SMF 160 may continue to send DL data notifications to AMF 155.

[0166] In the example, if the PDU session corresponds to an LADN and UE 100 may be outside the availability zone of the LADN, or if AMF 155 can notify SMF 160 that UE 100 is reachable for regulated priority services and the PDU session to be activated may not be used for regulated priority services; or if SMF 160 may decide to perform PSA UPF 110-3 relocation for the requested PDU session, then SMF 160 can send a message to AMF 155 to refuse the UP activation of the PDU session by including a reason in the Nsmf_PDUSession_UpdateSMContext response.

[0167] In the example, AMF 155 can send an N2 request message 1065 to (R)AN 105 (e.g., N2 SM information received from SMF 160, security context, AMF 155 signaling connection ID, handover restriction list, MM NAS service acceptance, and a list of recommended cell / TA / NG-RAN node identifiers). In the example, RAN 105 can store the security context, AMF 155 signaling connection ID, QoS information for the QoS flow of the PDU session that can be activated, and the N3 tunnel ID in the UE 100 RAN 105 context. In the example, the MM NAS service acceptance can include the PDU session state in AMF 155. If SMF 160 might refuse to activate the UP of the PDU session, the MM NAS service acceptance can include the PDU session ID and the reason why the user plane resource might not be activated (e.g., LADN is unavailable). Local PDU session release during the session request procedure can be indicated to UE 100 via the session state.

[0168] In the example, if there are a number of PDU sessions that may involve multiple SMF 160s, the AMF 155 may not wait for responses from all SMF 160s before it can send N2 SM information to the UE 100. The AMF 155 may wait for all responses from the SMF 160s before it can send an MM NAS service accept message to the UE 100.

[0169] In the example, if a procedure can be triggered for PDU session user plane activation, the AMF 155 may include at least one N2 SM information from the SMF 160. The AMF 155 may send additional N2 SM information from the SMF 160 in a separate N2 message (e.g., an N2 tunnel setup request, if present). Alternatively, if multiple SMFs 160s may be involved, the AMF 155 may send an N2 request message to the (R)AN 105 after receiving all Nsmf_PDUSession_UpdateSMContext response service operations from all SMFs 160s associated with the UE 100. In this case, the N2 request message may include the N2 SM information received in each Nsmf_PDUSession_UpdateSMContext response and the PDU session ID, enabling the AMF 155 to associate the response with the relevant SMF 160.

[0170] In the example, if the RAN 105 (e.g., NG RAN) node can provide a list of recommended cell / TA / NG-RAN node identifiers during the release procedure, the AMF 155 can include information from that list in the N2 request. RAN 105 can use this information to allocate RAN 105 notification areas when it may decide to enable RRC inactivity for UE 100.

[0171] If AMF 155 can receive from SMF 160 during the PDU session establishment procedure an indication that UE 100 may be using a PDU session related to a latency-sensitive service for any PDU session established for UE 100, and AMF 155 has received from UE 100 an indication that CM-CONNECTED can be supported in an RRC inactivity state, then AMF 155 may include the UE's RRC inactivity auxiliary information. In the example, AMF 155 based on network configuration may include the UE's RRC inactivity auxiliary information.

[0172] In the example, (R)AN 105 can send a message to UE 100 to perform an RRC connection reconfiguration 1070 with UE 100, depending on the QoS information of all QoS flows of the PDU session for which the UP connection can be activated, as well as the data radio bearer. In the example, user plane security can be established.

[0173] In the example, if the N2 request could include an MM NAS service acceptance message, RAN 105 could forward the MM NAS service acceptance to UE 100. UE 100 could then locally delete the context of a PDU session that might not be available in 5GC.

[0174] In the example, if N1 SM information can be transmitted to UE 100 and indicates that some PDU sessions can be re-established, then UE 100 can initiate PDU session re-establishment for PDU sessions that can be re-established after the service request procedure may be completed.

[0175] In the example, after the user plane radio resources can be configured, uplink data from UE 100 can be forwarded to RAN 105. RAN 105 (e.g., NG-RAN) can then send the uplink data to the provided UPF 110 address and tunnel ID.

[0176] In the example, (R)AN 105 can send an N2 request acknowledgment 1105 to AMF 155 (e.g., N2 SM information including: AN tunnel information, a list of accepted QoS flows for PDU sessions with UP connections active, and a list of rejected QoS flows for PDU sessions with UP connections active)). In the example, the N2 request message may include N2 SM information, such as AN tunnel information. RAN 105 can respond to the N2 SM information with a separate N2 message (e.g., an N2 tunnel setup response). In the example, if multiple N2 SM information items are included in the N2 request message, the N2 request acknowledgment may include multiple N2 SM information items and information that enables AMF 155 to associate the response with the relevant SMF 160.

[0177] In the example, AMF 155 can send an Nsmf_PDUSession_UpdateSMContext request 1110 (N2 SM information (AN tunnel information), RAT type) per PDU session to SMF 160. If AMF 155 can receive N2 SM information (one or more) from RAN 105, AMF 155 can forward the N2 SM information to the relevant SMF 160. If the UE 100 timezone may have changed compared to the last reported UE 100 timezone, AMF 155 can include the UE 100 timezone IE in the Nsmf_PDUSession_UpdateSMContext request message.

[0178] In the example, if a dynamic PCC is deployed, the SMF 160 can notify the PCF 135 of new location information (if subscribed) by invoking an event exposure notification operation (e.g., the Nsmf_EventExposure_Notify service operation). The PCF 135 can provide updated policies by invoking the policy control update notification message 1115 (e.g., the Npcf_SMPolicyControl_UpdateNotify operation).

[0179] In the example, if SMF 160 can select the new I-UPF 110 as the intermediate I-UPF 110 for the PDU session, then SMF 160 can initiate an N4 session modification procedure 1120 to the new I-UPF 110 and can provide AN tunneling information. Downlink data from the new I-UPF 110 can be forwarded to RAN 105 and UE 100. In the example, UPF 110 can send an N4 session modification response 1120 to SMF 160. In the example, SMF 160 can send an Nsmf_PDUSession_UpdateSMContext response 1140 to AMF 155.

[0180] In the example, if a forwarding tunnel to the new I-UPF 110 can be established, and if the timer set for the forwarding tunnel, SMF 160, may expire, SMF 160 can send an N4 session modification request 1145 to the new (intermediate) UPF 110, which serves as the N3 termination point, to release the forwarding tunnel. In the example, the new (intermediate) UPF 110 can send an N4 session modification response 1145 to SMF 160. In the example, SMF 160 can send an N4 session modification request 1150 or an N4 session release request to PSA UPF 110-3. In the example, if SMF 160 can continue using the old UPF 110-2, SMF 160 can send an N4 session modification request 1155, thereby providing AN tunnel information. In the example, if SMF 160 can select the new UPF 110 as the intermediate UPF 110, and the old UPF 110-2 may not be PSA UPF 110-3, then SMF 160 can initiate resource release by sending an N4 session release request (release reason) to the old intermediate UPF 110-2 after the timer expires.

[0181] In the example, the old intermediate UPF 110-2 can send an N4 session modification response or an N4 session release response 1155 to the SMF 160. The old UPF 110-2 can use the N4 session modification response or N4 session release response message to acknowledge the modification or release of the resource. The AMF 155 can invoke the Namf_EventExposure_Notify service operation to notify the NFs that may have subscribed to the event of the move-related event after this procedure may complete. In the example, if SMF 160 has subscribed to UE 100 moving into or out of its region of interest and if the UE's current location indicates that it may be moving into or out of its subscribed region of interest, or if SMF 160 has subscribed to LADN DNN and if UE 100 may be moving into or out of an area where LADN is available, or if UE 100 may be in MICO mode and AMF 155 has notified UE 100 that SMF 160 is unreachable and SMF 160 may not send DL data notifications to AMF 155, and AMF 155 can notify SMF 160 that UE 100 is reachable, then AMF 155 can call Namf_EventExposure_Notify on SMF 160. Alternatively, if SMF 160 has subscribed to UE 100's reachability status, then AMF 155 can notify UE 100 of its reachability.

[0182] exist Figure 12 and Figure 13The document describes an example PDU session establishment procedure. In one exemplary implementation, when a PDU session establishment procedure is available, UE 100 may send a NAS message 1205 (or an SM NAS message) to AMF 155. This NAS message includes NSSAI, S-NSSAI (e.g., requested S-NSSAI, allowed S-NSSAI, subscribed S-NSSAI, etc.), DNN, PDU session ID, request type, old PDU session ID, N1 SM container (PDU session establishment request), etc. In the example, UE 100 may generate a new PDU session ID to establish a new PDU session. In the example, when emergency service may be required and an emergency PDU session may not yet be established, UE 100 may initiate a UE 100-requested PDU session establishment procedure, where the request type indicates an emergency request. In the example, UE 100 may initiate a UE 100-requested PDU session establishment procedure by transmitting a NAS message containing a PDU session establishment request within the N1 SM container. PDU session establishment requests may include PDU type, SSC mode, protocol configuration options, etc. In the example, if the PDU session establishment is a request to establish a new PDU session, the request type may indicate an initial request, and if the request involves an existing PDU session between 3GPP access and non-3GPP access or an existing PDN connection in an EPC, the request type may indicate an existing PDU session. In the example, if the PDU session establishment is a request to establish a PDU session for emergency services, the request type may indicate an emergency request. If the request involves an existing PDU session for emergency services between 3GPP access and non-3GPP access, the request type may indicate an existing emergency PDU session. In the example, a NAS message sent by UE 100 may be encapsulated in an N2 message sent to AMF 155 that may include user location information and access technology type information. In the example, the PDU session establishment request message may contain an SM PDU DN request container containing information about external DN authorization for the PDU session. In the example, if the procedure can be triggered for SSC Mode 3 operation, then UE 100 can include the old PDU session ID in the NAS message. This old PDU session ID can indicate the PDU session ID of the ongoing PDU session to be released. The old PDU session ID can be an optional parameter that can be included in this case. In the example, AMF 155 can receive NAS messages (e.g., NAS SM messages) and user location information (e.g., cell ID in the case of RAN 105). In the example, when UE 100 is outside the availability area of ​​LADN, UE 100 may not trigger PDU session establishment corresponding to the PDU session of LADN.

[0183] In the example, AMF 155 can determine whether a NAS message or an SM NAS message corresponds to a request for a new PDU session based on the request type indicating an initial request and the PDU session ID not being used for any existing PDU session of UE100. If the NAS message does not contain an S-NSSAI, AMF 155 can determine the default S-NSSAI for the requested PDU session based on UE 100 subscriptions (if it can contain only one default S-NSSAI) or based on operator policies. In the example, AMF 155 can perform SMF 160 selection 1210 and select SMF 160. If the request type indicates an initial request or the request can be attributed to a handover from EPS, AMF 155 can store the association of the S-NSSAI, the PDU session ID, and the SMF 160 ID. In the example, if the request type is an initial request, and if the old PDU session ID indicating an existing PDU session can be included in the message, the AMF 155 can select the SMF 160 and can store the association between the new PDU session ID and the selected SMF 160 ID.

[0184] In the example, AMF 155 can send N11 message 1215 to SMF 160, such as Nsmf_PDUSession_CreateSMContext request (including: SUPI or PEI, DNN, S-NSSAI, PDU session ID, AMF 155 ID, request type, N1 SM container (PDU session establishment request), user location information, access type, PEI, GPSI), or Nsmf_PDUSession_UpdateSMContext request (SUPI, DNN, S-NSSAI, PDU session ID, AMF 155 ID, request type, N1 SM container (PDU session establishment request), user location information, access type, RAT type, PEI). In the example, if AMF 155 may not be associated with SMF 160 of the PDU session ID provided by UE 100 (e.g., when the request type indicates an initial request), AMF 155 can invoke the Nsmf_PDUSession_CreateSMContext request. However, if AMF 155 is already associated with SMF 160 of the PDU session ID provided by UE 100 (e.g., when the request type indicates an existing PDU session), AMF 155 can invoke the Nsmf_PDUSession_UpdateSMContext request. In the example, the AMF 155 ID can be the UE's GUAMI, which uniquely identifies the AMF 155 serving UE 100. AMF 155 can forward the PDU session ID along with the N1 SM container containing the PDU session establishment request received from UE 100. When UE 100 has registered for emergency services without providing SUPI, AMF 155 can provide PEI instead of SUPI. If UE 100 has registered for emergency services but has not yet been certified, AMF 155 can indicate that SUPI has not yet been certified.

[0185] In the example, if the request type may not indicate an urgent request or an existing urgent PDU session, and if SMF 160 has not yet registered and subscription data may be unavailable, SMF 160 may register with UDM 140 and may retrieve subscription data 1225 and be notified when subscription data can be modified. In the example, if the request type may indicate an existing PDU session or an existing urgent PDU session, SMF 160 may determine that the request is attributable to a handover between 3GPP access and non-3GPP access, or to a handover from EPS. SMF 160 may identify an existing PDU session based on the PDU session ID. SMF 160 may update an existing SM context instead of creating a new SM context, and may provide an updated representation of the SM context to AMF 155 in the response. If the request type may be an initial request, and if the old PDU session ID can be included in the Nsmf_PDUSession_CreateSMContext request, SMF 160 may identify the existing PDU session to be released based on the old PDU session ID.

[0186] In the example, SMF 160 can send N11 message response 1220 to AMF 155, such as a PDU session creation / update response, Nsmf_PDUSession_CreateSMContext response 1220 (reason, SM context ID or N1 SM container (PDU session rejected (reason))) or Nsmf_PDUSession_UpdateSMContext response.

[0187] In the example, if SMF 160 can perform secondary authorization / authentication 1230 during the PDU session establishment by the DN-AAA server, then SMF 160 can choose UPF 110 and can trigger PDU session establishment authentication / authorization.

[0188] In the example, if the request type indicates an initial request, the SMF 160 can select the SSC mode for the PDU session. The SMF 160 can select one or more UPFs as needed. In the case of an IPv4 or IPv6 PDU, the SMF 160 can assign an IP address / prefix to the PDU session. In the case of an IPv6 PDU, the SMF 160 can assign an interface identifier to the UE 100 so that the UE 100 can construct its link-local address. For unstructured PDU types, the SMF 160 can assign an IPv6 prefix to the PDU session and the N6 point-to-point tunnel (based on UDP / IPv6).

[0189] In the example, if a dynamic PCC is deployed, the SMF 160 can perform PCF 135 selection 1235. If the request type indicates an existing PDU session or an existing emergency PDU session, the SMF 160 can use PCF 135 already selected for the PDU session. If a dynamic PCC is not deployed, the SMF 160 can apply a local policy.

[0190] In the example, SMF 160 can execute Session Management Policy Establishment Procedure 1240 to establish a PDU session with PCF 135 and obtain the default PCC rules for the PDU session. GPSI can be included if available at SMF 160. If the request type in 1215 indicates an existing PDU session, SMF 160 can notify of events previously subscribed to by PCF 135 via the Session Management Policy Modification Procedure, and PCF 135 can update the policy information in SMF 160. PCF 135 can provide SMF 160 with an authorized session—AMBR—and authorized 5QI and ARP. PCF 135 can subscribe to IP allocation / release events in SMF 160 (and can subscribe to other events).

[0191] In the example, PCF 135, based on the Emergency DNN, can set the ARP of the PCC rule to a value that can be reserved for emergency services.

[0192] In the example, if the request type in 1215 indicates an initial request, the SMF 160 can select the SSC mode for the PDU session. The SMF 160 can select one or more UPFs in 1245 as needed. In the case of an IPv4 or IPv6 PDU, the SMF 160 can assign an IP address / prefix to the PDU session. In the case of an IPv6 PDU, the SMF 160 can assign an interface identifier to the UE100 so that the UE100 can build its link-local address. For unstructured PDU types, the SMF 160 can assign an IPv6 prefix (e.g., based on UDP / IPv6) to the PDU session and the N6 point-to-point tunnel. In the example, for a PDU session of the Ethernet PDU type, the SMF 160 cannot assign either a MAC address or an IP address to the UE100 for this PDU session.

[0193] In the example, if the request type in 1215 is an existing PDU session, then SMF 160 can maintain the same IP address / prefix that can be assigned to UE 100 in the source network.

[0194] In the example, if the request type in 1215 indicates an existing PDU session involving movement between 3GPP access and non-3GPP access, then SMF 160 can maintain the SSC mode of the PDU session, such as the current PDU session anchor and IP address. In the example, SMF 160 can trigger, for example, the insertion of a new intermediate UPF 110 or the allocation of a new UPF 110. In the example, if the request type indicates an urgent request, then SMF 160 can select 1245 UPF 110 and can select SSC mode 1.

[0195] In the example, the SMF 160 can execute a session management policy modification procedure 1250 to report certain events to a previously subscribed PCF 135. If the request type is an initial request, a dynamic PCC is deployed, and the PDU type is IPv4 or IPv6, the SMF 160 can notify the (previously subscribed) PCF 135 of the UE's assigned IP address / prefix.

[0196] In the example, PCF 135 can provide updated policies to SMF 160. PCF 135 can provide authorized sessions - AMBR and authorized 5QI and ARP to SMF 160.

[0197] In the example, if the request type indicates an initial request, SMF 160 can initiate an N4 session establishment procedure 1255 with the selected UPF 110. SMF 160 can also initiate an N4 session modification procedure with the selected UPF 110. In the example, SMF 160 can send an N4 session establishment / modification request 1255 to UPF 110 and can provide packet detection, execution, reporting rules, etc., to be installed on UPF 110 for this PDU session. If CN tunneling information is allocated by SMF 160, it can be provided to UPF 110. If this PDU session requires selective user plane deactivation, SMF 160 can determine an inactive timer and provide it to UPF 110. In the example, UPF 110 can acknowledge this by sending an N4 session establishment / modification response 1255. If CN tunneling information is allocated by the UPF, it can be provided to SMF 160. In the example, if multiple UPFs are selected for a PDU session, then SMF 160 can initiate an N4 session creation / modification procedure 1255 with each UPF 110 of the PDU session.

[0198] In the example, SMF 160 can send the Namf_Communication_N1N2MessageTransfer1305 message to AMF 155 (including PDU session ID, access type, N2 SM information (PDU session ID, QFI, QoS profile, CN tunnel information, S-NSSAI, session-AMBR, PDU session type, etc.) and N1 SM container (PDU session establishment acceptance (QoS rules, selected SSC mode, S-NSSAI, assigned IPv4 address, interface identifier, session-AMBR, selected PDU session type, etc.))). In cases where multiple UPFs are used for a PDU session, the CN tunnel information may include tunnel information related to the UPF 110 terminating N3. In the example, the N2 SM information may carry information that the AMF 155 can forward to the (R)AN 105 (e.g., CN tunnel information corresponding to the core network address of the N3 tunnel corresponding to the PDU session, one or more QoS profiles and corresponding QFIs may be provided to the (R)AN 105, the PDU session ID may indicate the association between AN resources and the PDU session for UE 100 via AN signaling with UE 100, etc.). In the example, the PDU session may be associated with S-NSSAI and DNN. In the example, the N1 SM container may contain PDU session establishment acceptance that the AMF 155 can provide to UE 100. In the example, multiple QoS rules and QoS profiles may be included in the PDU session establishment acceptance within the N1 SM and the N2 SM information. In the example, Namf_Communication_N1N2MessageTransfer 1305 may also include the PDU session ID and information that allows the AMF 155 to know which access is used for UE 100.

[0199] In the example, AMF 155 can send an N2 PDU session request 1310 to (R)AN 105 (including N2 SM information, NAS message (PDU session ID, N1 SM container (PDU session establishment acceptance, etc.))). In the example, AMF 155 can send a NAS message 1310 to (R)AN 105, which may include a PDU session ID and a PDU session establishment acceptance for UE 100, as well as the N2 SM information received from SMF 160 within the N2 PDU session request 1310.

[0200] In the example, (R)AN 105 can issue an AN-specific signaling exchange 1315 with UE 100, which can be related to information received from SMF 160. In the example, in the case of 3GPP RAN 105, an RRC connection reconfiguration procedure can be performed with UE 100 to establish the necessary RAN 105 resources related to the QoS rules of PDU session request 1310. In the example, (R)AN 105 can allocate (R)AN 105 N3 tunnel information for the PDU session. In the dual-connectivity case, the primary RAN 105 node can assign some (zero or more) QFIs to be configured to the primary RAN 105 node and assign other QFIs to the secondary RAN 105 node. The tunnel information can include the tunnel endpoints of each involved RAN 105 node and the QFIs assigned to each tunnel endpoint. QFIs can be assigned to either the primary or secondary RAN 105 node. In the example, (R)AN 105 can forward NAS message 1310 (PDU session ID, N1 SM container (PDU session establishment accepted)) to UE 100. If the necessary RAN 105 resources are established and (R)AN 105 tunnel information is successfully allocated, (R)AN 105 can provide the NAS message to UE 100.

[0201] In the example, the N2 PDU session response 1320 may include the PDU session ID, reason, N2 SM information (PDU session ID, AN tunnel information, list of accepted / rejected QFIs), etc. In the example, the tunnel information may correspond to the access network address of the N3 tunnel corresponding to the PDU session.

[0202] In the example, AMF 155 can forward N2 SM information received from (R)AN 105 to SMF 160 via Nsmf_PDUSession_UpdateSMContext request 1330 (including N2 SM information, request type, etc.). In the example, if the list of rejected QFIs is included in the N2 SM information, SMF 160 can release the QoS profile associated with the rejected QFI.

[0203] In the example, SMF 160 can initiate an N4 session modification procedure 1335 with UPF 110. SMF 160 can provide UPF 110 with AN tunnel information and corresponding forwarding rules. In the example, UPF 110 can provide an N4 session modification response 1335 to SMF 160.

[0204] In the example, SMF 160 can send an Nsmf_PDUSession_UpdateSMContext response 1340 (reason) to AMF 155. Following this step, SMF 160 can subscribe to UE 100 mobility event notifications (e.g., location reports, UE 100 moving into or out of the region of interest) from AMF 155 by invoking the Namf_EventExposure_Subscribe service operation. For LADN, SMF 160 can subscribe to UE 100 moving into or out of the LADN service area event notification by providing the LADN DNN as an indicator of the region of interest. AMF 155 can forward relevant events subscribed to by SMF 160.

[0205] In the example, SMF 160 can send Nsmf_PDUSession_SMContextStatusNotify(release) 1345 to AMF 155. In this example, if at any point during this procedure, the SMF 160 can notify the AMF 155 by calling Nsmf_PDUSession_SMContextStatusNotify(release) 1345, the SMF 160 can release any created N4 sessions, any PDU session addresses (if assigned) (e.g., IP addresses), and the association with PCF 135.

[0206] In the example, with the PDU type being IPv6, the SMF 160 can generate an IPv6 router advertisement 1350, which can be sent to the UE 100 via the N4 and UPF 110.

[0207] In the example, if a PDU session might not be established, the SMF 160 can use Nudm_SDM_Unsubscribe(SUPI, DNN, S-NSSAI) to unsubscribe from the modifications made by 1360 to the corresponding (SUPI, DNN, S-NSSAI) session management subscription data when the SMF 160 no longer processes the PDU session for this UE 100 (DNN, S-NSSAI). In the example, if a PDU session might not be established, the SMF 160 can use Nudm_UECM_Deregistration(SUPI, DNN, PDU session ID) to unregister 1360 for a given PDU session.

[0208] Figure 14 Another example of a mobile communication network in which embodiments of the present disclosure can be implemented is shown. Figure 14The mobile communication network depicted includes a radio device 1410, a base station 1420, a physical core network deployment 1430 (hereinafter referred to as "CN deployment 1430") with one or more network functions, and a physical core network deployment 1440 (hereinafter referred to as "CN deployment 1440") with one or more network functions. Deployment 1430 and deployment 1440 may be elements of the core network.

[0209] Wireless device 1410 can communicate with base station 1420 via air interface 1470. The communication direction from wireless device 1410 to base station 1420 via air interface 1470 is called uplink, and the communication direction from base station 1420 to wireless device 1410 via air interface 1470 is called downlink. Downlink transmission can be separated from uplink transmission using some combination of FDD, TDD, and / or two duplex technologies. Figure 14 A single wireless device 1410 and a single base station 1420 are shown, but it should be understood that the wireless device 1410 can communicate with any number of base stations or other access network components via the air interface 1470, and the base station 1420 can communicate with any number of wireless devices via the air interface 1470.

[0210] Wireless device 1410 may include processing system 1411 and memory 1412. Memory 1412 may include one or more computer-readable media, such as one or more non-transitory computer-readable media. Memory 1412 may include instructions 1413. Processing system 1411 may process and / or execute instructions 1413. Processing and / or execution of instructions 1413 may cause processing system 1411 to perform one or more functions or activities. Memory 1412 may include data (not shown). One of the functions or activities performed by processing system 1411 may be storing data in memory 1412 and / or retrieving previously stored data from memory 1412. In the example, downlink data received from base station 1420 may be stored in memory 1412, and uplink data for transmission to base station 1420 may be retrieved from memory 1412. Wireless device 1410 may communicate with base station 1420 using transmission processing system 1414 and reception processing system 1415. Wireless device 1410 may include one or more antennas 1416 to access air interface 1470. Although Figure 14 Not shown, but the transmission processing system 1414 and / or the receiving processing system 1415 may be coupled to a dedicated memory similar to but separate from the memory 1412, and include instructions that can be processed and / or executed to perform one or more of their respective functions.

[0211] Wireless device 1410 may include one or more other elements 1419. These other elements 1419 may include software and / or hardware providing features and / or functionality, such as a speaker, microphone, keyboard, display, touchpad, satellite transceiver, universal serial bus (USB) port, hands-free headset, FM radio unit, media player, internet browser, electronic control unit (e.g., for motor vehicles), and / or one or more sensors (e.g., accelerometer, gyroscope, temperature sensor, radar sensor, lidar sensor, ultrasonic sensor, light sensor, camera, GPS sensor, etc.). Wireless device 1410 may receive user input data from and / or provide user output data to these other elements 1419. These other elements 1419 may include a power source. Wireless device 1410 may receive power from the power source and may be configured to distribute power to other components within wireless device 1410. The power source may include one or more power sources, such as a battery, solar cell, fuel cell, or any combination thereof.

[0212] Wireless device 1410 can transmit data to base station 1420 via air interface 1470. To perform the transmission, processing system 1411 can implement Layer 3 and Layer 2 Open Systems Interconnection (OSI) functions to process data for uplink transmission. Layer 3 may include Radio Resource Control (RRC). Layer 14 may include Serving Data Application Protocol (SDAP), Packet Data Convergence Protocol (PDCP), Radio Link Control (RLC), and Media Access Control (MAC). Data can be provided to transmission processing system 1414, which can implement Layer 1 OSI functions. Layer 1 may include the Physical Layer (PHY). Wireless device 1410 can transmit data via air interface 1470 using one or more antennas 1416. Where one or more antennas 1416 include multiple antennas, the multiple antennas can be used to perform one or more multi-antenna techniques, such as spatial multiplexing (e.g., single-user multiple-input multiple-output (MIMO) or multi-user MIMO), transmit / receive diversity, and / or beamforming.

[0213] Wireless device 1410 can receive downlink data from base station 1420 via air interface 1470. The downlink data can be received via one or more antennas 1416. Receive processing system 1415 can implement Layer 1 OSI functions on the received downlink data and can provide the data to processing system 1411. Processing system 1411 can implement Layer 2 and Layer 3 OSI functions to process the received downlink data. Base station 1420 may include elements similar to those of wireless device 1410. Base station 1420 may include processing system 1421 and memory 1422. Memory 1422 may include one or more computer-readable media, such as one or more non-transitory computer-readable media. Memory 1422 may include instructions 1423. Processing system 1421 can process and / or execute instructions 1423. Processing and / or execution of instructions 1423 may cause processing system 1421 to perform one or more functions or activities. Memory 1422 may include data (not shown). One of the functions or activities performed by processing system 1421 may be storing data in memory 1422 and / or retrieving previously stored data from memory 1422. Base station 1420 may communicate with wireless device 1410 using transmission processing system 1424 and reception processing system 1425. Base station 1420 may include one or more antennas 1426 for accessing air interface 1470. Processing system 1421 may implement Layer 14 and Layer 3 OSI functions. Transmission processing system 1424 and reception processing system 1425 may implement Layer 1 OSI functions to perform downlink data transmission and uplink data reception, respectively.

[0214] Base station 1420 may include interface system 1427. Interface system 1427 may communicate with one or more units of the core network via interface 1480. Interface 1480 may be wired and / or wireless, and interface system 1427 may include one or more components adapted for communication via interface 1480. Figure 14 In this configuration, interface 1480 connects base station 1420 to a single CN deployment 1430; however, it will be understood that wireless device 1410 can communicate with any number of CN deployments via interface 1480, and CN deployment 1430 can communicate with any number of base stations via interface 1480. Base station 1420 may include one or more other elements 1429 similar to one or more other elements 1419.

[0215] CN deployment 1430 may include one or more network functions (NFs). For example, CN deployment 1430 may include similar to Figure 1The AMF and / or UPF depicted herein. CN deployment 1430 may include elements similar to those of wireless device 1410 and base station 1420 as described above. CN deployment 1430 may include processing system 1431 and memory 1432. Memory 1432 may include one or more computer-readable media, such as one or more non-transitory computer-readable media. Memory 1432 may include instructions 1433. Processing system 1431 may process and / or execute instructions 1433. Processing and / or execution of instructions 1433 may cause processing system 1431 to perform one or more functions or activities. Memory 1432 may include data (not shown). One of the functions or activities performed by processing system 1431 may be storing data in memory 1432 and / or retrieving previously stored data from memory 1432. CN deployment 1430 may access interface 1480 using interface system 1437. CN deployment 1430 may also use interface system 1437 to access interface 1490. CN deployment 1430 can use interface 1490 to connect with one or more data networks (similar to, for example) Figure 1 The DN and / or one or more other CN deployments described herein include Figure 14 The CN deployment 1430 described herein communicates. The CN deployment 1430 may include one or more other elements 1439.

[0216] CN deployment 1440 may include elements similar to those in CN deployment 1430, as described above. CN deployment 1440 may include a processing system 1441 and a memory 1442. Memory 1442 may include one or more computer-readable media, such as one or more non-transitory computer-readable media. Memory 1442 may include instructions 1443. Processing system 1441 may process and / or execute instructions 1443. Processing and / or execution of instructions 1443 may cause processing system 1441 to perform one or more functions or activities. Memory 1442 may include data (not shown). One of the functions or activities performed by processing system 1441 may be storing data in memory 1442 and / or retrieving previously stored data from memory 1442. CN deployment 1440 may access interface 1490 using interface system 1447. CN deployment 1440 may include one or more other elements.

[0217] Processing systems 1411, 1421, 1431, and / or 1441 may include one or more controllers and / or one or more processors. These controllers and / or processors may include, for example, general-purpose processors, digital signal processors (DSPs), microcontrollers, application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs) and / or other programmable logic devices, discrete gate and / or transistor logic, discrete hardware components, onboard units, or any combination thereof. Processing systems 1411, 1421, 1431, and / or 1441 may perform signal encoding / processing, data processing, power control, input / output processing, and / or any other functions that enable wireless device 1410, base station 1420, CN deployment 1430, and / or CN deployment 1440 to operate in a mobile communication system.

[0218] Each CN deployment may include one or more network functions. Depending on the context in which the term is used, a network function (NF) can refer to a specific set of functions and / or one or more physical elements (e.g., a processing system and a memory containing instructions that, when executed by the processing system, cause the processing system to perform those functions) that perform those functions. Many different types of NFs exist, and each type of NF can be associated with a different set of functions. Different NFs can be flexibly deployed in different locations (e.g., in different physical core network deployments) or in the same location (e.g., juxtaposed within the same physical core network deployment). Furthermore, a physical CN deployment is not limited to the implementation of NFs. For example, a particular physical CN deployment may also include a base station or a portion thereof and / or a data network or a portion thereof. Therefore, one or more NFs implemented on a particular physical core network deployment can be juxtaposed with one or more non-core elements (including elements of the access network or data network).

[0219] Many cellular networks can be deployed as PLMNs or NPNs (SNPNs). UEs can access PLMN services via SNPNs.

[0220] In one exemplary implementation, the default UE credential can be information that the UE possesses prior to the actual network access configuration procedure, enabling the UE to be uniquely identifiable and securely verifiable. The Default Credential Server (DCS) can be a server capable of authenticating the UE with the default UE credential or providing authentication means to another entity. The Non-Public Network (NPN) can be a private network deployed for an organization, specific application, etc. The NPN credential or SNPN credential can be information used by the UE to authenticate and access the NPN or SNPN. (S) The NPN credential can be a 3GPP credential or a non-3GPP credential. The Network Configuration (ON) can provide the UE with initial registration and / or access for network configuration. The Provider Server can be a server that provides subscription data and optional additional configuration information to the authenticated / authorized UE. The Subscription Owner (SO) can be an entity that stores subscription data and provides subscription data and optional additional configuration information to the UE via the Provider Server (PS) as a result of the UE network configuration procedure. UE network configuration may include providing the UE and the provider server within the network with the information required for the UE to obtain authorized access and connection to the NPN. A unique UE identifier can identify the UE in the network and the DCS and can be assigned and configured by the DCS. The unique UE identifier can be unique within the DCS and can take the form of the Network Access Identifier (NAI) using RFC 7542 (or include the NAI).

[0221] In such Figure 14 In the exemplary implementation described herein, the UE can access ON. ON can be a separate network. ON can be, for example, Figure 14 The SNPN described in the text. ON can be PLMN, PNI-NPN, etc. The desired network (e.g. Figure 14 The desired SNPN described herein can be SNPN, NPN, or PLMN. Figure 14 This describes UE configuration for network entry and remote provisioning, particularly for UE subscriptions to standalone, non-public networks. UEs without a desired SNPN can temporarily register with a 5G network that supports UE configuration for network entry and establish a restricted PDU session to receive newly assigned subscriptions to the desired SNPN from network entities for provisioning.

[0222] In the example, an SNPN can be deployed to support audio / video applications for program production and special events (PMSE) devices (including TV and broadcast studios, live news gathering, sporting events, music festivals, medical procedures, lecture halls, news centers, trade fairs, corporate / TV galas) that lack user interfaces (screen and keyboard) or physical ports (network ports, USB ports, and card slots), such as microphones, speakers, headphones, cameras, recorders, mixers, and consoles. The PMSE device can be provided / updated during UE configuration on the 5G network. The AAA server can act as a providing server and provide the UE with a newly assigned subscription (non-3GPP identity, such as non-IMSI and credentials) for the desired SNPN. If the 5G network being configured for network access is a PLMN or PNI-NPN, the UE can have a subscription and credentials to the PLMN to ensure that the UE is uniquely identifiable and verifiable secure during configuration and remote provisioning. If the 5G network to be configured for network access is an SNPN, the UE can have, for example, default UE credentials provided by the manufacturer, so that the UE is uniquely identifiable and verifiable and secure during network configuration and remote provisioning.

[0223] In an exemplary implementation, configuring the network access can be as follows: Figure 15 The SNPN (O-SNPN) described in [the text]. In, as [the text is incomplete and likely refers to a specific document or document]. Figure 15 In the exemplary implementation described herein, the procedure may allow a UE that was initially not provided with subscription credentials to access, for example, a Configuration On-Network SNPN (O-SNPN) and obtain subscription credentials and configuration from a Subscription Owner SNPN (SO-SNPN), which may be the same as or different from the O-SNPN. In the example, the UE may select an O-SNPN based on information broadcast by the O-SNPN and may register the Configuration On-Network service with that O-SNPN to obtain a connection to the providing server. If the UE has not configured network selection parameters for the O-SNPN, it may manually select an O-SNPN, or the UE may randomly select an available network that supports the Configuration On-Network function. If the UE fails to complete remote provisioning through the selected O-SNPN (e.g., the UE fails authentication through the DCS), the UE may select another O-SNPN to try the process again. During the registration procedure, the O-SNPN may authenticate the UE with the Default Credential Server (DCS) to determine whether the UE is a genuine device and whether it is authorized to access the providing server via a Configuration PDU session. After establishing a connection to the providing server, the UE can be provided with subscription credentials for SO-SNPN (i.e., the SNPN that will have the UE's subscription) along with additional configuration data. The UE can unregister from SO-SNPN, perform network selection, and register for SO-SNPN using the provided subscription credentials and configuration data.

[0224] In such Figure 16 and Figure 17 In the exemplary implementation described herein, the network configured for network access can be an NPN (O-NPN) integrated into a PLMN, SNPN, or another network. The UE can identify and access the O-NPN through a specific network ID (NID), CAG ID, S-NSSAI, DNN, a combination of PLMN ID and NID, etc. One or more providing servers can agree with one or more desired SNPNs (SO-SNPN).

[0225] In such Figure 18 In the exemplary implementation described herein, a PLMN can be used for UE configuration and network access. The UE can be configured with default credentials in its Universal Subscriber Identity Module (USIM) to attach to any PLMN with which the UE can register, such as a Configuration and Access Network (ON). This enables the provision of the network credentials and configuration required by the SNPN to which the UE will have a subscription. The UE can be manufactured with default credentials, which reside in a USIM profile that can be used for UE configuration and network access. The USIM profile can be published by any PLMN operator with which the manufacturer has an agreement. The PLMN that publishes the USIM profile... Figure 18 The PLMN is referred to as HPLMN. The HPLMN's UDM (or HSS) acts as the default credential server (DCS), and the provider server (PS) resides in the DN that provides access to the HPLMN. As part of the agreement between the UE manufacturer and the HPLMN, the UE subscription in the HPLMN allows access to the DN that provides connectivity to the PS. When performing UE configuration for network entry, any PLMN available at the UE's location can be used as ON, provided the UE has an agreement with the HPLMN. Upon power-up, the UE may not have information for SNPN selection and therefore performs a normal PLMN selection, registering and establishing a PDU session using the normal procedure. The UE subscription corresponding to the USIM profile contains the S-NSSAI and default DNN suitable for reaching the PS; therefore, a PDU session providing access to the PS can be established without the UE indicating any NSSAI or DNN information. The UE can connect to the PS through the established PDU session for configuration for network entry. The HPLMN can, for example, use header enrichment to provide the PS with the GPSI of the UE subscription. After establishing a connection to the PS, the UE can be provided with NPN credentials (used to register the SNPN that owns the UE's subscription) and additional configuration data. The UE can then deregister from the PLMN and, using the information obtained during UE login, perform a new network selection and register with the SNPN that owns the UE's subscription using the provided NPN credentials.

[0226] In such Figure 19 and Figure 20 In the exemplary implementations depicted, N3IWF or interoperability functionality can be used for connectivity between two or more networks. A UE can access the services of a PLMN via an SNPN. A UE can access the services of an SNPN via a PLMN. A UE can access the services of an SNPN via another SNPN. Figure 19 This describes the UPF PSA scenario for PDU sessions in SNPN. A dual-radio UE can register using one radio under SNPN NG-RAN and the other radio under SNPN N3IWF via PLMN NG-RAN and 5GC. From the perspective of SNPN 5GC, the UE can register under both 3GPP access and non-3GPP access. Figure 19 An example of a dual-radio UE is depicted. Figure 20 An example of a single radio UE is depicted.

[0227] In such Figure 21 In the exemplary implementation described herein, the UE can access the services of a second network (PLMN) via a first network (e.g., a non-public network). The UE can first obtain an IP connection by registering with the non-public network. The UE can then obtain a connection to the 5GC in the PLMN via an interoperability function (e.g., a proxy, N3IWF, etc.). The non-public network may deploy a 3GPP RAT, although this 3GPP RAT may not be considered a public PLMN. The UE can perform PLMN selection as part of N3IWF discovery.

[0228] In such Figure 22 and Figure 23 In the exemplary implementation described herein, the UE can access network 2 via network 1. In the example, the UE may have two subscriptions, for example, a PLMN (also referred to as "PLMN UE" for the PLMN portion of the UE) and an SNPN (also referred to as "SNPN UE" for the SNPN portion of the UE) subscription. The described scenario may employ both PLMN and SNPN, but the same principle applies between SNPNs if permissible.

[0229] In such Figure 22 and Figure 23In the exemplary implementation described herein, within the serving network (Network 1), the UE can be in a connected state or a power-saving state and still receive service from another network. The UE can always be in a CM connected state in both networks and can always maintain an IPsec tunnel between the UE and the N3IWF via Nwu. This may involve the UE sending IPsec keep-alive messages. In the example, to maintain the IPsec tunnel to Network 2, a PDU session in Network 1 may be required. Figure 22 and Figure 23 As described, the UE can register to Network 1 (e.g., NPN). The UE can request services to set up an IPsec tunnel to the N3IWF. The service request may require indicating a specific service (connection to the PLMN / Network 2). The PDU session can be set up in Network 1. The AMF can include in the RRC inactivity auxiliary information that the UE can be released to RRC inactivity only and can send the RRC inactivity auxiliary information to the RAN. This behavior in the AMF can be triggered by 1) the UE instruction based on the NAS message (SR or PDU session establishment), or 2) by the SMF / UPF notification. The SMF / UPF, when it detects that the destination address of the IPsec tunnel is a known N3IWF of the PLMN (in this case, if the RRC inactivity auxiliary IE has already been sent, it may need to update the RRC inactivity auxiliary IE), sets up the IPsec tunnel and registers to the PLMN (Network 2). Due to inactivity in Network 1 (NPN), the RAN can release the UE to RRC inactivity mode. The RAN can receive DL data or NAS messages from the PLMN (Network 2) to the UE. The RAN node can page the UE. The UE can restore the RRC connection. DL data or NAS messages can be sent to the UE.

[0230] In the prior art, a wireless device can execute a configuration access procedure, in which it uses a configuration access network to access a providing server. The providing server can provide credentials for accessing a second network (e.g., a target network). When using the configuration access procedure, the wireless device can access the configuration access network and use it to obtain credentials. After obtaining the credentials, the UE can deregister from the configuration access network and connect to the target network.

[0231] Existing technology allows wireless devices to access a second network via a first network. The wireless device can access the second network (e.g., an overlay network) via an interconnecting node (e.g., an N3IWF) of the second network, using the first network (e.g., an underlying network). During initial access and registration on the first network, AMF selection can be performed by the RAN node. If the RAN node selects an AMF that does not support the underlying network capabilities of SNPN, the wireless device may fail to establish a PDU session for an IPSec connection to the N3IWF, and the process of connecting to and accessing the overlay network or the second network (via the N3IWF) may fail.

[0232] Not all networks support configuration-to-network access for the target network and / or underlying support for the overlay network. For example, if the first network does not support configuration-to-network access, or if the RAN node sends a configuration-to-network access request to the mobility management function of the first network that does not support configuration-to-network access, the radio device may fail to establish a PDU session for configuration-to-network access. If the first network does not support the underlying layer, or if the RAN node sends a request to the mobility management function of the first network that does not support the underlying layer, the radio device may fail to establish a session with the overlay network. As a result, the radio device may not be able to access the second network via the first network.

[0233] An exemplary implementation provides enhanced signaling to facilitate access to a second network based on access to a first network. In the example, the base station can receive a configuration message from the first network that includes an indication that the first network supports configuration access to the second network. The configuration message can be received from OAM, NWDAF, or a mobility management function (e.g., a mobility management function that provides configuration access support). The configuration message may include an identifier of the second network. The presence of the second network identifier can be an indication that the first network supports configuration access to the second network. The base station can send a configuration access request to the mobility management function of the first network. The configuration access request can request a radio device to configure access to the second network. This enhanced signaling facilitates the connection of a radio device to a network that supports configuration access, especially when configuration access is a specific requirement for the radio device.

[0234] An exemplary implementation provides enhanced signaling for notifying of a lack of access to a second network based on access to a first network. In the example, a base station of the first network can receive an RRC message from a radio device that includes an identifier of the second network. The base station can determine that the first network (e.g., one or more mobility management functions of the first network) does not support configured entry into the second network. The base station can indicate that configured entry is not supported. This enhanced signaling can facilitate radio devices connecting to networks that support configured entry, especially when configured entry is a specific requirement for the radio device.

[0235] An exemplary implementation provides enhanced signaling to facilitate access to a second network based on access to a first network. In the example, a base station of the first network can receive an RRC message from a radio device that includes an indication of access to the second network. The base station can select a mobility management function of the first network that supports network access to the second network. The base station can send a registration request message for network access of the radio device to the mobility management function. This enhanced signaling can reduce the selection of mobility management functions within the first network when the mobility management function is not suitable for the specific needs of the radio device, particularly the need for network access to the second network.

[0236] An exemplary implementation includes signaling from a wireless device to a base station, wherein the signaling message includes an identifier of the SNPN (SNPN ID). The SNPN identifier can indicate to the network that network access support needs to be configured. The network (base station) can determine that network access configuration is required based on the indication (SNPN ID). The base station can select an AMF that supports SNPN configuration access based on the SNPN ID.

[0237] In an exemplary implementation, the base station can receive a configuration message from the AMF indicating configuration support for SNPN (Signal Provider Interface). The configuration message may include a configuration support indication, an SNPN ID, etc. The base station can select the AMF based on elements of the configuration message and the SNPN ID received from the radio device.

[0238] Exemplary implementations include signaling from a wireless device to a base station, wherein the signaling message includes an indication of underlying network capability support. This signaling may include an identifier for the SNPN (Secondary Network Provider Interface), which may indicate to the network the underlying network capabilities that may require connection to a second network (SNPN). The network (base station) may determine the required underlying network capabilities based on the indication (SNPN ID). The base station may select an AMF (Advanced Management Function) that supports the underlying network capabilities of the SNPN based on the SNPN ID. The underlying network capabilities may be SNPN interoperability support, SNPN signaling proxy support, SNPN coverage, or underlying support, etc.

[0239] Figure 24 A diagram is shown that includes wireless devices and networks (e.g., RAN nodes). Figure 24 An exemplary RRC connection procedure is described. The RRC connection procedure may include sending an RRC setup request message after completing the random access procedure. The purpose of this procedure is to establish an RRC connection. RRC connection establishment involves SRB1 establishment. This procedure can also be used to transmit initial NAS-specific information / messages from the UE to the network.

[0240] The network applies this procedure, for example, when establishing an RRC connection; when the UE restores or re-establishes an RRC connection and the network is unable to retrieve or verify the UE context. In this case, the UE can receive RRCSetup and respond with RRCSetupComplete. When the UE is in RRC_IDLE and has obtained the necessary system information, or for sidelink communication, when the upper layer requests the establishment of an RRC connection, the UE can initiate the RRC connection establishment procedure.

[0241] The UE can determine that the system information is valid and up-to-date. The UE can send an RRCSetupRequest message if it determines that network access is not blocked. The UE can receive RRC setup messages from the network. The UE can receive RRC rejection messages from the network.

[0242] In such Figure 24 In the exemplary implementation described herein, a wireless device (UE) may attempt to access the network. Attempts to access the network may include an RRC connection establishment procedure, a service request procedure, an RRC recovery procedure, etc. RRC connection establishment can be used to establish an RRC connection. RRC connection establishment may include the establishment of a signaling radio bearer, such as an SRB1 establishment. This procedure may be used to transmit initial NAS-specific information / messages from the UE to the network. The network may apply this procedure when an RRC connection is established, when the UE recovers or re-establishes an RRC connection, and when the network is unable to retrieve or verify the UE context, etc. In the example, the UE may receive an RRCSetup message and may respond with an RRCSetupComplete message. RRC connection establishment may include the wireless device (UE) receiving an RRC rejection message from the network.

[0243] In such Figure 25In the exemplary implementation depicted, the UE may send a Radio Resource Control (RRC) message including the Independent Non-Public Network Identifier (SNPN ID) of the second network to a base station (RAN node, NG-RAN, gNB, etc.) of a first network. The RRC message may be an RRC setup completion message. The RRC message may be an RRC setup request message. The RRC message may include the SNPN ID of the second network. In the example, the base station may determine that the UE needs to configure an access procedure to access the second network (e.g., SNPN). The base station may select an AMF based on elements of the RRC message. The selection of the AMF may be based on the AMF's configuration access support or configuration access capability. The base station may send an N2 message to the selected AMF. After completing this procedure (e.g., registration procedure, service request procedure, or PDU session establishment procedure), the UE may receive a response message from the AMF that supports configuration access (e.g., SNPN configuration access). In the example, the UE may receive the AMF of the first network, i.e., a first message indicating acceptance of registration with the first network. The first message may be a registration acceptance message. In the example, the UE can send a second message to the AMF of the first network to establish a Packet Data Unit (PDU) session. The second message can be a PDU session establishment request message, a NAS message, etc. The PDU session establishment request can include a configuration network entry indication. The PDU session establishment request can include an indication of the PDU session type for configuring the network entry PDU session. The PDU session establishment request can include an indication of the request type for configuring network entry (request type = configuration network entry).

[0244] In an exemplary implementation, the RRC message may include an SNPN ID. In an example, the RRC message may include a configuration entry indication. The RRC message may be an RRC setup complete message (message 5). In an example, the RRC message may be an RRC setup request message (message 3). In an example, the RRC setup request message may include an indication of the RRC establishment reason for configuration entry, an SNPN ID, etc. The RAN node may select an AMF that supports configuration entry of an SNPN with an SNPN ID.

[0245] The RRC setup completion message may include indications of the RRC information elements that need to be configured for network access support, the SNPN ID, etc. RAN nodes can select the AMF that supports network access configuration with an SNPN that has an SNPN ID based on these information elements.

[0246] In the example, when the ON is deployed as a PNI-NPN and access to the ON is restricted to one or more CAGs, the RRC message may include the ON's CAG ID. The RAN node can select the AMF for configuring network access based on the ON's CAG ID. In the example, when the ON is deployed as a PNI-NPN and access to the ON is restricted to one or more S-NSSAIs, the RRC message may include the ON's S-NSSAI. The RAN node can select the AMF for configuring network access based on the ON's S-NSSAI.

[0247] In an exemplary implementation, the base station can select an AMF based on indications from the network, the network's AMF, NWDAF, OAM, etc. For example, an AMF supporting (one or more SNPNs) configuration entry can send a configuration update message to the RAN node or base station, indicating that the AMF supports SNPN configuration entry. When the base station receives an RRC message and determines to select an AMF supporting SNPN configuration entry, the base station can select the AMF based on elements of the configuration update message.

[0248] In such Figure 25 and Figure 26 In the exemplary implementation described herein, the AMF pre-owned by the UE can subscribe to a UDM regarding configuration entry information. Several events can trigger the providing server to initiate the configuration entry procedure. The providing server can send a configuration entry request to the NEF, which includes configuration entry information (the target UE's GPSI, subscription credentials for accessing the SNPN, and DNN / NSSAI for accessing the SNPN) and optional triggering events. The configuration entry information can be protected by default UE credentials, which are also pre-configured in the UE (USIM). The UE can determine which default UE credentials are applied for protection (optionally via SNPN identity or default UE credential identity). The NEF can relay the configuration entry request to the UDM, which stores the target UE's subscriptions based on the GPSI. The AMF can subscribe to the triggering event from the target UE's serving AMF via a Nudm_SDM_Notification message. The UDM can send a configuration entry response to the NEF, and the NEF can then forward it to the providing server. In the example, when the AMF receives a configuration access notification from the UDM indicating configuration access support for the SNPN, the AMF can send an AMF configuration update message to the RAN node.

[0249] In such Figure 26In the exemplary implementation described herein, the AMF can receive a configuration entry indication or notification from the network (UDM). The AMF can send an AMF configuration update message to the base station. In the example, the base station (RAN) can receive a configuration entry support indication from network OAM (OA&M) network elements, NWDAF network elements, etc. In the example, after receiving a configuration entry support indication or configuration entry support indication from one or more SNPNs, the base station can broadcast system information. The base station can broadcast SIBs, such as SIB1. The system information can indicate that one or more cells of the network or RAN node, the base station, or the RAN node can support configuration entry.

[0250] Figure 27 The call flow of a registration request procedure performed by a wireless device (UE) according to an embodiment of this disclosure is illustrated. The registration request procedure can be used to configure network access. After successful registration to the configured network access (ON), the UE can execute a PDU session establishment procedure. The PDU session establishment procedure can be used for the UE's network access configuration. The UE can access the PS via a PDU session (e.g., a network access configuration PDU session) to receive credentials for the target network, desired network, SNPN, etc. The PDU session can be used to provide parameters and credentials to the UE for access and registration to the SNPN. This provision can be performed on the user plane or control plane of the PDU session. After successful provision, the UE can deregister from the ON and register to the SNPN based on the received parameters and credentials. Figure 8 and Figure 9 An example of the registration process is depicted in the document.

[0251] In such Figure 27In the example depicted, during the registration procedure, the UE may send a registration request message to the RAN node (base station). The registration request message may be or may include an AN message. In an exemplary implementation, the registration request message may be an RRC setup complete message. The registration request message may include an identifier of a second network (e.g., SNPN ID, second network ID, etc.). In the example, the second network may be a target network, a desired network, an SNPN, etc. The registration request message (or AN message) may include AN parameters, registration request (registration type, SUCI or 5G-GUTI or PEI, [last visited TAI (if available)], security parameters, [requested NSSAI], [mapped NSSAI], [default configured NSSAI indication], [UE radio capability update], [UE MM core network capability], [PDU session state], [list of PDU sessions to be activated], [follow-up request], [MICO mode preference], [requested active time], [requested DRX parameters], [extended idle mode DRX parameters], [LADN DNN or indicator requesting LADN information], [NAS message container], [support for enhanced coverage usage restrictions], [preferred network behavior], [UE paging probability information], [UE policy container (list of PSIs, indication of UE support for ANDSP and operating system identifier)] and [UE radio capability ID], PEI). In the NG-RAN case, the AN parameters may include 5G-S-TMSI or GUAMI, the selected PLMN ID (or PLMN ID and NID), and the requested NSSAI. The AN parameters may also include the establishment reason. The establishment reason can provide the reason for requesting to establish an RRC connection. Whether and how the UE includes the requested NSSAI as part of the AN parameters may depend on the value of the access stratum connection establishment NSSAI include mode parameter.

[0252] In such Figure 27 In the example depicted, the RAN node can select an AMF that supports configuration for network entry. The RAN node can select an AMF that supports configuration for network entry from a second network (e.g., an SNPN with an SNPN ID). If 5G-S-TMSI or GUAMI is not included, or if 5G-S-TMSI or GUAMI does not indicate a valid AMF, the RAN can select an AMF based on the RAT and the requested NSSAI (if available). The RAN node can select an AMF based on the indication received from the AMF for configuration support (e.g., ...). Figure 26(As depicted in the text). The RAN can select an AMF. If the UE is in CM-CONNECTED state, the RAN node can forward the registration request message to the AMF based on the UE's N2 connection. If the RAN cannot select a suitable AMF, it can forward the registration request to an AMF already configured in the RAN to perform AMF selection.

[0253] In an exemplary implementation, the AMF discovery and selection function can be applied to both 3GPP and non-3GPP access. The AMF selection function can be supported by a 5G-AN (e.g., RAN, N3IWF) and can be used to select an AMF instance for a given UE. The AMF can support the AMF selection function to select an AMF for relocation, or because the initially selected AMF is not a suitable AMF for the serving UE (e.g., due to changes in permitted NSSAI), because the initially selected AMF can support (e.g., SNPN) configuration for network entry. When the original AMF for the serving UE is unavailable or the AMF does not support (SNPN) configuration for network entry, other CP NFs (e.g., SMFs) can support the AMF selection function to select an AMF from the AMF set. The 5G-AN can select an AMF set and choose an AMF from the AMF set in the following situations: when the UE sends (e.g., via a registration request message) an SNPN ID and / or indicates that network access configuration may be required; when the 5G-AN receives an SNPN ID from the UE and determines that the SNPN ID may be associated with a second network that may need to be configured for network access; when the UE does not provide a 5G-S-TMSI or GUAMI to the 5G-AN; when the UE provides a 5G-S-TMSI or GUAMI but the routing information present in the 5G-S-TMSI or GUAMI (i.e., AMFs and AMF pointers identified by the AMF set ID) is insufficient and / or unavailable (e.g., the UE provides an AMF area ID from a different area to the GUAMI); the AMF has indicated to the RAN that the AMF (identified by the GUAMI) is unavailable; and no target AMF has been identified and / or the AN has detected that the AMF has failed, etc. In the case of NF-based service consumer discovery and selection, the CP NF may select an AMF from the AMF set in the following situations: when the AMF has indicated that an AMF identified by the CP NF by GUAMI is unavailable and the CP NF has not been notified of the target AMF; when the CP NF has detected an AMF failure; when the selected AMF does not support the UE's preferred network behavior (such as configuring network access or accessing the coverage network).

[0254] In an exemplary implementation, the AMF selection function in 5G-AN (RAN) can consider the following factors to select the AMF (set): - This includes the target network ID (such as SNPN ID) and AMF's configuration of the SNPN associated with the SNPN ID, as requested by the UE.

[0255] - AMF region ID and AMF set ID derived from GUAMI; -Required NSSAI; -Local operator policies; - 5G CIoT features indicated by the UE in the RRC signaling; -IAB-instruction; -NB-IoT RAT type; and - Category M indicator.

[0256] The AMF selection function in 5G-AN, CP NF, or SCP can consider the following factors when selecting an AMF from the AMF set: - Availability of candidate AMFs.

[0257] - Load balancing across candidate AMFs (e.g., considering the weighting factors of candidate AMFs in the AMF set).

[0258] In the case of NF service consumer discovery and selection, AMF or other CP NFs can utilize the NRF to discover AMF instances unless AMF information is available by other means, such as local configuration on the AMF or other CP NF. The NRF provides the NF profile of the AMF instance to the AMF or other CP NF. The AMF selection function in the AMF or other CP NF selects AMF instances as follows: When an NF service consumer performs discovery and selection, the following applies: When the AMF discovery and selection function in the AMF or other CP NF uses a Configuration Inclusion Support Indication (optionally with SNPN ID), GUAMI, or TAI to discover AMF instances, the NRF provides the NF profile of the associated AMF instance. If the associated AMF is unavailable due to planned AMF removal, the NF profile of the backup AMF for planned removal is provided by the NRF. If the associated AMF is unavailable due to AMF failure, the NF profile of the backup AMF for the failure is provided by the NRF. If the AMF pointer value in the GUAMI is associated with more than one AMF, the NRF provides all AMFs associated with this AMF pointer value. If no AMF instance is found associated with the indicated GUAMI, the NRF can provide a list of NF profiles for candidate AMF instances within the same AMF set. Another CP NF or AMF can then select any AMF instance from the list of candidate AMF instances. If no AMF NF profile is returned in the discovery results, another CP NF or AMF can use the AMF set to discover the AMF as follows. In cases where the AMF discovery and selection function uses the AMF set to discover AMF instances, the NRF can provide a list of NF profiles for AMF instances within the same AMF set.

[0259] In the example, an NF, RAN node, or AMF can discover an AMF based on NRF interactions (e.g., queries and responses to the NRF). An NF can send a discovery request message (e.g., Nnrf_discoveryRequest), which may include an SNPN ID and / or a configuration entry indication, the requested NF type (e.g., AMF), etc. The NRF can respond with a discovery response message (e.g., Nnrf_discoveryResponse), which may include one or more AMF candidates that support configuration entry or support SNPN.

[0260] Figure 28An example of an RRC setup completion message and elements according to an embodiment of this disclosure is shown. The information element (IE) of the RRC setup completion message may include an SNPN ID indicating network configuration entry. The network (RAN node, AMF, etc.) can use the SNPN ID to discover and select AMFs that support SNPN configuration entry.

[0261] In an exemplary implementation, the IE (such as...) sets the completion message. Figure 28 (in) can include based on Figures 19 to 23 The configuration described herein indicates the IPSec (tunneling) connection to the SNPN. The network can identify, discover, and select an AMF that can support the UE's connection to the second network via an IPSec tunnel / connection. The selected AMF can be a proxy of the second network's AMF or an interoperability function (N3IWF) of the second network (SNPN).

[0262] In an exemplary implementation, such as Figure 29 and Figure 30The configuration described herein enables the UE to obtain network connectivity, thereby providing the UE with the information required to access the PNI-NPN and the vertical network attached to the PNI-NPN. It provides the UE with a public subscription / credential for accessing the PLMN. It can provide the UE with configured access credentials for secondary authentication to allow access to the providing server. These access credentials can be provided during the manufacturing process or configured by the user. It can provide the UE with vertical credentials for secondary / slice authentication to allow access to the vertical network attached to the PNI-NPN. It can provide the UE with UE configurations (e.g., mobility restrictions, URSP, etc.) for CAG selection or DNN / NSSAI selection. The PLMN may be pre-configured with network-side subscriptions / credentials that include at least the minimum set of content possessed by a typical public UE, such as a UE identifier and associated security credentials, optionally supporting instructions and validity periods for configuring network registration. The PLMN may be pre-configured with static vertical configurations (e.g., Subscription Owner (SO) DNN, SO NSSAI), which may include a portion of a subscription that allows UEs to configure network access and access the vertical DN via PNI-NPN. Vertical enterprises may enter into agreements with the PLMN for static vertical subscription assignments. The PLMN may be pre-configured with server routing information (e.g., PS DNN, PSNSSAI, list of allowed PS and / or PS AAA addresses, port ID, SMF selection subscription data, and the allowed number of PDU sessions provided per UE and QoS), which can be used to trigger configuration network access authentication and establish a connection to the intended providing server. The OIMF (Configuration Network Access Message Mapping Function) may be pre-configured with mapping information for PNI-NPN IDs (e.g., CAG ID) and server routing information. Configuration network access credentials can be provided to the PS AAA to authenticate the UE's configuration network access. Configuration network access credentials can be provided out-of-band, such as via an application. Dynamic vertical configuration (e.g., updated CAG information, updated QoS) can be provided to the providing server at the UE level. This can form part of a subscription that allows UEs to configure network access and access vertical DNs via PNI-NPN. Vertical credentials (e.g., N3GPP credentials) can be provided to the providing server to update the NPN credentials of UEs allowed to configure network access. Figure 30The configuration described herein, including the Configuration for Network Access and Provisioning Function (OPF), enables a UE without subscription data to access the Configuration for Network Access SNPN (O-SNPN) to obtain complete provisioning data from the home network that holds the UE's subscription data. This allows the provided UE to access the desired network services normally. The Configuration for Network Access and Provisioning Function (OPF) exists, storing the UE's default configuration and provisioning data, and providing configuration for network access authentication and authorization between the UE and the OPF. The OPF may be located inside or outside the O-SNPN.

[0263] In the example, the UE can query configuration entry information. The UE can register to the PLMN using a public subscription / credentials and can perform primary authentication. The UE manually or automatically discovers and selects a PNI-NPN ID (e.g., CAG ID) for UE configuration entry based on broadcast information. The UE can then request server routing information (e.g., PS DNN, PS NSSAI, list of allowed PS and / or PS AAA addresses, port ID) from the OIMF via a NAS message using the PNI-NPN ID. If the public subscription includes an indication of support for configuration entry registration, the PLMN can provide the UE with restricted registration and PDU sessions for restricted services based on the validity period of the public subscription and additional restrictive information involved in providing server routing information (e.g., SMF selection of subscription data, and the allowed number of PDU sessions provided per UE, the list of allowed PS addresses, and QoS). In the example, registration request messages, RRC messages, RRC setup completion messages, etc., may include OIMF ID, OPF ID, SNPN ID, and the request may be an indication to the OIMF / OPF.

[0264] In the example, the UE can select a slice or DNN to access the PS based on the routing information provided by the server. The UE can use the selected slice to re-register with the PLMN. The UE can use configured access credentials to perform configured access authentication via PS AAA through the 5GC, potentially reusing the secondary authentication procedure triggered by the SMF to achieve configured access authentication. When the UE has been successfully authenticated, the PLMN subscription can be updated, including static vertical subscriptions and dynamic vertical credentials. Static vertical subscriptions (e.g., SO DNN, SO NSSAI) can be pre-configured in the PLMN based on the protocol between the PLMN and the vertical. By using configured access authentication, the 5GC can know the authentication result. If authentication is successful, the 5GC authorizes the UE and updates the UE's subscription according to the pre-configured static vertical subscription. Dynamic vertical subscriptions (e.g., updated CAG information, updated QoS) can be information that the vertical wants to revise regarding the UE's subscription. The PLMN can reject updates to dynamic vertical subscriptions. If the provision is successful, the providing server can transmit the UE's dynamic vertical subscription (e.g., updated CAG information, updated QoS) to the PLMN via the NEF, and the PLMN can update the UE's subscription to obtain the dynamic vertical subscription. The PS can provide UE configuration parameters to the PLMN and provide vertical credentials to the UE. When the UE configuration is updated, the PLMN can update the UE configuration by triggering a UE configuration update procedure. After successful configuration and network access authentication, the UE can be authorized to establish a PDU session to access the PS, and the PS can provide vertical credentials to the UE via the established user plane path and the PDU session. The UE can reuse existing N3GPP credential management protocols with the PS. For example, the CMPv2 protocol can be reused to request a CA to sign a vertical certificate. This credential can be stored in the UE (ME) or UICC. The UE can use the UE configuration parameters and vertical credentials to access the NPN. After the provision procedure, the UE can use the UE configuration to perform a re-registration procedure to reselect the CAG ID, slice, and DNN, and can establish a PDU session with the appropriate QoS. When the UE requests access to the vertical server, the PLMN can trigger secondary / slice authentication, and the UE uses the vertical credentials to process the authentication. After a successful procedure, the UE can initiate regular services to the vertical network via the PNI-NPN. During this procedure, if secondary authentication fails and / or the validity period expires, the PLMN can trigger a network-initiated deregistration.

[0265] Figure 31This illustration shows a call flow for a wireless device (UE) performing registration and access to ON procedures according to an embodiment of this disclosure. The UE may send a registration request procedure to the RAN node. The registration request procedure may be an RRC message, an RRC setup completion message, etc. The registration request message may include an SNPN ID, a target network ID, etc. The registration request message may include a configuration network entry indication. The registration request message may include identifiers such as OPF (OPF ID), OIMF ID, etc. In the example, the SNPN ID, configuration network entry indication, OPF ID, OIMF ID, etc., may be included in a NAS message container of the registration request message. In the example, the SNPN ID, configuration network entry indication, OPF ID, OIMF ID, etc., may be included in the RRC setup completion message. In the example, the UE may register to ON. The UE may send a PDU session establishment request message, a service request message, etc. In the example, the UE may send a NAS message to the AMF (MM-NAS) via the RAN node. The NAS message can be sent from the UE to the SMF (e.g., SM-NAS). In the example, the NAS message may be a PDU session establishment request message, a service request message, a registration request message, etc. In the example, the NAS message may include OPF ID, OIMF ID, target SNPN ID, etc.

[0266] In an exemplary implementation, the presence of the target SNPN ID in an RRC message or NAS message can indicate that the UE is accessing the network to configure network access and provide credentials.

[0267] In an exemplary implementation, the presence of the target SNPN ID in the RRC or NAS message indicates that the UE is accessing the target SNPN (overlay network) via a first network (underlying network), and the PDU session of the first network can be used to establish a connection to the second network via an interoperability function such as N3IWF. The presence of the target SNPN ID in the RRC or NAS message indicates that an underlying network capability is required. This can be an IPSec tunnel or IPSec connection (e.g., IPSec tunnel-based or IPSec transport). This capability or underlying network capability can be SNPN interoperability support, SNPN signaling proxy support, SNPN overlay, or underlying support, etc.

[0268] In an exemplary implementation, when a CP function such as AMF or SMF receives a request from NEF or OA&M or a configuration entity that the network can support configuration for network entry, it can be determined that the network configuration for network entry is supported.

[0269] In an exemplary implementation, when a CP function such as AMF or SMF receives a request from NEF or OA&M or a configuration entity that the network can support configuration for network entry, it can be determined that the network configuration for network entry is supported.

[0270] In the example, the capability indicating SNPN interoperability support, SNPN signaling proxy support, SNPN coverage or underlying support, etc., can instruct the AMF of the underlying network (Network 1) to establish a proxy for the AMF or signaling status or condition of the UE in the coverage network. This capability can instruct the AMF of the underlying network to establish external access or receive notifications to or from the coverage network, etc. This capability can instruct the underlying network to potentially configure an IPSec connection to the coverage network via the interoperability function (N3IWF). The IPSec connection can be between the UE and the N3IWF of the coverage network, or between the UPF of the underlying network and the N3IWF of the coverage network.

[0271] In exemplary embodiments, provisioning may include preparing or equipping a wireless device, network, or network node (or network element) to perform a service by providing one or more parameters to the network or network node. Provisioning may cause the initiation, configuration, activation, or deployment of a process or service on the network node. In response to provisioning, when one or more parameters are provided to the network, the network node may perform an action, activate, deploy a service, or enforce a policy or rule. In an example, provisioning may be performed via a configuration message. In an example, provisioning may include sending configuration messages, modification messages, setting messages, etc., to the network node to enable or activate the network node to perform the desired operation. Provisioning may be performed using an application programming interface (API), direct messaging, or service-based interaction. For example, the Access and Mobility Management Function (AMF) may deploy access and mobility control policies that include providing UE policies to the UE and providing a Radio Access Technology (RAT) Frequency Selection Priority (RFSP) index to the Radio Access Network (RAN).

[0272] In the example, providing policy and charging rules may include sending messages from a first network node to a second network node, containing policies or rules (such as charging rules or policies) based on user subscriptions, wireless devices, service types, PDU session types, QoS flows, etc. The second network node can implement the rules or policies based on elements of the message. For example, the Policy and Charging Control Function (PCF) can provide policy rules to the Session Management Function (SMF) via an interface (e.g., N7) for enforcing or implementing policy and charging control in the SMF and User Plane Function (UPF).

[0273] In the example, providing packet detection and forwarding rules may include providing configuration parameters for activating packet detection and forwarding on the user plane function. The control plane function (network node) can provide packet detection and forwarding rules to the user plane function (UPF). In response to this provision, the UPF can activate or initiate packet detection and forwarding based on the rules.

[0274] In such Figure 32 In the exemplary implementation described herein, a wireless device may send a Radio Resource Control (RRC) message including the Independent Non-Public Network Identifier (SNPN ID) of the second network to a base station of a first network. The wireless device may receive a first message from the Access and Mobility Management Function (AMF) of the first network instructing it to accept registration with the first network. The wireless device may send a second message to the AMF of the first network to establish a Packet Data Unit (PDU) session.

[0275] In the example, the RRC message may include a Closed Access Group Identifier (CAG ID) associated with the configuration for network entry. In the example, based on the CAG ID, the RAN can select an AMF that supports the configuration for network entry, and based on the SNPN ID, the RAN can select an AMF that supports the SNPN for configuration for network entry. In the example, the RRC message may include a configuration for network entry indication. In the example, the RRC message may include a Non-Access Stratum Packet Data Unit (NAS PDU) or a NAS message container. The NAS PDU or NAS message container may include an identifier for the SNPN. The RRC message may be a registration request message. The RRC message may be a service request message. In the example, in response to the RRC message, the radio device can receive a configuration update message from the network (AMF, RAN, etc.) including configuration information for configuration for network entry. The configuration information may include the Data Network Name (DNN) supporting the SNPN for configuration for network entry, the Slice Information (S-NSSAI) supporting the SNPN for configuration for network entry, the identifier of the AMF supporting the SNPN for configuration for network entry, etc. In the example, the network may be a configuration for network entry network (ON). In the example, the configuration for network entry network may be a Public Land Mobile Network (PLMN). In the example, the network to be configured for network access can be a non-public network (NPN). In the example, the network to be configured for network access can be identified by at least one of the Closed Access Group Identifier (CAG ID), S-NSSAI, etc. In the example, the RRC message can be an RRC setup complete message. In the example, the AMF can support configuration for network access to the SNPN. In the example, the AMF can indicate that acceptance of registration to the first network may be for configuration. In the example, the radio device can establish a Packet Data Unit (PDU) session for access to the SNPN. In the example, the radio device can send a PDU session request, which may include a configuration for network access indication (e.g., PDU session type = configuration for network access, request type = configuration for network access, etc.). In the example, the radio device can send a PDU session release message to the base station of the first network (or the first network, the AMF of the first network, the ON of the ON). The radio device can release the PDU session established for configuration for network access. The radio device can send a deregistration message to the base station (or network, AMF, ON). In the example, the radio device can send a second registration request message to the second network (base station, AMF). The wireless device can receive a second registration acceptance message from the second network. The wireless device can send a second PDU session establishment request to the second network (e.g., AMF, RAN).

[0276] In an exemplary implementation, the RRC message may include an indication of underlying network capability support. Underlying network capabilities may include SNPN interoperability support, SNPN signaling broker support, SNPN overlay, or underlying support, etc. In the example, the wireless device may receive a first message (registration acceptance) from an AMF that supports the underlying network capabilities. In the example, the wireless device may send a PDU session establishment request message to the first network, indicating that the PDU session is used for an IPSec tunnel / connection to an N3IWF in the second network. In the example, the wireless device may receive a PDU session acceptance message from the first network. In the example, the wireless device may send an IPSec connection request to the interoperating network node (N3IWF) of the second network via the PDU session (established for IPSec).

[0277] In such Figure 33 In the exemplary implementation depicted, the base station can receive Radio Resource Control (RRC) messages from a radio device. The RRC message may include an identifier of an Independent Non-Public Network (SNPN), such as an SNPN ID. The base station can select an Access and Mobility Management Function (AMF) based on the SNPN identifier or SNPN ID. The base station can send a registration request message to the AMF for configuring network access for the radio device. The base station can also send a registration request message to the AMF for the radio device to access a second network (overlay network).

[0278] In the example, the base station can receive a configuration message, including a configuration entry support indication, from the access and mobility management functions. In the example, the selection can be based on the configuration entry support indication. In the example, the selection can be based on underlying support indications, underlying network capability indications, etc. In the example, the RRC message can include a Closed Access Group Identifier (CAG ID) associated with the configuration entry (e.g., based on the CAG ID, the RAN selects an AMF that supports configuration entry, and based on the SNPN ID: the RAN selects an AMF that supports SNPN configuration entry. In the example, based on the SNPN ID, the RAN selects an AMF that supports SNPN underlying network capabilities). In the example, the base station can select an AMF based on the CAG ID associated with the configuration entry or based on a CAG associated with underlying network support, SNPN interoperability support, SNPN signaling proxy support, etc. In the example, the RRC message can include a configuration entry indication. The RRC message can include a Non-Access Stratum Packet Data Unit (NAS PDU, NAS container, etc.) that includes an SNPN identifier. The RRC message can be a registration request message. The selection of the AMF can be based on the base station's determination that configuration entry is required. This determination can be based on the SNPN ID.

[0279] In such Figure 34In the exemplary implementation depicted, the base station can receive a Radio Resource Control (RRC) message from a radio device. The RRC message may include an identifier for an Independent Non-Public Network (SNPN). The base station can determine that the Access and Mobility Management Function (AMF) does not support SNPN configuration for network entry. The base station can send a rejection message to the radio device indicating that configuration for network entry is not supported.

[0280] In such Figure 35 In the exemplary implementation depicted, the base station can receive Radio Resource Control (RRC) messages from a radio device. The RRC message may include an underlying network capability support indication, an Identifier of Independent Non-Public Network (SNPNID), an NPN ID, etc. The base station can determine that the Access and Mobility Management Function (AMF) does not support the underlying network capabilities of the SNPN. The base station can send a rejection message to the radio device indicating that the underlying network capabilities are not supported.

[0281] According to various implementation schemes, one or more devices, such as wireless devices, off-network wireless devices, base stations, core network devices, etc., may be employed in the system. One or more devices may be configured to perform specific operations or actions by installing software, firmware, hardware, or combinations thereof on one or more devices, which, in operation, cause or induce one or more devices to perform actions. One or more computer programs may be configured to perform specific operations or actions by including instructions that, when executed by a data processing device, cause the device to perform the action. Embodiments of exemplary actions are illustrated in the accompanying drawings and specification. Features from various implementation schemes can be combined to create other implementation schemes.

[0282] In this specification, “a” (“a” and “an”) and similar phrases will be interpreted as “at least one” and “one or more”. In this specification, the term “may” is interpreted as “may, for example.” In other words, the term “may” indicates that the phrase following the term “may” is an example of one of a variety of suitable possibilities that may or may not be used in one or more of various examples. If A and B are sets, and every element of A is also an element of B, then A is called a subset of B. In this specification, only non-empty sets and subsets are considered. For example, possible subsets of B = {cell1, cell2} are: {cell1}, {cell2}, and {cell1, cell2}.

[0283] Various examples are disclosed in this specification. Limitations, features, and / or elements from the disclosed exemplary embodiments may be combined to create further examples within the scope of this disclosure.

[0284] Various examples are disclosed in this specification. Limitations, features, and / or elements from the disclosed exemplary embodiments may be combined to create further examples within the scope of this disclosure.

[0285] In this specification, a parameter (information element: IE) may include one or more objects, and one of these objects may include one or more other objects. For example, if parameter (IE)N includes parameter (IE)M, and parameter (IE)M includes parameter (IE)K, and parameter (IE)K includes parameter (information element)J, then, for example, N includes K, and N includes J. In the example, when one or more messages include multiple parameters, it means that a parameter among the multiple parameters is in at least one of the one or more messages, but not necessarily in one of the one or more messages.

[0286] Many of the elements described in the disclosed examples can be implemented as modules. A module is defined herein as a separable element that performs a defined function and has a defined interface to other elements. The modules described in this disclosure can be implemented in hardware, software combined with hardware, firmware, wet hardware (i.e., hardware with biological elements), or combinations thereof, some of which are behaviorally equivalent. For example, a module can be implemented as software routines written in a computer language configured to be executed by a hardware machine (e.g., C, C++, Fortran, Java, Basic, Matlab, etc.) or a modeling / simulation program (e.g., Simulink, Stateflow, GNU Octave, or LabVIEW MathScript). Alternatively, it is possible to implement modules using physical hardware incorporating discrete or programmable analog, digital, and / or quantum hardware. Examples of programmable hardware include: computers; microcontrollers; microprocessors; application-specific integrated circuits (ASICs); field-programmable gate arrays (FPGAs); and complex programmable logic devices (CPLDs). Computers, microcontrollers, and microprocessors are programmed using languages ​​such as assembly, C, and C++. FPGAs, ASICs, and CPLDs are frequently programmed using hardware description languages ​​(HDLs), such as VHSIC Hardware Description Language (VHDL) or Verilog. These languages ​​configure connections between relatively small internal hardware modules on a programmable device. Finally, it is important to emphasize that the above techniques are often used in combination to achieve the desired functional modules.

[0287] The disclosure of this patent document incorporates copyrighted material. The copyright holder does not object to anyone making an exact copy of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office's patent documents or records for limited purposes required by law, but otherwise reserves all copyright rights.

[0288] Although various examples have been described above, it should be understood that they are presented by way of example rather than limitation. It will be apparent to those skilled in the art that various changes in form and detail may be made without departing from the spirit and scope of this disclosure. Indeed, after reading the above description, it will be apparent to those skilled in the art how to implement alternative examples. Therefore, the present examples should not be limited to any of the exemplary examples described above. In particular, it should be noted that for illustrative purposes, the above explanation has focused on examples using 5G AN. However, those skilled in the art will recognize that examples of the invention can be implemented in systems including one or more legacy systems or LTE. The disclosed methods and systems can be implemented in wireless or wired systems. Features of the various examples presented in this invention can be combined. One or more features (methods or systems) of one example can be implemented in other examples. A limited number of example combinations are shown to indicate to those skilled in the art the possibility of combining features from various examples to create enhanced transmission and reception systems and methods.

[0289] Furthermore, it should be understood that any diagrams highlighting features and benefits are presented for illustrative purposes only. The disclosed architecture is flexible and configurable enough that it can be utilized in ways other than those shown. For example, the actions listed in any flowchart can be reordered or used only optionally in certain examples.

[0290] Furthermore, the purpose of this abstract is to enable the U.S. Patent and Trademark Office and the general public, especially scientists, engineers, and practitioners unfamiliar with patent or legal terminology, to quickly determine the nature and substance of the technical disclosure of this application through a cursory examination. This abstract is not intended to limit the scope in any way.

[0291] Finally, the applicant's intention is that only claims including the phrases "apparatus for..." or "steps for..." should be interpreted according to 35 USC 112. Claims that do not explicitly include the phrases "device for..." or "steps for..." should not be interpreted according to 35 USC 112.

Claims

1. A method for accessing a second network, the method comprising: The first access and mobility management function (AMF) of the first network receives a forwarded registration request from the radio access network (RAN) node. The registration request is used for a radio device to configure its network access to the second network. If the radio device is in connected mode or the RAN node cannot select an appropriate AMF, the RAN node forwards the registration request. The first AMF sends a discovery request to the Network Storage Function (NRF) of the first network. The discovery request is used to discover the AMF that supports the configuration for network access of the wireless device. The discovery request includes a configuration for network access support indication. The first AMF receives a discovery response message from the NRF, the discovery response message including information on AMF candidates that support configuration for network entry.

2. The method of claim 1, wherein the discovery request includes the identifier of the second network.

3. The method of claim 1, wherein configuring network access includes the first network providing the wireless device with information for the wireless device to obtain authorized access and connection to the second network.

4. The method according to any one of claims 1 to 3, wherein: The first network is one or more of the following: Configure the network access; First public land mobile network; The first non-public network; and The first independent non-public network; and The second network is one or more of the following: Configure the network access; Second public land mobile network; A second non-public network; and A second independent, non-public network.

5. A first access and mobility management function (AMF), the first AMF comprising: One or more processors; and A memory for storing instructions that, when executed by the one or more processors, cause the first AMF to perform the method as described in any one of claims 1 to 4.

6. A method for accessing a second network, the method comprising: The network repository function (NRF) of the first network receives a discovery request from the first access and mobility management function (AMF) of the first network. The discovery request is used to discover an AMF that supports configuration access for wireless devices to the second network. The discovery request includes a configuration access support indication. The NRF sends a discovery response message to the first AMF, the discovery response message including information on AMF candidates that support configuration for network entry.

7. The method of claim 6, wherein the discovery request includes an identifier of the second network.

8. The method of claim 6, wherein the configuration for network access includes the first network providing the wireless device with information for the wireless device to obtain authorized access and connection to the second network.

9. The method of any one of claims 6 to 8, wherein: The first network is one or more of the following: Configure the network access; First public land mobile network; The first non-public network; and The first independent non-public network; and The second network is one or more of the following: Configure the network access; Second public land mobile network; A second non-public network; and A second independent, non-public network.

10. A network repository function, comprising: One or more processors; and A memory for storing instructions that, when executed by the one or more processors, cause the network storage function to perform the method as described in any one of claims 6 to 9.

11. A non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform the method as described in any one of claims 1 to 4 or 6 to 9.

Images