Blockchain-based low-altitude safety control method and system

Abstract

This invention discloses a blockchain-based low-altitude safety control method and system. The system includes a low-altitude aircraft device, a CA center, and an edge server. The edge server is equipped with a tool module, a core module, and a smart contract module. When a low-altitude aircraft sends a movement request or takeoff request, the edge server receives the request and initiates a transaction to the smart contract within the network. The smart contract determines whether the conditions for movement or takeoff are met and returns the result to the low-altitude aircraft. This invention offers high security by utilizing emerging blockchain technology for security management. Data sharing and security authentication within the low-altitude smart network are more convenient, and the smart contract-based method allows for automatic execution and greater scalability.

Description

Technical Field

[0001] This invention belongs to the field of low-altitude aircraft safety technology, and in particular relates to a blockchain-based low-altitude safety control method and system. Background Technology

[0002] Low-altitude intelligent networks refer to an intelligent digital network system built by integrating networking, digitalization, and intelligent technologies in low-altitude airspace. It is the most important infrastructure for promoting the industrialization of low-altitude airspace. Current research on the management and control of low-altitude intelligent network devices in areas such as flight control, identity authentication, data transmission, and risk management mainly focuses on low-altitude aircraft traffic management strategies, situational awareness, intrusion detection, data exchange, and authentication.

[0003] Regarding traffic management strategies for unmanned aerial vehicles (UAVs), the International Civil Aviation Organization (ICAO) has established at the top-level concept that civil UAVs need to be managed in two different ways for two types of operating scenarios: one is integrated operation with existing manned aircraft, represented by RPAS (Rolled-Rolled Aircraft System), and the other is isolated operation from existing manned aircraft, represented by light and small UAVs. The Joint Research and Development Consortium on Unmanned Aerial Vehicles (JARUS) has proposed a risk assessment method for permitted operations, which analyzes risk sources based on core events to reduce the consequences of accidents and prevent the probability of accidents. The US UTM framework extends the operating concept to controlled airspace below 400 feet true altitude, describing a more complex BVLOS (Browser-Vehicle-Low Altitude) flight scenario. The European U-space operating concept currently focuses on ultra-low altitude operation scenarios for civil UAVs, and is subdivided into X, Y, and Z airspaces based on the different services provided. The X airspace does not provide any conflict resolution services, the Y airspace provides conflict resolution services before flight, and the Z airspace provides conflict resolution services both before and during flight. In China, the National Key Laboratory of Special Technologies for Unmanned Aerial Vehicles at the School of Aeronautics, Northwestern Polytechnical University, has conducted research on unmanned aerial vehicle (UAV) design and take-off and landing technology verification, solar-powered UAV design and verification technology, guidance and experimental verification technology for attack UAVs, and UAV stealth testing technology.

[0004] However, existing technologies still have some problems: First, it is difficult to form a unified safety management and control strategy standard system; the Low-Altitude Intelligent Network covers a variety of low-altitude flight equipment such as drones, airships, and hot air balloons, resulting in diversified management and control objects and thus complex management and control strategies, making it difficult to form a unified standard system. At the same time, products from different manufacturers also have diversified characteristics, lacking unified strategies, standards, and platforms for collaborative management and control. Second, data sharing and security authentication are difficult; currently, several large-scale low-altitude flight equipment manufacturers have designed their own management and control platforms based on their own product characteristics. These platforms lack unified technical standards and are difficult to achieve services such as data sharing and security authentication. In addition, the scalability of existing methods is not high; the diverse and complex strategies generated by current heterogeneous low-altitude aircraft are characterized by diverse categories, large differences in requirements, multimodal data, and rapid data updates, requiring extremely high scalability of strategies and standards. Summary of the Invention

[0005] To address the shortcomings of the existing technologies, the purpose of this invention is to provide a blockchain-based low-altitude safety control method and system to achieve data sharing and security authentication among various low-altitude flight devices, and to solve the problems of existing technologies being unable to cross platforms and having poor scalability.

[0006] This invention addresses the limitations of existing technologies in terms of cross-platform compatibility and scalability through the following technical solution, and enables data sharing and security authentication among various low-altitude flight devices: a blockchain-based low-altitude safety control system, comprising:

[0007] Low-altitude aircraft equipment: used to collect data, encrypt and verify information using asymmetric encryption technology, and send mission requests to the edge server;

[0008] CA Center: Used to verify the legitimacy of public keys in the public key system, and to send and manage digital certificates to all devices participating in the low-altitude safety control system;

[0009] Edge server: used to generate public key pairs and apply for digital certificates from the CA center; use the return value to form return information and send it to the low-altitude aircraft equipment; the edge server includes a blockchain-based security management platform.

[0010] Furthermore, the blockchain-based security management platform includes:

[0011] Tool module: Used by the core module and smart contract module to implement data storage, processing and transmission functions;

[0012] Core module: Used to implement blockchain transactions published by the smart contract module; includes a complete blockchain core system;

[0013] Smart Contract Module: Used to build smart contract transactions and publish those transactions in the core module.

[0014] Furthermore, the tool module encapsulates digital signature and signature verification functions, message digest functions, byte encoding tools, encoding and decoding tools, file operation tools, JSON string tools, database operation tools, log file tools, and network utility classes. It also encapsulates a Merkle tree structure, where each node is marked with a cryptographic hash value of a data block.

[0015] Furthermore, the core module includes a network core;

[0016] The network core includes: local core, seed node initializer, node searcher, node broadcaster, blockchain height searcher, blockchain height broadcaster, block searcher, block broadcaster, and unconfirmed transaction searcher.

[0017] The local core includes: a blockchain database, an unconfirmed transaction database, and a block building module.

[0018] Furthermore, the smart contract module includes:

[0019] Contract layer: Provides the language and code library for smart contract development, as well as the necessary APIs for interacting with the blockchain;

[0020] Compilation layer: Used to compile contract code into bytecode that can be executed by the virtual machine;

[0021] Injection layer: Used to inject components into the contract bytecode before contract execution;

[0022] Execution layer: Checks the contract's execution permissions, creates a sandbox environment and allocates resources, and uses an interpreter to run the contract bytecode.

[0023] Another objective of this invention is to provide a blockchain-based low-altitude safety control method to achieve a unified safety control standard system for low-altitude aircraft equipment.

[0024] The control methods include a low-altitude aircraft safe takeoff control method and a low-altitude aircraft safe airspace control method:

[0025] The safe takeoff control method for low-altitude aircraft includes the following steps:

[0026] S11. All low-altitude aircraft equipment and edge servers generate their own public key pairs and apply for response certificates from the CA center.

[0027] S12, The low-altitude aircraft sends a takeoff request to the edge server of its region;

[0028] S13. The edge server verifies the task request through the tool module; after successful verification, it executes the task content in the task request and generates a transaction pointing to the takeoff smart contract address.

[0029] S14. The Takeoff smart contract responds to the transaction and outputs a return value to the edge server;

[0030] S15. The edge server generates return information based on the return value through the core module and sends it to the low-altitude aircraft equipment.

[0031] S16. After receiving the return information, the low-altitude aircraft equipment verifies it; if the verification is successful, it performs the corresponding operation based on the return information.

[0032] The method for controlling safe airspace for low-altitude aircraft includes the following steps:

[0033] S21. All low-altitude aircraft equipment and edge servers generate their own public key pairs and apply for response certificates from the CA center.

[0034] S22. The low-altitude aircraft sends a move request to the edge server of its region.

[0035] S23. The edge server verifies the task request through the tool module; after successful verification, it executes the task content in the task request and generates a transaction pointing to the mobile smart contract address.

[0036] S24. The mobile smart contract responds to the transaction, outputs a return value to the edge server, or continues to generate a transaction pointing to the address of the airspace control smart contract and triggers the airspace control smart contract, which outputs a return value to the edge server.

[0037] S25. The edge server generates return information based on the return value through the network core module and sends it to the low-altitude aircraft equipment.

[0038] S26. After receiving the return information, the low-altitude aircraft equipment verifies it; if the verification is successful, it performs the corresponding operation based on the return information.

