System and method for identifying a subscription-based unmanned aerial vehicle (UAV)

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 Art

[0002] (Background) The standardization body, the Third Generation Partnership Project (3GPP®), is currently in the process of defining a new radio interface called 5G New Radio (5G NR), as well as a 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 a user equipment (UE). To facilitate enabling different data services and requirements, the elements of the 5GC, also called network functions, are simplified and some of them are software-based and some are hardware-based so that they can be adapted as needed.

Summary of the Invention

Means for Solving the Problems

[0003] (Abstract) The exemplary embodiments disclosed herein are directed to solving one or more of the problems presented in the prior art, as well as providing additional features that will be readily apparent by reference to the following detailed description when considered in conjunction with the accompanying drawings. According to various embodiments, exemplary systems, methods, devices, and computer program products are disclosed herein. However, it will be apparent to those skilled in the art who have read this disclosure 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.

[0004] At least one aspect is directed to the following system, method, apparatus, or computer-readable medium. A wireless communication node (e.g., BS) may receive a first message including one or more configuration containers from a network (e.g., CN). The one or more configuration containers may include various information related to a terminal (e.g., an unmanned aerial vehicle (UAV)) service. 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 UAV identification configured to identify a wireless communication device, UAV subscription information configured to notify a wireless communication node that the wireless communication device is eligible to use a UAV service, addresses of one or more report receivers where 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 device.

[0006] In some embodiments, the wireless communication node may receive a second message including a UAV-specific preamble from a wireless communication device (e.g., UE). The wireless communication node may transmit a third message including at least one of an identification of the wireless communication device or a UAV identification query indicator to the network. The UAV identification query indicator may be configured to query the network as to whether the identification of the wireless communication device subscribes to a UAV service. The wireless communication node may receive a fourth message from the network confirming that the wireless communication device subscribes to a 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, from the wireless communication device, a second message that can be a Radio Resource Control (RRC) message. The second message may include at least one of an identification of the wireless communication device or a UAV identification. The wireless communication node may transmit, to the network, a third message including at least one of an identification of the wireless communication device, a UAV identification, or a UAV identification query indicator. The wireless communication node may receive, from the network, a fourth message for verifying that the wireless communication device is subscribed to a 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.

[0008] In some embodiments, in response to the network receiving, from the wireless communication device, a non-access stratum (NAS) message including at least one of an identification of the wireless communication device or a UAV identification, the wireless communication node may receive, from the network, a first message for verifying that the wireless communication device is subscribed to a UAV service. The first 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.

[0009] In some embodiments, the network (e.g., CN) may transmit, to the wireless communication node (e.g., BS), a first message including one or more configuration containers. The one or more configuration containers may include various information related to a terminal (e.g., an unmanned aerial vehicle (UAV)) service. The one or more configuration containers may correspond to different radio access technologies (RATs).

Brief Description 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 width, 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

[0012]

Figure 2

[0013]

Figure 3

[0014]

Figure 4

[0015]

Figure 5

[0016]

Figure 6

DETAILED DESCRIPTION OF THE INVENTION

[0017] (Detailed Description) (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, according to some embodiments of the present disclosure. In the following discussion, the wireless network 100 may be any wireless network such as a cellular network or a narrowband Internet of things (NB-IoT) network, and is referred to herein as the "network 100". Such an exemplary network 100 includes a base station 102 (hereinafter "BS102", also referred to as a wireless communication node) and a user equipment device 104 (hereinafter "UE104", 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), and a set of cells 126, 130, 132, 134, 136, 138, and 140 that overlap a geographic area 101. In FIG. 1, BS102 and UE104 are contained within the respective geographic boundaries of cell 126. Each of the other cells 130, 132, 134, 136, 138, and 140 may include at least one base station operating at its allocated bandwidth to provide sufficient radio coverage to its intended users.

[0018] For example, BS102 may operate at an allocated channel transmission bandwidth to provide sufficient coverage to UE104. BS102 may communicate via a downlink radio frame 118, and UE104 may communicate via an uplink radio frame 124. Each radio frame 118 / 124 may be further divided into subframes 120 / 127 that may include data symbols 122 / 128. In the present disclosure, BS102 and UE104 are described herein as non-limiting examples of "communication nodes", and generally, it can practice the methods disclosed herein. Such communication nodes may be capable of wireless and / or wired communication according to various embodiments of the present solution.

[0019] FIG. 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 exemplary 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 “BS202”) and a user equipment device 204 (hereinafter “UE204”). BS202 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, and each module is coupled and interconnected to each other via a data communication bus 220 as needed. UE204 includes a UE (user equipment) transceiver module 230, a UE antenna 232, a UE memory module 234, and a UE processor module 236, and each module is coupled and interconnected to each other via a data communication bus 240 as needed. BS202 communicates with UE204 via a communication channel 250 that can be any wireless channel or other medium suitable for transmission of data as described herein.

