Communication method and device performed by an unmanned aerial system

Abstract

A method performed by at least one processor in an unmanned aerial system (UAS) includes: sending a first registration request to a UAS service provider (USS) implemented on at least one server to register a first remote identification (RID) corresponding to the UAS with the USS; receiving from the USS an indication that the first RID is a duplicate RID registered with the USS; determining a second RID corresponding to the UAS based on the first RID; and sending a second registration request to the USS to register the second RID.

Description

[0001] Cross - reference to related applications

[0002] This application claims the benefit of priority to U.S. Provisional Application No. 63 / 121,834, filed on December 4, 2020, and U.S. Application No. 17 / 489,016, filed on September 29, 2021. The disclosures of these two U.S. applications are hereby incorporated by reference in their entireties. Technical field

[0003] The present disclosure generally relates to the technical field of unmanned driving, and more particularly, to a method executed by at least one processor in an unmanned aerial system and a device in an unmanned aerial system. Background art

[0004] An unmanned aerial vehicle (UAV) can have an identification (ID) associated with it. In fact, some UAVs are required to have an ID before flight. For example, in North America, the Federal Aviation Administration (FAA) has established regulations to ensure that all UAVs have some legal flight identification, and such identification is called the remote identification (RID) of the drone or UAV.

[0005] Due to various reasons, including manufacturing errors and registration process errors, the RID may be reused for two or more unmanned aerial systems (UAS). This may result in registration failure when these UASs attempt to register with a UAS Service Supplier (USS), and the registration failure will prevent the UAV with the duplicate RID from taking off. Since these registration types are statically assigned, the UAS cannot recover from this situation.

[0006] Therefore, the technical problem to be solved by the present invention is how to detect and recover UASs with duplicate RIDs. Summary of the invention

[0007] According to one or more embodiments, a method is provided that is executed by at least one processor in an unmanned aerial system (UAS). The method includes: sending a first registration request to a UAS Service Supplier (USS) implemented on at least one server to register a first remote identification (RID) corresponding to the UAS with the USS; receiving from the USS an indication that the first RID is a duplicate RID registered with the USS; determining a second RID corresponding to the UAS based on the first RID; and sending a second registration request to the USS to register the second RID.

[0008] According to one or more embodiments, a device in an unmanned aerial system (UAS) is provided. The device includes: at least one memory configured to store program code; and at least one processor configured to read the program code and operate as indicated by the program code. The program code includes: first sending code configured to cause the at least one processor to send a first registration request to a UAS Service Supplier (USS) implemented on at least one server to register a first remote identification (RID) corresponding to the UAS with the USS; first receiving code configured to cause the at least one processor to receive from the USS an indication that the first RID is a duplicate RID registered with the USS; determining code configured to cause the at least one processor to determine a second RID corresponding to the UAS based on the first RID; and second sending code configured to cause the at least one processor to send a second registration request to the USS to register the second RID.

[0009] According to one or more embodiments, a non-transitory computer-readable medium storing instructions is provided. The instructions are configured to, when executed by at least one processor of a device in an unmanned aerial system (UAS), cause the at least one processor to: send a first registration request to a UAS Service Supplier (USS) implemented on at least one server to register a first remote identification (RID) corresponding to the UAS with the USS; receive from the USS an indication that the first RID is a duplicate RID registered with the USS; determine a second RID corresponding to the UAS based on the first RID; and send a second registration request to the USS to register the second RID.

[0010] According to one or more embodiments, there is provided a device in an unmanned aerial system (UAS), the device comprising: a first sending module configured to send a first registration request to a UAS service provider (USS) implemented on at least one server to register a first remote identification (RID) corresponding to the UAS with the USS; a first receiving module configured to receive from the USS an indication that the first RID is a duplicate RID registered with the USS; a determining module configured to determine a second RID corresponding to the UAS based on the first RID; and a second sending module configured to send a second registration request to the USS to register the second RID.

[0011] According to one or more embodiments, there is provided a computer device comprising a processor and a memory, the memory for storing program code and transmitting the program code to the processor; the processor for executing according to instructions in the program code: sending a first registration request to a UAS service provider (USS) implemented on at least one server to register a first remote identification (RID) corresponding to the UAS with the USS; receiving from the USS an indication that the first RID is a duplicate RID registered with the USS; determining a second RID corresponding to the UAS based on the first RID; and sending a second registration request to the USS to register the second RID.

