Method, apparatus and system for session management in aviation systems

Abstract

A mobility management function receives a registration request message for the wireless device from a wireless device. The mobility management function determines an authentication and / or authorization (AA) for an aviation service of the wireless device. The mobility management function receives a request for session establishment for the aviation service from the wireless device. The mobility management function sends an indication of the AA for the aviation service of the wireless device to a session management function (SMF) based on the request for the session establishment.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to U.S. Provisional Application No. 63 / 086,572, filed on October 1, 2020, the entire contents of which are hereby incorporated by reference. Technical Field

[0003] The embodiments provided in the present application generally relate to a session management method for an aviation system, an access and mobility management function AMF device for session management of an aviation system, and a session management system for an aviation system. Background Art

[0004] In the prior art, a wireless device (e.g., a UAS, a UAV, a UAV controller, etc.) may request to establish one or more sessions (e.g., a PDU session, a PDN connection, etc.). One or more sessions may be used for aviation services (e.g., aviation system services, UAS services, etc.). In order to establish one or more sessions, the wireless device may send a request to a session management entity (SME, e.g., a session management function (SMF), a mobility management entity (MME), etc.). It may be necessary (e.g., required) to determine the authentication and / or authorization (AA) of the wireless device (e.g., before the session can be established and / or the request can be accepted by the SME). The AA may require one or more communications between the wireless device and / or the network and a traffic manager (e.g., a UAS traffic management (UTM) or a UAS service provider (USS)). When the need (e.g., requirement) for AA for aviation services is introduced, the prior art for session management (e.g., request, establish, modify, accept, reject, etc.) may cause delays, ambiguity, and / or signaling overhead. For example, a wireless device may request the establishment of a session associated with an aviation service. At the time of the request, the AA may be incomplete and / or the result of the AA procedure may be unknown. As a result, the request may be denied, retried and denied again, accepted after a delay, etc. Additionally or alternatively, the request may be accepted without the necessary AA, resulting in an unauthorized and / or inoperable session. Summary of the invention

[0005] The first embodiment of the present application provides a session management method for an aviation system, the method comprising: receiving, by an access and mobility management function AMF device, a registration request message for the wireless device from a wireless device; triggering, by the AMF device, an authentication and / or authorization procedure for the aviation service of the wireless device; receiving, by the AMF device, a protocol data unit PDU session establishment request from the wireless device to establish a PDU session associated with the aviation service; and based on receiving the PDU session establishment request from the wireless device, sending, by the AMF device, a create session management context message to a session management function SMF device, the create session management context message including an indication of whether the aviation service of the wireless device has been authenticated and / or authorized by an unmanned aerial system service provider USS.

[0006] In the second embodiment of the method described in the first embodiment of the present application, the AMF device also includes receiving an indication from the SMF device whether to accept the PDU session establishment request.

[0007] In a third embodiment of the method described in accordance with the first embodiment of the present application, the method further includes sending a protocol data unit session establishment rejection message to the wireless device, wherein the protocol data unit session establishment rejection message indicates a rejection of the PDU session establishment request and includes a cause value associated with the rejection.

[0008] In a fourth embodiment of the method according to the first embodiment of the present application, the create session management context message indicating whether the aviation service of the wireless device has been authenticated and / or authorized by the USS is a create session management context request message.

[0009] In a fifth embodiment of the method according to the first embodiment of the present application, the registration request message of the wireless device includes an aircraft identifier of the wireless device.

[0010] In a sixth embodiment of the method according to the first embodiment of the present application, the PDU session is used to communicate with the USS.

[0011] In a seventh embodiment of the method described in accordance with the first embodiment of the present application, the PDU session is used for command and control C2 communication of the USS.

[0012] In an eighth embodiment of the method described in the first embodiment of the present application, performing the authentication and / or authorization procedure includes sending an authentication and / or authorization request by the AMF device to the USS.

[0013] In a ninth embodiment of the method according to the eighth embodiment of the present application, the authentication and / or authorization request includes an aviation service identifier of the wireless device.

[0014] In a tenth embodiment of the method according to the eighth embodiment of the present application, the method according to the eighth embodiment of the present application, wherein the authentication and / or authorization request includes a universal public subscription identifier GPSI of the wireless device.

[0015] The eleventh embodiment of the present application provides an access and mobility management function AMF device for session management of an aviation system, comprising one or more processors and a memory storing instructions, wherein the instructions, when executed by the one or more processors, enable the AMF device to: receive a registration request message for the wireless device from a wireless device; trigger an authentication and / or authorization procedure for the aviation service of the wireless device; receive a protocol data unit PDU session establishment request from the wireless device to establish a PDU session associated with the aviation service; and based on receiving the PDU session establishment request from the wireless device, send a create session management context message to a session management function SMF device, wherein the create session management context message includes an indication of whether the aviation service of the wireless device has been authenticated and / or authorized by an unmanned aerial system service provider USS.

[0016] In the twelfth embodiment of the device described in accordance with the eleventh embodiment of the present application, the AMF device also includes receiving an indication from the SMF device whether to accept the PDU session establishment request.

[0017] In the thirteenth embodiment of the apparatus according to the eleventh embodiment of the present application, it also includes sending a protocol data unit session establishment rejection message to the wireless device, wherein the protocol data unit session establishment rejection message indicates the rejection of the PDU session establishment request and includes a cause value associated with the rejection.

[0018] In a fourteenth embodiment of the apparatus according to the eleventh embodiment of the present application, the create session management context message indicating whether the aviation service of the wireless device has been authenticated and / or authorized by the USS is a create session management context request message.

[0019] In a fifteenth embodiment of the apparatus according to the eleventh embodiment of the present application, the registration request message of the wireless device includes an aircraft identifier of the wireless device.

[0020] In a sixteenth embodiment of the apparatus according to the eleventh embodiment of the present application, the PDU session is used to communicate with the USS.

[0021] In the seventeenth embodiment of the apparatus according to the eleventh embodiment of the present application, the PDU session is used for command and control C2 communication of the USS.

[0022] In the eighteenth embodiment of the device described in the eleventh embodiment of the present application, performing the authentication and / or authorization procedure includes sending an authentication and / or authorization request by the AMF device to the USS.

[0023] In a nineteenth embodiment of the apparatus according to the eighteenth embodiment of the present application, the authentication and / or authorization request includes an aviation service identifier of the wireless device.

[0024] In a twentieth embodiment of the apparatus according to the eighteenth embodiment of the present application, the authentication and / or authorization request includes a universal public subscription identifier (GPSI) of the wireless device.

[0025] The twenty-first embodiment of the present application provides a session management system for an aviation system, comprising: an access and mobility management function AMF device, the AMF device comprising one or more first processors and a first memory storing instructions, the instructions, when executed by the one or more first processors, enable the AMF device to: receive a registration request message for the wireless device from a wireless device; trigger an authentication and / or authorization procedure for an aviation service of the wireless device; receive a protocol data unit PDU session establishment request from the wireless device to establish a PDU session associated with the aviation service; and based on receiving the PDU session establishment request from the wireless device, send a create session management context message to a session management function SMF device. The AMF device comprises: a create session management context message, wherein the create session management context message indicates whether the aviation service of the wireless device has been authenticated and / or authorized by an unmanned aerial system service provider USS; and the SMF device, wherein the SMF device comprises: one or more second processors and a second memory storing instructions, wherein the instructions, when executed by the one or more second processors, enable the SMF device to: receive the create session management context message from the AMF device, wherein the create session management context message includes an indication of whether the aviation service of the wireless device has been authenticated and / or authorized by the USS; and determine to accept or reject the session management context request of the wireless device based on whether the aviation service of the wireless device has been authenticated and / or authorized. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0027] Figure 1is a diagram of an example 5G system architecture according to aspects of an implementation of the present disclosure.

[0028] Figure 2 is a diagram of an example 5G system architecture according to aspects of an implementation of the present disclosure.

[0029] Figure 3 A system diagram of example wireless devices and network nodes in a 5G system according to aspects of an implementation of the present disclosure.

[0030] Figure 4 is a system diagram of an example wireless device according to aspects of an embodiment of the present disclosure.

[0031] Figure 5A and Figure 5B Two registration management state models in UE 100 and AMF 155 are depicted according to aspects of embodiments of the present disclosure.

[0032] Fig. 6A and Figure 6B Two connection management state models in UE 100 and AMF 155 according to aspects of embodiments of the present disclosure are depicted.

[0033] Figure 7 is a diagram for classifying and marking traffic according to aspects of an embodiment of the present disclosure.

[0034] Figure 8 An exemplary calling flow according to aspects of the embodiments of the present disclosure.

[0035] Fig. 9 An exemplary calling flow according to aspects of the embodiments of the present disclosure.

[0036] Fig.10 An exemplary calling flow according to aspects of the embodiments of the present disclosure.

[0037] Fig.11 An exemplary calling flow according to aspects of the embodiments of the present disclosure.

[0038] Fig.12 An exemplary calling flow according to aspects of the embodiments of the present disclosure.

[0039] Fig.13 An exemplary calling flow according to aspects of the embodiments of the present disclosure.

[0040] Fig.14 An example of an exemplary mobile communication network according to aspects of embodiments of the present disclosure is shown.

[0041] Fig.15The service-based architecture of a 5G network is shown with respect to the interaction between the control plane (CP) and the user plane (UP).

[0042] Fig.16 An exemplary architecture of a UAS according to an embodiment of the present disclosure is shown.

[0043] Fig.17 An exemplary scenario is shown of how a UAV interacts with a base station with respect to interference according to an embodiment of the present disclosure.

[0044] Fig.18 An exemplary architecture of a UAS regarding interfaces according to an embodiment of the present disclosure is shown.

[0045] Fig.19 An exemplary registration procedure for authentication and / or authorization (AA) of aviation services according to an embodiment of the present disclosure is shown.

[0046] Fig. 20 An exemplary service-specific AA procedure according to an embodiment of the present disclosure is shown.

[0047] Fig. 20 An exemplary procedure of impending communication failure handling by a base station with a wireless device and a control server according to an embodiment of the present disclosure is shown.

[0048] Fig.21 An exemplary session handling procedure of a 5G network according to an embodiment of the present disclosure is shown.

[0049] Fig. 22 An exemplary session handling procedure of a 5G network according to an embodiment of the present disclosure is shown.

[0050] Fig.23 An exemplary session modification procedure for a 5G network according to an embodiment of the present disclosure is shown.

[0051] Fig.24 A 4G system (eg, Evolved Packet System) including an access network and a 4G core network according to an embodiment of the present disclosure is depicted.

[0052] Fig.25 An exemplary session handling procedure of a 4G network according to an embodiment of the present disclosure is shown.

[0053] Fig.26 An exemplary session handling procedure of a 4G network according to an embodiment of the present disclosure is shown. DETAILED DESCRIPTION

[0054] The exemplary embodiments of the present invention enable enhanced features and functions to be implemented in 4G / 5G systems. The embodiments of the technology disclosed herein can be used in the technical field of 4G / 5G systems and network slicing for communication systems. More specifically, the embodiments of the technology disclosed herein can relate to a 5G core network and a 5G system for network slicing in a communication system. Throughout the present disclosure, UE, wireless device, terminal and mobile device are used interchangeably. Throughout the present disclosure, base station, (radio) access network ((R)AN), next generation radio access network (NG-RAN), new radio node B (gNB), next generation eNodeB (ng-eNB) are used interchangeably. Throughout the present disclosure, base station, radio access network (RAN), eNodeB are used interchangeably.

[0055] Throughout this disclosure, FNF, SNF, CHF, AMF, SMF, UPF, PCF, UDM, OAM, AF are exemplary network functions that may 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 virtualized functions instantiated on an appropriate platform.

[0056] The following abbreviations are used throughout this disclosure:

[0057] 3GPP 3rd Generation Partnership Project

[0058] 5G 5th generation mobile network

[0059] 5GC5G core network

[0060] 5G-GUTI5G Globally Unique Temporary Identifier

[0061] 5GS5G system

[0062] 5G-AN5G access network

[0063] 5QI5G QoS Indicator

[0064] ACK

[0065] AF application function

[0066] A-GNSSAssisted GNSS

[0067] AMBR Aggregate Maximum Bit Rate

[0068] AMF access and mobility management function

[0069] AN access network

[0070] ANDSP access network discovery and selection strategy

[0071] APN Access Point Name

[0072] ARP allocation and reservation priority

[0073] BD billing domain

[0074] BPS Air Pressure Sensor

[0075] CCNF Common Control Network Function

[0076] CDR charging data record

[0077] CHF charging function

[0078] CIoTCellular IoT

[0079] CN Core Network

[0080] CP Control Plane

[0081] C-V2X Cellular Vehicle-to-Everything (C-V2X)

[0082] DAB Digital Audio Broadcasting

[0083] DDN Downlink Data Notification

[0084] DDoS Distributed Denial of Service

[0085] DL Downlink

[0086] DN Data Network

[0087] DN-AAA Data Network Authentication Authorization and Accounting

[0088] DNN data network name

[0089] DRX Discontinuous Reception

[0090] DTMB Digital Terrestrial Multimedia Broadcasting

[0091] ECGIE - UTRAN Cell Global Identifier

[0092] ECID Enhanced Cell Identifier

[0093] eNodeB Evolved Node B

[0094] EPS Evolution Package System

[0095] E-UTRAN Evolved Universal Terrestrial Radio Access Network

[0096] FDD Frequency Division Duplex

[0097] FNF First Network Function

[0098] FQDN Fully Qualified Domain Name

[0099] F-TEID Fully Qualified TEID

[0100] GAD Geographic Area Description

[0101] GMLC Gateway Mobile Location Center

[0102] gNBNext Generation Node B

[0103] gNB-CU-CPgNB Central Unit Control Plane

[0104] GNSS Global Navigation Satellite System

[0105] GPSI General Public Subscription Identifier

[0106] GTPGPRS Tunneling Protocol

[0107] GUTI Globally Unique Temporary Identifier

[0108] GW Gateway

[0109] HGMLC Home GMLC

[0110] HPLMN Local Public Land Mobile Network

[0111] HSS Home Subscriber Server

[0112] HTC Holographic Communication

[0113] HTTP Hypertext Transfer Protocol

[0114] ID Identifier

[0115] IMEI International Mobile Equipment Identity

[0116] IMEI DBIMEI database

[0117] IMSIP Multimedia Subsystem

[0118] IMSI International Mobile Subscriber Identity

[0119] Internet Protocol (IP)

[0120] IP-CANIP connection access network

[0121] L2 Layer 2 (Data Link Layer)

[0122] L3 Layer 3 (Network Layer)

[0123] LAN

[0124] LADN Local Area Network Data Network

[0125] LCS Positioning Service

[0126] LI Lawful Interception

[0127] LMC location management component

[0128] LMF positioning management function

[0129] LPPLTE positioning protocol

[0130] LRF direction search function

[0131] MAC Media Access Control

[0132] MEI Mobile Equipment Identifier

[0133] MICO only initiates connections on mobile

[0134] MME mobility management entity

[0135] MO Mobile Origination

[0136] MO-LR Mobile Originated Location Request

[0137] MSISDN Mobile Subscriber ISDN

[0138] MT Mobile Termination

[0139] MT-LR Mobile Termination Location Request

[0140] N3IWF non-3GPP interworking function

[0141] NAI Network Access Identifier

[0142] NAS non-access layer

[0143] NAS-MM Non-Access Stratum Mobility Management

[0144] NAS-SM Non-Access Stratum Session Management

[0145] NAT Network Address Translation

[0146] NB-IoT Narrowband IoT

[0147] NCGINR Community Global Logo

[0148] NEF network exposure function

[0149] NF Network Function

[0150] NGAP Next Generation Application Protocol

[0151] ng-eNB Next generation eNB

[0152] NG-RANNR Radio Access Network

[0153] NI-LR network induced positioning request

[0154] NR New Radio

[0155] NRF Network Repository Features

[0156] NRPPa New Radiolocation Protocol A

[0157] NSI network slicing example

[0158] NSSAI Network Slice Selection Assistance Information

[0159] NSSF network slice selection function

[0160] NWDAF network data analysis function

[0161] OAM operation management and maintenance

[0162] OCS Online Charging System

[0163] OFCS Offline Toll Collection System

