WO2020244443A1 - 一种无人机身份标识模组及存储方法 - Google Patents

一种无人机身份标识模组及存储方法 Download PDF

Info

Publication number
WO2020244443A1
WO2020244443A1 PCT/CN2020/093001 CN2020093001W WO2020244443A1 WO 2020244443 A1 WO2020244443 A1 WO 2020244443A1 CN 2020093001 W CN2020093001 W CN 2020093001W WO 2020244443 A1 WO2020244443 A1 WO 2020244443A1
Authority
WO
WIPO (PCT)
Prior art keywords
storage area
uav
drone
card
erasable storage
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2020/093001
Other languages
English (en)
French (fr)
Inventor
李刚
卢海英
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to EP20818728.6A priority Critical patent/EP3968226A4/en
Publication of WO2020244443A1 publication Critical patent/WO2020244443A1/zh
Anticipated expiration legal-status Critical
Priority to US17/543,001 priority patent/US12347322B2/en
Ceased legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06K—GRAPHICAL DATA READING; PRESENTATION OF DATA; RECORD CARRIERS; HANDLING RECORD CARRIERS
    • G06K17/00—Methods or arrangements for effecting co-operative working between equipments covered by two or more of main groups G06K1/00 - G06K15/00, e.g. automatic card files incorporating conveying and reading operations
    • G06K17/0022—Methods or arrangements for effecting co-operative working between equipments covered by two or more of main groups G06K1/00 - G06K15/00, e.g. automatic card files incorporating conveying and reading operations arrangements or provisions for transferring data to distant stations, e.g. from a sensing device
    • G06K17/0029—Methods or arrangements for effecting co-operative working between equipments covered by two or more of main groups G06K1/00 - G06K15/00, e.g. automatic card files incorporating conveying and reading operations arrangements or provisions for transferring data to distant stations, e.g. from a sensing device the arrangement being specially adapted for wireless interrogation of grouped or bundled articles tagged with wireless record carriers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H04W8/183—Processing at user equipment or user record carrier
    • G—PHYSICS
    • G08—SIGNALLING
    • G08G—TRAFFIC CONTROL SYSTEMS
    • G08G5/00—Traffic control systems for aircraft
    • G08G5/20—Arrangements for acquiring, generating, sharing or displaying traffic information
    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B64—AIRCRAFT; AVIATION; COSMONAUTICS
    • B64U—UNMANNED AERIAL VEHICLES [UAV]; EQUIPMENT THEREFOR
    • B64U10/00—Type of UAV
    • B64U10/10—Rotorcrafts
    • B64U10/13—Flying platforms
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06K—GRAPHICAL DATA READING; PRESENTATION OF DATA; RECORD CARRIERS; HANDLING RECORD CARRIERS
    • G06K7/00—Methods or arrangements for sensing record carriers, e.g. for reading patterns
    • G06K7/10—Methods or arrangements for sensing record carriers, e.g. for reading patterns by electromagnetic radiation, e.g. optical sensing; by corpuscular radiation
    • G06K7/10544—Methods or arrangements for sensing record carriers, e.g. for reading patterns by electromagnetic radiation, e.g. optical sensing; by corpuscular radiation by scanning of the records by radiation in the optical part of the electromagnetic spectrum
    • G06K7/10821—Methods or arrangements for sensing record carriers, e.g. for reading patterns by electromagnetic radiation, e.g. optical sensing; by corpuscular radiation by scanning of the records by radiation in the optical part of the electromagnetic spectrum further details of bar or optical code scanning devices
    • G—PHYSICS
    • G08—SIGNALLING
    • G08G—TRAFFIC CONTROL SYSTEMS
    • G08G5/00—Traffic control systems for aircraft
    • G08G5/20—Arrangements for acquiring, generating, sharing or displaying traffic information
    • G08G5/22—Arrangements for acquiring, generating, sharing or displaying traffic information located on the ground
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/30—Security of mobile devices; Security of mobile applications
    • H04W12/35—Protecting application or service provisioning, e.g. securing SIM application provisioning
    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B64—AIRCRAFT; AVIATION; COSMONAUTICS
    • B64U—UNMANNED AERIAL VEHICLES [UAV]; EQUIPMENT THEREFOR
    • B64U2201/00—UAVs characterised by their flight controls
    • B64U2201/20—Remote controls
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/60—Context-dependent security
    • H04W12/69—Identity-dependent
    • H04W12/71—Hardware identity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/60—Context-dependent security
    • H04W12/69—Identity-dependent
    • H04W12/72—Subscriber identity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/30—Services specially adapted for particular environments, situations or purposes
    • H04W4/40—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H04W8/20—Transfer of user or subscriber data
    • H04W8/205—Transfer to or from user equipment or user record carrier

