METHOD AND DEVICE FOR ACCESSING UNMANNED AIRCRAFT

Description

TECHNICAL FIELD

[0001] The present disclosure generally relates to the technical field of communication, and more particularly, to an Unmanned Aerial Vehicle (UAV) access method and device.BACKGROUND

[0002] 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.

[0003] 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 CN102905266A, WO2017013417A1 and CN105225540A.SUMMARY

[0004] For solving the problem in the related art, embodiments of the present disclosure provide a UAV access method and device. The present invention is defined in the claims.

[0005] It is to be understood that the detailed descriptions below are only exemplary and explanatory and not intended to limit the present disclosure.BRIEF DESCRIPTION OF THE DRAWINGS

[0006] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and, together with the description, serve to explain the principles of the present disclosure. FIG 1 is a flow chart illustrating a UAV access method, according to an exemplary embodiment. FIG 2 is a flow chart illustrating another UAV access method, according to an exemplary embodiment. FIG 3 is a flow chart illustrating a UAV access method, according to an exemplary embodiment. FIG 4 is a flow chart illustrating a UAV access method, according to an exemplary embodiment. FIG 5 is a flow chart illustrating a UAV access method, according to an exemplary embodiment. FIG 6 is an information interaction diagram of a UAV access method, according to an exemplary embodiment. FIG 7 is a block diagram of a UAV access device, according to an exemplary embodiment. FIG 8 is a block diagram of another UAV access device, according to an exemplary embodiment. FIG 9 is a block diagram of another UAV access device, according to an exemplary embodiment. FIG 10 is a block diagram of another UAV access device, according to an exemplary embodiment. FIG 11 is a block diagram of another UAV access device, according to an exemplary embodiment. FIG 12 is a block diagram of another UAV access device, according to an exemplary embodiment. FIG 13 is a block diagram of a UAV access device, according to an exemplary embodiment. FIG 14 is a block diagram of another UAV access device, according to an exemplary embodiment. FIG 15 is a block diagram of another UAV access device, according to an exemplary embodiment. FIG 16 is a block diagram of a UAV access device, according to an exemplary embodiment. FIG 17 is a block diagram of a UAV access device, according to an exemplary embodiment. FIG 18 is a structure diagram of a UAV access device, according to an exemplary embodiment. FIG 19 is a structure diagram of a UAV access device, according to an exemplary embodiment. FIG 20 is a structure diagram of a UAV access device, according to an exemplary embodiment. DETAILED DESCRIPTION

[0007] Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. The following description refers to the accompanying drawings in which the same numbers in different drawings represent the same or similar elements unless otherwise represented. The implementations set forth in the following description of exemplary embodiments do not represent all implementations consistent with the present disclosure. Instead, they are merely examples of apparatuses and methods consistent with aspects related to the present disclosure as recited in the appended claims.

[0008] FIG 1 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 1, the UAV access method includes the following Steps 110-140.

[0009] In Step 110, an attach request sent by a UAV is received.

[0010] 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.

[0011] In Step 120, 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.

[0012] 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.

[0013] 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.

[0014] In Step 130, 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.

[0015] 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.

[0016] In Step 140, 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.

[0017] 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.

[0018] 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.

[0019] FIG 2 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 1. As illustrated in FIG 2, 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 210-270 may be included.

[0020] In Step 210, an IMSI of the UAV is acquired.

[0021] In Step 220, first verification is performed on the identity of the user using the UAV according to the IMSI of the UAV.

[0022] In Step 230, an IMEI of the UAV is acquired.

[0023] In Step 240, second verification is performed on the device identity of the UAV according to the IMEI of the UAV.

[0024] In the embodiment of the present disclosure, there is no sequence for execution of Step 210 and Step 230, and Step 210 may be executed at first and then Step 230 is executed, or Step 230 may be executed at first and then Step 210 is executed, or Step 210 and Step 230 may be executed at the same time.

[0025] In Step 250, whether both first verification and second verification succeed, if both first verification and second verification succeed, Step 260 is executed, and if at least one of first verification and second verification does not succeed, Step 270 is executed.