[0021] As will be understood 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 understand that the various example blocks, modules, circuits, and processing logics 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 interchangeability and compatibility of hardware, firmware, and software, the various example components, blocks, modules, circuits, and steps are generally described in terms of their functionality. Whether such functionality is implemented as hardware, firmware, or software can depend on the particular application and design constraints imposed on the overall system. Those skilled in the art of 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 an RF transmitter and an RF receiver, each having circuitry coupled to an antenna 232. A duplex switch (not shown) may alternatively couple the uplink transmitter or receiver to the uplink antenna in a time-division duplexing 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 having circuitry coupled to an antenna 212. The downlink duplex switch may alternatively couple the downlink transmitter or receiver to the downlink antenna 212 in a time-division duplexing manner. By being able to coordinate the operations of the two transceiver modules 210 and 230 in time, the uplink receiving circuit is coupled to the uplink antenna 232 for receiving transmissions through the wireless transmission link 250 at the same time that the downlink transmitter is coupled to the downlink antenna 212. Conversely, by being able to coordinate the operations of the two transceivers 210 and 230 in time, the downlink receiver is coupled to the downlink antenna 212 for receiving transmissions through the wireless transmission link 250 at the same time that the uplink transmitter is coupled to the uplink antenna 232. In some embodiments, tight time synchronization is performed with a minimum guard time between changes in the duplex direction.

[0023] The UE transceiver 230 and the base station transceiver 210 are configured to communicate via a wireless data communication link 250 and cooperate with RF antenna arrangements 212 / 232 that are suitably configured to support a particular wireless communication protocol and modulation scheme. In some exemplary 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 is understood that the present disclosure is not necessarily limited to the particular standards and associated protocols in an 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 variants thereof.

[0024] According to various embodiments, BS202 can be, for example, an evolved node B (eNB), serving eNB, target eNB, femto station or pico station. In some embodiments, UE204 can be embodied in various types of user devices such as mobile phones, smart phones, personal digital assistants (PDAs), tablets, laptop computers, wearable computing devices, and the like. Processor modules 214 and 236 can be implemented or realized using a general-purpose processor, associative memory, digital signal processor, application specific integrated circuit, field programmable gate array, any suitable programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, which are designated to perform the functions described herein. In this approach, the processor can be realized as a microprocessor, controller, microcontroller, state machine, or the like. The processor can also be implemented as a combination of computing devices (e.g., a digital signal processor and a microprocessor, multiple microprocessors, one or more microprocessors connected to a digital signal processor core, or any other such combination of configurations).

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

[0026] The network communication module 218 generally represents hardware, software, firmware, processing logic, and / or other components of the base station 202 that enable bidirectional communication 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 communication module 218 may be configured to support Internet or WiMAX traffic. In a typical deployment, without limitation, the network communication module 218 provides an 802.3 Ethernet (registered trademark) interface so that the base station transceiver 210 can communicate with a conventional Ethernet (registered trademark)-based computer network. In this approach, the network communication module 218 may include a physical interface for connection to a computer network (e.g., a Mobile Switching Center (MSC)). The terms "configured to" and "configured to do" and their conjugations, as used herein with respect 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 as the "Open System Interconnection Model" in this specification) is a conceptual and logical layout that defines network communication used by systems (such as wireless communication devices, wireless communication nodes) that are open to interconnection and communication with other systems. The model is divided into seven sub-components or layers, each of which represents a conceptual set of services provided to layers above and below. The OSI model also defines a logical network by using different layer protocols and efficiently describes computer packet transfer. The OSI model can also be referred to as the seven-layer OSI model or the seven-layer model. In some embodiments, the first layer can be a physical layer. In some embodiments, the second layer can be a Media Access Control (MAC) layer. In some embodiments, the third layer can be a Radio Link Control (RLC) layer. In some embodiments, the fourth layer can be a Packet Data Convergence Protocol (PDCP) layer. In some embodiments, the fifth layer can be a Radio Resource Control (RRC) layer. In some embodiments, the sixth layer can be a Non-Access Stratum (NAS) layer or an Internet Protocol (IP) layer, and the seventh layer is other layers.

