AMF Node, UAV, SMF Node, Method, and Program

Abstract

The purpose of the present invention is to provide a device capable of appropriately handling a UUAA procedure and another mobility management procedure or a session management procedure when the UUAA procedure and the other procedure conflict with each other. 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), stops 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. Therefore, it is possible for the AMF to, for example, appropriately handle the UUAA procedure and the other mobility management procedure when the procedures conflict with each other.

Description

Technical Field

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

Background Art

[0002] A 5G system (5GS) connects a wireless terminal (user equipment (UE) or Uncrewed Aerial Vehicle (UAV)) to a data network (DN). Hereinafter, it is possible to interchange UE and UAV. The connectivity service between the UE and the DN is supported by one or more Protocol Data Unit (PDU) sessions (see, for example, Non-Patent Documents 1 to 3). A PDU session is an association, session, or connection between the UE and the DN. A PDU session is used to provide a PDU connectivity service (i.e., the exchange of PDUs between the UE and the DN). A PDU session is established between the UE and a User Plane Function (UPF) (i.e., PDU session anchor) to which the UE and the DN are connected. From the viewpoint of data transfer, a PDU session is composed of a tunnel (N9 tunnel) in 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 define the PDU session establishment procedure, the PDU session modification procedure, and the 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 modification procedure is described, for example, in Chapter 4.3.3 of Non-Patent Document 2 and Chapter 6.4.2 of Non-Patent Document 3. The PDU session release procedure is described, for example, in Chapter 4.3.4 of Non-Patent Document 2 and Chapter 6.4.3 of Non-Patent Document 3.

[0004] 5GS further supports network slicing (see, for example, Non-Patent Documents 1 to 3, particularly Section 5.15 of Non-Patent Document 1). Network slicing uses Network Function Virtualization (NFV) technology and software-defined networking (SDN) technology to enable the creation of multiple virtualized logical networks on top of a physical network. Each virtualized logical network is called a network slice. A network slice provides specific network capabilities and network characteristics. A network slice instance (NSI) is defined as a set of a Network Function (NF) instance, 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). The S-NSSAI consists of a Slice / Service type (SST) and a Slice Differentiator (SD). The SST refers to the expected network slice behaviour with respect to features and services. The SD is optional information that complements the SST to distinguish multiple network slices of the same Slice / Service type.

[0006] The S-NSSAI can have standard values or non-standard values. At present, Standard SST values 1, 2, 3, and 4 are associated with enhanced Mobile Broad Band (eMBB), Ultra Reliable and Low Latency Communication (URLLC), Massive Internet of Things (MIoT), and Vehicle to Everything (V2X) slice types. The non-standard value of the S-NSSAI identifies one network slice within a specific Public Land Mobile Network (PLMN). That is, non-standard SST values are PLMN-specific values and are associated with the PLMN ID of the PLMN 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 S-NSSAI and Mapped S-NSSAI. The S-NSSAI identifies the network slice provided by the Public Land Mobile Network (PLMN) in 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 corresponding 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 subscriber information of the UE user. Hereinafter, in this specification, the S-NSSAI and the Mapped S-NSSAI may be collectively referred to simply as the S-NSSAI.

[0008] On one hand, Network Slice Selection Assistance Information (NSSAI) means a set of S-NSSAIs. Therefore, one or more S-NSSAIs can be included in one NSSAI. There are multiple types of NSSAI, which are known as Configured NSSAI, Requested NSSAI, Allowed NSSAI, Rejected NSSAI, and Pending NSSAI.

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

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

[0011] The Allowed NSSAI is provided by the Serving PLMN to the UE 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 a registration procedure. Thus, the Allowed NSSAI is signaled by the network (i.e., AMF) to the UE and stored in the respective (non-volatile) memories of the AMF and the UE.

[0012] The Rejected NSSAI contains one or more S-NSSAIs that have been rejected by the current (or serving) PLMN. When the UE is roaming, the Rejected NSSAI contains the S-NSSAIs of the Home PLMN (HPLMN). The Rejected NSSAI may also be referred to as rejected S-NSSAIs. The S-NSSAI is rejected either across the entire current PLMN or within the current registration area. If the AMF rejects any of the one or more S-NSSAIs included in the Requested NSSAI, for example, during the UE's registration procedure, these are included in the Rejected NSSAI. The Rejected NSSAI is signaled to the UE by the network (i.e., the AMF) and stored in the respective (non-volatile) memories of the AMF and the UE.

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

[0014] Pending NSSAI indicates one or more S-NSSAIs for which Network Slice-Specific Authentication and Authorization (NSSAA) is pending. The Pending NSSAI can include the S-NSSAI and the Mapped S-NSSAI. The Serving PLMN shall perform NSSAA for the S-NSSAIs of the HPLMN for which NSSAA has been imposed based on the subscription information. To perform NSSAA, the AMF invokes an Extensible Authentication Protocol (EAP)-based authorization procedure. The EAP-based authentication procedure takes a relatively long time to obtain its outcome. Therefore, the AMF determines the Allowed NSSAI as described above in the UE's registration procedure, but does not include the S-NSSAIs for which NSSAA has been imposed in the Allowed NSSAI, and includes these instead in the Pending NSSAI. The Pending NSSAI is signaled to the UE by the network (i.e., the 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 referred to as, but is not limited to, the Mobility Management (MM) context. The UE context may include any one or more of the above-mentioned Allowed NSSAI, Rejected NSSAI, Extended Rejected NSSAI, and Pending NSSAI. On the other hand, the UE manages the UE NSSAI configuration. The UE NSSAI configuration includes the above-mentioned Configured NSSAI, Allowed NSSAI, Rejected NSSAI, Extended Rejected NSSAI, and Pending NSSAI. The UE NSSAI configuration is stored in the non-volatile memory within 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 the NSSAI storage.

[0016] Section 5.15.10 of Non-Patent Document 1 and Section 4.2.9 of Non-Patent Document 2 define 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 the revocation of Slice-Specific Authorization triggered by an AAA server (AAA-S).

[0017] Section 5.2 of Non-Patent Document 4 defines UAV Authentication and Authorization (UUAA). More specifically, Sections 5.2.2, 5.2.3, and 5.2.4 of Non-Patent Document 4 describe UAV authentication and authorization (UUAA). Section 5.2.5 of Non-Patent Document 4 describes Authorization for C2 for realizing C2 communication. Hereinafter, it is possible to interchange UAV authentication and authorization (UUAA) and Authorization for C2.

[0018] The Third Generation Partnership Project (3GPP) SA2 working group has started standardization work on architecture enhancements for UAVs to enable drone systems that utilize mobile communications (see, for example, Non-Patent Document 4). The 5G architecture enhancements define the following enhanced functions: the authentication and authorization function of UAVs by the USS (UAS Service Supplier) in mobility management. This authentication and authorization of UAVs is called UUAA-MM. The 5G architecture enhancements also define the following enhanced function: the authentication and authorization function of UAVs by the USS in session management. This authentication and authorization of UAVs is called UUAA-SM. UUAA-MM and UUAA-SM may also be referred to as UUAA. The 5G architecture enhancements also define the following enhanced function: the C2 communication authorization function for realizing C2 communication.

[0019] The UAV needs to be authenticated and authorized before using the UAS (Uncrewed Aerial System) Service. The UAS Service refers to the communication with the USS that provides a safe and efficient airspace utilization service, C2 communication, remote identification of the UAV, and connectivity for the location and tracking of the UAV.

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

[0021] UUAA-MM is executed upon the opportunity of the registration procedure based on the operator policy. The AMF includes the aerial UE subscription in the Access and Mobility subscriber data of the UAV, and executes the UUAA-MM procedure when the registration request message includes the CAA (Civil Aviation Administration)-Level UAV ID. The CAA-Level-UAV ID is issued by the USS that conducts, for example, flight management of the drone and is used to identify the UAV.