[0026] In Step 260, it is determined that the verification result indicates that verification succeeds, and the flow is ended.

[0027] In Step 270, it is determined that the verification result indicates that verification fails, and the flow is ended.

[0028] 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.

[0029] 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 210, the following acquisition manner may be adopted:

[0030] 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.

[0031] 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.

[0032] 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 220, verification may be performed through an HSS. A specific verification process includes the following operations.

[0033] (1-1) An update location request is sent to the HSS, the update location request containing the IMSI of the UAV.

[0034] 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.

[0035] 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. (1-2) 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, it is determined that first verification succeeds. (1-3) 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, it is determined that first verification fails.

[0036] 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.

[0037] 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 210, 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.

[0038] 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.

[0039] In an embodiment, when second verification is performed on the device identity of the UAV according to the IMEI of the UAV in Step 220, verification may be performed through an EIR. A specific verification process includes the following operations. (2-1) A ME device identity check request is sent to the EIR, the ME device identity check request containing the IMEI of the UAV. (2-2) A ME device identity check ACK sent by the EIR is received, 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. (2-3) If the query result indicates that the registration record of the UAV is obtained by query, it is determined that second verification succeeds. (2-4) If the query result indicates that the registration record of the UAV is not obtained by query, it is determined that second verification fails.

[0040] 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.

[0041] FIG 3 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 3, the UAV access method includes the following Steps 310-330.

[0042] In Step 310, an attach request is sent to an MME.

[0043] In Step 320, 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.

[0044] In Step 330, 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.

[0045] 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.

[0046] In an embodiment, based on the device illustrated in FIG 3, the UAV access method may further include the following operations. (3-1) A 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. (3-2) A user identity response is sent to the MME, the user identity response containing the IMSI of the UAV.

[0047] 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.

[0048] In an embodiment, based on the device illustrated in FIG 3, the UAV access method may further include the following operations. (4-1) A 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. (4-2) A device identity response is sent to the MME, the device identity response containing the IMEI of the UAV.

[0049] 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.

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

[0051] 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.

[0052] FIG 4 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 4, the UAV access method includes the following Steps 410-440.

[0053] In Step 410, an update location request sent by the MME is received, the update location request containing an IMSI of the UAV that requests for access.

[0054] In Step 420, dedicated QoS configuration information of the UAV is queried according to the IMSI of the UAV.

[0055] In Step 430, 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.

[0056] In Step 440, 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.

[0057] 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.

[0058] FIG 5 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 5, the UAV access method includes the following Steps 410-430.

[0059] In Step 510, 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.

[0060] In Step 520, 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.

[0061] In Step 530, a ME device identity check ACK containing the query result is sent to the MME.

[0062] 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.

[0063] FIG 6 is an information interaction diagram of a UAV access method, according to an exemplary embodiment. As illustrated in FIG 6, the information interaction diagram includes a UAV, a base station, an MME, an HSS and an EIR. (1) The UAV sends an attach request to the base station, and the base station transparently transmits the attach request to the MME, the attach request containing an IMSI of the UAV. (2) The MME sends an update location request to the HSS, the update location request containing the IMSI of the UAV. (3) The HSS sends an update location reply to the MME. The update location reply may be a first update location reply for indicating that QoS configuration information of the UAV is obtained by query, the first update location reply containing the QoS configuration information of the UAV, and may also be a second update location reply for indicating that the QoS configuration information of the UAV is not obtained by query. (4) The MME sends a device identity request to the base station, and the base station transparently transmits the device identity request to the UAV, the device identity request being used to instruct the UAV to provide the UAV's own IMEI. (5) The UAV sends a device identity response to the base station, and the base station transparently transmits the device identity response to the MME, the device identity response containing the IMEI of the UAV. (6) The MME sends a ME device identity check request to the EIR, the ME device identity check request containing the IMEI of the UAV. (7) The EIR sends a ME device identity check ACK to the MME. The ME device identity check ACK may be a first ME device identity check ACK configured to indicate that the IMEI of the UAV has been registered, and may also be a second ME device identity check ACK configured to indicate that the IMEI of the UAV has yet not been registered. (8) The MME sends an attach response to the base station, and the base station transparently transmits the attach response to the UAV. The attach response may be a first attach response for indicating that access is allowed, and may also be a second attach response for indicating that access is rejected.

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