[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 variations 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. Additionally, the particular order or hierarchy of steps in the methods disclosed herein is merely an exemplary approach. Based on design preferences, the particular order or hierarchy of steps of the disclosed methods or processes 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 particular steps or hierarchies presented unless explicitly stated otherwise.

[0029] (2. System and Method for Identifying Subscription-Based Unmanned Aerial Vehicles (UAVs)) Subscription-based unmanned aerial vehicle (UAV) identification can be part of the UAV work item description (WID) in Rel-18. Currently, new radio (NR) does not have to support any UAV technology. By using the procedures introduced in this disclosure, the network can check whether a UE is subscribed to a UAV service. If the UE is subscribed to a UAV service, the network can configure UAV-related measurements for the UE and send approval information to a radio access network (RAN) node. The UE can use the UAV service. If the UAV is not subscribed to a UAV service, the network can treat the UE as a general UE or based on the network implementation. In addition, to maintain the continuity of the UAV service when the UE is moving in a heterogeneous area (e.g., an area with both LTE-based stations and NR-based stations), the network can configure a UAV configuration container for the RAN node. The UAV service is supported in the LTE specification. The UAV is not supported in the Rel-18 NR specification. In the WID, an enterprise may prefer to support the UAV nature in NR and may consider the LTE mechanism as a baseline.

[0030] (Implementation Example 1: UAV Configuration Container) This implementation example explains the reasons why a UAV configuration container can be introduced for inter-rat handover. For a heterogeneous network, inter-system handover (HO) (e.g., HO between gNB and eNB with a change in the core network (CN) between access and mobility management function (AMF) and mobility management entity (MME)), as well as intra-system inter-radio access technology (RAT) (e.g., HO between gNB and ng-eNB. CN can be AMF) handover can be performed during the movement of the UE. To maximize the continuity of the UAV service, the same UAV-related configuration with different encodings / formats for both NR and LTE can be configured to RAN nodes in different containers. The UE can continue to use the UAV-related functions even if the RATs used between RAN nodes during HO are different. 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 (UAV identification (ID), UAV subscription information, address(es) of the (one or more) report receivers, UAV position configuration, altitude reporting configuration, flight path information configuration, or measurement configuration) can be added into both the NR and LTE containers. The UAV ID can be used / configured to identify the UAV. The UAV subscription information can include a flag used / configured to notify the RAN node that the UE is eligible to use the UAV service. The address of the report receiver can include an IP address or a URL for the UAV data collector. Different types of UAV data can have the same destination or different destinations. The UAV position configuration can include information about UAV position measurement and reporting (e.g., exact requirements for the UAV's position), what types of positioning methods can be used, the frequency of measurement / reporting, and / or integrity requirements. The altitude reporting configuration can include criteria regarding when the UE can report its altitude, the frequency of measurement / reporting, the accuracy of altitude measurement, and / or integrity requirements. The flight path information configuration can include the UE's flight path history or prediction, calculation formula, flight path (e.g., cell ID, RAN node ID, list of coordinates), the number of points in the flight path list, timestamp requirements, accuracy requirements, integrity requirements, and / or the destination to report to (e.g., IP or URL). The measurement configuration can include UE frequency-related measurement information (e.g., cell 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) Several specific preambles can be defined by the RAN node for UEs with UAV characteristics. If an IDLE UE switches to RRC_CONNECTED and wishes to apply the network-supported UAV function, the UE can use a specific preamble for initial access. When the RAN node detects initial access using a special preamble, the RAN node can mark the UE as a potential UAV and send query information to the CN for further identification. Whether the UE can be treated as a UAV in the network may depend on the reply message from the CN. If the UAV information is valid, the CN can return an affirmative reply and may also send the UAV configuration to the RAN node. If the UAV information is not valid, the CN replies commonly to the RAN node. Whether the UE can be treated as a normal UE may depend on the implementation.

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

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

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

[0036] In step 3, when the RAN node detects that the UE is processing the initial access procedure using the UAV specific preamble, at least one of the following messages (UE identification information (e.g., UE ID) or UAV identification query indicator) may be contained in the next generation application protocol (NGAP) message (e.g., initial UE message). UAV identification can be used to query the CN whether a UE with a 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 messages. Otherwise, the AMF may process the common NGAP procedures. 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., initial UE message) using the above information and confirms that the UE is subscribed to the UAV service, the AMF may transfer an NGAP message (e.g., initial context setup request message) using at least one of the following information (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), or UAV configuration container (e.g., LTE configuration container or NR configuration container)).

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