[0164] OTDOA Observed Time Difference of Arrival

[0165] PCC Strategy and Charge Control

[0166] PCF policy control function

[0167] PCRF policy and charging rules function

[0168] PDN Packet Data Network

[0169] PDU packet / protocol data unit

[0170] PEI Persistent Equipment Identifier

[0171] PGWPDN Gateway

[0172] PLMN Public Land Mobile Network

[0173] PRACH Physical Random Access Channel

[0174] PLMN Public Land Mobile Network

[0175] ProSe Proximity-Based Services

[0176] PSAPDU Session Anchor

[0177] RAN Radio Access Network

[0178] QFIQoS flow identification

[0179] QoS Quality of Service

[0180] RM Registration Management

[0181] RA Random Access

[0182] RAN Radio Access Network

[0183] RAT Radio Access Technology

[0184] RRC Radio Resource Control

[0185] RM Registration Management

[0186] S1-APS1 Application Protocol

[0187] SBA Service-Based Architecture

[0188] SEA Safety Anchor Function

[0189] SCM Security Context Management

[0190] SEA Safety Anchor Function

[0191] SETSUPL Enable Terminal

[0192] SGW Service Gateway

[0193] SI system information

[0194] SIB System Information Block

[0195] SLPSUPL Location Platform

[0196] SM Session Management

[0197] SMF session management function

[0198] SMSFSMS Function

[0199] S-NSSAI Single Network Slice Selection Auxiliary Information

[0200] SS sync signal

[0201] SSC Session and Service Continuity

[0202] SUCI service user correlation ID

[0203] SUPI Subscriber Persistent Identifier

[0204] SUPL Secure User Plane Location

[0205] TA tracking area

[0206] TAI Tracking Area Identifier

[0207] TBS Ground Beacon System

[0208] TCP Transmission Control Protocol

[0209] TEID Tunnel Endpoint Identifier

[0210] TMSI Temporary Mobile Subscriber Identity

[0211] TNAN Trusted Non-3GPP Access Network

[0212] TNGF Trusted Non-3GPP Gateway

[0213] TRP Transmission and Reception Points

[0214] UAS unmanned aerial system, unmanned aerial system

[0215] UAV unmanned aerial vehicle

[0216] UAVCUAV Controller

[0217] UDM Unified Data Management

[0218] UDP User Datagram Protocol

[0219] UDR User Data Repository

[0220] UE User Equipment

[0221] UL Uplink

[0222] UL CL Uplink Classifier

[0223] UPF user plane function

[0224] USSUAS Service Providers

[0225] UTMUAS Traffic Management

[0226] UPF user plane function

[0227] V2X

[0228] VPLMN Access to Public Land Mobile Network

[0229] WLAN Wireless Local Area Network

[0230] XMLExtensible Markup Language

[0231] Example Figure 1 and Figure 2 A 5G system including an access network and a 5G core network is depicted. The example 5G access network may include an access network connected to a 5G core network. The access network may include an NG-RAN 105 and / or a non-3GPP AN 165. The example 5G core network may be connected to one or more 5G access networks 5G-ANs and / or NG-RANs. The 5G core network may include a 5G core network as shown in the example Figure 1 and examples Figure 2 A functional element or network function in which an interface can be used for communication between the functional elements and / or network elements.

[0232] In an example, a network function may be a processing function in a network, which may have functional behaviors and / or interfaces. A network function may be implemented as a network element on dedicated hardware and / or as Figure 3 and Figure 4 The network nodes depicted in are either implemented as software instances running on dedicated hardware and / or shared hardware, or as virtual functions instantiated on an appropriate platform.

[0233] In an example, the access and mobility management function 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 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 interface with 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 AUSF 150 and UE 100, receiving intermediate keys established as a result of the UE 100 authentication process, security context management SCM receiving keys from SEA for deriving access network specific keys, and the like.

[0234] In an example, the AMF 155 may support non-3GPP access networks through an N2 interface with the N3IWF 170, support NAS signaling with the UE 100 through the N3IWF 170, support authentication of UEs connected through the N3IWF 170, mobility management, authentication, and separate security context states for UEs 100 connected via a non-3GPP access 165 or simultaneously connected via a 3GPP access 105 and a non-3GPP access 165, support a coordinated RM context valid through the 3GPP access 105 and the non-3GPP access 165, support a CM management context for the UE 100 for connectivity through the non-3GPP access, and the like.

[0235] In an example, an AMF 155 region may include one or more AMF 155 sets. An AMF 155 set may include some AMF 155 serving a given region and / or network slice. In an example, multiple AMF 155 sets may be per AMF 155 region and / or network slice. An application identifier may be an identifier that may be mapped to a specific application traffic detection rule. A configured NSSAI may be an NSSAI that may be provided in the UE 100. For a DNN, a DN 115 access identifier (DNAI) may be an identifier of a user plane access DN 115. An initial registration may be related to a UE 100 registration in an RM-DEREGISTERED 500, 520 state. An N2AP UE 100 association may be a logical association between a 5G AN node and an AMF 155 according to a UE 100. An N2AP UE-TNLA association may be a combination between an N2AP UE 100 association and a specific transport network layer, a TNL association for a given UE 100.

[0236] In an 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 the SMF 160): session management (e.g., session establishment, modification, and release, including tunnel maintenance between the UPF 110 and AN 105 nodes), UE 100 IP address allocation and management (including optional authorization), selection and control of UP functions, configuring traffic steering at the UPF 110 to route traffic to the appropriate destination, terminating interfaces for policy control functions, controlling part of policy enforcement and QoS, lawful interception (for SM events and interface with LI system), terminating the SM part of NAS messages, downlink data notification, initiating AN-specific SM information, sent to (R)AN 105 via AMF 155 over N2, determining the SSC mode of the session, roaming functions, handling local execution to apply QoS SLA (VPLMN), charging data collection and charging interface (VPLMN), lawful interception (in VPLMN, for SM events and interface with LI system), supporting communication with external DN 115 to transmit signaling for PDU session authorization / authentication by external DN 115, etc.

[0237] In an 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 point for intra-RAT / inter-RAT mobility (if applicable), external PDU session point for interconnection to DN 115, packet routing and forwarding, packet inspection and user plane portion of policy rule enforcement, lawful interception (UP acquisition), traffic usage reporting, uplink classifier to support routed traffic flows for data networks, branch point to support multi-homed PDU sessions, QoS processing for user plane, uplink traffic validation (SDF to QoS flow mapping), transport level packet marking in uplink and downlink, downlink packet buffering, downlink data notification triggering, and the like.

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

[0239] In an exemplary embodiment, the 5GC elements and UE 100 may support the following mechanisms: 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 via DHCPv4 may be used. If IPv6 is supported, IPv6 prefix allocation may be supported via IPv6 stateless auto-configuration. In an example, the 5GC network element may support IPv6 parameter configuration via stateless DHCPv6.

[0240] 5GC may support allocation of static IPv4 addresses and / or static IPv6 prefixes based on subscription information in UDM 140 and / or based on configuration on a per-subscriber, per-DNN basis.

[0241] The user plane function (UPF 110) may handle the user plane path of the PDU session. The UPF 110 providing an interface to a data network may support the function of a PDU session anchor.

[0242] In an example, the policy control function PCF 135 may support a unified policy framework to control network behavior, provide policy rules to control plane functions to enforce policy rules, implement a front end to access subscription information related to policy decisions in a user data repository (UDR), and so on.

[0243] The network exposure function NEF 125 may provide a means to securely expose services and capabilities provided by 3GPP network functions, convert between information exchanged with AF 145 and information exchanged with internal network functions, receive information from other network functions, and so on.

[0244] In an example, the network repository function NRF 130 may support a service discovery function that may receive an NF discovery request from a NF instance, provide information about discovered NF instances (to be discovered) to the NF instance, and maintain information about available NF instances and their supported services, etc.

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

[0246] In an example, the data stored in the UDR may include at least user subscription data, including at least a subscription identifier, security credentials, access and mobility-related subscription data, session-related subscription data, policy data, and the like.

[0247] In an example, the AUSF 150 may support authentication server functionality (AUSF 150).

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

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

[0250] In an example, the 5GC may provide policy information from the PCF 135 to the UE 100. In an example, the policy information may include: access network discovery and selection policy, UE 100 routing selection policy (URSP), SSC mode selection policy (SSCMSP), network slice selection policy (NSSP), DNN selection policy, non-seamless offload policy, and the like.

[0251] In the example, as in Figure 5A and Figure 5B As depicted in the figure, the registration management RM can be used to register or deregister the UE / user 100 in the network and establish a user context in the network. The connection management can be used to establish and release the signaling connection between the UE 100 and the AMF 155.

[0252] In an example, the UE 100 may register on the network to receive services for which registration is requested. In an example, the UE 100 may periodically update its registration on the network to maintain reachability (periodic registration update), or update when moving (e.g., mobile registration update), or update its capabilities or renegotiate protocol parameters.

[0253] In the example, as in the example Figure 8 and Fig. 9 The initial registration procedure depicted in may involve performing network access control functions (eg, user authentication and access authorization based on a subscription profile in UDM 140). Fig. 9 yes Figure 8 A continuation of the initial registration procedure depicted in . As a result of the initial registration procedure, the identity of the serving AMF 155 can be registered in the UDM 140.

[0254] In an example, the Registration Management RM procedure may be applied on both the 3GPP access 105 and the non-3GPP access 165 .

[0255] Example Figure 5AThe RM states of the UE 100 as observed by the UE 100 and the AMF 155 may be depicted. In an exemplary embodiment, two RM states may be employed in the UE 100 and the AMF 155 that may reflect the registration state of the UE 100 in the selected PLMN: RM-DEREGISTERED 500 and RM-REGISTERED 510. In an example, in the RM-DEREGISTERED state 500, the UE 100 may not be registered in the network. The UE 100 context in the AMF 155 may not hold valid positioning or routing information for the UE 100, and thus the UE 100 may not be reachable through the AMF 155. In an example, the UE 100 context may be stored in the UE 100 and the AMF 155. In an example, in the RM REGISTERED state 510, the UE 100 may be registered on the network. In the RM-REGISTERED 510 state, the UE 100 may receive services that may require registration on the network.

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

[0257] As an example Fig. 6A and Figure 6B As depicted in , the connection management CM may include establishing and releasing a signaling connection between the UE 100 and the AMF 155 over the N1 interface. The signaling connection may be used to implement NAS signaling exchanges between the UE 100 and the core network. The signaling connection between the UE 100 and the AMF 155 may include both an AN signaling connection between the UE 100 and the (R)AN 105 (e.g., an RRC connection accessed via 3GPP) and an N2 connection of the UE 100 between the AN and the AMF 155. In an example, the signaling connection may be an N1 signaling connection. In an example, the signaling connection may be an N1 NAS signaling connection.

[0258] As an example Fig. 6A and Figure 6BAs depicted in , for the NAS signaling connection of the UE 100 with the AMF 155, two CM states may be adopted, namely CM-IDLE 600, 620 and CM-CONNECTED 610, 630. The UE 100 in the CM-IDLE 600 state may be in the RM-REGISTERED 510 state and may not have a NAS signaling connection established with the AMF 155 through N1. The UE 100 in the CM-IDLE 600 state may be in the RRC idle state. The UE 100 may perform cell selection, cell reselection, PLMN selection, etc. The UE 100 in the CM-CONNECTED 610 state may have a NAS signaling connection with the AMF 155 through N1. In the example, the UE 100 in the CM-CONNTED 610 state may be in the RRC connected state. The UE 100 in the CM-CONNTECTED 610 state may be in an RRC inactive state. In an example, the CM state in the AMF and the CM state in the UE may be different. This may be the case when a local state change occurs without an explicit signaling procedure (e.g., UE context release procedure) between the UE and the AMF. In an example, the RRC state in the UE (e.g., wireless device) and the RRC state in the base station (e.g., gNB, eNB) may be different. This may be the case when a local state change occurs without an explicit signaling procedure (e.g., RRC release procedure) between the UE and the base station.

[0259] In an exemplary embodiment, for the UE 100 at the AMF 155, two CM states, CM-IDLE 620 and CM-CONNECTED 630, may be employed.

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

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

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

[0263] In an example, for CM-IDLE 600, 620 states, two UE 100 reachability categories may be negotiated between the UE 100 and the AMF 155. 1) When the UE 100 is in CM-IDLE 600 mode, UE 100 reachability allows mobile device termination of data. 2) Mobile Initiated Connection Only (MICO) mode. The 5GC may support a PDU connection service that provides for PDU exchange between the UE 100 and a data network identified by a DNN. The PDU connection service may be supported via a PDU session established at the request of the UE 100.

[0264] In an example, a PDU session may support one or more PDU session types. A PDU session may be established (e.g., upon request of UE 100), modified (e.g., upon request of UE 100 and 5GC) and / or released (e.g., upon request of UE 100 and 5GC) using NAS SM signaling exchanged between UE 100 and SMF 160 over N1. Upon request of an application server, 5GC may be able to trigger a specific application in UE 100. When a trigger is received, UE 100 may send it to an identified application in UE 100. The identified application in UE 100 may establish a PDU session for a specific DNN.

[0265] In the example, the 5G QoS model can support the following example: Figure 7The QoS flow-based framework depicted in . The 5G QoS model can support both QoS flows that require guaranteed streaming bit rate and QoS flows that do not require guaranteed streaming bit rate. In an example, the 5G QoS model can support reflective QoS. The QoS model can include flow mapping or packet marking at the UPF 110 (CN_UP) 110, AN 105 and / or UE 100. In an example, packets can arrive from and / or be designated to the application / service layer 730 of the UE 100, UPF 110 (CN_UP) 110 and / or AF 145.

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

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

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

[0269] In an example, the 5G QoS indicator may be a scalar that may be used as a reference to a specific QoS forwarding behavior (e.g., packet loss rate, packet delay budget) to be provided to a 5G QoS flow. In an example, the 5G QoS indicator may be implemented in an access network by a 5QI reference node specific parameter (e.g., scheduling weight, admission threshold, queue management threshold, link layer protocol configuration, etc.) that may control the QoS forwarding process.

[0270] In an example, edge computing can provide computing and storage resources with sufficient connectivity close to the devices generating traffic.

[0271] In an example, the 5GC may support edge computing and may enable operator and third-party services to be hosted close to the UE's attachment access point. The 5G core network may select a UPF 110 close to the UE 100 and may perform traffic steering from the UPF 110 to the local data network via the N6 interface. In an example, the selection and traffic steering may be based on the UE 100's subscription data, the UE 100 location, information from the application function AF 145, policies, other relevant traffic rules, etc. In an example, the 5G core network may expose network information and capabilities to edge computing application functions. Functional support for edge computing may include: local routing, where the 5G core network can select UPF 110 to route user traffic to the local data network; traffic steering, where the 5G core network can select traffic for applications to be routed to 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 exposure, 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; LAN data network support, where the 5G core network can provide support for connecting to LADN in specific areas where applications are deployed; and so on.

[0272] An example 5G system may be a 3GPP system including a 5G access network 105, a 5G core network, and UE 100, etc. The allowed NSSAI may be the NSSAI provided by the serving PLMN during, for example, a registration procedure, indicating the network allowed NSSAI for UE 100 in the serving PLMN in the current registration area.

[0273] In an example, the PDU connection service may provide an exchange of PDUs between the UE 100 and the data network. A PDU session may be an association between the UE 100 and the data network DN 115 that may provide the PDU connection service. The type of association may be IP, Ethernet and / or unstructured.

[0274] Establishing a user plane connection to a data network via a network slice instance may include the following: executing an RM procedure to select an AMF 155 that supports the required network slice, and establishing one or a number of PDU sessions to the required data network via the network slice instance.

[0275] In an example, the network slice set of UE 100 may be changed at any time when UE 100 may be registered on the network, and may be initiated by the network or UE 100.

[0276] In an example, the periodic registration update may be a re-registration of the UE 100 upon expiration of a periodic registration timer. The requested NSSAI may be an NSSAI that the UE 100 may provide to the network.

[0277] In an example, a service-based interface may represent the way a set of services may be provided / exposed by a given NF.

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

