UE (user equipment)

Abstract

To provide a releasing method after a communication path is established for communication (direct C2 communication) with a UAV (Unmanned Aerial Vehicle) controller using 5GS (5G System).SOLUTION: A target UE has established a communication path for direct C2 communication with an initiating UE. When the target UE receives a first control message from the initiating UE indicating cancellation of authentication and / or approval of the communication path for direct C2 communication or indicating a grace time until the communication path is released, the target UE transmits a second control message initiating a procedure for releasing the communication path for direct C2 communication to the initiating UE based on the reception or after the grace time expires.SELECTED DRAWING: Figure 11

Description

Technical Field

[0001] The present invention relates to a UE (User Equipment).

Background Art

[0002] In 3GPP (3rd Generation Partnership Project), the system architecture of 5GS (5G System), which is a fifth-generation (5G) mobile communication system, is being studied, and discussions are being held to support new procedures and new functions (see Non-Patent Documents 1 to 3). In Release 17 of the 5G standard, a mobile communication system for drones is being discussed (see Non-Patent Document 4).

Prior Art Documents

Non-Patent Documents

[0003]

Non-Patent Document 1

Non-Patent Document 2

Non-Patent Document 3

[0004] In the 5GS (5G System), in order to provide a variety of services, a new core network, 5GCN (5G Core Network), is being considered. Furthermore, as a communication means for operating a UAV (Unmanned Aerial Vehicle), a communication means using 5GS is also being considered.

[0005] Currently, in the communication means of UAVs using 5GS, the UAV is also being defined for direct communication with the UAV controller (referred to as direct C2 communication) together with communication using 5GS.

[0006] On the one hand, regarding direct C2 communication, the method for establishing a communication path and the method for authentication and / or authorization are not clear. Furthermore, the behavior when the authentication and / or authorization for direct C2 communication is cancelled is not clear. Also, the procedure for releasing the communication path of direct C2 communication and the circumstances under which the communication path is to be released are not clear.

[0007] One aspect of the present invention has been made in view of the above circumstances, and its object is to show and clarify the behavior of a UAV when the UAV receives cancellation of authentication and / or authorization for direct C2 communication from a network. Also, the procedure for releasing direct C2 communication and the timing for starting the procedure are clarified.

Means for Solving the Problems

[0008] A User Equipment (UE) according to one aspect of the present invention includes a transmission / reception unit and a control unit. The UE has established a communication path for first direct C2 communication with a UAV-C. The transmission / reception unit receives a PDU session change command message including first identification information from a network. The first identification information is information indicating cancellation of authentication and / or authorization for the communication path for the first direct C2 communication. The control unit recognizes, based on the reception of the PDU session change command message, that the authentication and / or authorization for the communication path for the first direct C2 communication has been cancelled, and starts a procedure for releasing the communication path for the first direct C2 communication.

Effects of the Invention

[0009] According to one aspect of the present invention, it is possible to clarify the behavior of a UAV when the authentication and / or authorization for direct C2 communication is cancelled, the procedure for releasing direct C2 communication, and the timing for starting the procedure.

Brief Description of the Drawings

[0010]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Best Mode for Carrying Out the Invention

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

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

[0013] As shown in FIG. 1, the mobile communication system 1 is described as being composed of UE_A10, access network_A80, core network_A90, PDN (Packet Data Network)_A5, access network_B120, core network_B190, and DN (Data Network)_A6.

[0014] Hereinafter, these devices / functions may be described with symbols omitted, such as UE, access network_A, core network_A, PDN, access network_B, core network_B, DN, etc.

[0015] Also, as shown in FIG. 2, device / functions such as UE_A10, E-UTRAN80, MME40, SGW35, PGW-U30, PGW-C32, PCRF60, HSS50, 5G AN120, AMF140, UPF130, SMF132, PCF160, UDM150, N3IWF170, etc., and interfaces connecting these device / functions to each other are described.

[0016] Hereinafter, these devices / functions may be described with symbols omitted, such as UE, E-UTRAN, MME, SGW, PGW-U, PGW-C, PCRF, HSS, 5G AN, AMF, UPF, SMF, PCF, UDM, N3IWF, etc.

[0017] Currently, the EPS (Evolved Packet System), which is a 4G system, is composed of an access network_A and a core network_A, and may further include a UE and / or a PDN. Also, the 5GS (5G System), which is a 5G system, is composed of a UE, an access network_B and a core network_B, and may further include a DN.

[0018] A UE is a device that can be connected to network services via 3GPP access (also referred to as a 3GPP access network or 3GPP AN) and / or non-3GPP access (also referred to as a non-3GPP access network or non-3GPP AN). The UE may be a terminal device capable of wireless communication such as a mobile phone or a smartphone, and may be a terminal device connectable to both the EPS and the 5GS. The UE may be equipped with a UICC (Universal Integrated Circuit Card) or an eUICC (Embedded UICC). Incidentally, the UE may be referred to as a user device or a terminal device.

[0019] Also, the access network_A corresponds to an E-UTRAN (Evolved Universal Terrestrial Radio Access Network) and / or a wireless LAN access network. One or more eNBs (evolved Node B) 45 are arranged in the E-UTRAN. Incidentally, hereinafter, the eNB 45 may be described with the symbol omitted like eNB. Also, when there are multiple eNBs, each eNB is connected to each other, for example, by an X2 interface. Also, one or more access points are arranged in the wireless LAN access network.

[0020] In addition, Access Network_B supports a 5G Access Network (5G AN). The 5G AN is composed of an NG-RAN (NG Radio Access Network) and / or a non-3GPP access network. One or more gNBs (NR NodeBs) 122 are deployed in the NG-RAN. Hereinafter, the gNB 122 may be described with the symbol omitted as gNB. A gNB is a node that provides an NR (New Radio) user plane and a control plane to a UE, and is a node connected to a 5GCN via an NG interface (including an N2 interface or an N3 interface). That is, a gNB is a base station device newly designed for 5GS and has a different function from the base station device (eNB) used in the EPS which is a 4G system. Also, when there are multiple gNBs, each gNB is connected to each other, for example, via an Xn interface.

[0021] In addition, the non-3GPP access network may be an untrusted non-3GPP access network or a trusted non-3GPP access network. Here, the untrusted non-3GPP access network may be a non-3GPP access network that does not perform security management within the access network, such as a public wireless LAN. On the other hand, the trusted non-3GPP access network may be an access network defined by 3GPP and may be equipped with a TNAP (trusted non-3GPP access point) and a TNGF (trusted non-3GPP Gateway function).

[0022] In addition, hereinafter, E-UTRAN and NG-RAN may be referred to as 3GPP access. Also, a wireless LAN access network and a non-3GPP AN may be referred to as non-3GPP access. Also, the nodes deployed in Access Network_B may be collectively referred to as NG-RAN nodes.

[0023] Also, hereinafter, the access network_A, and / or the access network_B, and / or the devices included in the access network_A, and / or the devices included in the access network_B may be referred to as an access network or an access network device.

[0024] Also, the core network_A corresponds to the EPC (Evolved Packet Core). In the EPC, for example, an MME (Mobility Management Entity), an SGW (Serving Gateway), a PGW (Packet Data Network Gateway)-U, a PGW-C, a PCRF (Policy and Charging Rules Function), an HSS (Home Subscriber Server), etc. are arranged.

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

[0026] Also, hereinafter, the core network_A, and / or the core network_B, the devices included in the core network_A, and / or the devices included in the core network_B may be referred to as a core network, or a core network device or an in-core network device.

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

[0028] Also, in FIG. 1, the case where the PDN and the DN are the same is described, but they may be different. The PDN may be a DN (Data Network) that provides a communication service to the UE. Note that the DN may be configured as a packet data service network or may be configured for each service. Furthermore, the PDN may include connected communication terminals. Therefore, connecting to the PDN may mean connecting to a communication terminal or server device arranged in the PDN. Furthermore, transmitting and receiving user data to and from the PDN may mean transmitting and receiving user data to and from a communication terminal or server device arranged in the PDN. Note that the PDN may be expressed as the DN, or the DN may be expressed as the PDN.

[0029] Also, hereinafter, at least a part of the access network_A, core network_A, PDN, access network_B, core network_B, DN, and / or one or more devices included therein may be referred to as a network or a network device. That is, when a network and / or a network device transmits and receives messages and / or executes procedures, it means that at least a part of the access network_A, core network_A, PDN, access network_B, core network_B, DN, and / or one or more devices included therein transmits and receives messages and / or executes procedures.

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

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

[0032] In addition, the access network_A, core network_A, access network_B, core network_B, PDN_A, and DN_A may be configured with devices not described in FIG. 2. For example, the core network_A and / or core network_B may include an AUSF (Authentication Server Function) or an AAA (Authentication, authorization, and accounting) server (AAA-S).

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

[0034] In addition, the AAA server is a device having an authentication, authorization, and accounting function that is directly or indirectly connected to the AUSF via another network device. The AAA server may be a network device within the core network. Note that the AAA server may not be included in the core network_A and / or core network_B, but may be included in the PLMN. That is, the AAA server may be a core network device or a device outside the core network. For example, the AAA server may be a server device within the PLMN managed by a 3rd Party.

[0035] In FIG. 2, for the sake of simplifying the figure, each device / function is described one by one, but the mobile communication system 1 may be configured with a plurality of similar devices / functions. Specifically, the mobile communication system 1 may be configured with a plurality of devices / functions such as a plurality of UE_A10, E-UTRAN80, MME40, SGW35, PGW-U30, PGW-C32, PCRF60, HSS50, 5G AN120, AMF140, UPF130, SMF132, PCF160, and / or UDM150, etc.

[0036] UPF_A235 is connected to a DN, an SMF, other UPFs, and an access network. UPF_A235 may serve as an anchor for intra-RAT mobility or inter-RAT mobility, perform packet routing & forwarding, support the UL CL (Uplink Classifier) function for routing multiple traffic flows for one DN, support the Branching point function for multi-homed PDU sessions, perform QoS processing for the user plane, verify uplink traffic, buffer downlink packets, trigger the Downlink Data Notification function, etc. Also, UPF_A235 may be a relay device that transfers user data as a gateway between the DN and the core network_B190. Note that UPF_A235 may also be a gateway for IP communication and / or non-IP communication. Furthermore, UPF_A235 may have a function to transfer IP communication, or may have a function to convert non-IP communication and IP communication. Multiple gateways arranged may also be gateways that connect the core network_B190 and a single DN. Note that UPF_A235 may be provided with connectivity to other NFs and may be connected to each device via other NFs.

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

[0038] Further, UPF130 may be the same device as UPF_A235. Note that UPF130 and UPF_A235 may be described with the symbol omitted, like UPF.

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

[0040] Note that each storage unit (storage unit_A340, storage unit_A440, storage unit_B540, storage unit_A640, storage unit_B740) within each device / function appearing below is composed of, for example, a semiconductor memory, SSD (Solid State Drive), HDD (Hard Disk Drive), etc. Also, each storage unit can store not only the information originally set at the shipping stage, but also various types of information transmitted and received between devices / functions other than its own device / function (e.g., UE, and / or access network device, and / or core network device, and / or PDN, and / or DN). Also, each storage unit can store identification information, control information, flags, parameters, etc. included in the control messages transmitted and received within various communication procedures described later. Also, each storage unit may store these information for each UE. Also, when interworking between 5GS and EPS, each storage unit can store control messages and user data transmitted and received between devices / functions included in 5GS and / or EPS. At this time, not only those transmitted and received via the N26 interface but also those transmitted and received without passing through the N26 interface can be stored.

[0041] [2.1. Device Configuration of UE] First, an example of the device configuration of a UE (User Equipment) will be described with reference to FIG. 3. The UE is composed of a control unit _A300, an antenna 310, a transceiver unit _A320, and a storage unit _A340. The control unit _A300, the transceiver unit _A320, and the storage unit _A340 are connected via a bus. The transceiver unit _A320 is connected to the antenna 310.

[0042] The control unit _A300 is a functional unit that controls the operations and functions of the entire UE. The control unit _A300 realizes various processes in the UE by reading and executing various programs stored in the storage unit _A340 as needed.

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

[0044] Referring to FIG. 2 for a detailed description, the UE can communicate with a base station device (eNB) in the E-UTRAN via the LTE-Uu interface by using the transceiver unit _A320. Also, the UE can communicate with a base station device (gNB) in the 5G AN by using the transceiver unit _A320. Further, the UE can transmit and receive NAS (Non-Access-Stratum) messages with the AMF via the N1 interface by using the transceiver unit _A320. However, since the N1 interface is logical, in reality, the communication between the UE and the AMF is performed via the 5G AN.

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

[0046] [2.2. Device Configuration of gNB] Next, an example of the device configuration of the gNB will be described with reference to FIG. 4. The gNB is composed 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, the network connection unit _B520, the transceiver unit _B530, and the storage unit _B540 are connected via a bus. The transceiver unit _B530 is connected to the antenna 510.

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

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

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

[0050] Referring to FIG. 2 for detailed description, the gNB within the 5G AN can communicate with the AMF via the N2 interface and with the UPF via the N3 interface by using the network connection unit _B520. Also, the gNB can communicate with the UE by using the transceiver unit _B530.

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

[0052] [2.3. Device Configuration of AMF] Next, an example of the device configuration of the AMF will be described with reference to FIG. 5. The AMF is composed of a control unit _B700, a network connection unit _B720, and a storage unit _B740. The control unit _B700, the network connection unit _B720, and the storage unit _B740 are connected via a bus. The AMF may be a node that handles the control plane.

[0053] The control unit _B700 is a functional unit that controls the operations and functions of the entire AMF. The control unit _B700 reads and executes various programs stored in the storage unit _B740 as necessary to implement various processes in the AMF.

[0054] The network connection unit _B720 is a functional unit for the AMF to connect to a base station device (gNB), and / or SMF, and / or PCF, and / or UDM, and / or SCEF within the 5G AN. That is, the AMF can transmit and receive user data and / or control information to / from a base station device (gNB), and / or SMF, and / or PCF, and / or UDM, and / or SCEF within the 5G AN using the network connection unit _B720.

[0055] Describing in detail with reference to FIG. 2, the AMF within the 5GCN can communicate with the gNB via the N2 interface, communicate with the UDM via the N8 interface, communicate with the SMF via the N11 interface, and communicate with the PCF via the N15 interface by using the network connection unit _A620. Also, the AMF can transmit and receive NAS messages to / from the UE via the N1 interface by using the network connection unit _A620. However, since the N1 interface is logical, in reality, the communication between the UE and the AMF is performed via the 5G AN. Also, when the AMF supports the N26 interface, it can communicate with the MME via the N26 interface by using the network connection unit _A620.

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

[0057] Furthermore, the AMF has functions such as exchanging control messages with the RAN using the N2 interface, exchanging NAS messages with the UE using the N1 interface, encrypting and providing integrity protection for NAS messages, registration management (RM) function, connection management (CM) function, reachability management function, mobility management function for the UE, etc., transferring SM (Session Management) messages between the UE and the SMF, access authentication (Access Authentication, Access Authorization) function, security anchor function (SEA), security context management (SCM) function, supporting the N2 interface for the N3IWF (Non-3GPP Interworking Function), supporting the transmission and reception of NAS signals with the UE via the N3IWF, authenticating the UE connected via the N3IWF, etc.

[0058] Also, in registration management, the RM state for each UE is managed. The RM state may be synchronized between the UE and the AMF. The RM states include the deregistered state (RM-DEREGISTERED state) and the registered state (RM-REGISTERED state). In the RM-DEREGISTERED state, since the UE is not registered with the network, the UE context in the AMF does not have valid location information or routing information for that UE, so the AMF cannot reach the UE. Also, in the RM-REGISTERED state, since the UE is registered with the network, the UE can receive services that require registration with the network. Note that the RM state may be expressed as the 5GMM state (5GMM state). In this case, the RM-DEREGISTERED state may be expressed as the 5GMM-DEREGISTERED state, and the RM-REGISTERED state may be expressed as the 5GMM-REGISTERED state.

[0059] In other words, 5GMM-REGISTERED may be a state where each device has established a 5GMM context or a state where a PDU session context has been established. Note that when each device is 5GMM-REGISTERED, UE_A10 may start transmitting and receiving user data and control messages or may respond to paging. Furthermore, note that when each device is 5GMM-REGISTERED, UE_A10 may execute a registration procedure other than the registration procedure for initial registration and / or a service request procedure.

[0060] Furthermore, 5GMM-DEREGISTERED may be a state where each device has not established a 5GMM context, a state where the location information of UE_A10 is not grasped by the network, or a state where the network cannot reach UE_A10. Note that when each device is 5GMM-DEREGISTERED, UE_A10 may start a registration procedure or may establish a 5GMM context by executing a registration procedure.

[0061] Also, in connection management, the CM state for each UE is managed. The CM state may be synchronized between the UE and the AMF. The CM states include a non-connected state (CM-IDLE state) and a connected state (CM-CONNECTED state). In the CM-IDLE state, the UE is in the RM-REGISTERED state but does not have a NAS signaling connection established with the AMF via the N1 interface. Also, in the CM-IDLE state, the UE does not have an N2 connection and 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. Also, in the CM-CONNECTED state, the UE may have an N2 connection and / or an N3 connection.

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

