Unmanned aerial vehicle

Abstract

When a UAV (Unmanned Aerial Vehicle) corresponds to a UAV controller and establishes a connection, a procedure for explicitly updating connection information is not defined. In addition, a connection for performing UAV communication must activate a user plane resource. The UAV updates stored identification information and an IP address of the UAV controller based on a PDU session change command message including the identification information and the IP address of the UAV controller received from the network. In addition, the UAV transmits / receives information for establishing a network and an Always-on PDU session in a case where a PDU session providing a QoS flow for performing C2 (Command and Control) communication is established.

Description

Technical Field

[0001] This invention relates to a UAV (Unmanned Aerial Vehicle). This application claims priority based on Japanese Patent Application No. 2020-134326, filed on August 7, 2020, the contents of which are incorporated herein by reference. Background Technology

[0002] In 3GPP (3rd Generation Partnership Project), the system architecture of 5GS (5G System), a fifth-generation (5G) mobile communication system, was studied, and discussions were made on supporting new processes and new functions (see Non-Patent Literature 1-3). In Release 17 of the 5G specification, a mobile communication system for unmanned aerial vehicles (UAVs) was discussed (see Non-Patent Literature 4).

[0003] Existing technical documents

[0004] Non-patent literature

[0005] Non-patent document 1: 3GPP TS 23.501V16.5.1 (2020-08); 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; SystemArchitecture for the 5G System; Stage 2 (Release 16)

[0006] Non-patent document 2: 3GPP TS 23.502V16.5.0(2020-07); 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for the 5G System; Stage 2 (Release 16)

[0007] Non-patent document 3: 3GPP TS 24.501V16.5.1 (2020-07); 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 (Release 16)

[0008] Non-patent document 4: 3GPP TR 23.754V0.2.0 (2020-06); 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on supporting Unmanned Aerial Systems (UAS) connectivity, Identification and tracking (Release 17) Summary of the Invention

[0009] The problem the invention aims to solve

[0010] Non-Patent Document 4 discusses the correspondence and connection establishment between a UAV (Unmanned Aerial Vehicle) and its UAV controller. While a solution for establishing the connection is provided, the process for updating connection information is not. Furthermore, the connection used for UAV communication has the following problem: if user plane resources are not activated, communication may not be possible between the UAV and its controller, and / or between the UAV and the UTM (Unmanned Aerial System Traffic Management).

[0011] One aspect of the present invention addresses the aforementioned issues by clarifying the information included in the PDU (Protocol Data Unit) session change command message sent by the network device to the UAV and the behavior of the UAV upon receiving the message. Furthermore, it clarifies the information included in messages during the UAV's PDU session establishment process.

[0012] Technical solution

[0013] One embodiment of the present invention is a UAV (Unmanned Aerial Vehicle), characterized in that it comprises a transceiver unit and a control unit. The transceiver unit receives a PDU session change command message from the network, which includes first identification information and second identification information. Based on the receipt of the first identification information, the control unit updates the stored identification information of the UAV controller to the identification information shown in the first identification information, and updates the stored IP address of the UAV controller to the IP address shown in the second identification information based on the receipt of the second identification information. The first identification information is the new identification information of the UAV controller, the second identification information is the new IP address of the UAV controller, and the UAV corresponds to the UAV controller.

[0014] Furthermore, one aspect of the UAV of the present invention is characterized by comprising a transceiver unit and a control unit. When establishing a PDU session that provides a QoS (Quality of Service) stream for C2 (Command and Control) communication, the transceiver unit sends a PDU session establishment request message including first identification information to the network and receives a PDU session establishment acceptance message including second identification information from the network. The first identification information is Always-on PDU session requested, and the second identification information is Always-on PDU session indication.

[0015] Beneficial effects

[0016] According to one aspect of the present invention, it is possible to clearly define the information included in the PDU session change command message sent by the network device to the UAV and the behavior of the UAV receiving the message. Furthermore, it is possible to clearly define the information included in the messages during the UAV's PDU session establishment process. Attached Figure Description

[0017] Figure 1 This is a diagram illustrating the overview of a mobile communication system (EPS / 5GS).

[0018] Figure 2 This is a diagram illustrating the detailed structure of a mobile communication system (EPS / 5GS).

[0019] Figure 3 This is a diagram illustrating the device configuration of the UE.

[0020] Figure 4 This diagram illustrates the configuration of the access network device (gNB) in 5GS.

[0021] Figure 5 This diagram illustrates the configuration of the core network devices (AMF / SMF / UPF) in 5GS.

[0022] Figure 6 This is a diagram illustrating the login process.

[0023] Figure 7 This is a diagram illustrating the PDU session establishment process.

[0024] Figure 8 This is a diagram representing the network-led session management process.

[0025] Figure 9 This is a diagram illustrating the session management process led by the UE.

[0026] Figure 10 It is a diagram representing the communication process.

[0027] Figure 11 This is a diagram illustrating the UAV communication method. Detailed Implementation

[0028] Hereinafter, a preferred mode for implementing the present invention will be described with reference to the accompanying drawings. It should be noted that, in this embodiment, as an example, an implementation of a mobile communication system applying a solution of the present invention will be described.

[0029] [1. System Overview]

[0030] first, Figure 1 This is a diagram illustrating the general outline of the mobile communication system 1 used in various embodiments. Figure 2 This is a diagram used to illustrate the detailed configuration of the mobile communication system 1.

[0031] exist Figure 1 The description states that the mobile communication system 1 consists 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.

[0032] In the following descriptions of these devices / functions, symbols such as UE, Access Network_A, Core Network_A, PDN, Access Network_B, Core Network_B, DN, etc. will sometimes be omitted.

[0033] In addition, Figure 2The description includes 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 the interfaces for interconnecting these devices / functions.

[0034] In the following descriptions of these devices / functions, symbols such as UE, E-UTRAN, MME, SGW, PGW-U, PGW-C, PCRF, HSS, 5G AN, AMF, UPF, SMF, PCF, UDM, and N3IWF will sometimes be omitted.

[0035] It should be noted that the EPS (Evolved Packet System) of a 4G system consists of an access network_A and a core network_A, but may further include the UE and / or PDN. Similarly, the 5GS (5G System) of a 5G system consists of a UE, an access network_B, and a core network_B, but may further include the DN.

[0036] A UE is a device capable of connecting to network services via 3GPP access (also known as 3GPP access network, 3GPP AN) and / or non-3GPP access (also known as non-3GPP access network, non-3GPP AN). A UE can be a mobile phone, smartphone, or other terminal device capable of wireless communication, or a terminal device capable of connecting to EPS or 5GS. A UE can possess a UICC (Universal Integrated Circuit Card) or eUICC (Embedded UICC). It should be noted that a UE can be presented as either a user equipment or a terminal device.

[0037] Furthermore, Access Network A corresponds to E-UTRAN (Evolved Universal Terrestrial Radio Access Network) and / or the wireless LAN access network. One or more eNBs (evolved Node Bs) 45 are configured in the E-UTRAN. It should be noted that, hereinafter, symbols are sometimes omitted when describing eNB 45, such as eNB. Furthermore, in the case of multiple eNBs, each eNB is interconnected, for example, via an X2 interface. Additionally, one or more access points are configured in the wireless LAN access network.

[0038] Furthermore, the Access Network _B corresponds to the 5G Access Network (5G AN). The 5G AN consists of the NG-RAN (NG Radio Access Network) and / or a non-3GPP access network. One or more gNBs (NR Node Bs) 122 are configured in the NG-RAN. It should be noted that, in the following description, symbols such as gNB 122 may be omitted. A gNB is a node that provides the NR (New Radio) user plane and control plane to the UE, and is a node connected to the 5GCN via an NG interface (including the N2 or N3 interface). That is, a gNB is a base station device newly designed for 5GS, with different functions than the base station device (eNB) used in the EPS of a 4G system. Furthermore, in the case of multiple gNBs, each gNB is interconnected, for example, via an Xn interface.

[0039] Furthermore, a non-3GPP access network can be either an untrusted non-3GPP access network or a trusted non-3GPP access network. An untrusted non-3GPP access network can be, for example, a public wireless LAN or other non-3GPP access network that does not undergo security management within the access network. On the other hand, a trusted non-3GPP access network can be an access network defined by 3GPP and can possess TNAP (trusted non-3GPP access point) and TNGF (trusted non-3GPP gateway function).

[0040] Furthermore, E-UTRAN and NG-RAN are sometimes referred to as 3GPP access. Additionally, wireless LAN access networks and non-3GPP ANs are sometimes referred to as non-3GPP access. Furthermore, nodes configured in access network B are sometimes collectively referred to as NG-RAN nodes.

[0041] In addition, the devices included in Access Network_A and / or Access Network_B and / or Access Network_A and / or Access Network_B are sometimes referred to as Access Network or Access Network Devices.

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

[0043] Furthermore, the core network_B corresponds to 5GCN (5G Core Network). 5GCN includes, for example, AMF (Access and Mobility Management Function), UPF (User Plane Function), SMF (Session Management Function), PCF (Policy Control Function), and UDM (Unified Data Management). Here, 5GCN can be represented as 5GC.

[0044] In addition, the following will sometimes refer to core network_A and / or core network_B, devices included in core network_A and / or devices included in core network_B as core network or core network devices or devices within the core network.

[0045] The core network (core network_A and / or core network_B) can 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. It can also be the core network used by a mobile network operator that operates and manages the mobile communication system 1. Furthermore, it can be the core network used by virtual mobile network operators and virtual mobile communication service providers such as MVNO (Mobile Virtual Network Operator) and MVNE (Mobile Virtual Network Enabler).

[0046] In addition, Figure 1The text describes the similarities between PDN and DN, but they can also differ. A PDN can be a DN (Data Network) that provides communication services to the UE. It should be noted that a DN can be configured as a packet data service network or configured for each service. Furthermore, a PDN can include connected communication terminals. Therefore, connecting to a PDN can be connecting to a communication terminal or server device configured on the PDN. Furthermore, sending and receiving user data with the PDN can be sending and receiving user data with a communication terminal or server device configured on the PDN. It should be noted that a PDN can be represented as a DN, or a DN can be represented as a PDN.

[0047] Furthermore, hereinafter, at least a portion of Access Network_A, Core Network_A, PDN, Access Network_B, Core Network_B, DN, and / or more than one device included in these networks are sometimes referred to as a network or network device. In short, "network and / or network device sending and receiving messages and / or executing processes" means that at least a portion of Access Network_A, Core Network_A, PDN, Access Network_B, Core Network_B, DN, and / or more than one device included in these networks are sending and receiving messages and / or executing processes.

[0048] Furthermore, the UE can connect to the access network. Additionally, the UE can connect to the core network via the access network. Further, the UE can connect to the PDN or DN via the access network and core network. That is, the UE can send and receive user data with the PDN or DN. When sending and receiving user data, not only IP (Internet Protocol) communication can be used, but also non-IP communication.

[0049] Here, IP communication refers to data communication using IP, which involves sending and receiving data via IP packets. An IP packet consists of an IP header and a payload. The payload can include data transmitted and received by devices / functions included in the EPS and devices / functions included in the 5GS. Furthermore, non-IP communication refers to data communication that does not use IP, but rather transmits and receives data using a different structure than IP packets. For example, non-IP communication can be data communication achieved by transmitting and receiving application data without an IP header, or it can use other headers such as MAC headers or Ethernet (registered trademark) frame headers to transmit and receive user data sent and received by the UE.

[0050] Furthermore, access network_A, core network_A, access network_B, core network_B, PDN_A, and DN_A can form a network with... Figure 2Devices not described herein. For example, AUSF (Authentication Server Function) and AAA (Authentication, Authorization, and Accounting) servers (AAA-S) may be included in core network_A and / or core network_B.

[0051] Here, AUSF is a core network device with authentication functions for both 3GPP and non-3GPP access. Specifically, it is a network function unit that receives authentication requests for 3GPP and / or non-3GPP access from the UE and performs the authentication process.

[0052] Furthermore, an AAA server is a device capable of authentication, authorization, and accounting functions, connecting directly to AUSF or indirectly via other network devices. An AAA server can be a network device within the core network. It should be noted that an AAA server can be included in the PLMN but not in core network A and / or core network B. In short, an AAA server can be a core network device or a device located outside the core network. For example, an AAA server can be a server device within a PLMN managed by a third party (3rdParty).

[0053] It should be noted that, in Figure 2 To simplify the accompanying drawings, each device / function is described as one, but the mobile communication system 1 may also have multiple identical devices / functions. Specifically, the mobile communication system 1 may have multiple devices / functions such as UE_A10, E-UTRAN80, MME40, SGW35, PGW-U30, PGW-C32, PCRF60, HSS50, 5G AN120, AMF140, UPF130, SMF132, PCF160 and / or UDM150.

