Systems and methods for identifying subscription-based unmanned aerial vehicles (UAVs)

Abstract

A system and method for identifying subscription-based unmanned aerial vehicles (UAVs) are presented. At least one aspect is directed to a system, method, apparatus, or computer-readable medium. A wireless communication node may receive from a network a first message including one or more configuration containers. The one or more configuration containers include various information related to terminal services. The one or more configuration containers may correspond to different radio access technologies (RATs).

Description

[Technical Field]

[0001] (Technical field) The present disclosure relates generally to wireless communications, including, but not limited to, systems and methods for identifying subscription-based unmanned aerial vehicles (UAVs). [Background technology]

[0002] (background) The standards organization 3rd Generation Partnership Project (3GPP®) is currently in the process of specifying a new radio interface called 5G New Radio (5G NR), as well as the Next Generation Packet Core Network (NG-CN or NGC). 5G NR will have three main components: a 5G access network (5G-AN), a 5G core network (5GC), and user equipment (UE). To facilitate the enablement of different data services and requirements, the elements of the 5GC, also called network functions, have been simplified, some of which are software-based and some of which are hardware-based, so they can be adapted as needed. Summary of the Invention [Means for solving the problem]

[0003] (Abstract) The exemplary embodiments disclosed herein are directed to solving problems associated with one or more of the problems presented in the prior art, as well as providing additional features that will become readily apparent by reference to the following detailed description when considered in conjunction with the accompanying drawings. In accordance with various embodiments, exemplary systems, methods, devices, and computer program products are disclosed herein. However, it will be understood that these embodiments are presented by way of example, and not limitation, and that various modifications to the disclosed embodiments can be made while remaining within the scope of the present disclosure, as will be apparent to those skilled in the art upon reading this disclosure.

[0004] At least one aspect is directed to a system, method, apparatus, or computer-readable medium. A wireless communication node (e.g., a BS) may receive a first message from a network (e.g., a CN) including one or more configuration containers. The one or more configuration containers may include various information related to terminal (e.g., unmanned aerial vehicle (UAV)) services. The one or more configuration containers may correspond to different radio access technologies (RATs).

[0005] In some embodiments, the one or more configuration containers may include at least one of a Long-Term Evolution (LTE) configuration container or a New Radio (NR) configuration container. The various information may include at least one of a UAV identification configured to identify the wireless communication device, UAV subscription information configured to notify the wireless communication node that the wireless communication device is eligible to use UAV services, addresses of one or more reporting receivers from which UAV data should be collected, UAV position information configuring UAV position measurement and reporting, altitude report information related to the wireless communication device, flight path information related to the wireless communication device, or measurement information including frequency-related information for the wireless communication device.

[0006] In some embodiments, the wireless communication node may receive a second message from a wireless communication device (e.g., a UE) including a UAV-specific preamble. The wireless communication node may transmit a third message to the network including at least one of an identification of the wireless communication device or a UAV identification query indicator. The UAV identification query indicator may be configured to query the network whether the identification of the wireless communication device subscribes to the UAV service. The wireless communication node may receive a fourth message from the network confirming that the wireless communication device subscribes to the UAV service. The fourth message may include at least one of an identification of the wireless communication device, a UAV identification, UAV subscription information, or one or more configuration containers.

[0007] In some embodiments, the wireless communication node may receive a second message from the wireless communication device, which may be a radio resource control (RRC) message. The second message may include at least one of the wireless communication device identification or the UAV identification. The wireless communication node may transmit a third message to the network including at least one of the wireless communication device identification, the UAV identification, or the UAV identification inquiry indicator. The wireless communication node may receive a fourth message from the network confirming that the wireless communication device has subscribed to the UAV service. The fourth message may include at least one of the wireless communication device identification, the UAV identification, the UAV subscription information, or one or more configuration containers.

[0008] In some embodiments, in response to the network receiving a non-access stratum (NAS) message from the wireless communication device including at least one of the wireless communication device identification or the UAV identification, the wireless communication node may receive a first message from the network confirming that the wireless communication device has subscribed to the UAV service. The first message may include at least one of the wireless communication device identification, the UAV identification, the UAV subscription information, or one or more configuration containers.