[0022] UUAA-SM is executed upon the opportunity of the PDU session establishment procedure (PDU session establishment and PDU session modification) when UUAA-MM is not executed. The SMF executes the UUAA-SM procedure when 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] If the UE enables operations based on C2 (Command and Control) communication, it needs to obtain C2 communication authorization. C2 communication refers to the user plane link for propagating messages containing UAV operation commands and control information from a UAV controller (UAV-C) or UTM (UAS Traffic Management) to the UAV, or reporting telemetry data from the UAV to the UAV controller or UTM. The drone pilot can control the UAV through the UAV controller of the UAS. UTM refers to a system that supports the safe and efficient sharing of airspace by in-flight UAVs with other users.

[0024] The C2 communication authorization may be executed in the UUAA-SM procedure described above, or may be executed after the UAV is authenticated and authorized. When executed after the UAV is authenticated and authorized, the UE executes a PDU session modification procedure including the CAA-Level UAV ID and C2 authorization information. If the DNN and / or S-NSSAI of the PDU session to be updated in the PDU session modification contains the CAA-Level UAV ID and the PDU session is for UAS service, the SMF executes the C2 communication authorization procedure.

[0025] In the above-mentioned UUAA-MM, UUAA-SM, and C2 communication authorization, after each procedure is initiated, multiple exchanges of authentication and / or authorization information are carried out between the USS and the UE, and the results of authentication and authorization are notified to the UE. In the UUAA-MM procedure, the AMF notifies the UE by including the results of authentication and authorization in the DL NAS TRANSPORT message sent to the UE. In the UUAA-SM procedure, the SMF notifies the UE by including the results of authentication and authorization in the PDU session accept message sent to the UE.

Prior Art Documents

Non-Patent Documents

[0026]

Non-Patent Document 1

Non-Patent Document 2

Non-Patent Document 3

Non-Patent Document 4

Summary of the Invention

Problems to be Solved by the Invention

[0027] The inventors have studied the authentication and re - authorization procedures for UAS Service and found various problems. For example, when the UUAA procedure collides with other mobility management procedures or session management procedures, it is not clear how the UE or core network node should handle them. Therefore, one of the objectives to be achieved by the embodiments disclosed in this specification is to provide an apparatus, method, and program that can appropriately handle the situation when the UUAA procedure collides with other mobility management procedures or session management procedures. It should be noted that this objective is only one of the multiple objectives to be achieved by the multiple embodiments disclosed herein. Other objectives or problems and novel features will be clarified from the description of this specification or the attached drawings.

Means for Solving the Problems