[0054] The UPF_A235 connects to the DN, SMF, other UPFs, and access network. The UPF_A235 can perform the following functions: anchoring for intra-RAT mobility or inter-RAT mobility; packet routing and forwarding; UL CL (Uplink Classifier) ​​function for routing multiple service flows within a DN; branching point function supporting multi-homed PDU sessions; QoS processing for the user plane; uplink service verification; downlink packet buffering; and triggering downlink data notification. Furthermore, the UPF_A235 can act as a relay device for forwarding user data between the DN and the core network_B190. It should be noted that the UPF_A235 can be a gateway for IP communication and / or non-IP communication. Furthermore, the UPF_A235 can forward IP communications and also convert non-IP communications to IP communications. Furthermore, the configured multiple gateways can be gateways connecting the core network_B190 to a single DN. It should be noted that the UPF_A235 can have connectivity with other NFs and can also connect to various devices via other NFs.

[0055] It should be noted that between UPF_A235 and the access network, there can be a UPF_C239 (also known as a branching point or uplink classifier) ​​as a device or NF, which is a different UPF from UPF_A235. In the presence of UPF_C239, the PDU session between the UE and the DN is established via the access network, UPF_C239, and UPF_A235.

[0056] Furthermore, UPF130 can be the same device as UPF_A235. It should be noted that sometimes the symbols are omitted to describe UPF130 and UPF_A235, such as UPF.

[0057] [2. Composition of each device]

[0058] Next, the configuration of the various devices (UE and / or access network device and / or core network device) used in each embodiment will be described using the accompanying drawings. It should be noted that each device can be configured as physical hardware, as logical (virtual) hardware built on general-purpose hardware, or as software. Furthermore, at least some (including all) of the functions possessed by each device can also be configured as physical hardware, logical hardware, or software.

[0059] It should be noted that the storage units (Storage Unit_A340, Storage Unit_A440, Storage Unit_B540, Storage Unit_A640, Storage Unit_B740) within each device / function mentioned below are, for example, composed of semiconductor memory, SSD (Solid State Drive), HDD (Hard Disk Drive), etc. Furthermore, each storage unit can store not only the information originally set at the factory, but also various information exchanged between the device / function and other devices / functions (e.g., UE and / or access network devices and / or core network devices and / or PDN and / or DN). In addition, each storage unit can store identification information, control information, flags, parameters, etc., included in the control messages exchanged during the various communication processes described below. Furthermore, each storage unit can store this information in each UE. Moreover, in the case of interoperability between 5GS and EPS, each storage unit can store control messages and user data exchanged between the device / function included in 5GS and / or EPS. At this point, it can store not only data sent and received via the N26 interface, but also data not sent and received via the N26 interface.

[0060] [2.1. UE Device Configuration]

[0061] First, use Figure 3 An example of the device configuration of a UE (User Equipment) will be described. The UE consists of a control unit_A300, an antenna 310, a transceiver unit_A320, and a storage unit_A340. The control unit_A300, transceiver unit_A320, and storage unit_A340 are connected via a bus. The transceiver unit_A320 is connected to the antenna 310.

[0062] The control unit_A300 is a functional unit that controls the overall actions / functions of the UE. The control unit_A300 implements various processes within the UE by reading and executing various programs stored in the storage unit_A340 as needed.

[0063] The transceiver unit A320 is a functional unit used for wireless communication with base station equipment (eNB or gNB) within the access network via an antenna. That is, the UE can use the transceiver unit A320 to send and receive user data and / or control information with access network equipment and / or core network equipment and / or PDN and / or DN.

[0064] When reference Figure 2 In detail, the UE can communicate with the base station device (eNB) in the E-UTRAN via the LTE-Uu interface using the transceiver unit (A320). Furthermore, the UE can communicate with the base station device (gNB) in the 5G AN using the transceiver unit (A320). Additionally, the UE can send and receive NAS (Non-Access-Stratum) messages with the AMF via the N1 interface using the transceiver unit (A320). However, the N1 interface is a logical interface; therefore, communication between the UE and the AMF is actually conducted via the 5G AN.

[0065] The storage unit A340 is a functional unit used to store programs, user data, control information, etc. required for various actions of the UE.

[0066] [2.2. gNB Device Configuration]

[0067] Next, use Figure 4 An example of the gNB's device configuration will be described. The gNB consists of a control unit_B500, an antenna 510, a network connection unit_B520, a transceiver unit_B530, and a storage unit_B540. The control unit_B500, network connection unit_B520, transceiver unit_B530, and storage unit_B540 are connected via a bus. The transceiver unit_B530 is connected to the antenna 510.

[0068] The control unit_B500 is a functional unit that controls the overall operation / function of the gNB. The control unit_B500 performs various processes within the gNB by reading and executing various programs stored in the storage unit_B540 as needed.

[0069] The network connection unit_B520 is a functional unit for enabling communication between the gNB and the AMF and / or UPF. That is, the gNB can use the network connection unit_B520 to send and receive user data and / or control information with the AMF and / or UPF.

[0070] The transceiver unit_B530 is a functional unit used for wireless communication with the UE via the antenna 510. That is, the gNB can use the transceiver unit_B530 to send and receive user data and / or control information with the UE.

[0071] When reference Figure 2In detail, the gNB located within the 5G AN can communicate with the AMF via the N2 interface and with the UPF via the N3 interface using the network connection unit_B520. Furthermore, the gNB can communicate with the UE using the transceiver unit_B530.

[0072] The storage unit B540 is a functional unit used to store programs, user data, control information, etc., required for various operations of the gNB.

[0073] [2.3. AMF Device Configuration]

[0074] Next, use Figure 5 An example of the device configuration of an AMF will be described. The AMF consists of a control unit_B700, a network connection unit_B720, and a storage unit_B740. The control unit_B700, network connection unit_B720, and storage unit_B740 are connected via a bus. The AMF can be a node that processes the control plane.

[0075] The control unit_B700 is a functional unit that controls the overall operation / function of the AMF. The control unit_B700 performs various processes within the AMF by reading and executing various programs stored in the storage unit_B740 as needed.

[0076] The network connection unit_B720 is a functional unit for enabling the AMF to connect with base station devices (gNB) and / or SMF and / or PCF and / or UDM and / or SCEF within the 5G AN. That is, the AMF can use the network connection unit_B720 to send and receive user data and / or control information between itself and the base station devices (gNB) and / or SMF and / or PCF and / or UDM and / or SCEF within the 5G AN.

[0077] When reference Figure 2 In detail, the AMF (Active Network Module) within the 5GCN can communicate with the gNB via the N2 interface, with the UDM via the N8 interface, with the SMF via the N11 interface, and with the PCF via the N15 interface using the network connection unit_A620. Furthermore, the AMF can send and receive NAS messages with the UE via the N1 interface using the network connection unit_A620. However, the N1 interface is a logical interface; therefore, communication between the UE and AMF is actually via the 5G AN (Active Network Module). Additionally, when the N26 interface is supported, the AMF can communicate with the MME via the N26 interface using the network connection unit_A620.

[0078] The storage unit_B740 is a functional unit used to store programs, user data, control information, etc. required for various operations of the AMF.

[0079] It should be noted that the AMF has the following functions: 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; performing registration management (RM) functions; connection management (CM) functions; reachability management functions; mobility management functions for UEs, etc.; forwarding SM (Session Management) messages between the UE and the SMF; access authentication (Access Authentication, Access Authorization) functions; security anchor function (SEA); security context management (SCM); supporting the N2 interface for N3IWF (Non-3GPP Interworking Function); supporting the transmission and reception of NAS signals with the UE via N3IWF; and authenticating UEs connected via N3IWF.

[0080] Furthermore, the RM state of each UE is managed in login management. The RM state can be synchronized between the UE and the AMF. There are two RM states: a non-login state (RM-DEREGISTERED state) and a login state (RM-REGISTERED state). In the RM-DEREGISTERED state, the UE is not logged into the network; therefore, the UE context in the AMF does not have valid location and routing information for that UE, so the AMF is in a state where it cannot reach the UE. Conversely, in the RM-REGISTERED state, the UE is logged into the network; therefore, the UE can receive services that require network login. It should be noted that the RM state can also be represented as a 5GMM state. In this case, both the RM-DEREGISTERED state and the RM-REGISTERED state can be represented as 5GMM-REGISTERED states.

[0081] In other words, 5GMM-REGISTERED can refer to either the state where each device has established a 5GMM context or the state where a PDU session context has been established. It should be noted that when each device is in 5GMM-REGISTERED state, UE_A10 can begin sending and receiving user data and control messages, and can also respond to paging requests. Furthermore, it should be noted that when each device is in 5GMM-REGISTERED state, UE_A10 can execute login procedures and / or service request procedures other than the login procedure used for initial login.

[0082] Furthermore, 5GMM-DEREGISTERED can refer to a state where the devices have not established a 5GMM context, a state where the location information of UE_A10 is not known to the network, or a state where the network cannot reach UE_A10. It should be noted that when the devices are in the 5GMM-DEREGISTERED state, UE_A10 can either start the login process or establish a 5GMM context by executing the login process.

[0083] Furthermore, the CM state of each UE is managed within the connection management system. The CM state can be synchronized between the UE and the AMF. There are two CM states: a disconnected 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. Additionally, in the CM-IDLE state, the UE does not have an N2 connection or an N3 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. Furthermore, in the CM-CONNECTED state, the UE may also have an N2 connection and / or an N3 connection.

[0084] Furthermore, connection management can also be divided into CM states in 3GPP access and CM states in non-3GPP access, and managed accordingly. In this case, the CM states in 3GPP access can exist as both an IDLE state and a CONNECTED state. Similarly, the CM states in non-3GPP access can also exist as both an IDLE state and a CONNECTED state. It should be noted that the IDLE state can manifest as an idle mode, and the CONNECTED state can manifest as a connected mode.

[0085] It should be noted that the CM state can also be represented as 5GMM mode. In this case, the non-connected state can also be represented as 5GMM-IDLE mode, and the connected state can also be represented as 5GMM-CONNECTED mode. Furthermore, the non-connected state in 3GPP access can also be represented as 5GMM-IDLE mode over 3GPP access, and the connected state in 3GPP access can also be represented as 5GMM-CONNECTED mode over 3GPP access. Furthermore, the non-connected state in non-3GPP access can also be represented as 5GMM-IDLE mode over non-3GPP access, and the connected state in non-3GPP access can also be represented as 5GMM-CONNECTED mode over non-3GPP access. It should be noted that 5GMM non-connected mode can be represented as idle mode, and 5GMM connected mode can be represented as connected mode.

[0086] Furthermore, more than one AMF can be configured within the core network_B. Additionally, an AMF can be an NF (Network Function) that manages more than one NSI (Network Slice Instance). Furthermore, an AMF can also be a shared CP function (CCNF; Common CPNF) shared among multiple NSIs.

[0087] It should be noted that N3IWF is a device and / or function configured between non-3GPP access and 5GCN when the UE is connected to 5GS via non-3GPP access.

[0088] [2.4. SMF Device Configuration]

[0089] Next, use Figure 5 An example of the device configuration of an SMF will be described. The SMF consists of a control unit_B700, a network connection unit_B720, and a storage unit_B740. The control unit_B700, network connection unit_B720, and storage unit_B740 are connected via a bus. The SMF can be a node that processes the control plane.

[0090] The control unit_B700 is a functional unit that controls the overall operation / function of the SMF. The control unit_B700 performs various processes within the SMF by reading and executing various programs stored in the storage unit_B740 as needed.

[0091] The network connection unit_B720 is a functional unit for enabling the SMF to connect with the AMF and / or UPF and / or PCF and / or UDM. That is, the SMF can use the network connection unit_B720 to send and receive user data and / or control information with the AMF and / or UPF and / or PCF and / or UDM.

[0092] When reference Figure 2 In detail, the SMF located within 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 through the network connection unit _A620.

[0093] The storage unit_B740 is a functional unit used to store programs, user data, control information, etc. required for various operations of SMF.