[0065] FIG 7 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 1. As illustrated in FIG 7, the UAV access device may include a receiving module 71, a verification module 72, a first processing module 73 and a second processing module 74.

[0066] The receiving module 71 is configured to receive an attach request sent by a UAV.

[0067] The verification module 72 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.

[0068] The first processing module 73 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.

[0069] The second processing module 74 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.

[0070] 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.

[0071] FIG 8 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 7. As illustrated in FIG 8, the verification module 72 may include a first acquisition submodule 81, a first verification submodule 82, a second acquisition submodule 83, a second verification submodule 84, a first determination submodule 85, and a second determination submodule 86.

[0072] The first acquisition submodule 81 is configured to acquire an IMSI of the UAV.

[0073] The first verification submodule 82 is configured to perform first verification on the identity of the user using the UAV according to the IMSI of the UAV.

[0074] The second acquisition submodule 83 is configured to acquire an IMEI of the UAV.

[0075] The second verification submodule 84 is configured to perform second verification on the device identity of the UAV according to the IMEI of the UAV.

[0076] The first determination submodule 85 is configured to, if both first verification and second verification succeed, determine that the verification result indicates that verification succeeds.

[0077] The second determination submodule 86 is configured to, if at least one of first verification and second verification fails, determine that the verification result indicates that verification fails.

[0078] 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.

[0079] FIG 9 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 8. As illustrated in FIG 9, the first acquisition submodule 81 may include a first determination submodule 91, a first processing submodule 92 and a second processing submodule 93.

[0080] The first determination submodule 91 is configured to determine whether the attach request contains the IMSI of the UAV.

[0081] The first processing submodule 92 is configured to, if a determination result of the first determination submodule 91 is that the attach request contains the IMSI of the UAV, read the IMSI of the UAV from the attach request.

[0082] The second processing submodule 93 is configured to, if the determination result of the first determination submodule 91 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.

[0083] 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.

[0084] FIG 10 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 8 or FIG 9. As illustrated in FIG 10, the first verification submodule 82 may include a first sending submodule 101, a first succeeding verification submodule 102 and a first failing verification submodule 103.

[0085] The first sending submodule 101 is configured to send an update location request to an HSS, the update location request containing the IMSI of the UAV.

[0086] The first succeeding verification submodule 102 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.

[0087] The first failing verification submodule 103 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.

[0088] 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.

[0089] FIG 11 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 8. As illustrated in FIG 11, the second acquisition submodule 83 may include a second determination submodule 111, a third processing submodule 112 and a fourth processing submodule 113.

[0090] The second determination submodule 111 is configured to determine whether the attach request contains the IMEI of the UAV.

[0091] The third processing submodule 112 is configured to, if a determination result of the second determination submodule 111 is that the attach request contains the IMEI of the UAV, read the IMEI of the UAV from the attach request.

[0092] The fourth processing submodule 113 is configured to, if the determination result of the second determination submodule 111 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.

[0093] 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.

[0094] FIG 12 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 8 or FIG 11. As illustrated in FIG 12, the second verification submodule 84 may include a second sending submodule 121, a receiving submodule 122, a second succeeding verification submodule 123 and a second failing verification submodule 124.

[0095] The second sending submodule 121 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.

[0096] The receiving submodule 122 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.

[0097] The second succeeding verification submodule 123 is configured to, if the query result indicates that the registration record of the UAV is obtained by query, determine that second verification succeeds.

[0098] The second failing verification submodule 124 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.

[0099] 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.

[0100] FIG 13 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 3. As illustrated in FIG 13, the UAV access device may include a first sending module 131, a first determination module 132 and a second determination module 133.

[0101] The first sending module 131 is configured to send an attach request to an MME.

[0102] The first determination module 132 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.

[0103] The second determination module 133 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.

[0104] 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.