Definitions

  • the embodiments of the present application relate to the field of electronic technology, and in particular to a drone identity identification module and a storage method.
  • UAV As a new technology product, UAV has developed rapidly in recent years. The number of civilian-grade drones is increasing, but most of them are flights that are not monitored and managed. Therefore, relevant standards for UAVs need to be formulated urgently.
  • UAV identification As the basis of UAV application and management, UAV identification is valued by domestic and foreign industries and standardization organizations. It is the primary condition for UAV development. It is necessary to formulate relevant technical standards around UAV identification. Management structure and process, etc.
  • UAV identification is not only a simple device identification, but also related to many aspects such as manufacturing, registration and filing, use and operation. However, at present, each manufacturer has its own storage method and location for the various identification marks of drones. There is no unified standard and specification for the time being. Most of the drone equipment only has partial identification, and it is impossible to complete the complete identification of the drone. The life cycle information reading and tracking, and the unmanned aerial vehicle's identifiable, monitorable, and traceable technical control system is not ideal.
  • the embodiments of the present application provide an unmanned aerial vehicle identity identification module and a storage method, so as to realize information reading and tracking of the entire life cycle of an unmanned aerial vehicle.
  • an unmanned aerial vehicle identification module includes a processor and a memory.
  • the memory includes a non-erasable storage area, an authorized erasable storage area, and a repeatedly erased storage area.
  • the processor is used to: obtain the physical identification of the drone, and write the physical identification into the non-erasable storage area; obtain the access identification of the drone, and write the access identification into the authorized erasing storage area;
  • the application identification of the man-machine the application identification is written into the repeated erasing storage area.
  • the physical identification is the unmodifiable hardware identification of the drone;
  • the access identification is the identification of the drone subscription service;
  • the application identification is the identification related to the drone flight.
  • the UAV’s ID can be classified and stored in storage areas with different characteristics, and the storage method and storage location of the UAV ID can be standardized. For the needs of drone management, configure the location of storage areas with different characteristics and configure the classification of the drone's identity to read and track the information of the entire life cycle of the drone according to the management needs.
  • the non-erasable storage area, the authorized erasing storage area and the repeated erasing storage area in the UAV ID module can be deployed in the UAV ID One or more hardware units in the drone where the module is located.
  • the storage locations of various UAV logos can be deployed according to actual needs, and the application is flexible.
  • the UAV ID module when the non-erasable storage area, the authorized erasing storage area, and the repeated erasing storage area in the UAV ID module are deployed in a hardware unit in the UAV, the UAV ID module
  • the memory in the UAV is an independent hardware unit; when the non-erasable storage area, the authorized erasable storage area, and the repeated erasable storage area in the UAV identity module are deployed in multiple hardware units in the UAV,
  • the memory in the UAV identification module is a functional unit of distributed deployment.
  • the UAV identity identification module may also be located in the flight control module, and the flight control module is used to implement the UAV The flight control processing function of the UAV; the non-erasable storage area, the authorized erasing storage area and the repeated erasing storage area in the memory of the UAV ID module are deployed in the flight control module.
  • the read-only memory (ROM) area of the flight control module includes the non-erasable storage area for storing the physical identification of the drone; the random access memory (RAM) area of the flight control module Including the authorized erasing storage area for storing the UAV access ID; the electrically erasable programmable read-only memory (EEPROM) area of the flight control module includes the repeated erasing of the UAV application ID Write storage area. Since the flight control module is the basic unit of the drone, it is a module that all types of drones have. Therefore, each storage area used to store the drone logo is deployed in the flight control module with strong independence, The interface is easy to standardize and read, and is suitable for all types of drones.
  • the UAV identity identification module may also be located in an onboard computer, which is used to realize the flight of the UAV Task processing function.
  • the non-erasable storage area, the authorized erasable storage area and the repeated erasable storage area in the memory of the UAV identity identification module are deployed on the airborne computer of the UAV.
  • the ROM area of the onboard computer memory includes the non-erasable storage area for storing the physical identification of the drone;
  • the RAM area of the onboard computer memory includes the authorized erasing storage area for storing the access identification of the drone;
  • the secure digital memory card (SD-Card) area includes a repeated erasing storage area for storing drone application IDs. Since the airborne computer is used by drone manufacturers and has strong scalability, each manufacturer can define the package driver and interface of the airborne computer by itself, so this implementation method is highly popular.
  • the UAV identity identification module can also be located on an onboard computer, which is used to realize the flight mission of the UAV Processing function; the onboard computer includes an embedded subscriber identification module (eSIM) card or an embedded universal integrated circuit card (eUICC) card; the memory of the drone is not erasable
  • eSIM embedded subscriber identification module
  • eUICC embedded universal integrated circuit card
  • the eSIM card or eUICC card is integrated on the onboard computer.
  • the solution of this implementation mode can define standardized eSIM or eUICC file format, read-write interface, etc., which is convenient for drone manufacturers to integrate.
  • the UAV identity identification module may also be located on the onboard computer.
  • the onboard computer includes an eSIM card or eUICC card, and the onboard computer also includes an SD-Card card; the non-erasable storage area and the authorized erasable storage area in the memory of the UAV ID module are deployed on the eSIM card or eUICC card, the repeatedly erased storage area in the memory of the UAV ID module is deployed on the SD-Card card.
  • SD-Card to replace the limited memory of eUICC card to increase the storage capacity of UAV logo.
  • the UAV identity identification module can also be independently designed.
  • a dedicated module is configured to store the UAV's identity, which has high reliability and safety.
  • the identity identification module includes a backup power supply and a communication module; the drone identity identification module is used in a drone accident At the time, the wireless signal is sent through the backup power supply and the communication module to be captured by the UAV identification module, so that the data can be checked when the UAV crashes.
  • the memory in the UAV identity identification module is coupled with the processor, and the processor implements the function of the processor when executing the instructions stored in the memory.
  • a storage method for UAV identity identification is provided.
  • the method is applied to the UAV identity identification module.
  • the UAV identity identification module is configured with a non-erasable storage area, an authorized erase storage area and repeated Erase the storage area.
  • the method may specifically include: obtaining the physical identification of the drone, writing the physical identification to the non-erasable storage area, and the physical identification is the unmodifiable hardware identification of the drone; acquiring the access identification of the drone, and inserting the access identification Write the authorized erasing storage area, and the access ID is the ID of the UAV contracted service; obtain the UAV's application ID, write the application ID into the repeated erasing storage area, and the application ID is the ID related to the drone flight.
  • the UAV’s identities are classified and stored in storage areas with different characteristics, and the storage methods and storage locations of UAV identities are standardized.
  • configure the location of storage areas with different characteristics configure the classification of the drone's identity to read and track the information of the entire life cycle of the drone according to the management needs.
  • a processing device in a third aspect, is provided.
  • the device may be a device or a chip system in a drone, or a device that can be matched with the drone.
  • the device or drone is equipped with a non-erasable storage area, an authorized erasing storage area, and a repeated erasing storage area for storing the identity of the drone.
  • the processing device can realize the above-mentioned aspects or functions in each possible design, and the functions can be realized by hardware, or by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the aforementioned functions.
  • the processing device includes an acquisition unit and a writing unit.
  • the obtaining unit is used to obtain the identification of the drone, and the identification includes a physical identification, an access identification and an application identification;
  • the writing unit is used to write the physical identification into the non-erasable storage area and the access identification Authorize the erasing storage area, and write the application ID to the repeated erasing storage area.
  • the physical identification is the unmodifiable hardware identification of the drone;
  • the access identification is the identification of the drone subscription service;
  • the application identification is the identification related to the drone flight.
  • the UAV’s identities are classified and stored in storage areas with different characteristics, and the storage method and storage location of the UAV’s identities are standardized.
  • the UAV can be managed according to According to the requirements of management, the location of storage areas with different characteristics and the classification of the identity of the drone are configured to read and track the information of the entire life cycle of the drone according to the management needs.
  • the embodiments of the present application also provide a computer-readable storage medium, including instructions, which, when run on a computer, cause the computer to execute any of the above-mentioned aspects or any one of the possible implementations.
  • Machine identity storage method
  • the embodiments of the present application also provide a computer program product, which when running on a computer, causes the computer to execute the drone identity storage method described in any one of the above aspects or any one of the possible implementations .
  • an embodiment of the present application provides a chip system, which includes a processor and may also include a memory, configured to implement the functions in the foregoing method.
  • the chip system can be composed of chips, or can include chips and other discrete devices.
  • FIG. 1 is a schematic diagram of an application scenario of a drone provided by an embodiment of the application
  • Figure 2 is a schematic diagram of the internal architecture of a drone provided by an embodiment of the application.
  • FIG. 3 is a schematic diagram of the classification of a drone identity provided by an embodiment of the application.
  • FIG. 4 is a schematic structural diagram of a UAV identity identification module provided by an embodiment of the application.
  • FIG. 5a is a schematic structural diagram of an onboard computer provided by an embodiment of the application.
  • 5b is a schematic structural diagram of another airborne computer provided by an embodiment of the application.
  • FIG. 6 is a schematic structural diagram of still another airborne computer provided by an embodiment of the application.
  • FIG. 7 is a flowchart of a method for storing the identity of a drone according to an embodiment of the application.
  • FIG. 8 is a schematic structural diagram of a processing device provided by an embodiment of the application.
  • words such as “exemplary” or “for example” are used as examples, illustrations, or illustrations. Any embodiment or design solution described as “exemplary” or “for example” in the embodiments of the present application should not be construed as being more preferable or advantageous than other embodiments or design solutions. To be precise, words such as “exemplary” or “for example” are used to present related concepts in a specific manner to facilitate understanding.
  • A/B can mean A or B; "and/or” in this application is only It is a kind of association relationship that describes the associated objects, which means that there can be three kinds of relationships, for example, A and/or B, which can mean: A alone exists, A and B exist at the same time, and B exists alone, where A, B It can be singular or plural.
  • plural means two or more than two.
  • the following at least one item (a)” or similar expressions refers to any combination of these items, including any combination of a single item (a) or plural items (a).
  • at least one item (a) of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple .
  • At least one can also be described as one or more, and the multiple can be two, three, four or more, which is not limited in this application.
  • UAV unmanned aerial vehicles
  • FIG. 1 shows a schematic diagram of a UAV application scenario, which includes UAV, UAV management equipment and UAV users.
  • FIG. 1 is only an example and is not specifically limited.
  • FIG. 2 illustrates an internal structure diagram of an unmanned aerial vehicle 20.
  • the unmanned aerial vehicle 20 may include an onboard computer 201 on which a flight control module 2011 is deployed.
  • the onboard computer 201 may be an integrated circuit board on which electronic components and various connectors are deployed.
  • the flight control module 2011 is an electronic component deployed on the integrated circuit.
  • a central processing unit (CPU) is also deployed in the airborne computer 201 to implement the processing function of the drone.
  • a memory is also deployed in the onboard computer 201 to store instruction codes and data.
  • an SD card can also be deployed in the airborne computer 201 to expand the storage function of the drone.
  • other electronic components can also be deployed on the integrated circuit board to expand the various functions of the drone, which will not be repeated here.
  • the UAV ID is not only a simple device ID, but also related to many aspects such as manufacturing, registration, use and operation.
  • the UAV identity can include: device identity (DID), flight control identity (FCID), communication device identity (communication identity, CID), and sign identifier, SID), drone operator identification (unmanned aircraft system operator identity, UOID), application layer identification cloud provider number (CPN) or dynamic application layer identification cloud service number (dynamic cloud provider number, D- CPN) etc.
  • DID device identity
  • FCID flight control identity
  • communication device identity communication identity
  • CID communication device identity
  • sign identifier SID
  • drone operator identification unmanned aircraft system operator identity
  • UOID application layer identification cloud provider number
  • CPN application layer identification cloud provider number
  • D- CPN dynamic application layer identification cloud service number
  • this application provides a UAV and UAV identity storage method.
  • the basic principle is: According to the application characteristics of the UAV identity, the UAV identity is divided into physical identification, access identification and Application IDs, different types of IDs are stored in storage areas with different characteristics, so that you can configure the location of the storage areas with different characteristics and the classification of the drone's ID according to the needs of drone management , In order to read and track the information of the whole life cycle of the UAV according to the management requirements.
  • the physical identification is the physical unchangeable information of the drone, which is written by the drone manufacturer during the production stage.
  • the physical identification can include one or more of the following identifications: complete machine equipment identification, communication module identification, flight control Module identification, encryption and key, black box equipment identification, engine/motor identification, other equipment identification, etc.
  • the access ID is the ID of the drone contract service.
  • the access ID is generated during the drone contracting phase.
  • the access ID is the information that the drone can authorize to erase and write. It is written by the user of the drone before use.
  • the entry identifier may include one or more of the following identifiers: owner registration information, operator registration information, communication service provider contract information, communication key information, and so on.
  • the application identifier is an identifier related to the flight of the drone. It is the information that the drone can repeatedly erase and write. It is written by the drone's onboard CPU during the use phase.
  • the application identifier can include one or more of the following identifiers: Identification, flight route identification, flight direction identification, speed identification, altitude identification, latitude and longitude identification, time stamp identification, etc.
  • the drone IDs are stored in three types of storage areas: the non-erasable area stores the physical identifier, the authorized erase area stores the access identifier, and the repeated erase area stores the application identifier.
  • FIG. 4 is a schematic diagram of the composition of an unmanned aerial vehicle identification module 40 provided in an embodiment of the application.
  • the machine identification module 40 may include a processor 401 and a memory 402.
  • the memory 402 includes a non-erasable storage area, an authorized erasable storage area, and a repeated erasable storage area.
  • the processor 401 may be one processor or a collective name for multiple processing elements.
  • the processor 401 is a CPU, or an application specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of the present application, for example: one or more micro-processing A digital signal processor (DSP), or one or more field programmable gate arrays (FPGA).
  • the processor 401 can execute various functions by running or executing a software program stored in the memory 402 and calling data stored in the memory 402.
  • the processor 401 is configured to: obtain the physical identification of the drone, and write the physical identification into the non-erasable storage area; obtain the access identification of the drone, and write the access identification into the authorized erasing storage area; Obtain the application ID of the drone, and write the application ID into the repeated erasing storage area.
  • the physical identification is the unmodifiable hardware identification of the drone
  • the access identification is the identification of the drone subscription service
  • the application identification is the identification related to the drone flight.
  • the processor 401 obtains the physical identification of the drone, which may be directly written by the drone manufacturer during the production phase, so that the processor 401 obtains the physical identification; the processor 401 obtains the access identification of the drone, which may be The user of the drone enters through the user interface of the drone during the signing phase, so that the processor 401 obtains the access ID; the processor 401 obtains the application ID of the drone, which may be the user of the drone. The stage of the drone is input through the user interface of the drone, so that the processor 401 obtains the application identifier.
  • the processor 401 may also obtain the identity of the drone in other ways, which is not specifically limited in the embodiment of the present application.
  • non-erasable storage area, the authorized erasing storage area and the repeated erasing storage area in the UAV ID module 40 can be deployed in one or more hardware units in the UAV. This application The embodiment does not specifically limit this.
  • the memory 402 may be an independent hardware Unit; when the non-erasable storage area, the authorized erasable storage area and the repeated erasable storage area in the UAV ID module 40 are deployed in multiple hardware units in the UAV, the memory 402 is a distributed deployment Functional unit.
  • the following examples are the deployment schemes of several non-erasable storage areas, authorized erasable storage areas, and repeated erasable storage areas used to store drone IDs in drones, but they do not constitute a limitation.
  • the classification and storage of identification marks in different areas belong to the protection scope of this application.
  • Example 1 The identity identification module is located on the flight control module, and the identity of the drone is stored on the flight control module.
  • the flight control module is used to realize the flight control processing function of the UAV, which is a necessary equipment for the UAV.
  • the internal memory of the flight control module includes ROM, RAM and EEPROM.
  • the non-erasable storage area, the authorized erasing storage area, and the repeated erasing storage area in the memory of the UAV flight control module for storing the UAV ID are deployed in the flight control module.
  • the ROM area of the flight control module includes the non-erasable storage area for storing the physical identification of the drone;
  • the RAM area of the flight control module includes the authorized erasing storage area for storing the access identification of the drone;
  • the EEPROM area of the module includes the repeated erasing storage area for storing the UAV application identification.
  • the ROM area of the flight control module is generally written by the manufacturer of the flight control module with the flight control identification, which can be expanded to include other physical identifications;
  • the RAM area of the flight control module is generally used to load the program area, which can be A part is reserved to save the access identification;
  • the FLASH/DDR area in the EEPROM of the flight control module is generally used to load programs and save data, and a part can be reserved to save black box information such as application identification and log information.
  • Example 2 The UAV ID module is located on the onboard computer, and the UAV ID is stored in the memory of the onboard computer.
  • the onboard computer is used to implement the flight task processing functions of the UAV, such as obstacle avoidance, management flight and other task processing functions.
  • the onboard computer also has memory, including: ROM, RAM, SD-Card, etc., so it can be used to save the drone's identity.
  • the ROM area of the onboard computer memory includes the non-erasable storage area in the UAV ID module that stores the physical identity of the UAV;
  • the RAM area of the onboard computer memory includes the UAV ID module The authorized erasing storage area for storing the UAV access ID;
  • the SD-Card area of the onboard computer memory includes the repeated erasing storage area for storing the UAV application ID in the UAV ID module.
  • Figure 5a shows a structure of the airborne computer in the drone.
  • the airborne computer is on the airborne mainboard (ie a printed circuit board) on which the flight control module, CPU, Onboard memory, SD card and connection interface, etc.
  • the identity of the drone can be stored in the onboard memory of the onboard computer.
  • Figure 5a is only an example to illustrate the structure of the onboard computer, and does not constitute a specific limitation. In practical applications, other functional components can be deployed on the onboard motherboard according to actual needs to realize the various functions of the onboard computer. Features.
  • the ROM area of the onboard computer is generally written by the manufacturer of the complete device identification, and the ROM area can be expanded to write other physical identifications;
  • the RAM area of the onboard computer is generally used to load the program area , A part of RAM area can be reserved to save access identification;
  • the SD-Card area of the onboard computer is generally used to save data and logs, etc., and a part of SD-Card area can be reserved to save black boxes such as application identification and log information information.
  • Example 3 The drone's identity module is located on the onboard computer, the drone's onboard computer is deployed with eUICC or eSIM, and the drone's identity is stored in different storage areas in the onboard computer's eUICC or eSIM.
  • Figure 5b shows another structure of the airborne computer in the drone.
  • the airborne computer is on the airborne mainboard (ie a printed circuit board) on which the flight control module and CPU can be deployed. , EUICC/eSIM and connection interface, etc.
  • the identity of the drone can be stored in the onboard memory of the onboard computer.
  • eUICC/eSIM may include: profile data security domain (issuer security domain-profile, ISD-P), root security domain (issuer security domain-root, ISD-R), eUICC certification authority security domain (eUICC certificate authority security) domain, ECASD), eUICC operating system (Operating System), etc.
  • eUICC or eSIM is configured with a drone identity configuration area (such as DID Profile) when leaving the factory to save drone identity information and configure the configuration area in Policy Rules Enforcer to not be deleted. (disable) or authorized to rewrite or rewrite, and configure the corresponding read-write interface.
  • Policy Rules Policy Rules
  • the root key of the drone identity can be stored in the ECASD to be used for authentication and authorization to update the access identity.
  • more application identification information can be stored in the SD-Card area.
  • Example 4 The UAV ID module is located on the onboard computer.
  • the eUICC or eSIM is deployed on the UAV’s onboard computer, and the SD-Card is also deployed on the onboard computer to store the UAV’s identity on the onboard computer. Different areas in the eUICC or eSIM of the computer and SD-Card.
  • Example 4 the non-erasable storage area for storing the physical identity and the authorized erasable storage area for storing the access identity in the memory of the UAV identity identification module are deployed on the eSIM card or eUICC Card, the repeated erasing storage area used to store application identification in the memory of the UAV identity identification module is deployed on the SD-Card card.
  • Example 5 Independent deployment of UAV identification module.
  • the UAV ID module is dedicated to storing the UAV ID, and is a miniaturized airborne computer unit.
  • the UAV ID module can be equipped with black box functions, including backup power supply and communication module. Under normal operation conditions, through external power supply, it can meet the requirements of networked flight management and record and save UAV ID and status information.
  • Use communication modules such as enhanced machine type communication (eMTC) mode
  • eMTC enhanced machine type communication
  • Use communication modules such as narrowband Internet of Things (narrowband Internet of Things) internet of things (NB-IoT)/radio frequency identification (RFID)
  • NB-IoT narrowband Internet of Things internet of things
  • RFID radio frequency identification
  • Figure 6 illustrates the front and back structure of the onboard computer in the UAV, which is used to implement the storage UAV ID in Example 5.
  • the onboard computer is deployed on the front of the onboard mainboard (that is, a printed circuit board) with the drone identification module, backup power supply, flight control module, CPU, onboard memory, and connection interfaces.
  • the communication module is deployed on the back.
  • the onboard computer illustrated in FIG. 6 can implement the scheme of storing the identity of the drone in Example 5.
  • Figure 6 is only an example to illustrate the structure of the onboard computer, and does not constitute a specific limitation. In practical applications, other functional components can be deployed on the onboard motherboard according to actual needs to realize the various functions of the onboard computer. Features.
  • the drone's identity can be classified and stored in storage areas with different characteristics, and the storage method and storage location of the drone's identity can be standardized. In this way, According to the demand for drone management, configure the location of the storage area with different characteristics and configure the classification of the drone's identity to read and track the information of the entire life cycle of the drone according to the management requirements.
  • the embodiment of the present application provides a method for storing the identity of the drone, which is used to store the identity of the drone.
  • the identity of the drone includes: physical identification, access identification and application identification. The definition of each type of identification has been described in detail in the foregoing content, and will not be repeated here. As shown in Figure 7, the method may include:
  • the drone identification module obtains the physical identification of the drone, and writes the physical identification into the non-erasable storage area.
  • the UAV ID module obtains the physical ID of the UAV, which can be directly written by the UAV manufacturer in the production stage, so that the UAV ID module obtains the physical ID.
  • the UAV identity identification module may also obtain the physical identification of the UAV in other ways, which is not specifically limited in the embodiment of the present application.
  • the UAV identification module obtains the access identifier of the UAV, and writes the access identifier into the authorized erasing storage area.
  • the UAV ID module obtains the access ID of the UAV, which can be input by the user of the UAV through the user interface of the UAV at the signing stage, so that the UAV ID module can obtain the access ID. Into the logo.
  • the UAV identity identification module can also obtain the access identification of the UAV in other ways, which is not specifically limited in this embodiment of the application.
  • the drone identification module obtains the application identification of the drone, and writes the application identification into the repeated erasing storage area.
  • the UAV ID module obtains the application ID of the UAV, which can be input by the user of the UAV through the UAV user interface during the stage of using the UAV, so that the UAV ID module Get the application ID.
  • the UAV identity identification module can also obtain the UAV's application identification in other ways, which is not specifically limited in the embodiment of the present application.
  • UAV ID storage method illustrated in FIG. 7 is implemented by the above-mentioned UAV ID module 40. Therefore, the specific implementation of the UAV ID storage method illustrated in FIG. The specific implementation of the machine identification module 40 will not be repeated here.
  • the UAV’s identities are classified and stored in storage areas with different characteristics, and the storage methods and storage locations of UAV identities are standardized.
  • configure the location of storage areas with different characteristics configure the classification of the drone's identity to read and track the information of the entire life cycle of the drone according to the management needs.
  • an embodiment of the present application also provides a processing device 80.
  • the processing device 80 may be a device or a chip system in a drone, or a device that can be matched and used with the drone.
  • the processing device 80 or the drone is equipped with a non-erasable storage area, an authorized erasable storage area, and a repeated erasable storage area.
  • the processing device 80 can implement the functions in the foregoing embodiments, and the functions can be implemented by hardware, or by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the aforementioned functions.
  • the processing device 80 may include an obtaining unit 801 and a writing unit 802, which are used to support the processing device 80 to implement the processes S701 to S703 in the foregoing method embodiment.
  • a computer-readable storage medium is provided, and an instruction is stored thereon, and the method in the foregoing method embodiment is executed when the instruction is executed.
  • a computer program product containing instructions is provided, and when the instructions are executed, the method in the foregoing method embodiment is executed.
  • the embodiment of the present application further provides a chip system.
  • the chip system includes a processor for implementing the technical method in the embodiment of the present invention.
  • the chip system further includes a memory for storing necessary program instructions and/or data in the embodiment of the present invention.
  • the chip system further includes a memory for the processor to call application program codes stored in the memory.
  • the chip system may be composed of one or more chips, and may also include chips and other discrete devices, which are not specifically limited in the embodiment of the present application.
  • the steps of the method or algorithm described in conjunction with the disclosure of this application can be implemented in hardware, or implemented by a processor executing software instructions.
  • Software instructions can be composed of corresponding software modules, which can be stored in RAM, flash memory, ROM, erasable programmable read-only memory (erasable programmable ROM, EPROM), electrically erasable programmable read-only memory (electrically erasable programmable read-only memory, EPROM, EEPROM), registers, hard disk, mobile hard disk, CD-ROM or any other form of storage medium known in the art.
  • An exemplary storage medium is coupled to the processor, so that the processor can read information from the storage medium and can write information to the storage medium.
  • the storage medium may also be an integral part of the processor.
  • the processor and the storage medium may be located in the ASIC.
  • the ASIC may be located in the core network interface device.
  • the processor and the storage medium may also exist as discrete components in the core network interface device.
  • the memory may be coupled with the processor.
  • the memory may exist independently and be connected to the processor through a bus.
  • the memory can also be integrated with the processor.
  • the memory may be used to store application program codes that execute the technical solutions provided in the embodiments of the present application, and the processor controls the execution.
  • the processor is used to execute the application program code stored in the memory, so as to implement the technical solution provided by the embodiment of the present application.
  • the disclosed device and method may be implemented in other ways.
  • the device embodiments described above are merely illustrative.
  • the division of the modules or units is only a logical function division.
  • there may be other division methods for example, multiple units or components may be It can be combined or integrated into another device, or some features can be omitted or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate parts may or may not be physically separate.
  • the parts displayed as units may be one physical unit or multiple physical units, that is, they may be located in one place, or they may be distributed to multiple different places. . Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.
  • each unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
  • the above-mentioned integrated unit can be implemented in the form of hardware or software functional unit.
  • the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium.
  • the technical solutions of the embodiments of the present application are essentially or the part that contributes to the prior art, or all or part of the technical solutions can be embodied in the form of a software product, which is stored in a storage medium It includes several instructions to make a device (may be a single-chip microcomputer, a chip, etc.) or a processor (processor) execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage media include: U disk, mobile hard disk, ROM, RAM, magnetic disk or optical disk and other media that can store program codes.

