Session management node, method for session management node, user device, method for user device

Abstract

This document provides session management nodes and methods to clarify the behavior of network and wireless terminals when a service provider (USS) for an uncrewed aerial vehicle (UAV) is not found in the Uncrewed Aerial Vehicle (UAV) Authentication and Authorization (UUAA) Session Management (SM) procedure. [Solution] In an unmanned aerial system, the Session Management Function (SMF) receives a session establishment request message containing the USS address from a wireless terminal, sends a Network Exposure Function (NEF) authentication service call message containing the USS address to the UAS-NF, receives a response message from the UAS-NF9, and if the response message contains the cause of failure related to the USS corresponding to the USS address, sends a rejection response message to the session establishment request message containing information indicating a failure of the service related to the USS to the wireless terminal.

Description

Technical Field

[0001] This disclosure relates to cellular networks, and particularly to the authentication and authorization of drone systems.

Background Art

[0002] The 5G system (5GS) connects a wireless terminal (user equipment (UE) or Uncrewed Aerial Vehicle (UAV)) to a data network (Data Network (DN)) (hereinafter, it is possible to interchange UE and UAV). The connectivity service between the UE and the DN is supported by one or more Protocol Data Unit (PDU) sessions (see, for example, Non-Patent Documents 1 to 3). A PDU session is an association, session, or connection between the UE and the DN. A PDU session is used to provide a PDU connectivity service (i.e., the exchange of PDUs between the UE and the DN). A PDU session is established between the UE and a User Plane Function (UPF) (i.e., PDU session anchor) to which the UE and the DN are connected. From the perspective of data transfer, a PDU session is composed of a tunnel (N9 tunnel) in the 5G core network (5G core network (5GC)), a tunnel (N3 tunnel) between the 5GC and the access network (Access Network (AN)), and one or more radio bearers.

[0003] Non-Patent Documents 2 and 3 specify procedures for PDU session establishment, modification, and release. More specifically, the PDU session establishment procedure is described, for example, in Chapter 4.3.2 of Non-Patent Document 2 and Chapter 6.4.1 of Non-Patent Document 3. The PDU session modification procedure is described, for example, in Chapter 4.3.3 of Non-Patent Document 2 and Chapter 6.4.2 of Non-Patent Document 3. The PDU session release procedure is described, for example, in Chapter 4.3.4 of Non-Patent Document 2 and Chapter 6.4.3 of Non-Patent Document 3.

[0004] 5GS further supports network slicing (see, for example, Non-Patent Documents 1-3, particularly Section 5.15 of Non-Patent Document 1). Network slicing uses Network Function Virtualization (NFV) and software-defined networking (SDN) technologies to enable the creation of multiple virtualized logical networks on top of a physical network. Each virtualized logical network is called a network slice. A network slice provides specific network capabilities and network characteristics. A network slice instance (NSI) is defined as a set of Network Function (NF) instances, resources (e.g., computer processing resources, storage, and networking resources), and an access network (AN) (at least one of Next Generation Radio Access Network (NG-RAN) and Non-3GPP InterWorking Function (N3IWF)) to form a single network slice.

[0005] Network slices are identified by an identifier known as Single Network Slice Selection Assistance Information (S-NSSAI). S-NSSAI consists of a Slice / Service type (SST) and a Slice Differentiator (SD). SST refers to the expected network slice behavior with respect to its features and services. SD is optional information that complements SST to distinguish multiple network slices of the same Slice / Service type.

[0006] An S-NSSAI can have standard values ​​or non-standard values. Currently, standard SST values ​​1, 2, 3, and 4 are associated with enhanced Mobile Broadband (eMBB), Ultra Reliable and Low Latency Communication (URLLC), Massive Internet of Things (MIoT), and Vehicle to Everything (V2X) slice types. The non-standard values ​​of an S-NSSAI identify a single network slice within a particular Public Land Mobile Network (PLMN). That is, non-standard SST values ​​are PLMN-specific values ​​and are associated with the PLMN ID of the PLMN to which they are assigned. Each S-NSSAI assists a network in selecting a particular NSI. The same NSI may be selected through different S-NSSAIs. The same S-NSSAI may be associated with different NSIs. Each network slice may be uniquely identified by an S-NSSAI.

[0007] There are two types of S-NSSAI, known as S-NSSAI and Mapped S-NSSAI. S-NSSAI identifies the network slice provided by the Public Land Mobile Network (PLMN) to which the UE is registered. Mapped S-NSSAI may be an S-NSSAI of a Home PLMN (HPLMN) that is mapped (associated with, or applicable to) an S-NSSAI that identifies the network slice of the roaming network when the UE is roaming, and may also be an S-NSSAI included in the subscriber information of the UE user within that PLMN. Hereafter, in this specification, S-NSSAI and Mapped S-NSSAI may be collectively referred to simply as S-NSSAI.

[0008] On the other hand, Network Slice Selection Assistance Information (NSSAI) refers to a set of S-NSSAIs. Therefore, one or more S-NSSAIs can be contained within a single NSSAI. There are several types of NSSAIs, known as Configured NSSAI, Requested NSSAI, Allowed NSSAI, Rejected NSSAI, and Pending NSSAI.

[0009] A Configured NSSAI includes one or more S-NSSAIs, each applicable to one or more PLMNs. A Configured NSSAI can include S-NSSAIs and Mapped S-NSSAIs. A Configured NSSAI is configured, for example, by a Serving PLMN and applied to that Serving PLMN. Alternatively, a Configured NSSAI may be a Default Configured NSSAI. A Default Configured NSSAI is configured by a Home PLMN (HPLMN) and applied to any PLMNs for which a specific Configured NSSAI is not provided. A Default Configured NSSAI is provisioned, for example, from the HPLMN's Unified Data Management (UDM) to the User Equipment (UE) via the Access and Mobility Management Function (AMF).

[0010] A Requested NSSAI is signaled to the network by a UE, for example, during a registration procedure, enabling the network to determine the Serving AMF, one or more network slices, and one or more NSIs for that UE. A Requested NSSAI can include S-NSSAI and Mapped S-NSSAI.

[0011] An Allowed NSSAI is provided to the UE by the Serving PLMN and indicates one or more S-NSSAIs that the UE can use in the Serving PLMN's current Registration Area. An Allowed NSSAI can include S-NSSAIs and Mapped S-NSSAIs. An Allowed NSSAI is determined by the Serving PLMN's AMF, for example, during the registration procedure. Thus, an Allowed NSSAI is signaled to the UE by the network (i.e., AMF) and stored in the AMF's and the UE's respective (non-volatile) memory.

[0012] A Rejected NSSAI includes one or more S-NSSAIs rejected by the current (or serving) PLMN. When a UE is roaming, the Rejected NSSAI includes S-NSSAIs from the Home PLMN (HPLMN). Rejected NSSAIs are sometimes also called rejected S-NSSAIs. S-NSSAIs are rejected either across the current PLMN or within the current registration area. If the AMF rejects any of the S-NSSAIs included in the Requested NSSAI during the UE's registration procedure, for example, it includes them in the Rejected NSSAI. The Rejected NSSAI is signaled to the UE by the network (i.e., AMF) and stored in the (non-volatile) memory of both the AMF and the UE.

[0013] An Extended Rejected NSSAI includes one or more S-NSSAIs rejected by the current (or serving) PLMN. An Extended Rejected NSSAI may include S-NSSAIs and Mapped S-NSSAIs.

[0014] A Pending NSSAI indicates one or more S-NSSAIs for which Network Slice-Specific Authentication and Authorization (NSSAA) is pending. A Pending NSSAI can include both S-NSSAIs and Mapped S-NSSAIs. A Serving PLMN must perform NSSAA on S-NSSAIs of HPLMNs that are subject to NSSAA based on subscription information. To perform NSSAA, the AMF invokes an Extensible Authentication Protocol (EAP)-based authorization procedure. The EAP-based authentication procedure takes a relatively long time to produce an outcome. Therefore, in the UE registration procedure, the AMF determines the Allowed NSSAI as described above, but does not include S-NSSAIs subject to NSSAA in the Allowed NSSAI; instead, it includes them in the Pending NSSAI. Pending NSSAI is signaled to the UE via the network (i.e., AMF) and stored in the (non-volatile) memory of both the AMF and the UE.

[0015] The AMF manages the UE context of a UE in the Registration Management (RM)-REGISTERED state. The UE context may also be called the Mobility Management (MM) context, although it is not limited to this. The UE context may include one or more of the above-mentioned Allowed NSSAI, Rejected NSSAI, Extended Rejected NSSAI, and Pending NSSAI. On the other hand, the UE manages the UE NSSAI configuration. The UE NSSAI configuration includes the above-mentioned Configured NSSAI, Allowed NSSAI, Rejected NSSAI, Extended Rejected NSSAI, and Pending NSSAI. The UE NSSAI configuration is stored in non-volatile memory within the UE (Mobile Equipment (ME) excluding the Universal Subscriber Identity Module (USIM)). The memory or memory region where the UE NSSAI configuration is stored is called NSSAI storage.

[0016] Sections 5.15.10 of Non-Patent Document 1 and 4.2.9 of Non-Patent Document 2 define Network Slice-Specific Authentication and Authorization (NSSAA). More specifically, Sections 5.15.10 of Non-Patent Document 1 and 4.2.9.2 of Non-Patent Document 2 describe NSSAA. Sections 5.15.10 of Non-Patent Document 1 and 4.2.9.3 of Non-Patent Document 2 describe re-authentication and re-authorization triggered by an Authentication, Authorization and Accounting (AAA) server (AAA-S). Sections 5.15.10 of Non-Patent Document 1 and 4.2.9.4 of Non-Patent Document 2 describe revocation of Slice-Specific Authorization triggered by an AAA server (AAA-S).

[0017] Section 5.2 of Non-Patent Document 4 defines UAV Authentication and Authorization (UUAA). More specifically, Sections 5.2.2, 5.2.3, and 5.2.4 of Non-Patent Document 4 describe UAV authentication and authorization (UUAA). Section 5.2.5 of Non-Patent Document 4 describes C2 communication authorization (Authorization for C2) for realizing Command and Control (C2) Communication (hereinafter, UAV authentication and authorization (UUAA) and C2 communication authorization (Authorization for C2) can be read interchangeably).

[0018] The Third Generation Partnership Project (3GPP) SA2 Working Group has begun standardization work on 5G architecture enhancements for UAVs to enable drone systems utilizing mobile communications (see, for example, Non-Patent Document 4). These 5G architecture enhancements specify the following enhancements: UAV authentication and authorization functions by USS (UAS (Uncrewed Aerial System) Service Supplier) in mobility management. This UAV authentication and authorization is called UUAA-MM. The 5G architecture enhancements also specify the following enhancements: UAV authentication and authorization functions by USS in session management. This UAV authentication and authorization is called UUAA-SM. UUAA-MM and UUAA-SM may also be referred to as UUAA. The 5G architecture enhancements also specify the following enhancements: C2 communication authorization functions to enable C2 communication.

[0019] The UE performs either the UUAA-MM procedure or the UUAA-SM procedure to obtain the said certification and authorization.

[0020] UUAA-MM is executed based on operator policy, triggered by the registration procedure. AMF executes the UUAA-MM procedure if the UAV's Access and Mobility subscriber data includes an aerial UE subscription and the registration request message includes a CAA (Civil Aviation Administration)-Level UAV Identity (CAA-Level UAV ID). The CAA-Level UAV ID is issued, for example, by a USS that manages drone flights and is used to identify the UAV.

