UE(User Equipment)

Abstract

The present invention solves the problem that when a USS / UTM provides information to an unmanned aerial vehicle (UAV), the procedure for providing such information is not clearly defined. When USS / UTM information cannot be transmitted to the UVA, it is possible that the UAV cannot be connected to the USS / UTM. The UAV receives USS / UTM identification information from a default USS / UTM after establishing a PDU session. The UAV stores the USS / UTM identification information in memory on the basis of the USS / UTM identification information having been received. Furthermore, the UAV and the default USS / UTM transmit and receive information to and from each other in a UAS application layer.

Description

[Technical Field]

[0001] The present invention relates to UE (User Equipment). This application claims priority to Japanese Patent Application No. 2021-12786, filed on January 29, 2021, the contents of which are incorporated herein by reference. [Background technology]

[0002] The 3GPP (3rd Generation Partnership Project) is studying the system architecture of the 5G System (5GS), a fifth-generation (5G) mobile communication system, and is discussing how to support new procedures and new functions (see Non-Patent Documents 1 to 3). Release 17 of the 5G standard discusses mobile communication systems for drones (see Non-Patent Document 4). [Prior art documents] [Non-patent literature]

[0003] [Non-Patent Document 1] 3GPP TS 23.501 V16.7.0 (2020-12); 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System Architecture for the 5G System; Stage 2 (Release 16) [Non-patent document 2] 3GPP TS 23.502 V16.7.1 (2021-01); 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for the 5G System; Stage 2 (Release 16) [Non-patent document 3] 3GPP TS 24.501 V17.1.0 (2020-12); 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 (Release 17) [Non-patent document 4] 3GPP TR 23.754 V17.0.0 (2020-12); 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on supporting Unmanned Aerial Systems (UAS) connectivity, Identification and tracking (Release 17) [Non-patent document 5] 3GPP TR 23.755 V1.0.0 (2020-12); 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on application layer support for Unmanned Aerial Systems (UAS); (Release 17) Summary of the Invention [Problem to be solved by the invention]

[0004] Non-Patent Document 5 does not clarify the procedure for USS / UTM to provide information to UAVs (Unmanned Aerial Vehicles). If USS / UTM cannot transmit information to UAVs, there is a problem that UAVs cannot obtain information from USS / UTM and may not be able to connect.

[0005] One aspect of the present invention was made in consideration of the above circumstances, and clarifies the information that a USS / UTM transmits to a UAV and the behavior of the UAV upon receiving the message. It also defines information called UAV USD and clarifies the information to be included in the UAV USD transmitted from a USS / UTM to a UAV. [Means for solving the problem]

[0006] One embodiment of the User Equipment (UE) of the present invention is an Unmanned Aerial Vehicle (UAV), and the UE is equipped with a transceiver unit and a control unit, the transceiver unit receives a UAV (Unmanned Aerial Vehicle) USD (User Service Description) from a default UTM, the UAV USD includes first identification information, the first identification information is a list of information indicating identification information of a USS (Unmanned Aerial System Service Supplier) / UTM (Unmanned Aerial System Traffic Management), and the control unit stores the first identification information based on receiving the UAV USD. [Effects of the Invention]

[0007] According to one aspect of the present invention, it is possible to clarify the information that a USS / UTM transmits to a UAV and the behavior of the UAV that receives the message. Also, it is possible to define information called UAV USD and clarify the information to be included in the UAV USD transmitted from a USS / UTM to a UAV. [Brief explanation of the drawings]

[0008] [Figure 1] FIG. 1 is a diagram illustrating an outline of a mobile communication system (EPS / 5GS). [Figure 2] FIG. 1 is a diagram illustrating the detailed configuration of a mobile communication system (EPS / 5GS). [Figure 3] FIG. 1 is a diagram illustrating the device configuration of a UE. [Figure 4] A diagram explaining the configuration of an access network device (gNB) in 5GS. [Figure 5] A diagram explaining the configuration of core network devices (AMF / SMF / UPF) in 5GS. [Figure 6] FIG. 10 is a diagram illustrating a registration procedure. [Figure 7] A diagram explaining the PDU session establishment procedure. [Figure 8] A diagram showing a network-initiated session management procedure. [Figure 9] A diagram showing a UE-initiated session management procedure. [Figure 10] FIG. 1 is a diagram illustrating a communication procedure. [Figure 11] FIG. 1 is a diagram illustrating a communication mode of a UAV. [Figure 12] This is a diagram explaining UAV USD provisioning. DETAILED DESCRIPTION OF THE INVENTION

[0009] Hereinafter, a best mode for carrying out one aspect of the present invention will be described with reference to the drawings. In this embodiment, an embodiment of a mobile communication system to which one aspect of the present invention is applied will be described as an example.

[0010] [1. System Overview] First, FIG. 1 is a diagram for explaining an outline of a mobile communication system 1 used in each embodiment, and FIG. 2 is a diagram for explaining a detailed configuration of the mobile communication system 1. As shown in FIG.

[0011] FIG. 1 shows that the mobile communication system 1 is composed of UE_A10, access network _A80, core network _A90, PDN (Packet Data Network) _A5, access network _B120, core network _B190, and DN (Data Network) _A6.

[0012] In the following, these devices and functions may be referred to by abbreviating the symbols, such as UE, access network_A, core network_A, PDN, access network_B, core network_B, DN, etc.

[0013] Figure 2 also shows devices and functions such as UE_A10, E-UTRAN80, MME40, SGW35, PGW-U30, PGW-C32, PCRF60, HSS50, 5G AN120, AMF140, UPF130, SMF132, PCF160, UDM150, and N3IWF170, as well as interfaces that connect these devices and functions to each other.

[0014] In the following, these devices and functions may be referred to by abbreviated symbols such as UE, E-UTRAN, MME, SGW, PGW-U, PGW-C, PCRF, HSS, 5G AN, AMF, UPF, SMF, PCF, UDM, N3IWF, etc.

[0015] The 4G system EPS (Evolved Packet System) includes an access network _A and a core network _A, but may further include a UE and / or a PDN. The 5G system 5GS (5G System) includes a UE, an access network _B, and a core network _B, but may further include a DN.

[0016] A UE is a device that can connect to a network service via 3GPP access (also referred to as a 3GPP access network, or 3GPP AN) and / or non-3GPP access (also referred to as a non-3GPP access network, or non-3GPP AN). A UE may be a terminal device capable of wireless communication, such as a mobile phone or a smartphone, and may be a terminal device that can connect to both EPS and 5GS. A UE may include a UICC (Universal Integrated Circuit Card) or an eUICC (Embedded UICC). Note that a UE may be referred to as a user device or a terminal device.

[0017] Furthermore, access network_A corresponds to an E-UTRAN (Evolved Universal Terrestrial Radio Access Network) and / or a wireless LAN access network. One or more eNBs (evolved Node Bs) 45 are deployed in the E-UTRAN. Note that, hereinafter, the eNB 45 may be referred to by abbreviating the symbol eNB. If there are multiple eNBs, the eNBs are connected to each other, for example, via an X2 interface. Furthermore, one or more access points are deployed in the wireless LAN access network.

[0018] Furthermore, access network_B corresponds to a 5G access network (5G AN). The 5G AN is composed of an NG-RAN (NG Radio Access Network) and / or a non-3GPP access network. One or more gNBs (NR NodeBs) 122 are deployed in the NG-RAN. Note that, hereinafter, the symbol for gNB 122 may be abbreviated, such as gNB. The gNB is a node that provides the NR (New Radio) user plane and control plane to UEs and connects to the 5GCN via an NG interface (including an N2 interface or an N3 interface). In other words, the gNB is a base station device newly designed for 5GS, and has different functions from the base station device (eNB) used in the 4G system EPS. Furthermore, when there are multiple gNBs, the gNBs are connected to each other, for example, via an Xn interface.

[0019] Furthermore, the non-3GPP access network may be an untrusted non-3GPP access network or a trusted non-3GPP access network. Here, the untrusted non-3GPP access network may be a non-3GPP access network that does not perform security management within the access network, such as a public wireless LAN. On the other hand, the trusted non-3GPP access network may be an access network specified by 3GPP, and may include a trusted non-3GPP access point (TNAP) and a trusted non-3GPP gateway function (TNGF).

[0020] In the following, E-UTRAN and NG-RAN may be referred to as 3GPP access. Also, wireless LAN access networks and non-3GPP AN may be referred to as non-3GPP access. Also, nodes located in access network_B may be collectively referred to as NG-RAN nodes.

[0021] Furthermore, in the following, access network _A, and / or access network _B, and / or devices included in access network _A, and / or devices included in access network _B may be referred to as access networks or access network devices.

[0022] The core network_A corresponds to an EPC (Evolved Packet Core), which includes, for example, an MME (Mobility Management Entity), an SGW (Serving Gateway), a PGW (Packet Data Network Gateway)-U, a PGW-C, a PCRF (Policy and Charging Rules Function), and an HSS (Home Subscriber Server).

[0023] Furthermore, the core network_B corresponds to a 5G Core Network (5GCN). In the 5GCN, for example, an Access and Mobility Management Function (AMF), a User Plane Function (UPF), a Session Management Function (SMF), a Policy Control Function (PCF), a Unified Data Management (UDM), etc. are arranged. Here, the 5GCN may be expressed as a 5GC.

[0024] In addition, in the following, core network _A and / or core network _B, devices included in core network _A, and / or devices included in core network _B may be referred to as core networks, core network devices, or devices within the core network.

[0025] The core network (core network _A and / or core network _B) may be an IP mobile communication network operated by a mobile network operator (MNO) that connects the access network (access network _A and / or access network _B) to the PDN and / or DN, or it may be a core network for a mobile network operator that operates and manages the mobile communication system 1, or it may be a core network for a virtual mobile communication operator or virtual mobile communication service provider such as an MVNO (Mobile Virtual Network Operator) or MVNE (Mobile Virtual Network Enabler).

[0026] Also, while FIG. 1 illustrates a case where the PDN and the DN are the same, they may be different. The PDN may be a DN (Data Network) that provides communication services to the UE. The DN may be configured as a packet data service network, or may be configured for each service. Furthermore, the PDN may include a connected communication terminal. Therefore, connecting to the PDN may mean connecting to a communication terminal or a server device located in the PDN. Furthermore, transmitting and receiving user data to and from the PDN may mean transmitting and receiving user data to and from a communication terminal or a server device located in the PDN. The PDN may be referred to as the DN, and the DN may be referred to as the PDN.

[0027] In addition, hereinafter, at least a portion of the access network _A, the core network _A, the PDN, the access network _B, the core network _B, and the DN, and / or one or more devices included therein may be referred to as a network or a network device. In other words, when a network and / or a network device sends or receives a message and / or performs a procedure, it means that at least a portion of the access network _A, the core network _A, the PDN, the access network _B, the core network _B, and the DN, and / or one or more devices included therein send or receive a message and / or perform a procedure.

[0028] The UE can also connect to an access network. The UE can also connect to a core network via the access network. The UE can also connect to a PDN or DN via the access network and the core network. That is, the UE can transmit and receive (communicate) user data with the PDN or DN. When transmitting and receiving user data, not only IP (Internet Protocol) communication but also non-IP communication can be used.

[0029] Here, IP communication refers to data communication using IP, and data is transmitted and received using IP packets. An IP packet consists of an IP header and a payload. The payload may include data transmitted and received by devices and functions included in EPS or devices and functions included in 5GS. Non-IP communication refers to data communication that does not use IP, and data is transmitted and received in a format different from the IP packet structure. For example, non-IP communication may be data communication achieved by transmitting and receiving application data without an IP header, or it may be user data transmitted and received by a UE with a different header, such as a MAC header or an Ethernet (registered trademark) frame header, added.

[0030] In addition, access network _A, core network _A, access network _B, core network _B, PDN_A, and DN_A may be configured with devices not shown in Fig. 2. For example, core network _A and / or core network _B may include an AUSF (Authentication Server Function) and an AAA (Authentication, authorization, and accounting) server (AAA-S).