[0009] In some embodiments, a network (e.g., a CN) may send a first message to a wireless communication node (e.g., a BS) that includes one or more configuration containers. The one or more configuration containers may include various information related to terminal (e.g., unmanned aerial vehicle (UAV)) services. The one or more configuration containers may correspond to different radio access technologies (RATs). The present invention provides, for example, the following. (Item 1) 1. A wireless communication method, comprising: receiving, by the wireless communication node, a first message from a network, the first message including one or more configuration containers; 1. A wireless communication method, wherein the one or more configuration containers include various information related to terminal services, and the one or more configuration containers correspond to different radio access technologies (RATs). (Item 2) Item 1, wherein the one or more configuration containers include at least one of a Long-Term Evolution (LTE) configuration container or a New Radio (NR) configuration container. (Item 3) The various information includes: a UAV identification configured to identify a wireless communication device; UAV subscription information configured to notify the wireless communication node that the wireless communication device is entitled to use the UAV service; the address of one or more reporting receivers from which UAV data should be collected, UAV location information constituting UAV position measurement and reporting; altitude reporting information relating to said wireless communication device; flight path information relating to said wireless communication device; or Measurement information including frequency-related information of the wireless communication device Item 1, the wireless communication method including at least one of the following. (Item 4) receiving, by the wireless communication node, a second message from a wireless communication device, the second message including a UAV-specific preamble; transmitting, by the wireless communication node to the network, a third message including at least one of an identification of the wireless communication device or a UAV identification inquiry indicator; Item 1. The wireless communication method according to item 1, further comprising: (Item 5) 5. The wireless communication method of claim 4, wherein the UAV inquiry indicator is configured to inquire of the network whether the identification of the wireless communication device subscribes to the UAV service. (Item 6) receiving, by the wireless communication node, from the network, a fourth message confirming that the wireless communication device has subscribed to the UAV service; 5. The wireless communication method of claim 4, wherein the fourth message includes at least one of the identification of the wireless communication device, a UAV identification, UAV subscription information, or the one or more configuration containers. (Item 7) receiving, by the wireless communication node, a second message from the wireless communication device, the second message being a Radio Resource Control (RRC) message, the second message including at least one of an identification of the wireless communication device or a UAV identification; transmitting, by the wireless communication node to the network, a third message including at least one of the identification of the wireless communication device, the UAV identification, or a UAV identification inquiry indicator; Item 1. The wireless communication method according to item 1, further comprising: (Item 8) receiving, by the wireless communication node, from the network, a fourth message confirming that the wireless communication device has subscribed to the UAV service; 8. The wireless communication method of claim 7, wherein the fourth message includes at least one of the identification of the wireless communication device, the UAV identification, UAV subscription information, or the one or more configuration containers. (Item 9) The network further includes receiving, by the wireless communication node, from the network a first message confirming that the wireless communication device has subscribed to the UAV service in response to receiving a non-access stratum (NAS) message from the wireless communication device, the first message including at least one of an identification of the wireless communication device or a UAV identification; 2. The wireless communication method of claim 1, wherein the first message includes at least one of the identification of the wireless communication device, the UAV identification, UAV subscription information, or the one or more configuration containers. (Item 10) 1. A wireless communication method, comprising: transmitting a first message over a network to a wireless communication node, the first message including one or more configuration containers; 1. A wireless communication method, wherein the one or more configuration containers include various information related to terminal services, and the one or more configuration containers correspond to different radio access technologies (RATs). (Item 11) A wireless communication device comprising a processor and a memory, the processor being configured to read a code from the memory and to implement a method according to any one of items 1 to 10. (Item 12) A computer program product comprising computer-readable program medium code stored thereon, the code, when executed by a processor, causing the processor to implement a method according to any one of items 1 to 10. [Brief explanation of the drawings]

[0010] BRIEF DESCRIPTION OF THE DRAWINGS Various exemplary embodiments of the present solution are described in detail below with reference to the following figures or drawings. The drawings are provided for illustrative purposes only and merely depict exemplary embodiments of the present solution to facilitate the reader's understanding of the present solution. Therefore, the drawings should not be considered as limiting the breadth, scope, or applicability of the present solution. It should be noted that for clarity and ease of illustration, these drawings are not necessarily drawn to scale.

[0011] [Figure 1] FIG. 1 illustrates an exemplary cellular communication network in which the techniques disclosed herein may be implemented, according to embodiments of the present disclosure.

[0012] [Figure 2] FIG. 2 illustrates a block diagram of an exemplary base station and user equipment device in accordance with some embodiments of the present disclosure.

[0013] [Figure 3] FIG. 3 illustrates a sequence diagram illustrating a preamble-based unmanned aerial vehicle (UAV) identification configuration in accordance with some embodiments of the present disclosure.

[0014] [Figure 4] FIG. 4 illustrates a sequence diagram illustrating a user equipment (UE)-based unmanned aerial vehicle (UAV) identification configuration in accordance with some embodiments of the present disclosure.

[0015] [Figure 5] FIG. 5 illustrates a sequence diagram illustrating a core network (CN)-based unmanned aerial vehicle (UAV) identification configuration in accordance with some embodiments of the present disclosure.