[0021] UUAA-SM is executed when UUAA-MM is not performed, triggered by the PDU session establishment procedure (PDU session establishment and PDU session modification). SMF executes the UUAA-SM procedure if the DNN and / or S-NSSAI for PDU session establishment are subject to the UAS Service and the PDU session establishment procedure includes a CAA-Level UAV ID.

[0022] If a UE (Unmanned Aircraft) enables operations based on C2 (Command and Control) communication, it must obtain C2 communication authorization. C2 communication involves the propagation of messages containing UAV operation commands and control information from a UAV controller or UTM (UAS Traffic Management) to a UAV, and the reporting of telemetry data from a UAV to a UAV controller or UTM. UTM refers to a system that supports UAVs in flight in safely and efficiently sharing airspace with other users.

[0023] C2 communication authorization may be performed using the UUAA-SM procedure described above, or it may be performed after UAV authentication and authorization. If performed after UAV authentication and authorization, the UE performs a PDU session modification procedure including the CAA-Level UAV ID and C2 authorization information. The SMF performs the C2 communication authorization procedure if the DNN and / or S-NSSAI of the PDU session to be modified are subject to the UAS Service and the PDU session modification procedure includes the CAA-Level UAV ID.

[0024] In the UUAA-MM, UUAA-SM, and C2 communication authorization procedures described above, after initiating each procedure, authentication and / or authorization information is exchanged multiple times between the USS and the UE, and the results of authentication and authorization are notified to the UE. In the UUAA-MM procedure, the results of authentication and authorization are included in the DL NAS TRANSPORT message sent by the AMF to the UE. In the UUAA-SM procedure, the results of authentication and authorization are included in the PDU session accept message sent by the SMF to the UE. Existing Network Triggered service request procedures are specified in Figure 4.2.3.3-1 of Non-Patent Document 2. [Prior art documents] [Non-patent literature]

[0025] [Non-Patent Document 1] 3GPP TS 23.501 V17.2.0 (2021-09) “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System architecture for the 5G System (5GS); Stage 2(Release 17)”, September 2021 [Non-Patent Document 2] 3GPP TS 23.502 V17.2.0 (2021-09) “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for the 5G System (5GS); Stage 2 (Release 17)”, September 2021 [Non-Patent Document 3] 3GPP TS 24.501 V17.4.1 (2021-09) “3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 (Release 17)”, September 2021 [Non-Patent Document 4] 3GPP TS 23.256 V17.0.0 (2021-09) “3rd Generation Partnership Project;Technical Specification Group Services and System Aspects;Support of Uncrewed Aerial Systems (UAS) connectivity, identification and tracking; Stage 2(Release 17)”, September 2021

Non-Patent Document 5

Summary of the Invention

Problems to be Solved by the Invention

[0026] The inventors have considered the authentication and authorization procedures related to UAS Service in session management and found various problems. First, the operations of the SMF and UE when the USS is not found in the UUAA-SM procedure are unclear.

[0027] Second, during the UUAA-SM procedure in a UAS Service associated only with a DNN, the operation of the UE when sending a new PDU SESSION ESTABLISHMENT REQUEST message carrying the same combination of DNN and S-NSSAI is unclear.

[0028] Third, when the AMF manages a UE context containing information indicating that UUAA-MM has failed, the operations of the UE and AMF when the UE sends a PDU SESSION ESTABLISHMENT REQUEST message including a DNN and / or S-NSSAI for the UAS service are unclear. Fourth, when the AMF manages a UE context containing information indicating that UUAA-MM has failed, the operations of the UE, AMF, and SMF when the UE sends a PDU SESSION ESTABLISHMENT REQUEST message including a DNN and / or S-NSSAI for the UAS service are unclear.

[0029] One of the objectives that the embodiments disclosed herein seek to achieve is to provide apparatus, methods, and programs that contribute to clarifying the behavior of the network and UE when a USS is not found in the UUAA-SM procedure. It should be noted that this objective is only one of several objectives that the embodiments disclosed herein seek to achieve. Other objectives or problems and novel features will be evident from the description herein or from the accompanying drawings. [Means for solving the problem]

[0030] In a first embodiment, a first core network node performing session management includes memory and at least one processor coupled to the memory. The at least one processor is configured to receive a session establishment request message from User Equipment (UE) that includes the address of an Uncrewed Aerial System (UAS) Service Supplier (USS). The at least one processor is configured to send a Network Exposure Function (NEF) authentication service invocation message that includes the address of the USS to a second core network node providing UAS services. The at least one processor is configured to receive a response message to the invocation message from the second core network node. If the response message contains a cause of failure relating to the USS corresponding to the USS's address, the at least one processor is configured to send a rejection response message to the UE for the session establishment request message. The rejection response message includes information indicating a failure of service relating to the USS corresponding to the USS's address.

[0031] In a second embodiment, User Equipment (UE) comprises memory and at least one processor coupled to the memory. The at least one processor is configured to send a session establishment request message, including the address of an Uncrewed Aerial System (UAS) Service Supplier (USS), to a first core network node that manages sessions. The at least one processor is configured to receive a rejection response message to the session establishment request message from the first core network node if the response message to the Network Exposure Function (NEF) authentication service call message, including the address of the USS, received by the first core network node from a second core network node that provides UAS services, includes a cause of failure relating to the USS corresponding to the address of the USS. The rejection response message includes information indicating a failure of service relating to the USS corresponding to the address of the USS.

[0032] In a third embodiment, a second core network node providing Uncrewed Aerial System (UAS) services includes memory and at least one processor coupled to the memory. The at least one processor is configured to receive a Network Exposure Function (NEF) authentication service invocation message, which includes the address of a UAS Service Supplier (USS), from a first core network node that manages sessions. The at least one processor is configured to send a response message to the first core network node for the invocation message. The response message includes a cause of failure relating to the USS corresponding to the USS's address, thereby causing the first core network node to send a rejection response message to the User Equipment (UE) for the session establishment request. The rejection response message includes information indicating a failure of service relating to the USS corresponding to the USS's address.

[0033] In a fourth embodiment, a third core network node performing mobility management comprises memory and at least one processor coupled to the memory. The at least one processor is configured to receive a session establishment request message from User Equipment (UE) that includes the address of an Uncrewed Aerial System (UAS) Service Supplier (USS). If the at least one processor cannot identify a first core network node performing session management corresponding to the USS address based on the USS address, it is configured to send a rejection response message to the session establishment request message to the UE. The rejection response message includes a failure cause indicating that the first core network node corresponding to the USS address could not be identified.

[0034] In a fifth embodiment, the method at a first core network node performing session management includes: receiving a session establishment request message from User Equipment (UE) that includes the address of an Uncrewed Aerial System (UAS) Service Supplier (USS); sending a Network Exposure Function (NEF) authentication service invocation message that includes the address of the USS to a second core network node providing UAS services; receiving a response message to the invocation message from the second core network node; and, if the response message includes a cause of failure relating to the USS corresponding to the address of the USS, sending a rejection response message to the session establishment request message to the UE. The rejection response message includes information indicating a failure of service relating to the USS corresponding to the address of the USS.

[0035] In a sixth aspect, the method in User Equipment (UE) includes sending a session establishment request message containing the address of an Uncrewed Aerial System (UAS) Service Supplier (USS) to a first core network node that manages sessions, and receiving a rejection response message to the session establishment request message from the first core network node if the response message to the Network Exposure Function (NEF) authentication service call message containing the address of the USS, received by the first core network node from a second core network node that provides UAS services, contains a failure cause relating to the USS corresponding to the address of the USS. The rejection response message contains information indicating a failure of service relating to the USS corresponding to the address of the USS.

[0036] In a seventh aspect, a method in a second core network node providing Uncrewed Aerial System (UAS) services includes receiving a Network Exposure Function (NEF) authentication service invocation message, which includes the address of a UAS Service Supplier (USS), from a first core network node performing session management, and sending a response message to the invocation message to the first core network node. The response message includes a failure cause relating to the USS corresponding to the USS's address, thereby causing the first core network node to send a rejection response message to the User Equipment (UE) for the session establishment request. The rejection response message includes information indicating a failure of service relating to the USS corresponding to the USS's address.

[0037] In the eighth aspect, the method at a third core network node performing mobility management includes receiving a session establishment request message from User Equipment (UE) that includes the address of an Uncrewed Aerial System (UAS) Service Supplier (USS), and, if a first core network node performing session management corresponding to the USS address cannot be identified based on the USS address, sending a rejection response message to the session establishment request message to the UE. The rejection response message includes a failure cause indicating that the first core network node corresponding to the USS address could not be identified.

[0038] In the ninth aspect, the program includes a set of instructions (software code) that, when loaded into a computer, cause the computer to perform the methods described in the fifth to eighth aspects above. [Effects of the Invention]

[0039] According to the above-described embodiment, it is possible to provide an apparatus, method, and program that contribute to clarifying the behavior of core network nodes and UEs when a USS is not found in the UUAA-SM procedure. [Brief explanation of the drawing]

[0040] [Figure 1] This figure shows an example of a cellular network configuration according to the embodiment. [Figure 2] This is a flowchart illustrating an example of the operation of the SMF according to the embodiment. [Figure 3] This is a sequence diagram showing an example of the operation of the UE, AMF, SMF, and UAS-NF according to the embodiment. [Figure 4] A flowchart illustrating an example of the operation of the UE according to the embodiment. [Figure 5] This flowchart shows an example of the operation of the AMF according to the embodiment. [Figure 6]This is a sequence diagram showing an example of the operation of the UE, AMF, and SMF according to the embodiment. [Figure 7] This flowchart shows an example of the operation of the AMF according to the embodiment. [Figure 8] This is a sequence diagram showing an example of the operation of the UE, AMF, and SMF according to the embodiment. [Figure 9] This is a flowchart illustrating an example of the operation of the SMF according to the embodiment. [Figure 10] This is a block diagram showing an example configuration of a UE according to the embodiment. [Figure 11] This is a block diagram showing an example configuration of the AMF according to the embodiment. [Modes for carrying out the invention]

[0041] The following describes specific embodiments in detail with reference to the drawings. In each drawing, the same or corresponding elements are denoted by the same reference numeral, and redundant explanations are omitted where necessary for clarity.

[0042] The multiple embodiments described below can be implemented independently or in combination as appropriate. These multiple embodiments have novel features that differ from each other. Therefore, these multiple embodiments contribute to solving different objectives or problems and contribute to producing different effects.

[0043] The following embodiments are described primarily with reference to 3GPP fifth-generation mobile communication systems (5G systems (5GS)). However, these embodiments may also be applicable to other cellular communication systems.

[0044] In particular, some of the embodiments described below may be applied to 3GPP fourth-generation mobile communication systems (Evolved Packet Systems (EPS)) as shown in Table 1, for example.

[0045] [Table 1]

[0046] <First Embodiment> Figure 1 shows an example configuration of a cellular network (ie., 5GS) according to this embodiment. Each element shown in Figure 1 is a network function and provides an interface defined by the 3rd Generation Partnership Project (3GPP). Each element (network function) shown in Figure 1 can be implemented, for example, as a network element on dedicated hardware, as a running software instance on dedicated hardware, or as an instantiated virtualization function on an application platform.

[0047] The cellular network shown in Figure 1 may be provided by a Mobile Network Operator (MNO), or it may be a Non-Public Network (NPN) provided by a party other than an MNO. If the cellular network shown in Figure 1 is an NPN, it may be an independent network referred to as a Stand-alone Non-Public Network (SNPN), or it may be an NPN linked to an MNO network referred to as a Public network integrated NPN.