[0105] FIG 14 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 13. As illustrated in FIG 14, the UAV access device may further include a first receiving module 141 and a second sending module 142.

[0106] The first receiving module 141 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.

[0107] The second sending module 142 is configured to send a user identity response to the MME, the user identity response containing the IMSI of the UAV.

[0108] 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.

[0109] FIG 15 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 13. As illustrated in FIG 15, the UAV access device may further include a second receiving module 151 and a third sending module 152.

[0110] The second receiving module 151 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.

[0111] The third sending module 152 is configured to send a device identity response to the MME, the device identity response containing the IMEI of the UAV.

[0112] 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.

[0113] In an embodiment, based on the device illustrated in FIG 13, the attach request contains at least one of the IMSI of the UAV or the IMEI of the UAV.

[0114] 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.

[0115] FIG 16 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 4. As illustrated in FIG 16, the UAV access device may include a receiving module 161, a query module 162, a first sending module 163 and a second sending module 164.

[0116] The receiving module 161 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.

[0117] The query module 162 is configured to query dedicated QoS configuration information of the UAV according to the IMSI of the UAV.

[0118] The first sending module 163 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.

[0119] The second sending module 164 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.

[0120] 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.

[0121] FIG 17 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 5. As illustrated in FIG 17, the UAV access device may include a receiving module 171, a query module 172 and a sending module 173.

[0122] The receiving module 171 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.

[0123] The query module 172 is configured to query a corresponding registration record according to the IMEI of the UAV to obtain a query result.

[0124] The sending module 173 is configured to send a ME device identity check ACK containing the query result to the MME.

[0125] 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.

[0126] 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.

[0127] 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 1 or FIG 2.

[0128] 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 3.

[0129] 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 4.

[0130] 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 5.

[0131] The present disclosure also provides a UAV access device, which is applied to an MME and includes: a processor; and a memory configured to store processor-executable instructions, wherein the processor is configured to: receive an attach request sent by a UAV; 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; 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; and 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.

[0132] FIG 18 is a structure diagram of a UAV access device, according to an exemplary embodiment. As illustrated in FIG 18, the UAV access device 1800 according to the exemplary embodiment may be provided as an MME.

[0133] Referring to FIG 18, the device 1800 may include one or more of the following components: a processing component 1801, a memory 1802, a power component 1803, a multimedia component 1804, an audio component 1805, an Input / Output (I / O) interface 1806, a sensor component 1807, and a communication component 1808.

[0134] The processing component 1801 typically controls overall operations of the device 1800, such as the operations associated with display, telephone calls, data communications, camera operations, and recording operations. The processing component 1801 may include one or more processors 1809 to execute instructions to perform all or part of the steps in the abovementioned method. Moreover, the processing component 1801 may include one or more modules which facilitate interaction between the processing component 1801 and the other components. For instance, the processing component 1801 may include a multimedia module to facilitate interaction between the multimedia component 1804 and the processing component 1801.

[0135] The memory 1802 is configured to store various types of data to support the operation of the device 1800. Examples of such data include instructions for any application programs or methods operated on the device 1800, contact data, phonebook data, messages, pictures, video, etc. The memory 1802 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.

[0136] The power component 1803 provides power for various components of the device 1800. The power component 1803 may include a power management system, one or more power supplies, and other components associated with generation, management and distribution of power for the device 1800.

[0137] The multimedia component 1804 includes a screen providing an output interface between the device 1800 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. In some embodiments, the multimedia component 1804 includes a front camera and / or a rear camera. The front camera and / or the rear camera may receive external multimedia data when the device 1800 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.

[0138] The audio component 1805 is configured to output and / or input an audio signal. For example, the audio component 1805 includes a Microphone (MIC), and the MIC is configured to receive an external audio signal when the device 1800 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 1802 or sent through the communication component 1808. In some embodiments, the audio component 1805 further includes a speaker configured to output the audio signal.

[0139] The I / O interface 1806 provides an interface between the processing component 1801 and a peripheral interface module, and the peripheral interface module may be a keyboard, a click wheel, a button and the like. The button may include, but not limited to: a home button, a volume button, a starting button and a locking button.

