Connection control

Abstract

A wireless device receives, from a base station, a first message indicating a predicted communication failure of the wireless device. The wireless device sends, to a server, a second message indicating the predicted communication failure of the wireless device. The wireless device receives, from the server, action information for the predicted communication failure.

Description

[0001] Cross-reference to related applications

[0002] This application claims the benefit of U.S. Provisional Application No. 63 / 062,707, filed August 7, 2020, which is incorporated herein by reference in its entirety. Attached Figure Description

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

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

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

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

[0007] Figure 4 A system diagram of an example wireless device according to an embodiment of the present disclosure.

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

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

[0010] Figure 7 A diagram for classifying and labeling traffic according to aspects of the embodiments of this disclosure.

[0011] Figure 8 This is an exemplary invocation process according to an embodiment of this disclosure.

[0012] Figure 9 This is an exemplary invocation process according to an embodiment of this disclosure.

[0013] Figure 10 This is an exemplary invocation process according to an embodiment of this disclosure.

[0014] Figure 11 This is an exemplary invocation process according to an embodiment of this disclosure.

[0015] Figure 12This is an exemplary invocation process according to an embodiment of this disclosure.

[0016] Figure 13 This is an exemplary invocation process according to an embodiment of this disclosure.

[0017] Figure 14 This is an exemplary radio resource control (RRC) state transition aspect according to an embodiment of this disclosure.

[0018] Figure 15 This illustrates a service-based architecture for a 5G network regarding the interaction between the control plane (CP) and the user plane (UP).

[0019] Figure 16 An exemplary architecture for unmanned and / or unmanned aerial systems (UAS) is shown.

[0020] Figure 17 An exemplary scenario is shown regarding how unmanned and / or unmanned aerial vehicles (UAVs) interact with a base station regarding interference.

[0021] Figure 18 An exemplary architecture of UAS is shown.

[0022] Figure 19 An exemplary scenario of a communication failure (e.g., communication interruption) according to an embodiment of this disclosure is shown.

[0023] Figure 20 An exemplary procedure for handling impending communication failures by a base station, a wireless device, and a control server, according to an embodiment of this disclosure, is shown.

[0024] Figure 21 An exemplary procedure for handling impending communication failures via a control plan path interface between a wireless device and a control server, according to an embodiment of this disclosure, is shown.

[0025] Figure 22 An exemplary procedure for handling impending communication failures by a base station and a control server with mobility management functions, according to an embodiment of this disclosure, is shown.

[0026] Figure 23 An exemplary procedure for handling (imminent) communication failures performed by a wireless device according to an embodiment of this disclosure is shown.

[0027] Figure 24 An exemplary scenario of handling an impending communication failure performed by a wireless device according to an embodiment of this disclosure is shown.

[0028] Figure 25An exemplary scenario of communication failure handling performed by a wireless device according to an embodiment of the present disclosure is shown.

[0029] Figure 26 An exemplary flowchart of an embodiment according to this disclosure is shown.

[0030] Figure 27 An exemplary flowchart of an embodiment according to this disclosure is shown. Detailed Implementation

[0031] Exemplary embodiments of the present invention enable enhanced features and functionalities to be implemented in 4G / 5G systems. Embodiments of the technology disclosed herein can be used in the fields of 4G / 5G systems and network slicing for communication systems. More specifically, embodiments of the technology disclosed herein can relate to 5G core networks and 5G systems for network slicing in communication systems. Throughout this disclosure, UEs, wireless devices, and mobile devices are used interchangeably.

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

[0033] 3GPP 3rd Generation Partnership Project

[0034] 5G (Fifth Generation Mobile Network)

[0035] 5GC 5G Core Network

[0036] 5GS 5G system

[0037] 5G-AN 5G Access Network

[0038] 5QI 5G QoS Indicator

[0039] ACK confirmation

[0040] AF application functions

[0041] AMF Access and Mobility Management Functions

[0042] AN access network

[0043] CDR Fee Data Records

[0044] CCNF Public Control Network Functions

[0045] CIoT Cellular IoT

[0046] CN Core Network

[0047] CP control plane

[0048] DDN Downlink Data Notification

[0049] DL downlink

[0050] DN Data Network

[0051] DNN Data Network Name

[0052] DRX discontinuous reception

[0053] F-TEID Fully Qualified TEID

[0054] gNB Next Generation Node B

[0055] GPSI General Public Subscription Identifier

[0056] GTP GPRS Tunneling Protocol

[0057] GUTI (Globally Unique Temporary Identifier)

[0058] HPLMN Local Public Land Mobile Network

[0059] IMSI International Mobile Subscriber Identity

[0060] LADN Local Area Data Network

[0061] LI legitimate interception

[0062] MEI (Mobile Equipment Identifier)

[0063] MICO only initiates connections via mobile.

[0064] MME (Mobility Management Entity)

[0065] MO Mobile Initiation

[0066] MSISDN Mobile Subscriber ISDN

[0067] MT movement terminated

[0068] N3IWF Non-3GPP Interoperability Function

[0069] NAI Network Access Identifier

[0070] NAS Non-Access Layer

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

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

[0073] NB-IoT Narrowband IoT

[0074] NEF Network Exposure Function

[0075] NF Network Functions

[0076] NGAP Next Generation Application Protocol

[0077] NR New Radio

[0078] NRF Network Repository Functionality

[0079] NSI Network Slicing Example

[0080] NSSAI Network Slice Selection Auxiliary Information

[0081] NSSF Network Slice Selection Function

[0082] OCS Online Payment System

[0083] OFCS Offline Billing System

[0084] PCF policy control function

