Wireless terminal and method for wireless terminal

Abstract

To provide a device that appropriately handles conflicts between UUAA procedures and other mobility management procedures or session management procedures.SOLUTION: In a cellular network configuration, an Access and Mobility Management Function (AMF) node initiates a UAV authentication and authorization (UUAA-MM) procedure, receives a DEREGISTRATION REQUEST message in a UE-initiated de-registration procedure from an Uncrewed Aerial Vehicle (UAV), aborts the UUAA-MM procedure in response to receiving the DEREGISTRATION REQUEST message, and performs the UE-initiated de-registration procedure when the DEREGISTRATION REQUEST message is received.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present disclosure relates to cellular networks, and more particularly to authentication and authorization of drone systems. [Background technology]

[0002] The 5G system (5GS) connects wireless terminals (user equipment (UE) or uncrewed aerial vehicles (UAV)) to a data network (DN). Hereinafter, the terms UE and UAV can be read interchangeably. 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., an exchange of PDUs between the UE and the DN). A PDU session is established between the 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 consists of a tunnel (N9 tunnel) within the 5G core network (5GC), a tunnel (N3 tunnel) between the 5GC and the access network (AN), and one or more radio bearers.

[0003] Non-Patent Document 2 and Non-Patent Document 3 specify a PDU session establishment procedure, a PDU session modification procedure, and a PDU session release procedure. 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 update 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 also supports network slicing (see, for example, Non-Patent Documents 1 to 3, especially Section 5.15 of Non-Patent Document 1). Network slicing uses Network Function Virtualization (NFV) and software-defined networking (SDN) technologies to create multiple virtualized logical networks on a physical network. Each virtualized logical network is called a network slice. A network slice provides specific network capabilities and 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 a Next Generation Radio Access Network (NG-RAN) and a Non-3GPP InterWorking Function (N3IWF)) to form one network slice.

[0005] A network slice is 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 in terms of features and services. SD is optional information that complements SST to distinguish between multiple network slices of the same Slice / Service type.

[0006] The S-NSSAI can have standard 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. A non-standard value in the S-NSSAI identifies a network slice within a specific Public Land Mobile Network (PLMN). That is, non-standard SST values are PLMN-specific and are associated with the PLMN ID of the PLMN that assigned them. Each S-NSSAI assists the network in selecting a particular NSI. The same NSI may be selected via 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 the S-NSSAI and the Mapped S-NSSAI. The S-NSSAI identifies the network slice provided by the Public Land Mobile Network (PLMN) to which the UE is registered. The Mapped S-NSSAI may be the S-NSSAI of the Home PLMN (HPLMN) that is mapped (associated with or corresponds to) the S-NSSAI that identifies the network slice of the roaming network when the UE is roaming, and may further be the S-NSSAI included in the UE user's subscription information. Hereinafter, in this specification, the S-NSSAI and the Mapped S-NSSAI may be collectively referred to simply as the 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 included in one NSSAI. There are several types of NSSAI, known as Configured NSSAI, Requested NSSAI, Allowed NSSAI, Rejected NSSAI, and Pending NSSAI.

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

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

[0011] The 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 current Registration Area of the Serving PLMN. The Allowed NSSAI can include S-NSSAI and Mapped S-NSSAI. The Allowed NSSAI is determined by the AMF of the Serving PLMN, for example, during the registration procedure. Therefore, the Allowed NSSAI is signaled to the UE by the network (i.e., AMF) and stored in the non-volatile memory of the AMF and the UE.

[0012] The Rejected NSSAI includes one or more S-NSSAIs rejected by the current (or serving) PLMN. Note that when the UE is roaming, the Rejected NSSAI includes the S-NSSAI of the Home PLMN (HPLMN). The Rejected NSSAI is sometimes called the rejected S-NSSAIs. The S-NSSAI is rejected by the entire current PLMN or the current registration area. If the AMF rejects one or more S-NSSAIs included in the Requested NSSAI, for example, during the UE registration procedure, 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 the AMF and the UE.

[0013] The Extended Rejected NSSAI includes one or more S-NSSAIs that have been rejected by the current (or serving) PLMN. The Extended Rejected NSSAI may include an S-NSSAI and a Mapped S-NSSAI.

[0014] A Pending NSSAI indicates one or more S-NSSAIs for which Network Slice-Specific Authentication and Authorization (NSSAA) is pending. The Pending NSSAI may include an S-NSSAI and a Mapped S-NSSAI. The Serving PLMN must perform an NSSAA for the S-NSSAIs of the HPLMN for which an NSSAA is imposed based on subscription information. To perform an 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, the AMF determines the Allowed NSSAIs as described above during the UE registration procedure, but does not include the S-NSSAIs for which an NSSAA is imposed in the Allowed NSSAIs, but instead includes them in the Pending NSSAIs. The Pending NSSAI is signaled to the UE by the network (i.e., AMF) and stored in the respective (non-volatile) memories of 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 be, but is not limited to, referred to as a Mobility Management (MM) context. The UE context may include one or more of the above-mentioned Allowed NSSAI, Rejected NSSAI, Extended Rejected NSSAI, and Pending NSSAI. Meanwhile, 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 in the UE (Mobile Equipment (ME) excluding the Universal Subscriber Identity Module (USIM)). The memory or memory area where the UE NSSAI configuration is stored is called NSSAI storage.

[0016] Section 5.15.10 of Non-Patent Document 1 and Section 4.2.9 of Non-Patent Document 2 specify Network Slice-Specific Authentication and Authorization (NSSAA). More specifically, Section 5.15.10 of Non-Patent Document 1 and Section 4.2.9.2 of Non-Patent Document 2 describe NSSAA. Section 5.15.10 of Non-Patent Document 1 and Section 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). Section 5.15.10 of Non-Patent Document 1 and Section 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 specifies 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 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 that utilize mobile communications (see, for example, Non-Patent Document 4). The 5G architecture enhancements specify the following enhancement: a UAV authentication and authorization function by a USS (UAS Service Supplier) in mobility management. This UAV authentication and authorization is called UUAA-MM. The 5G architecture enhancements also specify the following enhancement: a UAV authentication and authorization function by a 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 enhancement: a C2 communication authorization function to realize C2 communication.

[0019] UAVs must be certified and authorized before they can use the UAS (Uncrewed Aerial System) Service, which refers to connectivity for communication with USS, C2 communication, remote identification of UAVs, and location and tracking of UAVs, providing safe and efficient airspace utilization services.

[0020] The UE performs either the UUAA-MM procedure or the UUAA-SM procedure to obtain the authentication and authorization.

[0021] UUAA-MM is executed as a trigger of the registration procedure based on operator policy. The 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 ID. The CAA-Level-UAV ID is issued by, for example, a USS that manages drone flight operations and is used to identify the UAV.

[0022] If UUAA-MM is not executed, UUAA-SM is executed in response to the PDU session establishment procedure (PDU session establishment and PDU session modification). The SMF executes the UUAA-SM procedure if the DNN and / or S-NSSAI of the PDU session establishment is for the UAS Service and the CAA-Level UAV ID is included in the PDU session establishment procedure.

[0023] A UE must be authorized for C2 (Command and Control) communications if it is capable of operating based on C2 communications. C2 communications refers to the user plane link used to transmit messages containing UAV operation command and control information from a UAV controller (UAV-C) or UAS Traffic Management (UTM) to a UAV, and to report telemetry data from a UAV to the UAV controller or UTM. The UAV controller of a UAS allows a drone pilot to control the UAV. UTM refers to a system that supports flying UAVs to share airspace safely and efficiently with other users.

[0024] C2 communication authorization may be performed using the UUAA-SM procedure described above, or after UAV authentication and authorization. If performed after UAV authentication and authorization, the UE performs a PDU session update procedure (PDU session modification) 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 updated is targeted for UAS Service and the CAA-Level UAV ID is included in the PDU session update procedure.

[0025] In the above-mentioned UUAA-MM, UUAA-SM, and C2 communication authorization, after initiating each procedure, authentication and / or authorization information is exchanged multiple times between the USS and the UE, and the authentication and authorization results are notified to the UE. In the UUAA-MM procedure, the AMF notifies the UE of the authentication and authorization results in the DL NAS TRANSPORT message sent to the UE. In the UUAA-SM procedure, the SMF notifies the UE of the authentication and authorization results in the PDU session accept message sent to the UE. [Prior art documents] [Non-patent literature]

[0026] [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)”, June 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)”, June 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 Summary of the Invention [Problem to be solved by the invention]

[0027] The inventors have studied authentication and re-authorization procedures for UAS services and found various problems. For example, it is unclear how a UE or a core network node should handle a collision between a UUAA procedure and another mobility management procedure or session management procedure. Therefore, one of the objectives to be achieved by the embodiments disclosed herein is to provide an apparatus, method, and program that can appropriately handle a collision between a UUAA procedure and another mobility management procedure or session management procedure. It should be noted that this objective is merely one of multiple objectives to be achieved by the multiple embodiments disclosed herein. Other objectives or problems and novel features will become apparent from the description of this specification or the accompanying drawings. [Means for solving the problem]

[0028] In a first aspect, an Access and Mobility Management Function (AMF) node comprises at least one memory and at least one processor coupled to the at least one memory, wherein the at least one processor is configured to initiate a UAV Authentication and Authorization (UUAA-MM) procedure, receive a DEREGISTRATION REQUEST message in a UE-initiated de-registration procedure from an Uncrewed Aerial Vehicle (UAV), and, in response to receiving the DEREGISTRATION REQUEST message, abort the UUAA-MM procedure and, if the DEREGISTRATION REQUEST message is received, perform the UE-initiated de-registration procedure.

[0029] In a second aspect, a method in an Access and Mobility Management Function (AMF) node initiates a UAV Authentication and Authorization (UUAA-MM) procedure, receives a DEREGISTRATION REQUEST message in a UE-initiated de-registration procedure from an Uncrewed Aerial Vehicle (UAV), aborts the UUAA-MM procedure in response to receiving the DEREGISTRATION REQUEST message, and performs the UE-initiated de-registration procedure if the DEREGISTRATION REQUEST message is received.

[0030] In a third aspect, a non-transitory computer-readable medium is a non-transitory computer-readable medium storing a program for causing a computer to perform the method according to the second aspect above.