[0016] [Figure 6]FIG. 6 illustrates a flow diagram for identifying subscription-based unmanned aerial vehicles (UAVs) in accordance with some embodiments of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0017] (Detailed explanation) (1. Mobile Communication Technology and Environment) FIG. 1 illustrates an exemplary wireless communication network and / or system 100 in which the techniques disclosed herein may be implemented, in accordance with some embodiments of the present disclosure. In the following discussion, the wireless network 100 may be any wireless network, such as a cellar network or a narrowband Internet of things (NB-IoT) network, and is referred to herein as “network 100.” Such exemplary network 100 includes a base station 102 (hereinafter “BS 102,” also referred to as a wireless communication node) and a user equipment device 104 (hereinafter “UE 104,” also referred to as a wireless communication device) that can communicate with each other via a communication link 110 (e.g., a wireless communication channel), as well as a collection of cells 126, 130, 132, 134, 136, 138, and 140 that overlap a geographic region 101. In FIG. 1, the BS 102 and the UE 104 are contained within respective geographic boundaries of the cell 126. Each of the other cells 130, 132, 134, 136, 138, and 140 may include at least one base station operating in its assigned bandwidth to provide sufficient radio coverage to its intended users.

[0018] For example, the BS 102 may operate with an assigned channel transmission bandwidth to provide sufficient coverage to the UE 104. The BS 102 may communicate via downlink radio frames 118, and the UE 104 may communicate via uplink radio frames 124. Each radio frame 118 / 124 may be further divided into subframes 120 / 127, which may include data symbols 122 / 128. In this disclosure, the BS 102 and the UE 104 are described herein as non-limiting examples of "communication nodes," which generally can practice the methods disclosed herein. Such communication nodes may be capable of wireless and / or wired communication in accordance with various embodiments of the present solution.

[0019] 2 illustrates a block diagram of an exemplary wireless communication system 200 for transmitting and receiving wireless communication signals (e.g., OFDM / OFDMA signals) in accordance with some embodiments of the present solution. System 200 may include components and elements configured to support known or conventional operational characteristics that need not be described in detail herein. In one illustrative embodiment, system 200 can be used to communicate (e.g., transmit and receive) data symbols in a wireless communication environment, such as wireless communication environment 100 of FIG. 1, as described above.

[0020] System 200 generally includes a base station 202 (hereinafter "BS 202") and a user equipment device 204 (hereinafter "UE 204"). BS 202 includes a BS (base station) transceiver module 210, a BS antenna 212, a BS processor module 214, a BS memory module 216, and a network communication module 218, each of which is coupled and interconnected, as needed, via a data communication bus 220. UE 204 includes a UE (user equipment) transceiver module 230, a UE antenna 232, a UE memory module 234, and a UE processor module 236, each of which is coupled and interconnected, as needed, via a data communication bus 240. BS 202 communicates with UE 204 via a communication channel 250, which can be any wireless channel or other medium suitable for the transmission of data as described herein.

[0021] As will be appreciated by those skilled in the art, system 200 may further include any number of modules other than those shown in FIG. 2 . Those skilled in the art will appreciate that the various illustrative blocks, modules, circuits, and processing logic described in connection with the embodiments disclosed herein may be implemented in hardware, computer-readable software, firmware, or any practical combination thereof. To clearly illustrate this compatibility and adaptability of hardware, firmware, and software, the various illustrative components, blocks, modules, circuits, and steps have been described generally in terms of their functionality. Whether such functionality is implemented as hardware, firmware, or software may depend on the particular application and design constraints imposed on the overall system. Those familiar with the concepts described herein may implement such functionality in a manner suitable for each particular application, but such implementation decisions should not be construed as limiting the scope of the present disclosure.

[0022] According to some embodiments, the UE transceiver 230 may be referred to herein as an “uplink” transceiver 230 and includes a radio frequency (RF) transmitter and an RF receiver, each with circuitry coupled to an antenna 232. A duplexing switch (not shown) may alternatively couple the uplink transmitter or receiver to an uplink antenna in a time-duplexed manner. Similarly, according to some embodiments, the BS transceiver 210 may be referred to herein as a “downlink” transceiver 210 and includes an RF transmitter and an RF receiver, each with circuitry coupled to an antenna 212. The downlink duplexing switch may alternatively couple the downlink transmitter or receiver to the downlink antenna 212 in a time-duplexed manner. The operation of the two transceiver modules 210 and 230 may be coordinated in time such that the downlink transmitter is coupled to the downlink antenna 212 while the uplink receiver circuitry is coupled to the uplink antenna 232 for reception of transmissions over the wireless transmission link 250. Conversely, the operation of the two transceivers 210 and 230 may be coordinated in time such that the uplink transmitter is coupled to the uplink antenna 232 while the downlink receiver is coupled to the downlink antenna 212 for reception of transmissions over the wireless transmission link 250. In some embodiments, tight time synchronization is achieved with minimal guard times between changes in duplex direction.

[0023] The UE transceiver 230 and the base station transceiver 210 are configured to communicate over a wireless data communication link 250 and cooperate with RF antenna arrangements 212 / 232 suitably configured to support particular wireless communication protocols and modulation schemes. In some illustrative embodiments, the UE transceiver 210 and the base station transceiver 210 are configured to support industry standards such as Long Term Evolution (LTE) and emerging 5G standards, and the like. However, it will be understood that the present disclosure is not necessarily limited to particular standards and related protocols in application. Rather, the UE transceiver 230 and the base station transceiver 210 may be configured to support alternative or additional wireless data communication protocols, including future standards or variations thereof.