[0063] Furthermore, the CM state may be expressed as the 5GMM mode. In this case, the non-connected state may be expressed as the 5GMM - IDLE mode, and the connected state may be expressed as the 5GMM - CONNECTED mode. Additionally, the non-connected state in 3GPP access may be expressed as the 5GMM - IDLE mode over 3GPP access, and the connected state in 3GPP access may be expressed as the 5GMM - CONNECTED mode over 3GPP access. Moreover, the non-connected state in non-3GPP access may be expressed as the 5GMM - IDLE mode over non-3GPP access, and the connected state in non-3GPP access may be expressed as the 5GMM - CONNECTED mode over non-3GPP access. Note that the 5GMM - IDLE mode may also be expressed as the idle mode, and the 5GMM - CONNECTED mode may also be expressed as the connected mode.

[0064] Also, one or more AMFs may be deployed within Core Network_B. Also, the AMF may be a Network Function (NF) that manages one or more Network Slice Instances (NSIs). Also, the AMF may be a Common Control Plane Network Function (CCNF) shared among multiple NSIs.

[0065] Note that the N3IWF is a device and / or function deployed between non-3GPP access and 5GCN when the UE connects to 5GS via non-3GPP access.

[0066] [2.4. SMF Device Configuration] Next, an example of the device configuration of the SMF will be described with reference to FIG. 5. The SMF is composed of a control unit _B700, a network connection unit _B720, and a storage unit _B740. The control unit _B700, the network connection unit _B720, and the storage unit _B740 are connected via a bus. The SMF may be a node that handles the control plane.

[0067] The control unit _B700 is a functional unit that controls the operations and functions of the entire SMF. The control unit _B700 reads and executes various programs stored in the storage unit _B740 as necessary to implement various processes in the SMF.

[0068] The network connection unit _B720 is a functional unit for the SMF to connect to the AMF, and / or UPF, and / or PCF, and / or UDM. That is, the SMF can send and receive user data and / or control information to and from the AMF, and / or UPF, and / or PCF, and / or UDM using the network connection unit _B720.

[0069] Referring to FIG. 2 for a detailed description, the SMF within the 5GCN can communicate with the AMF via the N11 interface, communicate with the UPF via the N4 interface, communicate with the PCF via the N7 interface, and communicate with the UDM via the N10 interface by using the network connection unit _A620.

[0070] The storage unit _B740 is a functional unit for storing programs, user data, control information, etc. necessary for each operation of the SMF.

[0071] The SMF has functions such as session management for establishing, modifying, and releasing PDU sessions, IP address allocation to the UE and its management function, UPF selection and control function, UPF configuration function for routing traffic to an appropriate destination (transmission destination), function of sending and receiving the SM part of NAS messages, function of notifying the arrival of downlink data (Downlink Data Notification), function of providing AN-specific (per-AN) SM information transmitted to the AN via the N2 interface through the AMF, function of determining the SSC mode (Session and Service Continuity mode) for the session, roaming function, etc.

[0072] [2.5. UPF Device Configuration] Next, an example of the UPF device configuration will be described with reference to FIG. 5. The UPF is composed of a control unit _B700, a network connection unit _B720, and a storage unit _B740. The control unit _B700, the network connection unit _B720, and the storage unit _B740 are connected via a bus. The UPF may be a node that handles the control plane.

[0073] The control unit _B700 is a functional unit that controls the operations and functions of the entire UPF. The control unit _B700 realizes various processes in the UPF by reading and executing various programs stored in the storage unit _B740 as necessary.

[0074] The network connection unit _B720 is a functional unit for the UPF to connect to a base station device (gNB) within the 5G AN, and / or the SMF, and / or the DN. That is, the UPF can send and receive user data and / or control information to and from a base station device (gNB) within the 5G AN, and / or the SMF, and / or the DN using the network connection unit _B720.

[0075] Referring to FIG. 2 for a detailed description, the UPF within the 5G CN can communicate with the gNB via the N3 interface by using the network connection unit _A620, can communicate with the SMF via the N4 interface, can communicate with the DN via the N6 interface, and can communicate with other UPFs via the N9 interface.

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

[0077] The UPF has functions such as a function as an anchor point for intra-RAT mobility or inter-RAT mobility, a function as an external PDU session point for interconnecting with the DN (i.e., a function of transferring user data as a gateway between the DN and the core network _B), a function of routing and transferring packets, a UL CL (Uplink Classifier) function of supporting routing of multiple traffic flows for one DN, a Branching point function of supporting a multi-homed PDU session, a QoS (Quality of Service) processing function for the user plane, a function of verifying uplink traffic, a function of buffering downlink packets, and a function of triggering downlink data notification.

[0078] Also, the UPF may be a gateway for IP communication and / or non-IP communication. Also, the UPF may have a function of transferring IP communication, or may have a function of converting non-IP communication and IP communication. Furthermore, multiple gateways arranged may be gateways for connecting the core network _B and a single DN. Note that the UPF may be provided with connectivity to other NFs and may be connected to each device via other NFs.

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

[0080] Furthermore, the control plane is the control message transmitted and received for performing communication control of the UE, etc. The control plane may be transmitted and received using the NAS (Non-Access-Stratum) signaling connection between the UE and the MME. Further, in the case of EPS, the control plane may be transmitted and received using the LTE-Uu interface and the S1-MME interface. Further, in the case of 5GS, the control plane may be transmitted and received using the interface between the UE and the NG RAN and the N2 interface. Hereinafter, the control plane may be expressed as the control plane or the C-Plane.

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

[0082] [2.6. Description of Other Devices and / or Functions] Next, other devices and / or functions will be described.

[0083] The PCF has functions such as providing policy rules.

[0084] Also, the UDM has functions such as an Authentication credential processing function, a user identification processing function, an access authentication function, a registration / mobility management function, and a subscription management function.

[0085] Also, the PCRF is connected to the PGW and / or the PDN and has functions such as performing QoS management for data delivery. For example, it manages the QoS of the communication path between UE_A10 and the PDN. Furthermore, the PCRF may be a device that creates and / or manages PCC (Policy and Charging Control) rules and / or routing rules used when each device transmits and receives user data.

[0086] Also, the HSS is connected to the MME and / or the SCEF and has functions such as managing subscriber information. The subscriber information of the HSS is referred to, for example, during the access control of the MME. Furthermore, the HSS may be connected to a location management device different from the MME.

[0087] [3. Description of Terms, Identification Information, and Procedures Used in Each Embodiment] Next, terms, identification information, and procedures that are used in at least one of the embodiments will be described in advance.

[0088] [3.1. Description of Terms and Identification Information Used in Each Embodiment] First, highly specialized terms used in each embodiment and identification information used in procedures will be described in advance.

[0089] The network refers to at least a part of the access network_B, the core network_B, and the DN. Also, one or more devices included in at least a part of the access network_B, the core network_B, and the DN may be referred to as a network or a network device. That is, when the network executes message transmission / reception and / or processing, it may mean that a device (network device and / or control device) within the network executes message transmission / reception and / or processing. Conversely, when a device within the network executes message transmission / reception and / or processing, it may mean that the network executes message transmission / reception and / or processing.

[0090] SM (Session Management) messages (also referred to as NAS (Non-Access-Stratum) SM messages) are NAS messages used in procedures for SM, and may be control messages transmitted and received between UE_A10 and SMF_A230 via AMF_A240. 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, PDU session release complete messages, etc. Also, procedures for SM or SM procedures may include PDU session establishment procedures, PDU session modification procedures, and UE-requested PDU session release procedures.Note that each procedure may be a procedure starting from the UE or a procedure starting from the NW.

[0091] An MM (Mobility management) message (also referred to as an NAS MM message) may be an NAS message used for MM procedures, and may be a control message transmitted and received between UE_A10 and AMF_A240. Further, the MM message may include a registration request message, a registration accept message, a registration reject message, a de-registration request message, a de-registration accept message, a configuration update command message, a configuration update complete message, a service request message, a service accept message, a service reject message, a notification message, a notification response message, etc. Also, the procedure for MM or the MM procedure may include a registration procedure, a de-registration procedure, a generic UE configuration update procedure, an authentication and / or authorization procedure, a service request procedure, a paging procedure, a notification procedure.

[0092] The 5GS (5G System) service may be a connection service provided using the core network_B190. Further, the 5GS service may be a service different from the EPS service or a service similar to the EPS service.

[0093] The non 5GS service may be a service other than the 5GS service and may include the EPS service and / or the non EPS service.

[0094] The PDN (Packet Data Network) type indicates the type of the PDN connection and includes IPv4, IPv6, IPv4v6, and non-IP. When IPv4 is specified, it indicates that data is transmitted and received using IPv4. When IPv6 is specified, it indicates that data is transmitted and received using IPv6. When IPv4v6 is specified, it indicates that data is transmitted and received using either IPv4 or IPv6. When non-IP is specified, it indicates that communication is performed by a communication method other than IP communication.

[0095] A PDU (Protocol Data Unit / Packet Data Unit) session can be defined as the association between a DN that provides a PDU connectivity service and a UE, but it can also be a connectivity established between the UE and an external gateway. In 5GS, the UE can establish a PDU session via access network_B and core network_B, and use this PDU session to send and receive user data with the DN. Here, this external gateway can be a UPF, SCEF, etc. The UE can use the PDU session to send and receive user data with devices such as application servers located in the DN. Each device (UE, and / or access network device, and / or core network device) may manage one or more identification information associated with the PDU session. These identification information may include one or more of DNN, QoS rules, PDU session type, application identification information, NSI identification information, access network identification information, and SSC mode, and may further include other information. Furthermore, when multiple PDU sessions are established, the identification information associated with each PDU session may have the same content or different content.

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

[0097] The PDU (Protocol Data Unit / Packet Data Unit) session type indicates the type of the PDU session, including IPv4, IPv6, Ethernet, and Unstructured. When IPv4 is specified, it indicates that data transmission and reception are performed using IPv4. When IPv6 is specified, it indicates that data transmission and reception are performed using IPv6. When Ethernet is specified, it indicates that Ethernet frames are transmitted and received. Also, Ethernet may indicate that communication using IP is not performed. When Unstructured is specified, it indicates that data is transmitted and received to / from an application server, etc. in the DN using the Point-to-Point (P2P) tunneling technology. As the P2P tunneling technology, for example, UDP / IP encapsulation technology may be used. In addition to the above, the PDU session type may include IP. IP can be specified when the UE can use both IPv4 and IPv6.

[0098] A PLMN (Public land mobile network) is a communication network that provides mobile radio communication services. A PLMN is a network managed by an operator who is a communication carrier, and the operator can be identified by the PLMN ID. The PLMN that matches the MCC (Mobile Country Code) and MNC (Mobile Network Code) of the UE's IMSI (International Mobile Subscriber Identity) may be the Home PLMN (HPLMN). Furthermore, the UE may hold an Equivalent HPLMN list for identifying one or more EPLMNs (Equivalent HPLMNs) in the USIM. A PLMN different from the HPLMN and / or EPLMN may be a VPLMN (Visited PLMN). The PLMN in which the UE's registration is successful may be an RPLMN (Registered PLMN).

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

[0100] The registration area (Registration area or registration area) is a set of one or more TAs assigned by the AMF to the UE. Note that UE_A10 may be able to move without transmitting or receiving signals for tracking area updates while moving within one or more TAs included in the registration area. In other words, the registration area may be a group of information indicating the area in which UE_A10 can move without performing a tracking area update procedure. The registration area may be identified by a TAI list composed of one or more TAIs.

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

[0102] An Always-on PDU session is a PDU session in which the UE has to activate user plane resources every time it transitions from the 5GMM-IDLE state to the 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 an instruction from a higher layer. The core network and / or core network devices determine whether the PDU session can be established as an Always-on PDU session. Here, the establishment of an Always-on PDU session may mean the establishment of a PDU session for C2 communication. Furthermore, the establishment of an Always-on PDU session may mean the establishment of a PDU session handling QoS flows for C2 communication. Here, the 5GMM-IDLE state may be a CM-IDLE state. Furthermore, the 5GMM-CONNECTED state may be a CM-CONNECTED state. Furthermore, the core network device that determines whether the PDU session can be established as an Always-on PDU session may be an SMF.

[0103] The Service-level-AA container information element (IE) is an IE for transferring information for authentication and authorization between the UE and the network to the upper layer. The Service-level-AA container IE may also include a Service-level device ID, and / or a Service-level-AA server address, and / or a Service-level-AA payload, and / or a Service-level-AA response. Furthermore, the Service-level-AA container IE may include a C2 authorization result, and / or C2 session security information, and / or identification information of the UAV-C to pair, and / or flight authorization information. Furthermore, the Service-level-AA container IE may include a Service-level-AA pending indication. Note that the Service-level-AA container IE may also be referred to as the Service-level-AA container.

[0104] The Service-level device ID is an IE for carrying the identity required for authentication and authorization by an external DN. The Service-level device ID may also be included in the Service-level-AA container IE. The Service-level device ID may also include a CAA-level UAV ID.

[0105] The Service-level-AA server address is an information element for carrying the address of the service level authentication and authorization server. Also, the Service-level-AA server address may be included in the Service-level-AA container information element. Also, the Service-level-AA server address may include the USS address.

[0106] The Service-level-AA payload is an information element for carrying the payload for authentication and authorization between the UE and the service-level-AA server to the upper layer. Also, the Service-level-AA payload may be included in the Service-level-AA container information element. Also, the Service-level-AA payload may include the UUAA aviation payload.

[0107] The Service-level-AA response is an information element for providing information regarding the service level authentication and authorization request. Specifically, the Service-level-AA response is an information element indicating whether the authentication and authorization request to the service level authentication server has been successful or not. Also, the Service-level-AA response may be included in the Service-level-AA container information element.

[0108] A UAV (Uncrewed Aerial Vehicle) is a flying drone. Also, the UAV may be a UE. Also, the UAV may be a 3GPP UE that supports UE functions.

[0109] Also, the UAV may be managed by the USS. The UAV may be associated with a UAV controller. Further, the UAV may be associated with a UAV controller and be managed by the core network device and / or the UTM. Further, when the UAV is associated with and managed by a UAV controller, it may be managed as a UAS by the core network device and / or the UTM. The UAV may have its own information (such as identification information, IP address, location information, etc.) managed by the core network device and / or the UTM. Also, the UE may be read as a UAV.

[0110] Also, a UAV capable of using UAS services may be a UAV capable of using C2 communication and / or direct C2 communication. Also, a UAV capable of using C2 communication and / or direct C2 communication may be a UAV capable of using UAS services.

[0111] A UAV controller (Uncrewed Aerial Vehicle controller) is a controller for operating a UAV. Also, the UAV controller may be a UE. Also, the UAV controller may be a 3GPP UE that supports UE functions.

[0112] The UAV controller may be associated with the UAV. Further, the UAV controller may be associated with the UAV and be managed by the core network device and / or the UTM. Further, when the UAV controller is associated with and managed by the UAV, it may be managed as a UAS by the core network device and / or the UTM. The UAV controller may have its own information (such as identification information, IP address, location information, etc.) managed by the core network device and / or the UTM. Note that the UAV controller may be expressed as UAC or UAV-C. Also, the UE may be read as UAV-C.

[0113] Also, the UAV-C capable of using the UAS service may be a UAV-C capable of using C2 communication and / or direct C2 communication. Also, the UAV-C capable of using C2 communication and / or direct C2 communication may be a UAV-C capable of using the UAS service.

[0114] A UAS (Uncrewed Aerial System) may be composed of a UAV and related functions. Here, the related functions may include a C2 (command and control) link. Further, the C2 link may be a link between the UAV and the control station, or a link between the UAV and the network. Further, the C2 link may be a link for remote identification. Also, the UAS may be composed of one or more UAVs and one or more UAV controllers. Also, the UAS may be managed by a network device and / or USS.

[0115] The USS (Uncrewed Aerial System Service Supplier) is a device with functions for managing UAVs, and / or UAV controllers, and / or UASs. The USS may be a device of the DN or a device within the core network. Also, the USS may be a device for autonomously controlling UAVs. Further, the USS may have functions for managing identification information, IP addresses, location information, etc. of UAVs and / or UAV controllers, or may have functions for managing information of UAVs and / or UAV controllers other than the above. Additionally, the USS may associate UAVs and UAV controllers and manage them as UASs. Also, the USS may send information for requesting network services to core network devices. Furthermore, the USS may be a device that provides one or more functions and services for managing the scope of automobile driving. Also, the USS may be a UAS application server.

[0116] Also, the USS may be a device with UTM functions. The USS may also be a device provided in the UTM or a device within the UTM. Note that the USS may be expressed as USS / UTM or UTM / USS. Also, the USS may be expressed as a network.

[0117] Also, the USS may send information to the core network and / or the UE via the UAS-NF (Uncrewed Aerial Systems Network Function). The information sent from the USS may be regarded as the information sent from the UAS-NF. Also, the information received by the USS may be regarded as the information received from the UAS-NF.

[0118] UTM (Uncrewed Aerial System Traffic Management) may be a device including the USS. UTM may be a device equipped with the USS. Also, UTM may be read as the USS.

[0119] Command and Control (C2) communication may be a user plane link for delivering a message including commands and control information for operating the UAV from a UAV controller or UTM to the UAV.

