(19)
(11)EP 3 893 594 A1

(12)EUROPEAN PATENT APPLICATION
published in accordance with Art. 153(4) EPC

(43)Date of publication:
13.10.2021 Bulletin 2021/41

(21)Application number: 18943694.2

(22)Date of filing:  17.12.2018
(51)International Patent Classification (IPC): 
H04W 76/11(2018.01)
H04W 76/14(2018.01)
(52)Cooperative Patent Classification (CPC):
H04W 76/14; H04W 76/11
(86)International application number:
PCT/CN2018/121555
(87)International publication number:
WO 2020/124321 (25.06.2020 Gazette  2020/26)
(84)Designated Contracting States:
AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR
Designated Extension States:
BA ME
Designated Validation States:
KH MA MD TN

(71)Applicant: Beijing Xiaomi Mobile Software Co., Ltd.
Beijing 100085 (CN)

(72)Inventor:
  • HONG, Wei
    Beijing 100085 (CN)

(74)Representative: Kudlek, Franz Thomas 
Dehns Germany Theresienstraße 6-8
80333 München
80333 München (DE)

  


(54)USER DEVICE PAIRING METHOD AND APPARATUS


(57) The present invention relates to a user device pairing method and apparatus. The method comprises: receiving a pairing request message, carrying a first identity identifier, sent by a first user device, the first user device being an unmanned aerial vehicle or an unmanned aerial vehicle controller; sending a query request message carrying the first identity identifier to an unmanned aerial vehicle traffic management (UTM); receiving a query response message which comprises a query result and is fed back by the UTM; when the query result comprises a second identity identifier of a second user device in a correlation between an unmanned aerial vehicle and an unmanned aerial vehicle controller, sending to the first user device a pairing response message carrying the second identity identifier, wherein when the first user device is an unmanned aerial vehicle, the second user device is an unmanned aerial vehicle controller, and when the first user device is an unmanned aerial vehicle controller, the second user device is an unmanned aerial vehicle..




Description

TECHNICAL FIELD



[0001] The present disclosure relates to the technical field of communications, and more particularly, to a method and device for pairing user devices.

BACKGROUND



[0002] In the related art, with the development of science and technology, Unmanned Aerial Vehicles (UAVs) are widely applied in fields such as aerial photography, transportation and monitoring. The UAV flies under the control of a controller. For the characteristic of long-distance flight of the UAV, it is required to perform long-distance communication between the UAV and the controller. As near-field communication modes such as Wireless Fidelity (WiFi) cannot meet the requirement of the long-distance communication, the UAV communicates with the controller through a mobile cellular network. The UAV and the controller are paired before connection. However, there is no effective solution yet on how to implement the pairing between the UAV and the controller in the mobile cellular network.

SUMMARY



[0003] The embodiments of the present disclosure provide a method and device for pairing user devices. The technical solutions are described as follows.

[0004] According to a first aspect of the embodiments of the present disclosure, a method for pairing user devices is provided, which includes operations as follows.

[0005] A pairing request message that is sent from a first user device and carries a first identity is received. The first user device includes an unmanned aerial vehicle (UAV) or a UAV controller.

[0006] A query request message carrying the first identity is sent to an Unmanned Aircraft System (UAS) Traffic Management (UTM).

[0007] A query response message that is fed back by the UTM and contains a query result is received.

[0008] When the query result includes a second identity of a second user device in correspondence between the UAV and the UAV controller, a pairing response message carrying the second identity is sent to the first user device. When the first user device is the UAV, the second user device is the UAV controller. When the first user device is the UAV controller, the second user device is the UAV.

[0009] The technical solution provided by the embodiment of the present disclosure can achieve the following beneficial effects. The embodiment provides an implementation solution that the UAV and the UAV controller are paired through a core network, thereby facilitating subsequent communication between the UAV and the UAV controller.

[0010] In an embodiment, the pairing request message is contained in attach request signaling, and the pairing response message is contained in attach accept signaling.

[0011] The technical solution provided by the embodiment of the present disclosure may achieve the following beneficial effect. The embodiment can implement a pairing process between the UAV and the UAV controller through an attach process, and implement transmission of the pairing response message through the attach accept signaling.

[0012] In an embodiment, when the query result includes query failure information, the pairing response message carries response information indicating that pairing is rejected.

[0013] The technical solution provided by the embodiment of the present disclosure can achieve the following beneficial effect. The embodiment supports a condition that the pairing is failed.

[0014] According to a second aspect of the embodiments of the present disclosure, a method for pairing user devices is provided, which is applied to a first user device, and include that operations as follows.

[0015] A pairing request message carrying a first identity is sent to a core network.

[0016] A pairing response message that is fed back by the core network and carries a second identity of a second user device is received. When the first user device is a Unmanned Aerial Vehicle (UAV), the second user device is a UAV controller. When the first user device is the UAV controller, the second user device is the UAV.

[0017] In an embodiment, the method further includes an operation as follows.

[0018] A binding request message is sent to the second user device according to the second identity.

[0019] In an embodiment, the operation that the binding request message is sent to the second user device according to the second identity includes an operation as follows.

[0020] The binding request message is sent to the second user device according to the second identity through one of the following networks: a mobile cellular network and a near-field communication network.

[0021] In an embodiment, the method further includes an operation as follows.

[0022] A pairing response message that is fed back by the core network and carries response information indicating that the pairing is rejected is received.

[0023] In an embodiment, the pairing request message is contained in attach request signaling, and the pairing response message is contained in attach accept signaling.

[0024] According to a third aspect of the embodiments of the present disclosure, a method for pairing user devices is provided, which is applied to a UTM side, and include operations as follows.