[0031] Here, the AUSF is a core network device having an authentication function for 3GPP access and non-3GPP access, specifically, a network function unit that receives an authentication request for 3GPP access and / or non-3GPP access from a UE and executes the authentication procedure.

[0032] The AAA server is a device that has authentication, authorization, and accounting functions and is connected to the AUSF directly or indirectly via another network device. The AAA server may be a network device within the core network. The AAA server may not be included in the core network _A and / or core network _B, but may be included in the PLMN. In other words, the AAA server may be a core network device or a device outside the core network. For example, the AAA server may be a server device within the PLMN managed by a third party.

[0033] 2, for the sake of simplicity, each device and function is shown one by one, but multiple similar devices and functions may be configured in the mobile communication system 1. Specifically, the mobile communication system 1 may be configured with multiple devices and functions such as UE_A10, E-UTRAN80, MME40, SGW35, PGW-U30, PGW-C32, PCRF60, HSS50, 5G AN120, AMF140, UPF130, SMF132, PCF160, and / or UDM150.

[0034] The UPF_A235 is connected to the DN, the SMF, other UPFs, and the access network. The UPF_A235 may perform functions such as an anchor for intra-RAT mobility or inter-RAT mobility, packet routing and forwarding, an UL CL (Uplink Classifier) ​​function that supports routing of multiple traffic flows for one DN, a branching point function that supports multi-homed PDU sessions, QoS processing for the user plane, verification of uplink traffic, buffering of downlink packets, and a trigger function for downlink data notification. The UPF_A235 may also be a relay device that forwards user data as a gateway between the DN and the core network_B190. The UPF_A235 may also be a gateway for IP communication and / or non-IP communication. The UPF_A235 may also have a function for forwarding IP communication and a function for converting non-IP communication to IP communication. Furthermore, multiple gateways may be gateways that connect the core network _B190 to a single DN. Note that UPF_A235 may have connectivity with other NFs and may be connected to each device via other NFs.

[0035] Between UPF_A235 and the access network, UPF_C239 (also called a branching point or uplink classifier), which is a UPF different from UPF_A235, may exist as a device or NF. When UPF_C239 exists, a PDU session between the UE and the DN will be established via the access network, UPF_C239, and UPF_A235.

[0036] Furthermore, the UPF 130 may be the same device as the UPF_A 235. Note that the UPF 130 and the UPF_A 235 may be written with the symbols omitted, such as UPF.

[0037] [2. Configuration of each device] Next, the configuration of each device (UE, and / or access network device, and / or core network device) used in each embodiment will be described with reference to the drawings. Each device may be configured as physical hardware, as logical (virtual) hardware configured on general-purpose hardware, or as software. Furthermore, at least a part (including all) of the functions of each device may be configured as physical hardware, logical hardware, or software.

[0038] Note that each memory unit (memory unit_A340, memory unit_A440, memory unit_B540, memory unit_A640, memory unit_B740) in each device / function mentioned below is configured with, for example, a semiconductor memory, a solid state drive (SSD), a hard disk drive (HDD), etc. Furthermore, each memory unit can store not only information that was originally set at the time of shipment, but also various information transmitted and received between devices / functions other than the device / function itself (e.g., UE, and / or access network device, and / or core network device, and / or PDN, and / or DN). Furthermore, each memory unit can store identification information, control information, flags, parameters, etc. included in control messages transmitted and received in various communication procedures described below. Furthermore, each memory unit may store this information for each UE. Furthermore, when interworking between 5GS and EPS is performed, each memory unit can store control messages and user data transmitted and received between 5GS and / or devices / functions included in EPS. At this time, not only those transmitted and received via the N26 interface but also those transmitted and received without going through the N26 interface can be stored.

[0039] [2.1. UE Device Configuration] First, an example of the device configuration of UE (User Equipment) will be explained using Figure 3. The UE is composed of a control unit _A300, an antenna 310, a transceiver unit _A320, and a memory unit _A340. The control unit _A300, the transceiver unit _A320, and the memory unit _A340 are connected via a bus. The transceiver unit _A320 is connected to the antenna 310.

[0040] The control unit _A300 is a functional unit that controls the operation and functions of the entire UE.The control unit _A300 realizes various processing in the UE by reading and executing various programs stored in the memory unit _A340 as necessary.

[0041] The transceiver unit _A320 is a functional unit for wireless communication with a base station device (eNB or gNB) in the access network via an antenna. That is, the UE can use the transceiver unit _A320 to transmit and receive user data and / or control information between an access network device, and / or a core network device, and / or a PDN, and / or a DN.

[0042] Explaining in detail with reference to Figure 2, the UE can communicate with a base station device (eNB) in the E-UTRAN via the LTE-Uu interface by using the transceiver unit _A320. The UE can also communicate with a base station device (gNB) in the 5G AN by using the transceiver unit _A320. The UE can also transmit and receive AMF and NAS (Non-Access-Stratum) messages via the N1 interface by using the transceiver unit _A320. However, since the N1 interface is logical, in reality, communication between the UE and the AMF is performed via the 5G AN.

[0043] The memory unit _A340 is a functional unit for storing programs, user data, control information, etc. necessary for each operation of the UE.

[0044] [2.2. gNB device configuration] Next, an example of the gNB device configuration will be described using Figure 4. The gNB is composed of a control unit _B500, an antenna 510, a network connection unit _B520, a transceiver unit _B530, and a memory unit _B540. The control unit _B500, the network connection unit _B520, the transceiver unit _B530, and the memory unit _B540 are connected via a bus. The transceiver unit _B530 is connected to the antenna 510.

[0045] The control unit _B500 is a functional unit that controls the operation and functions of the entire gNB. The control unit _B500 realizes various processes in the gNB by reading and executing various programs stored in the memory unit _B540 as necessary.

[0046] The network connection unit _B520 is a functional unit for the gNB to communicate with the AMF and / or UPF. That is, the gNB can send and receive user data and / or control information between the AMF and / or UPF using the network connection unit _B520.

[0047] The transceiver unit _B530 is a functional unit for wireless communication with the UE via the antenna 510. That is, the gNB can transmit and receive user data and / or control information to and from the UE using the transceiver unit _B530.

[0048] 2, a gNB in ​​a 5G AN can communicate with an AMF via an N2 interface by using a network connection unit _B 520, and can communicate with a UPF via an N3 interface, and can communicate with a UE by using a transceiver unit _B 530.

[0049] The memory unit _B540 is a functional unit for storing programs, user data, control information, etc. necessary for each operation of the gNB.

[0050] [2.3. AMF device configuration] Next, an example of the AMF device configuration will be explained using Figure 5. The AMF is composed of a control unit _B700, a network connection unit _B720, and a memory unit _B740. The control unit _B700, the network connection unit _B720, and the memory unit _B740 are connected via a bus. The AMF may be a node that handles the control plane.

[0051] The control unit _B700 is a functional unit that controls the operation and functions of the entire AMF.The control unit _B700 realizes various processing in the AMF by reading and executing various programs stored in the memory unit _B740 as necessary.

[0052] The network connection unit _B720 is a functional unit for the AMF to connect to a base station device (gNB), and / or SMF, and / or PCF, and / or UDM, and / or SCEF in a 5G AN. In other words, the AMF can use the network connection unit _B720 to send and receive user data and / or control information between a base station device (gNB), and / or SMF, and / or PCF, and / or UDM, and / or SCEF in a 5G AN.

[0053] Explaining in detail with reference to FIG. 2, the AMF in the 5GCN can communicate with a gNB via the N2 interface by using the network connection unit _A620, can communicate with a UDM via the N8 interface, can communicate with an SMF via the N11 interface, and can communicate with a PCF via the N15 interface. The AMF can also send and receive NAS messages with a UE via the N1 interface by using the network connection unit _A620. However, since the N1 interface is logical, communication between the UE and the AMF is actually performed via a 5G AN. Furthermore, if the AMF supports the N26 interface, it can communicate with an MME via the N26 interface by using the network connection unit _A620.

[0054] The memory unit _B740 is a functional unit for storing programs, user data, control information, etc. necessary for each operation of the AMF.

[0055] The AMF has functions such as exchanging control messages with the RAN using the N2 interface, exchanging NAS messages with the UE using the N1 interface, encrypting and protecting the integrity of NAS messages, registration management (RM) functions, connection management (CM) functions, reachability management functions, mobility management functions for UEs, etc., transferring SM (Session Management) messages between the UE and the SMF, access authentication (Access Authorization) functions, security anchor functionality (SEA), security context management (SCM), a function to support the N2 interface for the N3IWF (Non-3GPP Interworking Function), a function to support sending and receiving NAS signals with the UE via the N3IWF, and a function to authenticate UEs connected via the N3IWF.

[0056] In addition, registration management manages the RM state for each UE. The RM state may be synchronized between the UE and the AMF. The RM state includes an unregistered state (RM-DEREGISTERED state) and a registered state (RM-REGISTERED state). In the RM-DEREGISTERED state, the UE is not registered with the network, and therefore the UE context in the AMF does not have valid location information or routing information for the UE, and therefore the AMF cannot reach the UE. In the RM-REGISTERED state, the UE is registered with the network, and therefore the UE can receive services that require registration with the network. Note that the RM state may also be expressed as a 5GMM state. In this case, the RM-DEREGISTERED state may be expressed as a 5GMM-DEREGISTERED state, and the RM-REGISTERED state may be expressed as a 5GMM-REGISTERED state.

[0057] In other words, 5GMM-REGISTERED may be a state in which each device has established a 5GMM context or a PDU session context. When each device is 5GMM-REGISTERED, UE_A10 may start transmitting and receiving user data and control messages, or may respond to paging. Furthermore, when each device is 5GMM-REGISTERED, UE_A10 may perform registration procedures other than the registration procedure for initial registration, and / or service request procedures.

[0058] Furthermore, 5GMM-DEREGISTERED may be a state in which each device has not established a 5GMM context, a state in which UE_A10's location information is not known to the network, or a state in which UE_A10 is unreachable from the network. Note that when each device is 5GMM-DEREGISTERED, UE_A10 may initiate a registration procedure or may establish a 5GMM context by performing the registration procedure.

[0059] In addition, connection management manages the CM state for each UE. The CM state may be synchronized between the UE and the AMF. The CM state includes a non-connected state (CM-IDLE state) and a connected state (CM-CONNECTED state). In the CM-IDLE state, the UE is in the RM-REGISTERED state but does not have a NAS signaling connection established with the AMF via the N1 interface. In the CM-IDLE state, the UE does not have an N2 interface connection or an N3 interface connection. On the other hand, in the CM-CONNECTED state, the UE has a NAS signaling connection established with the AMF via the N1 interface. In the CM-CONNECTED state, the UE may have an N2 interface connection and / or an N3 interface connection.

[0060] Furthermore, in connection management, the CM state in 3GPP access and the CM state in non-3GPP access may be managed separately. In this case, the CM state in 3GPP access may include a non-connected state in 3GPP access (CM-IDLE state over 3GPP access) and a connected state in 3GPP access (CM-CONNECTED state over 3GPP access). Furthermore, the CM state in non-3GPP access may include a non-connected state in non-3GPP access (CM-IDLE state over non-3GPP access) and a connected state in non-3GPP access (CM-CONNECTED state over non-3GPP access). Note that the non-connected state may be expressed as an idle mode, and the connected state mode may be expressed as a connected mode.

[0061] The CM state may be expressed as a 5GMM mode. In this case, the unconnected state may be expressed as a 5GMM-IDLE mode, and the connected state may be expressed as a 5GMM-CONNECTED mode. Furthermore, the unconnected state in 3GPP access may be expressed as a 5GMM-IDLE mode over 3GPP access, and the connected state in 3GPP access may be expressed as a 5GMM-CONNECTED mode over 3GPP access. Furthermore, the unconnected state in non-3GPP access may be expressed as 5GMM unconnected mode in non-3GPP access (5GMM-IDLE mode over non-3GPP access), and the connected state in non-3GPP access may be expressed as 5GMM connected mode in non-3GPP access (5GMM-CONNECTED mode over non-3GPP access). Note that the 5GMM unconnected mode may be expressed as idle mode, and the 5GMM connected mode may be expressed as connected mode.

