Method and apparatus for unmanned aerial vehicle system (UAS) identification, binding and pairing

Cellular technologies like LTE and 5G enhance UAS communications by enabling reliable and high-data-rate operations through identification, binding, and authentication methods, addressing the limitations of ISM band communications in UAS.

CN119095147AActive Publication Date: 2024-12-06INTERDIGITAL PATENT HOLDINGS INC

Patent Information

Application Number
CN202411315175.1
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2019-08-23
Filing Date
2020-08-21
Publication Date
2024-12-06
Estimated Expiration
2040-08-21

AI Technical Summary

Technical Problem

Existing unmanned aerial systems (UAS) primarily rely on unlicensed industrial, scientific, and medical (ISM) bands for direct point-to-point communications, which limits their operational scope and results in unreliable and low data rate communications, hindering the full exploration of UAV applications.

Method used

Implementing cellular technologies like LTE and 5G for beyond-visual-range flight operations and high-performance communications, with methods for identifying, binding, and authenticating UAS in a cellular network through a UAV wireless transmit/receive unit (UAV WTRU) sending a non-access stratum (NAS) request message to an access and mobility management function (AMF) for pairing authorization with a UAV controller (UAV-C).

Benefits of technology

Enables reliable and high-data-rate communications for UAS, facilitating beyond-visual-range flight operations and enhancing the scope of UAV applications by ensuring secure and efficient pairing with UAV controllers.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119095147A_ABST
    Figure CN119095147A_ABST
Patent Text Reader

Abstract

Methods and apparatus for pairing an unmanned aerial vehicle (UAV) with a UAV controller (UAV-C) are described. For example, a UAV having a UAV wireless transmit / receive unit (UAV WTRU) may transmit a non-access stratum (NAS) request message to an access and mobility management function (AMF), the request message including a pairing request indication and a UAV controller (UAV-C) identification (UAV-C ID). The UAV-C ID may be carried in a pairing request sent to an unmanned aerial vehicle system (UAS) service provider (USS) / UAS traffic management (UTM) for pairing authorization of the UAV and a UAV-C associated with the UAV-C ID. The UAV may receive, from the AMF, a NAS response message including an unmanned aerial vehicle system (UAS) identification (UAS ID) indicating that the UAV is paired with the UAV-C, wherein the UAS ID is specified by the USS / UTM.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] This application is a divisional application of the Chinese invention patent application with the application date of August 21, 2020, application number 202080066075.3, and invention name “Method and device for identification, binding and pairing of unmanned aerial vehicle systems (UAS)”.

[0002] CROSS-REFERENCE TO RELATED APPLICATIONS

[0003] This application claims the benefit of U.S. Provisional Application No. 62 / 890,920, filed on August 23, 2019, the contents of which are incorporated herein by reference. Background Art

[0004] The number of unmanned aerial vehicles (UAVs) has grown rapidly in recent years, and the applications enabled by UAVs are expanding to a variety of industries. However, today's unmanned aerial systems (UAS) (e.g., UAVs and UAV controllers) rely primarily on direct point-to-point communications via unlicensed industrial, scientific, and medical (ISM) bands, which limits the scope of operation, and the communications are typically unreliable, unsafe, and low data rates. In order to fully explore the potential of UAV applications, cellular technologies such as long-term evolution (LTE) and 5G can be used to achieve beyond-visual-range flight (BVLOS) operations and high-performance and reliable communications of UAS. For example, when performing its mission, a UAS connected to a cellular network may involve various types of cellular communications, such as UAS to UAS traffic management (UTM) communications, non-payload communications, and / or payload communications. Therefore, in order to implement such communications in a cellular network, methods and devices for identifying, binding, pairing, and / or authenticating UAS in a cellular network are required. Summary of the invention

[0005] Methods and apparatus for pairing an unmanned aerial vehicle (UAV) with a UAV controller (UAV-C) are described herein. For example, a UAV having a UAV wireless transmit / receive unit (UAV WTRU) for cellular communication may send a non-access stratum (NAS) request message to an access and mobility management function (AMF), the request message including a pairing request indication and a UAV controller (UAV-C) identifier (UAV-C ID). The UAV-C ID may be carried in a pairing request for pairing authorization of the UAV and the UAV-C associated with the UAV-C ID sent to an unmanned aerial system (UAS) service provider (USS) / UAS traffic management (UTM). The pairing request for pairing authorization of the UAV with the UAV-C sent to the USS / UTM may include the UAV ID and the UAV-C ID. The UAV may receive a NAS response message from the AMF including an unmanned aerial system (UAS) identifier (UAS ID) indicating that the UAV is paired with the UAV-C, wherein the UAS ID is specified by the USS / UTM. The NAS request message may be a protocol data unit (PDU) session request message and the NAS response message may be a PDU session response message. BRIEF DESCRIPTION OF THE DRAWINGS

[0006] A more detailed understanding may be obtained from the following description given by way of example in conjunction with the accompanying drawings, in which like reference numerals indicate like elements, and in which:

[0007] Figure 1A is a system diagram illustrating an exemplary communication system in which one or more disclosed embodiments may be implemented;

[0008] Figure 1B It is shown that according to one embodiment, Figure 1A A system diagram of an exemplary wireless transmit / receive unit (WTRU) for use within the communication system shown;

[0009] Figure 1C It is shown that according to one embodiment, Figure 1A A system diagram of an exemplary radio access network (RAN) and an exemplary core network (CN) used within the illustrated communication system;

[0010] Figure 1D It is shown that according to one embodiment, Figure 1A A system diagram of another exemplary RAN and another exemplary CN used in the communication system shown;

[0011] Figure 2 is a schematic diagram illustrating an exemplary architecture of an unmanned aerial system (UAS) for supporting a 5G network;

[0012] Figure 3 is a schematic diagram illustrating exemplary types of unmanned aerial vehicle (UAV) communications enabled via a cellular network;

[0013] Figure 4 is a schematic diagram illustrating an exemplary UAS interaction with a network and UAS traffic management (UTM) for authorization;

[0014] Figure 5A is a schematic diagram showing an exemplary UAS pairing and authorization scenario with a UAV about to come online;

[0015] Figure 5B is a schematic diagram showing an exemplary UAS pairing and authorization scenario for UAV-C to be launched soon;

[0016] Figure 5C is a diagram showing an exemplary UAS pairing and authorization scenario where a UAV and a UAV-C are establishing communications;

[0017] Figure 6 is a schematic diagram illustrating an exemplary process of UAV controller (UAV-C) assisted UAS pairing;

[0018] Figure 7 is a diagram illustrating an exemplary process of subscription-based (bulk) pairing and authorization;

[0019] Figure 8 is a schematic diagram showing an exemplary process of UAV-C change;

[0020] Fig. 9 is a schematic diagram showing an exemplary process of UAS multi-level authorization promoted by the 3GPP system;

[0021] Fig.10 is a schematic diagram showing another exemplary process of UAS multi-level authorization promoted by the 3GPP system;

[0022] Fig.11A is a schematic diagram illustrating an exemplary process for multi-level authorization across multiple UTMs and / or UAS service providers (USSs);

[0023] Fig. 11B catch Fig.11A ;

[0024] Fig. 12A is a schematic diagram illustrating an exemplary process of identification, binding, pairing and authorization on a public land mobile network (PLMN);

[0025] Fig. 12B catch Fig. 12A ;as well as

[0026] Fig.13is a diagram showing an exemplary process for binding and pairing between a UAV and a UAV-C. DETAILED DESCRIPTION

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0064] Very high throughput (VHT) STA can support 20MHz, 40MHz, 80MHz and / or 160MHz wide channels. 40MHz and / or 80MHz channels can be formed by combining continuous 20MHz channels. A 160MHz channel can be formed by combining 8 continuous 20MHz channels, or by combining two non-continuous 80MHz channels (this can be called 80+80 configuration). For the 80+80 configuration, after channel coding, the data can pass through a segment parser that can divide the data into two streams. Each stream can be processed by inverse fast Fourier transform (IFFT) and time domain processing separately. These streams can be mapped to two 80MHz channels, and data can be transmitted by transmitting STA. At the receiver of the receiving STA, the above-mentioned operation for the 80+80 configuration can be reversed, and the combined data can be sent to the medium access control (MAC).

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

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

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

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

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

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

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

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

[0073] Figure 1DThe illustrated CN 106 may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one session management function (SMF) 183a, 183b, and possible data networks (DNs) 185a, 185b. Although the aforementioned elements are depicted as part of the CN 106, it should be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.

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

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

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

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

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

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

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