[0279] In an example, the 5G system architecture may support data connectivity and services, enabling deployments to use technologies such as network function virtualization and / or software-defined networking. The 5G system architecture may utilize service-based interactions between identified control plane (CP) network functions. In the 5G system architecture, the user plane (UP) functions may be considered to be separated from the control plane functions. If desired, the 5G system may enable network functions to interact directly with other NFs.

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

[0281] In the example, the 5G system can support a unified authentication framework, stateless NFs with separated computing and storage resources, capability exposure, and simultaneous access to local and centralized services. To support low-latency services and access to local data networks, UP functions can be deployed close to the access network.

[0282] In an example, the 5G system may support roaming with home-routed traffic and / or local breakout traffic in a visited PLMN. The example 5G architecture may be service-based, and the interactions between network functions may 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 network functions described by point-to-point reference points (e.g., N11) between any two network functions.

[0283] In an example, a network slice may include core network control plane and user plane network functions, 5G radio access network; N3IWF functions for non-3GPP access networks, etc. Network slices may differ in terms of supported features and network function implementations. An operator may deploy multiple network slice instances that deliver the same features but for different groups of UEs, for example, when they deliver different committed services and / or because they may be dedicated to a customer. NSSF 120 may store mapping information between slice instance IDs and NF IDs (or NF addresses).

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

[0285] In an example, per PLMN, a PDU session may belong to one specific network slice instance. In an example, different network slice instances may not share PDU sessions. Different slices may have slice-specific PDU sessions using the same DNN.

[0286] S-NSSAI (Single Network Slice Selection Assistance Information) may identify a network slice. S-NSSAI may include: a slice / service type (SST), which may refer to the expected network slice behavior in terms of features and services; and / or a slice differentiator (SD). The slice differentiator may be optional information that may be supplemented with a slice / service type that allows further differentiation to select a network slice instance from potential multiple network slice instances that conform to the indicated slice / service type. In an example, the same network slice instance may be selected with different S-NSSAIs. The CN portion of the network slice instance serving the UE 100 may be selected by the CN.

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

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

[0289] In an example, the allowed NSSAI of the PLMN may take precedence over the configured NSSAI. The UE 100 may use the S-NSSAI corresponding to the network slice in the serving PLMN for subsequent network slice selection related procedures among the allowed NSSAI.

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

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

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

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

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

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

[0296] In an example, if the UE 100 has one or more PDU sessions established corresponding to a particular S-NSSAI, the UE 100 may route user data for the application in one PDU session unless other conditions in the UE 100 may prohibit the use of the PDU session. If the application provides a DNN, the UE 100 may consider the DNN to determine which PDU session to use. In an example, if the UE 100 does not have a PDU session established with a particular S-NSSAI, the UE 100 may request a new PDU session corresponding to the S-NSSAI and having a DNN that may be provided by the application. In an example, in order for the RAN 105 to select appropriate resources for supporting network slices in the RAN 105, the RAN 105 may be aware of the network slices used by the UE 100.

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

[0298] In an example, to support network controlled privacy of slice information for slices accessible to UE 100, when UE 100 is aware or configured that privacy considerations may apply to NSSAI, UE 100 may not include NSSAI in NAS signaling unless UE 100 has a NAS security context, and UE 100 may not include NSSAI in unprotected RRC signaling.

[0299] In an example, for a roaming scenario, a network slice specific network function may be selected in the VPLMN and the HPLMN based on the S-NSSAI provided by the UE 100 during PDU connection establishment. If a standardized S-NSSAI is used, the selection of a slice specific NF instance may be performed by each PLMN based on the provided S-NSSAI. In an example, the VPLMN may map the S-NSSAI of the HPLMN to the S-NSSAI of the VPLMN (e.g., including a default S-NSSAI mapped to the VPLMN) based on a roaming agreement. In an example, the selection of a slice specific NF instance may be performed in the VPLMN based on the S-NSSAI of the VPLMN. In an example, any slice specific NF instance in the HPLMN may be selected based on the S-NSSAI of the HPLMN.

[0300] As an example Figure 8 and Fig. 9 As depicted in , a registration procedure may be performed by UE 100 to obtain authorization to receive services, to enable mobile tracking, to achieve reachability, and the like.

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

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

[0303] In an example, the (R)AN 105 may send an N2 message 810 (including: N2 parameters, RM-NAS registration request (registration type, SUPI or 5G-GUTI, last visited TAI (if available), security parameters, requested NSSAI, mapping of requested NSSAI, UE 100 5GC capabilities, PDU session status, PDU sessions to be reactivated, subsequent requests and MICO mode preferences), etc.) to the new AMF 155. In an example, when NG-RAN is used, the N2 parameters may include a selected PLMN ID, location information, cell identity, and a RAT type related to the cell in which the UE 100 is located. In an example, when NG-RAN is used, the N2 parameters may include an establishment cause.

[0304] In an example, the new AMF 155 may send a Namf_Communication_UEContextTransfer (full registration request) 815 to the old AMF 155. In an 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 may invoke a Namf_Communication_UEContextTransfer service operation 815 (including a full registration request IE which may be integrity protected) on the old AMF 155 to request the UE's SUPI and MM context. The old AMF 155 may use the integrity protected full registration request IE to verify that the context transfer service operation call corresponds to the requesting UE 100. In an example, the old AMF 155 may transfer event subscription information for each NF consumer for the UE to the new AMF 155. In an example, if the UE 100 identifies itself with a PEI, the SUPI request may be skipped.

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

[0306] In an example, if the SUPI is not provided by the UE 100 or retrieved from the old AMF 155, the Identity Request Procedure 820 may be initiated by the AMF 155 sending an Identity Request message to the UE 100 requesting the SUCI.

[0307] In an example, the UE 100 may respond with an identity response message 820 including the SUCI. The UE 100 may derive the SUCI by using the provided public key of the HPLMN.

[0308] In an example, the AMF 155 may decide to initiate UE 100 authentication 825 by invoking the AUSF 150. The AMF 155 may select the AUSF 150 based on the SUPI or SUCI. In an example, if the AMF 155 is configured to support emergency registration for unauthenticated SUPIs and the registration type Emergency Registration indicated by the UE 100, the AMF 155 may skip authentication and security setup, or the AMF 155 may accept that authentication may fail and may continue with the registration procedure.

[0309] In an example, authentication 830 may be performed by a Nudm_UEAuthenticate_Get operation. AUSF 150 may discover UDM 140. If AMF 155 provides SUCI to AUSF 150, AUSF 150 may return SUPI to AMF 155 after authentication is successful. In an example, if network slicing is used, AMF 155 may decide whether the registration request needs to be rerouted in the case where the initial AMF 155 references AMF 155. In an example, AMF 155 may initiate NAS security functions. In an example, upon completion of the NAS security function setup, AMF 155 may start an NGAP procedure to enable the 5G-AN to use it to protect procedures with the UE. In an example, the 5G-AN may store the security context and may confirm it to AMF 155. The 5G-AN may use the security context to protect messages exchanged with the UE.

[0310] In an example, the new AMF 155 may send a Namf_Communication_RegistrationCompleteNotify 835 to the old AMF 155. If the AMF 155 has changed, the new AMF 155 may inform the old AMF 155 that the registration of the UE 100 in the new AMF 155 may be completed by invoking the Namf_Communication_RegistrationCompleteNotify service operation. If the authentication / security procedure fails, the registration may be rejected and the new AMF 155 may invoke the Namf_Communication_RegistrationCompleteNotify service operation with a rejection indicating the cause code towards the old AMF 155. The old AMF 155 may continue as if the UE 100 context transfer service operation was never received. If one or more of the S-NSSAIs used in the old registration area may not be served in the target registration area, the new AMF 155 may determine which PDU sessions may not be supported in the new registration area. The new AMF 155 may call the Namf_Communication_RegistrationCompleteNotify service operation to the old AMF 155, including the rejected PDU session ID and the rejection reason (e.g., S-NSSAI becomes no longer available). The new AMF 155 may modify the PDU session state accordingly. The old AMF 155 may notify the corresponding SMF 160 to release the UE's SM context locally by calling the Nsmf_PDUSession_ReleaseSMContext service operation.

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

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

[0313] In an example, based on the SUPI, the new AMF 155 may select 905 the UDM 140. The UDM 140 may select a UDR instance. In an example, the AMF 155 may select the UDM 140.

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

[0315] In the example, if the AMF 155 decides to initiate PCF 135 communication, for example, the AMF 155 has not yet obtained the access and mobility policy of the UE 100, or if the access and mobility policy in the AMF 155 is no longer valid, the AMF 155 may select 925 PCF 135. If the new AMF 155 receives the PCF ID from the old AMF 155 and successfully contacts the PCF 135 identified by the PCF ID, the AMF 155 may select 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 the PCF 135), or if the PCF ID is not received from the old AMF 155, the AMF 155 may select 925 PCF 135.

[0316] In an example, the new AMF 155 may perform a 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 inter-AMF 155 mobility, the new AMF 155 may include the PCF-ID in the Npcf_AMPolicyControl Get operation. If the AMF 155 notifies the PCF 135 of mobility restrictions (e.g., UE 100 location) for adjustment, or if the PCF 135 updates its own mobility restrictions due to certain conditions (e.g., applications in use, time and date), the PCF 135 may provide the updated mobility restrictions to the AMF 155.

[0317] In an example, the PCF 135 may invoke the Namf_EventExposure_Subscribe service operation 935 for the UE 100 event subscription.

[0318] In an example, the AMF 155 may send a Nsmf_PDUSession_UpdateSMContext 936 to the SMF 160. In an example, if the PDU session to be reactivated is included in the registration request, the AMF 155 may call Nsmf_PDUSession_UpdateSMContext. The AMF 155 may send a Nsmf_PDUSession_UpdateSMContext request to the SMF 160 associated with the PDU session to activate the user plane connection for the PDU session. The SMF 160 may decide to trigger, for example, the intermediate UPF 110 to insert, remove or change the PSA. In the case where the intermediate UPF 110 is inserted, removed or relocated for a PDU session that is not included in the PDU session to be reactivated, the procedure may be performed without N11 and N2 interactions to update the N3 user plane between the (R)AN 105 and the 5GC. The AMF 155 may call the Nsmf_PDUSession_ReleaseSMContext service operation to the SMF 160 when any PDU session status indicates that it is released at the UE 100. The AMF 155 may call the Nsmf_PDUSession_ReleaseSMContext service operation to the SMF 160 in order to release any network resources related to the PDU session.

[0319] In an example, the new AMF 155 may send an N2 AMF 155 Move Request 940 to the N3IWF. If the AMF 155 has changed, the new AMF 155 may create an NGAP UE 100 association for the N3IWF connecting the UE 100. In an example, the N3IWF may respond to the new AMF 155 with an N2 AMF 155 Move Response 940.

[0320] In an example, the new AMF 155 may send a Registration Accept 955 to the UE 100 (including: 5G-GUTI, registration area, mobility restrictions, PDU session status, allowed NSSAI, [mapping of allowed NSSAI], periodic registration update timer, LADN information and accepted MICO modes, indication that IMS voice is supported over PS session, emergency service support indicator, etc.). In an example, the AMF 155 may send a Registration Accept message to the UE 100 indicating that the registration request has been accepted. If the AMF 155 allocates a new 5G-GUTI, the 5G-GUTI may be included. If the AMF 155 allocates a new registration area, it may send the registration area to the UE 100 via the Registration Accept message 955. If the registration area is not included in the Registration Accept message, the UE 100 may consider the old registration area to be valid. In an example, the mobility restrictions may be included in the case where the mobility restrictions may be applicable to the UE 100 and the registration type may not be an emergency registration. The AMF 155 may indicate the established PDU session to the UE 100 in the PDU session status. The UE 100 may locally remove any internal resources related to the PDU session that is not marked as established in the received PDU session status. In an example, when the UE 100 is connected to two AMFs 155 belonging to different PLMNs via 3GPP access and non-3GPP access, the UE 100 may locally remove any internal resources related to the PDU session of the current PLMN that are not marked as established in the received PDU session status. If the PDU session status information is in the registration request, the AMF 155 may indicate the PDU session status to the UE. The mapping of the allowed NSSAI may be a mapping of each S-NSSAI in the allowed NSSAI of the HPLMN to the S-NSSAI in the configured NSSAI. The AMF 155 may include LADN information of a LADN in the registration accept message 955 that is available within the registration area determined by the AMF 155 for the UE. If the UE 100 includes the MICO mode in the request, the AMF 155 may respond whether the MICO mode may be used. The AMF 155 may set an indication that IMS voice is supported over a PS session. In an example, in order to set an indication that IMS voice is supported over a PS session, the AMF 155 may perform a UE / RAN radio information and compatibility request procedure to check the compatibility of the UE 100 and RAN radio capabilities related to IMS voice over PS. In an example, the emergency service support indicator may inform the UE 100 that emergency services are supported, for example, the UE 100 may request a PDU session for emergency services. In an example, a handover restriction list and a UE-AMBR may be provided by the AMF 155 to the NG-RAN.

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

[0322] As an example Fig.10 and Fig.11 As depicted in , a service request procedure (e.g., a service request procedure triggered by the UE 100) may be used by a UE 100 in a CM-IDLE state to request establishment of a secure connection to the AMF 155. Fig.11 It describes the service request process Fig.10 Continuation of FIG. The service request procedure may be used to activate a user plane connection for an established PDU Session. The service request procedure may be triggered by the UE 100 or the 5GC and may be used when the UE 100 is in CM-IDLE and / or CM-CONNECTED and may allow selective activation of a user plane connection for some established PDU Sessions.

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

[0324] In an example, for any service request, the AMF 155 may respond with a service accept message to synchronize the PDU session state between the UE 100 and the network. If the service request may not be accepted by the network, the AMF 155 may respond to the UE 100 with a service reject message. The service reject message may include an indication or a reason code requesting the UE 100 to perform a registration update procedure. In an example, for a service request due to user data, if the user plane connection activation may not be successful, the network may take further action. In an example Fig.10 and Fig.11 In the example, more than one UPF may be involved, for example, the old UPF 110 - 2 and the PDU session anchor PSA UPF 110 - 3 .

[0325] In an example, the UE 100 may send a message to the (R)AN 105, the message including AN parameters, mobility management, MMNAS 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.), etc. In an example, when the UE 100 may reactivate the PDU session, the UE 100 may provide a list of PDU sessions to be activated. When the service request may be a response to a paging or NAS notification, the list of allowed PDU sessions may be provided by the UE 100 and may identify a PDU session that may be transferred to or associated with an access on which the service request may be sent. In an example, for the case of NG-RAN, the AN parameters may include a selected PLMN ID and an establishment cause. The establishment cause may provide a reason for requesting to establish an RRC connection. The UE 100 may send a NAS service request message to the AMF 155 encapsulated in an RRC message to the RAN 105.

[0326] In an example, if the service request may be triggered for user data, the UE 100 may use the list of PDU sessions to be activated to identify the PDU session for which the UP connection is to be activated in the NAS service request message. If the service request may be triggered for signaling, the UE 100 may not be able to identify any PDU session. If this procedure may be triggered for a paging response, and / or the UE 100 may have user data to be transmitted at the same time, the UE 100 may identify the PDU session for which the UP connection may be activated in the MM NAS service request message through the list of PDU sessions to be activated.

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

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

[0329] In an example, if the service request is not sent integrity protected or the integrity protection verification fails, the AMF 155 may initiate a NAS authentication / security procedure 1015 .

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

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

[0332] In an example, if the UE 100 can identify the PDU session to be activated in the NAS service request message, the Nsmf_PDUSession_UpdateSMContext request may be called by the AMF 155. In an example, the Nsmf_PDUSession_UpdateSMContext request may be triggered by the SMF 160, wherein the PDU session identified by the UE 100 may be related to other PDU session IDs other than the one that triggered the procedure. In an example, the Nsmf_PDUSession_UpdateSMContext request may be triggered by the SMF 160, wherein during the network-triggered service request procedure, the current UE 100 location may be outside the valid area of ​​the N2 information provided by the SMF 160. The AMF 155 may not send the N2 information provided by the SMF 160 during the network-triggered service request procedure.

[0333] In an example, the AMF 155 may determine a PDU session to be activated and may send a Nsmf_PDUSession_UpdateSMContext request to the SMF 160 associated with the PDU session, where the cause is set to indicate establishment of user plane resources for the PDU session.