[0031] In a fourth aspect, an Uncrewed Aerial Vehicle (UAV) comprises at least one memory and at least one processor coupled to the at least one memory, wherein the at least one processor is configured to initiate a UE-initiated de-registration procedure, receive a DL NAS TRANSPORT message in a UUAA-MM procedure from an Access and Mobility Management Function (AMF) node, ignore the received DL NAS TRANSPORT message, and perform the UE-initiated de-registration procedure if the DL NAS TRANSPORT message is received.

[0032] In a fifth aspect, a Session Management Function (SMF) node comprises at least one memory and at least one processor coupled to the at least one memory, wherein the at least one processor is configured to initiate a UAV Authentication and Authorization in Session Management procedure (UUAA-SM procedure), receive a PDU SESSION RELEASE REQUEST message for a PDU session providing a connection with a UAS NF9 in a UE-requested PDU session release procedure, and, in response to receiving the PDU SESSION RELEASE REQUEST message, abort the UUAA-SM procedure and, if the PDU SESSION RELEASE REQUEST message is received, perform the UE-requested PDU session release procedure.

[0033] In a sixth aspect, a Session Management Function (SMF) node comprises at least one memory and at least one processor coupled to the at least one memory, wherein the at least one processor is configured to initiate a C2 communication authorization procedure (Authorization for C2 procedure) or a UAV authentication and authorization procedure (UUAA-SM procedure), receive a PDU SESSION RELEASE REQUEST message in a UE-requested PDU session release procedure, and, in response to receiving the PDU SESSION RELEASE REQUEST message, abort the C2 communication authorization or the UUAA-SM procedure, and perform the UE-requested PDU session release procedure when the PDU SESSION RELEASE REQUEST message is received.

[0034] In a seventh aspect, an Uncrewed Aerial Vehicle (UAV) comprises at least one memory and at least one processor coupled to the at least one memory, wherein the at least one processor is configured to initiate a UE-requested PDU session release procedure, receive an authentication message in a UUAA-SM procedure, ignore the received authentication message, and perform the UE-requested PDU session release procedure if the authentication message is received.

[0035] In an eighth aspect, an Uncrewed Aerial Vehicle (UAV) includes at least one memory and at least one processor coupled to the at least one memory, wherein the at least one processor is configured to initiate a UE-requested PDU session release procedure, receive an authentication message in a C2 communication authorization procedure (Authorization for C2 procedure) or a UAV authentication and authorization procedure (UUAA-SM procedure), ignore the received authentication message, and perform the UE-requested PDU session release procedure if the authentication message is received.

[0036] In a ninth aspect, an Uncrewed Aerial Vehicle (UAV) comprises at least one memory and at least one processor coupled to the at least one memory, wherein the at least one processor is configured to receive, from a network, a PDU Session Modification Command message including information indicating that a C2 communication authorization procedure (Service-level authentication and authorization procedure) is being performed, and to transmit, to the network, a PDU Session Modification Command Ack or a PDU SESSION MODIFICATION COMPLETE message including information indicating that the Service-level authentication and authorization procedure (C2 communication authorization procedure) is being performed. [Effects of the Invention]

[0037] According to the above-described aspects, it is possible to provide an apparatus, a method, and a program that can appropriately handle a conflict between a UUAA procedure and another mobility management procedure or session management procedure. [Brief explanation of the drawings]

[0038] [Figure 1] FIG. 1 is a diagram illustrating an example of the configuration of a cellular network according to an embodiment. [Figure 2] 10 is a flowchart illustrating an example of an operation of an AMF according to an embodiment. [Figure 3] FIG. 10 is a sequence diagram showing an example of the operation of the UE, AMF, and UAS NF according to the embodiment. [Figure 4] 10 is a flowchart illustrating an example of an operation of a UE according to the embodiment. [Figure 5] A sequence diagram showing an example of the operation of a UE and an AMF according to the embodiment. [Figure 6] 10 is a flowchart showing an example of the operation of the SMF according to the embodiment. [Figure 7] A sequence diagram showing an example of the operation of the UE, AMF, SMF, and UAS NF according to the embodiment. [Figure 8] 10 is a flowchart showing an example of the operation of the SMF according to the embodiment. [Figure 9] A sequence diagram showing an example of the operation of the UE, AMF, SMF, and UAS NF according to the embodiment. [Figure 10] 10 is a flowchart illustrating an example of an operation of a UE according to the embodiment. [Figure 11] FIG. 10 is a sequence diagram showing an example of the operation of the UE and AMF according to the embodiment. [Figure 12] 10 is a flowchart illustrating an example of an operation of a UE according to the embodiment. [Figure 13] FIG. 10 is a sequence diagram showing an example of the operation of the UE and AMF according to the embodiment. [Figure 14] A sequence diagram showing an example of the operation of the UE, AMF and SMF according to the embodiment. [Figure 15] FIG. 2 is a block diagram illustrating an example of the configuration of a UE according to the embodiment. [Figure 16]A block diagram showing an example configuration of an AMF, an SMF, and an UAS-NF according to an embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0039] Hereinafter, specific embodiments will be described in detail with reference to the drawings. In each drawing, the same or corresponding elements are designated by the same reference numerals, and for clarity of explanation, duplicate explanations will be omitted as necessary.

[0040] The multiple embodiments described below can be implemented independently or in appropriate combination. These multiple embodiments have different novel features. Therefore, these multiple embodiments contribute to solving different purposes or problems and to achieving different effects.

[0041] The following embodiments are described primarily for the 3GPP fifth generation mobile communication system (5G system (5GS)). However, these embodiments may also be applied to other cellular communication systems that support network slicing similar to 5GS.

[0042] In particular, Table 1 shows an example of how to replace terms when applying the following embodiments to the 3GPP fourth generation mobile communication system (Evolved Packet System (EPS)).

[0043] [Table 1]

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

[0045] The cellular network shown in Figure 1 may be provided by a Mobile Network Operator (MNO), or 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 an NPN linked to an MNO network referred to as a Public network integrated NPN.

[0046] A wireless terminal (e.g., UE or UAV) 1 uses a 5G connectivity service and communicates with a data network (DN) 7. More specifically, the UE 1 is connected to an access network (i.e., 5G Access Network (5GAN)) 5 and communicates with the data network (DN) 7 via a User Plane Function (UPF) 6 in a core network (i.e., 5G core network (5GC)). Hereinafter, the term UE can be replaced with the term UAV.

[0047] The AN5 includes a Next Generation Radio Access Network (NG-RAN), a non-3GPP AN, or both. The non-3GPP AN may be a network handling wireless LAN (WiFi) communications, or a network handling wired communications, referred to as a Wireline 5G Access Network (W-5GAN). The UPF6 may include multiple interconnected UPFs.

[0048] In the 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. A PDU session is used to provide PDU connectivity services (i.e., exchange of PDUs between UE1 and DN7). UE1 establishes one or more PDU sessions between UE1 and a UPF6 (i.e., PDU session anchor) to which DN7 is connected. From a data transfer perspective, a PDU session consists of a tunnel within 5GC (N9 tunnel), a tunnel between 5GC and AN5 (N3 tunnel), and one or more radio bearers. UE1 may establish multiple PDU sessions with multiple UPFs (PDU session anchors)6 to access multiple DNs7 concurrently.

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

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