[0085] PDU (Packet / Protocol Data Unit)

[0086] PEI Permanent Device Identifier

[0087] PLMN Public Land Mobile Network

[0088] PRACH (Physical Random Access Channel)

[0089] PLMN Public Land Mobile Network

[0090] PSA PDU Session Anchor

[0091] RAN (Radio Access Network)

[0092] QFI QoS Stream Identity

[0093] RM Registration Management

[0094] S1-AP S1 Application Protocol

[0095] SBA Service-Based Architecture

[0096] SEA Safety Anchor Function

[0097] SCM Security Context Management

[0098] SI System Information

[0099] SIB System Information Block

[0100] SMF Session Management Function

[0101] SMSF SMS Function

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

[0103] SSC Session and Service Continuity

[0104] SUCI Service User Relevance ID

[0105] SUPI subscriber permanent identifier

[0106] TEID (Tunnel Endpoint Identifier)

[0107] UAS Unmanned and / or Unmanned Aviation Systems

[0108] UAV (Unmanned and / or unmanned aerial vehicle)

[0109] UAVC UAV controller

[0110] UDM Unified Data Management

[0111] UER Unified Data Storage

[0112] UDR User Data Storage

[0113] UE User Equipment

[0114] UL uplink

[0115] UL CL Uplink Classifier

[0116] UPF User Plane Functions

[0117] USS UAS service provider

[0118] UTM UAS Traffic Management

[0119] UPF User Plane Functions

[0120] VPLMN access to public terrestrial mobile networks

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0140] In the example, 5GC can provide policy information from PCF 135 to UE 100. In the example, 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 offloading policy, etc.

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

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

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

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

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

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

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

[0148] As shown in the example Figure 6A and Figure 6BAs described, for the NAS signaling connection between UE 100 and AMF 155, two CM states can be used: CM-IDLE (600, 620) and CM-CONNECTED (610, 630). UE 100 in CM-IDLE 600 state can be in RM-REGISTERED 510 state and may not have a NAS signaling connection established with AMF 155 via N1. UE 100 in CM-IDLE 600 state can be in RRC idle state. UE 100 can perform cell selection, cell reselection, PLMN selection, etc. UE 100 in CM-CONNECTED 610 state can have a NAS signaling connection with AMF 155 via N1. In the example, UE 100 in CM-CONNECTED 610 state can be in RRC connected state. A UE 100 in the CM-CONNTECTED 610 state can be in an RRC inactive state. In the example, the CM state in the AMF and the CM state in the UE can differ. This is possible when a local state change occurs without explicit signaling procedures (e.g., UE context release procedures) between the UE and the AMF. Similarly, in the example, the RRC state in the UE (e.g., radio device) and the RRC state in the base station (e.g., gNB, eNB) can differ. This is possible when a local state change occurs without explicit signaling procedures (e.g., RRC release procedures) between the UE and the base station.

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

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

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

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

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

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

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

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

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

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

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

[0160] In the example, edge computing can provide computing and storage resources with sufficient connectivity near the device that generates traffic.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0185] In the example, the network operator can provide UE 100 with a Network Slice Selection Policy (NSSP). An NSSP may include one or more NSSP rules.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0203] In the example, based on SUPI, the new AMF 155 can be selected as a 905UDM 140. UDM 140 can be selected as a UDR instance. In the example, AMF 155 can be selected as a UDM 140.

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

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

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

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

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

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

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

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

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

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

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

[0215] In the example, UE 100 may send a message to (R)AN 105, the AN message including AN parameters, mobility management, MM NAS service request 1005 (e.g., a list of PDU sessions to be activated, a list of allowed PDU sessions, security parameters, PDU session status, etc.), etc. In the example, when UE 100 can reactivate a PDU session, 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 UE 100, and may identify the access that can be transmitted to or the PDU session that can be associated with said access. In the example, for the NG-RAN case, AN parameters may include the selected PLMN ID and establishment reason. The establishment reason may provide the reason for requesting to establish an RRC connection. UE 100 may send a NAS service request message to RAN 105 for AMF 155 encapsulated in an RRC message.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0281] Figure 15This diagram illustrates a service-based architecture for a 5G network involving the interaction of the control plane (CP) and user plane (UP). The illustration depicts the logical connections between nodes and functions, and these connections should not be interpreted as direct physical connections. Radio devices can form radio access network (RAN) connections with a base station connected to a user plane (UP) function (UPF) via a network interface that provides defined interfaces, such as the N3 interface. The UPF can provide logical connections to the data network (DN) via network interfaces such as the N6 interface. The RAN connection between the radio device and the base station can be referred to as the data radio bearer (DRB).

[0282] A DN can be a data network used to provide operator services, third-party services such as the Internet, IP Multimedia Subsystem (IMS), Augmented Reality (AR), and Virtual Reality (VR). In some implementations, a DN can represent an edge computing network or resource, such as a Mobile Edge Computing (MEC) network.

[0283] The wireless device also connects to the AMF via a logical N1 connection. The AMF can handle authentication and authorization 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 represented as Namf.

[0284] SMF (Service-Based Function) is a network function that is responsible for allocating and managing IP addresses assigned to wireless devices, as well as selecting UPFs (User-Defined Functions) for traffic associated with specific sessions of wireless devices. Multiple SMFs typically exist in a network, each associated with a corresponding group of wireless devices, base stations, or UPFs. From a service-based perspective, SMFs can communicate with other core network functions through a service-based interface, represented as Nsmf. SMFs can also connect to UPFs through logical interfaces such as network interface N4.

