Patent Description:
An unmanned aerial vehicle is referred to as UAV, which is a non-manned aerial vehicle operated by a radio remote control device and the UAV's own program control device.

With the continuous development of a UAV technology, UAVs have also been widely used. In a related art, in order to further expand an application range of UAVs, a cellular network needs to provide a service for the UAV that satisfies the demand. However, there is yet no technical solution for an existing cellular network to control of a UAV, and if a UAV of any user is allowed to access the cellular network, strong interference may be brought to the cellular network. Related prior art can be found in <CIT>, <CIT> and <CIT>.

For solving the problem in the related art, embodiments of the present disclosure provide a UAV access method and device.

It is to be understood that the detailed descriptions below are only exemplary and explanatory and not intended to limit the present disclosure.

<FIG> is a flow chart illustrating a UAV access method, according to an exemplary embodiment. The UAV access method may be applied to an MME. As illustrated in <FIG>, the UAV access method includes the following Steps <NUM>-<NUM>.

In Step <NUM>, an attach request sent by a UAV is received.

In the embodiment of the present disclosure, the UAV is a cellular-network-based UAV, namely the UAV may accept service provided by a cellular network. When the UAV needs to access the cellular network, it is necessary to send the attach request to the MME at first to enable the MME to verify an identity of a user using the UAV and a device identity of the UAV. The UAV, when sending the attach request to the MME, may transparently transmit the attach request to the MME.

In Step <NUM>, an identity of a user using the UAV and a device identity of the UAV are verified according to the attach request to obtain a verification result.

In the embodiment of the present disclosure, the MME may verify the identity of the user using the UAV by many methods. For example, verification is performed according to an IMSI of the UAV. The IMSI is a label distinguishing the user of the UAV, is stored in a Subscriber Identity Module (SIM) card and is valid information configured to distinguish the user of the UAV.

The MME may also verify the device identity of the UAV by many methods. For example, verification is performed according to an IMEI of the UAV. In the Global System for Mobile Communications Alliance (GSMA), a new device type of a UAV is defined, a corresponding Type Allocation Code (TAC) is allocated for the device type of the UAV, and an IMEI is formed. An aforementioned IMEI is required to be allocated to each cellular-network-based UAV.

In Step <NUM>, if the verification result indicates that verification succeeds, access of the UAV is allowed, and a first attach response for indicating that access is allowed is sent to the UAV.

In the embodiment of the present disclosure, if the MME allows access of the UAV, it is indicated that the UAV may access the cellular network. Moreover, the MME, when sending the first attach response for indicating that access is allowed to the UAV, may further transparently transmit the first attach response to the UAV through a base station.

In Step <NUM>, if the verification result indicates that verification fails, access of the UAV is rejected, and a second attach response for indicating that access is rejected is sent to the UAV.

In the embodiment of the present disclosure, if the MME rejects access of the UAV, it is indicated that the UAV is not allowed to access the cellular network. Moreover, the MME, when sending the second attach response for indicating that access is rejected to the UAV, may further transparently transmit the second attach response to the UAV through the base station.

It may be seen from the embodiment that the attach request sent by the UAV is received, the identity of the user using the UAV and the device identity of the UAV are verified according to the attach request to obtain the verification result, if the verification result indicates that verification succeeds, access of the UAV is allowed and the first attach response for indicating that access is allowed is sent to the UAV, and if the verification result indicates that verification fails, access of the UAV is rejected and the second attach response for indicating that access is rejected is sent to the UAV, so that access of a UAV that fails to be verified to the cellular network may be prevented to reduce interference to the cellular network, access reliability of the UAV is improved, dedicated service may be conveniently provided for a UAV that is successfully verified, and working efficiency of the UAV is improved.

<FIG> is a flow chart illustrating another UAV access method, according to an exemplary embodiment. The UAV access method may be applied to the MME, and is established based on the method illustrated in <FIG>. As illustrated in <FIG>, when the MME verifies the identity of the user using the UAV and the device identity of the UAV according to the attach request to obtain the verification result, the following Steps <NUM>-<NUM> may be included.

