Authorization of command and control communications via direct link

By using the ProSe identifier and the destination strata 2 identifier in the wireless communication system, the problem of direct link communication authorization between user equipment is solved, and communication efficiency and security are improved.

CN118947211APending Publication Date: 2024-11-12QUALCOMM INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380030153.8
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-12-05
Filing Date
2023-03-07
Publication Date
2024-11-12

AI Technical Summary

Technical Problem

When existing wireless communication systems realize direct link command and control communication between user equipment, they lack effective authorization mechanisms, resulting in low communication efficiency and insufficient security.

Method used

Authorization and management of command and control communications are achieved by establishing and managing direct links between user equipment using proximity-based service (ProSe) identifiers and destination strata 2 identifiers.

Benefits of technology

It improves the efficiency and security of direct link communication between user equipment, and ensures the accurate transmission and effective management of command and control information.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118947211A_ABST
    Figure CN118947211A_ABST
Patent Text Reader

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a network entity may receive an authorization request for a command and control (C2) communication from an application server via a direct link between a pair of user equipments (UEs), where the authorization request indicates a proximity-based service (ProSe) identifier associated with the C2 communication. The network entity may send an authorization indication of the C2 communication to the application server via the direct link between the pair of UEs, wherein the authorization indication indicates a destination layer 2 identifier associated with the ProSe identifier. Numerous other aspects are described.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to U.S. Provisional Patent Application No. 63 / 362,437, filed on April 4, 2022, entitled “AUTHORIZATION OF COMMAND AND CONTROL COMMUNICATIONS VIA DIRECT LINK,” and U.S. Non-Provisional Patent Application No. 18 / 061,780, filed on December 5, 2022, entitled “AUTHORIZATION OF COMMAND AND CONTROL COMMUNICATIONS VIA DIRECT LINK,” which are hereby expressly incorporated herein by reference. Technical Field

[0003] Aspects of the present disclosure relate generally to wireless communications, and to techniques and apparatus for authorization of command and control (C2) communications via a direct link. Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).

[0005] A wireless network may include one or more base stations that support communications for a user equipment (UE) or multiple UEs. A UE may communicate with a base station via downlink communications and uplink communications. A "downlink" (or "DL") refers to the communication link from a base station to a UE, and an "uplink" (or "UL") refers to the communication link from a UE to a base station.

[0006] The above-mentioned multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate at a city, country, region and / or global level. New Radio (NR) (which may be referred to as 5G) is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by using orthogonal frequency division multiplexing (OFDM) (CP-OFDM) with a cyclic prefix (CP) on the downlink, using CP-OFDM and / or single carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink, and supporting beamforming, multiple input multiple output (MIMO) antenna technology and carrier aggregation to improve spectrum efficiency, reduce costs, improve services, utilize new spectrum, and better integrate with other open standards. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR and other radio access technologies remain useful. Summary of the invention

[0007] Some aspects described herein relate to a first user equipment (UE) for wireless communication. The first UE may include: a memory; and one or more processors, the one or more processors coupled to the memory. The one or more processors may be configured to: receive an indication of a proximity-based service (ProSe) identifier associated with authorized command and control (C2) communications and an indication of a destination layer 2 identifier associated with the ProSe identifier via a direct link between the first UE and a second UE. The one or more processors may be configured to: establish a direct link with the second UE based at least in part on the ProSe identifier and the destination layer 2 identifier.

[0008] Some aspects described herein relate to a network entity for wireless communication. The network entity may include: a memory; and one or more processors, the one or more processors coupled to the memory. The one or more processors may be configured to: receive an authorization request for C2 communication from an application server via a direct link between a pair of UEs, wherein the authorization request indicates a ProSe identifier associated with the C2 communication. The one or more processors may be configured to: send an authorization indication for the C2 communication to the application server via the direct link between the pair of UEs, wherein the authorization indication indicates a destination layer 2 identifier associated with the ProSe identifier.

[0009] Some aspects described herein relate to a method of wireless communication performed by a first UE. The method may include receiving, via a direct link between the first UE and a second UE, an indication of a ProSe identifier associated with authorized C2 communications and an indication of a destination layer 2 identifier associated with the ProSe identifier. The method may include establishing a direct link with the second UE based at least in part on the ProSe identifier and the destination layer 2 identifier.

[0010] Some aspects described herein relate to a method of wireless communication performed by a network entity. The method may include: receiving an authorization request for C2 communication from an application server via a direct link between a pair of UEs, wherein the authorization request indicates a ProSe identifier associated with the C2 communication. The method may include: sending an authorization indication for the C2 communication to the application server via the direct link between the pair of UEs, wherein the authorization indication indicates a destination layer 2 identifier associated with the ProSe identifier.

[0011] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a first UE. The instruction set, when executed by one or more processors of the UE, may cause the UE to receive an indication of a ProSe identifier associated with authorized C2 communications and an indication of a destination layer 2 identifier associated with the ProSe identifier via a direct link between the first UE and a second UE. The instruction set, when executed by one or more processors of the UE, may cause the UE to establish a direct link with the second UE based at least in part on the ProSe identifier and the destination layer 2 identifier.

[0012] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a network entity. The instruction set, when executed by one or more processors of the network entity, may cause the network entity to receive an authorization request for C2 communication from an application server via a direct link between a pair of UEs, wherein the authorization request indicates a ProSe identifier associated with the C2 communication. The instruction set, when executed by one or more processors of the network entity, may cause the network entity to send an authorization indication for the C2 communication to the application server via the direct link between the pair of UEs, wherein the authorization indication indicates a destination layer 2 identifier associated with the ProSe identifier.

[0013] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving, via a direct link between the apparatus and a UE, an indication of a ProSe identifier associated with authorized C2 communications and an indication of a destination layer 2 identifier associated with the ProSe identifier. The apparatus may include means for establishing a direct link with the UE based at least in part on the ProSe identifier and the destination layer 2 identifier.

[0014] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving an authorization request for C2 communication from an application server via a direct link between a pair of UEs, wherein the authorization request indicates a ProSe identifier associated with the C2 communication. The apparatus may include means for sending an authorization indication for the C2 communication to the application server via the direct link between the pair of UEs, wherein the authorization indication indicates a destination layer 2 identifier associated with the ProSe identifier.

[0015] Aspects generally include methods, apparatus, systems, computer program products, non-transitory computer readable media, user equipment, base stations, wireless communication devices and / or processing systems as fully described herein with reference to and as illustrated by the accompanying drawings and description.

[0016] The features and technical advantages of examples according to the present disclosure have been outlined quite extensively above so that the following specific embodiments may be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples may be easily used as a basis for modifying or designing other structures for achieving the same purpose of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, both in terms of their organization and method of operation, and the associated advantages will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the accompanying drawings is provided for the purpose of illustration and description, and not as a definition of the limitations of the claims.

[0017] Although various aspects are described in the present disclosure by illustrating some examples, it will be understood by those skilled in the art that such aspects can be implemented in many different arrangements and scenarios. The technology described herein can be implemented using different platform types, devices, systems, shapes, sizes and / or packaging arrangements. For example, some aspects can be implemented via integrated chip implementations or other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / shopping equipment, medical equipment and / or artificial intelligence devices). Various aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components and / or system-level components. The equipment incorporating the various aspects and features described may include additional components and features for implementing and practicing the various aspects claimed and described. For example, the transmission and reception of wireless signals may include one or more components (e.g., hardware components, including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders and / or summers) for analog and digital purposes. Various aspects described herein are intended to be practiced in various devices, components, systems, distributed arrangements and / or end-user devices of various sizes, shapes and configurations. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] In order to fully understand the above features of the present disclosure, a more specific description of the invention briefly summarized above can be obtained by referring to various aspects (some of which are illustrated in the accompanying drawings). However, it should be noted that the accompanying drawings only illustrate certain typical aspects of the present disclosure and are therefore not to be considered as limiting the scope thereof, as the specification may admit other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0019] Figure 1 is a diagram illustrating an example of a wireless network according to the present disclosure.

[0020] Figure 2 is a diagram illustrating an example of communication between a base station and a user equipment (UE) in a wireless network according to the present disclosure.

[0021] Figure 3 is a diagram illustrating an example of side link communication according to the present disclosure.

[0022] Figure 4 is a diagram illustrating an example of side link communication and access link communication according to the present disclosure.

[0023] Figure 5 is a diagram illustrating an example of an unmanned aerial vehicle (UAV) within a wireless communication network environment according to the present disclosure.

[0024] Figure 6is a diagram illustrating an example associated with authorization of command and control (C2) communications via a direct link according to the present disclosure.

[0025] Figures 7 and 8 is a diagram illustrating an example process associated with authorization of C2 communications via a direct link according to the present disclosure.

[0026] Figures 9 and 10 is a diagram of an example apparatus for wireless communications according to the present disclosure. DETAILED DESCRIPTION

[0027] The various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms, and should not be interpreted as being limited to any specific structure or function presented throughout the present disclosure. Instead, these aspects are provided so that the present disclosure will be thorough and complete, and the protection scope of the present disclosure will be fully conveyed to those skilled in the art. It should be appreciated by those skilled in the art that the scope of the present disclosure is intended to cover any aspect of the present disclosure disclosed herein, whether it is implemented independently or in combination with any other aspect of the present disclosure. For example, any number of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such devices or methods that are practiced using other structures, functionality, or structures and functionality in addition to or different from the various aspects of the present disclosure set forth herein. It should be understood that any aspect of the present disclosure disclosed herein may be embodied by one or more elements of the claims.

[0028] Several aspects of telecommunication systems will now be presented with reference to various devices and techniques. These devices and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements can be implemented using hardware, software, or a combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0029] Although aspects may be described herein using terminology generally associated with 5G or new radio (NR) radio access technology (RAT), aspects of the present disclosure may be applied to other RATs, such as 3G RAT, 4G RAT, and / or post-5G RATs (e.g., 6G).

[0030] Figure 11 is a diagram illustrating an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, or may include elements of a 5G (e.g., NR) network and / or elements of a 4G (e.g., Long Term Evolution (LTE)) network, among other examples. The wireless network 100 may include one or more base stations 110 (shown as BS110a, BS110b, BS110c, and BS110d), a user equipment (UE) 120 or multiple UEs 120 (shown as UE120a, UE 120b, UE 120c, UE 120d, and UE 120e), and / or other network entities. The base station 110 is an entity that communicates with the UE 120. Base station 110 (sometimes referred to as BS) may include, for example, an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, and / or a transmit receive point (TRP). Each base station 110 may provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP), the term "cell" may refer to a coverage area of ​​a base station 110 and / or a base station subsystem serving the coverage area, depending on the context in which the term is used.

[0031] The base station 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by a UE 120 with a service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by a UE 120 with a service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by a UE 120 associated with the femto cell (e.g., a UE 120 in a closed subscriber group (CSG)). A base station 110 for a macro cell may be referred to as a macro base station. A base station 110 for a pico cell may be referred to as a pico base station. A base station 110 for a femto cell may be referred to as a femto base station or a home base station. In Figure 1 In the example shown in , BS 110a may be a macro base station for macro cell 102a, BS 110b may be a pico base station for pico cell 102b, and BS 110c may be a femto base station for femto cell 102c. A base station may support one or more (eg, three) cells.