[0120] Also, C2 communication may be communication for delivering a message including commands and control information for operating the UAV from a UAV controller or UTM to the UAV. Also, C2 communication may be a link between the UAV controller and the UAV. Also, C2 communication may be a link between the USS and the UAV. Also, C2 communication may be communication between the UAV controller and the UAV. Also, C2 communication may be communication between the USS and the UAV.

[0121] Furthermore, C2 communication may be a user plane link for reporting telemetry data from the UAV to the UAV controller or UTM. Furthermore, C2 communication may be a user plane link for delivering a message including commands and control information for operating the UAV from the UAV controller to the UAV via the UTM. Here, C2 communication may be a link realized by a PDU session. Furthermore, the PDU session for C2 communication may be realized by an Always-on PDU session. Furthermore, the establishment of the PDU session for C2 communication may mean the establishment of an Always-on PDU session. Furthermore, the establishment of the PDU session handling the QoS flow for C2 communication may mean the establishment of an Always-on PDU session. Also, the link may be a communication path or a transmission path. C2 communication may be referred to as C2.

[0122] Also, C2 communication may be read as a communication path for C2 communication. Also, the communication path for C2 communication may be read as C2 communication.

[0123] Direct C2 communication may be a link between the UAV and the UAV-C. Also, direct C2 communication may be communication between the UAV and the UAV-C.

[0124] Also, direct C2 communication may be a direct link between the UAV and the UAV-C. Also, direct C2 communication may be a direct C2 link between the UAV and the UAV-C. Also, direct C2 communication may be a communication path on PC5. Direct C2 communication may be C2 communication.

[0125] Here, the UAV and / or UAV-C may be registered in the network. Also, the link may be a communication path or a transmission path.

[0126] Also, direct C2 communication may be construed as a communication path for direct C2 communication. Also, the communication path for direct C2 communication may be construed as direct C2 communication.

[0127] The C2 authorization result may be the result of the authorization of C2 communication. Specifically, it may be information indicating the failure or success of C2 communication authorization.

[0128] The result of the authorization of C2 communication may include and be composed of the authorization result of direct C2 communication. In that case, the C2 authorization result may be information indicating the success of C2 communication using the PDU session, or the success of direct C2 communication, or the success of both authorizations, or the failure of authorization. Or, the C2 authorization result indicates the success or failure of the authorization of C2 communication, and the network may notify the UE of the success or failure of the authorization of C2 communication using the PDU session and direct C2 communication, and the UE may recognize the notification.

[0129] Alternatively, the Service-level-AA container information element may include a direct C2 authorization result, which is the authorization result of direct C2 communication independent of the C2 authorization result. In that case, the direct C2 authorization result may be information indicating the success or failure of the authorization of direct C2 communication.

[0130] Also, the C2 authorization result may be construed as the direct C2 authorization result.

[0131] The direct C2 authorization result may be the result of the authorization of direct C2 communication. Specifically, it may be information indicating the failure or success of the authorization of direct C2 communication.

[0132] The result of the authorization of direct C2 communication may include and be composed of the authorization result of C2 communication. In that case, the direct C2 authorization result may be information indicating the success of the authorization of C2 communication using the PDU session, or the success of the authorization of direct C2 communication, or the success of both authorizations, or the failure of the authorization. Or, the direct C2 authorization result may indicate the success or failure of the authorization of direct C2 communication, and the UE may be notified of the success or failure of the authorization of direct C2 communication, and the UE may recognize the notification.

[0133] Authorization for C2 is the authorization and / or procedure required to be executed when the UAV and / or UAV-C establish a user plane connection for C2 operations. Here, the user plane connection for C2 operations may be C2 communication. In other words, in order for the UAV and / or UAV-C to establish C2 communication, the authorization of C2 communication needs to be executed.

[0134] In the authorization of C2 communication, the UAV and / or UAV-C may be authorized by the USS to establish a PDN connection and / or a PDU session for C2, and / or to establish direct C2 communication. Further, in the authorization of C2 communication, the authorization of the pairing of the UAV and the UAV-C, and / or flight authorization may be implemented. The authorization of the pairing of the UAV and the UAV-C, and / or flight authorization may be executed by the USS.

[0135] The approval of C2 communication may be executed during the UUAA procedure or by other procedures. Specifically, when the UAV wants to split the C2 communication with the USS and the C2 communication with the UAV-C, the approval of C2 communication may be executed within the procedures for the UAV to establish a new PDU session and / or PDN connection.

[0136] The case where the UAV wants to split the C2 communication with the USS and the C2 communication with the UAV-C may be, for example, when the UAV requests to establish a direct C2 communication.

[0137] When the UAV and / or UAV-C requests to establish a direct C2 communication, the approval of C2 communication for the direct C2 communication may be executed during the registration procedure and / or during the UUAA-MM procedure.

[0138] Also, the approval of C2 communication may be referred to as the Authorization for direct C2.

[0139] The approval of the pairing between the UAV and the UAV-C means that the UAV is approved to pair with the UAV-C and / or the UAV-C is approved to pair with the UAV, and it may be necessary to be executed before the exchange of information by C2 communication between the UAV and the UAV-C.

[0140] The flight approval is the approval for the UAV to fly. The flight approval may also need to be executed before the UAV flies. Or, the flight approval may be executed within the C2 communication approval procedure only when the UAV requests. In other words, with the approval of C2 communication, the pairing between the UAV and the UAV-C and / or the flight of the UAV may be approved.

[0141] The CAA-Level UAV ID is information assigned to a UAV by functions in the aviation domain such as the USS. Also, the CAA-Level UAV ID may be used for remote identification and tracking, or for identifying the UAV. Additionally, the CAA-Level UAV ID may be information provided by the UAV to the 3GPP system during the UUAA procedure.

[0142] Also, the aviation domain may assign a new CAA-Level UAV ID for the UAV at any time. Additionally, the new CAA-Level UAV ID may be provided to the UAV and the 3GPP system during UAS-related procedures.

[0143] The CAA-level UAV ID may be referred to as the identification information of the UAV, or as the information for identifying the UAV.

[0144] The 3GPP UAV ID is information associated with the UAV by the 3GPP system. Also, the 3GPP UAV ID may be information used by the 3GPP system to identify the UAV. Additionally, the USS may store the association between the CAA-level UAV ID and the 3GPP UAV ID.

[0145] The 3GPP UAV ID may be referred to as the identification information of the UAV, or as the information for identifying the UAV.

[0146] In the UE, there may be an initiating UE and a target UE.

[0147] The initiating UE may be a UE used in communication between two UEs. Also, the initiating UE may send a message to the target UE. Further, the initiating UE may be used in a procedure for establishing direct C2 communication. Additionally, the initiating UE may be a UAV or a UAV-C.

[0148] The target UE may be a UE used in communication between two UEs. Also, the target UE may send a message to the initiating UE. Further, the target UE may be used in a procedure for establishing direct C2 communication. Additionally, the target UE may be a UAV or a UAV-C.

[0149] The first identification information may be information indicating whether a UE supports direct C2 communication. Also, the first identification information may be information indicating that a UE supports direct C2 communication. Further, the first identification information may be information indicating that a UE does not support direct C2 communication.

[0150] Also, the first identification information may be information indicating a request for authentication and / or authorization of the establishment of direct C2 communication. Also, the first identification information may be information indicating a request for authentication and / or authorization of the use of direct C2 communication.

[0151] Also, the first identification information may be a 5GMM capability. Also, the first identification information may be information included in the 5GMM capability.

[0152] The second identification information may be information indicating a request for authentication and / or authorization of direct C2 communication and / or establishment of C2 communication using a PDU session. Further, the second identification information may be information indicating a request for authentication and / or authorization of direct C2 communication and / or establishment of C2 communication.

[0153] Further, the second identification information may be information indicating a request for authentication and / or authorization of simultaneously establishing direct C2 communication and C2 communication. Further, the second identification information may be information indicating a request for authentication and / or authorization of simultaneously using direct C2 communication and C2 communication.

[0154] Further, the second identification information may be information indicating whether the UE supports direct C2 communication and / or C2 communication. Further, the second identification information may be information indicating that the UE supports direct C2 communication and / or C2 communication. Further, the second identification information may be information indicating that the UE does not support direct C2 communication and / or C2 communication.

[0155] Further, the second identification information may be 5GSM capability. Further, the second identification information may be information included in 5GSM capability.

[0156] The first identification information and / or the second identification information may be information included in a Service-level-AA container.

[0157] Furthermore, the first identification information and / or the second identification information may be information selected and determined based on UE settings, and / or UE status, and / or user policies, and / or application requirements.

[0158] The third identification information may be source user information. Also, the third identification information may be the ID of the application layer of the initiating UE. Also, the third identification information may be the ID of the application layer of the UE on the side transmitting the message. Also, the third identification information may be information received from the upper layer. Also, the third identification information may be source user information in which the ID of the application layer of the initiating UE received from the upper layer is set.

[0159] Also, the third identification information may be information included in a message used in communication between two UEs.

[0160] The fourth identification information may be information for identifying the application of the UAS. Also, the fourth identification information may be information for requesting the application of the UAS. Also, the fourth identification information may be information for using the application of the UAS. Also, the fourth identification information may be information used in the application of the UAS.

[0161] Also, the fourth identification information may be a ProSe identifier.

[0162] The fifth identification information may be target user information. Also, the fifth identification information may be the ID of the application layer of the target UE. Also, the fifth identification information may be the ID of the application layer of the UE on the side receiving the message. Also, the fifth identification information may be information received from the upper layer. Also, the fifth identification information may be target user information in which the ID of the application layer of the target UE received from the upper layer is set.

[0163] Also, the fifth identification information may be information included in a message used in communication between two UEs.

[0164] The sixth identification information is a reason value. The sixth identification information may be a reason value indicating the reason why the communication path for direct C2 communication is released.

[0165] Here, the reason value may indicate that direct C2 communication with the target UE is not permitted. Also, the reason value may indicate that direct C2 communication with the target UE is not necessary. Also, the reason value may indicate that direct C2 communication is not available. Also, the reason value may indicate that there is a shortage of resources for direct C2 communication. Also, the reason value may indicate a congestion situation. Also, the reason value may indicate a protocol error.