[0048] A wireless terminal (ie, UE or UAV) 1 uses 5G connectivity services to communicate with a data network (DN) 7. More specifically, UE 1 is connected to an access network (ie, 5G Access Network (5GAN)) 5 and communicates with the data network (DN) 7 via a User Plane Function (UPF) 6 within the core network (ie, 5G core network (5GC)). AN5 includes a Next Generation Radio Access Network (NG-RAN) or a non-3GPP AN, or both. A Non-3GPP AN may be a network handling wireless LAN (WiFi) communication or a network handling wired communication, represented as a Wireline 5G Access Network (W-5GAN). UPF6 may include multiple interconnected UPFs. Hereafter, UE can be read as UAV.

[0049] In a 5G architecture, connectivity services between UE1 and DN7 are supported by one or more Protocol Data Unit (PDU) sessions. A PDU session is an association, session, or connection between UE1 and DN7. PDU sessions are used to provide PDU connectivity services (i.e., the exchange of PDUs between UE1 and DN7). UE1 establishes one or more PDU sessions with the UPF6 (i.e., PDU session anchors) to which UE1 and DN7 are connected. From a data transfer perspective, a PDU session consists of a tunnel within the 5GC (N9 tunnel), a tunnel between the 5GC and AN5 (N3 tunnel), and one or more radio bearers. UE1 may establish multiple PDU sessions with each of multiple UPFs (PDU session anchors)6 to access multiple DNs7 concurrently.

[0050] AMF2 is one of the network functions within the 5GC Control Plane. AMF2 provides the termination of the RAN Control Plane (CP) interface (i.e., N2 interface). AMF2 terminates a single signaling connection (i.e., N1 NAS signalling connection) with UE1 and provides registration management, connection management, and mobility management. AMF2 provides NF services (i.e., Namf interface) over a service-based interface (Namf interface) to NF consumers (e.g., other AMFs, Session Management Function (SMF)3, and Authentication Server Function (AUSF)4). The NF services provided by AMF2 include communication services (Namf_Communication). These communication services enable NF consumers (e.g., SMF3) to communicate with UE1 or AN5 via AMF2.

[0051] SMF3 is one of the network functions within the 5GC Control Plane. SMF3 manages PDU sessions. SMF3 sends and receives SM signaling messages (NAS-SM messages, N1 SM messages) to and from the Non-Access-Stratum (NAS) Session Management (SM) layer of UE1 via communication services provided by AMF2. SMF3 provides NF services on a service-based interface (i.e., Nsmf interface) to NF consumers (e.g., AMF2, other SMFs). The NF services provided by SMF3 include the PDU session management service (Nsmf_PDUSession). This NF service enables NF consumers (e.g., AMF2) to handle PDU sessions. SMF3 may also be an Intermediate SMF (I-SMF). I-SMF is inserted between AMF2 and the original SMF3 as needed when UPF6 belongs to a different SMF service area and cannot be controlled by the original SMF.

[0052] AUSF4 is one of the network functions within the 5GC Control Plane. AUSF4 provides NF services to NF consumers (e.g., AMF2, UDM8) over a service-based interface (i.e., Nausf interface). The NF services provided by AUSF4 include UE authentication services (e.g., Nausf_UEAuthentication and Nausf_NSSAA_Authenticate). The Nausf_UEAuthentication service provides UE authentication and related keying material to NF consumers (i.e., AMF). More specifically, AUSF4 works with UDM8 and the Authentication credential Repository and Processing Function (ARPF) to perform authentication using one of the two authentication methods supported by 5GS (i.e., 5G-Authentication and Key Agreement (AKA) and EAP-based authentication). After performing authentication, AUSF4 returns the authentication result and, if successful, the master key to AMF2. The master key is used by AMF2 to derive NAS security keys and other security key(s). For UE authentication, AUSF4 works closely with UDM8. The Nausf_NSSAA_Authenticate service provides NF consumers (e.g., AMF2) with authentication and authorization services specific to the network slice between UE1 and AAA servers via AUSF4.

[0053] UDM8 is one of the network functions within the 5GC Control Plane. UDM8 provides access to a database (i.e., User Data Repository (UDR)) where subscriber data (subscription information) is stored. UDM8 provides NF services (services) to NF consumers (e.g., AMF2, AUSF4, SMF3) via a service-based interface (i.e., NuDM interface). The NF services provided by UDM8 include subscriber data management services. These NF services enable NF consumers (e.g., AMF) to retrieve subscriber data and provide updated subscriber data to the NF consumers.

[0054] UAS NF9 is one of the network functions within the 5GC Control Plane. UAS NF9 is supported by NEF (Network Exposure Function) or SCEF (Service Capability Exposure Function) + NEF and is used for external exposure of services to the USS. UAS NF9 uses existing NEF / SCEF external exposure for UAV authentication / authorization, UAV flight authorization, UAV-UAVC pairing authorization and revocation related thereto, location reporting, and control of QoS / traffic filtering for C2 communications. Alternatively, it may be implemented and deployed in the form of a dedicated NEF that implements only UAS NF functionality. SCEF + NEF is a node that integrates SCEF, which is a logical node for 4G, and NEF, which is a logical node for 5G, in order to enable smooth interworking between 4G and 5G. SCEF+NEF nodes are associated with a UE for Service Capability Exposure if the UE supports mobility between EPS and 5GS.

[0055] UAS NF9 stores information regarding whether the re-authentication is in the AMF or SMF / SMF+PGW-C, and the address of the serving AMF or SMF / SMF+PGW-C, in order to support re-authentication requests by USS. Furthermore, UAS NF stores the results of the UUAA-MM procedure and the UUAA-SM procedure. SMF+PGW-C is a node that integrates the PGW-C, a logical node for 4G, and the SMF, a logical node for 5G, in order to facilitate smooth interworking between 4G and 5G. SMF / PGW-C is the core network node used for PDN connectivity when interworking between 5GS and EPS is supported.

[0056] NSSAAF (Network Slice-specific and SNPN Authentication and Authorization Function)10 connects to the authentication server, the AAA server (AAA-S), and supports network slice-specific authentication and authorization functions. If the AAA-S belongs to a third party, NSSAAF connects to the AAA-S via the AAA proxy (AAA-P).

[0057] The configuration example in Figure 1 shows only representative NFs for the sake of explanation. The cellular network according to this embodiment may also include other NFs not shown in Figure 1, such as Network Slice Selection Function (NSSF), Policy Control Function (PCF), Application Function (AF), NEF (Network Exposure Function), and NRF (Network Repository Function).

[0058] The inventors have examined the UUAA-SM procedure and identified various issues. For example, the behavior of the SMF and UE when the USS is not found is unclear.

[0059] This embodiment provides an example of the operation of SMF3 in the UUAA-SM procedure.

[0060] Figure 2 is a flowchart illustrating an example of the operation of SMF3 according to this embodiment. In step 201, SMF3 receives a PDU SESSION ESTABLISHMENT REQUEST message from UE1 containing a USS address (e.g., FQDN (Fully Qualified Domain Name)). The USS address is set to a Service-level-AA container IE.

[0061] In step 202, SMF3 invokes the Nnef_Authentication_authenticate service operation of UAS-NF9. This service operation includes the USS address (e.g., FQDN). For example, SMF3 sends an Nnef_Authentication_authenticate request message to UAS-NF9 that includes the USS address (e.g., FQDN) received from UE1.

[0062] In step 203, the Nnef_Authentication_authenticate response is received from UAS-NF9 in response to the Nnef_Authentication_authenticate service operation call.

[0063] If the Nnef_Authentication_authenticate response in step 203 contains the cause of failure (YES in step 204), the procedure proceeds to step 205. Note that at this time, the Nnef_Authentication_authenticate response may contain PEER_NOT_RESPONDING as the cause of failure (Application Error), although this is not the only possible option. Specifically, in response to the Nnef_Authentication_authenticate service operation call in step 202, UAS-NF9 attempts to call the Naf_Authentication_authenticate service operation, but since there is no response from USS (DN7), UAS-NF9 detects that an HTTP status code 504 Gateway Timeout has occurred and may set PEER_NOT_RESPONDING as the cause of failure (Application Error). In step 205, SMF3 sends a PDU SESSION ESTABLISHMENT REJECT message containing the cause of failure to UE1. The failure cause may indicate that the USS cannot be identified based on the specified USS address, or that there is no response from the USS identified based on the specified USS address. For example, the value indicating the failure cause is not limited to this, but could be "USS not available". Note that the failure cause is set in Service-level-AA response IE.

[0064] In contrast, if the Nnef_Authentication_authenticate response in step 203 does not contain the cause of failure (NO in step 204), the procedure proceeds to step 206. Here, if the Nnef_Authentication_authenticate response does not contain the cause of failure, the Nnef_Authentication_authenticate response may contain information indicating that the USS has been identified and connected to. For example, but not limited to this, "USS available" may be set in the Service-level-AA response IE. In step 206, SMF3 continues to perform the UUAA-SM procedure. Specifically, SMF3 sends the authentication message from the USS received via UAS-NF9 in step 203 to UE1. The authentication message may be included in the SERVICE-LEVEL AUTHENTICATION COMMAND message.

[0065] According to the operation shown in Figure 2, SMF3 can notify UE1 of the cause of failure specific to USS.

[0066] Figure 3 shows an example of the UUAA-SM procedure. In step 301, UE1 sends a UL NAS TRANSPORT message to AMF2 with the message PDU SESSION ESTABLISHMENT REQUEST set to request the establishment of a PDU session with DN7, which provides the UAS Service. The UL NAS TRANSPORT message may contain at least one of the following: the S-NSSAI corresponding to the UAS Service, the DNN corresponding to the UAS Service, and the CAA-Level UAV ID of UE1 as the Service Level Device Identity. The PDU SESSION ESTABLISHMENT REQUEST message may contain at least one of the following: the USS address corresponding to the UAS Service, and the CAA-Level UAV ID of UE1 as the Service Level Device Identity.

[0067] In step 302, AMF2 selects an SMF3 using at least one of the following: the S-NSSAI corresponding to the UAS Service, the DNN corresponding to the UAS Service, and the Service Level Device Identity, as configured in the UL NAS TRANSPORT message. If no SMF3 corresponding to the DN7 providing the UAS service is found in step 302, AMF2 executes step 308. In this case, AMF2 sets the failure cause as the inability to find a DN7 providing the UAS service and notifies UE1. Upon receiving this failure cause, UE1 may also notify the upper layer of the failure cause.

[0068] In step 303, AMF2 sends an Nsmf_PDUSession_CreateSMContext Request to SMF3, which contains the PDU SESSION ESTABLISHMENT REQUEST message received in step 302.

[0069] In step 304, SMF3 invokes the Nnef_Authentication_authenticate service operation of UAS-NF9. This service operation includes the USS address (e.g., FQDN). For example, SMF3 sends an Nnef_Authentication_authenticate request message to UAS-NF9 that includes the USS address (e.g., FQDN) received from UE1. In step 305, UAS-NF9 attempts to identify and connect to the USS based on the USS address specified in UE1. Specifically, UAS-NF9 identifies the USS using the specified USS address. Identifying the USS may also involve USS address resolution. If the USS identification is successful, UAS-NF9 calls the Naf_Authentication_authenticate service operation.