In Step <NUM>, an IMSI of the UAV is acquired.

In Step <NUM>, first verification is performed on the identity of the user using the UAV according to the IMSI of the UAV.

In Step <NUM>, an IMEI of the UAV is acquired.

In Step <NUM>, second verification is performed on the device identity of the UAV according to the IMEI of the UAV.

In the embodiment of the present disclosure, there is no sequence for execution of Step <NUM> and Step <NUM>, and Step <NUM> may be executed at first and then Step <NUM> is executed, or Step <NUM> may be executed at first and then Step <NUM> is executed, or Step <NUM> and Step <NUM> may be executed at the same time.

In Step <NUM>, whether both first verification and second verification succeed, if both first verification and second verification succeed, Step <NUM> is executed, and if at least one of first verification and second verification does not succeed, Step <NUM> is executed.

In Step <NUM>, it is determined that the verification result indicates that verification succeeds, and the flow is ended.

In Step <NUM>, it is determined that the verification result indicates that verification fails, and the flow is ended.

It may be seen from the embodiment that the IMSI of the UAV is acquired, first verification is performed on the identity of the user using the UAV according to the IMSI of the UAV, the IMEI of the UAV is acquired, second verification is performed on the device identity of the UAV according to the IMEI of the UAV, it is determined that the final verification result indicates that verification succeeds only when both first verification and second verification succeed, otherwise verification fails, so that it is ensured that access of the UAV is allowed only when both the identity of the user using the UAV and the device identity of the UAV are legal to reduce interference of an illegal UAV to the cellular network, and a verification standard for access of the UAV may be improved to provide network service for the UAV better.

In an embodiment, the UAV, when sending the attach request to the MME, may add the IMSI of the UAV into the attach request and may also not add the IMSI of the UAV into the attach request. Therefore, when the IMSI of the UAV is acquired in Step <NUM>, the following acquisition manner may be adopted:.

whether the attach request contains the IMSI of the UAV is determined; if the attach request contains the IMSI of the UAV, the IMSI of the UAV is read from the attach request; and if the attach request does not contain the IMSI of the UAV, a user identity request is sent to the UAV, the user identity request being used to instruct the UAV to provide the UAV's own IMSI, and a user identity response sent by the UAV is received, the user identity response containing the IMSI of the UAV.

It may be seen from the embodiment that the IMSI of the UAV may be directly read from the attach request and the UAV may also be actively required to provide its own IMSI. In such a manner, the MME may conveniently verify the identity of the user through the IMSI provided by the UAV, so that user identity verification efficiency is improved.

In an embodiment, when first verification is performed on the identity of the user using the UAV according to the IMSI of the UAV in Step <NUM>, verification may be performed through an HSS. A specific verification process includes the following operations.

(<NUM>-<NUM>) An update location request is sent to the HSS, the update location request containing the IMSI of the UAV.

The HSS, after receiving the update location request, queries dedicated QoS configuration information of the UAV according to the IMSI of the UAV, and sends a first update location reply for indicating that the QoS configuration information of the UAV is obtained by query to the MME if the QoS configuration information of the UAV is obtained by query, the first update location reply containing the QoS configuration information of the UAV, and sends a second update location reply for indicating that the QoS configuration information of the UAV is not obtained by query to the MME if the QoS configuration information of the UAV is not obtained by query.

The update location reply contains the QoS configuration information of the UAV, and the second update location reply does not contain the QoS configuration information of the UAV.

It may be seen from the embodiment that the update location request is sent to the HSS, the update location request containing the IMSI of the UAV, it is determined that first verification succeeds if the first update location reply configured to indicate that the QoS configuration information of the UAV is obtained by query is received from the HSS and the first update location reply contains the QoS configuration information of the UAV, and it is determined that first verification fails if the second update location reply configured to indicate that the QoS configuration information of the UAV is not obtained by query is received from the HSS, so that verification over the identity of the user using the UAV is implemented through the MME, and the user identity verification efficiency is further improved.