[0032] In some examples, the cells may not necessarily be stationary, and the geographic area of ​​the cells may move according to the location of the mobile base station 110 (e.g., a mobile base station). In some examples, the base stations 110 may be interconnected with each other and / or to one or more other base stations 110 or network nodes (not shown) in the wireless network 100 using any suitable transport network through various types of backhaul interfaces (such as direct physical connections or virtual networks).

[0033] The wireless network 100 may include one or more relay stations. A relay station is an entity that can receive transmissions of data from an upstream station (e.g., a base station 110 or a UE 120) and transmit transmissions of data to a downstream station (e.g., a UE 120 or a base station 110). A relay station may be a UE 120 that is capable of relaying transmissions for other UEs 120. Figure 1 In the example shown in FIG. 1 , BS 110d (eg, a relay base station) can communicate with BS 110a (eg, a macro base station) and UE 120d to facilitate communication between BS 110a and UE 120d. Base station 110 that relays communication may be referred to as a relay station, relay base station, relay, or the like.

[0034] The wireless network 100 may be a heterogeneous network that includes different types of base stations 110, such as macro base stations, pico base stations, femto base stations, relay base stations, etc. These different types of base stations 110 may have different transmit power levels, different coverage areas, and / or different impacts on interference in the wireless network 100. For example, a macro base station may have a high transmit power level (e.g., 5 watts to 40 watts), while a pico base station, a femto base station, and a relay base station may have a lower transmit power level (e.g., 0.1 watt to 2 watts).

[0035] The network controller 130 may be coupled to or in communication with a set of base stations 110 and may provide coordination and control for the base stations. The network controller 130 may communicate with the base stations 110 via a backhaul communication link. The base stations 110 may communicate with each other directly or indirectly via a wireless backhaul communication link or a wired backhaul communication link.

[0036] UE 120 can be distributed throughout the wireless network 100, and each UE 120 can be stationary or mobile. UE 120 can include, for example, an access terminal, a terminal, a mobile station and / or a subscriber unit. UE 120 can be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or a smart bracelet)), an entertainment device (e.g., a music device, a video device and / or a satellite radio), a vehicle component or sensor, a smart meter / sensor, an industrial manufacturing equipment, a global positioning system device and / or any other suitable device configured to communicate via a wireless medium.

[0037] Some UE 120 may be considered as machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UE. MTC UE and / or eMTC UE may include, for example, a robot, an unmanned aerial vehicle (UAV) (e.g., a drone), a remote device, a sensor, a meter, a monitor and / or a location tag, which may communicate with a base station, another device (e.g., a remote device), or some other entity. Some UE 120 may be considered as an Internet of Things (IoT) device and / or may be implemented as a NB-IoT (narrowband IoT) device. Some UE 120 may be considered as customer premises equipment. UE 120 may be included inside a housing that houses components of UE 120, such as a processor component and / or a memory component. In some examples, the processor component and the memory component may be coupled together. For example, a processor component (e.g., one or more processors) and a memory component (e.g., a memory) may be operationally coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0038] In general, any number of wireless networks 100 may be deployed in a given geographic area. Each wireless network 100 may support a specific RAT and may operate on one or more frequencies. RAT may be referred to as a radio technology, air interface, etc. Frequency may be referred to as a carrier, frequency channel, etc. Each frequency may support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.

[0039] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly using one or more side link channels (e.g., without using base station 110 as an intermediary to communicate with each other). For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols), and / or mesh networks. In such examples, UE 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by base station 110.

[0040] The devices of the wireless network 100 may communicate using an electromagnetic spectrum, which may be subdivided into various categories, bands, channels, etc., based on frequency or wavelength. For example, the devices of the wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency ranges designated FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). It should be understood that, although a portion of FR1 is greater than 6 GHz, FR1 is often (interchangeably) referred to as the "below 6 GHz" band in various documents and articles. A similar naming problem sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, although different from the extremely high frequency (EHF) band (30 GHz-300 GHz) identified as the "millimeter wave" band by the International Telecommunication Union (ITU).

[0041] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125GHz-24.25GHz). The bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, so the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6GHz-71GHz), FR4 (52.6GHz-114.25GHz) and FR5 (114.25GHz-300GHz). Each of these higher frequency bands falls within the EHF band.

[0042] In view of the above examples, unless otherwise specifically stated, it should be understood that the terms "below 6 GHz", etc., if used herein, can broadly represent frequencies that can be lower than 6 GHz, can be within FR1, or can include mid-band frequencies. In addition, unless otherwise specifically stated, it should be understood that the terms "millimeter wave", etc., if used herein, can broadly represent frequencies that can include mid-band frequencies, can be within FR2, FR4, FR4-a or FR4-1 and / or FR5, or can be within the EHF band. It is contemplated that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) can be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0043] In some aspects, the UE 120 may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may receive, via a direct link between the UE and another UE, an indication of a proximity-based service (ProSe) identifier associated with an authorized command and control (C2) communication and an indication of a destination layer 2 identifier associated with the ProSe identifier; and establish a direct link with the other UE based at least in part on the ProSe identifier and the destination layer 2 identifier. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0044] In some aspects, a network entity, such as a network controller 130, may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may receive an authorization request for C2 communication via a direct link between a pair of UEs, wherein the authorization request indicates a ProSe identifier associated with the C2 communication; and send an authorization indication for C2 communication via the direct link between the pair of UEs, wherein the authorization indication indicates a destination layer 2 identifier associated with the ProSe identifier. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0045] As indicated above, Figure 1 Other examples can be found in the Figure 1 Different than described.

[0046] Figure 2 2 is a diagram illustrating an example 200 of base station 110 communicating with UE 120 in wireless network 100 according to the present disclosure. Base station 110 may be equipped with a set of antennas 234a to 234t, such as T antennas (T≥1). UE 120 may be equipped with a set of antennas 252a to 252r, such as R antennas (R≥1).

[0047] At the base station 110, the transmit processor 220 may receive data intended for the UE 120 (or a set of UEs 120) from the data source 212. The transmit processor 220 may select one or more modulation and coding schemes (MCS) for the UE 120 based at least in part on one or more channel quality indicators (CQIs) received from the UE 120. The base station 110 may process (e.g., encode and modulate) the data for the UE 120 based at least in part on the MCS selected for the UE 120, and may provide data symbols for the UE 120. The transmit processor 220 may process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper layer signaling), and provide overhead symbols and control symbols. The transmit processor 220 may generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signals (PSS) or secondary synchronization signals (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., pre-decoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, where applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems) (shown as modems 232a to 232t). For example, each output symbol stream may be provided to a modulator component (shown as MOD) of the modem 232. Each modem 232 may process a corresponding output symbol stream (e.g., for OFDM) using a corresponding modulator component to obtain an output sample stream. Each modem 232 may further process (e.g., convert to analog, amplify, filter, and / or up-convert) the output sample stream using a corresponding modulator component to obtain a downlink signal. The modems 232a to 232t may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas) (shown as antennas 234a to 234t).

[0048] At the UE 120, a set of antennas 252 (shown as antennas 252a to 252r) can receive downlink signals from the base station 110 and / or other base stations 110 and can provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems) (shown as modems 254a to 254r). For example, each received signal can be provided to a demodulator component (shown as DEMOD) of the modem 254. Each modem 254 can use a corresponding demodulator component to condition (e.g., filter, amplify, downconvert and / or digitize) the received signal to obtain input samples. Each modem 254 can use a demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 can obtain received symbols from the modem 254, can perform MIMO detection on the received symbols where applicable, and can provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for the UE 120 to a data sink 260, and may provide decoded control information and system information to a controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and / or a CQI parameter, among other things. In some examples, one or more components of the UE 120 may be included in a housing 284.

[0049] The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 may include, for example, one or more devices in a core network. The network controller 130 may communicate with the base station 110 via the communication unit 294.

[0050] One or more antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include or be included within one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements, and / or antenna arrays may include one or more antenna elements (in a single housing or multiple housings), sets of coplanar antenna elements, sets of non-coplanar antenna elements, and / or may be coupled to one or more transmit and / or receive components (such as, Figure 2 One or more antenna elements of one or more components in.

[0051] On the uplink, at the UE 120, a transmit processor 264 may receive and process data from a data source 262 and control information from a controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI). The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be pre-decoded by the TX MIMO processor 266, where applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to the base station 110. In some examples, the modem 254 of the UE 120 may include a modulator and a demodulator. In some examples, the UE 120 includes a transceiver. The transceiver may include any combination of an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, and / or a TX MIMO processor 266. The transceiver may be used by a processor (eg, controller / processor 280) and memory 282 to perform the functions described herein (eg, with reference to Figures 6 to 10 ) or any aspect of any of the methods described herein.

[0052] At the base station 110, uplink signals from the UE 120 and / or other UEs may be received by the antenna 234, processed by the modem 232 (e.g., a demodulator component of the modem 232 shown as DEMOD), detected by the MIMO detector 236 (where applicable), and further processed by the receive processor 238 to obtain decoded data and control information transmitted by the UE 120. The receive processor 238 may provide the decoded data to the data sink 239 and the decoded control information to the controller / processor 240. The base station 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The base station 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink and / or uplink communications. In some examples, the modem 232 of the base station 110 may include a modulator and a demodulator. In some examples, the base station 110 includes a transceiver. The transceiver may include any combination of antenna 234, modem 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to perform the functions described herein (e.g., with reference to Figures 6 to 10 ) or any aspect of any of the methods described herein.

[0053] Controller / processor 240 of base station 110, controller / processor 280 of UE 120, controller / processor 290 of network controller 130, and / or Figure 2 Any other components of the base station 110 may perform one or more techniques associated with authorization of C2 communications via the direct link, as described in more detail elsewhere herein. For example, the controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component of the can perform or direct e.g. Figure 8 The process of 700 Figure 8 800 and / or operations of other processes as described herein. Memory 242 and memory 282 may store data and program codes for base station 110 and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium that stores one or more instructions (e.g., code and / or program code) for wireless communication. For example, the one or more instructions, when executed (e.g., directly, or after compilation, conversion, and / or interpretation) by one or more processors of base station 110 and / or UE 120, may cause the one or more processors, UE 120, base station 110, and / or network controller 130 to perform or direct, for example, Figure 7 The process of 700 Figure 8 In some aspects, the network entity described herein may be a network controller 130 (e.g., Figure 2 As shown), one or more components of a core network device or another network device may be included in one or more components of the network controller, the core network device or another network device, or may include one or more components of the network controller, the core network device or another network device.

[0054] In some aspects, a UE (e.g., UE 120) includes means for receiving an indication of a ProSe identifier associated with authorized C2 communications and an indication of a destination layer 2 identifier associated with the ProSe identifier via a direct link between the UE and another UE; and / or means for establishing a direct link with another UE based at least in part on the ProSe identifier and the destination layer 2 identifier. Means for the UE to perform operations described herein may include, for example, one or more of the following: communication manager 140, antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, controller / processor 280, or memory 282.

[0055] In some aspects, the network entity includes means for receiving an authorization request for C2 communication from an application server via a direct link between a pair of UEs, wherein the authorization request indicates a ProSe identifier associated with the C2 communication; and / or means for sending an authorization indication for C2 communication to the application server via the direct link between the pair of UEs, wherein the authorization indication indicates a destination layer 2 identifier associated with the ProSe identifier. In some aspects, the means for the network entity to perform operations described herein may include, for example, one or more of the following: the communication manager 150, the communication unit 294, the controller / processor 290, or the memory 292.

