Patent Description:
The following abbreviations are herewith defined, at least some of which are referred to within the following description: Third Generation Partnership Project ("3GPP"), Positive-Acknowledgment ("ACK" or "Ack"), Access Stratum ("AS"), Downlink ("DL"), Evolved Node B ("eNB"), Equipment Identity Register ("EIR"), Frequency Division Multiple Access ("FDMA"), Home Subscriber Server ("HSS"), Long Term Evolution ("LTE"), Multiple Access ("MA"), Mobility Management Entity ("MME"), Mobile Equipment ("ME"), Non-access Stratum ("NAS"), Next Generation Node B ("gNB"), Orthogonal Frequency Division Multiplexing ("OFDM"), PDN GateWay ("PGW"), Radio Resource Control ("RRC"), Access Network ("AN"), Radio Access Network ("RAN"), Radio Link Failure ("RLF"), Service Capability Exposure Function ("SCEF"), Single Carrier Frequency Division Multiple Access ("SC-FDMA"), Serving GateWay ("SGW"), User Entity/Equipment (Mobile Terminal) ("UE"), Uplink ("UL"), Worldwide Interoperability for Microwave Access ("WiMAX"), Core Access and Mobility Management Function ("AMF"), Network Exposure Function ("NEF"), Session Management Function ("SMF"), Unified Data Management ("UDM"), User Plane Function ("UPF"), Application Function ("AF"), Datacenter (DC), and Air-borne Assistance Information (ABI).

There has been increasing interest in covering the aerial vehicles such as drones with cellular networks. The use cases of commercial drones are growing very rapidly and include package delivery, search-and-rescue, monitoring of critical infrastructure, wildlife conservation, flying cameras, and surveillance. All of these use cases could see rapid growth and more will emerge in coming years. Many of these emerging use cases could benefit from connecting drones to the cellular network as a UE. LTE is well positioned to serve aerial vehicles such as drones. In fact, there have been an increasing number of field-trials involving the use of LTE networks to provide connectivity to drones. It is predicted that a rapid and vast growth in the drone industry will bring new promising business opportunities for LTE operators. To address this growing market demand, a new study item (SI) called the "Study on Enhanced LTE Support for Aerial Vehicles" has been approved by 3GPP TSG RAN#<NUM> [<NUM>]. In this, the following enhancements were proposed:.

Interference mitigation solutions for improving system-level performance in both UL and DL;.

Solutions to detect whether UL signal from an air-borne UE increases interference in multiple neighboring cells and whether an air-borne UE incurs interference from multiple cells;.

Identification of an air-borne UE that does not have proper certification for connecting to the cellular network while air-borne;.

Handover: Identify if enhancements in terms of cell selection and handover efficiency as well as robustness in handover signaling can be achieved;.

Positioning: If time allows as the 2nd priority, assess the achievable accuracy with existing positioning techniques and identify potential enhancements.

The solutions related with drone UE are mainly discussed in RAN <NUM> now. The following contributions have been submitted to RAN <NUM> meeting.

However, there are as yet no discussions related with drone UE in SA2. The solution proposed in this disclosure is mainly related to a network capability exposure feature (TS <NUM>. <NUM>) and an attach procedure (TS <NUM>).

The above references are identified by the RAN group from the radio aspect. However, there exist other problematic issues which also need to be solved.

R2-<NUM> describes methods relating to identification of aerial vehicles. R2-<NUM> describes methods relating to identification of air-borne drones. <CIT> describes systems and methods for UAV safety.

Accordingly, embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a "circuit", "module" or "system". Furthermore, embodiments may take the form of a program product embodied in one or more computer readable storage devices storing machine-readable code, computer readable code, and/or program code, referred to hereafter as "code".

Certain functional units described in this specification may be labeled "modules", in order to more particularly emphasize their implementation independence.

This operational data may be collected as a single data set, or may be distributed over different locations including over different computer readable storage devices.

The storage device may be, for example, but need not necessarily be, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.

A non-exhaustive list of more specific examples of the storage device would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, random access memory ("RAM"), read-only memory ("ROM"), erasable programmable read-only memory ("EPROM" or Flash memory), portable compact disc read-only memory ("CD-ROM"), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer-readable storage medium may be any tangible medium that can contain or store a program for use by or in connection with an instruction execution system, apparatus, or device.

The code may be executed entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the very last scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network ("LAN") or a wide area network ("WAN"), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).

The terms "including", "comprising", "having", and variations thereof mean "including but not limited to", unless expressly specified otherwise. The terms "a", "an", and "the" also refer to "one or more" unless expressly specified otherwise.

This code may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the schematic flowchart diagrams and/or schematic block diagrams for the block or blocks.

The code may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the code executed on the computer or other programmable apparatus provides processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

<FIG> depicts an embodiment of a wireless communication system <NUM>. In one embodiment, the wireless communication system <NUM> includes mobile units <NUM>, and base units <NUM>, a core network <NUM> and an aerial server <NUM>. A location platform <NUM> is also included in the wireless communication system <NUM>. Even though a specific number of mobile units <NUM> and base units <NUM> are depicted in <FIG>, one skilled in the art will recognize that any number of mobile units <NUM> and base units <NUM> may be included in the wireless communication system <NUM>. Similarly, even though only one core network <NUM> and only one aerial server <NUM> are depicted in <FIG>, one skilled in the art will recognize that more core networks <NUM> and more aerial servers <NUM> could be included in the wireless communication system <NUM>.

In one embodiment, the mobile units <NUM> may include aerial vehicles such as drones or the like. Examples of use cases of drones include package delivery, search-and-rescue, monitoring of critical infrastructure, wildlife conservation, flying cameras, and surveillance. The mobile units <NUM> may be referred to as remote units, subscriber units, mobiles, mobile stations, users, terminals, mobile terminals, UEs, subscriber stations, user terminals, a device, or by other terminology used in the art. The mobile units <NUM> may communicate wirelessly with one or more of the base units <NUM>.

The base units <NUM> may be distributed over a geographic region. In certain embodiments, a base unit <NUM> may also be referred to as an access point, an access terminal, a base, a base station, a Node-B, an eNB, a gNB, a Home Node-B, a relay node, a device, or by any other terminology used in the art. The base units <NUM> connect to the core network <NUM>, which may be coupled to other networks, like the Internet and public switched telephone networks, among other networks, such as the aerial server.

In one implementation, the wireless communication system <NUM> is compliant with the LTE of the 3GPP protocol. More generally, however, the wireless communication system <NUM> may implement some other open or proprietary communication protocol.

The base units <NUM> may serve a number of mobile units <NUM> within a serving area, for example, a cell or a cell sector via a wireless communication link. The base units <NUM> may communicate directly with one or more of the remote units <NUM> via communication signals. Generally, the base units <NUM> transmit downlink ("DL") communication signals to serve the remote units <NUM> in the time, frequency, and/or spatial domain.