[0051] AUSF4 is one of the network functions within the 5GC Control Plane. AUSF4 provides NF services to NF consumers (e.g., AMF2, UDM8) over the service-based interface (i.e., Nausf interface). 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 (e.g., 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, a 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 the AAA server via AUSF4.

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

[0053] The UAS NF9 is one of the network functions within the 5GC Control Plane. It is supported by the NEF (Network Exposure Function) or SCEF (Service Capability Exposure Function) + NEF and is used for external exposure of services to the USS. The SCEF + NEF node is associated with the UE for service capability exposure if the UE supports mobility between EPS and 5GS. The UAS NF9 uses the external exposure provided by the existing NEF / SCEF to control UAV authentication / authorization, UAV flight authorization, UAV-UAVC pairing authorization and their associated revocation, location reporting, and QoS / traffic filtering for C2 communications. The UAS NF9 may be implemented and deployed in the form of a dedicated NEF that implements only the UAS NF functions. The UAS NF may also be referred to as a UAS-NF.

[0054] To support re-authentication requests by the USS, the UAS NF9 stores and maintains information on 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. The SMF / PGW-C is a core network node used for PDN connectivity when interworking between 5GS and EPS is supported. Furthermore, the UAS NF9 stores and maintains the results of the UUAA-MM procedure and the UUAA-SM procedure.

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

[0056] For convenience of explanation, only representative NFs are shown in the configuration example of Fig. 1. The cellular network according to this embodiment may include other NFs not shown in Fig. 1, such as a Network Slice Selection Function (NSSF), a Policy Control Function (PCF), an Application Function (AF), an NEF, and a Network Repository Function (NRF).

[0057] The inventors have investigated the authentication and re-authorization procedures for UAS services and found various issues. For example, if UE1 performs a de-registration procedure while the network is performing a UUAA-MM procedure, it is unclear how AMF2 handles the DEREGISTRATION REQUEST message from UE1. In this case, the UUAA-MM procedure and the UE-initiated de-registration procedure may conflict in the network, causing one or both procedures to fail.

[0058] This embodiment provides a solution for appropriately handling the UUAA-MM procedure and the UE-initiated de-registration procedure when they conflict in the network.

[0059] FIG. 2 is a flowchart showing an example of the operation of the AMF 2 according to this embodiment.

[0060] In step 201, the AMF2 initiates the UAV authentication and authorization procedure in mobility management (UUAA-MM procedure). The AMF2 may initiate the UAV authentication and authorization procedure by sending an Nnef_Authentication_authenticate request message including a GPSI (Generic Public Subscription Identifier) and a CAA-Level UAV ID to the UAS NF9. In the UUAA-MM procedure, the AMF2 invokes the Nnef_Authentication_authenticate service operation. The Nnef_Authentication_authenticate service operation may include a USS address (e.g., a Fully Qualified Domain Name (FQDN)) and a UUAA Aviation Payload. The UAS NF9 identifies the USS address based on the CAA-Level UAV ID or the USS address specified by the UE1. The AMF2 may include user location information (e.g., a cell ID) in the Nnef_Authentication_authenticate service operation.

[0061] In step 202, AMF 2 receives a DEREGISTRATION REQUEST message in a UE-initiated de-registration procedure initiated by UE 1. Access type information ("3GPP" and / or "non 3GPP") specifying the access to be de-registrated may be set in the DEREGISTRATION REQUEST message.

[0062] In step 203, the AMF2 aborts the UUAA-MM procedure and progresses the UE-initiated de-registration procedure. The AMF2 aborting the UUAA-MM procedure may mean that the AMF2 and a related network node (e.g., UAS NF9) perform processing related to the abortion of the UUAA-MM procedure before performing the UE-initiated de-registration procedure. As another example, the AMF2 may check whether the access type information included in the DEREGISTRATION REQUEST message matches the access type for which the UUAA-MM procedure is being performed. If the access type information included in the DEREGISTRATION REQUEST message matches the access type for which the UUAA-MM procedure is being performed as a result of the check, the AMF2 may abort the UUAA-MM procedure and progress the UE-initiated de-registration procedure. Specifically, if the access type information included in the DEREGISTRATION REQUEST message is set to "3GPP access and non-3GPP access" and the access type for performing the UUAA-MM procedure is "3GPP access" and / or "non-3GPP access," the AMF2 may abort the UUAA-MM procedure and progress UE-initiated de-registration. If the access type information included in the DEREGISTRATION REQUEST message does not match the access type for performing the UUAA-MM procedure as a result of checking, the AMF2 may progress both the UUAA-MM procedure and the UE-initiated de-registration procedure. Specifically, if the access type information included in the DEREGISTRATION REQUEST message is set to "3GPP access" and the access type for performing the UUAA-MM procedure is "non-3GPP access," the AMF2 may progress both the UUAA-MM procedure and the UE-initiated de-registration procedure.If the access type information included in the DEREGISTRATION REQUEST message is set to "non 3GPP access" and the access type performing the UUAA-MM procedure is "3GPP access", AMF2 may progress both the UUAA-MM procedure and the UE-initiated de-registration procedure.

[0063] According to the operation shown in Figure 2, if the UUAA-MM procedure and the UE-initiated de-registration procedure conflict in the network, the AMF2 aborts the UUAA-MM procedure and performs the UE-initiated de-registration procedure. If the UUAA-MM procedure and the UE-initiated de-registration procedure conflict in the network, the AMF2 may prioritize the performance of the UE-initiated de-registration procedure by aborting the UUAA-MM procedure. This allows the network to appropriately handle both procedures even if they conflict in the network.

[0064] FIG. 3 shows an example of a UE-initiated de-registration procedure during a UUAA-MM procedure.

[0065] In step 301, the AMF2 initiates the UAV authentication and authorization procedure in mobility management (UUAA-MM procedure). The AMF2 may initiate the UAV authentication and authorization procedure by sending an Nnef_Authentication_authenticate request message including the GPSI and CAA-Level UAV ID to the UAS NF9. In the UUAA-MM procedure, the AMF2 invokes the Nnef_Authentication_authenticate service operation. The Nnef_Authentication_authenticate service operation may include a USS address (e.g., FQDN) and a UUAA Aviation Payload. The UAS NF9 identifies the USS address based on the CAA-Level UAV ID or the USS address specified by the UE1. The AMF2 may include user location information (e.g., cell ID) in the Nnef_Authentication_authenticate service operation.

[0066] In step 302, AMF 2 receives a DEREGISTRATION REQUEST message in a UE-initiated de-registration procedure initiated by UE 1 from UE 1. Access type information ("3GPP" and / or "non 3GPP") specifying the access to be de-registrated may be set in the DEREGISTRATION REQUEST message.

[0067] In step 303, AMF2 aborts the UUAA-MM procedure in response to the DEREGISTRATION REQUEST message received from UE1. As an example, AMF2 may detect a registration status change event of UE1 based on the initiation of the UE-initiated de-registration procedure and notify UAS NF9 that UE1's registration status has changed to "DEREGISTERED". The event notification may be referred to as Namf_EventExposure_Notify. The event notification may invoke a Namf_EventExposure_Notify service operation. UAS NF9 aborts the UUAA-MM procedure based on the event notification. In order to receive the event notification from AMF2, UAS NF9 subscribes to the AMF service before receiving the event notification. The subscription to the AMF service may be referred to as Namf_EventExposure_Subscribe or a Namf_EventExposure_Subscribe service operation. The UAS NF9 may invoke the Namf_EventExposure_Subscribe service operation to subscribe to the AMF service in response to receiving the Nnef_Authentication_authenticate request message in step 301. The UAS NF9 may invoke the Namf_EventExposure_Subscribe service operation to subscribe to the AMF service after the UUAA-MM procedure is successful. If the UUAA-MM procedure is successful, the UAS NF9 saves the UUAA context of the UAV indicating that authentication and authorization were successful, and sends an Nnef_Authentication_authenticate response to the AMF2 that includes information indicating that authentication and authorization were successful.Note that when invoking the Namf_EventExposure_Subscribe service operation after the UUAA-MM procedure is successful, the UAS NF9 may delete the stored UUAA context of the UAV indicating successful authentication and authorization, in addition to aborting the UUAA-MM procedure described above. As another example, in response to receiving a DEREGISTRATION REQUEST message from UE1, the AMF2 may send a request message including information indicating EAP failure to the UAS NF9 and invoke the Nmf_Authentication_authenticate service operation. The UAS NF9 aborts the UUAA-MM procedure in response to the invocation of this service operation. At this time, if the UAS NF9 has already stored a UUAA context of the UAV indicating successful authentication and authorization, it may delete the context. As another example, the AMF2 may check whether the access type information included in the DEREGISTRATION REQUEST message matches the access type for which the UUAA-MM procedure is being executed. If the access type information included in the DEREGISTRATION REQUEST message matches the access type for which the UUAA-MM procedure is being performed as a result of the check, the AMF2 may abort the UUAA-MM procedure and proceed with the UE-initiated de-registration procedure. If the access type information included in the DEREGISTRATION REQUEST message does not match the access type for which the UUAA-MM procedure is being performed as a result of the check, the AMF2 may proceed with both the UUAA-MM procedure and the UE-initiated de-registration procedure.

[0068] In step 304, AMF2 progresses the UE-initiated de-registration procedure after aborting the UUAA-MM procedure in step 303. AMF2 may simultaneously perform the operation of aborting the UUAA-MM procedure in step 303 and the progress of the UE-initiated de-registration procedure in response to the DEREGISTRATION REQUEST message received from UE1 in step 302. The UE-initiated de-registration procedure is similar to the existing UE-initiated de-registration procedure. The existing UE-initiated de-registration procedure is specified in Figure 4.2.2.3.2-1 of Non-Patent Document 2.

[0069] According to the operation shown in Figure 3, if the UUAA-MM procedure and the UE-initiated de-registration procedure conflict in the network, the AMF2 aborts the UUAA-MM procedure and performs the UE-initiated de-registration procedure. If the UUAA-MM procedure and the UE-initiated de-registration procedure conflict in the network, the AMF2 may prioritize the performance of the UE-initiated de-registration procedure by aborting the UUAA-MM procedure. This allows the network to appropriately handle both procedures even if they conflict in the network.

[0070] As a modification of the first embodiment, instead of step 302, AMF2 may receive Nudm_UECM_DeregistrationNotification from UDM8. In this case, AMF2 aborts the UUAA-MM procedure and progresses the network-initiated de-registration procedure initiated by UDM8. The specific operation performed by AMF9 with respect to UAS NF9 may be the same as the operation when receiving a DEREGISTRATION REQUEST message from UE1 (i.e., the operation described in step 303). In this case, AMF2 progresses the network-initiated de-registration procedure initiated by UDM8 instead of step 304. The network-initiated de-registration procedure may be performed as defined in Figure 4.2.2.3.3-1 of Non-Patent Document 2.

[0071] According to a modification of the first embodiment, when a conflict occurs between the UUAA-MM procedure and a UDM8-initiated network-initiated de-registration procedure in the network, the AMF2 aborts the UUAA-MM procedure and performs the UDM8-initiated network-initiated de-registration procedure. When a conflict occurs between the UUAA-MM procedure and a UDM8-initiated network-initiated de-registration procedure in the network, the AMF2 may prioritize the performance of the UDM8-initiated network-initiated de-registration procedure by aborting the UUAA-MM procedure. This allows the network to appropriately handle both procedures even when a conflict occurs between the UUAA-MM procedure and a UDM8-initiated network-initiated de-registration procedure in the network.

[0072] <Second embodiment> The inventors have investigated authentication and re-authorization procedures for UAS services and found various issues. For example, if the network performs a UUAA-MM procedure while the UE is performing a UE-initiated de-registration procedure, it is unclear how the UE handles a DL NAS TRANSPORT message in the UUAA-MM procedure from the network. In this case, the UE-initiated de-registration procedure and the UUAA-MM procedure may collide at the UE, causing one or both procedures to fail.

[0073] This embodiment provides a solution for appropriately handling the UUAA-MM procedure and the UE-initiated de-registration procedure when they conflict with each other in the UE.

[0074] An example of the configuration of the cellular network according to this embodiment may be the same as the example shown in FIG.

[0075] FIG. 4 is a flowchart showing an example of the operation of UE 1 according to this embodiment.

[0076] In step 401, UE1 initiates a UE-initiated de-registration procedure. UE1 sends a DEREGISTRATION REQUEST message in the UE-initiated de-registration procedure to AMF2. Access type information ("3GPP" and / or "non 3GPP") specifying the access to be de-registrated may be set in the DEREGISTRATION REQUEST message.

[0077] In step 402, UE 1 receives a DL NAS TRANSPORT message in a UUAA-MM procedure from AMF 2. The DL NAS TRANSPORT message may include a service-level authentication and authorization (Service-level-AA) container information element (IE) with an authentication message set.

[0078] In step 403, UE1 ignores the DL NAS TRANSPORT message in the UUAA-MM procedure and proceeds with the UE-initiated de-registration procedure. UE1 ignoring the DL NAS TRANSPORT message may mean that UE1 does not perform a further UUAA-MM procedure in response to receiving the DL NAS TRANSPORT message. UE1 ignoring the DL NAS TRANSPORT message may mean that UE1 suspends or temporarily does not perform a UUAA-MM procedure in response to receiving the DL NAS TRANSPORT message. As another example, UE1 may check whether the access type information included in the DEREGISTRATION REQUEST message matches the access type for which the UUAA-MM procedure is being performed. If the access type information included in the DEREGISTRATION REQUEST message matches the access type for which the UUAA-MM procedure is being performed as a result of the check, UE1 may ignore the DL NAS TRANSPORT message in the UUAA-MM procedure and proceed with the UE-initiated de-registration procedure. Specifically, if the access type information included in the DEREGISTRATION REQUEST message is set to "3GPP access and non-3GPP access" and the access type for which the UUAA-MM procedure is being performed is "3GPP access" and / or "non-3GPP access," UE1 may ignore the DL NAS TRANSPORT message in the UUAA-MM procedure and proceed with the UE-initiated de-registration procedure. If the access type information included in the DEREGISTRATION REQUEST message does not match the access type for which the UUAA-MM procedure is being performed as a result of the check, UE1 may proceed with both the UUAA-MM procedure and the UE-initiated de-registration procedure.Specifically, UE1 may perform both the UUAA-MM procedure and the UE-initiated de-registration procedure if the access type information included in the DEREGISTRATION REQUEST message is set to "3GPP access" and the access type used to perform the UUAA-MM procedure is "non-3GPP access." AMF2 may perform both the UUAA-MM procedure and the UE-initiated de-registration procedure if the access type information included in the DEREGISTRATION REQUEST message is set to "non-3GPP access" and the access type used to perform the UUAA-MM procedure is "3GPP access."

[0079] According to the operation shown in Figure 4, if the UUAA-MM procedure and the UE-initiated de-registration procedure conflict at UE1, UE1 ignores the UUAA-MM procedure and performs the UE-initiated de-registration procedure. If the UUAA-MM procedure and the UE-initiated de-registration procedure conflict in the network, UE1 may ignore the UUAA-MM procedure and prioritize performance of the UE-initiated de-registration procedure. This allows UE1 to handle both procedures appropriately even if the UUAA-MM procedure and the UE-initiated de-registration procedure conflict at UE1.

[0080] FIG. 5 shows an example of a UE-initiated de-registration procedure during a UUAA-MM procedure.

[0081] In step 501, UE 1 initiates a UE-initiated de-registration procedure. UE 1 may initiate the UE-initiated de-registration procedure by sending a DEREGISTRATION REQUEST message to AMF 2. The DEREGISTRATION REQUEST message may include access type information ("3GPP" and / or "non 3GPP") specifying the access to be de-registrated.

[0082] In step 502, UE1 receives a DL NAS TRANSPORT message in the UUAA-MM procedure from AMF2. Specifically, UE1 receives a DL NAS TRANSPORT message including a Service-level-AA container IE with an authentication message set.

[0083] In step 503, UE1 ignores the DL NAS TRANSPORT message in the UUAA-MM procedure received from AMF2 and proceeds with the UE-initiated de-registration procedure. As another example, UE1 may check whether the access type information included in the DEREGISTRATION REQUEST message matches the access type for which the UUAA-MM procedure is being performed. If the check shows that the access type information included in the DEREGISTRATION REQUEST message matches the access type for which the UUAA-MM procedure is being performed, UE1 may ignore the DL NAS TRANSPORT message in the UUAA-MM procedure and proceed with the UE-initiated de-registration procedure. If the check shows that the access type information included in the DEREGISTRATION REQUEST message does not match the access type for which the UUAA-MM procedure is being performed, UE1 may proceed with both the UUAA-MM procedure and the UE-initiated de-registration procedure.

[0084] According to the operation shown in Figure 5, if the UUAA-MM procedure and the UE-initiated de-registration procedure conflict at UE1, UE1 ignores the UUAA-MM procedure and performs the UE-initiated de-registration procedure. If the UUAA-MM procedure and the UE-initiated de-registration procedure conflict in the network, UE1 may ignore the UUAA-MM procedure and prioritize performance of the UE-initiated de-registration procedure. This allows UE1 to handle both procedures appropriately even if the UUAA-MM procedure and the UE-initiated de-registration procedure conflict at UE1.

[0085] <Third embodiment> The inventors have investigated the authentication and re-authorization procedures for UAS services and found various issues. For example, if the UE performs a PDU session release procedure while the network is performing a UUAA-SM procedure, it is unclear how the SMF handles the PDU SESSION RELEASE REQUEST message from the UE. In this case, the UUAA-SM procedure and the UE-requested PDU session release procedure may collide in the network, causing one or both procedures to fail.

[0086] This embodiment provides a solution for appropriately handling a collision between a UE-requested PDU session release procedure and a procedure for UAV authentication and authorization (UUAA-SM procedure) in the network. This embodiment also provides a solution for appropriately handling a collision between a UE-requested PDU session release procedure and a procedure for UAV re-authentication and re-authorization (UUAA-SM procedure) in the network. Therefore, in the third embodiment, the procedure for UAV authentication and authorization (UUAA-SM procedure) can be replaced with the procedure for UAV re-authentication and re-authorization (UUAA-SM procedure).

[0087] An example of the configuration of the cellular network according to this embodiment may be the same as the example shown in FIG.

[0088] FIG. 6 is a flowchart showing an example of the operation of the SMF 3 according to this embodiment. In step 601, the SMF 3 initiates the UAV authentication and authorization procedure (UUAA-SM procedure) in session management. The UUAA-SM procedure may be initiated in response to receiving an authentication and authorization request (Nnef_Auth_Notification notify) message from the UAS_NF 9. In the UUAA-SM procedure, the SMF 3 invokes the Nnef_Authentication_Authenticate service operation.

[0089] In step 602, the SMF 3 receives a PDU SESSION RELEASE REQUEST message for a PDU session providing a connection with the UAS NF 9 from the UE 1 via the AMF 2. The PDU SESSION RELEASE REQUEST message is a message in a UE-requested PDU session release procedure.

[0090] In step 603, the SMF 3 aborts the UUAA-SM procedure and performs a UE-requested PDU session release procedure. The SMF 3 aborting the UUAA-SM procedure may mean that the SMF 3 and related network nodes (e.g., UAS NF9) perform processing related to the abortion of the UUAA-SM procedure prior to performing the UE-initiated de-registration procedure. As another example, the SMF 3 may abort the UUAA-SM procedure and perform a UE-requested PDU session release procedure if the PDU session specified in the PDU SESSION RELEASE REQUEST message is the PDU session specified in the UUAA-SM procedure.

[0091] According to the operation shown in Figure 6, if the UE-requested PDU session release procedure and the UUAA-SM procedure conflict, the SMF 3 aborts the UUAA-SM procedure and performs the UE-requested PDU session release procedure. If the UE-requested PDU session release procedure and the UUAA-SM procedure conflict, the SMF 3 may prioritize the performance of the UE-requested PDU session release procedure by aborting the UUAA-SM procedure. This allows the SMF 3 to handle both procedures appropriately even if the UE-requested PDU session release procedure and the UUAA-SM procedure conflict in the SMF 3.

[0092] FIG. 7 shows an example of a UE-requested PDU session release procedure during a UUAA-SM procedure. In step 701, the SMF 3 initiates the UAV authentication and authorization procedure in session management (UUAA-SM procedure). The SMF 3 may initiate the UAV authentication and authorization procedure by receiving an Nnef_Auth_Notification notify message from the UAS NF 9. The SMF 3 invokes the Nnef_Auth_Notification service operation.

[0093] In step 702, the SMF 3 initiates the UUAA-SM procedure based on the receipt of the Nnef_Auth_Notification notify message from the UAS NF 9. Specifically, the SMF 3 sends an authentication message based on the authentication method used to the UE 1 via the AMF 2. The existing UUAA-SM procedure is specified in Figure 5.2.4.1-1 of Non-Patent Document 4.

[0094] In step 703, the SMF 3 receives a PDU SESSION RELEASE REQUEST message for the PDU session providing a connection with the UAS NF 9 from the UE 1 via the AMF 2. The PDU SESSION RELEASE REQUEST message is a message in the UE-requested PDU session release procedure.

[0095] In step 704, the SMF 3 aborts the UUAA-SM procedure in response to the PDU SESSION RELEASE REQUEST message received from UE 1. As another example, if the PDU session specified in the PDU SESSION RELEASE REQUEST message is the PDU session specified in the UUAA-SM procedure, the SMF 3 may abort the UUAA-SM procedure and proceed with the UE-requested PDU session release procedure.

[0096] In step 705, SMF3 progresses the UE-requested PDU session release procedure after aborting the UUAA-SM procedure in step 704. In response to the PDU SESSION RELEASE REQUEST message received from UE1 in step 703, SMF3 may simultaneously perform the operation of aborting the UUAA-SM procedure in step 704 and the progress of the UE-requested PDU session release procedure.

[0097] According to the operation shown in Figure 7, if the UE-requested PDU session release procedure and the UUAA-SM procedure conflict, the SMF 3 aborts the UUAA-SM procedure and performs the UE-requested PDU session release procedure. If the UE-requested PDU session release procedure and the UUAA-SM procedure conflict, the SMF 3 may prioritize the performance of the UE-requested PDU session release procedure by aborting the UUAA-SM procedure. This allows the SMF 3 to handle both procedures appropriately even if the UE-requested PDU session release procedure and the UUAA-SM procedure conflict in the SMF 3.

[0098] <Fourth embodiment> The inventors have investigated the authentication and re-authorization procedures for UAS services and found various issues. For example, if the UE performs a PDU session release procedure while the network is performing a C2 communication authorization procedure, it is unclear how the SMF handles a PDU SESSION RELEASE REQUEST message from the UE. In this case, the C2 communication authorization procedure and the UE-requested PDU session release procedure may collide in the network, causing one or both procedures to fail.

[0099] This embodiment provides a solution for appropriately handling a collision between a UE-requested PDU session release procedure and a C2 communication authorization procedure in a network. The C2 communication authorization procedure is a procedure for pairing a UAV and a UAV-C to realize C2 communication.

[0100] An example of the configuration of the cellular network according to this embodiment may be the same as the example shown in FIG.

[0101] FIG. 8 is a flowchart showing an example of the operation of the SMF 3 according to this embodiment.

[0102] In step 801, the SMF3 initiates a C2 communication authorization procedure to pair the UAV and UAV-C and realize C2 communication. The SMF3 may initiate the C2 communication authorization procedure by receiving a PDU SESSION MODIFICATION REQUEST message from the UE1 via the AMF2. In the C2 communication authorization procedure, the SMF3 invokes the Nnef_Auth_Reauth service operation. The C2 communication authorization procedure may also be referred to as Authorization of C2 communication.

[0103] In step 802, the SMF 3 receives a PDU SESSION RELEASE REQUEST message in a UE-requested PDU session release procedure from the UE 1 via the AMF 2.

[0104] In step 803, the SMF3 aborts the C2 communication authorization procedure and performs a UE-requested PDU session release procedure. The SMF3 aborting the C2 communication authorization procedure may mean that the SMF3 and a related network node (e.g., UAS NF9) perform processing related to the abortion of the C2 communication authorization procedure before performing the UE-requested PDU session release procedure. As another example, if the PDU session specified in the PDU SESSION RELEASE REQUEST message is the PDU session specified in the C2 communication authorization procedure, the SMF3 may abort the C2 communication authorization procedure and perform a UE-requested PDU session release procedure.

[0105] In this embodiment, the C2 communication authorization procedure may be read as a UAV authentication and authorization (UUAA) procedure.

[0106] According to the operation shown in Figure 8, if there is a conflict between the UE-requested PDU session release procedure and the C2 communication authorization procedure (or UAV authentication and authorization procedure), the SMF3 aborts the C2 communication authorization procedure (or UAV authentication and authorization procedure) and performs the UE-requested PDU session release procedure. If there is a conflict between the UE-requested PDU session release procedure and the C2 communication authorization procedure (or UAV authentication and authorization procedure), the SMF3 may prioritize performance of the UE-requested PDU session release procedure by aborting the C2 communication authorization procedure (or UAV authentication and authorization procedure). This allows the SMF3 to appropriately handle both procedures even if there is a conflict between the UE-requested PDU session release procedure and the C2 communication authorization procedure (or UAV authentication and authorization procedure) in the SMF3.

[0107] FIG. 9 illustrates an example of a UE-requested PDU session release procedure during a C2 communication authorization procedure.

[0108] In step 901, the SMF 3 receives a PDU SESSION MODIFICATION REQUEST message in a PDU session modification procedure from the UE 1 via the AMF 2.

[0109] In step 902, the SMF 3 initiates a C2 communication authorization procedure in response to receiving the PDU SESSION MODIFICATION REQUEST message from the UE 1. Specifically, the SMF 3 invokes the Nnef_Auth_Reauth service operation. The existing C2 communication authorization procedure is specified in Figure 5.2.5.2.2-1 of Non-Patent Document 4.

[0110] In step 903, the SMF 3 completes the PDU session modification procedure. The PDU session modification procedure may be similar to the existing PDU session modification procedure, which is specified in Figure 4.3.3.2-1 of Non-Patent Document 2. In step 904, the SMF3 receives a PDU SESSION RELEASE REQUEST message in a UE-requested PDU session release procedure via the UE1 AMF2.

[0111] In step 905, the SMF 3 aborts the C2 communication authorization procedure in response to the PDU SESSION RELEASE REQUEST message received from the UE 1. As another example, if the PDU session specified in the PDU SESSION RELEASE REQUEST message is the PDU session specified in the C2 communication authorization procedure, the SMF 3 may abort the C2 communication authorization procedure and proceed with a UE-requested PDU session release procedure.

[0112] In step 906, the SMF3 progresses the UE-requested PDU session release procedure after aborting the C2 communication authorization procedure in step 905. In response to the PDU SESSION RELEASE REQUEST message received from the UE1 in step 904, the SMF3 may simultaneously perform the operation of aborting the C2 communication authorization procedure in step 905 and the progress of the UE-requested PDU session release procedure.

[0113] In this embodiment, the C2 communication authorization procedure may be read as a UAV authentication and authorization (UUAA) procedure.

[0114] According to the operation shown in Figure 9, if the UE-requested PDU session release procedure and the C2 communication authorization procedure (or UAV authentication and authorization procedure) conflict, the SMF3 aborts the C2 communication authorization procedure (or UAV authentication and authorization procedure) and performs the UE-requested PDU session release procedure. If the UE-requested PDU session release procedure and the C2 communication authorization procedure (or UAV authentication and authorization procedure) conflict, the SMF3 may prioritize performance of the UE-requested PDU session release procedure by aborting the C2 communication authorization procedure (or UAV authentication and authorization procedure). This allows the SMF3 to appropriately handle both procedures even if the UE-requested PDU session release procedure and the C2 communication authorization procedure (or UAV authentication and authorization procedure) conflict in the SMF3.

[0115] <Fifth embodiment> The inventors have investigated the authentication and re-authorization procedures for UAS services and found various issues. For example, if the network performs a UUAA-SM procedure while the UE is performing a PDU session release procedure, it is unclear how the UE handles the authentication / authorization message in the UUAA-SM procedure from the network. In this case, the PDU session release procedure and the UUAA-SM procedure may collide in the UE, causing one or both procedures to fail.

[0116] This embodiment provides a solution for appropriately handling a collision between the UE-requested PDU session release procedure and the UUAA-SM procedure in the UE.

[0117] An example of the configuration of the cellular network according to this embodiment may be the same as the example shown in FIG.

[0118] FIG. 10 is a flowchart showing an example of the operation of UE 1 according to this embodiment.

[0119] In step 1001, UE1 initiates a UE-requested PDU session release procedure. UE1 may initiate the UE-requested PDU session release procedure by sending a UL NAS TRANSPORT message containing a PDU SESSION RELEASE REQUEST message to SMF3. In step 1002, UE 1 receives a DL NAS TRANSPORT message including an authentication message in the UUAA-SM procedure from SMF 3. As another example, UE 1 may receive a DL NAS TRANSPORT message including an authentication / authorization result in the UUAA-SM procedure from SMF 3.

[0120] In step 1003, UE1 ignores the authentication message in the UUAA-SM procedure received in step 1002 and performs a UE-requested PDU session release procedure. UE1 ignoring the authentication message may mean that UE1 does not perform a further UUAA-SM procedure in response to receiving the authentication message. UE1 ignoring the authentication message may mean that UE1 suspends or temporarily does not perform the UUAA-SM procedure in response to receiving the authentication message. As another example, if the PDU session targeted by the UE-requested PDU session release procedure is the PDU session specified in the UUAA-SM procedure, UE1 may ignore the authentication message in the UUAA-SM procedure and perform the UE-requested PDU session release procedure. As another example, if UE1 receives an authentication / authorization result in step 1002, UE1 may ignore the authentication / authorization result and perform the UE-requested PDU session release procedure. UE1 ignoring the authentication / authorization result may mean that UE1 does not perform any further UUAA-SM procedures in response to receiving the authentication / authorization result. UE1 ignoring the authentication / authorization result may mean that UE1 suspends or temporarily does not perform any UUAA-SM procedures in response to receiving the authentication message.As another example, if UE1 receives an authentication / authorization result in step 1002 and the PDU session targeted by the UE-requested PDU session release procedure is a PDU session specified in the UUAA-SM procedure, it may ignore the authentication / authorization result in the UUAA-SM procedure and perform the UE-requested PDU session release procedure.

[0121] According to the operation shown in Figure 10, when a conflict occurs between the UE-requested PDU session release procedure and the UUAA-SM procedure at the UE, UE1 ignores the UUAA-SM procedure and performs the UE-requested PDU session release procedure. When a conflict occurs between the UE-requested PDU session release procedure and the UUAA-SM procedure at the UE, UE1 may ignore the UUAA-SM procedure and prioritize performance of the UE-requested PDU session release procedure. In this way, even when a conflict occurs between the UUAA-SM procedure and the UE-requested PDU session release procedure at UE1, UE1 can appropriately handle both procedures.

[0122] FIG. 11 shows an example of a UUAA-SM procedure during a UE-requested PDU session release procedure.

[0123] In step 1101, UE1 sends a UL NAS TRANSPORT message containing a PDU SESSION RELEASE REQUEST message to SMF3.

[0124] In step 1102, UE1 receives a DL NAS TRANSPORT message including an authentication message in the UUAA-SM procedure from SMF 3. As another example, UE1 may receive a DL NAS TRANSPORT message including an authentication / authorization result in the UUAA-SM procedure from SMF 3.

[0125] In step 1103, UE1 ignores the DL NAS TRANSPORT message including the authentication message in the UUAA-SM procedure received from AMF2 and performs the UE-requested PDU session release procedure. As another example, if the PDU session targeted by the UE-requested PDU session release procedure is the PDU session specified in the UUAA-SM procedure, UE1 may ignore the DL NAS TRANSPORT message including the authentication message in the UUAA-SM procedure and perform the UE-requested PDU session release procedure. As another example, if UE1 receives the authentication / authorization result in step 1102, it may ignore the authentication / authorization result and perform the UE-requested PDU session release procedure. As another example, if UE1 receives an authentication / authorization result in step 1102 and the PDU session targeted by the UE-requested PDU session release procedure is a PDU session specified in the UUAA-SM procedure, it may ignore the authentication / authorization result in the UUAA-SM procedure and perform the UE-requested PDU session release procedure.

[0126] According to the operation shown in Figure 11, when a conflict occurs between the UE-requested PDU session release procedure and the UUAA-SM procedure at the UE, UE1 ignores the UUAA-SM procedure and performs the UE-requested PDU session release procedure. When a conflict occurs between the UE-requested PDU session release procedure and the UUAA-SM procedure at the UE, UE1 may ignore the UUAA-SM procedure and prioritize performance of the UE-requested PDU session release procedure. In this way, even when a conflict occurs between the UUAA-SM procedure and the UE-requested PDU session release procedure at UE1, UE1 can appropriately handle both procedures.

[0127] Sixth Embodiment The inventors have investigated the authentication and re-authorization procedures for UAS services and found various issues. For example, if the network performs a C2 communication authorization procedure while the UE is performing a PDU session release procedure, it is unclear how the UE handles the authentication / authorization message in the C2 communication authorization procedure from the network. In this case, the PDU session release procedure and the C2 communication authorization procedure may collide in the UE, causing one or both procedures to fail.

[0128] This embodiment provides a solution for appropriately handling a collision between a UE-requested PDU session release procedure and a C2 communication authorization procedure at the UE.

[0129] An example of the configuration of the cellular network according to this embodiment may be the same as the example shown in FIG.

[0130] FIG. 12 is a flowchart showing an example of the operation of UE 1 according to this embodiment.

[0131] In step 1201, UE1 initiates a UE-requested PDU session release procedure. UE1 may initiate the UE-requested PDU session release procedure by sending a UL NAS TRANSPORT message containing a PDU SESSION RELEASE REQUEST message to SMF3.

[0132] In step 1202, UE1 receives a DL NAS TRANSPORT message including an authentication message in the C2 communication authorization procedure from SMF 3. As another example, UE1 receives a DL NAS TRANSPORT message including an authentication / authorization result in the C2 communication authorization procedure from SMF 3. The C2 communication authorization procedure may also be referred to as Authorization of C2 communication.

[0133] In step 1203, UE1 ignores the authentication message in the C2 communication authorization procedure received in step 1202 and performs a UE-requested PDU session release procedure. UE1 ignoring the authentication message may mean that UE1 does not perform a further C2 communication authorization procedure in response to receiving the authentication message. UE1 ignoring the authentication message may mean that UE1 suspends or temporarily does not perform the C2 communication authorization procedure in response to receiving the authentication message. As another example, if the PDU session targeted by the UE-requested PDU session release procedure is the PDU session specified in the C2 communication authorization procedure, UE1 may ignore the authentication message in the C2 communication authorization procedure and perform the UE-requested PDU session release procedure. As another example, if UE1 receives an authentication / authorization result in step 1202, UE1 may ignore the authentication / authorization result and perform the UE-requested PDU session release procedure. The UE1 ignoring the authentication / authorization result may mean that the UE1 does not perform any further C2 communication authorization procedure in response to receiving the authentication / authorization result. The UE1 ignoring the authentication / authorization result may mean that the UE1 suspends or temporarily does not perform the C2 communication authorization procedure in response to receiving the authentication message.As another example, if UE1 receives an authentication / authorization result in step 1202 and the PDU session targeted by the UE-requested PDU session release procedure is a PDU session specified in the C2 communication authorization procedure, it may ignore the authentication / authorization result in the C2 communication authorization procedure and perform the UE-requested PDU session release procedure.

[0134] In this embodiment, the C2 communication authorization procedure may be read as a UAV authentication and authorization (UUAA) procedure.

[0135] According to the operation shown in Figure 12, if the UE-requested PDU session release procedure and the C2 communication authorization procedure (or UAV authentication and authorization procedure) conflict at the UE, UE1 ignores the C2 communication authorization procedure (or UAV authentication and authorization procedure) and performs the UE-requested PDU session release procedure. If the UE-requested PDU session release procedure and the C2 communication authorization procedure (or UAV authentication and authorization procedure) conflict at the UE, UE1 may prioritize performance of the UE-requested PDU session release procedure by ignoring the C2 communication authorization procedure (or UAV authentication and authorization procedure). This allows UE1 to appropriately handle both procedures even if the C2 communication authorization procedure (or UAV authentication and authorization procedure) and the UE-requested PDU session release procedure conflict at UE1.

[0136] FIG. 13 illustrates an example of a C2 communication authorization procedure during a UE-requested PDU session release procedure.

[0137] In step 1301, UE1 sends a UL NAS TRANSPORT message containing a PDU SESSION RELEASE REQUEST message to SMF3.

[0138] In step 1302, UE1 receives a DL NAS TRANSPORT message including an authentication message in the C2 communication authorization procedure from SMF3. As another example, UE1 receives a DL NAS TRANSPORT message including an authentication / authorization result in the C2 communication authorization procedure from AMF2.

[0139] In step 1303, UE1 ignores the DL NAS TRANSPORT message including the authentication message in the C2 communication authorization procedure received from AMF2 and performs the UE-requested PDU session release procedure. As another example, if the PDU session targeted by the UE-requested PDU session release procedure is the PDU session specified in the C2 communication authorization procedure, UE1 ignores the DL NAS TRANSPORT message including the authentication message in the C2 communication authorization procedure and performs the UE-requested PDU session release procedure. As another example, if UE1 receives the authentication / authorization result in step 1302, it may ignore the authentication / authorization result and perform the UE-requested PDU session release procedure. As another example, if UE1 receives an authentication / authorization result in step 1202 and the PDU session targeted by the UE-requested PDU session release procedure is a PDU session specified in the C2 communication authorization procedure, it may ignore the authentication / authorization result in the C2 communication authorization procedure and perform the UE-requested PDU session release procedure.

[0140] In this embodiment, the C2 communication authorization procedure may be read as a UAV authentication and authorization (UUAA) procedure.

[0141] According to the operation shown in Figure 13, if the UE-requested PDU session release procedure and the C2 communication authorization procedure (or UAV authentication and authorization procedure) conflict at the UE, UE1 ignores the C2 communication authorization procedure (or UAV authentication and authorization procedure) and performs the UE-requested PDU session release procedure. If the UE-requested PDU session release procedure and the C2 communication authorization procedure (or UAV authentication and authorization procedure) conflict at the UE, UE1 may prioritize performance of the UE-requested PDU session release procedure by ignoring the C2 communication authorization procedure (or UAV authentication and authorization procedure). This allows UE1 to appropriately handle both procedures even if the C2 communication authorization procedure (or UAV authentication and authorization procedure) and the UE-requested PDU session release procedure conflict at UE1.

[0142] Seventh Embodiment The inventors have investigated the Service-level authentication and authorization procedure (C2 communication authorization procedure) and found various issues. For example, it is unclear how to control a UE's attempt to perform a new PDU session modification or PDU session establishment procedure that triggers a C2 communication authorization procedure while the network is performing the C2 communication authorization procedure. Because the network is currently performing the C2 communication authorization procedure, triggering a new C2 communication authorization procedure would cause a procedure conflict.

[0143] This embodiment is a procedure for preventing the UE from performing a new PDU session modification procedure or a PDU session establishment procedure that triggers a Service-level authentication and authorization procedure (C2 communication authorization procedure) until the network completes the Service-level authentication and authorization procedure (C2 communication authorization procedure).

[0144] An example of the configuration of the cellular network according to this embodiment may be the same as the example shown in FIG.

[0145] FIG. 14 shows an example during the C2 communication authorization procedure.

[0146] In step 1401, SMF3 receives a PDU SESSION MODIFICATION REQUEST message in a PDU session modification procedure from UE1 via AMF2.

[0147] In step 1402, the SMF 3 initiates a C2 communication authorization procedure in response to receiving the PDU SESSION MODIFICATION REQUEST message from the UE 1. Specifically, the SMF 3 invokes the Nnef_Auth_Reauth service operation. The existing C2 communication authorization procedure is specified in Figure 5.2.5.2.2-1 of Non-Patent Document 4.

[0148] In step 1403, the SMF 3 sends an Nsmf_PDUSession_UpdateSMContext Response including information indicating that the Service-level authentication and authorization procedure (C2 communication authorization procedure) is in progress to the AMF 2. The information indicating that the Service-level authentication and authorization procedure (C2 communication authorization procedure) is in progress may be information indicating that the Service-level authentication and authorization procedure is pending. The information indicating that the Service-level authentication and authorization procedure (C2 communication authorization procedure) is in progress may be included in a Service-level-AA pending indication IE.

[0149] In step 1404, AMF2, which has received the Nsmf_PDUSession_UpdateSMContext Response, sends a PDU Session Modification Command message to UE1, including information indicating that the Service-level authentication and authorization procedure (C2 communication authorization procedure) is in progress.

[0150] In step 1405, upon receiving the PDU Session Modification Command message, UE1 responds to AMF2 with a PDU Session Modification Command Ack (or a PDU SESSION MODIFICATION COMPLETE message) to indicate that it recognizes that it is in the middle of a Service-level authentication and authorization procedure (C2 communication authorization procedure).

[0151] In step 1406, the AMF 2 sends Nsmf_PDUSession_UpdateSMContext to the SMF 3, including information indicating that the AMF 2 recognizes that the UE 1 is in the Service-level authentication and authorization procedure (C2 communication authorization procedure). The existing PDU session modification procedure is specified in Figure 4.3.3.2-1 of Non-Patent Document 2.

[0152] According to the operation shown in Fig. 14, the SMF 3 notifies the UE 1 of information indicating that the network is performing a Service-level authentication and authorization procedure (C2 communication authorization procedure), thereby preventing the UE 1 from performing a new PDU session modification procedure or PDU session establishment procedure that would trigger the Service-level authentication and authorization procedure (C2 communication authorization procedure) until the Service-level authentication and authorization procedure is completed.

[0153] However, as an exception, UE1 may be able to perform the UE-requested PDU session release procedure even during the Service-level authentication and authorization procedure (C2 communication authorization procedure).

[0154] Next, exemplary configurations of the UE 1, AMF 2, and SMF 3 according to the above-described embodiments will be described below.

[0155] FIG. 15 is a block diagram showing an example of the configuration of UE1.

[0156] The Radio Frequency (RF) transceiver 1501 performs analog RF signal processing for communication with NG-RAN nodes. The RF transceiver 1501 may include multiple transceivers. The analog RF signal processing performed by the RF transceiver 1501 includes frequency up-conversion, frequency down-conversion, and amplification. The RF transceiver 1501 is coupled to the antenna array 1502 and the baseband processor 1503. The RF transceiver 1501 receives modulation symbol data (or OFDM symbol data) from the baseband processor 1503, generates a transmit RF signal, and provides the transmit RF signal to the antenna array 1502. The RF transceiver 1501 also generates a baseband receive signal based on the receive RF signal received by the antenna array 1502 and provides the baseband receive signal to the baseband processor 1503. The RF transceiver 1501 may include an analog beamformer circuit for beamforming. The analog beamformer circuit includes, for example, multiple phase shifters and multiple power amplifiers.

[0157] The baseband processor 1503 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) transmission format (transmission frame) generation / decomposition, (d) transmission path coding / decoding, (e) modulation (symbol mapping) / demodulation, and (f) generation of OFDM symbol data (baseband OFDM signal) using Inverse Fast Fourier Transform (IFFT). Meanwhile, control plane processing includes communication management of 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 attachment, mobility, and call management).

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

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