[0012] According to the method executed by at least one processor in an unmanned aerial system and the device in an unmanned aerial system provided by the present disclosure, first, a first registration request is sent to a UAS service provider (USS) implemented on at least one server to register a first remote identification (RID) corresponding to the UAS with the USS, then, an indication that the first RID is a duplicate RID registered with the USS is received from the USS and a second RID corresponding to the UAS is determined based on the first RID, and finally, a second registration request is sent to the USS to register the second RID. Thus, even for a duplicate RID, the UAS can use the RID as an input to the HHIT to recalculate the RID and register again to ensure that the UAS continues to prepare for flight. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] Additional features, properties, and various advantages of the disclosed subject matter will become more apparent from the following detailed description and the accompanying drawings, in which:

[0014] Figure 1Schematic diagram of an unmanned aerial system (UAS) according to an embodiment.

[0015] Figure 2 Schematic diagram of a UAS including communication of the UAS with at least one server according to an embodiment.

[0016] Figure 3 Schematic diagram of an advanced process for UAS registration according to an embodiment.

[0017] Figure 4 Schematic diagram of an advanced process for UAS registration according to an embodiment.

[0018] Figures 5A to 5C Schematic diagram of an advanced workflow for UAS registration according to an embodiment.

[0019] Figure 6 Schematic diagram of a computer system according to an embodiment. DETAILED DESCRIPTION

[0020] Referring Figure 1 , an unmanned aerial system (UAS) (100) may include an unmanned aerial vehicle (UAV) (101) and a controller (102). The controller (102) may use a data link (103) to transmit control commands from the controller (102) to the UAV (101). The controller (102) may include at least one communication circuit configured to provide communication including the data link (103) via very high frequency (VHF), ultra-high frequency (UHF), or other wireless technologies as analog or digital radio transmissions. The controller (102) may control, via the data link (103), the control surfaces of the UAV (101) or the power level of the engine (114) of the UAV (101). More abstract commands, such as pitch, yaw, and roll, similar to those of a helicopter or an airplane, may also be used. An experienced pilot may use these basic controls to operate some UAVs without relying on any advanced on-board processing of control signals inside the UAV. The UAV can have various forms, including helicopters and airplanes.

[0021] Recent advancements in airborne electronics design have allowed for the transfer of certain tasks from human operators to the UAV itself. Nowadays, many UAVs include a sensor (104) that indicates characteristics of the UAV (101), such as the attitude and acceleration of the UAV (101), to the on-board controller (105) of the UAV (101). The on-board controller (105) can be a computer system with a scaled-down or non-existent user interface. In addition to control inputs received from the data link (103) from the controller (102), the information obtained by the sensor (104) can enable the UAV (101) to remain stable unless a positive control input is obtained from the controller (102).

[0022] Even more recently, UAVs can include a receiver (106) configured to receive communications from one of the Global Navigation Satellite Systems (GNSS), such as the Global Positioning System (GPS) operated by the United States. Figure 1 A single satellite (108) providing a signal (107) as such a communication is shown to represent the GNSS. However, the receiver (106) of the UAV (101) can receive communications from a GNSS that includes three or more, and typically four or more, line-of-sight satellites to triangulate the position of the UAV (101) in space. The receiver (106), which can be a GNSS receiver, can determine the position of the UAV (101) in time and space with reasonable accuracy. In some UAVs, the GNSS can be enhanced by additional sensors (such as ultrasonic or LIDAR sensors) on the vertical (Z-) axis of the UAV (101) to enable a soft landing (not depicted). According to some embodiments, the UAV (101) can be configured to perform features such as "fly home" and "automatic landing" based on GNSS capabilities, where the UAV (101) flies to a location defined as its home position. Such features can be performed by the UAV (101) based on a simple command from the controller (102) (such as pressing a single button) or in the event of a loss of the data link (103) from the controller (102) or other timeouts of meaningful control inputs.

[0023] As another recent development, the UAV (101) may also include one or more camera devices (109). In some cases, the UAV (101) may include a gimbal-mounted camera device as one of the camera devices (109), and may be used to record pictures and videos of a quality sufficient to satisfy the user of the UAV - nowadays, typically with high-definition television resolution. In some cases, the UAV (101) may include other camera devices (110) that generally cover some or all of the axes of movement, and the UAV (101) may be configured to perform on-board signal processing based on signals from the camera devices (110) for collision avoidance with both stationary and moving objects.