[0094] The SMF has the following functions: session management functions such as PDU session establishment / revision / release; IP address allocation and management functions for UE; UPF selection and control functions; UPF configuration functions for routing services to the appropriate destination (sending destination); functions for sending and receiving NAS messages (SM part); functions for notifying downlink data that has arrived (Downlink Data Notification); functions for providing AN-specific (each AN's) SM information sent to the AN via the N2 interface through the AMF; functions for determining the SSC mode (Session and Service Continuity mode) for the session; and roaming functions, etc.

[0095] [2.5. UPF Device Configuration]

[0096] Next, use Figure 5 An example of the UPF device configuration will be described. The UPF consists of a control unit_B700, a network connection unit_B720, and a storage unit_B740. The control unit_B700, network connection unit_B720, and storage unit_B740 are connected via a bus. The UPF can be a node that processes the control plane.

[0097] The control unit_B700 is a functional unit that controls the overall operation / function of the UPF. The control unit_B700 performs various processes within the UPF by reading and executing various programs stored in the storage unit_B740 as needed.

[0098] The network connection unit_B720 is a functional unit for connecting the UPF to the base station equipment (gNB) and / or SMF and / or DN within the 5G AN. That is, the UPF can use the network connection unit_B720 to send and receive user data and / or control information between itself and the base station equipment (gNB) and / or SMF and / or DN within the 5G AN.

[0099] When reference Figure 2 In detail, the UPF located within the 5GCN can communicate with the gNB via the N3 interface, with the SMF via the N4 interface, with the DN via the N6 interface, and with other UPFs via the N9 interface through the network connection unit _A620.

[0100] The storage unit B740 is a functional unit used to store the programs, user data, control information, etc. required for the various operations of the UPF.

[0101] UPF has the following functions: serving as an anchor point for intra-RAT mobility or inter-RAT mobility; serving as an external PDU session point for interconnection with the DN (in short, serving as a gateway for forwarding user data between the DN and the core network_B); packet routing and forwarding; UL CL (Uplink Classifier) ​​function for routing multiple service flows to a DN; branching point function for supporting multi-homed PDU sessions; QoS (Quality of Service) processing for the user plane; uplink service authentication function; triggering downlink packet buffering; and downlink data notification function.

[0102] Furthermore, a UPF can be a gateway for IP communication and / or non-IP communication. Additionally, a UPF can forward IP communications or convert between non-IP and IP communications. Moreover, the configured multiple gateways can be gateways connecting the core network (B) and a single DN. It should be noted that the UPF can have connectivity with other NFs and can also connect to various devices via other NFs.

[0103] It should be noted that the user plane refers to the user data transmitted and received between the UE and the network. The user plane can use PDN connections or PDU sessions for transmission and reception. Furthermore, in the case of EPS, the user plane can also use 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 for transmission and reception. Furthermore, in the case of 5GS, the user plane can also transmit and receive data 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. The user plane can also be represented as a U-Plane.

[0104] Furthermore, the control plane consists of control messages sent and received for UE communication control, etc. The control plane can be sent and received using the NAS (Non-Access-Stratum) signaling connection between the UE and the MME. Furthermore, in the case of EPS, the control plane can also be sent and received using the LTE-Uu interface and the S1-MME interface. Furthermore, in the case of 5GS, the control plane can also be sent and received using the interface between the UE and the NG RAN and the N2 interface. The control plane can also be represented as a Control Plane or a C-Plane.

[0105] Furthermore, the user plane (UP) can be a communication path for sending and receiving user data, or it can consist of multiple bearers. Similarly, the control plane (CP) can be a communication path for sending and receiving control messages, and it can also consist of multiple bearers.

[0106] [2.6. Other devices and / or functions]

[0107] Next, other devices and / or functions, as well as identification information, will be described.

[0108] A network refers to at least a portion of the access network_B, core network_B, and DN. Alternatively, one or more devices included in at least a portion of the access network_B, core network_B, and DN can also be referred to as a network or a network device. In short, the network performing message transmission, reception, and / or processing can mean that devices within the network (network devices and / or control devices) perform message transmission, reception, and / or processing. Conversely, devices within the network performing message transmission, reception, and / or processing can mean that the network performs message transmission, reception, and / or processing.

[0109] In addition, NSSF (Network Slice Selection Function) can refer to a network function (also known as NF) that has the ability to select the network slice serving the UE.

[0110] In addition, NWDAF (Network Data Analytics Function) can refer to an NF that has the ability to collect data from NFs and application functions (also known as AFs).

[0111] In addition, PCF (Policy Control Function) can refer to an NF that has the function of determining policies for controlling the behavior of the network.

[0112] Furthermore, an NRF (Network Repository Function) can refer to an NF that has service discovery capabilities. An NRF can be an NF that provides information about a discovered NF when it receives a discovery request from another NF.

[0113] Furthermore, SM (Session Management) messages (also known as NAS (Non-Access-Stratum) SM messages) can be NAS messages used during the SM process, or control messages sent and received between UE_A10 and SMF via AMF. Further, SM messages may include: PDU session establishment request messages, PDU session establishment accept messages, PDU session establishment reject messages, PDU session modification request messages, PDU session modification command messages, PDU session modification complete messages, PDU session modification command reject messages, PDU session modification reject messages, PDU session release request messages, PDU session release reject messages, PDU session release command messages, and PDU session release complete messages, etc.

[0114] In addition, the procedures used for SM, or the SM process itself, may include: PDU session establishment procedure, PDU session modification procedure, and PDU session release procedure. It should be noted that each procedure can be initiated by the UE or by the NW.

[0115] Furthermore, MM (Mobility Management) messages (also known as NAS MM messages) can be NAS messages used during the MM process, or control messages exchanged between UE_A10 and AMF. Further, MM messages can include: Registration request messages, Registration accept messages, Registration reject messages, De-registration request messages, De-registration accept messages, Configuration update command messages, Configuration update complete messages, Service request messages, Service accept messages, Service reject messages, Notification messages, and Notification response messages, etc.

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

[0117] Furthermore, 5GS (5G System) service can be a connectivity service provided using the core network _B190. Further, 5GS service can be a service different from EPS service, or it can be the same as EPS service.

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

[0119] Furthermore, the PDN (Packet Data Network) type indicates the type of PDN connection, which can be IPv4, IPv6, IPv4v6, or non-IP. Specifying IPv4 indicates that IPv4 is used for data transmission and reception. Specifying IPv6 indicates that IPv6 is used for data transmission and reception. Specifying IPv4v6 indicates that either IPv4 or IPv6 is used for data transmission and reception. Specifying non-IP indicates that communication is conducted using a method other than IP.

[0120] Furthermore, a PDU (Protocol Data Unit / Packet Data Unit) session can be defined as the association between the DN (Digital Network) providing PDU connectivity services and the UE, but it also refers to the connectivity established between the UE and an external gateway. By establishing a PDU session in the 5GS via the access network_B and core network_B, the UE can use the PDU session to send and receive user data with the DN. Here, the external gateway can refer to UPF, SCEF, etc. The UE can use the PDU session to perform the sending and receiving of user data with devices such as application servers configured on the DN.

[0121] It should be noted that each device (UE and / or access network device and / or core network device) can also associate and manage more than one identification information with a PDU session. This identification information can include one or more of the following: DNN, QoS rules, PDU session type, application identification information, NSI identification information, and access network identification information, and may further include other information. Furthermore, when multiple PDU sessions are established, the identification information corresponding to each PDU session can be the same or different.

[0122] Furthermore, the DNN (Data Network Name) can be identification information for identifying the core network and / or external networks such as DN. Further, the DNN can also be used as information for selecting gateways such as PGW / UPF that connect to the core network B190. Furthermore, the DNN can also be equivalent to the APN (Access Point Name).

[0123] Furthermore, the PDU (Protocol Data Unit / Packet Data Unit) session type indicates the type of PDU session, which can be IPv4, IPv6, Ethernet, or Unstructured. Specifying IPv4 indicates that IPv4 is used for data transmission and reception. Specifying IPv6 indicates that IPv6 is used for data transmission and reception. Specifying Ethernet indicates that Ethernet frames are transmitted and received. Additionally, Ethernet can indicate that communication does not use IP. Specifying Unstructured indicates that point-to-point (P2P) tunneling technology is used to send and receive data to and from application servers, etc., located in the DN. For example, UDP / IP encapsulation technology can be used as a P2P tunneling technology. It should be noted that the PDU session type can also include IP in addition to the types mentioned above. IP can be specified if the UE can use both IPv4 and IPv6.

[0124] Furthermore, a PLMN (Public Land Mobile Network) is a communication network that provides mobile wireless communication services. A PLMN is a network managed by an operator, and the operator can be identified through its PLMN ID. A PLMN whose MCC (Mobile Country Code) and MNC (Mobile Network Code) match the UE's IMSI (International Mobile Subscriber Identity) can be a Home PLMN (HPLMN). Further, the UE can maintain a list of equivalent HPLMNs in its USIM to identify one or more EPLMNs. A PLMN different from an HPLMN and / or EPLMN can be a Visited PLMN (VPLMN). The PLMN the UE successfully logs into can be an RPLMN (Registered PLMN).

[0125] A tracking area is one or more ranges managed by the core network that can be represented as location information for UE_A10. A tracking area can consist of multiple cells. Furthermore, a tracking area can be a range used for broadcasting control messages such as paging, or a range that UE_A10 can move within without a handover process. Furthermore, a tracking area can be a routing area or a location area, as long as it is the same as these areas. Hereinafter, the tracking area can also be a TA (Tracking Area). A tracking area can be identified by a TAI (Tracking Area Identity) consisting of a TAC (Tracking Area Code) and a PLMN.

[0126] A registration area is a set of one or more transferable areas (TAs) assigned to a UE by the AMF. It's important to note that UE_A10 can move within one or more TAs included in the registration area without transmitting or receiving signals for tracking area updates. In other words, a registration area can be a group of information representing areas where UE_A10 can move without performing a tracking area update process. Registration areas can be identified through a TAI list consisting of one or more TAIs.

[0127] UE ID refers to information used to identify a UE. Specifically, for example, a UE ID can be SUCI (Subscription Concealed Identifier), SUPI (Subscription Permanent Identifier), GUTI (Globally Unique Temporary Identifier), IMEI (International Mobile Subscriber Identity), IMEISV (IMEI Software Version), or TMSI (Temporary Mobile Subscriber Identity). Alternatively, a UE ID can be other information set within an application or network. Furthermore, a UE ID can also be information used to identify a user.

[0128] UAV (Unmanned Aerial Vehicle) refers to a flying unmanned aerial vehicle. A UAV can correspond to a UAV controller. Furthermore, a UAV can correspond to a UAV controller and be managed by core network devices and / or UTM. Further, when a UAV corresponds to and is managed by a UAV controller, it can act as a UAS managed by core network devices and / or UTM. The UAV can have its own information (identification information, IP address, location information, etc.) managed by the core network devices and / or UTM. Additionally, a UAV can also be a UE (User Equipment).

[0129] A UAV controller (Unmanned Aerial Vehicle) is a controller used to operate a UAV. A UAV controller can correspond to a UAV. Furthermore, a UAV controller can correspond to a UAV and be managed by core network devices and / or UTMs. Further, when corresponding to and managed by a UAV, a UAV controller can also act as a UAS managed by core network devices and / or UTMs. The UAV controller can have its own information (identification information, IP address, location information, etc.) managed by core network devices and / or UTMs. Additionally, a UAV controller can also be a UE (User Equipment). It should be noted that a UAV controller can manifest as a UAC (User Acquisition Center) or a UAV-C (User Availability Center).

[0130] A UAS (Unmanned Aerial System) can also consist of a UAV and a UAV controller. The UAS can be managed by core network devices and / or a UTM. A UAS can consist of one UAV and one UAV controller.

[0131] Furthermore, the UAS (Unmanned Aerial System) can also consist of functions related to the UAV. Here, these functions may include a C2 (command and control) link. Further, the C2 link can be a link between the UAV and the control device, or a link between the UAV and the network. Further, the C2 link can also be a link used for remote identification.

[0132] UTM (Unmanned Aerial System Traffic Management) is a device capable of managing UAVs and / or UAV controllers and / or UASs. The UTM can be a device within the core network or a DN (Network Controller). Furthermore, the UTM can be a device for autonomously operating UAVs. Additionally, the UTM can have functions for managing the identification information, IP address, location information, etc., of UAVs and / or UAV controllers, and can also have functions for managing information of UAVs and / or UAV controllers other than those mentioned above. Further, the UTM can also manage UAVs and UAV controllers as corresponding UASs. Moreover, the UTM can also send information requesting network services to core network devices.

[0133] Furthermore, a UTM can be a device that provides one or more functions or services for managing the driving range of a vehicle. Additionally, a UTM can be a device with USS functionality. It should be noted that a UTM can be represented as UTM / USS and / or USS / UTM.

[0134] A USS (Unmanned Aerial System Service Provider) can be a device within a UTM. A USS can be a device possessed by a UTM. Furthermore, functions that a UTM can perform can also be functions that a USS can perform. Additionally, actions that a UTM can perform can be interpreted as actions that a USS can perform. When a UTM appears to be processing, it can also be interpreted as the USS performing processing.

[0135] An Always-on PDU session refers to a PDU session that must activate user plane resources whenever a UE transitions from a 5GMM-IDLE state to a 5GMM-CONNECTED state. The UE can request the establishment of a PDU session as an Always-on PDU session from the core network and / or core network devices based on instructions from upper layers. The core network and / or core network devices determine whether a PDU session can be established as an Always-on PDU session. Here, the establishment of an Always-on PDU session can refer to the establishment of a PDU session used for C2 communication. Further, the establishment of an Always-on PDU session can refer to the establishment of a PDU session handling QoS flows for C2 communication.

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

[0137] Command and Control (C2) communication refers to a user plane communication path used to distribute messages, including command and control information for operating the UAV, from the UAV controller or UTM to the UAV. Further, C2 communication can also be a user plane communication path used to report telemetry data from the UAV to the UAV controller or UTM. More specifically, C2 communication can be a user plane communication path used to distribute messages, including command and control information for operating the UAV, from the UAV controller via the UTM to the UAV.

[0138] Here, C2 communication can be a communication path implemented through a PDU session. Furthermore, the PDU session used for C2 communication can be implemented through an Always-on PDU session. Furthermore, the establishment of a PDU session for C2 communication can mean the establishment of an Always-on PDU session. Furthermore, the establishment of a PDU session for processing QoS flows used for C2 communication can mean the establishment of an Always-on PDU session.

[0139] [2.7. Identification Information in this Embodiment]

[0140] Next, in this embodiment, the identification information transmitted, received, stored, and managed by each device will be explained.

[0141] First, the first identifying information is the request to establish a PDU session as an Always-on PDU session. The first identifying information can be information indicating whether a PDU session is requested to be established as an Always-on PDU session. Further, the first identifying information can be an Always-on PDU session requested information element.

[0142] Furthermore, the first identification information may be information indicating whether an Always-on PDU session is requested. For example, the first identification information may be information indicating a request to establish an Always-on PDU session. Conversely, the first identification information may be information indicating that an Always-on PDU session is not requested.

[0143] Here, the establishment of an Always-on PDU session can refer to the establishment of a PDU session used for C2 communication. Further, the establishment of an Always-on PDU session can refer to the establishment of a PDU session that processes QoS flows used for C2 communication.

[0144] Furthermore, the second identification information indicates that a PDU session is established as an Always-on PDU session. The second identification information may indicate whether a PDU session is established as an Always-on PDU session. Further, the second identification information may indicate whether establishing an Always-on PDU session is permitted. The second identification information may be an Always-on PDU session indication information element.

[0145] Furthermore, the second identification information can be information indicating whether an Always-on PDU session should be established. In other words, the second identification information can be information indicating whether an Always-on PDU session should be established. For example, the second identification information can be information indicating that an Always-on PDU session needs to be established. Conversely, the second identification information can be information indicating that an Always-on PDU session is not allowed.

[0146] Here, the establishment of an Always-on PDU session can refer to the establishment of a PDU session used for C2 communication. Further, the establishment of an Always-on PDU session can refer to the establishment of a PDU session that processes QoS flows used for C2 communication.

[0147] Furthermore, the tenth identification information is the identification information of the UAV controller. The tenth identification information can be the identification information of a new UAV controller. Further, the tenth identification information can be different from the UAV controller identification information stored in the UAV database. Conversely, the tenth identification information can be the same as the UAV controller identification information stored in the UAV database.

[0148] Furthermore, the tenth identification information can be information associated with the eleventh identification information. Specifically, the UAV controller identified by the tenth identification information can be a UAV controller assigned the IP address shown in the eleventh identification information.

[0149] Here, the UAV controller can be a UAV controller corresponding to a UAV. More specifically, the UAV controller can be a UAV controller corresponding to the UAV that receives the tenth identification information and / or the eleventh identification information.

[0150] Furthermore, the eleventh identification information is the IP address of the UAV controller. The eleventh identification information can be a new UAV controller's IP address. Further, the eleventh identification information can be different from the IP address of the UAV controller stored in the UAV database. Conversely, the eleventh identification information can be the same as the IP address of the UAV controller stored in the UAV database.

[0151] Furthermore, the eleventh identification information can be information associated with the tenth identification information. Specifically, the IP address shown in the eleventh identification information can be the IP address of the UAV controller identified by the tenth identification information.

[0152] Here, the UAV controller can be a UAV controller corresponding to a UAV. More specifically, the UAV controller can be a UAV controller corresponding to the UAV that receives the tenth identification information and / or the eleventh identification information.

[0153] Furthermore, the twelfth identification information is the UAV's identification information. The twelfth identification information can be the identification information of a new UAV. Further, the twelfth identification information can be different from the UAV identification information stored in the UAV controller. Conversely, the twelfth identification information can be the same as the UAV identification information stored in the UAV controller.

[0154] Furthermore, the twelfth identification information can be information associated with the thirteenth identification information. Specifically, the UAV identified by the twelfth identification information is the UAV assigned the IP address shown in the thirteenth identification information.

[0155] Here, the UAV can be a UAV corresponding to a UAV controller. More specifically, the UAV can be a UAV corresponding to a UAV controller that receives the twelfth and / or thirteenth identification information.

[0156] Furthermore, the thirteenth identification information is the UAV's IP address. The thirteenth identification information can be a new UAV's IP address. Further, the thirteenth identification information can be different from the UAV's IP address stored in the UAV controller. Conversely, the thirteenth identification information can be the same as the UAV's IP address stored in the UAV controller.

[0157] Furthermore, the thirteenth identification information can be information associated with the twelfth identification information. Specifically, the IP address shown in the thirteenth identification information can be the IP address of the UAV identified by the twelfth identification information.

[0158] Here, the UAV can be a UAV corresponding to a UAV controller. More specifically, the UAV can be a UAV corresponding to a UAV controller that receives the twelfth and / or thirteenth identification information.

[0159] In addition, the fourteenth identification information indicates whether a PDU session is established as an Always-on PDU session. The fourteenth identification information can be the same as the second identification information.

[0160] Furthermore, the fourteenth identification information may be information indicating whether the established PDU session is processed as an Always-on PDU session. Furthermore, the fourteenth identification information may be information indicating whether the established PDU session is re-established as an Always-on PDU session.

[0161] Furthermore, the content shown in the fourteenth identification information may be the same as or different from the information shown in the second identification information.

[0162] Specifically, if the second identification information indicates that an Always-on PDU session needs to be established, the fourteenth identification information can also indicate that an Always-on PDU session needs to be established. Furthermore, if the second identification information indicates that an Always-on PDU session is not allowed, the fourteenth identification information can also indicate that an Always-on PDU session is not allowed.

[0163] Conversely, if the second identification information indicates that an Always-on PDU session needs to be established, the fourteenth identification information can indicate that an Always-on PDU session is not allowed. Furthermore, if the second identification information indicates that an Always-on PDU session is not allowed, the fourteenth identification information can indicate that an Always-on PDU session needs to be established.

[0164] Here, the establishment of an Always-on PDU session can refer to the establishment of a PDU session used for C2 communication. Further, the establishment of an Always-on PDU session can refer to the establishment of a PDU session that processes QoS flows used for C2 communication.

[0165] In addition, the twentieth identification information is information representing more than one cause value, which indicates the reason why the PDU session change process and / or PDU session release process is rejected. For example, the cause value can be information indicating that the UE is in flight, or information indicating a rejection other than the UE being in flight.

[0166] [3. First Implementation Method]

[0167] [3.1. The process used in the first embodiment]

[0168] First, the 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, and a PDU session release procedure. Each procedure will be described below.

[0169] It should be noted that, in the first embodiment, as Figure 2 The description uses the case where HSS and UDM, PCF and PCRF, SMF and PGW-C, and UPF and PGW-U are configured as the same device / function (in short, the same physical hardware, the same logical hardware, or the same software). However, the content described in this embodiment can also be applied to cases where they are configured as different devices / functions (in short, different physical hardware, different logical hardware, or different software). For example, data can be sent and received directly between them, via the N26 interface between AMF and MME, or via UE.

[0170] Next, use Figure 10 The communication process will be described below. Hereinafter, the communication process will also be referred to as this process, which includes the registration procedure, the UE-led PDU session establishment procedure, and the session management procedure. Details of the registration procedure, the PDU session establishment procedure, and the session management procedure will be described later.

[0171] Specifically, after each device performs the login process (S900), the UE transitions to the state of being logged into the network (RM-REGISTERED state). Next, after each device performs the PDU session establishment process (S902), the UE establishes a PDU session with the DN providing PDU connection services via the core network_B190, and each device transitions to the first state transition (S904). It should be noted that this assumes the PDU session is established via the access network and UPF_A235, but it is not limited to this. That is, there can also be a different UPF (UPF_C239) between UPF_A235 and the access network. In this case, the PDU session is established via the access network, UPF_C239, and UPF_A235. Then, each device in the first state can execute the session management process at any time (S906). Here, the session management process can be a network-led session management process or a UE-led session management process.

[0172] It should be noted that each device can execute the session management procedure multiple times. For example, each device can execute a second session management procedure after executing a first session management procedure. Here, the first session management procedure can be a network-led session management procedure or a UE-led session management procedure. Furthermore, the second session management procedure can be a network-led session management procedure or a UE-led session management procedure. Furthermore, the first session management procedure and the second session management procedure can be the same type of procedure or different types of procedure.

[0173] It should be noted that each device can exchange various capability information and / or request information during the login process and / or PDU session establishment process and / or network-led session management process. Furthermore, if each device has exchanged various information and / or negotiated various requests during the login process, it may or may not have done so during the PDU session establishment process and / or network-led session management process. Conversely, if each device has not exchanged various information and / or negotiated various requests during the login process, it may have done so during the PDU session establishment process and / or network-led session management process. Moreover, even if each device has exchanged various information and / or negotiated various requests during the login process, it may still do so during the PDU session establishment process and / or network-led session management process.

[0174] Furthermore, each device can perform the PDU session establishment process either during or after the login process. When the PDU session establishment process is performed during login, the PDU session establishment request message, the PDU session establishment acceptance message, the PDU session establishment completion message, and the PDU session establishment rejection message can all be included in and sent within the login request message. Additionally, when the PDU session establishment process is performed during login, each device can either establish a PDU session based on the completion of the login process or transition to a state where a PDU session has been established between the devices.

[0175] Furthermore, each device involved in this process can send and receive one or more identification information included in each control message by sending and receiving the control messages described in this process, and store the sent and received identification information as context.

[0176] also, Figure 11 The communication method of the UAV in this process is illustrated. It should be noted that a UAV can correspond to a UAV controller and be managed by core network devices and / or UTM. Furthermore, when a UAV corresponds to and is managed by a UAV controller, it can also be managed as a UAS by core network devices and / or UTM.

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

[0178] It should be noted that communication between the UAV and the first 3GPP PLMN can be performed using the UAV1 interface (S1400). Furthermore, communication between the UAV controller and the second 3GPP PLMN can also be performed using the UAV1 interface (S1402). Furthermore, communication between the UTM and the first and / or second 3GPP PLMN can be performed using the UAV6 interface.

[0179] Next, the UAV and UTM can communicate via the first 3GPP PLMN (S1410). Further, the UAV controller and UTM can communicate via the second 3GPP PLMN (S1412).

[0180] It should be noted that communication between the UAV and the UTM can be performed using the UAV9 interface (S1410). Furthermore, communication between the UAV controller and the UTM can also be performed using the UAV9 interface (S1412).

[0181] Next, the UAV and the UAV controller can also communicate with each other. Specifically, the UAV and the UAV controller can communicate via the first 3GPP PLMN and the second 3GPP PLMN without going through the UTM (S1404), or they can communicate via the first 3GPP PLMN, the UTM, and the second 3GPP PLMN (S1410) (S1412).

[0182] It should be noted that communication between the UAV and the UAV controller, via the first 3GPP PLMN and the second 3GPP PLMN without going through the UTM, can be performed using the UAV3 interface. Furthermore, communication between the UAV and the UAV controller, via the first 3GPP PLMN, the UTM, and the second 3GPP PLMN, can be performed using the UAV9 interface.

[0183] Here, the UAV1 interface can be an interface connecting the UAV and / or the UAV controller to the 3GPP PLMN. Further, the UAV3 interface can be an interface connecting the UAV and the UAV controller. Further, the UAV6 interface can be an interface connecting the UTM and the 3GPP PLMN. Further, the UAV9 interface can be an interface connecting the UAV and / or the UAV controller to the UTM.

[0184] Furthermore, the first 3GPP PLMN and the second 3GPP PLMN can be communication networks providing mobile wireless communication services. The first 3GPP PLMN and the second 3GPP PLMN can be communication networks comprised of an access network and / or a core network. Furthermore, the first 3GPP PLMN and the second 3GPP PLMN can be simply referred to as PLMNs. Here, the first 3GPP PLMN and the second 3GPP PLMN can be the same PLMN or different PLMNs.

[0185] It should be noted that the above example illustrates that the PLMN connected to the UAV is different from the PLMN connected to the UAV controller, but the PLMN connected to the UAV and the PLMN connected to the UAV controller can also be the same PLMN. In this case, the first 3GPP PLMN and the second 3GPP PLMN described above can be the same PLMN. Furthermore, in this case, the UAV, UAV controller, and UTM can be connected to the same PLMN. Furthermore, in this case, the communication between the first 3GPP PLMN and the second 3GPP PLMN can be communication within the same PLMN. For example, in this case, the communication between the UAV and the UAV controller that does not pass through the UTM (S1404) can be loopback communication within a single PLMN.

[0186] [3.2. The process of acquiring system information]

[0187] [3.3. Login Process]

[0188] Next, use Figure 6 The registration procedure is described below. In this chapter, this registration procedure will sometimes be referred to simply as "this procedure." The registration procedure is used by the UE to initiate the registration process with the access network_B and / or core network_B and / or DN. If the UE is not registered to the network, this procedure can be executed at any time, such as when the power is on. In other words, if the UE is in a non-registered state (5GMM-DEREGISTERED state), this procedure can begin at any time. Furthermore, each device (especially the UE and AMF) can transition to a registered state (5GMM-REGISTEDED state) based on the completion of the registration procedure. It should be noted that each registration state can be managed by each device on a per-access basis. Specifically, each device can independently manage the registration state (registered state or non-registered state) for 3GPP access and the registration state for non-3GPP access.

[0189] Furthermore, the login process can be a process for updating the location login information of the UE in the network and / or periodically notifying the network of the UE's status and / or updating specific parameters related to the UE in the network.

[0190] The UE can initiate the login process while moving across TAs. In other words, the UE can initiate the login process when moving to a TA different from the TA shown in its maintained TA list. Furthermore, the UE can also initiate the login process when the context of each device needs to be updated due to a PDU session disconnection or failure. Furthermore, the UE can also initiate the login process when capability information and / or preferences related to the establishment of the UE's PDU session change. Furthermore, the UE can also initiate the login process periodically. Furthermore, the UE can also initiate the login process based on the completion of the login process or the completion of the PDU session establishment process, or information received from the network during either process. It should be noted that the UE is not limited to these limitations and can execute the login process at any arbitrary time.

[0191] It should be noted that the process described above for transitioning from a UE not logged into the network (non-login state) to a logged-in state (login state) can be an initial registration procedure or a registration procedure for initial registration. Furthermore, the login procedure performed while the UE is logged into the network (login state) can also be a registration procedure for mobility and periodic registration update or a mobility and periodic registration procedure.

[0192] First, the UE initiates the login process by sending a Registration Request message (S600)(S602)(S604) to the AMF. Specifically, the UE sends an RRC message including the login request message to the base station device (also known as the 5G AN, gNB) (S600). It should be noted that the login request message can be a NAS message transmitted and received on the N1 interface. Furthermore, the RRC message can be a control message transmitted and received between the UE and the base station device. Additionally, NAS messages are processed at the NAS layer, and RRC messages are processed at the RRC layer. It should be noted that the NAS layer is a higher layer than the RRC layer.

[0193] Here, the UE may include and send identification information indicating the type of this procedure in the login request message and / or RRC message. This identification information may be a 5GS login type IE (Information Element), or information indicating whether the procedure is for initial login, login information updates accompanying movement, periodic login information updates, or login in an emergency.

[0194] The UE can include its capability information in the login request message to notify the network of the functions it supports. Here, the UE's capability information can be the 5GMM capability IE of the 5GS.

[0195] The UE can include this identification information in control messages that are different from these messages, such as control messages from layers lower than the RRC layer (e.g., MAC (Medium Access Control), RLC (Radio Link Control), PDCP (Packet Data Convergence Protocol), SDAP (Service Data Adaptation Protocol), etc.). It should be noted that by sending this identification information, the UE can indicate that it supports various functions, make a request, or both.

[0196] The UE may include, for example, UE ID and / or PLMN ID and / or AMF identification information in the login request message and / or RRC message and send it. Here, AMF identification information may refer to information that identifies an AMF or a set of AMFs, such as 5G-S-TMSI (5G S-Temporary Mobile Subscription Identifier) ​​or GUAMI (Globally Unique AMF Identifier).

[0197] When the base station receives an RRC message that includes a login request message, it selects an AMF to forward the login request message (S602). The base station extracts the login request message from the received RRC message and forwards the login request message to the selected AMF (S604).

[0198] Upon receiving a login request message, the AMF can perform a first condition check. The first condition check is used to determine whether the network accepts the UE's request. If the first condition check is true, the AMF can execute procedures S610 to S612. Alternatively, the AMF can execute procedure S610 if the first condition check is false.

[0199] Furthermore, the first condition determination can also be performed by a network function other than the AMF (also known as an NF). This NF could be, for example, the NSSF (Network Slice Selection Function), NWDAF (Network Data Analysis Function), or PCF (Policy Control Function). When the first condition determination is performed by an NF other than the AMF, the AMF can provide that NF with the information required to perform the first condition determination, specifically providing at least a portion of the information received from the UE (S606). Further, if the NF determines the truth or falsehood of the first condition determination based on the information received from the AMF, it can transmit information including the result of the first condition determination (in short, whether it is true or false) to the AMF. The AMF can then determine the identification information and / or control messages to be sent to the UE based on the result of the first condition determination received from that NF.

[0200] It should be noted that if the first condition is true, the control message sent and received in S610 can be a Registration accept message, and if the first condition is false, the control message sent and received in S610 can be a Registration reject message.

[0201] It should be noted that the first condition determination can be performed based on the receipt of the login request message and / or the various identification information and / or subscriber information and / or network capability information and / or operator policies and / or network status and / or user login information and / or the context maintained by the AMF, etc.

[0202] For example, if the network allows the UE's request, the first condition determination can be determined as true; if the network does not allow the UE's request, the first condition determination can be determined as false. Furthermore, if the network and / or devices within the UE's login destination network support the function requested by the UE, the first condition determination can be determined as true; if the requested function is not supported, the first condition determination can be determined as false. Further, if the transmitted and received identification information is allowed, the first condition determination can be determined as true; if the transmitted and received identification information is not allowed, the first condition determination can be determined as false.

[0203] In addition, the AMF can indicate that the UE's request has been accepted by sending a login acceptance message based on the received identification information and / or subscriber information and / or network capability information and / or operator policies and / or network status and / or user login information and / or the context maintained by the AMF, or it can indicate that the UE's request has been rejected by sending a login rejection message.

[0204] The UE receives a control message (login acceptance message or login rejection message) via the base station device (S610). When the control message is a login acceptance message, the UE can identify whether the UE's request based on the login request message has been accepted and the content of various identification information included in the login acceptance message by receiving the login acceptance message. Similarly, when the control message is a login rejection message, the UE can identify whether the UE's request based on the login request message has been rejected and the content of various identification information included in the login rejection message by receiving the login rejection message.

[0205] Furthermore, when the control message is a login acceptance message, the UE can send a login completion message to the AMF via the first base station device as a response message to the login acceptance message (S612). Here, the login completion message is a NAS message transmitted and received on the N1 interface, but it can also be transmitted and received between the UE and the first base station device within an RRC message.

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

[0207] In addition, each device can also complete the login process based on the sending and receiving of login rejection messages.

[0208] It should be noted that each device can also transition to or maintain the UE's network-logged-in state (RM_REGISTERED state or 5GMM-REGISTERED state) based on the transmission and reception of login acceptance messages and / or login completion messages. Conversely, it can transition to or maintain the non-network-logged-in state (RM_DEREGISTERED state or 5GMM-DEREGISTERED state) when the UE receives a login rejection message for the current PLMN during access. Furthermore, transitions to different states can also be based on the transmission and reception of login completion messages or the completion of the login process.

[0209] Furthermore, each device can perform processing based on the information sent and received during the login process upon completion of the login process. For example, in the case of sending and receiving information indicating that a portion of the UE's request was rejected, the reason for the UE's request rejection can be identified. Furthermore, each device can re-enact the process based on the reason for the UE's request rejection, or it can perform the login process on the core network_A or other cells.

[0210] Furthermore, the UE can store the identification information received along with the login acceptance message and / or login rejection message based on the completion of the login process, and can also identify the network.

[0211] It should be noted that the login process described in this chapter can be a login process for initial login, or a login process for mobile and periodic login.

[0212] [3.4. PDU Session Establishment Process]

[0213] use Figure 7 This chapter describes the behavior of each device when the UE performs the PDU session establishment process. In this chapter, the PDU session establishment process is sometimes referred to simply as this process or the PDU session establishment process.

[0214] It should be noted that this process can be executed after the process in Chapter 3.3 has been executed more than once.

[0215] First, the UE sends a PDU session establishment request message to the SMF and begins the PDU session establishment process. Then, the SMF receives the PDU session establishment request message from the UE.

[0216] Specifically, the UE initiates the PDU session establishment process by sending a NAS message (S800) containing an N1 SM container to the AMF via the access network. This N1 SM container includes a PDU session establishment request message. The NAS message is, for example, a message sent via the N1 interface, and can be an uplink NAS transfer (UL NAS TRANSPORT) message.

[0217] Here, the access network is either 3GPP access or non-3GPP access, and may include base station equipment. That is, the UE sends NAS messages to the AMF via the base station equipment.

[0218] Furthermore, by including and sending the first identification information in the PDU session establishment request message and / or N1 SM container and / or NAS message, the UE can notify the network side of the UE's request. Here, the first identification information can be as described in Chapter 2.7.

[0219] Furthermore, in the case of establishing an Always-on PDU session, the UE can include and send the first identification information in the PDU session establishment request message and / or N1 SM container and / or NAS message.

[0220] Here, when establishing a PDU session supporting C2 communication, the UE can include and send the first identification information in the PDU session establishment request message and / or N1 SM container and / or NAS message. In other words, when establishing a PDU session supporting QoS flows for C2 communication, the UE can include and send the first identification information in the PDU session establishment request message and / or N1 SM container and / or NAS message.

[0221] Furthermore, when requesting the establishment of a PDU session supporting C2 communication, the UE can request the establishment of an Always-on PDU session. In other words, when requesting the establishment of a PDU session supporting QoS flows for C2 communication, the UE can request the establishment of an Always-on PDU session.

[0222] Furthermore, when establishing a PDU session providing C2 communication, the UE can include and send the first identification information in the PDU session establishment request message and / or N1 SM container and / or NAS message. In other words, when establishing a PDU session providing a QoS flow for C2 communication, the UE can include and send the first identification information in the PDU session establishment request message and / or N1 SM container and / or NAS message.

[0223] Furthermore, when requesting the establishment of a PDU session to provide C2 communication, the UE can request the establishment of an Always-on PDU session. In other words, when requesting the establishment of a PDU session to provide QoS flows for C2 communication, the UE can request the establishment of an Always-on PDU session.

[0224] Furthermore, in the event of a request to establish an Always-on PDU session, the UE may include and send the first identification information in the PDU session establishment request message and / or the N1 SM container and / or the NAS message.

[0225] It should be noted that the UE may determine whether to send the first identification information to the network based on the UE's capability information and / or UE policies and / or UE status and / or user login information and / or the context maintained by the UE.

[0226] It should be noted that the UE may also include this identification information in control messages that are different from these messages, such as control messages of layers lower than the NAS layer (e.g., RRC layer, MAC layer, RLC layer, PDCP layer, SDAP layer, etc.) or control messages of layers higher than the NAS layer (e.g., transport layer, session layer, presentation layer, application layer, etc.) and send them.

[0227] Next, when receiving NAS messages, the AMF can identify the UE request and / or the content of information (messages, containers, information) included in the NAS messages.

[0228] Next, the AMF selects the SMF as the forwarding destination for at least a portion of the information (messages, containers, information) included in the NAS message received from the UE (S802). It should be noted that the AMF may select the SMF as the forwarding destination based on the information (messages, containers, information) included in the NAS message and / or subscriber information and / or network capability information and / or UE policies and / or operator policies and / or network status and / or user login information and / or the context maintained by the AMF.

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

[0230] Next, when the SMF receives information (messages, containers, messages) sent from the AMF, it can identify the situation of the UE request and / or the content of the information (messages, containers, messages) received from the AMF.

[0231] Here, SMF can perform a second condition check. Furthermore, the second condition check can be used to determine whether the network accepts the UE's request. SMF can begin processing the request if the second condition check is true. Figure 7 (A) begins when the second condition is determined to be false. Figure 7 (B) process.

[0232] It should be noted that the second condition determination can also be performed by an NF other than the SMF. This NF could be, for example, the NSSF, NWDAF, PCF, or NRF. When the second condition determination is performed by an NF other than the SMF, the SMF can provide that NF with the information required for the second condition determination, specifically providing at least a portion of the information received from the UE (S806). Then, if the NF determines the truth or falsehood of the second condition determination based on the information received from the SMF, it can transmit information including the result of the second condition determination (in short, whether it is true or false) to the SMF. The SMF can then determine the identification information and / or control messages that should be sent to the UE based on the result of the second condition determination received from that NF.

[0233] It should be noted that the second condition determination can be performed based on information received from the AMF (messages, containers, information) and / or subscription information and / or network capability information and / or UE policies and / or operator policies and / or network status and / or user login information and / or the context maintained by the SMF.

[0234] For example, if the network allows the UE's request, the second condition can be determined to be true; if the network does not allow the UE's request, the second condition can be determined to be false. Furthermore, if the network at the UE's connection destination and / or devices within that network support the function requested by the UE, the second condition can be determined to be true; if the requested function is not supported, the second condition can be determined to be false. Additionally, if the transmitted and received identification information is allowed, the second condition can be determined to be true; if the transmitted and received identification information is not allowed, the second condition can be determined to be false.

[0235] Furthermore, if the SMF receives a control message (PDU session establishment request message and / or N1 SM container and / or NAS message) from the UE that does not include the first identification information, the truth or falsehood of the second condition can be determined based on the above.

[0236] It should be noted that the conditions for determining the truth or falsehood of the second condition are not limited to the conditions mentioned above.

[0237] Next, regarding Figure 7(A) will explain each step of the process.

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

[0239] Here, the SMF can select one or more UPFs based on information received from the AMF (messages, containers, information) and / or information such as PCC rules received from the PCF and / or subscriber information and / or network capability information and / or UE policies and / or operator policies and / or network status and / or user login information and / or the context maintained by the SMF. Furthermore, if multiple UPFs are selected, the SMF can send an N4 session establishment request message to each UPF. Here, we assume that a UPF has been selected.

[0240] Next, when the UPF receives the N4 session establishment request message (S808), it can identify the content of the information received from the SMF. Furthermore, the UPF can also send an N4 session establishment response message to the SMF via the N4 interface based on the receipt of the N4 session establishment request message (S810).

[0241] Next, when the SMF receives the N4 session establishment response message as a response to the N4 session establishment request message, it can identify the content of the information received from the UPF.

[0242] Next, the SMF sends a PDU session establishment acceptance message to the UE based on the receipt of the PDU session establishment request message and / or the selection of the UPF and / or the receipt of the N4 session establishment response message. Then, the UE receives the PDU session establishment acceptance message from the SMF.

[0243] Specifically, the SMF receives PDU session establishment request messages and / or selects UPF and / or receives N4 session establishment response messages, for example, by sending the N1 SM container and / or N2 SM information and / or PDU session ID to the AMF via the N11 interface (S812). Here, the N1 SM container may include a PDU session establishment acceptance message. Furthermore, the PDU session ID may be included in the PDU session establishment acceptance message.

[0244] Next, the AMF, having received the N1 SM container and / or N2 SM information and / or PDU session ID, sends a NAS message to the UE via the first base station device included in the access network (S814)(S816). Here, the NAS message is sent, for example, via the N1 interface. Furthermore, the NAS message can be a downlink NAS transport (DL NAS TRANSPORT) message.

[0245] Specifically, when the AMF sends an N2 PDU session request message to a base station device included in the access network (S814), the base station device receiving the N2 PDU session request message sends a NAS message to the UE (S816). Here, the N2 PDU session request message may include a NAS message and / or N2 SM information. In addition, the NAS message may include a PDU session ID and / or an N1 SM container.

[0246] Furthermore, a PDU session establishment acceptance message can be a response message to a PDU session establishment request. Additionally, a PDU session establishment acceptance message can indicate that the establishment of a PDU session has been accepted.

[0247] Here, the SMF and / or AMF can indicate that at least a portion of the UE's request based on the PDU session establishment request message has been accepted by sending a PDU session establishment accept message and / or an N1 SM container and / or a PDU session ID and / or a NAS message and / or an N2 SM information and / or an N2 PDU session request message.

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

[0249] It should be noted that by sending these identification information and / or PDU session establishment acceptance messages, the SMF can indicate that the network supports various functions, that the UE's request is accepted, that requests from the UE are not allowed, or a combination of these information. Furthermore, when sending and receiving multiple identification information, two or more of these identification information can constitute one or more identification information. It should also be noted that information indicating support for various functions and information indicating a request to use various functions can be sent and received as the same identification information or as different identification information.

[0250] Furthermore, the SMF can include the second identification information in the PDU session establishment accept message and send it based on the first identification information received from the UE. In other words, the SMF can include the second identification information in the PDU session establishment accept message and send it after receiving the first identification information from the UE.

[0251] Furthermore, when the UE establishes a PDU session supporting C2 communication, the SMF can include the second identification information in the PDU session establishment accept message and send it. In other words, when the UE establishes a PDU session supporting QoS flows for C2 communication, the SMF can include the second identification information in the PDU session establishment accept message and send it.

[0252] Furthermore, when the UE establishes a PDU session providing C2 communication, the SMF can include the second identification information in the PDU session establishment accept message and send it. In other words, when the UE establishes a PDU session providing a QoS flow for C2 communication, the SMF can include the second identification information in the PDU session establishment accept message and send it.

[0253] Here, when the UE indicates whether to allow the establishment of a PDU session as an Always-on PDU session, the SMF may include second identification information in the PDU session establishment acceptance message.

[0254] Furthermore, where establishing a PDU session as an Always-on PDU session is permitted, the SMF can include second identification information in the PDU session establishment acceptance message. In this case, the second identification information may be information indicating that an Always-on PDU session needs to be established.

[0255] Furthermore, if establishing a PDU session as an Always-on PDU session is not permitted, the SMF may include second identification information in the PDU session establishment acceptance message. In this case, the second identification information may be information indicating that an Always-on PDU session is not permitted.

[0256] Here, the Always-on PDU session can be a PDU session that supports C2 communication. In other words, the Always-on PDU session can be a PDU session that supports QoS flows for C2 communication.

[0257] By sending at least one of these identification information, the SMF and / or AMF can inform the UE of the content of these identification information.

[0258] It should be noted that the SMF and / or AMF can determine which identification information to include in the PDU session establishment accept message and / or N1 SM container and / or NAS message and / or N2 SM information and / or N2 PDU session request message based on the 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 login information and / or the context maintained by the SMF and / or AMF.

[0259] Next, when the UE receives a NAS message via the N1 interface (S816), it can identify the content of the UE's request to establish a PDU session request message being accepted and / or the information (message, container, information) included in the NAS message.

[0260] Furthermore, the UE can identify whether the accepted PDU session is an Always-on PDU session based on the receipt of the second identification information or a PDU session establishment accept message or an N1 SM container or NAS message that includes the second identification information. In other words, when the UE receives the second identification information or a PDU session establishment accept message or an N1 SM container or NAS message that includes the second identification information, it can identify whether the accepted PDU session is an Always-on PDU session.

[0261] Specifically, when a UE receives second identification information or a PDU session establishment acceptance message, N1 SM container, or NAS message that includes the second identification information, if the received second identification information is set to indicate that an Always-on PDU session needs to be established, the UE can identify the accepted PDU session as an Always-on PDU session. Conversely, when a UE receives second identification information or a PDU session establishment acceptance message, N1 SM container, or NAS message that includes the second identification information, if the received second identification information is set to indicate that an Always-on PDU session is not allowed, the UE can identify the accepted PDU session as not an Always-on PDU session.

[0262] Here, the Always-on PDU session can be a PDU session that supports C2 communication. In other words, the Always-on PDU session can be a PDU session that supports QoS flows for C2 communication.

[0263] Next, regarding Figure 7 (B) The process steps are explained.

[0264] First, the SMF receives the PDU session establishment request message, for example, by sending the N1 SM container and / or the PDU session ID to the AMF (S818) via the N11 interface. 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.

[0265] Next, the AMF, having received the N1 SM container and / or PDU session ID, sends a NAS message to the UE via a base station device included in the access network (S820)(S822). Here, the NAS message is sent, for example, via the N1 interface. Furthermore, the NAS message can be a downlink NAS transport (DL NAS TRANSPORT) message. Additionally, the NAS message may include the PDU session ID and / or the N1 SM container.

[0266] Furthermore, a PDU session establishment rejection message can be a response message to a PDU session establishment request. Additionally, a PDU session establishment rejection message can indicate that the establishment of a PDU session has been rejected.

[0267] Here, the SMF and / or AMF can indicate that the UE's request based on 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 a NAS message.

[0268] It should be noted that SMF can indicate that the UE's request is rejected, that requests from the UE are not allowed, or a combination of these information by sending a PDU session establishment rejection message.

[0269] By sending at least one of these identification information, the SMF and / or AMF can inform the UE of the content of these identification information.

[0270] It should be noted that the SMF and / or AMF can determine which identification information to include in the PDU session establishment rejection message and / or N1 SM container and / or NAS message and / or N2 SM information and / or N2 PDU session request message based on the 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 login information and / or the context maintained by the SMF and / or AMF.

[0271] Next, when the UE receives a NAS message via the N1 interface (S822), it can identify the content of the UE's request to establish a session based on the PDU message being rejected and / or the information (message, container, information) included in the NAS message.

[0272] Each device can complete this process by establishing and receiving message transmission and reception based on the PDU session. At this point, each device can transition to a state where it can communicate with the DN using the established PDU session.

[0273] Each device can also complete this process by sending and receiving accept messages or reject messages based on the establishment of a PDU session. In this case, each device cannot establish a PDU session, and therefore cannot communicate with the DN if no PDU session has been established.

[0274] It should be noted that, as mentioned above, the processes performed by the UE based on the receipt of each identification information can be performed during this process or after the completion of this process, or they can be performed after the completion of this process based on the completion of this process.

[0275] [3.5. Overview of Network-Driven Session Management Process]

[0276] Next, an overview of the network-led session management process will be provided. Hereinafter, the network-led session management process will also be referred to as this process. This process is used for session management performed by the network for established PDU sessions.

[0277] It should be noted that this process can be a network-led PDU session change (PDU session change) process and / or a network-led PDU session release (PDU session release) process, or it can execute network-led session management processes that are not limited to these. It should also be noted that each device can send and receive PDU session change messages during a network-led PDU session change process, and can also send and receive PDU session release messages during a network-led PDU session release process.

[0278] Furthermore, when this process is a network-led PDU session modification process, the session management request message in this process can be a PDU session modification command (PDU SESSION MODIFICATION COMMAND) message. Similarly, when this process is a network-led PDU session release process, the session management request message in this process can be a PDU session release command (PDU SESSION RELEASE COMMAND) message.

[0279] Furthermore, when this process is a network-led PDU session modification process, the session management completion message in this process can be a PDU session modification completion message. Conversely, when this process is a network-led PDU session release process, the session management completion message in this process can be a PDU session release completion message.

[0280] Furthermore, in this process, the UE can be either a UAV or a UAV controller. [3.5.1. Example of a network-led session management process]

[0281] use Figure 8 An example of a network-led session management process is illustrated below. In this chapter, this process refers to a network-led session management process. The steps of this process are described below.

[0282] Based on the completion of the login process and / or PDU session establishment process, the UE and each device in the core network_B190 start the network-led session management process at any time.

[0283] Specifically, devices within the core network_B190 can initiate this process based on the receipt of a PDU session change request message or a PDU session release request message. It should be noted that when the process is initiated based on the receipt of a PDU session change request message, this process can be a network-led PDU session change process. Furthermore, when the process is initiated based on the receipt of a PDU session release request message, this process can be a network-led PDU session release process.

[0284] Furthermore, devices within the core network_B190 can initiate this process based on requests from devices in the DN or other devices within the core network. Specifically, devices within the core network_B190 can initiate this process based on requests from the UTM. In other words, devices within the core network_B190 can initiate this process upon receiving a request from the UTM.

[0285] Here, the device within the core network_B190 that initiates this process can be an SMF and / or an AMF, and the UE can send and receive messages in this process via the AMF and / or the access network_B. Furthermore, the device located in the DN can be an AF (Application Function) located in the DN.

[0286] The device within the core network_B190 sends a network-led session management request message to the UE (S1202) to initiate network-led session management. Further, the UE receives the network-led session management request message from the device within the core network_B190.

[0287] Here, the devices within the core network_B190 may include at least one of the tenth to fourteenth identification messages in the network-led session management request message. By including this identification information, a request from the core network_B190 can be indicated. Furthermore, the devices within the core network_B190 may include a PDU session ID in the network-led session change request message, or they may request changes to a PDU session identified by the PDU session ID by including the PDU session ID.

[0288] Here, in the event of a change in the UAV controller's identification information, devices within the core network_B190 can include the tenth identification information in the network-dominated session management request message. Furthermore, in the event of a change in the UAV controller's IP address, devices within the core network_B190 can also include the tenth identification information in the network-dominated session management request message.

[0289] Furthermore, with a new UAV controller assigned, devices within the core network_B190 can include tenth identification information in network-dominated session management request messages. Furthermore, with a new UAV controller's IP address assigned, devices within the core network_B190 can also include tenth identification information in network-dominated session management request messages.

[0290] Furthermore, in the event of a change in the UAV controller's IP address, devices within the core network_B190 can include eleventh identification information in the network-dominated session management request message. Furthermore, in the event of a change in the UAV controller's identification information, devices within the core network_B190 can also include eleventh identification information in the network-dominated session management request message.

[0291] Furthermore, with a new UAV controller IP address assigned, devices within the core network_B190 can include eleventh identification information in network-dominated session management request messages.

[0292] Furthermore, in the event of a change in the UAV's identification information, devices within the core network_B190 can include twelfth identification information in the network-dominated session management request message. Furthermore, in the event of a change in the UAV's IP address, devices within the core network_B190 can also include twelfth identification information in the network-dominated session management request message.

[0293] Furthermore, when a new UAV is assigned, devices within the core network_B190 can include twelfth identification information in the network-dominated session management request message. Furthermore, when a new UAV's IP address is assigned, devices within the core network_B190 can also include twelfth identification information in the network-dominated session management request message.

[0294] Furthermore, in the event of a change in the UAV's IP address, devices within the core network_B190 can include thirteenth identification information in the network-dominated session management request message. Furthermore, in the event of a change in the UAV's identification information, devices within the core network_B190 can also include thirteenth identification information in the network-dominated session management request message.

[0295] Furthermore, when a new UAV's IP address is assigned, devices within the core network_B190 can include thirteenth identification information in the network-dominated session management request message.

[0296] Furthermore, when determining whether the PDU session transmitted to the UE is an Always-on PDU session, the device within the core network_B190 can include the fourteenth identification information in the network-led session management request message. Furthermore, when the information regarding whether the PDU session is an Always-on PDU session changes, the device within the core network_B190 can include the fourteenth identification information in the network-led session management request message.

[0297] Furthermore, when it is necessary to change an established PDU session to an Always-on PDU session, devices within the core network_B190 can include fourteenth identification information in the network-dominated session management request message. In this case, the fourteenth identification information can be information indicating that an Always-on PDU session needs to be established.

[0298] Furthermore, when it is necessary to change an established PDU session into a PDU session that is not an Always-on PDU session, devices within the core network_B190 can include fourteenth identification information in the network-dominated session management request message. In this case, the fourteenth identification information may be information indicating that the establishment of an Always-on PDU session is not permitted.

[0299] It should be noted that the PDU session ID included in the PDU session change request message can be the PDU session ID of the established PDU session. Furthermore, when this process is executed based on the UE-led session management process, the PDU session ID included in the PDU session change request message can be the same as the PDU session ID included in the PDU session change request message or the PDU session release request message.

[0300] Next, the UE that received the network-led session management request message sends a network-led session management completion message (S1204). Further, the UE may also perform the first process (S1206) based on at least one of the tenth to fourteenth identification information received from the core network_B190, thus completing this process. Furthermore, the UE may implement the first process based on the completion of this process.

[0301] Here, the UE may also include the PDU session ID in the network-led session management completion message. It should be noted that the PDU session ID included in the network-led session management completion message can be the same as the PDU session ID included in the network-led session management request message.

[0302] The following is an example of the first processing step.

[0303] Here, the first process can be the UE recognizing the matter indicated by the core network_B190, or it can be the process of recognizing the request from the core network_B190. Further, the first process can be the UE storing the received identification information as context, or it can be the process of forwarding the received identification information to the upper and / or lower layers.

[0304] In the first process, the UE can update the identification information of the UAV controller stored in the UE to the identification information of the UAV controller shown in the tenth identification information based on the received tenth identification information. Here, the UE can be a UAV. Furthermore, the UAV controller can be a UAV controller corresponding to the UAV.

[0305] In other words, when the UE receives the tenth identification information, it can update the identification information of the UAV controller stored in the UE to the identification information of the UAV controller shown in the tenth identification information during the first process.

[0306] Furthermore, based on the receipt of the tenth identification information, the UE can, in the first process, delete the UAV controller's stored identification information and store the received tenth identification information as the UAV controller's identification information. In other words, upon receiving the tenth identification information, the UE can, in the first process, delete the UAV controller's stored identification information and store the received tenth identification information as the UAV controller's identification information.

[0307] Furthermore, based on the receipt of the tenth identification information, the UE can identify the identification information of the new UAV controller in the first process. In other words, upon receiving the tenth identification information, the UE can identify the identification information of the new UAV controller in the first process.

[0308] More specifically, based on the receipt of the tenth identification information, the UE can, in the first process, identify the old UAV controller's identification information as invalid and the new UAV controller's identification information as valid. In other words, upon receiving the tenth identification information, the UE can, in the first process, identify the old UAV controller's identification information as invalid and the new UAV controller's identification information as valid.

[0309] Here, the identification information of the new UAV controller can be the information shown in the received tenth identification information. Furthermore, the identification information of the old UAV controller can be the UAV controller identification information stored in the UE.

[0310] In the first process, the UE can update the IP address of the UAV controller stored in the UE to the IP address of the UAV controller shown in the eleventh identification information based on the received eleventh identification information. Here, the UE can be a UAV. Furthermore, the UAV controller can be a UAV controller corresponding to the UAV.

[0311] In other words, upon receiving the eleventh identification information, the UE can update the IP address of the UAV controller stored in the UE to the IP address of the UAV controller shown in the eleventh identification information during the first processing.

[0312] Furthermore, based on the receipt of the eleventh identification information, the UE can, in the first process, delete the UAV controller's stored IP address and store the received eleventh identification information as the UAV controller's IP address. In other words, upon receiving the eleventh identification information, the UE can, in the first process, delete the UAV controller's stored IP address and store the received eleventh identification information as the UAV controller's IP address.

[0313] Furthermore, based on the receipt of the eleventh identification information, the UE can identify the IP address of the new UAV controller in the first process. In other words, upon receiving the eleventh identification information, the UE can identify the IP address of the new UAV controller in the first process.

[0314] More specifically, based on the receipt of the eleventh identification information, the UE can, in the first process, identify the old UAV controller's IP address as invalid and the new UAV controller's IP address as valid. In other words, upon receiving the eleventh identification information, the UE can, in the first process, identify the old UAV controller's IP address as invalid and the new UAV controller's IP address as valid.

[0315] Here, the IP address of the new UAV controller can be the information shown in the received eleventh identification information. Furthermore, the IP address of the old UAV controller can be the IP address of the UAV controller stored in the UE.

[0316] Furthermore, based on the receipt of the tenth identification information and / or the eleventh identification information, the UE can update the IP address of the UAV controller identified by the tenth identification information to the IP address shown in the eleventh identification information during the first process. In other words, upon receiving the tenth identification information and / or the eleventh identification information, the UE can update the IP address of the UAV controller identified by the tenth identification information to the IP address shown in the eleventh identification information during the first process.

[0317] Furthermore, based on the receipt of the tenth identification information and / or the eleventh identification information, the UE can, in the first process, delete the IP address of the UAV controller identified by the tenth identification information and store the IP address shown in the eleventh identification information as the IP address of the UAV controller identified by the tenth identification information. In other words, when the UE receives the tenth identification information and / or the eleventh identification information, in the first process, it can delete the IP address of the UAV controller identified by the tenth identification information and store the IP address shown in the eleventh identification information as the IP address of the UAV controller identified by the tenth identification information.

[0318] In the first process, the UE can update the identification information of the UAV stored in the UE to the identification information of the UAV shown in the twelfth identification information based on the received twelfth identification information. Here, the UE can also be a UAV controller. Furthermore, the UAV can be a UAV corresponding to the UAV controller.

[0319] In other words, when the UE receives the twelfth identification information, it can update the identification information of the UAV stored in the UE to the identification information of the UAV shown in the twelfth identification information in the first process.

[0320] Furthermore, based on the receipt of the twelfth identification information, the UE can, in the first process, delete the UAV identification information stored in the UE's memory and store the received twelfth identification information as the UAV's identification information. In other words, upon receiving the twelfth identification information, the UE can, in the first process, delete the UAV identification information stored in the UE's memory and store the received twelfth identification information as the UAV's identification information.

[0321] Furthermore, based on the receipt of the twelfth identification information, the UE can identify the identification information of the new UAV in the first process. In other words, upon receiving the twelfth identification information, the UE can identify the identification information of the new UAV in the first process.

[0322] More specifically, based on the receipt of the twelfth identification information, the UE can, in the first process, identify the old UAV's identification information as invalid and the new UAV's identification information as valid. In other words, upon receiving the twelfth identification information, the UE can, in the first process, identify the old UAV's identification information as invalid and the new UAV's identification information as valid.

[0323] Here, the identification information of the new UAV can be the information shown in the received twelfth identification information. Furthermore, the identification information of the old UAV can be the UAV identification information stored by the UE.

[0324] In the first process, the UE can update the IP address of the UAV stored in the UE to the IP address of the UAV shown in the thirteenth identification information based on the received thirteenth identification information. Here, the UE can also be a UAV controller. Furthermore, the UAV can be a UAV corresponding to the UAV controller.

[0325] In other words, when the UE receives the thirteenth identification information, it can update the IP address of the UAV stored in the UE to the IP address of the UAV shown in the thirteenth identification information during the first process.

[0326] Furthermore, based on the receipt of the thirteenth identification information, the UE can, in the first process, delete the UAV's IP address stored in the UE's memory and store the received thirteenth identification information as the UAV's IP address. In other words, upon receiving the thirteenth identification information, the UE can, in the first process, delete the UAV's IP address stored in the UE's memory and store the received thirteenth identification information as the UAV's IP address.

[0327] Furthermore, based on the receipt of the thirteenth identification information, the UE can identify the IP address of the new UAV in the first process. In other words, upon receiving the thirteenth identification information, the UE can identify the IP address of the new UAV in the first process.

[0328] More specifically, based on the receipt of the thirteenth identification information, the UE can, in the first process, identify the old UAV's IP address as invalid and the new UAV's IP address as valid. In other words, upon receiving the thirteenth identification information, the UE can, in the first process, identify the old UAV's IP address as invalid and the new UAV's IP address as valid.

[0329] Here, the new UAV's IP address can be the information shown in the received thirteenth identification information. Furthermore, the old UAV's IP address can be the UAV's IP address stored in the UE.

[0330] Furthermore, based on the receipt of the twelfth and / or thirteenth identification information, the UE can update the IP address of the UAV identified by the twelfth identification information to the IP address shown in the thirteenth identification information during the first process. In other words, upon receiving the twelfth and / or thirteenth identification information, the UE can update the IP address of the UAV identified by the twelfth identification information to the IP address shown in the thirteenth identification information during the first process.

[0331] Furthermore, based on the receipt of the twelfth and / or thirteenth identification information, the UE can, in the first process, delete the IP address of the UAV identified by the twelfth identification information and store the IP address shown in the thirteenth identification information as the IP address of the UAV identified by the twelfth identification information. In other words, upon receiving the twelfth and / or thirteenth identification information, the UE can, in the first process, delete the IP address of the UAV identified by the twelfth identification information and store the IP address shown in the thirteenth identification information as the IP address of the UAV identified by the twelfth identification information.

[0332] In the first process, the UE can identify whether the established PDU session is an Always-on PDU session based on the receipt of the fourteenth identification information. In other words, upon receiving the fourteenth identification information, the UE can identify whether the established PDU session is an Always-on PDU session in the first process.

[0333] Specifically, when the UE receives the fourteenth identification information, if the received fourteenth identification information is set to indicate that an Always-on PDU session needs to be established, the UE can identify the established and / or modified PDU session as an Always-on PDU session in the first processing. Conversely, if the UE receives the fourteenth identification information, if the received fourteenth identification information is set to indicate that an Always-on PDU session is not allowed, the UE can identify the established and / or modified PDU session as not an Always-on PDU session in the first processing.

[0334] Furthermore, if the UE does not receive the fourteenth identification information, it can identify whether the established and / or modified PDU session is an Always-on PDU session based on the second identification information and / or the fourteenth identification information received during the previous execution process.

[0335] Specifically, if the UE has not received the fourteenth identification information, and the second and / or fourteenth identification information received during previous execution is set to indicate that an Always-on PDU session needs to be established, then in the first processing, the established and / or modified PDU session can be identified as an Always-on PDU session. Conversely, if the UE has not received the fourteenth identification information, and the second and / or fourteenth identification information received during previous execution is set to indicate that an Always-on PDU session is not allowed, then in the first processing, the established and / or modified PDU session can be identified as not an Always-on PDU session.

[0336] Here, the Always-on PDU session can be a PDU session that supports C2 communication. In other words, the Always-on PDU session can be a PDU session that supports QoS flows for C2 communication.

[0337] Furthermore, each device can perform processing based on the identification information transmitted and received during this process based on the completion of this process. In other words, the UE can perform the first processing based on the completion of this process, or it can complete this process after the first processing is completed.

[0338] Furthermore, each device completes the first network-led session management process based on the completion of the above-mentioned processing and / or the sending and receiving of network-led session management request messages and / or network-led session management completion messages.

[0339] [3.6. Overview of UE-led Session Management Process]

[0340] Next, an overview of the UE-led session management process will be provided. Hereinafter, the UE-led session management process will also be referred to as this process. This process is used for session management performed by the UE for established PDU sessions.

[0341] It should be noted that this process can be a UE-led PDU session change (PDU session change) process and / or a UE-led PDU session release (PDU session release) process, or it can execute UE-led session management processes that are not limited to these. It should also be noted that each device can send and receive PDU session change request messages and / or PDU session change command messages and / or PDU session change completion messages and / or PDU session change rejection messages during the UE-led PDU session change process. Similarly, each device can send and receive PDU session release request messages and / or PDU session release command messages and / or PDU session release completion messages and / or PDU session release rejection messages during the UE-led PDU session release process.

[0342] Furthermore, each device completes the UE-led session management process based on the completion of the above-mentioned processing and / or the sending and receiving of UE-led session management request messages and / or UE-led session management completion messages.

[0343] [3.6.1. Example of UE-led PDU session change process]

[0344] In this chapter, this process refers to the UE-led PDU session change process. The following uses... Figure 9 The steps of this process are explained.

[0345] It should be noted that, based on the completion of the login process and / or PDU session establishment process, the UE can initiate a UE-led PDU session change process at any time. In other words, the UE can initiate a UE-led PDU session change process for the established PDU session at any time. Further, the UE can initiate a UE-led PDU session change process using the same PDU session ID as the established PDU session at any time.

[0346] First, the UE initiates a UE-led PDU session change process by sending a PDU session change request message (S1302) to the SMF. Here, the UE can include the PDU session ID in the PDU session change request message, or it can request a change to the PDU session identified by the PDU session ID by including the PDU session ID.

[0347] It should be noted that the PDU session ID included in the PDU session change request message can be the PDU session ID of the established PDU session.

[0348] Furthermore, the UE can choose not to send PDU session change request messages while in flight. In other words, the UE can be configured to disable the sending of PDU session change request messages while in flight.

[0349] Here, the UE can also be detected as in flight by 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.).