In an embodiment, the UAV, when sending the attach request to the MME, may add the IMEI of the UAV into the attach request and may also not add the IMEI of the UAV into the attach request. Therefore, when the IMEI of the UAV is acquired in Step <NUM>, the following acquisition manner may be adopted:
whether the attach request contains the IMEI of the UAV is determined; if the attach request contains the IMEI of the UAV, the IMEI of the UAV is read from the attach request; and if the attach request does not contain the IMEI of the UAV, a device identity request is sent to the UAV, the device identity request being used to instruct the UAV to provide the UAV's own IMEI, and a device identity response sent by the UAV is received, the device identity response containing the IMEI of the UAV.

It may be seen from the embodiment that the IMEI of the UAV may be directly read from the attach request and the UAV may also be actively required to provide its own IMEI. In such a manner, the MME may conveniently verify the device identity through the IMEI provided by the UAV, so that device identity verification efficiency is improved.

In an embodiment, when second verification is performed on the device identity of the UAV according to the IMEI of the UAV in Step <NUM>, verification may be performed through an EIR. A specific verification process includes the following operations.

It may be seen from the embodiment that the ME device identity check request is sent to the EIR, the ME device identity check request containing the IMEI of the UAV, the ME device identity check ACK sent by the EIR is received, the ME device identity check ACK containing the query result obtained after the MME queries the corresponding registration record according to the IMEI of the UAV, it is determined that second verification succeeds if the query result indicates that the registration record of the UAV is obtained by query, and it is determined that second verification fails if the query result indicates that the registration record of the UAV is not obtained by query, so that verification over the device identity of the UAV is implemented through the EIR, and the device identity verification efficiency is further improved.

<FIG> is a flow chart illustrating a UAV access method, according to an exemplary embodiment. The UAV access method may be applied to a UAV, the UAV having an IMSI and an IMEI. As illustrated in <FIG>, the UAV access method includes the following Steps <NUM>-<NUM>.

In Step <NUM>, an attach request is sent to an MME.

In Step <NUM>, when a first attach response for indicating that access is allowed is received from the MME, it is determined that the MME allows access of the UAV.

In Step <NUM>, when a second attach response for indicating that access is rejected is received from the MME, it is determined that the MME rejects access of the UAV.

It may be seen from the embodiment that the attach request is sent to the MME, it is determined that the MME allows access of the UAV when the first attach response for indicating that access is allowed is received from the MME, and it is determined that the MME rejects access of the UAV when the second attach response for indicating that access is rejected is received from the MME, so that the MME may control access of the UAV, and access security of the UAV is improved.

In an embodiment, based on the device illustrated in <FIG>, the UAV access method may further include the following operations.

It may be seen from the embodiment that the user identity request sent by the MME is received, the user identity request being used to instruct the UAV to provide the UAV's own IMSI, and the user identity response is sent to the MME, the user identity response containing the IMSI of the UAV. In such a manner, the MME may conveniently perform user identity verification by use of the IMSI provided by the UAV, so that user identity verification efficiency of the UAV is improved.

It may be seen from the embodiment that the device identity request sent by the MME is received, the device identity request being used to instruct the UAV to provide the UAV's own IMEI, and the device identity response is sent to the MME, the device identity response containing the IMEI of the UAV. In such a manner, the MME may conveniently perform device identity verification by use of the IMEI provided by the UAV, so that device identity verification efficiency of the UAV is improved.

In an embodiment, based on the device illustrated in <FIG>, the attach request sent by the UAV contains at least one of the IMSI of the UAV or the IMEI of the UAV.

It may be seen from the embodiment that the attach request contains at least one of the IMSI of the UAV or the IMEI of the UAV, so that the MME may directly read the IMSI and/or IMEI for legality verification of the UAV from the attach request conveniently, and access efficiency of the UAV is further improved.

<FIG> is a flow chart illustrating a UAV access method, according to an exemplary embodiment. The UAV access method may be applied to an HSS, the HSS being configured to assist an MME in performing verification over an identity of a user using a UAV. As illustrated in <FIG>, the UAV access method includes the following Steps <NUM>-<NUM>.