[0334] In an example, if the procedure may be triggered in response to a paging indicating non-3GPP access, and the list of allowed PDU sessions provided by the UE 100 may not include the PDU session for which the UE 100 has been paged, the AMF 155 may inform the 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 the AMF 155 may inform the UE 100.

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

[0336] In an example, if the PDU Session ID may correspond to a LADN, and the SMF 160 may determine that the UE 100 may be outside the availability area of ​​the LADN based on the UE 100 location reported from the AMF 155, the SMF 160 may decide (based on local policy) to release the PDU session. The SMF 160 may release the PDU session locally and may notify the AMF 155 that the PDU session may be released. The SMF 160 may respond to the AMF 155 with an appropriate rejection cause and may stop the user plane activation of the PDU session.

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

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

[0339] In an example, if SMF 160 selects new UPF 110 to replace old (intermediate) UPF 110-2, SMF 160 may include a data forwarding indication. The data forwarding indication may indicate to UPF 110 that a second tunnel endpoint may be reserved for buffering DL data from the old I-UPF.

[0340] In an example, the new UPF 110 (intermediate) may send an N4 session establishment response message 1030 to the SMF 160. In the case where the UPF 110 may allocate CN tunnel information, the UPF 110 may provide the DL CN tunnel information of the UPF 110 used as the PDU session anchor and the UL CN tunnel information (e.g., CN N3 tunnel information) to the SMF 160. If a data forwarding indication may be received, the new (intermediate) UPF 110 used as the N3 termination point may send the DL CN tunnel information of the old (intermediate) UPF 110-2 to the SMF 160. The SMF 160 may start a timer to release resources in the old intermediate UPF 110-2.

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

[0342] In an example, if a new intermediate UPF 110 may be added for the PDU session, the (PSA)UPF 110 - 3 may start sending DL data to the new I-UPF 110 , as indicated by the DL tunnel information.

[0343] In an example, if the service request may be triggered by the network, and the SMF 160 may remove the old I-UPF 110-2 and may not replace the old I-UPF 110-2 with the new I-UPF 110, then the SMF 160 may include a data forwarding indication in the request. The data forwarding indication may indicate to the (PSA) UPF 110-3 that a second tunnel endpoint may be reserved for buffering DL data from the old I-UPF 110-2. In this case, the PSA UPF 110-3 may start buffering DL data that it may simultaneously receive from the N6 interface.

[0344] In an example, the PSA UPF 110-3 (PSA) may send an N4 session modification response 1035 to the SMF 160. In an example, if a data forwarding indication may be received, the PSA UPF 110-3 may become an N3 termination point and may send the CN DL tunnel information of the old (intermediate) UPF 110-2 to the SMF 160. The SMF 160 may start a timer to release resources (if any) in the old intermediate UPF 110-2.

[0345] In an example, the SMF 160 may send an N4 session modification request 1045 to the old UPF 110-2 (e.g., may include a new UPF 110 address, a new UPF 110 DL tunnel ID, etc.). In an example, if the service request may be triggered by the network, and / or the SMF 160 may remove the old (intermediate) UPF 110-2, the SMF 160 may send an N4 session modification request message to the old (intermediate) UPF 110-2, and may provide DL tunnel information for buffering DL data. If the SMF 160 may allocate a new I-UPF 110, the DL tunnel information comes from the new (intermediate) UPF 110 that may serve as an N3 termination point. If the SMF 160 may not allocate a new I-UPF 110, the DL tunnel information may come from the new UPF 110 (PSA) 110-3 that serves as an N3 termination point. The SMF 160 may start a timer to monitor the forwarding tunnel. In the example, the old (intermediate) UPF 110-2 may send an N4 Session Modification Response message to the SMF 160.

[0346] In an example, if the I-UPF 110-2 may be relocated and a forwarding tunnel may be established to the new I-UPF 110, the old (intermediate) UPF 110-2 may forward its buffered data to the new (intermediate) UPF 110 serving as the N3 termination point. In an example, if the old I-UPF 110-2 may be removed and the new I-UPF 110 may not be allocated for the PDU session, and a forwarding tunnel may be established to the UPF 110 (PSA) 110-3, the old (intermediate) UPF 110-2 may forward its buffered data to the UPF 110 (PSA) 110-3 serving as the N3 termination point.

[0347] In an example, the SMF 160 may send an N11 message 1060, e.g., a Nsmf_PDUSession_UpdateSMContext response (including an 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), cause) to the AMF 155 upon receiving an Nsmf_PDUSession_UpdateSMContext request with a cause (including, e.g., establishment of user plane resources). The SMF 160 may determine whether UPF 110 reallocation may be performed based on UE 100 location information, UPF 110 service area, and operator policy. In an example, for a PDU session for which the SMF 160 may be determined to be served by the current UPF 110 (e.g., a PDU session anchor or an intermediate UPF), the SMF 160 may generate N2 SM information and may send an Nsmf_PDUSession_UpdateSMContext response 1060 to the AMF 155 to establish the user plane. The N2 SM information may include information that the AMF 155 may provide to the RAN 105. In an example, for a PDU session that the SMF 160 may determine requires the UPF 110 to relocate the PDU session anchor UPF, the SMF 160 may deny activating the UP for the PDU session by sending a Nsmf_PDUSession_UpdateSMContext response that may include an N1 SM container to the UE 100 via the AMF 155. The N1 SM container may include a corresponding PDU session ID and a PDU session reestablishment indication.

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

[0349] In an example, if the PDU session may correspond to a LADN and the UE 100 may be outside the availability area of ​​the LADN, or if the AMF 155 may inform the SMF 160 that the UE 100 may be reachable for a regulatory prioritization service and the PDU session to be activated may not be for a regulatory prioritization service; or if the SMF 160 may decide to perform a PSA UPF 110-3 relocation for the requested PDU session, the SMF 160 may send a message to the AMF 155 to reject activation of the UP for the PDU session by including a cause in the Nsmf_PDUSession_UpdateSMContext response.

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

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

[0352] In an example, if a procedure may 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., N2 Tunnel Setup Request), if present. Alternatively, if multiple SMFs 160 may be involved, the AMF 155 may send one N2 request message to the (R)AN 105 after receiving all Nsmf_PDUSession_UpdateSMContext response service operations from all SMFs 160 associated with the UE 100. In this case, the N2 request message may include the N2 SM information and the PDU session ID received in each Nsmf_PDUSession_UpdateSMContext response to enable the AMF 155 to associate the response with the relevant SMF 160.

[0353] In an example, if the RAN 105 (e.g., NG RAN) node can provide a list of recommended cell / TA / NG-RAN node identifiers during the AN release procedure, the AMF 155 can include information from the list in the N2 request. The RAN 105 can use this information to allocate a RAN 105 notification area when the RAN 105 may decide to enable the RRC inactive state of the UE 100.

[0354] If the AMF 155 may receive an indication from the SMF 160 during the PDU session establishment procedure that the UE 100 may be using a PDU session associated with a delay-sensitive service for any PDU session established for the UE 100, and the AMF 155 has received an indication from the UE 100 that CM-CONNECTED in the RRC inactive state may be supported, the AMF 155 may include the RRC inactive assistance information of the UE. In an example, the AMF 155 based on the network configuration may include the RRC inactive assistance information of the UE.

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

[0356] In an example, if the N2 request may include an MM NAS Service Accept message, the RAN 105 may forward the MM NAS Service Accept to the UE 100. The UE 100 may locally delete the context of the PDU session that may not be available in the 5GC.

[0357] In an example, if N1 SM information may be transmitted to the UE 100 and may indicate that some PDU sessions may be reestablished, the UE 100 may initiate PDU session reestablishment for the PDU sessions that may be reestablished after the service request procedure may be completed.

[0358] In an example, after user plane radio resources may be set up, uplink data from the UE 100 may be forwarded to the RAN 105. The RAN 105 (eg, NG-RAN) may send the uplink data to the provided UPF 110 address and tunnel ID.

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

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

[0361] In an example, if dynamic PCC is deployed, SMF 160 may initiate a notification (if subscribed) about the new location information to PCF 135 by calling an event exposure notification operation (e.g., Nsmf_EventExposure_Notify service operation). PCF 135 may provide updated policies by calling a policy control update notification message 1115 (e.g., Npcf_SMPolicyControl_UpdateNotify operation).

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

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

[0364] In an example, the old intermediate UPF 110-2 may send an N4 Session Modification Response or an N4 Session Release Response 1155 to the SMF 160. The old UPF 110-2 may confirm with an N4 Session Modification Response or an N4 Session Release Response message to confirm the modification or release of the resources. The AMF 155 may call a Namf_EventExposure_Notify service operation to notify the NFs that may have subscribed to the event of the mobile-related event after this procedure may be completed. In an example, if SMF 160 has subscribed to UE 100 moving into or out of an area of ​​interest and if the current location of the UE may indicate that it may be moving into or out of the subscribed area 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 SMF 160 of UE 100 that it is unreachable and SMF 160 may not send DL data notifications to AMF 155, and AMF 155 may notify SMF 160 that UE 100 is reachable, then AMF 155 may call Namf_EventExposure_Notify to SMF 160, or if SMF 160 has subscribed to the UE 100 reachability status, then AMF 155 may notify UE 100 of reachability.

[0365] exist Fig.12 and Fig.13An example PDU session establishment procedure is depicted in . In an exemplary embodiment, when the PDU session establishment procedure may be employed, the UE 100 may send a NAS message 1205 (or an SM NAS message) to the AMF 155, the NAS message including 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, the UE 100 may generate a new PDU session ID in order to establish a new PDU session. In the example, when emergency services may be required and an emergency PDU session may not have been established, the UE 100 may initiate a UE 100 requested PDU session establishment procedure, wherein the request type indicates an emergency request. In the example, the UE 100 may initiate a UE 100 requested PDU session establishment procedure by transmitting a NAS message containing a PDU session establishment request within an N1 SM container. The PDU session establishment request may include a PDU type, an SSC mode, a protocol configuration option, and the like. In an 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 a 3GPP access and a non-3GPP access or involves an existing PDN connection in the EPC, the request type may indicate an existing PDU session. In an example, if the PDU session establishment may be 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 a 3GPP access and a non-3GPP access, the request type may indicate an existing emergency PDU session. In an example, the NAS message sent by the UE 100 may be encapsulated by an AN in an N2 message sent to the AMF 155 that may include user location information and access technology type information. In an example, the PDU session establishment request message may include an SM PDUDN request container that includes information about an external DN authorization for a PDU session. In an example, if the procedure may be triggered for SSC mode 3 operation, the UE 100 may include an old PDU session ID in the NAS message, which may indicate the PDU session ID of the ongoing PDU session to be released. The old PDU session ID may be an optional parameter that may be included in this case. In an example, the AMF 155 may receive a NAS message (e.g., a NAS SM message) from the AN along with user location information (e.g., a cell ID in the case of the RAN 105). In an example, when the UE 100 is outside the availability area of ​​the LADN, the UE 100 may not trigger a PDU session establishment for the PDU session corresponding to the LADN.

[0366] In an example, the AMF 155 may determine that the NAS message or the SM NAS message may correspond to a request for a new PDU session based on the request type indicating an initial request and the PDU session ID may not be for any existing PDU session of the UE 100. If the NAS message does not contain an S-NSSAI, the AMF 155 may determine a default S-NSSAI for the requested PDU session based on UE 100 subscriptions (if it may contain only one default S-NSSAI), or based on operator policy. In an example, the AMF 155 may perform SMF 160 selection 1210 and select SMF 160. If the request type may indicate an initial request or the request may be attributable to a handover from EPS, the AMF 155 may store an association of the S-NSSAI, the PDU session ID, and the SMF 160 ID. In an example, if the request type is an initial request, and if an old PDU session ID indicating an existing PDU session may be included in the message, the AMF 155 may select the SMF 160, and may store an association of the new PDU session ID and the selected SMF 160 ID.

[0367] In an example, the AMF 155 may send an N11 message 1215 to the SMF 160, such as an 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 an 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 an example, if the AMF 155 may not be associated with the SMF 160 for the PDU session ID provided by the UE 100 (e.g., when the request type indicates an initial request), the AMF 155 may call a Nsmf_PDUSession_CreateSMContext request, but if the AMF 155 is already associated with the SMF 160 for the PDU session ID provided by the UE 100 (e.g., when the request type indicates an existing PDU session), the AMF 155 may call a Nsmf_PDUSession_UpdateSMContext request. In an example, the AMF 155 ID may be the GUAMI of the UE, which uniquely identifies the AMF 155 serving the UE 100. The AMF 155 may forward the PDU session ID and the N1 SM container containing the PDU session establishment request received from the UE 100. When the UE 100 is registered for emergency services without providing a SUPI, the AMF 155 may provide a PEI instead of a SUPI. If the UE 100 is registered for emergency services but has not yet been authenticated, the AMF 155 may indicate that the SUPI has not yet been authenticated.

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

[0369] In an example, the SMF 160 may send an N11 message response 1220 to the AMF 155, such as a PDU Session Create / Update Response, a Nsmf_PDUSession_CreateSMContext Response 1220 (Cause, SM Context ID or N1 SM Container (PDU Session Reject (Cause))), or a Nsmf_PDUSession_UpdateSMContext Response.

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

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

[0372] In an example, if a dynamic PCC is deployed, SMF 160 may perform PCF 135 selection 1235. If the request type indicates an existing PDU session or an existing emergency PDU session, SMF 160 may use the PCF 135 that has been selected for the PDU session. If a dynamic PCC is not deployed, SMF 160 may apply local policies.

[0373] In an example, SMF 160 may perform a session management policy establishment procedure 1240 to establish a PDU session with PCF 135, and may obtain the default PCC rules for the PDU session. GPSI may be included if available at SMF 160. If the request type in 1215 indicates an existing PDU session, SMF 160 may notify the event previously subscribed by PCF 135 through a session management policy modification procedure, and PCF 135 may update the policy information in SMF 160. PCF 135 may provide SMF 160 with an authorized session-AMBR and authorized 5QI and ARP. PCF 135 may subscribe to IP allocation / release events in SMF 160 (and may subscribe to other events).

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

[0375] In the example, if the request type in 1215 indicates an initial request, the SMF 160 may select an SSC mode for the PDU session. The SMF 160 may select 1245 one or more UPFs as needed. In the case where the PDU type is IPv4 or IPv6, the SMF 160 may allocate an IP address / prefix for the PDU session. In the case where the PDU type is IPv6, the SMF 160 may allocate an interface identifier for the UE 100 so that the UE 100 can construct its link local address. For unstructured PDU types, the SMF 160 may allocate an IPv6 prefix for the PDU session and N6 point-to-point tunnel (e.g., based on UDP / IPv6). In the example, for a PDU session of Ethernet PDU type, it is impossible for the SMF 160 to allocate neither a MAC nor an IP address to the UE 100 for this PDU session.

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

[0377] In an example, if the request type in 1215 indicates that the existing PDU session involves an existing PDU session moved between a 3GPP access and a non-3GPP access, the SMF 160 may maintain the SSC mode of the PDU session, e.g., the current PDU session anchor and IP address. In an example, the SMF 160 may trigger, e.g., the insertion of a new intermediate UPF 110 or the allocation of a new UPF 110. In an example, if the request type indicates an emergency request, the SMF 160 may select 1245 the UPF 110 and may select SSC mode 1.

[0378] In an example, the SMF 160 may perform a session management policy modification 1250 procedure to report some events to the 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 may inform the (previously subscribed) PCF 135 of the allocated UE 100 IP address / prefix.

[0379] In an example, PCF 135 may provide the updated policy to SMF 160. PCF 135 may provide SMF 160 with the Authorization Session-AMBR and Authorization 5QI and ARP.

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

[0381] In an example, SMF 160 may send a Namf_Communication_N1N2MessageTransfer1305 message (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.), N1 SM container (PDU session establishment accept (QoS rules, selected SSC mode, S-NSSAI, allocated IPv4 address, interface identifier, session-AMBR, selected PDU session type, etc.)) to AMF 155. In the case where multiple UPFs are used for a PDU session, the CN tunnel information may include tunnel information related to the UPF 110 that terminates N3. In an example, the N2 SM information may carry information that the AMF 155 may 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, a PDU session ID may indicate to the UE 100 the association between AN resources and the PDU session for the UE 100 through AN signaling with the UE 100, etc.). In an example, the PDU session may be associated with the S-NSSAI and the DNN. In an example, the N1 SM container may contain a PDU session establishment acceptance that the AMF 155 may provide to the UE 100. In an example, multiple QoS rules and QoS profiles may be included in the N1 SM and the PDU session establishment acceptance in the N2 SM information. In an example, the Namf_Communication_N1N2MessageTransfer 1305 may also include the PDU session ID and information that allows the AMF 155 to know which access to use for the UE 100.

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

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