[0024] According to various embodiments, the BS 202 may be, for example, an evolved node B (eNB), a serving eNB, a target eNB, a femto station, or a pico station. In some embodiments, the UE 204 may be embodied in various types of user devices, such as a mobile phone, a smartphone, a personal digital assistant (PDA), a tablet, a laptop computer, a wearable computing device, or the like. The processor modules 214 and 236 may be implemented or realized using a general-purpose processor, an associative memory, a digital signal processor, an application-specific integrated circuit, a field-programmable gate array, any suitable programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, designed to perform the functions described herein. In this manner, the processor may be realized as a microprocessor, a controller, a microcontroller, a state machine, or the like. The processor may also be implemented as a combination of computing devices (e.g., a combination of a digital signal processor and a microprocessor, multiple microprocessors, one or more microprocessors in connection with a digital signal processor core, or any other such configuration).

[0025] Furthermore, the steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, firmware, a software module executed by processor modules 214 and 236, respectively, or any practical combination thereof. Memory modules 216 and 234 may be realized as RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. In this regard, memory module 216 may be coupled to processor module 210, and memory module 234 may be coupled to processor module 230, respectively, such that processor module 210 can read information from memory module 216 and processor module 230 can read information from memory module 216 and processor module 230 can read information from memory module 234, and processor module 210 can write information to memory module 216 and processor module 230 can write information to memory module 234, respectively. Memory modules 216 and 234 may also be integrated into their respective processor modules 210 and 230. In some embodiments, memory module 216 and memory module 234 may each include cache memory for storing temporary variables or other intermediate information during execution of instructions executed by processor module 210 and processor module 230, respectively. Memory module 216 and memory module 234 may also each include non-volatile memory for storing instructions executed by processor module 210 and processor module 230, respectively.

[0026] The network communications module 218 generally represents the hardware, software, firmware, processing logic, and / or other components of the base station 202 that enable bidirectional communications between the base station transceiver 210 and other network components and communication nodes configured to communicate with the base station 202. For example, the network communications module 218 may be configured to support Internet or WiMAX traffic. In a typical deployment, without limitation, the network communications module 218 provides an 802.3 Ethernet interface to enable the base station transceiver 210 to communicate with conventional Ethernet-based computer networks. In this manner, the network communications module 218 may include a physical interface for connection to a computer network (e.g., a Mobile Switching Center (MSC)). The terms “configured for,” “configured to,” and conjugations thereof, as used herein in reference to a specified operation or function, refer to a device, component, circuit, structure, machine, signal, etc., that is physically constructed, programmed, formatted, and / or arranged to perform the specified operation or function.

[0027] The Open Systems Interconnection (OSI) model (referred to herein as the "Open Systems Interconnection Model") is a conceptual and logical layout that defines network communications used by open systems (e.g., wireless communication devices, wireless communication nodes) to interconnect and communicate with other systems. The model is divided into seven subcomponents or layers, each of which represents a conceptual collection of services provided to the layers above and below it. The OSI model also defines logical networks by using different layer protocols to efficiently describe computer packet transfers. The OSI model may also be referred to as the seven-layer OSI model or seven-layer model. In some embodiments, the first layer may be the physical layer. In some embodiments, the second layer may be the medium access control (MAC) layer. In some embodiments, the third layer may be the radio link control (RLC) layer. In some embodiments, the fourth layer may be the packet data convergence protocol (PDCP) layer. In some embodiments, the fifth layer may be the radio resource control (RRC) layer. In some embodiments, the sixth layer may be a non-access stratum (NAS) layer or an Internet Protocol (IP) layer, and the seventh layer is some other layer.

[0028] Various exemplary embodiments of the present solution are described below with reference to the accompanying drawings to enable those skilled in the art to make and use the present solution. As will be apparent to those skilled in the art upon reading this disclosure, various changes or modifications to the examples described herein can be made without departing from the scope of the present solution. Therefore, the present solution is not limited to the exemplary embodiments and applications described and illustrated herein. In addition, the specific order or hierarchy of steps in the methods disclosed herein is merely an example approach. Based on design preferences, the specific order or hierarchy of steps in a disclosed method or process can be rearranged while remaining within the scope of the present solution. Therefore, those skilled in the art will understand that the methods and techniques disclosed herein present various steps or acts in a single order, and that the present solution is not limited to the specific steps or hierarchy presented, unless expressly specified otherwise.

