Direct C2 communications setup, modification, and cancellation
The described systems and methods facilitate authorized C2 communication setup, modification, and cancellation for UAVs, addressing the need for efficient C2 communication in mobile networks, enabling secure direct and network-assisted operations.
Patent Information
- Application Number
- JP2024525201
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2021-11-05
- Filing Date
- 2022-11-04
- Publication Date
- 2024-11-13
AI Technical Summary
Existing mobile communication systems lack efficient methods for setting up, modifying, and canceling command and control (C2) communications, particularly for unmanned aerial vehicles (UAVs), which are crucial for direct and line-of-sight operations.
Implementing systems and methods for C2 communication authorization and discovery procedures through wireless transmit and receive units (WTRUs), including UAVs, using UAS network functions and network functions (NFs) to establish, modify, and cancel C2 communications via PDU sessions, leveraging direct discovery protocols and security credentials.
Enables secure and authorized C2 communications between UAVs and UAV-controllers, supporting direct and network-assisted operations, including beyond visual line of sight, enhancing operational flexibility and safety.
Smart Images

Figure 2024541959000001_ABST
Abstract
Description
[Technical field]
[0001] (CROSS REFERENCE TO RELATED APPLICATIONS) This application claims the benefit of U.S. Provisional Application No. 63 / 276,264, filed November 5, 2021, the contents of which are incorporated herein by reference in their entirety. [Background technology]
[0002] Mobile communications using wireless communication continues to evolve. The fifth generation may be referred to as 5G. The previous (conventional) generation of mobile communications may be, for example, the fourth generation (4G) long term evolution (LTE). Summary of the Invention
[0003] Systems and methods for command and control (C2) communication setup, modification, and / or cancellation are described herein. The C2 communication may be direct C2 communication. The C2 authorization may be performed by a wireless transmit and receive unit (WTRU) (e.g., an unmanned aerial vehicle (UAV)). The C2 authorization may be performed by the WTRU, for example, when the WTRU sends a C2 communication request. The C2 communication request may be sent to an unmanned aerial system (UAS) unmanned service supplier (USS), for example, via a UAS network function (NF), during packet data unit (PDU) session establishment and / or modification. The WTRU may perform discovery of peer WTRUs, for example, after successful authorization.
[0004] For example, the WTRU may perform setup, modification, and / or cancellation of C2 communication (e.g., direct C2 communication). The WTRU (e.g., UAV, UAV-C, etc.) may transmit 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 (e.g., in an authorization response), for example, from a USS via a PDU session modification or separate PDU establishment response message. The authorization may include authorization information. The WTRU may, for example, receive C2 authorization parameters (e.g., in an air container) and use them as part of direct discovery (e.g., unrestricted or restricted direct discovery) to facilitate the discovery procedure with the UAV-C (e.g., UAS app user ID, discovery credentials, etc.). The WTRU may perform (e.g., initiate) discovery. In an embodiment, the WTRU may perform discovery, provided that the WTRU receives C2 authorization information from the USS. The WTRU may use parameters from the USS to enable discovery by the UAV-C.
[0005] In one embodiment, a network function (NF) may perform setup, modification, and / or cancellation of C2 communication (e.g., direct C2 communication). An NF (e.g., UAS NF) may receive an authorization request from a session management function (SMF), for example, to allow C2 on PC5. The UAS NF may forward the authorization request to a 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.
[0006] For example, a management function (e.g., a direct discovery name management function (DDNMF)) may implement a direct discovery procedure for the UAV / UAV-C. The DDNMF may receive a discovery request. The discovery request may include a UAS ProSe App ID (e.g., set to CAA level ID), a WTRU ID, etc. The DDNMF may check for discovery authorization for the UAS ProSe App ID using unified data management (UDM). The DDNMF may interact with the UAS NF, for example, based on associated subscription data (e.g., a UAS App ID is associated with a USS / UAS application). The DDNMF may send a request message to the UAS NF for discovery authorization. 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.
[0007] In an embodiment, the first WTRU may send a first message to the 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 C2 authorization information. The C2 authorization information may include security credentials (e.g., an authorization token) and an identity of the second WTRU. The first WTRU may send a third message to the second WTRU using PC5, for example, if the first WTRU is authorized to communicate with the second WTRU. 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.
[0008] In an embodiment, a network node (e.g., a UAS NF) may send a first message to a second network node indicating a request for authorization associated with the WTRU. 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 (e.g., based on the second message) that the WTRU is authorized to establish C2 on PC5. The network node may determine discovery authorization parameter(s), for example, based on the second message. The network node may send a third message to the WTRU indicating the discovery authorization parameter(s).
[0009] In an embodiment, 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, a UAV identifier, a request type, an application level container, etc. associated with the first WTRU. The request type may indicate whether discovery is unrestricted or restricted. The network node may determine that the first WTRU is authorized to operate as a UAV and / or to conduct 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 transmit a second message indicating an authorization response (e.g., associated with the first message) indicating that the WTRU is authorized to operate as a UAV. The second message may indicate that the first WTRU is authorized to conduct unrestricted discovery (e.g., if the request type is associated with unrestricted discovery). The second message may indicate that the first WTRU is authorized to conduct restricted discovery (e.g., if the request type is associated with restricted discovery). The network node may determine the parameter(s) (e.g., restricted discovery parameters for restricted discovery, unrestricted discovery parameters for unrestricted discovery) based on, for example, the request type.
[0010] The discovery request may be a discovery request to monitor. The discovery request to monitor 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]
[0011] [Figure 1A] FIG. 1 is a system diagram illustrating an example communication system in which one or more disclosed embodiments may be implemented. [Figure 1B] 1B is a system diagram illustrating an example wireless transmit / receive unit (WTRU) that may be used within the communications system illustrated in FIG. 1A, according to one embodiment. [Figure 1C] FIG. 1B is a system diagram illustrating an example Radio Access Network (RAN) and an example Core Network (CN) that may be used within the communication system illustrated in FIG. 1A, according to one embodiment. [Figure 1D] FIG. 1B is a system diagram illustrating a further exemplary RAN and a further exemplary CN that may be used within the communication system illustrated in FIG. 1A, according to one embodiment. [Diagram 2] 1 illustrates an exemplary overview of C2 direct communication on PC5. [Diagram 3] 1 illustrates an exemplary UAV and UAV-C communications network using one or more PLMNs. [Figure 4] An example of PC5 direct communication with C2 authorization is shown, and discovery may follow. [Diagram 5] 1 illustrates an example PC5 direct communication with UAS peer discovery, which may be followed by C2 authorization. [Figure 6] 1 illustrates an example C2 authorization involving a PCF and a USS via a UAS NF. [Figure 7] 13 shows an exemplary announcement request procedure (roaming / inter-PLMN transmission) for contacting a USS via V / local PLMN. [Figure 8] 13 shows an exemplary announcement request procedure (roaming / inter-PLMN transmission) for contacting a USS via V / local PLMN. [Figure 9] 1 illustrates an exemplary announcement request procedure for restricted discovery (non-roaming). [Figure 10] 1 illustrates an exemplary monitor request procedure for restricted discovery (non-roaming). DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0012] 1A illustrates an example 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, broadcasts, 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 communications system 100 may use 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 multicarrier (FBMC), and the like.
[0013] 1A, communications 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, although it will be understood that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Each of 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), mobile stations, fixed or mobile subscriber units, subscription-based units, paging, mobile phones, personal digital assistants (PDAs), smartphones, laptops, netbooks, personal computers, wireless sensors, hotspots or Mi-Fi devices, Internet of Things (loT) devices, watches or other wearable, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., for remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in an industrial and / or automated processing chain context), consumer electronics devices, devices operating in commercial and / or industrial wireless networks, and the like. Any of the WTRUs 102a, 102b, 102c, and 102d may be referred to interchangeably as a UE.
[0014] 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 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 eNode B (eNB), a Home Node B, a Home eNode B, a gNode B (gNB), a NR NodeB, a site controller, an Access Point (AP), a wireless router, etc. Although the base stations 114a, 114b are each illustrated as a single element, it will be understood that the base stations 114a, 114b may include any number of interconnected base stations and / or network elements.
[0015] 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 a cell (not shown). These frequencies may be licensed spectrum, unlicensed spectrum, or a combination of licensed and unlicensed spectrum. A cell may provide wireless service coverage for a particular geographic area, which may be relatively fixed or may change over time. A cell may be further divided into cell sectors. For example, the cell associated with the base station 114a may be divided into three sectors. Thus, in one embodiment, the base station 114a may include three transceivers, i.e., one transceiver for each sector of the cell. In one 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, using beamforming to transmit and / or receive signals in a desired spatial direction.
[0016] 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).
[0017] More specifically, as noted above, the communications 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 stations 114a and the WTRUs 102a, 102b, 102c in the RAN 104 / 113 may implement a radio technology, such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may establish the air interface 115 / 116 / 117 using wideband CDMA (WCDMA). WCDMA may include communications 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 Uplink Packet Access (HSUPA).
[0018] 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).
[0019] In one embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology, such as New Radio (NR) radio access, which may establish the air interface 116 using NR technology.
[0020] 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, e.g., 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 transmitted to / from multiple types of base stations (e.g., eNBs and gNBs).
[0021] In other embodiments, the base station 114a and the WTRUs 102a, 102b, 102c may implement a wireless 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), Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), or the like.
[0022] 1A may be, for example, a wireless router, a Home Node B, a Home eNode B, or an access point, and may utilize any suitable RAT to facilitate wireless connectivity in a localized area, such as an office, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a road, etc. 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 establish a picocell or a femtocell using a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.). As shown in FIG. 1A, the base station 114b may have a direct connection to the Internet 110. Thus, the base station 114b may not need to access the Internet 110 via the CN 106 / 115.
[0023] The RAN 104 / 113 may communicate with the CN 106 / 115, which may be any type of network configured to provide voice, data, application, and / or voice over internet protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. The data may have various quality of service (QoS) requirements, such as different throughput requirements, latency 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, prepaid calling, Internet connectivity, video distribution, etc., and / or perform high level security functions such as user authentication. Although not shown in FIG. 1A, it will be appreciated that the RAN 104 / 113 and / or the CN 106 / 115 may communicate directly or indirectly with other RANs that use 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 communicate with another RAN (not shown) using GSM, UMTS, CDMA2000, WiMAX, E-UTRA, or WiFi radio technology.
[0024] 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 providing 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), user datagram protocol (UDP), and / or the internet protocol (IP) of 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 use the same RAT as the RANs 104 / 113 or a different RAT.
[0025] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communications 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 over different wireless links). For example, the WTRU 102c shown in FIG. 1A may be configured to communicate with a base station 114a, which may use a cellular-based wireless technology, and a base station 114b, which may use an IEEE 802 wireless technology.
[0026] 1B is a system diagram illustrating an example WTRU 102. As shown in FIG. 1B, 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 understood that the WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with an embodiment.
[0027] The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), multiple 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 functionality that enables 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 FIG. 1B illustrates the processor 118 and the transceiver 120 as separate components, it will be understood that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.
[0028] The transmit / receive element 122 may be configured to transmit signals to or receive signals from a base station (e.g., base station 114a) over the 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 IR, UV, or visible light signals, for example. In yet another embodiment, the transmit / receive element 122 may be configured to transmit and / or receive both RF and light signals. It will be appreciated that the transmit / receive element 122 may be configured to transmit and / or receive any combination of wireless signals.
[0029] 1B as a single element, the WTRU 102 may include any number of transmit / receive elements 122. More specifically, the WTRU 102 may use 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.
[0030] The transceiver 120 may be configured to modulate signals transmitted by the transmit / receive element 122 and demodulate signals received by the transmit / receive element 122. As mentioned above, the WTRU 102 may have multi-mode capabilities. Thus, the transceiver 120 may include multiple transceivers to enable the WTRU 102 to communicate via multiple RATs, such as, for example, NR and IEEE 802.11.
[0031] 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 device or an organic light-emitting diode (OLED) display device), which may receive user-entered data from the speaker / microphone 124, the keypad 126, and / or the display / touchpad 128. 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 non-removable memory 130 and / or 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, etc. In other embodiments, the processor 118 may access information from and store data in memory that is not physically located on the WTRU 102, such as on a server or a home computer (not shown).
[0032] The processor 118 may receive power from the power source 134 and may be configured to distribute and / or control the power to other components in the WTRU 102. The power source 134 may be any suitable device for providing power to the WTRU 102. For example, the power source 134 may include one or more dry batteries (e.g., nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, etc.
[0033] The processor 118 may also be coupled to a GPS chipset 136, which may be configured to provide position information (e.g., longitude and latitude) regarding a current location of the WTRU 102. In addition to or in lieu of information from the GPS chipset 136, the WTRU 102 may receive position 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 being received from two or more nearby base stations. It will be appreciated that the WTRU 102 may obtain position information by way of any suitable position determination method while remaining consistent with an embodiment.
[0034] The processor 118 may further be coupled to other peripherals 138, which may include one or more software 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 videos), a Universal Serial Bus (USB) port, a vibration device, a television transceiver, a hands-free headset, a Bluetooth module, a Frequency Modulated (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, a Virtual Reality and / or Augmented Reality (VR / AR) device, an activity tracker, and the like. The peripherals 138 may include one or more sensors, which may be one or more of 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.
[0035] The WTRU 102 may include a full-duplex radio where the transmission and reception of some or all of the signals associated with a particular subframe (e.g., for both the UL (e.g., for transmission) and the downlink (e.g., for reception) may be parallel and / or simultaneous. The full-duplex radio may include an interference management unit to reduce and or substantially eliminate self-interference via either hardware (e.g., a choke) or signal processing via a processor (e.g., via a separate processor (not shown) or the processor 118). In one embodiment, the WRTU 102 may include a half-duplex radio for the transmission and reception of either some or all of the signals (e.g., associated with a particular subframe for either the UL (e.g., for transmission) or the downlink (e.g., for reception)).
[0036] 1C is a system diagram illustrating the RAN 104 and the CN 106, according to one embodiment. As mentioned above, the RAN 104 may communicate with the WTRUs 102a, 102b, 102c over the air interface 116 using E-UTRA radio technology. The RAN 104 may also communicate with the CN 106.
[0037] The RAN 104 may include eNode-Bs 160a, 160b, 160c, although it will be understood that the RAN 104 may include any number of eNode-Bs while remaining consistent with an embodiment. The eNode-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 an embodiment, the eNode-Bs 160a, 160b, 160c may implement MIMO technology. Thus, the eNode-B 160a may, for example, use multiple antennas to transmit wireless signals to and / or receive wireless signals from the WTRU 102a.
[0038] Each of the eNode-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, user scheduling, etc. in the UL and / or DL. As shown in FIG 1C, the eNode-Bs 160a, 160b, 160c may communicate with each other via an X2 interface.
[0039] 1C may include a mobility management entity (MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN) gateway (or PGW) 166. Although each of the foregoing elements is illustrated as part of the CN 106, it will be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.
[0040] The MME 162 may be connected to each of the eNode-Bs 162a, 162b, 162c in the RAN 104 via an S1 interface and may function as a control node. For example, the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, activating / deactivating bearers, selecting a particular serving gateway during initial attachment 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.
[0041] The SGW 164 may be connected to each of the eNodeBs 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-eNode B handover, triggering paging when DL data is available to the WTRUs 102a, 102b, 102c, managing and storing the context of the WTRUs 102a, 102b, 102c, etc.
[0042] The SGW 164 may be connected to a 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.
[0043] 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 communicate 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.
[0044] Although the WTRU is illustrated in FIGS. 1A-1D as a wireless terminal, it is contemplated that in certain representative embodiments such a terminal may use a wired communications interface with the communications network (e.g., temporarily or permanently).
[0045] In an exemplary embodiment, the other network 112 may be a WLAN.
[0046] A WLAN in infrastructure Basic Service Set (BSS) mode may have an access point (AP) of the BSS and one or more stations (STAs) associated with the AP. The AP may have access or interface to a Distribution System (DS) or another type of wired / wireless network that carries traffic into and / or out of the BSS. Traffic originating from outside the BSS to the STAs may arrive through the AP and be delivered to the STAs. Traffic originating from the STAs to destinations outside the BSS may be sent to the AP and delivered to the respective destination. Traffic between STAs in the BSS may be sent, for example, through the AP, where the source STA may send traffic to the AP, which may deliver the traffic to the destination STA. Traffic between STAs in the BSS may be considered and / or referred to as peer-to-peer traffic. Peer-to-peer traffic may be sent in a Direct Link Setup (DLS) between the source STA and the destination STA (e.g., directly between them). In certain representative embodiments, the DLS may use 802.11e DLS or 802.11z tunneled DLS (TDLS). A WLAN using an Independent BSS (IBSS) mode may not have an AP, and the STAs (e.g., all of the STAs) within or using the IBSS may communicate directly with each other. The IBSS mode of communication may be referred to herein as an "ad-hoc" communication mode.
[0047] When using an 802.11ac infrastructure mode of operation or a similar mode of operation, an 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 20 MHz wide bandwidth) or a width that is dynamically set via signaling. The primary channel may be an operating channel of the BSS and may be used by STAs to establish a connection with the AP. In certain representative embodiments, for example, in an 802.11 system, Carrier Sense Multiple Access with Collision Avoidance (CSMA / CA) may be implemented. With CSMA / CA, STAs (e.g., all STAs), including the AP, may sense the primary channel. If the primary channel is sensed / detected and / or determined to be active by a particular STA, the particular STA may back off. One STA (e.g., only one station) may transmit at any given time in a given BSS.
[0048] A High Throughput (HT) STA may use a 40 MHz wide channel for communication, which may be formed, for example, through a combination of a 20 MHz primary channel and adjacent or non-adjacent 20 MHz channels.
[0049] A Very High Throughput (VHT) STA may support 20 MHz, 40 MHz, 80 MHz, and / or 160 MHz wide channels. A 40 MHz and / or 80 MHz channel may be formed by combining multiple contiguous 20 MHz channels. A 160 MHz channel may be formed by combining eight contiguous 20 MHz channels or by combining two non-contiguous 80 MHz channels, which 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, which may split the data into two streams. Inverse Fast Fourier Transform (IFFT) processing and time domain processing may be performed separately on each stream. The streams may be mapped to two 80 MHz channels, and the data may be transmitted by the 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 transmitted to the Medium Access Control (MAC).
[0050] Sub-1 GHz operating modes are supported by 802.11af and 802.11ah. Channel operating bandwidths and carriers are reduced in 802.11af and 802.11ah compared to those used in 802.11n and 802.11ac. 802.11af supports 5 MHz, 10 MHz, and 20 MHz bandwidths in TV White Space (TVWS) spectrum, and 802.11ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum. According to a representative embodiment, 802.11ah may support meter-type control / machine-type communication, such as MTC devices in macro communication coverage areas. MTC devices may have limited functionality, including specific functions, for example, support for (e.g., support only for) specific and / or limited bandwidths. MTC devices may include a battery with a battery life above a threshold (e.g., to maintain a very long battery life).
[0051] WLAN systems that may support multiple channels and channel bandwidths, such as 802.11n, 802.11ac, 802.11af, and 802.11ah, include a channel that may be designated as a primary channel. 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 by the STA and / or limited among all STAs operating in the BSS that support the smallest bandwidth operating mode. In an 802.11ah embodiment, the primary channel may be 1 MHz wide for STAs (e.g., MTC type devices) that support (e.g., only) the 1 MHz mode, even if the AP and other STAs in the BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, 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. For example, if the primary channel is active due to a STA (that only supports the 1 MHz mode of operation) transmitting to the AP, the entire available frequency band may be considered active even though most of the frequency band may remain dormant and available.
[0052] In the United States, the available frequency band that can be used by 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.
[0053] 1D is a system diagram illustrating the RAN 113 and the CN 115, according to one embodiment. As mentioned above, the RAN 113 may communicate with the WTRUs 102a, 102b, 102c over the air interface 116 using NR radio technology. The RAN 113 may also communicate with the CN 115.
[0054] The RAN 113 may include gNBs 180a, 180b, 180c, although it will be understood 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 for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In an embodiment, the gNBs 180a, 180b, 180c may implement MIMO technology. For example, the gNBs 180a, 108b may utilize beamforming to transmit signals to and / or receive signals from the gNBs 180a, 180b, 180c. Thus, the gNB 180a may transmit wireless signals to and / or receive wireless signals from the WTRU 102a, for example, using multiple antennas. 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, and the remaining component carriers may be on a licensed spectrum. In one embodiment, the gNBs 180a, 180b, 180c may implement Coordinated Multi-Point (CoMP) technology. For example, the WTRU 102a may receive coordinated transmissions from the gNBs 180a and 180b (and / or gNB 180c).
[0055] The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using transmissions associated with scalable value configurations. For example, the 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 different or scalable lengths (e.g., including different numbers of OFDM symbols and / or lasting different lengths of absolute time).
[0056] 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 without accessing another RAN (e.g., eNode-Bs 160a, 160b, 160c, etc.). In a standalone configuration, the WTRUs 102a, 102b, 102c may utilize 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 unlicensed bands. In a non-standalone configuration, the WTRUs 102a, 102b, 102c may communicate with and connect to a gNB 180a, 180b, 180c while also communicating with and connecting to another RAN, such as an eNode-B 160a, 160b, 160c. For example, the WTRUs 102a, 102b, 102c may implement DC principles 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-Bs 160a, 160b, 160c may act as mobility anchors for the WTRUs 102a, 102b, 102c, and the gNBs 180a, 180b, 180c may provide additional coverage and / or throughput for serving the WTRUs 102a, 102b, 102c.
[0057] 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 the UL and / or DL, support for network slicing, dual connectivity, interworking between NR and E-UTRA, routing of user plane data to User Plane Functions (UPFs) 184a, 184b, routing of control plane information to Access and Mobility Management Functions (AMFs) 182a, 182b, etc. As shown in FIG. 1D, the gNBs 180a, 180b, 180c may communicate with each other via an Xn interface.
[0058] 1D 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. Although each of the foregoing elements is illustrated as part of the CN 115, it will be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.
[0059] The AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via an N2 interface and may function as a control node. For example, the AMF 182a, 182b may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, supporting network slicing (e.g., handling different PDU sessions with different requirements), selecting a particular SMF 183a, 183b, managing registration areas, terminating NAS signaling, mobility management, etc. Network slicing may be used by the AMF 182a, 182b to customize the CN support of the WTRUs 102a, 102b, 102c based on the type of service utilizing the WTRUs 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 massive 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.
[0060] The SMFs 183a, 183b may be connected to the AMFs 182a, 182b in the CN 115 via an N11 interface. The SMFs 183a, 183b may also be connected to the UPFs 184a, 184b in the CN 115 via an N4 interface. The SMFs 183a, 183b may select and control the UPFs 184a, 184b and configure the routing of traffic through the UPFs 184a, 184b. The SMFs 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.
[0061] The UPFs 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 UPFs 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.
[0062] The CN 115 may facilitate communication with other networks. For example, the CN 115 may include or 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 through the UPFs 184a, 184b via an N3 interface to the UPFs 184a, 184b and an N6 interface between the UPFs 184a, 184b and the DNs 185a, 185b.
[0063] 1A-1D and the corresponding description thereof, one or more or all of the functions described herein with respect to one or more of the WTRUs 102a-d, base stations 114a-b, eNode-Bs 160a-c, MME 162, SGW 164, PGW 166, gNBs 180a-c, AMFs 182a-b, UPFs 184a-b, SMFs 183a-b, DNs 185a-b, and / or any other device(s) described herein may be performed by one or more emulation devices (not shown). The emulation devices may be one or more devices configured to emulate one or more or all of the functions described herein. For example, the emulation devices may be used to test other devices and / or to simulate network and / or WTRU functions.
[0064] The emulation device may be designed to implement one or more tests of other devices in a lab environment and / or an operator network environment. For example, one or more emulation devices may perform one or more or all of the functions while fully or partially implemented and / or deployed as part of a wired and / or wireless communication network to test other devices in the communication network. One or more emulation devices may perform one or more or all of the functions while temporarily implemented / deployed as part of a wired and / or wireless communication network. The emulation device may be directly coupled to another device for testing purposes and / or may use terrestrial wireless communication to implement the tests.
[0065] One or more emulation devices may perform one or more functions, inclusive, while not being implemented / deployed as part of a wired and / or wireless communication network. For example, the emulation devices may be utilized in test scenarios in a test lab and / or in undeployed (e.g., test) wired and / or wireless communication networks to implement testing of one or more components. One or more of the emulation devices may be test equipment. Direct RF coupling and / or wireless communication via RF circuitry (which may include, for example, one or more antennas) may be used by the emulation devices to transmit and / or receive data.
[0066] Systems and methods for command and control (C2) communication setup, modification, and / or cancellation are described herein. The C2 communication may be direct C2 communication. The C2 authorization may be performed by a wireless transmit / receive unit (WTRU) (e.g., an unmanned air vehicle (UAV)). The C2 authorization may be performed by the WTRU, for example, when the WTRU sends a C2 communication request. The C2 communication request may be sent to an unmanned air system (UAS) service provider (USS), for example, via a UAS network function (NF), during packet data unit (PDU) session establishment and / or modification. The WTRU may perform discovery of peer WTRUs, for example, after successful authorization.
[0067] For example, the WTRU may perform setup, modification, and / or cancellation of C2 communications (e.g., direct C2 communications). The WTRU (e.g., UAV, UAV-C, etc.) may transmit an authorization request (e.g., C2 authorization request on PC5) during PDU session establishment and / or modification. The authorization request may correspond to C2 communications, such as direct or line-of-sight C2 communications. The WTRU may receive authorization for direct C2 (e.g., in an authorization response), e.g., from a USS, via a PDU session modification or separate PDU establishment response message. The authorization may include authorization information. The WTRU may, for example, receive C2 authorization parameters (e.g., in an air container) to facilitate discovery procedures with the UAV-C (e.g., UAS app user ID, discovery credentials, etc.) and use them as part of direct discovery (e.g., unrestricted or restricted direct discovery). The WTRU may perform (e.g., initiate) discovery. In an embodiment, the WTRU may perform discovery, provided that the WTRU receives C2 authorization information from the USS. The WTRU may use parameters from the USS to enable discovery by the UAV-C.
[0068] In one embodiment, a network function (NF) may perform setup, modification, and / or cancellation of C2 communication (e.g., direct C2 communication). An NF (e.g., UAS NF) may receive an authorization request from a session management function (SMF), for example, to allow C2 on PC5. The UAS NF may forward the authorization request to a 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.
[0069] For example, a management function (e.g., a Direct Discovery Name Management Function (DDNMF)) may implement a direct discovery procedure for the UAV / UAV-C. The DDNMF may receive a discovery request. The discovery request may include a UAS ProSe App ID (e.g., set to CAA level ID), a WTRU ID, etc. The DDNMF may check using Unified Data Management (UDM) for discovery authorization for the UAS ProSe App ID based on associated subscription information. The DDNMF may decide to interact with a UAS NF based on, for example, associated subscription data (e.g., a UAS App ID is associated with a USS / UAS application). The DDNMF may send a request message to the UAS NF for discovery authorization. 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.
[0070] In an embodiment, the first WTRU may send a first message to the 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 C2 authorization information. The C2 authorization information may include security credentials (e.g., an authorization token) and an identity of the second WTRU. The first WTRU may send a third message to the second WTRU using PC5, for example, if the first WTRU is authorized to communicate with the second WTRU. 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.
[0071] In an embodiment, a network node (e.g., a UAS NF) may send a first message to a second network node indicating a request for authorization associated with the WTRU. 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 (e.g., based on the second message) that the WTRU is authorized to establish C2 on PC5. The network node may determine discovery authorization parameter(s), for example, based on the second message. The network node may send a third message to the WTRU indicating the discovery authorization parameter(s).
[0072] In an embodiment, 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, a UAV identifier, a request type, an application level container, etc. associated with the first WTRU. The request type may indicate whether the discovery is unrestricted discovery or restricted discovery. The network node may determine that the first WTRU is authorized to operate as a UAV and / or to conduct 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 transmit a second message indicating an authorization response (e.g., associated with the first message) indicating that the WTRU is authorized to operate as a UAV. The second message may indicate that the first WTRU is authorized to conduct unrestricted discovery (e.g., if the request type is associated with unrestricted discovery). The second message may indicate that the first WTRU is authorized to conduct restricted discovery (e.g., if the request type is associated with restricted discovery). The network node may determine the parameter(s) (e.g., restricted discovery parameters for restricted discovery, unrestricted discovery parameters for unrestricted discovery) based on, for example, the request type.
[0073] The discovery request may be a discovery request to monitor. The discovery request to monitor may indicate a subscription identifier, a UAV identifier, a PDU ID associated with the first WTRU, a target subscription identifier, a target UAV identifier, and / or a target PDU ID associated with the second WTRU. The network node may send a message indicating a monitoring response.
[0074] Unmanned (e.g., crewless) air systems (UAS) may be supported. Additional extensions may be provided for UAS support. Unmanned (e.g., crewless) air vehicles (UAVs) may be controlled using command and control (C2) messages and / or communications from, for example, a UAV Controller (UAV-C) and / or a UAS service supplier (USS) / UAS traffic manager (UTM).
[0075] The types of C2 communication may include one or more of direct communication, network-assisted communication, or UTM-navigated communication. Direct C2 communication may correspond to UAV-C and / or UAVs using a direct C2 communication link (e.g., D2D, PC5) to communicate. Network-assisted C2 communication may correspond to UAV-C and UAVs using a unicast C2 communication link (e.g., via Uu) with a network to communicate. Beyond visible line of sight (BVLOS) of UAVs may be enabled / supported, for example, using network-assisted C2 communication (e.g., different from direct C2 communication). UTM-navigated C2 communication may correspond to UAVs with autonomous flight capabilities that may be capable of flying according to a pre-scheduled flight plan under the supervision of the UTM. The C2 communication link between the UAV and the UTM may be used for flight monitoring, dynamic route updates, and / or ad-hoc navigation.
[0076] ProSe (e.g., 5G ProSe) may support PC5 direct communication between WTRUs (e.g., two WTRUs) and may enable discovery, for example, by using a Direct Discovery Name Management Function (DDNMF) and leveraging a ProSe application server. ProSe (e.g., 5G ProSe) may support discovery and communication for WTRUs in general (e.g., WTRUs that are not UAVs).
[0077] Support may be provided for (e.g., only for) indirect C2 communication, e.g., the USS may authorize C2 communication (e.g., via the UAS Network Function (NF)). C2 communication may be conducted using (e.g., through) PDU sessions. The UAV may discover the UAV-C (which may be a non-networked device, e.g., a ground station with an Internet connection) for C2 communication, e.g., by obtaining a UAV-C IP address from the USS with network assistance, e.g., during a pairing / C2 authorization procedure.
[0078] A web-based API interface between the core network and the USS may be provided and / or used.
[0079] One or more mechanisms for supporting authorization for direct C2 communications (e.g., via PC5) may be enabled. For example, mechanisms for supporting authorization for direct C2 communications (e.g., via PC5) may be enabled when a UAV may (e.g., may need to) fly in proximity to a UAV-C within line of sight (LOS). For example, mechanisms for supporting authorization for direct C2 communications (e.g., via PC5) may be enabled when an operator or USS may (e.g., needs to) restrict operations to LOS (e.g., LOS only).
[0080] In some communications technologies, such as 5G ProSe, authorization for direct one-to-one communications may not support scenarios in which third party (e.g., USS) authorization may be used (e.g., required) for provisioning of C2 authorization in addition to MNO authorization. Mechanisms to support authorization for direct C2 communications by a USS may be used (e.g., required) to complement existing mechanisms for network-assisted C2 communications authorization.
[0081] C2 communication authorization, such as direct C2 communication authorization, may be enabled, for example, by leveraging a network exposure function (NEF) / UAS NF to accommodate web-based API interface requirements from this vertical. For direct C2 communication, it may be desirable for the peers (e.g., UAV and UAV-C) to perform discovery and link establishment, for example, leveraging existing 5G ProSe-enabled procedures.
[0082] The UAV and UAV-C may discover each other, establish communication links, modify communication links, and / or release communication links used for direct (D2D, PC5) C2 communications. The UAV and UAV-C may be authorized for LOS / D2D C2 (e.g., by leveraging USS UAV authorization / authentication (UUAA) and / or C2 authorization). The UAV and UAV-C may discover and connect LOS / D2D C2 communications. The USS / UTM can be used to establish, modify, and revoke direct security associations used for C2 communications. The UAV and UAV-C can authenticate each other and establish secure PC5 links for C2 communications.
[0083] FIG. 2 illustrates an example overview of C2 direct communication over PC5. C2 over PC5 may be provided, for example, to add support for authorization of LOS operation. Direct C2 authorization may be performed, for example, when a ProSe-enabled UAV (e.g., WTRU) sends a (e.g., direct) C2 communication request to a USS (e.g., via a UAS NF during PDU session establishment / modification). The UAV / UAV-C may perform discovery of peer UAV-C / UAV, for example, based on (e.g., thereafter) successful authorization.
[0084] Discovery may be dynamic, for example, by leveraging the DDNMF (e.g., using unrestricted / restricted modes of discovery). Discovery may be static, for example, by involving a policy control function (PCF), an SMF, and / or a USS. The UAV(s) may receive dynamic discovery code(s) from the DDNMF (e.g., directly). The discovery code(s) may be provisioned by the PCF using USS-initiated policy configuration.
[0085] PC5 link establishment may be performed, for example, after (e.g., secure) discovery of the UAS peer(s). This D2D link may be secured using existing security mechanisms.
[0086] For example, the system may provide communication 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 the UAV or UAV-C herein. For example, the roles of the UAV and UAV-C may be interchangeable in the procedures described herein. For example, during a direct discovery procedure, the UAV may correspond to a role of discoverer / monitor and the UAV-C may correspond to a role of discoveree / announcer, or vice versa. The UAV or UAV-C may initiate the direct link establishment procedure. Both the UAV and UAV-C may perform direct C2 authorization. The civil aviation administration-level identity (CAA-level ID) and WTRU ID referred to in this specification may correspond to the CAA-level UAV ID and UAV ID (e.g., GPSI) for a UAV, or an equivalent identifier for a UAV-C.
[0087] 3 illustrates an exemplary UAV and UAV-C communication network using one or more PLMNs. As shown in FIG. 3, the UAV and UAV-C may be connected to different PLMNs and then connected to the same USS.
[0088] C2 communication authorization, such as direct C2 communication authorization, may be provided to the UAV / UAV-C. The C2 authorization may be extended to allow C2 via Uu and / or directly (e.g., PC5).
[0089] The WTRU (e.g., UAV and / or UAV-C) may indicate LOS and / or BVLOS or direct and / or network-assisted / indirect C2 communication when requesting C2 authorization, for example, in a PDU session establishment / modification request message (e.g., in a NAS message, in a UAS container). The WTRU may indicate its support for direct C2 communication (e.g., C2 over PC5) in the C2 authorization request.
[0090] The WTRU may obtain authorization information for direct C2 communication (e.g., parameters for peer discovery such as peer(s) 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., by the network), e.g., in a UAS application container.
[0091] A network function (e.g., SMF) that initiates a C2 authorization procedure with the USS may determine whether the WTRU supports direct C2 communications, e.g., based on the WTRU's capability information, and may determine whether the WTRU supports / is authorized for communications, such as ProSe communications. The network function may include a C2 support indication, such as direct C2 support, in the authorization request to the USS.
[0092] The UAS NF / NEF may receive C2 authorization information from the USS for LOS / direct and / or BVLOS / indirect communication. The C2 authorization information may include peer(s) CAA level ID / WTRU ID and / or security credentials to establish a secure direct / indirect link for C2 communication. The UAS NF may map the aviation domain (e.g., LOS / BVLOS) authorization information parameters to C2 on a direct link (e.g., PC5) or an indirect link (e.g., over Uu), respectively. The UAS NF may send the authorization information to the SMF / PCF.
[0093] In an embodiment, the USS may provide authorization for direct C2 communication (e.g., via the UAS NF) while refraining from providing (e.g., not providing) policy configuration information corresponding to a PDU session established for C2 communication (e.g., refraining from providing (e.g., not providing) an authorized peer UAV-C IP address via the UAS NF), for example, if the UAV is restricted to LOS operation. The USS may enable both communication modes, whereby the UAV and UAV-C may switch C2 communication between the direct / LOS and indirect / BVLOS communication modes, for example, using a C2 switching mechanism.
[0094] Peer discovery, such as direct discovery of UAV / UAV-C peers, may be enabled. The DDNMF / PCF may be extended to support dynamic / static discovery between UAVs and UAV-Cs. The DDNMF may use an interface with the UAS NF for USS-assisted authorization of UAV-UAV-C direct discovery (e.g., to obtain code seed, UAS peer(s) identifier(s), discovery key information).
[0095] The DDNMF may receive a discovery request including a ProSe App ID corresponding to a UAS ProSe App ID (e.g., set to a CAA level ID), a WTRU ID, and / or a UAS App ID. The DDNMF may check, using Unified Data Management (UDM), that authorization for discovery of the ProSe App ID / UAS ProSe App ID may be determined to interact with the UAS NF, for example, based on associated subscription data (e.g., the UAS App ID is associated with a USS / UAS application). The DDNMF may send a request message to the UAS NF for discovery authorization. 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.
[0096] In an embodiment, the USS may configure the PCF with discovery authorization information (e.g., USS-assigned discovery code / code suffix, discovery credentials), for example, via the UAS NF as part of a policy control procedure initiated during a C2 authorization procedure (e.g., as described herein).
[0097] The WTRU may, for example, use a discovery code obtained from the DDNMF or SMF / PCF to perform direct discovery of UAS peers (e.g., via PC5). In an embodiment, direct discovery and communication may be performed using direct WLAN communication. The discovery code may be associated with or correspond to an SSID.
[0098] Direct C2 communications may be established between the UAV and UAV-C. The UAV and UAV-C IP may establish secure PC5 communications using USS assistance. The UAV may use credentials for direct C2 communications received as part of a direct C2 authorization (e.g., as described herein). The authorization information may include P5 link security key information (e.g., a shared key between the UAV and UAV-C).
[0099] Direct C2 authorization and discovery models may be provided. The first model (e.g., Model #1) may correspond to direct C2 authorization for direct discovery. In the first model (e.g., Model #1), the UAV / UAV-C may be authorized for C2 communication with a peer UAV-C / UAV after, for example, successful authentication and authorization by the USS (e.g., whereby a peer identifier may be pre-configured in the UAV or USS). The UAV / UAV-C may perform direct discovery and direct link establishment for C2 communication after, for example, successful C2 authorization. The first model may be used, for example, when the pairing between the UAV and the UAV-C is pre-determined / pre-configured (e.g., by the pilot, USS).
[0100] FIG. 4 illustrates an example of PC5 direct communication with C2 authorization followed by discovery. As shown in FIG. 4, UUAA (e.g., conventional UUAA) may be performed, for example, by the UAV / UAV-C (e.g., WTRU). The WTRU may be ProSe-enabled. The WTRU may provide related functionality when registering with the network. As shown in FIG. 4, the WTRU may perform C2 authorization for LOS / direct and / or BVLOS / indirect C2 communication (e.g., as described herein) based, for example, on pre-configured UAS peers within the WTRU or in a USS. As shown in FIG. 4, 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, once the WTRU is authorized for C2 communication. The DDNMF may contact the UAS NF to retrieve discovery authorization information (e.g., authorization indication / flag, UAS peer identifier(s), remote identifier) providing the WTRU ID and / or the WTRU's ProSe app user ID, for example, if the WTRU performs a direct discovery procedure ProSe. The UAS NF may retrieve corresponding authorization information from the USS during C2 authorization, for example, using the provided identifiers. The UAS NF may contact the USS for authorization (e.g., additional authorization) for discovery (e.g., in case of UAS peer(s) identifier(s) at the UAS NF). As shown in FIG. 4, a secure direct link establishment between the peers may be performed (e.g., using the credentials received during the C2 authorization procedure).
[0101] 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 for performing C2 communication, e.g., after successful authentication and authorization by the USS. The WTRU may perform C2 authorization, e.g., using the discovered peer identifier. The WTRU may perform direct link establishment for C2 communication, e.g., after successful C2 authorization. The second model may be used, e.g., when pairing between the UAV and UAV-C is not predetermined (e.g., ad-hoc pairing, self-service model).
[0102] In an embodiment, the discovery type (e.g., unrestricted / restricted) may be communicated / established at the UAS application layer (e.g., as part of the UAS app container), e.g., in an end-to-end interaction between the USS and the UAV / UAV-C (e.g., as described herein with respect to FIGS. 5-10). For example, the parameter(s) (e.g., discovery type / request type) in the discovery message may be optional (e.g., in the case of a UAV). Whether the WTRU is monitoring / announcing may be established, e.g., based on the roles assigned to the UAV and UAV-C by the application / USS (e.g., based on application preferences, the UAV-C may be monitoring and the UAV may be announcing, 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 the UAS NF with information regarding the type of request, and (e.g., in response thereto) the UAS NF may send the (e.g., requested) information to the DDNMF (e.g., to monitor for a restricted request). The UAS NF may provide the target UAS peer identifier, for example, if the USS is not directly involved and the DDNMF is communicating with the UAS NF.
[0103] FIG. 5 illustrates an example PC5 direct communication with UAS peer discovery followed by C2 authorization. As shown in FIG. 5 (e.g., at 501 in FIG. 5), UUAA (e.g., conventional UUAA) may be performed by the UAV / UAV-C (e.g., WTRU), e.g., as described herein with respect to FIG. 4. As shown in FIG. 5 (e.g., at 502 in FIG. 5), dynamic discovery of UAS peers may be performed initially for (e.g., ad-hoc) pairing, e.g., instead of performing a C2 authorization procedure (e.g., as described in FIG. 4 with respect to Model #1). In an embodiment, the WTRU (e.g., UAV) may have peer information (e.g., peer identifiers) preconfigured (e.g., may receive configuration information indicating the peer information). The WTRU may match (e.g., may attempt to match) the peer information during the discovery procedure (e.g., as ProSe user information). In an embodiment, the WTRU may be pre-configured (e.g., by the PCF) with a ProSe service code corresponding to a UAS service code (USC) used for UAS peer discovery. The WTRU may use the USC to obtain peer WTRU information (e.g., set to a CAA level ID) during discovery. As shown in FIG. 5 (e.g., at 503 in FIG. 5), the WTRU may send the discovered peer information (e.g., an identifier of the peer (e.g., CAA level UAV ID or generic public subscription identifier (GPSI))) in a C2 authorization request (e.g., instead of using a pre-configured peer identifier), e.g., once the WTRU discovers its peer using a code provisioned by the DDNMF / PCF. As shown in FIG. 5 (e.g., at 504 in FIG. 5), secure direct link establishment between the peers is performed as described above, e.g., based on successful C2 authorization.
[0104] C2 authorization, such as direct C2 authorization (e.g., non-roaming), may be implemented. FIG. 6 illustrates an example C2 authorization involving a PCF and a USS via a UAS NF. As illustrated in FIG. 6 (e.g., at 601 in FIG. 6), a WTRU (e.g., a ProSe-enabled WTRU) may send a PDU session establishment / modification request for direct C2 communication (e.g., with a second WTRU) to an SMF. The message may include a C2 authorization request on PC5 (e.g., a first message, where 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 a USS (e.g., via a UAS NF).
[0105] As shown in FIG. 6 (e.g., at 602 in FIG. 6), 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 provision C2 authorization information (e.g., indication / code and security information) for the PCF and provide the C2 authorization information to the PCF. The USS may provide the UAS NF in the home PLMN (HPLMN), for example, an authorization token that the UAS NF can use to request discovery authorization from the USS while the WTRU is roaming (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, e.g., based on successful authorization from the USS (e.g., the UAS NF may determine that the WTRU is authorized to establish C2 on PC5, e.g., based on successful authorization from the USS (e.g., an indicated response to the request and indicated policy setting information).
[0106] As shown in FIG. 6 (e.g., at 603 in FIG. 6), authorization to initiate discovery may be provided to the WTRU by a subsequent PDU session modification command (e.g., indicating discovery authorization parameters). Direct C2 authorization may be provided by the PCF in the UCU. The WTRU may determine that it is authorized to communicate with the second WTRU (e.g., based on the C2 authorization and the C2 authorization information (the C2 authorization information includes security credentials and an identity of the second WTRU)). The WTRU may use PC5 (e.g., based on the C2 authorization) to send a message to the second WTRU, e.g., using security credentials (e.g., an authorization token). The message may indicate a request to perform discovery and / or link establishment procedures. The message may be protected (e.g., authenticated and / or encrypted), e.g., using the security credentials.
[0107] The UAV / UAV-C may, for example, broadcast a CAA level ID which it receives during C2 authorization to discover and establish a link with the UAV-C / UAV.
[0108] ProSe discovery may be performed. For example, ProSe discovery may correspond to unrestricted discovery (e.g., roaming). FIG. 7 illustrates an example announcement request procedure (roaming / inter-PLMN transmission) contacting a USS via a V / local PLMN. As shown in FIG. 7, the WTRU may be permitted 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 DDNMF1 (e.g., as shown at 701 in FIG. 7).
[0109] As shown in FIG. 7 (e.g., at 702 in FIG. 7), the DDNMF1 may check the authorization of the application represented by the Application ID. The UDM may provide the PLMN ID (e.g., Visited PLMN (VPLMN)) where the WTRU is registered. The DDNMF may determine that it needs to contact the UAS NF based on, for example, subscription data associated with the App ID (e.g., corresponding to the UAS App ID).
[0110] As shown in FIG. 7 (e.g., at 703 in FIG. 7), the DDNMF1 may send an authorization request (e.g., GPSI (e.g., subscription identifier associated with the WTRU), CAA level ID (e.g., UAV identifier), request type, application ID, UAS container) to the DDNMF2 in the VPLMN (e.g., if the USS authorized the WTRU / UAV via the UAS NF2 in the VPLMN (e.g., in a UUAA procedure). The DDNMF1 may indicate that discovery authorization can be obtained via the UAS NF (e.g., indicating an authorization request associated with discovery).
[0111] As shown in FIG. 7 (e.g., at 704 in FIG. 7), the DDNMF2 may forward the authorization request (e.g., received from the DDNMF1 as described herein) to the UAS NF2. The UAS NF2 may forward the request to the USS, for example, if direct C2 authorization information for discovery is not available at the UAS NF2 (e.g., discovery is performed prior to C2 authorization or the (e.g., requesting) USS explicitly authorizes direct discovery). The UAS NF2 may determine (e.g., based on an indication received from the USS) that the WTRU is authorized to operate as a UAV and / or conduct C2 communications.
[0112] 7 (e.g., at 705 of FIG. 7), the UAS NF2 may send an authorization response (e.g., response type, authorization indication to announce, discovery code material) message to the DDNMF2 (e.g., sending a second message indicating that the first WTRU is authorized to operate as a UAV). The UAS NF2 may generate the response from locally stored information (e.g., from previous C2 authorization information) and / or after requesting a USS.
[0113] As shown in FIG. 7 (eg, at 706 in FIG. 7), DDNMF2 can forward the message from UASNF2 / USS to the requester DDNMF1 in the HPLMN.
[0114] As shown in FIG. 7 (eg, at 707 in FIG. 7), the DDNMF1 in the HPLMN may respond to the WTRU with a discovery response (eg, GPSI, CAA level ID, discovery code material).
[0115] For example, ProSe discovery may correspond to unrestricted discovery (e.g., roaming). FIG. 8 illustrates an example monitor request procedure for discovery (non-roaming) that contacts the USS by obtaining a USS address from a local PLMN. As shown in FIG. 8, the WTRU may be permitted 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 DDNMF1 (e.g., at 801 in FIG. 8).
[0116] As shown in FIG. 8 (e.g., at 802 in FIG. 8), the DDNMF1 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 it can (e.g., needs to) contact the UAS NF based on, for example, subscription data associated with the app ID (e.g., UAS app id).
[0117] As shown in FIG. 8 (e.g., at 803 in FIG. 8), the DDNMF1 may send a PC5 authorization request to the DDNMF2 (e.g., in the VPLMN where the USS authorized the WTRU / UAV via the VPLMN's UAS NF2). The authorization request may include a GPSI and / or a CAA level ID. The DDNMF1 may indicate that discovery authorization information is obtained (e.g., via the UAS NF). The DDNMF1 may indicate that the HPLMN may contact the USS directly. The UAS NF2 may verify that a valid UAAA / C2 authorization is stored for this GPSI mapped to the WTRU. The UAS NF2 may verify that an authorization token is available (e.g., to allow the HPLMN to contact the USS via the UAS NF1, for example).
[0118] As shown in FIG. 8 (e.g., at 804 in FIG. 8), the UAS NF2 can send a PC5 authorization response (e.g., based on stored information) to the DDNMF1 (e.g., GPSI, CAA level ID, authorization information (e.g., USS address, authorization token that allows the HPLMN to directly contact the USS)).
[0119] As shown in FIG. 8 (e.g., at 805 in FIG. 8), DDNMF1 can send an authorization request (e.g., CAA level ID, request type (unrestricted / restricted), authorization token from VPLMN / UAS NF2, app level container) to UAS NF1. UAS NF1 can forward the request to a USS, for example, if valid authorization information is not available locally.
[0120] As shown in Figure 8 (e.g., at 806 in Figure 8), the UAS NF1 may return an authorization response (e.g., response type, discovery code material) message to the DDNMF2 of the HPLMN. The UAS NF1 may generate the response from locally stored information (e.g., from a previous discovery / C2 authorization procedure) and / or after requesting a USS.
[0121] As shown in FIG. 8 (e.g., at 807 in FIG. 8), the DDMF1 may notify the DDNM2, e.g., send an announce permission (e.g., GPSI, CAA level ID, application ID, discovery code material) message, if the WTRU is authorized to use that ProSe application ID.
[0122] As shown in FIG. 8 (eg, at 808 in FIG. 8), the DDNMF2 may send an announce grant ACK to the DDNMF1, for example, to allow the WTRU to perform direct discovery monitoring.
[0123] As shown in FIG. 8 (e.g., at 809 in FIG. 9), the DDNMF1 can send a discovery response (e.g., CAA level UAV ID, discovery code material / filter) to the WTRU. The DDNMF in the HPLMN can send a request to the DDNMF in the local / VPLMN and receive a response filter for monitoring between the two DDNMFs if / when addressing monitoring compared to an announcement in unrestricted discovery, for example.
[0124] The discovery announcement request may be sent, for example, corresponding to restricted discovery model A / model B. FIG. 9 illustrates an example announcement request procedure for restricted discovery (non-roaming). As shown in FIG. 9 (e.g., at 900 in FIG. 9), the USS may allocate a CAA level ID (e.g., a changed 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 may obtain the WTRU ID from the network instead. 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.
[0125] As shown in FIG. 9, the WTRU may announce (e.g., may be permitted 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., at 901 in FIG. 9).
[0126] 9 (e.g., at 902 in FIG. 9), the DDNMF may check discovery permissions for the application (e.g., represented by the application ID from the UDM). The DDNMF may determine that it can (e.g., should) contact the UAS NF based on, for example, subscription data associated with the app ID (e.g., UAS app ID).
[0127] As shown in FIG. 9 (e.g., at 903 in FIG. 9), the DDNMF can send an authorization request (e.g., CAA level ID, application container, and discovery request type (e.g., unrestricted / restricted)) to the UAS NF.
[0128] As shown in FIG. 9 (e.g., at 904 in FIG. 9), the UAS NF can return an authorization response (e.g., CAA level ID, WTRU ID, PDU ID, response type, discovery code material) to the DDNMF. The WTRU ID(s) can be associated with the CAA level ID(s) stored at the UAS NF. The UAS NF may generate the response, for example, from locally stored information (e.g., from a previous discovery / C2 authorization procedure) and / or after requesting a USS.
[0129] As shown in FIG. 9 (eg, at 905 in FIG. 9), the DDNMF in the HPLMN may respond to the WTRU with a discovery response (eg, CAA level ID, discovery code material).
[0130] For example, the discovery monitoring request may be sent according to a restricted discovery model, such as Model A or Model B. FIG. 10 illustrates an example monitoring request procedure for restricted discovery (non-roaming). As shown in FIG. 10 (e.g., at 1000 in FIG. 10), the USS may allocate a CAA level ID (e.g., a changed and / or new CAA level ID) to the WTRU (e.g., UAV / UAV-C), e.g., during a previous UUAA or C2 authorization procedure. In response, the WTRU may obtain a WTRU ID (e.g., from a network). The WTRU, the network (e.g., UAS NF), and the USS may store a binding / mapping between CAA level IDs and WTRU IDs. The WTRU may obtain their user's CAA level IDs (e.g., target CAA level ID(s)) from the USS via the network (e.g., during a C2 authorization procedure), e.g., when the WTRU intends to communicate / discover UAS peers. The WTRU may trigger monitoring, for example, by providing its own CAA level ID and the target CAA level ID to be monitored (which may be passed in an application level container, for example).
[0131] As shown in FIG. 10 (e.g., at 1001 in FIG. 10), the WTRU may send a discovery request message (e.g., CAA level ID, GPSI, discovery type, app ID, application level container) to DDNMF1. The application level container may include target CAA level IDs of UAS peers that the WTRU may monitor. The CAA level ID may indicate an identity that the WTRU uses to obtain permission to monitor.
[0132] 10 (e.g., at 1002 in FIG. 10), DDNMF1 may check discovery permissions for an application represented by an application ID from the UDM. DDNMF1 may determine that it can (e.g., should) contact UAS NF1 based on, for example, subscription data associated with the app ID (e.g., UAS app ID).
[0133] As shown in FIG. 10 (e.g., at 1003 in FIG. 10), the DDNMF1 may send an authorization request (e.g., ID, WTRU ID, CAA level ID, PDU ID, application container, discovery request type (e.g., unrestricted / restricted)) to the UAS NF.
[0134] As shown in FIG. 10 (e.g., at 1004 in FIG. 10), the UAS NF1 may send an authorization response message (e.g., WTRU ID, CAA level ID, PDU ID, target WTRU ID, target CAA level ID, target PDU ID, application container, discovery response type, discovery code material) to the DDNMF1. A (e.g., each) target WTRU ID from the set of WTRU IDs may be returned along with the corresponding target CAA UAV ID(s) that the CAA UAV ID can discover (e.g., is authorized to discover). The DDNMF1 may verify that the returned WTRU ID / PDU ID belongs to the requesting WTRU. The application level container may include the successfully authenticated target CAA UAV ID(s). The UAS NF1 may generate the response from locally stored information (e.g., from a previous discovery / C2 authorization procedure) and / or after requesting a USS.
[0135] As shown in FIG. 10 (e.g., at 1005 in FIG. 10), the DDNMF1 in the HPLMN may send a monitoring request message (e.g., WTRU ID, CAA level ID, PDU ID, target WTRU ID, target CAA level ID, target PDU ID, app ID) to the DDNMF2 in the other PLMN (e.g., to retrieve the corresponding restricted code), for example, if the PLMN ID in the target WTRU ID indicates a PLMN different from the HPLMN.
[0136] 10 (e.g., at 1006 in FIG. 10), the DDNMF2 in the other PLMN may send an authorization request (e.g., WTRU ID, PDU ID, CAA Level ID, target WTRU ID, target PDU ID, target CAA Level ID, request type) to the UAS NF2. The request type may be set to limited discovery / authorization.
[0137] As shown in FIG. 10 (e.g., at 1007 in FIG. 10), the UAS NF may send an authorization message (e.g., target WTRU ID, target CAA level ID, target PDU ID, response type), for example, if the CAA level ID is authorized to discover the target CAA level ID (e.g., based on authorization settings). The UAS NF2 may generate the response from locally stored information and / or after requesting a USS. The UAS NF may store and associate identifiers of the monitoring WTRU and target / announcer WTRU(s), for example, during a previous discovery or C2 authorization procedure. The UAS NF may verify the authorization to monitor by matching the identifiers (e.g., monitoring WTRU and target WTRU) provided by the DDNMF2 with the stored identifiers. The DDNMF2 may verify that the returned target WTRU ID / PDU ID corresponds to the WTRU to be monitored.
[0138] 10 (e.g., at 1008 in FIG. 10), the DDNMF2 may send a monitoring response (e.g., restricted code material) message to the DDNMF1. The DDNMF2 may store the WTRU ID of the monitoring WTRU (e.g., in the context of the announcing WTRU).
[0139] As shown in FIG. 10 (e.g., at 1009 in FIG. 10), the DDNMF1 may send a discovery response (e.g., discovery filter) message to the WTRU (e.g., for each pair of target WTRU ID and target CAA level ID returned by the UAS NF / USS), for example, if the DDNMF1 retrieves a (e.g., valid) ProSe restricted code.
[0140] 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 may be used in various combinations with or without the other features and elements.
[0141] Although the implementations described herein may take into account 3GPP-specific protocols, it will be understood that the implementations described herein are not limited to this scenario and may be applicable to other wireless systems. For example, while the solutions described herein take into account LTE, LTE-A, New Radio (NR), or 5G-specific protocols, it will be understood that the solutions described herein are not limited to this scenario and may be applicable to other wireless systems as well.
[0142] The above-described processes may be implemented in a computer program, software, and / or firmware embodied 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 over wired and / or wireless connections) 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, internal hard disks and removable disks, magneto-optical media, and / or optical media such as Compact Disc (CD)-ROM disks, and / or Digital Versatile Disks (DVDs). A processor in association with software may be used to implement a radio frequency transceiver for use in a WTRU, a terminal, a base station, an RNC, and / or any host computer.
Claims
1. A first wireless transmit / receive unit (WTRU), the first WTRU comprising: transmitting a first message to a network node, the first message indicating a command and control (C2) authorization request and indicating a request for a packet data unit (PDU) session; receiving a second message from the network node, the second message indicating that the PDU session is established, indicating a C2 authorization, and indicating 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, the C2 authorization information including security credentials and an identity of the second WTRU; A first wireless transmit / receive unit (WTRU), comprising a processor configured to: if the first WTRU is authorized to communicate with the second WTRU, send a third message to the second WTRU using PC5, the third message being protected based on the security credentials, the third message indicating a request to perform at least one of a discovery procedure or a link establishment procedure.
2. The first WTRU of claim 1 , wherein the third message is encrypted based on the security credentials.
3. The first WTRU of claim 1 , wherein the security credentials are an authorization token.
4. The processor, The first WTRU of claim 1 , further configured to determine a security key or a security token based on the security credentials, and the third message is based on the determined security key or the determined security token.
5. A first network node, the network node comprising: transmitting a first message to a second network node, the first message indicating a request for authorization, the authorization being associated with a wireless transmit / receive unit (WTRU); receiving a second message from the second network node; determining, based on the second message, that the WTRU is authorized to establish C2 on PC5; and determining a discovery permission parameter using the second message; and and transmitting a third message to the WTRU, the third message indicating the discovery permission parameter.
6. The first network node of claim 5, wherein the second message indicates a response to the request, indicates policy configuration information, and indicates security credentials associated with the WTRU.
7. The first network node of claim 6, wherein the determination based on the second message that the WTRU is authorized to establish C2 on PC5 is made based on the indicated response to the request and the indicated policy setting information.
8. The first network node of claim 6 , wherein the discovery permission parameters are determined using the second message based on the indicated policy setting information and the indicated security credentials.
9. 6. The first network node of claim 5, wherein said request for authorization is a request for approval to establish command and control (C2) on a PC5.
10. A first network node associated with a first network, the first network node comprising: receiving a first message, the first message indicating an authentication request associated with a discovery; determining that a first wireless transmit / receive unit (WTRU) is authorized to operate as an unmanned aerial vehicle (UAV); and transmitting a second message, the second message indicating an authorization response associated with the first message, the second message indicating that the first WTRU is authorized to operate as a UAV.
12. The processor, The first network node of claim 10, further configured to determine that the first WTRU is authorized to conduct command and control (C2) communications.
13. The processor, 13. The first network node of claim 12, further configured to receive an indication from an Unmanned Aerial System Service Provider (USS), and wherein the determination that the first WTRU is authorized to conduct C2 communications is based on the received indication.
14. 11. The first network node of claim 10, wherein the authentication request associated with a discovery indicates a subscription identifier, a UAV identifier, a request type, and an application level container associated with the WTRU, the request type indicating unrestricted discovery or restricted discovery.
15. If the request type indicates unrestricted discovery, the second message indicates that the first WTRU is authorized to perform unrestricted discovery; 15. The first network node of claim 14, wherein if the request type indicates limited discovery, the second message indicates that the WTRU is authorized to perform limited discovery.
16. The processor, further configured to determine a set of parameters based on the request type; If the request type indicates that the first WTRU is authorized to perform unrestricted discovery, the set of parameters includes parameters associated with performing unrestricted discovery; 16. The first network node of claim 15, wherein if the request type indicates that the first WTRU is authorized to perform limited discovery, the set of parameters includes parameters associated with performing limited discovery.
17. The first network node of claim 10 , wherein the authentication request associated with a discovery is a discovery request to monitor.
18. 20. The first network node of claim 17, wherein the discovery request to monitor indicates a subscription identifier, a UAV identifier, a prose discovery user equipment identifier (PDUID) associated with the first WTRU, a target subscription identifier, a target UAV identifier, and a target PDUID associated with a second WTRU.
19. The processor, 20. The first network node of claim 18, further configured to transmit a third message, the third message indicating a supervisory response.
Citation Information
Patent Citations
Direct peer link establishment in wireless networks
US20100255869A1
Third party control of a user equipment
US20210274344A1
Methods, apparatus and systems for command and control (C2) communications setup and update
WO2021202960A1
