User equipment

Abstract

To solve a problem in which progress is being made in standardizing communications between UEs operating as UAVs (Uncrewed Aerial Vehicles), UAV controllers, and AAMs (Area Airspace Managers) using the 5GS (5G System), the communication procedures and behavior between UE (User Equipment) operating as UAVs, UAV-C, and AAMs when the UAV does not support the DAA (Detect And Avoid) function has not been clarified.SOLUTION: UE operating as AAM includes means that receives information regarding DAA support for a UAV transmitted from the UAV or a network, and a method that performs appropriate processing regarding the establishment of a direct communication path for a DAA with the UAV on the basis of the reception of the information.SELECTED DRAWING: Figure 15

Description

[Technical field]

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

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

[0003] [Non-Patent Document 1] 3GPP TS 23.501 V18.0.0 (2022-12); 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System architecture for the 5G System (5GS); Stage 2 (Release 18) [Non-Patent Document 2] 3GPP TS 23.502 V18.0.0 (2022-12); 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for the 5G System (5GS); Stage 2 (Release 18) [Non-Patent Document 3] 3GPP TS 24.501 V18.0.1 (2022-09); 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 (Release 18) [Non-Patent Document 4] 3GPP TS 23.256 (Release 18); 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Support of Uncrewed Aerial Systems (UAS) connectivity, identification and tracking; Stage 2 (Release 17) [Non-Patent Document 5] 3GPP TS 24.587 V17.7.0 (2022-09); 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Vehicle-to-Everything (V2X) services in 5G System (5GS); Stage 3 (Release 17) [Non-Patent Document 6] 3GPP TR 23.700-58 V18.0.0 (2022-12); 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study of further architecture enhancements for uncrewed aerial systems and urban air mobility (Release 18) [Non-Patent Document 7] 3GPP TS 23.304 V18.0.0 (2022-12); 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Proximity based Services (ProSe) in the 5G System (5GS) (Release 18) [Non-Patent Document 8] 3GPP TS 24.554 V17.2.1 (2022-09); 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Proximity-services (ProSe) in 5G System (5GS) protocol aspects; Stage 3 (Release 17) [Non-Patent Document 9] 3GPP TS 23.247 V18.0.0 (2022-12); 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Architectural enhancements for 5G multicast-broadcast services; Stage 2 (Release 18) Summary of the Invention [Problem to be solved by the invention]

[0004] In order to provide a wide variety of services in the 5GS (5G System), a new core network, the 5GCN (5G Core Network), is being considered. Furthermore, communication methods using 5GS are being considered as a means of communication for operating UAVs (Uncrewed Aerial Vehicles, or Unmanned Aerial Vehicles).

[0005] Currently, in addition to communication using 5CN, direct communication for C2 or other purposes via PC5 (also called direct C2 communication, etc.), and new functions such as broadcasting of UAV ID and collision detection and avoidance (DAA; Detect And Avoid) function using direct communication are being considered as a means of communication between UAV, UAV controller, and related equipment and servers (USS / UTM). Furthermore, in the DAA function, UE (User Equipment) (also called AAM) that operates as AAM (Area Airspace Manager) installed on the ground to establish a communication path (also called a direct communication path) for direct communication with UAV and transmit and receive information required for the DAA function is also being considered.

[0006] On the other hand, when a UAV does not support the new DAA function, the procedures for direct communication between the UAV and the UE acting as an AAM, and for communication between each terminal and the network, the information sent and received in these communication procedures, and the behavior and processing of each terminal are not clear.

[0007] One aspect of the present invention has been made in consideration of the above circumstances, and its purpose is to provide a means for a UE operating as an AAM to receive information regarding DAA support for a UAV transmitted from a UAV or a network, and a method for performing appropriate processing regarding establishing a direct communication path for DAA with the UAV based on the reception of the information. [Means for solving the problem]

[0008] A UE (User Equipment) according to one aspect of the present invention is a UE including a transceiver unit and a control unit, the transceiver unit receiving a message including first identification information from a network and / or a UAV (Uncrewed Aerial Vehicle), the first identification information being capability information indicating that the UAV does not support DAA (Detect And Avoid), and the control unit not initiating a procedure for establishing a communication path for direct communication with the UAV based on the reception of the first identification information.A UE (User Equipment) according to one aspect of the present invention is a UE including a transceiver unit and a control unit, the transceiver unit receiving a message including second identification information from a network and / or a UAV (Uncrewed Aerial Vehicle), the second identification information being capability information indicating that the UAV supports DAA (Detect And Avoid), and the control unit not initiating a procedure for establishing a communication path for direct communication with the UAV based on the reception of the second identification information. One embodiment of a UE (User Equipment) of the present invention is a UE having a transceiver unit and a control unit, wherein the transceiver unit receives a message including a third identification information from a network and / or a UAV (Uncrewed Aerial Vehicle), the third identification information being an ID of the UAV to be used for direct communication with the UAV, and the control unit recognizes that the UE supports the DAA (Detect And Avoid) based on the reception of the third identification information, and initiates a procedure for establishing a communication path for direct communication between the UE and the UAV by sending a message including the third identification information to the UAV. Effect of the Invention

[0009] According to one aspect of the present invention, a UE operating as an AAM can determine whether to establish a communication path for DAA with a UAV based on information indicating whether the UAV supports DAA functions, and can clarify the behavior based on that decision and the information to be transmitted and received in the procedure. [Brief description of the drawings]

[0010] [Figure 1] 1 is a diagram illustrating an overview of a mobile communication system (EPS / 5GS). [Diagram 2] A diagram explaining the detailed configuration of a mobile communication system (EPS / 5GS). [Diagram 3] A diagram explaining the device configuration of a UE. [Figure 4] A diagram explaining the configuration of an access network device (gNB) in 5GS. [Diagram 5] A diagram explaining the configuration of core network devices (AMF / SMF / UPF) in 5GS. [Figure 6] FIG. 1 is a diagram illustrating a registration procedure. [Figure 7] A diagram explaining the PDU session establishment procedure. [Figure 8] A diagram showing a network-initiated session management procedure. [Figure 9] A diagram showing a UE-initiated session management procedure. [Figure 10] FIG. 10 is a diagram illustrating a procedure for establishing a communication path for direct communication. [Figure 11] FIG. 13 is a diagram illustrating a procedure for releasing a communication path for direct communication. [Figure 12] A diagram explaining the UUAA-MM procedure. [Figure 13] A diagram explaining the UUAA-SM procedure. [Figure 14] A diagram explaining the UUAA cancellation procedure. [Figure 15] FIG. 1 is a diagram illustrating procedures related to DAA. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

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

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

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

[0014] In the following, these devices and functions may be described with abbreviated symbols, such as UE, access network_A, core network_A, PDN, access network_B, core network_B, DN, etc.

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

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

[0017] In addition, the 4G system EPS (Evolved Packet System) is configured to include an access network _A and a core network _A, but may further include a UE and / or a PDN. In addition, the 5G system 5GS (5G System) is configured to include a UE, an access network _B, and a core network _B, but may further include a DN.

[0018] The UE is a device that can connect to a network service via 3GPP access (also referred to as a 3GPP access network, 3GPP AN) and / or non-3GPP access (also referred to as a non-3GPP access network, 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 that can connect to both EPS and 5GS. The UE may include a Universal Integrated Circuit Card (UICC) or an Embedded UICC (eUICC). The UE may be expressed as a user device or a terminal device.

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

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

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

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

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

[0024] Moreover, the core network_A corresponds to an 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] Moreover, the core network_B corresponds to a 5G Core Network (5GCN). For example, an Access and Mobility Management Function (AMF), a User Plane Function (UPF), a Session Management Function (SMF), a Policy Control Function (PCF), and a Unified Data Management (UDM) are arranged in the 5GCN. Here, the 5GCN may be expressed as a 5GC.

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

[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 the access network (access network _A and / or access network _B) to the PDN and / or DN, or it may be a core network for a mobile network operator that operates and manages the mobile communication system 1, or it may be a core network for a virtual mobile communication operator such as an MVNO (Mobile Virtual Network Operator) or MVNE (Mobile Virtual Network Enabler) or a virtual mobile communication service provider.

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

[0029] In addition, in the following, at least a portion of the access network _A, the core network _A, the PDN, the access network _B, the core network _B, and the DN, and / or one or more devices included therein may be referred to as a network or a network device. In other words, when a network and / or a network device transmits or receives a message and / or executes a procedure, it means that at least a portion of the access network _A, the core network _A, the PDN, the access network _B, the core network _B, and the DN, and / or one or more devices included therein transmits or receives a message and / or executes a procedure.

[0030] The UE can also connect to an access network. The UE can also connect to a core network via the access network. The UE can also connect to a PDN or DN via the access network and the core network. That is, the UE can transmit and receive (communicate) user data between 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 refers to data communication using IP, and data is transmitted and received by IP packets. The IP packet is composed of an IP header and a payload section. The payload section may include data transmitted and received by devices and functions included in EPS and devices and functions included in 5GS. In addition, non-IP communication refers to 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 to which an IP header is not attached, or may be user data transmitted and received by a UE with another header such as a MAC header or an Ethernet (registered trademark) frame header attached.

[0032] In addition, the access network_A, the core network_A, the access network_B, the core network_B, the PDN_A, and the DN_A may be configured with devices not shown in Fig. 2. For example, the core network_A and / or the core network_B may include an AUSF (Authentication Server Function) and 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, the AUSF is a network function unit that receives an authentication request for 3GPP access and / or non-3GPP access from a UE and executes an authentication procedure.

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

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

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

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

[0038] Moreover, the UPF 130 may be the same device as the UPF_A 235. Note that the UPF 130 and the UPF_A 235 may be described with the symbol omitted, such as 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. Each device may be configured as physical hardware, may be configured as logical (virtual) hardware configured on general-purpose hardware, or may be configured as software. Furthermore, at least a part (including all) of the functions of each device may be configured as physical hardware, logical hardware, or software.

[0040] Each memory unit (memory unit_A340, memory unit_A440, memory unit_B540, memory unit_A640, memory unit_B740) in each device / function described below is composed of, for example, a semiconductor memory, a solid state drive (SSD), a hard disk drive (HDD), etc. Each memory unit can store not only information that was originally set at the time of shipment, but also various information transmitted and received between the device / function other than the device / function itself (for example, UE, and / or access network device, and / or core network device, and / or PDN, and / or DN). Each memory unit can store identification information, control information, flags, parameters, etc. included in control messages transmitted and received in various communication procedures described later. Each memory unit may store this information for each UE. Each memory unit can store control messages and user data transmitted and received between the device / function included in the 5GS and / or EPS when interworking is performed between the 5GS and 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. UE device configuration] First, an example of the device configuration of 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 memory unit _A340. The control unit _A300, the transceiver unit _A320, and the memory unit _A340 are connected via a bus. The transceiver unit _A320 is connected to the antenna 310.

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

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

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

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

[0046] [2.2. gNB device configuration] 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 memory unit _B540. The control unit _B500, the network connection unit _B520, the transceiver unit _B530, and the memory unit _B540 are connected via a bus. The transceiver unit _B530 is connected to the antenna 510.

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

[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 between the AMF and / or UPF using the network connection unit _B520.

[0049] The transceiver unit _B530 is a functional unit for wirelessly communicating with the UE via the antenna 510. That is, the gNB can transmit and receive user data and / or control information between the UE and the transceiver unit _B530.

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

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

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

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

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

[0055] Explaining in detail with reference to FIG. 2, the AMF in the 5GCN can communicate with the gNB via the N2 interface by using the network connection unit_A620, can communicate with the UDM via the N8 interface, can communicate with the SMF via the N11 interface, and can communicate with the PCF via the N15 interface. In addition, the AMF can transmit and receive NAS messages to and from the UE via the N1 interface by using the network connection unit_A620. However, since the N1 interface is logical, in reality, communication between the UE and the AMF is performed via the 5G AN. In addition, if 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 AMF.

[0057] In addition, the AMF has a function of exchanging control messages with the RAN using the N2 interface, a function of exchanging NAS messages with the UE using the N1 interface, a function of encrypting and protecting the integrity of NAS messages, a registration management (RM) function, a connection management (CM) function, a reachability management function, a mobility management function for UEs, etc., a function of transferring SM (Session Management) messages between the UE and the SMF, an access authentication (access authorization) function, a security anchor functionality (SEA), a security context management (SCM) function, a function of supporting the N2 interface for the N3IWF (Non-3GPP Interworking Function), a function of supporting the transmission and reception of NAS signals with the UE via the N3IWF, and a function of authenticating UEs connected via the N3IWF.

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

[0059] In other words, 5GMM-REGISTERED may be a state in which each device has established a 5GMM context, or may be a state in which each device has established a PDU session context. When each device is 5GMM-REGISTERED, UE_A10 may start transmitting and receiving user data and control messages, or may respond to paging. Furthermore, when each device is 5GMM-REGISTERED, UE_A10 may 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 in which each device has not established a 5GMM context, a state in which the location information of UE_A10 is not known to the network, or a state in which the network cannot reach UE_A10. Note that when each device is 5GMM-DEREGISTERED, UE_A10 may initiate a registration procedure or establish a 5GMM context by executing the registration procedure.

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

[0062] Furthermore, in connection management, a CM state in 3GPP access and a CM state in non-3GPP access may be managed separately. In this case, the CM state in 3GPP access may be 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 be 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). The non-connected state may be expressed as an idle mode, and the connected state mode may be expressed as a connected mode.

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