[0140] The sensor component 1807 includes one or more sensors configured to provide status assessment in various aspects for the device 1800. For instance, the sensor component 1807 may detect an on / off status of the device 1800 and relative positioning of components, such as a display and small keyboard of the device 1800, and the sensor component 1807 may further detect a change in a position of the device 1800 or a component of the device 1800, presence or absence of contact between the user and the device 1800, orientation or acceleration / deceleration of the device 1800 and a change in temperature of the device 1800. The sensor component 1807 may include a proximity sensor configured to detect presence of an object nearby without any physical contact. The sensor component 1807 may also include a light sensor, such as a Complementary Metal Oxide Semiconductor (CMOS) or Charge Coupled Device (CCD) image sensor, configured for use in an imaging application. In some embodiments, the sensor component 1807 may also include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor or a temperature sensor.

[0141] The communication component 1808 is configured to facilitate wired or wireless communication between the device 1800 and another device. The device 1800 may access a communication-standard-based wireless network, such as a Wireless Fidelity (WiFi) network, a 2nd-Generation (2G) or 3rd-Generation (3G) network or a combination thereof. In an exemplary embodiment, the communication component 1808 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 1808 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.

[0142] In an exemplary embodiment, the device 1800 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.

[0143] In an exemplary embodiment, there is also provided a non-transitory computer-readable storage medium including an instruction, such as the memory 1802 including an instruction, and the instruction may be executed by the processor 1809 of the device 1800 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.

[0144] The instruction in the storage medium is executed by the processor to enable the device 1800 to execute any UAV access method.

[0145] 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: a processor; and a memory configured to store processor-executable instructions, wherein the processor is configured to: send an attach request to an MME; 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; and 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.

[0146] 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: a processor; and a memory configured to store processor-executable instructions, wherein the processor 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; query dedicated QoS configuration information of the UAV according to the IMSI of the UAV; 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; and 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.

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

[0148] 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: a processor; and a memory configured to store processor-executable instructions, wherein the processor 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; query a corresponding registration record according to the IMEI of the UAV to obtain a query result; and send a ME device identity check ACK containing the query result to the MME.

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

[0150] 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.

[0151] It will be appreciated that the present disclosure is not limited to the exact construction that has been described above and illustrated in the accompanying drawings, and that various modifications and changes may be made without departing from the scope thereof. It is intended that the scope of the present disclosure only be limited by the appended claims.

Claims

1. A method for Unmanned Aerial Vehicle, UAV, access, applied to a Mobility Management Entity, MME, and comprising: receiving (110) an attach request sent by a UAV; verifying (120) 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 (130); 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 (140).

2. The method of claim 1, wherein acquiring the IMSI of the UAV comprises: determining whether the attach request contains the IMSI of the UAV; if the attach request contains the IMSI of the UAV, reading the IMSI of the UAV from the attach request; and if the attach request does not contain the IMSI of the UAV, sending 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 receiving a user identity response sent by the UAV, the user identity response containing the IMSI of the UAV.

3. The method of claim 1, wherein acquiring the IMEI of the UAV comprises: determining whether the attach request contains the IMEI of the UAV; if the attach request contains the IMEI of the UAV, reading the IMEI of the UAV from the attach request; and if the attach request does not contain the IMEI of the UAV, sending 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 receiving a device identity response sent by the UAV, the device identity response containing the IMEI of the UAV.

4. The method of claim 1 or 3, wherein performing second verification on the device identity of the UAV according to the IMEI of the UAV comprises: sending a ME device identity check request to an Equipment Identity Register, EIR, the ME device identity check request containing the IMEI of the UAV; receiving a ME device identity check Acknowledgment, 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; if the query result indicates that the registration record of the UAV is obtained by query, determining that second verification succeeds; and if the query result indicates that the registration record of the UAV is not obtained by query, determining that second verification fails.