In one embodiment, the core network <NUM> is an evolved packet core ("EPC"). In another embodiment, the core network <NUM> may be a <NUM> core network. The core network <NUM> may be coupled to an external server such as the aerial server <NUM>.

The core network <NUM> includes several network elements. As depicted, the core network <NUM> includes a SCEF <NUM>, a HSS <NUM>, and a MME <NUM>. Although a specific number of MME <NUM> is depicted in <FIG>, one skilled in the art will recognize that any number of MMEs <NUM> may be included in the core network <NUM>. Although SCEF <NUM>, HSS <NUM> and MME <NUM> are described in the embodiment, a person skilled in the art will recognize that, in <NUM> network, a Network Exposure Function ("NEF") is equivalent to SCEF, a Unified Data Management ("UDM") is equivalent to HSS, and a Core Access and Mobility Management Function ("AMF") is equivalent to MME. Incidentally, in <NUM> network, a Session Management Function ("SMF") is equivalent to SGW, a User Plane Function ("UPF") is equivalent to PGW, an Application Function is equivalent to an external server.

The MME <NUM> is a control plane network element that handles signaling related to mobility and security for the mobile units <NUM>. The MME may be referred to as a control node. The MME <NUM> is a termination point for a NAS connection of the remote unit <NUM> to the core network <NUM>. The MME <NUM> may stop serving a mobile unit <NUM> due to various reasons. The HSS <NUM> is a server that is used for storing subscription information. The SCEF <NUM> is an apparatus that connects the core network <NUM> with external servers such as the aerial server <NUM>, among others.

The aerial server <NUM> is a server that holds information related to mobile units <NUM>, and in particular, related to aerial vehicles. The aerial server <NUM> holds subscription information configuration that will be explained in detail with reference to <FIG>. The SCEF <NUM> authenticates the aerial server <NUM>.

The location platform <NUM> may be connected to the MME <NUM> or the base units <NUM>. The detailed description of the location platform <NUM> will be discussed later with reference to <FIG>.

<FIG> illustrates a subscription information configuration <NUM> that is communicated from the aerial server <NUM> to the core network <NUM>, according to embodiments of the disclosure. A preferred embodiment of the subscription information configuration <NUM> includes an AS identity <NUM>, a UE identity <NUM>, mobility restrictions <NUM> and air-borne assistance information (ABI) <NUM>. A timer information <NUM> is optionally included in the subscription information configuration <NUM>.

The AS identity <NUM> is an identity of an aerial server <NUM>. Although <FIG> only shows one aerial server <NUM>, a person skilled in the art will recognize that any numbers of aerial servers <NUM> may be included in the wireless communication system <NUM>. Each aerial server <NUM> has its unique AS identity <NUM>.

The UE identity <NUM> is an identity of a mobile unit <NUM>. One aerial server <NUM> may hold subscription information configuration <NUM> for any numbers of mobile units <NUM>. Each mobile unit <NUM> has its unique UE identity <NUM>.

The mobility restrictions <NUM> serve as a restriction to the behavior of the mobile unit <NUM>. For example, an aerial vehicle, which is a preferred embodiment of the mobile unit <NUM>, may fly much higher than the height for which a base unit is allowed to provide connection. Therefore, a restriction on the height of the aerial vehicle is necessary.

A preferred embodiment of the mobility restrictions <NUM> includes altitude restriction <NUM>, speed restriction <NUM>, and etc. The altitude restriction <NUM> defines the maximum altitude of the mobile unit <NUM>. If the mobile unit <NUM> flies beyond the altitude restriction, the mobile unit <NUM> may not be able to communicate with the base unit <NUM> or the mobile unit <NUM> will not be allowed to communicate with the base unit <NUM>. The speed restriction <NUM> defines the maximum speed of the mobile unit <NUM>. If the mobile unit <NUM> flies beyond the speed restriction, the mobile unit <NUM> may not be able to communicate with the base unit <NUM> or the mobile unit <NUM> will not be allowed to communicate with the base unit <NUM>.

The air-borne assistance information (ABI) <NUM> serves as information that may help the base unit configure its parameters to provide a suitable service. The ABI <NUM> can also be seen as an indication of whether or not a mobile unit <NUM> can be used as an aerial vehicle. A preferred embodiment of the air-borne assistance information <NUM> includes an expected altitude range <NUM>, a mobility pattern <NUM>, path information <NUM> and etc. The air-borne assistance information <NUM> may be set by the aerial server <NUM>. Alternatively, the air-borne assistance information <NUM> may be predetermined by the core network <NUM>.

The expected altitude range <NUM> is a preferred height range by which the mobile unit <NUM> flies. The mobility pattern <NUM> is a parameter or a set of parameters that may be used by the core network to characterize and optimize the UE mobility. The mobility pattern <NUM> can be used by the MME or AMF to optimize mobility support provided to the mobile unit, for example, tracking / registration area list allocation. For example, the mobility pattern <NUM> may be an expected speed range, which is a preferred speed range by which the mobile unit <NUM> flies. The path information <NUM> refers to the path along which the mobile unit <NUM> flies. In one embodiment, the air-borne assistance information (ABI) <NUM> may include at least one of the expected altitude range <NUM>, the mobility pattern <NUM> and the path information <NUM>. In another embodiment, the air-borne assistance information (ABI) <NUM> may include other information. In yet another embodiment, the air-borne assistance information (ABI) <NUM> may be empty. In other words, an empty air-borne assistance information (ABI) <NUM> is also a valid ABI.

In some embodiments, the mobility restrictions <NUM> can be combined into the air-borne assistance information (ABI) <NUM>. That is, the air-borne assistance information (ABI) <NUM> may include all of the altitude restriction <NUM>, the speed restriction <NUM>, the expected altitude range <NUM>, the mobility pattern <NUM> and the path information <NUM>. In this embodiment, the air-borne assistance information (ABI) <NUM> is a container that contains information or parameters related to aerial vehicles. Needless to say, the air-borne assistance information (ABI) <NUM> may include other parameters related to aerial vehicles.

The timer information <NUM> may be optionally included in the subscription information configuration <NUM>. The timer information <NUM> may define the expiration time of the subscription information configuration <NUM>. For example, the timer information <NUM> may be duration of time such as one week, one day, several hours (e.g. <NUM> hours) or the like. The timer information <NUM> indicates that after the duration of time (e.g. <NUM> hours), the subscription information configuration <NUM> becomes invalid.

<FIG> depicts a method (<NUM>) for subscription information configuration, according to embodiments of the disclosure. In some embodiments, the method (<NUM>) is performed by apparatuses, such as the aerial server <NUM>, the SCEF <NUM>, and HSS <NUM>. In certain embodiments, the method (<NUM>) may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.