[0062] In addition, one or more AMFs may be placed in the core network_B. In addition, the AMF may be a Network Function (NF) that manages one or more Network Slice Instances (NSIs). In addition, the AMF may be a Common Control Plane Network Function (CCNF) shared among multiple NSIs.

[0063] In addition, the N3IWF is a device and / or function located between the non-3GPP access and the 5GCN when the UE connects to the 5GS via the non-3GPP access.

[0064] [2.4. SMF device configuration] Next, an example of the SMF device configuration will be explained using Figure 5. The SMF is composed of a control unit _B700, a network connection unit _B720, and a memory unit _B740. The control unit _B700, the network connection unit _B720, and the memory unit _B740 are connected via a bus. The SMF may be a node that handles the control plane.

[0065] The control unit _B700 is a functional unit that controls the operation and functions of the entire SMF.The control unit _B700 realizes various processing in the SMF by reading and executing various programs stored in the memory unit _B740 as necessary.

[0066] The network connection unit _B720 is a functional unit for the SMF to connect with the AMF, and / or UPF, and / or PCF, and / or UDM. In other words, the SMF can send and receive user data and / or control information between the AMF, and / or UPF, and / or PCF, and / or UDM using the network connection unit _B720.

[0067] Explaining in more detail with reference to Figure 2, the SMF in the 5GCN can communicate with the AMF via the N11 interface, with the UPF via the N4 interface, with the PCF via the N7 interface, and with the UDM via the N10 interface by using the network connection unit _A620.

[0068] The memory unit _B740 is a functional unit for storing programs, user data, control information, etc. required for each operation of the SMF.

[0069] The SMF has session management functions such as establishing, modifying, and releasing PDU sessions, IP address allocation for UEs and its management, UPF selection and control, UPF configuration for routing traffic to the appropriate destination, sending and receiving the SM portion of NAS messages, Downlink Data Notification, providing AN-specific (for each AN) SM information to be sent to the AN via the N2 interface via the AMF, determining the SSC mode (Session and Service Continuity mode) for the session, and roaming functions.

[0070] [2.5. UPF device configuration] Next, an example of the device configuration of the UPF will be explained using Figure 5. The UPF is composed of a control unit _B700, a network connection unit _B720, and a memory unit _B740. The control unit _B700, the network connection unit _B720, and the memory unit _B740 are connected via a bus. The UPF may be a node that handles the control plane.

[0071] The control unit _B700 is a functional unit that controls the operation and functions of the entire UPF.The control unit _B700 realizes various processing in the UPF by reading and executing various programs stored in the memory unit _B740 as necessary.

[0072] The network connection unit _B720 is a functional unit for the UPF to connect to a base station device (gNB), and / or SMF, and / or DN within the 5G AN. In other words, the UPF can use the network connection unit _B720 to transmit and receive user data and / or control information between the base station device (gNB), and / or SMF, and / or DN within the 5G AN.

[0073] Explaining in more detail with reference to Figure 2, a UPF in a 5GCN can communicate with a gNB via the N3 interface, with an SMF via the N4 interface, with a DN via the N6 interface, and with other UPFs via the N9 interface by using the network connection unit _A620.

[0074] The memory unit _B740 is a functional unit for storing programs, user data, control information, etc. required for each operation of the UPF.

[0075] The UPF has functions such as an anchor point for intra-RAT mobility or inter-RAT mobility, an external PDU session point for interconnecting to DNs (i.e., a gateway between DNs and core network_B that forwards user data), packet routing and forwarding, an UL CL (Uplink Classifier) ​​function that supports routing of multiple traffic flows to one DN, a branching point function that supports multi-homed PDU sessions, a QoS (Quality of Service) processing function for the user plane, an uplink traffic verification function, downlink packet buffering, and a function to trigger downlink data notifications.

[0076] The UPF may also be a gateway for IP communication and / or non-IP communication. The UPF may also have a function for forwarding IP communication and a function for converting non-IP communication and IP communication. Furthermore, multiple gateways may be gateways that connect the core network_B to a single DN. The UPF may also have connectivity with other NFs and may be connected to each device via other NFs.

[0077] The user plane refers to user data transmitted and received between a UE and a network. The user plane may be transmitted and received using a PDN connection or a PDU session. Furthermore, in the case of EPS, the user plane may be transmitted and received using the LTE-Uu interface, and / or the S1-U interface, and / or the S5 interface, and / or the S8 interface, and / or the SGi interface. Furthermore, in the case of 5GS, the user plane may be transmitted and received via the interface between the UE and the NG RAN, and / or the N3 interface, and / or the N9 interface, and / or the N6 interface. Hereinafter, the user plane may be referred to as the U-Plane.

[0078] Furthermore, the control plane refers to control messages transmitted and received to control UE communications, etc. The control plane may be transmitted and received using a Non-Access-Stratum (NAS) signaling connection between the UE and the MME. Furthermore, in the case of EPS, the control plane may be transmitted and received using the LTE-Uu interface and the S1-MME interface. Furthermore, in the case of 5GS, the control plane may be transmitted and received using the interface between the UE and the NG RAN and the N2 interface. Hereinafter, the control plane may be referred to as the control plane or the C-Plane.

[0079] Furthermore, the U-Plane (User Plane; UP) may be a communication path for transmitting and receiving user data and may be composed of multiple bearers. Furthermore, the C-Plane (Control Plane; CP) may be a communication path for transmitting and receiving control messages and may be composed of multiple bearers.

[0080] 2.6. Other Devices and / or Functions Next, other devices and / or functions and identification information will be described.

[0081] A network refers to at least a portion of an access network _B, a core network _B, and a DN. Furthermore, one or more devices included in at least a portion of an access network _B, a core network _B, and a DN may be referred to as a network or a network device. In other words, when a network transmits, receives, and / or processes messages, it may mean that devices within the network (network devices and / or control devices) transmit, receive, receive, and / or process messages. Conversely, when a device within the network transmits, receives, receives, and / or processes messages, it may mean that the network transmits, receives, receives, and / or processes messages.

[0082] In addition, an NSSF (Network Slice Selection Function) may be a network function (also referred to as an NF) that has the function of selecting a network slice that serves a UE.

[0083] Furthermore, an NWDAF (Network Data Analytics Function) may be an NF that has the function of collecting data from an NF or an application function (also referred to as an AF).

[0084] Furthermore, a PCF (Policy Control Function) may be an NF having a function of determining a policy for controlling the behavior of a network.

[0085] Furthermore, an NRF (Network Repository Function) may be an NF having a service discovery function, which may have a function of providing information about the discovered NF when receiving a discovery request for another NF from another NF.

[0086] Furthermore, the SM (Session Management) message (also referred to as a NAS (Non-Access-Stratum) SM message) may be an NAS message used in a procedure for SM, and may be a control message transmitted and received between the UE_A10 and the SMF via the AMF. Furthermore, the SM message may include a PDU session establishment request message, a PDU session establishment accept message, a PDU session establishment reject message, a PDU session modification request message, a PDU session modification command message, a PDU session modification complete message, a PDU session modification command reject message, a PDU session modification reject message, a PDU session release request message, a PDU session release reject message, a PDU session release command message, a PDU session release complete message, etc.

[0087] Furthermore, the procedure for SM or the SM procedure may include a PDU session establishment procedure, a PDU session modification procedure, and a UE-requested PDU session release procedure. Note that each procedure may be initiated by the UE or the NW.

[0088] Furthermore, an MM (Mobility management) message (also referred to as a NAS MM message) may be a NAS message used in a procedure for MM, and may be a control message transmitted and received between UE_A10 and AMF. Furthermore, the MM message may include a registration request message, a registration accept message, a registration reject message, a de-registration request message, a de-registration accept message, a configuration update command message, a configuration update complete message, a service request message, a service accept message, a service reject message, a notification message, a notification response message, etc.

[0089] In addition, the procedures for MM or MM procedures may include a registration procedure, a de-registration procedure, a generic UE configuration update procedure, an authentication and authorization procedure, a service request procedure, a paging procedure, and a notification procedure.

[0090] In addition, the 5GS (5G System) service may be a connection service provided using the core network_B190. Furthermore, the 5GS service may be a service different from the EPS service or may be a service similar to the EPS service.

[0091] In addition, non-5GS services may be services other than 5GS services, and may include EPS services and / or non-EPS services.

[0092] Also, the PDN (Packet Data Network) type indicates the type of PDN connection, and can be IPv4, IPv6, IPv4v6, or non-IP. If IPv4 is specified, it indicates that data will be sent and received using IPv4. If IPv6 is specified, it indicates that data will be sent and received using IPv6. If IPv4v6 is specified, it indicates that data will be sent and received using either IPv4 or IPv6. If non-IP is specified, it indicates that communication will not be via IP, but via a communication method other than IP.

[0093] Furthermore, a PDU (Protocol Data Unit / Packet Data Unit) session can be defined as an association between a DN that provides a PDU connectivity service and a UE, but it may also be connectivity established between a UE and an external gateway. In 5GS, a UE can transmit and receive user data to and from a DN by establishing a PDU session via an access network _B and a core network _B. Here, this external gateway may be a UPF, SCEF, or the like. The UE can transmit and receive user data to and from a device such as an application server located in the DN using the PDU session.

[0094] Each device (UE, and / or access network device, and / or core network device) may associate one or more pieces of identification information with a PDU session and manage them. These pieces of identification information may include one or more of the DNN, QoS rule, PDU session type, application identification information, NSI identification information, and access network identification information, or may further include other information. Furthermore, when multiple PDU sessions are established, the identification information associated with the PDU sessions may be the same or different.

[0095] Furthermore, the DNN (Data Network Name) may be identification information for identifying a core network and / or an external network such as a DN. Furthermore, the DNN can also be used as information for selecting a gateway such as a PGW / UPF that connects the core network B190. Furthermore, the DNN may be equivalent to an APN (Access Point Name).

[0096] Furthermore, the PDU (Protocol Data Unit / Packet Data Unit) session type indicates the type of PDU session, and can be IPv4, IPv6, Ethernet, or Unstructured. If IPv4 is specified, it indicates that data will be sent and received using IPv4. If IPv6 is specified, it indicates that data will be sent and received using IPv6. If Ethernet is specified, it indicates that Ethernet frames will be sent and received. Furthermore, Ethernet may indicate that communication using IP is not performed. If Unstructured is specified, it indicates that data will be sent and received to an application server or the like in the DN using Point-to-Point (P2P) tunneling technology. As the P2P tunneling technology, for example, UDP / IP encapsulation technology may be used. In addition to the above, the PDU session type may also include IP. IP can be specified if the UE is capable of using both IPv4 and IPv6.

[0097] A PLMN (Public Land Mobile Network) is a communication network that provides mobile radio communication services. A PLMN is a network managed by an operator, which is a communications carrier, and the operator can be identified by a PLMN ID. A PLMN that matches the MCC (Mobile Country Code) and MNC (Mobile Network Code) of a UE's IMSI (International Mobile Subscriber Identity) may be a Home PLMN (HPLMN). Furthermore, the UE may store an Equivalent HPLMN list in its USIM to identify one or more Equivalent HPLMNs (EPLMNs). A PLMN that is different from the HPLMN and / or EPLMN may be a Visited PLMN (VPLMN). A PLMN to which a UE has successfully registered may be a Registered PLMN (RPLMN).

[0098] A tracking area is a single or multiple ranges managed by the core network that can be represented by the location information of UE_A10. A tracking area may be composed of multiple cells. Furthermore, a tracking area may be an area in which control messages such as paging are broadcast, or an area in which UE_A10 can move without performing a handover procedure. Furthermore, a tracking area may be a routing area, a location area, or anything similar. Hereinafter, a tracking area may be a TA (Tracking Area). A tracking area may be identified by a TAI (Tracking Area Identity) consisting of a TAC (Tracking area code) and a PLMN.