[0285] The Authentication Server Function (AUSF) can provide authentication services to other network functions via a service-based NAUSF interface. Network Exposure Functions (NEFs) can be deployed within a network to allow servers, functions, and other entities (such as those outside the trust domain (carrier network)) to expose 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 illustrated network 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 via a service-based NNEF network interface. The NEF can have interfaces to non-3GPP functions.

[0286] Network repository functions (NRFs) provide network service discovery capabilities. An NRF may be specific to its associated Public Land Mobile Network (PLMN) or network operator. Service discovery allows network functions and wireless devices connected to the network to determine where and how to access existing network functions.

[0287] The PCF can communicate with other network functions through a service-based NPCF interface and can be used to provide policies and rules to other network functions, including those within the control plane. The enforcement and application of these policies and rules may not be the responsibility of the PCF. The responsibility for the PCF to transmit policies to the function it serves can be the responsibility of the AMF or SMF. In one such example, the PCF could transmit policies associated with session management to the SMF. This can be used to allow for a unified policy framework that can be used to manage network behavior.

[0288] The UDM can provide a service-based Nudm interface to communicate with other network functions. The UDM can provide data storage facilities to other network functions. A unified data store allows for a consistent view of network information, ensuring that the most relevant information is available from a single resource to different network functions. This can make it easier to implement other network functions, as they may not need to determine where specific types of data are stored within the network. The UDM can connect to the UDR using an interface such as Nudr. The PCF can be associated with the UDM.

[0289] The PCF can have a direct interface to the UDR, or it can connect to the UDR using a Nudr interface. The UDM can receive requests to retrieve content stored in the UDR, or requests to store content in the UDR. The UDM can handle functions such as credential processing, location management, and subscription management. The UDR can also support authentication credential processing, user identification processing, access authorization, registration / mobility management, subscription management, and Short Message Service (SMS) management. The UDR can 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 permissions to the stored data. In some implementations, the UDR can store policy data as well as user subscription data, which may include any or all of subscription identifiers, security credentials, access and mobility-related subscription data, and session-related data.

[0290] Application Functions (AFs) can represent non-data plane (also known as non-user plane) functions of applications deployed within network operator domains and 3GPP-compliant networks. AFs reside within internal Application Servers (ASs). AFs can interact with other core network functions via service-based Naf interfaces and can access network capability exposure information, as well as provide application information for use in decisions such as traffic routing. AFs can also interact with functions such as the PCF to provide application-specific input to policy and policy enforcement decisions. In many cases, AFs may not provide network services to other network functions. AFs can often be considered consumers or users of services provided by other network functions. Applications (application servers) outside the trust domain (operator network) can perform many of the same functions as AFs by using NEFs.

[0291] Wireless devices can communicate with network functions in the Core Network Control Plane (CN-UP) and Core Network User Plane (CN-CP). UPF and Data Network (DN) are part of CN-UP. DN may be outside the Core Network Domain (Cellular Network Domain). (See diagram) Figure 15 In this configuration, the base station is located on the CP-UP side. The base station can provide connectivity for both the CN-CP and CN-UP. The AMF, SMF, AUSF, NEF, NRF, PCF, and UDM can be functions residing within the CN-CP and are often referred to as control plane functions. If the AF resides in the trusted domain, it can communicate directly with other functions within the CN-CP via the service-based Naf interface. If the AF resides outside the trusted domain, the AM can communicate indirectly with other functions within the CN-CP via the NEF.

[0292] Unmanned and / or unmanned aerial vehicles (UAVs) can be aircraft without a human pilot or crew on board (e.g., unmanned) and / or without any passengers. Unmanned and / or unmanned aviation systems (UAS) may be the systems required to operate a UAV. Figure 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) enables the ground control system (e.g., a UAV controller, a UTM, a USS) to communicate with the UAV, which may be a component of the UAS.

[0293] In the example, the wireless device could be a UAV (Universal Aircraft Vehicle). The wireless device could be an aerial wireless device. The wireless device could be flying above the ground. For example... Figure 17As shown, wireless devices may experience a high line-of-sight (LOS) propagation probability. Compared to a typical terrestrial wireless device, the wireless device can receive downlink (e.g., from the base station to the wireless device) interference from a greater number of cells. In the downlink direction, the number of adjacent cells is more likely to cause high-level downlink interference at the wireless device compared to the case of a terrestrial wireless device. In the example, the 16 cells causing high-level downlink direction interference can be observed by the wireless device at an altitude of 50m or higher. In the example, the base station (e.g., eNB, gNB) antenna can be tilted downwards to serve the terrestrial wireless device. The wireless device can be located above the height of the base station antenna. The wireless device can be served by the sidelobes of the base station antenna. The wireless device can see a stronger signal from a distant base station than from the geographically nearest base station. The wireless device can be served by a distant base station instead of the nearest base station. The downlink direction path loss and uplink direction path loss of an aerial wireless device may differ 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 partitioning (FDD) deployments).

[0294] Base stations of wireless networks and wireless devices can use Radio Access Network (RAN) functions for aeronautical communication services (e.g., UAS, UAV, unmanned and / or unmanned aerial vehicle services). Base stations and wireless devices can support Radio Access Network (RAN) functions for aeronautical communication services (e.g., UAS, UAV). RAN functions for aeronautical communication services can be aeronautical user equipment (UE) communication. In the example, the aeronautical communication service can be aeronautical user equipment (UE) communication. The aeronautical communication service can support UAS. RAN functions for aeronautical communication services may include altitude-based measurement reporting, interference detection for aeronautical UE communication, interference mitigation for aeronautical UE communication, flight path information reporting, location reporting for aeronautical UE communication, etc.