[0056] Although Figure 2 The blocks in the 200 and 210 are illustrated as distinct components, but the functionality described above with respect to these blocks may be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functionality described with respect to the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be performed by or under the control of the controller / processor 280.

[0057] As indicated above, Figure 2 Other examples can be found in the Figure 2 Different than described.

[0058] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or components in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element or a network equipment (such as a base station (BS) or one or more units (or one or more components) that perform base station functionality) can be implemented in a clustered or decomposed architecture. For example, a base station (such as a node B (NB), an evolved NB (eNB), a NR base station, a 5G NB, an access point (AP), a TRP or a cell, etc.) can be implemented as a clustered base station (also referred to as an independent base station or a single-chip base station) or a decomposed base station.

[0059] A clustered base station may be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node. A decomposed base station may be configured to utilize a protocol stack physically or logically distributed between two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed in one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of a CU, a DU, and a RU may also be implemented as a virtual unit (e.g., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU)).

[0060] Base station type operations or network designs may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be used in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (network configurations such as those initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Decomposition may include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which may enable flexibility in network design. Individual units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0061] Figure 3 is a diagram illustrating an example 300 of sidelink communications according to the present disclosure.

[0062] like Figure 3As shown, the first UE 305-1 can communicate with the second UE 305-2 (and one or more other UEs 305) via one or more side link channels 310. UE 305-1 and UE 305-2 can communicate using one or more side link channels 310 for P2P communication, D2D communication, V2X communication (e.g., which may include V2V communication, V2I communication and / or V2P communication) and / or mesh network. In some aspects, UE 305 (e.g., UE 305-1 and / or UE 305-2) can correspond to one or more other UEs described elsewhere herein, such as UE 120. In some aspects, one or more side link channels 310 can use a PC5 interface and / or can operate in a high frequency band (e.g., a 5.9 GHz band). Additionally or alternatively, UE 305 can use global navigation satellite system (GNSS) timing to synchronize the timing of a transmit time interval (TTI) (e.g., a frame, subframe, time slot or symbol).

[0063] like Figure 3 As further shown, the one or more sidelink channels 310 may include a physical sidelink control channel (PSCCH) 315, a physical sidelink shared channel (PSSCH) 320, and / or a physical sidelink feedback channel (PSFCH) 325. The PSCCH 315 may be used to communicate control information, similar to a physical downlink control channel (PDCCH) and / or a physical uplink control channel (PUCCH) used for cellular communication with the base station 110 via an access link or access channel. The PSSCH 320 may be used to communicate data, similar to a physical downlink shared channel (PDSCH) and / or a physical uplink shared channel (PUSCH) used for cellular communication with the base station 110 via an access link or access channel. For example, the PSCCH 315 may carry sidelink control information (SCI) 330, which may indicate various control information for sidelink communication, such as one or more resources (e.g., time resources, frequency resources, and / or space resources), where a transport block (TB) 335 may be carried on the PSSCH 320. The TB 335 may include data. The PSFCH 325 may be used to communicate sidelink feedback 340, such as hybrid automatic repeat request (HARQ) feedback (eg, acknowledgement or negative acknowledgement (ACK / NACK) information), transmit power control (TPC), and / or scheduling request (SR).

[0064] Although shown on PSCCH 315, in some aspects, SCI 330 may include multiple communications in different levels, such as a first level SCI (SCI-1) and a second level SCI (SCI-2). SCI-1 may be sent on PSCCH 315. SCI-2 may be sent on PSSCH 320. SCI-1 may include, for example, an indication of one or more resources (e.g., time resources, frequency resources, and / or space resources) on PSSCH 320, information for decoding sidelink communications on PSSCH, quality of service (QoS) priority value, resource reservation period, PSSCH DMRS mode, SCI format for SCI-2, beta offset for SCI-2, number of PSSCH DMRS ports, and / or MCS. SCI-2 may include information associated with data transmission on PSSCH 320, such as HARQ process ID, new data indicator (NDI), source identifier, destination identifier, and / or channel state information (CSI) report trigger.

[0065] In some aspects, one or more sidelink channels 310 may use a resource pool. For example, a scheduling assignment (e.g., included in SCI 330) may be sent in a subchannel using specific resource blocks (RBs) across time. In some aspects, data transmissions associated with the scheduling assignment (e.g., on PSSCH 320) may occupy adjacent RBs in the same subframe as the scheduling assignment (e.g., using frequency division multiplexing). In some aspects, the scheduling assignment and the associated data transmission are not sent on adjacent RBs.

[0066] In some aspects, UE 305 may operate using a sidelink resource allocation mode (e.g., Mode 1) where resource selection and / or scheduling is performed by base station 110. For example, UE 305 may receive a grant for sidelink channel access and / or scheduling from base station 110 (e.g., in downlink control information (DCI) or in a radio resource control (RRC) message, such as a grant for configuration). In some aspects, UE 305 may operate using a resource allocation mode (e.g., Mode 2) where resource selection and / or scheduling is performed by UE 305 (e.g., instead of base station 110). In some aspects, UE 305 may perform resource selection and / or scheduling by sensing channel availability for transmission. For example, UE 305 may measure RSSI parameters associated with various side link channels (e.g., sidelink-RSSI (S-RSSI) parameters); may measure RSRP parameters associated with various side link channels (e.g., PSSCH-RSRP parameters); and / or may measure RSRQ parameters associated with various side link channels (e.g., PSSCH-RSRQ parameters); and may select a channel for sending side link communications based at least in part on the measurements.

[0067] Additionally or alternatively, the UE 305 may perform resource selection and / or scheduling using the SCI 330 received in the PSCCH 315, which may indicate occupied resources and / or channel parameters. Additionally or alternatively, the UE 305 may perform resource selection and / or scheduling by determining a channel busy rate (CBR) associated with each sidelink channel, which may be used for rate control (e.g., by indicating a maximum number of resource blocks that the UE 305 may use for a particular set of subframes).

[0068] In a resource allocation mode (e.g., Mode 2) in which resource selection and / or scheduling is performed by the UE 305, the UE 305 may generate a sidelink grant and may send the grant in the SCI 330. The sidelink grant may indicate, for example, one or more parameters (e.g., transmission parameters) to be used for an upcoming sidelink transmission, such as one or more resource blocks (e.g., for TB 335) to be used for an upcoming sidelink transmission on the PSSCH 320, one or more subframes to be used for an upcoming sidelink transmission, and / or an MCS to be used for an upcoming sidelink transmission. In some aspects, the UE 305 may generate a sidelink grant indicating one or more parameters for semi-persistent scheduling (SPS), such as the periodicity of the sidelink transmission. Additionally or alternatively, the UE 305 may generate a sidelink grant for event-driven scheduling, such as for an on-demand sidelink message.

[0069] As indicated above, Figure 3 Other examples can be found in the Figure 3 Different than described.

[0070] Figure 4 is a diagram illustrating an example 400 of side link communications and access link communications according to the present disclosure.

[0071] like Figure 4 As shown, the transmitter (Tx) / receiver (Rx) UE 405 and the Rx / Tx UE 410 can communicate with each other via a side link, as described above in conjunction with Figure 3 As further shown in the figure, in some sidelink modes, the base station 110 can communicate with the Tx / Rx UE 405 via the first access link. Additionally or alternatively, in some sidelink modes, the base station 110 can communicate with the Rx / Tx UE 410 via the second access link. The Tx / Rx UE 405 and / or the Rx / Tx UE 410 can correspond to one or more UEs described elsewhere in this document, such as Figure 1 120. Thus, a direct link between UEs 120 (e.g., via a PC5 interface) may be referred to as a side link, and a direct link between base station 110 and UE 120 (e.g., via a Uu interface) may be referred to as an access link. Side link communications may be sent via a side link, and access link communications may be sent via an access link. Access link communications may be downlink communications (from base station 110 to UE 120) or uplink communications (from UE 120 to base station 110).

[0072] As indicated above, Figure 4 Other examples can be found in the Figure 4 Different than described.

[0073] Figure 5 is a diagram illustrating an example of a UAV UE 120 within a wireless communication network environment 500 according to the present disclosure. Figure 5 As shown, environment 500 may include one or more UEs 120, which may include one or more UAVs 120-1 and one or more UAV controllers (UAV-C) 120-2, RAN 505, core network 520, UAV service provider (USS) equipment 515, and ground control system (GCS) 510. The devices of environment 500 may be interconnected via wired connections, wireless connections, or a combination of wired and wireless connections.

[0074] UAV 120-1 (also referred to herein as UAV UE 120-1) includes an aircraft without a human pilot on board and may also be referred to as an unmanned aircraft (UA), a drone, a remotely piloted vehicle (RPV), a remotely piloted aircraft (RPA), a remotely operated aircraft (ROA), or an unmanned aerial vehicle. UAV 120-1 may have various shapes, sizes, configurations, characteristics, etc. for various purposes and applications. In some implementations, UAV 120-1 may include one or more sensors, such as electromagnetic spectrum sensors (e.g., visual spectrum, infrared or near infrared cameras, radar systems, etc.), biosensors, temperature sensors, and / or chemical sensors, etc. In some implementations, UAV 120-1 may include one or more components for communicating with one or more base stations 110. Additionally or alternatively, UAV 120-1 may send information to GCS 510 and / or receive information from the GCS, such as sensor data, flight plan information, etc. Such information may be communicated directly (e.g., via RRC signals, etc.) and / or via base stations 110 on RAN 505. UAV 120-1 may be a component of an unmanned aircraft system (UAS). The UAS may include UAV 120-1, UAV-C 120-2 (also referred to herein as UAV-C UE 120-2), and a communication system (such as wireless network environment 500 or another communication system) between UAV 120-1 and UAV-C 120-2.

[0075] The RAN 505 may include one or more base stations 110 that provide the UAV UE 120 with access to the core network 520. For example, the RAN 505 may include one or more aggregated base stations and / or one or more decomposed base stations (e.g., including one or more CUs, one or more DUs, and / or one or more RUs). The UAV 120-1 may communicate with the base station 110 via a Uu interface. For example, the UAV 120-1 may send communications to and / or receive communications from the base station 110 via the Uu interface. Such Uu connectivity may be used to support different applications for the UAV 120-1, such as video transmission from the UAV 120-1 or C2 communications for remote command and control of the UAV 120-1.

[0076] GCS 510 may include one or more devices capable of managing UAV 120-1 and / or the flight plan of UAV 120-1. For example, GCS 510 may include a server device, a desktop computer, a laptop computer, or a similar device. In some examples, GCS 510 may communicate with one or more devices (e.g., UAV 120-1, USS device 515, etc.) of environment 500 to receive information about the flight plan of UAV UE 120-1 and / or provide suggestions associated with such flight plan, as described elsewhere herein. In some specific implementations, GCS 510 may allow a user (e.g., via UAV-C 120-2) to control one or more UAVs in UAV 120-1. Additionally or alternatively, GCS 510 may use neural networks and / or other artificial intelligence (AI) to control one or more UAVs in UAV 120-1. In some implementations, the GCS 510 may be included in a data center, cloud computing environment, server farm, or the like that may include multiple GCSs 510. Figure 5 In some aspects, GCS 510 may reside at least partially within core network 520 .