[0039] Furthermore, the mission request sent by the low-altitude aircraft includes a mission number, mission content, the low-altitude aircraft's signature, and the low-altitude aircraft's certificate; the returned information includes a mission number, mission content, return value, the edge server's signature, and the edge server's certificate.

[0040] Furthermore, the transaction generated by the edge server includes the transaction initiator, transaction address, and parameters; the transaction initiator is the edge server, the transaction address is the address of the mobile smart contract, and the parameters are the relevant information of the low-altitude aircraft and its location information.

[0041] Furthermore, when the edge server verifies the task request, it verifies the task request by using the low-altitude aircraft signature and the low-altitude aircraft certificate in the task request.

[0042] The specific process of generating the transaction is as follows: the edge server generates a transaction pointing to the smart contract based on the task content and publishes it to the core of the blockchain network, triggering the smart contract to obtain a return value; wherein, the transaction initiator is the edge server; the transaction address is the address of the smart contract, and the parameters are the relevant information of the low-altitude aircraft and the task content information.

[0043] Furthermore, the response process of the mobile smart contract is as follows:

[0044] S241. The edge server receives the low-altitude aircraft's movement request and sends a transaction to the movement smart contract in the network.

[0045] S242. The mobile smart contract determines the movement method, including three parameters: longitude, latitude, and altitude to be moved to. The parameter fields in the transaction are used as the parameters for movement, and the method is executed.

[0046] S243. During the operation of the movement method, the movement smart contract determines whether the location to be moved to is under control through the control location database. If the area is not under control, the movement smart contract returns True, and this return value is also returned to the edge server as the return value of the movement smart contract. After receiving the return value, the edge server returns the return value to the corresponding low-altitude aircraft. If the area is under control, a new transaction is returned, in which the transaction initiator is the edge server, the transaction address is the address of the airspace control smart contract, and the parameters are the low-altitude aircraft information and the movement location information. After receiving the new transaction, the edge server sends it to the blockchain network, triggering the airspace control smart contract and receiving the return value False. After receiving the return value, the edge server returns the return value to the corresponding low-altitude aircraft.

[0047] The response process of the takeoff smart contract is as follows:

[0048] S141. The edge server receives the takeoff request from the low-altitude aircraft and sends a transaction in the network to the takeoff smart contract.

[0049] S142. The takeoff smart contract determines the takeoff method, where the parameters represent the longitude and latitude of the takeoff point, respectively; the parameter fields in the transaction are used as the parameters for takeoff, and the method is executed.

[0050] S143. During the operation of the takeoff method, the takeoff smart contract determines whether the current takeoff point has been controlled by the control location database. If the area is not controlled, the takeoff smart contract returns True; if the area is controlled, the takeoff smart contract returns False. This return value will also be returned to the edge server as the return value of the takeoff smart contract. After receiving the return value, the edge server will return the return value to the corresponding low-altitude aircraft.

[0051] Compared with the prior art, the beneficial effects of the present invention are: (1) Based on sorting out the complex application scenarios of heterogeneous low-altitude aircraft, the present invention uses blockchain-based smart contracts to model the space environment, cyber-physical data, policy relationships, and control parameters, and constructs a multi-dimensional cross-platform policy paradigm, and constructs a unified description specification for behavior actions, logical judgments, control flow, etc. (2) Based on the blockchain system, the present invention focuses on aircraft identity authentication, access control, data collection, data sharing, data interaction, behavior recognition, and situational awareness, and realizes the configurable management of various security services through the setting of smart contracts. (3) The security control method of the present invention is implemented based on smart contracts on the blockchain, which can be easily and conveniently extended and updated. Attached Figure Description

[0052] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0053] Figure 1 This is a schematic diagram of a blockchain-based low-altitude safety control system;

[0054] Figure 2 This is a block diagram of the components of the edge server layer;

[0055] Figure 3 (a) is a flowchart of the safety control method for low-altitude aircraft; (b) is a flowchart of the takeoff control method for low-altitude aircraft.

[0056] Figure 4 It is the block structure diagram generated by the edge server;

[0057] Figure 5 It is a diagram of the aggregated block structure built by the edge servers;

[0058] Figure 6 This is a diagram of a smart contract architecture. Detailed Implementation