[0064] In addition, one or more AMFs may be placed in the core network_B. In addition, the AMF may be a network function (NF) that manages one or more network slice instances (NSIs). In addition, the AMF may be a common control plane network function (CCNF) shared between multiple NSIs.

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

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

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

[0068] The network connection unit _B720 is a functional unit for connecting the SMF to the AMF, and / or the UPF, and / or the PCF, and / or the UDM. In other words, the SMF can use the network connection unit _B720 to transmit and receive user data and / or control information between the AMF, and / or the UPF, and / or the PCF, and / or the UDM.

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

[0070] The memory 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 a session management function such as establishing, modifying, and releasing PDU sessions, an IP address allocation for UEs and its management function, a UPF selection and control function, a UPF setting function for routing traffic to the appropriate destination (destination), a function for sending and receiving the SM part of NAS messages, a function for notifying that downlink data has arrived (Downlink Data Notification), a function for providing AN-specific (for each AN) SM information to be sent to the AN via the N2 interface via the AMF, a function for determining the SSC mode (Session and Service Continuity mode) for the session, and a roaming function.

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

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

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

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

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

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

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

[0079] The user plane refers to 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. Furthermore, in the case of EPS, the user plane may be transmitted and received using the LTE-Uu interface, and / or the S1-U interface, and / or the S5 interface, and / or the S8 interface, and / or the SGi interface. Furthermore, in the case of 5GS, the user plane may be transmitted and received via an 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 U-Plane.

[0080] Furthermore, the control plane refers to a control message transmitted and received to control communication of the UE. The control plane may be transmitted and received using a Non-Access-Stratum (NAS) signaling connection between the UE and the MME. Furthermore, in the case of EPS, the control plane may be transmitted and received using the LTE-Uu interface and the S1-MME interface. Furthermore, in the case of 5GS, the control plane may be transmitted and received using the interface between the UE and the NG RAN and the N2 interface. Hereinafter, the control plane may be 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 multiple bearers. Furthermore, the C-Plane (Control Plane; CP) may be a communication path for transmitting and receiving control messages and may be composed of multiple bearers.

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

[0083] The PCF has a function of providing policy rules.

[0084] The UDM also has an authentication credential processing function, a user identification processing function, an access authentication function, a registration / mobility management function, a subscription management function, and the like.

[0085] The PCRF is connected to the PGW and / or the PDN and has a function of managing QoS for data delivery. For example, the PCRF manages the QoS of the communication path between the UE_A10 and the PDN. The PCRF may also be a device that creates and / or manages PCC (Policy and Charging Control) rules and / or routing rules used by each device when transmitting and receiving user data.

[0086] The HSS is connected to the MME and / or the SCEF and has a function of managing subscriber information. The subscriber information of the HSS is referred to, for example, when controlling access to the MME. Furthermore, the HSS may be connected to a location management device different from the MME.

[0087] [3. Explanation of terms, identification information, and procedures used in each embodiment] Next, terms, identification information, and procedures used in each embodiment will be explained in advance.

[0088] [3.1. Explanation of terms used in each embodiment] Next, highly specialized terms used in each embodiment and identification information used in the procedures will be described.

[0089] The network refers to at least a part of the access network _B, the core network _B, and the DN. Furthermore, 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. In other words, when a network transmits, receives, and / or processes messages, it may mean that a device in the network (a network device and / or a control device) transmits, receives, and / or processes messages. Conversely, when a device in the network transmits, receives, receives, and / or processes messages, it may mean that the network transmits, receives, and / or processes messages.

[0090] The SM (Session Management) message (also referred to as a NAS (Non-Access-Stratum) SM message) may be a NAS message used in procedures for SM, and may be a control message transmitted and received between UE_A10 and SMF_A230 via AMF_A240. Furthermore, the SM message may include a PDU session establishment request message, a PDU session establishment accept message, a PDU session establishment reject message, a PDU session modification request message, a PDU session modification command message, a PDU session modification complete message, a PDU session modification command reject message, a PDU session modification reject message, a PDU session release request message, a PDU session release reject message, a PDU session release command message, a PDU session release complete message, etc. Furthermore, the procedure for SM or the SM procedure may include a PDU session establishment procedure, a PDU session modification procedure, and a UE-requested PDU session release procedure.Each procedure may be initiated by the UE or may be initiated by the NW.

[0091] An MM (Mobility management) message (also referred to as a NAS MM message) may be a NAS message used in a procedure for MM, and may be a control message transmitted and received between UE_A10 and AMF_A240. Furthermore, the MM message may include a registration request message, a registration accept message, a registration reject message, a de-registration request message, a de-registration accept message, a configuration update command message, a configuration update complete message, a service request message, a service accept message, a service reject message, a notification message, a notification response message, and the like. Furthermore, procedures for MM or MM procedures 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, and a Notification procedure.

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

[0093] Non-5GS services may be services other than 5GS services and may include EPS services and / or non-EPS services.

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

[0095] A PDU (Protocol Data Unit / Packet Data Unit) session can be defined as an association between a DN providing a PDU connectivity service and a UE, but may also be connectivity established between a UE and an external gateway. In 5GS, a UE can transmit and receive user data between a DN and a DN by establishing a PDU session via an access network_B and a core network_B. Here, the external gateway may be a UPF, a SCEF, or the like. A UE can transmit and receive user data to and from a device such as an application server located in a DN by using a PDU session. Each device (UE, and / or an access network device, and / or a core network device) may manage one or more pieces of identification information in association with a PDU session. These pieces of identification information may include one or more of a DNN, a QoS rule, a PDU session type, an application identification information, an NSI identification information, an access network identification information, and an SSC mode, or may further include other information. Furthermore, when a plurality of PDU sessions are established, each piece of identification information associated with a PDU session may be the same or different.

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

[0097] The PDU (Protocol Data Unit / Packet Data Unit) session type indicates the type of the PDU session, and can be IPv4, IPv6, Ethernet, or Unstructured. If IPv4 is specified, it indicates that data is transmitted and received using IPv4. If IPv6 is specified, it indicates that data is transmitted and received using IPv6. If Ethernet is specified, it indicates that Ethernet frames are transmitted and received. Ethernet may also indicate that communication using IP is not performed. If Unstructured is specified, it indicates that data is transmitted and received to an application server or the like in a DN using Point-to-Point (P2P) tunneling technology. As the P2P tunneling technology, for example, UDP / IP encapsulation technology may be used. In addition to the above, the PDU session type may also include IP. IP can be specified when the UE is capable of using 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, which is a communication carrier, and the operator can be identified by a PLMN ID. A PLMN that matches the MCC (Mobile Country Code) and MNC (Mobile Network Code) of a UE's IMSI (International Mobile Subscriber Identity) may be a Home PLMN (HPLMN). Furthermore, the UE may hold an Equivalent HPLMN list in the USIM to identify one or more Equivalent HPLMNs (EPLMNs). A PLMN different from the HPLMN and / or EPLMN may be a Visited PLMN (VPLMN). A PLMN to which the UE has successfully registered may be a Registered PLMN (RPLMN).

[0099] A tracking area is a single or multiple ranges managed by the core network that can be represented by the location information of UE_A10. The tracking area may be composed of multiple cells. Furthermore, the tracking area may be a range in which control messages such as paging are broadcast, or a 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 to these. 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] A registration area is a collection of one or more TAs that the AMF assigns to a UE. Note that while UE_A10 is moving within one or more TAs included in the registration area, it may be able to move without sending or receiving a signal for tracking area update. In other words, a registration area may be a group of information indicating an area in which UE_A10 can move without performing a tracking area update procedure. A registration area may be identified by a TAI list consisting of one or more TAIs.

[0101] The UE ID is information for identifying a UE. For example, the UE ID may be a SUCI (Subscription Concealed Identifier), or a 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 in an application or a network. Furthermore, the UE ID may be information for identifying a user.

[0102] The Always-on PDU session is a PDU session for which user plane resources must be activated every time the UE transitions from the 5GMM-IDLE state to the 5GMM-CONNECTED state. The UE may request the core network and / or the core network device to establish the PDU session as an Always-on PDU session based on an instruction from a higher layer. The core network and / or the core network device determines whether the PDU session can be established as an Always-on PDU session. Here, the establishment of the Always-on PDU session may mean the establishment of a PDU session for C2 communication. Furthermore, the establishment of the Always-on PDU session may mean the establishment of a PDU session handling a QoS flow 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 (Service-level-AA container IE (Information Element)) is an information element for transferring information for authentication and authorization between the UE and the network to a higher layer. The Service-level-AA container information element may 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. The Service-level-AA container information element may include a C2 authorization result, and / or a C2 session security information, and / or identification information of UAV-C to pair, and / or flight authorization information. The Service-level-AA container information element may include a Service-level-AA pending indication. The Service-level-AA container information element may be referred to as a Service-level-AA container.

[0104] The Service-level device ID is an information element for carrying an identity required for authentication and authorization by an external DN. The Service-level device ID may also be included in a Service-level-AA container information element. 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 a service-level authentication and authorization server. The Service-level-AA server address may also be included in the Service-level-AA container information element. The Service-level-AA server address may also include a USS address.

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

[0107] The Service-level-AA response is an information element for providing information about a service level authentication and authorization request. Specifically, the Service-level-AA response is an information element indicating that the authentication and authorization request to the service level authentication server was successful or unsuccessful. The Service-level-AA response may also be included in a Service-level-AA container information element.

[0108] An Uncrewed Aerial Vehicle (UAV) is a flying drone. The UAV may also be a UE. The UAV may also 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. Furthermore, the UAV may be associated with the UAV controller and managed by the core network device and / or the UTM. Furthermore, when the UAV is associated with the UAV controller and managed, the UAV may be managed as a UAS by the core network device and / or the UTM. The UAV may have its own information (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] In addition, a UAV capable of using the UAS service may be a UAV capable of using C2 communication and / or direct C2 communication. In addition, a UAV capable of using C2 communication and / or direct C2 communication may be a UAV capable of using the UAS service.

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

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

[0113] Furthermore, the UAV-C capable of using the UAS service may be a UAV-C capable of using C2 communication and / or direct C2 communication. Furthermore, 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] An Uncrewed Aerial System (UAS) may be composed of a UAV and related functions. Here, the related functions may include a command and control (C2) link. Furthermore, the C2 link may be a link between a UAV and a control station, or a link between a UAV and a network. Furthermore, the C2 link may be a link for remote identification. Furthermore, the UAS may be composed of one or more UAVs and one or more UAV controllers. Furthermore, the UAS may be managed by a network device and / or a USS.

[0115] An USS (Uncrewed Aerial System Service Supplier) is a device having a function for managing a UAV, and / or a UAV controller, and / or a UAS. The USS may be a device of a DN, or may be a device in a core network. The USS may also be a device for autonomously piloting a UAV. The USS may also be equipped with a function for managing identification information, IP addresses, location information, etc. of a UAV and / or a UAV controller, or may also be equipped with a function for managing information of a UAV and / or a UAV controller other than the above. Furthermore, the USS may associate a UAV with a UAV controller and manage them as a UAS. The USS may also transmit information for requesting a network service to a core network device. Furthermore, the USS may be a device that provides one or more functions or services for managing the range of autonomous vehicle operation. The USS may also be a UAS application server.

[0116] Furthermore, the USS may be a device having the functions of the UTM. Furthermore, the USS may be a device provided in the UTM. Furthermore, the USS may be a device within the UTM. Furthermore, the USS may be expressed as USS / UTM or UTM / USS. Furthermore, the USS may be expressed as a network.

[0117] The USS may also transmit information to the core network and / or the UE via an Uncrewed Aerial Systems Network Function (UAS-NF). Information transmitted from the USS may also be considered as information transmitted from the UAS-NF. Information received from the USS may also be considered as information received from the UAS-NF.

[0118] UTM (Uncrewed Aerial System Traffic Management) may be a device that includes a USS. UTM may be a device that includes a USS. UTM may also be read as USS.

[0119] Command and Control (C2) communications may be a user plane link for delivering messages from a UAV controller or UTM to a UAV that contain command and control information for operating the UAV.

[0120] Furthermore, the C2 (Command and Control) communication may be communication for delivering a message including command and control information for operating the UAV from a UAV controller or a UTM to a UAV. Furthermore, the C2 communication may be a user plane link between the UAV controller and the UAV. Furthermore, the C2 communication may be a link between a USS and a UAV. Furthermore, the C2 communication may be communication between a UAV controller and a UAV. Furthermore, the C2 communication may be communication between a USS and a UAV.

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

[0122] In addition, C2 communication may be read as a communication path for C2 communication. In addition, a communication path for C2 communication may be read as C2 communication.