The method (<NUM>) starts and transmits (<NUM>) a subscription information configuration message from the aerial server <NUM> to the SCEF <NUM>. The transmission of the subscription information configuration message may be initiated by the aerial server <NUM>. Alternatively, the transmission of the subscription information configuration message may be in response to a request by the HSS <NUM>.

As depicted in <FIG>, the subscription information configuration includes the AS identity <NUM>, the UE identity <NUM>, the mobility restrictions <NUM> and the air-borne assistance information (ABI) <NUM> and optionally the timer information <NUM>. A person skilled in the art may recognize that the subscription information configuration message may not include all of these contents. For example, the mobility restrictions <NUM> may not be included. In other words, a subscription information configuration message including only the air-borne assistance information (ABI) <NUM> may be transmitted to the SCEF <NUM>. As described above, the air-borne assistance information (ABI) <NUM> may also be empty.

The method further includes authenticating (<NUM>) the subscription information configuration message at the SCEF <NUM>. The SCEF <NUM> judges whether the AS identity <NUM> and the UE identity <NUM> are valid. If this judgment is successful, the SCEF <NUM> sends (<NUM>) the subscription information configuration message to the HSS <NUM>. If this judgment is not successful, the method goes to step <NUM> that will be discussed later.

The method (<NUM>) further includes receiving (<NUM>) the subscription information configuration message at the HSS <NUM>. If the receiving is successful, the HSS <NUM> stores (<NUM>) the subscription information configuration message. If the receiving is not successful, the method goes to step <NUM> that will be discussed later.

In step <NUM>, the HSS <NUM> stores the subscription information configuration message. If an existing subscription information configuration message for a particular mobile unit <NUM> has been stored at the HSS <NUM>, the HSS may replace the existing subscription information configuration message with the newly received subscription information configuration message.

As described above, the mobility restrictions <NUM> may be combined into the air-borne assistance information (ABI) <NUM>. That is, the air-borne assistance information (ABI) <NUM> may include the altitude restriction <NUM>, the speed restriction <NUM>, the expected altitude range <NUM>, the mobility pattern <NUM>, the path information <NUM> and etc. All of the altitude restriction <NUM>, the speed restriction <NUM>, the expected altitude range <NUM>, the mobility pattern <NUM> and the path information <NUM> are optional parameters. That is, all of the altitude restriction <NUM>, the speed restriction <NUM>, the expected altitude range <NUM>, the mobility pattern <NUM> and the path information <NUM> may be empty, and therefore, the air-borne assistance information (ABI) <NUM> may be empty. An empty air-borne assistance information (ABI) <NUM> is still valid air-borne assistance information (ABI) <NUM>.

The method further includes sending (<NUM>) a response from the HSS <NUM> to the SCEF <NUM>. If the receiving of the subscription information configuration message fails at step <NUM>, a response including a cause value to indicate the failure of the receiving is sent to the SCEF <NUM>. If the receiving of the subscription information configuration message is successful at step <NUM>, after the storing of the subscription information configuration message or the replacement of the existing subscription information configuration message is performed at the step <NUM>, a response including a cause value to indicate the success of the receiving is sent to the SCEF <NUM>.

The method further includes transmitting (<NUM>) a response from the SCEF <NUM> to the aerial server <NUM>. If the authentication fails in step <NUM>, a response containing a cause value to indicate the failure of the authentication is sent to the aerial server <NUM>. If a response including the cause value to indicate the failure or the success of the receiving is received from the HSS <NUM>, the same response is sent from the SCEF <NUM> to the aerial server <NUM>.

<FIG> depicts another method (<NUM>) for subscription information configuration, according to embodiments of the disclosure. The method (<NUM>) differs from the method (<NUM>) mainly in the steps <NUM>, <NUM> and <NUM>. The other steps <NUM>, <NUM>, <NUM>, <NUM> and <NUM> are the same as the steps <NUM>, <NUM>, <NUM>, <NUM> and <NUM>.

In step <NUM> of <FIG>, SCEF <NUM> sends the subscription information configuration message to the HSS <NUM>. On the other hand, according to the embodiment depicted in <FIG>, the SCEF <NUM> converts <NUM> the subscription information configuration <NUM> into a format that is easily understandable by the base unit <NUM>.

In some embodiments, only a part of the subscription information configuration <NUM> is converted.

For example, the path information <NUM> may be converted to a base unit list or a cell list. The list preferably contains an access order. The path information transmitted from the aerial server <NUM> may include a particular route that a mobile unit <NUM> will travel.

In step <NUM>, the SCEF <NUM> sends the converted subscription information configuration to the HSS <NUM>. In step <NUM>, the HSS <NUM> receives the converted subscription information configuration. In step <NUM>, the HSS <NUM> stores the converted subscription information configuration. Alternatively, the HSS <NUM> may replace the existing converted subscription information configuration with the newly received converted subscription information configuration.

<FIG> illustrates an attach procedure <NUM>, according to embodiments of the disclosure.

In step <NUM>, a mobile unit <NUM> sends an Attach Request to the MME <NUM>.

In step <NUM>, the HSS <NUM> authenticates the mobile unit <NUM> and sets up NAS security to activate integrity protection and NAS ciphering. If the authentication succeeds, the HSS <NUM> sends the subscription information configuration <NUM> as subscription information of the mobile unit <NUM> to the MME <NUM>. As illustrated in <FIG>, the subscription information configuration <NUM> includes the air-borne assistance information (ABI) <NUM> and the mobility restrictions <NUM>. The mobility restrictions <NUM> may not be included in the subscription information configuration <NUM>. Further, the air-borne assistance information (ABI) <NUM> included in the subscription information configuration <NUM> may be empty. In the condition that the mobility restrictions <NUM> are combined into the air-borne assistance information (ABI) <NUM>, the combined air-borne assistance information (ABI) <NUM> may also be empty. As explained earlier, the subscription information configuration <NUM> may preferably be the converted subscription information configuration that is easily understandable by the base unit.

In step <NUM>, an ME Identity (IMEISV) shall be retrieved from the mobile unit <NUM>. The ME identity shall be transferred encrypted. In order to minimize signaling delays, the retrieval of the ME Identity may be performed at the same time as the NAS security setup in step <NUM>. The MME <NUM> may send the ME Identity Check Request (ME Identity, IMSI) to an EIR. The EIR shall respond with ME Identity Check Ack (Result). Depending upon the Result, the MME <NUM> decides whether to continue with this attach procedure or to reject the mobile unit.

In step <NUM>, the MME sends the Create session request to SGW.

In step <NUM>, the SGW sends Create session request to PGW.

In step <NUM>, the PGW sends Create session response to SGW.