[0024] In some cases, the UAV (101) may include a "main" camera device as one of the camera devices (109), and its camera device signal may be transmitted in real time by the communication interface (e.g., communication circuitry) of the UAV (101) towards a human user via a data link (111), and displayed on a display device (112) included in, attached to, or separate from the controller (102). The data link (111) may be the same as or different from the data link (103). Thus, the UAV can successfully fly out of the sight of a human pilot using a technique known as "First Person View" (FPV).

[0025] Referring Figure 2 , the UAS (200) may include a UAV (201) and a controller (202). The UAV (201) and the controller (202) may be respectively coupled to Figure 1The UAV (101) and the controller (102) shown are the same or similar. According to an embodiment, a UAS (200) potentially operated by a UAS operator (203) such as a human pilot can be configured to notify one or more UAS Service Suppliers (USSs) (204) in real time about the location of the UAV (201). In an embodiment, the USS can be implemented on or using, for example, a server. Reporting can be performed using the Internet (205). For all but the most exotic use cases involving tethered UAVs, this can mean that one or both of the UAV (201) and the controller (202) of the UAS (200) can be configured to have a connection (206) to the Internet (205) via a wireless network such as a network (207) (e.g., a cellular network), and the USS (204) can also have a connection (208) to the Internet (205). Such a scenario can be assumed herein, but the embodiments of the present disclosure are not limited thereto. Networks other than the Internet (205) can also be used. For example, it can be envisioned that a closed wireless network that is not the Internet can be used for communication between the UAS (200) and the USS (204). Closed wireless networks can be used for certain military UAVs. When "Internet" is mentioned hereinafter, it means including such networks.

[0026] Many physical wireless network technologies can be deployed for the purpose of enabling a connection (206) (e.g., a wireless connection) and a network (207) (e.g., a wireless network) to connect a system such as the controller (202) or the UAV (201) of the UAS (200) to the Internet (205). For outdoor applications, a mobile network such as the 5th generation or "5G" network can be used. Hereinafter, the use of such a 5G network can be assumed, but the embodiments of the present disclosure are not limited thereto. Other physical network technologies can be equally adopted, including, for example, 3G, 3.5G, 4G, LTE mobile networks, wireless LANs in infrastructure or ad hoc mode, zig-bee, etc. In the embodiments of the present disclosure, the mobile network carrying the Internet can provide, for example, two-way communication between the UAS (200) and the USS (204). However, the quality of service in each direction may be different. According to the embodiments of the present disclosure, the UAV (201), the controller (202), and / or the USS (204) can include a communication interface (including, for example, a transmitter and / or a receiver) and at least one processor having a memory implementing one or more of the physical wireless network technologies, to be configured to communicate via one or more of the network types of the present disclosure.

[0027] Refer to Figure 2, the connection (206) between the Internet (205) and the UAV (201) and / or the controller (202) via a network (207) (such as a cellular network) can be bidirectional. When Internet protocols such as Internet Protocol (IP), Transmission Control Protocol (TCP), User Datagram Protocol (UDP), Hypertext Transfer Protocol (HTTP), Quick UDP Internet Connection (QUIC), etc. are used for communication between the UAS (200) and the USS (204), then due to the nature of these protocols, a bidirectional link may be required for these protocols to work.

[0028] As discussed above, a UAV such as UAV (101) or UAV (201) can have an identification (ID) associated with it. In fact, some UAVs are required to have an ID before flight. For example, in North America, the Federal Aviation Administration (FAA) has established regulations to ensure that all UAVs have some form of legal flight identification, and such identification is called the remote identification (RID) of the drone or UAV.

[0029] Some RID types have been identified by the Civil Aviation Authority (CAA), and all RIDs must be registered with the USS, such as USS (204). The USS maintains all direct communication with the UAS and forwards appropriate information to the UTM. The UTM can have other information sources about the UAS and can query the USS for more information about the UAS, such as UAS 200.

[0030] The following are examples of RID types:

[0031] ο American National Standards Institute (ANSI) and Consumer Technology Association (CTA) ANSI / CTA-2063-A serial number. This can be assigned to the UAS by the manufacturer of the UAS and can be hard-coded into the hardware of the UAV (201). The UAS operator (203) can use this number to register with the USS (204).

[0032] The registration number assigned at the CAA level. This registration number can be assigned by a local or international CAA. The UAS operator (203) can use this number to register with the USS (204).

[0033] ο Universally Unique Identifier (UUID). This number may be created by the manufacturer of the UAS (200) or by the USS (204) during registration. In either case, the UAS operator (203) can use this number to register with the USS (204).