[0070] In step 306, UAS-NF9 notifies SMF3 of the USS identification and connection attempt results shown in step 305, including them in the Nnef_Authentication_authenticate response. For example, if the USS cannot be identified or there is no response from the identified USS, UAS-NF9 may notify SMF3 of the cause of the failure. For example, if there is a successful response from the identified USS, UAS-NF9 may notify SMF3 of the success, including information indicating the success.

[0071] In step 307, if SMF3 receives an Nnef_Authentication_authenticate response from UE1 containing the Service-level-AA container IE with the USS address set in the PDU SESSION ESTABLISHMENT REQUEST message, it sends a PDU SESSION ESTABLISHMENT REJECT message to AMF2 containing the reason for the failure.

[0072] In step 308, AMF2 sets the received PDU SESSION ESTABLISHMENT REJECT message into a DL NAS TRANSPORT message and sends it to UE1. Upon receiving the PDU SESSION ESTABLISHMENT REJECT message containing the cause of failure, UE1 may notify the upper layer of the cause of failure if it had sent a REGISTRAION REQUEST message with the USS address set to the Service-level-AA container IE.

[0073] According to this, in the UUAA-SM procedure, if the USS is not found or does not respond from the USS, the SMF will be able to notify the UE of the cause of the failure.

[0074] <Second Embodiment> This embodiment provides an example of the operation of UE1 in the UUAA-SM procedure. The example cellular network configuration according to this embodiment may be the same as the example shown in Figure 1.

[0075] Figure 4 is a flowchart illustrating an example of the operation of UE1 according to this embodiment. In step 401, UE1 sends a PDU SESSION ESTABLISHMENT REQUEST to AMF2 for a specific DNN, including the CAA-Level UAV ID (Service-level device ID). UE1 may determine the specific DNN based on URSP (UE Route Selection Policy). Specifically, if the Route selection components for a Traffic descriptor indicating a UAS Service include the specific DNN, UE1 may select the specific DNN in the PDU session establishment request for the UAS Service. An existing URSP structure is defined in Non-Patent Document 5, section 6.6.2. The specific DNN may be any DNN capable of providing a UAS Service. Upon receiving the PDU SESSION ESTABLISHMENT REQUEST for the specific DNN, AMF2 initiates the UUAA-SM procedure.

[0076] In step 402, UE1 detects a trigger for establishing a new PDU session for a specific combination of DNN and S-NSSAI. Here, the specific DNN may be the same as the specific DNN included in the PDU session establishment request in step 401. The specific S-NSSAI may be a specific S-NSSAI not included in the PDU session establishment request in step 401. Note that if the specific DNN selected by UE1 in step 401 is subject to UAS Service, UE1 may be configured not to send a new PDU session establishment request for that specific DNN until it receives a response to the PDU session establishment request in step 401. Alternatively, if UE1 has sent a PDU SESSION ESTABLISHMENT REQUEST message as a PDU session establishment request and has received a SERVICE-LEVEL AUTHENTICATION COMMAND message containing an authentication message from the network, UE1 may be configured not to send a new PDU session establishment request for that specific DNN until it receives a response to the PDU session establishment request. Furthermore, if UE1 selects a specific DNN and S-NSSAI combination as the UAS Service target in step 401, UE1 may be configured not to send a new PDU session establishment request for that specific DNN and S-NSSAI combination. Alternatively, if UE1 has sent a PDU SESSION ESTABLISHMENT REQUEST message as a PDU session establishment request and has received a SERVICE-LEVEL AUTHENTICATION COMMAND message containing an authentication message from the network, UE1 may be configured not to send a new PDU session establishment request for that specific DNN and S-NSSAI combination until it receives a response to the PDU session establishment request.

[0077] If the specific DNN and S-NSSAI combination is associated with a UAS Service (YES in step 403), the procedure proceeds to step 404. UE1 may perform the determination in step 403 based on URSP. In step 404, UE1 suspends the attempt to establish a new PDU session for the specific DNN and S-NSSAI combination. UE1 may also delay the attempt to establish a new PDU session for the specific DNN and S-NSSAI combination for a predetermined period.

[0078] Conversely, if the specific DNN and S-NSSAI combination is not associated with a UAS Service (NO in step 403), the procedure proceeds to step 405. In step 405, UE1 sends a new PDU session establishment request for the specific DNN and S-NSSAI combination.

[0079] As shown in Figure 4, UE1 can control PDU session establishment requests during the execution of the UUAA-SM procedure. This allows UE1 to prevent conflicts between the UUAA-SM procedure and the PDU session establishment procedure. For example, if UE1 has not received a response to a PDU session establishment request for a DNN associated with the UAS Service, it is not permitted to send a PDU session establishment request (without S-NSSAI) for the same DNN. On the other hand, even if UE1 has not received a response to a PDU session establishment request for a DNN associated with the UAS Service, it is permitted to send a PDU session establishment request for the same DNN and S-NSSAI combination. The response may be a PDU SESSION ESTABLISHMENT REJECT message or a PDU SESSION ESTABLISHMENT ACCEPT message.

[0080] Up to this point, we have described the control of PDU session establishment requests during the execution of the UUAA-SM procedure, but UE1 may perform similar actions for PDU session establishment requests during the execution of C2 communication authorization.

[0081] According to this, the network load can be reduced by interrupting the transmission of a new PDU SESSION ESTABLISHMENT REQUEST message by the UE containing the same DNN and S-NSSAI combination during the UUAA-SM procedure in a UAS Service associated only with a DNN.

[0082] Figure 4 illustrates the UE1's determination process for whether or not it can make a new PDU session establishment request based on a specific DNN or a specific DNN and a specific S-NSSAI. However, in other examples, UE1 may make this determination based on the CAA-Level UAV ID. Specifically, if the specific DNN selected by UE1 in step 401 is subject to UAS Service, UE1 recognizes that the UUAA-SM procedure is in progress (pending) until it receives a response to the PDU session establishment request in step 401, until the PLMN is changed, or until the UE is powered off, and does not send a new PDU session establishment request that includes the same CAA-Level UAV ID as the one included in the PDU session establishment request. Here, the response to the PDU session establishment request may be PDU SESSION ESTABLISHMENT ACCEPT or PDU SESSION ESTABLISHMENT REJECT. Furthermore, the response to the PDU session establishment request may include the same CAA-Level UAV ID that UE1 included in the PDU session establishment request. Note that even if UE1 selects a specific DNN and a specific S-NSSAI in step 401, the same operation as described above may be performed. Also, the CAA-Level UAV ID may be a Service Level Device Identity, a UAV identifier, or a recognition identifier for other UAVs.

[0083] <Third Embodiment> This embodiment provides the operation of AMF2 in the UUAA-SM procedure. The example of the cellular network configuration according to this embodiment may be the same as the example shown in Figure 1.

[0084] Figure 5 is a flowchart illustrating an example of the operation of AMF2 according to this embodiment. In step 501, AMF2 manages the UE context of UE1 which is in the RM-REGISTERED state. This UE context includes information indicating that UE1 failed UUAA-MM up to the time the UE context was generated. If UE1, which supports UUAA-MM in subscriber information, does not include the CAA-Level UAV ID in the registration request message during the registration procedure, AMF2 grants registration permission but includes information in the UE context indicating that UUAA-MM failed.

[0085] In step 502, AMF2 receives a PDU SESSION ESTABLISHMENT REQUEST message from UE1 to the UAS Service. AMF2 determines whether the PDU SESSION ESTABLISHMENT REQUEST message is for the UAS Service based on the DNN included in the UL NAS TRANSPORT message containing the PDU SESSION ESTABLISHMENT REQUEST message, or the combination of the DNN and S-NSSAI. This determination may be based, for example, on the DNN being the DNN corresponding to the UAS Service. Alternatively, this determination may be based on, for example, the S-NSSAI being the S-NSSAI corresponding to the UAS Service. Alternatively, this determination may be based on, for example, the DNN being the DNN corresponding to the UAS Service and the S-NSSAI being the S-NSSAI corresponding to the UAS Service. Furthermore, AMF2 may determine that the PDU SESSION ESTABLISHMENT REQUEST message is for a UAS Service if the CAA-Level UAV ID of UE1 is set as the Service Level Device Identity in the UL NAS TRANSPORT message containing the PDU SESSION ESTABLISHMENT REQUEST message.

[0086] In step 503, based on the information that the UE context managed in step 501 contains information indicating that UUAA-MM failed, the PDU SESSION ESTABLISHMENT REQUEST message received in step 502 is not forwarded to SMF3, and a DL NAS TRANSPORT message containing a PDU SESSION ESTABLISHMENT REJECT message is sent to UE1.

[0087] As shown in Figure 5, AMF2 can prevent UE1 from using the UAS Service if the UUAA-MM procedure has failed. In other words, it can prevent UEs that are not UAV authenticated and authorized from using the UAS Service. Specifically, as an example, AMF2 receives a UL NAS TRANSPORT message from UE1 that includes a DNN for the UAS Service, or a combination of DNN and S-NSSAI, along with a PDU SESSION ESTABLISHMENT REQUEST message. If the UE context of UE1 held by AMF2 contains information indicating that UUAA-MM has failed, AMF2 sends a DL NAS TRANSPORT message to UE1 that includes a failure cause value indicating that UUAA-MM has failed, or that UUAA-MM failed because it did not include the CAA-Level UAV ID. The failure cause value may be, but is not limited to, 5GMM cause "CAA-Level UAV ID is missing".

[0088] Figure 6 shows an example of the UUAA-SM procedure in this embodiment. In step 601, AMF2 manages the UE context of UE1, which is in the RM-REGISTERED state. This UE context contains information indicating that UE1 failed UUAA-MM up to the time the UE context was generated.

[0089] In step 602, AMF2 receives a UL NAS TRANSPORT message containing a PDU SESSION ESTABLISHMENT REQUEST message. The PDU SESSION ESTABLISHMENT REQUEST message may be a PDU SESSION ESTABLISHMENT REQUEST message containing a DNN to the UAS Service, or a combination of a DNN and S-NSSAI.

[0090] In step 603, AMF2 sends a DL NAS TRANSPORT message containing a PDU SESSION ESTABLISHMENT REJECT message. The sending of the DL NAS TRANSPORT message containing the PDU SESSION ESTABLISHMENT REJECT message in step 603 may be based, for example, on the fact that the DNN is a DNN corresponding to the UAS Service and the UE context in step 601 includes information indicating that UUAA-MM failed. Alternatively, it may be based on the fact that the S-NSSAI is an S-NSSAI corresponding to the UAS Service and the UE context in step 601 includes information indicating that UUAA-MM failed. The DL NAS TRANSPORT message may include a failure cause value. The failure cause value may be a value indicating that UUAA-MM has failed, or that UUAA-MM failed because it did not include the CAA-Level UAV ID. For example, but is not limited to this, it may be 5GMM cause "CAA-Level UAV ID is missing".

[0091] If the DNN, or a combination of DNN and S-NSSAI, sent from UE1 along with the PDU SESSION ESTABLISHMENT REQUEST message is for the UAS Service, and UE1 receives the PDU SESSION ESTABLISHMENT REJECT message along with the above-mentioned failure cause in step 603, UE1 may notify the upper layer of the failure cause. In another example, if the DNN, or a combination of DNN and S-NSSAI, sent from UE1 along with the PDU SESSION ESTABLISHMENT REQUEST message is for the UAS Service, and UE1 receives the PDU SESSION ESTABLISHMENT REJECT message along with the above-mentioned failure cause in step 603, UE1 may de-register locally. Furthermore, UE1 may perform the registration procedure including the CAA-Level UAV ID.