[0025] A query request message that is sent from a core network and carries a first identity of a first user device is received.

[0026] A second identity of a second user device in correspondence between a UAV and a UAV controller is queried. When the first user is the UAV, the second user device is the UAV controller, and when the first user device is the UAV controller, the second user device is the UAV.

[0027] When a query result includes the second identity, a query response message which carries the second identity is fed back to the core network.

[0028] In an embodiment, the method further includes an operation as follows.

[0029] When the query result includes query failure information, a query response message carrying the query failure information is fed back to the core network.

[0030] In an embodiment, the method further includes an operation as follows.

[0031] Correspondence, sent from a UAV manufacturer, between the UAV and the UAV controller is received

[0032] According to a fourth aspect of the embodiments of the present disclosure, a device for pairing user devices is provided, which is applied to a core network, and include a first receiving module, a first sending module, a second receiving module and a second sending module.

[0033] The first receiving module is configured to receive a pairing request message that is sent from a first user device and carries a first identity. The first user device is a UAV or a UAV controller.

[0034] The first sending module is configured to send a query request message carrying the first identity to a UTM.

[0035] The second receiving module is configured to receive a query response message that is fed back by the UTM and contains a query result.

[0036] The second sending module is configured to send, when the query result includes a second identity of a second user device in correspondence between the UAV and the UAV controller, a pairing response message carrying the second identity to the first user device. When the first user device is the UAV, the second user device is the UAV controller. When the first user device is the UAV controller, the second user device is the UAV.

[0037] In an embodiment, the pairing request message is contained in attach request signaling, and the pairing response message is contained in attach accept signaling.

[0038] In an embodiment, when the query result includes query failure information, the pairing response message carries response information indicating that pairing is rejected.

[0039] According to a fifth aspect of the embodiments of the present disclosure, a device for pairing user devices is provided, which may be applied to a first user device, and include a first sending module and a first receiving module.

[0040] The first sending module is configured to send a pairing request message carrying a first identity to a core network.

[0041] The first receiving module is configured to receive a pairing response message that is fed back by the core network and carries a second identity of a second user device. When the first user device is a UAV, the second user device is a UAV controller. When the first user device is the UAV controller, the second user device is the UAV.

[0042] In an embodiment, the device further includes a second sending module.

[0043] The second sending module is configured to send a binding request message to the second user device according to the second identity.

[0044] In an embodiment, the second sending module further includes a sending submodule.

[0045] The second sending submodule is configured to send the binding request message to the second user device according to the second identity through one of the following networks: a mobile cellular network and a near-field communication network.

[0046] In an embodiment, the device further includes a second receiving module.

[0047] The second receiving module is configured to receive a pairing response message that is fed back by the core network and carries response information indicating that the pairing is rejected.

[0048] In an embodiment, the pairing request message is contained in attach request signaling; and the pairing response message is contained in attach accept signaling.

[0049] According to a sixth aspect of the embodiments of the present disclosure, a device for pairing user devices is provided, which is applied to a UTM side, and include a first receiving module, a querying module and a first sending module.

[0050] The first receiving module is configured to receive a query request message sent from a core network and carrying a first identity of a first user device.

[0051] The querying module is configured to query a second identity of a second user device in correspondence between a UAV and a UAV controller. When the first user is the UAV, the second user device is the UAV controller, and when the first user device is the UAV controller, the second user device is the UAV.

[0052] The first sending module is configured to feed, when a query result includes the second identity, a query response message carrying the second identity back to the core network.

[0053] In an embodiment, the device further includes a second sending module.

[0054] The second sending module is configured to feed, when the query result includes query failure information, a query response message carrying the query failure information back to the core network.

[0055] In an embodiment, the device further includes a second receiving module.

[0056] The second receiving module is configured to receive correspondence, sent from a UAV manufacturer, between the UAV and the UAV controller.

[0057] According to a seventh aspect of the embodiments of the present disclosure, a device for pairing user devices is provided, which may include a processor; and a memory configured to store a processor-executable instruction.

[0058] The processor is configured to: receive a pairing request message that is sent from a first user device and carries a first identity, where the first user device is a UAV or a UAV controller; send a query request message carrying the first identity to a UTM; receive a query response message fed back by the UTM and containing a query result; and send, when the query result includes a second identity of a second user device in the correspondence between the UAV and the UAV controller, a pairing response message carrying the second identity to the first user device. When the first user device is the UAV, the second user device is the UAV controller. When the first user device is the UAV controller, the second user device is the UAV.

[0059] According to an eighth aspect of the embodiments of the present disclosure, a device for pairing user devices is provided, which may include: a processor; and a memory configured to store a processor-executable instruction.

[0060] The processor is configured to: send a pairing request message carrying a first identity to a core network; and receive a pairing response message that is fed back by the core network and carries a second identity of a second user device. When the first user device is a UAV, the second user device is a UAV controller. When the first user device is the UAV controller, the second user device is the UAV.

[0061] According to an ninth aspect of the embodiments of the present disclosure, a device for pairing user devices is provided, which may include: a processor; and a memory configured to store a processor-executable instruction.

[0062] The processor is configured to: receive a query request message that is sent from a core network and carries a first identity of a first user device; query a second identity of a second user device in a correspondence between a UAV and a UAV controller, where when the first user is the UAV, the second user device is the UAV controller, and when the first user device is the UAV controller, the second user device is the UAV; feed, when a query result includes the second identity, a query response message carrying the second identity back to the core network.

[0063] According to a tenth aspect of the embodiments of the present disclosure, a computer-readable storage medium is provided, on which a computer instruction is stored. The instruction is executed by a processor to implement the method of the core network.