[0034] ο The Internet Engineering Task Force (IETF) is developing another type of RID called the Hierarchical Host Identity Tag (HHIT), which can also be used for registering the UAS (200) with the USS (204). The UAS operator (203) can use this number to register with the USS (204).

[0035] In an embodiment, regardless of what RID type is assigned to the UAS (200), the RID must be registered with the USS (204). To register the UAS (200) with the USS, the UAS (200) must present a unique RID to the USS (204).

[0036] Two of the above RID types - the ANSI / CTA-2063-A serial number and the registration number assigned at the CAA level - can be statically assigned to, for example, the UAS (200) or the UAV (201), and can be used by the UAS (200) for registration.

[0037] As discussed above, due to various reasons including manufacturing errors and registration process errors, the RIDs of these RID types may be duplicated for two or more UASs (200). This can lead to registration failures when these UASs (200) attempt to register with the USS (204), and the registration failures prevent the takeoff of the controlled UAV (201). Since these registration types are statically assigned, the UAS cannot recover from this situation.

[0038] Figure 3Illustrated is an example process 300 for registering a UAS, such as UAS (200), using an ANSI / CTA-2063-A serial number. In process 300, at block 301, the UAS (200) may determine the ANSI / CTA-2063-A serial number that it will use as the RID. For example, the UAS may determine the ANSI / CTA-2063-A serial number hard-coded into the hardware of the UAV (201). At block 302, the UAS (200) attempts to register the RID with the USS (204).

[0039] If the registration is successful at block 303, then at block 304, the UAS (200) may continue to prepare for the flight of the UAV (201).

[0040] If at block 303, the registration fails because the RID is a duplicate, then at block 305, the UAS (200) may use the current RID as input to calculate a 64-bit Overlay Routable Cryptographic Hash Identifier (ORCHID) hash, and then use the hash value to construct a HHIT. Then, at block 302, the UAS (200) may attempt to register with the USS (204) using the HHIT as the RID.

[0041] Figure 4 Illustrated is an example process 400 for registering a UAS, such as UAS (200), using a registration number assigned at the CAA level. In process 400, at block 401, the UAS (200) may determine the registration number assigned at the CAA level that it will use as the RID, and at block 402, may attempt to register the RID with the USS (204).

[0042] If the registration is successful at block 403, then at block 404, the UAS (200) may continue to prepare for the flight.

[0043] If at block 403, the registration fails because the RID is a duplicate, then at block 405, the UAS (200) may use the current RID as input to calculate a 64-bit ORCHID hash, and then use the hash value to construct a HHIT. Then, at block 402, the UAS (200) may attempt to register with the USS (204) using the HHIT as the RID.

[0044] In an implementation, the HHIT RID can be used because the HHIT RID uses a 64-bit hash size and thus has a 0.01% probability of collision given 66 million HHIT RIDs.

[0045] Accordingly, an embodiment can provide a method that enables a UAS to recover from a registration failure due to a duplicate registration ID of the ANSI / CTA-2063-A serial number type by attempting to register a registration number created by hashing a duplicate registration number using the IETF HHIT algorithm with the ANSI / CTA-2063-A serial number used as input.

[0046] In addition, an embodiment can provide a method that enables a UAS to recover from a registration failure due to a duplicate registration ID of the registration number assigned at the CAA level by attempting to register a registration number created by hashing a duplicate registration number using the IETF HHIT algorithm with the registration number assigned at the CAA level used as input.

[0047] In an embodiment, and as described above for example, the ANSI / CTA-2063-A serial number, the registration number assigned at the CAA level, and the Universally Unique IDentifier (UUID) can be serial numbers or registration numbers that can be assigned to any one of the UAS (100), UAV (101), controller (102), UAS (200), UAV (201), controller (202), or any associated hardware or software, and can be assigned or associated as needed by any one of a manufacturer, a local or international CAA, or any other serial number or registration number management agency.

[0048] Figures 5A to 5C is a flowchart showing example processes 500A to 500C for managing a UAS, for example, during a UAS registration process. It can be described with the aid of Figures 1 to 4 to describe Figures 5A to 5C . In an embodiment, one or more blocks of processes 500A to 500C can be combined in any order.

[0049] As Figure 5A shown, process 500A can include sending a first registration request (block 511) to a USS implemented on at least one server to register a first RID corresponding to the UAS with the USS. In an embodiment, the UAS can correspond to UAS (100) and / or UAS (200), and the USS can correspond to USS (204). In an embodiment, the first registration request can correspond to blocks 301 to 302 or blocks 401 to 402 discussed above, and the first RID can correspond to or include an ANSI / CTA-2063-A serial number, a registration number assigned at the CAA level, or any other identifier discussed above.