[0295] In the example, the base station can send RRC messages (e.g., RRC configuration messages, RRC reconfiguration messages) to the wireless device. The RRC message can include one or more measurement events related to altitude-based measurement reporting. These one or more measurement events can indicate an altitude threshold for the altitude-based measurement reporting to the wireless device. The wireless device can receive measurement events that include the altitude threshold. If the wireless device's altitude is above or below the altitude threshold, the wireless device can send an altitude report. The altitude report can include the wireless device's altitude, location, etc.

[0296] If the received signaling power (e.g., RSRP) of multiple neighboring cells exceeds a specific level for the wireless device, the wireless device may experience or introduce interference. For interference detection, the base station can configure Radio Resource Management (RRM) events that trigger a measurement report when the RSRP values ​​of each (per cell) of a configured number of cells (e.g., 8, 16) meet the configured event. The configured events can be used for interference detection. RRM events can be A3, A4, or A5. In response to determining that an RRM event has occurred, the wireless device can send a measurement report.

[0297] In the example, to mitigate interference, the base station can configure device-specific α parameters with Physical Uplink Shared Channel (PUSCH) power control. The base station can send Radio Resource Control (RRC) messages that include the α parameters for PUSCH power control. If the device receives dedicated α parameters from the base station (e.g., α-UE), the device can apply the dedicated α parameters instead of the common α parameters.

[0298] In the example, the base station can request a wireless device to report flight path information by sending a User Equipment Information Request (UEIS) message. The flight path information may include the number of waypoints defined as 3D locations. The UEIS message may indicate the maximum number of waypoints and / or whether timestamps are required for the waypoints. The wireless device can receive the UEIS message. If the wireless device is available to report the flight path, it can send a UEIS Response message to the base station. The UEIS Response message may include one or more waypoints and one or more timestamps associated with those waypoints. The base station can use the flight path information for congestion prediction or resource management to mitigate interference.

[0299] In the example, for location reporting in aviation UE communications, the base station may request the wireless device to provide its horizontal and vertical velocities for location information reporting. The wireless device may then send a location information report to the base station. The location information report may include horizontal velocity, vertical velocity, etc. The location information may also include the wireless device's altitude.

[0300] Remote Identification (RID) may be a technology to avoid collisions between different UAVs or between manned aircraft and UAVs. To prevent collisions, the Federal Aviation Administration (FAA) can integrate UAVs into the National Airspace System (NAS) by introducing RID. RID can provide an in-flight UAV with identification and tracking information that can be received by other parties, and can function in identifying unauthorized UAVs in restricted areas and grounding them. In this example, UAVs weighing 0.55 pounds or more may be required to support RID. There are likely two types of RID: standard RID and restricted RID. For standard RID, UAVs may support both network-published identification (ID) and direct broadcast ID. For restricted RID, UAVs may support network-published ID. For restricted RID, UAVs may not support direct broadcast ID. Network-published ID can be based on communication via the Internet from an RID server provider that interfaces with the UAV. Direct broadcast ID can be based on direct transmission of the RID by the UAV using its onboard direct transmission technology (e.g., Bluetooth, Wi-Fi module). UAVs supporting restricted RIID (e.g., those that do not support direct broadcast IDs) may not be permitted to fly above 400 feet. During flight, UAVs supporting restricted RIID and network connectivity may be required. UAS supporting standard RIID are permitted to fly above 400 feet and have no restrictions on network connectivity.

[0301] In the example, command and control communication can be a user plane link to deliver messages containing commands and control information for UAV operation from the UAV controller or UTM to the UAV. Command and control communication can be C2 communication. C2 communication includes three types of communication: 1) direct C2 communication, 2) network-assisted C2 communication, and 3) UTM-guided C2 communication. Direct C2 communication can use a direct communication link between the UAV and the UAV controller. Network-assisted C2 communication can use a cellular network (e.g., a public terrestrial mobile network) for communication between the UAV and the UAV controller. For UTM-guided C2 communication, the UTM can provide the UAV with a pre-arranged flight plan, while the UTM can track and verify the UAV's latest restrictions or flight plans.

[0302] Figure 18Exemplary interfaces (e.g., U2U, UAV3, UAV6, UAV8, UAV9) for unmanned aerial systems with wireless networks (e.g., PLMN1, PLMN2) are shown. Interfaces can be communication connections. In the example, the U2U interface can be an interface for direct broadcast ID. The UAV8 interface can be an interface for direct C2 communication between the UAV and the UAV controller. The UAV3 interface can be an interface between the UAV and the UAV controller via a wireless network. In the example, UAV3 can be within a PLMN or between PLMNs. In the example, for within a PLMN, PLMN1 and PLMN2 can be the same PLMN. For between PLMNs, PLMN1 and PLMN2 can be different PLMNs. In the example, UAV9 can be an interface between the UAV and the networked UAV controller, and between the USS / UTM for UAS management (e.g., authentication and authorization, C2 transmission, RID, and UAV tracking). In the example, UAV6 can be an interface between a PLMN (e.g., a 3GPP network) and the USS / UTM for function exposure, support identification and tracking, and UAV authentication / authorization.

[0303] like Figure 19 As shown, a wireless device can move along a path (e.g., a flight path) indicated by a dotted line. In the example, the base station of "Cell A" may be inactive due to a power outage or malfunction. When the wireless device moves across the area of ​​"Cell A," it may experience a communication failure. This failure can be short-term (e.g., 1 minute, 5 minutes) or a complete communication interruption. In the example, there is no available base station near the coverage area of ​​"Cell B." After the wireless device leaves the coverage area of ​​"Cell B" and moves to the right, it may experience a communication failure. This failure can be long-term (e.g., 30 minutes, 1 hour).