[0081] The number of unmanned aerial vehicles (UAVs) has grown rapidly in recent years, and the applications enabled by UAVs are expanding to a variety of industries. However, today's unmanned aerial systems (UAS) (e.g., UAVs and UAV controllers) mainly rely on direct point-to-point communications via unlicensed industrial, scientific, and medical (ISM) bands, which limits the range of operation, and the communications are often unreliable, unsafe, and low data rates. In order to fully explore the potential of UAV applications, advanced cellular technologies such as LTE and 5G can be used to achieve beyond visual line of sight (BVLOS) operations and high performance and reliable communications for UAS.

[0082] The benefits of using cellular networks are obvious. For example, ubiquitous mobile network coverage can provide an operating range far beyond the limitations of point-to-point communications using ISM frequencies. The advanced communication capabilities of modern cellular networks (especially 5G networks) (such as high bandwidth, low latency, guaranteed QoS, etc.) greatly improve the performance of UAV applications. The advanced security mechanisms of modern cellular networks can address the serious security issues involved in managing UAV applications.

[0083] Figure 2 An exemplary architecture 200 for supporting unmanned aerial systems (UAS) in a 5G network is shown, which may be used in conjunction with any other embodiments described herein. Figure 2As shown, UAS Traffic Management (UTM) 210 can be a framework for UAS traffic management. The roles and responsibilities of UTM 210 and the procedures and protocols applied in UTM 210 may be different between countries. UTM 210 may refer to a set of functions for authenticating UAVs, authorizing UAS services, managing UAS policies, and controlling UAV traffic in airspace. For example, UTM can be a server that implements such functions for UAVs, UAV-Cs, and / or UASs. An authorized user or UTM client 220 can query the identities and metadata of UAVs 202a to 202e and their UAV controllers 203a, 203b via UTM 210. UTM 210 can store data required for operating UAS. Air traffic control agents can use UTM servers 210 to authorize, execute, and / or regulate UAS operations.

[0084] like Figure 2 As shown, the 5G core network 206 may include PCF 281a, SMF 282a, SMF 283a, UPF 284a, 284b, NEF 285a, etc. Figure 2In the illustrated architecture, the UAS (e.g., UAVs 202a to 202e and / or UAV-Cs 203a, 203b) may communicate with the UTM 210 via a network user plane for identification, authentication, and authorization processes, and also for other command and control message / data exchanges. 3GPP network functions (such as SMF 283a, PCF 281a, etc.) may also have a direct or indirect (e.g., via a network exposure function (NEF 285a)) control interface with the UTM 210. The UAV may include a WTRU or UAV WTRU for cellular network communications (e.g., 3GPP, 5G, 6G, etc.). In this regard, a WTRU or UAV WTRU may refer to an embedded communication device (e.g., a 3GPP modem / module / chipset capable of 3GPP communications) that enables the UAV to communicate over a cellular network. The WTRU or UAV WTRU may include a SIM or USIM in a device for a subscription to cellular communications. The terms WTRU, UE, UAV WTRU, UAV UE, WTRU on UAV, and UE on UAV are used interchangeably in the present disclosure. Similar to the UAV, the UAV-C may include a WTRU or UAV-C WTRU for cellular network communications (e.g., 3GPP, 5G, 6G, etc.). In this regard, a WTRU or UAV-C WTRU may refer to an embedded communication device that enables the UAV-C to communicate over a cellular network (e.g., a 3GPP module capable of 3GPP communications). The terms WTRU, UE, UAV-C WTRU, UAV-C UE, WTRU on UAV-C, and UE on UAV-C are used interchangeably in the present disclosure. The UAV WTRU or UAV-C WTRU may include a SIM or USIM in an embedded communication device for a subscription to cellular communications.

[0085] Exemplary communications for a UAS are described herein. Figure 3 An exemplary type of unmanned aerial vehicle (UAV) communication 300 enabled via a cellular network is shown, which may be used in conjunction with any other embodiment described herein. Figure 3 As shown, a cellular network-connected UAS (e.g., UAV 302 and / or UAV-C 303) may engage in various types of cellular communications used to perform its mission: UAS-UTM communications, non-payload communications (ie, command and control), and payload communications.

[0086] UAS-UTM communications may refer to communications between a UAS and a UTM. It may be desirable to enable UAS-UTM communications, for example, for identification, authorization, "command and control," and law enforcement activities. It may be assumed that a user plane connection is used between the UAS and the UTM, although control plane communications may also be used between the two. UAS may refer to a UAV and / or a combination of a UAV and a UAV-C.

[0087] Non-payload communications may include command and control (C&C or C2) communications. Command and control messages and data exchanges are critical to UAV missions and safety considerations. Some C&C exchanges (e.g., position or flight data reports) may occur between the UAV and the UTM and between the UAV and its UAV-C. The UAV and UAV-C may perform C2 communications based on a PDU session established between the UAV and the UAV-C using a cellular network (e.g., 5G).

[0088] Exemplary types of C&C or C2 communications may include, but are not limited to, those disclosed in Table 1 below:

[0089] Table 1.

[0090]

[0091]

[0092]

[0093] For payload communication, a UAV in a mission may send payload data, such as real-time video or sensor data, to its UAV-C or some application server or storage in the network. Payload communication may typically be heavy in the uplink and lighter in the downlink.

[0094] 3GPP has identified use cases and potential requirements for UAS support in 3GPP specifications. Specifically, requirements for UAS remote identification and authorization have been specified in 3GPP specifications. Additional enhancements to UAS support in 3GPP may include: UAS command and control (C2) communications; unmanned aerial vehicle (UAV) navigation through a UAV controller (UAV-C) or through UAS traffic management (UTM); and / or changes of UAV-C during a flight mission.

[0095] Figure 4 An exemplary UAS interaction 400 with a network and UAS traffic management (UTM) for authorization is shown, which may be used in conjunction with any other embodiment described herein. Figure 4As shown, UAS 401 may refer to a combination of UAV 402 (e.g., drone) and UAV-C 403, and the network may include RAN 404a, 404b and CN 406a, 406b. The 3GPP system (e.g., RAN 404a, 404b and CN 406a, 406b) may provide communication capabilities between UAV 402 and UAV-C 403, which may communicate through the same or different RAN nodes (e.g., 404a, 404b) and include communicating via different PLMNs. UTM 410 may provide UAS identification and tracking, authorization, execution, and regulation of UAS operations, and also store data required to operate the UAS.

[0096] In one embodiment, the UAV and UAV-C may be paired and identified as a UAS by the 3GPP system and / or UTM. Specifically, the network may be responsible for certifying the WTRU (e.g., UAV WTRU or UAV-C WTRU) 3GPP credentials for initial network access, while the UTM is responsible for certifying the UAS credentials for operating the UAS. The network and UTM may need to be able to associate the UAV and UAV-C and identify them as a UAS during the authorization process to ensure access to command and control (C2) communication services, and grant and perform flight operations for that particular UAS (i.e., UAV and UAV-C pair).

[0097] A given UAV-C may command a fleet of UAVs and be authorized to operate in the context of multiple UASs. For example, the UAV-C may be required to perform a separate authentication and authorization process in order to be able to control another UAV (i.e., establish yet another UAS identifier with the network / UTM). Another scenario where unique UAS identifier establishment may be critical is during a change of UAV-C, where control of the UAV may be switched to a new UAV-C during flight operations (e.g., due to an emergency). The 3GPP system and UTM may need to identify the UAV and new UAV-C pair as another UAS separate from the pair comprising the UAV and the old UAV-C.

[0098] During the UAS authentication and authorization process, it may be assumed that the 3GPP system may provide one or more 3GPP identifiers (e.g., MSISDN, IMEI of the UAV WTRU / UAV-C WTRU) to the UTM, and in response, the UTM may provide the corresponding UASID to the network. The UAS ID may also be referred to as a Civil Aviation Authorization (CAA) level UAV ID. The 3GPP identifier used to identify the UAV may also be referred to as a 3GPP UAV ID. These various identifiers may be exchanged and authenticated between the WTRU (e.g., UAV WTRU, UAV-C WTRU), the network, and the UTM. The 3GPP system may enable a secure UAS pairing mechanism (e.g., to mitigate spoofing attacks on UAS identities).