[0029] 2. Systems and methods for identifying subscription-based unmanned aerial vehicles (UAVs) Subscription-based unmanned aerial vehicle (UAV) identification may be part of the UAV Work Item Description (WID) in Rel-18. Currently, new radio (NR) may not support any UAV technology. Using the procedures introduced in this disclosure, the network can check whether a UE subscribes to UAV service. If the UE subscribes to UAV service, the network can configure UAV-related measurements for the UE and send authorization information to a radio access network (RAN) node. The UE can use the UAV service. If the UAV does not subscribe to UAV service, the network can treat the UE as a general UE or based on the network implementation. Additionally, to maintain UAV service continuity when the UE moves through a heterogeneous area (e.g., an area with both LTE and NR base stations), the network can configure a UAV configuration container for the RAN node. UAV service is supported in the LTE specification. UAVs are not supported in the Rel-18 NR specification. In WID, companies may prefer to support UAV capabilities in NR and may consider LTE mechanisms as a baseline.

[0030] (Implementation example 1: UAV configuration container) This implementation example explains why a UAV configuration container can be introduced for inter-lat handover. For heterogeneous networks, inter-system handover (HO) (e.g., HO between a gNB and an eNB with a change in the core network (CN) between the access and mobility management function (AMF) and the mobility management entity (MME)) and intra-system inter-radio access technology (RAT) (e.g., HO between a gNB and an ng-eNB, where the CN can be an AMF) handover can occur during UE mobility. To maximize UAV service continuity, the same UAV-related configuration with different encoding / formats for both NR and LTE can be configured to RAN nodes in different containers. The UE can continue to use UAV-related functions even if different RATs are used between RAN nodes during HO. The UAV configuration container can be configured to the UE before or during HO.

[0031] In some embodiments, at least one of the following information may be added into both the NR and LTE containers: UAV identification (ID), UAV subscription information, reporting receiver address(es), UAV location configuration, altitude reporting configuration, flight path information configuration, or measurement configuration. The UAV ID may be used / configured to identify the UAV. The UAV subscription information may include a flag used / configured to notify the RAN node that the UE is eligible to use the UAV service. The reporting receiver address may include an IP address or URL for a UAV data collector. Different UAV data types may have the same or different destinations. The UAV location configuration may include information about UAV location measurement and reporting (e.g., UAV location accuracy requirements), what type of positioning method may be used, measurement / reporting frequency, and / or completeness requirements. The altitude reporting configuration may include criteria for when the UE may report its altitude, measurement / reporting frequency, altitude measurement accuracy, and / or completeness requirements. The flight path information configuration may include the UE's flight path history or prediction, a calculation formula, a flight path (e.g., cell ID, RAN node ID, list of coordinates), the number of points in the flight path list, a timestamp requirement, an accuracy requirement, a completeness requirement, and / or a reporting destination (e.g., IP or URL). The measurement configuration may include UE frequency-related measurement information (e.g., cell's Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ), Signal-to-Noise-and-Interference Ratio (SINR)).

[0032] (Implementation example 2: Preamble-based UAV identification) Some specific preambles may be defined by the RAN node for UEs with UAV characteristics. When an IDLE UE switches to RRC_CONNECTED and wants to apply network-supported UAV functionality, the US may use a specific preamble for initial access. If the RAN node detects initial access using the special preamble, the RAN node may mark the UE as a potential UAV and send inquiry information to the CN for further identification. Whether the UE can be treated as a UAV in the network may depend on a reply message from the CN. If the UAV information is valid, the CN may return a positive reply and may also further send the UAV configuration to the RAN node. If the UAV information is not valid, the CN commonly replies to the RAN node. Whether the UE can be treated as a normal UE may depend on the implementation.

[0033] Figure 3 shows the call flow for preamble-based UAV identification.

[0034] In step 1, the UE may be in RRC_IDLE at the start of this procedure.

[0035] In step 2, the UE may perform initial access by using a UAV-specific preamble.

[0036] In step 3, when the RAN node detects that the UE is processing the initial access procedure using a UAV-specific preamble, at least one of the following messages (UE identification information (e.g., UE ID) or UAV identification query indicator) may be included in a Next Generation Application Protocol (NGAP) message (e.g., initial UE message). The UAV identification can be used to query the CN whether the UE with the UE ID is subscribed to the UAV service. If the UE is subscribed to the UAV service, the AMF may add UAV-related information into the following NGAP message. Otherwise, the AMF may process a common NGAP procedure. In this implementation example, the UE may subscribe to the UAV function.

[0037] In step 4, when the AMF receives the above NGAP message (e.g., an initial UE message) using the above information and confirms that the UE is subscribed to the UAV service, the AMF may forward the NGAP message (e.g., an initial context setup request message) using at least one of the following information: UE identification information (e.g., a UE ID), UAV identification information (e.g., a UAV ID), UAV subscription information (e.g., a flag used to notify the RAN node that the UE is eligible to use the UAV service), or a UAV configuration container (e.g., an LTE configuration container or an NR configuration container).

[0038] In step 5, the RAN node may receive the above NGAP message and may send a reply message (e.g., an initial context setup response) to the AMF.