In Step <NUM>, an update location request sent by the MME is received, the update location request containing an IMSI of the UAV that requests for access.

In Step <NUM>, dedicated QoS configuration information of the UAV is queried according to the IMSI of the UAV.

In Step <NUM>, if the QoS configuration information of the UAV is obtained by query, a first update location reply for indicating that the QoS configuration information of the UAV is obtained by query is sent to the MME, the first update location reply containing the QoS configuration information of the UAV.

In Step <NUM>, if the QoS configuration information of the UAV is not obtained by query, a second update location reply for indicating that the QoS configuration information of the UAV is not obtained by query is sent to the MME.

It may be seen from the embodiment that the update location request sent by the MME is received, the update location request containing the IMSI of the UAV that requests for access, the first update location reply configured to indicate that the QoS configuration information of the UAV is obtained by query is sent to the MME if the QoS configuration information of the UAV is obtained by query, the first update location reply containing the QoS configuration information of the UAV, and the second update location reply configured to indicate that the QoS configuration information of the UAV is not obtained by query is sent to the MME if the QoS configuration information of the UAV is not obtained by query, so that the HSS may assist the MME in completing verification over the identity of the user using the UAV, and access reliability of the UAV is improved.

<FIG> is a flow chart illustrating a UAV access method, according to an exemplary embodiment. The UAV access method may be applied to an EIR, the EIR being configured to assist an MME in performing verification over a device identity of a UAV. As illustrated in <FIG>, the UAV access method includes the following Steps <NUM>-<NUM>.

In Step <NUM>, a ME device identity check request sent by the MME is received, the ME device identity check request containing an IMEI of the UAV that requests for access.

In Step <NUM>, a corresponding registration record is queried according to the IMEI of the UAV to obtain a query result. The query result may include that the registration record of the UAV is obtained by query or that the registration record of the UAV is not obtained by query.

In Step <NUM>, a ME device identity check ACK containing the query result is sent to the MME.

It may be seen from the embodiment that the ME device identity check request sent by the MME is received, the ME device identity check request containing the IMEI of the UAV that requests for access, the corresponding registration record is queried according to the IMEI of the UAV to obtain the query result, and the ME device identity check ACK containing the query result is sent to the MME, so that the EIR may assist the MME in completing verification over the device identity of the UAV, and access reliability of the UAV is improved.

<FIG> is an information interaction diagram of a UAV access method, according to an exemplary embodiment. As illustrated in <FIG>, the information interaction diagram includes a UAV, a base station, an MME, an HSS and an EIR.

Corresponding to the embodiments of the UAV access method, the present disclosure also provides embodiments of a UAV access device.

<FIG> is a block diagram of a UAV access device, according to an exemplary embodiment. The UAV access device may be applied to an MME, and is configured to execute the UAV access method illustrated in <FIG>. As illustrated in <FIG>, the UAV access device may include a receiving module <NUM>, a verification module <NUM>, a first processing module <NUM> and a second processing module <NUM>.

The receiving module <NUM> is configured to receive an attach request sent by a UAV.

The verification module <NUM> is configured to verify an identity of a user using the UAV and a device identity of the UAV according to the attach request to obtain a verification result.

The first processing module <NUM> is configured to, if the verification result indicates that verification succeeds, allow access of the UAV and send a first attach response for indicating that access is allowed to the UAV.

The second processing module <NUM> is configured to, if the verification result indicates that verification fails, reject access of the UAV and send a second attach response for indicating that access is rejected to the UAV.

<FIG> is a block diagram of another UAV access device, according to an exemplary embodiment. The UAV access device may be applied to the MME, and is established based on the device illustrated in <FIG>. As illustrated in <FIG>, the verification module <NUM> may include a first acquisition submodule <NUM>, a first verification submodule <NUM>, a second acquisition submodule <NUM>, a second verification submodule <NUM>, a first determination submodule <NUM>, and a second determination submodule <NUM>.