[0350] Furthermore, prior to implementing this procedure, the UE can detect that it is in flight based on the receipt of a flight request control message. In other words, prior to implementing this procedure, the UE can detect that it is in flight upon receiving a flight request control message.

[0351] Furthermore, prior to implementing this procedure, the UE could also be detected as in flight by 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.) upon receiving a flight request control message. In other words, prior to implementing this procedure, the UE could also be detected as in flight by 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.) upon receiving a flight request control message.

[0352] Next, the SMF receives the PDU session change request message sent by the UE. If the UE's request is accepted, the SMF initiates a network-led PDU session change process. Conversely, if the UE's request is rejected, the SMF sends a PDU session change rejection message to the UE. The following explains the situation where the SMF rejects the UE's request.

[0353] Based on the acceptance of the PDU session establishment request message, the SMF sends a PDU session change rejection message to the UE (S1304). Here, the SMF may include the identification information of the fifteenth identification information or the PDU session ID in the PDU session change rejection message, or it may indicate that the UE's request has been rejected by including this identification information.

[0354] Here, if the UE is in flight, the SMF can include a twentieth identification information in the PDU session change rejection message. In other words, if the UE is identified as being in flight, the SMF can include a twentieth identification information in the PDU session change rejection message.

[0355] Furthermore, upon receiving information from the UTM indicating that the UE is in flight, the SMF can include twentieth identification information in the PDU session change rejection message.