[0123] Direct C2 communication may be a link between a UAV and a UAV-C. Direct C2 communication may also be communication between a UAV and a UAV-C.

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

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

[0126] Moreover, direct C2 communication may be read as a communication path for direct C2 communication. Moreover, a communication path for direct C2 communication may be read as direct C2 communication or direct communication for C2 communication. Moreover, direct C2 communication may be read as a PC5 unicast link. Moreover, a direct link may be read as a PC5 unicast link. A PC5 unicast link may simply be referred to as a unicast link.

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

[0128] The result of the authorization of the C2 communication may also include the result of the authorization of the direct C2 communication. In this case, the C2 authorization result may be information indicating the success of the authorization of the C2 communication using the PDU session, or the success of the authorization of the direct C2 communication, or the success of the authorization of both, or the failure of the authorization. Alternatively, the C2 authorization result may indicate the success or failure of the authorization of the C2 communication, and the network may notify the UE of the success or failure of the authorization of the C2 communication using the PDU session and the 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 an authorization result of the direct C2 communication independent of the C2 authorization result. In this case, the direct C2 authorization result may be information indicating the success or failure of the authorization of the direct C2 communication.

[0130] In addition, the C2 approval result may be read as a direct C2 approval result.

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

[0132] The result of the authorization of the direct C2 communication may also include an authorization result of the C2 communication. In this case, the direct C2 authorization result may be information indicating the success of the authorization of the C2 communication using the PDU session, or the success of the authorization of the direct C2 communication, or the success of the authorization of both, or the failure of the authorization. Alternatively, the direct C2 authorization result may indicate the success or failure of the authorization of the direct C2 communication, and may notify the UE of the success or failure of the authorization of the direct C2 communication, or the UE may recognize the notification.

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