The first acquisition submodule <NUM> is configured to acquire an IMSI of the UAV.

The first verification submodule <NUM> is configured to perform first verification on the identity of the user using the UAV according to the IMSI of the UAV.

The second acquisition submodule <NUM> is configured to acquire an IMEI of the UAV.

The second verification submodule <NUM> is configured to perform second verification on the device identity of the UAV according to the IMEI of the UAV.

The first determination submodule <NUM> is configured to, if both first verification and second verification succeed, determine that the verification result indicates that verification succeeds.

The second determination submodule <NUM> is configured to, if at least one of first verification and second verification fails, determine that the verification result indicates that verification fails.

<FIG> is a block diagram of another UAV access device, according to an exemplary embodiment. The UAV access device may be applied to the MME, and is established based on the device illustrated in <FIG>. As illustrated in <FIG>, the first acquisition submodule <NUM> may include a first determination submodule <NUM>, a first processing submodule <NUM> and a second processing submodule <NUM>.

The first determination submodule <NUM> is configured to determine whether the attach request contains the IMSI of the UAV.

The first processing submodule <NUM> is configured to, if a determination result of the first determination submodule <NUM> is that the attach request contains the IMSI of the UAV, read the IMSI of the UAV from the attach request.

The second processing submodule <NUM> is configured to, if the determination result of the first determination submodule <NUM> is that the attach request does not contain the IMSI of the UAV, send a user identity request to the UAV, the user identity request being used to instruct the UAV to provide the UAV's own IMSI, and receive a user identity response sent by the UAV, the user identity response containing the IMSI of the UAV.

<FIG> is a block diagram of another UAV access device, according to an exemplary embodiment. The UAV access device may be applied to the MME, and is established based on the device illustrated in <FIG>. As illustrated in <FIG>, the first verification submodule <NUM> may include a first sending submodule <NUM>, a first succeeding verification submodule <NUM> and a first failing verification submodule <NUM>.

The first sending submodule <NUM> is configured to send an update location request to an HSS, the update location request containing the IMSI of the UAV.

The first succeeding verification submodule <NUM> is configured to, if a first update location reply for indicating that QoS configuration information of the UAV is obtained by query is received from the HSS and the first update location reply contains the QoS configuration information of the UAV, determine that first verification succeeds.

The first failing verification submodule <NUM> is configured to, if a second update location reply for indicating that the QoS configuration information of the UAV is not obtained by query is received from the HSS, determine that first verification fails.

<FIG> is a block diagram of another UAV access device, according to an exemplary embodiment. The UAV access device may be applied to the MME, and is established based on the device illustrated in <FIG>. As illustrated in <FIG>, the second acquisition submodule <NUM> may include a second determination submodule <NUM>, a third processing submodule <NUM> and a fourth processing submodule <NUM>.

The second determination submodule <NUM> is configured to determine whether the attach request contains the IMEI of the UAV.

The third processing submodule <NUM> is configured to, if a determination result of the second determination submodule <NUM> is that the attach request contains the IMEI of the UAV, read the IMEI of the UAV from the attach request.

The fourth processing submodule <NUM> is configured to, if the determination result of the second determination submodule <NUM> is that the attach request does not contain the IMEI of the UAV, send a device identity request to the UAV, the device identity request being used to instruct the UAV to provide the UAV's own IMEI, and receive a device identity response sent by the UAV, the device identity response containing the IMEI of the UAV.

<FIG> is a block diagram of another UAV access device, according to an exemplary embodiment. The UAV access device may be applied to the MME, and is established based on the device illustrated in <FIG> or <FIG>. As illustrated in <FIG>, the second verification submodule <NUM> may include a second sending submodule <NUM>, a receiving submodule <NUM>, a second succeeding verification submodule <NUM> and a second failing verification submodule <NUM>.

The second sending submodule <NUM> is configured to send a ME device identity check request to an EIR, the ME device identity check request containing the IMEI of the UAV.