[0059] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of the present invention.

[0060] like Figure 1 This invention proposes a blockchain-based security control system for low-altitude smart network environments, and utilizes smart contracts to implement method customization and parsing (such as...). Figure 1 (As shown). The proposed system consists of low-altitude aircraft equipment, an edge server, and a CA center.

[0061] CA Center: As a trusted third party in the system, the CA is responsible for verifying the legitimacy of public keys in the public key system and for sending and managing digital certificates for all devices participating in the system.

[0062] Low-altitude aircraft equipment: Low-altitude aircraft equipment is the source of data and uses asymmetric encryption technology to encrypt and verify information to eliminate data leakage problems.

[0063] Edge Servers: The edge server layer inherits multiple modules from the blockchain, building a blockchain-based security management platform. For example... Figure 2 The edge server layer blockchain, as shown, adopts a modular design, divided into a tool module, a core module, and a smart contract module. The core module utilizes a combination of a local core and a network core to complete basic blockchain operations. The local core's functions include: blockchain account generation, transfers, submitting transactions to the blockchain, adding new blocks to the blockchain, data verification (block verification, transaction verification), on-chain block rollback, on-chain block query, transaction query, and account fund query. The local core system consists of the following parts: a blockchain database (used to persist data on the local blockchain), an unconfirmed transaction database (stores unconfirmed transaction data), and a block building module (putting new blocks into the blockchain database).

[0064] The network core represents a complete blockchain network core system. The blockchain network core relies on the local blockchain core (BlockchainCore) at its core, adding network functionality on top of the local core: automatically searching for and publishing nodes, blocks, and transactions throughout the entire blockchain network. Upon startup, it adds seed nodes to its known node list through a seed node initializer, searches for nodes in the blockchain network through a node searcher, informs other nodes of its existence through a node broadcaster, searches for the height of known nodes through a blockchain height searcher, finds the latest block through a block searcher, informs other nodes of its height through a blockchain height broadcaster, and broadcasts its latest block through a block broadcaster. Each network core performs these operations, thus interconnecting and collaborating to form the blockchain network. The network core consists of the following components: local core, seed node initializer, node searcher, node broadcaster, blockchain height searcher, blockchain height broadcaster, block searcher, block broadcaster, and unconfirmed transaction searcher.

[0065] The smart contract module implements functions including contract compilation, contract deployment, contract debugging, contract upgrade, and contract testing.

[0066] The utility module encapsulates digital signature and signature verification functions, message digest functions (SHA-256, RipeMD160), byte encoding tools (Base58, Hex), encoding / decoding tools (encoding Object T to byte arrays), file operation tools (creating, deleting, modifying, and querying files), JSON string tools (converting JSON strings and class objects), database operation tools (creating, deleting, modifying, and querying databases), log file tools (error message retrieval), and network utility classes (network connectivity). It also encapsulates a Merkle tree structure, where each node is marked with a cryptographic hash value representing a data block. Merkle trees can be used to verify any data stored, processed, and transmitted within and between computers. They ensure that data transmission speed is unaffected, and that data is neither corrupted nor altered in peer-to-peer networks.

[0067] Example 1: Airspace Control Method for Low-Altitude Aircraft

[0068] like Figure 3 In (a), the airspace control method is implemented through the following process:

[0069] 1) Low-altitude aircraft x sends a move request to the edge server of its region.

[0070] 2) When the edge server receives the movement request from the low-altitude aircraft x, it triggers the original movement smart contract. When executing the movement smart contract, it finds that the airspace that the low-altitude aircraft x intends to move to has been controlled, triggering the airspace control smart contract. The edge server sends a rejection message to the low-altitude aircraft x.

[0071] Example 2: Low-altitude aircraft takeoff control method

[0072] like Figure 3 In (b), the low-altitude aircraft takeoff control method is implemented through the following process:

[0073] The low-altitude aircraft x sends a takeoff request to the edge server of its region.

[0074] The edge server receives a takeoff request from low-altitude aircraft x, triggering the scheduled takeoff smart contract. The edge server then sends an agreement / disagreement message to low-altitude aircraft x.