[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, the authorization of C2 communication may include authorization of pairing of the UAV and UAV-C and / or flight authorization. The authorization of pairing of the UAV and UAV-C and / or flight authorization may be performed by the USS.

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

[0136] A case in which a UAV may wish to separate its C2 communications with the USS and its C2 communications with the UAV-C may be, for example, a case in which the UAV requests the establishment of direct C2 communications.

[0137] If the UAV and / or UAV-C requests establishment of direct C2 communication, C2 communication authorization for direct C2 communication may be performed during the registration procedure and / or during the UUAA-MM procedure.

[0138] Authorization for C2 communication may also be referred to as authorization for direct C2 communication.

[0139] Approval for pairing between a UAV and a 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 may need to be performed prior to the exchange of information between the UAV and the UAV-C via C2 communication.

[0140] Flight approval is approval for a UAV to fly (flight). Flight approval may also need to be performed before the UAV can fly. Alternatively, flight approval may be performed within the C2 communication approval procedure only when the UAV requests it. In other words, C2 communication approval may approve the pairing of the UAV and UAV-C and / or the flight of the UAV.

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

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

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

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

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

[0146] A remote ID (RID) is an identification (ID) for identifying a UAV. The remote ID may be, for example, a CAA-level UAV ID. Furthermore, the remote ID may be an ID broadcast via the Uu interface and / or the PC5 interface.

[0147] In addition, as a remote ID broadcast function that takes into consideration the legal regulations of each country regarding UAVs, there may be a function in which the UAV broadcasts via the PC5 interface and a function in which the UAV broadcasts via the Uu interface. Here, the function in which the UAV broadcasts the remote ID via the PC5 is also referred to as BRID (Broadcast Remote Identification). In addition, the broadcast function of the remote ID via the Uu interface is also referred to as network remote ID (NRID). Note that the broadcast of the remote ID via the Uu interface may be performed based on the 5GS MBS (Multicast / Broadcast Service) function and the procedure for the MBS function.

[0148] Among the UEs attempting to establish a communication path for direct communication, there may be an initiating UE and a target UE.

[0149] The initiating UE may be a UE used in direct communication between two UEs. The initiating UE may send a message to the target UE. The initiating UE may receive a message sent from the target UE. The initiating UE may be used in a procedure for establishing direct C2 communication. The initiating UE may be a UAV, a UAV-C, or an AAM.

[0150] The target UE may be a UE used in direct communication between two UEs. The target UE may send a message to the initiating UE. The target UE may receive a message sent from the initiating UE. The target UE may be used in a procedure for establishing direct C2 communication. The target UE may be a UAV, a UAV-C, or an AAM.

[0151] Note that the initiating UE and the target UE may establish a direct communication path by a procedure manually performed by the initiating UE, or the established communication path may be a direct communication path via the PC 5. Furthermore, the direct communication path established between the initiating UE and the target UE via the PC 5 may be a communication path for direct C2 communication, or may be a communication path for communication other than direct C2 communication.

[0152] DAA (Detect And Avoid) may be a function for collision avoidance of aircraft or UAV. DAA may be realized by broadcasting information for DAA by direct communication between UAVs via PC5 and / or broadcasting information for DAA via AAM described later. The communication path used for communication for DAA may be a direct communication path via a PC5 interface (PC5 reference point). Furthermore, the communication path used for communication for DAA may be a direct communication path via PC5 for C2 communication. Alternatively, the communication path used for communication for DAA may be a direct communication path via PC5 for a purpose other than C2 communication. In this specification, an application for DAA or for realizing DAA is also referred to as a DAA application, a DAA function, or simply a DAA. Furthermore, a UE supporting a DAA function may indicate that the UE is capable of using DAA or has the ability to use DAA.

[0153] In addition, the DAA may be provided in the form of transmitting and receiving information for DAA by broadcast or unicast via a PC5 direct communication path between UAVs, or by a USS notifying DAA information (information regarding DAA or DAA applications) via a 3GPP network or other network, or by transmitting and receiving information for DAA via a PC5 direct communication path between an AAM, which is a UE for network-assisted (ground based) DAA, and a UAV.

[0154] An AAM (Area Airspace Manager) is one or more UEs installed in a specific area to provide a network-assisted (ground-based) DAA solution. The AAM has a function for managing the area airspace and may further have a function for direct communication with UAVs via PC5. The AAM may also grasp detailed spatial information of facilities in a specific area and apply local DAA rules defined based on the information to UAVs in the managed airspace.

[0155] The AAM may identify the UAV by the network BRID or NRID, and the AAM may perform ProSe Direct Discovery on the C5 reference point, specify AAM-UAS-control as the application service, and send a solicitation message with the detected remote ID as the application ID, thereby providing the AAM with the Layer-2 ID of the target UAV. The AAM may then establish a PC5 direct communication path using the provided Layer-2 ID.

[0156] In addition, the AAM may be the initiating UE in establishing direct C2 communication (section 3.3.5) described below.

[0157] U2X (UAV-to-Everything) communication is communication that supports U2X communication services over Uu and / or PC5 reference points (interfaces). Furthermore, U2X services are realized in various types of U2X applications, such as between UAVs (U2U) and between UAVs and networks (U2N).

[0158] Additionally, U2X messages may include messaging types dedicated to the U2X service, such as broadcast remote ID messages.

[0159] Furthermore, the U2X service type is a type of U2X service identified by, for example, an ITS-AID (ITS Application Identifier), a PSID (Provider Service Identifier), or an AID (Application Identifier).

[0160] The U2X (UAV to Everything) capability may be UE capability information indicating whether or not the UE supports U2X communication. The U2X capability is UE capability information indicating whether or not the UE supports the DAA function, and may further include the DAA capability. Having the U2X capability may mean supporting the U2X function.

[0161] Furthermore, the DAA capability may be UE capability information indicating whether or not the UE supports DAA or communication for the DAA function. Here, having the DAA capability may mean supporting DAA or communication for the DAA function. Here, a UE having the U2X capability may or may not also have the DAA capability. Furthermore, a UE not having the UAX capability may not have the DAA capability. In this specification, the DAA capability is also referred to as support for the DAA function.

[0162] The PC5 capability may be UE capability information indicating whether or not the UE supports direct communication between UEs via PC5. Furthermore, the PC5 capability may be UE capability information indicating whether or not the UE supports UE direct communication via PC5 in the UAS service. More specifically, the PC5 capability may be information indicating the UE capability information of U2X communication via E-UTRA-PC5 and / or the UE capability information of U2X communication via NR-PC5. Unless otherwise specified in this specification, the PC5 capability of the UE may be capability information for U2X communication.

[0163] Here, the NR-PC5 may be a PC5 reference point via the NR. In this specification, the NR-PC5 is also referred to as the NR PC5 or simply as the PC5.

[0164] The form of direct communication between UEs in direct C2 communication via PC5 may include a unicast mode, a broadcast mode, and a groupcast mode.

[0165] In addition, unless otherwise specified, the UE described in this section may be a UAV and / or a UAV-C and / or an AAM, or may be a UE other than these.

[0166] [3.2. Description of Identification Information in the Present Embodiment] Various types of identification information in the present invention will be described below. In addition, unless otherwise specified, the UE in the description of each identification information may be a UAV and / or a UAV-C and / or an AAM, or may be a UE other than these.

[0167] The first identification information in the present invention is capability information of the UE. More specifically, the first identification information may be information indicating whether the UE supports the DAA function. Also, the first identification information may be information indicating that the UE supports the DAA function. Also, the first identification information may be information indicating that the UE does not support the DAA function.

[0168] Here, support of the DAA function may mean having a function for DAA communication, and a UE that supports the DAA function may be capable of communication for DAA. Note that in this specification, the DAA function is also referred to as a function for DAA communication, DAA capability, etc.

[0169] Furthermore, the first identification information may be information indicating whether the DAA function is supported. For example, the UE may include information indicating that the DAA function is supported or information indicating that the DAA function is not supported in the first identification information based on its own capabilities. Or, for example, if the UE supports the DAA function, the first identification information may be included in the message, and if the UE does not support the DAA function, the first identification information may not be included in the message.

[0170] Also, the first identification information may be information included in U2X capability indicating the presence or absence of support for U2X. More specifically, for example, the UE may include the first identification information in U2X capability included in a 5GMM capability information element (IE) in an MM message and transmit the information to the network. Alternatively, the first identification information may be identification information separate from the U2X capability, and for example, the UE may include the first identification information in a 5GMM capability IE in an MM message as information separate from the U2X capability and transmit the information to the network.

[0171] Furthermore, when the first identification information is included in the U2X capability, the first identification information may be included in the U2X capability only when the UE supports the U2X function. In other words, for example, when the UE does not support U2X, the UE may not support the DAA function. Or, for example, when the UE supports U2X, the UE may support the DAA function or may not support the DAA function. In this case, the UE may further include the first identification information indicating the presence or absence of support for each DAA function in the U2X capability indicating support for U2X.

[0172] The UE may indicate to the network what the first identity indicates by sending the first identity in a message to the network. Furthermore, the UE may include the first identity in the message according to a network policy, or a UE policy, or a policy of the USS / UTM to which the UE subscribes.

[0173] The second identity information in the present invention is a cause value that the network indicates to the UE. The second identity information may be a cause value indicating that the UE is rejected to register with the network or UAS service. The second identity information may also be information included in a 5GMM cause IE in an MM message. The MM message including the second identity information may be, for example, a registration rejection message.

[0174] The network may determine whether to include the second identification information in the MM message to be sent to the UE based on the presence or absence of support for the DAA function and / or the direct communication function via the PC5 interface, as indicated in the capability information including the first identification information received from the UE. More specifically, for example, if the network recognizes that the UE supports either or both of the DAA function and / or the direct communication function via the PC5 interface, the network may not include the second identification information in the message to be sent to the UE. Conversely, for example, if the network recognizes that the UE does not support either or both of the DAA function and / or the direct communication function via the PC5 interface, the network may include the second identification information in the message to be sent to the UE.

[0175] In other words, for example, the network may determine whether to include the second identity in the message based on the UE's capability information including the first identity included by the UE in the registration request message, and may further determine whether to include the second identity in the message based on an operator policy, a network policy, or a policy of the UAS service.

[0176] Here, the information indicating support for the direct communication function via the PC5 interface that the UE sends together with the first identification information may be PC5 capability and / or ProSe capability, and may be information included in a 5GMM capability information element in an MM message that the network receives from the UE.

[0177] Also, for example, the second identification information may be a 5GMM cause value of #79 (UAS services not allowed) or may be another reason value.

[0178] A UE that receives the second identification information may recognize what the second identification information indicates, and may behave based on the second identification information.

[0179] The eleventh identification information in the present invention is a reason value that the network indicates to the UE. The eleventh identification information may be a reason value indicating that the UE is denied establishment of a communication path to the network and / or UAS service. Here, the communication path from the UE to the network and / or UAS service may be a PDU session. In addition, the PDU session may be a normal PDU session or a PDU session for C2 communication.

[0180] In addition, the 11th identification information may be information included in the 5GSM cause IE in the SM message. Furthermore, the SM message including the 11th identification information may be, for example, a PDU session establishment rejection message or a PDU session change rejection message.

[0181] The network may determine whether to include the eleventh identification information in the MM message to be sent to the UE based on the presence or absence of support for the DAA function and / or the direct communication function via the PC5 interface, as indicated in the capability information including the first identification information received from the UE. More specifically, for example, if the network recognizes that the UE supports either or both of the DAA function and / or the direct communication function via the PC5 interface, the network may not include the eleventh identification information in the message to be sent to the UE. Conversely, for example, if the network recognizes that the UE does not support either or both of the DAA function and / or the direct communication function via the PC5 interface, the network may include the eleventh identification information in the message to be sent to the UE.

[0182] In other words, for example, the network may determine whether to include the eleventh identity in the message in the PDU session establishment procedure after the registration procedure is completed based on the UE's capability information including the first identity included by the UE in the registration request message. Furthermore, the network may determine whether to include the eleventh identity in the message based on an operator policy, a network policy, or a policy of the UAS service.

[0183] Here, the information indicating support for the direct communication function via the PC5 interface that the UE sends together with the first identification information may be PC5 capability and / or ProSe capability, and may be information included in a 5GMM capability information element in an MM message that the network receives from the UE.

[0184] Also, for example, the 11th identification information may be a 5GSM cause value of #86 (UAS services not allowed) or another cause value.

[0185] A UE that receives the eleventh identification information may recognize what the second identification information indicates and may behave based on the second identification information.

[0186] The 21st identification information in the present invention is capability information of the UE. More specifically, the 11th identification information may be information indicating whether or not the UE supports the DAA function. Furthermore, the 21st identification information may be equivalent to the first identification information, or may include the first identification information. Alternatively, the 21st identification information may include capability information regarding the support of the DAA function and / or the direct communication function via PC5 that the UE indicates to the network in the registration procedure. Furthermore, the 21st identification information may be transmitted together with the remote ID of the corresponding UE. Here, the remote ID of the UE may be a CAA-level UAV ID. Also, the remote ID of the UE may be a UE ID. Also, the 21st identification information may be associated with the remote ID of the UE.

[0187] Furthermore, the 21st identification information may be information broadcast from the network via the gNB based on the MBS (Multicast / Broadcast Service) function of 5GS, and / or the 21st identification information may be information broadcast or unicast between UAVs directly connected via the PC5 interface, or between the UE and the AAM.

[0188] In addition, the broadcast and / or unicast including the 21st identification information may be executed based on the UE capability information including the first identification information that the UE indicated to the network in the registration procedure. More specifically, for example, information regarding support for the DAA function and / or the direct communication function via the PC5 interface that the UE indicated to the network in the registration procedure may be included in the 21st identification information and transmitted in the broadcast and / or unicast message.

[0189] In addition, a UE (UAV or AAM) that receives the 21st identification information may recognize that the UAV associated with the 21st identification information has a DAA function, and may establish a PC5 direct communication path for the DAA function, and perform communication for the DAA function via that communication path.

[0190] The 22nd identification information in the present invention is identification information on the network of each UE that is used by the UE in direct communication via the PC 5. For example, the 22nd identification information may be identification information that can specify each UE, which is required when the UEs establish a direct communication link via the PC 5. For example, the 22nd identification information may be a destination Layer-2 ID, or other information for identifying the UE.

[0191] Furthermore, the 22nd identification information may be transmitted together with the corresponding UE's remote ID, where the UE's remote ID may be a CAA-level UAV ID.

[0192] In addition, the 22nd identification information may be information broadcast from the network via the gNB based on the MBS (Multicast / Broadcast Service) function of 5GS, and / or the 22nd identification information may be information broadcast or unicast between UAVs directly connected via the PC5 interface, or between the UE and the AAM.

[0193] Here, the network and / or UE may indicate that the UE indicated by the 22nd identification information has the DAA function and / or the direct communication function via PC5 by including the 22nd identification information in the broadcast and / or unicast message. In other words, for example, the network may indicate that the information indicated by the 21st identification information, i.e., the corresponding UE supports the DAA function and / or the function of directly communicating via PC5 by including the 22nd identification information in the broadcast and / or unicast message. That is, for example, the network may indicate that the corresponding UE supports the DAA function and / or the function of directly communicating via PC5 by including the 22nd identification information in the broadcast and / or unicast message without including the 21st identification information.

[0194] In addition, the network and / or UE may indicate that the UE indicated by the 22nd identification information does not have DAA functionality and / or direct communication functionality via PC5 by not including the 22nd identification information in a broadcast and / or unicast message.

[0195] In addition, the broadcast and / or unicast including the 22nd identification information may be executed based on the UE capability information including the first identification information that the UE indicated to the network in the registration procedure. More specifically, for example, when the UE supports the DAA function and / or the direct communication function via the PC5 interface that the UE indicated to the network in the registration procedure, the 22nd identification information may be included in the broadcast and / or unicast message and transmitted.

[0196] In addition, a UE (UAV or AAM) that receives the 22nd identification information may recognize that the UAV associated with the 22nd identification information has a DAA function, and based on the information contained in the 22nd identification information, may establish a PC5 direct communication path for the DAA function and perform communication for the DAA function via that communication path.

[0197] Furthermore, the UE (UAV or AAM) that has received the 22nd identification information may perform a procedure for establishing a direct communication path or direct link for DAA communication with the UE (UAV or AAM) by transmitting a message including the 22nd identification information. Here, the message that the AAM transmits including the 22nd identification information may be, for example, a Direct Communication Request (DCR).

[0198] [3.3. Description of procedures used in each embodiment] Next, procedures used in each embodiment will be described. The procedures used in each embodiment include a registration procedure, a PDU session establishment procedure, a network-initiated session management procedure, a UE-initiated PDU session modification procedure, a procedure for establishing direct C2 communication, a procedure for releasing direct C2 communication, and a procedure initiated by a USS. Each procedure will be described below.

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

[0200] [3.3.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 take the initiative in registering to the access network_B and / or the core network_B and / or the DN. If the UE is not registered to the network, it can execute this procedure at any time, such as when the power is turned on. In other words, if the UE is in a deregistered state (RM-DEREGISTERED state), it can start this procedure at any time. Furthermore, each device (especially the UE and the AMF) can transition to a registered state (RM-REGISTERED state) based on the completion of the registration procedure.

[0201] The registration procedure may also be an initial registration initiated by the UE, the registration procedure may also be a mobility and periodic registration, or the registration procedure may also be an MM procedure.

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

[0203] In addition, the registration or registration procedure in this procedure may be a registration or registration procedure for C2 communication or a registration or registration procedure for direct C2 communication. In addition, the PDU session in this procedure may be a PDU session for UAS service or a PDU session for C2 communication.

[0204] Alternatively, the registration or registration procedure in this procedure may be a registration or registration procedure for communication other than C2 communication, or a registration or registration procedure for communication other than direct C2 communication. Also, the PDU session in this procedure may be a PDU session for a service other than UAS service, or a PDU session for communication other than C2 communication.

[0205] The UE may start the registration procedure when mobility across TAs is performed. In other words, the UE may start the registration procedure when the UE moves to a TA different from the TA indicated in the TA list held by the UE. Furthermore, the UE may start this procedure when an active timer expires. Furthermore, the UE may start the registration procedure when it is necessary to update the context of each device due to disconnection or invalidation of a PDU session. Furthermore, the UE may start the registration procedure when a change occurs in capability information and / or preferences regarding the establishment of a PDU session of the UE. Furthermore, the UE may start the registration procedure periodically. Furthermore, the UE may start the registration procedure based on the completion of a UE configuration update procedure. It should be noted that the UE can execute the registration procedure at any timing, not limited to the above.

[0206] Furthermore, even if the UE is in a registered state, the UE may periodically initiate or perform a registration procedure, in other words, the UE may initiate or perform a registration procedure based on the expiration of a timer.

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

[0208] Next, each step of the registration procedure will be described. Note that the registration procedure described below may be an initial registration procedure, or a registration procedure for mobility and registration renewal.

[0209] 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 a registration request message to the 5G AN (or gNB) (S800). The registration request message is a NAS message. The RRC message may be a control message transmitted and received between the UE and the 5G AN (or gNB). The NAS message is processed in the NAS layer, and the RRC message is processed in the RRC layer. The NAS layer is a layer higher than the RRC layer.

[0210] Here, the UE may transmit the first identification information in a registration request message, or may transmit the first identification information in a NAS message.

[0211] In addition, the UE may select and decide whether to include the first identification information in the registration request message based on the UE's capabilities, and / or subscription information, and / or user registration information, and / or context held by the UE, etc.

[0212] In addition, the UE may indicate that the UE supports the DAA function by sending the first identification information in a registration request message, or may indicate that the UE does not support the DAA function.

[0213] In addition, if the UE does not support the function indicated by the first identification information, the UE may not need to send a registration request message. In addition, if the UE does not support the DAA function, the UE may not need to send a registration request message.

[0214] The UE may also initiate a PDU session establishment procedure during the registration procedure by sending a SM message in or together with a registration request message, where the SM message may be a PDU session establishment request message.

[0215] When the 5G AN (or gNB) receives an RRC message including a registration request message, it selects an AMF to which the registration request message is to be transferred (S802). The 5G AN (or gNB) can select an AMF based on 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).

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

[0217] The first condition determination may be performed based on the reception of a registration request message, and / or each identification information included in the registration request message, and / or subscriber information, and / or network capability information, and / or operator policy, and / or network status, and / or user registration information, and / or a context held by the AMF. For example, if the network permits the request of the UE, the first condition determination may be true, and if the network does not permit the request of the UE, the first condition determination may be false. In addition, if the network to which the UE is registered and / or a device in the network supports a function requested by the UE, the first condition determination may be true, and if the network does not support the function requested by the UE, the first condition determination may be false. Furthermore, if the identification information to be transmitted and received is permitted, the first condition determination may be true, and if the identification information to be transmitted and received is not permitted, the first condition determination may be false. In addition, the conditions for determining whether the first condition determination is true or false may not be limited to the above-mentioned conditions.

[0218] First, a case where the first condition determination is true will be described. In the procedure of (A) in Fig. 6, the AMF can first execute the fourth condition determination. The fourth condition determination is for determining whether the AMF transmits and receives an SM message between the AMF and the SMF.

[0219] In addition, the fourth condition determination may be performed based on whether the AMF has received an SM message. In addition, the fourth condition determination may be performed based on whether the registration request message includes an SM message. For example, if the AMF has received an SM message and / or if the registration request message includes an SM message, the fourth condition determination may be true, and if the AMF has not received an SM message and / or if the registration request message does not include an SM message, the fourth condition determination may be false. In addition, the conditions that determine the truth or falsehood of the fourth condition determination may not be limited to the above-mentioned conditions.

[0220] Next, 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 based on the reception of the registration request message and / or the completion of the transmission and reception of the SM message with the SMF (S808). For example, when the fourth condition determination is false, the AMF may transmit a registration accept 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 accept message based on the completion of the transmission and reception of the SM message with the SMF. Note that the registration accept message is a NAS message transmitted and received on the N1 interface, but is transmitted and received between the UE and the 5G AN (gNB) in an RRC message.

[0221] Here, the network may indicate the content of the above-mentioned identification information to the UE by sending a registration accept message.

[0222] Furthermore, the AMF may include and send the SM message in a registration accept message, or may send the SM message together with the registration accept message. However, this sending method may be executed when the SM message is included in the registration request message and the fourth condition determination is true. Also, this sending 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 sending 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.

[0223] The AMF may also indicate that the UE's request has been accepted by sending a registration acceptance message based on the received identification information, and / or subscription information, and / or network capability information, and / or operator policies, and / or network status, and / or user registration information, and / or context held by the AMF, etc.

[0224] Furthermore, the AMF may include information indicating that some of the UE's requests have been rejected in the registration acceptance message and transmit it, or may indicate the reason why some of the UE's requests have been rejected by transmitting information indicating that some of the UE's requests have been rejected. Furthermore, the UE may recognize the reason why some of the UE's requests have been rejected by receiving information indicating that some of the UE's requests have been rejected. In addition, the reason for the rejection may be information indicating that the content indicated by the identification information received by the AMF is not permitted.

[0225] 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 UE's request by the registration request message has been accepted and the contents of various identification information included in the registration acceptance message.

[0226] Furthermore, the UE may transmit 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 included in an RRC message and transmitted and received between the UE and the 5G AN (gNB).

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

[0228] Next, a case where the first condition determination is false will be described. In the procedure of (B) of Fig. 6, 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 included in an RRC message and transmitted and received between the UE and the 5G AN (gNB).

[0229] Furthermore, the AMF may indicate that the UE's request by the registration request message has been rejected by sending a registration rejection message. Furthermore, the AMF may include information indicating the reason for the rejection in the registration rejection message and transmit it, or may indicate the reason for the rejection by sending the reason for the rejection. Furthermore, 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. In addition, the reason for the rejection may be information indicating that the content indicated by the identification information received by the AMF is not permitted.

[0230] Here, the AMF may include the second identification information in the registration rejection message and send it. The AMF may determine whether to include the second identification information in the registration message based on the content of the first identification information received from the UE, and / or the subscriber information, and / or the network capability information, and / or the operator policy, and / or the network status, and / or the user's registration information, and / or the context held by the AMF, etc. Furthermore, for example, the AMF may indicate to the UE that the registration has been rejected based on the UE capability information indicated by the first identification information by including the second identification information in the registration rejection message. In addition, the network may include the second identification information in the registration rejection message based on the first identification information received from the UE indicating that the DAA function is not supported.

[0231] 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 by the registration request message has been rejected and the contents of various identification information included in the registration rejection message. In addition, if the UE does not receive a registration rejection message even after a predetermined period has elapsed after transmitting the registration request message, the UE may recognize that the UE's request has been rejected. Each device completes the procedure (B) in this procedure based on the transmission and reception of the registration rejection message.

[0232] Furthermore, when the UE receives the registration rejection message including the second identity, the UE may recognize that the registration has been rejected based on the UE capability indicated by the first identity transmitted by the UE to the network, or that the network has rejected the registration based on the network not supporting either or both of the DAA function and / or the PC5 direct communication function indicated by the first identity.

[0233] Furthermore, when the UE receives a registration rejection message including the second identification information, the UE may perform a new registration procedure. Furthermore, when the UE receives a registration rejection message including the second identification information, the UE may perform a new PLMN selection or SNPN selection. Furthermore, when the UE receives a registration rejection message including the second identification information, the UE may not include a service-level device ID with a CAA-level UAV ID set in a Service-level-AA container IE of a registration request message.

[0234] The procedure in FIG. 6(B) may be started when the procedure in FIG. 6(A) is stopped.

[0235] Each device completes the registration procedure based on the completion of the procedure of (A) or (B) in Fig. 6. Each device may transition to a state in which the UE is registered in the network (RM_REGISTERED state) based on the completion of the procedure of (A) in Fig. 6, and may maintain a state in which the UE is not registered in the network (RM_DEREGISTERED state) or transition to a state in which the UE is not registered in the network based on the completion of the procedure of (B) in Fig. 6. Furthermore, the transition of each device to each state may be performed based on the completion of the registration procedure or the establishment of a PDU session.

[0236] The UE may also complete the registration procedure based on receiving the registration accept message or the registration reject message.

[0237] 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 transmitting and receiving information indicating that some of the UE's requests have been rejected, the device may recognize the reason why the UE's requests have been rejected. Furthermore, each device may perform this procedure again based on the reason why the UE's request has been rejected, or may perform the registration procedure for the core network_B or another cell.

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

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

[0240] In addition, the behavior to be performed when each piece of identification information is received may be performed based on the received identification information.

[0241] [3.3.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. The PDU session establishment procedure may also be an SM procedure.

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

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

[0244] This procedure may be performed after the registration procedure has been performed one or more times.

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

[0246] Specifically, the UE initiates 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 an access network (5GAN or gNB) (S1400). The NAS message is, for example, a message sent via the N1 interface and may be an uplink NAS transport (UL NAS TRANSPORT) message.

[0247] Here, the UE may indicate the contents of each identification information to the network by sending a PDU session establishment request message or a NAS message.

[0248] In addition, the access network may be a 3GPP access or a non-3GPP access and may include a base station device. That is, the UE transmits a NAS message to the AMF via the base station device.

[0249] The UE may also request establishment of a PDU session supporting C2 communication by sending a PDU session establishment request message. In other words, the UE may request establishment of a PDU session supporting a QoS flow for C2 communication by sending a PDU session establishment request message.

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

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

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

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

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

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

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

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

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

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

[0260] Next, each step of the procedure in FIG.

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

[0262] The SMF may decide whether to perform approval of C2 communication during this procedure based on information received from the AMF (message, container, information), and / or information such as PCC rules received from the PCF, and / or subscriber information, and / or network capability information, and / or UE policy, and / or operator policy, and / or network status, and / or user registration information, and / or context held by the SMF, etc.

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

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

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

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

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

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

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

[0270] 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 receives the N2 PDU session request message transmits a NAS message to the UE (S1416). Here, the N2 PDU session request message may include a NAS message and / or N2 SM information. In addition, the NAS message may include a PDU session ID and / or an N1 SM container.

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

[0272] Here, the SMF and / or AMF may indicate that at least a portion 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.

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

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

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

[0276] First, based on receiving the PDU session establishment request message, the SMF sends an N1 SM container and / or a PDU session ID to the AMF, for example via the N11 interface (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.

[0277] 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 an N1 interface. The NAS message may be a downlink NAS transport (DL NAS TRANSPORT) message. The NAS message may include the PDU session ID and / or the N1 SM container.

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

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

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

[0281] Here, the SMF and / or AMF may include an eleventh identity in the PDU session establishment rejection message. The SMF and / or AMF may include the eleventh identity in the PDU session establishment rejection message based on the first identity indicated by the UE to the network in the registration request message. Also, for example, the SMF and / or AMF may include the eleventh identity in the PDU session establishment message based on the UE not supporting the DAA function and / or the PC5 direct communication function indicated by the first identity.

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

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

[0284] In addition, the UE behavior may be implemented after receiving a PDU session accept message or a PDU session reject message, or after receiving one or more of the identification information of the 10th to 12th and the 15th to 18th identification information.

[0285] The UE may recognize the contents of the above identification information by receiving a NAS message or a PDU session establishment acceptance message or a PDU session establishment rejection message.

[0286] Each device may complete this procedure based on the transmission and reception of the 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 in which it can communicate with the DN using the established PDU session.

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

[0288] In addition, each process that the UE performs based on the reception of each identification information shown above may be performed during this procedure or after completion of this procedure, or may be performed after completion of this procedure based on the completion of this procedure.

[0289] [3.3.3. Overview of network-initiated session management procedures] Next, an overview of the network-initiated session management procedure will be described. Hereinafter, the network-initiated session management procedure will also be referred to as this procedure. This procedure is a procedure for session management that is initiated by the network for an established PDU session. The network-initiated session management procedure may also be an SM procedure.

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

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

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

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

[0294] [3.3.3.1. Example of network-initiated session management procedures] Next, an example of a network-initiated session management procedure will be described with reference to Figure 8. Hereinafter, this procedure refers to the network-initiated session management procedure. Each step of this procedure will be described.

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

[0296] Specifically, the device in the core network_B190 may start this procedure based on receiving a PDU session modification request message from the UE, or may start this procedure based on receiving a PDU session release request message from the UE. If this procedure is started based on receiving a PDU session modification request message, this procedure may be a network-initiated PDU session modification procedure. Furthermore, if this procedure is started based on receiving a PDU session release request message, this procedure may be a network-initiated PDU session release procedure.

[0297] Additionally, a device in Core Network _B 190 may initiate this procedure based on a request from a device in the DN or another device in the core network.

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

[0299] An apparatus in the core network _B 190 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 an apparatus in the core network _B 190.

[0300] Further, a device in Core Network _B190 may include a PDU session ID in a network-initiated session management request message, or may include the PDU session ID to request that changes be made to the PDU session identified by the PDU session ID.

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

[0302] Next, the UE that has received the network initiated session management request message transmits a network initiated session management completion message (S1604). In addition, the UE may perform a first process based on the completion of this procedure.

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

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

[0305] The first process may be a process in which the UE recognizes something indicated by the core network_B190, or may be a process in which the UE recognizes a request from the core network_B190. Furthermore, 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 forwards the received identification information to a higher layer and / or a lower layer.

[0306] Furthermore, the UE may execute, as the first process, a behavior when receiving each of the above-mentioned identification information.

[0307] Furthermore, each device may perform a process 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 a first process based on the completion of this procedure, or may complete this procedure after the completion of the first process.

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

[0309] In addition, each device may change the existing PDU session or release the existing PDU session based on the completion of the network-initiated session management procedure. In other words, each device may change the existing PDU session based on the completion of the PDU session change procedure. In other words, each device may release the existing PDU session based on the completion of the PDU session release procedure.

[0310] [3.3.4. Overview of UE-initiated session management procedures] Next, an overview of the UE-initiated session management procedure will be described. Hereinafter, the UE-initiated session management procedure will also be referred to as this procedure. This procedure is a procedure for session management that is initiated by the UE for an established PDU session. The UE-initiated session management procedure may also be an SM procedure.

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

[0312] In addition, this procedure may be a UE initiated PDU session modification procedure and / or a UE initiated PDU session release procedure, etc., and may execute a UE initiated session management procedure including but not limited to these. In addition, each device may transmit and receive a PDU session modification request message, a PDU session modification command message, a PDU session modification completion message, and / or a PDU session modification rejection message in the UE initiated PDU session modification procedure. In addition, each device may transmit and receive a PDU session release request message, a PDU session release command message, a PDU session release completion message, and / or a PDU session release rejection message in the UE initiated PDU session release procedure.

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

[0314] [3.3.4.1. Example of UE initiated PDU session modification procedure] Next, each step of this procedure will be described with reference to Fig. 9. Hereinafter, this procedure refers to the UE-initiated PDU session modification procedure.

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

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

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

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

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

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

[0321] The UE receives the PDU session modification rejection message, and each device completes the procedure based on sending and receiving the PDU session modification rejection message and / or completing the network-initiated PDU session modification procedure.

[0322] Here, the UE may recognize that the UE request is rejected based on the reception of the PDU session change reject message. Furthermore, the UE may perform a second process based on the reception of the PDU session change reject message (S1806). Note that the second process may be performed based on the completion of this procedure.

[0323] 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 a context, or may be a process in which the UE forwards the received identification information to a higher layer and / or a lower layer. Furthermore, the second process may be a process in which the UE recognizes that the request for this procedure has been rejected.

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

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

[0326] [3.3.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.

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

[0328] Specifically, if this procedure is a UE-initiated PDU session release procedure, the above-mentioned PDU session change request message may be read as a PDU session release request message. Furthermore, if this procedure is a UE-initiated PDU session release procedure, the above-mentioned PDU session change request message may be read as a PDU session release request message, and the above-mentioned PDU session change rejection message may be read as a PDU session release rejection message. Furthermore, the behavior of changing the PDU session may be read as a behavior of releasing the PDU session.

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

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

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

[0332] 3.3.5. Procedures for establishing a channel for direct communication Next, the behavior of each device when the UE executes a procedure for establishing a communication path for direct communication will be described with reference to Fig. 10. Hereinafter, the procedure for establishing a communication path for direct communication will also be referred to as this procedure. In addition, the procedure for establishing a communication path for direct communication may be referred to as a communication path establishment procedure for direct communication.

[0333] In addition, this procedure may be a procedure for establishing a communication path for direct C2 communication, or a procedure for establishing a communication path for communication other than direct C2 communication. In addition, if this procedure is a procedure for establishing a communication path for communication other than direct C2 communication, the direct C2 communication described in this section may be read as a communication path for direct communication, a direct communication path, a direct link, etc.

[0334] This procedure may be performed after one or more of the registration procedure, the PDU session establishment procedure, the network initiated session management procedure, and / or the UE initiated session management procedure are performed. This procedure may also be performed during the registration procedure, the PDU session establishment procedure, the network initiated session management procedure, or the UE initiated session management procedure.

[0335] This procedure may be performed when the UE is authenticated and / or authorized for direct C2 communication by the network 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. The UE may also start this procedure regardless of the authorization for direct C2 communication from the network.

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

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

[0338] The procedure also includes a ProSe direct link establishment procedure and a PC5 unicast link establishment procedure. Here, the ProSe direct link establishment procedure may establish a ProSe direct link for direct C2 communication. The PC5 unicast link establishment procedure may establish a PC5 unicast link for direct C2 communication. In other words, the procedure may be a procedure for establishing a ProSe direct link or a PC5 unicast link for direct C2 communication.

[0339] These are explained in Sections 3.3.5.1 and 3.3.5.2 below, respectively.

[0340] [3.3.5.1. ProSe direct link establishment procedure] This section describes the ProSe direct link establishment procedure. Note that the start of this procedure is based on the description in Section 3.3.5.

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

[0342] Here, the first control message may be a message requesting 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.

[0343] Here, the initiating UE may transmit the first control message to indicate to the target UE the contents of each piece of identification information included in the message.

[0344] The initiating UE may also request establishment of the direct C2 communication by sending a first control message.

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

[0346] 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) contained in the first control message.

[0347] Here, the target UE may perform a third condition determination. The third condition determination may be for the target UE to determine whether or not to accept the request of the initiating UE. If the target UE determines that the third condition determination is true, the target UE may start the procedure of (A) in Fig. 10, and if the target UE determines that the third condition determination is false, the target UE may start the procedure of (B) in Fig. 10.

[0348] In addition, the third condition determination may be performed based on information (message, container, information) 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 status, and / or user registration information, and / or context held by the target UE, etc.

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

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

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

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

[0353] Here, the second control message may be a message 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.

[0354] The second control message may be a response message to the first control message, and may indicate that the first control message has been accepted.

[0355] Here, the target UE may indicate that at least a portion of the initiating UE's request in the first control message has been accepted by sending a second control message.

[0356] By transmitting these identification information and / or the second control message, the target UE may indicate that the target UE supports each function, may indicate that the request from the initiating UE has been accepted, may indicate that the request from the initiating UE is not permitted, or may indicate a combination of these. Furthermore, when multiple pieces of identification information are transmitted and received, two or more 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 use of each function may be transmitted and received as the same identification information, or may be transmitted and received as different identification information.

[0357] Furthermore, the target UE may determine 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 status, and / or user registration information, and / or context held by the target UE, etc.

[0358] The initiating UE then receives a second control message from the target UE.

[0359] When the initiating UE receives the second control message, it can recognize that the UE's request in the first control message has been accepted and / or the contents of the information, etc. (message, container, or identification information) contained in the second control message.

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

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

[0362] Here, the third control message may be a message for rejecting 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.

[0363] Furthermore, the third control message may be a response message to the first control message, and may indicate that the establishment of the direct C2 communication is rejected.

[0364] Here, the target UE may send a third control message to indicate that the initiating UE's request in the first control message is rejected.

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

[0366] In addition, the target UE may determine which identification information to include in the third 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 status, and / or user registration information, and / or context held by the target UE, etc.

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

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

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

[0370] In addition, each process that the initiating UE shown above performs based on the reception of each identification information may be performed during this procedure or after completion of this procedure, or may be performed after completion of this procedure based on the completion of this procedure.

[0371] 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 over a ProSe direct link.

[0372] [3.3.5.2. PC5 unicast link establishment procedure] This section describes the PC5 unicast link establishment procedure. The start of this procedure is based on the description in Section 3.3.5. First, the initiating UE transmits a first control message to the target UE (S2000) to start this procedure.

[0373] Here, the first control message may be a message requesting establishment of direct C2 communication. Also, the first control message may be a Direct Link Establishment Request message. Also, the first control message may be a Direct Communication Request message.

[0374] Here, the initiating UE may transmit the first control message to indicate to the target UE the contents of each piece of identification information included in the message.

[0375] The initiating UE may also request establishment of the direct C2 communication by sending a first control message.

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

[0377] 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) contained in the first control message.

[0378] Here, the target UE may perform a third condition determination. The third condition determination may be for the target UE to determine whether or not to accept the request of the initiating UE. If the target UE determines that the third condition determination is true, the target UE may start the procedure of (A) in Fig. 10, and if the target UE determines that the third condition determination is false, the target UE may start the procedure of (B) in Fig. 10.

[0379] In addition, the third condition determination may be performed based on information (message, container, information) 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 status, and / or user registration information, and / or context held by the target UE, etc.

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

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

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

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

[0384] Here, the second control message may be a message accepting the establishment of direct C2 communication. Also, the second control message may be a Direct Link Establishment Accept message. Also, the second control message may be a Direct Communication Accept message.

[0385] The second control message may be a response message to the first control message, and may indicate that the first control message has been accepted.

[0386] Here, the target UE may indicate that at least a portion of the initiating UE's request in the first control message has been accepted by sending a second control message.

[0387] By transmitting the second control message, the target UE may indicate that the target UE supports each function, may indicate that the request from the initiating UE has been accepted, may indicate that the request from the initiating UE is not permitted, or may indicate a combination of these. Furthermore, when multiple pieces of identification information are transmitted and received, two or more pieces of identification information may be configured as one or more pieces of identification information. The information indicating support for each function and the information indicating a request to use each function may be transmitted and received as the same identification information, or may be transmitted and received as different identification information.

[0388] Furthermore, the target UE may determine 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 status, and / or user registration information, and / or context held by the target UE, etc.

[0389] The initiating UE then receives a second control message from the target UE.

[0390] When the initiating UE receives the second control message, it can recognize that the UE's request in the first control message has been accepted and / or the contents of the information, etc. (message, container, or identification information) contained in the second control message.

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

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

[0393] Here, the third control message may be a message for rejecting the establishment of direct C2 communication. Also, the third control message may be a Direct Link Establishment Reject message. Also, the third control message may be a Direct Communication Reject message.

[0394] Furthermore, the third control message may be a response message to the first control message, and may indicate that the establishment of the direct C2 communication is rejected.

[0395] Here, the target UE may send a third control message to indicate that the initiating UE's request in the first control message is rejected.

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

[0397] In addition, the target UE may determine which identification information to include in the third 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 status, and / or user registration information, and / or context held by the target UE, etc.

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

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

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

[0401] In addition, each process that the initiating UE shown above performs based on the reception of each identification information may be performed during this procedure or after completion of this procedure, or may be performed after completion of this procedure based on the completion of this procedure.

[0402] Upon completion of this procedure, the initiating UE and the target UE that have established direct C2 communication via a PC5 unicast link may start exchanging information using direct C2 communication.

[0403] [3.3.6. Procedure for releasing a channel for direct communication] Next, the behavior of each device when the UE executes a procedure for releasing a communication path for direct communication will be described with reference to FIG. 11. Hereinafter, the procedure for releasing direct C2 communication will also be referred to as this procedure. Also, the procedure for releasing direct C2 communication may be referred to as a release procedure for direct C2 communication. Note that this procedure may be a procedure for releasing direct C2 communication established by any of the procedures described in Section 3.3.5.

[0404] This procedure may be performed after one or more of the registration procedure, the PDU session establishment procedure, the network initiated session management procedure, and / or the UE initiated session management procedure are performed. This procedure may also be performed during the registration procedure, the PDU session establishment procedure, the network initiated session management procedure, or the UE initiated session management procedure.

[0405] This procedure may be performed when the UE is deauthorized and / or authorized for direct C2 communication by the network during the registration procedure, the PDU session establishment procedure, the network-initiated session management procedure, and / or the UE-initiated session management procedure. The UE may also initiate this procedure regardless of the deauthorization of direct C2 communication by the network.

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

[0407] This procedure may also be performed when the UE receives from a lower layer an indication of a radio link failure or an indication of a release of the PC5-RRC connection.

[0408] This procedure may also be performed when the initiating UE receives a request from a higher layer to release a 5G ProSe direct link or a PC5 unicast link. This procedure may also be performed when the initiating UE receives a request from a higher layer to release a communication path for direct C2 communication.

[0409] This procedure may also be performed when the target UE is in an unresponsive state.

[0410] This procedure may also be performed when the initiating UE reaches a maximum number of established 5G ProSe direct links and / or needs to establish a new 5G ProSe direct link. This procedure may also be performed when the initiating UE reaches a maximum number of established direct C2 communication paths and / or needs to establish a new 5G ProSe direct link or a new PC5 unicast link.

[0411] This procedure may also be performed when the initiating UE operates 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. More specifically, this procedure may be performed based on, for example, a PDU session release procedure performed in a procedure initiated by the USS described below. Or, this procedure may be performed based on, for example, a PDU session modification procedure performed in a procedure initiated by the USS described above.

[0412] This procedure may also be performed 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.

[0413] This procedure may also be performed 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 authorization of the initiating UE is revoked after receiving the configuration parameters.

[0414] This procedure may also be performed when the initiating UE is operating as a 5G ProSe layer-3 UE-to-network relay UE and / or when the service authorization of the initiating UE is revoked after receiving the configuration parameters.

[0415] In addition, the 5G ProSe layer-2 UE-to-network relay UE may be a UE capable of 5G ProSe or direct C2 communication that provides functionality to support network connectivity for a 5G ProSe layer-2 remote UE via a layer 2 protocol.

[0416] Additionally, a 5G ProSe layer-3 UE-to-network relay UE may be a UE capable of 5G ProSe or direct C2 communication that provides functionality to support network connectivity for a 5G ProSe layer-3 remote UE via a layer 3 protocol.

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

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

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

[0420] This procedure may be executed after or based on the completion of any of the USS-initiated procedures described below (Section 3.3.7). Furthermore, this procedure may be executed based on the completion of the PDU session change procedure executed in any of the various USS-initiated procedures or the completion of any of the PDU session change procedures.

[0421] The procedures include a ProSe direct link release procedure and a PC5 unicast link release procedure. Here, the ProSe direct link release procedure may be a procedure for releasing a ProSe direct link established for direct C2 communication. Also, the PC5 unicast link release procedure may be a procedure for releasing a PC5 unicast link established for direct C2 communication. In other words, the procedures may be a procedure for releasing a ProSe direct link or a PC5 unicast link that has already been established for direct C2 communication.

[0422] These are explained in Sections 3.3.6.1 and 3.3.6.2 below, respectively.

[0423] [3.3.6.1. ProSe direct link release procedure] This section describes the ProSe direct link release procedure. Note that the start of this procedure is based on the description in Section 3.3.6.

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

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

[0426] Here, the initiating UE may select and decide whether to include various identification information in the first control message based on subscriber information, and / or network status, and / or user registration information, and / or context held by the UE, etc.

[0427] The initiating UE may also request release of the direct C2 communication with the target UE by sending a first control message.

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

[0429] 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) contained in the first control message.

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

[0431] Here, the second control message may be a message accepting the release of the direct C2 communication, and may be a ProSe direct link release accept message.

[0432] The second control message may be a response message to the first control message, and may indicate that the first control message has been accepted.

[0433] Here, the target UE may indicate that at least a portion of the initiating UE's request in the first control message has been accepted by sending a second control message.

[0434] In addition, by transmitting the second control message, the target UE may indicate that the target UE supports each function, may indicate that the request from the initiating UE has been accepted, may indicate that the request from the initiating UE has not been allowed, or may indicate a combination of these.

[0435] The initiating UE then receives a second control message from the target UE.

[0436] When the initiating UE receives the second control message, it can recognize that the UE's request in the first control message has been accepted and / or the contents of the information, etc. (message, container, identification information) contained in the second control message.

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

[0438] [3.3.6.2. PC5 unicast link release procedure] This section describes the PC5 unicast link release procedure. Note that the start of this procedure is based on the explanation in Section 3.3.7.

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

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

[0441] Here, the initiating UE may select and decide whether to include various identification information in the first control message based on subscriber information, and / or network status, and / or user registration information, and / or context held by the UE, etc.

[0442] The initiating UE may also request release of the direct C2 communication with the target UE by sending a first control message.

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

[0444] 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) contained in the first control message.

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