[0092] <Fourth Embodiment> This embodiment provides the operation of AMF2 in the UUAA-SM procedure. The example of the cellular network configuration according to this embodiment may be the same as the example shown in Figure 1.

[0093] Figure 7 is a flowchart illustrating an example of the operation of AMF2 according to this embodiment. In step 701, AMF2 manages the UE context of UE1 which is in the RM-REGISTERED state. This UE context includes information indicating that UE1 failed UUAA-MM up to the time the UE context was generated. If UE1, which supports UUAA-MM in subscriber information, does not include the CAA-Level UAV ID in the registration request message during the registration procedure, AMF2 grants registration permission but includes information in the UE context indicating that UUAA-MM failed.

[0094] In step 702, AMF2 receives a PDU SESSION ESTABLISHMENT REQUEST message from UE1 to the UAS Service. AMF2 determines whether the message is a PDU SESSION ESTABLISHMENT REQUEST message to the UAS Service based on the DNN included in the UL NAS TRANSPORT message containing the PDU SESSION ESTABLISHMENT REQUEST message, or a combination of the DNN and S-NSSAI. AMF2 may also determine that the message is a PDU SESSION ESTABLISHMENT REQUEST message to the UAS Service if the CAA-Level UAV ID of UE1 is set as the Service Level Device Identity in the UL NAS TRANSPORT message containing the PDU SESSION ESTABLISHMENT REQUEST message.

[0095] In step 703, AMF2 sends a PDU SESSION ESTABLISHMENT REQUEST message to SMF3, along with a value indicating that UUAA-MM has failed or a value indicating that UUAA-MM has failed because it did not include the CAA-Level UAV ID.

[0096] According to the operation shown in Figure 7, AMF2 can prevent UE1 from using the UAS Service if the UUAA-MM procedure has failed. In other words, it can prevent UEs that are not UAV authenticated and authorized from using the UAS Service. Specifically, AMF2 receives a UL NAS TRANSPORT message from UE1 that includes a DNN for the UAS Service, or a combination of DNN and S-NSSAI, along with a PDU SESSION ESTABLISHMENT REQUEST message. If the UE context held by AMF2 contains information indicating that UUAA-MM has failed, AMF2 sends information to SMF3 indicating that UUAA-MM has failed, or that UUAA-MM failed because it did not include the CAA-Level UAV ID. Specifically, the information indicating that UUAA-MM has failed, or that UUAA-MM failed because it did not include the CAA-Level UAV ID, may be, but is not limited to, "UUAA-MM failed due to missing CAA-Level UAV ID".

[0097] Figure 8 shows an example of the UUAA-SM procedure in this embodiment. In step 801, AMF2 manages the UE context of UE1, which is in the RM-REGISTERED state. This UE context contains information indicating that UE1 failed UUAA-MM up to the time the UE context was generated.

[0098] In step 802, AMF2 receives a UL NAS TRANSPORT message containing a PDU SESSION ESTABLISHMENT REQUEST message. The PDU SESSION ESTABLISHMENT REQUEST message may be a PDU SESSION ESTABLISHMENT REQUEST message containing a DNN to the UAS Service, or a combination of a DNN and S-NSSAI.

[0099] In step 803, AMF2 calls the Nsmf_PDUSession_CreateSMContext request service operation. This service operation may be called with information indicating that the UAA-MM has failed, or that the UUAA-MM failed because it did not include the CAA-Level UAV ID.

[0100] In step 804, SMF3 sends an Nsmf_PDUSession_CreateSMContext response to AMF2 with information indicating that UUAA-MM has failed or that UUAA-MM has failed because it did not include the CAA-Level UAV ID. Specifically, but not limited to, "SERVICE_NOT_AUTHORIZED" or "SERVICE_NOT ALLOWED" may be set in the Nsmf_PDUSession_CreateSMContext response as an application error.

[0101] In step 805, AMF2 sends a DL NAS TRANSPORT message containing a PDU SESSION ESTABLISHMENT REJECT message. This DL NAS TRANSPORT message may include a failure cause value. The failure cause value may be a value indicating that the UUAA-MM failed, or that the UUAA-MM failed because it did not include the CAA-Level UAV ID. For example, but is not limited to, it may be 5GSM cause "CAA-Level UAV ID is missing".

[0102] If the DNN, or a combination of DNN and S-NSSAI, sent from UE1 along with the PDU SESSION ESTABLISHMENT REQUEST message is for the UAS Service, and UE1 receives the PDU SESSION ESTABLISHMENT REJECT message along with the above-mentioned failure cause in step 805, UE1 may notify the upper layer of the failure cause. In another example, if the DNN, or a combination of DNN and S-NSSAI, sent from UE1 along with the PDU SESSION ESTABLISHMENT REQUEST message is for the UAS Service, and UE1 receives the PDU SESSION ESTABLISHMENT REJECT message along with the above-mentioned failure cause in step 805, UE1 may de-register locally. Furthermore, UE1 may perform the registration procedure including the CAA-Level UAV ID.

[0103] <Fifth Embodiment> This embodiment provides an example of the operation of SMF3 in the UUAA-SM procedure. The example cellular network configuration according to this embodiment may be the same as the example shown in Figure 1.

[0104] Figure 9 is a flowchart showing an example of the operation of SMF3 according to this embodiment. In step 901, SMF3 executes a UUAA-SM procedure associated with a specific CAA-Level UAV ID (Service-level device ID). For example, it may execute a UUAA-SM procedure associated with a UAV ID assigned to a USS.

[0105] In step 902, SMF3 receives a PDU session establishment request from UE1 that includes the same CAA-Level UAV ID as the CAA-Level UAV ID associated with the running UUAA-SM. For example, while executing the UUAA-SM procedure in step 901, SMF3 may receive a session establishment request message from UE1 that includes the same UAV ID as the UAV ID in step 901.

[0106] In step 903, SMF3 rejects the PDU session establishment request received in step 902 because it is currently executing the UUAA-SM associated with the CAA-Level UAV ID. Specifically, SMF3 sends a PDU SESSION ESTABLISHMENT REJECT message to UE1, including a cause value indicating that the UUAA-SM associated with the CAA-Level UAV ID is currently executing. The cause value may be a 5GSM Cause value. The cause value may also be called the failure cause. The cause value may also indicate that the rejection is based on the fact that the UUAA-SM procedure is currently executing for the UAV ID.

[0107] As shown in Figure 9, SMF3 can control PDU session establishment requests during the execution of the UUAA-SM procedure. This allows SMF3 to prevent conflicts between the UUAA-SM procedure and the PDU session establishment procedure.

[0108] Next, the configuration examples of UE1, AMF2, SMF3, and UAS-NF9 according to the above-described multiple embodiments will be explained. Figure 10 is a block diagram showing a configuration example of UE1. The Radio Frequency (RF) transceiver 1401 performs analog RF signal processing to communicate with NG-RAN nodes. The RF transceiver 1401 may include multiple transceivers. The analog RF signal processing performed by the RF transceiver 1401 includes frequency upconversion, frequency downconversion, and amplification. The RF transceiver 1401 is coupled with the antenna array 1402 and the baseband processor 1403. The RF transceiver 1401 receives modulation symbol data (or OFDM symbol data) from the baseband processor 1403, generates a transmit RF signal, and supplies the transmit RF signal to the antenna array 1402. The RF transceiver 1401 also generates a baseband receive signal based on the received RF signal received by the antenna array 1402 and supplies this to the baseband processor 1403. The RF transceiver 1401 may include an analog beamformer circuit for beamforming. The analog beamformer circuit may include, for example, multiple phase shifters and multiple power amplifiers.

[0109] The baseband processor 1403 performs digital baseband signal processing (data plane processing) and control plane processing for wireless communication. Digital baseband signal processing includes (a) data compression / decompression, (b) data segmentation / concatenation, (c) generation / decomposition of transmission format (transmission frame), (d) transmission path coding / decoding, (e) modulation (symbol mapping) / demodulation, and (f) generation of OFDM symbol data (baseband OFDM signal) by Inverse Fast Fourier Transform (IFFT). Control plane processing, on the other hand, includes communication management at Layer 1 (e.g., transmit power control), Layer 2 (e.g., radio resource management and hybrid automatic repeat request (HARQ) processing), and Layer 3 (e.g., signaling related to attach, mobility, and call management).

[0110] For example, the digital baseband signal processing by the baseband processor 1403 may include signal processing for the Service Data Adaptation Protocol (SDAP) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, Medium Access Control (MAC) layer, and Physical (PHY) layer. Furthermore, the control plane processing by the baseband processor 1403 may include processing for the Non-Access Stratum (NAS) protocol, Radio Resource Control (RRC) protocol, and MAC Control Elements (CEs).

[0111] The baseband processor 1403 may perform Multiple Input Multiple Output (MIMO) encoding and precoding for beamforming.

[0112] The baseband processor 1403 may include a modem processor (e.g., Digital Signal Processor (DSP)) that performs digital baseband signal processing and a protocol stack processor (e.g., Central Processing Unit (CPU) or Micro Processing Unit (MPU)) that performs control plane processing. In this case, the protocol stack processor that performs control plane processing may be shared with the application processor 1404 described later.

[0113] The application processor 1404 is also called a CPU, MPU, microprocessor, or processor core. The application processor 1404 may include multiple processors (multiple processor cores). The application processor 1404 implements various functions of the UE1 by executing system software programs (Operating System (OS)) and various application programs (e.g., calling applications, web browsers, mail clients, camera operation applications, music playback applications) read from memory 1406 or memory not shown.

[0114] In some implementations, the baseband processor 1403 and the application processor 1404 may be integrated on a single chip, as shown by the dashed line (1405) in Figure 10. In other words, the baseband processor 1403 and the application processor 1404 may be implemented as a single System on Chip (SoC) device 1405. An SoC device is sometimes called a System Large Scale Integration (LSI) or chipset.

[0115] Memory 1406 is volatile memory, non-volatile memory, or a combination thereof. Memory 1406 may include multiple physically independent memory devices. Volatile memory is, for example, Static Random Access Memory (SRAM) or Dynamic RAM (DRAM), or a combination thereof. Non-volatile memory is Mask Read Only Memory (MROM), Electrically Erasable Programmable ROM (EEPROM), flash memory, or hard disk drive, or any combination thereof. For example, memory 1406 may include an external memory device accessible from the baseband processor 1403, the application processor 1404, and the SoC 1405. Memory 1406 may also include an internal memory device integrated within the baseband processor 1403, the application processor 1404, or the SoC 1405. Furthermore, memory 1406 may include memory within a Universal Integrated Circuit Card (UICC).

[0116] Memory 1406 may store one or more software modules (computer programs) 1407 containing instruction sets and data for performing the processing by UE1 as described in the above-described embodiments. In some implementations, the baseband processor 1403 or application processor 1404 may be configured to read and execute the software modules 1407 from memory 1406 to perform the processing of UE1 as described with reference to the drawings in the above embodiments.

[0117] Furthermore, the control plane processing and operation performed by the UE1 described in the above embodiment can be realized by other elements other than the RF transceiver 1401 and antenna array 1402, namely at least one of the baseband processor 1403 and application processor 1404 and the memory 1406 storing the software module 1407.