[0099] A registration area is a collection of one or more TAs assigned to a UE by the AMF. Note that while UE_A10 is moving within one or more TAs included in the registration area, it may be able to move without sending or receiving signals for tracking area update. In other words, a registration area may be a group of information indicating areas in which UE_A10 can move without performing a tracking area update procedure. A registration area may be identified by a TAI list consisting of one or more TAIs.

[0100] The UE ID is information for identifying a UE. Specifically, for example, the UE ID may be a SUCI (Subscription Concealed Identifier), a SUPI (Subscription Permanent Identifier), a GUTI (Globally Unique Temporary Identifier), an IMEI (International Mobile Subscriber Identity), an IMEISV (IMEI Software Version), or a TMSI (Temporary Mobile Subscriber Identity). Alternatively, the UE ID may be other information set in an application or a network. Furthermore, the UE ID may be information for identifying a user.

[0101] A UAV (Unmanned Aerial Vehicle) is a flying drone. The UAV may be associated with a UAV controller. Furthermore, the UAV may be associated with the UAV controller and managed by a core network device and / or a UTM. Furthermore, when the UAV is associated with the UAV controller and managed, it may be managed as a UAS by the core network device and / or a UTM. The UAV's own information (identification information, IP address, location information, etc.) may be managed by the core network device and / or a UTM. Furthermore, the UAV may be a UE.

[0102] A UAV controller (Unmanned Aerial Vehicle controller) is a controller for operating a UAV. The UAV controller may be associated with the UAV. Furthermore, the UAV controller may be associated with the UAV and managed by a core network device and / or a UTM. Furthermore, when the UAV controller is associated with the UAV and managed, it may be managed as a UAS by the core network device and / or a UTM. The UAV controller's own information (identification information, IP address, location information, etc.) may be managed by the core network device and / or a UTM. Furthermore, the UAV controller may be a UE. Note that the UAV controller may be expressed as a UAC or a UAV-C.

[0103] An Unmanned Aerial System (UAS) may consist of a UAV and a UAV controller. The UAS may be managed by a core network device and / or a UTM. The UAS may consist of one UAV and one UAV controller.

[0104] Furthermore, a UAS (Unmanned Aerial System) may be composed of a UAV and related functions. Here, the related functions may include a C2 (command and control) link. Furthermore, the C2 (command and control) link may be a link between the UAV and a control device, or a link between the UAV and a network. Furthermore, the C2 link may be a link for remote identification.

[0105] UTM (Unmanned Aerial System Traffic Management) is a device equipped with a function for managing UAVs, UAV controllers, and / or UASs. The UTM may be a device within a core network or a DN device. The UTM may also be a device for autonomously piloting UAVs. The UTM may also be equipped with a function for managing identification information, IP addresses, location information, etc. of UAVs and / or UAV controllers, or may also be equipped with a function for managing information on UAVs and / or UAV controllers other than those mentioned above. Furthermore, the UTM may associate UAVs with UAV controllers and manage them as UASs. The UTM may also transmit information for requesting network services to a core network device.

[0106] Furthermore, a UTM may be a device that provides one or more functions or services for managing the scope of automated vehicle operation. A UTM may also be a device that has USS functionality. A UTM may also be expressed as UTM / USS and / or USS / UTM. A USS / UTM may also be expressed as "USS and / or UTM." A UTM may also be a UAS application server.

[0107] The USS (Unmanned Aerial System Service Supplier) may be a device within the UTM. The USS may be a device provided in the UTM. Furthermore, functions that can be executed by the UTM may be functions that can be executed by the USS. Furthermore, behaviors that can be executed by the UTM may be interpreted as behaviors that can be executed by the USS. When it is stated that the UTM performs processing, it may be interpreted as the USS performing the processing.

[0108] An Always-on PDU session is a PDU session for which user plane resources must be activated every time the UE transitions from 5GMM-IDLE state to 5GMM-CONNECTED state. Based on an instruction from a higher layer, the UE can request the core network and / or a core network device to establish a PDU session as an Always-on PDU session. The core network and / or a core network device determines whether a PDU session can be established as an Always-on PDU session. Here, the establishment of an Always-on PDU session may refer to the establishment of a PDU session for C2 communication. Furthermore, the establishment of an Always-on PDU session may refer to the establishment of a PDU session handling a QoS flow for C2 communication.

[0109] Here, the 5GMM-IDLE state may be a CM-IDLE state, and the 5GMM-CONNECTED state may be a CM-CONNECTED state. Furthermore, the core network device that determines whether the PDU session can be established as an Always-on PDU session may be an SMF.

[0110] Command and Control (C2) communication is a user plane communication channel for delivering messages containing command and control information for operating the UAV from a UAV controller or UTM to a UAV. Additionally, C2 communication may be a user plane communication channel for reporting telemetry data from a UAV to a UAV controller or UTM. Additionally, C2 communication may be a user plane communication channel for delivering messages containing command and control information for operating the UAV from a UAV controller via a UTM to a UAV.

[0111] Here, the C2 communication may be a communication path realized by a PDU session. Furthermore, the PDU session for the C2 communication may be realized by an Always-on PDU session. Furthermore, the establishment of a PDU session for the C2 communication may mean the establishment of an Always-on PDU session. Furthermore, the establishment of a PDU session handling a QoS flow for the C2 communication may mean the establishment of an Always-on PDU session.

[0112] The USD may include information indicating a unique identifier, which may be a serviceId attribute. The USD may also include information providing a title of a user service, which may be a name element. The USD may also include information indicating available languages ​​for the user service, which may be a serviceLanguage element. The USD may also include an access point name (APN), a data network name (DNN), and / or Single Network Slice Selection Assistance Information (S-NSSAI), which may be an accessPointName attribute. The USD may also include information listing capabilities required to use a related MBMS user service, which may be a requiredCapabilities element. The USD may also include information defining a list of access networks, which may be an accessGroup element. The USD may also include parameters used by the MBMS UE to randomize initiation and termination operations over time, which may be an initiationRandomization element or a terminationRandomization element. The USD may also include unicast server information, which may be a unicastAccessURI element. The USD may also include information identifying an application content component, which may be an r12:appComponent child element. The USD may also include information specifying a service area in which the content is available, which may be an r12:serviceArea child element. The USD may also include information identifying a service class for the delivered service, which may be a serviceClass attribute.The USD may also include information on applying a set of USDs to one USD, which may be a serviceGroup element. The USD may also include information indicating whether to send registration and deregistration, which may be a Registration element. The USD may also include information indicating a service area and / or frequency, which may be an availabilityInfo element.

[0113] A UAV (Unmanned Aerial Vehicle) USD (User Service Description) may be a USD transmitted from a USS / UTM to a UE. The UAV USD may also be information for controlling a UAV and / or a UAV controller and / or a UAS. The UAV USD may also be composed of one or more pieces of information included in the USD.

[0114] The default USS / UTM may be a device that has the function of only providing information to the UE. The default USS / UTM may simply be a USS / UTM.

[0115] The UAS application layer may be a UAS application specific layer, a UAE layer, and / or a SEAL layer. The UAS application layer may include a UAS application specific layer, a UAE layer, and / or a SEAL layer. Each layer within the UAS application layer may provide information to each other. The UE and the default USS / UTM may be connected via the U1-APP reference point, a U1-AE reference point, and / or a SEAL-UU. The UAS application layer may be a layer in which a UAE client communicates with a UAE server via the U1-AE reference point. The UAS application layer may be a layer in which a UAS application specific client communicates with a UAS application specific server via the U1-APP reference point.

[0116] The HTTP POST request message may be information transmitted and received on the UAS application layer. The HTTP POST request message may also be a message transmitted from the USS / UTM to the UE. The HTTP POST request message may also be composed of one or more pieces of information. The HTTP POST request message may also be a message transmitted and received on the established PDU session after the PDU session is established.

[0117] [2.7. Identification Information in This Embodiment] Next, the identification information transmitted, received, stored, and managed by each device in this embodiment will be described.

[0118] First, the first identification information is a UAV (Unmanned Aerial Vehicle) USD (User Service Description). The first identification information may include one or more of the second to fourth identification information. The first identification information may be included in an HTTP POST request message. The first identification information may be information transmitted from the USS / UTM to the UE. The first identification information may also be information for controlling the UAV and / or the UAV controller and / or the UAS.

[0119] The second identification information may be the identification information of a USS / UTM. The second identification information may be a list including the identification information of multiple USS / UTMs. The second identification information may be the name element of an MBMS USD. The second identification information may be information to be included in the name element of an MBMS USD.

[0120] Furthermore, the third identification information is information on an area where USS / UTM can be used. The third identification information may be a list including information on areas where multiple USS / UTMs can be used. The third identification information may be a serviceArea element of MBMS USD. The third identification information may be information included in the serviceArea element of MBMS USD.

[0121] Furthermore, the fourth identification information may be information indicating an access network. The fourth identification information may be a list of information indicating a plurality of access networks. The fourth identification information may be an accessGroup element of MBMS USD. The fourth identification information may be information to be included in the accessGroup element of MBMS USD. The fourth identification information may be information indicating that the access network is 5G-RAN. The fourth identification information may be information indicating that the access network is E-UTRAN. The fourth identification information may be information that restricts use of access networks other than the designated access network.

[0122] 3. First Embodiment [3.1. Procedures used in the first embodiment] First, procedures used in the first embodiment will be described. The procedures used in the first embodiment include a registration procedure, a PDU session establishment procedure, a PDU session modification procedure, a PDU session release procedure, UAV USD provisioning, etc. Each procedure will be described below.

[0123] In the first embodiment, as shown in FIG. 2, an example will be described in which the HSS and UDM, the PCF and PCRF, the SMF and PGW-C, and the UPF and PGW-U are configured as the same device / function (i.e., the same physical hardware, the same logical hardware, or the same software). However, the contents described in this embodiment are also applicable to cases in which these are configured as different devices / functions (i.e., different physical hardware, different logical hardware, or different software). For example, data may be transmitted and received directly between these, or may be transmitted and received via the N26 interface between the AMF and MME, or may be transmitted and received via the UE.

[0124] Next, the communication procedure will be explained using Fig. 10. Hereinafter, the communication procedure will also be referred to as the present procedure, and the present procedure includes a registration procedure, a UE-initiated PDU session establishment procedure, a session management procedure, and UAV USD provisioning. Details of the registration procedure, PDU session establishment procedure, session management procedure, and UAV USD provisioning will be described later.

[0125] Specifically, when each device executes a registration procedure (S900), the UE transitions to a state registered in the network (RM-REGISTERED state). Next, when each device executes a PDU session establishment procedure (S902), the UE establishes a PDU session with the DN that provides the PDU connection service via the core network_B190, and each device transitions to the first state (S904). Note that this PDU session is assumed to be established via the access network and UPF_A235, but is not limited to this. That is, a UPF (UPF_C239) different from UPF_A235 may exist between UPF_A235 and the access network. In this case, this PDU session is established via the access network, UPF_C239, and UPF_A235. Next, each device in the first state may execute a session management procedure at any timing (S906). Here, the session management procedure may be a network-initiated session management procedure or a UE-initiated session management procedure. Furthermore, each device in the first state may execute UAV USD provisioning at any timing (S908).

[0126] Each device may execute the session management procedure multiple times. For example, each device may execute a first session management procedure and then execute a second session management procedure. Here, the first session management procedure may be a network-initiated session management procedure or a UE-initiated session management procedure. Furthermore, the second session management procedure may be a network-initiated session management procedure or a UE-initiated session management procedure. Furthermore, the first session management procedure and the second session management procedure may be the same type of procedure or different types of procedures.