[0050] As Figure 5AAlso shown, process 500A may include receiving an indication from the USS that the first RID is a duplicate RID registered with the USS (block 512).

[0051] As Figure 5A Also shown, process 500A may include determining a second RID corresponding to the UAS based on the first RID (block 513).

[0052] As Figure 5A Also shown, process 500A may include sending a second registration request to the USS to register the second RID (block 514). In an embodiment, the second registration request may correspond to blocks 305 to 302 or blocks 405 to 402 discussed above, and the second RID may correspond to or include an ANSI / CTA-2063-A serial number, a registration number assigned by the CAA level, or any other identifier discussed above.

[0053] In an embodiment, the first RID may include an ANSI / CTA-2063-A serial number.

[0054] In an embodiment, the ANSI-CTA-2063-A serial number may be encoded into the hardware of the UAV associated with the UAS. In an embodiment, the UAV may correspond to UAV(101) and / or UAV(201).

[0055] In an embodiment, the first RID may include a registration number assigned by the Civil Aviation Authority (CAA).

[0056] In an embodiment, Figure 5B The process 500B shown may be combined with process 500A. For example, the blocks of process 500B may be executed after block 514 of process 500A.

[0057] As Figure 5B As shown, process 500B may include receiving an indication from the USS to register the UAS with the USS based on the second RID (block 521).

[0058] As Figure 5B Also shown, process 500B may include preparing the unmanned aerial vehicle (UAV) associated with the UAS for flight based on the second RID (block 522).

[0059] In an embodiment, Figure 5C The process 500C shown may be combined with process 500A. For example, the blocks of process 500C may be executed in combination with block 513 of process 500A. In an embodiment, the blocks of process 500C may be sub-blocks of block 513 of process 500A.

[0060] As Figure 5C shown, process 500C may include obtaining a hash value based on a first RID (block 531).

[0061] As Figure 5A also shown, process 500A may include calculating a second RID based on the hash value (block 532).

[0062] In an implementation, the hash value may be a 64-bit hash value.

[0063] In an implementation, the hash value may be an Overlay Routable Cryptographic Hash Identifier (ORCHID) hash value.

[0064] In an implementation, the second RID may include an Internet Engineering Task Force (IETF) Hierarchical Host Identity Tag (HHIT) constructed based on the hash value.

[0065] It can be appreciated that Figures 5A to 5C only illustrations of implementations are provided and do not imply any limitations on how different implementations may be implemented. Many modifications may be made to the depicted environment based on design and implementation requirements.

[0066] Although Figures 5A to 5C example blocks of processes 500A to 500C are shown, in some implementations, compared to the blocks depicted in Figures 5A to 5C those, processes 500A to 500C may include additional blocks, fewer blocks, different blocks, or differently arranged blocks. For example, any one or more of the blocks in processes 500A to 500C may replace or be combined with any other one or more of the blocks in processes 500A to 500C in any order. Additionally or alternatively, two or more of the blocks of processes 500A to 500C may be executed in parallel.

[0067] Furthermore, the proposed method may be implemented by a processing circuit (e.g., one or more processors or one or more integrated circuits). In one example, one or more processors execute a program stored in a non-transitory computer-readable medium to perform one or more of the proposed methods.

[0068] The system of the present disclosure may include at least one processor and a memory storing computer code. The computer code, when executed by the at least one processor, may be configured to cause the at least one processor to perform the functions of the embodiments of the present disclosure. For example, each of the UAS, UAV, and USS of the present disclosure may include a respective at least one processor and a memory storing computer code configured to cause the UAS, UAV, and USS to perform their respective functions.

[0069] The techniques described above for unmanned aircraft system communication may be implemented as computer software using computer-readable instructions and physically stored in one or more computer-readable media, for example, in a controller and a UAV. For example, Figure 6 FIG. 600 is a computer system suitable for implementing certain embodiments of the disclosed subject matter.

[0070] According to an embodiment of the present disclosure, there is also provided a device in an unmanned aircraft system (UAS), the device including: a first sending module configured to send a first registration request to a UAS service provider (USS) implemented on at least one server to register a first remote identification (RID) corresponding to the UAS with the USS; a first receiving module configured to receive from the USS an indication that the first RID is a duplicate remote identification registered with the USS; a determining module configured to determine a second RID corresponding to the UAS based on the first RID; and a second sending module configured to send a second registration request to the USS to register the second RID.