[0064] According to an eleventh aspect of the embodiments of the present disclosure, a computer-readable storage medium is provided, on which a computer instruction is stored. The instruction is executed by a processor to implement the method of the user device.

[0065] According to a twelfth aspect of the embodiments of the present disclosure, a computer-readable storage medium is provided, on which a computer instruction is stored. The instruction is executed by a processor to implement the method of the UTM side.

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

BRIEF DESCRIPTION OF THE DRAWINGS



[0067] 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 showing a method for pairing user devices according to an exemplary embodiment.

FIG. 2 is a flow chart showing a method for pairing user devices according to an exemplary embodiment.

FIG. 3 is a flow chart showing a method for pairing user devices according to an exemplary embodiment.

FIG. 4 is a flow chart showing a method for pairing user devices according to an exemplary embodiment.

FIG. 5 is a flow chart showing a method for pairing user devices according to an exemplary embodiment.

FIG. 6 is a block diagram illustrating a device for pairing user devices according to an exemplary embodiment.

FIG. 7 is a block diagram illustrating a device for pairing user devices according to an exemplary embodiment.

FIG. 8 is a block diagram illustrating a device for pairing user devices according to an exemplary embodiment.

FIG. 9 is a block diagram illustrating a second sending module according to an exemplary embodiment.

FIG. 10 is a block diagram illustrating a device for pairing user devices according to an exemplary embodiment.

FIG. 11 is a block diagram illustrating a device for pairing user devices according to an exemplary embodiment.

FIG. 12 is a block diagram illustrating a device for pairing user devices according to an exemplary embodiment.

FIG. 13 is a block diagram illustrating a device for pairing user devices according to an exemplary embodiment.

FIG. 14 is a block diagram illustrating a device applied for pairing user devices according to an exemplary embodiment.

FIG. 15 is a block diagram illustrating a device applied for pairing user devices according to an exemplary embodiment.


DETAILED DESCRIPTION



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

[0069] In the related art, with the development of science and technology, Unmanned Aerial Vehicles (UAVs) are widely applied in fields such as aerial photography, transportation and monitoring. The UAV flies under the control of a controller. For the characteristic of long-distance flight of the UAV, it is required to perform long-distance communication between the UAV and the controller. As near-field communication modes such as Wireless Fidelity (WiFi) cannot meet the requirement of the long-distance communication, the UAV communicates with the controller through a mobile cellular network. The UAV and the controller are paired before connection. However, there is no effective solution yet on how to implement the pairing between the UAV and the controller in the mobile cellular network.

[0070] In order to solve the above-mentioned problem, the embodiments provide an implementation solution that the UAV and the UAV controller are paired through a mobile cellular network. The mobile cellular network has characteristics of wide coverage and long-distance communication, thereby facilitating long-distance transmission between the UAV and the UAV controller.

[0071] FIG. 1 is a flow chart showing a method for pairing user devices according to an exemplary embodiment. The method for pairing user devices is applied to a device in a core network. As shown in FIG. 1, the method may include the following operations 101-104.

[0072] At operation 101, a pairing request message that is sent from a first user device and carries a first identity is received. The first user device includes a UAV or a UAV controller.

[0073] At operation 102, a query request message carrying the first identity is sent to a UTM.

[0074] At operation 103, a query response message that is fed back by the UTM and contains a query result is received.

[0075] At operation 104, when the query result includes a second identity of a second user device in a correspondence between the UAV and the UAV controller, a pairing response message carrying the second identity is sent to the first user device. When the first user device is the UAV, the second user device is the UAV controller, and when the first user device is the UAV controller, the second user device is the UAV.

[0076] In the embodiment, when the first user is the UAV, the second user device is the UAV controller, and when the first user device is the UAV controller, the second user device is the UAV.

[0077] Either the UAV or the UAV controller may automatically search a mobile cellular network after being started or restarted, and access to the mobile cellular network and send a pairing request message to the core network to request acquiring identity information of a peer device (the second user device), to complete a pairing process. Both the UAV and the UAV controller may respectively send the pairing request message to the core network, that is, the above process is executed for two times.

[0078] The correspondence between the UAV and the UAV controller is stored in the UTM. The UAV operator or the UAV manufacturer or the like may store the correspondence between the UAV and the UAV controller into the UTM in advance. As the UTM is not the device in the core network, the connection between the core network and the UTM is established in the embodiment. The core network may send a query request message to the UTM, so as to request querying a second identity corresponding to the first identity. The core network sends the queried second identity to the first user device, for completing the pairing between the first user device and the second user device. The first user device may communicate with the second user device subsequently through the mobile cellular network.

[0079] The core network may obtain the first identity through the pairing request message. The core network obtains the pairing request of the first user device on one hand, may further perform identity identification on the first identity on the other hand to determine whether the first identity conforms to an identity rule between the UAV and the UAV controller. The core network determines that the pairing request is an legal pairing request if the first identity conforms to the identity rule.

[0080] In an embodiment, the pairing request message is contained in attach request signaling, and the pairing response message is contained in attach accept signaling.

[0081] The pairing process between the UAV and the UAV controller can be implemented through an attach process in the embodiment. The pairing request is implemented through the attach request signaling, and the pairing response is implemented through the attach accept signaling, thereby saving network resources without increasing additional transmission process.

[0082] In an embodiment, when the query result includes query failure information, the pairing response message carries response information indicating that pairing is rejected.

[0083] In the embodiment, the UTM may not find the second identity corresponding to the first identity, that is, the query is failed. The core network notifies, through the pairing response message, the first user device that the pairing cannot be completed.