[0039] (Implementation example 3: UE-based UAV identification) UAV identification subscription information (e.g., UAV ID) may be configured to a UE subscribing to a UAV service. The UE may add the subscription information (e.g., UAV ID) to an RRC message and activate the UAV function. When the RAN node receives the information, the RAN node may forward the received ID to the CN for further checking. If the UAV identification is valid, the CN may return a positive reply and may also further send the UAV configuration to the RAN node. If the UAV information is not valid, the CN may reply commonly to the RAN node. The UE may still be treated as a normal UE.

[0040] In step 1, the UE may send a radio resource control (RRC) configuration request message to a RAN node.

[0041] In step 2, the RAN node may send an RRC setup message to the UE.

[0042] In step 3, the UE may subscribe to the UAV service. The UE may add at least one of the following information into an RRC message (e.g., RRC Setup Complete) and forward the RRC message to the RAN node. At least one of the information may include UE identification information (e.g., UE ID) or UAV identification information (e.g., UAV ID).

[0043] In step 4, the RAN node may receive the UAV information and forward the UAV information to the AMF via an NGAP message (e.g., an Initial UE message). At least one of the following information may be included in the NGAP message: UE identification information (e.g., a UE ID), UAV identification information (e.g., a UAV ID), or a UAV identification query indicator. The UAV identification query indicator is used to query the CN whether a UE with a UE ID has subscribed to the UAV service.

[0044] In step 5, the AMF may receive the UAV subscription information and check whether the UE is eligible to activate the UAV service. The AMF may send an NGAP message (e.g., an Initial Context Setup Request message) to the RAN node. For eligible UEs, at least one of the following information may be added to the message: UE identification information (e.g., UE ID), UAV identification information (e.g., UAV ID), UAV subscription information (e.g., a flag used to notify the RAN node that the UE is eligible to use the UAV service), and a UAV configuration container (e.g., an LTE configuration container or an NR configuration container).

[0045] In step 6, when the RAN node receives the above information, the RAN node may know that the UE can use the UAV service, and the RAN node may send a reply NGAP message (e.g., an Initial Context Setup Response message) to the AMF.

[0046] (Implementation example 4: CN-based UAV identification) In step 1, the UE may send a non-access stratum (NAS) message to the AMF. At least one of the following information may be added to the NAS message: UE identification information (e.g., UE ID), UAV identification information (e.g., UAV ID).

[0047] In step 2, when the AMF receives the NAS message using the above information, the AMF may check whether the UAV subscription information is valid. If yes, the AMF may send an NGAP message to the RAN node. At least one of the following information may be added to the NGAP message: UE identification information (e.g., UE ID), UAV identification information (e.g., UAV ID), UAV subscription information (e.g., a flag used to notify the RAN node that the UE is eligible to use the UAV service), and a UAV configuration container (e.g., an LTE configuration container or an NR configuration container).

[0048] In step 3, when the RAN node receives the above information, the RAN node may know that the UE can use the UAV function, and the RAN node may send a reply NGAP message (e.g., ACK) to the AMF.

[0049] It should be understood that one or more features from the above implementations are not exclusive to a particular implementation, but can be combined in any manner (e.g., in any priority and / or order, simultaneously or otherwise).

[0050] FIG. 6 illustrates a flow diagram of a method 600 for identifying subscription-based unmanned aerial vehicles (UAVs). Method 600 may be implemented using any one or more of the components and devices detailed herein in conjunction with FIGS. 1-2. In summary, method 600 may be performed by a wireless communication node in some embodiments. Additional, fewer, or different operations may be performed in method 600 according to embodiments. At least one aspect of the operations may be directed to a system, a method, an apparatus, or a computer-readable medium.

[0051] A wireless communication node (e.g., a BS) may receive a first message from a network (e.g., a CN) that includes one or more configuration containers. The one or more configuration containers may include various information related to terminal (e.g., unmanned aerial vehicle (UAV)) services. The one or more configuration containers may correspond to different radio access technologies (RATs).

[0052] In some embodiments, the one or more configuration containers may include at least one of a Long-Term Evolution (LTE) configuration container or a New Radio (NR) configuration container. The various information may include at least one of a UAV identification configured to identify the wireless communication device, UAV subscription information configured to notify the wireless communication node that the wireless communication device is eligible to use UAV services, addresses of one or more reporting receivers from which UAV data should be collected, UAV position information configuring UAV position measurement and reporting, altitude report information related to the wireless communication device, flight path information related to the wireless communication device, or measurement information including frequency-related information of the wireless communication information.

[0053] In some embodiments, the wireless communication node may receive a second message from a wireless communication device (e.g., a UE) including a UAV-specific preamble. The wireless communication node may transmit a third message to the network including at least one of an identification of the wireless communication device or a UAV identification query indicator. The UAV identification query indicator may be configured to query the network whether the identification of the wireless communication device subscribes to the UAV service. The wireless communication node may receive a fourth message from the network confirming that the wireless communication device subscribes to the UAV service. The fourth message may include at least one of an identification of the wireless communication device, a UAV identification, UAV subscription information, or one or more configuration containers.