The receiving submodule <NUM> is configured to receive a ME device identity check ACK sent by the EIR, the ME device identity check ACK containing a query result obtained by the MME querying a corresponding registration record according to the IMEI of the UAV.

The second succeeding verification submodule <NUM> is configured to, if the query result indicates that the registration record of the UAV is obtained by query, determine that second verification succeeds.

The second failing verification submodule <NUM> is configured to, if the query result indicates that the registration record of the UAV is not obtained by query, determine that second verification fails.

<FIG> is a block diagram of a UAV access device, according to an exemplary embodiment. The UAV access device may be applied to a UAV, the UAV having an IMSI and an IMEI, and is configured to execute the UAV access method illustrated in <FIG>. As illustrated in <FIG>, the UAV access device may include a first sending module <NUM>, a first determination module <NUM> and a second determination module <NUM>.

The first sending module <NUM> is configured to send an attach request to an MME.

The first determination module <NUM> is configured to, when a first attach response for indicating that access is allowed is received from the MME, determine that the MME allows access of the UAV.

The second determination module <NUM> is configured to, when a second attach response for indicating that access is rejected is received from the MME, determine that the MME rejects access of the UAV.

<FIG> is a block diagram of another UAV access device, according to an exemplary embodiment. The UAV access device may be applied to the UAV, and is established based on the device illustrated in <FIG>. As illustrated in <FIG>, the UAV access device may further include a first receiving module <NUM> and a second sending module <NUM>.

The first receiving module <NUM> is configured to receive a user identity request sent by the MME, the user identity request being used to instruct the UAV to provide the UAV's own IMSI.

The second sending module <NUM> is configured to send a user identity response to the MME, the user identity response containing the IMSI of the UAV.

<FIG> is a block diagram of another UAV access device, according to an exemplary embodiment. The UAV access device may be applied to the UAV, and is established based on the device illustrated in <FIG>. As illustrated in <FIG>, the UAV access device may further include a second receiving module <NUM> and a third sending module <NUM>.

The second receiving module <NUM> is configured to receive a device identity request sent by the MME, the device identity request being used to instruct the UAV to provide the UAV's own IMEI.

The third sending module <NUM> is configured to send a device identity response to the MME, the device identity response containing the IMEI of the UAV.

In an embodiment, based on the device illustrated in <FIG>, the attach request contains at least one of the IMSI of the UAV or the IMEI of the UAV.

It may be seen from the embodiment that the attach request contains at least one of the IMSI of the UAV or the IMEI of the UAV, so that the MME may directly read information, i.e., the IMSI and/or the IMEI, for legality verification of the UAV from the attach request conveniently, and access efficiency of the UAV is further improved.

<FIG> is a block diagram of a UAV access device, according to an exemplary embodiment. The UAV access device may be applied to an HSS, the HSS being configured to assist an MME in performing verification over an identity of a user using a UAV, and is configured to execute the UAV access method illustrated in <FIG>. As illustrated in <FIG>, the UAV access device may include a receiving module <NUM>, a query module <NUM>, a first sending module <NUM> and a second sending module <NUM>.

The receiving module <NUM> is configured to receive an update location request sent by the MME, the update location request containing an IMSI of the UAV that requests for access.

The query module <NUM> is configured to query dedicated QoS configuration information of the UAV according to the IMSI of the UAV.

The first sending module <NUM> is configured to, if the QoS configuration information of the UAV is obtained by query, send a first update location reply for indicating that the QoS configuration information of the UAV is obtained by query to the MME, the first update location reply containing the QoS configuration information of the UAV.

The second sending module <NUM> is configured to, if the QoS configuration information of the UAV is not obtained by query, send a second update location reply for indicating that the QoS configuration information of the UAV is not obtained by query to the MME.

<FIG> is a block diagram of a UAV access device, according to an exemplary embodiment. The UAV access device may be applied to an EIR, the EIR being configured to assist an MME in performing verification over a device identity of a UAV, and is configured to execute the UAV access method illustrated in <FIG>. As illustrated in <FIG>, the UAV access device may include a receiving module <NUM>, a query module <NUM> and a sending module <NUM>.