[0118] Figure 11 shows an example configuration of AMF2. SMF3 and UAS-NF9 may also be configured as shown in Figure 11. Referring to Figure 11, AMF2 includes a network interface 1501, a processor 1502, and memory 1503. The network interface 1501 is used, for example, to communicate with RAN nodes and with other network functions (NFs) or nodes within the 5GC. Other NFs or nodes within the 5GC include, for example, UDM, AUSF, SMF, and PCF. The network interface 1501 may include, for example, a network interface card (NIC) compliant with the IEEE 802.3 series.

[0119] The processor 1502 may be, for example, a microprocessor, a Micro Processing Unit (MPU), or a Central Processing Unit (CPU). The processor 1502 may include multiple processors.

[0120] Memory 1503 is composed of volatile memory and non-volatile memory. Memory 1503 may include multiple physically independent memory devices. Volatile memory is, for example, Static Random Access Memory (SRAM) or Dynamic RAM (DRAM), or a combination thereof. Non-volatile memory is Mask Read Only Memory (MROM), Electrically Erasable Programmable ROM (EEPROM), flash memory, or hard disk drive, or any combination thereof. Memory 1503 may include storage located away from the processor 1502. In this case, the processor 1502 may access memory 1503 via a network interface 1501 or an I / O interface not shown.

[0121] The memory 1503 may store one or more software modules (computer programs) 1504 containing instruction sets and data for performing the processing by the AMF2 as described in the above embodiments. In some implementations, the processor 1502 may be configured to perform the processing of the AMF2 as described in the above embodiments by reading and executing the software modules 1504 from the memory 1503.

[0122] As illustrated with Figures 10 and 11, each of the processors in the UE1, AMF2, and SMF3 according to the above embodiment executes one or more programs containing a set of instructions for causing a computer to perform the algorithm described with reference to the drawings. This program can be stored and supplied to the computer using various types of non-transitory computer-readable medium. Non-transitory computer-readable mediums include various types of tangible storage mediums. Examples of non-transitory computer-readable mediums include magnetic recording media (e.g., flexible disks, magnetic tapes, hard disk drives), magneto-optical recording media (e.g., magneto-optical disks), Compact Disc Read Only Memory (CD-ROM), CD-R, CD-R / W, and semiconductor memory (e.g., mask ROM, programmable ROM (PROM), erasable PROM (EPROM), flash ROM, and random access memory (RAM)). The program may also be supplied to the computer using various types of transient computer-readable medium. Examples of temporary computer-readable media include electrical signals, optical signals, and electromagnetic waves. Temporary computer-readable media can supply programs to a computer via wired communication channels such as electric wires and optical fibers, or via wireless communication channels.

[0123] In this specification, a User Equipment (UE) is an entity connected to a network via a wireless interface. A User Equipment (UE) in this specification is not limited to a dedicated communication device, but may be any device having the communication capabilities of a User Equipment (UE) as described herein, such as the following:

[0124] The terms "User Equipment (UE)," "mobile station," "mobile terminal," "mobile device," and "wireless device" (as used in 3GPP) are generally intended to be synonymous with each other. A UE may be a standalone mobile station such as a terminal, mobile phone, smartphone, tablet, cellular IoT terminal, or IoT device. The terms "UE" and "wireless device" also encompass devices that remain stationary for extended periods.

[0125] UE may include, for example, production equipment, manufacturing equipment and / or energy-related machinery (such as boilers, engines, turbines, solar panels, wind turbines, hydroelectric generators, thermal power generators, nuclear power generators, batteries, nuclear systems, nuclear-related equipment, heavy electrical equipment, pumps including vacuum pumps, compressors, fans, blowers, hydraulic equipment, pneumatic equipment, metalworking machinery, manipulators, robots, robotic application systems, tools, molds, rolls, conveying equipment, lifting equipment, cargo handling equipment, textile machinery, sewing machinery, printing presses, printing-related machinery, paper processing machinery, chemical machinery, mining machinery, mining-related machinery, construction machinery, construction-related machinery, agricultural machinery and / or equipment, forestry machinery and / or equipment, fishing machinery and / or equipment, safety and / or environmental protection equipment, tractors, bearings, precision bearings, chains, gears, power transmissions, lubrication systems, valves, pipe fittings and / or application systems of any of the above-mentioned equipment or machinery).

[0126] UE may be, for example, a transport device (such as a vehicle, automobile, motorcycle, bicycle, train, bus, handcart, rickshaw, ship and other watercraft, airplane, rocket, satellite, drone, balloon, etc.).

[0127] The UE may be, for example, information and communication equipment (such as computers and related devices, communication equipment and related devices, electronic components, etc.). UE may include, for example, refrigerators, refrigerator applications and equipment, commercial and service equipment, vending machines, automated service machines, office machinery and equipment, and consumer electrical and electronic machinery and appliances (such as audio equipment, speakers, radios, video equipment, televisions, microwave ovens, rice cookers, coffee makers, dishwashers, washing machines, dryers, fans, ventilation fans and related products, vacuum cleaners, etc.).

[0128] The UE may be, for example, an electronic application system or electronic application device (such as an X-ray device, particle accelerator, radioactive material application device, sound wave application device, electromagnetic application device, power application device, etc.).

[0129] UE may include, for example, light bulbs, lighting, weighing machines, analytical instruments, testing machines and measuring instruments (such as smoke detectors, human alarm sensors, motion sensors, and wireless tags), watches or clocks, scientific and chemical instruments, optical instruments, medical equipment and / or medical systems, weapons, tools and implements, or hand tools.

[0130] The UE may be, for example, a personal digital assistant or device with wireless communication capabilities (for example, an electronic device configured to have a wireless card or wireless module attached or inserted into it, such as a personal computer or electronic measuring instrument).

[0131] An UE (Unified User) may be a device or part of a device that provides the following applications, services, and solutions in the Internet of Things (IoT), for example, using wired or wireless communication technologies: An IoT device (or thing) comprises appropriate electronics, software, sensors, network connectivity, etc., that enable the device to collect and exchange data with each other and with other communication devices. An IoT device may be an automated device that follows software instructions stored in internal memory. An IoT device may operate without requiring human supervision or response. An IoT device may be a device that is installed for a long period of time and / or may remain in an inactive state for a long period of time. An IoT device may be implemented as part of a stationary device. An IoT device may be embedded in a non-stationary device (e.g., a vehicle) or attached to an animal or person that is being monitored / tracked. IoT technology may be implemented on any communication device that can be connected to a communication network that sends and receives data regardless of human input control or software instructions stored in memory. IoT devices are sometimes also called Machine Type Communication (MTC) devices, Machine to Machine (M2M) communication devices, or Narrow Band-IoT (NB-IoT) UEs.

[0132] The UE may support one or more IoT or MTC applications.

[0133] Some examples of MTC applications are listed in 3GPP TS22.368 V13.2.0 (2017-01-13) Annex B (the contents of which are incorporated herein by reference). This list is not exhaustive and represents only examples of MTC applications. In this list, the service area of ​​an MTC application includes Security, Tracking & Tracing, Payment, Health, Remote Maintenance / Control, Metering, and Consumer Devices.

[0134] Examples of MTC applications related to security include surveillance systems, landline backup, control of physical access (e.g., to buildings), and car / driver security.

[0135] Examples of MTC applications related to tracking and tracing include fleet management, order management, telematics insurance: pay as you drive (PAYD), asset tracking, navigation, traffic information, road tolling, and road traffic optimization / steering.

[0136] Examples of MTC applications related to payments include point of sales (POS), vending machines, and gaming machines.

[0137] Examples of health-related MTC applications include monitoring vital signs, supporting the aged or handicapped, web-access telemedicine points, and remote diagnostics.

[0138] Examples of MTC applications related to remote maintenance / control include sensors, lighting, pumps, valves, elevator control, vending machine control, and vehicle diagnostics.

[0139] Examples of MTC applications related to metering include power, gas, water, heating, grid control, and industrial metering.

[0140] Examples of MTC applications for consumer electronics include digital photo frames, digital cameras, and ebooks.

[0141] Applications, services, and solutions include, by way of example, MVNO (Mobile Virtual Network Operator) services / systems, disaster prevention radio services / systems, in-building wireless telephone (PBX (Private Branch eXchange)) services / systems, PHS / digital cordless telephone services / systems, Point of sales (POS) systems, advertising transmission services / systems, multicast (Multimedia Broadcast and Multicast Service (MBMS)) services / systems, V2X (Vehicle to Everything) services / systems, in-train mobile radio services / systems, location information-related services / systems, disaster / emergency wireless communication services / systems, IoT (Internet of Things) services / systems, community services / systems, video distribution services / systems, Femto cell application services / systems, VoLTE (Voice over LTE) services / systems, wireless tag services / systems, charging services / systems, radio on-demand services / systems, roaming services / systems, user behavior monitoring services / systems, communication carrier / communication NW selection services / systems, function-limited services / systems, PoC (Proof of Concept) services / systems, personal information management services / systems for terminals, display / video services / systems for terminals, non-communication services / systems for terminals, ad hoc NW / DTN (Delay Tolerant Networking) services / systems, and the like.

[0142] The categories of UEs described above are merely application examples of the technical ideas and embodiments described in this specification. The UEs in this specification are not limited to these examples, and those skilled in the art can make various changes to them.

[0143] The embodiments described above are merely examples of how the technical concept obtained by the present inventor can be applied. In other words, the technical concept is not limited to the embodiments described above, and various modifications can be made to them.