[0075] like Figure 4 At regular intervals, low-altitude aircraft within the service area of ​​an edge server will package all the information they have served during that interval into blocks and broadcast them to other edge servers. For example... Figure 5 Once the edge server receives all the blocks from the edge servers, it constructs an aggregated block using the MPT tree method.

[0076] Example 3: Security Authentication and Data Sharing

[0077] In the architecture proposed in this invention, all edge servers have their own private key and corresponding public key address. The process is as follows:

[0078] The edge server randomly generates (or specifies) a 32-byte private key.

[0079] An elliptic curve cryptography algorithm is used to generate a 64-byte public key from the private key.

[0080] A 32-byte compressed public key is generated from a 64-byte public key using keccak-256.

[0081] Take the last 20 bytes of the 32-bit compressed public key as the account address of the edge server.

[0082] All information in communication between edge servers and between edge servers and low-altitude aircraft is signed with a private key, thus preventing information tampering such as man-in-the-middle attacks. The signer uses their private key to sign the information to be signed, and the verifier uses the signature, the signed information, and the signer's public key to verify the signed information. To increase the scalability of the architecture and facilitate rapid block retrieval by edge servers, this invention constructs different blocks from different edge servers in the aggregated block structure using account addresses as the standard, in the form of an MPT tree (an MPT tree is a data structure that combines the advantages of Merkle trees and prefix trees). Figure 1 As shown, low-altitude aircraft devices in the same edge server region can directly share data, while low-altitude aircraft devices across different regions can share data through the edge server.

[0083] Example 4: Strategies Based on Smart Contracts

[0084] A smart contract is a piece of code written on the blockchain. Once an event triggers a clause in the contract, the code executes automatically. In other words, it executes as soon as the conditions are met, without human intervention. Unlike traditional server scripts, smart contracts give applications two important characteristics: first, they use on-chain data to determine contract conditions and execute automatically when they are met, with no institution able to interfere with the process; second, the execution process satisfies ALL or Nothing, i.e., atomicity.

[0085] The working principle of the smart contract module is as follows:

[0086] Smart contracts are deployed on the blockchain in the form of bytecode. Developers encapsulate the smart contract methods they want to call and their parameters in the form of a transaction and send it to the virtual machine. The virtual machine obtains the corresponding contract bytecode and uses the thread scheduler to complete the call to the contract method. Smart contracts have the characteristic of asynchronous response, meaning that when other users call them, the code within the smart contract is triggered to execute and return a value. However, this transaction (smart contract) is only recognized by all users in the system and truly responded to after it is packaged into a block and linked to the blockchain.

[0087] The architecture of smart contracts is as follows Figure 6 As shown, from top to bottom, it includes the contract layer, compilation layer, injection layer, and execution layer.

[0088] Contract layer: Provides the language and code library for smart contract development, as well as the necessary APIs for interacting with the blockchain.

[0089] Compilation layer: Responsible for compiling contract code into bytecode that can be executed by the virtual machine.

[0090] Injection layer: Generally, some components are injected into the contract bytecode before the contract is executed, including the specific implementation of the Env API, the gas measurement function, and the context environment for the contract execution.

[0091] Execution layer: Checks contract execution permissions, creates a sandbox environment and allocates resources, and runs the contract bytecode using an interpreter. During execution, a state database and blockchain ledger are provided as the data backend.

[0092] Example 5: Edge Server Workflow

[0093] S1. System initialization and key generation: All systems generate their own public key pairs and apply for the corresponding certificates from the CA structure;

[0094] S2, the low-altitude aircraft sends a mission request (mission number, mission content, low-altitude aircraft signature, low-altitude aircraft certificate) to the edge server;

[0095] S3. After receiving the task request from the low-altitude aircraft, the edge server uses the low-altitude aircraft signature and certificate in the task request to verify the task and determine whether the task is from the correct source and has not been tampered with.

[0096] S4. After the task request is verified, the edge server will execute the task content in the task request. The task content is a low-altitude aircraft movement request. The edge server will generate a transaction <transaction initiator, transaction address, parameters>, where the transaction initiator is the edge server, the transaction address is the address of the mobile smart contract, and the parameters are the relevant information of the low-altitude aircraft and its movement location information. The edge server publishes the transaction to the blockchain network, triggering the mobile smart contract and receiving a return value.