[0099] In another embodiment, an airframe identifier (such as a manufacturer serial number, etc., referred to as a UAV ID) and a 3GPP modem identifier (such as an IMSI, referred to herein as a UAV WTRU ID) identified by the 3GPP system and / or UTM / USS may be combined together or bound for a UAV with a removable cellular modem. Using these combined or bound identifiers, flight authorization of the UAS may be achieved by the 3GPP system with the help of the UTM / USS.

[0100] Specifically, for ease of operation, flexibility and economic reasons, the UAV may support a removable cellular modem (e.g., WTRU or UAV WTRU). In addition, for deployment in different locations, exchangeable modems and / or exchangeable SIM / UICCs may be required. For similar reasons, UAV-C may adopt a similar architecture. For 3GPP systems, the UAV WTRU ID and UAV-C WTRU ID may remain relevant, while from the UTM / USS perspective, the basic identifiers may be the UAV ID and UAV-C ID. Therefore, there is a need for methods and devices to bind these different identities to achieve cross-references on both domains (cellular and UTM / USS) and also enable different levels of authorization to result in flight authorization and possible additional services.

[0101] The 3GPP system may enable the UAS to send different UAS data to the UTM based on different authentication and authorization levels applied to the UAS. It should be noted that, depending on regional regulations, the different authentication and authorization levels may be: initial network access authentication and authorization, UAS identity authentication, UAV flight plan authorization, additional UTM service authentication, such as flight monitoring, collision avoidance services, etc.

[0102] In another embodiment, the UAV, UAV-C and their associated WTRUs may be authenticated and / or authorized by multiple UTM / USSs. A single UAV mission may require support from more than one UTM / USS. One reason may be that the UAV flight plan spans an area that is not controlled / covered by a single UTM / USS. In this case, the UAV and its controller and their associated WTRUs need to be identified, authenticated and authorized by all relevant UTM / USSs before use of the flight and 3GPP systems is allowed.

[0103] In another embodiment, the mutual exchange of identifiers, authentication and authorization of the UAV and UAV-C may be done when they belong to different PLMNs. The 3GPP network may need to support UAVs and corresponding UAV-Cs connected to different PLMNs simultaneously.

[0104] Embodiments of UAV / UAV-C (eg, UAS) pairing and authorization are described herein.

[0105] FIG. 5A to FIG. 5C An exemplary UAS pairing and authorization scenario is shown that can be used in conjunction with any other embodiment described herein. FIG. 5A to FIG. 5C As shown, UAV 502 and UAV-C 503 may be paired as a UAS and simultaneously authenticated and authorized by UTM 510. UAS pairing during an authentication and authorization scenario may include the following phases: (1) WTRU (i.e., UAV WTRU) comes online; (2) UAV-C comes online; and (3) UAV establishes C2 communication with UAV-C.

[0106] Figure 5A An exemplary UAS pairing and authorization scenario is shown in which a UAV 502 is about to go online, which may be used in conjunction with any other embodiment described herein. With respect to the first phase (i.e., WTRU or UAV WTRU going online), at step 551, the UAV 502 may be registered on a network, such as a 5G network 506. At step 552, the UAV 502 may authenticate to the UTM 510 via the network 506 (e.g., using a control plane or user plane path). During this process, the UAV 502 may provide an identifier (e.g., UAV-C ID) of the target UAV-C 503 (if available). At step 553, the UAV 502 may only be partially authorized and await final authorization to fly. The final authorization may be conditional on the UAV-C 503 obtaining authorization to guide the UAV 502. The UAV 502 may not be authorized by the network 506 to use C2 communication services until the final flight authorization is granted. In this case, the UAV 502 may remain in an idle state, waiting to be notified (eg, asynchronously) by the UTM 510 / network 506 of the final authorization (eg, via paging, application notification, etc.).

[0107] Figure 5B 503 is about to come online, which may be used in conjunction with any other embodiment described herein. With respect to the second phase (i.e., UAV-C 503 coming online), at step 554, UAV-C 503 may be registered on network 506. At step 555, UAV-C 503 may authenticate to UTM 510 via network 506 (e.g., using a control plane or user plane path). During this process, UAV-C 503 may provide an identifier (e.g., UAV WTRU ID) of the target UAV 502 (if available). If the target UAV 502 has been temporarily authorized (e.g., Figure 5A 502 ), the UAV-C 503 may obtain authorization to operate as part of the process. In the process, the UAV-C 503 may obtain a designated UAS ID (and / or remote ID) that identifies the UAV-C 503, UAV 502 pair in the UTM 510. The authorized UAS ID may be obtained as part of the authentication and authorization exchange or via a subsequent notification (such as the notification for UAV 502 below). At step 556, the UAV 502 may receive a final authorization grant notification indicating the UAS ID and the associated UAV-C ID.

[0108] Figure 5C An exemplary UAS pairing and authorization scenario is shown in which the UAV 502 and the UAV-C 503 are establishing communications, which may be used in conjunction with any other embodiment described herein. With respect to the third phase (i.e., the UAV 502 and the UAV-C 503 establish C2 communications), at steps 557a, 557b, the UAV 502 and the UAV-C 503 may establish a C2 communication path, for example, using a PDU session establishment. The UAS ID in the UAS and optionally the ID of the peer WTRU (i.e., the UAV WTRU and / or the UAV-C WTRU) may be indicated during the connection setup. At step 558, the UAV 502 and the UAV-C 503 may exchange C2 data traffic.

[0109] It should be noted that FIG. 5A to FIG. 5C The embodiments described in the preceding paragraphs may occur in the reverse order, where the UAV-C 503 may first request authorization for UAS operations. In this case, the UAV-C 503 may perform Figure 5A The UAV 502 may perform the steps described in the first phase of Figure 5B The steps described in the second phase of Figure 5A , Figure 5B 502 and UAV-C 503 in FIG. 503). It should also be noted that in FIG. 5A to FIG. 5C The steps described in each stage in are not limited to this sequential order, but can be performed or executed in any order to achieve UAV registration / authentication, UAV-C registration / authentication and / or C2 communication establishment between UAV 502 and UAV-C 503.

[0110] Embodiments of UAV-C / UAV-assisted UAS pairing are described herein.

[0111] Figure 6 An exemplary process 600 for UAV controller (UAV-C) assisted UAS pairing is shown, which may be used in conjunction with any other embodiment described herein. Figure 6 As shown, UAS (e.g., UAV 602 and UAV-C 603) may be paired with the assistance of UAV-C during authentication and authorization of USS / UTM 610. An example of call flow steps is described here:

[0112] At steps 550a, 550b, the WTRUs (i.e., UAV WTRUs and UAV-C WTRUs) may have both registered with the network. The authorization for flight operations of the UAV 602 may be to suspend the authorization of the UAV-C 603 to fly the UAV 602. As described above, the UAV 602 may perform initial authentication and authorization steps with the network 606 and the UTM 610.

[0113] At steps 651 to 652, the UAV-C 603 may send an authentication request message to the USS / UTM 610 via the network 606. The message may include its own identity and the identity of the target UAV 602 (if available). The messages between the UAV-C 603 and the network 606 may be transmitted via the control plane (e.g., NAS signaling, such as a registration message, a service request, a general NAS transmission message, or a new NAS message) or via the user plane. In the case of user plane transmission, it is assumed that the UAV-C 603 has been authorized to establish a previous data connection (i.e., a PDU session has been established).

[0114] At step 653, the USS / UTM 610 may authenticate the UAV-C 603 based on UAS-specific credentials (e.g., UAV pilot certificate, owner certificate, etc.), and perform an authorization check based on various UAS parameters, such as: the submitted flight plan; the authenticated UAV ID provided (i.e., the flight authorization is pending this UAV-C authorization); and / or common authenticated binding parameters presented by the UAV 602 and UAV-C 603 (e.g., the same owner certificate). After successful authentication and authorization checks, the USS / UTM 610 may assign and store a unique UAS ID assigned to the UAV-C 603 and UAV 602 pair.

[0115] At step 654, the USS / / UTM 610 may send an authentication response message to the UAV-C 603 via the network 606, indicating the result of the authorization, i.e., the identities of the UAS, UAV 602, and UAV-C 603 that have been authorized to operate. When the authentication and authorization exchange with the USS / UTM 610 is completed at the application layer (e.g., on the user plane N6), the USS / UTM 610 may also send a separate notification to the network 606 via an appropriate signaling interface (e.g., via the NEF).

[0116] At step 655, the network 606 may set the authorization information locally (eg, stored in its respective UAV and UAV-C WTRU contexts).