[0356] Furthermore, upon receiving information from the UAV controller indicating that the UE is in flight, the SMF can include twentieth identification information in the PDU session change rejection message.

[0357] Furthermore, upon receiving information from the core network device indicating that the UE is in flight, the SMF can include twentieth identification information in the PDU session change rejection message.

[0358] Furthermore, in addition to the above, in the case of rejecting PDU session changes, SMF may include twentieth identification information in the PDU session change rejection message.

[0359] Here, the PDU session ID included in the PDU session change rejection message can be the same as the PDU session ID included in the PDU session change request message. In other words, the PDU session ID included in the PDU session change rejection message can be the same as the PDU session ID provided by the UE in this process.

[0360] The UE receives a PDU session change rejection message. Further, each device completes this process based on the transmission and reception of the PDU session change rejection message and / or the completion of the network-led PDU session change procedure.

[0361] Here, the UE can identify that its request has been rejected based on the receipt of the PDU session change rejection message. Furthermore, the UE can implement a second process based on the receipt of the PDU session change rejection message. It should be noted that the second process can be implemented based on the completion of this procedure.

[0362] Here, the second process can be the UE identifying the matter indicated by the SMF. Further, the second process can be the UE storing the received identification information as context, or the UE forwarding the received identification information to an upper and / or lower layer. Further, the second process can also be the UE identifying that the request for this process has been rejected.