5. A method for Unmanned Aerial Vehicle, UAV, access, applied to a UAV, the UAV having an International Mobile Subscriber Identification Number, IMSI, and an International Mobile Equipment Identity, IMEI, the method comprising: sending (310) an attach request to a Mobility Management Entity, MME performing the method of claim 1; receiving 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; sending a user identity response to the MME, the user identity response containing the IMSI of the UAV, wherein the IMSI of the UAV is used by the MME to perform the first verification on the identity of a user using the UAV; receiving 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; and sending a device identity response to the MME, the device identity response containing the IMEI of the UAV; wherein the IMEI of the UAV is used by the MME to perform the second verification on a device identity of the UAV according to the IMEI of the UAV; wherein if both the first verification and the second verification succeed, it is determined that the MME allows access of the UAV and the MME sends the first attach response for indicating that the access is allowed to the UAV; and if at least one of the first verification or the second verification fails, it is determined that the MME rejects access of the UAV and the MME sends the second attach response for indicating that the access is rejected to the UAV; and wherein performing the first verification by the MME 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; when the first attach response for indicating that access is allowed is received from the MME, determining that the MME allows access of the UAV (320); and when the second attach response for indicating that access is rejected is received from the MME, determining that the MME rejects access of the UAV (330).

6. A device for Unmanned Aerial Vehicle, UAV, access, applied to a Mobility Management Entity, MME, and comprising: a receiving module (71), configured to receive an attach request sent by a UAV; a verification module (72), 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; wherein the verification module (72) comprises: a first acquisition submodule (81), configured to acquire an International Mobile Subscriber Identification Number, IMSI, of the UAV; a first verification submodule (82), configured to perform first verification on the identity of the user using the UAV according to the IMSI of the UAV; a second acquisition submodule (83), configured to acquire an International Mobile Equipment Identity, IMEI, of the UAV; a second verification submodule (84), configured to perform second verification on the device identity of the UAV according to the IMEI of the UAV; a first determination submodule (85), configured to, if both the first verification and the second verification succeed, determine that the verification result indicates that verification succeeds; and a second determination submodule (86), configured to, if at least one of the first verification or the second verification fails, determine that the verification result indicates that the verification fails; wherein the first verification submodule comprises: a first sending submodule, configured to send 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; a first succeeding verification submodule, configured to, 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, determine that the first verification succeeds; and a first failing verification submodule, configured to, 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, determine that the first verification fails; a first processing module (73), 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; and a second processing module (74), 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.

7. The device of claim 6, wherein the first acquisition submodule (81) comprises: a first determination submodule (91), configured to determine whether the attach request contains the IMSI of the UAV; a first processing submodule (92), configured to, if a determination result of the first determination submodule is that the attach request contains the IMSI of the UAV, read the IMSI of the UAV from the attach request; and a second processing submodule (93), configured to, if the determination result of the first determination submodule 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.

8. A device for Unmanned Aerial Vehicle, UAV, access, applied to a UAV, the UAV having an International Mobile Subscriber Identification Number, IMSI, and an International Mobile Equipment Identity, IMEI, the device comprising: a first sending module (131), configured to send an attach request to a Mobility Management Entity (MME) performing the method if claim 1; a first determination module (132), configured to, when the first attach response for indicating that access is allowed is received from the MME, determine that the MME allows access of the UAV; a second determination module (133), configured to, when the second attach response for indicating that access is rejected is received from the MME, determine that the MME rejects access of the UAV; a first receiving module (141), 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; a second sending module (142), configured to send a user identity response to the MME, the user identity response containing the IMSI of the UAV, wherein the IMSI of the UAV is used by the MME to perform the first verification on the identity of a user using the UAV; a second receiving module (151), 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; and a third sending module (152), configured to send a device identity response to the MME, the device identity response containing the IMEI of the UAV; wherein the IMEI of the UAV is used by the MME to perform second verification on a device identity of the UAV according to the IMEI of the UAV; wherein if both the first verification and the second verification succeed, it is determined that the MME allows access of the UAV and the MME sends the first attach response for indicating that the access is allowed to the UAV; and if at least one of the first verification or the second verification fails, it is determined that the MME rejects access of the UAV and the MME sends the second attach response for indicating that the access is refused to the UAV; and wherein the MME is configured to: send 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, determine 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, determine that the first verification fails.