[0084] The foregoing describes the implementation process of the core network. Correspondingly, there are also improvement at the user device. The implementation process of the user device is described below.

[0085] FIG. 2 is a flow chart showing a method for pairing user devices according to an exemplary embodiment. The method for pairing user devices is applied to a terminal. The terminal may be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a gaming console, a tablet, a medical device, exercise equipment, a Personal Digital Assistant (PDA), and the like. As shown in FIG. 2, the method may include the following operations 201-202.

[0086] At operation 201, a pairing request message carrying a first identity is sent to a core network.

[0087] At operation 202, a pairing response message that is fed back by the core network and carries a second identity of a second user device is received. When the first user device is a UAV, the second user device is a UAV controller, and when the first user device is the UAV controller, the second user device is the UAV.

[0088] In an embodiment, the above process may be implemented by the UAV or the UAV controller. Alternatively, both the UAV and the UAV controller may serve as the first user device to respectively execute the above process.

[0089] The first user device automatically searches the mobile cellular network after being started or restarted, accesses to the mobile cellular network, and sends a pairing request message to the core network to request acquiring identity information of a peer device (the second user device), and receives the second identity fed back by the core network, for completing the pairing process.

[0090] In an embodiment, the method may further include operation A.

[0091] At operation A, a binding request message is sent to the second user device according to the second identity.

[0092] After completing pairing, the first user device may directly communicate with the second user device to complete the binding process, and may further perform subsequent communication.

[0093] In an embodiment, operation A may include operation A1.

[0094] At operation A1, the binding request message is sent to the second user device according to the second identity through one of the following networks: a mobile cellular network and a near-field communication network.

[0095] In the embodiment, the first user device and the second user device may complete the binding process by continuing using the mobile cellular network, or through the near-field communication network (such as WiFi).

[0096] In an embodiment, the method may further include operation B.

[0097] At operation B, a pairing response message that is fed back by the core network and carries response information indicating that pairing is rejected is received.

[0098] In the embodiment, the first user device may receive the pairing response message indicating that pairing is rejected, i.e., the pairing between the first user device and the second user device is failed.

[0099] In an embodiment, the pairing request message is contained in attach request signaling, and the pairing response message is contained in attach accept signaling.

[0100] The pairing process between the UAV and the UAV controller can be implemented through an attach process in the embodiment. The pairing request is implemented through the attach request signaling, and the pairing response is implemented through the attach accept signaling, thereby saving network resources without increasing additional transmission process.

[0101] An implementation process of the user device is described below in detail with the embodiment.

[0102] FIG. 3 is a flow chart showing a method for pairing user devices according to an exemplary embodiment. The method for pairing user devices is applied in a terminal. The terminal may be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a gaming console, a tablet, a medical device, exercise equipment, a PDA, and the like. As shown in FIG. 2, the method may include the following operations 301-303.

[0103] At operation 301, a pairing request message carrying a first identity is sent to a core network.

[0104] At operation 302, a pairing response message that is fed back by the core network and carries a second identity of a second user device is received. When the first user device is a UAV, the second user device is a UAV controller, and when the first user device is the UAV controller, the second user device is the UAV.

[0105] At operation 303, a binding request message is sent to the second user device according to the second identity.

[0106] The foregoing describes the implementation process of the core network and the user device. Correspondingly, there are also improvement at the UTM side. Hereinafter, the implementation process of the UTM side is described.

[0107] FIG. 4 is a flow chart showing a method for pairing user devices according to an exemplary embodiment. The method for pairing user devices is applied to a UTM. As shown in FIG. 4, the method may include the following operations 401-403.

[0108] At operation 401, a query request message that is sent from a core network and carries a first identity of a first user device is received.

[0109] At operation 402, a second identity of a second user device in correspondence between a UAV and a UAV controller is queried. When the first user is the UAV, the second user device is the UAV controller, and when the first user device is the UAV controller, the second user device is the UAV.

[0110] At operation 403, when a query result includes the second identity, a query response message carrying the second identity is fed back to the core network.

[0111] In the embodiment, the correspondence between the UAV and the UAV controller is stored in the UTM. The UAV operator or the UAV manufacturer or the like may store the correspondence between the UAV and the UAV controller into the UTM in advance. As the UTM is not the device in the core network, the connection between the core network and the UTM is established in the embodiment. The core network may send a query request message to the UTM, to request querying the second identity corresponding to the first identity. Upon the reception of the query request message, the UTM queries the correspondence between the UAV and the UAV controller to the UTM, to obtain the second identity corresponding to the first identity and feed the query result back to the core network. The process helps the core network complete the pairing and identity authentication process between the UAV and the UAV controller.

[0112] In an embodiment, the method may further include operation C.

[0113] At operation C, when the query result includes query failure information, a query response message carrying the query failure information is fed back to the core network.

[0114] In the embodiment, when the query is failed, the UTM may feed the query response message carrying the query failure information back to the core network.

[0115] In an embodiment, the method may further include operation D.

[0116] At operation D, the correspondence sent from a UAV manufacturer, between the UAV and the UAV controller is received.

[0117] In the embodiment, the correspondence between the UAV and the UAV controller is stored in the UTM. The UAV operator or the UAV manufacturer or the like may pre-store the correspondence between the UAV and the UAV controller into the UTM.

[0118] The implementation process is described in combination with the core network, the user device and the UTM.

[0119] FIG. 5 is a flow chart showing a method for pairing user devices according to an exemplary embodiment. As shown in FIG. 5, the method may include the following operations 501-505.

[0120] At operation 501, a first user device sends a pairing request message carrying a first identity to a core network.