[0160] The baseband processor 1503 may include a modem processor (e.g., a Digital Signal Processor (DSP)) that performs digital baseband signal processing and a protocol stack processor (e.g., a Central Processing Unit (CPU) or a 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 1504, which will be described later.

[0161] The application processor 1504 is also referred to as a CPU, an MPU, a microprocessor, or a processor core. The application processor 1504 may include multiple processors (multiple processor cores). The application processor 1504 executes a system software program (operating system (OS)) and various application programs (e.g., a call application, a web browser, a mailer, a camera operation application, and a music playback application) read from the memory 1506 or a memory not shown, thereby realizing various functions of the UE1.

[0162] In some implementations, the baseband processor 1503 and the application processor 1504 may be integrated on a single chip, as indicated by the dashed line (1505) in Figure 15. In other words, the baseband processor 1503 and the application processor 1504 may be implemented as a single System on Chip (SoC) device 1505. An SoC device may also be called a system Large Scale Integration (LSI) or a chipset.

[0163] The memory 1506 is volatile memory, nonvolatile memory, or a combination thereof. The memory 1506 may include multiple physically independent memory devices. The volatile memory may be, for example, static random access memory (SRAM), dynamic RAM (DRAM), or a combination thereof. The nonvolatile memory may be mask read only memory (MROM), electrically erasable programmable ROM (EEPROM), flash memory, a hard disk drive, or any combination thereof. For example, the memory 1506 may include an external memory device accessible from the baseband processor 1503, the application processor 1504, and the SoC 1505. The memory 1506 may also include an internal memory device integrated within the baseband processor 1503, the application processor 1504, or the SoC 1505. Furthermore, the memory 1506 may include memory within a universal integrated circuit card (UICC).

[0164] The memory 1506 may store one or more software modules (computer programs) 1507 including instructions and data for performing the processes described in the above embodiments by the UE 1. In some implementations, the baseband processor 1503 or the application processor 1504 may be configured to read and execute the software modules 1507 from the memory 1506 to perform the processes described in the above embodiments using the drawings by the UE 1.

[0165] It should be noted that the control plane processing and operations performed by UE1 described in the above embodiment can be realized by elements other than the RF transceiver 1501 and the antenna array 1502, namely, at least one of the baseband processor 1503 and the application processor 1504, and the memory 1506 storing the software module 1507.

[0166] FIG. 16 shows an example configuration of the AMF2. The SMF3 and UAS-NF9 may also be configured as shown in FIG. 16. Referring to FIG. 16, the AMF2 includes a network interface 1601, a processor 1602, and a memory 1603. The network interface 1601 is used, for example, to communicate with RAN nodes and other network functions (NFs) or nodes in the 5GC. The other NFs or nodes in the 5GC include, for example, a UDM, an AUSF, a UPF, a DN, an NSSAAF, and a PCF. The network interface 1601 may include, for example, a network interface card (NIC) compliant with the IEEE 802.3 series.

[0167] The processor 1602 may be, for example, a microprocessor, a microprocessing unit (MPU), or a central processing unit (CPU). The processor 1602 may include multiple processors.

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

[0169] The memory 1603 may store one or more software modules (computer programs) 1604 including instructions and data for performing the processing by the AMF2 described in the above-described embodiments. In some implementations, the processor 1602 may be configured to read and execute the software modules 1604 from the memory 1603 to perform the processing by the AMF2 described in the above-described embodiments.

[0170] As described with reference to FIGS. 15 and 16 , each of the processors included in the UE1, AMF2, SMF3, and UAS-NF9 according to the above-described embodiments executes one or more programs including instructions for causing a computer to execute the algorithms described with reference to the drawings. The programs can be stored and provided to a computer using various types of non-transitory computer-readable media. Non-transitory computer-readable media include various types of tangible storage media. Examples of non-transitory computer-readable media include magnetic storage media (e.g., flexible disks, magnetic tapes, hard disk drives), magneto-optical storage 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, random access memory (RAM)). The programs may also be provided to a computer by various types of transitory computer-readable media. Examples of the temporary computer-readable medium include an electric signal, an optical signal, and an electromagnetic wave. The temporary computer-readable medium can provide the program to the computer via a wired communication path such as an electric wire or an optical fiber, or via a wireless communication path.