[0144] For example, some or all of the above embodiments may also be described as follows, but are not limited to the following. (Note 1-1) The first core network node that performs session management, Memory and At least one processor coupled to the memory, Equipped with, The at least one processor is configured to receive a session establishment request message from User Equipment (UE) that includes the address of an Uncrewed Aerial System (UAS) Service Supplier (USS). The at least one processor is configured to send a Network Exposure Function (NEF) authentication service invocation message, including the address of the USS, to a second core network node that provides UAS services. The at least one processor is configured to receive a response message to the call message from the second core network node. The at least one processor is configured to send a rejection response message to the session establishment request message if the response message contains a cause of failure relating to the USS corresponding to the address of the USS. The rejection response message includes information indicating a failure of service relating to the USS corresponding to the USS address, The first core network node. (Appendix 1-2) The aforementioned cause of failure was, In response to the aforementioned call message, the second core network node sends an authentication request message to the USS corresponding to the USS's address, indicating that there is no response from the USS, or This indicates that the USS cannot be identified based on the address of the USS. The first core network node described in Appendix 1-1. (Appendix 1-3) User Equipment (UE), Memory and At least one processor coupled to the memory, Equipped with, The at least one processor is configured to send a session establishment request message containing the address of an Uncrewed Aerial System (UAS) Service Supplier (USS) to a first core network node that manages the session. The at least one processor is configured to receive a rejection response message to the session establishment request message from the first core network node if the response message to the Network Exposure Function (NEF) authentication service call message, which includes the address of the USS, received by the first core network node from the second core network node providing the UAS service, includes a failure cause relating to the USS corresponding to the address of the USS. The rejection response message includes information indicating a failure of service relating to the USS corresponding to the USS address, UE. (Appendix 1-4) A second core network node that provides Uncrewed Aerial System (UAS) services, Memory and At least one processor coupled to the memory, Equipped with, The at least one processor is configured to receive a Network Exposure Function (NEF) authentication service call message, which includes the address of the UAS Service Supplier (USS), from a first core network node that performs session management. The at least one processor is configured to send a response message to the call message to the first core network node. By including the cause of failure for the USS corresponding to the USS address in the response message, the first core network node is prompted to send a rejection response message to the User Equipment (UE) for the session establishment request. The rejection response message includes information indicating a failure of service relating to the USS corresponding to the USS address, The second core network node. (Appendix 1-5) A third core network node that performs mobility management, Memory and At least one processor coupled to the memory, Equipped with, The at least one processor is configured to receive a session establishment request message from User Equipment (UE) that includes the address of an Uncrewed Aerial System (UAS) Service Supplier (USS). The at least one processor is configured to send a rejection message to the session establishment request message to the UE if it cannot identify a first core network node that performs session management corresponding to the USS address based on the USS address. The rejection message includes a failure reason indicating that the first core network node corresponding to the USS address could not be identified. The third core network node. (Appendix 1-6) A method for performing session management on a first core network node, The User Equipment (UE) receives a session establishment request message containing the address of the Uncrewed Aerial System (UAS) Service Supplier (USS). Send a Network Exposure Function (NEF) authentication service call message, including the address of the aforementioned USS, to the second core network node providing the UAS service. Receiving a response message to the aforementioned call message from the second core network node, If the response message contains a failure cause relating to the USS corresponding to the address of the USS, the UE sends a rejection response message to the session establishment request message. The rejection response message includes information indicating a failure of service relating to the USS corresponding to the USS address, method. (Appendix 1-7) A method in User Equipment (UE), Send a session establishment request message containing the address of the Uncrewed Aerial System (UAS) Service Supplier (USS) to the first core network node that manages the session. The system includes receiving a rejection response message to the session establishment request message from the first core network node if the response message to the Network Exposure Function (NEF) authentication service call message, which includes the address of the USS, received by the first core network node from the second core network node providing the UAS service, contains a failure cause related to the USS corresponding to the address of the USS, The rejection response message includes information indicating a failure of service relating to the USS corresponding to the USS address, method. (Appendix 1-8) A method in a second core network node providing Uncrewed Aerial System (UAS) services, The first core network node that manages the session receives a Network Exposure Function (NEF) authentication service call message containing the address of the UAS Service Supplier (USS). The system includes sending a response message to the aforementioned call message to the first core network node, By including the cause of failure for the USS corresponding to the USS address in the response message, the first core network node is prompted to send a rejection response message to the User Equipment (UE) for the session establishment request. The rejection response message includes information indicating a failure of service relating to the USS corresponding to the USS address, method. (Appendix 1-9) A method for a third core network node that performs mobility management, The User Equipment (UE) receives a session establishment request message containing the address of the Uncrewed Aerial System (UAS) Service Supplier (USS). If, based on the USS address, a first core network node that performs session management corresponding to the USS address cannot be identified, a rejection response message to the session establishment request message is sent to the UE. The rejection message includes a failure reason indicating that the first core network node corresponding to the USS address could not be identified. method. (Appendix 1-10) A non-temporary computer-readable medium containing a program for causing a computer to perform a method in a first core network node that performs session management, The aforementioned method, The User Equipment (UE) receives a session establishment request message containing the address of the Uncrewed Aerial System (UAS) Service Supplier (USS). Send a Network Exposure Function (NEF) authentication service call message, including the address of the aforementioned USS, to the second core network node providing the UAS service. Receiving a response message to the aforementioned call message from the second core network node, If the response message contains a failure cause relating to the USS corresponding to the address of the USS, the UE sends a rejection response message to the session establishment request message. The rejection response message includes information indicating a failure of service relating to the USS corresponding to the USS address, A non-temporary computer-readable medium equipped with [a specific feature / ability]. (Appendix 1-11) A non-temporary computer-readable medium containing a program for causing a computer to perform a method in User Equipment (UE), The aforementioned method, Send a session establishment request message containing the address of the Uncrewed Aerial System (UAS) Service Supplier (USS) to the first core network node that manages the session. The system includes receiving a rejection response message to the session establishment request message from the first core network node if the response message to the Network Exposure Function (NEF) authentication service call message, which includes the address of the USS, received by the first core network node from the second core network node providing the UAS service, contains a failure cause related to the USS corresponding to the address of the USS, The rejection response message includes information indicating a failure of service relating to the USS corresponding to the USS address, A non-temporary computer-readable medium equipped with [a specific feature / ability]. (Appendix 1-12) A non-temporary computer-readable medium containing a program for causing a computer to perform a method in a second core network node that provides Uncrewed Aerial System (UAS) services, The aforementioned method, The first core network node that manages the session receives a Network Exposure Function (NEF) authentication service call message containing the address of the UAS Service Supplier (USS). The system includes sending a response message to the aforementioned call message to the first core network node, By including the cause of failure for the USS corresponding to the USS address in the response message, the first core network node is prompted to send a rejection response message to the User Equipment (UE) for the session establishment request. The rejection response message includes information indicating a failure of service relating to the USS corresponding to the USS address, A non-temporary computer-readable medium equipped with [a specific feature / ability]. (Appendix 1-13) A non-temporary computer-readable medium containing a program for causing a computer to perform a method in a third core network node that performs mobility management, The aforementioned method, The User Equipment (UE) receives a session establishment request message containing the address of the Uncrewed Aerial System (UAS) Service Supplier (USS). If, based on the USS address, a first core network node that performs session management corresponding to the USS address cannot be identified, a rejection response message to the session establishment request message is sent to the UE. The rejection message includes a failure reason indicating that the first core network node corresponding to the USS address could not be identified. A non-temporary computer-readable medium equipped with [a specific feature / ability]. (Note 2-1) User Equipment (UE), Memory and At least one processor coupled to the memory, Equipped with, The at least one processor is configured to send a first session establishment request message to a first core network node that performs session management, requesting the establishment of a first session for a Data Network Name (DNN) corresponding to an Uncrewed Aerial System (UAS) Service Supplier (USS). If at least one processor detects a trigger requesting the establishment of a second session for a combination of the DNN and Single Network Slice Selection Assistance Information (S-NSSAI) before receiving a response to the session establishment request message, it is configured to interrupt sending a second session establishment request message requesting the establishment of the second session to the first core network node, depending on whether the combination of the DNN and the first S-NSSAI among the S-NSSAI is associated with the service of the UAS. The second session described above is different from the first session described above. UE. (Note 2-2) The at least one processor is configured to, if it detects a trigger requesting the establishment of a second session for the combination of the DNN and the S-NSSAI before receiving a response to the session establishment request message, send a second session establishment request message to the first core network node requesting the establishment of the second session, depending on whether the combination of the DNN and the second S-NSSAI among the S-NSSAIs is associated with a service of the UAS. UE as described in Appendix 2-1. (Appendix 2-3) A method in User Equipment (UE), Send a first session establishment request message to the first core network node that manages sessions, requesting the establishment of a first session for the Data Network Name (DNN) corresponding to the Uncrewed Aerial System (UAS) Service Supplier (USS). If, before receiving a response to the session establishment request message, a trigger is detected that requests the establishment of a second session for the combination of the DNN and Single Network Slice Selection Assistance Information (S-NSSAI), the transmission of a second session establishment request message requesting the establishment of the second session to the first core network node is interrupted, depending on whether the combination of the DNN and the first S-NSSAI among the S-NSSAI is associated with the service of the UAS. The second session described above is different from the first session described above. method. (Appendix 2-4) A non-temporary computer-readable medium containing a program for causing a computer to perform a method in User Equipment (UE), The aforementioned method, Send a first session establishment request message to the first core network node that manages sessions, requesting the establishment of a first session for the Data Network Name (DNN) corresponding to the Uncrewed Aerial System (UAS) Service Supplier (USS). If, before receiving a response to the session establishment request message, a trigger is detected that requests the establishment of a second session for the combination of the DNN and Single Network Slice Selection Assistance Information (S-NSSAI), the transmission of a second session establishment request message requesting the establishment of the second session to the first core network node is interrupted, depending on whether the combination of the DNN and the first S-NSSAI among the S-NSSAI is associated with the service of the UAS. The second session described above is different from the first session described above. A non-temporary computer-readable medium. (Note 3-1) A third core network node that performs mobility management, Memory and At least one processor coupled to the memory, Equipped with, The at least one processor is configured to manage a UE context that includes information indicating that the User Equipment (UE) failed the authentication and authorization procedure (UUAA-MM procedure) for Uncrewed Aerial Vehicles (UAVs) in mobility management. The at least one processor is configured to receive a session establishment request message from the UE, which includes at least one Data Network Name (DNN) corresponding to the Uncrewed Aerial System (UAS) service and Single Network Slice Selection Assistance Information (S-NSSAI) corresponding to the UAS service. The at least one processor is configured to send a rejection response message to the session establishment request message to the UE based on information indicating that the UUAA-MM procedure has failed. The third core network node. (Appendix 3-2) The rejection response message includes a failure cause indicating that the rejection is based on the UE failing to perform the UUAA-MM procedure. The third core network node described in Appendix 3-1. (Appendix 3-3) The at least one processor is configured not to forward the session establishment request message to the first core network node that performs session management, based on information indicating that the UE has failed the UUAA-MM procedure. The third core network node as described in Appendix 3-1 or Appendix 3-2. (Appendix 3-4) User Equipment (UE), Memory and At least one processor coupled to the memory, Equipped with, The at least one processor is configured to send a session establishment request message to a third core network node that performs mobility management, which includes at least one Data Network Name (DNN) corresponding to the Uncrewed Aerial System (UAS) service and at least one Single Network Slice Selection Assistance Information (S-NSSAI) corresponding to the UAS service. The at least one processor is configured to receive a rejection response message for the session establishment request message from the third core network node. The rejection response message is transmitted from the third core network node to the UE in the UE context managed by the third core network node, in accordance with the information indicating that the UE failed the authentication and authorization procedure for Uncrewed Aerial Vehicles (UAVs) in mobility management (UUAA-MM procedure). UE. (Appendix 3-5) A method for a third core network node that performs mobility management, In mobility management, the authentication and authorization procedure (UUAA-MM procedure) for Uncrewed Aerial Vehicles (UAVs) involves managing the UE context, which includes information indicating that the User Equipment (UE) has failed. The UE receives a session establishment request message from the UE that includes at least one of the Data Network Name (DNN) corresponding to the Uncrewed Aerial System (UAS) service and Single Network Slice Selection Assistance Information (S-NSSAI) corresponding to the UAS service. The procedure includes sending a rejection response message to the session establishment request message to the UE based on information indicating that the UE has failed the UUAA-MM procedure. method. (Appendix 3-6) A method in User Equipment (UE), Send a session establishment request message to the third core network node performing mobility management, which includes at least one of the following: a Data Network Name (DNN) corresponding to the Uncrewed Aerial System (UAS) service, and Single Network Slice Selection Assistance Information (S-NSSAI) corresponding to the UAS service. The system includes receiving a rejection response message for the session establishment request message from the third core network node, The rejection response message is transmitted from the third core network node to the UE in the UE context managed by the third core network node, in accordance with the information indicating that the UE failed the authentication and authorization procedure for Uncrewed Aerial Vehicles (UAVs) in mobility management (UUAA-MM procedure). method. (Appendix 3-7) A non-temporary computer-readable medium containing a program for causing a computer to perform a method in a third core network node that performs mobility management, The aforementioned method, In mobility management, the authentication and authorization procedure (UUAA-MM procedure) for Uncrewed Aerial Vehicles (UAVs) involves managing the UE context, which includes information indicating that the User Equipment (UE) has failed. The UE receives a session establishment request message from the UE that includes at least one of the Data Network Name (DNN) corresponding to the Uncrewed Aerial System (UAS) service and Single Network Slice Selection Assistance Information (S-NSSAI) corresponding to the UAS service. The procedure includes sending a rejection response message to the session establishment request message to the UE based on information indicating that the UE has failed the UUAA-MM procedure. A non-temporary computer-readable medium. (Appendix 3-8) A non-temporary computer-readable medium containing a program for causing a computer to perform a method in User Equipment (UE), The aforementioned method, Send a session establishment request message to the third core network node performing mobility management, which includes at least one of the following: a Data Network Name (DNN) corresponding to the Uncrewed Aerial System (UAS) service, and Single Network Slice Selection Assistance Information (S-NSSAI) corresponding to the UAS service. The system includes receiving a rejection response message for the session establishment request message from the third core network node, The rejection response message is transmitted from the third core network node to the UE in the UE context managed by the third core network node, in accordance with the information indicating that the UE failed the authentication and authorization procedure for Uncrewed Aerial Vehicles (UAVs) in mobility management (UUAA-MM procedure). A non-temporary computer-readable medium. (Note 4-1) A third core network node that performs mobility management, Memory and At least one processor coupled to the memory, Equipped with, The at least one processor is configured to manage a UE context that includes information indicating that the User Equipment (UE) failed the authentication and authorization procedure (UUAA-MM procedure) for Uncrewed Aerial Vehicles (UAVs) in mobility management. The at least one processor is configured to receive a session establishment request message from the UE requesting the establishment of a first session, the session establishment request message includes at least one of a Data Network Name (DNN) corresponding to an Uncrewed Aerial System (UAS) service and Single Network Slice Selection Assistance Information (S-NSSAI) corresponding to a UAS service, The at least one processor is configured to send to a first core network node that manages sessions information indicating that the UE failed the UUAA-MM procedure and a call message for the session establishment service for the first session. The third core network node. (Appendix 4-2) The at least one processor is configured to send a rejection response message to the session establishment request message to the UE when it receives a rejection response message to the session establishment service call message from the first core network node. The rejection response message includes a failure cause indicating that the rejection is based on the UE failing to perform the UUAA-MM procedure. The third core network node described in Appendix 4-1. (Appendix 4-3) User Equipment (UE), Memory and At least one processor coupled to the memory, Equipped with, The at least one processor is configured to send a session establishment request message to a third core network node that performs mobility management, which requests the establishment of a first session, and the session establishment request message includes at least one of a Data Network Name (DNN) corresponding to the Uncrewed Aerial System (UAS) service and Single Network Slice Selection Assistance Information (S-NSSAI) corresponding to the UAS service. The at least one processor is configured to receive a rejection response message for the session establishment request message from the third core network node. The rejection response message includes a failure cause indicating that the rejection is based on the UE failing to perform the authentication and authorization procedure for Uncrewed Aerial Vehicles (UAVs) in mobility management (UUAA-MM procedure). UE. (Appendix 4-4) A method for a third core network node that performs mobility management, In mobility management, the authentication and authorization procedure (UUAA-MM procedure) for Uncrewed Aerial Vehicles (UAVs) involves managing the UE context, which includes information indicating that the User Equipment (UE) has failed. Receiving a session establishment request message from the UE requesting the establishment of a first session, The process includes sending information indicating that the UE failed the UUAA-MM procedure, and a call message for the session establishment service for the first session, to a first core network node that performs session management. The session establishment request message includes at least one of the following: Data Network Name (DNN) corresponding to the Uncrewed Aerial System (UAS) service, and Single Network Slice Selection Assistance Information (S-NSSAI) corresponding to the UAS service. method. (Appendix 4-5) A method in User Equipment (UE), Send a session establishment request message to the third core network node that manages mobility, requesting the establishment of the first session. The system includes receiving a rejection response message for the session establishment request message from the third core network node, The session establishment request message includes at least one of the following: Data Network Name (DNN) corresponding to the Uncrewed Aerial System (UAS) service, and Single Network Slice Selection Assistance Information (S-NSSAI) corresponding to the UAS service. The rejection response message includes a failure cause indicating that the rejection is based on the UE failing to perform the authentication and authorization procedure for Uncrewed Aerial Vehicles (UAVs) in mobility management (UUAA-MM procedure). method. (Appendix 4-6) A non-temporary computer-readable medium containing a program for causing a computer to perform a method in a third core network node that performs mobility management, The aforementioned method, In mobility management, the authentication and authorization procedure (UUAA-MM procedure) for Uncrewed Aerial Vehicles (UAVs) involves managing the UE context, which includes information indicating that the User Equipment (UE) has failed. Receiving a session establishment request message from the UE requesting the establishment of a first session, The process includes sending information indicating that the UE failed the UUAA-MM procedure, and a call message for the session establishment service for the first session, to a first core network node that performs session management. The session establishment request message includes at least one of the following: Data Network Name (DNN) corresponding to the Uncrewed Aerial System (UAS) service, and Single Network Slice Selection Assistance Information (S-NSSAI) corresponding to the UAS service. A non-temporary computer-readable medium. (Appendix 4-7) A non-temporary computer-readable medium containing a program for causing a computer to perform a method in User Equipment (UE), The aforementioned method, Send a session establishment request message to the third core network node that manages mobility, requesting the establishment of the first session. The system includes receiving a rejection response message for the session establishment request message from the third core network node, The session establishment request message includes at least one of the following: Data Network Name (DNN) corresponding to the Uncrewed Aerial System (UAS) service, and Single Network Slice Selection Assistance Information (S-NSSAI) corresponding to the UAS service. The rejection response message includes a failure cause indicating that the rejection is based on the UE failing to perform the authentication and authorization procedure for Uncrewed Aerial Vehicles (UAVs) in mobility management (UUAA-MM procedure). A non-temporary computer-readable medium. (Note 5-1) The first core network node that performs session management, Memory and At least one processor coupled to the memory, Equipped with, The at least one processor is configured to perform the authentication and authorization procedure for UAVs in session management (UUAA-SM procedure), associated with the Uncrewed Aerial System (UAS) Service Supplier (USS) Uncrewed Aerial Vehicle (UAV) ID assigned to the Uncrewed Aerial System (UAS) Service Supplier (USS). The at least one processor is configured to send a rejection message to the User Equipment (UE) if it receives a session establishment request message including the UAVID from the User Equipment (UE) during the execution of the UUAA-SM procedure. The rejection response message includes a failure cause indicating that the rejection is based on the fact that the UUAA-SM procedure is being executed against the UAVID. The first core network node. (Note 5-2) A method for performing session management on a first core network node, Perform the authentication and authorization procedure (UUAA-SM procedure) for UAVs in session management, associated with the Uncrewed Aerial System (UAS) Service Supplier (USS) Uncrewed Aerial Vehicle (UAV) ID assigned to the UAS. During the execution of the UUAA-SM procedure, if a session establishment request message including the UAVID is received from the User Equipment (UE), a rejection response message to the session establishment request message is sent to the UE. The rejection response message includes a failure cause indicating that the rejection is based on the fact that the UUAA-SM procedure is being executed against the UAVID. method. (Appendix 5-3) A non-temporary computer-readable medium containing a program for causing a computer to perform a method in a first core network node that performs session management, The aforementioned method, Perform the authentication and authorization procedure (UUAA-SM procedure) for UAVs in session management, associated with the Uncrewed Aerial System (UAS) Service Supplier (USS) Uncrewed Aerial Vehicle (UAV) ID assigned to the UAS. During the execution of the UUAA-SM procedure, if a session establishment request message including the UAVID is received from the User Equipment (UE), a rejection response message to the session establishment request message is sent to the UE. The rejection response message includes a failure cause indicating that the rejection is based on the fact that the UUAA-SM procedure is being executed against the UAVID. A non-temporary computer-readable medium.