In step <NUM>, the SGW sends Create session response to MME.

In step <NUM>, the MME sends Initial Context Setup Request or Downlink NAS transport with Attach Accept to the base unit. This message includes UE temp identity (GUTI) and the subscription information configuration <NUM> (or the converted subscription information configuration). The base unit may use the subscription information configuration <NUM> (or the converted subscription information configuration) to set specific parameters.

In step <NUM>, the base unit sends RRC Connection Reconfiguration to the mobile unit. This message includes UE temp identity and the subscription information configuration <NUM> (or the converted subscription information configuration).

In the attach procedure, the subscription information configuration is received at the base unit. The base unit may set its parameters according to the subscription information configuration <NUM>. As described earlier, the subscription information configuration <NUM> includes at least the air-borne assistance information (ABI) <NUM>. The air-borne assistance information (ABI) <NUM> may include at least one of the expected altitude range <NUM>, the mobility pattern <NUM> and the path information <NUM>. Alternatively, the air-borne assistance information (ABI) <NUM> may be empty. In the condition that the mobility restrictions <NUM> are combined into the air-borne assistance information (ABI) <NUM>, the combined air-borne assistance information (ABI) <NUM> may include at least one of the altitude restriction <NUM>, the speed restriction <NUM>, the expected altitude range <NUM>, the mobility pattern <NUM> and the path information <NUM>, or may be empty. In the condition that the air-borne assistance information (ABI) <NUM> of a particular mobile unit, which either is empty or includes at least one of the expected altitude range <NUM>, the mobility pattern <NUM> and the path information <NUM> (or includes at least one of the altitude restriction <NUM>, the speed restriction <NUM>, the expected altitude range <NUM>, the mobility pattern <NUM> and the path information <NUM>), is received and stored at the base unit <NUM>, the particular mobile unit is regarded as being a registered aerial vehicle. On the other hand, if no air-borne assistance information (ABI) <NUM> of a certain mobile unit is received at the base unit, the certain mobile unit will be regarded as being an unregistered aerial vehicle. Preferably, the subscription information configuration is received at the mobile unit. The mobile unit may adjust its own flying parameters according to the subscription information configuration.

<FIG> illustrates a detailed embodiment of the step <NUM> of <FIG>. In <FIG>, the communications of step <NUM> are performed among the mobile unit <NUM>, the MME <NUM> and the HSS <NUM>. <FIG> describes in detail the communications performed between the MME <NUM> and the HSS <NUM>. In step <NUM>, the MME <NUM> sends a request to the HSS <NUM> for the subscription information configuration <NUM>. As discussed earlier with reference to <FIG>, if the authentication by the HSS <NUM> succeeds, the HSS <NUM> sends the subscription information configuration <NUM> as subscription information of the mobile unit <NUM> to the MME <NUM>.

However, there may exist a situation in which a valid subscription information configuration <NUM> is unavailable at the HSS <NUM>. For example, the HSS may not receive any subscription information configuration <NUM>. Alternatively, the timer information <NUM> of the subscription information configuration <NUM> may indicate that the duration of time for the subscription information configuration <NUM> has expired in the HSS <NUM>. In this condition, since no valid subscription information configuration <NUM> is stored at the HSS <NUM>, the HSS <NUM> is unable to authenticate the UE as an aerial UE and unable to send the aerial usage related subscription information configuration <NUM> to the MME <NUM>.

In the condition that no valid subscription information configuration <NUM> is stored at the HSS <NUM>, the HSS <NUM>, in step <NUM>, sends a request to the aerial server <NUM> via the SCEF <NUM> to request for the subscription information configuration <NUM>. In response, the aerial server <NUM>, in step <NUM>, sends a response message including the subscription information configuration <NUM> to the HSS <NUM>. The step <NUM> may be implemented by the method <NUM> shown in <FIG> or the method <NUM> shown in <FIG>. In step <NUM>, the HSS <NUM> sends the subscription information configuration <NUM> as part of subscription information of the mobile unit <NUM> to the MME <NUM>.

The timer information <NUM> has been discussed as a part of the subscription information configuration <NUM>. The timer information <NUM> defines the expiration time of the subscription information configuration <NUM> in the HSS <NUM>. Therefore, according to an embodiment, the subscription information configuration <NUM> or the converted subscription information configuration contains the timer information <NUM> when it is stored at the HSS <NUM>. The subscription information configuration <NUM> or the converted subscription information configuration sent to the base unit <NUM>, as shown in step <NUM> of <FIG>, may not contain the timer information <NUM>. Needless to say, the subscription information configuration <NUM> or the converted subscription information configuration sent to the mobile unit <NUM>, as shown in step <NUM> of <FIG>, may not contain the timer information <NUM> either.

The step <NUM> of <FIG> indicates that the subscription information configuration <NUM> is sent from the MME <NUM> to the base unit <NUM>. The subscription information configuration <NUM> may be also communicated between different MMEs or between different base units.

As described above, the air-borne assistance information (ABI) <NUM> is contained in the subscription information configuration <NUM>. Therefore, when the MME <NUM> sends the subscription information configuration <NUM> to the base unit <NUM>, the air-borne assistance information (ABI) <NUM> is sent to the base unit <NUM>. Once the base unit <NUM> receives the air-borne assistance information (ABI) <NUM> of a particular mobile unit <NUM>, the base unit <NUM> considers that the particular mobile unit <NUM> is a registered aerial vehicle. If the base unit <NUM> does not receive the air-borne assistance information (ABI) <NUM> of the particular mobile unit <NUM>, the base unit <NUM> considers that the particular mobile unit <NUM> may be an unregistered aerial vehicle. In the condition that the particular mobile unit <NUM> that is an unregistered aerial vehicle is in the state of flying, the particular mobile unit <NUM> may be regarded as being a misused aerial vehicle, which would cause the MME <NUM> to stop serving the particular mobile unit.

In the step <NUM>, the MME <NUM> sends the subscription information configuration <NUM> including the air-borne assistance information (ABI) <NUM> to the base unit <NUM>. The MME <NUM> can have different behaviors to send the air-borne assistance information (ABI) <NUM> to the base unit <NUM>.

As described above, the air-borne assistance information (ABI) <NUM> may be empty or includes at least one of the altitude restriction <NUM>, the speed restriction <NUM>, the expected altitude range <NUM>, the mobility pattern <NUM> and the path information <NUM> (or includes at least one of the expected altitude range <NUM>, the mobility pattern <NUM> and the path information <NUM>). In behavior <NUM> of the MME, the MME <NUM> sends the ABI <NUM> to the base unit <NUM>, no matter whether or not the ABI <NUM> is empty. In other words, in the behavior <NUM>, the MME <NUM> does not check whether or not the ABI <NUM> is empty.