[0171] The term "user equipment (UE)" in this specification refers to an entity connected to a network via a radio interface. The term "UE" in this specification is not limited to a dedicated communication device, but may be any device having the communication function of the wireless terminal (UE) described in this specification, such as:

[0172] The terms "User Equipment (UE)" (as used in 3GPP), "mobile station," "mobile terminal," "mobile device," and "wireless device" 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, IoT device, etc. The terms "UE" and "wireless terminal" also encompass devices that are stationary for extended periods of time.

[0173] The UE may be, for example, production or manufacturing equipment and / or energy-related machinery (including, by way of example only, boilers, engines, turbines, solar panels, wind turbines, hydroelectric generators, thermal power generators, nuclear 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, dies, rolls, conveying equipment, lifting equipment, cargo handling equipment, textile machinery, sewing machinery, printing presses, printing-related machinery, paper-converting 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, cogwheels, power transmissions, lubrication systems, valves, pipe fittings, and / or application systems of any of the above-mentioned equipment or machinery).

[0174] The UE may be, for example, a transportation device (for example, a vehicle, an automobile, a motorcycle, a bicycle, a train, a bus, a handcart, a rickshaw, a ship and other watercraft, an airplane, a rocket, a satellite, a drone, a balloon, etc.).

[0175] The UE may be, for example, an information communication device (for example, an electronic computer and related devices, a communication device and related devices, an electronic component, etc.).