The receiving module <NUM> is configured to receive a ME device identity check request sent by the MME, the ME device identity check request containing an IMEI of the UAV that requests for access.

The query module <NUM> is configured to query a corresponding registration record according to the IMEI of the UAV to obtain a query result.

The sending module <NUM> is configured to send a ME device identity check ACK containing the query result to the MME.

The device embodiments substantially correspond to the method embodiments, and thus related parts refer to part of descriptions of the method embodiments. The device embodiments described above are only schematic, units described as separate parts therein may or may not be physically separated, and parts displayed as units may or may not be physical units, and namely may be located in the same place or may also be distributed to multiple network units. Part or all of the modules therein may be selected according to a practical requirement to achieve the purpose of the solutions of the present disclosure. Those of ordinary skill in the art may understand and implement without creative work.

The present disclosure also provides a non-transitory computer-readable storage medium having stored thereon a computer program for executing the UAV access method illustrated in <FIG>.

The present disclosure also provides a UAV access device, which is applied to an MME and includes:.

<FIG> is a structure diagram of a UAV access device, according to an exemplary embodiment. As illustrated in <FIG>, the UAV access device <NUM> according to the exemplary embodiment may be provided as an MME.

The processing component <NUM> may include one or more processors <NUM> to execute instructions to perform all or part of the steps in the abovementioned method. Moreover, the processing component <NUM> may include one or more modules which facilitate interaction between the processing component <NUM> and the other components. For instance, the processing component <NUM> may include a multimedia module to facilitate interaction between the multimedia component <NUM> and the processing component <NUM>.

Examples of such data include instructions for any application programs or methods operated on the device <NUM>, contact data, phonebook data, messages, pictures, video, etc. The memory <NUM> may be implemented by any type of volatile or non-volatile memory devices, or a combination thereof, such as a Static Random Access Memory (SRAM), an Electrically Erasable Programmable Read-Only Memory (EEPROM), an Erasable Programmable Read-Only Memory (EPROM), a Programmable Read-Only Memory (PROM), a Read-Only Memory (ROM), a magnetic memory, a flash memory, and a magnetic or optical disk.

The multimedia component <NUM> includes a screen providing an output interface between the device <NUM> and a user. In some embodiments, the screen may include a Liquid Crystal Display (LCD) and a Touch Panel (TP). If the screen includes the TP, the screen may be implemented as a touch screen to receive an input signal from the user. The TP includes one or more touch sensors to sense touches, swipes and gestures on the TP. The touch sensors may not only sense a boundary of a touch or swipe action but also detect a duration and pressure associated with the touch or swipe action. The front camera and/or the rear camera may receive external multimedia data when the device <NUM> is in an operation mode, such as a photographing mode or a video mode. Each of the front camera and the rear camera may be a fixed optical lens system or have focusing and optical zooming capabilities.

The audio component <NUM> is configured to output and/or input an audio signal. For example, the audio component <NUM> includes a Microphone (MIC), and the MIC is configured to receive an external audio signal when the device <NUM> is in the operation mode, such as a call mode, a recording mode and a voice recognition mode. The received audio signal may further be stored in the memory <NUM> or sent through the communication component <NUM>. In some embodiments, the audio component <NUM> further includes a speaker configured to output the audio signal.

The communication component <NUM> is configured to facilitate wired or wireless communication between the device <NUM> and another device. The device <NUM> may access a communication-standard-based wireless network, such as a Wireless Fidelity (WiFi) network, a 2nd-Generation (<NUM>) or 3rd-Generation (<NUM>) network or a combination thereof. In an exemplary embodiment, the communication component <NUM> receives a broadcast signal or broadcast associated information from an external broadcast management system through a broadcast channel. In an exemplary embodiment, the communication component <NUM> further includes a Near Field Communication (NFC) module to facilitate short-range communication. For example, the NFC module may be implemented based on a Radio Frequency Identification (RFID) technology, an Infrared Data Association (IrDA) technology, an Ultra-WideBand (UWB) technology, a Bluetooth (BT) technology and another technology.