[0384] In an example, the N2 PDU Session Response 1320 may include a PDU Session ID, a cause, N2 SM information (PDU Session ID, AN Tunnel Information, a list of accepted / rejected QFIs), etc. In an example, the AN Tunnel Information may correspond to an access network address of an N3 tunnel corresponding to the PDU session.

[0385] In one example, AMF 155 may forward the 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 one example, if a list of rejected QFIs is included in the N2 SM information, SMF 160 may release the QoS profile associated with the rejected QFI.

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

[0387] In an example, the SMF 160 may send a Nsmf_PDUSession_UpdateSMContext response 1340 (cause) to the AMF 155. In an example, the SMF 160 may subscribe to UE 100 movement event notifications (e.g., location report, UE 100 moving into or out of an area of ​​interest) from the AMF 155 by calling the Namf_EventExposure_Subscribe service operation after this step. For LADN, the SMF 160 may subscribe to UE 100 moving into or out of a LADN service area event notification by providing the LADN DNN as an indicator of the area of ​​interest. The AMF 155 may forward the relevant events subscribed by the SMF 160.

[0388] In an example, the SMF 160 may send a Nsmf_PDUSession_SMContextStatusNotify(release) 1345 to the AMF 155. In an example, if at any time during this procedure, the PDU session establishment is unsuccessful, the SMF 160 may notify the AMF 155 by calling Nsmf_PDUSession_SMContextStatusNotify(release) 1345. The SMF 160 may release any N4 sessions created, any PDU session addresses (if assigned) (e.g., IP addresses), and may release the association with the PCF 135.

[0389] In an example, where the PDU type is IPv6, the SMF 160 may generate an IPv6 router advertisement 1350 and may send it to the UE 100 via N4 and the UPF 110.

[0390] In an example, if a PDU session may not be established, the SMF 160 may unsubscribe 1360 from modifications to the session management subscription data of the corresponding (SUPI, DNN, S-NSSAI) using Nudm_SDM_Unsubscribe (SUPI, DNN, S-NSSAI) when the SMF 160 no longer handles the PDU session of the UE 100 for this (DNN, S-NSSAI). In an example, if a PDU session may not be established, the SMF 160 may deregister 1360 for a given PDU session using Nudm_UECM_Deregistration (SUPI, DNN, PDU Session ID).

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

[0392] The wireless device 1410 may communicate with the base station 1420 over the air interface 1470. The direction of communication from the wireless device 1410 to the base station 1420 over the air interface is referred to as uplink, and the direction of communication from the base station 1420 to the wireless device 1410 over the air interface 1470 is referred to as downlink. Downlink transmissions may be separated from uplink transmissions using FDD, TDD, and / or some combination of the two duplexing techniques. Fig.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 over the air interface 1470, and the base station 1420 can communicate with any number of wireless devices over the air interface 1470.

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

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

[0395] The wireless device 1410 may transmit data to the base station 1420 via the air interface 1470. To perform the transmission, the processing system 1411 may implement layer 3 and layer 2 open system interconnection (OSI) functions to process data for uplink transmission. Layer 3 may include a radio resource control layer (RRC). Layer 14 may include a service data application protocol layer (SDAP), a packet data convergence protocol layer (PDCP), a radio link control layer (RLC), and a media access control layer (MAC). The data may be provided to a transmission processing system 1414, which may implement layer 1 OSI functions. Layer 1 may include a physical layer (PHY). The wireless device 1410 may use one or more antennas 1416 to transmit data over the air interface 1470. For situations where one or more antennas 1416 include multiple antennas, the multiple antennas may 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.

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

[0397] Base station 1420 may include an 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 suitable for communicating via interface 1480. Fig.14 14, interface 1480 connects base station 1420 to a single CN deployment 1430, but it will be understood that wireless device 1410 may communicate with any number of CN deployments through interface 1480, and CN deployment 1430 may communicate with any number of base stations through interface 1480. Base station 1420 may include one or more other elements 1429 similar to one or more of one or more other elements 1419.

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

[0399] CN deployment 1440 may include elements similar to those of CN deployment 1430, as described above. CN deployment 1440 may include processing system 1441 and 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.

[0400] The processing system 1411, the processing system 1421, the processing system 1431 and / or the processing system 1441 may include one or more controllers and / or one or more processors. The one or more controllers and / or one or more processors may include, for example, a general purpose processor, a digital signal processor (DSP), a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) and / or other programmable logic devices, discrete gates and / or transistor logic, discrete hardware components, on-board units or any combination thereof. The processing system 1411, the processing system 1421, the processing system 1431 and / or the processing system 1441 may perform signal encoding / processing, data processing, power control, input / output processing and / or any other functions that may enable the wireless device 1410, the base station 1420, the CN deployment 1430 and / or the CN deployment 1440 to operate in a mobile communication system.

[0401] Each CN deployment may include one or more network functions. Depending on the context in which the term is used, a network function (NF) may refer to a specific set of functions and / or one or more physical elements configured to perform those functions (e.g., a processing system and a memory including instructions that, when executed by a processing system, cause the processing system to perform these functions). There are many different types of NFs, and each type of NF may be associated with a different set of functions. Different NFs may be flexibly deployed in different locations (e.g., in different physical core network deployments) or in the same location (e.g., juxtaposed in the same physical core network deployment). In addition, a physical CN deployment is not limited to the implementation of NFs. For example, a specific 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 specific physical core network deployment may be juxtaposed with one or more non-core elements (including elements of an access network or a data network).

[0402] Fig.15 A service-based architecture of a 5G network is shown with respect to the interaction of the control plane (CP) and the user plane (UP). The illustration may depict logical connections between nodes and functions, and the connections shown therein may not be construed as direct physical connections. A wireless device may form a radio access network connection with a base station, which is connected to a user plane (UP) function (UPF) through a network interface that provides a defined interface, such as the N3 interface. The UPF may provide a logical connection to a data network (DN) through a network interface, such as the N6 interface. The radio access network connection between a wireless device and a base station may be referred to as a data radio bearer (DRB).

[0403] DN may be a data network used to provide operator services, third-party services such as the Internet, IP Multimedia Subsystem (IMS), augmented reality (AR), virtual reality (VR). In some embodiments, DN may represent an edge computing network or resource, such as a mobile edge computing (MEC) network.

[0404] The wireless device is also connected to the AMF through a logical N1 connection. The AMF can be responsible for AA of access requests, as well as mobility management functions. The AMF can perform other roles and functions. From a service-based perspective, the AMF can communicate with other core network control plane functions through a service-based interface denoted as Namf.

[0405] The SMF is a network function that can be responsible for allocating and managing IP addresses assigned to wireless devices, as well as selecting the UPF for traffic associated with a specific session of the wireless device. There will typically be multiple SMFs in the network, each of which can be associated with a corresponding group of wireless devices, base stations, or UPFs. From a service-based perspective, the SMF can communicate with other core network functions through a service-based interface denoted as Nsmf. The SMF can also be connected to the UPF through a logical interface such as the network interface N4.

[0406] The Authentication Server Function (AUSF) can provide authentication services to other network functions through the service-based Nausf interface. The Network Exposure Function (NEF) can be deployed in the network to allow servers, functions and other entities, such as entities outside the trust domain (operator network), to be exposed to services and capabilities within the network. In one such example, the NEF can act as a proxy between an external application server (AS) outside the network shown and network functions such as PCF, SMF, UDM and AMF. The external AS can provide information that can be used in parameter settings associated with data sessions. The NEF can communicate with other network functions through the service-based Nnef network interface. The NEF may have an interface to non-3GPP functions.

[0407] A network repository function (NRF) may provide a network service discovery function. The NRF may be specific to the public land mobile network (PLMN) or network operator with which it is associated. The service discovery function may allow network functions and wireless devices connected to the network to determine where and how to access existing network functions.

[0408] The PCF may communicate with other network functions through a service-based Npcf interface and may be used to provide policies and rules to other network functions, including those within the control plane. The execution and application of policies and rules may not be the responsibility of the PCF. The responsibility of the functions to which the PCF transmits policies may be the responsibility of the AMF or SMF. In one such example, the PCF may transmit policies associated with session management to the SMF. This may be used to allow a unified policy framework with which network behavior may be managed.

[0409] The UDM may provide a service-based Nudm interface to communicate with other network functions. The UDM may provide data storage facilities to other network functions. Unified data storage may allow a unified view of network information that can be used to ensure that the most relevant information is available to different network functions from a single resource. This may allow other network functions to be implemented more easily because they may not need to determine where a particular type of data is stored in the network. The UDM may employ an interface such as Nudr to connect to the UDR. The PCF may be associated with the UDM.

[0410] The PCF may have a direct interface to the UDR, or may use the Nudr interface to connect to the UDR. The UDM may receive a request to retrieve content stored in the UDR, or a request to store content in the UDR. The UDM may be responsible for functions such as credential processing, location management, and subscription management. The UDR may also support authentication credential processing, user identity processing, access authorization, registration / mobility management, subscription management, and short message service (SMS) management. The UDR may be responsible for storing data provided by the UDM. The stored data is associated with policy profile information (which may be provided by the PCF) that manages access rights to the stored data. In some embodiments, the UDR may store policy data as well as user subscription data, which may include any or all of a subscription identifier, security credentials, access and mobility-related subscription data, and session-related data.

[0411] An application function (AF) may represent the non-data plane (also known as non-user plane) functionality of an application deployed within a network operator domain and within a 3GPP compliant network. The AF may be in an internal application server (AS). The AF may interact with other core network functions through a service-based Naf interface and may access network capability exposure information, as well as provide application information for use in decisions such as traffic routing. The AF may also interact with functions such as the PCF to provide application-specific input to policy and policy enforcement decisions. In many cases, the AF may not provide network services to other network functions. The AF may generally be viewed as a consumer or user of services provided by other network functions. Applications (application servers) outside the trust domain (operator network) may perform many of the same functions as the AF by using the NEF.

[0412] The wireless device can communicate with the network functions in the core network control plane (CN-UP) and the core network user plane (CN-CP). The UPF and the data network (DN) are part of the CN-UP. The DN may be outside the core network domain (cellular network domain). In the figure ( Fig.15 ), the base station is located on the CP-UP side. The base station can provide connectivity for both the CN-CP and the CN-UP. AMF, SMF, AUSF, NEF, NRF, PCF, and UDM can be functions residing in the CN-CP and are generally referred to as control plane functions. If the AF resides in the trust domain, the AF can communicate directly with other functions in the CN-CP via the service-based Naf interface.

[0413] If the AF resides outside the trust domain, the AM may communicate with other functions within the CN-CP indirectly via the NEF.

[0414] An unmanned and / or unmanned aerial vehicle (UAV) may be an aircraft without a human pilot or crew on board (e.g., unmanned) and / or without any passengers (e.g., unmanned). An unmanned and / or unmanned aerial system (UAS) may be a system used to operate a UAV. Fig.16 As shown, the UAS may include a UAV, a ground control system (e.g., a UAV controller), a camera, a positioning system, and / or any other suitable equipment for operating the UAS. A wireless network (e.g., a cellular network, a 4G cellular network, a 5G cellular network) may enable the ground control system (e.g., a UAV controller, a UTM, a USS) to communicate with the UAV, which may be one of the components of the UAS.

[0415] In an example, the wireless device may be a UAV. The wireless device may be an aerial wireless device. The wireless device may be flying above the ground. Fig.17As shown, the wireless device may experience a high probability of line-of-sight (LOS) propagation. The wireless device may receive downlink (e.g., from a base station to the wireless device) interference from a greater number of cells than a typical terrestrial wireless device. In the downlink direction, the number of neighboring cells has a higher probability of causing a high level of downlink interference at the wireless device than in the case of a terrestrial wireless device. In an example, the 16 cells causing high levels of downlink direction interference may be observed by the wireless device at an altitude of 50m or more. In an example, the antenna of a base station (e.g., eNB, gNB) may be tilted downward to serve the terrestrial wireless device. The wireless device may be located above the height of the antenna of the base station. The wireless device may be served by the side lobes of the antenna of the base station. The wireless device may see a stronger signal from a distant base station than the geographically nearest base station. The wireless device may be served by a distant base station instead of the nearest base station. The downlink direction path loss and the uplink direction path loss of an aeronautical wireless device may be different in some scenarios where reciprocity does not hold (e.g., due to different sidelobe orientations in the uplink and downlink, or different channel characteristics in frequency domain division deployment (FDD)).

[0416] The base stations of the wireless network and the wireless devices may use the radio access network (RAN) functions for aeronautical communication services (e.g., UAS, UAV, UAV controller, etc.). The base stations and the wireless devices may support the radio access network (RAN) functions for aeronautical communication services. The RAN functions for aeronautical communication services may be aeronautical user equipment (UE) communications. In an example, the aeronautical communication services may be aeronautical UE communications. The aeronautical communication services may support UAS. The RAN functions for aeronautical communication services may include altitude-based measurement reporting, interference detection for aeronautical UE communications, interference mitigation for aeronautical UE communications, flight path information reporting, location reporting for aeronautical UE communications, etc.

[0417] In an example, a base station may send an RRC message (e.g., an RRC configuration message, an RRC reconfiguration message) to a wireless device. The RRC message may include one or more measurement events regarding altitude-based measurement reporting. The one or more measurement events may indicate to the wireless device an altitude threshold for altitude-based measurement reporting. The wireless device may receive a measurement event including an altitude threshold. If the altitude of the wireless device is above or below the altitude threshold, the wireless device may send an altitude report. The altitude report may include the altitude of the wireless device, the location of the wireless device, etc.

[0418] If the received signaling power (e.g., RSRP) of multiple neighboring cells is above a certain level for the wireless device, the wireless device may experience or introduce interference. For interference detection, the base station can configure a radio resource management (RRM) event that triggers a measurement report when the individual (per cell) RSRP values ​​of a configured number of cells (e.g., 8, 16) meet the configured event. The configured event can be used for interference detection. The RRM event can be A3, A4, or A5. In response to determining that an RRM event occurs, the wireless device can send a measurement report.

[0419] In an example, to mitigate interference, a base station may be configured with a wireless device-specific alpha parameter for physical uplink shared channel (PUSCH) power control. The base station may send a radio resource control (RRC) message including the alpha parameter for PUSCH power control. If the wireless device receives a dedicated alpha parameter (e.g., alpha-UE) from the base station, the wireless device may apply the dedicated alpha parameter instead of the common alpha parameter.

[0420] In an example, a base station may request a wireless device to report flight path information by sending a user equipment information request message. The flight path information may include the number of waypoints defined as 3D locations. The user equipment information message may indicate the maximum number of waypoints and / or whether the waypoints require timestamps. The wireless device may receive the user equipment information message. If the wireless device is available to report the flight path, the wireless device may send a user equipment information response message to the base station. The user equipment response message may include one or more waypoints and one or more timestamps associated with the one or more waypoints. The base station may use the flight path information for congestion prediction or resource handling to mitigate interference.

[0421] In an example, for location reporting of aviation UE communications, the base station may request from the wireless device the horizontal and vertical speeds of the wireless device for location information reporting. The wireless device may send a location information report to the base station. The location information report may include horizontal speed, vertical speed, etc. The location information may also include the altitude of the wireless device.