[0176] The UE may be, for example, a refrigerator, refrigerator-applied products and equipment, commercial and service equipment, vending machines, automatic service machines, office machines and equipment, consumer electrical and electronic machinery and appliances (e.g., audio equipment, speakers, radios, video equipment, televisions, oven ranges, rice cookers, coffee makers, dishwashers, washing machines, dryers, fans, ventilation fans and related products, vacuum cleaners, etc.).

[0177] The UE may be, for example, an electronic application system or device (eg, an X-ray device, a particle accelerator device, a radioactive material application device, a sonic application device, an electromagnetic application device, a power application device, etc.).

[0178] The UE may be, for example, a light bulb, a light fixture, a weighing machine, analytical equipment, testing and measuring equipment (including, by way of example, a smoke alarm, a occupancy alarm sensor, a motion sensor, a radio tag, etc.), a watch or clock, a laboratory machine, an optical machine, medical equipment and / or a medical system, a weapon, a sharp tool, or a hand tool.

[0179] The UE may be, for example, a personal digital assistant or device with wireless communication capabilities (e.g., an electronic device (e.g., a personal computer, electronic measuring instrument, etc.) configured to accommodate or accept a wireless card, wireless module, etc.).

[0180] A UE may be, for example, a device or part of a device that provides applications, services, or solutions in the "Internet of Things" (IoT) using wired and wireless communication technologies. IoT devices (or things) include appropriate electronics, software, sensors, network connectivity, etc., that enable devices to collect and exchange data with each other and with other communication devices. IoT devices may be automated devices that follow software instructions stored in their internal memory. IoT devices may operate without the need for human supervision or attention. IoT devices may be attached to devices and / or remain inactive for long periods of time. IoT devices may be implemented as part of a stationary device. IoT devices may be embedded in non-stationary devices (e.g., vehicles) or attached to animals or people being monitored / tracked. IoT technology can be implemented on any communication device that can be connected to a communication network to send and receive data without the control of human input or software instructions stored in memory. IoT devices are also called Machine Type Communication (MTC) devices, Machine to Machine (M2M) communication devices, or Narrow Band-IoT (NB-IoT) UEs.