[0127] Note that each device may exchange various capability information and / or various request information of each device in the registration procedure and / or PDU session establishment procedure and / or network-initiated session management procedure and / or UAV USD provisioning. Furthermore, if each device exchanges various information and / or negotiates various requests in the registration procedure, it may or may not exchange various information and / or negotiate various requests in the PDU session establishment procedure and / or network-initiated session management procedure. Furthermore, if each device does not exchange various information and / or negotiate various requests in the registration procedure, it may exchange various information and / or negotiate various requests in the PDU session establishment procedure and / or network-initiated session management procedure and / or UAV USD provisioning. Furthermore, even if each device exchanges various information and / or negotiates various requests in the registration procedure, it may exchange various information and / or negotiate various requests in the PDU session establishment procedure and / or network-initiated session management procedure and / or UAV USD provisioning.

[0128] Furthermore, each device may perform the PDU session establishment procedure during the registration procedure, or may perform it after the registration procedure is completed. Furthermore, when the PDU session establishment procedure is performed during the registration procedure, the PDU session establishment request message may be included in a registration request message and transmitted / received, the PDU session establishment accept message may be included in a registration accept message and transmitted / received, the PDU session establishment complete message may be included in a registration complete message and transmitted / received, and the PDU session establishment rejection message may be included in a registration rejection message and transmitted / received. Furthermore, when the PDU session establishment procedure is performed during the registration procedure, each device may establish a PDU session based on the completion of the registration procedure, or may transition to a state in which a PDU session is established between each device.

[0129] In addition, each device involved in this procedure may send and receive each control message described in this procedure, thereby sending and receiving one or more pieces of identification information contained in each control message, and may store each sent and received piece of identification information as context.

[0130] The communication mode of the UAV in this procedure is shown in Figure 11. The UAV may be associated with a UAV controller and managed by a core network device and / or a UTM. Furthermore, when the UAV is managed in association with a UAV controller, it may be managed as a UAS by a core network device and / or a UTM.

[0131] First, the UAV is connected to a first 3GPP PLMN (S1400), and the UAV controller is connected to a second 3GPP PLMN (S1402). Furthermore, the UTM is connected to the first 3GPP PLMN and / or the second 3GPP PLMN (S1406) (S1408).

[0132] Note that communication between the UAV and the first 3GPP PLMN may be performed using a UAV1 interface (S1400). Furthermore, communication between the UAV controller and the second 3GPP PLMN may also be performed using a UAV1 interface (S1402). Furthermore, communication between the UTM and the first 3GPP PLMN and / or the second 3GPP PLMN may be performed using a UAV6 interface.

[0133] Next, the UAV and the UTM may communicate via a first 3GPP PLMN (S1410). Furthermore, the UAV controller and the UTM may communicate via a second 3GPP PLMN (S1412).

[0134] Note that communication between the UAV and the UTM may be performed using a UAV9 interface (S1410). Furthermore, communication between the UAV controller and the UTM may also be performed using a UAV9 interface (S1412).

[0135] Next, the UAV and the UAV controller may communicate with each other. Specifically, the UAV and the UAV controller may communicate with each other via a first 3GPP PLMN and a second 3GPP PLMN without via a UTM (S1404), or may communicate with each other via the first 3GPP PLMN, a UTM, and a second 3GPP PLMN (S1410) (S1412).

[0136] Note that communication between the UAV and the UAV controller via the first 3GPP PLMN and the second 3GPP PLMN without via the UTM may be performed using a UAV3 interface, and communication between the UAV and the UAV controller via the first 3GPP PLMN, the UTM, and the second 3GPP PLMN may be performed using a UAV9 interface.

[0137] Here, the UAV1 interface may be an interface connecting a UAV and / or a UAV controller with a 3GPP PLMN. Furthermore, the UAV3 interface may be an interface connecting a UAV and a UAV controller. Furthermore, the UAV6 interface may be an interface connecting a UTM and a 3GPP PLMN. Furthermore, the UAV9 interface may be an interface connecting a UAV and / or a UAV controller with a UTM.

[0138] Furthermore, the first 3GPP PLMN and the second 3GPP PLMN may be communication networks that provide mobile wireless communication services. The first 3GPP PLMN and the second 3GPP PLMN may be communication networks configured by an access network and / or a core network. Furthermore, the first 3GPP PLMN and the second 3GPP PLMN may be simply referred to as PLMNs. Here, the first 3GPP PLMN and the second 3GPP PLMN may be the same PLMN or different PLMNs.

[0139] Note that, although an example has been described above in which the PLMN to which the UAV connects and the PLMN to which the UAV controller connects are different, the PLMN to which the UAV connects and the PLMN to which the UAV controller connects may be the same PLMN. In this case, the first 3GPP PLMN and the second 3GPP PLMN described above may be the same PLMN. Furthermore, in this case, the UAV, the UAV controller, and the UTM may be connected to the same PLMN. Furthermore, in this case, the communication between the first 3GPP PLMN and the second 3GPP PLMN may be communication within the same PLMN. For example, in this case, the communication between the UAV and the UAV controller (S1404) that does not go through the UTM may be communication that is looped back within a single PLMN.

[0140] 3.2. Registration Procedures Next, the registration procedure will be described with reference to FIG. 6. In this chapter, this registration procedure may be simply referred to as this procedure. The registration procedure is a procedure initiated by the UE to register with the access network _B and / or the core network _B and / or the DN. If the UE is not registered with a network, it can execute this procedure at any time, for example, when powered on. In other words, if the UE is in a deregistered state (5GMM-DEREGISTERED state), it can start this procedure at any time. Furthermore, each device (especially the UE and the AMF) can transition to a registered state (5GMM-REGISTED state) based on the completion of the registration procedure. Note that each registration state may be managed by each device for each access. Specifically, each device may independently manage the registration state (registered state or unregistered state) for 3GPP access and the registration state for non-3GPP access.

[0141] Furthermore, the registration procedure may be a procedure for updating the location registration information of the UE in the network, and / or for the UE to periodically notify the network of the status of the UE, and / or for updating certain parameters related to the UE in the network.

[0142] The UE may initiate the registration procedure when performing mobility across TAs. In other words, the UE may initiate the registration procedure when it moves to a TA different from the TA indicated in the TA list it holds. Furthermore, the UE may initiate the registration procedure when the context of each device needs to be updated due to PDU session disconnection or invalidation. Furthermore, the UE may initiate the registration procedure when there is a change in the capability information and / or preferences related to the UE's PDU session establishment. Furthermore, the UE may initiate the registration procedure periodically. Furthermore, the UE may initiate the registration procedure based on the completion of the registration procedure, the completion of the PDU session establishment procedure, or information received from the network during each procedure. However, the UE is not limited to these, and may perform the registration procedure at any timing.

[0143] The procedure for the UE to transition from a state where it is not registered in the network (unregistered state) to a state where it is registered (registered state) may be an initial registration procedure or a registration procedure for initial registration. Furthermore, the registration procedure executed when the UE is registered in the network (registered state) may be a registration procedure for mobility and periodic registration update or a mobility and periodic registration procedure.

[0144] First, the UE starts the registration procedure by transmitting a registration request message to the AMF (S600) (S602) (S604). Specifically, the UE transmits an RRC message including a registration request message to a base station device (also referred to as a 5G AN or gNB) (S600). The registration request message is a NAS message transmitted and received on the N1 interface. The RRC message may be a control message transmitted and received between the UE and the base station device. The NAS message is processed in the NAS layer, and the RRC message is processed in the RRC layer. The NAS layer is a layer higher than the RRC layer.

[0145] Here, the UE may transmit a registration request message and / or an RRC message including identification information indicating the type of this procedure. Here, the identification information indicating the type of this procedure may be a 5GS registration type IE (Information Element), and may be information indicating that this procedure is a registration procedure for initial registration, for updating registration information due to movement, for periodic registration information update, or for emergency registration.

[0146] The UE may include UE capability information in the registration request message to inform the network of the capabilities that the UE supports, where the UE capability information may be a 5GMM capability IE for 5GS.

[0147] The UE may transmit this identification information by including it in a control message different from the above, for example, a control message of a layer lower than the RRC layer (for example, a Medium Access Control (MAC) layer, a Radio Link Control (RLC) layer, a Packet Data Convergence Protocol (PDCP) layer, a Service Data Adaptation Protocol (SDAP) layer, etc.) Note that by transmitting this identification information, the UE may indicate that it supports each function, may indicate a request from the UE, or may indicate both of these.

[0148] The UE may transmit, for example, a UE ID and / or a PLMN ID and / or an AMF identification information in the registration request message and / or the RRC message. Here, the AMF identification information may be information for identifying an AMF or a set of AMFs, and may be, for example, a 5G-S-TMSI (5G S-Temporary Mobile Subscription Identifier) ​​or a GUAMI (Globally Unique AMF Identifier).

[0149] When the base station device receives an RRC message including a registration request message, it selects an AMF to which to transfer the registration request message (S602). The base station device extracts the registration request message from the received RRC message and transfers the registration request message to the selected AMF (S604).

[0150] When the AMF receives the registration request message, the AMF may perform a first condition determination. The first condition determination is for determining whether the network accepts the UE's request. When the AMF determines that the first condition determination is true, the AMF may perform the procedures from S610 to S612. Also, when the AMF determines that the first condition determination is false, the AMF may perform the procedure of S610.

[0151] In addition, the first condition determination may be performed by a network function (also referred to as NF) other than the AMF. The NF may be, for example, a Network Slice Selection Function (NSSF), a Network Data Analytics Function (NWDAF), or a Policy Control Function (PCF). When an NF other than the AMF performs the first condition determination, the AMF may provide the NF with information necessary to perform the first condition determination, specifically, at least a portion of the information received from the UE (S606). Then, when the NF determines whether the first condition determination is true or false based on the information received from the AMF, it may convey information including the result of the first condition determination (i.e., true or false) to the AMF. The AMF may determine identification information and / or a control message to be transmitted to the UE based on the result of the first condition determination received from the NF.

[0152] If the first condition determination is true, the control message transmitted and received in S610 may be a Registration accept message, and if the first condition determination is false, the control message transmitted and received in S610 may be a Registration reject message.

[0153] Furthermore, the first condition determination may be performed based on the receipt of a registration request message, and / or each identification information contained in the registration request message, and / or subscriber information, and / or network capability information, and / or operator policy, and / or network status, and / or user registration information, and / or context held by the AMF, etc.

[0154] For example, if the network permits the UE's request, the first condition determination may be determined as true, and if the network does not permit the UE's request, the first condition determination may be determined as false. Furthermore, if the network to which the UE is registered and / or a device within the network supports the function requested by the UE, the first condition determination may be determined as true, and if the function requested by the UE is not supported, the first condition determination may be determined as false. Furthermore, if the identification information to be transmitted and received is permitted, the first condition determination may be determined as true, and if the identification information to be transmitted and received is not permitted, the first condition determination may be determined as false.

[0155] In addition, the AMF may indicate that the UE's request has been accepted by sending a registration acceptance message, or may indicate that the UE's request has been rejected by sending a registration rejection message, based on the received identification information, and / or subscriber information, and / or network capability information, and / or operator policy, and / or network status, and / or user registration information, and / or context held by the AMF, etc.

[0156] The UE receives a control message (a registration acceptance message or a registration rejection message) via the base station device (S610). If the control message is a registration acceptance message, the UE can recognize by receiving the registration acceptance message that the UE's request in the registration request message has been accepted and the contents of various identification information included in the registration acceptance message. If the control message is a registration rejection message, the UE can recognize by receiving the registration rejection message that the UE's request in the registration request message has been rejected and the contents of various identification information included in the registration rejection message.

[0157] If the control message is a registration accept message, the UE may further transmit a registration complete message to the AMF via the first base station device as a response message to the registration accept message (S612). Here, the registration complete message is an NAS message transmitted and received on the N1 interface, but may be transmitted and received between the UE and the first base station device by being included in an RRC message.

[0158] The AMF receives the registration completion message via the first base station device (S612). Furthermore, each device completes this procedure based on the transmission and reception of the registration acceptance message and / or the registration completion message.

[0159] Additionally, each device may complete the registration procedure based on sending and receiving a registration rejection message.