[0097] S5. The edge server uses the return value to form return information (task number, task content, return value, edge server signature, edge server certificate) and sends it to the low-altitude aircraft.

[0098] S6. After receiving the return information, the low-altitude aircraft also verifies the signature and certificate of the edge server to prevent information tampering. Once verification is successful, the low-altitude aircraft performs the corresponding operation based on the return value in the returned information.

[0099] Example 6: Mobile Smart Contract Response Process

[0100] When a transaction address in the network points to a smart contract, that smart contract is triggered. For example, in a low-altitude aircraft movement request, the edge server receives the low-altitude aircraft movement request and sends a transaction in the network pointing to the movement smart contract. The movement smart contract then responds through the following steps:

[0101] S1. The mobile smart contract originally defined a move method (Longitude, Dimensionality, Height), where the parameters represent the longitude, latitude, and altitude to which the move is to be made. The parameter fields in the transaction are used as the parameters for the move, and the method is executed.

[0102] S2. During the execution of the move method, the system queries the controlled location database to determine whether the location to be moved to is already controlled. If the area is not controlled, the move method will return True, and this return value will also be returned to the edge server as the return value of the move smart contract. After receiving the return value, the edge server will return it to the corresponding task initiator. If the area is controlled, the move method will return a new transaction, where the transaction initiator is the edge server, the transaction address is the address of the airspace control smart contract, and the parameters are low-altitude aircraft information and movement location information. After receiving the new transaction, the edge server sends it to the blockchain network, triggering the airspace control smart contract and receiving the return value.

[0103] Example 7: Takeoff Smart Contract Response Process

[0104] The edge server receives a takeoff request from the low-altitude aircraft and sends a transaction to the takeoff smart contract over the network. The takeoff smart contract then responds through the following steps:

[0105] S1. The edge server receives the takeoff request from the low-altitude aircraft and sends a transaction in the network to the takeoff smart contract;

[0106] S2, the Take-off smart contract originally defined the Take-off(Longitude, Dimensionality) method, where the parameters represent the longitude and latitude of the take-off point, respectively. The parameter fields in the transaction are used as the parameters for Take-off, and this method is executed.

[0107] S3. During the takeoff process, the takeoff smart contract determines whether the current takeoff point has been controlled by the control location database. If the area is not controlled, the takeoff smart contract returns True; if the area is controlled, the takeoff smart contract returns False. This return value will also be returned to the edge server as the return value of the takeoff smart contract. After receiving the return value, the edge server will return the return value to the corresponding low-altitude aircraft.

[0108] This invention proposes implementing various strategies and standards in the low-altitude intelligent network in the form of smart contracts. This allows different manufacturers and different aircraft to customize and parse the corresponding strategies and standards, as long as they possess the same virtual machine environment for smart contract parsing. Implementing strategies and standards in the form of smart contracts also facilitates their expansion and updates. If a strategy or standard needs updating, only the original smart contract needs to be modified and redeployed into the blockchain system; other edge servers and low-altitude aircraft equipment can then receive the updated strategy and standard instantly.

[0109] The various embodiments in this specification are described in a related manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, the system embodiments are basically similar to the method embodiments, so the description is relatively simple; relevant parts can be referred to the descriptions of the method embodiments.

[0110] The above description is merely a preferred embodiment of the present invention and is not intended to limit the scope of protection of the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention are included within the scope of protection of the present invention.

Claims