Landscapes

  • Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • Aviation & Aerospace Engineering (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • General Physics & Mathematics (AREA)
  • Signal Processing (AREA)
  • Mechanical Engineering (AREA)
  • Remote Sensing (AREA)
  • Databases & Information Systems (AREA)
  • Electromagnetism (AREA)
  • Computer Security & Cryptography (AREA)
  • Theoretical Computer Science (AREA)
  • Health & Medical Sciences (AREA)
  • General Health & Medical Sciences (AREA)
  • Toxicology (AREA)
  • Artificial Intelligence (AREA)
  • Computer Vision & Pattern Recognition (AREA)
  • General Engineering & Computer Science (AREA)
  • Traffic Control Systems (AREA)
  • Time Recorders, Dirve Recorders, Access Control (AREA)
  • Control Of Position, Course, Altitude, Or Attitude Of Moving Bodies (AREA)

Abstract

本申请实施例公开了一种无人机身份标识模组及存储方法，涉及电子技术领域，以实现对无人机全生命周期的信息读取和追踪。所述方法包括：获取无人机的物理标识，将物理标识写入不可擦写存储区，物理标识为无人机不可修改的硬件标识；获取无人机的接入标识，将接入标识写入授权擦写存储区，接入标识为无人机签约服务的标识；获取无人机的应用标识，将应用标识写入反复擦写存储区，应用标识为无人机飞行相关的标识。

Description

一种无人机身份标识模组及存储方法
本申请要求于2019年06月05日提交国家知识产权局、申请号为201910486503.7、发明名称为“一种无人机身份标识模组及存储方法”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请实施例涉及电子技术领域，尤其涉及一种无人机身份标识模组及存储方法。
背景技术
无人机作为新兴的科技产品，最近几年得到了快速发展。民用级无人机的数量越来越多，但越大多数都属于未进行监控以及管理的飞行。因此，无人机的相关标准急需制定。
2017年12月，工信部下发《关于促进和规范民用无人机制造业发展的指导意见》，指出：“推动形成民用无人机可识别、可监控、可追溯的技术管控体系。安全管控技术手段不断完善。国家级安全管控平台基本建立，企业级监管平台基本实现全覆盖，民用无人机产品全部实现“一机一码”，自动识别率达到100％，满足接入管控平台的功能要求”。“一机一码”，与传统的硬件设备标识不同，是通过一组身份标识在无人机的全生命周期对无人机进行识别管控。
无人机身份标识作为无人机应用与管理的基础，受到国内外行业以及标准化组织的重视，是无人机发展的首要条件，需围绕着无人机身份标识制定相关技术标准，无人机管理的架构和流程等。
无人机身份标识不仅仅只是一个简单的设备标识，还涉及生产制造、注册备案、使用运营等多个方面相关的标识。但是，目前对于无人机的各类身份标识，各个厂家都有自己保存的方式及位置，暂无统一的标准和规范，大部分无人机设备只存在部分标识，无法完成对无人机全生命周期的信息读取和追踪，无人机的可识别、可监控、可追溯的技术管控体系实现的很不理想。
发明内容
本申请实施例提供一种无人机身份标识模组及存储方法，以实现对无人机全生命周期的信息读取和追踪。
为达到上述目的，本申请实施例采用如下技术方案：
第一方面，提供一种无人机身份标识模组，该无人机身份标识模组包括处理器及存储器，该存储器包括不可擦写存储区、授权擦写存储区以及反复擦写存储区。具体的，处理器用于：获取无人机的物理标识，将该物理标识写入不可擦写存储区；获取无人机的接入标识，将接入标识写入授权擦写存储区；获取无人机的应用标识，将应用标识写入反复擦写存储区。其中，物理标识为该无人机不可修改的硬件标识；接入标识为无人机签约服务的标识；应用标识为无人机飞行相关的标识。
通过本申请提供的无人机身份标识模组，将无人机的身份标识分类并存储于不同特性的存储区中，规范无人机身份标识的存储方式以及存储位置，这样一来，可以根 据对无人机管理的需求，配置不同特性的存储区的位置以及配置无人机的身份标识所属的分类，以按照管理需求对无人机全生命周期的信息读取和追踪。
结合第一方面，在一种可能的实现方式中，该无人机身份标识模组中的不可擦写存储区、授权擦写存储区以及反复擦写存储区，可以部署在无人机身份标识模组所在的无人机中一个或多个硬件单元中。通过该实现方式，可以按照实际需求部署无人机各类标识的存储位置，应用灵活。
其中，当无人机身份标识模组中的不可擦写存储区、授权擦写存储区以及反复擦写存储区，部署在无人机中一个硬件单元中时，该无人机身份标识模组中的存储器是一个独立硬件单元；当无人机身份标识模组中的不可擦写存储区、授权擦写存储区以及反复擦写存储区，部署在无人机中多个硬件单元中时，该无人机身份标识模组中的存储器是分布式部署的功能性单元。
结合第一方面或上述任一种可能的实现方式，在另一种可能的实现方式中，该无人机身份标识模组还可位于飞控模组，飞控模组用于实现无人机的飞行控制处理功能；该无人机身份标识模组的存储器中的不可擦写存储区、授权擦写存储区以及反复擦写存储区部署在该飞控模组。其中，飞控模组的只读存储器(read-only memory，ROM)区域包括存储无人机物理标识的不可擦写存储区；飞控模组的随机存取存储器(random access memory，RAM)区域包括存储无人机接入标识的授权擦写存储区；飞控模组的带电可擦可编程只读存储器(electrically erasable programmable read-only memory，EEPROM)区域包括存储无人机应用标识的反复擦写存储区。由于飞控模组是无人机的基本单元，是所有类型无人机均具有的模块，因此，将用于存储无人机标识的各个存储区域部署在飞控模组中，独立性强、接口易标准化及读取，且适用于所有类型的无人机。
结合第一方面或上述任一种可能的实现方式，在另一种可能的实现方式中，该无人机身份标识模组还可位于机载计算机，机载计算机用于实现无人机的飞行任务处理功能。该无人机身份标识模组的存储器中的不可擦写存储区、授权擦写存储区以及反复擦写存储区部署在无人机中的机载计算机。其中，机载计算机存储器的ROM区域包括存储无人机物理标识的不可擦写存储区；机载计算机存储器的RAM区域包括存储无人机接入标识的授权擦写存储区；机载计算机存储器的安全数码卡(secure digital memory card，SD-Card)区域包括存储无人机应用标识的反复擦写存储区。由于机载计算机由无人机厂家体用，扩展性强，各厂家可以自己定义机载计算机的封装驱动和接口，因此该实现方式的推广性强。
结合第一方面或上述任一种可能的实现方式，在另一种可能的实现方式中，无人机身份标识模组还可位于机载计算机，机载计算机用于实现无人机的飞行任务处理功能；该机载计算机包括嵌入式用户身份识别(embedded subscriber identification module，eSIM)卡或嵌入式通用集成电路卡(embedded universal integrated circuit card，eUICC)卡；该无人机的存储器中的不可擦写存储区、授权擦写存储区以及反复擦写存储区部署在该机载计算机上的eSIM卡或eUICC卡。eSIM卡或eUICC卡是集成在机载计算机上的，本实现方式的方案，可以定义标准化的eSIM或eUICC文件格式、读写接口等，便于无人机厂家集成。
结合第一方面或上述任一种可能的实现方式，在另一种可能的实现方式中，无人机身份标识模组还可位于机载计算机。该机载计算机包括eSIM卡或eUICC卡，该机载计算机还包括SD-Card卡；该无人机身份标识模组的存储器中的不可擦写存储区、授权擦写存储区部署在eSIM卡或eUICC卡，该无人机身份标识模组的存储器中反复擦写存储区部署在该SD-Card卡。通过SD-Card替代eUICC卡有限的内存，提高无人机标识存储的容量。
结合第一方面或上述任一种可能的实现方式，在另一种可能的实现方式中，无人机身份标识模组还可独立设计。在该实现方式中，配置专用模块用于存储无人机的标识，可靠性及安全性高。
结合第一方面或上述任一种可能的实现方式，在另一种可能的实现方式中，身份标识模组包括备用电源和通信模组；无人机身份标识模组用于在无人机事故时，通过备用电源和通信模组发送无线信号以被捕获无人机身份标识模组，以实现无人机失事时数据可查。
进一步的，无人机身份标识模组中的存储器与处理器耦合，处理器执行存储器中存储的指令时实现处理器的功能。
第二方面，提供一种无人机身份标识存储方法，该方法应用于无人机身份标识模组，该无人机身份标识模组配置了不可擦写存储区、授权擦写存储区以及反复擦写存储区。该方法具体可以包括：获取无人机的物理标识，将物理标识写入不可擦写存储区，物理标识为无人机不可修改的硬件标识；获取无人机的接入标识，将接入标识写入授权擦写存储区，接入标识为无人机签约服务的标识；获取无人机的应用标识，将应用标识写入反复擦写存储区，应用标识为无人机飞行相关的标识。
通过本申请提供的无人机身份标识存储方法，将无人机的身份标识分类并存储于不同特性的存储区中，规范无人机身份标识的存储方式以及存储位置，这样一来，可以根据对无人机管理的需求，配置不同特性的存储区的位置以及配置无人机的身份标识所属的分类，以按照管理需求对无人机全生命周期的信息读取和追踪。
需要说明的是，第二方面提供的无人机身份标识存储方法的具体实现，可以参考第一方面的具体实现，此处不再进行赘述。
第三方面，提供一种处理装置，该装置可以是无人机中的装置或者芯片系统，或者是能够和无人机匹配使用的装置。该装置或者无人机配置了用于存储无人机身份标识的不可擦写存储区、授权擦写存储区以及反复擦写存储区。该处理装置可以实现上述各方面或者各可能的设计中的功能，所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个上述功能相应的模块。如：该处理装置包括获取单元及写入单元。
其中，获取单元用于获取无人机的标识，该标识包括物理标识、接入标识及应用标识；所述写入单元用于将物理标识写入不可擦写存储区，将接入标识写入授权擦写存储区，将应用标识写入反复擦写存储区。其中，物理标识为无人机不可修改的硬件标识；接入标识为无人机签约服务的标识；应用标识为无人机飞行相关的标识。
通过本申请提供的处理装置，将无人机的身份标识分类并存储于不同特性的存储区中，规范无人机身份标识的存储方式以及存储位置，这样一来，可以根据对无人机 管理的需求，配置不同特性的存储区的位置以及配置无人机的身份标识所属的分类，以按照管理需求对无人机全生命周期的信息读取和追踪。
需要说明的是，第三方面提供的处理装置的具体实现，可以参考第一方面的具体实现，此处不再进行赘述。
第四方面，本申请实施例中还提供一种计算机可读存储介质，包括指令，当其在计算机上运行时，使得计算机执行上述任一方面或任意一种可能的实现方式所述的无人机身份标识存储方法。
第五方面，本申请实施例中还提供一种计算机程序产品，当其在计算机上运行时，使得计算机执行上述任一方面或任意一种可能的实现方式所述的无人机身份标识存储方法。
第六方面，本申请实施例提供了一种芯片系统，该芯片系统包括处理器，还可以包括存储器，用于实现上述方法中功能。该芯片系统可以由芯片构成，也可以包含芯片和其他分立器件。
上述第四方面至第六方面提供的方案，用于实现上述第二方面提供的无人机身份标识存储方法，因此可以与第二方面达到相同的有益效果，此处不再进行赘述。
附图说明
图1为本申请实施例提供的一种无人机的应用场景示意图；
图2为本申请实施例提供的一种无人机内部架构示意图；
图3为本申请实施例提供的一种无人机身份标识的分类示意图；
图4为本申请实施例提供的一种无人机身份标识模组的结构示意图；
图5a为本申请实施例提供的一种机载计算机的结构示意图；
图5b为本申请实施例提供的另一种机载计算机的结构示意图；
图6为本申请实施例提供的再一种机载计算机的结构示意图；
图7为本申请实施例提供的一种无人机身份标识存储方法的流程图；
图8为本申请实施例提供的一种处理装置的结构示意图。
具体实施方式
在本申请实施例中，“示例性的”或者“例如”等词用于表示作例子、例证或说明。本申请实施例中被描述为“示例性的”或者“例如”的任何实施例或设计方案不应被解释为比其它实施例或设计方案更优选或更具优势。确切而言，使用“示例性的”或者“例如”等词旨在以具体方式呈现相关概念，便于理解。
在本申请的描述中，除非另有说明，“/”表示前后关联的对象是一种“或”的关系，例如，A/B可以表示A或B；本申请中的“和/或”仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况，其中A,B可以是单数或者复数。并且，在本申请的描述中，除非另有说明，“多个”是指两个或多于两个。“以下至少一项(个)”或其类似表达，是指的这些项中的任意组合，包括单项(个)或复数项(个)的任意组合。例如，a，b，或c中的至少一项(个)，可以表示：a，b，c，a-b，a-c，b-c，或a-b-c，其中a，b，c可以是单个，也可以是多个。
在本申请实施例中，至少一个还可以描述为一个或多个，多个可以是两个、三个、 四个或者更多个，本申请不做限制。
本申请实施例提供的方案可用于无人机，无人机也可以称之为无人驾驶航空器(unmanned aerial vehicle，UAV)。
图1示意了一种无人机的应用场景示意图，该场景中包括无人机、无人机管理设备以及无人机使用者。当然，图1仅为示例，并不是具体限定。
图2示意了一种无人机20的内部架构图，该无人机20可以包括机载计算机201，机载计算机201上部署了飞控模块2011。
其中，机载计算机201可以为一块部署了电子元器件及各种接插件的集成电路板。飞控模块2011即为该集成电路上部署的一个电子元器件。例如，机载计算机201中还部署了中央处理器(central processing unit，CPU)，以实现无人机的处理功能。例如，机载计算机201中还部署了存储器，以存储指令代码及数据。例如，机载计算机201中还可以部署SD卡，以扩展无人机的存储功能。当然，也可以在该集成电路板上部署其他电子元器件，以扩展无人机各种功能，此处不再进行赘述。
本申请涉及无人机身份标识存储，无人机身份标识不仅仅只是一个简单的设备标识，还涉及生产制造、注册备案、使用运营等多个方面相关的标识。例如，如图3所示，无人机身份标识可以包括：设备标识(device identity，DID)、飞控标识(fly control identity，FCID)、通信设备标识(communication identity，CID)、签约标识(sign identifier，SID)、无人机运营人标识(unmanned aircraft system operator identity，UOID)、应用层标识云服务号(cloud provider number，CPN)或动态应用层标识云服务号(dynamic cloud provider number，D-CPN)等。目前，无人机身份标识分布在无人机中不同的设备当中，暂无统一的标准和规范。
基于此，本申请提供一种无人机及无人机身份标识存储方法，其基本原理是：根据无人机身份标识的应用特点，把无人机身份标识分为物理标识、接入标识和应用标识，不同类别的身份标识存储于不同特征的存储区域中，这样一来，可以根据对无人机管理的需求，配置不同特性的存储区的位置以及配置无人机的身份标识所属的分类，以按照管理需求对无人机全生命周期的信息读取和追踪。
其中，物理标识是无人机物理不可改信息，在生产阶段由无人机厂家写入，物理标识可以包括下述标识中的一种或多种：整机设备标识、通信模块标识、飞控模块标识、加密跟密钥、黑匣子设备标识、发动机/马达标识、其他设备标识等。
接入标识是无人机签约服务的标识，接入标识在无人机签约阶段产生，接入标识是无人机可授权擦写信息，在使用前由对无人机使用人写入，接入标识可以包括下述标识中的一种或多种：拥有者登记信息、运营人登记信息、通信服务商签约信息、通信密钥信息等。
应用标识为无人机飞行相关的标识，是无人机可反复擦写信息，在使用阶段由无人机机载CPU写入，应用标识可以包括下述标识中的一种或多种：传输标识、飞行路线标识、飞行航向标识、速度标识、高度标识、经纬度标识以及时间戳标识等。
具体的，将无人机身份标识分别放到三类存储区域进行保存：不可擦写区保存物理标识、授权擦写区保存接入标识、反复擦写区保存应用标识。
下面将结合附图对本申请实施例的实施方式进行详细描述。
一方面，本申请实施例提供一种无人机身份标识模组，图4为本申请实施例提供的一种无人机身份标识模组40的组成示意图，如图4所示，该无人机身份标识模组40可以包括处理器401，存储器402。其中，存储器402包括不可擦写存储区、授权擦写存储区以及反复擦写存储区。
处理器401，可以是一个处理器，也可以是多个处理元件的统称。例如，处理器401是一个CPU，也可以是特定集成电路(application specific integrated circuit，ASIC)，或者是被配置成实施本申请实施例的一个或多个集成电路，例如：一个或多个微处理器(digital signal processor，DSP)，或，一个或者多个现场可编程门阵列(field programmable gate array，FPGA)。其中，处理器401可以通过运行或执行存储在存储器402内的软件程序，以及调用存储在存储器402内的数据，执行各种功能。
具体的，处理器401用于：获取无人机的物理标识，将该物理标识写入不可擦写存储区；获取无人机的接入标识，将接入标识写入授权擦写存储区；获取无人机的应用标识，将应用标识写入反复擦写存储区。其中，物理标识为该无人机不可修改的硬件标识；接入标识为无人机签约服务的标识；应用标识为无人机飞行相关的标识。
其中，处理器401获取无人机的物理标识，可以是无人机厂家在生产阶段直接写入，以使得处理器401获取该物理标识；处理器401获取无人机的接入标识，可以是无人机的使用者在签约阶段通过无人机的用户界面输入，以使得处理器401获取该接入标识；处理器401获取无人机的应用标识，可以是无人机的使用者在使用无人机的阶段通过无人机的用户界面输入，以使得处理器401获取该应用标识。当然，处理器401还可以通过其他方式获取无人机的身份标识，本申请实施例对此不进行具体限定。
需要说明的是，无人机身份标识模组40中的不可擦写存储区、授权擦写存储区以及反复擦写存储区，可以部署在无人机中一个或多个硬件单元中，本申请实施例对此不进行具体限定。
其中，当无人机身份标识模组40中的不可擦写存储区、授权擦写存储区以及反复擦写存储区，部署在无人机中一个硬件单元中时，存储器402可以是一个独立硬件单元；当无人机身份标识模组40中的不可擦写存储区、授权擦写存储区以及反复擦写存储区，部署在无人机中多个硬件单元中时，存储器402是分布式部署的功能性单元。
下面示例几种用于存储无人机身份标识的不可擦写存储区、授权擦写存储区以及反复擦写存储区在无人机中的部署方案，但并不构成限定，凡是将无人机身份标识分类存储于不同区域都属于本申请的保护范围。
示例1、身份标识模组位于飞控模组上，无人机的身份标识存储在飞控模组上。
其中，飞控模组用于实现无人机的飞行控制处理功能，是无人机的必选设备。飞控模组的内部具有存储器，包括：ROM、RAM和EEPROM等。在示例1中，该无人机飞控模组的存储器中用于存储无人机身份标识的不可擦写存储区、授权擦写存储区以及反复擦写存储区部署在该飞控模组。在示例1中，飞控模组的ROM区域包括存储无人机物理标识的不可擦写存储区；飞控模组的RAM区域包括存储无人机接入标识的授权擦写存储区；飞控模组的EEPROM区域包括存储无人机应用标识的反复擦写存储区。
具体的，在示例1中，飞控模块ROM区域一般由飞控模组的厂家写入飞控标识， 可扩充包含其他物理标识；飞控模组的RAM区域一般用于加载程序区域，可预留一部分保存接入标识；飞控模组的EEPROM中的FLASH/DDR区域一般用于加载程序和保存数据，可预留一部分保存应用标识、日志信息等黑匣子信息。
示例2、无人机身份标识模组位于机载计算机，无人机的身份标识存储在机载计算机的存储器中。
机载计算机用于实现无人机的飞行任务处理功能，例如避障、打点飞行等任务处理功能。机载计算机上同时具有存储器，包括：ROM、RAM和SD-Card等，因此可以用来保存无人机身份标识。在示例2中，机载计算机存储器的ROM区域包括无人机身份标识模组中存储无人机物理标识的不可擦写存储区；机载计算机存储器的RAM区域包括无人机身份标识模组中存储无人机接入标识的授权擦写存储区；机载计算机存储器的SD-Card区域包括无人机身份标识模组中存储无人机应用标识的反复擦写存储区。
图5a示意了无人机中的机载计算机的一种结构，如图5a所示，机载计算机是在机载主板(即一块印制电路板)，其上可以部署飞控模块、CPU、板载存储器、SD卡以及连接接口等。可以将无人机的身份标识存储在机载计算机的板载存储器中。
需要说明的是，图5a只是对机载计算机的结构进行示例说明，并不构成具体限定，在实际应用中，可以根据实际需求在机载主板上部署其他功能原件以实现机载计算机的各种功能。
具体的，在示例2中，机载计算机ROM区域一般由整机厂家写入整机设备标识，可扩充该ROM区域，用来写入其他物理标识；机载计算机RAM区域一般用于加载程序区域，可预留一部分RAM区域，用来保存接入标识；机载计算机SD-Card区域一般用于保存数据和日志等，可预留一部分SD-Card区域，用来保存应用标识、日志信息等黑匣子信息。
示例3、无人机身份标识模组位于机载计算机，无人机机载计算机上部署了eUICC或eSIM，将无人机的身份标识存储在机载计算机的eUICC或者eSIM中的不同存储区域。
图5b示意了无人机中的机载计算机的另一种结构，如图5b所示，机载计算机是在机载主板(即一块印制电路板)，其上可以部署飞控模块、CPU、eUICC/eSIM以及连接接口等。可以将无人机的身份标识存储在机载计算机的板载存储器中。
其中，eUICC/eSIM可以包括：配置文件数据安全域(issuer security domain-profile，ISD-P)、根安全域(issuer security domain-root，ISD-R)、eUICC认证授权安全域(eUICC certificate authority security domain，ECASD)、eUICC操作系统(Operating System)等。
具体的，eUICC或eSIM出厂时配置一个无人机身份标识配置区域(如DID Profile)，用来保存无人机身份标识信息，并在策略规则执行(Policy Rules Enforcer)中配置该配置区域不可删除(disable)或者授权改写或者可改写，并配置对应的读写接口。按照该规则定义三块区域并配置策略规则(Policy Rules)，分别叫作：物理标识信息区域(配置为不可改写，用于存储物理标识)、接入标识信息区域(配置为含通信密钥，需授权改写，用于存储接入标识)，应用标识信息区域(配置为可改写，用于存储应 用标识)。
可选的，可以在ECASD中保存无人机身份标识根密钥，用来认证鉴权，并授权更新接入标识。
可选的，由于eUICC内存有限，可通过SD-Card区域保存更多应用标识信息。
示例4、无人机身份标识模组位于机载计算机，无人机机载计算机上部署了eUICC或eSIM，机载计算机上还部署了SD-Card，将无人机的身份标识存储在机载计算机的eUICC或者eSIM中的不同区域以及SD-Card。
具体的，在示例4中，该无人机身份标识模组的存储器中的用于存储物理标识的不可擦写存储区、用于存储接入标识的授权擦写存储区部署在eSIM卡或eUICC卡，该无人机身份标识模组的存储器中用于存储应用标识的反复擦写存储区部署在SD-Card卡。
示例5、独立部署无人机身份标识模组。
具体的，无人机身份标识模组专用于存储无人机身份标识，是一个小型化的机载计算机单元。
可选的，无人机身份标识模组可以配置黑匣子功能，包括备用电源及通信模块，正常作业情况下，通过外部供电，满足联网飞行管理要求，记录、保存无人机身份标识、状态信息，利用通信模块(如增强机器类通信(enhanced machine type communication，eMTC)模式)接收和发送信息；在异常事故情况下，通过备用电源，满足黑匣子设计要求，利用通信模块(如窄带物联网(narrow band internet of things,NB-IoT)/射频识别(radio frequency identification)RFID)，在无人机事故时，发送无线信号以被捕获无人机身份标识模组。
图6示意了无人机中的机载计算机的正反面结构，用于实现示例5中的存储无人机身份标识。机载计算机是在机载主板(即一块印制电路板)的正面部署了无人机身份标识模组、备用电源、飞控模块、CPU、板载存储器以及连接接口等，在机载主板的背面部署了通信模块。图6示意的机载计算机可以实现示例5中的存储无人机的身份标识的方案。
需要说明的是，图6只是对机载计算机的结构进行示例说明，并不构成具体限定，在实际应用中，可以根据实际需求在机载主板上部署其他功能原件以实现机载计算机的各种功能。
通过本申请提供的无人机身份标识模组40，将无人机的身份标识分类并存储于不同特性的存储区中，规范无人机身份标识的存储方式以及存储位置，这样一来，可以根据对无人机管理的需求，配置不同特性的存储区的位置以及配置无人机的身份标识所属的分类，以按照管理需求对无人机全生命周期的信息读取和追踪。
另一方面，本申请实施例提供一种无人机身份标识存储方法，用于存储无人机的身份标识。无人机的身份标识包括：物理标识、接入标识以及应用标识。对于每一种标识的定义，已经在前述内容进行了详细说明，此处不再进行赘述。如图7所示，该方法可以包括：
S701、无人机身份标识模组获取无人机的物理标识，将物理标识写入不可擦写存储区。
其中，无人机身份标识模组获取无人机的物理标识，可以是无人机厂家在生产阶段直接写入，以使得无人机身份标识模组获取该物理标识。当然，无人机身份标识模组还可以通过其他方式获取无人机的物理标识，本申请实施例对此不进行具体限定。
S702、无人机身份标识模组获取无人机的接入标识，将接入标识写入授权擦写存储区。
其中，无人机身份标识模组获取无人机的接入标识，可以是无人机的使用者在签约阶段通过无人机的用户界面输入，以使得无人机身份标识模组获取该接入标识。当然，无人机身份标识模组还可以通过其他方式获取无人机的接入标识，本申请实施例对此不进行具体限定。
S703、无人机身份标识模组获取无人机的应用标识，将应用标识写入反复擦写存储区。
其中，无人机身份标识模组获取无人机的应用标识，可以是无人机的使用者在使用无人机的阶段通过无人机的用户界面输入，以使得无人机身份标识模组获取该应用标识。当然，无人机身份标识模组还可以通过其他方式获取无人机的应用标识，本申请实施例对此不进行具体限定。
需要说明的是，图7示意的无人机身份标识存储方法由上述无人机身份标识模组40实现，因此，图7示意的无人机身份标识存储方法的具体实现，可以参考前述无人机身份标识模组40的具体实现，此处不再进行赘述。
通过本申请提供的无人机身份标识存储方法，将无人机的身份标识分类并存储于不同特性的存储区中，规范无人机身份标识的存储方式以及存储位置，这样一来，可以根据对无人机管理的需求，配置不同特性的存储区的位置以及配置无人机的身份标识所属的分类，以按照管理需求对无人机全生命周期的信息读取和追踪。
再一方面，本申请实施例还提供一种处理装置80，处理装置80可以是无人机中的装置或者芯片系统，或者是能够和无人机匹配使用的装置。该处理装置80或者无人机配置了不可擦写存储区、授权擦写存储区以及反复擦写存储区。该处理装置80可以实现上述各实施例中的功能，所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个上述功能相应的模块。如图8所示，该处理装置80可以包括获取单元801及写入单元802，用于支持处理装置80实现上述方法实施例中的过程S701至S703。
作为本实施例的另一种形式，提供一种计算机可读存储介质，其上存储有指令，该指令被执行时执行上述方法实施例中的方法。
作为本实施例的另一种形式，提供一种包含指令的计算机程序产品，该指令被执行时执行上述方法实施例中的方法。
本申请实施例再提供一种芯片系统，该芯片系统包括处理器，用于实现本发明实施例的技术方法。在一种可能的设计中，该芯片系统还包括存储器，用于保存本发明实施例必要的程序指令和/或数据。在一种可能的设计中，该芯片系统还包括存储器，用于处理器调用存储器中存储的应用程序代码。该芯片系统，可以由一个或多个芯片构成，也可以包含芯片和其他分立器件，本申请实施例对此不作具体限定。
结合本申请公开内容所描述的方法或者算法的步骤可以硬件的方式来实现，也可 以是由处理器执行软件指令的方式来实现。软件指令可以由相应的软件模块组成，软件模块可以被存放于RAM、闪存、ROM、可擦除可编程只读存储器(erasable programmable ROM，EPROM)、电可擦可编程只读存储器(electrically EPROM，EEPROM)、寄存器、硬盘、移动硬盘、只读光盘(CD-ROM)或者本领域熟知的任何其它形式的存储介质中。一种示例性的存储介质耦合至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息。当然，存储介质也可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。另外，该ASIC可以位于核心网接口设备中。当然，处理器和存储介质也可以作为分立组件存在于核心网接口设备中。或者，存储器可以与处理器耦合，例如存储器可以是独立存在，通过总线与处理器相连接。存储器也可以和处理器集成在一起。存储器可以用于存储执行本申请实施例提供的技术方案的应用程序代码，并由处理器来控制执行。处理器用于执行存储器中存储的应用程序代码，从而实现本申请实施例提供的技术方案。
通过以上的实施方式的描述，所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，仅以上述各功能模块的划分进行举例说明，实际应用中，可以根据需要而将上述功能分配由不同的功能模块完成，即将装置的内部结构划分成不同的功能模块，以完成以上描述的全部或者部分功能。
在本申请所提供的几个实施例中，应该理解到，所揭露的装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述模块或单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个装置，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是一个物理单元或多个物理单元，即可以位于一个地方，或者也可以分布到多个不同地方。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个可读取存储介质中。基于这样的理解，本申请实施例的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该软件产品存储在一个存储介质中，包括若干指令用以使得一个设备(可以是单片机，芯片等)或处理器(processor)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、ROM、RAM、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何在本申请揭露的技术范围内的变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (16)

  1. 一种无人机身份标识模组，其特征在于，包括处理器及存储器，所述存储器包括不可擦写存储区、授权擦写存储区以及反复擦写存储区；其中，所述处理器用于：
    获取所述无人机的物理标识，将所述物理标识写入所述不可擦写存储区；所述物理标识为所述无人机不可修改的硬件标识；
    获取所述无人机的接入标识，将所述接入标识写入所述授权擦写存储区；所述接入标识为所述无人机签约服务的标识；
    获取所述无人机的应用标识，将所述应用标识写入所述反复擦写存储区；所述应用标识为所述无人机飞行相关的标识。
  2. 根据权利要求1所述的无人机身份标识模组，其特征在于，所述不可擦写存储区、所述授权擦写存储区以及所述反复擦写存储区，部署在所述无人机身份标识模组所在的无人机中一个或多个硬件单元中。
  3. 根据权利要求1或2所述的无人机身份标识模组，其特征在于，所述无人机身份标识模组位于飞控模组中，所述飞控模组用于实现无人机的飞行控制处理功能；
    所述不可擦写存储区、所述授权擦写存储区以及所述反复擦写存储区部署在所述无人机中的飞控模组；
    所述飞控模组的只读存储器ROM区域包括所述不可擦写存储区；
    所述飞控模组的随机存取存储器RAM区域包括所述授权擦写存储区；
    所述飞控模组的带电可擦可编程只读存储器EEPROM区域包括所述反复擦写存储区。
  4. 根据权利要求1或2所述的无人机身份标识模组，其特征在于，所述无人机身份标识模组位于机载计算机，所述机载计算机用于实现无人机的飞行任务处理功能；
    所述不可擦写存储区、所述授权擦写存储区以及所述反复擦写存储区部署在所述无人机中的机载计算机；
    所述机载计算机存储器的ROM区域包括所述不可擦写存储区；
    所述机载计算机存储器的随机存取存储器RAM区域包括所述授权擦写存储区；
    所述机载计算机存储器的安全数码卡SD-Card区域包括所述反复擦写存储区。
  5. 根据权利要求1或2所述的无人机身份标识模组，其特征在于，所述无人机身份标识模组位于机载计算机，所述机载计算机用于实现无人机的飞行任务处理功能；所述机载计算机包括嵌入式用户身份识别eSIM卡或嵌入式通用集成电路卡eUICC卡；
    所述不可擦写存储区、所述授权擦写存储区以及所述反复擦写存储区部署在所述eSIM卡或eUICC卡。
  6. 根据权利要求1或2所述的无人机身份标识模组，其特征在于，所述无人机身份标识模组可位于机载计算机，所述机载计算机用于实现所述无人机的飞行任务处理功能；所述机载计算机包括嵌入式用户身份识别eSIM卡或eUICC卡；所述机载计算机还包括SD-Card卡；
    所述不可擦写存储区、所述授权擦写存储区部署在所述eSIM卡或eUICC卡，所述反复擦写存储区部署在所述SD-Card卡。
  7. 根据权利要求1或2所述的无人机身份标识模组，其特征在于，所述无人机身 份标识模组还包括备用电源及通信模组；所述身份标识模组用于在无人机事故时，通过所述备用电源和所述通信模组发送无线信号以被捕获所述无人机身份标识模组。
  8. 一种无人机身份标识存储方法，其特征在于，应用于无人机身份标识模组，所述无人机身份标识模组配置了不可擦写存储区、授权擦写存储区以及反复擦写存储区；所述方法包括：
    获取所述无人机的物理标识，将所述物理标识写入所述不可擦写存储区；所述物理标识为所述无人机不可修改的硬件标识；
    获取所述无人机的接入标识，将所述接入标识写入所述授权擦写存储区；所述接入标识为所述无人机签约服务的标识；
    获取所述无人机的应用标识，将所述应用标识写入所述反复擦写存储区；所述应用标识为所述无人机飞行相关的标识。
  9. 根据权利要求8所述的方法，其特征在于，所述不可擦写存储区、所述授权擦写存储区以及所述反复擦写存储区，部署在所述无人机中一个或多个硬件单元中。
  10. 根据权利要求8或9所述的方法，其特征在于，所述无人机身份标识模组位于飞控模组，所述飞控模组用于实现无人机的飞行控制处理功能；
    所述不可擦写存储区、所述授权擦写存储区以及所述反复擦写存储区部署在所述无人机中的飞控模组；
    所述飞控模组的只读存储器ROM区域包括所述不可擦写存储区；
    所述飞控模组的随机存取存储器RAM区域包括所述授权擦写存储区；
    所述飞控模组的带电可擦可编程只读存储器EEPROM区域包括所述反复擦写存储区。
  11. 根据权利要求8或9所述的方法，其特征在于，所述无人机身份标识模组位于机载计算机，所述机载计算机用于实现无人机的飞行任务处理功能；
    所述不可擦写存储区、所述授权擦写存储区以及所述反复擦写存储区部署在所述无人机中的机载计算机；
    所述机载计算机存储器的ROM区域包括所述不可擦写存储区；
    所述机载计算机存储器的随机存取存储器RAM区域包括所述授权擦写存储区；
    所述机载计算机存储器的安全数码卡SD-Card区域包括所述反复擦写存储区。
  12. 根据权利要求8或9所述的方法，其特征在于，所述无人机身份标识模组位于机载计算机，所述机载计算机用于实现无人机的飞行任务处理功能，所述机载计算机包括嵌入式用户身份识别eSIM卡或eUICC卡；
    所述不可擦写存储区、所述授权擦写存储区以及所述反复擦写存储区部署在所述eSIM卡或eUICC卡。
  13. 根据权利要求8或9所述的方法，其特征在于，所述无人机身份标识模组位于机载计算机，所述机载计算机用于实现无人机的飞行任务处理功能；所述机载计算机包括嵌入式用户身份识别eSIM卡或eUICC卡；所述机载计算机算还包括SD-Card卡；
    所述不可擦写存储区、所述授权擦写存储区部署在所述eSIM卡或eUICC卡，所述反复擦写存储区部署在所述SD-Card卡。
  14. 根据权利要求8或9所述的方法，其特征在于，所述无人机身份标识模组还包括备用电源和通信模组；所述方法还包括：
    在所述无人机事故时，通过所述备用电源和所述通信模组发送无线信号以被捕获所述无人机身份标识模组。
  15. 一种计算机可读存储介质，其特征在于，包括指令，当其在计算机上运行时，使得计算机执行如权利要求8-14任一项所述的无人机身份标识存储方法。
  16. 一种计算机程序产品，其特征在于，当其在计算机上运行时，使得计算机执行如权利要求8-14任一项所述的无人机身份标识存储方法。
PCT/CN2020/093001 2019-06-05 2020-05-28 一种无人机身份标识模组及存储方法 Ceased WO2020244443A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP20818728.6A EP3968226A4 (en) 2019-06-05 2020-05-28 UNMANNED AIR VEHICLE IDENTIFICATION MODULE AND STORAGE METHOD
US17/543,001 US12347322B2 (en) 2019-06-05 2021-12-06 Unmanned aircraft identity module and storage method

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910486503.7 2019-06-05
CN201910486503.7A CN112052918B (zh) 2019-06-05 2019-06-05 一种无人机身份标识模组及存储方法

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/543,001 Continuation US12347322B2 (en) 2019-06-05 2021-12-06 Unmanned aircraft identity module and storage method

Publications (1)

Publication Number Publication Date
WO2020244443A1 true WO2020244443A1 (zh) 2020-12-10

Family

ID=73609309

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/093001 Ceased WO2020244443A1 (zh) 2019-06-05 2020-05-28 一种无人机身份标识模组及存储方法

Country Status (4)

Country Link
US (1) US12347322B2 (zh)
EP (1) EP3968226A4 (zh)
CN (1) CN112052918B (zh)
WO (1) WO2020244443A1 (zh)

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020170332A1 (ja) * 2019-02-19 2020-08-27 賢一 金子 無人飛行装置、管理装置、及び飛行管理方法
US11837100B2 (en) * 2019-06-29 2023-12-05 Rumfert, Llc Method and system for pre-flight programming of a remote identification (remote ID) system for monitoring the flight of an unmanned aircraft system (UAS) in the national airspace system (NAS)
CN113990112B (zh) * 2021-10-25 2023-01-31 浙江这里飞科技有限公司 一种无人机的监管方法、装置、电子设备及存储介质
CN114745710B (zh) * 2022-04-13 2023-04-18 中国联合网络通信集团有限公司 一种空域准入方法、装置及系统
US11651694B1 (en) * 2022-05-04 2023-05-16 Beta Air, Llc Apparatus for encrypting external communication for an electric aircraft
AU2024376397A1 (en) 2023-06-23 2025-12-18 File, David J. Twin fan, redundantly configured vertical lift vehicle
CN117975595A (zh) * 2023-12-26 2024-05-03 中国航空工业集团公司西安飞机设计研究所 一种飞行参数记录及回放系统

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2008105591A (ja) * 2006-10-26 2008-05-08 Hiroboo Kk 自律制御無人飛行体の飛行管理方法
CN101788958A (zh) * 2010-02-04 2010-07-28 杭州晟元芯片技术有限公司 一种存储器数据保护的方法
CN103578300A (zh) * 2013-11-06 2014-02-12 华北计算技术研究所 一种面向网络的低空飞行动态监视系统
CN107609612A (zh) * 2017-09-15 2018-01-19 山东东进航空科技有限公司 通用航空飞行器监视管控数字标识系统及方法

Family Cites Families (53)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9489813B1 (en) * 2006-09-22 2016-11-08 Michael L. Beigel System for location in environment and identification tag
US8509982B2 (en) * 2010-10-05 2013-08-13 Google Inc. Zone driving
CN102915576B (zh) * 2012-08-17 2015-09-09 中国航天空气动力技术研究院 一种无人机电子履历记录装置
US9821910B1 (en) * 2015-05-19 2017-11-21 uAvionix Corporation Unmanned vehicle control system and apparatus
WO2015175440A1 (en) * 2014-05-12 2015-11-19 Unmanned Innovation, Inc. Unmanned aerial vehicle authorization and geofence envelope determination
KR20160013713A (ko) * 2014-07-28 2016-02-05 현대자동차주식회사 자율주행차량의 전역경로 생성장치 및 방법
EP3271688B1 (en) * 2015-03-16 2022-08-03 Nokia Technologies Oy Location privacy
CN107409051B (zh) * 2015-03-31 2021-02-26 深圳市大疆创新科技有限公司 用于生成飞行管制的认证系统和方法
WO2016164892A1 (en) * 2015-04-10 2016-10-13 The Board Of Regents Of The Nevada System Of Higher Education On Behalf Of The University Of Nevada, Las Vegas Methods and systems for unmanned aircraft system (uas) traffic management
WO2017013417A1 (en) * 2015-07-17 2017-01-26 Relmatech Limited An aircraft controlled by a secure integrated airspace management system
US10733894B1 (en) * 2015-08-24 2020-08-04 uAvionix Corporation Direct-broadcast remote identification (RID) device for unmanned aircraft systems (UAS)
WO2017032906A2 (en) * 2015-08-27 2017-03-02 Dronsystems Limited A highly automated system of air traffic control (atm) for at least one unmanned aerial vehicle (unmanned aerial vehicles uav)
US9605970B1 (en) * 2015-09-03 2017-03-28 Harman International Industries, Incorporated Methods and systems for driver assistance
US10229329B2 (en) * 2016-11-08 2019-03-12 Dedrone Holdings, Inc. Systems, methods, apparatuses, and devices for identifying, tracking, and managing unmanned aerial vehicles
WO2017084031A1 (en) * 2015-11-17 2017-05-26 SZ DJI Technology Co., Ltd. Systems and methods for managing flight-restriction regions
US10319245B2 (en) * 2015-12-28 2019-06-11 Kddi Corporation Flight vehicle control device, flight permitted airspace setting system, flight vehicle control method and program
US10061311B2 (en) * 2016-03-01 2018-08-28 Vigilent Inc. System for identifying and controlling unmanned aerial vehicles
US9805238B2 (en) * 2016-03-01 2017-10-31 Vigilent Inc. System for identifying and controlling unmanned aerial vehicles
US10126136B2 (en) * 2016-06-14 2018-11-13 nuTonomy Inc. Route planning for an autonomous vehicle
EP3494445B1 (en) * 2016-08-02 2020-11-04 PCMS Holdings, Inc. System and method for optimizing autonomous vehicle capabilities in route planning
US10060753B2 (en) * 2016-08-17 2018-08-28 Apple Inc. On-demand shortcut computation for routing
JP6778063B2 (ja) * 2016-09-07 2020-10-28 株式会社Ｓｏｋｅｎ 運転支援装置、運転支援方法
CN114419932A (zh) * 2016-09-27 2022-04-29 深圳市大疆创新科技有限公司 Uav系统的部件和用户管理
US20180120832A1 (en) * 2016-10-27 2018-05-03 Melvin Marx Hintze Unmanned aircraft systems (uas) robotic-platform (drone) management
US10710710B2 (en) * 2016-10-27 2020-07-14 International Business Machines Corporation Unmanned aerial vehicle (UAV) compliance using standard protocol requirements and components to enable identifying and controlling rogue UAVS
CN108698704B (zh) * 2017-01-24 2022-02-08 深圳市大疆创新科技有限公司 飞行指示设备、系统和相关方法
CN106937275B (zh) * 2017-02-13 2020-10-16 深圳盈达信息科技有限公司 一种在安卓系统下保存系统唯一标识及硬件id的设备
US10825345B2 (en) * 2017-03-09 2020-11-03 Thomas Kenji Sugahara Devices, methods and systems for close proximity identification of unmanned aerial systems
US11218840B2 (en) * 2017-03-31 2022-01-04 Telefonaktiebolaget Lm Ericsson (Publ) Methods and systems for using network location services in a unmanned aircraft systems traffic management framework
CN110476455B (zh) * 2017-04-28 2021-10-26 Kddi株式会社 无线通信装置、通信控制方法和计算机程序
US10663597B1 (en) * 2017-08-21 2020-05-26 Wing Aviation Llc Dual-technology onboard air traffic tracking system for autonomous aerial vehicles
CN207115471U (zh) * 2017-09-15 2018-03-16 山东东进航空科技有限公司 通航“低慢小”飞行器数字身份电子标识系统
US11508245B2 (en) * 2017-09-28 2022-11-22 Kyocera Corporation Preamble management for unmanned aerial vehicles
US10710607B2 (en) * 2018-02-12 2020-07-14 Lenovo (Singapore) Pte. Ltd. Systems and methods for identifying first route to destination as involving less human driving of vehicle than second route to destination
WO2019186245A1 (en) * 2018-03-30 2019-10-03 Telefonaktiebolaget Lm Ericsson (Publ) Network coverage and policy information generation and distribution for unmanned aerial vehicle flight planning
US12033516B1 (en) * 2018-09-22 2024-07-09 Pierce Aerospace Incorporated Systems and methods for remote identification of unmanned aircraft systems
JP6748797B1 (ja) * 2018-12-25 2020-09-02 楽天株式会社 無人航空機制御システム、無人航空機制御方法、及びプログラム
US11837100B2 (en) * 2019-06-29 2023-12-05 Rumfert, Llc Method and system for pre-flight programming of a remote identification (remote ID) system for monitoring the flight of an unmanned aircraft system (UAS) in the national airspace system (NAS)
US20210048825A1 (en) * 2019-08-13 2021-02-18 GM Global Technology Operations LLC Predictive and reactive field-of-view-based planning for autonomous driving
US11453410B2 (en) * 2019-11-18 2022-09-27 Hitachi, Ltd. Reducing processing requirements for vehicle control
WO2021168347A1 (en) * 2020-02-20 2021-08-26 Skytask, Inc. Uavs, including multi-processor uavs with secured parameters, and associated systems, devices, and methods
US11495131B2 (en) * 2020-02-21 2022-11-08 Qualcomm Incorporated Vehicle to vehicle safety messaging congestion control for platooning vehicles
WO2021231165A1 (en) * 2020-05-12 2021-11-18 Qualcomm Incorporated Providing security credentials to an unmanned aerial vehicle
US11610492B2 (en) * 2020-05-16 2023-03-21 Aero Systems West, Inc. Unified data management system for unmanned vehicles using distributed architecture
US11543259B2 (en) * 2020-06-05 2023-01-03 Hitachi, Ltd. Determining landmark detectability
US11585669B2 (en) * 2020-08-31 2023-02-21 Hitachi, Ltd. Vehicle routing using connected data analytics platform
US11713060B2 (en) * 2020-09-18 2023-08-01 Guident Ltd. Systems and methods for remote monitoring of a vehicle, robot or drone
US20210108929A1 (en) * 2020-12-22 2021-04-15 Yi Zhang Dynamic selection of autonomous vehicle stopping points
US12123729B2 (en) * 2021-09-16 2024-10-22 Hitachi, Ltd. Precautionary observation zone for vehicle routing
US11651694B1 (en) * 2022-05-04 2023-05-16 Beta Air, Llc Apparatus for encrypting external communication for an electric aircraft
US20240118096A1 (en) * 2022-10-07 2024-04-11 Hitachi, Ltd. Localization and path planning of electric systems during dynamic charging
US12093698B2 (en) * 2023-01-23 2024-09-17 Arinc Incorporated Dynamic pre-boot configuration for flight systems
US12014640B1 (en) * 2023-06-07 2024-06-18 MetroStar Systems LLC Drone to drone communication and task assignment

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2008105591A (ja) * 2006-10-26 2008-05-08 Hiroboo Kk 自律制御無人飛行体の飛行管理方法
CN101788958A (zh) * 2010-02-04 2010-07-28 杭州晟元芯片技术有限公司 一种存储器数据保护的方法
CN103578300A (zh) * 2013-11-06 2014-02-12 华北计算技术研究所 一种面向网络的低空飞行动态监视系统
CN107609612A (zh) * 2017-09-15 2018-01-19 山东东进航空科技有限公司 通用航空飞行器监视管控数字标识系统及方法

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3968226A4

Also Published As

Publication number Publication date
CN112052918A (zh) 2020-12-08
CN112052918B (zh) 2022-05-10
EP3968226A4 (en) 2022-07-20
US20220092989A1 (en) 2022-03-24
EP3968226A1 (en) 2022-03-16
US12347322B2 (en) 2025-07-01

Similar Documents

Publication Publication Date Title
WO2020244443A1 (zh) 一种无人机身份标识模组及存储方法
KR102771444B1 (ko) 클라우드 기반의 edr 데이터 관리 방법 및 시스템
JP7685184B2 (ja) セキュアロックダウンを実装するように構成された関連装置を有する特別にプログラムされたコンピューティングシステムおよびその使用方法
US12407525B2 (en) Verifying vehicular identity
US20240323657A1 (en) Misbehavior detection using data consistency checks for collective perception messages
EP3084676B1 (en) Secure vehicular data management with enhanced privacy
Singh et al. Accountability in the IoT: Systems, law, and ways forward
US20180336024A1 (en) Method and system for hardware identification and software update control
US8290660B2 (en) Data access to electronic control units
KR20140009511A (ko) 광역 접속성을 갖는 ｒｆｉｄ 디바이스
WO2021177670A1 (ko) 차량 생성 데이터를 수집 및 관리하는 방법 및 시스템
US20120330498A1 (en) Secure data store for vehicle networks
US20160062762A1 (en) Self-contained storage device for self-contained application execution
US11640268B2 (en) Timed memory access
CN120811468A (zh) 无人机的飞行数据处理方法、装置以及电子设备
US20170279752A1 (en) Aircraft Message Management System
US9674169B2 (en) Method and system for writing, updating and reading static and dynamic identification data for an aeronautical appliance
CN104023014A (zh) 数据访问权限的控制方法及系统
JP2019118059A (ja) 通信システム、通信制御装置、及び通信制御方法
KR102635485B1 (ko) 무인 이동체의 사고 데이터를 기록하는 방법
CN117473481A (zh) 一种通信方法、装置、域控制器及可读存储介质
WO2020133509A1 (zh) 飞行处理方法及控制设备、无人机、服务器、智能终端
KR20210112241A (ko) 차량 생성 데이터를 수집 및 관리하는 방법 및 시스템
CN109756546B (zh) 智能网联汽车云控操作系统
CN119180016A (zh) 鉴权方法、装置、电子设备、存储介质及程序产品

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20818728

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2020818728

Country of ref document: EP

Effective date: 20211209