[0446] Here, the second control message may be a message accepting the release of the direct C2 communication, or may be a direct link release accept message.

[0447] The second control message may be a response message to the first control message, and may indicate that the first control message has been accepted.

[0448] Here, the target UE may indicate that at least a portion of the initiating UE's request in the first control message has been accepted by sending a second control message.

[0449] In addition, by transmitting the second control message, the target UE may indicate that the target UE supports each function, may indicate that the request from the initiating UE has been accepted, may indicate that the request from the initiating UE has not been allowed, or may indicate a combination of these.

[0450] The initiating UE then receives a second control message from the target UE.

[0451] When the initiating UE receives the second control message, it can recognize that the UE's request in the first control message has been accepted and / or the contents of the information, etc. (message, container, identification information) contained in the second control message.

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

[0453] [3.3.7. USS-led Procedures] Next, we will explain the procedure led by the USS. The procedure led by the USS is also referred to as the procedure in this section. Note that the procedure led by the USS may be led by either the USS or the UTM.

[0454] Here, this procedure is a procedure initiated by the USS when the USS determines that the conditions of each procedure are satisfied, and a network- or UE-initiated session management procedure may be performed during this procedure. Furthermore, the session management procedure performed during this procedure may be a network requested PDU session release procedure or a network requested PDU session modification procedure.

