|
US$1849.00 · In stock
Delivery: <= 9 days. True-PDF full-copy in English will be manually translated and delivered via email.
MHT2011-2019: Data specifications of unmanned aircraft cloud system
Status: Valid
| Standard ID | Contents [version] | USD | STEP2 | [PDF] delivered in | Standard Title (Description) | Status | PDF |
| MH/T 2011-2019 | English | 1849 |
Add to Cart
|
9 days [Need to translate]
|
Data specifications of unmanned aircraft cloud system
| Valid |
MH/T 2011-2019
|
PDF similar to MHT2011-2019
Basic data | Standard ID | MH/T 2011-2019 (MH/T2011-2019) | | Description (Translated English) | Data specifications of unmanned aircraft cloud system | | Sector / Industry | Civil Aviation Industry Standard (Recommended) | | Classification of Chinese Standard | V53 | | Word Count Estimation | 74,734 | | Date of Issue | 2019-10-22 | | Date of Implementation | 2020-1-1 | | Issuing agency(ies) | Civil Aviation Administration of China | MHT2011-2019: Data specifications of unmanned aircraft cloud system---This is a DRAFT version for illustration, not a final translation. Full copy of true-PDF in English version (including equations, symbols, images, flow-chart, tables, and figures etc.) will be manually/carefully translated upon your order.
Data specifications of unmanned aircraft cloud system
ICS 35.240.99
V 53
Civil Aviation Industry Standard of the People's Republic of China
UAV cloud system data specification
2019-10-22 release
2020-01-01 Implementation
Issued by Civil Aviation Administration of China
Table of contents
Foreword...II
1 Scope...1
2 Normative references...1
3 Terms and definitions...1
4 Abbreviations...2
5 Overview...2
6 Data transmission requirements for UAV system and UAV cloud system...5
7 Data transmission requirements for UAV cloud system and UAV cloud exchange system...9
8 Other capability requirements of UAV cloud system...9
9 Test requirements for UAV cloud system...11
10 Data interface description of UAV system and UAV cloud system...12
11 Description of data interface between UAV cloud system and UAV cloud exchange system...25
Appendix A (informative appendix) UAV cloud system and UAV cloud exchange system data interface description...32
Appendix B (informative appendix) Description of message header and message number for UAV flight management data transmission...45
Appendix C (informative appendix) UAV cloud system data specification test outline...47
Appendix D (Normative appendix) UAV operation scene classification and data specification code table...64
Appendix E (informative appendix) Description of related information elements...67
Foreword
This standard was drafted in accordance with the rules given in GB/T 1.1-2009.
This standard was proposed by the Flight Standards Department of the Civil Aviation Administration of China.
This standard is under the jurisdiction of the China Academy of Civil Aviation Science and Technology.
The organization responsible for drafting this standard. China Academy of Civil Aviation Science and Technology.
Participants in the drafting of this standard. The Second Research Institute of the Civil Aviation Administration of China, Beijing Youyun Zhixiang Aviation Technology Co., Ltd., Shanghai Huawei
Technology Co., Ltd., Beijing Yunwuyou Big Data Technology Co., Ltd., Qingdao Cloud Century Information Technology Co., Ltd., Tianyu Jingwei (Beijing) Branch
Technology Co., Ltd.
The main drafters of this standard. Bai Yiqin, Chen Xinfeng, Zou Xiang, Wang Hanqing, Li Gang, Zhou Zhenbo, Wang Liang, Yang Meng, Sun Longni.
UAV cloud system data specification
1 Scope
This standard specifies that the data in the cloud system of civil drones that meet the requirements of the "Regulations on the Operation of Light and Small UAVs (Trial)" (AC-91-31)
Data transmission requirements, data encryption requirements, coding rules, and performance requirements between content and format and civil UAV cloud systems.
This standard applies to civil UAV cloud systems operating in China and the data exchange and integration between them.
2 Normative references
The following documents are indispensable for the application of this standard. For dated reference documents, only the dated version applies to this standard.
For undated references, the latest version (including all amendments) is applicable to this standard.
3 Terms and definitions
3.1
Flight control system, FCS
A system that performs one or more flight-related controls through an automatic control system, generally including pre-flight route, attitude, airspeed,
Control of aerodynamic shape, structural mode, etc.
3.2
UAV flight data
The longitude, latitude, altitude, speed, direction, mission and other related information of the UAV flight.
3.3
Data link, DL
Data terminal and data communication regulations for UAV system management and control, remote control, telemetry, tracking and positioning, and mission load information transmission
An established data communication network, where equipment includes airborne data terminals, ground (ship) data terminals, and data communication procedures including transmission channels,
Communication protocol, standardized message format.
3.4
MH
Mandatory data
In order to ensure flight safety, the regulator requires the drone system and the data content that its owner and users must report, including the drone’s
Static data such as identification, performance parameters, owner information, operator information, and dynamic data such as flight plans and real-time trajectories.
3.5
Extended data
In order to improve service levels, the cloud system encourages UAV systems and their owners and users to choose the data content to report, including UAV
Static data such as flight envelope and mission load information, as well as dynamic operating data such as telemetry data and detection data.
3.6
Basic service
In order to ensure flight safety, the cloud system provides all UAV systems and their owners, managers and operators with the minimum
Limited information services mainly include services such as airspace information, safety warnings, and plan applications.
3.7
Third party system
A system that provides services such as data, information, and location for UAV cloud systems and UOM.
3.8
Unmanned aircraft cloud exchange system
A real-time dynamic database system that can provide real-time data exchange and sharing for multiple UAV cloud systems. It is a comprehensive civil unmanned aircraft
Integrated management platform (UAS Operation Management System, UOM) subsystem.
4 Abbreviations
The following abbreviations apply to this standard.
5 overview
5.1 The relationship between UAV cloud system and surrounding network elements
This standard specification is based on the classification and classification stipulated by MH/T 2009, and is oriented to drones with different performances, operating scenarios, and flight tasks.
Define unified UAV cloud system data requirements, and support through the optional/required definition of information elements and the ability of UAV cloud system
Flight management with drones. The UAV cloud system and surrounding network elements are shown in Figure 1.
Figure 1 Schematic diagram of UAV cloud system and surrounding network elements
The air traffic management information service system for unmanned aircraft in Figure 1 is the Civil Aviation Administration of China (CAAC for short)
Pilot aircraft flight activities, provide airspace, planning, safety assessment and other services for unmanned aircraft flight, realize and relevant supervision
The information system for departmental collaborative management is the window for the operation and management of unmanned aircraft.
5.2 Data link description
The scope of data link applicable to this standard includes. data transmission link between UAV system and UAV cloud system, UAV cloud system
Data transmission link with UAV cloud exchange system (referred to as exchange system). This standard mainly defines related transmissions for these two data links.
Output requirements, ability requirements, test requirements, etc. Figure 2 shows the data link between UAV system and UAV cloud system.
Figure 2 Schematic diagram of data link between UAV system and UAV cloud system
UAV system and UAV cloud system mainly include the following data link communication.
a) Command and control data link, which is used for the flight operation data link between the UAV and the controller/ground station. It mainly includes two modes.
formula.
1) The driver directly controls the UAV through the local controller, including distributed local control UAV, the data link physical layer
There are huge differences in communication modules;
2) The driver remotely controls the drone through the network, including the distributed network remote control of the drone. In this case, the enterprise server needs to be used.
The server establishes the data link relationship between the UAV and the controller;
b) UAV management and control data link, used for UAV management and control data link between UAV system and UAV cloud system, including
Two sub data links.
1) The data link between the controller and the UAV cloud system is used to control the data between the controller and the UAV cloud system
chain. There are multiple data transmission methods between the controller and the UAV cloud system. the controller communicates directly with the UAV cloud system,
Or relay communication based on enterprise server, etc.;
2) UAV and UAV cloud system data link, used for UAV control data between UAV and UAV cloud system
chain. There are multiple data transmission methods between drones and drone cloud systems. direct communication between drones and drone cloud systems,
Controller-based relay communication, or enterprise server-based relay communication, etc. Different transmission methods to connect to drones
The cloud system meets the requirements of different communication capability levels.
5.3 Data transmission process of UAV cloud system
UAV users and UAV systems should carry out message interaction according to the data transmission process in Figure 3 during the use of UAVs, with different capabilities, etc.
There are differences in the services provided by the UAV cloud system and the message interaction process. UAV system and UAV cloud system data transmission
Refer to Chapter 6 for the transmission process, mainly including. UAV cloud system registration data transmission process, UAV cloud system pre-flight management data transmission
The flight management data transmission process of the flight and UAV flight management and the pilot flight experience data transmission process. UAV cloud system and UAV cloud exchange system
The data transmission process between these processes also mainly includes these processes, but the UAV cloud exchange system mainly completes the message transmission with the UAV cloud system.
Therefore, this standard only makes requirements for certain data transmission processes, please refer to Chapter 7.
Figure 3 Schematic diagram of the data transmission process of the UAV cloud system
6 Data transmission requirements for UAV systems and UAV cloud systems
6.1 Registration data transmission requirements for UAV cloud system
6.1.1 Basic requirements
The user/operator of the drone needs to complete user registration with the drone cloud system. The registration information is that the drone system registers the drone cloud system.
The relevant information required to register drone flight services includes. drone user/operator information, drone pilot information, and
Information such as human-machine system-related identities, and the UAV cloud system contract identifier assigned by the UAV cloud system to the UAV. Registration information should meet
Requirements for content and data format in MH/T 2009.
The UAV cloud system should provide an effective network interface to the UAV system to ensure that the UAV system can complete the UAV through the controller interface
Cloud system registration.
After the UAV system is successfully registered, the UAV cloud system assigns a static CPN number to the UAV system.
The man-machine cloud system uses this static CPN number when requesting system access verification.
6.1.2 Requirements for registration information of users/operators of UAV systems
The registration information submitted by the drone user/operator to the drone cloud system should include at least the following.
a) User's name, valid certificate number (such as ID number, passport number, etc.), mobile phone, e-mail, and purpose of use;
b) Enterprise users need to fill in the unit name, unified social credit code or organization code, etc.;
c) For special types of users (such as rural cooperatives, etc.), a separate application must be submitted to the administrative agency of the Civil Aviation Administration to obtain a proprietary code.
When the UAV cloud system registers the UAV user/operator, etc., it should have the ability to authenticate the user/operator.
It should include the identification of the name, valid certificate number, mobile phone, etc.
6.1.3 Registration information requirements for drone pilots
The drone driver registration information submitted by the drone user/operator to the drone cloud system should at least contain the following content.
a) The valid ID information of the drone pilot;
b) Driver's mobile phone.
The above information should be encrypted, and technical measures and other necessary measures should be taken to ensure the safety of the personal information collected and prevent
Information leakage, damage, or loss. For example, using a hash algorithm for encryption.
The information of the independent control drone pilot license or certificate (plant protection category) should include categories, classification levels, etc. UAV cloud system
When registering drone pilots, the system should have the ability to verify the identity of the pilot, including the name, valid certificate number,
Identity verification is performed on mobile phones, etc.
6.1.4 Requirements for registration information of UAV system equipment
The UAV system equipment registration information submitted by the UAV user/operator to the UAV Cloud System shall include at least the following.
a) Real-name registration identification information of drones of the Civil Aviation Administration;
b) Other equipment identification information required by the UAV cloud system;
c) Other identification information required by national laws and regulations.
When the UAV system is registered in the UAV cloud system, the UAV cloud system should have the ability to verify the identity of the UAV system.
Power, including verification of the UAV equipment identification, the real-name registration identification of the UAV of the Civil Aviation Administration, and other equipment identifications.
Since there are multiple communication methods between the UAV system and the UAV cloud system, it is limited by the communication
For unpacking, grouping, or data compression, when the UAV system registers with the UAV cloud system, you can choose specific communication methods,
Data transmission mode, etc.
6.2 Data transmission requirements for pre-flight management of UAV cloud system
The following content only applies to drones operating in controlled airspace.
6.2.1 Airspace application requirements
The UAV cloud system should have the ability to apply for the controlled airspace and receive the approval results, and submit the flight airspace application to the exchange system.
When submitting the application, provide relevant risk assessment report, guarantee plan and other information to the system or platform designated by the government
Domain audit. The risk assessment report includes, but is not limited to, various risk indicators (such as flight altitude, flight weather, flight intensity of the flight area)
Wait).
The UAV cloud system can have the ability to conduct preliminary operation risk management and preliminary operation risk assessment of the airspace applied for by the UAV system.
force.
6.2.2 Flight plan application requirements
The UAV cloud system should have the ability to apply for flight plans and receive approval results, and submit flight plan applications to UOM.
A flight plan must correspond to a UAV user/operator and at least one UAV system. UAV cloud system needs to apply to
People give feedback on the approval result of the flight plan application.
The UAV cloud system should have the ability to conduct a preliminary review of the flight plan. If the flight conditions are met, the flight plan can be submitted to
The exchange system is planned and reviewed by the system or platform designated by the government management department.
6.3 UAV flight management data transmission requirements
6.3.1 System access verification/startup reporting requirements
6.3.1.1 Basic requirements
The UAV cloud system should have the ability to verify the system access before the UAV system takes off. When the drone is turned on for access verification,
Report their capabilities.
The UAV cloud system should complete the verification of the UAV's identity and auxiliary location, and ensure that the user completes the operation scenario code.
After the UAV system access verification is successful, the UAV cloud system returns a data reporting number to the UAV, and the UAV reports the data in real time.
The data report number or the real-name registration number of the drone from the Civil Aviation Administration of China must be used to report the data.
UAVs must complete system access verification before each takeoff. UAVs that meet the AC-91-31 exemptions can be released directly.
For UAV systems that are planned to operate in the controlled airspace, the UAV cloud system should also confirm that it has obtained the flight airspace of the national regulatory agency
Approval of domain, flight plan, and release application.
6.3.1.2 Requirements for access verification of drone identity
UAV system access verification needs to include at least the real-name registration number of the drone from the Civil Aviation Administration, the drone flight control serial number, the drone serial number,
The information of the drone manufacturer and the data that needs to be reported when it is turned on, including the information source identification, which means that the request comes from the drone,
Ground station equipment or server equipment, etc.
6.3.1.3 Requirements for verification of initial access position of drones
Only drones that meet the location service (LBS) verification capabilities required in MH/T 2008 can join the drones with higher capabilities.
The machine cloud system ensures the authenticity of the initial access location of the drone.
6.3.2 Requirements for UAV release application/online authorization
The UAV cloud system should have the ability to release applications and receive approval results, and to authorize the UAV system online. Possessive exchange
The function of the system to submit applications for release. Each application for release must include the flight plan authorization number, the pilot’s mobile phone number and other information.
Must correspond to one UAV user/operator and at least one UAV system. The drone cloud system needs to feedback the application to the applicant
The result of approval.
The UAV cloud system should have the ability to conduct a preliminary review of the flight application. If the flight conditions are met, the flight application can be submitted to
UAV cloud exchange system/UOM, the application is reviewed by the system or platform designated by the government management department.
The UAV cloud system with a higher capability level should have the function of applying for UAV release and the ability to conduct preliminary review of this.
Whether the application meets the flight plan (including the specific category of drones that meet the AC-91-31 condition exemption), and assist the government management department
Current airspace capacity, weather conditions, UAV fences, etc. apply/online authorization for UAV release.
UAVs that meet the AC-91-31 exemption conditions do not need to submit a flight plan, and the UAV cloud system should process the release application according to the exemption conditions
please.
6.3.3 Data link heartbeat keep-alive requirements
The data link heartbeat keep-alive is mainly used in the UAV control data link. After the UAV cloud system and UAV system are successfully connected and verified
Need to have the ability to keep alive with the heartbeat of the UAV system. The UAV system periodically sends the flight heartbeat keep-alive, the sending period is 10 s, continuous
If 6 heartbeats are not received, it is considered that the UAV control data link is disconnected. At this time, the UAV should perform actions such as returning to home or landing, or resending.
Start the system access verification process.
6.3.4 UAV fence and data verification requirements
The UAV cloud system shall pass the UAV fence safety capability test in accordance with the requirements of MH/T 2008.UAV cloud system should have relative
The corresponding UAV fence data is kept synchronized with the government management agency database, and it is equipped to manage the UAV system through the UAV fence.
Ability to control.
The UAV system should have the ability to verify and update the UAV fence data with the UAV cloud system. Connected to the drone cloud system
Before the drone takes off, the drone fence should be verified online. If the drone system electronic fence verification fails, the drone is prohibited from taking off. UAV series
The system regularly checks the drone cloud system based on the drone's location information, and carries the drone fence version number and update radius. If school
If the verification fails, all drone fences will be updated.
During the flight of the drone, it can initiate a request to update the drone fence data with the drone cloud system in real time. UAV gets according to GNSS
Current location information, periodically obtain the drone fence information of the current location from the drone cloud system, and carry the drone fence version number and update
The new radius. If the radius is invalid, all drone fences will be updated. If the drone does not have the latest drone fence data at the current location, no
The man-machine fence version number is invalid.
The process of the drone to the drone cloud system to verify the drone fence is as follows.
a) The drone sends to the drone cloud system, and the information should carry the updated radius parameter R and the current position P(x,y), where P(x,y) is
The current position of the drone, R is the maximum flying distance of the drone during the fence update cycle;
b) The drone cloud system sends the drone its current position P(x,y) update cycle to the drone fence within the maximum flight distance R
data;
c) If R is equal to the round trip Voy of the drone, the drone only needs to be turned on and updated once; if R is less than the round trip Voy,
The UAV needs to be refreshed periodically during the flight, which depends on the storage capacity of the UAV, and needs to be based on the manufacturer’s capabilities.
Line definition.
6.3.5 Alarm and notification requirements
6.3.5.1 General
The UAV cloud system should have the ability to provide users (users/operators) with notification and warning services, which are divided into manual and automatic services.
Services, including.
a) Abnormal weather warning information, national/government management notification information, flight conflict/collision warning information and other services;
b) Real-time push information and historical announcement information, etc.
6.3.5.2 Forbidden zone/restricted flight zone warning requirements
When the UAV touches the restricted area warning boundary during the flight, the UAV cloud system can send relevant restricted area warnings to the UAV
Ability. Meet the corresponding requirements of MH/T 2008 and realize the UAV fence warning function.
The UAV cloud system with a higher capability level should be able to automatically send warning instructions to the UAV system and perform
For the ability of direct control, drones need to perform corresponding control procedures according to safety requirements. such as hovering, returning to home, landing, etc.
6.3.5.3 Flight information notification requirements
The UAV cloud system should have the ability to send relevant intelligence information before the UAV system is used, before the flight, and during the flight.
The ability of the machine, controller, driver, user/operator to send notifications.
Flight information information may include but is not limited to. other civil aircraft flight dynamics, aviation control information, meteorological information, etc.
6.3.6 Data reporting requirements
6.3.6.1 Requirements for real-time reporting of flight data
All real-time reported data in the UAV system needs to include the UAV data transmission serial number, time stamp, flight status and other information.
The human-machine cloud system saves these dynamic information in the order of receipt and uploads it to the exchange system in real time. At the same time, digital signatures, blockchain,
Technologies such as location verification to ensure the authenticity of flight data and prevent flight data from being tampered with. UAV cloud systems of different ability levels are unmanned
Different services provided by aircraft systems require different real-time flight data.
The drone dynamic information in the drone cloud system is the information that characterizes the real-time operating status of the drone, and the drone system reports the number of flights in real time
The frequency should meet the relevant ...
Tips & Frequently Asked Questions:Question 1: How long will the true-PDF of MHT2011-2019_English be delivered?Answer: Upon your order, we will start to translate MHT2011-2019_English as soon as possible, and keep you informed of the progress. The lead time is typically 6 ~ 9 working days. The lengthier the document the longer the lead time. Question 2: Can I share the purchased PDF of MHT2011-2019_English with my colleagues?Answer: Yes. The purchased PDF of MHT2011-2019_English will be deemed to be sold to your employer/organization who actually pays for it, including your colleagues and your employer's intranet. Question 3: Does the price include tax/VAT?Answer: Yes. Our tax invoice, downloaded/delivered in 9 seconds, includes all tax/VAT and complies with 100+ countries' tax regulations (tax exempted in 100+ countries) -- See Avoidance of Double Taxation Agreements (DTAs): List of DTAs signed between Singapore and 100+ countriesQuestion 4: Do you accept my currency other than USD?Answer: Yes. If you need your currency to be printed on the invoice, please write an email to [email protected]. In 2 working-hours, we will create a special link for you to pay in any currencies. Otherwise, follow the normal steps: Add to Cart -- Checkout -- Select your currency to pay.
|