[0181] A UE may support one or more IoT or MTC applications.

[0182] Some examples of MTC applications are listed in the list provided 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 but shows exemplary MTC applications. In this list, the service areas of the MTC applications include security, tracking and tracing, payment, health, remote maintenance / control, metering, and consumer devices.

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

[0184] Examples of MTC applications related to track and trace include Fleet Management, Order Management, Telematics Insurance: Pay as you drive (PAYD), Asset Tracking, Navigation, Traffic information, Road tolling, and Road traffic optimisation / steering.

[0185] Examples of payment related MTC applications include Point of sales (POS), Vending machines, and Gaming machines.

[0186] Examples of health-related MTC applications include Monitoring vital signs, Supporting the aged or handicapped, Web Access Telemedicine points, and Remote diagnostics.

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

[0188] Examples of MTC applications related to metering include Power, Gas, Water, Heating, Grid control, and Industrial metering.

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

[0190] Examples of applications, services, and solutions include MVNO (Mobile Virtual Network Operator) services / systems, disaster prevention radio services / systems, private branch exchange (PBX) services / systems, PHS / digital cordless telephone services / systems, Point of sales (POS) systems, advertising services / systems, Multimedia Broadcast and Multicast Service (MBMS) services / systems, V2X (Vehicle to Everything: vehicle-to-vehicle communication and road-to-vehicle and pedestrian-to-vehicle communication) services / systems, in-train mobile radio services / systems, location information related services / systems, disaster / emergency radio communication services / systems, IoT (Internet of Things) services / systems, community services / systems, video distribution services / systems, Femtocell application services / systems, and VoLTE (Voice over LTE) services / systems. LTE) services / systems, wireless tag services / systems, billing services / systems, radio on-demand services / systems, roaming services / systems, user behavior monitoring services / systems, communication carrier / communication network selection services / systems, function restriction services / systems, PoC (Proof of Concept) services / systems, personal information management services / systems for terminals, display and video services / systems for terminals, non-communication services / systems for terminals, ad hoc networks / DTN (Delay Tolerant Networking) services / systems, etc.

[0191] The above-mentioned categories of UE are merely examples of applications of the technical concepts and embodiments described herein, and the UEs herein are not limited to these examples, and those skilled in the art can make various modifications thereto.

[0192] The above-described embodiments are merely examples of application of the technical ideas obtained by the inventors of the present invention. In other words, the technical ideas are not limited to the above-described embodiments, and various modifications can be made to them.