[0121] At operation 502, the core network sends a pairing request message carrying the first identity to a UTM.

[0122] At operation 503, the UTM queries a second identity of a second user device in a correspondence between a UAV and a UAV controller.

[0123] At operation 504, when a query result includes the second identity, the UTM feeds a query response message carrying the second identity back to the core network.

[0124] At operation 505, the core network sends the pairing response message carrying the second identity to the first user device.

[0125] The above embodiments may be combined freely according to an actual need.

[0126] The device embodiments of the present disclosure are set forth hereinafter, and may be configured to execute the method embodiments of the present disclosure.

[0127] FIG. 6 is a block diagram illustrating a device for pairing user devices according to an exemplary embodiment. The device may be implemented through software, hardware or a combination thereof to form a part or all of the electronic device. The device for pairing user devices is applied to a core network. Referring to FIG. 6, the device for pairing user devices may include a first receiving module 601, a first sending module 602, a second receiving module 603 and a second sending module 604.

[0128] The first receiving module 601 is configured to receive a pairing request message that is sent from a first user device and carries a first identity. The first user device includes a UAV or a UAV controller.

[0129] The first sending module 602 is configured to send a query request message carrying the first identity to a UTM.

[0130] The second receiving module 603 is configured to receive a query response message that is fed back by the UTM and contains a query result.

[0131] The second sending module 604 is configured to send, when the query result includes a second identity of a second user device in a correspondence between the UAV and the UAV controller, a pairing response message carrying the second identity to the first user device. When the first user device is the UAV, the second user device is the UAV controller, and when the first user device is the UAV controller, the second user device is the UAV.

[0132] In an embodiment, the pairing request message is contained in attach request signaling, and the pairing response message is contained in attach accept signaling.

[0133] In an embodiment, when the query result includes query failure information, the pairing response message carries response information indicating that the pairing is rejected.

[0134] FIG. 7 is a block diagram illustrating a device for pairing user devices according to an exemplary embodiment. The device may be implemented through software, hardware or a combination thereof to form a part or all of the electronic device. The device for pairing user devices is applied to a first user device. Referring to FIG. 7, the device for pairing user devices may include a first sending module 701 and a first receiving module 702.

[0135] The first sending module 701 is configured to send a pairing request message carrying a first identity to a core network.

[0136] The first receiving module 702 is configured to receive a pairing response message that is fed back by the core network and carries a second identity of a second user device. When the first user device is a UAV, the second user device is a UAV controller, and when the first user device is the UAV controller, the second user device is the UAV.

[0137] In an embodiment, as shown in FIG. 8, the device may further include a second sending module 801.

[0138] The second sending module 801 is configured to send a binding request message to the second user device according to the second identity.

[0139] In an embodiment, as shown in FIG. 9, the second sending module 801 may further include a sending submodule 901.

[0140] The second sending submodule 901 is configured to send the binding request message to the second user device according to the second identity through one of the following networks: a mobile cellular network and a near-field communication network.

[0141] In an embodiment, as shown in FIG. 10, the device may further include a second receiving module 1001.

[0142] The second receiving module 1001 is configured to receive a pairing response message that is fed back by the core network and carries response information indicating that pairing is rejected.

[0143] In an embodiment, the pairing request message is contained in attach request signaling; and the pairing response message is contained in attach accept signaling.

[0144] FIG. 11 is a block diagram illustrating a device for pairing user devices according to an exemplary embodiment. The device may be implemented through software, hardware or a combination thereof to form a part or all of the electronic device. The device for pairing user devices is applied to a UTM side. Referring to FIG. 11, the device for pairing user devices may include a first receiving module 1101, a querying module 1102 and a first sending module 1103.

[0145] The first receiving module 1101 is configured to receive a query request message that is sent from a core network and carries a first identity of a first user device.

[0146] The querying module 1102 is configured to query a second identity of a second user device in a correspondence between a UAV and a UAV controller. When the first user is the UAV, the second user device is the UAV controller, and when the first user device is the UAV controller, the second user device is the UAV.

[0147] The first sending module 1103 is configured to feed, when a query result includes the second identity, a query response message carrying the second identity back to the core network.

[0148] In an embodiment, as shown in FIG. 12, the device may further include a second sending module 1201.

[0149] The second sending module 1201 is configured to feed, when the query result includes query failure information, a query response message carrying the query failure information back to the core network.

[0150] In an embodiment, as shown in FIG. 13, the device may further include a second receiving module 1301.

[0151] The second receiving module 1301 is configured to receive the correspondence, sent from a UAV manufacturer, between the UAV and the UAV controller.

[0152] For the device in the above embodiments, the specific mode for the operation executed by each module has been described in detail in the embodiments related to the method, and is not elaborated herein.

[0153] FIG. 14 is a block diagram illustrating a device for pairing user devices according to an exemplary embodiment. For example, the device 1400 may be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a gaming console, a tablet, a medical device, exercise equipment, a PDA, and the like.

[0154] The device 1400 may include one or more of the following components: a processing component 1402, a memory 1404, a power component 1406, a multimedia component 1408, an audio component 1410, an Input/Output (I/O) interface 1414, a sensor component 1414, and a communication component 1416.

[0155] The processing component 1402 typically controls overall operations of the device 1400, such as the operations associated with display, telephone calls, data communications, camera operations, and recording operations. The processing component 1402 may include one or more processors 1420 to execute instructions to perform all or part of the operations in the above described methods. Moreover, the processing component 1402 may include one or more modules which facilitate interaction between the processing component 1402 and other components. For instance, the processing component 1402 may include a multimedia module to facilitate interaction between the multimedia component 1408 and the processing component 1402.