[0304] In existing technologies, wireless devices may move out of the coverage area of ​​wireless communication. Wireless devices can detect communication interruptions. If a wireless device moves out of the coverage area, it can indicate to the user that it is outside the coverage area. The user can then decide whether to remain outside the coverage area or move into the coverage area. For certain types of wireless devices (e.g., unmanned aerial systems or aircraft (UAS or UAV)), wireless communication is mandatory for a period of time. This period can be the flight time of the wireless device. In the example, the control server of the wireless device may require a wireless communication connection during or during a portion of the flight time. The control server may require connectivity so that it can control the wireless device during flight (e.g., for safety reasons, such as crash warnings, flight path changes, flight cancellations, or emergency landings).

[0305] According to an exemplary embodiment of this disclosure, a base station can estimate, predict, and / or determine that a communication failure of a wireless device is about to occur, and can take one or more actions in advance. In an example, the base station can determine that there is no available base station in the direction the wireless device is moving, and / or that no base station is available to hand over the wireless device. The base station can determine the communication failure before the wireless device moves out of its coverage area. The pre-determined communication failure can be referred to as an impending communication failure. The base station can indicate the impending communication failure to the wireless device. The wireless device can receive the impending communication failure indication. In response to receiving the impending communication failure indication, the wireless device can send a first message indicating the impending communication failure to a control server. The control server can send a second message including appropriate actions in response to the communication failure. Appropriate actions may include a changed flight path, landing location, or applicability of moving outside the coverage area. The first message may also indicate the duration of the communication failure, the current location of the wireless device, and / or any other information suitable for preventing or managing the communication failure.

[0306] According to an exemplary embodiment of this disclosure, a base station can indicate an impending communication failure to a network function. The network function may be an Access and Mobility Management Function (AMF). The network can indicate the impending communication failure of the wireless device to a control server. In the example, the network may also indicate the duration of the communication failure, the current location of the wireless device, and / or any other information suitable for preventing or managing the communication failure. The control server can send a message to the wireless device including appropriate actions.

[0307] According to an exemplary embodiment of this disclosure, the wireless device can determine that it is outside the coverage area. If the wireless device determines that it is outside the coverage area, it can move back to the area where it can successfully communicate with the cellular network.

[0308] According to an exemplary embodiment of this disclosure, a wireless device can determine an impending communication failure. The wireless device can determine the impending communication failure based on a threshold. The threshold can be RSRP or RSRQ. The wireless device can receive the threshold from a base station. The wireless device can also receive the threshold from a control server. If the wireless device determines, for example, that a measured RSRP or RSRQ is higher or lower than the threshold, the wireless device can indicate this to the control server. The control server can then send a message to the wireless device, including an appropriate action, based on this indication.

[0309] Figure 20An exemplary procedure for handling impending communication failures by a base station and a wireless device (e.g., UAV) and a control server (e.g., UTM / USS) according to embodiments of this disclosure is illustrated. In the example, the wireless device may receive a first message from the base station indicating an impending communication failure of the wireless device. The wireless device may send a second message to the control server indicating an impending communication failure of the wireless device. Sending may be in response to receiving. The wireless device may receive a third message from the control server, which includes action information of the impending communication failure. In the example, the impending communication failure may be a communication failure detected in advance before the actual occurrence of the communication failure. In the example, the first message may be a Radio Resource Control (RRC) message. The impending communication failure may be that the wireless device or the base station is aware in advance of moving out of the coverage area. When the wireless device or the base station detects the impending communication failure, the wireless device can still communicate via the base station. In the example, the wireless device may send a second message with an established PDU session to the control server via the UPF via the user plane path. The control server may send the third message via the UPF via the user plane path. An exemplary implementation can minimize potential accidents (e.g., plane crashes, injuries) by controlling wireless devices before communication failures occur via UTM.

[0310] In the example, the first message may also include a first time period of the impending communication failure, a first cause value for the impending communication failure, one or more first modified flight paths, etc. The first time period can be the amount of time until the communication failure. The first time period can be the duration of the communication failure. The first cause value can indicate the cause / reason for the impending communication failure. The first cause value can indicate an interruption of a network node. The first cause value can indicate that the wireless device has moved out of the coverage area. One or more first modified flight paths can be alternative flight paths based on the first flight path of the wireless device. In the example, one or more first modified flight paths can exclude the interrupted area. One or more first modified flight paths can exclude the coverage area. One or more first modified flight paths can include one or more waypoints and one or more timestamps associated with the waypoints.

[0311] In the example, the second message may include at least one of the following: the unmanned and / or unmanned aerial vehicle (UAV) identifier of the wireless device, a second time period of the impending communication failure, a second cause value of the impending communication failure, and one or more second modified flight paths of the wireless device. The second time period may be based on the first time period. The second cause value may be based on the first cause value. The one or more second modified flight paths may be based on one or more first modified flight paths.

[0312] In the example, action information may indicate one or more actions that the wireless device can perform. One or more actions may be based on an impending communication failure. Action information may include one or more second flight paths, landing locations, indications of permission for autonomous flight, etc. One or more second flight paths may be modified flight paths to avoid areas of communication failure. One or more second flight paths may be based on one or more second modified flight paths. In response to receiving one or more second flight paths, the wireless device moves / flies based on one or more second flight paths. The landing location may indicate the landing location that the wireless device may land in response to receiving action information. The landing location may include geographic coordinates of the landing, landing time, etc. Geographic coordinates may be represented as ellipsoidal points, such as points on the surface of an ellipsoid. Ellipsoidal points may include latitude, longitude, altitude, etc. The landing time may be 0 seconds, 1 minute, or the time value itself. If the landing time indicates 1 minute, the wireless device may land 1 minute after receiving the action information. In the example, this indication may indicate permission for autonomous flight for the wireless device. The wireless device may fly based on one or more first flight paths (e.g., the original flight path). The wireless device may fly outside the coverage area. The wireless device may fly when communication with the base station is unavailable.