[0193] For example, some or all of the above embodiments can be described as, but are not limited to, the following supplementary notes. (Appendix 1-1) at least one memory; at least one processor coupled to the at least one memory; Equipped with The at least one processor: Initiate the UAV authentication and authorization (UUAA-MM) procedure; receiving a DEREGISTRATION REQUEST message in a UE-initiated de-registration procedure from an Uncrewed Aerial Vehicle (UAV); responsive to receiving the DEREGISTRATION REQUEST message, aborting the UUAA-MM procedure; configured to perform the UE-initiated de-registration procedure when receiving the DEREGISTRATION REQUEST message; Access and Mobility Management Function (AMF) node. (Appendix 1-2) Initiate the UAV authentication and authorization (UUAA-MM) procedure; receiving a DEREGISTRATION REQUEST message in a UE-initiated de-registration procedure from an Uncrewed Aerial Vehicle (UAV); responsive to receiving the DEREGISTRATION REQUEST message, aborting the UUAA-MM procedure; If the DEREGISTRATION REQUEST message is received, the UE performs the UE-initiated de-registration procedure. A method in an Access and Mobility Management Function (AMF) node. (Appendix 1-3) A non-transitory computer-readable medium storing a program for causing a computer to perform a method in an Access and Mobility Management Function (AMF) node, comprising: The method comprises: Initiate the UAV authentication and authorization (UUAA-MM) procedure; receiving a DEREGISTRATION REQUEST message in a UE-initiated de-registration procedure from an Uncrewed Aerial Vehicle (UAV); responsive to receiving the DEREGISTRATION REQUEST message, aborting the UUAA-MM procedure; If the DEREGISTRATION REQUEST message is received, the UE performs the UE-initiated de-registration procedure. Non-transitory computer-readable medium. (Appendix 2-1) at least one memory; at least one processor coupled to the at least one memory; Equipped with The at least one processor: Initiating a UE-initiated de-registration procedure; receiving a DL NAS TRANSPORT message in a UUAA-MM procedure from an Access and Mobility Management Function (AMF) node; Ignoring the received DL NAS TRANSPORT message; configured to perform the UE-initiated de-registration procedure when receiving the DL NAS TRANSPORT message; Uncrewed aerial vehicle (UAV). (Appendix 2-2) Initiating a UE-initiated de-registration procedure; receiving a DL NAS TRANSPORT message in a UUAA-MM procedure from an Access and Mobility Management Function (AMF) node; Ignoring the received DL NAS TRANSPORT message; If the DL NAS TRANSPORT message is received, the UE-initiated de-registration procedure is performed. Methods in Uncrewed Aerial Vehicles (UAVs). (Appendix 2-3) A non-transitory computer-readable medium storing a program for causing a computer to perform a method in an Uncrewed Aerial Vehicle (UAV), The method comprises: Initiating a UE-initiated de-registration procedure; receiving a DL NAS TRANSPORT message in a UUAA-MM procedure from an Access and Mobility Management Function (AMF) node; Ignoring the received DL NAS TRANSPORT message; If the DL NAS TRANSPORT message is received, the UE-initiated de-registration procedure is performed. Non-transitory computer-readable medium. (Appendix 3-1) at least one memory; at least one processor coupled to the at least one memory; Equipped with The at least one processor: Initiating the UAV authentication and authorization procedure in session management (UUAA-SM procedure); receiving a PDU SESSION RELEASE REQUEST message for a PDU session providing a connection with a UAS NF9 in a UE-requested PDU session release procedure; responsive to receiving the PDU SESSION RELEASE REQUEST message, aborting the UUAA-SM procedure; configured to perform the UE-requested PDU session release procedure when the PDU SESSION RELEASE REQUEST message is received; Session Management Function (SMF) node. (Appendix 3-2) Initiating the UAV authentication and authorization procedure in session management (UUAA-SM procedure); receiving a PDU SESSION RELEASE REQUEST message for a PDU session providing a connection with a UAS NF9 in a UE-requested PDU session release procedure; responsive to receiving the PDU SESSION RELEASE REQUEST message, aborting the UUAA-SM procedure; If the PDU SESSION RELEASE REQUEST message is received, the UE performs the UE-requested PDU session release procedure. A method in a Session Management Function (SMF) node. (Appendix 3-3) A non-transitory computer-readable medium storing a program for causing a computer to perform a method in a Session Management Function (SMF) node, The method comprises: Initiating the UAV authentication and authorization procedure in session management (UUAA-SM procedure); receiving a PDU SESSION RELEASE REQUEST message for a PDU session providing a connection with a UAS NF9 in a UE-requested PDU session release procedure; responsive to receiving the PDU SESSION RELEASE REQUEST message, aborting the UUAA-SM procedure; If the PDU SESSION RELEASE REQUEST message is received, the UE performs the UE-requested PDU session release procedure. Non-transitory computer-readable medium. (Appendix 4-1) at least one memory; at least one processor coupled to the at least one memory; Equipped with The at least one processor: Initiate the C2 communications authorization procedure (Authorization for C2 procedure) or the UAV authentication and authorization procedure (UUAA-SM procedure), receiving a PDU SESSION RELEASE REQUEST message in a UE-requested PDU session release procedure; responsive to receiving the PDU SESSION RELEASE REQUEST message, aborting the C2 Communication Authorization or the UUAA-SM procedure; configured to perform the UE-requested PDU session release procedure when the PDU SESSION RELEASE REQUEST message is received; Session Management Function (SMF) node. (Appendix 4-2) Initiate the C2 communications authorization procedure (Authorization for C2 procedure) or the UAV authentication and authorization procedure (UUAA-SM procedure), receiving a PDU SESSION RELEASE REQUEST message in a UE-requested PDU session release procedure; responsive to receiving the PDU SESSION RELEASE REQUEST message, aborting the C2 Communication Authorization or the UUAA-SM procedure; If the PDU SESSION RELEASE REQUEST message is received, the UE performs the UE-requested PDU session release procedure. A method in a Session Management Function (SMF) node. (Appendix 4-3) A non-transitory computer-readable medium storing a program for causing a computer to perform a method in a Session Management Function (SMF) node, The method comprises: Initiate the C2 communications authorization procedure (Authorization for C2 procedure) or the UAV authentication and authorization procedure (UUAA-SM procedure), receiving a PDU SESSION RELEASE REQUEST message in a UE-requested PDU session release procedure; responsive to receiving the PDU SESSION RELEASE REQUEST message, aborting the C2 Communication Authorization or the UUAA-SM procedure; If the PDU SESSION RELEASE REQUEST message is received, the UE performs the UE-requested PDU session release procedure. Non-transitory computer-readable medium. (Appendix 5-1) at least one memory; at least one processor coupled to the at least one memory; Equipped with The at least one processor: Initiate a UE-requested PDU session release procedure; receiving an authentication message in the UUAA-SM procedure; Ignoring the received authentication message; configured to perform the UE-requested PDU session release procedure when the authentication message is received; Uncrewed aerial vehicle (UAV). (Appendix 5-2) Initiate a UE-requested PDU session release procedure; receiving an authentication message in the UUAA-SM procedure; Ignoring the received authentication message; If the authentication message is received, the UE-requested PDU session release procedure is performed. Methods in Uncrewed Aerial Vehicles (UAVs). (Appendix 5-3) A non-transitory computer-readable medium storing a program for causing a computer to perform a method in an Uncrewed Aerial Vehicle (UAV), The method comprises: Initiate a UE-requested PDU session release procedure; receiving an authentication message in the UUAA-SM procedure; Ignoring the received authentication message; If the authentication message is received, the UE-requested PDU session release procedure is performed. Non-transitory computer-readable medium. (Appendix 6-1) at least one memory; at least one processor coupled to the at least one memory; Equipped with The at least one processor: Initiate a UE-requested PDU session release procedure; Receive an authentication message in a C2 communication authorization procedure (Authorization for C2 procedure) or a UAV authentication and authorization procedure (UUAA-SM procedure); Ignoring the received authentication message; configured to perform the UE-requested PDU session release procedure when the authentication message is received; Uncrewed aerial vehicle (UAV). (Appendix 6-2) Initiate a UE-requested PDU session release procedure; Receive an authentication message in a C2 communication authorization procedure (Authorization for C2 procedure) or a UAV authentication and authorization procedure (UUAA-SM procedure); Ignoring the received authentication message; If the authentication message is received, the UE-requested PDU session release procedure is performed. Methods in Uncrewed Aerial Vehicles (UAVs). (Appendix 6-3) A non-transitory computer-readable medium storing a program for causing a computer to perform a method in an Uncrewed Aerial Vehicle (UAV), The method comprises: Initiate a UE-requested PDU session release procedure; Receive an authentication message in a C2 communication authorization procedure (Authorization for C2 procedure) or a UAV authentication and authorization procedure (UUAA-SM procedure); Ignoring the received authentication message; If the authentication message is received, the UE-requested PDU session release procedure is performed. Non-transitory computer-readable medium. (Appendix 7-1) at least one memory; at least one processor coupled to the at least one memory; Equipped with The at least one processor: receiving a PDU Session Modification Command message from the network, the PDU Session Modification Command message including information indicating that a C2 communication authorization procedure (Service-level authentication and authorization procedure) is in progress; and transmitting to the network a PDU Session Modification Command Ack or a PDU SESSION MODIFICATION COMPLETE message including information indicating that the network recognizes that it is in a Service-level authentication and authorization procedure (C2 communication authorization procedure), Uncrewed aerial vehicle (UAV). (Appendix 7-2) receiving a PDU Session Modification Command message from the network, the PDU Session Modification Command message including information indicating that a C2 communication authorization procedure (Service-level authentication and authorization procedure) is in progress; sending a PDU Session Modification Command Ack or PDU SESSION MODIFICATION COMPLETE message to the network, the PDU Session Modification Command Ack including information indicating that the network recognizes that it is in a Service-level authentication and authorization procedure (C2 communication authorization procedure); Methods in Uncrewed Aerial Vehicles (UAVs). (Appendix 7-3) A non-transitory computer-readable medium storing a program for causing a computer to perform a method in an Uncrewed Aerial Vehicle (UAV), The method comprises: receiving a PDU Session Modification Command message from the network, the PDU Session Modification Command message including information indicating that a C2 communication authorization procedure (Service-level authentication and authorization procedure) is in progress; sending a PDU Session Modification Command Ack or PDU SESSION MODIFICATION COMPLETE message to the network, the PDU Session Modification Command Ack including information indicating that the network recognizes that it is in a Service-level authentication and authorization procedure (C2 communication authorization procedure); Non-transitory computer-readable medium.

[0194] This application claims priority based on Japanese Patent Application No. 2021-160146, filed on September 29, 2021, the disclosure of which is incorporated herein in its entirety. [Explanation of symbols]

[0195] 1 UE 2 AMF 3 SMF 4. AUSF 5AN 6 UPF 7DN 8 UDM 9 UAS NF 10 NSSAAF 1503 Baseband Processor 1504 Application Processor 1506 memory 1507 Modules 1602 processor 1603 memory 1604 modules

Claims

1. receiving an authentication message in an authentication and authorization procedure during a UE-requested PDU session release procedure; If the PDU session indicated by the authentication message is a PDU session that the wireless terminal requests to release, Ignore the authentication message, A wireless terminal configured to proceed with the UE-requested PDU session release procedure.

2. The wireless terminal of claim 1 , wherein the authentication and authorization procedure is used for authentication and authorization procedures of a UAV.

3. The radio terminal according to claim 1 or 2, wherein the radio terminal requests the release of the PDU session by transmitting a UE-requested PDU session release request message.

4. receiving an authentication message in an authentication and authorization procedure during a UE-requested PDU session release procedure; If the PDU session indicated by the authentication message is a PDU session that the wireless terminal requests to release, ignoring the authentication message; and proceeding with the UE-requested PDU session release procedure.

5. The method of claim 4 , wherein the authentication and authorization procedure is used for authentication and authorization procedures of UAVs.

6. 6. The method according to claim 4 or 5, wherein the release of the PDU session is requested by sending a UE-requested PDU session release request message.

Images