[0455] Here, the procedure initiated by the USS may be, but is not limited to, a Revocation of C2 Connectivity procedure or a UUAA Revocation procedure, or may be, but is not limited to, a UAV-C replacement procedure or a C2 pairing policy configuration.

[0456] As an example of this procedure, the UUAA procedure is described in the next section.

[0457] [3.3.7.1. UUAA] This section describes the outline of the UUAA (USS UAV Authorization / Authentication) procedure. Hereinafter, the UUAA procedure may be referred to as UUAA or this procedure.

[0458] This procedure is for authentication and / or authorization of the UE by the USS. Note that authorization for C2 communication may be performed during the UUAA procedure.

[0459] This procedure may be initiated by the network or by the UE.

[0460] The UUAA may be a UUAA-MM procedure performed when registering with 5GS. The UUAA may be a UUAA-SM procedure performed during PDU session establishment. The UUAA may be an MM procedure or an SM procedure. The procedure used in the UUAA may be an MM procedure or an SM procedure.

[0461] Also, if UUAA-MM is not implemented, UUAA-SM may be implemented.

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

[0463] Note that a successful UUAA may be interpreted as authentication and authorization of the UAV being permitted, and a failed UUAA may be interpreted as authentication and authorization of the UAV not being permitted.

[0464] In addition, "certification and approval of the UAV is permitted" may be read as "the UAV is certified and approved." In addition, "certification and approval of the UAV is not permitted" may be read as "the UAV is not certified and approved."

[0465] In addition, the term "authentication and authorization of a UAV is successful" may be read as "the UAV is authenticated and authorized." In addition, the term "authentication and authorization of a UAV is unsuccessful" may be read as "the UAV is not authenticated and authorized."

[0466] In addition, "certification and approval of the USS has been permitted" may be read as "the UAV has been certified and approved." In addition, "certification and approval of the USS has not been permitted" may be read as "the UAV has not been certified and approved."