[0054] In some embodiments, the wireless communication node may receive a second message from the wireless communication device, which may be a radio resource control (RRC) message. The second message may include at least one of the wireless communication device identification or the UAV identification. The wireless communication node may transmit a third message to the network including at least one of the wireless communication device identification, the UAV identification, or the UAV identification inquiry indicator. The wireless communication node may receive a fourth message from the network confirming that the wireless communication device has subscribed to the UAV service. The fourth message may include at least one of the wireless communication device identification, the UAV identification, the UAV subscription information, or one or more configuration containers.

[0055] In some embodiments, in response to the network receiving a non-access stratum (NAS) message from the wireless communication device including at least one of the wireless communication device identification or the UAV identification, the wireless communication node may receive a first message from the network confirming that the wireless communication device has subscribed to the UAV service. The first message may include at least one of the wireless communication device identification, the UAV identification, the UAV subscription information, or one or more configuration containers.

[0056] In some embodiments, a network (e.g., a CN) may send a first message to a wireless communication node (e.g., a BS) that includes one or more configuration containers. The one or more configuration containers may include various information related to terminal (e.g., unmanned aerial vehicle (UAV)) services. The one or more configuration containers may correspond to different radio access technologies (RATs).

[0057] While various embodiments of the present solution have been described above, it should be understood that they have been presented by way of example only, and not limitation. Similarly, various diagrams may depict example structures or configurations, which are provided to enable those skilled in the art to understand the example properties and functionality of the present solution. However, such skilled artisans will understand that the solution is not limited to the example structures or configurations shown, but can be implemented using a variety of alternative structures or configurations. Additionally, as will be understood by those skilled in the art, one or more features of one embodiment can be combined with one or more features of the other embodiments described herein. Therefore, the breadth and scope of the present disclosure should not be limited by any of the example embodiments described above.

[0058] It will also be understood that any reference to elements herein using designations such as "first," "second," etc. generally does not limit the quantity or order of those elements. Instead, these designations may be used herein as a convenient means of distinguishing between two or more elements or instances of an element. Thus, reference to a first and a second element does not imply that only two elements are used or that the first element must precede the second element in some manner.

[0059] Additionally, those skilled in the art will understand that information and signals may be represented using any of a variety of different technologies and techniques. For example, the data, instructions, commands, information, signals, bits, and symbols that may be referenced in the above description may be represented by, for example, voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0060] Those skilled in the art will further appreciate that any of the various illustrative logical blocks, modules, processors, means, circuits, methods, and functions described in connection with the aspects disclosed herein can be implemented by electrical hardware (e.g., digital implementations, analog implementations, or a combination of the two), firmware, various forms of program or design code incorporating instructions (which may be referred to herein for convenience as “software” or “software modules”), or any combination of these techniques. To clearly illustrate this interchangeability of hardware, firmware, and software, the various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware, firmware, or software, or a combination of these techniques, depends on the particular application and design constraints imposed on the overall system. Those skilled in the art may implement the described functions in various ways for each particular application, and such implementation decisions do not cause a departure from the scope of the present disclosure.

[0061] Furthermore, those skilled in the art will understand that the various illustrative logic blocks, modules, devices, components, and circuits described herein can be implemented in or performed by integrated circuits (ICs), which can include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, or any combination thereof. The logic blocks, modules, and circuits can further include an antenna and / or a transceiver for communicating with various components within a network or device. A general-purpose processor can be a microprocessor, but in the alternative, the processor can be any conventional processor, controller, or state machine. A processor can also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other suitable configuration for performing the functions described herein).

[0062] If implemented in software, the functions can be stored as one or more instructions or code on a computer-readable medium. Thus, the steps of a method or algorithm disclosed herein can be implemented as software stored on a computer-readable medium. Computer-readable media includes both computer storage media and communication media, including any medium that can enable a computer program or code to be transferred from one place to another. A storage medium can be any available medium that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store desired program code in the form of instructions or data structures and that can be accessed by a computer.

[0063] In this document, the term "module," as used herein, refers to software, firmware, hardware, and any combination of these elements for performing the relevant functions described herein. Additionally, for purposes of discussion, various modules are described as separate modules; however, as will be apparent to one skilled in the art, two or more modules may be combined to form a single module that performs the relevant functions according to embodiments of the present solution.

[0064] Additionally, memory or other storage, as well as communication components, may be used in embodiments of the solution. It will be understood that, for purposes of clarity, the above description describes embodiments of the solution with reference to different functional units and processors. However, it will be apparent that any suitable distribution of functionality between different functional units, processing logic elements, or domains may be used without detracting from the solution. For example, functionality illustrated as being performed by separate processing logic elements or controllers may be performed by the same processing logic element or controller. References to specific functional units therefore do not refer to a strict logical or physical structure or organization, but merely to means suitable for providing the described functionality.