[0363] Here, in the second process, the UE can identify the reason for the rejection based on the reception of the twentieth identification information and / or the PDU session change rejection message included in the twentieth identification information. Specifically, the UE can identify that the PDU session change is rejected because the UE is in flight, based on the reception of the twentieth identification information and / or the PDU session change rejection message included in the twentieth identification information.

[0364] In other words, in the second process, when the UE receives the twentieth identification information and / or the PDU session change rejection message included in the twentieth identification information, it can identify the reason for the rejection. Specifically, when the UE receives the twentieth identification information and / or the PDU session change rejection message included in the twentieth identification information, it can identify that the PDU session change is rejected because the UE is in flight.

[0365] Furthermore, upon receiving the twentieth identification information and / or a PDU session change rejection message included in the twentieth identification information, the UE can be configured to prohibit the initiation of the PDU session change process and / or PDU session release process for the same PDU session. In other words, further, upon receiving the twentieth identification information and / or a PDU session change rejection message included in the twentieth identification information, the UE can be configured to prohibit the transmission of PDU session change request messages and / or PDU session release request messages for the same PDU session.

[0366] More specifically, upon receiving the twentieth identification information and / or a PDU session change rejection message included in the twentieth identification information, the UE can be configured to prohibit the initiation of the PDU session change process and / or PDU session release process for the same PDU session during a fixed time period. In other words, further, upon receiving the twentieth identification information and / or a PDU session change rejection message included in the twentieth identification information, the UE can be configured to prohibit the transmission of PDU session change request messages and / or PDU session release request messages for the same PDU session during a fixed time period.