[0160] Each device may transition to or maintain a state in which the UE is registered in the network (RM_REGISTERED state or 5GMM-REGISTERED state) based on the transmission and reception of a registration accept message and / or a registration complete message, or may transition to or maintain a state in which the UE is not registered in the network on the access from which the registration reject message was received for the current PLMN (RM_DEREGISTERED state or 5GMM-DEREGISTERED state) based on the transmission and reception of a registration reject message. Also, the transition to each state of each device may be based on the transmission and reception of a registration complete message or the completion of the registration procedure.

[0161] Furthermore, each device may perform processing based on the information transmitted and received during the registration procedure based on the completion of the registration procedure. For example, if the device transmits or receives information indicating that some of the UE's requests have been rejected, the device may recognize the reason why the UE's requests have been rejected. Furthermore, each device may perform this procedure again based on the reason why the UE's requests have been rejected, or may perform the registration procedure for core network_A or another cell.

[0162] Furthermore, the UE may store the identification information received with the registration accept message and / or the registration reject message and may recognize the network's decision based on the completion of the registration procedure.

[0163] The registration procedure described in this chapter may be a registration procedure for initial registration, or a registration procedure for movement and periodic registration.

[0164] [3.3. PDU Session Establishment Procedure] The behavior of each device when a UE executes a PDU session establishment procedure will be explained using Figure 7. In this chapter, the PDU session establishment procedure may be simply referred to as this procedure or the PDU session establishment procedure.

[0165] This procedure may be performed after the registration procedure in Section 3.2 has been performed one or more times.

[0166] First, the UE sends a PDU session establishment request message to the SMF to initiate the PDU session establishment procedure, and then the SMF receives the PDU session establishment request message from the UE.

[0167] Specifically, the UE initiates the PDU session establishment procedure by sending a NAS message including an N1 SM container containing a PDU session establishment request message to the AMF via the access network (S800). The NAS message is, for example, a message sent via the N1 interface and may be an uplink NAS transport (UL NAS TRANSPORT) message.

[0168] Here, the access network may be a 3GPP access or a non-3GPP access and may include a base station device, that is, the UE sends a NAS message to the AMF via the base station device.

[0169] Furthermore, when the UE requests establishment of a PDU session supporting C2 communication, the UE may request establishment of an Always-on PDU session. In other words, when the UE requests establishment of a PDU session supporting a QoS flow for C2 communication, the UE may request establishment of an Always-on PDU session.

[0170] Furthermore, when the UE requests establishment of a PDU session that provides C2 communication, the UE may request establishment of an Always-on PDU session. In other words, when the UE requests establishment of a PDU session that provides a QoS flow for performing C2 communication, the UE may request establishment of an Always-on PDU session.

[0171] Next, when the AMF receives the NAS message, it can recognize what the UE is requesting and / or the contents of the information contained in the NAS message (message, container, information, etc.).

[0172] Next, the AMF selects an SMF as a transfer destination for at least part of the information, etc. (message, container, information) included in the NAS message received from the UE (S802). The AMF may select the transfer destination SMF based on the information, etc. (message, container, information) included in the NAS message, and / or subscriber information, and / or network capability information, and / or UE policy, and / or operator policy, and / or network status, and / or user registration information, and / or context held by the AMF, etc.

[0173] Next, the AMF sends at least a portion of the information (message, container, information) contained in the NAS message received from the UE to the selected SMF, for example via the N11 interface (S804).

[0174] Next, when the SMF receives information (messages, containers, information) sent from the AMF, it can recognize what the UE is requesting and / or the content of the information (messages, containers, information) received from the AMF.

[0175] Here, the SMF may perform a second condition determination. The second condition determination may be for determining whether the network accepts the UE request. If the SMF determines that the second condition determination is true, it may start the procedure of (A) in Figure 7, and if the SMF determines that the second condition determination is false, it may start the procedure of (B) in Figure 7.

[0176] Note that the second condition determination may be performed by an NF other than the SMF. The NF may be, for example, an NSSF, an NWDAF, a PCF, or an NRF. When an NF other than the SMF performs the second condition determination, the SMF may provide the NF with information necessary for performing the second condition determination, specifically, at least a portion of the information received from the UE (S806). Then, when the NF determines whether the second condition determination is true or false based on the information received from the SMF, it may convey information including the result of the second condition determination (i.e., true or false) to the SMF. The SMF may determine identification information and / or a control message to be transmitted to the UE based on the result of the second condition determination received from the NF.

[0177] Furthermore, the second condition determination may be performed based on information received from the AMF (message, container, information), and / or subscription information, and / or network capability information, and / or UE policy, and / or operator policy, and / or network status, and / or user registration information, and / or context held by the SMF, etc.

[0178] For example, if the network permits the UE's request, the second condition determination may be determined as true, and if the network does not permit the UE's request, the second condition determination may be determined as false. Furthermore, if the network to which the UE is connected and / or a device within the network supports the function requested by the UE, the second condition determination may be determined as true, and if the function requested by the UE is not supported, the second condition determination may be determined as false. Furthermore, if the transmitted and received identification information is permitted, the second condition determination may be determined as true, and if the transmitted and received identification information is not permitted, the second condition determination may be determined as false.

[0179] The conditions for determining whether the second condition is true or false are not limited to the above-mentioned conditions.

[0180] Next, each step of the procedure in FIG. 7(A) will be explained.

[0181] Next, the SMF may select a UPF for the PDU session to be established and send an N4 session establishment request message to the selected UPF, for example, via the N4 interface (S808). The N4 session establishment request message may include at least a portion of the PCC rules received from the PCF.

[0182] Here, the SMF may select one or more UPFs based on information received from the AMF (message, container, information), and / or information such as PCC rules received from the PCF, and / or subscriber information, and / or network capability information, and / or UE policy, and / or operator policy, and / or network status, and / or user registration information, and / or context held by the SMF, etc. If multiple UPFs are selected, the SMF may send an N4 session establishment request message to each UPF. Here, it is assumed that a UPF is selected.

[0183] Next, when the UPF receives the N4 session establishment request message (S808), it can recognize the content of the information received from the SMF. Furthermore, based on the reception of the N4 session establishment request message, the UPF may send an N4 session establishment response message to the SMF, for example, via the N4 interface (S810).

[0184] Next, when the SMF receives an N4 session establishment response message as a response message to the N4 session establishment request message, it can recognize the contents of the information received from the UPF.

[0185] Next, the SMF sends a PDU session establishment accept message to the UE based on receiving the PDU session establishment request message, and / or selecting a UPF, and / or receiving the N4 session establishment response message, etc. Then, the UE receives the PDU session establishment accept message from the SMF.

[0186] Specifically, the SMF sends an N1 SM container, N2 SM information, and / or a PDU session ID to the AMF, for example, via the N11 interface, based on receiving a PDU session establishment request message, selecting a UPF, and / or receiving an N4 session establishment response message (S812). Here, the N1 SM container may include a PDU session establishment accept message. Furthermore, the PDU session ID may be included in the PDU session establishment accept message.

[0187] Next, the AMF that has received the N1 SM container, and / or the N2 SM information, and / or the PDU session ID, transmits a NAS message to the UE via a first base station device included in the access network (S814) (S816). Here, the NAS message is transmitted, for example, via the N1 interface. The NAS message may be a downlink NAS transport (DL NAS TRANSPORT) message.

[0188] Specifically, the AMF transmits an N2 PDU session request message to a base station device included in the access network (S814). The base station device that receives the N2 PDU session request message transmits an NAS message to the UE (S816). Here, the N2 PDU session request message may include an NAS message and / or N2 SM information. The NAS message may also include a PDU session ID and / or an N1 SM container.

[0189] The PDU session establishment acceptance message may be a response message to a PDU session establishment request, and may indicate that the establishment of the PDU session has been accepted.

[0190] Here, the SMF and / or AMF may indicate that at least part of the UE's request in the PDU session establishment request message has been accepted by sending a PDU session establishment acceptance message, and / or an N1 SM container, and / or a PDU session ID, and / or an NAS message, and / or N2 SM information, and / or an N2 PDU session request message.

[0191] Here, the SMF and / or AMF may include the first to fourth identification information in the PDU session establishment accept message, and / or the N1 SM container, and / or the NAS message, and / or the N2 SM information, and / or the N2 PDU session request message and send it. Here, the first to fourth identification information may be as described in Chapter 2.7.

[0192] By transmitting these identification information and / or the PDU session establishment acceptance message, the SMF may indicate that the network supports each function, that the UE request has been accepted, that the UE request has not been permitted, or a combination of these. Furthermore, when multiple identification information is transmitted and received, two or more of these identification information may be configured as one or more identification information. Note that the information indicating support of each function and the information indicating a request for use of each function may be transmitted and received as the same identification information or as different identification information.

[0193] Furthermore, the SMF and / or AMF may determine which identification information to include in the PDU session establishment acceptance message, and / or the N1 SM container, and / or the NAS message, and / or the N2 SM information, and / or the N2 PDU session request message based on each received identification information, and / or subscriber information, and / or network capability information, and / or UE policy, and / or operator policy, and / or network status, and / or user registration information, and / or context held by the SMF and / or AMF, etc.

[0194] Next, when the UE receives the NAS message (S816), for example via the N1 interface, it can recognize that the UE's request via the PDU session establishment request message has been accepted and / or the contents of the information, etc. (message, container, information) contained in the NAS message.

[0195] Next, each step of the procedure in FIG. 7B will be explained.

[0196] First, based on receiving the PDU session establishment request message, the SMF sends an N1 SM container and / or a PDU session ID to the AMF, for example, via the N11 interface (S818). Here, the N1 SM container may include a PDU session establishment rejection message. Furthermore, the PDU session ID may be included in the PDU session establishment rejection message.

[0197] Next, the AMF that has received the N1 SM container and / or the PDU session ID transmits a NAS message to the UE via a base station device included in the access network (S820) (S822). Here, the NAS message is transmitted, for example, via an N1 interface. The NAS message may be a downlink NAS transport (DL NAS TRANSPORT) message. The NAS message may include the PDU session ID and / or the N1 SM container.

[0198] The PDU session establishment rejection message may be a response message to a PDU session establishment request, and may indicate that the establishment of the PDU session has been rejected.

[0199] Here, the SMF and / or AMF may indicate that the UE's request via the PDU session establishment request message has been rejected by sending a PDU session establishment rejection message, and / or an N1 SM container, and / or a PDU session ID, and / or an NAS message.

[0200] Furthermore, by sending a PDU session establishment rejection message, the SMF may indicate that the UE request has been rejected, or that the request from the UE has not been permitted, or may indicate a combination of these.

[0201] Furthermore, the SMF and / or AMF may determine which identification information to include in the PDU session establishment rejection message, and / or the N1 SM container, and / or the NAS message, and / or the N2 SM information, and / or the N2 PDU session request message based on each received identification information, and / or subscriber information, and / or network capability information, and / or UE policy, and / or operator policy, and / or network status, and / or user registration information, and / or context held by the SMF and / or AMF, etc.

[0202] Next, when the UE receives the NAS message (S822), for example via the N1 interface, it can recognize that the UE's request via the PDU session establishment request message has been rejected and / or the contents of the information, etc. (message, container, information) contained in the NAS message.

[0203] Each device may complete this procedure based on sending and receiving a PDU session establishment acceptance message. At this time, each device may transition to a state in which it can communicate with the DN using the established PDU session.

[0204] Each device may complete this procedure based on sending and receiving a PDU session establishment acceptance message or a PDU session establishment rejection message. At this time, each device cannot establish a PDU session, and therefore cannot communicate with the DN if there is no already established PDU session.

[0205] In addition, each of the processes performed by the UE based on the reception of each identification information shown above may be performed during this procedure or after completion of this procedure, or may be performed after completion of this procedure based on the completion of this procedure.

[0206] [3.4. Overview of Network-Initiated Session Management Procedures] Next, an overview of the network-initiated session management procedure will be explained. Hereinafter, the network-initiated session management procedure will also be referred to as this procedure. This procedure is a procedure for session management that is initiated by the network for an established PDU session.