In an exemplary embodiment, the device <NUM> may be implemented by one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), Digital Signal Processing Devices (DSPDs), Programmable Logic Devices (PLDs), Field Programmable Gate Arrays (FPGAs), controllers, micro-controllers, microprocessors or other electronic components, and is configured to execute the abovementioned method.

In an exemplary embodiment, there is also provided a non-transitory computer-readable storage medium including an instruction, such as the memory <NUM> including an instruction, and the instruction may be executed by the processor <NUM> of the device <NUM> to implement the abovementioned method. For example, the non-transitory computer-readable storage medium may be a ROM, a Random Access Memory (RAM), a Compact Disc Read-Only Memory (CD-ROM), a magnetic tape, a floppy disc, an optical data storage device and the like.

The instruction in the storage medium is executed by the processor to enable the device <NUM> to execute any UAV access method.

The present disclosure also provides a UAV access device, which is applied to a UAV, the UAV having an IMSI and an IMEI, the device including:.

The present disclosure also provides a UAV access device, which is applied to an HSS, the HSS being configured to assist an MME in performing verification over an identity of a user using a UAV, the device including:.

<FIG> is a structure diagram of a UAV access device, according to an exemplary embodiment. As illustrated in <FIG>, the UAV access device <NUM> according to the exemplary embodiment may be provided as an HSS. Moreover, components of the device <NUM> are similar to <FIG> and elaborations thereof will not be repeated herein.

The present disclosure also provides a UAV access device, which is applied to an EIR, the EIR being configured to assist an MME in performing verification over a device identity of a UAV, the device including:.

<FIG> is a structure diagram of a UAV access device, according to an exemplary embodiment. As illustrated in <FIG>, the UAV access device <NUM> according to the exemplary embodiment may be provided as an EIR. Moreover, components of the device <NUM> are similar to <FIG> and elaborations thereof will not be repeated herein.

Other implementation solutions of the present disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the present disclosure. This application is intended to cover any variations, uses, or adaptations of the present disclosure following the general principles thereof and including such departures from the present disclosure as come within known or customary practice in the art. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the present disclosure being indicated by the following claims.

Claim 1:
A method for Unmanned Aerial Vehicle, UAV, access, applied to a Mobility Management Entity, MME, and comprising:
receiving (<NUM>) an attach request sent by a UAV;
verifying (<NUM>) an identity of a user using the UAV and a device identity of the UAV according to the attach request to obtain a verification result;
wherein verifying the identity of the user using the UAV and the device identity of the UAV according to the attach request to obtain the verification result comprises:
acquiring an International Mobile Subscriber Identification Number, IMSI, of the UAV;
performing first verification on the identity of the user using the UAV according to the IMSI of the UAV;
acquiring an International Mobile Equipment Identity, IMEI, of the UAV;
performing second verification on the device identity of the UAV according to the IMEI of the UAV;
if both the first verification and the second verification succeed, determining that the verification result indicates that verification succeeds; and
if at least one of the first verification or the second verification fails, determining that the verification result indicates that the verification fails;
wherein performing first verification on the identity of the user using the UAV according to the IMSI of the UAV comprises:
sending an update location request to a Home Subscriber Server, HSS, the update location request containing the IMSI of the UAV, wherein the HSS, after receiving the update location request, queries dedicated QoS configuration information of the UAV according to the IMSI of the UAV;
if a first update location reply for indicating that Quality of Service, QoS, configuration information of the UAV is obtained by the query is received from the HSS and the first update location reply contains the QoS configuration information of the UAV, determining that the first verification succeeds; and
if a second update location reply for indicating that the QoS configuration information of the UAV is not obtained by the query is received from the HSS,
determining that the first verification fails;
if the verification result indicates that the verification succeeds, allowing access of the UAV and sending a first attach response for indicating that access is allowed to the UAV (<NUM>); and
if the verification result indicates that the verification fails, rejecting access of the UAV and sending a second attach response for indicating that access is rejected to the UAV (<NUM>).