Direct C2 communication establishment, modification and revocation

Abstract

Systems and methods for commanding and controlling (C2) communication setup, modification, and / or revocation are described herein. The C2 communication may be a direct C2 communication. The C2 authorization may be performed by a wireless transmit and receive unit (WTRU) (e.g., an unmanned (unmanned reconnaissance) aircraft (UAV)). For example, if the WTRU sends a C2 communication request, C2 authorization may be performed by the WTRU. The C2 communication request may be sent to an unmanned (unmanned reconnaissance) air system (UAS) service provider (USS) during packet data unit (PDU) session establishment and / or modification, such as via a UAS network function (NF). For example, after successful authorization, the WTRU may perform discovery of a peer-to-peer WTRU.

Description

[0001] This application is a divisional application of the Chinese invention patent application with an application date of November 4, 2022, application number 202280080382.6 (international application number PCT / US2022 / 048970), and invention name “Direct C2 communication establishment, modification and cancellation”.

[0002] CROSS-REFERENCE TO RELATED APPLICATIONS

[0003] This application claims the benefit of U.S. Provisional Application No. 63 / 276,264, filed on November 5, 2021, the entire contents of which are incorporated herein by reference. Background Art

[0004] Mobile communications using wireless communications continue to evolve. The fifth generation may be referred to as 5G. Previous (legacy) mobile communications may be, for example, fourth generation (4G) Long Term Evolution (LTE). Summary of the invention

[0005] Systems and methods for command and control (C2) communication establishment, modification and / or revocation are described herein. The C2 communication may be a direct C2 communication. C2 authorization may be performed by a wireless transmission and reception unit (WTRU), such as an unmanned (unmanned reconnaissance) aerial vehicle (UAV). For example, if the WTRU sends a C2 communication request, the C2 authorization may be performed by the WTRU. The C2 communication request may be sent to an unmanned (unmanned reconnaissance) aerial system (UAS) service provider (USS), such as via a UAS network function (NF) during a packet data unit (PDU) session establishment and / or modification. For example, after successful authorization, the WTRU may perform discovery of peer WTRUs.

[0006] For example, the WTRU may perform C2 communication (e.g., direct C2 communication) establishment, modification, and / or revocation. The WTRU (e.g., UAV, UAV-C, etc.) may send an authorization request (e.g., C2 authorization request on PC5) during PDU session establishment and / or modification. The authorization request may correspond to C2 communication, such as direct or line-of-sight C2 communication. The WTRU may receive authorization for direct C2 from the USS (e.g., in an authorization response), for example, via a PDU session modification or a separate PDU setup response message. The authorization may include authorization information. The WTRU may receive C2 authorization parameters (e.g., in an air container to facilitate a discovery procedure with the UAV-C (e.g., UAS application user ID, discovery credentials, etc.), for example, to be used as part of direct discovery (e.g., open or restricted direct discovery). The WTRU may perform (e.g., start) discovery. In an example, the WTRU may perform discovery if the WTRU receives C2 authorization information from the USS. The WTRU may use parameters from the USS to enable discovery of the UAV-C.

[0007] In one example, a network function (NF) may perform C2 communication (e.g., direct C2 communication) establishment, modification, and / or revocation. The NF (e.g., UAS NF) may receive an authorization request from a session management function (SMF), for example, to enable PC5 via C2. The UAS NF may forward the authorization request to the USS. The UAS NF may receive an authorization response from the USS indicating that C2 on PC5 is authorized. The UAS NF may store the authorization information. The UAS NF may forward the authorization response to the SMF.

[0008] For example, a management function (e.g., a Direct Discovery Name Management Function (DDNMF)) may perform a direct discovery procedure for a UAV / UAV-C. The DDNMF may receive a discovery request. The discovery request may include a UAS ProSe application ID (e.g., set to a CAA level ID), a WTRU ID, etc. The DDNMF may utilize unified data management (UDM) to check authorization for discovery of the UAS ProSe application ID. The DDNMF may interact with the UAS NF, for example, based on associated subscription data (e.g., the UAS application ID is associated with the USS / UAS application). The DDNMF may send a request message for discovery authorization to the UAS NF. The DDNMF may receive a response message from the UAS NF. The response message may include authorization information for discovery, such as an authorization flag or a UAS discovery code. The DDNMF may send a discovery response message (e.g., to the UAV). The discovery response message may include UAS information for discovery.

[0009] In an example, a first WTRU may send a first message to a network node indicating a C2 authorization request and a request for a PDU session. The first WTRU may receive a second message from the network node indicating that the PDU session has been established. The second message may indicate a C2 authorization and C2 authorization information. The first WTRU may determine that the first WTRU is authorized to communicate with the second WTRU based on the C2 authorization and the C2 authorization information. The C2 authorization information may include security credentials (e.g., an authorization token) and the identity of the second WTRU. For example, if the first WTRU is authorized to communicate with the second WTRU, the first WTRU may send a third message to the second WTRU using PC5. The third message may be protected based on the security credentials (e.g., authenticated and / or encrypted using the security credentials). The third message may indicate a request to perform a discovery procedure and / or a link establishment procedure.

[0010] In an example, a network node (e.g., a UAS NF) may send a first message indicating a request for authorization associated with the WTRU to a second network node. The network node may receive a second message indicating a response to the request, indicating policy configuration information, and / or indicating security credentials associated with the WTRU. The network node may determine that the WTRU is authorized to establish C2 over PC5 (e.g., based on the second message). The network node may determine, for example, discovery authorization parameters based on the second message. The network node may send a third message to the WTRU indicating the discovery authorization parameters.

[0011] In an example, a network node (e.g., a UAS NF) may receive a first message indicating an authorization request associated with discovery. The authorization request may indicate a subscription identifier associated with the first WTRU, a UAV identifier, a request type, an application level container, etc. The request type may indicate whether the discovery is open or restricted. The network node may determine that the first WTRU is authorized to operate as a UAV and / or is authorized to perform C2 communications. The network node may determine that the first WTRU is authorized, for example, based on a received indication (e.g., from a USS). The network node may send a second message indicating an authorization response (e.g., associated with the first message), the authorization response indicating that the WTRU is authorized to operate as a UAV. The second message may indicate that the first WTRU is authorized to perform open discovery (e.g., if the request type is associated with open discovery). The second message may indicate that the first WTRU is authorized to perform restricted discovery (e.g., if the request type is associated with restricted discovery). The network node may determine parameters (e.g., restricted discovery parameters for restricted discovery, open discovery parameters for open discovery), for example, based on the request type.

[0012] The discovery request may be a discovery request for monitoring. The discovery request for monitoring may indicate a subscription identifier, a UAV identifier, a Prose Discovery UE Identifier (PDUID) associated with the first WTRU, a target subscription identifier, a target UAV identifier, and / or a target PDUID associated with the second WTRU. The network node may send a message indicating a monitoring response. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] Figure 1A is a system diagram illustrating an example communication system in which one or more disclosed embodiments may be implemented.

[0014] Figure 1B It is shown that according to the embodiment, Figure 1A A system diagram of an example wireless transmit / receive unit (WTRU) for use within a communication system is shown.

[0015] Figure 1C It is shown that according to the embodiment, Figure 1A System diagram of an example radio access network (RAN) and an example core network (CN) for use within a communication system is shown.

[0016] Figure 1D It is shown that according to the embodiment, Figure 1A A system diagram of another example RAN and another example CN used within the communication system is shown.

[0017] Figure 2 An example overview of C2 direct communications through PC5 is shown.

[0018] Figure 3 An example UAV and UAV-C communication network using one or more PLMNs is shown.

[0019] Figure 4 An example is shown of PC5 communicating directly with C2 authorization which can then perform discovery.

[0020] Figure 5 An example PC5 is shown communicating directly with a UAS peer discovery which may then proceed to C2 authorization.

[0021] Figure 6 An example C2 authorization involving the PCF and USS via the UAS NF is shown.

[0022] Figure 7 An example Notification Request procedure contacting the USS via the V / Home PLMN is shown (Roaming / Inter-PLMN Transfer).

[0023] Figure 8An example Notification Request procedure contacting the USS via the V / Home PLMN is shown (Roaming / Inter-PLMN Transfer).

[0024] Fig. 9 An example advertisement request procedure for restricted discovery (non-roaming) is shown.

[0025] Fig.10 An example monitoring request procedure for restricted discovery (non-roaming) is shown. DETAILED DESCRIPTION

[0026] Figure 1A 1 is a diagram illustrating an exemplary communication system 100 in which one or more disclosed embodiments may be implemented. The communication system 100 may be a multiple access system that provides content such as voice, data, video, messaging, broadcast, etc. to multiple wireless users. The communication system 100 may enable multiple wireless users to access such content through sharing of system resources (including wireless bandwidth). For example, the communication system 100 may employ one or more channel access methods such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single carrier FDMA (SC-FDMA), zero tail unique word DFT spread OFDM (ZT UW DTS-s OFDM), unique word OFDM (UW-OFDM), resource block filtered OFDM, filter bank multi-carrier (FBMC), etc.

[0027] like Figure 1AAs shown, the communication system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, RAN 104 / 113, CN 106 / 115, public switched telephone network (PSTN) 108, Internet 110 and other networks 112, but it should be understood that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Each of the WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and / or communicate in a wireless environment. By way of example, the WTRUs 102a, 102b, 102c, 102d (any of which may be referred to as a “station” and / or “STA”) may be configured to transmit and / or receive wireless signals and may include user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular phone, a personal digital assistant (PDA), a smart phone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi-Fi device, an Internet of Things (IoT) device, a watch or other wearable device, a head-mounted display (HMD), a vehicle, a drone, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in an industrial and / or automated process chain environment), a consumer electronic device, a device operating on a commercial and / or industrial wireless network, etc. Any of the WTRUs 102a, 102b, 102c, and 102d may be interchangeably referred to as a UE.