[0207] This procedure may be a network-initiated PDU session modification procedure and / or a network-initiated PDU session release procedure, or may execute other network-initiated session management procedures, including but not limited to these. Each device may send and receive a PDU session modification message in the network-initiated PDU session modification procedure, or may send and receive a PDU session release message in the network-initiated PDU session release procedure.

[0208] If this procedure is a network-initiated PDU session modification procedure, the session management request message in this procedure may be a PDU session modification command (PDU SESSION MODIFICATION COMMAND) message.If this procedure is a network-initiated PDU session release procedure, the session management request message in this procedure may be a PDU session release command (PDU SESSION RELEASE COMMAND) message.

[0209] If this procedure is a network-initiated PDU session modification procedure, the session management completion message in this procedure may be a PDU session modification complete (PDU SESSION MODIFICATION COMPLETE) message.If this procedure is a network-initiated PDU session release procedure, the session management completion message in this procedure may be a PDU session release complete (PDU SESSION RELEASE COMPLETE) message.

[0210] In addition, in this procedure, the UE may be a UAV or a UAV controller.

[0211] [3.4.1. Network-Initiated Session Management Procedure Example] An example of a network-initiated session management procedure will be explained using Figure 8. In this chapter, this procedure refers to the network-initiated session management procedure. Each step of this procedure will be explained below.

[0212] Based on the completion of the registration procedure and / or PDU session establishment procedure, the UE and each device in the core network _B190 initiate a network-initiated session management procedure at any time.

[0213] Specifically, a device in core network _B190 may initiate this procedure based on receiving a PDU session change request message, or may initiate this procedure based on receiving a PDU session release request message. Note that if this procedure is initiated based on receiving a PDU session change request message, this procedure may be a network-initiated PDU session change procedure. Furthermore, if this procedure is initiated based on receiving a PDU session release request message, this procedure may be a network-initiated PDU session release procedure.

[0214] Furthermore, a device within core network _B190 may initiate this procedure based on a request from a device in the DN or another device within the core network. Specifically, a device within core network _B190 may initiate this procedure based on a request from a UTM. In other words, a device within core network _B190 may also initiate this procedure when it receives a request from a UTM.

[0215] Here, the device in the core network _B 190 that initiates this procedure may be an SMF and / or an AMF, and the UE may send and receive messages in this procedure via the AMF and / or the access network _B. Furthermore, the device in the DN may be an AF (Application Function) in the DN.

[0216] An apparatus within core network _B190 sends a network-initiated session management request message to the UE (S1202) to start network-initiated session management. Further, the UE receives a network-initiated session management request message from an apparatus within core network _B190.

[0217] Here, the device in core network _B190 may include at least one of the first to fourth identification information in the network-initiated session management request message, or may indicate a request from core network _B190 by including this identification information. Further, the device in core network _B190 may include a PDU session ID in the network-initiated session management request message, or may request a change to be made to the PDU session identified by the PDU session ID by including the PDU session ID.

[0218] The PDU session ID included in the PDU session change request message may be the PDU session ID of the established PDU session. Furthermore, if this procedure is performed based on a UE-initiated session management procedure, the PDU session ID included in the PDU session change request message may be the same as the PDU session ID included in the PDU session change request message or the PDU session release request message.

[0219] Next, the UE that has received the network-initiated session management request message sends a network-initiated session management complete message (S1204). Furthermore, the UE may perform a first process based on at least one of the first to fourth identification information received from the core network_B190 (S1206) to complete this procedure. The UE may also perform the first process based on the completion of this procedure.

[0220] Here, the UE may include a PDU session ID in the network initiated session management complete message, which may be the same as the PDU session ID included in the network initiated session management request message.

[0221] An example of the first process will be described below.

[0222] Here, the first processing may be a processing in which the UE recognizes something indicated by the core network _B190, or a processing in which the UE recognizes a request from the core network _B190. Furthermore, the first processing may be a processing in which the UE stores the received identification information as context, or a processing in which the UE forwards the received identification information to a higher layer and / or a lower layer.

[0223] Furthermore, each device may perform a process based on the identification information transmitted and received in this procedure based on completion of this procedure. In other words, the UE may perform a first process based on completion of this procedure, or may complete this procedure after completing the first process.

[0224] Furthermore, each device completes the first network-initiated session management procedure based on the completion of the above-mentioned processing and / or the sending and receiving of a network-initiated session management request message and / or a network-initiated session management completion message.

[0225] [3.5. Overview of UE-led Session Management Procedures] Next, an overview of the UE-initiated session management procedure will be described. Hereinafter, the UE-initiated session management procedure will also be referred to as this procedure. This procedure is a procedure for session management that is initiated by the UE for an established PDU session.

[0226] This procedure may be a UE-initiated PDU session modification procedure and / or a UE-initiated PDU session release procedure, or may be a UE-initiated session management procedure, including but not limited to these. Each device may transmit and receive a PDU session modification request message, a PDU session modification command message, a PDU session modification complete message, and / or a PDU session modification rejection message in the UE-initiated PDU session modification procedure. Each device may transmit and receive a PDU session release request message, a PDU session release command message, a PDU session release complete message, and / or a PDU session release rejection message in the UE-initiated PDU session release procedure.

[0227] Furthermore, each device completes the UE-initiated session management procedure based on the completion of the above-mentioned processing and / or the sending and receiving of a UE-initiated session management request message and / or a UE-initiated session management completion message.

[0228] [3.5.1. Example of UE-initiated PDU session change procedure] In this chapter, this procedure refers to the UE-initiated PDU session modification procedure. Each step of this procedure will be explained below with reference to Figure 9.

[0229] In addition, based on the completion of the registration procedure and / or the PDU session establishment procedure, the UE can initiate a UE-initiated PDU session modification procedure at any timing. In other words, the UE may initiate a UE-initiated PDU session modification procedure for an established PDU session at any timing. In other words, the UE may initiate a UE-initiated PDU session modification procedure using the same PDU session ID as the established PDU session at any timing.

[0230] First, the UE initiates a UE-initiated PDU session modification procedure by sending a PDU session modification request message to the SMF (S1302). Here, the UE may include a PDU session ID in the PDU session modification request message, or may include the PDU session ID to request a change to be made to the PDU session identified by the PDU session ID.

[0231] Furthermore, the PDU session ID included in the PDU session change request message may be the PDU session ID of an established PDU session.

[0232] In addition, the UE may not transmit a PDU session change request message when in flight, in other words, the UE may be configured to prohibit transmission of a PDU session change request message when in flight.

[0233] Here, the UE may detect that it is in flight at a layer lower than the NAS layer (e.g., RRC layer, MAC layer, RLC layer, PDCP layer, SDAP layer, etc.) or at a layer higher than the NAS layer (e.g., transport layer, session layer, presentation layer, application layer, etc.).

[0234] The UE may also detect that it is in flight based on receiving a control message requesting flight before the procedure is performed. In other words, the UE may detect that it is in flight if it receives a control message requesting flight before the procedure is performed.

[0235] The UE may also detect that it is in flight based on receiving a control message requesting flight at a layer lower than the NAS layer (e.g., RRC layer, MAC layer, RLC layer, PDCP layer, SDAP layer, etc.) or a layer higher than the NAS layer (e.g., transport layer, session layer, presentation layer, application layer, etc.) before this procedure is performed. In other words, the UE may detect that it is in flight if it receives a control message requesting flight at a layer lower than the NAS layer (e.g., RRC layer, MAC layer, RLC layer, PDCP layer, SDAP layer, etc.) or a layer higher than the NAS layer (e.g., transport layer, session layer, presentation layer, application layer, etc.) before this procedure is performed.

[0236] Next, the SMF receives the PDU session modification request message sent by the UE. If the SMF accepts the UE request, it initiates a network-initiated PDU session modification procedure. Conversely, if the SMF rejects the UE request, it sends a PDU session modification rejection message to the UE. The following describes the case where the SMF rejects the UE request.

[0237] Based on the acceptance of the PDU session establishment request message, the SMF sends a PDU session change rejection message to the UE (S1304).

[0238] Here, the PDU session ID included in the PDU session change reject message may be the same as the PDU session ID included in the PDU session change request message, i.e., the PDU session ID included in the PDU session change reject message may be the same as the PDU session ID provided by the UE during this procedure.

[0239] The UE receives the PDU session modification rejection message, and each device completes the procedure based on the transmission and reception of the PDU session modification rejection message and / or the completion of the network-initiated PDU session modification procedure.

[0240] Here, the UE may recognize that the UE request has been rejected based on receiving the PDU session modification reject message, and may perform a second process based on receiving the PDU session modification reject message, which may be performed based on completing the procedure.

[0241] Here, the second process may be a process in which the UE recognizes the matter indicated by the SMF. Furthermore, the second process may be a process in which the UE stores the received identification information as context, or may be a process in which the UE forwards the received identification information to a higher layer and / or a lower layer. Furthermore, the second process may be a process in which the UE recognizes that the request for this procedure has been rejected.

[0242] Furthermore, a PDU session change procedure and / or a PDU session release procedure for the same PDU session may refer to a PDU session change procedure and / or a PDU session release procedure using the same PDU session ID.

[0243] Furthermore, each device completes the UE-initiated PDU session modification procedure based on the completion of the above-mentioned processing and / or the sending and receiving of a UE-initiated PDU session modification rejection message.

[0244] [3.5.2. Example of UE-initiated PDU session release procedure] In this chapter, this procedure refers to the UE-initiated PDU session release procedure. Each step of this procedure is described below.

[0245] The UE-initiated PDU session release procedure may be a procedure similar to the PDU session modification procedure described above.

[0246] Specifically, if this procedure is a UE-initiated PDU session release procedure, the aforementioned PDU session modification request message may be read as a PDU session release request message. Furthermore, if this procedure is a UE-initiated PDU session release procedure, the aforementioned PDU session modification request message may be read as a PDU session release request message, and the aforementioned PDU session modification rejection message may be read as a PDU session release rejection message. Furthermore, the behavior of modifying a PDU session may be read as a behavior of releasing a PDU session.

[0247] Furthermore, if this procedure is a UE-initiated PDU session release procedure, the behavior of the SMF performed upon receipt of a PDU session release request message may be the same as the behavior of the SMF performed upon receipt of the PDU session modification request message described above. Furthermore, if this procedure is a UE-initiated PDU session release procedure, the behavior of the UE performed upon receipt of a PDU session release rejection message may be the same as the behavior of the UE performed upon receipt of the PDU session modification rejection message described above.

[0248] Furthermore, if this procedure is a UE-initiated PDU session release procedure, the SMF may initiate a network-initiated PDU session release procedure based on receiving a PDU session release request message, or may send a PDU session release rejection message to the UE.

[0249] Furthermore, each device completes the UE-initiated PDU session release procedure based on the completion of the above-mentioned processing and / or the sending and receiving of a UE-initiated PDU session release rejection message.

[0250] [3.6. UAV USD provisioning] The behavior of each device when a UE performs UAV USD provisioning will be described with reference to Figure 12. In this chapter, UAV USD provisioning may be simply referred to as this procedure or USS / UTM provisioning.

[0251] Furthermore, this procedure may be performed after the registration procedure and / or PDU session establishment procedure have been performed one or more times.

[0252] Furthermore, the default USS / UTM may be a device that has the function of only providing information to the UE, or may simply be a USS / UTM.

[0253] This procedure may be initiated when the UE does not have USS / UTM information and the USS / UTM provides the information to the UE in order to connect to the USS / UTM. Specifically, this procedure may be initiated based on the UE requesting USS / UTM information from the USS / UTM. This procedure may also be initiated based on the establishment of a communication path after the registration procedure and / or PDU session establishment procedure between the UE and USS / UTM. The default USS / UTM may also periodically initiate this procedure. The default USS / UTM may also initiate this procedure based on the completion of the registration procedure or the PDU session establishment procedure, or based on information received from the network during each procedure.