[0467] [3.3.7.1.1. UUAA-MM] Next, the UUAA-MM procedure will be described with reference to Fig. 12. Hereinafter, the UUAA-MM procedure will be referred to as UUAA-MM or this procedure. This procedure may be a procedure performed when registering with 5GS.

[0468] The UUAA-MM procedure may be performed during or after the 5GS registration procedure. In other words, the first communication during the UUAA-MM procedure described below and the above-mentioned registration procedure may be collectively referred to as the registration procedure, or the first communication during the UUAA-MM procedure described below may be a procedure independent of the above-mentioned registration procedure.

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

[0470] UUAA-MM may be optional. UUAA-MM may be performed for a UE that requests authentication and authorization of the UAV by the USS when registering with 5GS. UUAA-MM may be performed by the AMF. UUAA-MM may be performed during UE registration based on local network policy if the UE has an airborne UE subscription with 5GS and if the UE provides the CAA-Level UAV ID of the UAV in the registration request message. UUAA-MM may be performed when the USS that authorized the UAV performs re-authentication.

[0471] The UE may also be authenticated and authorized by the USS using the CAA-Level UAV ID and credentials associated with the CAA-Level UAV ID. During UUAA-MM, the AMF may also communicate with the USS via the UAS NF and forward authentication messages between the UE and the UAS NF.

[0472] Next, we will explain each step of UUAA-MM.

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

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

[0475] Here, the UE and / or the AMF may recognize whether the UUAA-MM is successful through the message of the first communication. In other words, the UE and / or the AMF may recognize whether the authentication and authorization of the UAV is allowed through the message of the first communication.

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

[0477] Furthermore, the fifth condition determination may be performed based on receipt of a message 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 context held by the AMF, etc.

[0478] For example, if UUAA-MM is successful, the fifth condition determination may be true, and if UUAA-MM is unsuccessful, the fifth condition determination may be false. Furthermore, if the identification information to be transmitted and received is permitted, the fifth condition determination may be true, and if the identification information to be transmitted and received is not permitted, the fifth condition determination may be false. Note that the conditions that determine whether the fifth condition determination is true or false do not have to be limited to the conditions described above.

[0479] The AMF may also indicate the result of UUAA-MM to the UE by a procedure performed depending on the truth or falsity of the fifth condition determination.

[0480] Each device may also complete this procedure based on the first communication, and / or the performance of a UE configuration update procedure, and / or a de-registration procedure.

[0481] The UE may also recognize the result of UUAA-MM through the procedure of (A) or (B) in Figure 12. In other words, the UE may recognize the result of UUAA-MM through a message received in the procedure of (A) or (B) in Figure 12. The UE may also recognize the result of UUAA-MM based on the completion of this procedure.

[0482] In addition, if approval of C2 communication is performed during the UUAA-MM procedure, the UE may be aware of the results of approval of C2 communication and / or pairing of the UAV with the UAV-C, and / or flight approval of the UAV.

[0483] The UE may be prohibited from transmitting MM messages and / or SM messages during the UUAA-MM procedure, i.e., the UE may be controlled not to transmit MM messages and / or SM messages until the first communication and / or the UE configuration update procedure and / or the de-registration procedure are completed.

[0484] [3.3.7.1.2. UUAA-SM] Next, the UUAA-SM procedure will be described with reference to Fig. 13. Hereinafter, the UUAA-SM procedure will be referred to as UUAA-SM or this procedure. This procedure may be a procedure that is performed while a PDU session is being established.

[0485] Furthermore, the messages sent and received in this procedure may have the same behavior as described in the PDU session establishment procedure chapter.

[0486] In addition, when the UE requests establishment of a PDU session, the PDU session may require UUAA authentication of the UAV.

[0487] Also, when the UUAA is revoked, all PDU sessions associated with the UAV may be released, in other words, when the authentication and authorization of the UAV is revoked, all PDU sessions associated with the UAV may be released.

[0488] The UUAA-SM may also be performed by the SMF during the PDU session establishment procedure and 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.

[0489] Next, we will explain each step of UUAA-SM.

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

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

[0492] Here, the UE and / or the SMF may know whether the UUAA-SM is successful through the message of the second communication. In other words, the UE and / or the SMF may know whether the authentication and authorization of the UAV is allowed through the message of the second communication.

[0493] Next, the SMF can execute a sixth condition determination. The sixth condition determination is for the network (or SMF) to determine whether the UUAA-SM is successful or not. If the sixth condition determination is true, the SMF transmits the PDU session establishment acceptance message of Fig. 13(A) (S2604), whereas if the sixth condition determination is false, the SMF transmits the PDU session establishment rejection message of Fig. 13(B) (S2606).

[0494] Furthermore, the sixth condition determination may be performed based on receipt of a message used in the second 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 context held by the AMF, etc.

[0495] For example, if UUAA-SM is successful, the sixth condition determination may be true, and if UUAA-SM is unsuccessful, the sixth condition determination may be false. Furthermore, if the identification information to be transmitted and received is permitted, the sixth condition determination may be true, and if the identification information to be transmitted and received is not permitted, the sixth condition determination may be false. Note that the conditions that determine whether the sixth condition determination is true or false do not have to be limited to the above-mentioned conditions.

[0496] The SMF may also indicate the result of the UUAA-SM to the UE by a message sent depending on the truth or falsity of the sixth condition determination.

[0497] Furthermore, each device may complete the procedure based on performing a second communication, and / or sending and receiving a PDU session accept message, and / or sending and receiving a PDU session rejection message.

[0498] The UE may also recognize the result of the UUAA-SM by receiving the message of (A) or (B) in Figure 13. The UE may also recognize the result of the UUAA-SM based on the completion of this procedure.

[0499] In addition, if approval of C2 communication is performed during the UUAA-SM procedure, the UE may be aware of the results of approval of C2 communication and / or pairing of the UAV with the UAV-C, and / or approval of the flight of the UAV.

[0500] The UE may be prohibited from transmitting MM messages and / or SM messages during the UUAA-SM procedure, i.e., the UE may be controlled not to transmit MM messages and / or SM messages until the second communication and / or PDU session establishment procedure is completed.

[0501] [3.3.7.1.3. UUAA Cancellation Procedure] Next, the UUAA revocation procedure will be described with reference to Fig. 14. Hereinafter, the UUAA revocation procedure will be referred to as UUAA revocation, or UAV authorization revocation procedure, or this procedure. This procedure may be performed during the registration procedure and / or during PDU session establishment.

[0502] This procedure may also be a procedure initiated by the core network or the USS, or a procedure for the network or the USS to revoke authentication and authorization of the UAV to the UE.

[0503] Next, each step of this procedure will be explained.

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

[0505] Next, the core network may initiate the procedures (S2802) and (S2804) of FIG. 14(A), or may initiate the procedure (S2806) of FIG. 14(B).

[0506] Furthermore, the core network may determine whether to perform the procedure (A) of Figure 14 or the procedure (B) of Figure 14 based on reception of a message 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 context held by the AMF, etc.

[0507] For example, if UUAA-MM has been performed, the procedure in (A) of Fig. 14 may be performed. Also, if UUAA-SM has been performed, the procedure in (B) of Fig. 14 may be performed. Note that the decision as to whether to perform (A) or (B) of Fig. 14 does not have to be limited to the above-mentioned conditions.

[0508] The core network may also indicate to the UE the revocation of authentication and authorization of the UAV by performing the procedure of (A) or (B) of Figure 14.

[0509] Each device may also complete this procedure based on the fourth communication and / or implementation of the procedure of (A) or (B) of FIG.

[0510] The UE may also recognize the revocation of certification and approval of the UAV based on the completion of this procedure.

[0511] [3.3.8. DAA and Related Procedures] Next, the DAA and related procedures will be described with reference to Figure 15. Hereinafter in this chapter, the DAA and related procedures will also be referred to as the present procedures.

[0512] Here, the DAA and related procedures may be procedures that are composed of and executed in combination with any one or more of the following: registration procedure and / or first communication, PDU session establishment procedure and / or second communication (S3000) (S3002), first broadcast (S3004), second broadcast (S3006), and DAA communication (S3010) executed between the UE (UAV) or the UE (AAM) and the NW and USS.

[0513] Here, each procedure executed during this procedure may be the procedure described in Chapter 3.3, and each terminal and device may transmit and receive the identification information described in each chapter. Here, for example, the registration procedure (S3000) (S3002) may be the procedure described in Chapter 3.3.1. For example, the first communication (S3000) (S3002) may be the procedure described in Chapter 3.3.7.1, more specifically, the procedure in 3.3.7.1.1. For example, the second communication (S3000) (S3002) may be the procedure described in Chapter 3.3.7.1, more specifically, the procedure in 3.3.7.1.2. For example, the PDU session establishment procedure (S3000) (S3002) may be the procedure described in Chapter 3.3.2. Also, for example, the direct link establishment procedure (S3008) may be the procedure described in Chapter 3.3.5.

[0514] Also, for example, in the procedure (S3002) performed between the UE (AAM) and the network or USS, the first communication and / or the second communication may or may not be performed.

[0515] The following describes in detail the first broadcast (S3004), the second broadcast (S3006), the direct link establishment procedure (S3008), and the DAA communication (S3010). For the direct link establishment procedure, the following describes in detail the behavior based on the identification information transmitted and received in the first broadcast and / or the second broadcast.

[0516] [3.3.8.1. First broadcast] Next, the first broadcast will be described. Hereinafter, the first broadcast will also be referred to as this procedure. This procedure may be a procedure executed based on the MBS procedure described in Non-Patent Document 9.

[0517] This procedure may be initiated by the USS / UTM requesting the establishment of a broadcast session to the NEF and / or MBSF (Multicast / Broadcast Service Function) in the 5G network when a session for the first broadcast has not been established.

[0518] This procedure may be initiated when the USS / UTM receives a report of a remote ID from a UAV without a session being established for broadcasting. The RID broadcasted in the first broadcast may be the NRID.

[0519] Note that the broadcasting of the message via the broadcast link established in this procedure may be as shown in S3004 of FIG.

[0520] In addition, using the session for the first broadcast established in this procedure, the USS / UTM may broadcast a message including the UAV's remote ID, and / or the 21st identification information, and / or the 22nd identification information, and / or information on whether or not the PC5 direct communication function is supported, etc. In addition, the AAM may receive the broadcasted message from the USS / UTM.

[0521] Furthermore, the AAM receiving the message in the first broadcast may determine whether to perform a direct link establishment procedure based on the UAV's remote ID, and / or the 21st identification information, and / or the 22nd identification information, and / or whether or not the PC5 direct communication function is supported, etc.

[0522] More specifically, for example, when the 21st identification information is received, the AAM may determine whether or not to execute a direct link establishment procedure. Also, when the 22nd identification information is received, the AAM may determine whether or not to execute a direct link establishment procedure. Also, when the 22nd identification information is received, the AAM may store the 22nd identification information. Also, when the 22nd identification information is received, the AAM may update the 22nd identification information stored in the AAM. Also, when the AAM determines not to execute a direct link establishment procedure, the AAM may delete the 22nd identification information stored in the AAM. Also, when the AAM determines not to execute a direct link establishment procedure, the AAM may delete information related to the UAV stored in the AAM.

[0523] The direct link establishment procedure will be described later.

[0524] [3.3.8.2. Secondary Broadcast] Next, the second broadcast will be described. Hereinafter, the second broadcast will also be referred to as the main procedure.

[0525] In addition, this procedure does not necessarily involve the establishment of a communication path for broadcasting, but may be a procedure executed by a UE (UE, UAV, UAV-C, AAM) authorized by the network based on a policy authorized by the network.

[0526] This procedure may be performed based on broadcasting supported by E-UTRA-PC5 or NR-PC5 between UAVs or between a UAV and an AAM. Furthermore, the broadcasting according to this procedure may be as shown in S3006 of Fig. 15. Furthermore, the RID transmitted in this procedure may be a BRID.

[0527] In addition, the UAV may broadcast a message, packet, or data including information such as the UAV's remote ID, and / or the 21st identification information, and / or the 22nd identification information in the second broadcast. Note that the broadcast information in this procedure may or may not include information about the DAA. The AAM may receive the broadcast message from the UAV.

[0528] Further, the AAM receiving information in the second broadcast may determine whether to perform a direct link establishment procedure based on the UAV's remote ID, and / or the 21st identification information, and / or the 22nd identification information, etc.

[0529] More specifically, for example, when the 21st identification information is received, the AAM may determine whether or not to execute a direct link establishment procedure. Also, when the 22nd identification information is received, the AAM may determine whether or not to execute a direct link establishment procedure. Also, when the 22nd identification information is received, the AAM may store the 22nd identification information. Also, when the 22nd identification information is received, the AAM may update the 22nd identification information stored in the AAM. Also, when the AAM determines not to execute a direct link establishment procedure, the AAM may delete the 22nd identification information stored in the AAM. Also, when the AAM determines not to execute a direct link establishment procedure, the AAM may delete information related to the UAV stored in the AAM.