[0313] In the example, the wireless device may support a Limited Remote Identifier (RID). The wireless device may not broadcast the RID. The wireless device may not fly in areas where communication is unavailable.

[0314] In the example, the wireless device may send a fourth message to the control server requesting authentication and authorization for one or more flights. The control server may be a UTM or a USS. In response to sending the fourth message, the wireless device may receive a fifth message from the control server indicating the result of the authentication and authorization request for one or more flights. The fourth message may include at least one of the following: the wireless device's UAV identifier, the requested flight type, the requested flight path, the requested flight time, and the RID of supported wireless devices. The wireless device may receive the UAV identifier from the control server. In the example, the requested flight type may include direct C2 communication, network-assisted C2 communication, UTM navigation C2 communication, etc. Supported remote RIDs may include standard RIDs, restricted RIDs, etc. The fifth message may include the authentication and authorization result, the authorized flight type, the authorized flight path, the authorized flight time, etc. In the example, the result may indicate yes or no; in the example, the result may indicate success or failure. The authorized flight type may indicate at least one of direct C2 communication, network-assisted C2 communication, UTM navigation C2 communication, etc. The authorized flight path can be the first flight path of the wireless device. The authorized flight time can indicate the time period of the authorized flight (e.g., from... to...).

[0315] In the example, the base station can receive the first flight path of the wireless device from the network device. The base station can determine an impending communication failure based on the wireless device's flight path, neighboring cell deployment information, interruption information of neighboring base stations (cells), operational and management information, congestion information, local policies, measurement information, etc. In response to this determination, the base station can send a first message to the wireless device indicating the impending communication failure.

[0316] In the example, network nodes can be wireless devices. Network nodes can be mobility management functions (e.g., AMF, MME). The first flight path can include one or more waypoints, one or more timestamps associated with the waypoints, etc. The base station can learn about neighboring cell deployment information, neighboring base station outage information, and congestion information using operator-provided O&M (operation and maintenance) methods. In the example, the base station can receive neighboring cell deployment information, neighboring base station outage information, and congestion information from one or more network nodes. One or more network nodes can be Network Data Analysis Functions (NWDAF). One or more network nodes can be mobility management functions. The base station can receive neighboring cell deployment information or neighboring cell outage information from other base stations via the Xn or X2 interface. Neighboring cell information can include a list of available neighboring cells or neighboring cell outage information. Neighboring cell information can also include coverage area information associated with available neighboring cells. The wireless device can transmit measurement information. The base station can measure the measurement information. The measurement information can indicate the actual coverage information of one or more cells of the base station and one or more cells of neighboring base stations.

[0317] Figure 21 An exemplary procedure for handling impending communication failures via a control plan path interface between a wireless device and a control server is illustrated. In the example, the wireless device can receive a first message from a base station indicating an impending communication failure, such as... Figure 20 As shown. The wireless device can send a second message to the control server indicating an impending communication failure of the wireless device. Sending can be in response to receiving. The wireless device can receive a third message from the control server, which includes action information regarding the impending communication failure. In the example, the wireless device can send the second message to a mobility management function (e.g., AMF, MME) via a control plane path using the NAS protocol. The mobility management function can forward the second message to the control server via a Network Exposure Function (NEF) or a UAS Application Function (AF). The wireless device can receive the third message via the control plane path. Implementation of the exemplary embodiment can minimize potential incidents (e.g., crashes, injuries) by controlling the wireless device before a communication failure occurs via UTM.

[0318] Figure 22 An exemplary procedure for handling impending communication failures, performed by a base station with mobility management functions (e.g., AMF, MME) and a control server (e.g., UTM / USS), according to embodiments of this disclosure, is illustrated. In the example, the base station may receive one or more first flight paths (e.g., flight path information) of a wireless device from a network node. The network node may be a wireless device. The network node may be a mobility management function. The base station may determine an impending communication failure based on one or more first flight paths of the wireless device. This determination may also be based on neighboring cell deployment information, outage information of neighboring base stations (cells), operation and management information, congestion information, local policies, measurement information, etc. In response to determining an impending communication failure, the base station may send a first message indicating the impending communication failure to the mobility management function. In the example, the first message may include a first time period of the impending communication failure, a first cause value of the impending communication failure, one or more first modified flight paths, etc. In response to receiving the first message, the mobility management function may send a second message indicating the impending communication failure to the control server. The second message may include the unmanned and / or unmanned aerial vehicle (UAV) identifier of the wireless device, the GPSI of the wireless device, a second time period of the impending communication failure, a second cause of the impending communication failure, and one or more second modified flight paths of the wireless device. The second time period may be based on the first time period. The second cause value may be based on the first cause value. One or more second modified flight paths may be based on one or more first modified flight paths. In response to receiving the second message from the mobility management function, the control server may send a third message, which includes action information of the impending communication failure. In the example, the control server may send the third message via a user plane path, such as... Figure 20 The control server can use the NAS protocol to send third-party messages via the control plane path, such as... Figure 21 The exemplary implementation can minimize potential accidents (e.g., plane crashes, casualties) by controlling the wireless device before communication failures occur via UTM. Specific implementations of the exemplary implementation can minimize any interaction with the wireless device.