In behavior <NUM> of the MME, the MME <NUM> first checks whether or not the ABI <NUM> is empty. Only in the condition that the ABI <NUM> is not empty, the MME <NUM> sends the non-empty ABI <NUM> to the base unit <NUM>. That is, in the behavior <NUM> of the MME, the MME <NUM> does not send an empty ABI <NUM> to the base unit <NUM>.

Therefore, in the behavior <NUM> of the MME, the base unit <NUM> will receive the air-borne assistance information (ABI) <NUM> of all of the registered aerial vehicles, even if the air-borne assistance information (ABI) <NUM> of some of the registered aerial vehicles are empty. In this condition, the base unit <NUM> knows whether a mobile unit is a registered aerial vehicle.

In the behavior <NUM> of the MME, the base unit <NUM> only receives the air-borne assistance information (ABI) <NUM> of registered aerial vehicles that are not empty. Therefore, when the base unit <NUM> does not receive the air-borne assistance information (ABI) <NUM> of a particular mobile unit, there may exist two situations: one situation is that the particular mobile unit does not have the air-borne assistance information (ABI) <NUM> (i.e. the aerial server has not sent the subscription information configuration <NUM>, including the air-borne assistance information (ABI) <NUM> to the HSS <NUM> and/or the MME <NUM>) and therefore is an unregistered aerial vehicle; and the other situation is that the particular mobile unit has an empty air-borne assistance information (ABI) <NUM> and therefore is a registered aerial vehicle.

Due to various reasons, the network may choose to only provide particular service(s) to registered aerial vehicles. That is, if a mobile unit is an unregistered aerial vehicle, the network may choose to stop providing services to the mobile unit that is the unregistered aerial vehicle.

A mobile unit is determined as a registered aerial vehicle or an unregistered aerial vehicle based on the air-borne assistance information (ABI) <NUM> of the mobile unit, in particular, based on whether the air-borne assistance information (ABI) <NUM> of the mobile unit is stored at the base unit <NUM> or at the MME <NUM>. In addition, the mobile unit should be checked on whether it is in the state of flying. A mobile unit that is NOT in the state of flying is considered as being a normal mobile unit. The network may provide normal services to the normal mobile unit if the network has authenticated the UE.

A location platform is deployed in the mobile network to help check whether or not a mobile unit is in the state of flying. The location platform stores the location information of a certain area. Preferably, the location information is three dimensional (3D) information. Depending on the cover area of the location platform, different scenarios can be set up.

<FIG> illustrates one embodiment of location platform deployment. The location platform <NUM> is deployed within a local datacenter (DC). In this situation, the base units <NUM> may be connected directly to the location platform <NUM>.

<FIG> illustrates another embodiment of location platform deployment. The location platform <NUM> is deployed within a center datacenter (DC). In this situation, the location platform <NUM> is connected to the MME <NUM>, instead to the base unit(s) <NUM>.

<FIG> illustrates a first embodiment of misused aerial usage identification. In the first embodiment, it is assumed that the MME complies with its behavior <NUM> and the location platform is deployed as illustrated in <FIG>. That is, in the first embodiment, the MME <NUM> sends the ABI <NUM> to the base unit <NUM> no matter whether or not the ABI <NUM> is empty. In addition, the location platform is connected directly to the base unit <NUM>.

In step <NUM>, the base unit <NUM> receives location information of the mobile unit <NUM>. Preferably, the location information of the mobile unit <NUM> is comprised of three dimensional coordinates of the place where the mobile unit <NUM> resides. More preferably, the three dimensional coordinates may be Cartesian coordinates. Alternatively, the three dimensional coordinates may be represented by polar coordinates.

In step <NUM>, the base unit <NUM> checks whether it has received air-borne assistance information (ABI) <NUM> of the mobile unit <NUM>. Because in behavior <NUM> of the MME, the MME sends the air-borne assistance information (ABI) <NUM> of all of registered aerial vehicles, the receipt of the ABI <NUM> of the mobile unit <NUM> in the first embodiment means that the mobile unit <NUM> is a registered aerial vehicle. In this condition, the base unit <NUM> continues serving the mobile unit <NUM> that is the registered aerial vehicle. The steps <NUM>-<NUM> will not be performed in the condition that the mobile unit <NUM> is the registered aerial vehicle.

On the other hand, if the base unit <NUM> has not received the ABI <NUM> of the mobile unit <NUM>, the base unit <NUM> considers that the mobile unit <NUM> is an unregistered aerial vehicle. In this condition, the method proceeds to step <NUM>.

In the step <NUM>, the base unit <NUM> sends a location check request to the location platform <NUM>. The location check request includes the location information of the mobile unit <NUM>, which is preferably the three dimensional coordinates of the mobile unit <NUM>.

As described above, the location platform stores the location information (e.g. three dimensional information) of the area where the mobile unit <NUM> resides. Therefore, based on the comparison between the location information of the mobile unit <NUM> and the location information of the area where the mobile unit <NUM> resides, whether or not the mobile unit <NUM> is in the state of flying can be determined.

In some embodiments, the location information of the mobile unit <NUM> may be represented as X, Y, Z, in which X and Y represent two dimensional coordinates of the mobile unit <NUM> while Z represents an altitude of the mobile unit <NUM>. In the embodiments, the location platform <NUM> stores the location information (e.g. three dimensional information) of the area where the mobile unit <NUM> resides. At the location platform <NUM>, all of the valid locations, at which the mobile unit is considered as not being in the state of flying, can be identified by comparing the location information of the mobile unit <NUM> with the location information (e.g. three dimensional information) of the area where the mobile unit <NUM> resides. For example, if the mobile unit <NUM> is in a place where Z is much more than zero, this implies that the mobile unit <NUM> is in the air. Based on the check at the location platform <NUM>, if the place is in a high building, the mobile unit <NUM> is regarded as NOT being in the state of flying. As a whole, after receiving the location information (e.g. the three dimensional coordinates) of the mobile unit <NUM>, the location platform <NUM> can check whether the location information of the mobile unit <NUM> is valid, which means that it has high possibility that the mobile unit is NOT in the state of flying. Otherwise, the location information of the mobile unit <NUM> is checked as invalid, which means that the mobile unit <NUM> is considered as being in the state of flying.

In step <NUM>, the location platform <NUM> sends a response message (i.e. location check response) indicating "valid" or "invalid" to the base unit <NUM>.

If the base unit <NUM> receives the response message indicating "valid", which means that the mobile unit <NUM> is not in the state of flying, the base unit considers the mobile unit <NUM> as a normal mobile unit and continues serving the mobile unit <NUM>. If the base unit <NUM> receives the response message indicating "invalid", which means that the mobile unit <NUM> is in the state of flying, the method proceeds to step <NUM>.