[0039] (Implementation Example 3: UE-based UAV Identification) UAV identification subscription information (e.g., UAV ID) can be configured to the UE subscribed to the UAV service. The UE can add the subscription information (e.g., UAV ID) into the RRC message and can activate the UAV function. When the RAN node receives the information, the RAN node can transfer the received ID to the CN for further checking. If the UAV identification is valid, the CN can return an affirmative reply and can further send the UAV configuration to the RAN node. If the UAV information is not valid, the CN can return a common reply to the RAN node. The UE can be treated as a normal UE as it is.

[0040] In step 1, the UE can send a Radio Resource Control (RRC) setup request message to the RAN node.

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

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

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

[0044] In step 5, the AMF may receive 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 an eligible UE, at least one of the following information (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), UAV configuration container (e.g., an LTE configuration container or an NR configuration container)) may be added to the message.

[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. 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 (UE identification information (e.g., UE ID), UAV identification information (e.g., UAV ID)) may be added to the NAS message.

[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 (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), UAV configuration container (e.g., an LTE configuration container or an NR configuration container)) may be added to the NGAP message.

[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. The RAN node may send a reply NGAP message (e.g., ACK) to the AMF.

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

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

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

[0052] In some embodiments, 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. Various information may include at least one of UAV identification configured to identify a wireless communication device, UAV subscription information configured to notify a wireless communication node that the wireless communication device is eligible to use UAV services, addresses of one or more report receivers where UAV data should be collected, UAV position information that constitutes UAV position measurement and reporting, altitude report information related to the wireless communication device, flight path information related to the wireless communication device, or frequency-related information of wireless communication information.

[0053] In some embodiments, the wireless communication node may receive a second message including a UAV-specific preamble from a wireless communication device (e.g., UE). The wireless communication node may send a third message including at least one of an identification of the wireless communication device or a UAV identification query indicator to the network. The UAV identification query indicator may be configured to query the network as to whether the identification of the wireless communication device subscribes to UAV services. The wireless communication node may receive a fourth message from the network confirming that the wireless communication device subscribes to UAV services. 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, from the wireless communication device, a second message that can be a radio resource control (RRC) message. The second message may include at least one of an identification of the wireless communication device or a UAV identification. The wireless communication node may send, to the network, a third message that includes at least one of an identification of the wireless communication device, a UAV identification, or a UAV identification query indicator. The wireless communication node may receive, from the network, a fourth message for verifying that the wireless communication device is subscribed to a 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.

[0055] In some embodiments, in response to the network receiving, from the wireless communication device, a non-access stratum (NAS) message that includes at least one of an identification of the wireless communication device or a UAV identification, the wireless communication node may receive, from the network, a first message for verifying that the wireless communication device is subscribed to a UAV service. The first 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.

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

[0057] Although 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 by way of limitation. Similarly, the various figures may depict exemplary structures or configurations, which are provided to enable those skilled in the art to understand the exemplary nature and functionality of the present solution. However, such those skilled in the art will understand that the solution is not limited to the exemplary structures or configurations illustrated, but can be implemented using various alternative structures or configurations. In addition, as will be understood by those skilled in the art, one or more properties of one embodiment can be combined with one or more properties of other embodiments described herein. Therefore, the breadth and scope of the present disclosure should not be limited by any of the exemplary embodiments described above.

[0058] It should also be understood that any reference in this specification to elements using designations such as "first", "second", etc., generally does not limit the quantity or order of those elements. Rather, these designations can be used in this specification as a convenient means of distinguishing between two or more elements or instances of an element. Therefore, references to a first and a second element do not mean that only two elements are used, or that the first element must precede the second element in some manner.

[0059] In addition, those skilled in the art will understand that information and signals can 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 can be represented, for example, by voltage, current, electromagnetic waves, magnetic fields or magnetic force particles, optical fields or optical 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 implementation, analog implementation, 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 the interchangeability of hardware, firmware, and software, various illustrative components, blocks, modules, circuits, and steps are generally described above in terms of their functionality. Whether such functionality is implemented as hardware, firmware, 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 can implement the described functionality in various ways for each particular application, but such implementation decisions do not depart from the scope of the present disclosure.

[0061] Furthermore, those skilled in the art will understand that the various example logical blocks, modules, devices, components, and circuits described herein can be implemented within, or performed by, an integrated circuit (IC) that includes 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 logical blocks, modules, and circuits can further include antennas and / or transceivers to communicate with various components within a network or within a device. The general-purpose processor can be a microprocessor, but in the alternative, the processor can be any conventional processor, controller, or state machine. The 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] When implemented in software, the functions can be stored as one or more instructions or code on a computer-readable medium. Therefore, the steps of the methods or algorithms disclosed herein can be implemented as software stored on a computer-readable medium. The computer-readable medium includes both computer storage media and communication media including any medium that can be enabled to transfer a computer program or code from one location to another. The storage media can be any available media 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 the desired program code in the form of instructions or data structures and that can be accessed by a computer.

[0063] As used herein, the term "module" as used herein refers to software, firmware, hardware, and any combination of these elements for performing the related functions described herein. Additionally, for purposes of discussion, various modules are described as separate modules, however, as will be apparent to those skilled in the art, two or more modules can be combined to form a single module that performs the related functions in accordance with embodiments of the present solution.

[0064] In addition, memory or other storage, as well as communication components, may be used in embodiments of the present solution. For the purpose of clarity, it will be understood that the above description describes embodiments of the present 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 departing from the present solution. For example, the functionality illustrated as being performed by separate processing logic elements or controllers may be performed by the same processing logic elements or controllers. Therefore, the reference to a particular functional unit is not an indication of a strict logical or physical structure or organization, but rather a mere reference to a means suitable for providing the described functionality.

[0065] Various modifications to the embodiments described in the present disclosure will be readily apparent to those skilled in the art, and the general principles defined herein can be applied to other embodiments without departing from the scope of the present disclosure. Therefore, while the present disclosure is not intended to be limited to the embodiments shown herein, the broadest scope consistent with the novel features and principles disclosed herein is given as described in the following claims.

Claims

1. A wireless communication method, comprising: receiving, by a wireless communication node, a first message including one or more configuration containers from a network, 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).