[0254] Furthermore, based on the completion of this procedure, the UE may perform a registration procedure, and / or a PDU session establishment procedure, and / or a UE-initiated session management procedure, and / or a network-initiated session management procedure at any time. Furthermore, based on the completion of this procedure, the UE may transition to a state in which it has received a UAV USD. Furthermore, based on the completion of this procedure, the UE may store or update the UAV USD. Specifically, based on the completion of this procedure, the UE may delete the old UAV USD and store a new UAV USD. Furthermore, based on the completion of this procedure, the default USS / UTM may instruct the core network device to perform a network-initiated session management procedure at any time. Furthermore, based on the completion of this procedure, the USS / UTM may transition to a state in which it has sent a UAV USD.

[0255] First, the default USS / UTM sends an HTTP POST request message to the UE. The default USS / UTM may include at least one of the first to fourth identification information in the HTTP POST request message. The default USS / UTM may send at least one of the first to fourth identification information to the UE.

[0256] When notifying a UE of information, the default USS / UTM may include at least one of the first to fourth identification information in the HTTP POST request message. When notifying a UE of the identification information of the USS / UTM, the default USS / UTM may include the second identification information in the HTTP POST request message. When notifying a UE of information on an area in which the USS / UTM can be used, the default USS / UTM may include the third identification information in the HTTP POST request message. When notifying a UE of information indicating an access network, the default USS / UTM may include the fourth identification information in the HTTP POST request message. When requested by a UE to provide information, the default USS / UTM may include at least one of the first to fourth identification information in the HTTP POST request message. When requested by a core network device to provide information, the default USS / UTM may include at least one of the first to fourth identification information in the HTTP POST request message. Furthermore, if the information stored in the default USS / UTM is changed, the default USS / UTM may include at least one of the first to fourth pieces of identification information in the HTTP POST request message. Furthermore, if the information in another USS / UTM is changed, the default USS / UTM may include at least one of the first to fourth pieces of identification information in the HTTP POST request message.

[0257] Then, the UE may receive at least one of the first to fourth identification information from the default USS / UTM (S1502).

[0258] Specifically, the UE performs a registration procedure and a PDU session establishment procedure to enable communication with the default USS / UTM. Then, the default USS / UTM may transmit at least one of the first to fourth pieces of identification information to the UE via the UAS application layer. The first identification information may include USD information. The first to fourth pieces of identification information may be included in the HTTP POST request.

[0259] Then, the UE receives an HTTP POST request message from the default USS / UTM. The UE may receive at least one of the first to fourth identification information from the default USS / UTM via the UAS application layer. The first identification information may include information on the USD.

[0260] The UAS application layer may be a UAS application specific layer, a UAE layer, and / or a SEAL layer. The UAS application layer may include a UAS application specific layer, a UAE layer, and / or a SEAL layer. Each layer within the UAS application layer may provide information to each other. The UE and the default USS / UTM may be connected via the U1-APP reference point, a U1-AE reference point, and / or a SEAL-UU. The UAS application layer may be a layer in which a UAE client communicates with a UAE server via the U1-AE reference point. The UAS application layer may be a layer in which a UAS application specific client communicates with a UAS application specific server via the U1-APP reference point.

[0261] Next, the UE may recognize information included in the first identification information based on reception of the first identification information. The UE may store the first identification information based on reception of the first identification information. The UE may also store information included in the first identification information based on reception of the first identification information. The UE may also perform a behavior that would occur if the second to fourth identification information were received based on reception of the first identification information. The UE may also release a PDU session established for this procedure based on reception of the first identification information. The UE may also release a PDU session that was established for connecting to the default USS / UTM based on reception of the first identification information. The UE may also release an already established PDU session based on reception of the first identification information.

[0262] In other words, when the UE receives the first identification information, it may recognize the information included in the first identification information. When the UE receives the first identification information, it may store the first identification information. When the UE receives the first identification information, it may also store the information included in the first identification information. When the UE receives the first identification information, it may also perform the behaviors performed when the second to fourth identification information are received. When the UE receives the first identification information, it may also release the PDU session established for this procedure. When the UE receives the first identification information, it may also release the PDU session established for connecting to the default USS / UTM. When the UE receives the first identification information, it may also release the PDU session that was already established.

[0263] Also, when the first identification information includes the second identification information, the second identification information may be a list including identification information of multiple USS / UTMs, and the UE may store the second identification information included in the first identification information based on receiving the first identification information. In other words, when the first identification information includes the second identification information, the second identification information may be a list including identification information of multiple USS / UTMs, and the UE may store the second identification information included in the first identification information when receiving the first identification information.

[0264] Furthermore, when the first identification information includes third identification information, the third identification information may be a list including information on areas where multiple USS / UTMs can be used, and the UE may store the third identification information included in the first identification information based on reception of the first identification information. In other words, when the first identification information includes third identification information, the third identification information may be a list including information on areas where multiple USS / UTMs can be used, and the UE may store the third identification information included in the first identification information when receiving the first identification information.

[0265] Furthermore, when the first identification information includes the fourth identification information, the fourth identification information may be a list of information indicating a plurality of access networks, and the UE may store the fourth identification information included in the first identification information based on reception of the first identification information. In other words, when the first identification information includes the fourth identification information, the fourth identification information may be a list of information indicating a plurality of access networks, and the UE may store the fourth identification information included in the first identification information when receiving the first identification information.

[0266] Next, the UE may recognize the second identification information based on the reception of the second identification information. The UE may also store the second identification information based on the reception of the second identification information. The UE may also select a USS / UTM to use based on the reception of the second identification information. The UE may also select a USS / UTM to use based on the reception of the second identification information and the third identification information. The UE may also release the PDU session established for this procedure based on the reception of the second identification information. The UE may also release the PDU session established for connecting to the default USS / UTM based on the reception of the second identification information. The UE may also release an already established PDU session based on the reception of the second identification information.

[0267] In other words, when the UE receives the second identification information, it may recognize the second identification information. When the UE receives the second identification information, it may store the second identification information. When the UE receives the second identification information, it may select a USS / UTM to use. When the UE receives the second identification information and the third identification information, it may select a USS / UTM to use. When the UE receives the second identification information, it may release the PDU session established for this procedure. When the UE receives the second identification information, it may release the PDU session established for connecting to the default USS / UTM. When the UE receives the second identification information, it may release an already established PDU session.

[0268] Next, the UE may recognize the third identification information based on the reception of the third identification information. The UE may also store the third identification information based on the reception of the third identification information. The UE may also select a USS / UTM to use based on the reception of the second identification information and the third identification information. The UE may also release the PDU session established for this procedure based on the reception of the third identification information. The UE may also release the PDU session established for connecting to the default USS / UTM based on the reception of the third identification information. The UE may also release an already established PDU session based on the reception of the third identification information.

[0269] In other words, when the UE receives the third identification information, it may recognize the third identification information. When the UE receives the third identification information, it may store the third identification information. When the UE receives the second identification information and the third identification information, it may select the USS / UTM to use. When the UE receives the third identification information, it may release the PDU session established for this procedure. When the UE receives the third identification information, it may release the PDU session established to connect to the default USS / UTM. When the UE receives the third identification information, it may release the PDU session that was already established.

[0270] The UE may then recognize the fourth identification based on the receipt of the fourth identification, may store the fourth identification based on the receipt of the fourth identification, and may restrict the UE from moving to an access network other than the access network indicated in the fourth identification based on the receipt of the fourth identification.

[0271] In other words, when the UE receives the fourth identification information, the UE may recognize the fourth identification information. Also, when the UE receives the fourth identification information, the UE may store the fourth identification information. Also, when the UE receives the fourth identification information, the UE may restrict movement to an access network other than the access network indicated in the fourth identification information.

[0272] Furthermore, the UE may release the established PDU session when it moves to an access network other than that indicated by the fourth identification information. Furthermore, the UE may restrict the establishment of a new PDU session when it moves to an access network other than that indicated by the fourth identification information. Here, the PDU session may be a PDU session for C2 communication.

[0273] Furthermore, the UE may release the PDU session established for this procedure based on the receipt of the fourth identification information. Furthermore, the UE may release the PDU session established for connecting to the default USS / UTM based on the receipt of the fourth identification information. Furthermore, the UE may release the PDU session that was already established based on the receipt of the fourth identification information.

[0274] In other words, when the UE receives the fourth identification information, it may release the PDU session established for this procedure. Also, when the UE receives the fourth identification information, it may release the PDU session established for connecting to the default USS / UTM. Also, when the UE receives the fourth identification information, it may release the PDU session that was already established.

[0275] For example, if the fourth identification information is information indicating that the access network is 5G-RAN, the UE may restrict movement to networks other than 5G-RAN based on the reception of the fourth identification information. In other words, if the fourth identification information is information indicating that the access network is 5G-RAN, the UE may restrict movement to networks other than 5G-RAN based on the reception of the fourth identification information. Furthermore, if the fourth identification information is information indicating that the access network is E-UTRAN, the UE may restrict movement to networks other than E-UTRAN based on the reception of the fourth identification information. In other words, if the fourth identification information is information indicating that the access network is E-UTRAN, the UE may restrict movement to networks other than E-UTRAN based on the reception of the fourth identification information.

[0276] 4. Variations A program running on an apparatus according to one aspect of the present invention may be a program that controls a central processing unit (CPU) or the like to cause a computer to function so as to realize the functions of an embodiment according to the present invention. The program or information handled by the program is temporarily stored in a volatile memory such as a random access memory (RAM), a non-volatile memory such as a flash memory, a hard disk drive (HDD), or another storage device system.

[0277] A program for implementing the functions of an embodiment according to one aspect of the present invention may be recorded on a computer-readable recording medium. The program may be loaded into a computer system and executed. The term "computer system" as used herein refers to a computer system built into a device, including hardware such as an operating system and peripheral devices. The term "computer-readable recording medium" may refer to a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a medium that dynamically stores a program for a short period of time, or any other computer-readable recording medium.

[0278] Additionally, each functional block or feature of the device used in the above-described embodiments may be implemented or performed by an electrical circuit, such as an integrated circuit or multiple integrated circuits. The electrical circuit designed to perform the functions described herein may include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or a combination thereof. The general-purpose processor may be a microprocessor, or a conventional processor, controller, microcontroller, or state machine. The electrical circuit may be composed of digital circuits or analog circuits. Furthermore, as advances in semiconductor technology emerge, one or more aspects of the present invention may utilize new integrated circuit technologies that replace current integrated circuits.

[0279] The present invention is not limited to the above-described embodiment. Although one example of a device has been described in the embodiment, the present invention is not limited to this and can be applied to stationary or non-movable electronic devices installed indoors or outdoors, such as terminal devices or communication devices for AV equipment, kitchen equipment, cleaning / washing equipment, air conditioning equipment, office equipment, vending machines, and other household appliances.

[0280] Although the embodiments of the present invention have been described in detail above with reference to the drawings, the specific configuration is not limited to this embodiment and includes design modifications within the scope of the invention. Furthermore, the present invention is susceptible to various modifications within the scope of the claims, and embodiments obtained by appropriately combining the technical means disclosed in different embodiments are also included in the technical scope of the present invention. Furthermore, configurations in which elements described in the above embodiments are substituted with elements that achieve the same effect are also included.

Claims

1. A UE (User Equipment) comprising a transceiver unit and a control unit, the UE is a UAV (Unmanned Aerial Vehicle), The transceiver unit receives a UAV USD (UAV User Service Description) including first information, second information, and third information from a default USS (Unmanned Aerial System Service Supplier), the first information is identification information of the USS; The second information is information indicating an area in which the USS is available, the third information is information indicating an access network; The control unit stores the first information, the second information, and the third information based on reception of the UAV USD, If the third information indicates that the access network is 5G-RAN, the control unit restricts movement to networks other than 5G-RAN based on reception of the UAV USD. A UE characterized by:

2. If the third information indicates that the access network is E-UTRAN (Evolved Universal Terrestrial Radio Access Network), the control unit restricts movement to networks other than E-UTRAN based on reception of the UAV USD.

2. The UE of claim 1 .

Images