[0145] This application claims priority based on Japanese Patent Application No. 2021-160148, filed on 29 September 2021, and incorporates all of its disclosures herein. [Explanation of Symbols]

[0146] 1 UE 2 AMF 3 SMF 4 AUSF 5 AN 6 UPF 7 DN 8 UDM 9 UAS-NF 10 NSSAAF 1403 Baseband Processor 1404 Application Processors 1406 memory 1407 modules 1502 Processors 1503 memory 1504 modules

Claims

1. It is a session management node, Means for receiving a session establishment request message from a user device via a mobility management node, which includes a combination of Single Network Slice Selection Assistance Information (S-NSSAI) and Data Network Name (DNN) that is dedicated to aviation services, and A means of initiating an authentication service operation for network nodes related to unmanned aerial systems, Means for receiving an authentication response from a network node relating to the unmanned aerial system, including the cause of failure due to the lack of a response from a service provision node relating to the unmanned aerial system within a predetermined time; Means for sending a session establishment rejection message including the cause of failure to the user device via the movement management node, A session management node equipped with the necessary components.

2. The session establishment request message includes the Uncrewed Aerial System (UAS) Service Supplier (USS) address (USS address), The means for initiating the activation is to activate the authentication service operation using the USS address. The session management node according to claim 1.

3. The session management node according to claim 1 or 2, wherein PEER NOT RESPONDING is set as the cause of failure.

4. A method for session management nodes, The system receives a session establishment request message from the user device via the mobility management node, which includes Single Network Slice Selection Assistance Information (S-NSSAI) and Data Network Name (DNN). The combination of S-NSSAI and DNN is dedicated to aviation services. To initiate an authentication service operation for network nodes related to unmanned aerial systems, Receiving an authentication response from the network node relating to the unmanned aerial system within a predetermined time, including the reason for failure due to the lack of response from the service provision node relating to the unmanned aerial system in the authentication service operation, A method comprising sending a session establishment rejection message, including the cause of the failure, to the user device via the movement management node.

5. User device, A means for sending a session establishment request message to a session management node via a movement management node, which includes Single Network Slice Selection Assistance Information (S-NSSAI), Data Network Name (DNN), and Uncrewed Aerial System (UAS) Service Supplier (USS) address, Means for receiving a session establishment rejection message, including the cause of failure, from the session management node via the aforementioned movement management node, Equipped with, The combination of S-NSSAI and DNN is dedicated to aviation services. The aforementioned session establishment request message is used to trigger an authentication service operation on the network node related to the unmanned aerial system. The cause of the failure is that, upon activation of the authentication service operation, the network node relating to the unmanned aerial system does not respond to the authentication service operation from the service provision node relating to the unmanned aerial system within a predetermined time, and the user device is received by the session management node as part of the authentication response, and further received by the user device from the session management node as part of the session establishment rejection message.

6. The session establishment request message includes the Uncrewed Aerial System (UAS) Service Supplier (USS) address (USS address), The aforementioned USS address is used to activate the authentication service operation. The user device according to claim 5.

7. The user device according to claim 5 or 6, wherein the cause of failure is set to PEER NOT RESPONDING.

8. A method for user equipment, Sending a session establishment request message to the session management node via the movement management node, including Single Network Slice Selection Assistance Information (S-NSSAI), Data Network Name (DNN), and Uncrewed Aerial System (UAS) Service Supplier (USS) address, This includes receiving a session establishment rejection message, including the cause of failure, from the session management node via the mobilization management node. The combination of S-NSSAI and DNN is dedicated to aviation services. The USS address included in the session establishment request message is used to initiate an authentication service operation on the network node related to the unmanned aerial system. The method is such that, upon activation of the authentication service operation, the network node relating to the unmanned aerial system does not respond to the authentication service operation from the service provision node relating to the unmanned aerial system within a predetermined time, and this is included in the authentication response and received by the session management node, and further, from the session management node, it is included in the session establishment rejection message and received by the user device.

Images