[0071] In one example, the program module further includes: a second receiving module configured to receive from the USS an indication to register the UAS with the USS based on the second RID; and a preparation module configured to cause an unmanned aerial vehicle (UAV) associated with the UAS to prepare for flight based on the second RID.

[0072] In one example, the first RID includes an American National Standards Institute / Consumer Technology Association (ANSI / CTA)-2063-A serial number.

[0073] In one example, the ANSI-CTA-2063-A serial number is encoded into the hardware of an unmanned aerial vehicle (UAV) associated with the UAS.

[0074] In one example, the first RID includes a registration number assigned by the Civil Aviation Authority (CAA).

[0075] In one example, the determining module further includes: an obtaining module configured to obtain a hash value based on the first RID; and a calculating module configured to calculate the second RID based on the hash value.

[0076] In one example, the hash value is a 64-bit hash value.

[0077] In one example, the hash value is an Overlay Routable Cryptographic Hash Identifier (ORCHID) hash value.

[0078] In one example, the second RID includes an Internet Engineering Task Force (IETF) Hierarchical Host Identity Tag (HHIT) constructed based on the hash value.

[0079] According to an embodiment of the present disclosure, there is also provided a computer device, including a processor and a memory, the memory being configured to store program code and transmit the program code to the processor; the processor being configured to execute according to instructions in the program code: sending a first registration request to a UAS Service Supplier (USS) implemented on at least one server to register a first Remote Identifier (RID) corresponding to the UAS with the USS; receiving from the USS an indication that the first RID is a duplicate RID registered with the USS; determining a second RID corresponding to the UAS based on the first RID; and sending a second registration request to the USS to register the second RID.

[0080] Refer to Figure 6 , which shows a computer system (600) suitable for implementing certain embodiments of the disclosed subject matter.

[0081] Computer software can be encoded using any suitable machine code or computer language, which may be subject to mechanisms such as assembly, compilation, linking, or the like to create code including instructions that can be directly executed by a computer central processing unit (CPU), a Graphics Processing Unit (GPU), etc., or executed through interpretation, microcode execution, etc.

[0082] The instructions can be executed on various types of computers or their components, including, for example, personal computers, tablet computers, servers, smart phones, gaming devices, Internet of Things devices, etc.

[0083] Figure 6The components shown for the computer system (600) are exemplary in nature and are not intended to imply any limitation as to the functionality or scope of use of computer software for implementing embodiments of the present disclosure. The configuration of the components should not be construed as having any dependency or requirement related to any one or combination of the components shown in the exemplary embodiments of the computer system (600).

[0084] The computer system (600) may include certain human-machine interface input devices. Such human-machine interface input devices may respond to inputs made by one or more human users through, for example, tactile inputs (e.g., keystrokes, swipes, data glove movements), audio inputs (e.g., voice, clapping), visual inputs (e.g., gestures), olfactory inputs (not depicted). The human-machine interface devices may also be used to capture certain media not necessarily directly related to conscious human input, such as, for example, audio (e.g., voice, music, ambient sound), images (e.g., scanned images, photographic images obtained from a still-image camera device), video (e.g., two-dimensional video, three-dimensional video including stereoscopic video).

[0085] The input human-machine interface devices may include one or more of the following (only one of each is depicted): keyboard (601), mouse (602), touchpad (603), touch screen (610), joystick (605), microphone (606), scanner (607), and camera device (608).

[0086] The computer system (600) may also include certain human-machine interface output devices. Such human-machine interface output devices may stimulate the senses of one or more human users through, for example, tactile output, sound, light, and smell / taste. Such human-machine interface output devices may include tactile output devices (e.g., tactile feedback through the touch screen (610), data glove, or joystick (605), but there may also be tactile feedback devices that do not serve as input devices). For example, such devices may be audio output devices (e.g., speakers (609), headphones (not depicted)), visual output devices (e.g., screen 610, including CRT screens, LCD screens, plasma screens, OLED screens, each with or without touch screen input capabilities, each with or without tactile feedback capabilities - some of which may be capable of outputting two-dimensional visual output or more than three-dimensional output through means such as stereoscopic image output, virtual reality glasses (not depicted), holographic displays, and smoke cans (not depicted)), and printers (not depicted).

[0087] The computer system (600) may also include human-accessible storage devices and their associated media, such as optical media including CD / DVD ROM / RW (620) with media such as CD / DVD (621), thumb drives (622), removable hard disk drives or solid state drives (623), traditional magnetic media such as tapes and floppy disks (not depicted), devices based on dedicated ROM / ASIC / PLD such as security dongles (not depicted), etc.