[0166] Also, the reason value may be (#1 direct communication to the target UE not allowed), or (#2 direct communication to the target UE no longer needed), or (#4 direct connection is not available anymore), or (#5 lack of resources for 5G ProSe direct link), or (#13 congestion situation), or (#111 protocol error, unspecified).

[0167] Also, the reason value may be selected and determined based on subscriber information, and / or network status, and / or user registration information, and / or context held by the UE, etc., as to whether it indicates the degree information among the above information. Also, the reason value may be selected and determined based on the information indicated by the network and / or USS as to whether it indicates the degree information among the above information.

[0168] Further, the reason value may be indicated by the network and / or USS.

[0169] The tenth identification information may be information indicating whether the network authenticates and / or approves direct C2 communication. Further, the tenth identification information may be information indicating that the network authenticates and / or approves direct C2 communication. Further, the tenth identification information may be information indicating that the network does not authenticate and / or approve direct C2 communication.

[0170] The tenth identification information may be information indicating whether the network permits direct C2 communication. Further, the tenth identification information may be information indicating that the network permits direct C2 communication. Further, the tenth identification information may be information indicating that the network does not permit direct C2 communication.

[0171] The eleventh identification information may be information indicating that direct C2 communication and / or C2 communication using a PDU session is authenticated and / or approved. Further, the eleventh identification information may be information indicating that direct C2 communication and / or C2 communication is authenticated and / or approved. Further, the eleventh identification information may be information indicating that direct C2 communication and / or C2 communication is not authenticated and / or approved. Further, the eleventh identification information may be information indicating whether direct C2 communication and / or C2 communication is authenticated and / or approved.

[0172] Further, the 11th identification information may be information indicating permission for direct C2 communication and / or C2 communication. Further, the 11th identification information may be information indicating non - permission for direct C2 communication and / or C2 communication. Further, the 11th identification information may be information indicating whether to permit direct C2 communication and / or C2 communication.

[0173] The 10th identification information and / or the 11th identification information may be information included in the Service - level - AA container. The 10th identification information and / or the 11th identification information may be the C2 approval result and / or the Service - level - AA response and / or the direct C2 approval result included in the Service - level - AA container, or may be information included in the C2 approval result and / or the Service - level - AA response and / or the direct C2 approval result.

[0174] Further, the 10th identification information and / or the 11th identification information may be information transmitted by the USS.

[0175] Furthermore, the 10th identification information and / or the 11th identification information may be information selected and determined based on the identification information received by the network, and / or the information associated with the NSI, and / or the network capability information, and / or the operator policy, and / or the network state, and / or the user registration information, etc.

[0176] The 12th identification information may be information for identifying a UAV. Further, the 12th identification information may be information for identifying a UAV - C. Further, the 12th identification information may be information for identifying a UAV paired with a UAV - C. Further, the 12th identification information may be information for identifying a UAV - C paired with a UAV. Further, the 12th identification information may be information used in direct C2 communication.

[0177] Further, the 12th identification information may be information included in the Service-level-AA container. Also, the 12th identification information may be the Service-level device ID included in the Service-level-AA container.

[0178] Also, the 12th identification information may be the CAA-level UAV ID or the 3GPP UAV ID.

[0179] The 13th identification information may be the source user info. Also, the 13th identification information may be the ID of the application layer of the target UE. Also, the 13th identification information may be the ID of the application layer of the UE on the side transmitting the message. Also, the 13th identification information may be information received from the upper layer. Also, the 13th identification information may be the source user info with the ID of the application layer of the target UE received from the upper layer set therein.

[0180] Also, the 13th identification information may be information included in the message used for communication between two UEs.

[0181] The 14th identification information may be information for identifying the application of the UAS. Also, the 14th identification information may be information for requesting the application of the UAS. Also, the 14th identification information may be information for using the application of the UAS. Also, the 14th identification information may be information used in the application of the UAS.

[0182] Also, the 14th identification information may be information for identifying the application of the UAS accepted by the target UE. Also, the 14th identification information may be information for requesting the application of the UAS accepted by the target UE. Also, the 14th identification information may be information for using the application of the UAS accepted by the target UE. Also, the 14th identification information may be information used for the application of the UAS accepted by the target UE.

[0183] Also, the 14th identification information may be a response to the 5th identification information. Also, the 14th identification information may be the 5th identification information accepted by the target UE.

[0184] Also, the 14th identification information may be a ProSe identifier.

[0185] The 15th identification information may be information indicating cancellation of authentication and / or authorization of direct C2 communication. Also, the 15th identification information may be information indicating whether to cancel authentication and / or authorization of direct C2 communication.

[0186] Also, the 15th identification information may be information indicating cancellation of permission for direct C2 communication. Also, the 15th identification information may be information indicating whether to cancel permission for direct C2 communication.

[0187] The 16th identification information may be information indicating cancellation of authentication and / or authorization of direct C2 communication and / or C2 communication using a PDU session. Also, the 16th identification information may be information indicating whether to cancel authentication and / or authorization of direct C2 communication and / or C2 communication.

[0188] Also, the 16th identification information may be information indicating cancellation of direct C2 communication and / or permission for C2 communication. Also, the 16th identification information may be information indicating whether to cancel direct C2 communication and / or permission for C2 communication.

[0189] The 15th identification information and / or the 16th identification information may be information included in the Service-level-AA container. The 15th identification information and / or the 16th identification information may be the C2 approval result and / or the Service-level-AA response and / or the direct C2 approval result included in the Service-level-AA container, or may be information included in the C2 approval result and / or the Service-level-AA response and / or the direct C2 approval result.

[0190] Also, the 15th identification information and / or the 16th identification information may be information transmitted by the USS.

[0191] Furthermore, the 15th identification information and / or the 16th identification information may be information selected and determined based on the identification information received by the network, and / or the information associated with the NSI, and / or the network capability information, and / or the operator policy, and / or the network state, and / or the user registration information, etc.

[0192] The 17th identification information may be a reason value indicating the reason for which the registration procedure or the PDU session establishment procedure was rejected. Also, the 17th identification information may be a reason value indicating the reason for which the PDU session change procedure was started. Also, the 17th identification information may be a reason value indicating the reason for which the PDU session release procedure was started. The 17th identification information may be a 5GSM (5GS Session Management) reason value.

[0193] The 17th identification information may be a reason value indicating a reason for canceling the authentication and / or authorization of direct C2 communication and / or C2 communication using a PDU session.

[0194] Also, the 17th identification information may be a reason value indicating a reason for canceling the permission of direct C2 communication and / or C2 communication.

[0195] The 17th identification information may be information included in the Service-level-AA container. The 17th identification information may be information included in the C2 approval result and / or Service-level-AA response and / or direct C2 approval result.

[0196] Furthermore, the 17th identification information may be information selected and determined by the network based on the received identification information, and / or information associated with the NSI, and / or the network capability information, and / or the operator policy, and / or the network state, and / or the user registration information, etc.

[0197] The 18th identification information is a timer value. The 18th identification information may be a timer value indicating a grace period until the release of the PDU session for direct C2 communication and / or C2 communication. Also, the 18th identification information may be a timer value indicating the time to release the PDU session for direct C2 communication and / or C2 communication.

[0198] The 18th identification information may be a timer value with a specified start time and / or end time.

[0199] Also, when the timer value is zero, the 18th identification information may indicate that direct C2 communication and / or the PDU session for C2 communication must be released immediately after receiving the 18th identification information. Also, when the timer value is zero, the 18th identification information may indicate canceling the authentication and / or authorization of direct C2 communication and / or C2 communication using the PDU session. Also, when the timer value is zero, the 18th identification information may indicate not authenticating and / or authorizing direct C2 communication and / or C2 communication using the PDU session.

[0200] The 18th identification information may be information included in the Service-level-AA container. The 18th identification information may be information included in the C2 approval result and / or Service-level-AA response and / or direct C2 approval result.

[0201] Furthermore, the 18th identification information may be information selected and determined by the network based on the received identification information, and / or information associated with the NSI, and / or the network capability information, and / or the operator policy, and / or the network state, and / or the user's registration information, etc.

[0202] [3.2. Description of Procedures Used in Each Embodiment] Next, the procedures used in each embodiment will be described. Note that the procedures used in each embodiment include a registration procedure. Hereinafter, each procedure will be described.

[0203] Furthermore, in each embodiment, as described in FIG. 2, an example will be described where the HSS and the UDM, the PCF and the PCRF, the SMF and the PGW-C, and the UPF and the PGW-U are each configured as the same device (i.e., the same physical hardware, or the same logical hardware, or the same software). However, the content described in this embodiment is also applicable when these are configured as different devices (i.e., different physical hardware, or different logical hardware, or different software). For example, direct data transmission and reception may be performed between them, or data may be transmitted and received via the N26 interface between the AMF and the MME, or data may be transmitted and received via the UE.

[0204] [3.2.1. Registration Procedure] First, the registration procedure will be described with reference to FIG. 6. The registration procedure is a procedure in 5GS. Hereinafter, this procedure refers to the registration procedure. The registration procedure is a procedure for the UE to register with the access network_B, and / or the core network_B, and / or the DN. If the UE is not registered with the network, it can execute this procedure at any timing, for example, at power-on. In other words, if the UE is in the non-registered state (RM-DEREGISTERED state), it can start this procedure at any timing. Also, each device (especially the UE and the AMF) can transition to the registered state (RM-REGISTERED state) based on the completion of the registration procedure.

[0205] Also, the registration procedure may be an initial registration started by the UE. Also, the registration procedure may be a mobility and periodic registration. Also, the registration procedure may be an MM procedure.

[0206] Furthermore, the registration procedure may be a procedure for updating the location registration information of the UE in the network, and / or for periodically notifying the network of the UE's state from the UE, and / or for updating specific parameters regarding the UE in the network.

[0207] Also, the registration in this procedure may be registration for C2 communication or registration for direct C2 communication. Also, the PDU session in this procedure may be registration for UAS service.

[0208] The UE may initiate the registration procedure when it has mobility across TAs. In other words, the UE may initiate the registration procedure when it moves to a TA different from the TA indicated in the TA list it holds. Furthermore, the UE may initiate this procedure when the timer it is running expires. Furthermore, the UE may initiate the registration procedure when the context of each device needs to be updated due to the disconnection or invalidation of the PDU session. Furthermore, the UE may initiate the registration procedure when there is a change in the capability information and / or preference regarding the establishment of the UE's PDU session. Furthermore, the UE may initiate the registration procedure periodically. Furthermore, the UE may initiate the registration procedure based on the completion of the UE configuration update procedure. Note that the UE is not limited to these and can execute the registration procedure at any timing.

[0209] Furthermore, even when in the registered state, the UE may periodically initiate the registration procedure. In other words, the UE may initiate the registration procedure based on the expiration of a timer.

[0210] The registration procedure executed based on the mobility of the UE and the registration procedure executed periodically may be expressed as the registration procedure for mobility and registration update. In other words, the registration procedure for mobility and registration update may be the registration procedure executed based on the mobility of the UE, or may be the registration procedure executed periodically. Further, the registration procedure for mobility and registration update may be the registration procedure executed based on the UE setting update. Further, the registration procedure for mobility and registration update may be the registration procedure executed to establish a communication path for transmitting and receiving user data. Further, the registration procedure for mobility and registration update may be the registration procedure executed based on a request from the network. Further, in other words, the registration procedure for mobility and registration update may be the registration procedure other than the initial registration procedure. Hereinafter, the registration procedure for mobility and registration update may be expressed as this procedure.

[0211] Next, each step of the registration procedure will be described. Note that the registration procedure described below may be the initial registration procedure or the registration procedure for mobility and registration update.

[0212] First, the UE starts the registration procedure by transmitting a Registration request message to the AMF (S800)(S802)(S804). Specifically, the UE transmits an RRC message including the registration request message to the 5G AN (or gNB) (S800). Note that the registration request message is an NAS message. Also, the RRC message may be a control message transmitted and received between the UE and the 5G AN (or gNB). Also, the NAS message is processed in the NAS layer, and the RRC message is processed in the RRC layer. Note that the NAS layer is a layer higher than the RRC layer.

[0213] Here, the UE may include one or more of the first to second identification information in the registration request message and / or the RRC message and transmit it. More specifically, the UE may include one or more of the first to second identification information in the registration request message and / or the RRC message and transmit it, or include it in a control message different from these, for example, a control message of a layer lower than the RRC layer (for example, the MAC layer, the RLC layer, the PDCP layer) and transmit it.

[0214] In addition, by transmitting these identification information, the UE may indicate that the UE supports each function or indicate the UE's request. Further, when a plurality of identification information is transmitted and received, two or more of these identification information may be configured as one or more identification information. In addition, the information indicating the support of each function and the information indicating the request for the use of each function may be transmitted and received as the same identification information or as different identification information.

[0215] Here, the UE may indicate the content of each identification information to the network by transmitting a registration request message.

[0216] In other words, when the UE supports direct C2 communication and / or when the UE requests authentication and / or approval for the establishment of direct C2 communication from the network and / or when the UE requests authentication and / or approval for the use of direct C2 communication from the network, the UE may include the first identification information in the registration request message or transmit it together with the registration request message.

[0217] Similarly, in other words, when the UE supports direct C2 communication, and / or when the UE requests authentication and / or authorization for the establishment of direct C2 communication and / or C2 communication using a PDU session from the network, and / or when the UE requests authentication and / or authorization for the use of direct C2 communication and / or C2 communication using a PDU session from the network, the UE may include the second identification information in the registration request message or transmit it together with the registration request message.

[0218] Furthermore, the UE may indicate to the network the content indicated by the identification information included in the registration request message by including one or more pieces of identification information out of the first to second identification information in the registration request message. Furthermore, the UE may request the network for the content indicated by the identification information included in the registration request message by including one or more pieces of identification information out of the first to second identification information in the registration request message.

[0219] Still, the UE may select and determine whether to include one or more pieces of identification information out of the first to second identification information in the registration request message based on subscriber information, and / or network status, and / or user registration information, and / or context held by the UE, etc.

[0220] Still, the UE may also include and transmit identification information other than the first to second identification information in the registration request message. Specifically, the UE may include the Service-level-AA container in the registration request message. Or, the UE may use the Service-level-AA container for the transmission of the first to second identification information. Specifically, the UE may include one or more pieces of identification information out of the first to second identification information in the Service-level-AA container, and further include the Service-level-AA container in the registration request message.

[0221] Also, the UE may start the PDU session establishment procedure during the registration procedure by including the SM message in the registration request message and sending it, or by sending the SM message together with the registration request message. Here, the SM message may be a PDU session establishment request message.

[0222] When the 5G AN (or gNB) receives an RRC message including a registration request message, it selects an AMF that transfers the registration request message (S802). Note that the 5G AN (or gNB) can select an AMF based on the information included in the registration request message and / or the RRC message. The 5G AN (or gNB) extracts the registration request message from the received RRC message and transfers the registration request message to the selected AMF (S804).

[0223] When the AMF receives a registration request message, it can perform a first condition determination. The first condition determination is for determining whether the network (or the AMF) accepts the UE's request. When the first condition determination is true, the AMF starts the procedure in (A) of FIG. 6, whereas when the first condition determination is false, the AMF starts the procedure in (B) of FIG. 6.

[0224] First, the first condition determination may be executed based on reception of a registration request message, and / or each piece of identification information included in the registration request message, and / or subscriber information, and / or network capability information, and / or operator policy, and / or network state, and / or user registration information, and / or context held by the AMF, etc. For example, when the network permits the UE's request, the first condition determination is true, and when the network does not permit the UE's request, the first condition determination may be false. Also, when the network to which the UE is to be registered and / or a device in the network supports the function requested by the UE, the first condition determination is true, and when the network does not support the function requested by the UE, the first condition determination may be false. Further, when the transmitted and received identification information is permitted, the first condition determination is true, and when the transmitted and received identification information is not permitted, the first condition determination may be false. Note that the conditions for determining the truth or falsehood of the first condition determination are not limited to the conditions described above.

[0225] First, the case where the first condition determination is true will be described. In the procedure of FIG. 6(A), the AMF can first execute the fourth condition determination. The fourth condition determination is for determining whether the AMF performs transmission and reception of SM messages to and from the SMF.

[0226] Note that the fourth condition determination may be executed based on whether the AMF has received an SM message. Also, the fourth condition determination may be executed based on whether an SM message is included in the registration request message. For example, when the AMF has received an SM message and / or when an SM message is included in the registration request message, the fourth condition determination may be true, and when the AMF has not received an SM message and / or when an SM message is not included in the registration request message, the fourth condition determination may be false. Note that the conditions for determining the truth or falsehood of the fourth condition determination are not limited to the conditions described above.

[0227] Next, based on the reception of the registration request message and / or the completion of the transmission and reception of the SM message between the AMF and the SMF, the AMF transmits a Registration accept message to the UE via the 5G AN (or gNB) as a response message to the registration request message (S808). For example, when the fourth condition determination is false, the AMF may transmit a registration acceptance message based on the reception of the registration request message from the UE. Also, when the fourth condition determination is true, the AMF may transmit a registration acceptance message based on the completion of the transmission and reception of the SM message between the AMF and the SMF. Note that the registration acceptance message is a NAS message transmitted and received on the N1 interface, but is transmitted and received included in the RRC message between the UE and the 5G AN (gNB).

[0228] The AMF may include in the registration acceptance message one or more pieces of identification information out of the identification information from 10 to 12 and 15 to 18. Note that by transmitting these pieces of identification information, the AMF may indicate that the network supports each function or that the UE's request has been accepted. Furthermore, when a plurality of pieces of identification information are transmitted and received, two or more of these pieces of identification information may be configured as one or more pieces of identification information. Note that the information indicating the support of each function and the information indicating the request for the use of each function may be transmitted and received as the same piece of identification information or as different pieces of identification information.

[0229] Furthermore, the network may indicate to the UE the content indicated by the identification information included in the registration acceptance message by including one or more pieces of identification information out of the identification information from 10 to 12 and 15 to 18 in the registration acceptance message. Furthermore, the network may permit the UE the content indicated by the identification information included in the registration acceptance message by including one or more pieces of identification information out of the identification information from 10 to 12 and 15 to 18 in the registration acceptance message.

[0230] Here, the network may indicate to the UE the content of the above identification information by transmitting the registration acceptance message.

[0231] Still, the AMF may select and determine whether to include one or more of the identification information from the 10th to 12th and 15th to 18th identification information in the registration acceptance message based on each received identification information, and / or subscriber information, and / or network capability information, and / or operator policy, and / or network status, and / or user registration information, and / or context held by the AMF, etc.

[0232] Still, the AMF may also include and transmit identification information other than the 10th to 12th and 15th to 18th identification information in the registration acceptance message. Specifically, the AMF may include the Service-level-AA container in the registration acceptance message. Or, the AMF may use the Service-level-AA container for transmitting the 10th to 12th and 15th to 18th identification information. Specifically, the AMF may include one or more of the 10th to 12th and 15th to 18th identification information in the Service-level-AA container, and further include the Service-level-AA container in the registration acceptance message. The UE may receive the registration acceptance message including the Service-level-AA container.

[0233] Also, the AMF can include the SM message in the registration acceptance message and transmit it, or transmit the SM message together with the registration acceptance message. However, this transmission method may be executed when the SM message is included in the registration request message and the fourth condition determination is true. Also, this transmission method may be executed when the SM message is included together with the registration request message and the fourth condition determination is true. By performing such a transmission method, the AMF can indicate that the procedure for SM has been accepted in the registration procedure. Here, the SM message may be a PDU session establishment request message or a PDU session establishment acceptance message.

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

[0235] Furthermore, the AMF may include in the registration acceptance message information indicating that some of the UE's requests have been rejected, or may indicate the reasons why some of the UE's requests have been rejected by sending information indicating that some of the UE's requests have been rejected. Furthermore, the UE may recognize the reasons why some of the UE's requests have been rejected by receiving information indicating that some of the UE's requests have been rejected. Note that the reason for rejection may be information indicating that the content indicated by the identification information received by the AMF is not permitted.

[0236] The UE receives a registration acceptance message from the AMF via the 5G AN (gNB) (S808). By receiving the registration acceptance message, the UE can recognize that the request by the registration request message has been accepted and the content of various identification information included in the registration acceptance message.

[0237] Furthermore, the UE can send a registration completion message to the AMF via the 5G AN (gNB) as a response message to the registration acceptance message (S810). Here, the registration completion message is a NAS message transmitted and received on the N1 interface, but is transmitted and received included in an RRC message between the UE and the 5G AN (gNB).

[0238] The AMF receives the registration completion message via the 5G AN (gNB) (S810). Also, each device completes the procedure in (A) of FIG. 6 based on the transmission and reception of the registration acceptance message and / or the registration completion message.

[0239] Next, the case where the first condition determination is false will be described. In the procedure of FIG. 6(B), the AMF transmits a Registration reject message to the UE via the 5G AN (gNB) as a response message to the registration request message (S812). Here, the registration reject message is a NAS message transmitted and received on the N1 interface, but is transmitted and received included in the RRC message between the UE and the 5G AN (gNB).

[0240] Here, the AMF may include one or more pieces of identification information among the identification information from 10 to 12 and 15 to 18 in the registration reject message. Furthermore, the AMF may indicate that the UE's request has been rejected or indicate the reason for the rejection of the UE's request by transmitting one or more pieces of identification information among the identification information from 10 to 12 and 15 to 18.

[0241] Furthermore, the network may show the UE the content indicated by the identification information included in the registration reject message by including one or more pieces of identification information among the identification information from 10 to 12 and 15 to 18 in the registration reject message. Furthermore, the network may not permit the UE the content indicated by the identification information included in the registration reject message by including one or more pieces of identification information among the identification information from 10 to 12 and 15 to 18 in the registration reject message.

[0242] Note that the AMF may select and determine whether to include one or more pieces of identification information among the identification information from 10 to 12 and 15 to 18 in the registration reject message based on each received piece of identification information, and / or subscriber information, and / or network capability information, and / or operator policy, and / or network status, and / or user registration information, and / or the context held by the AMF, etc.

[0243] Furthermore, the AMF may indicate that the UE's request in the registration request message has been rejected by sending a registration rejection message. Further, the AMF may include information indicating the reason for rejection in the registration rejection message and send it, or may indicate the reason for rejection by sending the reason for rejection. Further, the UE may recognize the reason for the rejection of the UE's request by receiving information indicating the reason for the rejection of the UE's request. Note that the reason for rejection may be information indicating that the content indicated by the identification information received by the AMF is not permitted.

[0244] The UE receives a registration rejection message from the AMF via the 5G AN (gNB) (S812). By receiving the registration rejection message, the UE can recognize that the UE's request in the registration request message has been rejected and the content of various identification information included in the registration rejection message. Also, after the UE sends a registration request message, if the UE does not receive a registration rejection message even after a predetermined period has elapsed, the UE may recognize that the UE's request has been rejected. Each device completes the procedure (B) during this procedure based on the transmission and reception of the registration rejection message.

[0245] Note that the procedure (B) in FIG. 6 may be started when the procedure (A) in FIG. 6 is aborted.

[0246] Each device completes the registration procedure based on the completion of the procedure (A) or (B) in FIG. 6. Note that each device may transition to a state where the UE is registered with the network (RM_REGISTERED state) based on the completion of the procedure (A) in FIG. 6, or may maintain a state where the UE is not registered with the network (RM_DEREGISTERED state) or transition to a state where the UE is not registered with the network based on the completion of the procedure (B) in FIG. 6. Also, the transition of each device to each state may be performed based on the completion of the registration procedure or may be performed based on the establishment of a PDU session.

[0247] Also, the UE may complete the registration procedure based on the receipt of a registration acceptance message or a registration rejection message.

[0248] Furthermore, each device may perform processing based on the information transmitted and received in the registration procedure based on the completion of the registration procedure. For example, when information indicating that some requests of the UE have been rejected is transmitted and received, the UE may recognize the reason why the request has been rejected. Furthermore, each device may perform this procedure again based on the reason why the UE's request has been rejected, or may perform a registration procedure for the core network_B or another cell.

[0249] Furthermore, the UE may store the identification information received together with the registration acceptance message and / or the registration rejection message based on the completion of the registration procedure, or may recognize the determination of the network.

[0250] Furthermore, when the UE receives one or more pieces of identification information among the identification information from 10 to 12 and from 15 to 18, the UE may recognize the content indicated by the received identification information. Furthermore, when the UE receives one or more pieces of identification information among the identification information from 10 to 12 and from 15 to 18, the UE may recognize that the content indicated by the identification information included in the registration acceptance message or the registration rejection message has been permitted.

[0251] Here, when the UE receives the identification information of 10, the UE may start the procedure for establishing direct C2 communication. In other words, when the UE receives the identification information of 10, the UE may recognize that the direct C2 communication has been authenticated and / or approved, and may start the procedure for establishing direct C2 communication.

[0252] Also, when the UE receives the identification information of 10, the UE may not start the procedure for establishing direct C2 communication. In other words, when the UE receives the identification information of 10, the UE may recognize that the direct C2 communication has not been authenticated and / or approved, and may not start the procedure for establishing direct C2 communication.

[0253] Also, when the UE receives the 11th identification information, it may start the procedure for establishing direct C2 communication and / or the procedure for establishing a PDU session for C2 communication. In other words, when the UE receives the 11th identification information, it recognizes that direct C2 communication and / or C2 communication using a PDU session has been authenticated and / or approved, and may start the procedure for establishing direct C2 communication and / or the procedure for establishing a PDU session for C2 communication.

[0254] Also, when the UE receives the 11th identification information, it may not start the procedure for establishing direct C2 communication and / or the procedure for establishing a PDU session for C2 communication. In other words, when the UE receives the 11th identification information, it recognizes that direct C2 communication and / or C2 communication using a PDU session has not been authenticated and / or approved, and may not start the procedure for establishing direct C2 communication and / or the procedure for establishing a PDU session for C2 communication.

[0255] Also, when the UE receives the 12th identification information, it may set the identification information of the UAV or UAV-C. Also, when the UE receives the 12th identification information, it may delete the stored identification information of the UAV or UAV-C and store the received identification information of the UAV or UAV-C.

[0256] Also, when the UE receives the 15th identification information, it may start the procedure for releasing direct C2 communication. In other words, when the UE receives the 15th identification information, it recognizes that the authentication and / or approval of direct C2 communication has been cancelled, and may start the procedure for releasing direct C2 communication.

[0257] Also, when the UE receives the 16th identification information, it may initiate the release procedure for direct C2 communication and / or the PDU session release procedure for C2 communication. In other words, when the UE receives the 16th identification information, it recognizes that the authentication and / or authorization of direct C2 communication and / or C2 communication using the PDU session has been cancelled, and may initiate the release procedure for direct C2 communication and / or the PDU session release procedure for C2 communication.

[0258] Also, when the UE receives the 18th identification information, it may set the timer value indicated by the 18th identification information to the first timer. Also, when the UE receives the 18th identification information, it may start the first timer using the timer value indicated by the 18th identification information. Further, when the first timer expires, the UE may initiate the release procedure for the communication path for direct C2 communication. Also, before the first timer expires, the UE may initiate the release procedure for the communication path for direct C2 communication.

[0259] Here, the first timer may be a timer for managing the grace period until the release of direct C2 communication and / or the PDU session for C2 communication. Also, the first timer may be a timer for managing the time to release direct C2 communication and / or the PDU session for C2 communication. Also, the first timer may be a timer for managing the timer value indicated by the 18th identification information.

[0260] Note that the above behavior of the UE may be performed after receiving the registration acceptance message or the registration rejection message. Also, the above behavior of the UE may be performed after receiving one or more pieces of identification information among the 10th to 12th, 15th to 18th identification information.

[0261] The UE may recognize the content of the above identification information by receiving a registration acceptance message or a registration rejection message.

[0262] Furthermore, the behavior to be executed when each piece of identification information is received may be executed based on the received identification information.

[0263] [3.2.2. PDU Session Establishment Procedure] Next, the behavior of each device when the UE executes the PDU session establishment procedure will be described with reference to FIG. 7. Hereinafter, the PDU session establishment procedure may be referred to as this procedure. Also, the PDU session establishment procedure may be an SM procedure.

[0264] Also, the PDU session in this procedure may be a PDU session for C2 communication or a PDU session for direct C2 communication. Also, the PDU session in this procedure may be a PDU session for the UAS service.

[0265] Furthermore, this procedure may be executed after executing the registration procedure one or more times.

[0266] First, the UE sends a PDU session establishment request message to the SMF (S1400)(S1402)(S1404) to start the PDU session establishment procedure. Then, the SMF receives the PDU session establishment request message from the UE.

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

[0268] Here, the UE may include one or more pieces of identification information out of the first to second identification information in a PDU session establishment request message or an NAS message and transmit them.

[0269] Furthermore, by transmitting these identification information, the UE may indicate that the UE supports each function, or may indicate the UE's request. Further, when a plurality of identification information is transmitted and received, two or more pieces of these identification information may be configured as one or more pieces of identification information. Note that the information indicating the support of each function and the information indicating the request for the use of each function may be transmitted and received as the same identification information, or may be transmitted and received as different identification information.

[0270] Here, the UE may indicate the content of each identification information to the network by transmitting a PDU session establishment request message or an NAS message.

[0271] In other words, when the UE supports direct C2 communication and / or when the UE requests authentication and / or authorization for the establishment of direct C2 communication from the network and / or when the UE requests authentication and / or authorization for the use of direct C2 communication from the network, the UE may include the first identification information in a PDU session establishment request message or include it in an NAS message together with the PDU session establishment request message and transmit it.

[0272] Similarly, in other words, when the UE supports direct C2 communication and / or when the UE requests authentication and / or authorization for the establishment of direct C2 communication and / or C2 communication using a PDU session from the network and / or when the UE requests authentication and / or authorization for the use of direct C2 communication and / or C2 communication using a PDU session from the network, the UE may include the second identification information in a PDU session establishment request message or include it in an NAS message together with the PDU session establishment request message and transmit it.

[0273] Also, the access network is 3GPP access or non-3GPP access and may include a base station device. That is, the UE transmits NAS messages to the AMF via the base station device.

[0274] Also, the UE may request the establishment of a PDU session that supports C2 communication by transmitting a PDU session establishment request message. In other words, the UE may request the establishment of a PDU session that supports a QoS flow for C2 communication by transmitting a PDU session establishment request message.

[0275] Also, when the UE requests the establishment of a PDU session that supports C2 communication, it may request the establishment of an Always-on PDU session. In other words, when the UE requests the establishment of a PDU session that supports a QoS flow for C2 communication, it may request the establishment of an Always-on PDU session.

[0276] In addition, the UE may select and determine whether to include one or more pieces of identification information out of the first to second identification information in the PDU session establishment request message based on subscriber information, and / or network status, and / or user registration information, and / or context held by the UE, etc.

[0277] Furthermore, the UE may also include identification information other than the first to second identification information in the PDU session establishment request message. Specifically, the UE may include a Service-level-AA container in the PDU session establishment request message. Alternatively, the UE may use the Service-level-AA container to transmit the first to second identification information. Specifically, the UE may include one or more of the first to second identification information in the Service-level-AA container, and may further include the Service-level-AA container information element in the PDU session establishment request message.

[0278] Next, when the AMF receives a NAS message, it can recognize what the UE is requesting and / or the content of the information (messages, containers, information) included in the NAS message.

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

[0280] Next, the AMF transmits at least a part of the information (messages, containers, information) included in the NAS message received from the UE to the selected SMF via, for example, the N11 interface (S1404).

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

[0282] Here, the SMF may perform a second condition determination. Also, the second condition determination may be for determining whether the network accepts the UE's request. If the SMF determines that the second condition determination is true, it may start the procedure in (A) of FIG. 7. If the SMF determines that the second condition determination is false, it may start the procedure in (B) of FIG. 7.

[0283] In addition, the second condition determination may be performed by an NF other than the SMF. That NF may be, for example, the NSSF, NWDAF, PCF, or NRF. When an NF other than the SMF performs the second condition determination, the SMF may provide that NF with at least a part of the information necessary for performing the second condition determination, specifically, the information received from the UE (S1406). Then, when that NF determines the truth or falsehood of the second condition determination based on the information received from the SMF, it may transmit information including the result of the second condition determination (that is, true or false) to the SMF. The SMF may determine the identification information and / or control message to be transmitted to the UE based on the result of the second condition determination received from that NF.

[0284] In addition, the second condition determination may be performed based on information received from the AMF (messages, containers, information), and / or subscriber information, and / or network capability information, and / or UE policy, and / or operator policy, and / or network status, and / or user registration information, and / or context held by the SMF, etc.

[0285] For example, when the network permits the request of the UE, the second condition determination may be determined to be true, and when the network does not permit the request of the UE, the second condition determination may be determined to be false. Also, when the network to which the UE is connected and / or the device in the network supports the function requested by the UE, the second condition determination may be determined to be true, and when the function requested by the UE is not supported, the second condition determination may be determined to be false. Also, when the transmitted and received identification information is permitted, the second condition determination may be determined to be true, and when the transmitted and received identification information is not permitted, the second condition determination may be determined to be false.

[0286] Note that the conditions for determining the truth or falsehood of the second condition determination are not necessarily limited to the conditions described above.

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

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

[0289] 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 policy, and / or operator policy, and / or network status, and / or user registration information, and / or context held by the SMF, etc., the SMF may determine whether to perform approval of C2 communication during this procedure.

[0290] When approval of C2 communication is performed during this procedure, the SMF may determine approval of the establishment of direct C2 communication and / or C2 communication using the PDU session based on at least one of the first to second identification information.

[0291] Here, the SMF may select one or more UPFs based on information received from the AMF (such as 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 registration information, and / or context held by the SMF, etc. Also, when multiple UPFs are selected, the SMF may send an N4 session establishment request message to each UPF. Here, it is assumed that a UPF has been selected.

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

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

[0294] Next, based on the reception of a PDU session establishment request message, and / or the selection of a UPF, and / or the reception of an N4 session establishment response message, etc., the SMF sends a PDU session establishment acceptance message to the UE. Then, the UE receives the PDU session establishment acceptance message from the SMF (S1418)(S1420)(S1422).

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

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

[0297] Specifically, when the AMF transmits an N2 PDU session request message to a base station device included in the access network (S1414), the base station device that has received the N2 PDU session request message transmits an NAS message to the UE (S1416). Here, the N2 PDU session request message may include an NAS message, and / or N2 SM information. Also, the NAS message may include a PDU session ID and / or an N1 SM container.

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

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

[0300] Here, the SMF and / or AMF may include one or more of the identification information from items 10 to 12 and 15 to 18 in the PDU session establishment acceptance message, and / or the N1 SM container, and / or the NAS message, and / or the N2 SM information, and / or the N2 PDU session request message when sending them.

[0301] In addition, the SMF may indicate that the network supports each function, or that the UE's request has been accepted, or that the request from the UE is not permitted, or a combination of these by sending these identification information and / or the PDU session establishment acceptance message. Further, when multiple pieces of identification information are transmitted and received, two or more of these pieces of identification information may be configured as one or more pieces of identification information. Note that the information indicating support for each function and the information indicating a request for the use of each function may be transmitted and received as the same identification information or as different identification information.

[0302] Here, the network may indicate the content of the above identification information to the UE by sending a PDU session establishment acceptance message.

[0303] Furthermore, the network may also include identification information other than the identification information from 10 to 12 and from 15 to 18 in the PDU session establishment acceptance message and transmit it. Specifically, the network may include the Service-level-AA container in the PDU session establishment acceptance message. Alternatively, the network may use the Service-level-AA container for transmitting the identification information from 10 to 12 and from 15 to 18. Specifically, the network may include one or more pieces of the identification information from 10 to 12 and from 15 to 18 in the Service-level-AA container, and further include the Service-level-AA container in the PDU session establishment acceptance message. The UE may receive the PDU session establishment acceptance message including the Service-level-AA container.

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

[0305] Next, when the UE receives a NAS message via, for example, the N1 interface (S1416), it can recognize that the request of the UE by the PDU session establishment request message has been accepted and / or the content of information (message, container, information) included in the NAS message.

[0306] Next, each step of the procedure in (B) of FIG. 7 will be described.

[0307] First, based on the reception of a PDU session establishment request message, the SMF transmits, for example, via the N11 interface, an N1 SM container and / or a PDU session ID to the AMF (S1418). Here, the N1 SM container may include a PDU session establishment rejection message. Further, the PDU session ID may be included in the PDU session establishment rejection message.

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

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

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

[0311] In addition, the SMF may indicate that the request of the UE has been rejected by transmitting a PDU session establishment rejection message, or may indicate that the request from the UE has not been permitted, or may indicate information combining these.

[0312] Here, the SMF and / or AMF may include one or more of the identification information from 10 to 12, 15 to 18 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 when transmitting.

[0313] In addition, the SMF and / or AMF may 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 each received identification information, and / or subscriber information, and / or network capability information, and / or UE policy, and / or operator policy, and / or network status, and / or user registration information, and / or context held by the SMF and / or AMF, etc.

[0314] Next, when the UE receives a NAS message via, for example, the N1 interface (S1422), it can recognize that the request of the UE by the PDU session establishment request message has been rejected and / or the content of the information (message, container, information) included in the NAS message.

[0315] Furthermore, when the UE receives one or more of the identification information from 10 to 12, 15 to 18, it may recognize the content indicated by the received identification information. Furthermore, when the UE receives one or more of the identification information from 10 to 12, 15 to 18, it may recognize that the content indicated by the identification information included in the NAS message or PDU session establishment acceptance message or PDU session establishment rejection message is permitted.

[0316] Here, when the UE receives the tenth identification information, it may start the procedure for establishing direct C2 communication. In other words, when the UE receives the tenth identification information, it may recognize that the direct C2 communication has been authenticated and / or approved, and start the procedure for establishing direct C2 communication.

[0317] Also, when the UE receives the tenth identification information, it may not start the procedure for establishing direct C2 communication. In other words, when the UE receives the tenth identification information, it may recognize that the direct C2 communication has not been authenticated and / or approved, and may not start the procedure for establishing direct C2 communication.

[0318] Also, when the UE receives the eleventh identification information, it may start the procedure for establishing direct C2 communication and / or the procedure for establishing a PDU session for C2 communication. In other words, when the UE receives the eleventh identification information, it may recognize that the direct C2 communication and / or the C2 communication using the PDU session has been authenticated and / or approved, and may start the procedure for establishing direct C2 communication and / or the procedure for establishing a PDU session for C2 communication.

[0319] Also, when the UE receives the eleventh identification information, it may not start the procedure for establishing direct C2 communication and / or the procedure for establishing a PDU session for C2 communication. In other words, when the UE receives the eleventh identification information, it may recognize that the direct C2 communication and / or the C2 communication using the PDU session has not been authenticated and / or approved, and may not start the procedure for establishing direct C2 communication and / or the procedure for establishing a PDU session for C2 communication.

[0320] Also, when the UE receives the 12th identification information, it may set the identification information of the UAV or UAV-C. Also, when the UE receives the 12th identification information, it may delete the stored identification information of the UAV or UAV-C and store the received identification information of the UAV or UAV-C.

[0321] Also, when the UE receives the 15th identification information, it may start the release procedure for direct C2 communication. In other words, when the UE receives the 15th identification information, it may recognize that the authentication and / or authorization of direct C2 communication has been canceled and start the release procedure for direct C2 communication.

[0322] Also, when the UE receives the 16th identification information, it may start the release procedure for direct C2 communication and / or the PDU session release procedure for C2 communication. In other words, when the UE receives the 16th identification information, it may recognize that the authentication and / or authorization of direct C2 communication and / or C2 communication using the PDU session has been canceled and start the release procedure for direct C2 communication and / or the PDU session release procedure for C2 communication.

[0323] Also, when the UE receives the 18th identification information, it may set the timer value indicated by the 18th identification information to the first timer. Also, when the UE receives the 18th identification information, it may start the first timer using the timer value indicated by the 18th identification information. Further, when the first timer expires, the UE may start the release procedure for the communication path for direct C2 communication. Also, before the first timer expires, the UE may start the release procedure for the communication path for direct C2 communication.

[0324] Here, the first timer may be a timer for managing the grace period until the release of direct C2 communication and / or the PDU session for C2 communication. Also, the first timer may be a timer for managing the time to release direct C2 communication and / or the PDU session for C2 communication. Further, the first timer may be a timer for managing the timer value indicated by the 18th identification information.

[0325] Note that the behavior of the UE may be performed after receiving a PDU session acceptance message or a PDU session rejection message. Also, the behavior of the UE may be performed after receiving one or more pieces of identification information among the 10th to 12th and 15th to 18th identification information.

[0326] The UE may recognize the content of the identification information by receiving an NAS message, a PDU session establishment acceptance message, or a PDU session establishment rejection message.

[0327] Each device may complete this procedure based on the transmission and reception of a PDU session establishment acceptance message. Also, each device may establish a PDU session based on the completion of this procedure. At this time, each device may transition to a state where it can communicate with the DN using the established PDU session.

[0328] Each device may complete this procedure based on the transmission and reception of a PDU session establishment acceptance message or a PDU session establishment rejection message. At this time, since each device cannot establish a PDU session, if there is no already established PDU session, it cannot communicate with the DN.

[0329] Note that each process executed by the UE based on the reception of each piece of identification information shown above may be executed during this procedure, after the completion of this procedure, or after the completion of this procedure based on the completion of this procedure.

[0330] [3.2.3. Overview of Network-Driven Session Management Procedures] Next, an overview of the network-driven session management procedure will be described. Hereinafter, the network-driven session management procedure is also referred to as this procedure. This procedure is a procedure for session management that the network executes in a leading manner for an established PDU session. Also, the network-driven session management procedure may be an SM procedure.

[0331] Also, the PDU session in this procedure may be a PDU session for C2 communication or a PDU session for direct C2 communication. Also, the PDU session in this procedure may be a PDU session for UAS services.

[0332] Note that this procedure may be a network-driven PDU session modification procedure and / or a network-driven PDU session release procedure, etc., or may execute a network-driven session management procedure not limited to these. Note that each device may transmit and receive a PDU session modification message in the network-driven PDU session modification procedure, or may transmit and receive a PDU session release message in the network-driven PDU session release procedure.

[0333] Also, when this procedure is a network-driven PDU session modification procedure, the session management request message in this procedure may be a PDU SESSION MODIFICATION COMMAND message. Also, when this procedure is a network-driven PDU session release procedure, the session management request message in this procedure may be a PDU SESSION RELEASE COMMAND message.

[0334] Also, when this procedure is a network-initiated PDU session modification procedure, the session management completion message in this procedure may be a PDU SESSION MODIFICATION COMPLETE message. Also, when this procedure is a network-initiated PDU session release procedure, the session management completion message in this procedure may be a PDU SESSION RELEASE COMPLETE message.

[0335] [3.2.3.1. Example of Network-Initiated Session Management Procedure] Next, an example of a network-initiated session management procedure will be described with reference to FIG. 8. Hereinafter, this procedure refers to a network-initiated session management procedure. Each step of this procedure will be described.

[0336] Based on the completion of the registration procedure and / or the PDU session establishment procedure, each device in the UE and the core network_B190 starts a network-initiated session management procedure at an arbitrary timing.

[0337] Specifically, the device in the core network_B190 may start this procedure based on the reception of a PDU session modification request message from the UE, or may start this procedure based on the reception of a PDU session release request message from the UE. Note that when this procedure is started based on the reception of a PDU session modification request message, this procedure may be a network-initiated PDU session modification procedure. Further, when this procedure is started based on the reception of a PDU session release request message, this procedure may be a network-initiated PDU session release procedure.

[0338] Furthermore, the device in the core network_B190 may start this procedure based on a request from a device in the DN or another device in the core network.

[0339] Here, the device in the core network_B190 that starts this procedure may be the SMF and / or the AMF, and the UE may send and receive messages in this procedure via the AMF and / or the access network_B. Further, the device in the DN may be the AF (Application Function) in the DN.

[0340] The device in the core network_B190 sends a network-initiated session management request message to the UE (S1602) to start network-initiated session management. Further, the UE receives a network-initiated session management request message from the device in the core network_B190.

[0341] Here, the device in the core network_B190 may include at least one of the identification information from 10 to 12 and 15 to 18 in the network-initiated session management request message, and by including this identification information, it may indicate the request of the core network_B190. Further, the device in the core network_B190 may include the PDU session ID in the network-initiated session management request message, and by including the PDU session ID, it may request to perform a change to the PDU session identified by the PDU session ID.

[0342] Note that the PDU session ID included in the PDU session change request message may be the PDU session ID of the established PDU session. Further, when this procedure is executed based on the UE-initiated session management procedure, the PDU session ID included in the PDU session change request message may be the same as the PDU session ID included in the PDU session change request message or the PDU session release request message.

[0343] Here, when the UE receives the tenth identification information, it may start the procedure for establishing direct C2 communication. In other words, when the UE receives the tenth identification information, it may recognize that the direct C2 communication has been authenticated and / or approved, and start the procedure for establishing direct C2 communication.

[0344] Also, when the UE receives the tenth identification information, it may not start the procedure for establishing direct C2 communication. In other words, when the UE receives the tenth identification information, it may recognize that the direct C2 communication has not been authenticated and / or approved, and may not start the procedure for establishing direct C2 communication.

[0345] Also, when the UE receives the eleventh identification information, it may start the procedure for establishing direct C2 communication and / or the procedure for establishing a PDU session for C2 communication. In other words, when the UE receives the eleventh identification information, it may recognize that the direct C2 communication and / or the C2 communication using the PDU session has been authenticated and / or approved, and may start the procedure for establishing direct C2 communication and / or the procedure for establishing a PDU session for C2 communication.

[0346] Also, when the UE receives the eleventh identification information, it may not start the procedure for establishing direct C2 communication and / or the procedure for establishing a PDU session for C2 communication. In other words, when the UE receives the eleventh identification information, it may recognize that the direct C2 communication and / or the C2 communication using the PDU session has not been authenticated and / or approved, and may not start the procedure for establishing direct C2 communication and / or the procedure for establishing a PDU session for C2 communication.

[0347] In addition, when the UE receives the 12th identification information, it may set the identification information of the UAV or UAV-C. Also, when the UE receives the 12th identification information, it may delete the stored identification information of the UAV or UAV-C and store the received identification information of the UAV or UAV-C.

[0348] In addition, when the UE receives the 15th identification information, it may start the release procedure for direct C2 communication. In other words, when the UE receives the 15th identification information, it may recognize that the authentication and / or authorization of direct C2 communication has been cancelled and start the release procedure for direct C2 communication.

[0349] In addition, when the UE receives the 16th identification information, it may start the release procedure for direct C2 communication and / or the PDU session release procedure for C2 communication. In other words, when the UE receives the 16th identification information, it may recognize that the authentication and / or authorization of direct C2 communication and / or C2 communication using the PDU session has been cancelled and start the release procedure for direct C2 communication and / or the PDU session release procedure for C2 communication.

[0350] In addition, when the UE receives the 18th identification information, it may set the timer value indicated by the 18th identification information in the first timer. Also, when the UE receives the 18th identification information, it may start the first timer using the timer value indicated by the 18th identification information. Further, when the first timer expires, the UE may start the release procedure for the communication path for direct C2 communication. Also, before the first timer expires, the UE may start the release procedure for the communication path for direct C2 communication.

[0351] Here, the first timer may be a timer for managing the grace period until the release of direct C2 communication and / or the PDU session for C2 communication. Also, the first timer may be a timer for managing the time to release direct C2 communication and / or the PDU session for C2 communication. Further, the first timer may be a timer for managing the timer value indicated by the 18th identification information.

[0352] Note that the behavior of the UE may be performed after receiving a PDU session change command message or a PDU session release command message. Also, the behavior of the UE may be performed after receiving one or more pieces of identification information among the 10th to 12th and 15th to 18th identification information.

[0353] Next, the UE that has received a network-initiated session management request message transmits a network-initiated session management completion message (S1604). Further, the UE may execute a first process (S1606) based on at least one piece of identification information among the 10th to 12th and 15th to 18th identification information received from the core network_B190, and complete this procedure. Also, the UE may perform the first process based on the completion of this procedure.

[0354] Here, the UE may include the PDU session ID in the network-initiated session management completion message. Note that the PDU session ID included in the network-initiated session management completion message may be the same as the PDU session ID included in the network-initiated session management request message.

[0355] Hereinafter, an example of the first process will be described.

[0356] The first process may be a process in which the UE recognizes what is indicated by the core network_B190, or may be a process in which the UE recognizes a request from the core network_B190. Further, the first process may be a process in which the UE stores the received identification information as a context, or may be a process in which the UE transfers the received identification information to an upper layer and / or a lower layer.

[0357] Also, the UE may execute, as the first process, the behavior when receiving each of the foregoing identification information.

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

[0359] Furthermore, each device completes the network-initiated session management procedure based on the completion of the above-described processing and / or the transmission and reception of a network-initiated session management request message and / or a network-initiated session management completion message.

[0360] Note that each device may change an existing PDU session or release an existing PDU session based on the completion of the network-initiated session management procedure. In other words, each device may change an existing PDU session based on the completion of the PDU session change procedure. Similarly, in other words, each device may release an existing PDU session based on the completion of the PDU session release procedure.

[0361] [3.2.4. Outline of UE-initiated session management procedure] Next, an overview of the UE-initiated session management procedure will be described. Hereinafter, the UE-initiated session management procedure is also referred to as this procedure. This procedure is a procedure for session management that the UE initiates and executes for an established PDU session. Also, the UE-initiated session management procedure may be an SM procedure.

[0362] Also, the PDU session in this procedure may be a PDU session for C2 communication or a PDU session for direct C2 communication. Also, the PDU session in this procedure may be a PDU session for UAS services.

[0363] Note that this procedure may be, for example, a UE-initiated PDU session modification procedure and / or a UE-initiated PDU session release procedure, or may execute a UE-initiated session management procedure not limited to these. Note that each device may transmit and receive a PDU session change request message, and / or a PDU session change command message, and / or a PDU session change completion message, and / or a PDU session change rejection message in the UE-initiated PDU session change procedure. Also, each device may transmit and receive a PDU session release request message, and / or a PDU session release command message, and / or a PDU session release completion message, and / or a PDU session release rejection message in the UE-initiated PDU session release procedure.

[0364] Furthermore, each device completes the UE-initiated session management procedure based on the completion of the above-described processing and / or the transmission and reception of a UE-initiated session management request message and / or a UE-initiated session management completion message.

[0365] [3.2.4.1. Example of UE-initiated PDU session change procedure] Next, each step of this procedure will be described with reference to FIG. 9. Hereinafter, this procedure refers to a UE-initiated PDU session change procedure.

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

[0367] First, the UE starts a UE-initiated PDU session change procedure by sending a PDU session change request message to the SMF (S1802). Here, the UE may include the PDU session ID in the PDU session change request message, or by including the PDU session ID, may request to perform a change on the PDU session identified by the PDU session ID.

[0368] Here, the UE may include at least one of the first to second identification information in the PDU session change request message.

[0369] The PDU session ID included in the PDU session change request message may be the PDU session ID of the established PDU session.

[0370] Next, the SMF receives the PDU session change request message sent by the UE. When the SMF accepts the UE's request, it starts a network-initiated PDU session change procedure. Conversely, when the SMF rejects the UE's request, it sends a PDU session change rejection message to the UE. Hereinafter, the case where the SMF rejects the UE's request will be described.

[0371] Based on the acceptance of the PDU session modification request message, the SMF sends a PDU session modification rejection message to the UE (S1804).

[0372] Here, the SMF may include at least one of the identification information from 10 to 12 and 15 to 18 in the PDU session modification rejection message.

[0373] Here, the PDU session ID included in the PDU session modification rejection message may be the same as the PDU session ID included in the PDU session modification request message. In other words, the PDU session ID included in the PDU session modification rejection message may be the same as the PDU session ID provided by the UE during this procedure.

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

[0375] Here, based on the reception of the PDU session modification rejection message, the UE may recognize that its request has been rejected. Furthermore, based on the reception of the PDU session modification rejection message, the UE may perform a second process (S1806). Note that the second process may also be performed based on the completion of this procedure.

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

[0377] Also, the PDU session change procedure and / or PDU session release procedure for the same PDU session may be the PDU session change procedure and / or PDU session release procedure using the same PDU session ID.

[0378] Furthermore, each device completes the UE-initiated PDU session change procedure based on the completion of the above-described processing and / or the transmission and reception of a UE-initiated PDU session change rejection message.

[0379] [3.2.4.2. Example of UE-initiated PDU session release procedure] Next, each step of this procedure will be described. Hereinafter, this procedure refers to the UE-initiated PDU session release procedure.

[0380] The UE-initiated PDU session release procedure may be the same as the above-described PDU session change procedure.

[0381] Specifically, when this procedure is the UE-initiated PDU session release procedure, the above-described PDU session change request message may be read as a PDU session release request message. Furthermore, when this procedure is the UE-initiated PDU session release procedure, the above-described PDU session change request message may be read as a PDU session release request message, or the above-described PDU session change rejection message may be read as a PDU session release rejection message. Also, the action of changing the PDU session may be read as the action of releasing the PDU session.

[0382] Furthermore, when this procedure is a UE-initiated PDU session release procedure, the behavior of the SMF performed based on the reception of a PDU session release request message may be the same as the behavior of the SMF performed based on the reception of a PDU session modification request message described above. Furthermore, when this procedure is a UE-initiated PDU session release procedure, the behavior of the UE performed based on the reception of a PDU session release rejection message may be the same as the behavior of the UE performed based on the reception of a PDU session modification rejection message described above.

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

[0384] Also, the UE may send a PDU session release request message including at least one of the first to second identification information to the network.

[0385] Furthermore, each device completes the UE-initiated PDU session release procedure based on the completion of the above-described processing and / or the transmission and reception of a UE-initiated PDU session release rejection message.

[0386] [3.2.5. Procedure for Establishing Direct C2 Communication] Next, the behavior of each device when the UE executes a procedure for establishing direct C2 communication will be described with reference to FIG. 10. Hereinafter, the procedure for establishing direct C2 communication may be referred to as this procedure. Also, the procedure for establishing direct C2 communication may be referred to as a direct C2 communication establishment procedure.

[0387] Furthermore, this procedure may be executed after performing the registration procedure, and / or the PDU session establishment procedure, and / or the network-initiated session management procedure, and / or the UE-initiated session management procedure one or more times. Also, this procedure may be executed during the registration procedure, or the PDU session establishment procedure, or the network-initiated session management procedure, or the UE-initiated session management procedure.

[0388] This procedure may be executed in the registration procedure, and / or the PDU session establishment procedure, and / or the network-initiated session management procedure, and / or the UE-initiated session management procedure when the UE is authenticated and / or approved for direct C2 communication by the network. In other words, the UE may start this procedure when receiving the identification information from 10 to 12, 15 to 18. Also, the UE may start this procedure without approval of direct C2 communication from the network.

[0389] Furthermore, in this procedure, there may be an initiating UE and a target UE in the UE.

[0390] Furthermore, in this procedure, the initiating UE and the target UE may send and receive each control message on PC5.

[0391] First, the initiating UE sends a first control message to the target UE (S2000) and starts this procedure.

[0392] Here, the first control message may be a message requesting the establishment of direct C2 communication. Also, the first control message may be a ProSe direct link establishment request message. Also, the first control message may be a Direct Communication Request message.

[0393] Here, the initiating UE may include one or more of the identification information from the third to fifth identification information in the first control message and transmit it. Also, the initiating UE may transmit one or more of the identification information from the third to fifth identification information together with the first control message.

[0394] In addition, by transmitting these identification information, the initiating UE may indicate that the initiating UE supports each function, or may indicate the request of the initiating UE. Further, when a plurality of identification information is transmitted and received, two or more of these identification information may be configured as one or more identification information. In addition, the information indicating the support of each function and the information indicating the request for the use of each function may be transmitted and received as the same identification information, or may be transmitted and received as different identification information.

[0395] Here, the initiating UE may indicate the content of each identification information to the network by transmitting the first control message. Also, the initiating UE may indicate the content of each identification information to the network by transmitting one or more of the identification information from the third to fifth identification information.

[0396] In addition, the initiating UE may select and determine whether to include one or more of the identification information from the third to fifth identification information in the first control message based on the subscriber information, and / or the network state, and / or the user registration information, and / or the context held by the UE, etc.

[0397] Further, the UE may also include, in the first control message, identification information other than the identification information of the third to fifth.

[0398] Also, the initiating UE may request the establishment of direct C2 communication by transmitting the first control message. Further, the initiating UE may request the establishment of direct C2 communication by transmitting one or more pieces of identification information among the identification information of the third to fifth.

[0399] Next, the target UE receives the first control message from the initiating UE.

[0400] When the target UE receives the first control message, it may recognize the content requested by the initiating UE and / or the content of the information (message, container, identification information, etc.) included in the first control message.

[0401] Here, the target UE may perform the third condition determination. Further, the third condition determination may be for the target UE to determine whether to accept the request of the initiating UE. When the target UE determines that the third condition determination is true, it may start the procedure of (A) in FIG. 10, and when the target UE determines that the third condition determination is false, it may start the procedure of (B) in FIG. 10.

[0402] Further, the third condition determination may be executed based on the information (message, container, information, etc.) received from the initiating UE, and / or subscription information, and / or network capability information, and / or UE policy, and / or operator policy, and / or network state, and / or user registration information, and / or context held by the target UE, etc.

[0403] For example, when the target UE permits the request of the initiating UE, the third condition determination may be determined to be true, and when the target UE does not permit the request of the initiating UE, the third condition determination may be determined to be false. Also, when the target UE that the initiating UE connects to and / or a device in the target UE supports the function requested by the initiating UE, the third condition determination may be determined to be true, and when the function requested by the initiating UE is not supported, the third condition determination may be determined to be false. Also, when the transmitted and received identification information is permitted, the third condition determination may be determined to be true, and when the transmitted and received identification information is not permitted, the third condition determination may be determined to be false.

[0404] Note that the conditions for determining the truth or falsehood of the third condition determination do not have to be limited to the conditions described above.

[0405] Next, each step of the procedure in FIG. 10(A) will be described.

[0406] Based on the reception of the first control message, the target UE transmits a second control message to the initiating UE (S2002).

[0407] Here, the second control message may be a message for accepting the establishment of direct C2 communication. Also, the second control message may be a ProSe direct link establishment accept message. Also, the second control message may be a Direct Communication Accept message.

[0408] Also, the second control message may be a response message to the first control message. Also, the second control message may indicate that the first control message has been accepted.

[0409] Here, the target UE may include one or more pieces of identification information out of the 13th to 14th identification information in the second control message and transmit it.

[0410] Here, the target UE may indicate that at least a part of the request of the initiating UE by the first control message has been accepted by transmitting the second control message. Also, the target UE may indicate that at least a part of the request of the initiating UE by the first control message has been accepted by transmitting one or more pieces of identification information out of the 13th to 14th identification information.

[0411] In addition, the target UE may indicate that the target UE supports each function, or indicate that the request of the initiating UE has been accepted, or indicate that the request from the initiating UE is not permitted, or indicate the combined information by transmitting these identification information and / or the second control message. Further, when a plurality of identification information is transmitted and received, two or more pieces of these identification information may be configured as one or more pieces of identification information. In addition, the information indicating the support of each function and the information indicating the request for the use of each function may be transmitted and received as the same identification information or as different identification information.

[0412] In addition, the target UE may make a decision on which identification information to include in the second control message based on each received identification information, and / or subscriber information, and / or network capability information, and / or UE policy, and / or operator policy, and / or network state, and / or user registration information, and / or the context held by the target UE, etc.

[0413] Next, the initiating UE receives the second control message from the target UE.

[0414] When the initiating UE receives the second control message, it can recognize that the request of the UE by the first control message has been accepted and / or the content of information etc. (message, container, identification information) included in the second control message.

[0415] Next, each step of the procedure in FIG. 10(B) will be described.

[0416] First, based on the reception of the first control message, the target UE transmits a third control message to the initiating UE (S2004).

[0417] Here, the third control message may be a message that rejects the establishment of direct C2 communication. Also, the third control message may be a ProSe direct link establishment reject message. Also, the third control message may be a Direct Communication Reject message.

[0418] Also, the third control message may be a response message to the first control message. Also, the third control message may indicate that the establishment of direct C2 communication has been rejected.

[0419] Here, by transmitting the third control message, the target UE may indicate that the request of the initiating UE by the first control message has been rejected.

[0420] Note that by transmitting the third control message, the target UE may indicate that the request of the initiating UE has been rejected, or may indicate that the request from the initiating UE has not been permitted, or may indicate a combination of these.

[0421] Here, the target UE may include, in the third control message, one or more pieces of identification information out of the identification information from the 13th to the 14th.

[0422] In addition, the target UE may determine which identification information to include in the third control message based on each received piece of identification information, and / or subscriber information, and / or network capability information, and / or UE policy, and / or operator policy, and / or network state, and / or user registration information, and / or context held by the target UE, etc.

[0423] Next, the initiating UE receives the third control message (S2004). When the initiating UE receives the third control message, it can recognize that the request of the initiating UE by the first control message has been rejected, and / or the content of information (message, container, identification information) included in the third control message.

[0424] Each device may complete this procedure based on the transmission and reception of the second control message. Each device may establish a communication path for direct C2 communication based on the completion of this procedure. At this time, each device may transition to a communicable state between the initiating UE and the target UE using the established direct C2 communication.

[0425] In addition, each device may complete this procedure based on the transmission and reception of the third control message. At this time, since each device cannot establish direct C2 communication, if there is no already established direct C2 communication, communication between the initiating UE and the target UE is not possible.

[0426] Note that each process executed by the initiating UE shown above based on the reception of each identification information may be executed during this procedure or after the completion of this procedure, or may be executed based on the completion of this procedure after the completion of this procedure.

[0427] Based on the completion of this procedure, the initiating UE and the target UE that have established direct C2 communication may start exchanging information using direct C2 communication.

[0428] [3.2.6. Procedure for Releasing Direct C2 Communication] Next, the behavior of each device when the UE executes the procedure for releasing direct C2 communication will be described with reference to FIG. 11. Hereinafter, the procedure for releasing direct C2 communication may be referred to as this procedure. Also, the procedure for releasing direct C2 communication may be referred to as the direct C2 communication release procedure.

[0429] Note that this procedure may be executed after executing the registration procedure, and / or the PDU session establishment procedure, and / or the network-initiated session management procedure, and / or the UE-initiated session management procedure one or more times. Also, this procedure may be executed during the registration procedure, or the PDU session establishment procedure, or the network-initiated session management procedure, or the UE-initiated session management procedure.

[0430] This procedure may be executed when the UE has its authentication and / or authorization for direct C2 communication revoked by the network in a registration procedure, and / or a PDU session establishment procedure, and / or a network-initiated session management procedure, and / or a UE-initiated session management procedure. In other words, the UE may start this procedure when receiving the identification information from 10 to 12, 15 to 18. Also, the UE may start this procedure regardless of the cancellation of direct C2 communication from the network.

[0431] In addition, in this procedure, there may be an initiating UE and a target UE in the UE.

[0432] Also, this procedure may be executed when the UE receives an indication of radio link failure or an indication of release of the PC5-RRC connection from the lower layer.

[0433] Also, this procedure may be executed when the initiating UE receives a request from the upper layer to release the 5G ProSe direct link. Also, this procedure may be executed when the initiating UE receives a request from the upper layer to release the communication path of direct C2 communication.

[0434] Also, this procedure may be executed when the target UE is in a non-responsive state.

[0435] Also, this procedure may be executed when the initiating UE reaches the maximum number of established 5G ProSe direct links and / or needs to establish a new 5G ProSe direct link. Also, this procedure may be executed when the initiating UE reaches the maximum number of communication paths of established direct C2 communication and / or needs to establish a new 5G ProSe direct link.

[0436] Also, this procedure may be executed when the initiating UE is operating as a 5G ProSe layer-3 UE-to-network relay UE and / or when the PDU session is released by the initiating UE or the network.

[0437] Also, this procedure may be executed when the initiating UE is operating as a 5G ProSe layer-2 remote UE or a 5G ProSe layer-3 remote UE and / or when the initiating UE is in 5GMM-IDLE mode.

[0438] Also, this procedure may be executed when the initiating UE is operating as a 5G ProSe layer-2 remote UE or a 5G ProSe layer-3 remote UE or a 5G ProSe layer-2 UE-to-network relay UE and / or when the service approval of the initiating UE is cancelled after receiving configuration parameters.

[0439] Also, this procedure may be executed when the initiating UE is operating as a 5G ProSe layer-3 UE-to-network relay UE and / or when the service approval of the initiating UE is cancelled after receiving configuration parameters.

[0440] Note that the 5G ProSe layer-2 UE-to-network relay UE may be a UE capable of using 5G ProSe or direct C2 communication that provides a function to support the connectivity to the network for the 5G ProSe layer-2 remote UE via the layer 2 protocol.

[0441] Also, a 5G ProSe layer-3 UE-to-network relay UE may be a UE capable of using 5G ProSe or direct C2 communication that provides a function to support connectivity to the network for a 5G ProSe layer-3 remote UE via a layer 3 protocol.

[0442] Also, a 5G ProSe layer-2 remote UE may be a UE capable of using 5G ProSe or direct C2 communication that communicates with a DN via a 5G ProSe layer-2 UE-to-network relay UE.

[0443] Also, a 5G ProSe layer-3 remote UE may be a UE capable of using 5G ProSe or direct C2 communication that communicates with a DN via a 5G ProSe layer-3 UE-to-network relay UE.

[0444] In addition, in this procedure, the initiating UE and the target UE may transmit and receive each control message on PC5.

[0445] First, the initiating UE transmits a first control message to the target UE (S2200) to start this procedure.

[0446] Here, the first control message may be a message requesting the release of direct C2 communication. Also, the first control message may be a ProSe direct link release request message.

[0447] Here, the initiating UE may include the sixth identification information in the first control message and transmit it. Also, the initiating UE may transmit the sixth identification information together with the first control message.

[0448] Here, the initiating UE may indicate the content of the identification information to the network by transmitting a first control message. Also, the initiating UE may indicate the content of the identification information to the network by transmitting sixth identification information.

[0449] In addition, the initiating UE may select and determine whether to include the sixth identification information in the first control message based on subscriber information, and / or network status, and / or user registration information, and / or the context held by the UE, etc.

[0450] In addition, the UE may also include and transmit identification information other than the sixth identification information in the first control message.

[0451] Also, the initiating UE may request the release of direct C2 communication with the target UE by transmitting the first control message. Also, the initiating UE may request the release of direct C2 communication with the target UE by transmitting the sixth identification information.

[0452] Next, the target UE receives the first control message from the initiating UE.

[0453] When the target UE receives the first control message, it may recognize the content requested by the initiating UE and / or the content of the information (message, container, identification information) included in the first control message.

[0454] Next, based on the reception of the first control message, the target UE transmits a second control message to the initiating UE (S2202).

[0455] Here, the second control message may be a message that accepts the release of direct C2 communication. Also, the second control message may be a ProSe direct link release accept message.

[0456] Also, the second control message may be a response message to the first control message. Also, the second control message may indicate that the first control message has been accepted.

[0457] Here, the target UE may indicate that at least a part of the request of the initiating UE by the first control message has been accepted by transmitting the second control message.

[0458] Note that the target UE may indicate that the target UE supports each function, or that the request of the initiating UE has been accepted, or that the request from the initiating UE is not permitted, or a combination of these by transmitting the second control message.

[0459] Next, the initiating UE receives the second control message from the target UE.

[0460] When the initiating UE receives the second control message, it can recognize that the request of the UE by the first control message has been accepted and / or the content of the information (message, container, identification information) included in the second control message.

[0461] Each device may complete this procedure based on the transmission and reception of the second control message. Each device may release the communication path for direct C2 communication based on the completion of this procedure. At this time, each device may transition to a state where communication is impossible between the initiating UE and the target UE.

[0462] [3.2.7. UUAA] Next, the overview of the UUAA (USS UAV Authorization / Authentication) procedure will be described. Hereinafter, the UUAA procedure may also be referred to as UUAA or this procedure.

[0463] This procedure is a procedure for the authentication and / or authorization of the UE by the USS. In addition, the authorization for C2 communication (Authorization for C2) may be performed during the UUAA procedure.

[0464] In addition, this procedure may be initiated by the network or by the UE.

[0465] Also, UUAA may be the UUAA-MM procedure performed during registration to 5GS. Also, UUAA may be the UUAA-SM procedure performed during PDU session establishment. Also, UUAA may be an MM procedure or an SM procedure. Also, the procedure used in UUAA may be an MM procedure or an SM procedure.

[0466] Also, if UUAA-MM is not performed, UUAA-SM may be performed.

[0467] Also, the PDU session for the UAS service may be established only after the UAV is authenticated and authorized by the USS. This behavior may be performed during UUAA-MM or during UUAA-SM.

[0468] In addition, the success of UUAA may be read as the authentication and authorization of the UAV being permitted. Also, the failure of UUAA may be read as the authentication and authorization of the UAV not being permitted.

[0469] Also, "the authentication and authorization of the UAV are permitted" may be read as "the UAV is authenticated and authorized". Also, "the authentication and authorization of the UAV are not permitted" may be read as "the UAV is not authenticated and authorized".

[0470] Also, "the authentication and authorization of the UAV are successful" may be read as "the UAV is authenticated and authorized". Also, "the authentication and authorization of the UAV fail" may be read as "the UAV is not authenticated and authorized".

[0471] Also, "the authentication and authorization of the USS are permitted" may be read as "the UAV is authenticated and authorized". Also, "the authentication and authorization of the USS are not permitted" may be read as "the UAV is not authenticated and authorized".

[0472] [3.2.7.1. UUAA-MM] Next, the UUAA-MM procedure will be described with reference to FIG. 12. Hereinafter, the UUAA-MM procedure may also be referred to as UUAA-MM or this procedure. This procedure may be a procedure performed at the time of registration with the 5GS.

[0473] The UUAA-MM procedure may be executed during the registration procedure with the 5GS or after the registration procedure with the 5GS. In other words, the first communication in the UUAA-MM procedure described below and the aforementioned registration procedure may be collectively referred to as the registration procedure, or the first communication in the UUAA-MM procedure described below may be an independent procedure from the aforementioned registration procedure.

[0474] Also, UUAA-MM may be performed upon registration to 5GS based on the operator policy. Also, when requested by the operator and / or when the UE has an aerial UE subscription within the Access and Mobility Subscription Data and provides the CAA-Level UAV ID in the registration request message, UUAA-MM may be performed. Also, when UUAA-MM is not performed, the UE may be authenticated and / or authorized in the PDU session establishment in UUAA-SM.

[0475] Also, UUAA-MM may be optional. Also, UUAA-MM may be performed for a UE that requests authentication and authorization of the UAV by the USS when registering to 5GS. Also, UUAA-MM may be performed by the AMF. Also, when the UE has an aerial UE subscription in 5GS and the UE provides the CAA-Level UAV ID of the UAV in the registration request message, UUAA-MM may be performed while the UE is registered based on the local network policy. Also, UUAA-MM may be performed when the USS that has authenticated the UAV performs re-authentication.

[0476] Also, the UE may be authenticated and authorized by the USS using the CAA-Level UAV ID and the credentials associated with the CAA-Level UAV ID. Also, while UUAA-MM is being performed, the AMF may communicate with the USS via the UAS NF and transfer the authentication messages between the UE and the UAS NF.

[0477] Next, each step of UUAA-MM will be described.

[0478] First, the UE performs the registration procedure (S2400).

[0479] Next, a first communication is performed between the UE, the AMF, and the USS (S2402). In the first communication, messages for authentication and authorization used by the USS may be transmitted and received between the UE, the AMF, and the USS.

[0480] Here, the UE and / or the AMF may recognize whether the UUAA-MM has succeeded based on the messages of the first communication. In other words, the UE and / or the AMF may recognize whether the authentication and authorization of the UAV have been permitted based on the messages of the first communication.

[0481] Next, the AMF can perform a fifth condition determination. The fifth condition determination is for the network (or the AMF) to determine whether the UUAA-MM has succeeded. If the fifth condition determination is true, the AMF may start the UE configuration update procedure in (A) of FIG. 12 (S2404). Also, if the fifth condition determination is false, the AMF may start the deregistration procedure in (B) of FIG. 12 (S2406).

[0482] Note that the fifth condition determination may be performed based on the reception of the messages used in the first communication, and / or subscriber information, and / or network capability information, and / or operator policy, and / or network status, and / or user registration information, and / or the context held by the AMF, etc.

[0483] For example, if the UUAA-MM has succeeded, the fifth condition determination may be true, and if the UUAA-MM has failed, the fifth condition determination may be false. Further, if the transmitted and received identification information is permitted, the fifth condition determination may be true, and if the transmitted and received identification information is not permitted, the fifth condition determination may be false. Note that the conditions for determining the truth or falsehood of the fifth condition determination may not be limited to the conditions described above.

[0484] Also, the AMF may indicate the result of the UUAA-MM to the UE according to the procedure performed based on the truth or falsehood of the fifth condition determination.

[0485] Also, each device may complete this procedure based on the implementation of the first communication, and / or UE configuration update procedure, and / or deregistration procedure.

[0486] Also, the UE may recognize the result of UUAA-MM by the procedure of (A) or (B) in FIG. 12. In other words, the UE may recognize the result of UUAA-MM by the message received in the procedure of (A) or (B) in FIG. 12. Also, the UE may recognize the result of UUAA-MM based on the completion of this procedure.

[0487] In addition, when the approval of C2 communication is executed during the UUAA-MM procedure, the UE may recognize the approval of C2 communication and / or the pairing of the UAV and UAV-C, and / or the result of the approval of the UAV flight.

[0488] During the execution of the UUAA-MM procedure, the UE may be prohibited from transmitting MM messages and / or SM messages. In other words, the UE may be controlled not to transmit MM messages and / or SM messages until the first communication, and / or UE configuration update procedure, and / or deregistration procedure is completed.

[0489] [3.2.7.2. UUAA-SM] Next, the UUAA-SM procedure will be described with reference to FIG. 13. Hereinafter, the UUAA-SM procedure may also be referred to as UUAA-SM or this procedure. This procedure may be a procedure performed during PDU session establishment.

[0490] Note that the messages transmitted and received in this procedure may have the same behavior as described in the chapter of the PDU session establishment procedure.

[0491] Also, when the UE requests the establishment of a PDU session, the PDU session may request the UUAA authentication of the UAV.

[0492] Also, when UUAA is cancelled, the PDU sessions related to all UAVs may be released. In other words, when the authentication and authorization of UAVs are cancelled, the PDU sessions related to all UAVs may be released.

[0493] Also, UUAA-SM may be performed by the SMF during the PDU session establishment procedure. Also, based on the SM subscription data obtained from the UDM and based on the service level device ID provided by the UE in the PDU session establishment request message, UUAA-SM may be performed.

[0494] Next, each step of UUAA-SM will be described.

[0495] First, the UE performs the PDU session establishment procedure. Specifically, the UE sends a PDU session establishment request message to the SMF (S2600).

[0496] Next, a second communication is performed between the UE, the SMF, and the USS (S2602). In the second communication, messages for authentication and authorization used by the USS may be transmitted and received between the UE, the SMF, and the USS.

[0497] Here, the UE and / or the SMF may recognize whether UUAA-SM has succeeded based on the message of the second communication. In other words, the UE and / or the SMF may recognize whether the authentication and authorization of the UAV have been permitted based on the message of the second communication.

[0498] Next, the SMF can perform the sixth condition determination. The sixth condition determination is for the network (or the SMF) to determine whether UUAA-SM has succeeded. When the sixth condition determination is true, the SMF sends the PDU session establishment acceptance message in (A) of FIG. 13 (S2604), whereas when the sixth condition determination is false, the SMF sends the PDU session establishment rejection message in (B) of FIG. 13 (S2606).

[0499] Further, the sixth condition determination may be executed based on reception of a message used in the second communication, and / or subscriber information, and / or network capability information, and / or operator policy, and / or network state, and / or user registration information, and / or context held by the AMF, etc.

[0500] For example, when UUAA-SM is successful, the sixth condition determination may be true, and when UUAA-SM fails, the sixth condition determination may be false. Further, when the transmitted and received identification information is permitted, the sixth condition determination may be true, and when the transmitted and received identification information is not permitted, the sixth condition determination may be false. Note that the conditions for determining the truth or falsehood of the sixth condition determination may not be limited to the conditions described above.

[0501] Also, the SMF may indicate the result of UUAA-SM to the UE by a message transmitted according to the truth or falsehood of the sixth condition determination.

[0502] Also, each device may complete this procedure based on execution of the second communication, and / or transmission and reception of a PDU session acceptance message, and / or transmission and reception of a PDU session rejection message.

[0503] Also, the UE may recognize the result of UUAA-SM by receiving the message of (A) or (B) in FIG. 13. Also, the UE may recognize the result of UUAA-SM based on completion of this procedure.

[0504] Note that when approval of C2 communication is executed during the UUAA-SM procedure, the UE may recognize the result of approval of C2 communication and / or pairing of the UAV and UAV-C, and / or flight of the UAV.

[0505] During the execution of the UUAA-SM procedure, the UE may be prohibited from sending MM messages and / or SM messages. In other words, the UE may be controlled not to send MM messages and / or SM messages until the second communication and / or the PDU session establishment procedure is completed.

[0506] [3.2.7.3. UUAA Cancellation Procedure] Next, the UUAA cancellation procedure (UUAA Revocation procedure) will be described with reference to FIG. 14. Hereinafter, the UUAA cancellation procedure is also referred to as the UUAA Revocation, or the UAV authorization revocation procedure, or this procedure. This procedure may be a procedure performed during the registration procedure and / or during the PDU session establishment.

[0507] Also, this procedure may be a procedure initiated by the core network or the USS. Also, this procedure may be a procedure for the network or the USS to cancel the authentication and authorization of the UAV for the UE.

[0508] Next, each step of this procedure will be described.

[0509] First, a fourth communication is performed between the core network and the USS (S2800). In the fourth communication, a message for requesting the cancellation of the UAV may be transmitted and received between the core network and the USS.

[0510] Next, the core network may start the procedure of (A) in FIG. 14 (S2802)(S2804), or may start the procedure of (B) in FIG. 14 (S2806).

[0511] The core network may also determine whether to perform the procedure of FIG. 14(A) or the procedure of FIG. 14(B) based on, for example, the reception of messages used in the first communication, and / or subscriber information, and / or network capability information, and / or operator policies, and / or network status, and / or user registration information, and / or the context held by the AMF, etc.

[0512] For example, if UUAA-MM is being performed, the procedure of FIG. 14(A) may be performed. Also, if UUAA-SM is being performed, the procedure of FIG. 14(B) may be performed. Note that the determination of whether to perform either FIG. 14(A) or (B) is not limited to the above-mentioned conditions.

[0513] In addition, the core network may indicate to the UE the cancellation of UAV authentication and authorization by performing the procedure of FIG. 14(A) or (B).

[0514] In addition, each device may complete this procedure based on the fourth communication and / or the performance of the procedure of FIG. 14(A) or (B).

[0515] In addition, the UE may recognize the cancellation of UAV authentication and authorization based on the completion of this procedure.

[0516] [4. Embodiments] Next, each embodiment will be described.

[0517] [4.1. First Embodiment] First, the first embodiment will be described. Hereinafter, the first embodiment may also be referred to as this embodiment.

[0518] In this embodiment, a PDU session modification procedure or a PDU session release procedure may be performed.

[0519] In this embodiment, the first control message may be a PDU session change command message or a PDU session release command message.

[0520] Also, in this embodiment, the UAV or UAV-C may be read as the UE. Also, the UE may be read as the UAV or UAV-C. Also, each device may be the UAV and / or UAV-C and / or the network.

[0521] Also, in this embodiment, the UAV may be read as the UAV-C, or the UAV-C may be read as the UAV.

[0522] Also, this embodiment may be supported in 5GS and / or EPS.

[0523] Also, in this embodiment, UUAA-MM and / or UUAA-SM may already have been implemented once. Also, this embodiment may be implemented during UUAA-MM, or UUAA-SM, or the UUAA cancellation procedure.

[0524] Also, in this embodiment, the UAV may or may not have established a PDU session for C2 communication with the UAV-C and / or USS and / or the network.

[0525] Also, in this embodiment, the UAV has established a communication path for direct C2 communication with the UAV-C.

[0526] First, the network sends a first control message to the UAV. Also, the network may send one or more pieces of identification information from among the identification information of 10 to 12 and 15 to 18 to the UAV. Here, the network may include one or more pieces of identification information from among the identification information of 10 to 12 and 15 to 18 in the first control message.

[0527] Here, the network may indicate to the UAV the content indicated by the identification information included in the first control message by including one or more pieces of identification information among the identification information from 10 to 12 and from 15 to 18 in the first control message. Further, the network may permit the UAV the content indicated by the identification information included in the first control message by including one or more pieces of identification information among the identification information from 10 to 12 and from 15 to 18 in the first control message. Also, the network may indicate to the UAV the content indicated by each piece of identification information by transmitting one or more pieces of identification information among the identification information from 10 to 12 and from 15 to 18 to the UAV.

[0528] Specifically, the network may indicate to the UAV to cancel the authentication and / or approval of direct C2 communication by transmitting the 15th piece of identification information.

[0529] Also, the network may indicate to the UAV to cancel the authentication and / or approval of direct C2 communication and / or C2 communication using a PDU session by transmitting the 16th piece of identification information. Also, the network may transmit the 15th piece of identification information and / or the 16th piece of identification information to the UAV included in a Service-level-AA container.

[0530] Also, the network may indicate to the UAV the reason for canceling the authentication and / or approval of direct C2 communication and / or C2 communication using a PDU session by transmitting the 17th piece of identification information.

[0531] Also, the network may indicate to the UAV a timer value indicating the grace period until releasing direct C2 communication and / or the PDU session for C2 communication by transmitting the 18th piece of identification information.

[0532] In addition, the network may indicate to the UAV the content of each identification information included in the first control message by transmitting the first control message.

[0533] In addition, the network may indicate to the UAV the content of each identification information by transmitting each identification information.

[0534] Note that the network may select and determine whether to include one or more pieces of identification information among the identification information from 10 to 12 and from 15 to 18 in the first control message based on the state of the UAV, and / or the information received from the USS, and / or the information received from the UAS-NF, etc.

[0535] In addition, the network may determine whether to transmit the first control message and / or each identification information based on the state of the UAV, and / or the information received from the USS, and / or the information received from the UAS-NF, etc. Also, when the network receives information indicating that it cancels the authentication and / or approval of direct C2 communication and / or C2 communication using a PDU session from the USS or UAS-NF, the network may transmit the first control message and / or each identification information.

[0536] Next, the UAV receives the first control message. Also, the UAV may receive the first control message including one or more pieces of identification information among the identification information from 10 to 12 and from 15 to 18 from the network. Also, the UAV may receive one or more pieces of identification information among the identification information from 10 to 12 and from 15 to 18 from the network.

[0537] Furthermore, the UAV may store the identification information received together with the first control message based on the reception of the first control message, or may recognize the decision of the network.

[0538] Furthermore, when the UAV receives one or more pieces of identification information from among the identification information of numbers 10 to 12 and 15 to 18, the UAV may recognize the content indicated by the received identification information. Furthermore, when the UAV receives one or more pieces of identification information from among the identification information of numbers 10 to 12 and 15 to 18, the UAV may recognize that the content indicated by the identification information included in the first control message has been permitted.

[0539] Here, when the UAV receives the identification information of number 10, the UAV may start the procedure for establishing direct C2 communication. In other words, when the UAV receives the identification information of number 10, the UAV may recognize that the direct C2 communication has been authenticated and / or approved, and start the procedure for establishing direct C2 communication.

[0540] Also, when the UAV receives the identification information of number 10, the UAV may not start the procedure for establishing direct C2 communication. In other words, when the UAV receives the identification information of number 10, the UAV may recognize that the direct C2 communication has not been authenticated and / or approved, and may not start the procedure for establishing direct C2 communication.

[0541] Also, when the UAV receives the identification information of number 11, the UAV may start the procedure for establishing direct C2 communication and / or the procedure for establishing a PDU session for C2 communication. In other words, when the UAV receives the identification information of number 11, the UAV may recognize that the direct C2 communication and / or the C2 communication using the PDU session has been authenticated and / or approved, and may start the procedure for establishing direct C2 communication and / or the procedure for establishing a PDU session for C2 communication.

[0542] Also, when the UAV receives the 11th identification information, it may not start the procedure for establishing direct C2 communication and / or the procedure for establishing a PDU session for C2 communication. In other words, when the UAV receives the 11th identification information, it recognizes that the direct C2 communication and / or the C2 communication using the PDU session has not been authenticated and / or approved, and may not start the procedure for establishing direct C2 communication and / or the procedure for establishing a PDU session for C2 communication.

[0543] Also, when the UAV receives the 12th identification information, it may set the identification information of the UAV or UAV-C. Also, when the UAV receives the 12th identification information, it may delete the stored identification information of the UAV or UAV-C and store the received identification information of the UAV or UAV-C.

[0544] Also, when the UAV receives the 15th identification information, it may recognize that the authentication and / or approval of the direct C2 communication has been cancelled. Also, when the UAV receives the 1st control message, it may recognize that the authentication and / or approval of the direct C2 communication has been cancelled.

[0545] Also, when the UAV receives the 15th identification information, it may start the release procedure for the direct C2 communication. In other words, when the UAV receives the 15th identification information, it recognizes that the authentication and / or approval of the direct C2 communication has been cancelled, and may start the release procedure for the direct C2 communication.

[0546] Also, when the UAV receives the 16th identification information, it may recognize that the authentication and / or authorization of direct C2 communication and / or C2 communication using the PDU session have been cancelled. Also, when the UAV receives the 1st control message, it may recognize that the authentication and / or authorization of direct C2 communication and / or C2 communication using the PDU session have been cancelled.

[0547] Also, when the UAV receives the 16th identification information, it may initiate the release procedure for direct C2 communication and / or the PDU session release procedure for C2 communication. In other words, when the UAV receives the 16th identification information, it may recognize that the authentication and / or authorization of direct C2 communication and / or C2 communication using the PDU session have been cancelled, and may initiate the release procedure for direct C2 communication and / or the PDU session release procedure for C2 communication.

[0548] Also, when the UAV receives the 17th identification information, it may recognize the reason why the authentication and / or authorization of direct C2 communication and / or C2 communication using the PDU session have been cancelled. Also, when the UAV receives the 1st control message, it may recognize the reason why the authentication and / or authorization of direct C2 communication and / or C2 communication using the PDU session have been cancelled.

[0549] Also, when the UAV receives the 18th identification information, it may recognize a timer value indicating a grace period until the release of the direct C2 communication and / or the PDU session for C2 communication. Also, when the UAV receives the 18th identification information, it may start the first timer using the timer value indicated by the 18th identification information. Further, when the first timer expires, the UAV may start the procedure for releasing the communication path for direct C2 communication. Also, during the period until the first timer expires, the UAV may start the procedure for releasing the communication path for direct C2 communication.

[0550] Here, the first timer may be a timer for managing the grace period until the release of the direct C2 communication and / or the PDU session for C2 communication. Also, the first timer may be a timer for managing the time for releasing the direct C2 communication and / or the PDU session for C2 communication. Also, the first timer may be a timer for managing the timer value indicated by the 18th identification information.

[0551] Also, when the UAV receives the first control message, it may recognize that the authentication and / or authorization of direct C2 communication has been canceled. Also, when the UAV receives the first control message, it may start the first timer using the timer value indicated by the 18th identification information. Further, when the first timer expires, the UAV may start the procedure for releasing the communication path for direct C2 communication. Also, before the first timer expires, the UAV may start the procedure for releasing the communication path for direct C2 communication. Also, when the UAV receives the first control message, it may start the procedure for releasing the communication path for direct C2 communication. Also, when the UAV receives the first control message, it may start the procedure for releasing the communication path for direct C2 communication and recognize that the authentication and / or authorization of direct C2 communication has been canceled.

[0552] Note that the above behavior of the UAV may be performed after receiving the first control message. Also, the above behavior of the UAV may be performed after receiving one or more pieces of identification information among the 10th to 12th and 15th to 18th identification information.

[0553] Also, when the UAV receives the first control message, it may recognize the content of each piece of identification information included in the first control message, or may perform the behavior when each piece of identification information is received.

[0554] Also, when the UAV receives each piece of identification information, it may recognize the content of each piece of identification information.

[0555] [4. Variation Example] A program that operates on an apparatus according to an aspect of the present invention may be a program that controls a Central Processing Unit (CPU) or the like to make a computer function so as to realize the functions of an embodiment according to an aspect of the present invention. The program or the information handled by the program is temporarily stored in a volatile memory such as a Random Access Memory (RAM), a non-volatile memory such as a flash memory, a Hard Disk Drive (HDD), or other storage device systems.

[0556] In addition, a program for realizing the functions of an embodiment according to an aspect of the present invention may be recorded on a computer-readable recording medium. The functions may be realized by causing a computer system to read and execute the program recorded on this recording medium. Here, the "computer system" refers to a computer system built in an apparatus and including hardware such as an operating system and peripheral devices. Further, the "computer-readable recording medium" may be a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a medium that temporarily holds a program, or other recording media readable by a computer.

[0557] Furthermore, each functional block or various features of the apparatus used in the above-described embodiments can be implemented or executed by an electric circuit, for example, an integrated circuit or a plurality of integrated circuits. The electric circuit designed to execute the functions described in this specification may include a general-purpose use processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices, discrete gates or transistor logic, discrete hardware components, or a combination thereof. The general-purpose use processor may be a microprocessor, or a conventional type processor, controller, microcontroller, or state machine. The aforementioned electric circuit may be composed of a digital circuit or an analog circuit. Also, when an integrated circuit technology that replaces current integrated circuits appears due to the progress of semiconductor technology, one or more aspects of the present invention can also use a new integrated circuit based on such technology.

[0558] Note that the invention of the present application is not limited to the above-described embodiments. In the embodiments, an example of the apparatus has been described, but the invention of the present application is not limited thereto, and it can be applied to stationary or non-mobile electronic devices installed indoors and outdoors, for example, terminal devices or communication devices such as AV devices, kitchen devices, cleaning and washing devices, air conditioning devices, office devices, vending machines, and other household appliances.

[0559] As described above, the embodiments of this invention have been described in detail with reference to the drawings. However, the specific configuration is not limited to this embodiment, and design changes and the like within the scope not departing from the gist of this invention are also included. Also, the present invention can be variously modified within the scope shown in the claims, and embodiments obtained by appropriately combining the technical means disclosed in different embodiments are also included in the technical scope of the present invention. Also, a configuration in which elements described in the above embodiments and having the same effects are substituted for each other is included.

Description of Reference Numerals

[0560] 1 Mobile communication system 10 UE_A 30 PGW-U 32 PGW-C 35 SGW 40 MME 45 eNB 50 HSS 60 PCRF 80 Access network_A (E-UTRAN) 90 Core network_A 120 Access network_B (5G AN) 122 gNB 130 UPF 132 SMF 140 AMF 150 UDM 160 PCF 190 Core network_B 235 UPF_A 239 UPF_C

Claims

1. A User Equipment (UE), wherein the UE comprises a transceiver and a control unit, the UE has established a communication path for a first direct C2 communication with a UAV-C, the transceiver receives, from a network, a PDU session change command message including first identification information, the first identification information is information indicating cancellation of authentication and / or authorization of the communication path for the first direct C2 communication, the control unit, based on the reception of the PDU session change command message, recognizes that the authentication and / or authorization of the communication path for the first direct C2 communication has been cancelled, and starts a release procedure for the communication path for the first direct C2 communication. The UE is characterized by this.

2. The transceiver receives, from a network, a PDU session change command message including second identification information, the second identification information is a timer value indicating a grace period until the communication path for the first direct C2 communication is released, and the control unit, based on the reception of the PDU session change command message, starts a timer using the timer value, and when the timer expires, starts a release procedure for the communication path for the first direct C2 communication. The UE according to Claim 1 is characterized by this.

Images