[0319] In an exemplary implementation, the mobility management function can determine an impending communication failure in the wireless device. In this case, the mobility management function can initiate an impending communication failure handling procedure by sending a second message to the control server.

[0320] Figure 23An exemplary procedure for handling (impending) communication failures by a wireless device according to embodiments of this disclosure is illustrated. In the example, the wireless device may determine an impending communication failure based on measurement results. In the example, the wireless device may determine an impending communication failure based on one or more signals received from one or more base stations. In the example, the wireless device may determine that there is no suitable communication strength / signal in the direction in which the wireless device is moving. In the example, the wireless device may determine that there is no serving base station in the direction in which the wireless device is moving. Before the wireless device experiences a communication failure, the wireless device may stop moving and remain in its current area (e.g., ...). Figure 23 (A) Remaining within the coverage area). The wireless device can send a message indicating an impending communication failure to the control server. The wireless device can receive action information about the impending communication failure from the control server. In an exemplary implementation, the action information can be pre-configured in the wireless device. The action information can indicate one or more secondary flight paths (e.g., alternative flight paths), landing location, indication of autonomous flight permission, etc. For impending communication failure detection, the wireless device can use a threshold. The wireless device can determine the impending communication failure based on measurement results, the threshold, one or more flight paths, etc. The wireless device can receive the threshold from the serving base station, such as... Figure 24 The wireless device can receive thresholds from the control server. The wireless device can also receive thresholds from mobility management functions. The thresholds can be pre-configured in the wireless device. The wireless device can receive one or more first flight paths from the control server during the flight authorization procedure.

[0321] In the example, the wireless device can determine communication faults based on measurement results, such as... Figure 25 As described above, in this example, the wireless device can determine that it is located at "Location B," outside the coverage area. If the wireless device determines a communication failure (e.g., outside the coverage area), it can move to its last communication location, "Location A." The wireless device can successfully transmit a final measurement report at the last communication location. The wireless device can receive / measure signaling power greater than a threshold at the last communication location. The wireless device can perform one or more actions based on pre-configured action information. In an exemplary implementation, the wireless device can send a message indicating a communication failure to a control server. This message may include a failure cause value, a communication failure area, the last communication location, etc. As described above, the wireless device can receive action information from the control server.

[0322] Figure 26 , Figure 27 This is an exemplary flowchart as part of an exemplary implementation. Figure 26In this example, the wireless device can send a message indicating an impending communication failure. The wireless device can receive a second message from the UTM, which includes action information regarding the impending communication failure. In this example, the wireless device can determine the impending communication failure. In this example, the wireless device can receive a third message indicating the impending communication failure from the network device. The network device can be a base station. The network device can be a mobility management function. In this example, the transmission can be based on the third message.