[0088] Those skilled in the art should also understand that the term "computer-readable medium" used in connection with the presently disclosed subject matter does not include transmission media, carrier waves, or other transient signals.

[0089] The computer system (600) may also include an interface to one or more communication networks. The network may be, for example, wireless, wired, optical. The network may also be local, wide area, metropolitan area, vehicular and industrial, real-time, delay-tolerant, etc. Examples of networks include: local area networks such as Ethernet, wireless LANs, cellular networks including GSM, 3G, 4G, 5G, LTE, etc., television cable or wireless wide area digital networks including cable television, satellite television, and terrestrial broadcast television, vehicular and industrial including CANBus, etc. Certain networks typically require an external network interface adapter attached to certain common data ports or peripheral buses (649) (such as, for example, the USB port of the computer system (600)); other networks are typically integrated into the core of the computer system (600) by attaching to the system bus (for example, an Ethernet interface to a PC computer system or a cellular network interface to a smart phone computer system) as described below. The computer system (600) may communicate with other entities using any of these networks. Such communication may be one-way, receive-only (e.g., broadcast television), one-way transmit-only (e.g., CANbus to certain CANbus devices), or two-way (e.g., to other computer systems using local or wide area digital networks). Such communication may include communication to a cloud computing environment (655). Certain protocols and protocol stacks may be used on each of these networks and network interfaces as described above.

[0090] The above-mentioned human-machine interface devices, human-accessible storage devices, and network interfaces (654) may be attached to the core (640) of the computer system (600).

[0091] The core (640) may include one or more central processing units (CPUs) (641), graphics processing units (GPUs) (642), field programmable gate area (FPGA) (643) in the form of dedicated programmable processing units, hardware accelerators (644) for certain tasks, etc. These devices, together with read-only memory (ROM) (645), random-access memory (RAM) (646), and internal mass storage devices such as internal non-user-accessible hard disk drives, SSDs, etc., can be connected through a system bus (648). In some computer systems, the system bus (648) can be accessed in the form of one or more physical plugs to enable expansion through additional CPUs, GPUs, etc. Peripheral devices can be attached directly or through a peripheral bus (649) to the system bus (648) of the core. The architecture of the peripheral bus includes PCI, USB, etc. A graphics adapter (650) can be included in the core 640.

[0092] The CPU (641), GPU (642), FPGA (643), and accelerator (644) can execute certain instructions, which can be combined to form the computer code mentioned above. The computer code can be stored in the ROM (645) or RAM (646). Transitional data can also be stored in the RAM (646), while permanent data can be stored in, for example, the internal mass storage device (647). Fast storage and retrieval of any memory device in the memory devices can be achieved by using a cache memory, where the cache memory can be closely associated with one or more CPUs (641), GPUs (642), mass storage devices (647), ROM (645), RAM (646), etc.

[0093] Computer-readable media may have computer code for performing various computer-implemented operations. The media and computer code may be media and computer code specifically designed and constructed for the purposes of this disclosure, or the media and computer code may be of the type well-known and available to those skilled in the art of computer software.

[0094] By way of example and not limitation, a computer system (600) having an architecture and in particular having a core (640) can provide functionality as a result of a processor (including a CPU, GPU, FPGA, accelerator, etc.) executing software implemented in one or more tangible computer-readable media. Such computer-readable media can be media associated with a user-accessible mass storage device as introduced above, and certain storage devices of the core (640) having a non-transitory nature, such as an on-core mass storage device (647) or ROM (645). The software implementing various embodiments of the present disclosure can be stored in such devices and executed by the core (640). Depending on specific needs, the computer-readable media can include one or more memory devices or chips. The software can cause the core (640) and in particular the processors therein (including the CPU, GPU, FPGA, etc.) to execute specific processes or specific portions of specific processes described herein, including defining data structures stored in RAM (646) and modifying such data structures according to processes defined by the software. Additionally or alternatively, the computer system can provide functionality as a result of logic hard-wired or otherwise implemented in circuitry (e.g., an accelerator (644)), which can operate instead of or in conjunction with the software to execute specific processes or specific portions of specific processes described herein. In appropriate cases, the software mentioned can include logic, and conversely, the logic mentioned can include software. In appropriate cases, the computer-readable media mentioned can include circuitry (e.g., an integrated circuit (IC)) storing software for execution, circuitry implementing logic for execution, or both of the above. The present disclosure encompasses any suitable combination of hardware and software.