1. A blockchain-based low-altitude safety control method, characterized in that, This includes methods for safe takeoff control of low-altitude aircraft and methods for safe airspace control of low-altitude aircraft. The safe takeoff control method for low-altitude aircraft includes the following steps: S11. All low-altitude aircraft equipment and edge servers generate their own public key pairs and apply for response certificates from the CA center. S12, The low-altitude aircraft sends a takeoff request to the edge server of its region; S13. The edge server verifies the task request through the tool module; after successful verification, it executes the task content in the task request and generates a transaction pointing to the takeoff smart contract address. S14. The Takeoff smart contract responds to the transaction and outputs a return value to the edge server; S15. The edge server generates return information based on the return value through the core module and sends it to the low-altitude aircraft equipment. S16. After receiving the return information, the low-altitude aircraft equipment verifies it; if the verification is successful, it performs the corresponding operation based on the return information. The method for controlling safe airspace for low-altitude aircraft includes the following steps: S21. All low-altitude aircraft equipment and edge servers generate their own public key pairs and apply for response certificates from the CA center. S22. The low-altitude aircraft sends a move request to the edge server of its region. S23. The edge server verifies the task request through the tool module; after successful verification, it executes the task content in the task request and generates a transaction pointing to the mobile smart contract address. S24. The mobile smart contract responds to the transaction, outputs a return value to the edge server, or continues to generate a transaction pointing to the address of the airspace control smart contract and triggers the airspace control smart contract, which outputs a return value to the edge server. S25. The edge server generates return information based on the return value through the core module and sends it to the low-altitude aircraft equipment. S26. After receiving the return information, the low-altitude aircraft equipment verifies it; if the verification is successful, it performs the corresponding operation based on the return information.

2. The blockchain-based low-altitude safety control method according to claim 1, characterized in that, The mission request sent by the low-altitude aircraft includes a mission number, mission content, the low-altitude aircraft's signature, and the low-altitude aircraft's certificate; the returned information includes a mission number, mission content, return value, the edge server's signature, and the edge server's certificate.

3. The blockchain-based low-altitude safety control method according to claim 1, characterized in that, The transaction generated by the edge server includes the transaction initiator, transaction address, and parameters; the transaction initiator is the edge server, the transaction address is the address of the mobile smart contract, and the parameters are the relevant information of the low-altitude aircraft and its location information.

4. The blockchain-based low-altitude safety control method according to any one of claims 1 to 3, characterized in that, When the edge server verifies a task request, it verifies the task request by using the signature and certificate of the low-altitude aircraft in the task request. The specific process of generating a transaction is as follows: the edge server generates a transaction pointing to a smart contract based on the task content and publishes it to the core of the blockchain network, triggering the smart contract to obtain a return value; the transaction initiator is the edge server; the transaction address is the address of the smart contract; and the parameters are relevant information about the low-altitude aircraft and the task content information.

5. The blockchain-based low-altitude safety control method according to claim 1, characterized in that, The response process of the mobile smart contract is as follows: S241. The edge server receives the low-altitude aircraft's movement request and sends a transaction to the movement smart contract in the network. S242. The mobile smart contract determines the movement method, including three parameters: longitude, latitude, and altitude to be moved to. The parameter fields in the transaction are used as the parameters for movement, and the method is executed. S243. During the operation of the movement method, the movement smart contract determines whether the location to be moved to is under control through the control location database. If the area is not under control, the movement smart contract returns True, and this return value is also returned to the edge server as the return value of the movement smart contract. After receiving the return value, the edge server returns the return value to the corresponding low-altitude aircraft. If the area is under control, a new transaction is returned, in which the transaction initiator is the edge server, the transaction address is the address of the airspace control smart contract, and the parameters are the low-altitude aircraft information and the movement location information. After receiving the new transaction, the edge server sends it to the blockchain network, triggering the airspace control smart contract and receiving the return value False. After receiving the return value, the edge server returns the return value to the corresponding low-altitude aircraft. The response process of the takeoff smart contract is as follows: S141. The edge server receives the takeoff request from the low-altitude aircraft and sends a transaction in the network to the takeoff smart contract. S142. The takeoff smart contract determines the takeoff method, where the parameters represent the longitude and latitude of the takeoff point, respectively; the parameter fields in the transaction are used as the parameters for takeoff, and the method is executed. S143. During the operation of the takeoff method, the takeoff smart contract determines whether the current takeoff point has been controlled by the control location database. If the area is not controlled, the takeoff smart contract returns True; if the area is controlled, the takeoff smart contract returns False. This return value will also be returned to the edge server as the return value of the takeoff smart contract. After receiving the return value, the edge server will return the return value to the corresponding low-altitude aircraft.

Images