[0156] The memory 1404 is configured to store various types of data to support the operation of the device 1400. Examples of such data include instructions for any applications or methods operated on the device 1400, contact data, phonebook data, messages, pictures, video, etc. The memory 1404 may be implemented by using 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, a magnetic or optical disk.

[0157] The power component 1406 provides power to various components of the device 1400. The power component 1406 may include a power management system, one or more power sources, and any other components associated with the generation, management, and distribution of power in the device 1400.

[0158] The multimedia component 1408 includes a screen providing an output interface between the device 1400 and the 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 sense a period of time and a pressure associated with the touch or swipe action. In some embodiments, the multimedia component 1408 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 1400 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 focus and optical zoom capability.

[0159] The audio component 1410 is configured to output and/or input audio signals. For example, the audio component 1410 includes a Microphone (MIC) configured to receive an external audio signal when the device 1400 is in an 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 1404 or transmitted via the communication component 1416. In some embodiments, the audio component 1410 further includes a speaker configured to output audio signals.

[0160] The I/O interface 1414 provides an interface between the processing component 1402 and peripheral interface modules. The peripheral interface modules may be a keyboard, a click wheel, buttons, and the like. The buttons may include, but are not limited to, a home button, a volume button, a starting button, and a locking button.

[0161] The sensor component 1414 includes one or more sensors to provide status assessments of various aspects of the device 1400. For instance, the sensor component 1414 may detect an on/off status of the device 1400 and relative positioning of components. For example, the component is a display and small keyboard of the device 1400, and the sensor component 1414 may further detect a change in a position of the device 1400 or a component of the device 1400, presence or absence of contact between the user and the device 1400, orientation or acceleration/deceleration of the device 1400 and a change in temperature of the device 1400. The sensor component 1414 may include a proximity sensor, configured to detect the presence of nearby objects without any physical contact. The sensor component 1414 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 1414 may also include an accelerometer sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.

[0162] The communication component 1416 is configured to facilitate wired or wireless communication between the device 1400 and other devices. The device 1400 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 one exemplary embodiment, the communication component 1416 receives a broadcast signal or broadcast associated information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, the communication component 1416 further includes a near field communication (NFC) module to facilitate short-range communications. 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 other technologies.

[0163] In exemplary embodiments, the device 1400 may be implemented with 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, for performing the above described methods.