[0422] Remote identification (RID) may be a technology to avoid collisions between different UAVs or between manned aircraft and UAVs. To prevent collision accidents, the Federal Aviation Administration (FAA) may integrate UAVs into the National Airspace System (NAS) by introducing RID. RID may be the ability of a UAS in flight to provide identification and tracking information that can be received by other parties, and may play a role in identifying unauthorized UAS in restricted areas and grounding them. In an example, UAVs above 0.55 pounds may be forced to support RID. There may be two types of RIDs: standard RIDs and restricted RIDs. For standard RIDs, UAVs may support network-issued identification (ID) and direct broadcast IDs. For restricted RIDs, UAVs may support network-issued IDs. For restricted RIDs, UAVs may not support direct broadcast IDs. Network-issued IDs may be based on communications via the Internet from a RID server provider that interfaces with the UAV. Direct broadcast IDs may be based on direct transmission of RIDs by the UAV using its onboard direct transmission technology (e.g., Bluetooth, Wi-Fi module). UAVs supporting restricted RIDs (e.g., not supporting direct broadcast IDs) may not be allowed to fly above 400 feet. UAVs supporting restricted RIDs may be required to have network connectivity during flight. UAS supporting standard RIDs may be allowed to fly above 400 feet and have no restrictions on network connectivity.

[0423] In an example, command and control communications may be user plane links to deliver messages with information about command and control of UAV operations from a UAV controller or UTM to the UAV. Command and control communications may be C2 communications. C2 communications include three types of communications: 1) direct C2 communications, 2) network-assisted C2 communications, and 3) UTM navigation C2 communications. Direct C2 communications may use a direct communication link between the UAV and the UAV controller. Network-assisted C2 communications may use a cellular network (e.g., a public land mobile network) for communications between the UAV and the UAV controller. For available UTM-navigated C2 communications, the UTM may provide the UAV with a pre-arranged flight plan, and the UTM may track and verify the latest restrictions or flight plan for the UAV.

[0424] Fig.18Exemplary interfaces (e.g., U2U, UAV3, UAV6, UAV8, UAV9) for a UAS with a wireless network (e.g., PLMN1, PLMN2) are shown. The interface may be a communication connection. In an example, the U2U interface may be an interface for direct broadcast ID. The UAV8 interface may be an interface for direct C2 communication between the UAV and the UAV controller. The UAV3 interface may be an interface between the UAV and the UAV controller via a wireless network. In an example, UAV3 may be intra-PLMN or inter-PLMN. In an example, for intra-PLMN, PLMN1 and PLMN2 may be the same PLMN. For inter-PLMN, PLMN1 and PLMN2 may be different PLMNs. In an example, UAV9 may be an interface between a UAV and a networked UAV controller and a USS / UTM for UAS management (e.g., authentication and / or authorization (AA), transmission C2, RID, and tracking of the UAV). In an example, UAV6 may be an interface between a PLMN (eg, a 3GPP network) and a USS / UTM for functional exposure, supporting identification and tracking, and UAV authentication and / or authorization.

[0425] like Fig.19 As shown, the wireless device may move along a movement path (e.g., a flight path) shown as a dotted line. In the example, the base station of "cell A" may not be working due to power outage or failure. When the wireless device moves through the area of ​​"cell A", the wireless device may experience a communication failure. The communication failure may be a short-term (e.g., 1 minute, 5 minutes) communication failure. The communication failure may be a communication interruption. In the example, there are no available base stations near the coverage area of ​​"cell B". After the wireless device leaves the coverage area of ​​"cell B" and moves to the right, the wireless device may experience a communication failure. The communication failure may be a long-term (e.g., 30 minutes, 1 hour) communication failure.

[0426] In an example, the wireless device may send a registration request message to the AMF via a base station. The registration request message may include an identification of the wireless device, capabilities of aviation services (e.g., aviation service capabilities, aviation communication service capabilities, UAS service capabilities), slice information, UAV identifiers (e.g., Civil Aviation Administration (CAA) UAV identifiers, etc.), and the like. In an example, the capabilities of aviation services may be whether the wireless device supports RAN functions for aviation services. In an example, the capabilities of aviation services may be whether the wireless device requires aviation services (e.g., acting as a UAV or UAV controller). The aviation domain or the functions of the aviation domain may assign a UAV identifier to the wireless device. In an example, the aviation domain may be UAS Traffic Management (UTM) or a UAS Service Provider (USS). The UAV identifier may be a CAA-level UAV identifier. The UAV identifier may be used for RID and tracking of the wireless device. The identification of the wireless device may include at least one of SUCI, 5G-GUTI, International Mobile Equipment Identity (IMEI), IMEI Software Version (IMEISV), a simplified version of 5G-GUTI, and the like.

[0427] In response to receiving the registration request message, the AMF may send a UE context request message to the subscription service (e.g., UDM, etc.). The UE context request message may include an identifier of the wireless device, capabilities of the UAS, slice information, etc. In an example, the identity of the wireless device may be a subscriber permanent identifier of the wireless device (e.g., IMSI, SUPI).

[0428] In an example, the UDM may receive a UE context request message from the AMF. In response to receiving the UE context request message, the UDM may send a UE context response message including subscription information of the wireless device to the AMF. The UDM may determine the subscription information based on the capability of the aviation service and the presence of slice information. In an example, if the capability of the aviation service is present in the UE context request message, the UDM may include the UAS subscription information in the subscription information. The subscription information may be subscription data. In an example, the subscription information may indicate whether the wireless device is allowed to obtain aviation services. In an example, the subscription information may indicate whether the wireless device is allowed to obtain aviation services. The subscription information may also indicate whether the aviation service requires authentication and / or authorization (AA).

[0429] The AMF may receive a UE context response message including subscription information. In response to receiving the UE context response message, the AMF may determine whether authentication and / or authorization (AA) for the aviation service is required. The determination may be based on capabilities provided by the wireless device, subscription information provided by the subscription server, etc. If the capability indicates that the wireless device does not support aviation services, the AMF may not allow aviation services and may not perform AA for the service.

[0430] In an example, the subscription information may indicate that the wireless device is allowed to obtain the aviation service. If the aviation service is allowed for the wireless device, the AMF may check whether the wireless device requires authentication and / or authorization (AA). If the service requires AA, the AMF may indicate to the wireless device that the AA for the aviation service is pending. When the AA for the aviation service of the wireless device is pending, the AMF may suppress the activation of RAN functions associated with the base station and the service of the wireless device.

[0431] If authentication and / or authorization (AA) for aviation services is required based on the subscription information, the AMF may perform the AA procedure for aviation services by sending an AA request message to the AA server. The AA server may be a UTM or USS. The AMF may send an AA request message to the AA server via the NEF or a new network device for aviation services. The AA request message may include a UAV identifier, GPSI, etc. The AA server may use the UAV identifier to identify the AA server or a wireless device within an aviation domain (e.g., UTM / USS). The 3GPP network (e.g., a cellular operator) may assign a GPSI for aviation services. The AA server may use the GPSI to communicate with the 3GPP network.

[0432] The AA request message may trigger the execution of authentication and / or authorization procedures between the AA server and the wireless device. Detailed procedures for service-specific AA procedures are described in Fig. 20 If the service-specific AA procedure is completed, the AA server may send an AA response message to the AMF. The AA response message may include an AA result, an authorization type, an authorization level, an authorization path, etc. In an example, AA completion may mean that the use of the service in the application layer between the wireless device and the AA server is ready.

[0433] In an example, the AMF may receive an AA response message from the AA server. In response to receiving the AA response message, the AMF may send a configuration update message indicating the AA result (e.g., whether the wireless device is authenticated and / or authorized for the aviation service). If the AA result indicates that the aviation service is not authenticated / authorized for the wireless device (e.g., AA failed), the wireless device may not request to establish one or more PDU sessions associated with the aviation service. If the AA result indicates that the aviation service is authenticated / authorized for the wireless device (e.g., AA succeeded), the wireless device may request to the SMF to establish one or more PDU sessions associated with the aviation service. In an example, the AAA-S may be an AA server.

[0434] Fig. 20An exemplary service-specific AA procedure is shown. The AMF may trigger the start of a service-specific AA procedure for a service. The AMF may be an MME. The AMF may send an Extensible Authentication Protocol (EAP) Identity Request for a service to the wireless device in a NAS MM transport message including the service name. The wireless device may provide an EAP Identity Response for the service along with the service name in a NAS MM transport message to the AMF. The AMF may send an EAP Identity Response to the AA server in an AA Request (EAP Identity Response, AAA-S Address, GPSI, Service Name) message. If there is an AAA-P (for example, because the AAA-S belongs to a third party and the operator deploys a proxy to the third party), the AA server forwards the EAP ID Response message to the AAA-P. Otherwise, the AA server forwards the message directly to the AAA-S. The AA server may use AAA protocol messages of the same protocol supported by the AAA-S to the AAA-P or AAA-S. The AAA-P may forward the EAP Identity message along with the service and GPSI to the AAA-S addressable by the AAA-S. AAA-S may store GPSI to create an association with the EAP identity in the EAP ID response message, so AAA-S can later use GPSI to revoke authorization or trigger reauthentication. EAP messages may be exchanged with the wireless device. One or more iterations of these steps may be performed. If EAP authentication is complete, AAA-S may store the services for which authorization has been granted, so AAA-S may decide to trigger reauthentication and / or reauthorization based on its local policy. EAP success / failure messages may be delivered to AAA-P (or directly to the AA server if AAA-P does not exist) along with GPSI and service name. If AAA-P is used, AAA-P may send an AAA protocol message including (EAP success / failure, service name, GPSI) to the AA server. The AA server may send an authentication response (EAP success / failure, service name, GPSI) to the AMF. The AMF may transmit a NAS MM transport message (EAP success / failure) to the wireless device. The AMF may store the EAP results for each service for which a service-specific AA procedure is performed. In an example, the AAA-S may be an AA server.

[0435] In the prior art, a wireless device (e.g., a UAS, a UAV, a UAV controller, etc.) may request to establish one or more sessions (e.g., a PDU session, a PDN connection, etc.). One or more sessions may be used for aviation services (e.g., aviation system services, UAS services, etc.). In order to establish one or more sessions, the wireless device may send a request to a session management entity (SME, e.g., a session management function (SMF), a mobility management entity (MME), etc.). It may be necessary (e.g., required) to determine the authentication and / or authorization (AA) of the wireless device (e.g., before the session can be established and / or the request can be accepted by the SME). The AA may require one or more communications between the wireless device and / or the network and a traffic manager (e.g., a UAS traffic management (UTM) or a UAS service provider (USS)). When the need (e.g., requirement) for AA for aviation services is introduced, the prior art for session management (e.g., request, establish, modify, accept, reject, etc.) may cause delays, ambiguity, and / or signaling overhead. For example, a wireless device may request the establishment of a session associated with an aviation service. At the time of the request, the AA may be incomplete and / or the result of the AA procedure may be unknown. As a result, the request may be denied, retried and denied again, accepted after a delay, etc. Additionally or alternatively, the request may be accepted without the necessary AA, resulting in an unauthorized and / or inoperable session.

[0436] According to an exemplary embodiment of the present disclosure, a mobility management function (MMF) (e.g., an access and mobility management function (AMF), a mobility management entity (MME), etc.) may determine the AA of an aviation service of a wireless device. The determination may be based on, for example, a registration request message received from the wireless device, or any other suitable signal or information that prompts the MMF to determine the AA of the wireless device. In an example, the registration or other signal / information may indicate an aviation service (e.g., may include a UAS indicator, a UAV identifier, etc. of the wireless device). The MMF may send an indication of the AA of the aviation service of the wireless device to a session management entity (SME) (e.g., a serving gateway (S-GW), a serving gateway controller (S-GW-C), a session management function (SMF), etc.). The indication may enable the SME to manage the session of the wireless device without the delay, ambiguity, or signaling overhead associated with the prior art (e.g., faster, more accurate, less signaling overhead, etc.).

[0437] In the prior art, a wireless device (e.g., a UAS, a UAV, a UAV controller, etc.) may establish one or more sessions (e.g., a PDU session, a PDN connection) for an aviation service (e.g., an aviation system service, a UAS service, etc.). To establish the one or more sessions, the wireless device may obtain authentication and / or authorization (AA) from a traffic manager (e.g., a UAS traffic manager (UTM) or a UAS service provider (USS)). The wireless device may request one or more sessions associated with the aviation service. If the wireless device obtains the AA from the traffic manager, the wireless device may be allowed to use the one or more sessions.

[0438] In an example, a problem may occur when the AA of a wireless device fails. A problem may occur when the traffic manager revokes the AA of a wireless device of a UAS. For example, the traffic manager may revoke the AA if the wireless device is outside of an authorized area, or the wireless device's subscription expires. If the AA of a wireless device of a UAS fails, one or more sessions associated with the UAS may be rejected. If the AA of a wireless device of a UAS is revoked, one or more sessions associated with the UAS may be released. Existing session rejection or release procedures may increase ambiguity for wireless devices and increase signaling exchanges to handle the procedure. Therefore, an enhanced session handling procedure for UAS failure or revocation may be needed.

[0439] According to an exemplary embodiment of the present disclosure, a network device (e.g., SMF, AMF) may terminate (e.g., release, reject PDU session establishment, deregister) one or more packet data unit (PDU) sessions associated with one or more aviation services of a wireless device. The network function may terminate the one or more PDU sessions associated with the one or more aviation services by sending an indication that the AA of the service of the wireless device is revoked or fails. The network device may terminate the one or more PDU sessions of the wireless device by sending a message indicating that the AA of the aviation service of the wireless device is revoked or fails. The network device may terminate the one or more PDU sessions by sending a second message indicating that the AA of the command and control (C2) of the aviation service of the wireless device is revoked or fails. The network device may indicate the level, category, or type of AA revocation or failure. Based on different levels of AA revocation (e.g., per aviation service, per C2 service), the wireless device may be able to handle sessions associated with the aviation service without further signaling exchange.

[0440] According to an exemplary embodiment of the present disclosure, a session management function (SMF) may receive a first message from a network device (e.g., AMF, traffic manager). The first message may indicate that the AA of the aviation service of the wireless device is revoked or fails. The SMF may determine to release one or more packet data unit (PDU) sessions based on the first message. The SMF may determine to reject the PDU session establishment based on the first message. One or more PDU sessions may be associated with aviation services. The SMF may send a second message indicating the determination to the wireless device. The second message may include a reason parameter indicating that the AA of the aviation service of the wireless device is revoked or fails. An exemplary embodiment may allow the SMF to determine that the PDU session release or rejection is associated with the AA of the aviation service. An exemplary embodiment may allow the SMF to determine that the PDU session release or rejection is associated with the AA of the aviation service rather than the network device. Therefore, the release or rejection can be determined dynamically and intelligently (e.g., if the PDU session has a higher priority, the SMF may determine not to release or reject the PDU session).

[0441] According to an exemplary embodiment of the present disclosure, a wireless device may receive a message from an SMF requesting modification of a PDU session. The message may include a cause parameter indicating that, for example, the AA of C2 of the UAS is revoked or fails. The message may indicate a QoS flow to be deleted from the PDU session. In the example, the indicated QoS flow may be associated with C2. The exemplary embodiment may reduce ambiguity for the wireless device by indicating the cause. In the absence of a cause parameter, the wireless device may request modification of the PDU session to request one or more QoS flows of C2. Based on the cause parameter, the wireless device may reduce delays and / or signaling overhead by avoiding useless and / or unnecessary modification requests. Based on the cause parameter, before requesting the modification, the wireless device may request an AA server (e.g., UTM / USS) to update the credentials of the AA of C2.

[0442] According to an exemplary embodiment of the present disclosure, a mobility management function (MME) may receive a first message from a wireless device requesting to establish a packet data network (PDN) connection. The PDN connection may be associated with an aviation service. The MME may send a second message to a serving gateway (S-GW) requesting to create a PDN connection. The MME may receive a third message indicating a reason parameter that the AA of the aviation service of the wireless device is revoked or fails. The MME may send a fourth message indicating a refusal to establish the PDN connection. The fourth message may include a reason. The exemplary embodiment may reduce ambiguity of the wireless device by indicating the reason as the AA of the aviation service of the wireless device being revoked or failing.

[0443] According to an exemplary embodiment of the present disclosure, the MME may receive a first message requesting the release of the bearer of the wireless device from a serving gateway (S-GW). The first message may include a cause parameter indicating that the AA of the air service of the wireless device is revoked or fails. The MME may determine that the first message may result in the release of the last packet data network (PDN) connection of the wireless device. Based on the determination, the MME may send a second message requesting the wireless device to detach. The second message may be a detach request message. The second message may include a cause parameter indicating that the AA of the air service of the wireless device is revoked or fails. Based on the cause parameter, the wireless device may realize that the UTM or USS may need the AA of the air service. The exemplary embodiment may reduce the ambiguity of the MME by introducing a determination condition for the detachment of the wireless device regarding the revocation of the AA of the air service. The exemplary embodiment may reduce the signaling overhead of the wireless device by indicating the detachment cause of the wireless device. Based on the cause parameter that the AA of the air service is revoked or fails, the wireless device may not send an attachment request to the MME. Based on the cause parameter that the AA of the air service is revoked or fails, the wireless device may update the AA of the air service to the UTM / USS.