[0028] The communication system 100 may also include a base station 114a and / or a base station 114b. Each of the base stations 114a, 114b may be any type of device that is configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communication networks, such as the CN 106 / 115, the Internet 110, and / or other networks 112. By way of example, the base stations 114a, 114b may be a base transceiver station (BTS), a Node B, an evolved Node B (eNB), a Home Node B, a Home evolved Node B, a next generation Node B (gNB), an NR Node B, a site controller, an access point (AP), a wireless router, and the like. Although the base stations 114a, 114b are each depicted as a single element, it should be appreciated that the base stations 114a, 114b may include any number of interconnected base stations and / or network elements.

[0029] The base station 114a may be part of the RAN 104 / 113, which may also include other base stations and / or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), a relay node, etc. The base station 114a and / or the base station 114b may be configured to transmit and / or receive wireless signals on one or more carrier frequencies, which may be referred to as cells (not shown). These frequencies may be in a licensed spectrum, an unlicensed spectrum, or a combination of licensed and unlicensed spectrum. A cell may provide coverage of wireless services to a specific geographic area, which may be relatively fixed or may change over time. The cell may be further divided into cell sectors. For example, a cell associated with the base station 114a may be divided into three sectors. Therefore, in one embodiment, the base station 114a may include three transceivers, i.e., one transceiver for each sector of the cell. In an embodiment, the base station 114a may employ multiple-input multiple-output (MIMO) technology and may utilize multiple transceivers for each sector of the cell. For example, beamforming may be used to transmit and / or receive signals in a desired spatial direction.

[0030] The base stations 114a, 114b may communicate with one or more of the WTRUs 102a, 102b, 102c, 102d over an air interface 116, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet (UV), visible light, etc.). The air interface 116 may be established using any suitable radio access technology (RAT).

[0031] More specifically, as noted above, the communication system 100 may be a multiple access system and may employ one or more channel access schemes such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, etc. For example, the base station 114a in the RAN 104 / 113 and the WTRUs 102a, 102b, 102c may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may use Wideband CDMA (WCDMA) to establish the air interface 115 / 116 / 117. WCDMA may include communication protocols such as High Speed ​​Packet Access (HSPA) and / or Evolved HSPA (HSPA+). HSPA may include High Speed ​​Downlink (DL) Packet Access (HSDPA) and / or High Speed ​​UL Packet Access (HSUPA).

[0032] In one embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which may establish the air interface 116 using Long Term Evolution (LTE) and / or LTE-Advanced (LTE-A) and / or LTE-Advanced Pro (LTE-A Pro).

[0033] In one embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as NR radio access, which may establish the air interface 116 using New Radio (NR).

[0034] In one embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement multiple radio access technologies. For example, the base station 114a and the WTRUs 102a, 102b, 102c may implement LTE radio access and NR radio access together, for example using dual connectivity (DC) principles. Thus, the air interface utilized by the WTRUs 102a, 102b, 102c may be characterized by multiple types of radio access technologies and / or transmissions sent to / from multiple types of base stations (e.g., eNBs and gNBs).

[0035] In other embodiments, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as IEEE 802.11 (i.e., Wireless Fidelity (WiFi)), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile Communications (GSM), GSM Enhanced Data Rates for Evolution (EDGE), GSM EDGE (GERAN), etc.

[0036] Figure 1AThe base station 114b in the example may be, for example, a wireless router, a Home NodeB, a Home eNodeB, or an access point, and may utilize any suitable RAT to facilitate wireless connectivity in a local area, such as a business location, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a road, and the like. In one embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN). In one embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN). In yet another embodiment, the base station 114b and the WTRUs 102c, 102d may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.) to establish a picocell or a femtocell. As Figure 1A As shown, base station 114b may have a direct connection to Internet 110. Therefore, base station 114b may not need to access Internet 110 via CN 106 / 115.

[0037] The RAN 104 / 113 may be in communication with the CN 106 / 115, which may be any type of network configured to provide voice, data, applications and / or Voice over Internet Protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. The data may have different quality of service (QoS) requirements, such as different throughput requirements, delay requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, etc. The CN 106 / 115 may provide call control, billing services, mobile location-based services, pre-paid calling, Internet connectivity, video distribution, etc., and / or perform high-level security functions, such as user authentication. Although not described in detail in the specification, the CN 106 / 115 may be configured to provide voice, data, applications and / or Voice over Internet Protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. Figure 1A Although not shown in the figure, it will be appreciated that the RAN 104 / 113 and / or the CN 106 / 115 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 104 / 113 or a different RAT. For example, in addition to being connected to the RAN 104 / 113, which may utilize NR radio technology, the CN 106 / 115 may also be in communication with another RAN (not shown) that employs GSM, UMTS, CDMA2000, WiMAX, E-UTRA, or WiFi radio technology.

[0038] The CN 106 / 115 may also act as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and / or other networks 112. The PSTN 108 may include a circuit-switched telephone network that provides plain old telephone service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices that use common communication protocols, such as the Transmission Control Protocol (TCP), the User Datagram Protocol (UDP), and / or the Internet Protocol (IP) in the TCP / IP Internet protocol suite. The networks 112 may include wired and / or wireless communication networks owned and / or operated by other service providers. For example, the networks 112 may include another CN connected to one or more RANs, which may employ the same RAT as the RAN 104 / 113 or a different RAT.

[0039] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communication system 100 may include multi-mode capabilities (e.g., the WTRUs 102a, 102b, 102c, 102d may include multiple transceivers for communicating with different wireless networks via different wireless links). Figure 1A The illustrated WTRU 102c may be configured to communicate with the base station 114a, which may employ a cellular-based radio technology, and with the base station 114b, which may employ an IEEE 802 radio technology.

[0040] Figure 1B is a system diagram illustrating an example WTRU 102. Figure 1B As shown, the WTRU 102 may include, among other things, a processor 118, a transceiver 120, a transmit / receive element 122, a speaker / microphone 124, a keypad 126, a display / touchpad 128, non-removable memory 130, removable memory 132, a power source 134, a global positioning system (GPS) chipset 136, and / or other peripherals 138. It will be appreciated that the WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with an embodiment.

[0041] The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. The processor 118 may perform signal coding, data processing, power control, input / output processing, and / or any other functions that enable the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit / receive element 122. Although Figure 1B The processor 118 and the transceiver 120 are depicted as separate components, but it is understood that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.

[0042] The transmit / receive element 122 may be configured to transmit signals to or receive signals from a base station (e.g., base station 114a) via an air interface 116. For example, in one embodiment, the transmit / receive element 122 may be an antenna configured to transmit and / or receive RF signals. In one embodiment, the transmit / receive element 122 may be an emitter / detector configured to transmit and / or receive, for example, IR, UV, or visible light signals. In yet another embodiment, the transmit / receive element 122 may be configured to transmit and / or receive RF and light signals. It should be understood that the transmit / receive element 122 may be configured to transmit and / or receive any combination of wireless signals.

[0043] Although the transmit / receive element 122 Figure 1B 102 as a single element, but the WTRU 102 may include any number of transmit / receive elements 122. More specifically, the WTRU 102 may employ MIMO technology. Thus, in one embodiment, the WTRU 102 may include two or more transmit / receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface 116.

[0044] The transceiver 120 may be configured to modulate signals to be transmitted by the transmit / receive element 122 and to demodulate signals received by the transmit / receive element 122. As noted above, the WTRU 102 may have multi-mode capabilities. For example, the transceiver 120 may include multiple transceivers to enable the WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.11.

[0045] The processor 118 of the WTRU 102 may be coupled to a speaker / microphone 124, a keypad 126, and / or a display / touchpad 128 (e.g., a liquid crystal display (LCD) display unit or an organic light emitting diode (OLED) display unit) and may receive user input data therefrom. The processor 118 may also output user data to the speaker / microphone 124, the keypad 126, and / or the display / touchpad 128. In addition, the processor 118 may access information from and store data in any type of suitable memory, such as a non-removable memory 130 and / or a removable memory 132. The non-removable memory 130 may include a random access memory (RAM), a read-only memory (ROM), a hard disk, or any other type of memory storage device. The removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like. In other embodiments, the processor 118 may access information from and store data in a memory that is not physically located on the WTRU 102, such as on a server or a home computer (not shown).