2. The wireless communication method according to claim 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.

3. The various information includes: 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 eligible to use the UAV service, addresses of one or more reporting receivers where UAV data should be collected, UAV position information constituting UAV position measurement and reporting, altitude reporting 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 device. The wireless communication method according to claim 1, including at least one of the above.

4. further comprising: receiving, by the wireless communication node, a second message including a UAV-specific preamble from a wireless communication device; and transmitting, by the wireless communication node, a third message including at least one of an identification of the wireless communication device or a UAV identification query indicator to the network. The wireless communication method according to claim 1.

5. The wireless communication method according to claim 4, wherein the UAV query indicator is configured to query the network whether the identification of the wireless communication device subscribes to the UAV service.

6. further comprising: receiving, by the wireless communication node, a fourth message from the network to confirm that the wireless communication device subscribes to the UAV service, wherein the fourth message includes at least one of the identification of the wireless communication device, UAV identification, UAV subscription information, or the one or more configuration containers.

7. Receiving, by the wireless communication node, from a wireless communication device, a second message that is a radio resource control (RRC) message, where the second message includes 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 query indicator; The wireless communication method according to claim 1, further comprising.

8. Further comprising receiving, by the wireless communication node from the network, a fourth message for confirming that the wireless communication device has subscribed to the UAV service, The wireless communication method according to 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.

9. The network receives, from a wireless communication device, a non-access stratum (NAS) message including at least one of an identification of the wireless communication device or a UAV identification, and in response, the wireless communication node receives, from the network, a first message for confirming that the wireless communication device has subscribed to the UAV service, The wireless communication method according to 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.

10. A wireless communication method, comprising: Transmitting, by a network to a wireless communication node, a first message including one or more configuration containers, 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). A wireless communication method.

11. A wireless communication apparatus comprising a processor and a memory, wherein the processor reads code from the memory and is configured to implement the method according to any one of claims 1 to 10. A wireless communication apparatus.

12. A computer program product, comprising computer-readable program media code stored thereon, which, when executed by a processor, causes the processor to implement the method according to any one of claims 1 to 10.

Images