See schemas, examples and descriptions below.
- URL: https://{baseUrl}/api/v1/droneDevice/register/
- Request Method: POST
- Signing Algorithm: RSASSA-PKCS1-v1_5 SHA-256
The registration request to the server should be constructed as per JWS specification (IETF RFC7515). The registration data payload specified above should be encoded in base64 encoding and signed using Flight Module Provider Private Key securely through PKI Token/HSM.
Schemas: schemas
- URL: https://{baseUrl}/api/v1/droneDevice/deregister/
- Request Method: POST
- Signing Algorithm: RSASSA-PKCS1-v1_5 SHA-256
The registration request to the server should be constructed as per JWS specification (IETF RFC7515). The registration data payload specified above should be encoded in base64 encoding and signed using Flight Module Provider Private Key securely through PKI Token/HSM.
Schemas: schemas
The flight log should be constructed as per JWS specification (IETF RFC7515). The TBS flight log payload should be encoded in base64 encoding and signed using Flight Module Private Key.
Refer to schemas for flight log schema.
Proposals that are currently under consideration or review will be available in the proposals directory.
Proposals that have been accepted will be available in the standards directory.
Earlier this was refered to as RPAS Guidance Manual, or Technology standards document. To build a PDF version of the document, refer to this readme.