[0095] Although the present disclosure has described several non-limiting example embodiments, there are variations, permutations, and various alternative equivalents that fall within the scope of the present disclosure. Accordingly, it will be recognized that those skilled in the art will be able to envision many systems and methods that, although not explicitly shown or described herein, implement the principles of the present disclosure and are thus within the spirit and scope of the present disclosure.

Claims

1. A communication method performed by an unmanned aerial system (UAS), the method comprising: Sending a first registration request to an unmanned aerial system (UAS) service supplier (USS) implemented on at least one server to register a first remote identifier (RID) corresponding to the UAS with the USS; Receiving from the USS an indication that the first RID is a duplicate remote identifier registered with the USS; Determining a second RID corresponding to the UAS based on the first RID; And Sending a second registration request to the USS to register the second RID.

2. The method according to claim 1, further comprising: Receiving from the USS an indication to register the UAS with the USS based on the second RID; And Preparing an unmanned aerial vehicle (UAV) associated with the UAS for flight based on the second RID.

3. The method according to claim 1, wherein The first RID includes an American National Standards Institute / Consumer Technology Association (ANSI / CTA)-2063-A serial number.

4. The method according to claim 3, wherein The ANSI / CTA-2063-A serial number is encoded into the hardware of an unmanned aerial vehicle (UAV) associated with the UAS.

5. The method according to claim 1, wherein The first RID includes a registration number assigned by the Civil Aviation Authority (CAA).

6. The method according to any one of claims 1-5, characterized in that The determining further comprises: Obtaining a hash value based on the first RID; and Calculating the second RID based on the hash value.

7. The method according to claim 6, wherein The hash value is a 64-bit hash value.

8. The method according to claim 6, characterized in that, The hash value is a covered routable cryptographic hash identifier (ORCHID) hash value.

9. The method according to claim 6, characterized in that, The second RID includes an Internet Engineering Task Force (IETF) hierarchical host identity tag (HHIT) constructed based on the hash value.

10. A device in an unmanned aerial system (UAS), the device comprising: A first sending module configured to send a first registration request to an unmanned aerial system (UAS) service supplier (USS) implemented on at least one server to register a first remote identifier (RID) corresponding to the UAS with the USS; A first receiving module configured to receive from the USS an indication that the first RID is a duplicate remote identifier registered with the USS; A determination module configured to determine a second remote identification (RID) corresponding to the unmanned aerial system (UAS) based on the first remote identification (RID); and A second sending module configured to send a second registration request for registering the second remote identification (RID) to the service supplier (USS).

11. The device according to claim 10, characterized in that, The device further includes: A second receiving module configured to receive from the service supplier (USS) an indication to register the unmanned aerial system (UAS) with the service supplier (USS) based on the second remote identification (RID); and A preparation module configured to prepare the unmanned aerial vehicle (UAV) associated with the unmanned aerial system (UAS) for flight based on the second remote identification (RID).

12. The device according to claim 10, wherein The first remote identification (RID) includes an American National Standards Institute / Consumer Technology Association (ANSI / CTA)-2063-A serial number.

13. The device according to claim 12, characterized in that, The American National Standards Institute / Consumer Technology Association (ANSI / CTA)-2063-A serial number is encoded into the hardware of the unmanned aerial vehicle (UAV) associated with the unmanned aerial system (UAS).

14. The device according to claim 10, characterized in that, The first remote identification (RID) includes a registration number assigned by the Civil Aviation Authority (CAA).

15. The device according to any one of claims 10 to 14, characterized in that, The determination module further includes: An obtaining module configured to obtain a hash value based on the first remote identification (RID); and A calculation module configured to calculate the second remote identification (RID) based on the hash value.

16. The device according to claim 15, characterized in that, The hash value is a 64-bit hash value.

17. The device according to claim 15, characterized in that, The hash value is a covered routable cryptographic hash identifier (ORCHID) hash value.

18. The device according to claim 15, characterized in that, The second remote identification (RID) includes an Internet Engineering Task Force (IETF) hierarchical host identity tag (HHIT) constructed based on the hash value.

19. A non-transitory computer-readable medium storing instructions that, when executed by at least one processor of a device in an unmanned aerial system (UAS), cause the at least one processor to perform the method according to any one of claims 1-9.

20. A computer device, comprising a processor and a memory, characterized in that the memory is used to store program code and transmit the program code to the processor; the processor is used to execute the method according to any one of claims 1-9 according to the instructions in the program code.

Images