[0323] exist Figure 27 In this example, the base station can determine an impending communication failure of a wireless device. In this example, the base station can identify the wireless device as a UAV (User Available). In this example, the base station can activate RAN functions associated with the UAV (e.g., the wireless device's UAS). This determination can be based on the wireless device's flight path, neighboring cell deployment information, neighboring cell outage information, measurement reports from the wireless device, etc. The base station can send a message indicating the impending communication failure to a network node. The network node can be the wireless device. The network node can be a mobility management function serving the wireless device.

[0324] In the example, the wireless device can receive a first message from the base station indicating an impending communication failure. The wireless device can then send a second message to the Unmanned Traffic Management (UTM) server indicating the impending communication failure. The wireless device can receive a third message from the UTM server, which includes action information related to the impending communication failure. According to an exemplary embodiment, the first message may include the time period of the impending communication failure, the cause of the impending failure, a modification of the flight path, etc. The time period can be the amount of time until the communication failure. The time period can also be the duration of the communication failure.

[0325] According to an exemplary implementation, the second message may include the UAV identifier of the wireless device, the time period of the impending communication failure, the cause of the impending communication failure, one or more modified flight paths of the wireless device, etc.

[0326] According to an exemplary implementation, the action information may include modifications to the flight path, landing location, and instructions indicating permission for autonomous flight. The wireless device may be a UAV. The wireless device may support a Limited Remote Identifier (RID).

[0327] According to an exemplary implementation, the wireless device can send a fourth message to a UTM server requesting authentication and authorization for one or more flights. The wireless device can receive a fifth message from the UTM server indicating the result of the authentication and authorization request for one or more flights. The fourth message may include the wireless device's UAV identifier, the requested flight mode, the requested flight path, the requested flight time, the remote identifier of supported wireless devices, etc. The fifth message may include the authentication and authorization request, the authorized flight mode, the authorized flight path, etc.

[0328] In the example, the base station can receive flight path information of the wireless device from the network device. Based on the flight path information, the base station can determine an impending communication failure of the wireless device. The base station can then send a message to the wireless device indicating the impending communication failure.

[0329] According to an exemplary embodiment, the network device may be a wireless device. The network device may be an Access and Mobility Management Function (AMF).

[0330] According to an exemplary implementation, flight path information includes one or more waypoints, one or more timestamps associated with the waypoints, etc.

[0331] According to an exemplary implementation, this determination can be further based on neighboring base station deployment information, neighboring cell deployment information, neighboring base station outage information, operation and management information, wireless device congestion information, etc.

[0332] According to an exemplary implementation, the message may include a change in flight path, a time period of impending communication failure, etc.

[0333] In the example, the base station can receive flight path information of the wireless device from the network device. Using this flight path information, the base station can determine an impending communication failure of the wireless device. The base station can then send a message indicating the impending communication failure to the Access and Mobility Management Function (AMF).

[0334] In the example, the Access and Mobility Management Function (AMF) can receive a first message from the base station indicating an impending communication failure of the wireless device. The AMF can then send a second message indicating the impending communication failure to the UAS Traffic Management (UTM) or UAS Service Provider (USS) server. The AMF can receive a third message from the UTM / USS server, which includes action information regarding the impending communication failure of the wireless device. The AMF can also send this third message to the wireless device.

[0335] In the example, the wireless device can determine that it has experienced a communication failure. Based on this failure, the wireless device can move to its last communication location. The wireless device can send a first message indicating the communication failure to the UTM / USS server. The wireless device can receive a second message from the UTM / USS, including motion information. The wireless device can then send a final measurement report from its last communication location. The received signaling power at the last communication location can exceed a threshold. This determination can be based on flight path information.

[0336] In the example, the wireless device can determine an impending communication failure. The wireless device can send a first message indicating the impending communication failure to the UTM / USS server. The wireless device can receive a second message from the UTM / USS, which includes action information related to the impending communication failure. This determination can be based on a threshold for the impending communication failure. The determination can be based on received signal power and / or received signal quality. The determination can be based on flight path information. The wireless device can receive the threshold from the base station. The wireless device can receive the threshold from access and mobility management functions. The threshold can be pre-configured in the wireless device. The wireless device can receive the threshold from the UTM / USS server.

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

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

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

[0340] Exemplary embodiments of the present invention can be implemented using various physical and / or virtual network elements, software-defined networks, and virtual network functions.

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

[0342] Although various embodiments have been described above, it should be understood that they are presented by way of example rather than limitation. It will be apparent to those skilled in the art that various changes in form and detail may be made without departing from the spirit and scope of this disclosure. Indeed, after reading the above description, it will be apparent to those skilled in the art how to implement alternative embodiments. Therefore, the current embodiments should not be limited to any of the exemplary embodiments described above. In particular, it should be noted that, for illustrative purposes, the above explanation has focused on examples using 5G AN. However, those skilled in the art will recognize that embodiments of the invention can also be implemented in systems including one or more legacy systems or LTE. The disclosed methods and systems can be implemented in wireless or wired systems. Features of the various embodiments proposed in this invention can be combined. One or more features (methods or systems) of one embodiment can 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 features in various embodiments to create enhanced transmission and reception systems and methods. Furthermore, it should be understood that any figures highlighting features and advantages are presented for illustrative purposes only. The disclosed architecture is flexible and configurable enough that it can be utilized in ways other than those shown. For example, any actions listed in a flowchart may be reordered or optionally used in certain embodiments. Furthermore, the purpose of this abstract is to enable the U.S. Patent and Trademark Office and the general public, especially scientists, engineers, and practitioners unfamiliar with patent or legal terminology or usage, to quickly determine the nature and substance of the technical disclosure of this application through a cursory examination. This abstract is not intended to limit the scope in any way. Finally, the applicant intends that only claims including the phrases “means for…” or “steps for…” should be interpreted according to 35 U.SC 112. Claims that do not explicitly include the phrases “means for…” or “steps for…” should not be interpreted according to 35 U.SC 112.

Claims

1. A communication method, comprising: A first message is received by the wireless device from the base station, the first message indicating a predicted communication failure of the wireless device and the amount of time until the predicted communication failure, wherein: The predicted communication failure is determined by the base station based on flight path information and when there is no available base station for handover, before the wireless device moves out of the base station's coverage area; and The predicted communication failure indicates that the predicted communication between the wireless device and the base station is interrupted; The wireless device sends a second message to the server indicating the predicted communication failure of the wireless device; and The wireless device receives the action information for predicting communication failures from the server.

2. The method of claim 1, wherein the first message is a Radio Resource Control (RRC) message from the base station.

3. The method of claim 1, wherein the action information includes modifying the flight path and landing location.

4. The method of claim 1, wherein the action information includes an instruction authorizing autonomous driving.

5. The method of claim 1, wherein the second message includes the unmanned aerial vehicle identifier and / or the unmanned aerial vehicle identifier of the wireless device.

6. The method of claim 1, wherein the first message includes the duration of the predicted communication failure.

7. The method of claim 1, wherein the first message includes the predicted cause of the communication failure.

8. The method of claim 1, wherein the first message includes one or more modifications to the flight path.

9. The method of claim 1, further comprising the movement of the wireless device following a flight path through the coverage area of ​​the base station.

10. The method of claim 9, wherein the predicted communication failure is based on the flight path of the wireless device through the coverage area of ​​the base station.

11. The method of claim 10, further comprising the movement of the wireless device following a flight path through a second coverage area of ​​the second base station.

12. The method of claim 11, wherein the predicted communication failure is based on the flight path of the wireless device through the second coverage area of ​​the second base station.

13. The method of claim 1, wherein the wireless device is one or more of the following: Unmanned aerial vehicles; and Unmanned aerial vehicles.

14. The method of claim 1, wherein the server is one or more of the following: Traffic management using unmanned aerial systems; Traffic management for unmanned aerial systems; Unmanned aerial systems service providers; and Unmanned aerial system service provider.

15. A wireless device comprising one or more processors and a memory storing instructions, the instructions, when executed by the one or more processors, causing the wireless device to perform the method as claimed in any one of claims 1 to 14.

16. A non-transitory computer-readable medium comprising instructions that, when executed by one or more processors of a wireless device, cause the wireless device to perform the method as described in any one of claims 1 to 14.

Images