In the step <NUM>, the base unit <NUM> sends a "Detach request or indication of session/ bearer release" message to MME, to request the MME to stop serving the mobile unit <NUM> that is in the state of flying but is an unregistered aerial vehicle. According to some embodiments, the message may include a cause value to indicate the reason why the MME should stop serving the mobile unit <NUM>. The reason may be that the mobile unit <NUM> is in the state of flying but is an unregistered aerial vehicle.

In step <NUM>, upon receiving the "Detach request or indication of session/ bearer release" message from the base unit <NUM>, the MME initiates "Detach procedure" message or "Delete session/bearer request" message, to stop serving the mobile unit <NUM>. According to some embodiments, the message may include a cause value to indicate the reason why the MME should stop serving the mobile unit <NUM>. The reason may be that the mobile unit <NUM> is in the state of flying but is an unregistered aerial vehicle.

Incidentally, the "Detach request or indication of session/ bearer release" and the "Detach procedure" or "Delete session/bearer request" are in the context of EPS architecture. In a <NUM> network, the "Detach request or indication of session/ bearer release" is changed to "Deregistration request or PDU session release request"; while the "Detach procedure" or "Delete session/bearer request" is changed to "AMF initiated deregistration and PDU session release request".

<FIG> illustrates a schematic flow chart diagram of the first embodiment of misused aerial usage identification.

Step <NUM> is the same as the step <NUM>.

If the judgment of the step <NUM> is Yes (i.e. the base unit <NUM> has received the air-borne assistance information (ABI) <NUM> of the mobile unit <NUM>), the base unit <NUM> continues serving the mobile unit <NUM> as a registered aerial vehicle, in step <NUM>.

If the judgment of the step <NUM> is No (i.e. the base unit <NUM> has NOT received the air-borne assistance information (ABI) <NUM> of the mobile unit <NUM>), the base unit <NUM> checks whether the mobile unit <NUM> is in the state of flying by communicating with the location platform <NUM>, in step <NUM>. The step <NUM> corresponds to steps <NUM> and <NUM>.

If the judgment of the step <NUM> is Yes (i.e. the mobile unit <NUM> is in the state of flying), the base unit <NUM> takes further actions to stop serving the mobile unit <NUM>, in step <NUM>. The step <NUM> corresponds to the steps <NUM> and <NUM>.

If the judgment of the step <NUM> is No (i.e. the mobile unit <NUM> is NOT in the state of flying), the base unit <NUM> continues serving the mobile unit <NUM> as a normal mobile unit, in step <NUM>.

<FIG> illustrates a second embodiment of misused aerial usage identification. In the second embodiment, it is assumed that the MME complies with its behavior <NUM> and the location platform <NUM> is deployed as illustrated in <FIG>. That is, in the second embodiment, the MME <NUM> sends the ABI <NUM> to the base unit <NUM> no matter whether or not the ABI <NUM> is empty. In addition, the location platform <NUM> is connected to the MME <NUM>.

In step <NUM>, the base unit <NUM> receives location information of the mobile unit <NUM>. Preferably, the location information of the mobile unit <NUM> is comprised of three dimensional coordinates of the place where the mobile unit <NUM> resides.

In step <NUM>, the base unit <NUM> checks whether it has received air-borne assistance information (ABI) <NUM> of the mobile unit <NUM>. If the base unit <NUM> has received the air-borne assistance information (ABI) <NUM> of the mobile unit <NUM>, the base unit <NUM> continues serving the mobile unit <NUM> that is a registered aerial vehicle. The steps <NUM>-<NUM> will not be performed in the condition that the mobile unit <NUM> is the registered aerial vehicle.

In the step <NUM>, the base unit <NUM> sends a location check request to the MME <NUM>. The location check request includes a UE temp identity (GUTI) of the mobile unit <NUM> and location information of the mobile unit <NUM>.

In step <NUM>, in response to the receipt of the location check request from the base unit <NUM>, the MME <NUM> sends a location check request to the location platform <NUM>. The location check request includes the location information of the mobile unit <NUM>.

In step <NUM>, similar to the step <NUM>, the location platform <NUM> checks whether the mobile unit <NUM> is in the state of flying according to the comparison between the three dimensional information of the area where the mobile unit <NUM> resides and the location information of the mobile unit <NUM>, and sends a response message (i.e. location check response) indicating "valid" or "invalid" to the MME <NUM>, in which "valid" means that it has high possibility that the mobile unit <NUM> is not in the state of flying, while "invalid" means that the mobile unit <NUM> is considered as being in the state of flying.

If the MME <NUM> receives the response message indicating "valid", the MME <NUM> considers that the mobile unit <NUM> is not in the state of flying and continues serving the mobile unit <NUM> as a normal mobile unit. If the MME <NUM> receives the response message indicating "invalid", which means that the mobile unit <NUM> is in the state of flying, the method proceeds to step <NUM>.

In the step <NUM>, the MME initiates "Detach procedure" or "Delete session/bearer request", to stop serving the mobile unit <NUM>. According to some embodiments, the request may include a cause value to indicate the reason why the MME stops serving the mobile unit <NUM>. The reason may be that the mobile unit <NUM> is in the state of flying but is an unregistered aerial vehicle.

<FIG> illustrates a schematic flow chart diagram of the second embodiment of misused aerial usage identification.

If the judgment of the step <NUM> is No (i.e. the base unit <NUM> has NOT received the air-borne assistance information (ABI) <NUM> of the mobile unit <NUM>), the base unit <NUM> sends a location check request to the MME <NUM>, in step <NUM>. The location check request includes a UE temp identity (GUTI) of the mobile unit <NUM> and location information of the mobile unit <NUM>.

In step <NUM>, the MME checks whether the mobile unit <NUM> is in the state of flying by communicating with the location platform <NUM>. The step <NUM> corresponds to the steps <NUM> and <NUM>.

If the judgment of step <NUM> is Yes (i.e. the mobile unit <NUM> is in the state of flying), the MME <NUM> takes further actions to stop serving the mobile unit <NUM>, in step <NUM>. In particular, the MME <NUM> initiates Detach procedure or Delete session/bearer request.

If the judgment of step <NUM> is No (i.e. the mobile unit <NUM> is NOT in the state of flying), the MME <NUM> continues serving the mobile unit <NUM> as a normal mobile unit, in step <NUM>.

<FIG> illustrates a third embodiment of misused aerial usage identification. In the third embodiment, it is assumed that the MME complies with its behavior <NUM> and the location platform is deployed as illustrated in <FIG>. That is, in the third embodiment, the MME <NUM> first checks whether or not the ABI <NUM> is empty. Only in the condition that the ABI <NUM> is not empty, the MME <NUM> sends the non-empty ABI <NUM> to the base unit <NUM>. In addition, the location platform <NUM> is connected directly to the base unit <NUM>.