[0046] The processor 118 may receive power from the power source 134, and may be configured to distribute and / or control power to other components in the WTRU 102. The power source 134 may be any suitable device for powering the WTRU 102. For example, the power source 134 may include one or more dry cell batteries (e.g., nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel-metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, etc.

[0047] The processor 118 may also be coupled to the GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102. In addition to or in lieu of the information from the GPS chipset 136, the WTRU 102 may receive location information from a base station (e.g., base stations 114a, 114b) over the air interface 116 and / or determine its location based on the timing of signals received from two or more nearby base stations. It will be appreciated that the WTRU 102 may acquire location information by any suitable location-determination method while remaining consistent with an embodiment.

[0048] The processor 118 may also be coupled to other peripherals 138, which may include one or more software modules and / or hardware modules that provide additional features, functionality, and / or wired or wireless connectivity. For example, the peripherals 138 may include an accelerometer, an electronic compass, a satellite transceiver, a digital camera (for photos and / or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands-free headset, a Bluetooth® module, frequency modulation (FM) radio unit, digital music player, media player, video game player module, Internet browser, virtual reality and / or augmented reality (VR / AR) device, activity tracker, etc. Peripheral device 138 may include one or more sensors, which may be one or more of the following: a gyroscope, an accelerometer, a Hall effect sensor, a magnetometer, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor; a geolocation sensor; an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, and / or a humidity sensor.

[0049] The WTRU 102 may include a full-duplex radio for which transmission and reception of some or all signals (e.g., associated with specific subframes for UL (e.g., for transmission) and downlink (e.g., for reception)) may be concurrent and / or simultaneous. The full-duplex radio may include an interference management unit for reducing and / or substantially eliminating self-interference via hardware (e.g., a choke) or via signal processing performed by a processor (e.g., a separate processor (not shown) or via the processor 118). In one embodiment, the WRTU 102 may include a half-duplex radio for which transmission and reception of some or all signals (e.g., associated with specific subframes for UL (e.g., for transmission) or downlink (e.g., for reception)) may be concurrent and / or simultaneous.

[0050] Figure 1C 1 is a system diagram illustrating the RAN 104 and the CN 106 according to one embodiment. As noted above, the RAN 104 may employ an E-UTRA radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 104 may also be in communication with the CN 106.

[0051] The RAN 104 may include evolved Node-Bs 160a, 160b, 160c, though it will be appreciated that the RAN 104 may include any number of evolved Node-Bs while remaining consistent with an embodiment. The evolved Node-Bs 160a, 160b, 160c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In one embodiment, the evolved Node-Bs 160a, 160b, 160c may implement MIMO technology. Thus, the evolved Node-B 160a, for example, may use multiple antennas to transmit wireless signals to and / or receive wireless signals from the WTRU 102a.

[0052] Each of the evolved Node Bs 160a, 160b, 160c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in UL and / or DL, etc. Figure 1C As shown, the eNode-Bs 160a, 160b, 160c may communicate with one another via an X2 interface.

[0053] Figure 1C The illustrated CN 106 may include a mobility management entity (MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN) gateway (or PGW) 166. While each of the foregoing elements is depicted as being part of the CN 106, it should be understood that any of these elements may be owned and / or operated by an entity other than a CN operator.

[0054] The MME 162 may be connected to each of the evolved Node-Bs 162a, 162b, 162c in the RAN 104 via an S1 interface and may serve as a control node. For example, the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, bearer activation / deactivation, selecting a particular serving gateway during an initial attach of the WTRUs 102a, 102b, 102c, etc. The MME 162 may provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM and / or WCDMA.

[0055] The SGW 164 may be connected to each of the evolved Node-Bs 160a, 160b, 160c in the RAN 104 via an S1 interface. The SGW 164 may generally route and forward user data packets to / from the WTRUs 102a, 102b, 102c. The SGW 164 may perform other functions, such as anchoring the user plane during inter-evolved Node-B handovers, triggering paging when DL data is available for the WTRUs 102a, 102b, 102c, managing and storing the context of the WTRUs 102a, 102b, 102c, and the like.

[0056] The SGW 164 may be connected to the PGW 166, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.

[0057] The CN 106 may facilitate communications with other networks. For example, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional land-line communications devices. For example, the CN 106 may include or may be in communication with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that serves as an interface between the CN 106 and the PSTN 108. In addition, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to other networks 112, which may include other wired and / or wireless networks owned and / or operated by other service providers.

[0058] Although the WTRU Figures 1A to 1D Although described as a wireless terminal, it is contemplated that in certain representative embodiments such a terminal may (eg, temporarily or permanently) employ a wired communications interface with a communications network.

[0059] In a representative embodiment, the other network 112 may be a WLAN.

[0060] A WLAN in infrastructure basic service set (BSS) mode may have an access point (AP) for the BSS and one or more stations (STAs) associated with the AP. The AP may have access or an interface to a distribution system (DS) or another type of wired / wireless network that carries traffic to and / or carries traffic away from the BSS. Traffic originating from outside the BSS and directed to the STA may arrive through the AP and may be delivered to the STA. Traffic originating from the STA and directed to a destination outside the BSS may be sent to the AP to be delivered to the corresponding destination. Traffic between STAs within the BSS may be sent through the AP, for example, where the source STA may send traffic to the AP, and the AP may deliver the traffic to the destination STA. Traffic between STAs within the BSS may be considered and / or referred to as point-to-point traffic. Point-to-point traffic may be sent between the source STA and the destination STA (e.g., directly between them) using direct link establishment (DLS). In certain representative embodiments, the DLS may use 802.11e DLS or 802.11z tunnel DLS (TDLS). A WLAN using an independent BSS (IBSS) mode may not have an AP, and STAs (eg, all STAs) within or using the IBSS may communicate directly with each other. The IBSS communication mode may sometimes be referred to herein as an "ad-hoc" communication mode.

[0061] When using the 802.11ac infrastructure operating mode or a similar operating mode, the AP may transmit a beacon on a fixed channel (such as a primary channel). The primary channel may be a fixed width (e.g., a 20MHz wide bandwidth) or a width dynamically set via signaling. The primary channel may be an operating channel of the BSS and may be used by the STA to establish a connection with the AP. In certain representative embodiments, carrier sense multiple access / collision avoidance (CSMA / CA) may be implemented, for example, in an 802.11 system. For CSMA / CA, a STA (e.g., each STA) (including the AP) may sense the primary channel. If the primary channel is sensed / detected and / or determined to be busy by a specific STA, the specific STA may back off. One STA (e.g., only one station) may transmit at any given time in a given BSS.

[0062] High throughput (HT) STAs may communicate using a 40 MHz wide channel, for example, via a combination of a primary 20 MHz channel and adjacent or non-adjacent 20 MHz channels to form a 40 MHz wide channel.

[0063] Very high throughput (VHT) STAs may support 20MHz, 40MHz, 80MHz, and / or 160MHz wide channels. 40MHz and / or 80MHz channels may be formed by combining consecutive 20MHz channels. A 160MHz channel may be formed by combining 8 consecutive 20MHz channels, or by combining two non-contiguous 80MHz channels (this may be referred to as an 80+80 configuration). For the 80+80 configuration, after channel coding, the data may pass through a segment parser that may separate the data into two streams. Each stream may be individually processed by an inverse fast Fourier transform (IFFT) and time domain processing. These streams may be mapped to two 80MHz channels, and data may be transmitted by a transmitting STA. At the receiver of the receiving STA, the operations described above for the 80+80 configuration may be reversed, and the combined data may be sent to a medium access control (MAC).

[0064] 802.11af and 802.11ah support operating modes below 1 GHz. Channel operating bandwidths and carriers are reduced in 802.11af and 802.11ah relative to those used in 802.11n and 802.11ac. 802.11af supports 5MHz, 10MHz, and 20MHz bandwidths in the TV White Space (TVWS) spectrum, and 802.11ah supports 1MHz, 2MHz, 4MHz, 8MHz, and 16MHz bandwidths using non-TVWS spectrum. According to a representative embodiment, 802.11ah may support meter type control / machine type communications, such as MTC devices in macro coverage areas. MTC devices may have certain capabilities, such as limited capabilities, including support for (e.g., only support for) certain bandwidths and / or limited bandwidths. MTC devices may include batteries with battery life above a threshold (e.g., to maintain very long battery life).

[0065] WLAN systems that can support multiple channels and channel bandwidths such as 802.11n, 802.11ac, 802.11af, and 802.11ah include channels that can be designated as primary channels. The primary channel may have a bandwidth equal to the maximum common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel may be set and / or limited by a STA (which supports the minimum bandwidth operating mode) from all STAs operating in the BSS. In the example of 802.11ah, for STAs (e.g., MTC-type devices) that support (e.g., only support) 1MHz mode, the primary channel may be 1MHz wide, even if the AP and other STAs in the BSS support 2MHz, 4MHz, 8MHz, 16MHz, and / or other channel bandwidth operating modes. Carrier sensing and / or network allocation vector (NAV) settings may depend on the state of the primary channel. If the primary channel is busy, for example, because a STA (supporting only the 1MHz operating mode) is transmitting to the AP, the entire available frequency band may be considered busy even if most of the frequency bands remain idle and may be available.

[0066] In the United States, the available frequency band for 802.11ah is 902MHz to 928MHz. In South Korea, the available frequency band is 917.5MHz to 923.5MHz. In Japan, the available frequency band is 916.5MHz to 927.5MHz. The total bandwidth available for 802.11ah is 6MHz to 26MHz, depending on the country code.

[0067] Figure 1D1 is a system diagram showing the RAN 113 and the CN 115 according to one embodiment. As noted above, the RAN 113 may employ NR radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 113 may also be in communication with the CN 115.

[0068] The RAN 113 may include gNBs 180a, 180b, 180c, though it will be appreciated that the RAN 113 may include any number of gNBs while remaining consistent with an embodiment. The gNBs 180a, 180b, 180c may each include one or more transceivers to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. In one embodiment, the gNBs 180a, 180b, 180c may implement MIMO technology. For example, the gNBs 180a, 180b may utilize beamforming to transmit signals to and / or receive signals from the gNBs 180a, 180b, 180c. Thus, the gNB 180a may, for example, use multiple antennas to transmit wireless signals to and / or receive wireless signals from the WTRU 102a. In one embodiment, the gNBs 180a, 180b, 180c may implement carrier aggregation technology. For example, the gNB 180a may transmit multiple component carriers to the WTRU 102a (not shown). A subset of these component carriers may be on an unlicensed spectrum, while the remaining component carriers may be on a licensed spectrum. In one embodiment, the gNBs 180a, 180b, 180c may implement a coordinated multi-point (CoMP) technique. For example, the WTRU 102a may receive coordinated transmissions from the gNB 180a and gNB 180b (and / or gNB 180c).

[0069] The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using transmissions associated with scalable parameter sets. For example, OFDM symbol spacing and / or OFDM subcarrier spacing may vary for different transmissions, different cells, and / or different portions of the wireless transmission spectrum. The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using subframes or transmission time intervals (TTIs) of varying or scalable lengths (e.g., containing varying numbers of OFDM symbols and / or varying absolute time lengths over time).

[0070] The gNBs 180a, 180b, 180c may be configured to communicate with the WTRUs 102a, 102b, 102c in a standalone configuration and / or a non-standalone configuration. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c while also not accessing other RANs (e.g., such as the eNodeBs 160a, 160b, 160c). In a standalone configuration, the WTRUs 102a, 102b, 102c may use one or more of the gNBs 180a, 180b, 180c as mobility anchor points. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using signals in an unlicensed band. In a non-standalone configuration, the WTRUs 102a, 102b, 102c may communicate or be connected with the gNB 180a, 180b, 180c while also communicating or being connected with another RAN, such as the eNode-B 160a, 160b, 160c. For example, the WTRUs 102a, 102b, 102c may implement the DC principle to communicate with one or more gNBs 180a, 180b, 180c and one or more eNode-Bs 160a, 160b, 160c substantially simultaneously. In a non-standalone configuration, the eNode-B 160a, 160b, 160c may serve as a mobility anchor for the WTRUs 102a, 102b, 102c, and the gNB 180a, 180b, 180c may provide additional coverage and / or throughput for serving the WTRUs 102a, 102b, 102c.

[0071] Each of the gNBs 180a, 180b, 180c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in UL and / or DL, support of network slicing, dual connectivity, interworking between NR and E-UTRA, routing of user plane data towards a user plane function (UPF) 184a, 184b, routing of control plane information towards an access and mobility management function (AMF) 182a, 182b, etc. As shown in FIG. Figure 1D As shown, gNBs 180a, 180b, and 180c may communicate with each other via an Xn interface.

[0072] Figure 1DThe illustrated CN 115 may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one session management function (SMF) 183a, 183b, and possibly a data network (DN) 185a, 185b. While each of the foregoing elements is depicted as part of the CN 115, it should be understood that any of these elements may be owned and / or operated by an entity other than a CN operator.

[0073] The AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via the N2 interface and may serve as a control node. For example, the AMF 182a, 182b may be responsible for authenticating users of the WTRU 102a, 102b, 102c, support of network slicing (e.g., handling of different PDU sessions with different requirements), selecting a specific SMF 183a, 183b, management of registration areas, termination of NAS signaling, mobility management, etc. The AMF 182a, 182b may use network slicing to customize CN support for the WTRU 102a, 102b, 102c based on the type of services used by the WTRU 102a, 102b, 102c. For example, different network slices may be established for different use cases, such as services relying on ultra-reliable low latency (URLLC) access, services relying on enhanced mobile broadband (eMBB) access, services for machine type communication (MTC) access, etc. The AMF 162 may provide a control plane function for switching between the RAN 113 and other RANs (not shown) that employ other radio technologies, such as LTE, LTE-A, LTE-A Pro, and / or non-3GPP access technologies such as WiFi.

[0074] The SMF 183a, 183b may be connected to the AMF 182a, 182b in the CN 115 via the N11 interface. The SMF 183a, 183b may also be connected to the UPF 184a, 184b in the CN 115 via the N4 interface. The SMF 183a, 183b may select and control the UPF 184a, 184b, and configure traffic routing through the UPF 184a, 184b. The SMF 183a, 183b may perform other functions such as managing and allocating UE IP addresses, managing PDU sessions, controlling policy enforcement and QoS, providing downlink data notification, etc. The PDU session type may be IP-based, non-IP-based, Ethernet-based, etc.

[0075] The UPF 184a, 184b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via an N3 interface, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices. The UPF 184, 184b may perform other functions, such as routing and forwarding packets, enforcing user plane policies, supporting multi-homed PDU sessions, handling user plane QoS, buffering downlink packets, providing mobility anchoring, etc.

[0076] The CN 115 may facilitate communications with other networks. For example, the CN 115 may include or may communicate with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that serves as an interface between the CN 115 and the PSTN 108. In addition, the CN 115 may provide the WTRUs 102a, 102b, 102c with access to other networks 112, which may include other wired and / or wireless networks owned and / or operated by other service providers. In one embodiment, the WTRUs 102a, 102b, 102c may be connected to local data networks (DNs) 185a, 185b via UPFs 184a, 184b via N3 interfaces to the UPFs 184a, 184b and N6 interfaces between the UPFs 184a, 184b and the DNs 185a, 185b.

[0077] Given that Figures 1A to 1D as well as Figures 1A to 1D Corresponding to the description of the present invention, one or more or all of the functions described herein with reference to one or more of the following may be performed by one or more simulation devices (not shown): WTRU102a-d, base station 114a-b, eNode-B 160a-c, MME 162, SGW 164, PGW 166, gNB 180a-c, AMF 182a-b, UPF 184a-b, SMF 183a-b, DN 185a-b and / or any other device described herein. The simulation device may be one or more devices configured to emulate one or more or all of the functions described herein. For example, the simulation device may be used to test other devices and / or simulate network and / or WTRU functions.

[0078] The simulation device may be designed to implement one or more tests of other devices in a laboratory environment and / or an operator network environment. For example, the one or more simulation devices may perform one or more functions or all functions while being fully or partially implemented and / or deployed as part of a wired and / or wireless communication network in order to test other devices within the communication network. The one or more simulation devices may perform one or more functions or all functions while being temporarily implemented / deployed as part of a wired and / or wireless communication network. The simulation device may be directly coupled to another device for testing purposes and / or may use over-the-air wireless communications to perform testing.

[0079] The one or more simulation devices may perform one or more (including all) functions without being implemented / deployed as part of a wired and / or wireless communication network. For example, the simulation device may be used in a test lab and / or a test scenario in a non-deployed (e.g., testing) wired and / or wireless communication network to enable testing of one or more components. The one or more simulation devices may be test equipment. Direct RF coupling and / or wireless communication via RF circuitry (e.g., which may include one or more antennas) may be used by the simulation device to transmit and / or receive data.

[0080] Systems and methods for command and control (C2) communication establishment, modification and / or revocation are described herein. The C2 communication may be a direct C2 communication. C2 authorization may be performed by a wireless transmission and reception unit (WTRU), such as an unmanned (unmanned reconnaissance) aerial vehicle (UAV). For example, if the WTRU sends a C2 communication request, the C2 authorization may be performed by the WTRU. The C2 communication request may be sent to an unmanned (unmanned reconnaissance) aerial system (UAS) service provider (USS), such as via a UAS network function (NF) during a packet data unit (PDU) session establishment and / or modification. For example, after successful authorization, the WTRU may perform discovery of peer WTRUs.

[0081] For example, the WTRU may perform C2 communication (e.g., direct C2 communication) establishment, modification, and / or revocation. The WTRU (e.g., UAV, UAV-C, etc.) may send an authorization request (e.g., C2 authorization request on PC5) during PDU session establishment and / or modification. The authorization request may correspond to C2 communication, such as direct or line-of-sight C2 communication. The WTRU may receive authorization for direct C2 from the USS (e.g., in an authorization response), for example, via a PDU session modification or a separate PDU setup response message. The authorization may include authorization information. The WTRU may receive C2 authorization parameters (e.g., in an air container to facilitate a discovery procedure with the UAV-C (e.g., UAS application user ID, discovery credentials, etc.), for example, to be used as part of direct discovery (e.g., open or restricted direct discovery). The WTRU may perform (e.g., start) discovery. In an example, the WTRU may perform discovery if the WTRU receives C2 authorization information from the USS. The WTRU may use parameters from the USS to enable discovery of the UAV-C.

[0082] In one example, a network function (NF) may perform C2 communication (e.g., direct C2 communication) establishment, modification, and / or revocation. The NF (e.g., UAS NF) may receive an authorization request from a session management function (SMF), for example, to enable PC5 via C2. The UAS NF may forward the authorization request to the USS. The UAS NF may receive an authorization response from the USS indicating that C2 on PC5 is authorized. The UAS NF may store the authorization information. The UAS NF may forward the authorization response to the SMF.

[0083] For example, a management function (e.g., a Direct Discovery Name Management Function (DDNMF)) may perform a direct discovery procedure for a UAV / UAV-C. The DDNMF may receive a discovery request. The discovery request may include a UAS ProSe application ID (e.g., set to a CAA level ID), a WTRU ID, etc. The DDNMF may check the authorization for discovery of the UAS ProSe application ID using a unified data management (UDM) based on associated subscription information. The DDNMF may determine to interact with the UAS NF, for example, based on associated subscription data (e.g., the UAS application ID is associated with the USS / UAS application). The DDNMF may send a request message for discovery authorization to the UAS NF. The DDNMF may receive a response message from the UAS NF. The response message may include authorization information for discovery, such as, for example, an authorization flag or a UAS discovery code. The DDNMF may send a discovery response message (e.g., to the UAV). The discovery response message may include UAS information for discovery.

[0084] In an example, a first WTRU may send a first message to a network node indicating a C2 authorization request and a request for a PDU session. The first WTRU may receive a second message from the network node indicating that the PDU session has been established. The second message may indicate a C2 authorization and C2 authorization information. The first WTRU may determine that the first WTRU is authorized to communicate with the second WTRU based on the C2 authorization and the C2 authorization information. The C2 authorization information may include security credentials (e.g., an authorization token) and the identity of the second WTRU. For example, if the first WTRU is authorized to communicate with the second WTRU, the first WTRU may send a third message to the second WTRU using PC5. The third message may be protected based on the security credentials (e.g., authenticated and / or encrypted using the security credentials). The third message may indicate a request to perform a discovery procedure and / or a link establishment procedure.

[0085] In an example, a network node (e.g., a UAS NF) may send a first message indicating a request for authorization associated with the WTRU to a second network node. The network node may receive a second message indicating a response to the request, indicating policy configuration information, and / or indicating security credentials associated with the WTRU. The network node may determine that the WTRU is authorized to establish C2 over PC5 (e.g., based on the second message). The network node may determine, for example, discovery authorization parameters based on the second message. The network node may send a third message to the WTRU indicating the discovery authorization parameters.

[0086] In an example, a network node (e.g., a UAS NF) may receive a first message indicating an authorization request associated with discovery. The authorization request may indicate a subscription identifier associated with the first WTRU, a UAV identifier, a request type, an application level container, etc. The request type may indicate whether the discovery is an open discovery or a restricted discovery. The network node may determine that the first WTRU is authorized to operate as a UAV and / or is authorized to perform C2 communications. The network node may determine that the first WTRU is authorized, for example, based on a received indication (e.g., from a USS). The network node may send a second message indicating an authorization response (e.g., associated with the first message), the authorization response indicating that the WTRU is authorized to operate as a UAV. The second message may indicate that the first WTRU is authorized to perform open discovery (e.g., if the request type is associated with open discovery). The second message may indicate that the first WTRU is authorized to perform restricted discovery (e.g., if the request type is associated with restricted discovery). The network node may determine parameters (e.g., restricted discovery parameters for restricted discovery, open discovery parameters for open discovery), for example, based on the request type.

[0087] The discovery request may be a discovery request for monitoring. The discovery request for monitoring may indicate a subscription identifier, a UAV identifier, a PDUID associated with the first WTRU, a target subscription identifier, a target UAV identifier, and / or a target PDUID associated with the second WTRU. The network node may send a message indicating a monitoring response.

[0088] Unmanned (e.g., unmanned reconnaissance) aerial systems (UAS) may be supported. Additional enhancements may be provided for UAS support. Unmanned (e.g., unmanned reconnaissance) aerial vehicles (UAVs) may be controlled, for example, using command and control (C2) messages and / or communications from a UAV controller (UAV-C) and / or a UAS service provider (USS) / UAS traffic manager (UTM).

[0089] The type of C2 communication may include one or more of the following: direct; network-assisted; or UTM navigation. Direct C2 may correspond to a UAV-C and / or UAV communicating using a direct C2 communication link (e.g., D2D, PC5). Network-assisted C2 communication may correspond to a UAV-C and UAV communicating using a unicast C2 communication link with a network (e.g., via Uu). For example, network-assisted C2 communication (e.g., unlike direct C2 communication) may be used to enable / support flying a UAV beyond visual line of sight (BVLOS). UTM-navigated C2 communication may correspond to a UAV with autonomous flight capabilities that may be able to fly according to a pre-arranged flight plan under the supervision of a UTM. The C2 communication link between the UAV and the UTM may be used for flight monitoring, dynamic route updates, and / or occasional navigation.

[0090] ProSe (e.g., 5G ProSe) may support PC5 direct communication between WTRUs (e.g., two WTRUs) and may allow discovery, for example, by using a Direct Discovery Name Management Function (DDNMF) and leveraging a ProSe application server. ProSe (e.g., 5G ProSe) may generally support discovery and communication of WTRUs (e.g., WTRUs that are not UAVs).

[0091] Support for indirect C2 communications may be provided (e.g., only), e.g., the USS may allow (e.g., via a UAS network function (NF)) C2 communications. C2 communications may be performed using (e.g., through) PDU sessions. The UAV may discover a UAV-C (e.g., which may be a non-networked device, such as, for example, a ground station with an internet connection) for C2 communications, e.g., by obtaining the UAV-C IP address from the USS with network assistance, e.g., during a pairing / C2 authorization procedure.

[0092] A network-based API interface between the core network and the USS may be provided and / or used.

[0093] One or more mechanisms to support authorization for direct C2 communications (e.g., via PC5) may be enabled. For example, if the UAV may (e.g., need to) fly near the UAV-C in line of sight (LOS), mechanisms to support authorization for direct C2 communications (e.g., via PC5) may be enabled. For example, if the operator or USS restricts (e.g., needs to restrict) operations to LOS (e.g., LOS only), mechanisms to support authorization for direct C2 communications (e.g., via PC5) may be enabled.

[0094] Some communication technologies such as 5G ProSe may not support scenarios where authorization for direct one-to-one communication may use (e.g., require) authorization by a third party (e.g., USS) for providing C2 authorization in addition to MNO authorization. Mechanisms supporting authorization for direct C2 communication through USS may be used to (e.g., required to) supplement existing mechanisms for network-assisted C2 communication authorization.

[0095] C2 communication authorization (such as direct C2 communication authorization) can be achieved, for example, by leveraging the Network Exposure Function (NEF) / UASNF to accommodate network-based API interface requirements from this vertical. For direct C2 communication, peers (e.g., UAV and UAV-C) may be expected to perform discovery and link establishment, for example, while leveraging existing 5G ProSe corresponding procedures.

[0096] The UAV and UAV-C may discover each other, establish communication links, modify communication links, and / or release communication links for direct (D2D, PC5) C2 communications. The UAV and UAV-C may be authorized for LOS / D2D C2 (e.g., by utilizing USS UAV Authorization / Authentication (UUAA) and / or C2 authorization). The UAV and UAV-C may discover and connect for LOS / D2D C2 communications. The USS / UTM may be used to establish, modify, and revoke direct security associations for C2 communications. The UAV and UAV-C may authenticate each other and establish a secure PC5 link for C2 communications.

[0097] Figure 2An example overview of C2 direct communication over PC5 is shown. For example, C2 on PC5 may be provided to add support for authorization of LOS operations. For example, if a ProSe-capable UAV (e.g., WTRU) sends (e.g., directly) a C2 communication request to a USS (e.g., via a UAS NF during PDU session establishment / modification), direct C2 authorization may be performed. The UAV / UAV-C may, for example, perform discovery of peer UAV-Cs / UAVs based on (e.g., after) a successful authorization.

[0098] Discovery may be dynamic, for example, by leveraging the DDNMF (e.g., using open / restricted discovery modes). Discovery may be static, for example, by involving a policy control function (PCF), SMF, and / or USS. The UAV may receive a dynamic discovery code from the DDNMF (e.g., directly). The discovery code may be provided by the PCF using a policy configuration initiated by the USS.

[0099] PC5 link establishment may be performed, for example, after (eg, secure) discovery of UAS peers. Existing security mechanisms may be used to protect the D2D link.

[0100] For example, the system may provide communication capabilities between a UAV and a UAV-C, which may communicate over the same or different public land mobile networks (PLMNs). The UAV and UAV-C may be equipped with a WTRU, for example, to enable device-to-device (D2D) communication (e.g., PC5). The WTRU may refer to a UAV or a UAV-C in this document. For example, the UAV and UAV-C roles may be interchanged in the procedures described herein. For example, during a direct discovery procedure, the UAV may correspond to the role of a discoverer / monitor, and the UAV-C may correspond to the role of a discoverer / notifier, or vice versa. The UAV or UAV-C may initiate a direct link establishment procedure. Both the UAV and the UAV-C may perform direct C2 authorization. The Civil Aviation Administration-level identity (CAA-level ID) and the WTRU ID mentioned herein may correspond to a CAA-level UAV ID and a UAV ID (e.g., GPSI) for the UAV or an equivalent identifier for the UAV-C.

[0101] Figure 3 An example UAV and UAV-C communication network using one or more PLMNs is shown. Figure 3 As shown, the UAV and UAV-C may be connected to different PLMNs and then connected to the same USS.

[0102] The UAV / UAV-C may be provided with C2 communication authorization, such as direct C2 communication authorization. The C2 authorization may be enhanced to allow C2 over Uu and / or direct (eg, PC5).

[0103] For example, if C2 authorization is requested in a PDU Session Establishment / Modification Request message (e.g., in a NAS message, in a UAS container), the WTRU (e.g., UAV and / or UAV-C) may indicate LOS and / or BVLOS or direct and / or network-assisted / indirect C2 communication. The WTRU may indicate its support for direct C2 communication (e.g., C2 on PC5) in the C2 authorization request.

[0104] The WTRU may obtain authorization information for direct C2 communication (e.g., parameters for peer discovery such as peer CAA Level ID / WTRU ID and / or credentials for direct link security, e.g., in a NAS message / UAS container) in a message from the SMF (e.g., PDU Session Establishment Accept / Command) and / or from the PCF (e.g., in a WTRU Configuration Update (UCU)). The type of authorized C2 communication (e.g., direct or indirect) may be provided to the UAV (e.g., through the network), for example, in a UAS application container.

[0105] The network function (e.g., SMF) initiating the C2 authorization procedure with the USS may determine, for example, based on the WTRU capability information, whether the WTRU supports direct C2 communication, whether the WTRU supports / is authorized for communications, such as ProSe communications. The network function may include a C2 support (such as direct C2 support) indication in the authorization request to the USS.

[0106] The UAS NF / NEF may receive C2 authentication information for LOS / direct and / or BVLOS / indirect communications from the USS. The C2 authorization information may include peer CAA level ID / WTRU ID and / or security credentials for establishing a secure direct / indirect link for C2 communications. The UAS NF may map aviation domain (e.g., LOS / BVLOS) authorization information parameters to C2 over a direct link (e.g., PC5) or an indirect link (e.g., over Uu), respectively. The UAS NF may transmit the authorization information to the SMF / PCF.

[0107] In an example, for example, if the UAV is restricted to LOS operation, the USS may refrain from providing (e.g., not providing) policy configuration information corresponding to a PDU session established for C2 communication (e.g., refrain from providing (e.g., not providing) an authorized peer UAV-C IP address via the UAS NF), while providing authorization for direct C2 communication (e.g., via the UAS NF). The USS may allow two communication modes, whereby the UAV and UAV-C may switch C2 communication between direct / LOS and indirect / BVLOS communication modes, for example, using a C2 switching mechanism.

[0108] Peer discovery may be enabled, such as direct discovery of peers of UAV / UAV-C. DDNMF / PCF may be enhanced to support dynamic / static discovery between UAV and UAV-C. DDNMF may use the interface with UAS NF for USS-assisted authorization of UAV-UAV-C direct discovery (e.g., to obtain code seeds, UAS peer identifiers, discovery key material).

[0109] The DDNMF may receive a discovery request including a UAS ProSe application ID (e.g., set to a CAA level ID), a WTRU ID, and / or a ProSe application ID corresponding to the UAS application ID. The DDNMF may utilize a unified data management (UDM) check, and the authorization for discovery of the ProSe App ID / UAS ProSe App ID may be determined to be interacting with the UAS NF, for example, based on associated subscription data (e.g., the UAS app ID is associated with the USS / UAS application). The DDNMF may send a request message for discovery authorization to the UAS NF. The DDNMF may receive a response message from the UAS NF. The response message may include authorization information for discovery (e.g., an authorization flag, a UAS discovery code, a UAS peer identifier). The DDNMF may send a discovery response message (e.g., to the UAV). The discovery response message may include UAS information for discovery.

[0110] In an example, as part of a policy control procedure initiated during a C2 authorization procedure, the USS may configure the PCF (eg, as described herein), eg, via the UAS NF, with discovery authorization information (eg, USS-assigned discovery code / code suffix, discovery credentials).

[0111] For example, the WTRU may perform direct discovery of UAS peers (e.g., via PC5) using a discovery code obtained from the DDNMF or SMF / PCF. In an example, direct discovery and direct communication may be performed using direct WLAN communication. The discovery code may be associated with or correspond to an SSID.

[0112] Direct C2 communications may be established between the UAV and the UAV-C. The UAV and UAV-C IP may establish secure PC5 communications with the assistance of the USS. The UAV may use credentials for direct C2 communications received as part of the direct C2 authorization (e.g., as described herein). The authorization information may include P5 link security key material (e.g., a shared key between the UAV and the UAV-C).

[0113] A direct C2 authorization and discovery model may be provided. A first model (e.g., Model #1) may correspond to direct C2 authorization for direct discovery. In the first model (e.g., Model #1), for example, after successful authentication and authorization by a USS, a UAV / UAV-C may be authorized for C2 communications with a peer UAV-C / UAV (e.g., whereby a peer identifier may be pre-configured in the UAV or USS). The UAV / UAV-C may, for example, perform direct discovery and direct link establishment for C2 communications after successful C2 authorization. For example, if the pairing of the UAV and UAV-C is predetermined / pre-configured (e.g., by a pilot, USS), the first model may be used.

[0114] Figure 4 An example of PC5 communicating directly with C2 authorization is shown, which then performs discovery. Figure 4 As shown, UUAA (e.g., conventional UUAA) may be performed, for example, by a UAV / UAV-C (e.g., a WTRU). The WTRU may have ProSe capabilities. When registering with the network, the WTRU may provide relevant capabilities. Figure 4 As shown, for example, based on a UAS peer pre-configured in the WTRU or in the USS, the WTRU may perform C2 authorization (e.g., as described herein) for LOS / direct and / or BVLOS / indirect C2 communications. Figure 4 As shown, for example, once the WTRU is authorized for C2 communication, the WTRU may perform dynamic direct discovery (e.g., using dynamic discovery codes / filters from the DDNMF or static codes obtained via the PCF or SMF). For example, if the WTRU performs the direct discovery procedure ProSe, the DDNMF may contact the UAS NF to retrieve discovery authorization information (e.g., authorization indication / flag, UAS peer identifier, remote identifier) ​​providing the WTRU ID and / or the ProSe application user ID of the WTRU. The UAS NF may, for example, retrieve the corresponding authorization information from the USS during C2 authorization using the provided identifier. The UAS NF may contact the USS for authorization (e.g., additional authorization) for discovery (e.g., if the UAS peer identifier is at the UAS NF). As shown Figure 4As shown, a secure direct link establishment between peers may be performed (eg, using credentials received during the C2 authorization procedure).

[0115] Direct discovery for direct C2 authorization may be provided. A second model (e.g., Model #2) may correspond to direct discovery for direct C2 authorization. In the second model (e.g., Model #2), the UAV / UAV-C (e.g., WTRU) may perform direct discovery to obtain a peer identifier to perform C2 communication, for example, after successful authentication and authorization by the USS. The WTRU may, for example, use the discovered peer identifier to perform C2 authorization. For example, after successful C2 authorization, the WTRU may perform a direct link establishment for C2 communication. For example, the second model may be used if the pairing of the UAV and the UAV-C is not predetermined (e.g., ad-hoc pairing, self-service model).

[0116] In an example, the discovery type (e.g., open / restricted) may be communicated / established at the UAS application layer (e.g., as part of a UAS application container), e.g., in an end-to-end interaction between a USS and a UAV / UAV-C (e.g., as described herein with respect to Figures 5 to 10 As described). For example, the parameters in the discovery message (e.g., discovery type / request type) may be optional (e.g., in the case of a UAV). Whether the WTRU is monitoring / announcement may be established, for example, based on the roles assigned to the UAV and UAV-C by the application / USS (e.g., the UAV-C may be monitoring and the UAV may be announcing based on application preference, or vice versa). The type of discovery request may be pre-configured in the application (e.g., the type of discovery request may be indicated by the received configuration information). The parameter may provide information about the request type to the UAS NF, and (e.g., in response) the UAS NF may send (e.g., required) information to the DDNMF (e.g., for monitoring restricted requests. The UAS NF may provide a target UAS peer identifier), for example, if the USS is not directly involved and the DDNMF is communicating with the UAS NF.

[0117] Figure 5 An example PC5 is shown communicating directly with a UAS peer discovery followed by C2 authorization. Figure 5 As shown in (for example, in Figure 5 At 501 in the example, UUAA (e.g., conventional UUAA) may be performed by a UAV / UAV-C (e.g., a WTRU), for example, as described herein with respect to Figure 4 As described. Figure 5 As shown in (for example, in Figure 5At 502 in the example, dynamic discovery of UAS peers may first be performed for (e.g., ad hoc) pairing, for example, rather than performing a C2 authorization procedure (e.g., as Figure 4 1). In an example, a WTRU (e.g., UAV) may be pre-configured with (e.g., receiving configuration information indicating) peer information (e.g., an identifier of a peer). The WTRU may (e.g., attempt to) match the peer information (e.g., as ProSe user information) during a discovery procedure. In an example, the WTRU may be pre-configured (e.g., by a PCF) with a ProSe service code corresponding to a UAS service code (USC) for UAS peer discovery. The WTRU may obtain peer WTRU information (e.g., set to a CAA level ID) during discovery using the USC. Figure 5 As shown (for example, in Figure 5 503 in the C2 authorization request), for example, once the WTRU discovers its peers using the code provided by the DDNMF / PCF, the WTRU may send the discovered peer information (e.g., such as an identifier of the peer (e.g., CAA-level UAV ID or Universal Public Subscription Identifier (GPSI))) in the C2 authorization request (e.g., instead of using a pre-configured peer identifier). Figure 5 As shown in (for example, in Figure 5 At 504 in ), for example based on successful C2 authorization, a secure direct link establishment between peers is performed as described above.

[0118] A C2 authorization may be performed, such as a direct C2 authorization (eg, non-roaming). Figure 6 An example C2 authorization involving PCF and USS via UAS NF is shown. Figure 6 As shown (for example, in Figure 6 At 601 in FIG. 5 ), a WTRU (e.g., a WTRU with ProSe capability) may send a PDU session establishment / modification request for direct C2 communication (e.g., with a second WTRU) to the SMF. The message may include a C2 authorization request on PC5 (e.g., a first message, wherein the first message indicates a C2 authorization request and a request for a PDU session). The SMF may forward the request for authorization of the C2 connection to the USS (e.g., via the UAS NF).

[0119] like Figure 6 As shown (for example, in Figure 6At 602 in the figure, the UAS NF may receive a C2 authorization response from the USS. The USS may forward the C2 authorization response to the SMF (e.g., sending a first message indicating a request for authorization associated with the WTRU). The USS may provide the C2 authorization information (e.g., an indication / code and security information) to the PCF, and may provide the C2 authorization information to the PCF. The USS may provide an authorization token to a home PLMN (HPLMN) UAS NF, for example when the WTRU is roaming, and the UAS NF may use the authorization token to request discovery authorization from the USS (e.g., as described herein). The UAS NF may receive a second message from the USS (e.g., indicating a response to the request, indicating policy configuration information, and security credentials associated with the WTRU). The UAS NF may request a PDUID from the PCF, for example based on a successful authorization from the USS (e.g., the UAS NF may determine that the WTRU is authorized to establish C2 through PC5, for example based on a successful authorization from the USS (e.g., the indicated response to the request and the indicated policy configuration information).

[0120] like Figure 6 As shown (for example, in Figure 6 At 603 in the PDU session modification command, authorization to initiate discovery may be provided to the WTRU via a subsequent PDU session modification command (e.g., indicating a discovery authorization parameter). Direct C2 authorization may be provided by the PCF in the UCU. The WTRU may determine that the WTRU is authorized to communicate with the second WTRU (e.g., based on a C2 authorization and C2 authorization information, wherein the C2 authorization information includes security credentials and the identity of the second WTRU). The WTRU may send a message to the second WTRU using PC5 (e.g., based on the C2 authorization), for example, using security credentials (e.g., an authorization token). The message may indicate a request to perform a discovery procedure and / or a link establishment procedure. For example, security credentials may be used to protect (e.g., authenticate and / or encrypt) the message.

[0121] The UAV / UAV-C may broadcast the CAA Level ID it received during C2 authorization, for example, to discover UAV-C / UAV and link establishment.

[0122] ProSe discovery may be performed. For example, ProSe discovery may correspond to open discovery (eg, roaming). Figure 7 An example notification request procedure (roaming / inter-PLMN transfer) is shown in FIG. Figure 7 As shown, the WTRU may be authorized to announce (e.g., in the HPLMN). The WTRU may be triggered to announce (e.g., by the application layer). The WTRU may send a discovery request (e.g., CAA level ID, App ID, UAS container) message to the DDNMF 1 (e.g., as shown in FIG. Figure 7 701 in FIG. 1 ).

[0123] like Figure 7 As shown (for example, in Figure 7 At 702 in FIG. 1 ), the DDNMF 1 may check the authorization of the application represented by the application ID. The UDM may provide the PLMN ID (e.g., a visited PLMN (VPLMN)) where the WTRU is registered. The DDNMF may determine that the UAS NF needs to be contacted, for example, based on subscription data associated with the application ID (e.g., corresponding to the UAS application ID).

[0124] like Figure 7 As shown (for example, in Figure 7 At 703 in the , DDNMF 1 may send an authorization request (e.g., GPSI (e.g., a subscription identifier associated with the WTRU), CAA level ID (e.g., UAV identifier), request type, application ID, UAS container) to the DDNMF 2 in the VPLMN (e.g., where the USS authorizes the WTRU / UAV via the UAS NF 2 of the VPLMN (e.g., in a UUAA procedure)). The DDNMF 1 may indicate that discovery authorization may be obtained via the UAS NF (e.g., indicating an authorization request associated with discovery).

[0125] like Figure 7 As shown (for example, in Figure 7 ), the DDNMF 2 may forward the authorization request (e.g., received from the DDNMF 1 as described herein) to the UAS NF 2. For example, if direct C2 authorization information for discovery is not available at the UAS NF 2 (e.g., discovery is performed prior to C2 authorization or the USS (e.g., requires) to explicitly authorize direct discovery), the UAS NF 2 may forward the request to the USS. The UAS NF 2 may determine that the WTRU is authorized to operate as a UAV and / or perform C2 communications (e.g., based on an indication received from the USS).

[0126] like Figure 7 As shown (for example, in Figure 7 At 705 in FIG. 1 ), UAS NF 2 may send an authorization response (e.g., response type, authorization indication to be announced, discovery code material) message to DDNMF 2 (e.g., sending a second message indicating that the first WTRU is authorized to operate as a UAV). UAS NF 2 may generate the response based on locally stored information (e.g., based on previous C2 authorization information) and / or after requesting the USS.

[0127] like Figure 7 As shown in (for example, in Figure 7At 706 in FIG. 1 ), DDNMF 2 may forward the message from UASNF2 / USS to the requesting DDNMF 1 in the HPLMN.

[0128] like Figure 7 As shown (for example, in Figure 7 At 707 in FIG. 1 ), the DDNMF 1 in the HPLMN may respond to the WTRU with a discovery response (eg, GPSI, CAA level ID, discovery code material).

[0129] For example, ProSe discovery may correspond to open discovery (eg, roaming). Figure 8 An example monitoring request procedure for discovering a (non-roaming) contact USS by obtaining the USS address from the home PLMN is shown. Figure 8 As shown, the WTRU may be authorized to announce in the HPLMN. The WTRU may be triggered to announce. The WTRU may send a discovery request (e.g., CAA level ID, GPSI, App ID, UAS container) message to the DDNMF 1 (e.g., in Figure 8 801 in the ).

[0130] like Figure 8 As shown in (for example, in Figure 8 At 802 in FIG. 1 ), the DDNMF 1 may check the authorization of the application represented by the application ID. The UDM may provide the VPLMN ID where the WTRU is registered. The DDNMF may determine that the UAS NF may (e.g., needs to) be contacted, for example based on subscription data associated with the application ID (e.g., UAS application id).

[0131] like Figure 8 As shown (for example, in Figure 8 At 803 in ), DDNMF 1 may send a PC5 authorization request to DDNMF 2 (e.g., in a VPLMN, where the USS authorizes the WTRU / UAV via UAS NF 2 of the VPLMN). The authorization request may include the GPSI and / or CAA level ID. DDNMF 1 may indicate that discovery authorization information is to be obtained (e.g., via UAS NF). DDNMF 1 may indicate that the HPLMN may contact the USS directly. UAS NF 2 may verify that a valid UUAA / C2 authorization is stored for this GPSI mapped to the WTRU. UAS NF 2 may verify that an authorization token is available (e.g., to allow the HPLMN to contact the USS, e.g., via UAS NF 1).

[0132] like Figure 8 As shown (for example, in Figure 8At 804 in FIG. 1 ), UAS NF 2 may send (e.g., based on stored information) a PC5 authorization response (e.g., GPSI, CAA level ID, authorization information (e.g., USS address, authorization token allowing HPLMN to contact USS directly)) to DDNMF 1.

[0133] like Figure 8 As shown (for example, in Figure 8 At 805 in FIG. 1 , DDNMF 1 may send the authorization request (e.g., CAA level ID, request type (open / restricted), authorization token from VPLMN / UAS NF 2, application level container) to UAS NF 1. For example, if no valid authorization information is available locally, UAS NF 1 may forward the request to USS.

[0134] like Figure 8 As shown (for example, in Figure 8 At 806 in FIG. 1 ), UAS NF 1 may return an authorization response (e.g., response type, discovery code material) message to the HPLMN's DDNMF 2. UAS NF 1 may generate the response based on locally stored information (e.g., based on a previous discovery / C 2 authorization procedure) and / or after requesting the USS.

[0135] like Figure 8 As shown (for example, in Figure 8 807 in the example, if the WTRU is authorized to use the ProSe application ID, the DDMF 1 may notify the DDNM 2 and may send a Notify Authorization (e.g., GPSI, CAA Level ID, Application ID, Discovery Code Material) message.

[0136] like Figure 8 As shown (for example, in Figure 8 At 808 in the figure), DDNMF 2 can send a notification authorization confirmation to DDNMF 1, for example, to authorize the WTRU to perform direct discovery monitoring.

[0137] like Figure 8 As shown (for example, in Fig. 9 At 809 in the , DDNMF 1 may send a discovery response (e.g., CAA level UAV ID, discovery code material / filters) to the WTRU. The DDNMF in the HPLMN may send a request to the DDNMF in the local / VPLMN and may receive a response filter for monitoring between the two DDNMFs, for example, if / when addressed monitoring is compared to an announcement in open discovery.

[0138] The discovery advertisement request may be sent, for example, corresponding to a restricted discovery model A / model B. Fig. 9An example advertisement request procedure for restricted discovery (non-roaming) is shown. Fig. 9 As shown (for example, in Fig. 9 At 900 in FIG. 1 ), the USS may assign a CAA level ID (e.g., a modified and / or new CAA level ID) to the WTRU (e.g., UAV / UAV-C), for example, during a previous UUAA or C2 authorization procedure, and obtain a WTRU ID from the network in return. The WTRU, the network (e.g., UAS NF), and / or the USS may store the binding / mapping (e.g., corresponding to the CAA level ID) and the WTRU ID.

[0139] like Fig. 9 As shown, the WTRU may (e.g., be authorized) to announce in the HPLMN. The WTRU may be triggered to announce. The WTRU may send a discovery request message (e.g., CAA level ID, GPSI, application ID, UAS container) to the DDNMF (e.g., in Fig. 9 901 in the ).

[0140] like Fig. 9 As shown (for example, in Fig. 9 At 902 in FIG. 1 ), the DDNMF may check the discovery authorization of the application (eg, represented by the application ID from the UDM). The DDNMF may determine that the UAS NF may be contacted (eg, required) based on, for example, subscription information associated with the application ID (eg, the UAS application ID).

[0141] like Fig. 9 As shown in (for example, in Fig. 9 At 903 in the example, the DDNMF may send an authorization request (eg, CAA level ID, application container, and discovery request type (eg, open / restricted)) to the UAS NF.

[0142] like Fig. 9 As shown (for example, in Fig. 9 At 904 in FIG. 1 ), the UAS NF may return an authorization response (e.g., CAA level ID, WTRU ID, PDUID, response type, discovery code material) to the DDNMF. The WTRU ID may be associated with the CAA level ID stored in the UAS NF. The UAS NF may generate the response, for example, based on locally stored information (e.g., based on a previous discovery / C2 authorization procedure) and / or after requesting the USS.

[0143] like Fig. 9 As shown (for example, in Fig. 9 At 905 in the figure), the DDNMF in the HPLMN may respond to the WTRU with a discovery response (eg, CAA level ID, discovery code material).

[0144] For example, a discovery monitoring request may be sent according to a restricted discovery model (such as Model A or Model B). Fig.10 An example monitoring request procedure for restricted discovery (non-roaming) is shown. Fig.10 As shown (for example, in Fig.10 1000 in ), for example, during a previous UUAA or C2 authorization procedure, the USS may assign a CAA Level ID (e.g., a modified and / or new CAA Level ID) to the WTRU (e.g., UAV / UAV-C). In return, the WTRU may obtain a WTRU ID (e.g., from the network). The WTRU, the network (e.g., UAS NF), and the USS may store a binding / mapping between the CAA Level ID and the WTRU ID. For example, if the WTRU intends to communicate / discover UAS peers, the WTRU may obtain the CAA Level IDs (e.g., target CAA Level IDs) of those users from the USS via the network (e.g., during the C2 authorization procedure). The WTRU may trigger monitoring, for example, by providing its own CAA Level ID and the target CAA Level ID to be monitored (e.g., which may be passed in an application level container).

[0145] like Fig.10 As shown (for example, in Fig.10 At 1001 in FIG. 1 ), the WTRU may send a discovery request message (e.g., CAA level ID, GPSI, discovery type, application ID, application level container) to the DDNMF 1. The application level container may contain the target CAA level IDs of the UAS peers that the WTRU may monitor. The CAA level ID may indicate the identity that the WTRU uses to obtain authorization for monitoring.

[0146] like Fig.10 As shown (for example, in Fig.10 At 1002 in FIG. 1 ), the DDNMF 1 may check the discovery authorization of the application represented by the application ID from the UDM. The DDNMF 1 may determine that the UAS NF 1 may be contacted (eg, required) based on, for example, subscription data associated with the application ID (eg, the UAS application ID).

[0147] like Fig.10 As shown (for example, in Fig.10 At 1003 in the figure), DDNMF 1 can send the authorization request (e.g., ID, WTRU ID, CAA level ID, PDUID, application container, discovery request type (e.g., open / restricted)) to the UAS NF.

[0148] like Fig.10 As shown in (for example, in Fig.10At 1004 in the flow), UAS NF 1 may send an authorization response message (e.g., WTRU ID, CAA level ID, PDUID, target WTRU ID, target CAA level ID, target PDUID, application container, discovery response type, discovery code material) to DDNMF 1. (e.g., each) target WTRU ID in the set of WTRU IDs may be returned along with the corresponding target CAA UAV ID that the CAA UAV ID may (e.g., be allowed to) discover. DDNMF 1 may verify that the returned WTRU ID / PDUID belongs to the requesting WTRU. The application level container may include the target CAA UAV ID that was successfully authenticated. UASNF1 may generate a response based on locally stored information (e.g., based on a previous discovery / C 2 authorization procedure) and / or after requesting the USS.

[0149] like Fig.10 As shown (for example, in Fig.10 ), for example, if the PLMN ID in the target WTRUID indicates a PLMN different from the HPLMN, the DDNMF 1 in the HPLMN may send a monitoring request message (e.g., WTRU ID, CAA level ID, PDUID, target WTRU ID, target CAA level ID, target PDUID, application ID) to the DDNMF 2 in another PLMN (e.g., to retrieve the corresponding restricted code).

[0150] like Fig.10 As shown in (for example, in Fig.10 At 1006 in FIG. 1 ), the DDNMF 2 in the other PLMN may send an authorization request (e.g., WTRU ID, PDUID, CAA level ID, target WTRU ID, target PDUID, target CAA level ID, request type) to the UAS NF2. The request type may be set to restricted discovery / permission.

[0151] like Fig.10 As shown (for example, in Fig.10), for example, if the CAA Level ID is allowed to discover the target CAA Level ID (e.g., based on the permission setting), the UAS NF may send an authorization message (e.g., target WTRU ID, target CAA Level ID, target PDUID, response type). The UAS NF2 may generate a response based on locally stored information and / or after requesting the USS. For example, during a previous discovery or C2 authorization procedure, the UAS NF may store and associate identifiers of the monitoring WTRU and the target / notifying WTRU. The UAS NF may verify the authorization for monitoring by matching the identifiers provided by the DDNMF 2 (e.g., monitoring and target WTRUs) with the stored identifiers. The DDNMF 2 may verify that the returned target WTRUID / PDUID corresponds to the WTRU to be monitored.

[0152] like Fig.10 As shown (for example, in Fig.10 ), DDNMF 2 may send a monitoring response (eg, restricted code material) message to DDNMF 1. DDNMF 2 may store (eg, in the context of the notifying WTRU) the WTRUID of the monitoring WTRU.

[0153] like Fig.10 As shown (for example, in Fig.10 ), for example, if DDNMF 1 has retrieved a (e.g., valid) ProSe restricted code, DDNMF 1 may send a discovery response (e.g., discovery filter) message to the WTRU (e.g., for each pair of target WTRU ID-target CAA level ID returned by the UAS NF / USS).

[0154] Although the above features and elements are described in particular combinations, each feature or element may be used alone without the other features and elements of the preferred embodiments, or in various combinations with or without the other features and elements.

[0155] Although the implementations described herein may consider 3GPP specific protocols, it should be understood that the implementations described herein are not limited to such scenarios and may be applicable to other wireless systems. For example, although the solutions described herein consider LTE, LTE-A, New Radio (NR) or 5G specific protocols, it should be understood that the solutions described herein are not limited to such scenarios and may be applicable to other wireless systems.

[0156] The processes described above may be implemented in a computer program, software, and / or firmware incorporated in a computer-readable medium for execution by a computer and / or a processor. Examples of computer-readable media include, but are not limited to, electronic signals (transmitted via a wired or wireless connection) and / or computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, read-only memory (ROM), random access memory (RAM), registers, cache memory, semiconductor memory devices, magnetic media (such as, but not limited to, built-in hard disks and removable disks), magneto-optical media, and optical media (such as compact disk (CD)-ROM disks and / or digital versatile disks (DVDs)). A processor associated with the software may be used to implement a radio frequency transceiver for a WTRU, terminal, base station, RNC, and / or any host computer.

Claims

1. A first wireless transmit / receive unit (WTRU), the first WTRU comprising: A processor, the processor being configured to: sending a first message to a network node, wherein the first message indicates a command and control (C2) authorization request, indicates a request for a packet data unit (PDU) session, and indicates a request to use direct C2 communications; receiving a second message from the network node, wherein the second message indicates that the PDU session has been established, indicates C2 authorization, and indicates C2 authorization information; determining that the first WTRU is authorized to communicate with a second WTRU based on the C2 authorization and the C2 authorization information, wherein the C2 authorization information includes an identity of the second WTRU; and If the first WTRU is authorized to communicate with the second WTRU, a third message is sent to the second WTRU using PC5, wherein the third message indicates a request to perform or link establishment procedure.

2. The first WTRU of claim 1 , wherein: The C2 authorization information includes security credentials, and wherein the third message is encrypted based on the security credentials.

3. The first WTRU of claim 1 , wherein: The C2 authorization information includes security credentials, and wherein the security credentials are authorization tokens.

4. The first WTRU of claim 1 , wherein: The C2 authorization information includes security credentials, wherein the processor is further configured to: A security key or a security token is determined based on the security credential, and wherein the third message is based on the determined security key or the determined security token.

5. The first WTRU of claim 1 , wherein: The C2 authorization information further includes an unmanned aerial vehicle controller (UAV-C) application identifier.

6. A first network node, the network node comprising: A processor, the processor being configured to: sending a first message to a second network node, wherein the first message indicates a request for authorization, wherein the authorization is associated with a wireless transmit / receive unit (WTRU), and wherein the authorization is associated with direct command and control (C2) communications; receiving a second message from the second network node; determining, based on the second message, that the WTRU is authorized to establish C2 via PC5; determining a discovery authorization parameter based on the second message; and A third message is sent to the WTRU, wherein the third message indicates the discovery authorization parameter.

7. The first network node according to claim 6, wherein: The second message indicates a response to the request and indicates policy configuration information.

8. The first network node according to claim 7, wherein: Determining that the WTRU is authorized to establish C2 through PC5 based on the second message is performed based on the indicated response to the request and the indicated policy configuration information.

9. The first network node according to claim 7, wherein: The second message indicates security credentials associated with the WTRU, and wherein the discovery authorization parameters are determined using the second message based on the indicated policy configuration information and the indicated security credentials.

10. The first network node according to claim 9, wherein: The security credential associated with the WTRU is an authorization token.

11. The first network node according to claim 6, wherein: The request for authorization is a request for permission to establish command and control (C2) through PC 5.

12. The first network node according to claim 6, wherein: The third message further indicates an unmanned aerial vehicle controller (UAV-C) application identifier.

13. A method comprising: sending a first message to a network node, wherein the first message indicates a command and control (C2) authorization request, indicates a request for a packet data unit (PDU) session, and indicates use of direct C2 communication; receiving a second message from the network node, wherein the second message indicates that the PDU session has been established, indicates C2 authorization, and indicates C2 authorization information; determining that a first wireless transmit / receive unit (WTRU) is authorized to communicate with a second WTRU based on the C2 authorization and the C2 authorization information, wherein the C2 authorization information includes an identity of the second WTRU; and If the first WTRU is authorized to communicate with the second WTRU, a third message is sent to the second WTRU using PC5, wherein the third message indicates a request to perform a link establishment procedure.

14. The method according to claim 13, wherein: The C2 authorization information includes security credentials, and wherein the third message is encrypted based on the security credentials.

15. The method according to claim 13, wherein: The C2 authorization information includes security credentials, and wherein the security credentials are authorization tokens.

16. The method according to claim 13, wherein: The C2 authorization information includes security credentials, wherein the method further comprises: A security key or a security token is determined based on the security credential, and wherein the third message is based on the determined security key or the determined security token.

17. The method according to claim 13, wherein: The C2 authorization information further includes an unmanned aerial vehicle controller (UAV-C) application identifier.

18. A first wireless transmit / receive unit (WTRU), the first WTRU comprising: A processor, the processor being configured to: sending a first message to a network node associated with direct C2 communication; receiving a second message indicating C2 authorization information; determining, based on the C2 authorization information, that the first WTRU is authorized to communicate with the second WTRU; Based on determining that the first WTRU is authorized to communicate with the second WTRU, a third message is sent to the second WTRU using PC5.

19. A first network entity, the network entity comprising: A processor, the processor being configured to: receiving a discovery request from a wireless transmit / receive unit (WTRU), wherein the discovery request indicates an identifier, and wherein the WTRU is authorized to advertise in a home public land mobile network; Determining to send an authorization request based on the received discovery request; sending the authorization request to a second network entity, wherein the authorization request indicates the identifier; receiving an authorization response; and A discovery response is sent to the WTRU.

Images