[0444] Fig.21 and Fig. 22 An exemplary session handling procedure for a 5G network and a wireless device regarding the revocation / failure of an AA for an airline service is shown. In the example, the wireless device may register with the 5G network. Fig.19 As shown, the AMF may perform an AA procedure for the aviation service. The SMF may receive a first message from a network device indicating that the AA (AA) of the aviation service of the wireless device is revoked or failed. The first message may be a PDU session creation message. The first message may be a PDU session update message. The SMF may determine to reject one or more PDU session establishments. The SMF may determine the release of one or more PDU sessions of the wireless device. One or more PDU sessions may be associated with the aviation service. The SMF may send a second message indicating the determination to the wireless device. The second message may include a cause parameter indicating that the AA of the aviation service of the wireless device is revoked or failed. The cause parameter may indicate that the AA of the command and control (C2) of the wireless device is revoked or failed. In an example, the wireless device may be a UAV. The wireless device may be a UAV controller.

[0445] Fig.21 A call flow is shown in which the SMF notifies the wireless device of a rejection of an establishment request for one or more PDU sessions based on the AA status of the aeronautical service received from the network device. The network device may be the AMF.

[0446] The wireless device may send a PDU session establishment request message to the AMF to obtain aviation services (e.g., communicating with UTM / USS, C2 sessions). The PDU session establishment request message may include UAS capabilities (e.g., aviation service capabilities, UAS service capabilities, etc.), PDU session identifiers, UAV identifiers, DNNs, S-NSSAIs, etc. The DNNs and / or S-NSSAIs may be associated with aviation services. In an example, the DNNs may indicate aviation services or C2 services. The S-NSSAIs may indicate aviation services or C2 services.

[0447] In response to receiving a PDU session establishment request associated with an aviation service, the AMF may call a create session management (SM) context request service with an SMF service by sending a first message (e.g., a create SM context request message, Nsmf_PDUSession_CreateSMContext) to the SMF. The first message may be a create SM context request message. The create SM context request message may include an identifier of the wireless device, a DNN, an S-NSSAI, UAS capabilities, a PDU session identifier, a UAV identifier, an SM container including the PDU session establishment request message, and the like. In an example, the create SM context request message may also include an AA (AA) status of the UAS of the wireless device. The AA status of the UAS may indicate whether the wireless device is authenticated and / or authorized for aviation services. The AA status of the aviation service of the wireless device may include a first parameter indicating whether the wireless device is authenticated and / or authorized for aviation services. The AA status of the aviation service of the wireless device may include a second parameter indicating whether the wireless device is authenticated and / or authorized for C2 of the aviation service.

[0448] In an example, the SMF may receive a Create SM Context Request message from the AMF. In an example, the SMF may determine whether to accept or reject the Create SM Context Request based on the AA status of the aviation service. If the AA status indicates that the wireless device is authenticated and / or authorized for aviation services, the SMF may determine to accept the Create SM Context Request. If the AA status indicates that the wireless device is not authenticated and / or authorized for aviation services, the SMF may determine to reject the Create SM Context Request. In an example, the PDU session may be a higher priority PDU session (e.g., an emergency PDU session). If the AA status indicates that the wireless device is not authenticated and / or authorized for aviation services, the SMF may determine to accept the Create SM Context Request.

[0449] Based on the determination, the SMF may send a create SM context response message to the AMF. The SM context response message may include a PDU session accept message. The SMF context response message may include a PDU session reject message. The PDU session reject message may include a cause parameter indicating that the AA of the UAS of the wireless device is revoked or failed. The PDU session reject message may include a cause parameter indicating that the AA of the C2 of the aviation service is revoked or failed.

[0450] In response to receiving the Create SM Context Response message, the AMF may send a PDU Session Reject message to the wireless device. In response to receiving the PDU Session Reject message, the wireless device may send a Confirmation message. In response to receiving the Cause parameter, the wireless device may update the AA status of the aviation service of the wireless device. The wireless device may not request a PDU session establishment associated with the aviation service. The wireless device may not request a PDU session establishment associated with the aviation service before indicating to the AMF that the aviation service is (re)authenticated and (re)authorized. This exemplary embodiment may reduce potential PDU session rejections by indicating the AA status of the aviation service to the wireless device.

[0451] Fig. 22 A situation is shown in which the SMF determines the release of one or more PDU sessions regarding the revocation or failure of the AA (AA) of the aviation service. In the example, the wireless device may request to establish one or more PDU sessions associated with the aviation service. The SMF may accept the establishment of one or more PDU sessions associated with the aviation service. Later, the SMF may receive a first message from a network device indicating that the AA of the aviation service of the wireless device is revoked or failed. In response to receiving the first message, the SMF may determine to release one or more PDU sessions associated with the aviation service. Based on the determination, the SMF may send a second message to the wireless device to indicate the release of the one or more PDU sessions. The second message may include a reason parameter indicating that the AA of the aviation service of the wireless device is revoked or failed. The reason parameter may further indicate that the AA of C2 of the aviation service of the wireless device is revoked or failed.

[0452] In an example, the network device may be an AMF. The first message may be an update session management (SM) context request message (Nsmf_PDUSession_UpdateSMContext). The update SM context request message may include an SM context identifier, user equipment (UE) location information, and an indication that the AA of the UAS is revoked or failed. The SM context identifier may identify one or more PDU sessions. The SMF may send an update SM context response message including a second message to the AMF. The second message may be a PDU session release command message. The PDU session release command message may include one or more PDU session identifiers, a reason parameter indicating that the AA of the aviation service is revoked or failed, etc. In response to receiving the update SM context response message, the AMF may send a PDU session release message to the wireless device. In response to receiving the PDU session release command message, the wireless device may delete information associated with one or more PDU sessions.

[0453] In an example, the network device may be an AA server (e.g., UTM, USS) for aviation services. The first message may be an AA (AA) revocation request message. The AA revocation request message may include an indication that the AA for the aviation services of the wireless device is revoked or fails. The AA revocation request message may further indicate that the AA for the command and control (C2) of the aviation services of the wireless device is revoked or fails. The AA revocation request message may include an indication that the AA for the command and control (C2) of the aviation services of the wireless device is revoked or fails. In response to receiving the AA revocation request message, the SMF may determine the release of one or more PDU sessions. Based on the determination, the SMF may invoke message delivery to the AMF by sending an N1N2 message transfer message including a second message. In response to receiving the N1N2 message transfer message from the SMF, the AMF may send a second message (e.g., a PDU session release command) to the wireless device.

[0454] In response to receiving the PDU Session Release Command message, the wireless device may send a PDU Session Release Complete message to the SMF. Based on the cause parameter, the wireless device may update the AA status of the air service of the wireless device. The wireless device may not request a PDU session establishment associated with the air service. The wireless device may not request a PDU session establishment associated with the air service before indicating to the AMF that the air service is (re)authenticated and (re)authorized. This exemplary embodiment may reduce potential PDU session rejections by indicating the AA status of the air service to the wireless device.

[0455] Fig.23An exemplary session modification procedure for a 5G network and a wireless device regarding the revocation / failure of AA for aviation services is shown. The wireless device may be a UAV or a UAV controller. The SMF may send a message to the wireless device requesting modification of a PDU session. The PDU session may be associated with an aviation service. The message may be a PDU session modification command message. The message may include a PDU session identifier indicating the PDU session, a cause parameter indicating that the AA (AA) of C2 for aviation services is revoked or failed, and the like. The message may also include one or more QoS flows to be deleted from the PDU session. In an example, one or more QoS flows may be associated with C2. The wireless device may receive a message from the SMF. The wireless device may delete one or more QoS flows based on the message. In response to receiving the message, the wireless device may send a response message (e.g., PDU session modification completed) to indicate the completion of the modification. Based on the cause parameter, the wireless device may update the AA status of the aviation service, i.e., the AA of C2 is revoked or failed. Based on the cause parameter, the wireless device may not send a PDU session modification request message to obtain the C2 service.

[0456] Based on the cause parameter, the wireless device may not request to modify the PDU session to request one or more QoS flows of C2.Exemplary embodiments may reduce signaling exchanges by indicating the withdrawal / failure of the AA of C2 to the wireless device during the modification procedure.

[0457] Fig.24 A 4G system (e.g., an evolved packet system) including an access network and a 4G core network is depicted. An exemplary 4G access network may include an access network connected to a 5G core network. The access network may include a RAN. An exemplary 4G core network may be connected to one or more 4G access networks. The 4G core network may include an MME, an HSS, a gateway (e.g., S-GW, PDN-GW), etc. The MME may be a node responsible for the functions of the AMF and SMF of the 5G system. The gateway may be a node responsible for the UPF function. The HSS may be a node responsible for the function of the UDM. In an example, a wireless device (e.g., a UE) may attach to the MME by sending an attach request message to obtain services from the 4G system. The wireless device may send a PDN connection request message to the MME to conduct a session with a data network (DN) via a gateway (e.g., S-GW, PDN-GW).

[0458] Fig.25 An exemplary session handling procedure for a failed 4G network and a wireless device for an AA of an airline service is shown. In an example, the wireless device may perform an attach procedure by sending an attach request message to the MME. The MME may send an attach accept message to the wireless device in response to receiving the attach request message.

[0459] The wireless device may be a UAV. The wireless device may be a UAV controller. The wireless device may send a first message requesting to establish a packet data network (PDN) connection associated with an aviation service. The first message may be a PDN connection request message to obtain an aviation service (e.g., communicating with a UTM / USS, C2 session / C2 service). The first message may include UAS capabilities, a UAV identifier, etc. The MME may receive the first message. In response to receiving the first message, the MME may send a second message requesting to create a PDN connection to a PDN gateway (P-GW) via a serving gateway (S-GW). The second message may be a create session request message. The second message may include a protocol configuration option (PCO), an APN, UAS capabilities, and an AA status of an aviation service. In an example, the protocol configuration option (PCO) may include information of an AA for an aviation service. The APN may be associated with an aviation service. In an example, the P-GW may perform AA for an aviation service by sending an AA request message to an AA server (e.g., UTM / USS). The AA request message may include a UAV identifier, a PCO, etc. The P-GW may receive an AA response message for the AA request. The AA response message may include a result of the AA request. The P-GW may determine whether to accept or reject the creation of the PDN connection. The determination may be based on the result. In the example, if the result indicates that the AA of the aviation service has failed, the P-GW may determine to reject the creation of the PDN connection. Based on the determination, the P-GW may send a third message to the MME via the S-GW. The third message may be a create session response message. The third message may include the result of the AA failure of the PCO, the UAS, etc. In response to receiving the third message, the MME may send a fourth message indicating the rejection of the creation of the PDN connection. The fourth message may be based on the third message. The fourth message may be a PDN connection rejection message. The fourth message may include a cause parameter indicating the AA failure of the aviation service.

[0460] In an exemplary implementation, the first message may be a PDN connection (e.g., a C2 session) for a C2 service. The first message may include a second PCO, the second PCO including AA information for the C2 service. The APN of the first message may be associated with the C2 service. The P-GW may perform AA (AA) for the C2 service by sending an AA request message to an AA server. The AA request message may include a UAV identifier, a second PCO, a UAV identifier of a paired UAV device, and the like. In an example, the wireless device may be a UAV. If the wireless device is a UAV, the UAV identifier of the paired UAV device may be a UAV identifier of a UAV controller of the wireless device. In an example, the wireless device may be a UAV controller. If the wireless device is a UAV controller, the UAV identifier of the paired UAV device may be a UAV identifier of a UAV of the wireless device. The P-GW may receive an AA response message to the AA request message. The AA response message may include a result of the AA request. The P-GW may determine whether to accept or reject the creation of the PDN connection. The determination may be based on the result. In an example, if the result indicates that the AA of C2 fails, the P-GW may determine to reject the creation of the PDN connection associated with the C2 service. Based on the determination, the P-GW may send a third message to the MME via the S-GW. The third message may be a create session response message. The third message may include the PCO, a result indicating the failure of AA of C2, etc. In response to receiving the third message, the MME may send a fourth message indicating a rejection of creating a PDN connection. The fourth message may be based on the third message. The fourth message may be a PDN connection rejection message. The fourth message may include a cause parameter. The cause parameter may be based on the result. The cause parameter may indicate the failure of AA of C2.

[0461] In an exemplary implementation, the PDN connection associated with the airline service may be a default PDN connection for the wireless device. If the PDN connection associated with the airline service is the default PDN connection, then Fig.25 The depicted procedure may be performed as part of an attach procedure. The attach request message may include a first message (e.g., a PDN connection request). The AA for the aviation service may fail. If the AA for the UAS fails, the P-GW may reject the creation of the PDN connection. In response to receiving a third message indicating that the creation of the PDN connection is rejected, the MME may send an attach reject message to the wireless device. The attach reject message may include a PDN connection reject message, a cause value, etc. The cause value may indicate that the AA for the aviation service failed.

[0462] Fig.26An exemplary session handling procedure for a 4G network and a wireless device regarding the revocation of an AA for aviation services and C2 services is shown. The wireless device may have one or more PDN connections associated with aviation services or C2 services. In an example, the P-GW may detect that the AA for aviation services or the AA for C2 services is revoked or fails. In response to the detection, the P-GW may trigger a bearer deactivation procedure by sending a first message to the MME via the S-GW. The first message may be a delete bearer request message. The first message may include a cause parameter indicating that the AA for aviation services or the AA for C2 services is revoked or fails. In response to receiving the first message, the MME may determine that the first message causes the release of the last PDN connection of the wireless device. If the first message causes the release of the last PDN connection, the MME may send a second message to the wireless device requesting the detachment of the wireless device. The second message may be a detach request message. The second message may include a cause parameter indicating that the AA for aviation services is revoked or fails. The second message may include a cause parameter indicating that the AA for C2 services is revoked or fails. In an example, in the absence of a PDN connection, the wireless device or the MME may not support attachment. The first message may include a linked evolved packet system (EPS) bearer identifier (LBI), one or more EPS bearer identifiers, a cause parameter, etc. In an example, the cause parameter may also include that the radio access technology (RAT) is changed from a third generation partnership project (3GPP) to non-3GPP. In an example, the wireless device may receive a detach request message indicating that the AA for the aviation service is revoked or failed. The wireless device may send a second attach request message requesting reauthentication and reauthorization for the aviation service. Sending the second attach request message may be based on the indication (e.g., the AA for the aviation service is revoked or failed).

[0463] In an exemplary implementation, the MME may determine that the first message will not result in the release of the last PDN connection of the wireless device. Based on the determination, the MME may send a third message requesting the bearer to be deactivated. The third message may include a cause parameter. The third message may be a deactivate EPS bearer context request message.

[0464] In an exemplary implementation, the MME and the wireless device may support attaching without a PDN connection. Based on the determination, the MME may send a fourth message requesting deactivation of the bearer. The fourth message may include a cause parameter. The fourth message may be a Deactivate EPS Bearer Context Request message. In response to receiving the fourth message, the wireless device may send a Deactivate PES Bearer Context Accept message to the MME.

[0465] In an example, a session management function (SMF) may receive a first message from a network device indicating that an AA (AA) for an aviation service of a wireless device is revoked or failed. The SMF may determine to release one or more packet data unit (PDU) sessions. The SMF may determine to reject the establishment of one or more PDU sessions. The determination may be based on the first message. The SMF may send a second message indicating the determination to the wireless device. The second message may include a reason parameter indicating that the AA for the aviation service of the wireless device is revoked or failed.

[0466] According to an exemplary embodiment, one or more PDU sessions may be associated with an airline service.

[0467] According to an exemplary embodiment, the network device may be an access and mobility management function (AMF). The first message may be a PDU session creation message. The first message may include a subscriber permanent identifier (SUPI) or a permanent equipment identifier (PEI), a data network name (DNN), an identifier of the AMF, a PDU session identifier, a session management container, an indication that the AA of the UAS is revoked or failed, etc. The session management container may include a PDU session establishment request message.