[0367] Here, a fixed time period can refer to a time period determined by a timer and / or the state maintained by the UE. Specifically, a fixed time period can be the time period during which the timer is executing. Further, a fixed time period can be the period during which the UE is in flight. In other words, a fixed time period can be the period indicating that the state is in flight. It should be noted that a fixed time period can also be any time period that is not limited to these periods.

[0368] In addition, the PDU session change process and / or PDU session release process for the same PDU session can refer to the PDU session change process and / or PDU session release process using the same PDU session ID.

[0369] Furthermore, each device completes the UE-led PDU session change process based on the completion of the above processing and / or the sending and receiving of UE-led PDU session change rejection messages.

[0370] [3.6.2. Example of UE-led PDU session release process]

[0371] In this chapter, this process refers to the UE-led PDU session release process. The following describes each step of this process.

[0372] The UE-led PDU session release process can be the same as the PDU session change process described above.

[0373] Specifically, in the case of a UE-led PDU session release process, the aforementioned PDU session change request message can be interpreted as a PDU session release request message. Furthermore, in the case of a UE-led PDU session release process, the aforementioned PDU session change request message can be interpreted as a PDU session release request message, and the aforementioned PDU session change rejection message can be interpreted as a PDU session release rejection message. In addition, the act of changing the PDU session can be interpreted as the act of releasing the PDU session.