[0164] In an exemplary embodiment, a non-temporary computer readable storage medium including an instruction is further provided, for example, the memory 1404 including the instruction; and the instruction may be executed by the processor 1420 of the device 1400 to complete the above method. For example, the non-transitory computer-readable storage medium may be a Read Only Memory (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.

[0165] In an exemplary embodiment, a device for pairing user devices is provided, which includes: a processor; and a memory, configured to store a processor-executable instruction.

[0166] The processor is configured to: send a pairing request message carrying a first identity to a core network; and receive a pairing response message fed back by the core network and carrying a second identity of a second user device. When the first user device is a UAV, the second user device is a UAV controller, and when the first user device is the UAV controller, the second user device is the UAV.

[0167] The processor may further be configured to: send a binding request message to the second user device according to the second identity.

[0168] The processor may further be configured to, regarding sending the binding request message to the second user device according to the second identity, send the binding request message to the second user device according to the second identity through one of the following networks: a mobile cellular network and a near-field communication network.

[0169] The processor may further be configured to receive a pairing response message fed back by the core network and carrying response information indicating that pairing is rejected.

[0170] The processor may further be configured to contain the pairing request message in attach request signaling; and contain the pairing response message in attach accept signaling.

[0171] A computer-readable storage medium is provided, an instruction in the storage medium when executed by a processor of a device, enables the device to execute the method for pairing user devices. The method may include the following operations.

[0172] A pairing request message carrying a first identity is sent to a core network.

[0173] A pairing response message fed back by the core network and carrying a second identity of a second user device is received. When the first user device is a UAV, the second user device is a UAV controller, and when the first user device is the UAV controller, the second user device is the UAV.

[0174] The instruction in the storage medium may further include sending a binding request message to the second user device according to the second identity.

[0175] The instruction in the storage medium may further include, regarding sending the binding request message to the second user device according to the second identity, sending a binding request message to the second user device according to the second identity through one of the following networks: a mobile cellular network and a near-field communication network.
The instruction in the storage medium may further include: receiving a pairing response message fed back by the core network and carrying response information indicating that pairing is rejected.
The instruction in the storage medium may further include: containing the pairing request message in attach request signaling; and containing the pairing response message in attach accept signaling.

[0176] FIG. 15 is a block diagram illustrating a device 1500 for synchronizing data according to an exemplary embodiment. For example, the device 1500 may be provided as a computer. Referring to Fig. 15, the device 1500 includes a processing component 1522, which further includes one or more processors, and a memory resource represented by a memory 1532 and configured to store an instruction that may be executed by the processing component 1522, such as an application program. The application program stored in the memory 1532 may include one or more modules, with each module corresponding to one set of instructions. In addition, the processing component 1522 is configured to execute the instruction to the above method for synchronizing data.

[0177] The device 1500 may further include a power component 1526, configured to execute power management of the device 1500, a wired or wireless network interface 1550 configured to connect the device 1500 to the network, and an I/O interface 1558. The device 1500 may be operated based on an operating system stored in the memory 1532, for example, Windows ServerTM, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM or the like.

[0178] In an exemplary embodiment, a device for pairing user devices is provided, which may include: a processor; and a memory, configured to store a processor-executable instruction.

[0179] The processor is configured to: receive a pairing request message sent from a first user device and carrying a first identity, the first user device being a UAV or a UAV controller; send a query request message carrying the first identity to a UTM; receive a query response message fed back by the UTM and including a query result; and send, when the query result includes a second identity of a second user device in a correspondence between the UAV and the UAV controller, a pairing response message carrying the second identity to the first user device. When the first user device is the UAV, the second user device is the UAV controller, and when the first user device is the UAV controller, the second user device is the UAV.

[0180] The processor may further be configured to enable the pairing request message to be contained in attach request signaling; and the pairing response message to be contained in attach accept signaling.

[0181] The processor may further be configured to: enable, when the query result includes query failure information, the pairing response message to carry response information indicating that pairing is rejected.

[0182] A computer-readable storage medium is provided. An instruction in the storage medium, when executed by a processor of a device, enables the device to execute the above method for pairing user devices. The method may include the following operations.

[0183] A pairing request message sent from a first user device and carrying a first identity is received. The first user device includes a UAV or a UAV controller.

[0184] A query request message carrying the first identity is sent to a UTM.

[0185] A query response message fed back by the UTM and containing a query result is received.

[0186] When the query result includes a second identity of a second user device in a correspondence between the UAV and the UAV controller, a pairing response message carrying the second identity is sent to the first user device. When the first user device is the UAV, the second user device is the UAV controller, and when the first user device is the UAV controller, the second user device is the UAV.

[0187] The instruction in the storage medium may further include containing the pairing request message in attach request signaling; and containing the pairing response message in attach accept signaling.

[0188] The instruction in the storage medium may further include, when the query result includes query failure information, the pairing response message carries response information indicating that the pairing is rejected.

[0189] In an exemplary embodiment, a device for pairing user devices is provided, which may include: a processor; and a memory, configured to store a processor-executable instruction.

[0190] The processor is configured to: receive a query request message sent from a core network and carrying a first identity of a first user device; query a second identity of a second user device in a correspondence between a UAV and a UAV controller, wherein when the first user is the UAV, the second user device is the UAV controller, where when the first user device is the UAV controller, the second user device is the UAV; and feed, when a query result includes the second identity, a query response message carrying the second identity back to the core network.

[0191] The processor may further be configured to: when the query result includes query failure information, feed a query response message carrying the query failure information back to the core network.

[0192] The processor may further be configured to receive the correspondence, sent from a UAV manufacturer, between the UAV and the UAV controller.

[0193] A computer-readable storage medium is provided. An instruction in the storage medium, when executed by a processor of a device, enables the device to execute the above method for pairing user devices. The method may include the following operations.

[0194] A query request message sent from a core network and carrying a first identity of a first user device is received.

[0195] A second identity of a second user device in a correspondence between a UAV and a UAV controller is queried. When the first user is the UAV, the second user device is the UAV controller, and when the first user device is the UAV controller, the second user device is the UAV.

[0196] When a query result includes the second identity, a query response message carrying the second identity is fed back to the core network.

[0197] The instruction in the storage medium may further include: when the query result includes query failure information, feeding a query response message carrying the query failure information back to the core network.

[0198] The instruction in the storage medium may further include: receiving the correspondence, sent from a UAV manufacturer, between the UAV and the UAV controller.

[0199] Other embodiments of the present disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the present disclosure disclosed here. The disclosure is intended to cover any variations, uses, or adaptations of the disclosure conforming to 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 disclosure being indicated by the following claims.

[0200] 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. The scope of the present disclosure is only limited by the appended claims.


Claims

1. A method for pairing user devices, applied to a core network, and comprising:

receiving a pairing request message that is sent from a first user device and carries a first identity, wherein the first user device comprises a Unmanned Aerial Vehicle (UAV) or a UAV controller;

sending a query request message carrying the first identity to an Unmanned Aircraft System (UAS) Traffic Management (UTM);

receiving a query response message that is fed back by the UTM and contains a query result; and

sending, when the query result comprises a second identity of a second user device in a correspondence between the UAV and the UAV controller, a pairing response message carrying the second identity to the first user device, wherein when the first user device is the UAV, the second user device is the UAV controller, and while the first user device is the UAV controller, the second user device is the UAV.


 
2. The method of claim 1, wherein the pairing request message is contained in attach request signaling, and the pairing response message is contained in attach accept signaling.
 
3. The method of claim 1, wherein when the query result comprises query failure information, the pairing response message carries response information indicating that pairing is rejected.
 
4. A method for pairing user devices, applied to a first user device, and comprising:

sending a pairing request message carrying a first identity to a core network; and

receiving a pairing response message that is fed back by the core network and carries a second identity of a second user device, wherein when the first user device is a Unmanned Aerial Vehicle (UAV), the second user device is a UAV controller, and when the first user device is the UAV controller, the second user device is the UAV.


 
5. The method of claim 4, further comprising:
sending a binding request message to the second user device according to the second identity.
 
6. The method of claim 5, wherein sending the binding request message to the second user device according to the second identity comprises:
sending the binding request message to the second user device according to the second identity through one of following networks: a mobile cellular network and a near-field communication network.
 
7. The method of claim 4, further comprising:
receiving a pairing response message that is fed back by the core network and carries response information indicating that pairing is rejected.
 
8. The method of claim 4, wherein the pairing request message is contained in attach request signaling, and the pairing response message is contained in attach accept signaling.
 
9. A method for pairing user devices, applied to an Unmanned Aircraft System (UAS) Traffic Management (UTM), and comprising:

receiving a query request message that is sent from a core network and carries a first identity of a first user device;

querying a second identity of a second user device in a correspondence between an Unmanned Aerial Vehicle (UAV) and a UAV controller, wherein when the first user is the UAV, the second user device is the UAV controller, and while the first user device is the UAV controller, the second user device is the UAV; and

feeding, when a query result comprises the second identity, a query response message carrying the second identity back to the core network.


 
10. The method of claim 9, further comprising:
feeding, when the query result comprises query failure information, a query response message carrying the query failure information back to the core network.
 
11. The method of claim 9, further comprising:
receiving the correspondence, sent from a UAV manufacturer, between the UAV and the UAV controller.
 
12. A device for pairing user devices, applied to a core network, and comprising:

a first receiving module, configured to receive a pairing request message that is sent from a first user device and carries a first identity, wherein the first user device comprises a Unmanned Aerial Vehicle (UAV) or a UAV controller;

a first sending module, configured to send a query request message carrying the first identity to an Unmanned Aircraft System (UAS) Traffic Management (UTM);

a second receiving module, configured to receive a query response message that is fed back by the UTM and contains a query result; and

a second sending module, configured to send, when the query result comprises a second identity of a second user device in a correspondence between the UAV and the UAV controller, a pairing response message carrying the second identity to the first user device, wherein when the first user device is the UAV, the second user device is the UAV controller, and while the first user device is the UAV controller, the second user device is the UAV.


 
13. The device of claim 12, wherein the pairing request message is contained in attach request signaling, and the pairing response message is contained in attach accept signaling.
 
14. The device of claim 12, wherein when the query result comprises query failure information, the pairing response message carries response information indicating that pairing is rejected.
 
15. A device for pairing user devices, applied to a first user device, and comprising:

a first sending module, configured to send a pairing request message carrying a first identity to a core network; and

a first receiving module, configured to receive a pairing response message that is fed back by the core network and carries a second identity of a second user device, wherein when the first user device is a Unmanned Aerial Vehicle (UAV), the second user device is a UAV controller, and when the first user device is the UAV controller, the second user device is the UAV.


 
16. The device of claim 15, further comprising:
a second sending module, configured to send a binding request message to the second user device according to the second identity.
 
17. The device of claim 16, wherein the second sending module comprises:
a sending submodule, configured to send the binding request message to the second user device according to the second identity through one of following networks: a mobile cellular network and a near-field communication network.
 
18. The device of claim 15, further comprising:
a second receiving module, configured to receive a pairing response message that is fed back by the core network and carries response information indicating that pairing is rejected.
 
19. The device of claim 15, wherein the pairing request message is contained in attach request signaling, and the pairing response message is contained in attach accept signaling.
 
20. A device for pairing user devices, applied to an Unmanned Aircraft System (UAS) Traffic Management (UTM) side, and comprising:

a first receiving module, configured to receive a query request message that is sent from a core network and carries a first identity of a first user device;

a querying module, configured to query a second identity of a second user device in a correspondence between an Unmanned Aerial Vehicle (UAV) and a UAV controller, wherein when the first user is the UAV, the second user device is the UAV controller, and when the first user device is the UAV controller, the second user device is the UAV; and

a first sending module, configured to feed, when a query result comprises the second identity, a query response message carrying the second identity back to the core network.


 
21. The device of claim 20, further comprising:
a second sending module, configured to feed, when the query result comprises query failure information, a query response message carrying the query failure information back to the core network.
 
22. The device of claim 20, further comprising:
a second receiving module, configured to receive the correspondence, sent from a UAV manufacturer, between the UAV and the UAV controller.
 
23. A device for pairing user devices, comprising:

a processor; and

a memory configured to store a processor-executable instruction,

wherein the processor is configured to:

receive a pairing request message that is sent from a first user device and carries a first identity, wherein the first user device comprises a Unmanned Aerial Vehicle (UAV) or a UAV controller;

send a query request message carrying the first identity to an Unmanned Aircraft System (UAS) Traffic Management (UTM);

receive a query response message that is fed back by the UTM and contains a query result; and

send, when the query result comprises a second identity of a second user device in a correspondence between the UAV and the UAV controller, a pairing response message carrying the second identity to the first user device, wherein when the first user device is the UAV, the second user device is the UAV controller, and while the first user device is the UAV controller, the second user device is the UAV.


 
24. A device for pairing user devices, comprising:

a processor; and

a memory configured to store a processor-executable instruction,

wherein the processor is configured to:

a pairing request message carrying a first identity to a core network; and

receive a pairing response message that is fed back by the core network and carries a second identity of a second user device, wherein when the first user device is a Unmanned Aerial Vehicle (UAV), the second user device is a UAV controller, and while the first user device is the UAV controller, the second user device is the UAV.


 
25. A device for pairing user devices, comprising:

a processor; and

a memory configured to store a processor-executable instruction,

wherein the processor is configured to:

receiving a query request message that is sent from a core network and carries a first identity of a first user device;

query a second identity of a second user device in a correspondence between an Unmanned Aerial Vehicle (UAV) and a UAV controller, wherein when the first user is the UAV, the second user device is the UAV controller, and while the first user device is the UAV controller, the second user device is the UAV; and

feed, when a query result comprises the second identity, a query response message carrying the second identity back to the core network.


 
26. A computer-readable storage medium having stored thereon a computer instruction, which, when executed by a processor, implements the method of any one of claims 1 to 3.
 
27. A computer-readable storage medium having stored thereon a computer instruction, which, when executed by a processor, implements the method of any one of claims 4 to 8.
 
28. A computer-readable storage medium having stored thereon a computer instruction, which, when executed by a processor, implements the method of any one of claims 9 to 11.
 




Drawing

















































Search report