[0077] The USS device 515 includes one or more devices capable of receiving, storing, processing, and / or providing information associated with the UAV UE 120 and / or the GCS 510. For example, the USS device 515 may include an application server, a desktop computer, a laptop computer, a tablet computer, a mobile phone, or a similar device. In some specific implementations, the UAV 120-1 may interact with the USS device 515 to register a flight plan, receive approvals, analyses, and / or recommendations related to the flight plan, etc. The USS device 515 may register the UAV UE 120 with the USS device 515 by assigning an application-level UAV identifier to the UAV UE 120. The application-level UAV identifier may be an aviation authority (e.g., a regulatory agency that manages aviation operations in the jurisdiction in which the USS device 515 and the UAV UE 120 are operating) UAV identifier.

[0078] The core network 520 includes a network that enables communication between the RAN 505 (e.g., the base station 110) and one or more devices and / or networks connected to the core network 520. For example, the core network 520 may be a 5G core network. The core network 520 may include one or more core network devices 525, such as one or more access and mobility management functions (AMRs) (hereinafter referred to as "AMFs") 530, one or more network exposure functions (NEFs) (hereinafter referred to as "NEFs") 535, one or more session management functions (SMFs) (hereinafter referred to as "SMFs") 540, one or more policy control functions (PCFs) (hereinafter referred to as "PCFs") 545 and / or other entities and / or functions that provide mobility functions for the UAV UE 120 and enable the UAV UE 120 to communicate with other devices of the environment 500.

[0079] The AMF 530 may include one or more network devices, such as one or more server devices, capable of managing authentication, activation, deactivation, and / or mobility functions associated with the UAV UE 120 connected to the core network 520. In some implementations, the AMF 530 may perform operations related to authentication of the UAV 120-1. The AMF 530 may maintain a non-access stratum (NAS) signaling connection with the UAV 120-1.

[0080] NEF 535 may include one or more network exposure devices, such as one or more server devices, that can expose capabilities, events, information, etc. in one or more wireless networks to help other devices in the one or more wireless networks discover network services and / or efficiently utilize network resources. In some examples, NEF 535 may receive services from UAV 120-1 and / or transmit services to the UAV via AMF 530 and base station 110, and NEF 535 may receive services from USS device 515 and / or transmit services to the USS device via UAS network function (UAS-NF) 560. In some examples, NEF 535 may obtain a data structure, such as an approval of a flight plan of UAV 120-1, from USS device 515 and divide the data structure into multiple data segments. In some examples, NEF 535 may determine the location and / or reachability of UAV 120-1 and / or the communication capabilities of base station 110 to determine how to transmit multiple data segments to UAV 120-1.

[0081] SMF 540 may include one or more network devices, such as one or more server devices, capable of managing sessions for RAN 505 and assigning addresses (such as Internet Protocol (IP) addresses) to UAV 120-1. In some examples, SMF 540 may perform operations related to registration of UAV 120-1. For example, AMF 530 may receive a registration request from UAV 120-1 and forward the request to SMF 540 to create a corresponding packet data unit (PDU) session. SMF 540 may assign an address to UAV 120-1 and establish a PDU session for AMF 530.

[0082] The PCF 545 may include one or more network devices, such as one or more server devices, capable of managing traffic to and from the UAV UE 120 through the RAN 505 and implementing QoS on the RAN 505. In some examples, the PCF 545 may implement charging rules and traffic control rules, manage traffic priorities, and / or manage QoS for the UAV 120-1.

[0083] The USS device 515 may communicate with the core network 520 using the UAS-NF 560. The UAS-NF 560 may be a service-based interface to enable the USS device 515 to provide information to the core network 520. For example, the USS device 515 may provide registration information associated with the registration between the UAV 120-1 and the USS device 515 via the UAS-NF 560. The UAS-NF 560 may include a device external to the core network 520, such as a server device, or the UAS-NF 560 may reside at least partially on a core network device 525 within the core network 520. In some aspects, the UAS-NF 560 may be co-located with the NEF 535. In some aspects, one or more of the core network device 525 and / or the UAS-NF 560 may correspond to the network controller 130, as described above in conjunction with Figure 1 described.

[0084] UAV-C 120-2 can remotely control UAV 120-2 by sending C2 communications to UAV 120-1 and / or receiving C2 communications from UAV 120-1. In some examples, UAV-C 120-2 and UAV 120-1 can use the Uu interface for C2 communication. For example, UAV-C 120-2 can send C2 communications to UAV 120-1 (and receive C2 communications from UAV 120-1) via base station 110. In some examples, UAV-C 120-2 and UAV 120-1 can use non-cellular communication systems (e.g., non-3GPP connectivity) (such as wireless fidelity (Wi-Fi)) for C2 communication. Currently, in the specifications issued by 3GPP, NR does not support sending C2 communications via the PC5 interface. However, in some cases, UAV-C 120-2 may be able to communicate via the PC5 interface, but may not have Uu capabilities. Furthermore, since PC5 can cover longer distances than Wi-Fi, sending C2 communications via PC5 unicast communications may result in an increased range of C2 communications compared to Wi-Fi. Furthermore, sending C2 communications via PC5 unicast communications (e.g., via a PC5 direct link between UAV 120-1 and UAV-C 120-2) may result in reduced latency compared to C2 communications sent via base station 110 using a Uu interface.

[0085] In some examples, UAV 120-1 may subscribe to a mobile network operator (MNO) of a 5G system (5GS) (e.g., a 5GS including a core network 520 and a RAN 505), and UAV 120-1 may register with the 5GS. In this case, the 5GS may control the PC5 policy for UAV 120-1. However, in some cases, UAV-C 120-2 may not subscribe to the MNO, and UAV-C may not register with the 5GS. In this case, if UAV 120-1 and UAV-C 120-2 (e.g., via USS device 515) are pre-configured with PC5 policy, UAV-C may establish a PC5 direct link with UAV 120-1 (e.g., via core network device 525) without MNO management. This may result in UAV-C 120-2 sending C2 communications to UAV 120-1 via a PC5 direct link using radio resources managed by the MNO (e.g., in the licensed PC5 band) without authorization from the MNO. For UEs that have not registered with 5GS (and have not subscribed to an MNO), there is currently no mechanism to control and / or authorize communications via a PC5 direct link.

[0086] Some techniques and apparatuses described herein enable a network entity to receive an authorization request for C2 communication from an application server via a direct link between a pair of UEs (e.g., a UAV UE and a UAV-CUE). The authorization request may indicate a ProSe identifier associated with the C2 communication between the pair of UEs. The network entity may send an authorization indication for C2 communication to the application server via the direct link between the pair of UEs, and the authorization indication may indicate a destination layer 2 identifier associated with the ProSe identifier. In some aspects, the application server may send the ProSe identifier to the pair of UEs, and the pair of UEs may use the ProSe identifier and the associated destination layer 2 identifier to establish a direct link (e.g., a PC5 direct link). In some aspects, since the ProSe identifier is allocated for C2 communication between a specific pair of UEs, once C2 communication via the direct link between the pair of UEs is authorized, the ProSe identifier may be used to identify the authorized pair of UEs during a direct link (e.g., a PC5 direct link) establishment procedure. Therefore, C2 communication on a direct link (e.g., PC5 direct link) between a UAV UE and a UAV-C UE can be authorized (e.g., by a PCF in the core network) even if the UAV-C UE is not registered with the core network.

[0087] As indicated above, Figure 5 Other examples can be found in the Figure 5 Different than described.

[0088] Figure 6 6 is a diagram illustrating an example 600 associated with authorization of C2 communications via a direct link according to the present disclosure. Figure 6 As shown, example 600 includes a UAV UE 120-1, a UAV-C UE 120-2, a RAN node 601 (e.g., a base station 110, a RU, a DU, a CU, or a combination thereof), a core network device 525, a UAS-NF 560, and an application server 602. The UAV UE 120-1 may communicate with the RAN node 601 via a wireless access link (e.g., via a Uu interface), which may include an uplink and a downlink.

[0089] As above combined Figure 5 As described, the core network device 525 may include AMF 530, NEF 535, SMF 540 and / or PCF 545, etc. In some aspects, the UAV UE 120-1 may communicate with the core network device 525 using NAS signaling. In some aspects, the UAV UE 120-1 may communicate with the core network device 525 via the RAN node 601.