On the other hand, if the base unit <NUM> has not received the ABI <NUM> of the mobile unit <NUM>, the base unit <NUM> cannot judge whether the mobile unit <NUM> is an unregistered aerial vehicle or not. In this condition, the method proceeds to step <NUM>.

In step <NUM>, similar to the step <NUM>, the location platform checks whether the mobile unit <NUM> is in the state of flying according to the comparison between the three dimensional information of the area where the mobile unit <NUM> resides and the location information of the mobile unit <NUM>, and sends a response message (i.e. location check response) indicating "valid" or "invalid" to the base unit <NUM>, in which "valid" means that it has high possibility that the mobile unit <NUM> is not in the state of flying, while "invalid" means that the mobile unit <NUM> is considered as being in the state of flying.

If the base unit <NUM> receives the response message indicating "valid", which means that the mobile unit <NUM> is not in the state of flying, the base unit <NUM> considers the mobile unit <NUM> as a normal mobile unit and continues serving the mobile unit <NUM> as the normal mobile unit. If the base unit <NUM> receives the response message indicating "invalid", which means that the mobile unit <NUM> is in the state of flying, the method proceeds to step <NUM>.

As described above, in the behavior <NUM> of the MME, the base unit <NUM> only receives the air-borne assistance information (ABI) <NUM> of registered aerial vehicles that are not empty. Therefore, when the base unit <NUM> does not receive the air-borne assistance information (ABI) <NUM> of a particular mobile unit, it does not know whether the particular mobile unit is an unregistered aerial vehicle, or the particular mobile unit is a registered aerial vehicle that has an empty air-borne assistance information (ABI) <NUM>.

In the step <NUM>, the base unit <NUM> sends a S1 message to the MME <NUM>. The S1 message includes a UE temp identity (GUTI) of the mobile unit <NUM> and an indicator indicating that the mobile unit <NUM> is in the state of flying.

In step <NUM>, in response to receiving the S1 message, the MME <NUM> checks whether it has received the air-borne assistance information (ABI) <NUM> of the mobile unit <NUM>. If the MME <NUM> has received the air-borne assistance information (ABI) <NUM> of the mobile unit <NUM>, the MME <NUM> continues serving the mobile unit <NUM> that is a registered aerial vehicle. In the condition that the mobile unit <NUM> is the registered aerial vehicle, step <NUM> is NOT performed.

On the other hand, if the MME <NUM> has not received the ABI <NUM> of the mobile unit <NUM>, the MME <NUM> considers that the mobile unit <NUM> is an unregistered aerial vehicle. The method proceeds to the step <NUM>.

<FIG> illustrates a schematic flow chart diagram of the third embodiment of misused aerial usage identification.

If the judgment of the step <NUM> is Yes (i.e. the mobile unit <NUM> is in the state of flying), the base unit <NUM> sends a S1 message to the MME <NUM>, in step <NUM>. The S1 message includes a UE temp identity (GUTI) of the mobile unit <NUM> and an indicator indicating that the mobile unit <NUM> is in the state of flying.

In step <NUM>, in response to receiving the S1 message, the MME <NUM> checks whether it has received the air-borne assistance information (ABI) <NUM> of the mobile unit <NUM>.

If the judgment of the step <NUM> is Yes (i.e. the MME <NUM> has received the air-borne assistance information (ABI) <NUM> of the mobile unit <NUM>), the MME <NUM> continues serving the mobile unit <NUM> as a registered aerial vehicle, in step <NUM>.

If the judgment of the step <NUM> is No (i.e. the MME <NUM> has not received the air-borne assistance information (ABI) <NUM> of the mobile unit <NUM>), the MME takes further actions to stop serving the mobile unit <NUM>, in step <NUM>. In particular, the MME <NUM> initiates "Detach procedure" or "Delete session/bearer request".

<FIG> illustrates a fourth embodiment of misused aerial usage identification. In the fourth embodiment, it is assumed that the MME complies with its behavior <NUM> and the location platform is deployed as illustrated in <FIG>. That is, in the fourth embodiment, the MME <NUM> first checks whether or not the ABI <NUM> is empty. Only in the condition that the ABI <NUM> is not empty, the MME <NUM> sends the ABI <NUM> to the base unit <NUM>. In addition, the location platform <NUM> is connected to the MME <NUM>.

On the other hand, if the base unit <NUM> has not received the ABI <NUM> of the mobile unit <NUM>, the base unit <NUM> cannot judge whether or not the mobile unit <NUM> is an unregistered aerial vehicle. In this condition, the method proceeds to step <NUM>.

In the step <NUM>, the base unit <NUM> sends an S1 message to the MME <NUM>. The S1 message includes a UE temp identity (GUTI) of the mobile unit <NUM> and location information of the mobile unit <NUM>. Preferably, the location information of the mobile unit <NUM> is comprised of three dimensional coordinates of the place where the mobile unit <NUM> resides.

In step <NUM>, in response to receiving the S1 message, the MME <NUM> checks whether it has received the air-borne assistance information (ABI) <NUM> of the mobile unit <NUM>. If the MME <NUM> has received the air-borne assistance information (ABI) <NUM> of the mobile unit <NUM>, the MME <NUM> continues serving the mobile unit <NUM> that is a registered aerial vehicle. In the condition that the mobile unit <NUM> is the registered aerial vehicle, steps <NUM>-<NUM> are NOT performed.

On the other hand, if the MME <NUM> has not received the ABI <NUM> of the mobile unit <NUM>, the MME <NUM> considers that the mobile unit <NUM> is an unregistered aerial vehicle. The method proceeds to step <NUM>.

In the step <NUM>, the MME sends a location check request to the location platform <NUM>. The location check request includes the location information of the mobile unit <NUM>, which is preferably the three dimensional coordinates of the mobile unit <NUM>.

In the step <NUM>, similar to the step <NUM>, the location platform <NUM> checks whether the mobile unit <NUM> is in the state of flying according to the comparison between the three dimensional information of the area where the mobile unit <NUM> resides and the location information of the mobile unit <NUM>, and sends a response message (i.e. location check response) indicating "valid" or "invalid" to the MME <NUM>, in which "valid" means that there is a high possibility that the mobile unit <NUM> is not in the state of flying, while "invalid" means that the mobile unit <NUM> is considered as being in the state of flying.

If the MME <NUM> receives the response message indicating "valid", the MME considers that the mobile unit <NUM> is not in the state of flying and continues serving the mobile unit <NUM> as a normal mobile unit. If the MME <NUM> receives the response message indicating "invalid", which means that the mobile unit <NUM> is in the state of flying, the method proceeds to step <NUM>.

<FIG> illustrates a schematic flow chart diagram of the fourth embodiment of misused aerial usage identification.