[0530] The direct link establishment procedure will be described later.

[0531] [3.3.8.3. Direct link establishment procedure] Next, the direct link establishment procedure will be described. Hereinafter, the direct link establishment procedure will also be referred to as this procedure. The direct link establishment procedure may be the procedure of S3008 in FIG. 15. Note that this procedure may be a procedure for establishing a communication path for direct communication between UAVs and / or between a UAV and an AAM for communication of the DAA.

[0532] Furthermore, this procedure may be a procedure initiated by the AAM to establish a direct communication path with the UAV, and may be a procedure that is determined and initiated or executed by the AAM based on information contained in the first broadcast and / or the second broadcast.

[0533] This procedure may be initiated when the AAM receives the 21st identification information, and / or the 22nd identification information, and / or the PC5 direct communication function in the first broadcast during the procedure of (A) of Figure 15 and recognizes that the UAV supports the DAA function and the PC5 direct communication function.

[0534] Alternatively, this procedure may be initiated when the AAM receives the 21st identification information and / or the 22nd identification information via the PC5 direct communication path in the first broadcast during the procedure of (A) of Figure 15 and recognizes that the UAV supports the DAA function.

[0535] Furthermore, the AAM may determine to start this procedure based on the 21st identification information, and / or the 22nd identification information, and / or information regarding support of the PC5 direct communication function received in either the first broadcast or the second broadcast, or may determine to start this procedure based on the 21st identification information, and / or the 22nd identification information, and / or information regarding support of the PC5 direct communication function received from both the first broadcast and the second broadcast.

[0536] This procedure may be performed based on the direct link establishment procedure described in Section 3.3.5. The direct link establishment procedure in this section may be a direct link establishment procedure for C2 communication, a direct link establishment procedure for non-C2 communication, or a direct link establishment procedure for DAA communication.

[0537] Although the establishment of a direct communication path for C2 communication has been described in Section 3.3.5, the direct communication path in this procedure is not limited to the communication path for C2 communication, and detailed description will be omitted in this section.

[0538] [3.3.8.4. DAA Communication] Next, the DAA communication will be described. Hereinafter, the DAA communication will also be referred to as the main communication.

[0539] The AAM and UE that have completed the direct link establishment procedure (S3008) described in Figure 15 may perform communication for DAA via a direct communication path via PC5 established in the direct link establishment procedure.

[0540] Here, in the DAA communication, the UAV may transmit messages, packets, data, or the like related to the DAA communication to the AAM via a direct communication path. Furthermore, the UAV may transmit its own capability information to the AAM via the direct communication path, for example, the UE may transmit the DAA capability and / or the U2X capability including the DAA capability and / or the U2X capability not including the DAA capability. Furthermore, the UAV may transmit information on the associated UAV-C, for example, may transmit pairing information including the UAV-C ID or address information of the UAV-C stored in the UAV.

[0541] Furthermore, when the need for this communication is eliminated, the UAV or AAM may execute a procedure for opening the established communication path for direct communication. Here, the procedure for opening the communication path for direct communication may be initiated or executed based on the procedure in Section 3.3.6. Furthermore, the procedure for opening the communication path for direct communication may be initiated by either the UAV or the AAM. In other words, the procedure for opening the communication path for direct communication may be initiated or executed by the UAV or the AAM.

[0542] [4. Embodiment] Next, an embodiment of the present invention will be described.

[0543] In addition, in this embodiment, the initiating UE may be an AAM, and the target UE may be a UAV.

[0544] In addition, for each embodiment, the behavior of each terminal or device when the AAM receives a message including the UAV's remote ID, and / or the 21st identification information, and / or information regarding support for the PC5 direct communication function in the first broadcast and / or the second broadcast will be described. Also, the message transmitted in the second broadcast does not need to include information indicating whether or not the PC5 direct communication function is supported.

[0545] [4.1. First embodiment] A first embodiment of the present invention will be described with reference to FIG. 15. In this section, the first embodiment will also be referred to as the present embodiment. The contents of the various procedures used in this embodiment are based on the procedures described in Section 3.3. In this section, only the features of this embodiment will be described. Although the description of UAV-C is omitted in FIG. 15, as described in Section 3.3, UAV-C may also perform registration procedures, PDU session establishment procedures, UUAA procedures, etc. before the procedure (A) in this embodiment, like other UEs (UAVs and / or AAMs).

[0546] In this embodiment, the first broadcast and / or the second broadcast message may not include the 22nd identification information. In addition, the second broadcast message may not include information indicating support for the PC5 direct communication function. In other words, the first broadcast and / or the second broadcast message in this embodiment may include the remote ID and the 21st identification information of the UAV.

[0547] This embodiment is an embodiment in which the 21st identification information included in the message received by the AAM is capability information indicating that the UAV does not support DAA. In other words, the AAM may receive a first broadcast and / or a second broadcast message including the 21st identification information indicating that the UAV does not support DAA. The AAM that receives the 21st identification information indicating that the UAV does not support DAA may recognize that the UAV does not support DAA and may decide not to perform the subsequent procedure.

[0548] That is, when the AAM or UE operating as an AAM in this embodiment receives a message, packet or data including 21st identification information indicating that the UAV does not support DAA in the first broadcast (S3004) and / or the second broadcast (S3006), the AAM does not need to perform a direct link establishment procedure (S3008) with the UAV.

[0549] In other words, an AAM that receives a message from a network and / or UAV including a 21st identification information, which is capability information indicating that the UAV does not support DAA, may recognize that the UAV does not support DAA based on the reception of the 21st identification information or the content of the received 21st identification information, and may not need to initiate or perform a direct link establishment procedure with the UAV.

[0550] [4.2. Second embodiment] A second embodiment of the present invention will be described. In this section, the second embodiment will also be referred to as the present embodiment. The contents of the various procedures used in this embodiment are based on the procedures described in section 3.3. In this section, only the features of this embodiment will be described.

[0551] In this embodiment, the message received by the AAM may include the 21st identification information and / or the 22nd identification information indicating that the UAV supports DAA. In other words, the AAM may receive a first broadcast and / or a second broadcast message including the 21st identification information and / or the 22nd identification information indicating that the UAV supports DAA. Since the first broadcast and / or the second broadcast message includes the 21st identification information and / or the 22nd identification information indicating that the UAV supports DAA, the AAM may decide to initiate a direct link establishment procedure as a subsequent procedure.

[0552] That is, when the AAM or a UE operating as an AAM in this embodiment receives a message, packet or data including 21st identification information indicating that the UAV supports DAA in the first broadcast (S3004) and / or the second broadcast (S3006), the AAM may perform a direct link establishment procedure (S3008) with the UAV.

[0553] In other words, an AAM that receives a message from a network and / or UAV including a 21st identification information, which is capability information indicating that the UAV supports DAA, may recognize that the UAV supports DAA based on the reception of the 21st identification information or the content of the received 21st identification information, and may initiate or perform a direct link establishment procedure with the UAV.

[0554] [4.3. Third embodiment] A third embodiment of the present invention will be described. In this section, the third embodiment will also be referred to as the present embodiment. The contents of the various procedures used in this embodiment are based on the procedures described in section 3.3. In this section, only the features of this embodiment will be described.

[0555] In this embodiment, the message received by the AAM may include the 21st identification information indicating that the UAV supports DAA. In other words, the AAM may receive the first broadcast and / or the second broadcast message including the 21st identification information indicating that the UAV supports DAA. Since the first broadcast and / or the second broadcast message includes the 21st identification information and / or the 22nd identification information indicating that the UAV supports DAA, the AAM may decide to start a direct link establishment procedure as a subsequent procedure.

[0556] That is, when the AAM of this embodiment receives a message, packet, or data including the 22nd identification information in the first broadcast (S3004) and / or the second broadcast (S3006), the AAM may execute a direct link establishment procedure (S3008). Here, the AAM may use a destination Layer-2 ID, which is the identification information on the network of the UAV indicated by the 22nd identification information received from the network and / or the UAV in the direct link establishment procedure, or the like. In other words, the AAM may start or execute a direct link establishment procedure for the UAV by transmitting a message including the 22nd identification information. Here, the AAM may include the identification information on the network of the UAV indicated by the 22nd identification information in the message as the destination and transmit it. In addition, the message in which the AAM includes the 22nd identification information may be a Direct Communication Request (DCR) message.

[0557] In other words, the AAM that receives a message including the 22nd identification information from the network and / or UAV may recognize that the UE supports the DAA function based on the reception or content of the 21st identification information, and may initiate or perform a direct link establishment procedure with the UAV by sending a message including the 22nd identification information received by the AAM to the UAV.

[0558] [4.4. Fourth embodiment] A fourth embodiment of the present invention will be described. In this section, the fourth embodiment will also be referred to as the present embodiment. The contents of the various procedures used in this embodiment are based on the procedures described in section 3.3. In this section, only the features of this embodiment will be described.

[0559] In this embodiment, the message received by the AAM may include the 21st identification information and / or the 22nd identification information indicating that the UAV supports DAA. In other words, the AAM may receive a first broadcast and / or a second broadcast message including the 21st identification information and / or the 22nd identification information indicating that the UAV supports DAA. Since the first broadcast and / or the second broadcast message includes the 21st identification information and / or the 22nd identification information indicating that the UAV supports DAA, the AAM may decide to initiate a direct link establishment procedure for the UAV as a subsequent procedure.

[0560] That is, when the AAM of this embodiment receives the 21st identification information and / or the 22nd identification information indicating that the UAV supports DAA in the first broadcast (S3004) and / or the second broadcast (S3006), the AAM may execute a direct link establishment procedure (S3008) for the UAV. In addition, when the 22nd identification information is received, the AAM may send a message including the identification information on the network of the UAV indicated by the 22nd identification information as the destination in the direct link establishment procedure for the UAV. In addition, the message in which the AAM includes the 22nd identification information may be a Direct Communication Request (DCR) message.

[0561] In other words, when an AAM receives a message including the 21st identification information and / or the 22nd identification information, which are capability information indicating that the UAV supports DAA, from the network and / or the UAV, the AAM may recognize that the UAV supports DAA based on the reception or content of the received 21st identification information and / or the 22nd identification information, and may initiate or execute a direct link establishment procedure with the UAV. Furthermore, when the AAM receives the 22nd identification information, the AAM may initiate or execute a direct link establishment procedure with the UAV by sending a message including the received 22nd identification information to the UAV. Here, the 22nd identification information may be included in the message as the destination of the message.

[0562] 5. Variations 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 cause a computer to function so as to realize the functions of an embodiment according to an aspect of the present invention. The program or information handled by the program is temporarily stored in a volatile memory such as a Random Access Memory (RAM), a non-volatile memory such as a flash memory, a Hard Disk Drive (HDD), or other storage device system.

[0563] A program for implementing the functions of the embodiment according to one aspect of the present invention may be recorded on a computer-readable recording medium. The program may be implemented by loading the program recorded on the recording medium into a computer system and executing it. The term "computer system" as used herein refers to a computer system built into an apparatus, and includes hardware such as an operating system and peripheral devices. The term "computer-readable recording medium" may be a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a medium that dynamically holds a program for a short period of time, or any other recording medium that can be read by a computer.

[0564] In addition, each functional block or feature of the device used in the above-mentioned embodiment may be implemented or performed by an electric circuit, for example, an integrated circuit or a plurality of integrated circuits. The electric circuit designed to perform the functions described herein may include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or a combination thereof. The general-purpose processor may be a microprocessor, or a conventional processor, controller, microcontroller, or state machine. The electric circuit described above may be composed of a digital circuit or an analog circuit. In addition, when a technology for integrated circuitization that replaces current integrated circuits appears due to the progress of semiconductor technology, one or more aspects of the present invention may use a new integrated circuit based on that technology.

[0565] The present invention is not limited to the above-mentioned embodiment. In the embodiment, one example of the device is described, but the present invention is not limited to this and can be applied to stationary or non-movable electronic devices installed indoors or outdoors, such as terminal devices or communication devices of AV equipment, kitchen equipment, cleaning / washing equipment, air conditioners, office equipment, vending machines, and other household appliances.

[0566] Although the embodiments of the present invention have been described above in detail with reference to the drawings, the specific configuration is not limited to this embodiment, and design changes and the like within the scope of the gist of the present invention are also included. Furthermore, the present invention can be modified in various ways within the scope of the claims, and embodiments obtained by appropriately combining the technical means disclosed in different embodiments are also included in the technical scope of the present invention. Furthermore, configurations in which elements described in the above embodiments are replaced with elements that have the same effect are also included. [Explanation of symbols]

[0567] 1 Mobile communication systems 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

[Claim 1] A UE (User Equipment) including a transceiver unit and a control unit, The UE operates as an AAM (Area Airspace Manager), The transceiver receives a message including first information and second information from a UAV (Uncrewed Aerial Vehicle), The first information is capability information indicating that the UAV supports DAA (Detect And Avoid), The second information is a CCA-level UAV ID assigned to the UAV associated with the first information; The control unit initiates a procedure for establishing a communication path for direct communication with the UAV using the second information based on the reception of the first information. A UE characterized by:

Images