[0065] Various modifications to the embodiments described in this disclosure will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the scope of the present disclosure. Thus, the present disclosure is not intended to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the novel features and principles disclosed herein, as set forth in the following claims.

Claims

1. 1. A wireless communication method, comprising: receiving, by a wireless communication node, a first message from a network, the first message including a plurality of configuration containers; Including, the plurality of configuration containers contain information related to terminal services, the plurality of configuration containers corresponding to different radio access technologies (RATs); The wireless communication method, wherein the information includes unmanned aerial vehicle (UAV) subscription information configured to notify the wireless communication node that the wireless communication device is entitled to use UAV services.

2. 2. The wireless communication method of claim 1, wherein the plurality of configuration containers include at least one of a Long-Term Evolution (LTE) configuration container or a New Radio (NR) configuration container.

3. The network receives a non-access stratum (NAS) message from a wireless communication device, the NAS message including an unmanned aerial vehicle (UAV) identification; The method of claim 1 , wherein the first message indicates that the wireless communication device is subscribing to a UAV service.

4. 1. A wireless communication method, comprising: a network transmitting a first message to a wireless communication node, the first message including a plurality of configuration containers; Including, the plurality of configuration containers include various information related to terminal services, the plurality of configuration containers corresponding to different radio access technologies (RATs); The wireless communication method, wherein the information includes unmanned aerial vehicle (UAV) subscription information configured to notify the wireless communication node that the wireless communication device is entitled to use UAV services.

5. The wireless communication method of claim 4, wherein the plurality of configuration containers include at least one of a Long-Term Evolution (LTE) configuration container or a New Radio (NR) configuration container.

6. The method of claim 1, further comprising receiving, from a wireless communication device, a non-access stratum (NAS) message including an unmanned aerial vehicle (UAV) identification; The method of claim 4 , wherein the first message indicates that the wireless communication device is subscribing to a UAV service.

7. A wireless communication node comprising at least one processor, the at least one processor comprising: receiving a first message from a network via a receiver, the first message including a plurality of configuration containers; configured to: the plurality of configuration containers contain information related to terminal services, the plurality of configuration containers corresponding to different radio access technologies (RATs); The wireless communication node, wherein the information includes unmanned aerial vehicle (UAV) subscription information configured to notify the wireless communication node that a wireless communication device is eligible to use UAV services.

8. The wireless communication node of claim 7, wherein the plurality of configuration containers include at least one of a Long-Term Evolution (LTE) configuration container or a New Radio (NR) configuration container.

9. The network comprising: a wireless communication device configured to receive a non-access stratum (NAS) message including an unmanned aerial vehicle (UAV) identification; The wireless communication node of claim 7 , wherein the first message indicates that the wireless communication device is subscribing to a UAV service.

10. A network node comprising at least one processor, the at least one processor comprising: transmitting, via a transmitter, a first message to a wireless communication node, the first message including a plurality of configuration containers; configured to: the plurality of configuration containers include various information related to terminal services, the plurality of configuration containers corresponding to different radio access technologies (RATs); The network node, wherein the information includes unmanned aerial vehicle (UAV) subscription information configured to notify the wireless communication node that a wireless communication device is eligible to use UAV services.

11. The network node of claim 10, wherein the plurality of configuration containers include at least one of a Long-Term Evolution (LTE) configuration container or a New Radio (NR) configuration container.

12. The at least one processor is configured to receive, from a wireless communication device, a non-access stratum (NAS) message including an unmanned aerial vehicle (UAV) identification; The network node of claim 10 , wherein the first message indicates that the wireless communication device is subscribing to a UAV service.

13. A non-transitory computer-readable program medium, the non-transitory computer-readable program medium having code stored thereon, the code, when executed by at least one processor, causing the at least one processor to implement the method of claim 1.

14. A non-transitory computer readable program medium, the non-transitory computer readable program medium having code stored thereon, the code, when executed by at least one processor, causing the at least one processor to implement the method of claim 2.

15. A non-transitory computer readable program medium, the non-transitory computer readable program medium having code stored thereon, the code, when executed by at least one processor, causing the at least one processor to implement the method of claim 3.

16. A non-transitory computer readable program medium, the non-transitory computer readable program medium having code stored thereon, the code, when executed by at least one processor, causing the at least one processor to implement the method of claim 4.

17. A non-transitory computer readable program medium, the non-transitory computer readable program medium having code stored thereon, the code, when executed by at least one processor, causing the at least one processor to implement the method of claim 5.

18. A non-transitory computer readable program medium, the non-transitory computer readable program medium having code stored thereon, the code, when executed by at least one processor, causing the at least one processor to implement the method of claim 6.

Images