If the judgment of the step <NUM> is No (i.e. the base unit <NUM> has NOT received the air-borne assistance information (ABI) <NUM> of the mobile unit <NUM>), the base unit <NUM> sends a S1 message to the MME <NUM>, in step <NUM>. Similar to the step <NUM>, the S1 message includes the UE temp identity (GUTI) of the mobile unit <NUM> and the location information of the mobile unit <NUM>. Preferably, the location information of the mobile unit <NUM> comprises three dimensional coordinates of the place where the mobile unit <NUM> resides.

In step <NUM>, the MME <NUM> checks whether the mobile unit <NUM> is in the state of flying by communicating with the location platform <NUM>.

If the judgment of the step <NUM> is No (i.e. the MME <NUM> has not received the air-borne assistance information (ABI) <NUM> of the mobile unit <NUM>), the MME <NUM> checks whether the mobile unit <NUM> is in the state of flying by communicating with the location platform <NUM>, in step <NUM>. The step <NUM> corresponds to the steps <NUM> and <NUM>.

If the judgment of the step <NUM> is Yes (i.e. the mobile unit <NUM> is in the state of flying), the MME <NUM> takes further actions to stop serving the mobile unit <NUM>, in step <NUM>. In particular, the MME <NUM> initiates the Detach procedure or the Delete session/bearer request.

If the judgment of the step <NUM> is No (i.e. the mobile unit <NUM> is NOT in the state of flying), the MME <NUM> continues serving the mobile unit <NUM> as a normal mobile unit, in step <NUM>.

<FIG> depicts one embodiment of an apparatus <NUM> that may be used in performing misused aerial usage identification. The apparatus <NUM> includes one embodiment of the mobile unit <NUM>. Furthermore, the mobile unit <NUM> may include a processor <NUM>, a memory <NUM>, an input device <NUM>, a display <NUM>, a transmitter <NUM>, and a receiver <NUM>. In some embodiments, the input device <NUM> and the display <NUM> are combined into a single device, such as a touch screen. In certain embodiments, the mobile unit <NUM> may not include any input device <NUM> and/or display <NUM>. In various embodiments, the mobile unit <NUM> may include one or more of the processor <NUM>, the memory <NUM>, the transmitter <NUM>, and the receiver <NUM>, and may not include the input device <NUM> and/or the display <NUM>.

The memory <NUM>, in one embodiment, is a computer-readable storage medium. For example, the memory <NUM> may include RAM, including dynamic RAM ("DRAM"), synchronous dynamic RAM ("SDRAM"), and/or static RAM ("SRAM"). In some embodiments, the memory <NUM> also stores program code and related data, such as an operating system or other controller algorithms operating on the mobile unit <NUM>.

In some embodiments, the input device <NUM> may be integrated with the display <NUM>, for example, as a touch screen or similar touch-sensitive display. In some embodiments, the input device <NUM> includes a touch screen such that text may be input using a virtual keyboard displayed on the touch screen and/or by handwriting on the touch screen.

As another, nonlimiting example, the display <NUM> may include a wearable display such as a smart watch, smart glasses, a heads-up display, or the like.

For example, the input device <NUM> and display <NUM> may form a touch screen or similar touch-sensitive display.

The transmitter <NUM> is used to provide UL communication signals to the base unit <NUM> and the receiver <NUM> is used to receive DL communication signals from the base unit <NUM>. Although only one transmitter <NUM> and one receiver <NUM> are illustrated, the mobile unit <NUM> may have any suitable number of transmitters <NUM> and receivers <NUM>. The transmitter <NUM> and the receiver <NUM> may be any suitable type of transmitter and receiver.

<FIG> depicts one embodiment of an apparatus <NUM> that may be used for performing misused aerial usage identification. The apparatus <NUM> includes one embodiment of the base unit <NUM>. Furthermore, the base unit <NUM> may include a processor <NUM>, a memory <NUM>, an input device <NUM>, a display <NUM>, a transmitter <NUM>, and a receiver <NUM>. As may be appreciated, the processor <NUM>, the memory <NUM>, the input device <NUM>, the display <NUM>, the transmitter <NUM>, and the receiver <NUM> may be substantially similar to the processor <NUM>, the memory <NUM>, the input device <NUM>, the display <NUM>, the transmitter <NUM>, and the receiver <NUM> of the mobile unit <NUM>, respectively.

In some embodiments, the receiver <NUM> may be used to receive location information of the mobile unit <NUM> from the transmitter <NUM> of the mobile unit <NUM>. Although only one transmitter <NUM> and one receiver <NUM> are illustrated, the base unit <NUM> may have any suitable number of transmitters <NUM> and receivers <NUM>. The transmitter <NUM> and the receiver <NUM> may be any suitable type of transmitter and receiver.

<FIG> depicts one embodiment of a control node <NUM> that may be used for performing misused aerial usage identification. The control node <NUM> includes one embodiment of the MME <NUM>. Furthermore, the MME <NUM> may include a processor <NUM>, a memory <NUM>, an input device <NUM>, a display <NUM>, a transmitter <NUM>, and a receiver <NUM>. As may be appreciated, the processor <NUM>, the memory <NUM>, the input device <NUM>, the display <NUM>, the transmitter <NUM>, and the receiver <NUM> may be substantially similar to the processor <NUM>, the memory <NUM>, the input device <NUM>, the display <NUM>, the transmitter <NUM>, and the receiver <NUM> of the base unit <NUM>, respectively.

In some embodiments, the receiver <NUM> may be used to receive message(s) from the transmitter <NUM> of the base unit <NUM>. Although only one transmitter <NUM> and one receiver <NUM> are illustrated, the MME <NUM> may have any suitable number of transmitters <NUM> and receivers <NUM>.

Claim 1:
A method of determining aerial vehicle status, performed by a base unit (<NUM>, <NUM>), the method comprising:
receiving (<NUM>) location information of a mobile unit (<NUM>, <NUM>);
judging whether the mobile unit (<NUM>, <NUM>) is a registered aerial vehicle or an unregistered aerial vehicle, wherein:
in the condition that air-borne assistance information for the mobile unit (<NUM>, <NUM>) is stored at the base unit, judging that the mobile unit is a registered aerial vehicle, even if the air-borne assistance information is empty; and
in the condition that air-borne assistance information for the mobile unit (<NUM>, <NUM>) is not stored at the base unit, judging that the mobile unit is an unregistered aerial vehicle;
determining whether the mobile unit (<NUM>, <NUM>) is in a state of flying based on the location information of the mobile unit (<NUM>, <NUM>); and
identifying the mobile unit as a misused aerial vehicle in the condition that the mobile unit (<NUM>, <NUM>) is determined as being in the state of flying and is judged as being an unregistered aerial vehicle.