[0117] At steps 656a, 656b, the network 606 may forward the result of the UTM authorization to the WTRUs (e.g., UAV-C 603 and UAV 602). For example, at step 656a, the network 606 may send an authorization response message including the specified UAS ID and additionally / optionally the associated UAV ID to UAV-C 603. At step 656b, the network 606 may send an authorization response message including the specified UAS ID and additionally / optionally the associated UAV-C ID to UAV 602.

[0118] At steps 657a, 657b, the UAV 602 and UAV-C 603 may store the authorization information locally (eg, in the WTRU configuration).

[0119] At step 658, the UAV 602 and the UAV-C 603 may set up a connection (e.g., a PDU session) for C2 communications. The UAV-C 603 and the UAV 602 may provide a UAS ID during the connection setup. The network 606 may use the UAS ID provided by the UAV-C 603 to distinguish between multiple C2 communications that the UAV-C 603 may use when controlling multiple UAVs. Similarly, the UAS ID provided by the UAV 602 may help the network 606 distinguish between two C2 communications that the UAV 602 may have when UAV control is transferred from one UAV-C 603 to another (as described in the change of UAV-C use case below).

[0120] At step 659, UAV 602 and UAV-C 603 may exchange C2 data traffic.

[0121] Although Figure 6The call flow steps described in FIG. 6 show the case where UAV 602 is the first entity requesting authorization for UAS operation, but it should be understood that the process is equally applicable to the reverse scenario (i.e., by exchanging Figure 6 In addition, the message names used in the call flow are examples and other signaling or user plane messages may be used to achieve the intended purpose. It should also be noted that Figure 6 The steps described in are not limited to a sequential order, but may be performed or executed in any order different from the above steps to achieve UAV-C / UAV-assisted UAS pairing.

[0122] An implementation of subscription-based UAS pairing is described herein.

[0123] Figure 7 An exemplary process 700 for subscription-based (bulk) pairing and authorization is shown, which may be used in conjunction with any other embodiment described herein. Figure 7 As shown, the UAS during authentication and authorization may be performed by the USS / UTM 710 based on the subscription information. An example of the call flow steps is described here:

[0124] At step 750a, authorization for UAS operation suspension may be registered with UAV-1 702a and UAV-2 702b. At step 750b, UAV-C 703 may register on the network and obtain authorization to operate as a UAV controller. UAV-C 703 may wish to pair with multiple UAVs.

[0125] At step 751, UAV-C 703 may send a request message to network 706 to pair with multiple UAVs by including a "UAV Fleet Control" indication or similar indication. Network 706 may have a list of UAVs (e.g., including UAVs 702a, 702b) associated with / stored with UAV-C subscriptions.

[0126] At step 752, the network 706 may forward a pairing request to the UAS server / UTM 710, the pairing request including a list of UAVs 702a, 702b to be paired retrieved from the UAV-C subscription information. The network may limit the list of UAVs 702a, 702b to be paired with those that are currently registered on the network and authorized to operate as UAVs 702a, 702b. For example, identifiers of offline UAVs may be excluded from the pairing request to the UTM 710. Alternatively or in addition, the list of UAVs associated with the UAV-C may be maintained at the UAS server instead of the 3GPP network. In this case, the network 706 may check from the UAV-C subscription information that the UAV-C 703 is authorized for "bulk pairing" of the UAVs 702a, 702b. The network 706 may include a "UAV fleet control" indication instead of a list of UAV pairing requests to the UTM 710. In yet another embodiment, the network 706 may send one or more separate pairing requests for each UAV-C, UAV pair. In this case, the remainder of the process is similar to the UAV-C / UAV-assisted pairing, but is repeated as many times as there are UAVs to be paired.

[0127] At step 753, the UAS server / UTM 710 may check that the UAV-C 703 is authorized to "bulk pair" with the UAVs 702a, 702b based on the UAV-C and UAV credentials. The UAS server / UTM 710 may pair the UAV-C 703 with each UAV 702a, 702b, assigning a UAS ID to each UAV-C, UAV pair.

[0128] At step 754, the UAS server / UTM 710 may send a pairing response to the network 706 providing a list of UAS ID, UAV ID pairs.

[0129] At step 755, the network 706 may store the pairing information locally (eg, in its respective UAV and UAV-C WTRU contexts).

[0130] At steps 756a to 756c, the network 706 may forward the results of the pairing operation to the WTRUs (i.e., the UAV-C WTRU and the UAV WTRU). For example, at step 756a, the network 706 may send a pairing response message including a list of UAS ID, UAV ID pairs to the UAV-C 703. At steps 756b and 756c, the network 706 may send a pairing notification message including a specified UAS ID and, additionally / optionally, an associated UAV-C ID to each of the UAVs 702a, 702b.

[0131] At step 757, the UAV-C 703 may store the pairing information locally (eg, in the WTRU configuration or WTRU context). The UAVs 702a, 702b may also store the pairing information locally (eg, in the WTRU configuration or WTRU context).

[0132] At steps 758 and 759, C2 communications may be established between UAV-C 703 and each UAV 702a, 702b.

[0133] It should be noted that Figure 7 The steps described in are not limited to a sequential order, but may be performed or executed in any order different from the above steps to achieve subscription-based UAS pairing.

[0134] Embodiments of UAV-C changes are described herein.

[0135] Figure 8 An exemplary process 800 for UAV-C modification is shown, which may be used in conjunction with any other embodiment described herein. Figure 8 As shown, the UAS pairing update process may be performed during the period when control of UAV 802 is taken over by a new UAV-C (e.g., UAV-C#2 803b). An example of the call flow steps is described here:

[0136] At step 850, UAV 802 may be under the control of UAV-C#1 803a. UAV-C#2 803b may wish to take over control of UAV 802 (eg, due to an emergency).

[0137] Steps 850 to 859 are similar to the UAV-C / UAV-assisted UAS pairing process described above, and therefore are not described here for the sake of brevity. In the case where the UAV control is taken over by the UTM 810, the process may start with a command from the UTM 810 (at step 854). Once the C2 communication path is established, UAV-C#2 803b may begin sending C2 commands or receiving data from the UAV 802. The UAV 802 may execute the (instantaneous) C2 commands from UAV-C#1 803a until C2 communication is established with UAV-C#2 803b, and / or until the first C2 command from UAV-C#2 803b is received, to help minimize control switching delays.

[0138] At step 860, the network 806 may send a pairing update notification to the UAV 802 and the UAV-C#1 803a to remove their respective UAV / UAV-C#1 pairing information.

[0139] At step 861, UAV 802 and UAV-C#1 803a may remove their respective UAV / UAV-C#1 pairing information (eg, delete from local configuration). Network 806 may optionally or additionally release the PDU session for C2 communication between UAV 802 and UAV-C#1 803a.

[0140] It should be noted that Figure 8 The steps described in are not limited to a sequential order, but may be performed or performed in any order different from the steps described above in order to achieve changes in UVA-C.

[0141] Implementations of UAS binding and multi-level authorization are described herein.

[0142] The complete authorization process can be completed in multiple steps, each step implementing a larger function, and the final step provides flight authorization. Generally speaking, communication-related authorization occurs within the 3GPP system, while flight-related authorization is facilitated by the 3GPP system supporting UTM / USS. In order to implement a flexible system, it is assumed that the WTRU (i.e., UAV WTRU or UAV-C WTRU) and / or UICC / SIM are independent of the UAV or UAV-C. Therefore, the WTRU ID (i.e., UAV WTRU ID or UAV-C WTRU ID) may need to be associated with the corresponding UAV ID or UAV-C ID, and the entire system (including UAV and UAV-C) may be referred to as a UAS and be assigned a UAS ID.

[0143] Fig. 9 and Fig.10 Exemplary processes 900 and 1000 of UAS multi-level authorization promoted by the 3GPP system are shown, which can be used in conjunction with any other embodiments described herein. Fig. 9 and Fig.10As shown, the UTM / USS 910 may facilitate processes 900, 1000 for multi-level identification, binding, pairing, and authorization. The UAV 902 may include a UAS client 902a and a UAV WTRU 902b. The UAV-C 903 may include a UAS client 903a and a UAV WTRU 903b. The UAS clients 902a, 902b may include entities (e.g., protocol stacks or layers) that enable the UAVWTRU 902b and the UAV-C WTRU 903b to communicate with the USS / UTM 910. For example, the UAS client 902a may provide an information element (e.g., a UAV ID) to the UAV WTRU 902b to send to the USS / UTM 910. The UAS client 902a may be part of the UAV WTRU 902b (e.g., a UAV WTRU protocol stack or layer) or a separate entity. The UAS-C client 903a may be a part of the UAV-C WTRU 903b (eg, a UAV-C WTRU protocol stack or layer) or a separate entity. Examples of call flow steps are described herein.

[0144] like Fig. 9 As shown, at step 951a, the UAV WTRU 902b may perform a registration process with the network. In addition to conventional parameters, the UAV WTRU 902b may also include WTRU capabilities in the registration request message. This may indicate to the network (e.g., AMF 906) that the UAV WTRU 902b is a UAS-capable WTRU.

[0145] At step 951b, the UAV-C WTRU 903b may perform a registration procedure with the network (e.g., AMF 906) in a manner similar to that followed by the UAV WTRU 902b. In addition to the normal parameters, the UAV-C WTRU 903b may also include WTRU capabilities in the Registration Request message. This may indicate to the network (e.g., AMF 906) that the UAV-C WTRU 903b is a UAS-capable WTRU.

[0146] It should be noted that the registration process of the UAV WTRU 902b and the UAV-C WTRU 903b may be performed in any order. The UAV WTRU 902b or the UAV-C WTRU 903b may move to the next step in the overall authorization process without waiting for the other WTRU (e.g., the UAV-C WTRU 903b or the UAV WTRU 902b, respectively) to complete its registration request process.

[0147] At the end of the process at step 952, the WTRUs (ie, UAV WTRU 902b, UAV-C WTRU 903b) may achieve Level 1 authorization (ie, initial network access authentication and authorization), which allows them to begin communicating with the UTM / USS 910 using NAS messages.

[0148] The UAV WTRU 902b that has achieved Level 1 authorization may then perform a binding to associate the UAV WTRU ID with the UAV 902 (i.e., the UAV ID) or the body ID of the UAV 902. This occurs in two steps. In the first step, the USS / UTM 910 may authenticate the UAV ID. Once the UAV ID is authenticated by the USS / UTM 910, the AMF 906 may bind the UAV ID with the UAV WTRU ID that has been authenticated in the previous WTRU registration process. Thus, the UAV ID and the UAV WTRU ID are first authenticated separately by the USS / UTM 910 and the AMF 906, respectively, and then bound together.

[0149] At step 953a, the UAV WTRU 902b may first send a registration request (e.g., a NAS request message) with the registration type set to a binding request, including the UAV ID and USSID (if applicable). Alternatively or in addition, the binding request may also be transmitted via other types of NAS messages. At this point, the AMF 906 may already know that the UAV WTRU 902b is a legitimate WTRU based on the above-mentioned Level 1 authorization, but may not know that the UAV is a legitimate UAV.

[0150] The UAV ID may be a serial number assigned by the manufacturer or a registration number assigned by the Central Aviation Authority (CAA) or its authorized representative, or other ID that uniquely identifies the UAV airframe.

[0151] When the USSID is included in the Registration Request message, it may indicate to the AMF where to forward the Binding Request. For example, the USSID may be a destination address, such as an IP address, a domain name, a fully qualified domain name (FQDN), etc. The USSID may be pre-configured in the UAV by the USS provider. In the event that the UAV 902 wants to perform flight operations involving multiple USS / UTMs, the UAV WTRU 902b may replace the USSID with a list of USSIDs. In an alternative or additional embodiment, one of the included USSIDs together with the list of USSIDs may be identified as the primary USS.

[0152] At step 953b, the AMF 906 may forward the binding request to the USS / UTM 910 including the UAV ID. The AMF 906 may also include the UAV WTRU ID in the binding request, such as a Universal Public Subscription Identifier (GPSI) (e.g., MSIDN or External Identifier), an International Mobile Equipment Identity (IMEI), a Mobile Station International Subscriber Directory Number (MSISDN), an International Mobile Subscriber Identity (IMSI), etc. If the UAV 902 provides a list of UAS service providers (USSs) without identifying a primary USS, the AMF 906 may forward the binding request message to each USS included in the USSID list. However, if the UAV 902 also includes a primary USSID as well as a USSID list, the AMF 906 may only forward the binding request message to the primary USS. In this example, the primary USS may play the role of forwarding the binding request to other USSs. Before the result of the UAV ID authentication process is finally transmitted back to the AMF 906, the binding response message is collected in the USSID list.

[0153] At step 954, the USS / UTM 910 may authenticate the UAV ID. This may involve additional signaling between the USS / UTM 910 and the UAV 902, which is handled in a similar manner to a conventional registration request.

[0154] At step 955a, the USS / UTM 910 may send a binding response message including the result of the UAV ID authentication process at the USS / UTM 910 to the AMF 906. If a primary USS is identified in the corresponding binding request in the USSID list, the binding response from the primary USS to the AMF 906 may include the aggregate results of the UAV ID authentication process at all listed USSs. However, if the initial registration request includes a USSID list without any primary USSID, the AMF 906 may need to wait for each USS to which it sent a binding request in response to the UAV ID authentication process result.

[0155] The binding response message may include an indication (eg, a code) indicating the status of the UAV ID authentication process. For example, the code or indication may include, but is not limited to, one or more of the following: ACCEPT, REJECT-USSID, etc.

[0156] At step 955b, the AMF 906 may forward the binding response within a registration accept message (e.g., a NAS response message) to the requesting UAV 902.

[0157] At step 955c, the binding process may be repeated for UAV-C 903. The detailed process performed at step 955c is similar to the UAV and UAV WTRU binding process described above and therefore will not be described here for the sake of brevity.

[0158] It should be noted that the binding process may be performed in any order by UAV 902 and UAV-C 903. At the end of the process, UAV 902 and UAV-C 903 may achieve level 2 authorization (ie, binding authorization).

[0159] The UAV WTRU 902b that has achieved bonding (with the UAV 902) or Level 2 authorization may then perform a pairing process to pair the UAV 902 with the UAV-C 903. At the end of the process, the UAV 902 and UAV-C 903 may be associated with each other, considered a pair, and assigned a UAS ID and / or Remote ID.

[0160] At step 956a, the UAV 902 may first send a registration request to the AMF 906, with the registration type set to UAS pairing request, including the identity of the UAV-C 903 with which it seeks to pair (i.e., the UAV-C ID). The UAV-C ID may be pre-configured in the UAV 902 or received from the network or USS / UTM 910. It may also include the UAV-C WTRU ID (if available). For UAVs with autonomous flight capabilities (e.g., using UTM navigation), it is contemplated that the UAV-C ID provided may refer to the USSID / UTMID (if available). Alternatively or in addition, an indication for autonomous flight, etc. may be provided. The pairing process in the case of a UAV with autonomous flight capabilities may refer to UAV-UTM pairing in the embodiments described herein.

[0161] At step 956b, the AMF 906 may forward the pairing request to the USS / UTM 910 including the UAV ID, UAV-C ID (if provided by the UAV). Alternatively or in addition, the pairing request may include a side link command and control request (SL C2 request) for direct communication between the UAV 902 and the UAV-C 903. Examples of direct communication may include, but are not limited to, proximity services (Pro Se) using licensed bands or ISM, WiFi Direct, and D2D.

[0162] At step 957, upon receiving the pairing request, the USS / UTM 910 may retrieve a stored profile of the provided UAV ID and UAV-C ID. Based on the UAV 902 and UAV-C 903 capabilities, an allowed pairing list provided by, for example, an operator, etc., the USS / UTM 910 may determine the outcome of the pairing process and / or assign a UAS ID to the UAV 902 and UAV-C 903 pair.

[0163] At step 958a, the USS / UTM 910 may send a pairing response message including the result of the pairing authorization process to the AMF 906.

[0164] The pairing response message may include a code or indication indicating the status of the UAS pairing process. This may include, but is not limited to, one or more of the following: ACCEPT, REJECT-UAV-C capabilities, REJECT-allowed pairing list, and REJECT-corresponding binding not completed. The pairing response message may also include a UAS ID, a remote ID, and / or an SL C2 response that implicitly indicates that the UAV 902 is paired with the UAV-C 903.

[0165] At step 958b, the AMF 906 may forward the pairing response within a Registration Accept message (e.g., NAS Response message) to both the requesting UAV 902 and the requested UAV-C 903. The Registration Accept message (or NAS Response message) may include the specified UAS ID and / or Remote ID. In one embodiment, the pairing request and response messages may be exchanged with the USS / UTM via the SMF using PDU Session Establishment Request and PDU Session Establishment Accept messages, respectively.

[0166] At step 958c, alternatively or additionally, a binding process is initiated by the UAV-C. It should be noted that the pairing process may be performed in any order by the UAV 902 and the UAV-C 903. The details of the pairing process initiated by the UAV-C 903 are similar to those initiated by the UAV 902, and therefore are not described herein for the sake of brevity.

[0167] At the end of this process, UAV 902 and UAV-C 903 may be paired together and as a pair, they may achieve Level 3 authorization (ie, paired authorization).

[0168] Although in Fig. 9903. Although not shown in the figure, the level 2 authorization (i.e., binding authorization) and the level 3 authorization (i.e., pairing authorization) may be combined and performed as one binding and pairing authorization from the UAV 902 and / or the UAV-C 903. For example, in the case where the UAV 902 initiates the binding and pairing process, the UAV 902 may send a NAS request message including one or more information elements required for the binding and pairing authorization. For example, the UAV 902 may send a NAS request message that may include at least one of a binding request indication, a UAV ID, a USS ID, a UAS pairing request indication, a UAV-C ID, or a UAV-WTRU ID. In the case where the UAV-C 903 initiates the binding and pairing process, the UAV-C 903 may send a similar NAS request message for binding and pairing authorization.

[0169] Next, flight authorization or Level 4 authorization may allow direct communications to be established between UAV 1002 and UAV-C 1003, enabling UAV 1002 to conduct flight.

[0170] like Fig.10 As shown, at step 1059a, to initiate the flight authorization process, UAV-C 1003 may send an uplink NAS transport message including a NAS message container to AMF 1006. The NAS message container may include one or more fields including UAS ID, flight plan, intended mission, and pilot credentials.

[0171] At step 1059b, the AMF 1006 may forward the flight authorization request message to the USS / UTM 1010 including the same elements as received from the UAV-C 1003 in the uplink NAS message.

[0172] At step 1060a, the USS / UTM 1010 may send a flight plan authorization request, including the UAS ID and the requested flight plan, to the AMF 1006. The flight plan may include waypoints from the takeoff point to the landing point, or a series of regularly spaced coordinates that the UAV 1002 intends to fly along a path from the takeoff point to the landing point, and corresponding times.

[0173] The AMF 1006 may check the requested flight plan against a series of network-related parameters, such as available network coverage along the flight path, network loading at corresponding cells along the flight plan.

[0174] At step 1060b, the AMF 1006 may respond to the USS / UTM 1010 with a flight plan authorization response including the flight plan authorization result. Some possible result codes included in the message may include, but are not limited to, ACCEPT, REJECT-network unavailable (flight plan segment), REJECT-network congestion. In the case of a result code of REJECT, the flight plan authorization response may also include suggested alternatives, including alternative routes that achieve network coverage for the entire flight plan or alternative times that avoid network congestion.

[0175] At step 1061a, the USS / UTM 1010 may send a flight authorization response including a result code to the UAV-C WTRU 1003b.

[0176] At step 1061b, the AMF 1006 may send a flight authorization response back to the requesting UAV-C 1003 using a downlink NAS transmission including a NAS message container. The flight authorization response may also be repeated to the UAV 1002. The message may include a reason code for rejecting the response. Successful completion of this process may result in the establishment of C2 communication between the UAV 1002 and the UAV-C 1003.

[0177] At step 1062, in another option (e.g., a UAV 1002 using UTM navigation), the flight authorization process may also be initiated by the UAV 1002. The details of these steps are similar to those initiated by the UAV-C 1003, so they are not described here for the sake of brevity.

[0178] At the end of this step, Level 4 authorization (ie, flight authorization) may be granted to the UAS 1002 , enabling direct C2 communications between the UAV 1002 and the UAV-C 1003 to be established, thereby facilitating UAV flight.

[0179] It should be noted that the flight authorization or Level 4 authorization is valid for the requested flight mission. At the end of the authorized flight mission, the AMF 1006 may terminate the authorization (e.g., locally or via explicit signaling between WTRUs (e.g., UAV WTRU 1002b and UAV-C WTRU 1003b)) and may require UAV 1002 and UAV-C 1003 to initiate a flight authorization process for a different flight mission.

[0180] At steps 1063a, 1063b, 1064 and 1065a, 1065b, after successfully obtaining flight authorization or level 4 authorization, the UAV-C 1003 (or UAV 1002) may initiate a request message to request authorization for further services, such as network positioning services, weather information, etc. In some cases, these additional services may be authorized by the AMF 1006 with the assistance of the UAS service provider (USS) / UTM 1010. The result code of the authorization is transmitted to the WTRU (e.g., UAV WTRU 1002b or UAV-C WTRU 1003b) via a downlink NAS transport message including a NAS message container.

[0181] Upon successful completion of this process, the UAS may obtain Level 5 authorization (Additional Services Authorization) to implement specific network services in support of flight operations.

[0182] It should be noted that Fig. 9 and Fig.10 The steps described in are not limited to a sequential order, but may be performed or executed in any order different from the above steps to achieve the above-mentioned multi-level authorization.

[0183] In some embodiments, a WTRU (e.g., a UAV WTRU or a UAV-C WTRU) may be configured to send different levels of UAS data based on different authorization levels. For example, conditional upon the WTRU having received a successful response for WTRU authentication and authorization, it may send a UAS Binding Request including at least the UAV-C ID and USSID. Conditional upon the WTRU having received a successful UAS Binding Response, it may send a UAS Pairing Request including at least the UAV ID (and optionally or additionally the UAV WTRU ID). Conditional upon the WTRU having received a successful UAS Pairing Response including the UAS ID and / or Remote ID, it may send a UAS Flight Authorization Request including at least the UAS ID or Remote ID, a flight plan, a mission profile, and pilot credentials via a UL NAS transmission. Conditional upon the flight plan being successfully authorized, the WTRU may receive configuration for C2 (and optionally payload) communications.

[0184] In other embodiments, the USSID of the UAS binding request may include a list of USSIDs (example scenarios for flight plans including more than one USS), or optionally a list of primary and secondary USSIDs. The UAS ID may be a subset or portion of the remote ID, such as from a most significant bit (MSB) to a least significant bit (LSB). The UAV-C ID may include the USSID as part of a modified name (e.g., UAV C id@USSID). Additional services may be authorized from / by the USS / UTM before or after flight authorization. The UAS entity (UAV or UAV-C) may be able to discover an available corresponding entity (e.g., UAV-C or UAV) after successful authentication and binding but before pairing.

[0185] An implementation utilizing multiple UTM / USS for identification, binding, and authorization is described herein.

[0186] Fig.11A , Fig. 11B An exemplary process 1100 for multi-level authorization across multiple UTMs and / or UAS service providers (USSs) is shown, which may be used in conjunction with any other embodiment described herein. Fig.11A , Fig. 11B As shown, multi-level UAS authorization across multiple USS / UTMs may be performed using two USS / UTMs 1110a, 1110b identified by USSID 1 and USSID 2. An example of call flow steps is described herein.

[0187] Steps 1151a, 1151b and 1152 may be performed with Fig. 9 The steps are the same or similar to those described in , and therefore are not described here for the sake of brevity.

[0188] At steps 1153a, 1153b, 1154 and 1155a, 1155b, the AMF 1106 may send a Binding Request message to both USS / UTMs 1110a, 1110b (i.e., USSID 1 and USS2). Only when the AMF 1106 receives a Binding Response from both USS / UTMs 1110a, 1110b, can it forward the complete decision along with any applicable decision codes to the UAV 1102. For example, when the UAV 1102 receives a Pairing Response message with a result code of SUCCESS from each of the requested USS / UTMs 1110a, 1110b, it may proceed to the next step (i.e., pairing).

[0189] At steps 1156a, 1156b, 1157 and 1158a to 1158d, the pairing authorization process may require separate authorization from each USS / UTM 1110a, 1110b listed in the UAV request. In this case, the AMF 1106 may send a pairing request message to one of the USS / UTMs 1110a, 1110b and, if successful, return a pairing response message with a result code of SUCCESS and the UAS ID and / or Remote ID specified by the USS / UTM. When sending subsequent pairing request messages to other requested USS / UTMs 1110a, 1110b, the AMF 1106 may include the UAS ID and / or Remote ID in the pairing request message.

[0190] At steps 1159a, 1159b, 1160a, 1160b and 1161a, 1161b, when there are multiple USS / UTMs 1110a, 1110b, the flight authorization process may require the AMF 1106 to send a flight plan request message to each of the USS / UTMs 1110a, 1110b individually and then collect responses from them collectively.

[0191] At step 1162, alternatively, the process may also be initiated by UAV 1102. The details of the steps initiated by UAV 1102 are similar to those initiated by UAV-C 1103, and therefore are not described here for the sake of brevity.

[0192] At step 1163, when UAV 1102 and UAV-C 1103 receive the flight authorization response message with the reason code set to SUCCESS, a direct link (e.g., a PDU session) for C2 communication between UAV 1102 and UAV-C 1103 may be established via SMF 1 1106a, and level 4 authorization may be established.

[0193] It should be noted that Fig.11A , Fig. 11B The steps described in are not limited to a sequential order, but may be performed or executed in any order different from the above steps to achieve the above-described multi-level authorization across multiple UTM / USSs 1110a, 1110b.

[0194] In some embodiments, when the UAVs belong to different PLMNs, the WTRU (e.g., UAV-C WTRU) may be configured to perform multi-level authorization. For example, subject to the WTRU having received a successful response for WTRU authentication and authorization, it may send a UAS Binding Request including at least the UAV-C ID and USSID. Subject to the WTRU having received a successful UAS Binding Response, it may send a UAS Pairing Request including at least the UAV ID (and optionally the UAV WTRU ID) and the PLMN ID of the network serving the UAV. Subject to the WTRU having received a successful UAS Pairing Response including the UAS ID and / or Remote ID, it may send a UAS Flight Authorization Request including at least the UAS ID or Remote ID, a flight plan, a mission profile, and pilot credentials via a UL NAS transmission. Subject to the flight plan being successfully authorized, the WTRU may receive configuration for C2 (and optionally payload) communications.

[0195] In another embodiment, the PLMN ID of the network serving the corresponding entity (e.g., UAV-C or UAV) may not be provided by the UAV or UAV-C, in which case the USS / UTM may provide the PLMN ID to the requesting 3GPP network.

[0196] Embodiments of identification, binding, pairing and authorization across PLMNs are described herein.

[0197] Fig. 12A , Fig. 12B An exemplary process 1200 for identification, binding, pairing, and authorization across public land mobile networks (PLMNs) is shown, which can be used in conjunction with any other embodiments described herein. For example, when UAV 1202 and UAV-C 1203 belong to different PLMNs, it may be necessary to support identification, binding, pairing, and multi-level authorization across multiple PLMNs. Fig. 12A , Fig. 12B The example shown refers to two AMFs 1206a, 1206b belonging to different PLMNs, where UAV 1202 and UAV-C 1203 are connected as AMF1 / SMF 1 1206a and AMF2 / SMF 2 1206b respectively. An example of call flow steps is described here.

[0198] Steps 1251a, 1251b and 1252 may be performed with Fig. 9 The steps are the same or similar to those described in , and therefore are not described here for the sake of brevity.

[0199] At steps 1253a, 1253b, 1254 and 1255a to 1255c, a binding procedure for binding the UAV ID to the UAV WTRU ID and the UAV-C ID to the UAV-WTRU ID is performed using the corresponding AMF (i.e., AMF 1 1206a or AMF 2 1206b) of the PLMN to which the UAV WTRU 1202b or UAV-C 1203 is connected. As the case may be, the UAV ID or the UAV-C ID may be authenticated by the USS / UTM 1210, and then the relevant AMF (i.e., AMF 1 1206a or AMF 2 1206b) may bind the UAV ID to the UAVWTRU ID or the UAV-C ID to the UAV-WTRU ID.

[0200] At steps 1256a, 1256b, 1257, 1258a-1258c, after the binding process is complete (i.e., Level 2 authorization is achieved), the UAV 1202 or UAV-C 1203 may initiate a pairing process to pair the two entities and identify them as a UAS. Fig. 12A , Fig. 12B In the example shown, the UAV initiates the pairing process by sending a registration request (e.g., a NAS request message) with a registration type set to UAS Pairing Request and including the requested UAV-C ID. Alternatively or in addition, the UAV 1202 may also include the UAV-C WTRU ID if it is available. AMF 1 1206a may forward the pairing request to the USS / UTM 1210 to authorize pairing of the two entities.

[0201] Once the USS / UTM 1210 authorizes the pairing of the UAV 1202 and the UAV-C 1203, a pairing response message (e.g., a NAS response message) may be sent to the AMF that made the request (i.e., AMF 1 1206a, which is responsible for the UAV 1202 in this example), and may also be sent to the AMF responsible for the corresponding entity within the UAS (i.e., AMF 2 1206b, which is responsible for the UAV-C 1203 in this example). Each of the AMFs (i.e., AMF 1 1206a and AMF 2 1206b in this example) may then forward the pairing response to the UAV 1202 and the UAV-C 1203, respectively, within a Registration Accept message.

[0202] At steps 1259a, 1259b, 1260a, 1260b, 1261a, 1261b, and 1262, a flight authorization request may be initiated by UAV 1202 or UAV-C 1203. Fig. 12A , Fig. 12BIn the example shown, UAV-C 1203 initiates the process by sending an uplink NAS transport message including a UAS flight authorization to AMF 2 1206b. This may include the proposed flight plan, pilot credentials, and mission profile. The flight authorization request may be forwarded by AMF 2 1206b to USS / UTM 1210. USS / UTM 1210 may send the flight plan as part of a flight plan authorization request message to the AMF of the PLMN responsible for the UAV (i.e., AMF 1 1206a in this example), and receive a flight plan authorization response in response.

[0203] The USS / UTM 1210 may then send a flight authorization response to both AMFs 1206a, 1206b, which are then forwarded in NAS downlink transport messages to the UAV 1202 and UAV-C 1203, respectively. This may include a reason code, such as ACCEPT, REJECT-reason, etc.

[0204] When UAV 1202 and UAV-C 1203 receive the flight authorization response message with the reason code set to SUCCESS, a direct link (e.g., PDU session) for C2 communication between UAV 1202 and UAV-C 1203 can be established via SMF 1 1206a, and Level 4 authorization can be established.

[0205] It should be noted that Fig. 12A , Fig. 12B The steps described in are not limited to a sequential order, but may be performed or executed in any order different from the above steps to achieve the above-mentioned cross-PLMN identification, binding, pairing and authorization.

[0206] In some embodiments, when the UAVs belong to different PLMNs, the WTRU (e.g., UAV-C WTRU) is configured to perform multi-level authorization. Conditional upon the WTRU having received a successful response for WTRU authentication and authorization, it may send a UAS Binding Request including at least the UAV-CID and USSID. Conditional upon the WTRU having received a successful UAS Binding Response, it may send a UAS Pairing Request including at least the UAV ID (and optionally the UAV WTRU ID) and the PLMN ID of the network serving the UAV. Conditional upon the WTRU having received a successful UAS Pairing Response including the UAS ID and / or Remote ID, it may send a UAS Flight Authorization Request including at least the UAS ID or Remote ID, a flight plan, a mission profile, and pilot credentials via a UL NAS transmission. Conditional upon the flight plan being successfully authorized, the WTRU may receive configuration for C2 (and optionally payload) communications.

[0207] In another embodiment, the PLMN ID of the network serving the corresponding entity (UAV-C or UAV) may not be provided by the UAV or UAV-C, in which case the USS / UTM may provide the PLMN ID to the requesting 3GPP network.

[0208] Fig.13 An exemplary process 1300 for binding and pairing between a UAV and a UAV-C is shown, which may be used in conjunction with any other embodiment described herein. The UAV may include a UAV WTRU for cellular communication. The UAV-C may include a UAV-C WTRU for cellular communication. At step 1305, the UAV may send a (first) NAS request message to the AMF, the message including an authentication and authorization request with a UAV WTRU identity (UAV WTRU ID) and one or more UAV WTRU capabilities for cellular communication. The NAS request message may be sent to the AMF via the UAV WTRU. The one or more UAV WTRU capabilities may include one or more indicators indicating that the UAV WTRU is a WTRU that supports UAS. At step 1310, the UAV may receive a (first) NAS response message from the AMF, the message including an authentication and authorization response indicating whether the UAV WTRU is authenticated and authorized for network access. The UAV may receive a NAS response message from the AMF via the UAV WTRU.

[0209] At step 1315, the UAV may send a (second) NAS request message to the AMF, the message including a binding request indication, a UAV identity (UAV ID) and a USS identity (USSID). Based on the USSID, the UAV ID may be carried by the AMF in a binding request message sent to the USS / UTM for binding authorization of the UAV WTRU and the UAV associated with the UAV ID. The USSID may be the destination address of the NAS request message (i.e., the address of the USS / UTM), such as an IP address, a domain name, a fully qualified domain name (FQDN), etc. The USSID may be pre-configured in the UAV by the USS provider or received from the network. The (second) NAS request message may be sent to the AMF via the UAV WTRU. At step 1320, the UAV may receive a (second) NAS response message from the AMF, the message including a binding response indication indicating whether the UAV is bound to the UAV WTRU. The binding response indication may be determined by the USS / UTM and notified to the AMF by the USS / UTM. The (second) NAS response message may be received from the AMF via the UAV WTRU.

[0210] At step 1325, if the binding response indication indicates that the UAV is successfully bound to the UAV WTUR, then at step 1330, the UAV may send a (third) NAS request message including a pairing request indication and a UAV-C ID to the AMF. The UAV-C ID may be carried in a pairing request message sent by the AMF to the USS / UTM for pairing authorization of the UAV and the UAV-C associated with the UAV-C ID. The (third) NAS request message may be a PDU session request and sent by the UAV WTRU to the SMF via the AMF. At step 1335, the UAV may receive a (third) NAS response message from the AMF, which includes a UASID indicating that the UAV is paired with the UAV-C. The NAS response message may also include a remote ID. The UAS ID may be specified by the USS / UTM when authorizing the UAV and UAV-C pair and forwarded from the USS / UTM to the AMF. The (third) NAS response message may be a PDU session response and received by the UAV WTRU from the SMF via the AMF.

[0211] At step 1340, upon receiving the UAS ID, the UAV may establish a PDU session with the UAV-C via a session management function (SMF) for command and control (C2) communications. The UAV ID may be a manufacturer-assigned serial number (or fuselage ID), and the UAV WTRU ID is GPSI, MSIDN, IMEI, MSISDN, IMSI, etc. The UAV-C ID may be a manufacturer-assigned serial number.

[0212] Although features and elements are described above in specific combinations, it will be understood by those of ordinary skill in the art that each feature or element may be used alone or in any combination with other features and elements. In addition, the methods described herein may be implemented in a computer program, software, or firmware incorporated in a computer-readable medium for execution by a computer or processor. Examples of computer-readable media include electronic signals (transmitted via a wired or wireless connection) and computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, read-only memory (ROM), random access memory (RAM), registers, cache memory, semiconductor memory devices, magnetic media (such as built-in hard disks and removable disks), magneto-optical media, and optical media (such as CD-ROM disks and digital versatile disks (DVDs)). A processor associated with software may be used to implement a radio frequency transceiver for a WTRU, UE, terminal, base station, RNC, or any host computer.

Claims

1. A method for use in an unmanned aerial vehicle (UAV) having a UAV wireless transmit / receive unit (WTRU) for cellular communications, the method comprising: Sending a first non-access stratum (NAS) request message to a network node, wherein the first NAS request message includes a registration request indication, a UAV identifier (UAV ID), and a USS identifier (USSID); receiving a first NAS response message from the network node indicating that the registration is accepted; sending a second NAS request message to the network node, the second NAS request message including pairing information for the UAV and a UAV controller (UAV-C) paired with the UAV, wherein sending the second NAS request message is performed after receiving the first NAS response message; receiving a second NAS response message from the network node indicating that the pairing is accepted; after receiving the indication that pairing is accepted, sending a request to the network node for authorization of command and control (C2) communications between the UAV and the UAV-C; as well as Based on the request for C2 authorization, a third NAS response message is received from the network node indicating a denial of authorization for C2 communications.

2. The method of claim 1, wherein the second NAS request message is a protocol data unit (PDU) session request message and the second NAS response message is a PDU session response message.

3. The method according to claim 1, further comprising: Upon receiving the second NAS response message, a PDU session with the UAV-C is established via a network node executing a session management function (SMF) for the C2 communication.

4. The method of claim 1, wherein the second NAS response message includes a remote identification (Remote ID). 5 . The method of claim 1 , wherein the second NAS request message includes a UAV-Controller (UAV-C) Identification (UAV-C ID) and the UAV-C ID is a serial number assigned by a manufacturer.

6. The method according to claim 1, wherein: the UAVID being carried in a bind request sent to an unmanned aerial system (UAS) service provider (USS) / UAS traffic management (UTM) for a bind authorization of the UAV WTRU and the UAV associated with the UAV ID based on the USSID; wherein the binding response indication is determined by the USS / UTM; and Wherein sending the second NAS request message is performed in response to receiving the binding response indication.

7. The method of claim 6, wherein the second NAS request message is sent under the condition that the UAV is bound to the UAV WTRU, and wherein the second NAS request message includes the UAV-C ID.

8. The method according to claim 6, further comprising: sending another NAS request message including an authentication and authorization request with a UAV WTRU identity (UAV WTRUID) and one or more UAV WTRU capabilities for the cellular communication to the network node; as well as Another NAS response message is received from the network node including an authentication and authorization response indicating whether the UAV WTRU is authenticated and authorized to access the cellular network.

9. The method of claim 8, wherein the UAV ID is a manufacturer-assigned serial number and the UAVWTRU ID is an International Mobile Equipment Identity (IMEI).

10. The method of claim 1, wherein the second NAS request message includes a UAV ID associated with the UAV and a UAV-C ID associated with the UAV-C, and wherein a UAS includes the UAV and the UAV-C.

11. An unmanned aerial vehicle (UAV), comprising: UAV wireless transmit / receive unit (WTRU) for cellular communications; and processor, The UAV WTRU and the processor are configured to: Sending a first non-access stratum (NAS) request message to a network node, wherein the first NAS request message includes a registration request indication, a UAV identifier (UAV ID), and a USS identifier (USSID); receiving a first NAS response message from the network node indicating that the registration is accepted; sending a second NAS request message to the network node, the second NAS request message including pairing information for the UAV and a UAV controller (UAV-C) paired with the UAV, wherein sending the second NAS request message is performed after receiving the first NAS response message; receiving a second NAS response message from the network node indicating that the pairing is accepted; After receiving an indication that the pairing is accepted, sending a request to the network node for authorization of command and control (C2) communications between the UAV and the UAV-C; and A third NAS response message is received from the network node indicating a denial of authorization for C2 communications.

12. The UAV of claim 11, wherein the second NAS request message is a protocol data unit (PDU) session request message and the second NAS response message is a PDU session response message.

13. The UAV of claim 11, wherein the UAV WTRU and the processor are further configured to establish a PDU session with the UAV-C via a network node executing a session management function (SMF) for the C2 communication upon receiving the second NAS response message.

14. The UAV of claim 11, wherein the second NAS response message includes a remote identification (remote ID).

15. The UAV of claim 11, wherein the second NAS request message includes a UAV-Controller (UAV-C) Identification (UAV-C ID) and the UAV-C ID is a serial number assigned by a manufacturer.

16. The UAV of claim 11, wherein: the UAVID being carried in a bind request sent to an unmanned aerial system (UAS) service provider (USS) / UAS traffic management (UTM) for a bind authorization of the UAV WTRU and the UAV associated with the UAV ID based on the USSID; wherein the binding response indication is determined by the USS / UTM; and Wherein sending the second NAS request message is performed in response to receiving the binding response indication.

17. The UAV of claim 16, wherein the second NAS request message is sent under the condition that the UAV is bound to the UAV WTRU, wherein the second NAS request message includes the UAV-C ID.

18. The UAV of claim 16, wherein the UAV WTRU and the processor are further configured to: sending another NAS request message including an authentication and authorization request with a UAV WTRU identity (UAV WTRUID) and one or more UAV WTRU capabilities for the cellular communication to the network node; and Another NAS response message is received from the network node including an authentication and authorization response indicating whether the UAV WTRU is authenticated and authorized to access the cellular network.

19. The UAV of claim 18, wherein the UAV ID is a manufacturer-assigned serial number and the UAVWTRU ID is an International Mobile Equipment Identity (IMEI).

20. The UAV of claim 11, wherein the second NAS request message includes a UAV ID associated with the UAV and a UAV-C ID associated with the UAV-C, and wherein a UAS includes the UAV and the UAV-C.

Citation Information

Patent Citations

  • Network registration method and device

    CN109716806A

  • Protocol design for unmanned aerial system (UAS) traffic management (UTM)

    WO2019079286A1

  • Methods of a mobile edge computing (MEC) deployment for unmanned aerial system traffic management (UTM) system applications

    WO2019148188A1

Cited By

  • Methods and devices for configuring specific cell information

    WO2026118271A1