[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. The at least one processor is configured to initiate an Uncrewed Aerial Vehicle Authentication and Authorization (UUAA-MM) procedure, receive a DEREGISTRATION REQUEST message in a UE-initiated de-registration procedure from an Uncrewed Aerial Vehicle (UAV), abort the UUAA-MM procedure in response to receiving the DEREGISTRATION REQUEST message, and, when 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 comprises initiating an Uncrewed Aerial Vehicle Authentication and Authorization (UUAA-MM) procedure, receiving a DEREGISTRATION REQUEST message in a UE-initiated de-registration procedure from an Uncrewed Aerial Vehicle (UAV), aborting the UUAA-MM procedure in response to receiving the DEREGISTRATION REQUEST message, and, when the DEREGISTRATION REQUEST message is received, performing the UE-initiated de-registration procedure.

[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 described 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. 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, when the DL NAS TRANSPORT message is received, perform the UE-initiated de-registration procedure.

[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. The at least one processor is configured to initiate a UAV authentication and authorization procedure (UUAA-SM procedure) in session management, receive a PDU SESSION RELEASE REQUEST message for a PDU session that provides a connection to UAS NF9 in a UE-requested PDU session release procedure, abort the UUAA-SM procedure in response to the reception of the PDU SESSION RELEASE REQUEST message, and, when 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. The at least one processor is configured to initiate a C2 communication authorization procedure (Authorization for C2 procedure) or an Unmanned Aerial Vehicle (UAV) authentication and authorization procedure (UUAA-SM procedure), receive a PDU SESSION RELEASE REQUEST message in a UE-requested PDU session release procedure, abort the C2 communication authorization or the UUAA-SM procedure in response to receiving the PDU SESSION RELEASE REQUEST message, and, when receiving the PDU SESSION RELEASE REQUEST message, perform the UE-requested PDU session release procedure.

[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. 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, when receiving the authentication message, perform the UE-requested PDU session release procedure.

[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. 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, when the authentication message is received, perform the UE-requested PDU session release procedure.

[0036] In a ninth aspect, an Uncrewed Aerial Vehicle (UAV) includes at least one memory and at least one processor coupled to the at least one memory. 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 in progress, and transmit, to the network, a PDU Session Modification Command Ack or PDU SESSION MODIFICATION COMPLETE message including information indicating that it has recognized that the Service-level authentication and authorization procedure (C2 communication authorization procedure) is in progress.

Advantages of the Invention

[0037] According to the above aspect, it is possible to provide an apparatus, a method, and a program that can appropriately handle a situation where a UUAA procedure conflicts with other mobility management procedures or session management procedures.

Brief Description of Drawings

[0038]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Embodiments for Carrying Out 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 denoted by the same reference numerals, and redundant descriptions are omitted as necessary for clarity of explanation.

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

[0041] The plurality of embodiments shown below are mainly described with respect to the 3GPP 5th generation mobile communication system (5G system (5GS)). However, these embodiments may be applied to other cellular communication systems that support network slicing similar to 5GS.

[0042] In particular, Table 1 shows an example of vocabulary substitution when applying the plurality of embodiments shown below to the 3GPP 4th generation mobile communication system (Evolved Packet System (EPS)).

[0043]

Table 1

[0044] <The First Embodiment> Figure 1 shows a configuration example of a cellular network (i.e., 5GS) according to this embodiment. Each of the elements shown in Figure 1 is a network function and provides an interface defined by the 3rd Generation Partnership Project (3GPP). Each element (network function) shown in Figure 1 can be implemented, for example, as a network element on dedicated hardware, as a 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 someone other than the MNO. If the cellular network shown in Figure 1 is an NPN, it may be an independent network represented as a Stand-alone Non-Public Network (SNPN) or may be an NPN linked to an MNO network represented as a Public network integrated NPN.

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

[0047] AN5 includes Next Generation Radio Access Network (NG-RAN) or non-3GPP AN or both. Non-3GPP AN may be a network handling wireless LAN (WiFi) communication or a network handling wired communication represented as Wireline 5G Access Network (W-5GAN). UPF6 may include a plurality of interconnected UPFs.

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

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

[0050] SMF3 is one of the network functions within the 5GC Control Plane. SMF3 manages the PDU session. 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 AMF2. SMF3 provides NF services on the service-based interface (i.e., Nsmf interface) to NF consumers (e.g., AMF2, other SMFs). The NF services provided by SMF3 include PDU session management services (e.g., Nsmf_PDUSession). The NF services enable NF consumers (e.g., AMF2) to handle PDU sessions. SMF3 may be an Intermediate SMF (I-SMF). The I-SMF is inserted between AMF2 and the original SMF3 as necessary when 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 on the service-based interface (i.e., Nausf interface) to NF consumers (e.g., AMF2, UDM8). The NF services provided by AUSF4 include the UE authentication service (e.g., Nausf_UEAuthentication and Nausf_NSSAA_Authenticate). The Nausf_UEAuthentication service provides UE authentication and related keying material to the NF consumer (i.e., AMF). More specifically, AUSF4 cooperates with UDM8 and the Authentication credential Repository and Processing Function (ARPF) to perform authentication using either of the two authentication methods supported in 5GS (i.e., 5G-Authentication and Key Agreement (AKA) and EAP-based authentication). After performing authentication, AUSF4 returns the authentication result and, if successful, the master key to AMF2. The master key is used by AMF2 to derive NAS security keys and other security key(s). For UE authentication, AUSF4 closely cooperates with UDM8. The Nausf_NSSAA_Authenticate service provides the NF consumer (e.g., AMF2) with authentication and authorization services specialized for the network slice between UE1 and the AAA server via AUSF4.

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

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

[0054] The UAS NF9 stores and maintains information regarding whether the re - authentication is at the AMF or the SMF / SMF+PGW - C, and the addresses of the serving AMF or SMF / SMF+PGW - C, in order to support the re - authentication request by the USS. The SMF / PGW - C is a core network node used for PDN connections when 5GS - EPS inter - working is supported. Further, the UAS NF9 stores and maintains the results of the UUAA - MM procedure and the UUAA - SM procedure.

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

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

[0057] The inventors have examined the authentication and re - authorization procedures related to UAS Service and found various issues. For example, when UE1 executes the de - registration procedure while the network is executing the UUAA - MM procedure, it is not clear how AMF2 should handle 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, and there is a risk that one or both of the procedures may fail.

[0058] This embodiment provides a solution for properly 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 AMF2 according to this embodiment.

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

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

[0062] In step 203, AMF2 aborts the UUAA-MM procedure and proceeds with the UE-initiated de-registration procedure. When AMF2 aborts the UUAA-MM procedure, it may mean that AMF2 and related network nodes (e.g., UAS NF9) perform processing related to aborting the UUAA-MM procedure prior to proceeding with the UE-initiated de-registration procedure. As another example, 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 executed as a result of this check, the UUAA-MM procedure may be aborted and the UE-initiated de-registration procedure may be proceeded with. 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 executed is "3GPP access" and / or "non-3GPP access", the UUAA-MM procedure may be aborted and UE-initiated de-registration may be proceeded with. 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 executed as a result of the check, AMF2 may proceed with 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 which the UUAA-MM procedure is being executed is "non 3GPP access", AMF2 may proceed with 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" in AMF2, and the access type for which the UUAA-MM procedure is being executed is "3GPP access", both the UUAA-MM procedure and the UE-initiated de-registration procedure may be progressed.

[0063] According to the operation shown in FIG. 2, if the UUAA-MM procedure and the UE-initiated de-registration procedure conflict in the network, AMF2 aborts the UUAA-MM procedure and executes the UE-initiated de-registration procedure. AMF2 may prioritize the execution of the UE-initiated de-registration procedure by aborting the UUAA-MM procedure when the UUAA-MM procedure and the UE-initiated de-registration procedure conflict in the network. Thereby, even when the UUAA-MM procedure and the UE-initiated de-registration procedure conflict in the network, the network can appropriately handle both procedures.

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

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

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

[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 the registration status of UE1 has changed to "DEREGISTERED". This event notification may be referred to as Namf_EventExposure_Notify. The Namf_EventExposure_Notify service operation may be initiated by this event notification. UAS NF9 aborts the UUAA-MM procedure based on this event notification. In order for UAS NF9 to receive this event notification from AMF2, it subscribes to the AMF service before receiving the event notification. This subscription to the AMF service may also be referred to as the Namf_EventExposure_Subscribe or Namf_EventExposure_Subscribe service operation. UAS NF9 may initiate the Namf_EventExposure_Subscribe service operation and subscribe to the AMF service in response to receiving the Nnef_Authentication_authenticate request message in step 301. UAS NF9 may also initiate the Namf_EventExposure_Subscribe service operation and subscribe to the AMF service after the UUAA-MM procedure is successful. If the UUAA-MM procedure is successful, UAS NF9 saves the UAV's UUAA context indicating successful authentication and authorization, and sends an Nnef_Authentication_authenticate response carrying information indicating successful authentication and authorization to AMF2.In addition, when the Namf_EventExposure_Subscribe service operation is started after the successful UUAA-MM procedure, in addition to the operation of aborting the above-mentioned UUAA-MM procedure, UAS NF9 may also delete the UUAA context of the UAV indicating successful authentication and authorization that it has saved. As another example, in response to receiving a DEREGISTRATION REQUEST message from UE1, AMF2 may send a request message containing information indicating an EAP failure to UAS NF9 and call the Nnef_Authentication_authenticate service operation. UAS NF9 aborts the UUAA-MM procedure in response to the call of the service operation. At this time, if UAS NF9 has saved the UUAA context of the UAV indicating successful authentication and authorization, it may also delete the context. As another example, 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 executed as a result of the check, AMF2 may abort the UUAA-MM procedure and progress 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 executed as a result of the check, AMF2 may progress both the UUAA-MM procedure and the UE-initiated de-registration procedure.

[0068] In step 304, after AMF2 aborts the UUAA-MM procedure in step 303, it progresses the UE-initiated de-registration procedure. AMF2 may simultaneously perform the operation of aborting the UUAA-MM procedure in step 303 and progressing 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 the same as the existing UE-initiated de-registration procedure. The existing UE-initiated de-registration procedure is defined in Figure 4.2.2.3.2-1 of Non-Patent Document 2.

[0069] According to the operation shown in Figure 3, when the UUAA-MM procedure and the UE-initiated de-registration procedure conflict in the network, AMF2 aborts the UUAA-MM procedure and progresses the UE-initiated de-registration procedure. AMF2 may prioritize the progress of the UE-initiated de-registration procedure by aborting the UUAA-MM procedure when the UUAA-MM procedure and the UE-initiated de-registration procedure conflict in the network. Thereby, even when the UUAA-MM procedure and the UE-initiated de-registration procedure conflict in the network, the network can appropriately handle both procedures.

[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 for starting UDM8. The specific operations that AMF9 performs on UAS NF9 may be the same as the operations when receiving a DEREGISTRATION REQUEST message from UE1 (i.e., the operations described in step 303). In this case, instead of step 304, AMF2 progresses the Network-initiated de-registration procedure for starting UDM8. 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 the modification of the first embodiment, when the UUAA-MM procedure and the Network-initiated de-registration procedure for starting UDM8 conflict in the network, AMF2 aborts the UUAA-MM procedure and progresses the Network-initiated de-registration procedure for starting UDM8. AMF2 may prioritize the progress of the Network-initiated de-registration procedure for starting UDM8 by aborting the UUAA-MM procedure when the UUAA-MM procedure and the Network-initiated de-registration procedure for starting UDM8 conflict in the network. Thereby, even when the UUAA-MM procedure and the Network-initiated de-registration procedure for starting UDM8 conflict in the network, the network can appropriately handle both procedures.

[0072] <Second Embodiment> The inventors have examined the authentication and re - authorization procedures related to UAS Service and found various issues. For example, when the network executes the UUAA - MM procedure while the UE is executing the UE - initiated de - registration procedure, it is not clear how the UE should handle the 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 in the UE, and there is a risk that one or both of the procedures may fail.

[0073] This embodiment provides a solution for appropriately handling the situation where the UUAA - MM procedure and the UE - initiated de - registration procedure collide in the UE.

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

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

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

[0077] In step 402, UE1 receives a DL NAS TRANSPORT message from AMF2 in the UUAA-MM procedure. The DL NAS TRANSPORT message may include a service-level authentication and authorization (Service-level-AA) container information element (IE) in which an authentication message is 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. For UE1 to ignore the DL NAS TRANSPORT message may mean that UE1 does not perform further UUAA-MM procedures in response to the reception of the DL NAS TRANSPORT message. For UE1 to ignore the DL NAS TRANSPORT message may mean that UE1 holds off on or temporarily does not perform the UUAA-MM procedure in response to the reception of 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 in which the UUAA-MM procedure is being executed. If, as a result of this check, the access type information included in the DEREGISTRATION REQUEST message matches the access type in which the UUAA-MM procedure is being executed, 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 in which the UUAA-MM procedure is being executed 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, as a result of the check, the access type information included in the DEREGISTRATION REQUEST message does not match the access type in which the UUAA-MM procedure is being executed, UE1 may proceed with 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" in UE1, and the access type for which the UUAA-MM procedure is being executed is "non 3GPP access", both the UUAA-MM procedure and the UE-initiated de-registration procedure may proceed. If the access type information included in the DEREGISTRATION REQUEST message is set to "non 3GPP access" in AMF2, and the access type for which the UUAA-MM procedure is being executed is "3GPP access", both the UUAA-MM procedure and the UE-initiated de-registration procedure may proceed.

[0079] According to the operation shown in FIG. 4, when the UUAA-MM procedure and the UE-initiated de-registration procedure conflict in UE1, UE1 ignores the UUAA-MM procedure and proceeds with the UE-initiated de-registration procedure. When the UUAA-MM procedure and the UE-initiated de-registration procedure conflict in the network, UE1 may prioritize the execution of the UE-initiated de-registration procedure by ignoring the UUAA-MM procedure. Thereby, even when the UUAA-MM procedure and the UE-initiated de-registration procedure conflict in UE1, UE1 can appropriately handle both procedures.

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

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

[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 containing 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 executed. If the access type information included in the DEREGISTRATION REQUEST message matches the access type for which the UUAA-MM procedure is being executed 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. 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 executed as a result of the check, UE1 may proceed with both the UUAA-MM procedure and the UE-initiated de-registration procedure.

[0084] According to the operation shown in FIG. 5, when the UUAA-MM procedure and the UE-initiated de-registration procedure conflict at UE1, UE1 ignores the UUAA-MM procedure and proceeds with the UE-initiated de-registration procedure. When the UUAA-MM procedure and the UE-initiated de-registration procedure conflict in the network, UE1 may prioritize the execution of the UE-initiated de-registration procedure by ignoring the UUAA-MM procedure. Thereby, even when the UUAA-MM procedure and the UE-initiated de-registration procedure conflict at UE1, UE1 can appropriately handle both procedures.

[0085] <The Third Embodiment> The inventors have considered the authentication and re - authentication procedures for UAS Service and found various issues. For example, when the UE executes the PDU session release procedure while the network is executing the UUAA - SM procedure, it is not clear how the SMF should handle 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, and there is a risk that one or both of the procedures may fail.

[0086] This embodiment provides a solution for appropriately handling the UE - requested PDU session release procedure and the procedure for UAV authentication and authorization (UUAA - SM procedure) when they collide in the network. This embodiment also provides a similar solution for appropriately handling the UE - requested PDU session release procedure and the procedure for UAV re - authentication and re - authorization (UUAA - SM procedure) when they collide in the network. Therefore, in the third embodiment, the procedure for UAV authentication and authorization (UUAA - SM procedure) can be read as the procedure for UAV re - authentication and re - authorization (UUAA - SM procedure).

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

[0088] FIG. 6 is a flowchart showing an example of the operation of SMF3 according to this embodiment. In step 601, SMF3 activates the UAV authentication and authorization procedure (UUAA - SM procedure) in session management. The UUAA - SM procedure may be activated in response to the reception of an authentication and authorization request (Nnef_Auth_Notification notify) message from UAS_NF9. In the UUAA - SM procedure, SMF3 calls the Nnef_Authentication_Authenticate service operation.

[0089] In step 602, SMF3 receives, from UE1 via AMF2, a PDU SESSION RELEASE REQUEST message for the PDU session that provides a connection with UAS NF9. The PDU SESSION RELEASE REQUEST message is a message in the UE-requested PDU session release procedure.

[0090] In step 603, SMF3 aborts the UUAA-SM procedure and proceeds with the UE-requested PDU session release procedure. For SMF3 to abort the UUAA-SM procedure may mean that SMF3 and related network nodes (e.g., UAS NF9) perform processing related to aborting the UUAA-SM procedure prior to performing the UE-initiated de-registration procedure. 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, SMF3 may abort the UUAA-SM procedure and proceed with the UE-requested PDU session release procedure.

[0091] According to the operations shown in FIG. 6, when the UE-requested PDU session release procedure and the UUAA-SM procedure conflict, SMF3 aborts the UUAA-SM procedure and proceeds with the UE-requested PDU session release procedure. When the UE-requested PDU session release procedure and the UUAA-SM procedure conflict, SMF3 may give priority to proceeding with the UE-requested PDU session release procedure by aborting the UUAA-SM procedure. Thereby, even when the UE-requested PDU session release procedure and the UUAA-SM procedure conflict in SMF3, SMF3 can handle both procedures appropriately.

[0092] Figure 7 shows an example of the UE-requested PDU session release procedure in the UUAA-SM procedure. In step 701, SMF3 activates the UAV authentication and authorization procedure (UUAA-SM procedure) in session management. SMF3 may activate the UAV authentication and authorization procedure by receiving the Nnef_Auth_Notification notify message from UAS NF9. SMF3 invokes the Nnef_Auth_Notification service operation.

[0093] In step 702, SMF3 activates the UUAA-SM procedure based on the reception of the Nnef_Auth_Notification notify message from UAS NF9. Specifically, an authentication message based on the authentication method used is sent to UE1 via AMF2. The existing UUAA-SM procedure is defined in Figure 5.2.4.1-1 of Non-Patent Document 4.

[0094] In step 703, SMF3 receives, from UE1 via AMF2, a PDU SESSION RELEASE REQUEST message for the PDU session that provides a connection with UAS NF9. The PDU SESSION RELEASE REQUEST message is a message in the UE-requested PDU session release procedure.

[0095] In step 704, in response to the PDU SESSION RELEASE REQUEST message received from UE1, the UUAA-SM procedure is aborted. 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, SMF3 may abort the UUAA-SM procedure and proceed with the UE-requested PDU session release procedure.

[0096] In step 705, after aborting the UUAA-SM procedure in step 704, SMF3 proceeds with the UE-requested PDU session release procedure. 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 in response to the PDU SESSION RELEASE REQUEST message received from UE1 in step 703.

[0097] According to the operations shown in FIG. 7, when the UE-requested PDU session release procedure and the UUAA-SM procedure conflict, SMF3 aborts the UUAA-SM procedure and proceeds with the UE-requested PDU session release procedure. When the UE-requested PDU session release procedure and the UUAA-SM procedure conflict, SMF3 may prioritize the progress of the UE-requested PDU session release procedure by aborting the UUAA-SM procedure. Thereby, even when the UE-requested PDU session release procedure and the UUAA-SM procedure conflict in SMF3, SMF3 can appropriately handle both procedures.

[0098] <Fourth Embodiment> The inventors have examined the authentication and re - authorization procedures related to UAS Service and found various issues. For example, when the UE executes the PDU session release procedure while the network is executing the C2 communication authorization procedure, it is not clear how the SMF should handle the 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, and there is a risk that one or both of the procedures may fail.

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

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

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

[0102] In step 801, the SMF3 starts the C2 communication authorization (Authorization for C2) procedure for pairing the UAV and UAV - C to realize C2 communication. The SMF3 may start 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 calls 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 SMF3 receives a PDU SESSION RELEASE REQUEST message in the UE-requested PDU session release procedure from the UE1 via the AMF2.

[0104] In step 803, the SMF3 aborts the C2 communication authorization procedure and proceeds with the UE-requested PDU session release procedure. When the SMF3 aborts the C2 communication authorization procedure, it may mean that the SMF3 and related network nodes (e.g., UAS NF9) perform processing related to aborting the C2 communication authorization procedure prior to proceeding with the UE-requested PDU session release procedure. As another example, if the PDU session specified in the PDU SESSION RELEASE REQUEST message is the same as the PDU session specified in the C2 communication authorization procedure, the SMF3 may abort the C2 communication authorization procedure and proceed with the 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 FIG. 8, when the UE-requested PDU session release procedure and the C2 communication authorization procedure (or UAV authentication and authorization procedure) conflict, SMF3 aborts the C2 communication authorization procedure (or UAV authentication and authorization procedure) and executes the UE-requested PDU session release procedure. When the UE-requested PDU session release procedure and the C2 communication authorization procedure (or UAV authentication and authorization procedure) conflict, SMF3 may prioritize the execution of the UE-requested PDU session release procedure by aborting the C2 communication authorization procedure (or UAV authentication and authorization procedure). Thereby, even when the UE-requested PDU session release procedure and the C2 communication authorization procedure (or UAV authentication and authorization procedure) conflict in SMF3, SMF3 can appropriately handle both procedures.

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

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

[0109] In step 902, in response to receiving the PDU SESSION MODIFICATION REQUEST message from UE1, SMF3 activates the C2 communication authorization procedure. Specifically, SMF3 invokes the Nnef_Auth_Reauth service operation. The existing C2 communication authorization procedure is defined in FIG. 5.2.5.2.2-1 of Non-Patent Document 4.

[0110] In step 903, SMF3 completes the PDU session modification procedure. The PDU session modification procedure may be the same as the existing PDU session modification procedure. The existing PDU session modification procedure is defined in Figure 4.3.3.2-1 of Non-Patent Document 2. In step 904, SMF3 receives a PDU SESSION RELEASE REQUEST message in the UE-requested PDU session release procedure via UE1AMF2.

[0111] In step 905, in response to the PDU SESSION RELEASE REQUEST message received from UE1, SMF3 aborts the C2 communication authorization 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, SMF3 may abort the C2 communication authorization procedure and proceed with the UE-requested PDU session release procedure.

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

[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 FIG. 9, when 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. When the UE-requested PDU session release procedure and the C2 communication authorization procedure (or UAV authentication and authorization procedure) conflict, the SMF3 may prioritize the execution of the UE-requested PDU session release procedure by aborting the C2 communication authorization procedure (or UAV authentication and authorization procedure). Thereby, even when the UE-requested PDU session release procedure and the C2 communication authorization procedure (or UAV authentication and authorization procedure) conflict in the SMF3, the SMF3 can appropriately handle both procedures.

[0115] <Fifth Embodiment> The inventors have studied the authentication and re-authorization procedures for the UAS Service and found various problems. For example, when the network executes the UUAA-SM procedure while the UE is executing the PDU session release procedure, it is not clear how the UE should handle 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 collide in the UE, and there is a risk that one or both of the procedures may fail.

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

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

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

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

[0120] In step 1003, UE1 ignores the authentication message in the UUAA-SM procedure received in step 1002 and performs the UE-requested PDU session release procedure. For UE1 to ignore the authentication message may mean that UE1 does not perform further UUAA-SM procedures in response to the reception of the authentication message. For UE1 to ignore the authentication message may mean that UE1 suspends or temporarily does not perform the UUAA-SM procedure in response to the reception of the authentication message. As another example, if the PDU session targeted in 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. For UE1 to ignore the authentication / authorization result may mean that UE1 does not perform further UUAA-SM procedures in response to the reception of the authentication / authorization result. For UE1 to ignore the authentication / authorization result may mean that UE1 suspends or temporarily does not perform the UUAA-SM procedure in response to the reception of the authentication message.As another example, when the UE1 receives the authentication / authorization result in step 1002 and the PDU session targeted in the UE-requested PDU session release procedure is the PDU session specified in the UUAA-SM procedure, the UE1 may ignore the authentication / authorization result in the UUAA-SM procedure and execute the UE-requested PDU session release procedure.

[0121] According to the operation shown in FIG. 10, when the UE-requested PDU session release procedure and the UUAA-SM procedure conflict in the UE, the UE1 ignores the UUAA-SM procedure and executes the UE-requested PDU session release procedure. When the UE-requested PDU session release procedure and the UUAA-SM procedure conflict in the UE, the UE1 may prioritize the execution of the UE-requested PDU session release procedure by ignoring the UUAA-SM procedure. Thereby, even when the UUAA-SM procedure and the UE-requested PDU session release procedure conflict in the UE1, the UE1 can appropriately handle both procedures.

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

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

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

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

[0126] According to the operation shown in FIG. 11, when the UE-requested PDU session release procedure and the UUAA-SM procedure conflict in the UE, UE1 ignores the UUAA-SM procedure and executes the UE-requested PDU session release procedure. When the UE-requested PDU session release procedure and the UUAA-SM procedure conflict in the UE, UE1 may prioritize the execution of the UE-requested PDU session release procedure by ignoring the UUAA-SM procedure. Thereby, even when the UUAA-SM procedure and the UE-requested PDU session release procedure conflict in UE1, UE1 can appropriately handle both procedures.

[0127] <Sixth Embodiment> The inventors et al. studied the authentication and re-authorization procedures for the UAS Service and found various problems. For example, when the network executes the C2 communication authorization procedure while the UE is executing the PDU session release procedure, it is not clear how the UE should handle 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 conflict (collision) in the UE, and there is a risk that one or both of the procedures may fail.

[0128] This embodiment provides a solution for appropriately handling the UE-requested PDU session release procedure and the C2 communication authorization procedure when they conflict (collision) in the UE.

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

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

[0131] In step 1201, UE1 initiates the 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 containing an authentication message in the Authorization for C2 procedure from SMF3. As another example, UE1 receives a DL NAS TRANSPORT message containing an authentication / authorization result in the Authorization for C2 procedure from SMF3. The Authorization for C2 procedure may also be referred to as Authorization of C2 communication.

[0133] In step 1203, the authentication message in the C2 communication authorization procedure received in step 1202 is ignored and the UE-requested PDU session release procedure is proceeded with. For UE1 to ignore the authentication message may mean that UE1 does not perform further C2 communication authorization procedures in response to the reception of the authentication message. For UE1 to ignore the authentication message may mean that UE1 reserves or temporarily does not perform the C2 communication authorization procedure in response to the reception of the authentication message. As another example, if the PDU session targeted in 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 proceed with 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 proceed with the UE-requested PDU session release procedure. For UE1 to ignore the authentication / authorization result may mean that UE1 does not perform further C2 communication authorization procedures in response to the reception of the authentication / authorization result. For UE1 to ignore the authentication / authorization result may mean that UE1 reserves or temporarily does not perform the C2 communication authorization procedure in response to the reception of the authentication message.As another example, if UE1 receives an authentication / authorization result in step 1202 and the PDU session targeted in the UE-requested PDU session release procedure is the PDU session specified in the C2 communication authorization procedure, UE1 may ignore the authentication / authorization result in the C2 communication authorization procedure and execute 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 operations shown in FIG. 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 executes the UE-requested PDU session release procedure. When 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 the execution of the UE-requested PDU session release procedure by ignoring the C2 communication authorization procedure (or UAV authentication and authorization procedure). Thereby, even when the C2 communication authorization procedure (or UAV authentication and authorization procedure) and the UE-requested PDU session release procedure conflict at UE1, UE1 can appropriately handle both procedures.

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

[0137] In step 1301, UE1 transmits 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 containing an authentication message in the C2 communication authorization procedure from SMF3. As another example, UE1 receives a DL NAS TRANSPORT message containing an authentication / authorization result in the C2 communication authorization procedure from AMF2.

[0139] In step 1303, UE1 ignores the DL NAS TRANSPORT message containing the authentication message in the C2 communication authorization procedure received from AMF2 and proceeds with the UE-requested PDU session release procedure. As another example, if the PDU session targeted in 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 containing the authentication message in the C2 communication authorization procedure and proceeds with the UE-requested PDU session release procedure. As another example, if UE1 receives the authentication / authorization result in step 1302, UE1 may ignore the authentication / authorization result and proceed with the UE-requested PDU session release procedure. As another example, if UE1 receives the authentication / authorization result in step 1202 and the PDU session targeted in the UE-requested PDU session release procedure is the PDU session specified in the C2 communication authorization procedure, UE1 may ignore the authentication / authorization result in the C2 communication authorization procedure and proceed with 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 FIG. 13, when the UE-requested PDU session release procedure and the C2 communication authorization procedure (or UAV authentication and authorization procedure) conflict in the UE, the UE1 ignores the C2 communication authorization procedure (or UAV authentication and authorization procedure) and executes the UE-requested PDU session release procedure. When the UE-requested PDU session release procedure and the C2 communication authorization procedure (or UAV authentication and authorization procedure) conflict in the UE, the UE1 may prioritize the execution of the UE-requested PDU session release procedure by ignoring the C2 communication authorization procedure (or UAV authentication and authorization procedure). Thereby, even when the C2 communication authorization procedure (or UAV authentication and authorization procedure) and the UE-requested PDU session release procedure conflict in the UE1, the UE1 can appropriately handle both procedures.

[0142] <The Seventh Embodiment> The inventors have studied the Service-level authentication and authorization procedure (C2 communication authorization procedure) and found various problems. For example, it is not clear how to control the trial of a new PDU session modification procedure or a PDU session establishment procedure that triggers the C2 communication authorization procedure by the UE while the network is executing the C2 communication authorization procedure. Since the network is executing the C2 communication authorization procedure, the trigger of a new C2 communication authorization procedure will cause a conflict in the procedure.

[0143] This embodiment is a procedure for preventing the UE from executing a new PDU session modification procedure or a PDU session establishment procedure that triggers the 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] The configuration example of the cellular network according to this embodiment may be the same as the example shown in FIG. 1.

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

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

[0147] In step 1402, in response to receiving the PDU SESSION MODIFICATION REQUEST message from the UE1, the SMF3 activates the C2 communication authorization procedure. Specifically, the SMF3 calls the Nnef_Auth_Reauth service operation. The existing C2 communication authorization procedure is defined in FIG. 5.2.5.2.2-1 of Non-Patent Document 4.

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

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

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

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

[0152] According to the operations shown in Figure 14, SMF3 notifies UE1 of information indicating that the network is executing the Service-level authentication and authorization procedure (C2 communication authorization procedure). Thereby, until the Service-level authentication and authorization procedure is completed, UE1 can be prevented from executing a new PDU session modification procedure or a PDU session establishment procedure that triggers the Service-level authentication and authorization procedure (C2 communication authorization procedure).

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

[0154] Subsequently, hereinafter, configuration examples of UE1, AMF2, and SMF3 according to the above-described plurality of embodiments will be described.

[0155] Figure 15 is a block diagram showing a configuration example of UE1.

[0156] The Radio Frequency (RF) transceiver 1501 performs analog RF signal processing to communicate with NG-RAN nodes. The RF transceiver 1501 may include a plurality of 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 transmission RF signal, and supplies the transmission RF signal to the antenna array 1502. Also, the RF transceiver 1501 generates a baseband received signal based on the received RF signal received by the antenna array 1502 and supplies this to the baseband processor 1503. The RF transceiver 1501 may include an analog beamformer circuit for beamforming. The analog beamformer circuit includes, for example, a plurality of phase shifters and a plurality of power amplifiers.

[0157] The baseband processor 1503 performs digital baseband signal processing (data plane processing) and control plane processing for wireless communication. The digital baseband signal processing includes (a) data compression / decompression, (b) data segmentation / concatenation, (c) generation / decomposition of a transmission format (transmission frame), (d) channel coding / decoding, (e) modulation (symbol mapping) / demodulation, and (f) generation of OFDM symbol data (baseband OFDM signal) by Inverse Fast Fourier Transform (IFFT), etc. On the other hand, the control plane processing includes communication management of layer 1 (e.g., transmission 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 the Service Data Adaptation Protocol (SDAP) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, Medium Access Control (MAC) layer, and Physical (PHY) layer. Also, the control plane processing by the baseband processor 1503 may include processing of the Non-Access Stratum (NAS) protocol, 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., Digital Signal Processor (DSP)) that performs digital baseband signal processing and a protocol stack processor (e.g., Central Processing Unit (CPU) or Micro Processing Unit (MPU)) that performs control plane processing. In this case, the protocol stack processor that performs control plane processing may be shared with the application processor 1504 described later.

[0161] The application processor 1504 is also referred to as a CPU, MPU, microprocessor, or processor core. The application processor 1504 may include a plurality of processors (a plurality of processor cores). The application processor 1504 realizes various functions of the UE1 by executing a system software program (Operating System (OS)) and various application programs (for example, a call application, a WEB browser, an e-mail, a camera operation application, a music playback application) read from the memory 1506 or a memory not shown.

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

[0163] The memory 1506 is a volatile memory, a non-volatile memory, or a combination thereof. The memory 1506 may include a plurality of physically independent memory devices. The volatile memory is, for example, Static Random Access Memory (SRAM), Dynamic RAM (DRAM), or a combination thereof. The non-volatile memory is a mask Read Only Memory (MROM), Electrically Erasable Programmable ROM (EEPROM), flash memory, or 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 include an embedded memory device integrated within the baseband processor 1503, within the application processor 1504, or within the SoC 1505. Further, the memory 1506 may include the memory within a Universal Integrated Circuit Card (UICC).

[0164] The memory 1506 may store one or more software modules (computer programs) 1507 including instruction groups and data for performing the processing by the UE1 described in the above-described multiple embodiments. In some implementations, the baseband processor 1503 or the application processor 1504 may be configured to perform the processing of the UE1 described with reference to the drawings in the above-described embodiments by reading and executing the software module 1507 from the memory 1506.

[0165] Note that the control plane processing and operations performed by the UE1 described in the above-described embodiments can be realized by other elements excluding the RF transceiver 1501 and the antenna array 1502, that is, 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 a configuration example of AMF2. SMF3 and UAS-NF9 may also be configured as shown in FIG. 16. Referring to FIG. 16, 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 to communicate with other network functions (NFs) or nodes within 5GC. Other NFs or nodes within 5GC include, for example, UDM, AUSF, UPF, DN, NSSAAF, and 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 Micro Processing Unit (MPU), or a Central Processing Unit (CPU). The processor 1602 may include a plurality of processors.

[0168] The memory 1603 is composed of volatile memory and non-volatile memory. The memory 1603 may include a plurality of physically independent memory devices. The volatile memory is, for example, Static Random Access Memory (SRAM) or Dynamic RAM (DRAM) or a combination thereof. The non-volatile memory is a mask Read Only Memory (MROM), an Electrically Erasable Programmable ROM (EEPROM), a flash memory, or a hard disk drive, or any combination thereof. The memory 1603 may include storage located away 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] Memory 1603 may store one or more software modules (computer programs) 1604 containing instruction groups and data for performing the processing by AMF2 described in the above-described embodiments. In some implementations, processor 1602 may be configured to perform the processing of AMF2 described in the above-described embodiments by reading and executing the software module 1604 from memory 1603.

[0170] As described with reference to FIGS. 15 and 16, each of the processors of UE1, AMF2, SMF3, and UAS-NF9 according to the above-described embodiments executes one or more programs including instruction groups for causing a computer to perform the algorithms described with reference to the drawings. This program is stored using various types of non-transitory computer readable media and can be supplied to a computer. Non-transitory computer readable media include various types of tangible storage media. Examples of non-transitory computer readable media include magnetic recording media (e.g., flexible disks, magnetic tapes, hard disk drives), magneto-optical recording media (e.g., magneto-optical disks), Compact Disc Read Only Memory (CD-ROM), CD-R, CD-R / W, semiconductor memories (e.g., mask ROM, Programmable ROM (PROM), Erasable PROM (EPROM), flash ROM, Random Access Memory (RAM)). Also, the program may be supplied to a computer by various types of transitory computer readable media. Examples of transitory computer readable media include electrical signals, optical signals, and electromagnetic waves. The transitory computer readable media can supply the program to a computer via a wired communication path such as electric wires and optical fibers, or a wireless communication path.

[0171] The wireless terminal (User Equipment (UE)) in this specification is an entity connected to a network via a wireless interface. The wireless terminal (UE) in this specification is not limited to a dedicated communication device, and may be any device having the communication function of the wireless terminal (UE) described in this specification.

[0172] The terms "user terminal (User Equipment (UE) as a word used in 3GPP)", "mobile station", "mobile terminal", "mobile device", and "wireless device" are generally intended to be synonymous with each other. The UE may be a stand-alone mobile station such as a terminal, a mobile phone, a smartphone, a tablet, a cellular IoT terminal, an IoT device, etc. The terms "UE" and "wireless terminal" also include devices that have been stationary for a long time.

[0173] The UE may be, for example, production equipment, manufacturing equipment, and / or energy-related machinery (including, as an example, pumps such as boilers, engines, turbines, solar panels, wind turbines, hydroelectric generators, thermal power generators, nuclear power generators, storage batteries, nuclear power systems, nuclear-related equipment, heavy electrical equipment, vacuum pumps, etc., compressors, fans, blowers, hydraulic equipment, pneumatic equipment, metalworking machines, manipulators, robots, robot application systems, tools, dies, rolls, conveying devices, lifting devices, cargo handling devices, textile machines, sewing machines, printing machines, printing-related machines, paper-making machines, chemical machines, mining machines, mining-related machines, construction machines, construction-related machines, agricultural machines and / or implements, forestry machines and / or implements, fishery machines and / or implements, safety and / or environmental protection implements, tractors, bearings, precision bearings, chains, gears, power transmission devices, lubrication devices, valves, pipe fittings, and / or application systems of any of the devices or machines described above).

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

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

[0176] The UE may be, for example, a refrigerator, refrigeration application products and devices, commercial and service equipment, vending machines, automatic service machines, office machines and devices, consumer electric and electronic appliances (such as audio equipment, speakers, radios, video equipment, TVs, ovens, 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 electronic application device (such as an X-ray device, particle accelerator device, radioactive substance application device, sound wave application device, electromagnetic application device, power application device, etc.).

[0178] The UE may be, for example, a light bulb, lighting, measuring instrument, analytical instrument, testing machine and measuring machinery (such as a smoke detector, human alarm sensor, motion sensor, wireless tag, etc.), a watch (watch or clock), a physicochemical machine, an optical machine, a medical device and / or 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 a wireless communication function (such as an electronic device (e.g., a personal computer or electronic measuring instrument) configured to be attached with or insert a wireless card or wireless module, etc.).

[0180] The UE may be a device or a part thereof that provides the following applications, services, and solutions in, for example, the "Internet of Things (IoT)" using wired or wireless communication technologies. An IoT device (or thing) is equipped with appropriate electronic devices, software, sensors, network connections, etc. that enable the devices to collect and exchange data with each other and with other communication devices. The IoT device may be an automated device that follows software instructions stored in an internal memory. The IoT device may operate without the need for human supervision or response. The IoT device may be installed as part of a stationary device and may be installed in a non-stationary device (e.g., a vehicle) or attached to an animal or person to be monitored / tracked. The IoT technology can be implemented on any communication device that can be connected to a communication network that transmits and receives data regardless of human input control or software instructions stored in memory. The IoT device may also be called a Machine Type Communication (MTC) device, or a Machine to Machine (M2M) communication device, or a Narrow Band-IoT (NB-IoT) UE.

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

[0182] Some examples of MTC applications are listed in the list shown in 3GPP TS22.368 V13.2.0 (2017-01-13) Annex B, the content of which is incorporated herein by reference. This list is not exhaustive and shows MTC applications as an example. In this list, the service areas of MTC applications include Security, Tracking & 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 Tracking & Tracing 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 MTC applications related to payment include Point of sales (POS), Vending machines, and Gaming machines.

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

[0187] Examples of MTC applications related to 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 related to Consumer devices include Digital photo frames, Digital cameras, and e-books (ebooks).

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

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

[0192] The above-described embodiments are merely examples regarding the application of the technical idea obtained by the present inventor. That is, the technical idea is not limited to the above-described embodiments, and various changes can be made thereto.

[0193] For example, part or all of the above-described embodiments may be described as follows, but are not limited thereto. (Appendix 1-1) At least one memory, At least one processor coupled to the at least one memory, Comprising, The at least one processor Starts the Uncrewed Aerial Vehicle Authentication and Authorization (UUAA-MM) procedure, Receives a DEREGISTRATION REQUEST message in the UE-initiated de-registration procedure from an Uncrewed Aerial Vehicle (UAV), In response to receiving the DEREGISTRATION REQUEST message, aborts the UUAA-MM procedure, When the DEREGISTRATION REQUEST message is received, is configured to perform the UE-initiated de-registration procedure, Access and Mobility Management Function (AMF) node. (Appendix 1-2) Starts the Uncrewed Aerial Vehicle Authentication and Authorization (UUAA-MM) procedure, Receives a DEREGISTRATION REQUEST message in the UE-initiated de-registration procedure from an Uncrewed Aerial Vehicle (UAV), In response to receiving the DEREGISTRATION REQUEST message, aborts the UUAA-MM procedure, When receiving the DEREGISTRATION REQUEST message, perform 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, The method includes: Starting the Uncrewed Aerial Vehicle Authentication and Authorization (UUAA-MM) procedure, Receiving a DEREGISTRATION REQUEST message from an Uncrewed Aerial Vehicle (UAV) in a UE-initiated de-registration procedure, In response to receiving the DEREGISTRATION REQUEST message, aborting the UUAA-MM procedure, When receiving the DEREGISTRATION REQUEST message, perform the UE-initiated de-registration procedure. A non-transitory computer-readable medium. (Appendix 2-1) At least one memory, At least one processor coupled to the at least one memory, Comprising: The at least one processor: Starts a UE-initiated de-registration procedure, Receives a DL NAS TRANSPORT message in the UUAA-MM procedure from an Access and Mobility Management Function (AMF) node, Ignores the received DL NAS TRANSPORT message, When receiving the DL NAS TRANSPORT message, it is configured to perform the UE-initiated de-registration procedure. Uncrewed Aerial Vehicle (UAV). (Appendix 2-2) Initiate the UE-initiated de-registration procedure. Receive the DL NAS TRANSPORT message in the UUAA-MM procedure from the Access and Mobility Management Function (AMF) node. Ignore the received DL NAS TRANSPORT message. When receiving the DL NAS TRANSPORT message, perform the UE-initiated de-registration procedure. Method in an Uncrewed Aerial Vehicle (UAV). (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 includes: Initiate the UE-initiated de-registration procedure. Receive the DL NAS TRANSPORT message in the UUAA-MM procedure from the Access and Mobility Management Function (AMF) node. Ignore the received DL NAS TRANSPORT message. When receiving the DL NAS TRANSPORT message, perform the UE-initiated de-registration procedure. Non-transitory computer-readable medium. (Appendix 3-1) At least one memory, At least one processor coupled to the at least one memory, comprising, wherein the at least one processor initiates a UAV authentication and authorization procedure (UUAA - SM procedure) in session management, receives a PDU SESSION RELEASE REQUEST message for a PDU session that provides a connection to UAS NF9 in a UE - requested PDU session release procedure, in response to receiving the PDU SESSION RELEASE REQUEST message, aborts the UUAA - SM procedure, and when receiving the PDU SESSION RELEASE REQUEST message, is configured to perform the UE - requested PDU session release procedure, a Session Management Function (SMF) node. (Appendix 3 - 2) initiates a UAV authentication and authorization procedure (UUAA - SM procedure) in session management, receives a PDU SESSION RELEASE REQUEST message for a PDU session that provides a connection to UAS NF9 in a UE - requested PDU session release procedure, in response to receiving the PDU SESSION RELEASE REQUEST message, aborts the UUAA - SM procedure, and when receiving the PDU SESSION RELEASE REQUEST message, 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, wherein the method comprises: initiating a UAV authentication and authorization procedure (UUAA-SM procedure) in session management; receiving a PDU SESSION RELEASE REQUEST message for a PDU session that provides a connection to UAS NF9 in a UE-requested PDU session release procedure; aborting the UUAA-SM procedure in response to receiving the PDU SESSION RELEASE REQUEST message; performing the UE-requested PDU session release procedure when the PDU SESSION RELEASE REQUEST message is received; a non-transitory computer-readable medium. (Appendix 4-1) at least one memory; at least one processor coupled to the at least one memory; and comprising: 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; abort the C2 communication authorization or the UUAA-SM procedure in response to receiving the PDU SESSION RELEASE REQUEST message; and 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 communication authorization procedure (Authorization for C2 procedure) or the UAV authentication and authorization procedure (UUAA-SM procedure), Receive the PDU SESSION RELEASE REQUEST message in the UE-requested PDU session release procedure, In response to the reception of the PDU SESSION RELEASE REQUEST message, abort the C2 communication authorization or the UUAA-SM procedure, When the PDU SESSION RELEASE REQUEST message is received, perform the UE-requested PDU session release procedure, 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 includes: Initiate the C2 communication authorization procedure (Authorization for C2 procedure) or the UAV authentication and authorization procedure (UUAA-SM procedure), Receive the PDU SESSION RELEASE REQUEST message in the UE-requested PDU session release procedure, In response to the reception of the PDU SESSION RELEASE REQUEST message, abort the C2 communication authorization or the UUAA-SM procedure, When the PDU SESSION RELEASE REQUEST message is received, perform 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, Comprising, The at least one processor, Starts a UE-requested PDU session release procedure, Receives an authentication message in the UUAA-SM procedure, Ignores the received authentication message, When the authentication message is received, is configured to perform the UE-requested PDU session release procedure, Uncrewed Aerial Vehicle (UAV). (Appendix 5-2) Starts a UE-requested PDU session release procedure, Receives an authentication message in the UUAA-SM procedure, Ignores the received authentication message, When the authentication message is received, performs the UE-requested PDU session release procedure, Method in an Uncrewed Aerial Vehicle (UAV). (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 includes, Starts a UE-requested PDU session release procedure, Receives an authentication message in the UUAA-SM procedure, Ignore the received authentication message, When the authentication message is received, perform the UE-requested PDU session release procedure, A non-transitory computer-readable medium. (Appendix 6-1) At least one memory, At least one processor coupled to the at least one memory, Comprising, The at least one processor, Starts the UE-requested PDU session release procedure, Receives an authentication message in the C2 communication authorization procedure (Authorization for C2 procedure) or the UAV authentication and authorization procedure (UUAA-SM procedure), Ignore the received authentication message, When the authentication message is received, it is configured to perform the UE-requested PDU session release procedure, Uncrewed Aerial Vehicle (UAV). (Appendix 6-2) Starts the UE-requested PDU session release procedure, Receives an authentication message in the C2 communication authorization procedure (Authorization for C2 procedure) or the UAV authentication and authorization procedure (UUAA-SM procedure), Ignore the received authentication message, When the authentication message is received, perform the UE-requested PDU session release procedure, Method in an Uncrewed Aerial Vehicle (UAV). (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 includes: Starting a UE-requested PDU session release procedure, Receiving 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, When the authentication message is received, performing the UE-requested PDU session release procedure, A non-transitory computer-readable medium. (Appendix 7-1) At least one memory, At least one processor coupled to the at least one memory, Comprising: 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 in progress, Send to the network a PDU Session Modification Command Ack or PDU SESSION MODIFICATION COMPLETE message including information indicating that it has recognized that it is in the middle of a Service-level authentication and authorization procedure (C2 communication authorization procedure). Uncrewed Aerial Vehicle (UAV). (Appendix 7-2) Receive a PDU Session Modification Command message from the network that includes information indicating that the C2 communication authentication and authorization procedure (Service-level authentication and authorization procedure) is in progress, Send a PDU Session Modification Command Ack or PDU SESSION MODIFICATION COMPLETE message to the network that includes information indicating that it has recognized that it is in the Service-level authentication and authorization procedure (C2 communication authentication and authorization procedure), A method in an Uncrewed Aerial Vehicle (UAV). (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 includes, Receive a PDU Session Modification Command message from the network that includes information indicating that the C2 communication authentication and authorization procedure (Service-level authentication and authorization procedure) is in progress, Send a PDU Session Modification Command Ack or PDU SESSION MODIFICATION COMPLETE message to the network that includes information indicating that it has recognized that it is in the Service-level authentication and authorization procedure (C2 communication authentication and 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, and incorporates the entire disclosure thereof herein.

Explanation of Reference Numerals

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

Claims

Claim 1 An Access and Mobility Management Function (AMF) node, initiates an Unmanned Aerial Vehicle Authentication and Authorization (UUAA-MM) procedure, receives a DEREGISTRATION REQUEST message from an Uncrewed Aerial Vehicle (UAV) in a UE-initiated de-registration procedure, in response to receiving the DEREGISTRATION REQUEST message, aborts the UUAA-MM procedure, when receiving the DEREGISTRATION REQUEST message, is configured to perform the UE-initiated de-registration procedure, the AMF node. Claim 2 initiates an Unmanned Aerial Vehicle Authentication and Authorization (UUAA-MM) procedure, receives a DEREGISTRATION REQUEST message from an Uncrewed Aerial Vehicle (UAV) in a UE-initiated de-registration procedure, in response to receiving the DEREGISTRATION REQUEST message, aborts the UUAA-MM procedure, when receiving the DEREGISTRATION REQUEST message, performs the UE-initiated de-registration procedure, A method in an Access and Mobility Management Function (AMF) node. Claim 3 A program for causing a computer to perform a method in an Access and Mobility Management Function (AMF) node, the method comprising: the method comprising: initiating an Unmanned Aerial Vehicle Authentication and Authorization (UUAA-MM) procedure, receiving a DEREGISTRATION REQUEST message from an Uncrewed Aerial Vehicle (UAV) in a UE-initiated de-registration procedure, in response to receiving the DEREGISTRATION REQUEST message, aborting the UUAA-MM procedure, when receiving the DEREGISTRATION REQUEST message, performing the UE-initiated de-registration procedure, the program. Claim 4 An Uncrewed Aerial Vehicle (UAV), executes the UAV authentication and authorization (UUAA-MM) procedure, when a DEREGISTRATION REQUEST message for initiating a UE-initiated de-registration procedure is sent to an Access and Mobility Management Function (AMF) node during the execution of the UUAA-MM procedure, a part of the UUAA-MM procedure is aborted and is configured to perform the UE-initiated de-registration procedure, UAV.

5. executes the UAV authentication and authorization (UUAA-MM) procedure, when a DEREGISTRATION REQUEST message for initiating a UE-initiated de-registration procedure is sent to an Access and Mobility Management Function (AMF) node during the execution of the UUAA-MM procedure, a part of the UUAA-MM procedure is aborted and performs the UE-initiated de-registration procedure, A method in an Uncrewed Aerial Vehicle (UAV).

6. A program for causing a computer to perform a method in an Uncrewed Aerial Vehicle (UAV), wherein the method executes the UAV authentication and authorization (UUAA-MM) procedure, when a DEREGISTRATION REQUEST message for initiating a UE-initiated de-registration procedure is sent to an Access and Mobility Management Function (AMF) node during the execution of the UUAA-MM procedure, a part of the UUAA-MM procedure is aborted and performs the UE-initiated de-registration procedure, program.

7. A Session Management Function (SMF) node, initiates a UAV authentication and authorization procedure in session management (UUAA-SM procedure), Receives a PDU SESSION RELEASE REQUEST message for a PDU session that provides a connection to UAS NF9 in the UE-requested PDU session release procedure, In response to receiving the PDU SESSION RELEASE REQUEST message, aborts the UUAA-SM procedure, When receiving the PDU SESSION RELEASE REQUEST message, is configured to perform the UE-requested PDU session release procedure, SMF node.

8. A Session Management Function (SMF) node, Starts a C2 communication authorization procedure (Authorization for C2 procedure) or a UAV authentication and authorization procedure (UUAA-SM procedure), Receives a PDU SESSION RELEASE REQUEST message in the UE-requested PDU session release procedure, In response to receiving the PDU SESSION RELEASE REQUEST message, aborts the C2 communication authorization or the UUAA-SM procedure, When receiving the PDU SESSION RELEASE REQUEST message, is configured to perform the UE-requested PDU session release procedure, SMF node.

9. An Uncrewed Aerial Vehicle (UAV), Starts a UE-requested PDU session release procedure, Receives an authentication message in the UUAA-SM procedure, Ignores the received authentication message, When receiving the authentication message, is configured to perform the UE-requested PDU session release procedure, UAV.

10. An Uncrewed Aerial Vehicle (UAV), Starts a UE-requested PDU session release procedure, Receive an authentication message in the C2 communication authorization procedure (Authorization for C2 procedure) or the UAV authentication and authorization procedure (UUAA-SM procedure), Ignore the received authentication message, When the authentication message is received, it is configured to perform the UE-requested PDU session release procedure, UAV.

Images