[0090] In some aspects, the application server 602 may be a USS device (e.g., Figure 5 The application server 602 may include an application function (AF) of the USS that provides aviation services to the UAV UE 120-1. In some aspects, the AF may access the core network (e.g., access the core network device 525 via the UAS-NF 560) to request authorization to establish a direct unicast link (e.g., a PC5 link) for C2 communication between a pair of UEs (e.g., UAV UE 120-1 and UAV-C UE 120-2). The application server 602 may communicate with the core network device 525 using the UAS-NF 560. The UAS-NF 560 may be a network entity, such as a network device associated with and / or included in the core network, or a network entity (e.g., a network device) may include the UAS-NF 560.

[0091] like Figure 6 As shown, and by reference numeral 605, the UAV UE 120-1 and the core network device 525 may perform registration and USS UAV authentication and authorization (UUAA) procedures. The UAV UE 120-1 and the core network device 525 may perform registration procedures to register the UAV UE 120-1 with the network. The registration procedure may include the UAV UE 120-1 sending a registration request to the core network device 525 (e.g., to the AMF 530). In some aspects, the registration request may indicate that the UAV UE 120-1 is registering for an air service (e.g., a UAS service) provided by the network. The core network device 525 may determine that the UUAA procedure will be performed on the UAV UE 120-1. For example, the core network device 525 may obtain subscription information associated with the UAV UE 120-1, and the core network device 525 may determine that the UUAA procedure will be performed by the UAV UE 120-1 based at least in part on the subscription information. The core network device 525 may perform UUAA procedures on the UAV UE 120-1 to authenticate the UAV UE 120-1 and authorize the UAV UE 120-1 to use air services (e.g., UAS services) provided by the network. The UUAA procedures may be defined by a regulatory body (such as an aviation administration or aviation management agency) that manages aviation operations within the jurisdiction in which the UAV UE 120 is operating.

[0092] In some aspects, the UAV-C UE 120-2 may not be registered with the core network device 525. For example, the UAV-C UE 120-2 may not subscribe to the MNO associated with the core network, or the UAV-C UE 120-2 may not have Uu capabilities. In other aspects, the UAV-C UE 120-2 may be registered with the core network device 525.

[0093] like Figure 6 As further shown, and by reference numeral 610, the UAV UE 120-1 and / or the UAV-C UE 120-2 may communicate with the application server 602 via application layer signaling. For example, the application signaling may indicate to the application server 602 that the UAV UE 120-1 and the UAV-C UE 120-2 are operating. In some aspects, the application layer signaling may include information related to the flight plan of the UAV UE 120-1. For example, the UAV UE 120-1 may send an indication of the flight plan to the application server 602, and the application server 602 may indicate that the flight plan is authorized (or not authorized). In some aspects, the application signaling may include a request to pair the UAV UE 120-1 with the UAV-C UE 120-2 for C2 communication. For example, UAV UE 120 - 1 may send a request to the application server 602 to pair with UAV-CUE 120 - 2 for C2 communication, or UAV-CUE 120 - 2 may send a request to the application server 602 to pair with UAV UE 120 - 1 for C2 communication.

[0094] like Figure 6As further shown, and by reference numeral 615, the application server 602 (e.g., AF) may determine to pair the UAV UE 120-1 with the UAV-C UE 120-2 for C2 communication via a direct link (e.g., a PC5 direct link), and the application server 602 (e.g., AF) may allocate a ProSe identifier for use in C2 communication between the particular pair of UEs (e.g., UAV UE 120-1 and UAV-C UE 120-2). In some aspects, the application server 602 may determine to pair the UAV UE 120-1 with the UAV-C UE 120-2 for C2 communication via a PC5 direct link based at least in part on receiving a request from the UAV UE 120-1 to pair the UAV UE 120-1 with the UAV-C UE 120-2. In some aspects, the application server 602 may determine to pair the UAV UE 120-1 with the UAV-C UE 120-2 for C2 communication via a PC5 direct link based at least in part on receiving a request from the UAV-C UE 120-2 to pair the UAV UE 120-1 with the UAV-C UE 120-2. In some aspects, the application server 602 may determine to pair the UAV UE 120-1 with the UAV-C UE 120-2 for C2 communication via a PC5 direct link regardless of any request from the UAV UE 120-1 or the UAV-C UE 120-2.

[0095] The application server 602 may allocate a ProSe identifier associated with C2 communication via a PC5 link between the specific pair of UEs (e.g., UAV UE 120-1 and UAV-C UE 120-2) to be paired as determined by the application server 602. "ProSe identifier" refers to an identifier used to indicate a ProSe application associated with ProSe operations in ProSe direct discovery and ProSe direct communication. A ProSe identifier may be associated with one or more ProSe applications, and a ProSe application may be associated with one or more ProSe identifiers. "ProSe direct discovery" refers to a procedure used by a ProSe-enabled UE to discover one or more other ProSe-enabled UEs in the vicinity of the ProSe-enabled UE, and "ProSe direct communication" refers to communication between two or more ProSe-enabled UEs in the vicinity via a path that does not traverse any network nodes. For ProSe direct discovery, the ProSe identifier may be equivalent to an application ID that identifies a specific application. In some aspects, in the case where V2X communication is used for C2 communication between the UAV UE 120-1 and the UAV-C UE 120-2, the ProSe identifier may be a V2X service identifier. In some aspects, the application server 602 may allocate a temporarily valid ProSe identifier for C2 communication between the UAV UE 120-1 and the UAV-C UE 120-2 via a PC5 direct link. In this case, a validity timer may be associated with the ProSe identifier, and the ProSe identifier may be temporarily valid (for establishing a direct PC5 link between the pair of UEs) for the duration of the validity timer.

[0096] like Figure 6As further shown, and by reference numeral 620, an application server 602 (e.g., AF) may send an authorization request for C2 communications to the UAS-NF 560 via a direct link (e.g., a PC5 direct link) between the UAV UE 120-1 and the UAV-C UE 120-2. The UAS-NF 560 may receive the authorization request from the application server 602. The authorization request may be a request submitted to the core network device 525 for authorization to establish a direct PC5 unicast link for C2 communications between a particular pair of UEs (e.g., the UAV UE 120-1 and the UAV-C UE 120-2). The authorization request may include an indication of a ProSe identifier associated with the C2 communications between the UAV UE 120-1 and the UAV-C UE 120-2. The authorization request may also include a UAV identifier (UAV ID) associated with the UAVUE 120-1, a UAV-C identifier (UAV-CID) associated with the UAV-C UE 120-2, and the duration of the validity timer associated with the ProSe identifier. In some aspects, the UAV ID may be a universal public subscription identifier (GPSI). In some aspects, the UAV ID may be a Civil Aviation Authority (CAA) level UAV ID. In this case, the core network device 525 may store (e.g., in the subscription information of the UAV UE 120-1) a mapping between the CAA level UAV ID of the UAV UE 120-1 and the GPSI of the UAV UE 120-1. In some aspects (e.g., when the UAV-C UE 120-2 is not subscribed to the core network / 5GS), the UAV-C ID may be a device ID, such as an international mobile equipment identity (IMEI) or a mobile equipment identifier (MEID).

[0097] like Figure 6 As further shown, and by reference numeral 625, the UAS-NF 560 may send a request for PCF authorization of C2 communications between the UAV UE 120-1 and the UAV-C UE 120-2 to the core network device 525 via a direct link (e.g., a PC5 direct link). For example, the UAS-NF 560 may send a request for authorization of C2 communications to the PCF 545 via a direct PC5 link between the UAV UE 120-1 and the UAV-C UE 120-2. The request for PCF authorization may include an indication of a ProSe identifier associated with the C2 communications between the UAV UE 120-1 and the UAV-C UE 120-2. The request for PCF authorization may also include a UAV ID associated with the UAV UE 120-1, a UAV-C ID associated with the UAV-C UE 120-2, and a duration of a validity timer associated with the ProSe identifier.

[0098] like Figure 6 As further shown, and by reference numeral 630, the core network device 525 (e.g., PCF 545) may authorize the request, assign a destination Layer 2 identifier to the ProSe identifier, and determine a ProSe policy. The core network device 525 (e.g., PCF 545) may receive a request for PCF authorization from the UAS-NF 560. The request for PCF authorization may indicate a ProSe identifier associated with C2 communications via a direct PC5 link between a particular pair of UEs (e.g., UAV UE 120-1 and UAV-C UE 120-2) indicated by a UAV ID and a UAV-C ID. The PCF 545 may determine whether to authorize the pair of UEs (e.g., UAV UE 120-1 and UAV-C UE 120-2) to establish a direct PC5 link between the UEs for C2 communications based at least in part on information included in the request for PCF authorization. For example, PCF 545 may determine whether to authorize a direct PC5 link for C2 communications between UAV UE 120-1 and UAV-C UE 120-2 based at least in part on determining whether the UAV UE 120-1 or UAV-C UE 120-2 has been paired with another UE for C2 communications and / or based at least in part on the availability of radio resources for sending C2 communications via a PC5 link, etc.

[0099] In conjunction with a determination to authorize C2 communications associated with a ProSe identifier (e.g., a determination to authorize the UAV UE 120-1 and the UAV-C UE 120-2 to establish a direct PC5 link for C2 communications), the PCF 545 may assign a destination Layer 2 identifier associated with the ProSe identifier. A "destination Layer 2 identifier" refers to a link layer identity that identifies a device or group of devices that are recipients of a ProSe communication frame. In some aspects, the destination Layer 2 identifier assigned by the PCF 545 may be a default destination Layer 2 identifier for establishing a direct link for C2 communications. For example, in the event that the UAV-C UE 120-2 is not registered with the core network, the PCF 545 may assign a default destination Layer 2 identifier for the ProSe identifier associated with C2 communications, and the default destination Layer 2 identifier may be used by the UAV UE 120-1 in a link establishment procedure for establishing a direct PC5 link with the UAV-C UE 120-2. This may allow the UAV UE 120-1 to establish a direct PC5 link with the UAV-C UE 120-2, where otherwise the UAV UE 120-1 may be unable to initiate a PC5 direct link establishment procedure due to a lack of a destination layer 2 identifier.

[0100] In some aspects, the PCF 545 may determine (e.g., compose) a ProSe policy associated with a ProSe identifier and an associated destination Layer 2 identifier for C2 communications. The ProSe policy may be a policy configured for the UAV UE 120-1 for communications (e.g., C2 communications) sent via a PC5 direct link between the UAV UE 120-1 and the UAV-C UE 120-2. The ProSe policy may indicate parameters to be used by the UAV UE 120-1 for C2 communications via a direct PC5 link, such as parameters related to security policies and / or parameters related to radio resources to be used for C2 communications via a direct PC5 link, etc. In some aspects, in the case where V2X communications are used for C2 communications between the UAV UE 120-1 and the UAV-C UE 120-2, the ProSe policy may be a V2X policy.

[0101] like Figure 6 As further shown, and by reference numeral 635, the core network device 525 (e.g., PCF 545) may send an authorization response to the UAS-NF 560. The UAS-NF 560 may receive the authorization response from the core network device 525 (e.g., from the PCF 545). The authorization response may be a response to the PCF's request for authorization. For example, the authorization response may indicate whether C2 communications associated with the ProSe identifier indicated in the request for PCF authorization (e.g., C2 communications via a direct PC5 link between the UAV UE 120-1 and the UAV-C UE 120-2) are authorized. In some aspects, when C2 communications are authorized by the PCF, the authorization response may indicate a destination layer 2 identifier associated with the ProSe identifier for the C2 communications, and the authorization response may indicate a ProSe policy for the ProSe identifier and the destination layer 2 identifier.

[0102] like Figure 6As further shown, and by reference numeral 640, the UAS-NF 560 may send an authorization indication to the application server 602. For example, the UAS-NF 560 may send the authorization indication to the application server 602 in conjunction with receiving an authorization response indicating that C2 communication via the direct PC5 link between the UAV UE 120-1 and the UAV-C UE 120-2 is authorized. The application server 602 may receive the authorization indication from the UAS-NF 560. The authorization indication may indicate that C2 communication associated with the ProSe identifier indicated in the authorization request (e.g., C2 communication via the direct PC5 link between the UAV UE 120-1 and the UAV-C UE 120-2) is authorized. The authorization indication may indicate a destination layer 2 identifier associated with the ProSe identifier for C2 communication. The authorization indication may also indicate a ProSe policy for the ProSe identifier for C2 communication and a destination layer 2 identifier associated with the ProSe identifier (e.g., a default destination layer 2 identifier).

[0103] like Figure 6 As further shown, and by reference numeral 645, the core network device 525 may send, to the UAV UE 120-1, an indication of a ProSe policy associated with a ProSe identifier and a destination layer 2 identifier assigned to the Pro-Se identifier. For example, the core network device 525 (e.g., the PCF 545) may send the indication of the ProSe policy to the UAV UE 120-1 via NAS signaling or via the RAN node 601. The UAV UE 120-1 may receive the indication of the ProSe policy determined by the PCF 545. The indication of the ProSe policy may configure the ProSe policy to be used by the UAV UE 120-1 for C2 communications associated with the ProSe identifier and a destination layer 2 ID assigned to the ProSe identifier (e.g., a default destination layer 2 identifier). That is, the indication of the ProSe policy may configure the ProSe policy for the UAV UE 120 - 1 to perform C2 communication via a direct PC5 link established between the UAV UE 120 - 1 and the UAV-C UE 120 - 2.

[0104] In some aspects, when the UAV-C UE 120-2 is registered with the core network, the core network device 525 may send an indication of the ProSe policy to the UAV-C UE 120-2 to configure the UAV-C UE 120-2 with the ProSe policy for C2 communications associated with the ProSe identifier and the destination Layer 2 identifier.

[0105] like Figure 6As further shown, and by reference numeral 650, the application server 602 (e.g., AF) may send an indication of a ProSe identifier associated with C2 communications and an indication of a duration of a validity timer associated with the ProSe identifier to the UAV UE 120-1 and / or the UAV-C UE 120-2 via a direct link (e.g., a direct PC5 link) between the UAV UE 120-1 and the UAV-C UE 120-2. In this case, the ProSe identifier may be associated with C2 communications that have been authorized (e.g., by the PCF 545) to be sent via the direct link (e.g., PC5 link) between the UAV UE 120-1 and the UAV-C UE 120-2. The application server 602 (e.g., AF) may also send an indication of a destination layer 2 identifier (e.g., a default destination layer 2 identifier) ​​assigned to the ProSe identifier to the UAV UE 120-1 and / or the UAV-C UE 120-2. In some aspects, the application server 602 may send an indication of the ProSe identifier to the application layer of the UAV UE 120-1 (e.g., via application layer signaling) for use by the UAV UE 120-1 in application layer operations. Additionally or alternatively, the application server 602 may send an indication of the ProSe identifier to the application layer of the UAV-C UE 120-2 (e.g., via application layer signaling) for use by the UAV-C UE 120-2 in application layer operations. In some aspects, the application server 602 (e.g., AF) may also send an indication of the destination layer 2 identifier (e.g., a default destination layer 2 identifier) ​​assigned to the ProSe identifier to the UAV UE 120-1 and / or the UAV-C UE 120-2. In some aspects, the application server 602 may send an indication of the duration of the validity timer to the application layer of the UAV UE 120-1 (e.g., via application layer signaling) for use by the UAV UE 120-1 in application layer operations. Additionally or alternatively, the application server 602 may send an indication of the duration of the validity timer to the application layer of the UAV-C UE 120-2 (e.g., via application layer signaling) for use by the UAV-C UE 120-2 in application layer operations.

[0106] In some aspects, the application server 602 (e.g., AF) may send an indication of a ProSe policy associated with a ProSe identifier and a destination layer 2 ID (e.g., a default destination layer 2 identifier) ​​assigned to the ProSe identifier to the UAV-C UE 120-2. In this case, the application server 602 (e.g., AF) may send an indication of a ProSe policy to the UAV-C UE 120-2 to configure the ProSe policy for the UAV-C UE 120-2 to perform C2 communication (e.g., C2 communication associated with the ProSe identifier and the destination layer 2 identifier) ​​via a direct PC5 link between the UAV-C UE 120-2 and the UAVUE 120-1.

[0107] like Figure 6 As further shown, and by reference numeral 655, the UAV UE 120-1 and the UAV-C UE 120-2 may establish a direct link (e.g., a direct PC5 link) for C2 communications based at least in part on a ProSe identifier and a destination layer 2 identifier associated with the C2 communications. The ProSe identifier may be associated with C2 communications that have been authorized (e.g., by the PCF 545) to be sent via a direct PC5 link between a particular pair of UEs (e.g., the UAV UE 120-1 and the UAV-C UE 120-2). The UAV UE 120-1 and / or the UAV-C UE 120-2 may use the ProSe identifier and the destination layer 2 identifier in a PC5 direct link establishment procedure. In some aspects, the UAV UE 120-1 may initiate a PC5 direct link establishment procedure by sending a PC5 direct link establishment request to the UAV-C UE 120-2, the PC5 direct link establishment request including an indication of the ProSe identifier and an indication of an associated destination layer 2 identifier (e.g., a default destination layer 2 identifier). In some aspects, the UAV-C UE 120-2 may initiate a PC5 direct link establishment procedure by sending a PC5 direct link establishment request to the UAV UE 120-1, the PC5 direct link establishment request including an indication of the ProSe identifier and an indication of an associated destination layer 2 identifier (e.g., a default destination layer 2 identifier).

[0108] In some aspects, the UAV UE 120-1 and the UAV-C UE 120-2 may establish a direct link (e.g., a direct PC5 link) between the UAV UE 120-1 and the UAV-C UE 120-2 before the validity timer associated with the ProSe identifier expires (e.g., within the duration of the validity timer). For example, the UAV UE 120-1 or the UAV-C UE 120-2 may initiate a PC5 direct link establishment procedure before the validity timer expires. For example, the duration of the validity timer may start when the C2 communication associated with the ProSe identifier is approved by the PCF 545, or the duration of the validity timer may start when the application server 602 sends an indication of the ProSe identifier of the approved C2 communication to the UAV UE 120-1 and / or the UAV-C UE 120-2. In some aspects, after the validity timer expires, if the PC5 direct link between the UAV UE 120-1 and the UAV-C UE 120-2 is released (or has not yet been established), the UAV-C UE 120-2 and the UAV-C UE 120-2 may no longer use the ProSe identifier for C2 communication between the UAV UE 120-1 and the UAV-C UE 120-2.

[0109] like Figure 6 As further shown, and by reference numeral 660, one or more C2 communications may be sent between the UAV UE 120-1 and the UAV-C UE 120-2 via a direct link (e.g., a PC5 direct link) between the UAV UE 120-1 and the UAV-C UE 120-2. In some aspects, via the PC5 direct link between the UAV UE 120-1 and the UAV-C UE 120-2, the UAV-C UE 120-2 may send and the UAV UE 120-1 may receive one or more C2 communications. In some aspects, via the PC5 direct link between the UAV UE 120-1 and the UAV-C UE 120-2, the UAV UE 120-1 may send and the UAV-C UE 120-2 may receive one or more C2 communications. For example, UAV-C UE 120 - 2 and / or UAV UE 120 - 1 may send C2 communications via unicast PC5 communications via a PC5 direct link established between UAV UE 120 - 1 and UAV-C UE 120 - 2.

[0110] In some aspects, a handover of remote control between UAV-C UEs may be performed in the event that multiple UAV-C UEs are capable of performing C2 communications with the UAV UE 120-1. In this case, a temporarily valid ProSe identifier for C2 communications may be assigned to a specific pair of UAV UEs 120-1 and a UAV-C UE list (e.g., including UAV-C UE 120-2). As long as there is another UAV-C UE performing C2 communications via a PC5 interface using the same ProSe identifier, the UAV UE 120-1 may switch from a PC5 link established with one UAV-C UE to a PC5 link established with another UAV-C, for example, based on the flight position of the UAV UE 120-1. The UAV UE 120-1 may release the PC5 link with one UAV-C UE after deciding to switch control of the UAV UE 120-1 to a new UAV-C UE. For example, the UAV UE 120-1 may release a direct link (e.g., a PC5 direct link) established with the UAV-C UE 120-2, and the UAV UE 120-1 may establish a direct link (e.g., a PC5 link) with another UAV-C based at least in part on the same ProSe identifier and destination Layer 2 identifier as used to establish the direct link with the UAV-C UE 120-2.

[0111] As indicated above, Figure 6 Other examples can be found in the Figure 6 Different than described.

[0112] Figure 7 7 is a diagram illustrating an example process 700 performed, for example, by a first UE according to the present disclosure. Example process 700 is an example in which a first UE (eg, UAV UE 120-1 or UAV-C UE 120-2) performs operations associated with authorization of C2 communications via a direct link.

[0113] like Figure 7 As shown, in some aspects, process 700 may include receiving, via a direct link between a first UE and a second UE, an indication of a ProSe identifier associated with an authorized C2 communication and an indication of a destination Layer 2 identifier associated with the ProSe identifier (block 710). For example, a first UE (e.g., using Fig. 9 The communication manager 140 and / or receiving component 902 depicted in FIG. 1 may receive, via a direct link between the first UE and the second UE, an indication of a ProSe identifier associated with the authorized C2 communication and an indication of a destination Layer 2 identifier associated with the ProSe identifier, as described above.

[0114] like Figure 7 As further shown, in some aspects, process 700 may include establishing a direct link with a second UE based at least in part on the ProSe identifier and the destination Layer 2 identifier (block 720). Fig. 9 The communications manager 140 and / or direct link establishment component 908 depicted in FIG. 1 may establish a direct link with the second UE based at least in part on the ProSe identifier and the destination Layer 2 identifier, as described above.

[0115] Process 700 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0116] In a first aspect, process 700 includes receiving an indication of a duration of a validity timer associated with a ProSe identifier, wherein establishing a direct link with a second UE includes establishing the direct link with the second UE based at least in part on the ProSe identifier and a destination Layer 2 identifier for the duration of the validity timer associated with the ProSe identifier.

[0117] In a second aspect, a ProSe identifier is associated with C2 communication via a direct link between a first UE and a second UE, the C2 communication being authorized based at least in part on an authorization request from an application server.

[0118] In a third aspect, process 700 includes receiving an indication of a ProSe policy associated with a ProSe identifier and a destination Layer 2 identifier.

[0119] In a fourth aspect, the ProSe identifier is a V2X service identifier, and the ProSe policy is a V2X policy.

[0120] In a fifth aspect, receiving an indication of a ProSe identifier and an indication of a destination layer 2 identifier includes receiving an indication of a ProSe identifier and an indication of a destination layer 2 identifier from an application server.

[0121] In a sixth aspect, receiving an indication of a ProSe identifier and an indication of a destination layer 2 identifier comprises receiving an indication of a ProSe identifier and an indication of a destination layer 2 identifier from a network entity.

[0122] In a seventh aspect, the first UE is a UAV and the second UE is a UAV-C.

[0123] In an eighth aspect, process 700 includes receiving one or more C2 communications from a second UE via a direct link with the second UE.

[0124] In a ninth aspect, the process 700 includes releasing the direct link with the second UE and establishing a direct link with a third UE based at least in part on the ProSe identifier and the destination Layer 2 identifier, wherein the third UE is another UAV-C.

[0125] In a tenth aspect, the first UE is a UAV-C and the second UE is a UAV.

[0126] In an eleventh aspect, process 700 includes sending one or more C2 communications to a second UE via a direct link with the second UE.

[0127] In a twelfth aspect, establishing a direct link with a second UE based at least in part on a ProSe identifier and a destination layer 2 identifier comprises establishing a PC5 direct link with the second UE based at least in part on a ProSe identifier and a destination layer 2 identifier.

[0128] although Figure 7 Example blocks of process 700 are shown, but in some aspects, process 700 may include Figure 7 In the embodiment of the present invention, the process 700 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 700. Additionally or alternatively, two or more blocks of the blocks of the process 700 may be executed in parallel.

[0129] Figure 8 is a diagram illustrating an example process 800, performed, for example, by a network entity, in accordance with the present disclosure. The example process 800 is an example of operations in which a network entity (eg, UAS-NF 560) performs authorization of C2 communications via a direct link.

[0130] like Figure 8 As shown, in some aspects, process 800 may include receiving an authorization request for C2 communication from an application server via a direct link between a pair of UEs, wherein the authorization request indicates a ProSe identifier associated with the C2 communication (block 810). For example, a network entity (e.g., using Fig.10 The communication manager 1008 and / or receiving component 1002 depicted in FIG. 1004 may receive an authorization request for C2 communication from an application server via a direct link between a pair of UEs, wherein the authorization request indicates a ProSe identifier associated with the C2 communication, as described above.

[0131] like Figure 8 As further shown, in some aspects, process 800 may include sending an authorization indication for C2 communication to an application server via a direct link between the pair of UEs, wherein the authorization indication indicates a destination layer 2 identifier associated with the ProSe identifier (block 820). Fig.10The communication manager 1008 and / or the sending component 1004 depicted in FIG. 1004 may send an authorization indication for C2 communication to the application server via the direct link between the pair of UEs, wherein the authorization indication indicates a destination layer 2 identifier associated with the ProSe identifier, as described above.

[0132] Process 800 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0133] In a first aspect, the pair of UEs includes a UAV and a UAV-C.

[0134] In a second aspect, the authorization request indicates a UAV identifier associated with the UAV and a UAV-C identifier associated with the UAV-C.

[0135] In a third aspect, the authorization request indicates a duration of a validity timer associated with the ProSe identifier.

[0136] In a fourth aspect, the authorization indication indicates a ProSe policy for a ProSe identifier and a destination Layer 2 identifier.

[0137] In a fifth aspect, process 800 includes sending a request for PCF authorization for C2 communication to a core network device via a direct link between the pair of UEs, and receiving from the core network device an indication of a destination layer 2 identifier associated with the ProSe identifier and an indication of a ProSe policy for the ProSe identifier and the destination layer 2 identifier.

[0138] In a sixth aspect, the destination layer 2 identifier is a default destination layer 2 identifier for establishing a direct link for C2 communications.

[0139] In a seventh aspect, the authorization request is a request for authorization to conduct C2 communications via a PC5 direct link between the pair of UEs.

[0140] although Figure 8 An example block diagram of process 800 is shown, but in some aspects, process 800 may include Figure 8 In the embodiment of the present invention, the process 800 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 800. Additionally or alternatively, two or more blocks in the blocks of process 800 may be executed in parallel.

[0141] Fig. 9900 is a diagram of an example apparatus 900 for wireless communication. The apparatus 900 may be a UE, or the UE may include the apparatus 900. In some aspects, the apparatus 900 includes a receiving component 902 and a transmitting component 904 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, the apparatus 900 may communicate with another apparatus 906 (such as a UE, a base station, or another wireless communication device) using the receiving component 902 and the transmitting component 904. As further shown, the apparatus 900 may include a communication manager 140. The communication manager 140 may include one or more of a direct link establishment component 908 and / or a direct link release component 910, etc.

[0142] In some aspects, the apparatus 900 may be configured to perform Figure 6 Additionally or alternatively, the apparatus 900 may be configured to perform one or more of the processes described herein (such as Figure 7 In some aspects, the apparatus 900 and / or Fig. 9 One or more of the components shown may include a combination of Figure 2 Additionally or alternatively, Fig. 9 One or more of the components shown may be combined Figure 2 Additionally or alternatively, one or more components in a set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and may be executed by a controller or processor to perform the function or operation of the component.

[0143] The receiving component 902 may receive communications from the device 906, such as reference signals, control information, data communications, or a combination thereof. The receiving component 902 may provide the received communications to one or more other components of the device 900. In some aspects, the receiving component 902 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 900. In some aspects, the receiving component 902 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of the described UE.

[0144] Transmit component 904 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 906. In some aspects, one or more other components of device 900 may generate communications and may provide the generated communications to transmit component 904 for transmission to device 906. In some aspects, transmit component 904 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to device 906. In some aspects, transmit component 904 may include combining Figure 2 One or more antennas, modems, demodulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described UE. In some aspects, the transmit component 904 can be co-located with the receive component 902 in a transceiver.

[0145] Receiving component 902 may receive, via a direct link between the first UE and the second UE, an indication of a ProSe identifier associated with the authorized C2 communication and an indication of a destination layer 2 identifier associated with the ProSe identifier. Direct link establishing component 908 may establish a direct link with the second UE based at least in part on the ProSe identifier and the destination layer 2 identifier.

[0146] The receiving component 902 may receive an indication of a duration of a validity timer associated with the ProSe identifier, wherein establishing the direct link with the second UE comprises establishing the direct link with the second UE based at least in part on the ProSe identifier and the destination layer 2 identifier within the duration of the validity timer associated with the ProSe identifier.

[0147] Receiving component 902 may receive an indication of a ProSe policy associated with a ProSe identifier and a destination Layer 2 identifier.

[0148] Receiving component 902 can receive one or more C2 communications from a second UE via a direct link with the second UE.

[0149] The direct link releasing component 910 may release the direct link with the second UE.

[0150] The direct link establishing component 908 may establish a direct link with a third UE based at least in part on the ProSe identifier and the destination Layer 2 identifier, where the third UE is another UAV-C.

[0151] Transmitting component 904 can transmit one or more C2 communications to the second UE via a direct link with the second UE.

[0152] Fig. 9The number and arrangement of components shown are provided as examples. In practice, there may be Fig. 9 Additional components, fewer components, different components, or components arranged in a different manner than those shown in FIG. Fig. 9 Two or more components shown in may be implemented in a single component, or Fig. 9 A single component shown in may be implemented as multiple distributed components. Additionally or alternatively, Fig. 9 A set (one or more) of components shown in can perform the operations described in Fig. 9 One or more functions performed by another set of components shown in FIG.

[0153] Fig.10 1 is a diagram of an example apparatus 1000 for wireless communication. Apparatus 1000 may be a network entity, or a network entity may include apparatus 1000. In some aspects, apparatus 1000 includes a receiving component 1002 and a transmitting component 1004 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1000 may communicate with another apparatus 1006 (such as a UE, a base station, or another wireless communication device) using receiving component 1002 and transmitting component 1004. As further shown, apparatus 1000 may include a communication manager 1008. Communication manager 1008 may include, among other things, a determining component 1010.

[0154] In some aspects, the apparatus 1000 may be configured to perform Figure 6 Additionally or alternatively, the apparatus 1000 may be configured to perform one or more of the processes described herein (such as Figure 8 In some aspects, the apparatus 1000 and / or Fig.10 One or more of the components shown may include a combination of Figure 2 Additionally or alternatively, Fig.10 One or more of the components shown may be combined Figure 2 Additionally or alternatively, one or more components in a set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and may be executed by a controller or processor to perform the function or operation of the component.

[0155] The receiving component 1002 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the apparatus 1006. The receiving component 1002 may provide the received communications to one or more other components of the apparatus 1000. In some aspects, the receiving component 1002 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the apparatus 1000. In some aspects, the receiving component 1002 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of the described network entities.

[0156] The transmitting component 1004 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the apparatus 1006. In some aspects, one or more other components of the apparatus 1000 may generate communications and may provide the generated communications to the transmitting component 1004 for transmission to the apparatus 1006. In some aspects, the transmitting component 1004 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the apparatus 1006. In some aspects, the transmitting component 1004 may include a combination of Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described network entities. In some aspects, the transmit component 1004 can be co-located with the receive component 1002 in a transceiver.

[0157] The receiving component 1002 may receive an authorization request for C2 communication from an application server via a direct link between a pair of UEs, wherein the authorization request indicates a ProSe identifier associated with the C2 communication. The sending component 1004 may send an authorization indication for C2 communication to the application server via the direct link between the pair of UEs, wherein the authorization indication indicates a destination layer 2 identifier associated with the ProSe identifier.

[0158] The sending component 1004 can send a request for PCF authorization of C2 communications to the core network device via the direct link between the pair of UEs.

[0159] Receiving component 1002 may receive, from a core network device, an indication of a destination layer 2 identifier associated with the ProSe identifier and an indication of a ProSe policy for the ProSe identifier and the destination layer 2 identifier.

[0160] Determining component 1010 can determine a request for PCF authorization based at least in part on the authorization request.

[0161] Fig.10 The number and arrangement of components shown are provided as examples. In practice, there may be Fig.10 Additional components, fewer components, different components, or components arranged in a different manner than those shown in FIG. Fig.10 Two or more components shown in may be implemented in a single component, or Fig.10 A single component shown in may be implemented as multiple distributed components. Additionally or alternatively, Fig.10 A set (one or more) of components shown in can perform the operations described in Fig.10 One or more functions performed by another set of components shown in FIG.

[0162] The following provides an overview of some aspects of the disclosure:

[0163] Aspect 1: A method of wireless communication performed by a first user equipment (UE), the method comprising: receiving an indication of a proximity-based service (ProSe) identifier associated with authorized command and control (C2) communications and an indication of a destination layer 2 identifier associated with the ProSe identifier via a direct link between the first UE and a second UE; and establishing a direct link with the second UE based at least in part on the ProSe identifier and the destination layer 2 identifier.

[0164] Aspect 2: According to the method of aspect 1, the method also includes: receiving an indication of the duration of a validity timer associated with the ProSe identifier, wherein establishing the direct link with the second UE includes: establishing the direct link with the second UE based at least in part on the ProSe identifier and the destination layer 2 identifier within the duration of the validity timer associated with the ProSe identifier.

[0165] Aspect 3: The method according to any one of Aspects 1 to 2, wherein the ProSe identifier is associated with C2 communication via the direct link between the first UE and the second UE, and the C2 communication is authorized based at least in part on an authorization request from an application server.

[0166] Aspect 4: The method according to any one of Aspects 1 to 3, further comprising: receiving an indication of a ProSe policy associated with the ProSe identifier and the destination Layer 2 identifier.

[0167] Aspect 5: The method according to aspect 4, wherein the ProSe identifier is a vehicle-to-everything (V2X) service identifier, and the ProSe policy is a V2X policy.

[0168] Aspect 6: The method according to any one of Aspects 1 to 5, wherein receiving the indication of the ProSe identifier and the indication of the destination Layer 2 identifier includes: receiving the indication of the ProSe identifier and the indication of the destination Layer 2 identifier from an application server.

[0169] Aspect 7: The method according to any one of Aspects 1 to 6, wherein receiving the indication of the ProSe identifier and the indication of the destination Layer 2 identifier includes: receiving the indication of the ProSe identifier and the indication of the destination Layer 2 identifier from a network entity.

[0170] Aspect 8: The method according to any one of aspects 1 to 7, wherein the first UE is an unmanned aerial vehicle (UAV) and the second UE is an unmanned aerial vehicle controller (UAV-C).

[0171] Aspect 9: The method according to aspect 8, the method also includes: receiving one or more C2 communications from the second UE via the direct link with the second UE.

[0172] Aspect 10: According to any one of Aspects 8 to 9, the method also includes: releasing the direct link with the second UE; and establishing a direct link with a third UE based at least in part on the ProSe identifier and the destination layer 2 identifier, wherein the third UE is another UAV-C.

[0173] Aspect 11: The method according to any one of aspects 1 to 7, wherein the first UE is an unmanned aerial vehicle controller (UAV-C) and the second UE is an unmanned aerial vehicle (UAV).

[0174] Aspect 12: The method according to aspect 11, the method also includes: sending one or more C2 communications to the second UE via the direct link with the second UE.

[0175] Aspect 13: A method according to any one of Aspects 1 to 12, wherein establishing the direct link with the second UE based at least in part on the ProSe identifier and the destination Layer 2 identifier includes: establishing a PC5 direct link with the second UE based at least in part on the ProSe identifier and the destination Layer 2 identifier.

[0176] Aspect 14: A method of wireless communication performed by a network entity, the method comprising: receiving an authorization request for command and control (C2) communication from an application server via a direct link between a pair of user equipment (UE), wherein the authorization request indicates a proximity-based service (ProSe) identifier associated with the C2 communication; and sending an authorization indication for the C2 communication to the application server via the direct link between the pair of UEs, wherein the authorization indication indicates a destination layer 2 identifier associated with the ProSe identifier.

[0177] Aspect 15: The method according to aspect 14, wherein the pair of UEs includes an unmanned aerial vehicle (UAV) and an unmanned aerial vehicle controller (UAV-C).

[0178] Aspect 16: The method according to Aspect 15, wherein the authorization request indicates a UAV identifier associated with the UAV and a UAV-C identifier associated with the UAV-C.

[0179] Aspect 17: The method according to any one of Aspects 14 to 16, wherein the authorization request indicates a duration of a validity timer associated with the ProSe identifier.

[0180] Aspect 18: The method according to any one of Aspects 14 to 17, wherein the authorization indication indicates a ProSe policy for the ProSe identifier and the destination Layer 2 identifier.

[0181] Aspect 19: According to the method described in Aspect 18, the method also includes: sending a request for policy control function (PCF) authorization for the C2 communication to a core network device via the direct link between the pair of UEs; and receiving from the core network device an indication of the destination layer 2 identifier associated with the ProSe identifier and an indication of the ProSe policy for the ProSe identifier and the destination layer 2 identifier.

[0182] Aspect 20: The method according to any one of aspects 18 to 19, wherein the destination layer 2 identifier is a default destination layer 2 identifier for establishing a direct link for C2 communication.

[0183] Aspect 21: The method according to any one of aspects 14 to 20, wherein the authorization request is a request for authorization to conduct C2 communication via a PC5 direct link between the pair of UEs.

[0184] Aspect 22: An apparatus for performing wireless communications at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 1 to 13.

[0185] Aspect 23: A device for wireless communication, the device comprising: a memory; and one or more processors, the one or more processors coupled to the memory, the one or more processors configured to execute the method according to one or more of aspects 1 to 13.

[0186] Aspect 24: An apparatus for wireless communication, the apparatus comprising at least one means for performing the method according to one or more of aspects 1 to 13.

[0187] Aspect 25: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 1 to 13.

[0188] Aspect 26: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 1 to 13.

[0189] Aspect 27: An apparatus for performing wireless communications at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 14 to 21.

[0190] Aspect 28: A device for wireless communication, the device comprising: a memory; and one or more processors, the one or more processors coupled to the memory, the one or more processors configured to execute the method according to one or more of aspects 14 to 21.

[0191] Aspect 29: An apparatus for wireless communication, the apparatus comprising at least one means for performing the method according to one or more of aspects 14 to 21.

[0192] Aspect 30: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 14 to 21.

[0193] Aspect 31: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 14 to 21.

[0194] While the foregoing disclosure provides illustration and description, it is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations are possible in light of the above disclosure or may be acquired from practice of these aspects.

[0195] As used herein, the term "component" is intended to be broadly interpreted as a combination of hardware and / or hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other names, "software" should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures and / or functions, etc. As used herein, a "processor" is implemented in a combination of hardware and / or hardware and software. It will be apparent that the systems and / or methods described herein can be implemented by a combination of hardware and / or hardware and software in different forms. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit various aspects. Therefore, the operation and behavior of the system and / or method are not described herein with reference to specific software codes, because those skilled in the art will understand that software and hardware can be designed to implement the system and / or method based at least in part on the description herein.

[0196] As used herein, "satisfying a threshold" may mean a value is greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc., depending on the context.

[0197] Although specific combinations of features are set forth in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features can be combined in a manner that is not specifically described in the claims and / or is not disclosed in the specification. The disclosure of various aspects includes each dependent claim combined with each other claim in the claim set. As used herein, the phrase "at least one of" the list of items refers to any combination of these items (which includes a single member). As an example, "at least one of a, b or c" is intended to cover a, b, c, a+b, a+c, b+c and a+b+c, and any combination with multiple identical elements (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c and c+c+c, or any other ordering of a, b and c).

[0198] Any element, action or instruction used herein should not be interpreted as critical or necessary unless clearly described as such. Moreover, as used herein, the articles "one" and "a kind of" are intended to include one or more entries and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more entries connected to the article "said", and can be used interchangeably with "one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more entries and can be used interchangeably with "one or more". If you only want to refer to an entry, the phrase "only one" or similar terms will be used. Moreover, as used herein, the term "having" etc. is intended to be an open term, which does not limit the elements they modify (for example, "having" A elements can also have B). In addition, the phrase "based on" is intended to mean "based at least in part on", unless otherwise explicitly stated. Furthermore, as used herein, the term "or" when used in a series is intended to be open-ended and may be used interchangeably with "and / or" unless expressly stated otherwise (eg, if used in conjunction with "either" or "only one of").

Claims

1. A first user equipment (UE) for wireless communication, the first user equipment (UE) comprising: Memory; and one or more processors, the one or more processors coupled to the memory, the one or more processors configured to: Receiving, via a direct link between the first UE and a second UE, a proximity-based service (ProSe) associated with an authorized command and control (C2) communication an indication of an identifier and an indication of a destination Layer 2 identifier associated with the ProSe identifier; as well as A direct link is established with the second UE based at least in part on the ProSe identifier and the destination Layer 2 identifier.

2. The UE of claim 1, wherein the one or more processors are further configured to: receiving an indication of a duration of a validity timer associated with the ProSe identifier, wherein establishing the direct link with the second UE comprises: The direct link with the second UE is established based at least in part on the ProSe identifier and the destination Layer 2 identifier within the duration of the validity timer associated with the ProSe identifier. 3 . The UE of claim 1 , wherein the ProSe identifier is associated with C2 communication via the direct link between the first UE and the second UE, the C2 communication being authorized based at least in part on an authorization request from an application server.

4. The UE of claim 1, wherein the one or more processors are further configured to: An indication of a ProSe policy associated with the ProSe identifier and the destination Layer 2 identifier is received, wherein the ProSe identifier is a vehicle-to-everything (V2X) service identifier and the ProSe policy is a V2X policy.

5. The UE of claim 1 , wherein to receive the indication of the ProSe identifier and the indication of the destination Layer 2 identifier, the one or more processors are configured to: The indication of the ProSe identifier and the indication of the destination Layer 2 identifier are received from an application server.

6. The UE of claim 1 , wherein to receive the indication of the ProSe identifier and the indication of the destination Layer 2 identifier, the one or more processors are configured to: The indication of the ProSe identifier and the indication of the destination Layer 2 identifier are received from a network entity.

7. The UE of claim 1, wherein the first UE is an unmanned aerial vehicle (UAV) and the second UE is an unmanned aerial vehicle controller (UAV-C).

8. The UE of claim 7, wherein the one or more processors are further configured to: One or more C2 communications are received from the second UE via the direct link with the second UE.

9. The UE of claim 7, wherein the one or more processors are further configured to: releasing the direct link with the second UE; and A direct link is established with a third UE based at least in part on the ProSe identifier and the destination Layer 2 identifier, wherein the third UE is another UAV-C.

10. The UE of claim 1, wherein the first UE is an unmanned aerial vehicle controller (UAV-C) and the second UE is an unmanned aerial vehicle (UAV).

11. The UE of claim 10, wherein the one or more processors are further configured to: One or more C2 communications are sent to the second UE via the direct link with the second UE.

12. The UE of claim 1 , wherein to establish the direct link with the second UE based at least in part on the ProSe identifier and the destination Layer 2 identifier, the one or more processors are configured to: A PC5 direct link is established with the second UE based at least in part on the ProSe identifier and the destination Layer 2 identifier.

13. A network entity for wireless communication, the network entity comprising: Memory; and one or more processors, the one or more processors coupled to the memory, the one or more processors configured to: receiving, from an application server via a direct link between a pair of user equipments (UEs), an authorization request for command and control (C2) communications, wherein the authorization request indicates a proximity-based service (ProSe) identifier associated with the C2 communications; and An authorization indication for the C2 communication is sent to the application server via the direct link between the pair of UEs, wherein the authorization indication indicates a destination layer 2 identifier associated with the ProSe identifier.

14. The network entity of claim 13, wherein the pair of UEs comprises an unmanned aerial vehicle (UAV) and an unmanned aerial vehicle controller (UAV-C).

15. The network entity of claim 14, wherein the authorization request indicates a UAV identifier associated with the UAV and a UAV-C identifier associated with the UAV-C. 16 . The network entity of claim 13 , wherein the authorization request indicates a duration of a validity timer associated with the ProSe identifier.

17. The network entity of claim 13, wherein the authorization indication indicates a ProSe policy for the ProSe identifier and the destination Layer 2 identifier, and wherein the one or more processors are further configured to: sending a request for policy control function (PCF) authorization of the C2 communication to a core network device via the direct link between the pair of UEs; and An indication of the destination Layer 2 identifier associated with the ProSe identifier and an indication of the ProSe policy for the ProSe identifier and the destination Layer 2 identifier are received from the core network device.

18. The network entity of claim 17, wherein the destination layer 2 identifier is a default destination layer 2 identifier for establishing a direct link for C2 communication.

19. The network entity of claim 13, wherein the authorization request is a request for authorization to conduct C2 communication via a PC5 direct link between the pair of UEs.

20. A method of wireless communication performed by a first user equipment (UE), the method comprising: receiving, via a direct link between the first UE and a second UE, an indication of a proximity-based service (ProSe) identifier associated with authorized command and control (C2) communications and an indication of a destination layer 2 identifier associated with the ProSe identifier; as well as A direct link is established with the second UE based at least in part on the ProSe identifier and the destination Layer 2 identifier.

21. The method according to claim 20, further comprising: and receiving an indication of a duration of a validity timer associated with the ProSe identifier, wherein establishing the direct link with the second UE comprises: establishing the direct link with the second UE based at least in part on the ProSe identifier and the destination Layer 2 identifier for the duration of the validity timer associated with the ProSe identifier.

22. The method of claim 20, wherein the ProSe identifier is associated with C2 communication via the direct link between the first UE and the second UE, the C2 communication being authorized based at least in part on an authorization request from an application server.

23. The method of claim 20, wherein receiving the indication of the ProSe identifier and the indication of the destination Layer 2 identifier comprises: The indication of the ProSe identifier and the indication of the destination Layer 2 identifier are received from an application server.

24. The method of claim 20, wherein receiving the indication of the ProSe identifier and the indication of the destination Layer 2 identifier comprises: The indication of the ProSe identifier and the indication of the destination Layer 2 identifier are received from a network entity.

25. The method of claim 20, wherein the first UE is an unmanned aerial vehicle (UAV) and the second UE is an unmanned aerial vehicle controller (UAV-C), and wherein the method further comprises: One or more C2 communications are received from the second UE via the direct link with the second UE.

26. The method according to claim 25, further comprising: releasing the direct link with the second UE; as well as A direct link is established with a third UE based at least in part on the ProSe identifier and the destination Layer 2 identifier, wherein the third UE is another UAV-C.

27. The method of claim 20, wherein the first UE is an unmanned aerial vehicle controller (UAV-C) and the second UE is an unmanned aerial vehicle (UAV), and wherein the method further comprises: One or more C2 communications are sent to the second UE via the direct link with the second UE.

28. A method of wireless communication performed by a network entity, the method comprising: receiving, from an application server via a direct link between a pair of user equipments (UEs), an authorization request for command and control (C2) communications, wherein the authorization request indicates a proximity-based service (ProSe) identifier associated with the C2 communications; and An authorization indication for the C2 communication is sent to the application server via the direct link between the pair of UEs, wherein the authorization indication indicates a destination layer 2 identifier associated with the ProSe identifier.

29. The method of claim 28, wherein the pair of UEs comprises an unmanned aerial vehicle (UAV) and an unmanned aerial vehicle controller (UAV-C), and wherein the authorization request indicates a UAV identifier associated with the UAV and a UAV-C identifier associated with the UAV-C. 30 . The method of claim 28 , wherein the authorization request indicates a duration of a validity timer associated with the ProSe identifier.