[0468] According to an exemplary embodiment, the network device may be an access and mobility management function (AMF). The first message may be a PDU session update message. The first message may include a session management (SM) context identifier, user equipment (UE) location information, an indication that the AA of the UAS is revoked or failed, etc.

[0469] According to an exemplary embodiment, the SMF may receive a first non-access stratum (NAS) message from the wireless device requesting the establishment of a PDU session for aviation services. The SMF may send a second NAS message to the wireless device accepting the establishment of the PDU session for aviation services. The first NAS message may include a Civil Aviation Administration (CAA) unmanned aircraft (UAV) identifier, a PDU session identifier, a subscriber permanent identifier (SUPI) or a permanent equipment identifier (PEI), a data network name (DNN), single network slice selection assistance information, etc.

[0470] According to an exemplary embodiment, the network device may be an AA server for aviation services. The network device may be a UAS traffic management (UTM) server. The network device may be an aviation service provider (USS) server. The first message may be an AA revocation request message. The AA revocation request message may include an indication that the AA of the aviation service of the wireless device is revoked or failed. The indication may further indicate that the AA of the command and control (C2) of the wireless device is revoked or failed.

[0471] According to an exemplary embodiment, the wireless device may be an unmanned aerial vehicle (UAV).The wireless device may be an unmanned aerial vehicle (UAV) controller.

[0472] In an example, the wireless device may receive a message from a session management function (SMF) requesting termination of a packet data unit (PDU) session. The message may include a cause parameter. The cause parameter may indicate that an AA for air service (AA) of the wireless device is revoked or failed. The cause parameter may indicate that an AA for command and control (C2) of the wireless device is revoked or failed. The wireless device may send a confirmation message indicating completion of the termination based on the message.

[0473] According to an exemplary embodiment, the termination may be the release of an established PDU session.The message is a PDU Session Release Command message.

[0474] According to an exemplary embodiment, the wireless device may send a first non-access stratum (NAS) message to the SMF requesting establishment of a PDU session for the aeronautical service. The wireless device may receive a second NAS message from the SMF accepting establishment of the PDU session for the aeronautical service.

[0475] According to an exemplary embodiment, termination may be a refusal to establish a PDU session.

[0476] According to an exemplary embodiment, the message may be a PDU Session Reject message.

[0477] According to an exemplary embodiment, the wireless device may update the AA state of the UAS based on the cause parameter. The AA state of the UAS may include at least one of the following: a first parameter indicating whether the wireless device is authenticated and / or authorized for aviation service; a second parameter indicating whether the wireless device is authenticated and / or authorized for aviation service C2.

[0478] In an example, the wireless device may receive a message from a session management function (SMF) requesting release of a first packet data unit (PDU) session. The message may include a cause parameter indicating that the AA for aviation services (AA) is revoked or the AA for command and control (C2) of aviation services is revoked. Based on the message, the wireless device may send a confirmation message indicating that the release is complete.

[0479] According to an exemplary embodiment, in response to a cause parameter indicating that the AA for the aviation service is revoked, the wireless device may determine not to request to establish a PDU session associated with the aviation service. In response to a cause parameter indicating that the AA for the C2 of the aviation service is revoked, the wireless device may determine not to request to establish a PDU session associated with the aviation service.

[0480] In an example, the wireless device may send a registration request message including aviation service capabilities to an access and access and mobility management function (AMF). The wireless device may receive a registration rejection message from the AMF indicating that the AA (AA) for aviation services is revoked or failed. The AA for aviation services may also include that the AA (AA) for aviation services is revoked; or the AA for command and control (C2) of aviation services is revoked.

[0481] In an example, the wireless device may receive a message from a session management function (SMF) requesting modification of a packet data unit (PDU) session. The message may include a reason parameter indicating that an AA (AA) of a command and control (C2) of the wireless device was revoked or failed. The wireless device may send a confirmation message indicating completion of the termination based on the message.

[0482] According to an exemplary embodiment, the reason parameter may further indicate that the AA of the airline service (AA) is revoked.

[0483] In an example, a mobility management entity (MME) may receive a first message from a wireless device requesting establishment of a packet data network (PDN) connection associated with an aviation service. The MME may send a second message to a serving gateway (S-GW) requesting the creation of the PDN connection. The MME may receive a third message from the S-GW indicating a cause parameter that an AA for the aviation service of the wireless device is revoked or failed. The MME may send a fourth message to the wireless device indicating a rejection of establishing the PDN connection. The fourth message may include a cause.

[0484] In an example, a wireless device may send a first message to a mobility management entity (MME) requesting establishment of a packet data network (PDN) connection associated with an aviation service. The wireless device may receive a second message from the MME indicating a rejection of the request to establish. The second message may include a cause parameter indicating that the AA of the aviation service of the wireless device is revoked or failed. The first message may be a PDN connection request message. The PDN connection request message may include a capability indication of the aviation service, a Civil Aviation Authority (CAA) unmanned aircraft (UAV) identifier, a packet data name (APN) associated with the aviation service, and the like. In an example, the attachment request message may include a PDN connection request message. The second message may be a PDN connection rejection message. The PDN connection rejection message may include a second cause parameter, which includes: user authentication failure, AA failure or revocation of the UAS, AA failure or revocation of the command and control (C2).

[0485] In an example, the second message may be a Detach Request message.The PDN connection may be the last PDN connection of the wireless device.

[0486] In an example, a mobility management entity (MME) may receive a first message from a serving gateway (S-GW) requesting the release of a bearer of a wireless device. The first message may include a cause parameter indicating that an AA (AA) of an aviation service of the wireless device is revoked or fails. The MME may determine that the first message causes the release of the last packet data network (PDN) connection of the wireless device. Based on the determination, the MME may send a second message to the wireless device requesting the detachment of the wireless device, the second message including the cause parameter. In the absence of a PDN connection, the wireless device of the MME may not support attachment. The first message may be a delete bearer request message. The delete bearer request message may include a linked evolved packet system (EPS) bearer identifier (LBI), one or more EPS bearer identifiers, a cause parameter, and the like. The cause parameter may include an indication indicating that an AA of an aviation service is revoked or fails, an indication indicating that an AA of a command and control (C2) is revoked or fails, or an indication indicating that a radio access technology (RAT) is changed from a third generation partnership project (3GPP) to a non-3GPP.

[0487] In an example, the MME may determine that the first message will not result in a release of a last packet data network (PDN) connection of the wireless device. Based on the determination, the MME may send a third message to the wireless device requesting deactivation of the bearer, the third message including a cause parameter.

[0488] In an example, the MME may determine that the wireless device and the MME support attaching without a PDN connection.Based on the determination, the MME may send a fourth message to the wireless device requesting deactivation of the bearer, the fourth message including a cause parameter.

[0489] In an example, the wireless device may receive a Detach Request message from a Mobility Management Entity (MME), the Detach Request message including a cause value indicating that AA for an aviation service of the wireless device is revoked or failed. Based on the cause value, the wireless device may send an Attach Request message to the MME requesting reauthentication and reauthorization of the aviation service. The wireless device may send a Detach Request Accept message to the MME, wherein the Detach Request Accept message is responsive to receiving.

[0490] The present disclosure may relate to possible combinations of enumerated elements. For the sake of brevity and readability, the present disclosure does not explicitly describe each arrangement that can be obtained by selecting from the set of optional features. The present disclosure should be interpreted as explicitly disclosing all such arrangements. For example, seven possible combinations of enumerated elements A, B, and C consist of the following: (1) "A"; (2) "B"; (3) "C"; (4) "A and B"; (5) "A and C"; (6) "B and C"; and (7) "A, B, and C". For the sake of brevity and readability, these seven possible combinations can be described using any of the following interchangeable expressions: "at least one of A, B, and C"; "at least one of A, B, or C"; "one or more of A, B, and C"; "one or more of A, B, or C"; "A, B, and / or C". It should be understood that impossible combinations are excluded. For example, "X and / or non-X" should be interpreted as "X or non-X". It should also be understood that these expressions may describe alternative wordings of overlapping and / or synonymous concepts, for example, "identifier, identification and / or ID number."

[0491] In this specification, "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 after the term "may" is an example of a suitable possibility among multiple suitable possibilities that may or may not be used for one or more embodiments in various embodiments. If A and B are sets, and each 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, the possible subsets of B = {cell1, cell2} are: {cell1}, {cell2}, and {cell1, cell2}. In this specification, a parameter (information element: IE) can include one or more objects, and each of those objects can 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 an exemplary embodiment, when one or more messages include multiple parameters, this means that the parameters in the multiple parameters are in at least one of the one or more messages, but not necessarily in each of the one or more messages. Many elements described in the disclosed embodiments can be implemented as modules. Modules are defined here as separable elements that perform defined functions and have defined interfaces to other elements. The modules described in this disclosure can be implemented in hardware, software combined with hardware, firmware, wetware (i.e., hardware with biological elements) or a combination thereof, all of which can be equivalent in behavior. For example, a module can be implemented as a software routine written in a computer language, and the computer language is 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 LabVIEWMathScript). In addition, it is possible to implement a module using physical hardware that incorporates 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, C++, etc. FPGAs, ASICs, and CPLDs are often programmed using hardware description languages ​​(HDLs), such as VHSIC Hardware Description Language (VHDL) or Verilog, which configure the connections between internal hardware blocks with less functionality on the programmable device. Finally, it is important to emphasize that the above techniques are often used in combination to achieve the results of functional blocks.Exemplary embodiments of the present invention may be implemented using various physical and / or virtual network elements, software-defined networks, and virtual network functions. The disclosure of this patent document incorporates copyrighted materials. The copyright owner has no objection to anyone reproducing the patent document or patent disclosure as it appears in the patent and trademark office patent documents or records for the limited purpose required by law, but reserves all copyright rights in any other respects. Although various embodiments have been described above, it should be understood that they are presented by way of example and not limitation. It will be apparent to those skilled in the relevant art that various changes can be made in form and detail without departing from the spirit and scope of the present disclosure. In fact, after reading the above description, it will be apparent to those skilled in the relevant art how to implement alternative embodiments. Therefore, the current embodiment should not be limited to any of the above exemplary embodiments. In particular, it should be noted that, for the purpose of illustration, the above explanation has focused on the example of using a 5G AN. However, those skilled in the art will recognize that embodiments of the present invention may also be implemented in systems including one or more legacy systems or LTE. The disclosed methods and systems may be implemented in wireless or wired systems. The features of the various embodiments presented in the present invention may be combined. One or more features (methods or systems) of one embodiment may be implemented in other embodiments. A limited number of example combinations are shown to indicate to those skilled in the art the possibility of combining in various embodiments to create enhanced transmission and reception systems and methods of features. In addition, it should be understood that any diagram highlighting the functions and advantages is presented for the purpose of example only. The disclosed architecture is flexible and configurable enough so that it can be utilized in a manner different from that shown. For example, the actions listed in any flow chart can be reordered or optionally used in certain embodiments. In addition, the purpose of the abstract of the present disclosure is to generally enable the U.S. Patent and Trademark Office and the public, especially scientists, engineers and practitioners in the field who are not familiar with patent or legal terms or phrases, to quickly determine the nature and essence of the technical disclosure of the present application by a rough review. The abstract of the present disclosure is not intended to limit the scope in any way. Finally, the applicant's intention is that only claims that include the expression language "device for..." or "step for..." are interpreted according to 35 USC 112. Claims that do not explicitly include the phrase "device for..." or "step for..." should not be interpreted according to 35U.SC 112.

Claims

1. A session management method for an aviation system, the method comprising: Receiving, by an access and mobility management function (AMF) means, a registration request message for the wireless device from the wireless device; triggering, by the AMF means, an authentication and / or authorization procedure for aviation services of the wireless device; Receiving, by the AMF device, a protocol data unit (PDU) session establishment request from the wireless device to establish a PDU session associated with the aviation service; as well as Based on receiving the PDU session establishment request from the wireless device, the AMF device sends a create session management context message to the session management function SMF device, and the create session management context message includes an indication of whether the aviation service of the wireless device has been authenticated and / or authorized by the unmanned aerial system service provider USS.

2. The method of claim 1 further comprises the AMF device receiving an indication from the SMF device as to whether the PDU session establishment request is accepted.

3. The method of claim 1 , further comprising sending a protocol data unit session establishment reject message to the wireless device, the protocol data unit session establishment reject message indicating a rejection of the PDU session establishment request and including a cause value associated with the rejection.

4. The method of claim 1, wherein the create session management context message indicating whether the aeronautical service of the wireless device has been authenticated and / or authorized by the USS is a create session management context request message.

5. The method of claim 1, wherein the registration request message of the wireless device includes an aircraft identifier of the wireless device. The method of claim 1 , wherein the PDU session is used to communicate with the USS.

7. The method of claim 1, wherein the PDU session is used for command and control communication of the USS.

8. The method of claim 1, wherein performing an authentication and / or authorization procedure comprises sending an authentication and / or authorization request by the AMF device to the USS.

9. The method of claim 8, wherein the authentication and / or authorization request includes an aviation service identifier of the wireless device.

10. The method of claim 8, wherein the authentication and / or authorization request includes a General Public Subscription Identifier (GPSI) of the wireless device.

11. An access and mobility management function (AMF) device for session management of an aviation system, comprising one or more processors and a memory storing instructions, wherein the instructions, when executed by the one or more processors, cause the AMF device to: receiving, from a wireless device, a registration request message for the wireless device; triggering an authentication and / or authorization procedure for aviation services of the wireless device; receiving a protocol data unit (PDU) session establishment request from the wireless device to establish a PDU session associated with the aviation service; as well as Based on receiving the PDU session establishment request from the wireless device, a create session management context message is sent to a session management function SMF device, wherein the create session management context message includes an indication of whether the aviation service of the wireless device has been authenticated and / or authorized by an unmanned aerial system service provider USS.

12. The apparatus of claim 11, further comprising receiving, by the AMF device, an indication from the SMF device as to whether the PDU session establishment request is accepted.

13. The apparatus of claim 11, further comprising sending a protocol data unit session establishment reject message to the wireless device, the protocol data unit session establishment reject message indicating a rejection of the PDU session establishment request and including a cause value associated with the rejection.

14. The apparatus of claim 11, wherein the create session management context message indicating whether the aeronautical service of the wireless device has been authenticated and / or authorized by the USS is a create session management context request message.

15. The apparatus of claim 11, wherein the registration request message of the wireless device includes an aircraft identifier of the wireless device.

16. The apparatus of claim 11, wherein the PDU session is used to communicate with the USS.

17. The apparatus of claim 11, wherein the PDU session is used for command and control communication of the USS.

18. The apparatus of claim 11, wherein performing an authentication and / or authorization procedure comprises sending an authentication and / or authorization request by the AMF apparatus to the USS.

19. The apparatus of claim 18, wherein the authentication and / or authorization request includes an aviation service identifier of the wireless device.

20. The apparatus of claim 18, wherein the authentication and / or authorization request includes a General Public Subscription Identifier (GPSI) of the wireless device.

21. A system for session management of an aviation system, comprising: An access and mobility management function AMF device, the AMF device comprising one or more first processors and a first memory storing instructions, the instructions, when executed by the one or more first processors, causing the AMF device to: receiving, from a wireless device, a registration request message for the wireless device; triggering an authentication and / or authorization procedure for aviation services of said wireless device; receiving a protocol data unit (PDU) session establishment request from the wireless device to establish a PDU session associated with the aviation service; as well as Based on receiving the PDU session establishment request from the wireless device, sending a create session management context message to a session management function SMF device, wherein the create session management context message indicates whether the aviation service of the wireless device has been authenticated and / or authorized by an unmanned aerial system service provider USS; and The SMF device, wherein the SMF device comprises: one or more second processors and a second memory storing instructions, wherein the instructions, when executed by the one or more second processors, cause the SMF device to: receiving the create session management context message from the AMF device, the create session management context message including an indication of whether the aeronautical service of the wireless device has been authenticated and / or authorized by the USS; as well as Based on whether the wireless device's air service has been authenticated and / or authorized, a determination is made to accept or deny the wireless device's session management context request.

Images