[0374] Furthermore, in the case where this process is a UE-led PDU session release process, the actions performed by the SMF based on the receipt of the PDU session release request message can be the same as the actions performed by the SMF based on the receipt of the aforementioned PDU session change request message. Furthermore, in the case where this process is a UE-led PDU session release process, the actions performed by the UE based on the receipt of the PDU session release rejection message can be the same as the actions performed by the UE based on the receipt of the aforementioned PDU session change rejection message.

[0375] Furthermore, in the case of a UE-led PDU session release process, the SMF can either initiate a network-led PDU session release process or send a PDU session release rejection message to the UE based on the receipt of the PDU session release request message.

[0376] Furthermore, each device completes the UE-led PDU session release process based on the completion of the above-mentioned processing and / or the sending and receiving of UE-led PDU session release rejection messages.

[0377] [4. Variations]

[0378] The program running in the apparatus of one embodiment of the present invention may be a program that controls a central processing unit (CPU) or similar device to enable the computer to perform its functions in order to achieve the functions of an embodiment of the present invention. The program or the information processed by the program is temporarily stored in volatile memory such as random access memory (RAM) or non-volatile memory such as flash memory, hard disk drive (HDD), or other storage device systems.

[0379] It should be noted that a program for implementing the functions of one embodiment of the present invention can also be recorded in a computer-readable recording medium. This can be achieved by reading the program recorded in the recording medium into a computer system and executing it. The term "computer system" here refers to a computer system built into the device and includes hardware such as an operating system and external devices. Furthermore, "computer-readable recording medium" can refer to a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a medium for short-term dynamic storage of programs, or other computer-readable recording media.

[0380] Furthermore, the functional blocks or features of the apparatus used in the above embodiments can be installed or executed by circuits such as integrated circuits or multiple integrated circuits. Circuits designed to perform the functions described in this specification may include: general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or combinations thereof. A general-purpose processor may be a microprocessor, or a processor, controller, microcontroller, or state machine of existing types. The above circuits may be constructed from digital circuits or analog circuits. Furthermore, in cases where advancements in semiconductor technology have led to the emergence of integrated circuit technologies that replace current integrated circuits, one or more embodiments of the present invention may also utilize new integrated circuits based on this technology.

[0381] It should be noted that the present invention is not limited to the embodiments described above. In the embodiments, an example of the device is described, but one aspect of the present invention is not limited thereto, and can be applied to fixed or non-movable electronic devices installed indoors or outdoors, such as AV equipment, kitchen equipment, cleaning / washing equipment, air conditioning equipment, office equipment, vending machines, other living equipment, and other terminal equipment or communication devices.

[0382] The embodiments of the present invention have been described in detail above with reference to the accompanying drawings. However, the specific configuration is not limited to these embodiments, and design changes that do not depart from the spirit of the present invention are also included. Furthermore, various modifications can be made to one aspect of the present invention within the scope of the claims, and embodiments obtained by appropriately combining technical means disclosed in different embodiments are also included within the technical scope of the present invention. In addition, configurations obtained by substituting elements described in the above embodiments that achieve the same effect are also included.

Claims

1. A UAV, characterized in that, include: Receiving and Dispatch Department; as well as Control Department During a network-driven PDU session change process, when the transceiver receives a PDU session change command message from the network that includes first identification information and second identification information, the control unit forwards the first identification information to the upper layer. The first identification information is the identification information of the UAV, and The second identification information is the PDU session ID.

2. The UAV according to claim 1, characterized in that, The transceiver unit receives a PDU session change command message that includes third identification information and / or fourth identification information; The third identification information is the identification information of the new UAV controller, and The fourth identification information is the IP address of the new UAV controller.

3. A communication control method executed by a UAV, the communication control method comprising: During network-led PDU session change processes, PDU session change command messages are received from the network. When the PDU session change command message includes first identification information and second identification information, the first identification information is forwarded to the upper layer, wherein, The first identification information is the identification information of the UAV, and The second identification information is the PDU session ID.

Images