-
Notifications
You must be signed in to change notification settings - Fork 12
/
canonical.yaml
1775 lines (1723 loc) · 70.3 KB
/
canonical.yaml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
---
openapi: 3.0.2
info:
title: Discovery and Synchronization Service - USS-DSS, USS-USS
version: 1.0.0
description: |-
Interface to Discovery and Synchronization Service and service providers used by participating clients to discover and inform other service providers.
Unless otherwise specified, fields specified in a message but not declared in the API shall be ignored.
paths:
/v1/dss/identification_service_areas:
summary: Set of Identification Service Areas in the DSS.
description: ""
get:
tags:
- dss
parameters:
- name: area
description: The area in which to search for Identification Service Areas. Some
Identification Service Areas near this area but wholly outside it may also
be returned.
schema:
$ref: '#/components/schemas/GeoPolygonString'
in: query
required: true
- name: earliest_time
description: If specified, indicates non-interest in any Identification Service
Areas that end before this time. RFC 3339 format, per OpenAPI specification.
schema:
format: date-time
type: string
in: query
required: true
- name: latest_time
description: If specified, indicates non-interest in any Identification Service
Areas that start after this time. RFC 3339 format, per OpenAPI specification.
schema:
format: date-time
type: string
in: query
required: true
responses:
200:
content:
application/json:
schema:
$ref: '#/components/schemas/SearchIdentificationServiceAreasResponse'
description: Identification Service Areas were successfully retrieved.
400:
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
description: One or more input parameters were missing or invalid.
401:
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
description: Bearer access token was not provided in Authorization header,
token could not be decoded, or token was invalid.
403:
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
description: The access token was decoded successfully but did not include
a scope appropriate to this endpoint.
413:
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
description: The requested area was too large.
security:
- AuthFromAuthorizationAuthority:
- dss.read.identification_service_areas
summary: /dss/identification_service_areas
description: Retrieve all Identification Service Areas in the DAR for a given
area during the given time. Note that some Identification Service Areas returned
may lie entirely outside the requested area.
/v1/dss/identification_service_areas/{id}:
summary: An Identification Service Area in the DSS.
get:
tags:
- dss
responses:
200:
content:
application/json:
schema:
$ref: '#/components/schemas/GetIdentificationServiceAreaResponse'
description: Full information of the Identification Service Area was retrieved
successfully.
400:
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
description: One or more input parameters were missing or invalid.
401:
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
description: Bearer access token was not provided in Authorization header,
token could not be decoded, or token was invalid.
403:
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
description: The access token was decoded successfully but did not include
a scope appropriate to this endpoint.
404:
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
description: The requested Entity could not be found.
security:
- AuthFromAuthorizationAuthority:
- dss.read.identification_service_areas
summary: /dss/identification_service_areas/{id}
description: Retrieve full information of an Identification Service Area owned
by the client.
put:
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/CreateIdentificationServiceAreaParameters'
required: true
tags:
- dss
responses:
200:
content:
application/json:
schema:
$ref: '#/components/schemas/PutIdentificationServiceAreaResponse'
description: An existing Identification Service Area was created successfully
in the DSS.
400:
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
description: |-
* One or more input parameters were missing or invalid.
* The request attempted to mutate the Identification Service Area in a disallowed way.
401:
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
description: Bearer access token was not provided in Authorization header,
token could not be decoded, or token was invalid.
403:
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
description: The access token was decoded successfully but did not include
a scope appropriate to this endpoint.
409:
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
description: |-
* An Identification Service Area with the specified ID already exists and is owned by a different client.
* Despite repeated attempts, the DSS was unable to update the DAR because of other simultaneous changes.
413:
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
description: The area of the Identification Service Area is too large.
security:
- AuthFromAuthorizationAuthority:
- dss.write.identification_service_areas
summary: /dss/identification_service_areas/{id}
description: |-
Create a new Identification Service Area. This call will fail if an Identification Service Area with the same ID already exists.
The DSS assumes the USS has already added the appropriate retention period to operation end time in `time_end` field before storing it.
parameters:
- name: id
description: EntityUUID of the Identification Service Area.
schema:
$ref: '#/components/schemas/EntityUUID'
in: path
required: true
/v1/dss/identification_service_areas/{id}/{version}:
summary: A specific version of an Identification Service Area in the DSS.
put:
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/UpdateIdentificationServiceAreaParameters'
required: true
tags:
- dss
responses:
200:
content:
application/json:
schema:
$ref: '#/components/schemas/PutIdentificationServiceAreaResponse'
description: An existing Identification Service Area was updated successfully
in the DSS.
400:
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
description: |-
* One or more input parameters were missing or invalid.
* The request attempted to mutate the Identification Service Area in a disallowed way.
401:
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
description: Bearer access token was not provided in Authorization header,
token could not be decoded, or token was invalid.
403:
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
description: The access token was decoded successfully but did not include
a scope appropriate to this endpoint.
409:
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
description: |-
* The specified Identification Service Area's current version does not match the provided version.
* Despite repeated attempts, the DSS was unable to update the DAR because of other simultaneous changes.
413:
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
description: The area of the Identification Service Area is too large.
security:
- AuthFromAuthorizationAuthority:
- dss.write.identification_service_areas
summary: /dss/identification_service_areas/{id}/{version}
description: |-
Update an Identification Service Area. The full content of the existing Identification Service Area will be replaced with the provided information as only the most recent version is retained.
The DSS assumes the USS has already added the appropriate retention period to operation end time in `time_end` field before storing it. Updating `time_start` is not allowed if it is before the current time.
delete:
tags:
- dss
responses:
200:
content:
application/json:
schema:
$ref: '#/components/schemas/DeleteIdentificationServiceAreaResponse'
description: Identification Service Area was successfully deleted from DSS.
400:
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
description: One or more input parameters were missing or invalid.
401:
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
description: Bearer access token was not provided in Authorization header,
token could not be decoded, or token was invalid.
403:
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
description: |-
* The access token was decoded successfully but did not include a scope appropriate to this endpoint.
* The Identification Service Area does not belong to the client requesting deletion.
404:
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
description: Entity could not be deleted because it could not be found.
409:
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
description: |-
* The specified Identification Service Area's current version does not match the provided version.
* Despite repeated attempts, the DSS was unable to update the DAR because of other simultaneous changes.
security:
- AuthFromAuthorizationAuthority:
- dss.write.identification_service_areas
summary: /dss/identification_service_areas/{id}/{version}
description: Delete an Identification Service Area. USSs should not delete
Identification Service Areas before the end of the last managed flight plus
the retention period.
parameters:
- name: id
description: EntityUUID of the Identification Service Area.
schema:
$ref: '#/components/schemas/EntityUUID'
in: path
required: true
- name: version
description: Version string used to reference an Identification Service Area
at a particular point in time. Any updates to an existing Identification Service
Area must contain the corresponding version to maintain idempotent updates.
schema:
type: string
in: path
required: true
/v1/uss/flights:
summary: Basic operation details to meet remote ID requirements.
description: This endpoint may be polled by remote ID display providers to display
basic aircraft activity near a user in real time.
get:
tags:
- p2p_rid
responses:
200:
content:
application/json:
schema:
$ref: '#/components/schemas/GetFlightsResponse'
description: Flight information was successfully retrieved.
400:
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
description: One or more input parameters were missing or invalid.
401:
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
description: Bearer access token was not provided in Authorization header,
token could not be decoded, or token was invalid.
403:
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
description: The access token was decoded successfully but did not include
a scope appropriate to this endpoint.
404:
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
description: The requested view is entirely outside any remote ID service
provision areas (PositionReporting Entity volumes) this provider has. A
display provider receiving this response should discontinue polling for
this endpoint for the view port requested until otherwise directed by
DSS interactions.
413:
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
description: The requested view rectangle was too large.
security:
- AuthFromAuthorizationAuthority:
- dss.read.identification_service_areas
summary: /uss/flights
description: Retrieve basic flight information from a remote ID service provider
to meet remote ID requirements. This endpoint will be polled by remote ID
display providers to display basic aircraft activity near a user in real time. All
flights that have any recent positions (past [NetUasInAreaWindow] seconds)
inside the requested view must be returned.
parameters:
- name: view
description: 'The area of this view: lat1,lng1,lat2,lng2. Size may not exceed
a diagonal length specified in the standard. The view is the smallest box
bounded by the provided corner points.'
schema:
type: string
example: 29.97816,31.13296,29.98025,31.13535
in: query
required: true
- name: include_recent_positions
description: |-
If specified as true, include recent positions. Otherwise, do not include recent positions.
A display provider's first poll of this endpoint for a particular view will usually request recent positions while follow-up polls for that same view will usually not need to request recent positions.
schema:
type: boolean
in: query
/v1/uss/flights/{id}/details:
summary: A remote ID flight reported by a remote ID service provider.
get:
tags:
- p2p_rid
responses:
200:
content:
application/json:
schema:
$ref: '#/components/schemas/GetFlightDetailsResponse'
description: Flight details were successfully retrieved.
400:
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
description: One or more input parameters were missing or invalid.
401:
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
description: Bearer access token was not provided in Authorization header,
token could not be decoded, or token was invalid.
403:
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
description: The access token was decoded successfully but did not include
a scope appropriate to this endpoint.
404:
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
description: The requested flight could not be found.
security:
- AuthFromAuthorizationAuthority:
- dss.read.identification_service_areas
summary: /uss/flights/{id}/details
description: Retrieve details of a flight from a remote ID service provider
to meet remote ID requirements.
parameters:
- name: id
description: Remote ID flight ID for this flight; may be obtained in general
/flights query.
schema:
$ref: '#/components/schemas/RIDFlightID'
in: path
required: true
/v1/dss/subscriptions:
summary: Subscriptions for airspace updates to a volume of interest.
get:
tags:
- dss
parameters:
- name: area
description: The area in which to search for Subscriptions. Some Subscriptions
near this area but wholly outside it may also be returned.
schema:
$ref: '#/components/schemas/GeoPolygonString'
in: query
required: true
responses:
200:
content:
application/json:
schema:
$ref: '#/components/schemas/SearchSubscriptionsResponse'
description: Subscriptions were retrieved successfully.
400:
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
description: One or more input parameters were missing or invalid.
401:
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
description: Bearer access token was not provided in Authorization header,
token could not be decoded, or token was invalid.
403:
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
description: The access token was decoded successfully but did not include
a scope appropriate to this endpoint.
413:
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
description: The requested area was too large.
security:
- AuthFromAuthorizationAuthority:
- dss.read.identification_service_areas
summary: /dss/subscriptions
description: |-
Retrieve subscriptions intersecting an area of interest. Subscription notifications are only triggered by (and contain full information of) changes to, creation of, or deletion of, Entities referenced by or stored in the DSS; they do not involve any data transfer (such as remote ID telemetry updates) apart from Entity information.
Only Subscriptions belonging to the caller are returned. This endpoint would be used if a USS lost track of Subscriptions they had created and/or wanted to resolve an error indicating that they had too many existing Subscriptions in an area.
/v1/dss/subscriptions/{id}:
summary: Subscription for airspace updates to a volume of interest.
get:
tags:
- dss
responses:
200:
content:
application/json:
schema:
$ref: '#/components/schemas/GetSubscriptionResponse'
description: Subscription information was retrieved successfully.
400:
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
description: One or more input parameters were missing or invalid.
401:
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
description: Bearer access token was not provided in Authorization header,
token could not be decoded, or token was invalid.
403:
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
description: The access token was decoded successfully but did not include
a scope appropriate to this endpoint.
404:
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
description: A Subscription with the specified ID was not found.
security:
- AuthFromAuthorizationAuthority:
- dss.read.identification_service_areas
- dss.write.identification_service_areas
summary: /dss/subscriptions/{id}
description: Verify the existence/valdity and state of a particular subscription.
put:
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/CreateSubscriptionParameters'
required: true
tags:
- dss
responses:
200:
content:
application/json:
schema:
$ref: '#/components/schemas/PutSubscriptionResponse'
description: A new Subscription was created successfully.
400:
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
description: |-
* One or more input parameters were missing or invalid.
* The request attempted to mutate the Subscription in a disallowed way.
401:
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
description: Bearer access token was not provided in Authorization header,
token could not be decoded, or token was invalid.
403:
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
description: |-
* The access token was decoded successfully but did not include a scope appropriate to this endpoint or the request.
* An EntityType was specified in `types_filter` to which the scopes included in the access token do not provide access.
409:
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
description: |-
* A Subscription with the specified ID already exists and is owned by a different client.
* Despite repeated attempts, the DSS was unable to update the DAR because of other simultaneous changes.
429:
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
description: Client already has too many Subscriptions in the area where
a new Subscription was requested. To correct this problem, the client
may query GET /subscriptions to see which Subscriptions are counting against
their limit. This problem should not generally be encountered because
the Subscription limit should be above what any consumer that reasonably
aggregates their Subscriptions should request. But, a Subscription limit
is necessary to bound performance requirements for DSS instances and would
likely be hit by, e.g., a large remote ID display provider that created
a Subscription for each of their display client users' views.
security:
- AuthFromAuthorizationAuthority:
- dss.read.identification_service_areas
summary: /dss/subscriptions/{id}
description: |-
Create a subscription. This call will fail if a Subscription with the same ID already exists.
Subscription notifications are only triggered by (and contain full information of) changes to, creation of, or deletion of, Entities referenced by or stored in the DSS; they do not involve any data transfer (such as remote ID telemetry updates) apart from Entity information.
parameters:
- name: id
description: SubscriptionUUID of the subscription of interest.
schema:
$ref: '#/components/schemas/SubscriptionUUID'
in: path
required: true
/v1/dss/subscriptions/{id}/{version}:
summary: Specific version of a Subscription for airspace updates to a volume of
interest.
put:
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/UpdateSubscriptionParameters'
required: true
tags:
- dss
responses:
200:
content:
application/json:
schema:
$ref: '#/components/schemas/PutSubscriptionResponse'
description: An existing Subscription was updated successfully.
400:
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
description: |-
* One or more input parameters were missing or invalid.
* The request attempted to mutate the Subscription in a disallowed way.
401:
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
description: Bearer access token was not provided in Authorization header,
token could not be decoded, or token was invalid.
403:
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
description: |-
* The access token was decoded successfully but did not include a scope appropriate to this endpoint or the request.
* An EntityType was specified in `types_filter` to which the scopes included in the access token do not provide access.
409:
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
description: |-
* The specified Subscriptions's current version does not match the provided version.
* Despite repeated attempts, the DSS was unable to update the DAR because of other simultaneous changes.
429:
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
description: Client already has too many Subscriptions in the area where
a new Subscription was requested. To correct this problem, the client
may query GET /subscriptions to see which Subscriptions are counting against
their limit. This problem should not generally be encountered because
the Subscription limit should be above what any consumer that reasonably
aggregates their Subscriptions should request. But, a Subscription limit
is necessary to bound performance requirements for DSS instances and would
likely be hit by, e.g., a large remote ID display provider that created
a Subscription for each of their display client users' views.
security:
- AuthFromAuthorizationAuthority:
- dss.read.identification_service_areas
summary: /dss/subscriptions/{id}/{version}
description: |-
Update a Subscription. The full content of the existing Subscription will be replaced with the provided information as only the most recent version is retained.
Subscription notifications are only triggered by (and contain full information of) changes to, creation of, or deletion of, Entities referenced by or stored in the DSS; they do not involve any data transfer (such as remote ID telemetry updates) apart from Entity information.
delete:
tags:
- dss
responses:
200:
content:
application/json:
schema:
$ref: '#/components/schemas/DeleteSubscriptionResponse'
description: Subscription was deleted successfully.
400:
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
description: One or more input parameters were missing or invalid.
401:
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
description: Bearer access token was not provided in Authorization header,
token could not be decoded, or token was invalid.
403:
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
description: |-
* The access token was decoded successfully but did not include a scope appropriate to this endpoint.
* The Entity does not belong to the client requesting deletion.
404:
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
description: Subscription could not be deleted because it could not be found.
409:
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
description: |-
* The specified Subscriptions's current version does not match the provided version.
* Despite repeated attempts, the DSS was unable to update the DAR because of other simultaneous changes.
security:
- AuthFromAuthorizationAuthority:
- dss.read.identification_service_areas
summary: /dss/subscriptions/{id}/{version}
description: Delete a subscription.
parameters:
- name: id
description: SubscriptionUUID of the subscription of interest.
schema:
$ref: '#/components/schemas/SubscriptionUUID'
in: path
required: true
- name: version
description: Version string used to reference a Subscription at a particular
point in time. Any updates to an existing Subscription must contain the corresponding
version to maintain idempotent updates.
schema:
type: string
in: path
required: true
/v1/uss/identification_service_areas/{id}:
summary: Notifications of change to Identification Service Areas.
post:
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/PutIdentificationServiceAreaNotificationParameters'
required: true
tags:
- p2p_rid
responses:
204:
description: Information for Identification Service Area was updated successfully.
400:
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
description: |-
* One or more parameters were missing or invalid.
* The Identification Service Area information could not be parsed, or contains illegal data.
401:
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
description: Bearer access token was not provided in Authorization header,
token could not be decoded, or token was invalid.
403:
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
description: |-
* The access token was decoded successfully but did not include a scope appropriate to this endpoint.
* The client identified in the access token is not the owner of this Entity according to the receiving client's records.
409:
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
description: The Entity version specified in this message is identical to
a previously-received notification and the Entity is different.
security:
- AuthFromAuthorizationAuthority:
- dss.write.identification_service_areas
summary: /uss/identification_service_areas/{id}
description: 'Hosted by a remote ID display provider using Subscriptions: publish
new full information of an Identification Service Area to the host of this
endpoint (usually because of instructions from the DSS triggered by a subscription).'
parameters:
- name: id
description: EntityUUID of the Identification Service Area.
schema:
$ref: '#/components/schemas/EntityUUID'
in: path
required: true
components:
schemas:
Volume3D:
description: A three-dimensional geographic volume consisting of a vertically-extruded
polygon.
required:
- footprint
type: object
properties:
footprint:
anyOf:
- $ref: '#/components/schemas/GeoPolygon'
description: Projection of this volume onto the earth's surface.
altitude_lo:
anyOf:
- $ref: '#/components/schemas/Altitude'
description: Minimum bounding altitude of this volume.
altitude_hi:
anyOf:
- $ref: '#/components/schemas/Altitude'
description: Maximum bounding altitude of this volume.
Volume4D:
description: Contiguous block of geographic spacetime.
required:
- spatial_volume
type: object
properties:
spatial_volume:
anyOf:
- $ref: '#/components/schemas/Volume3D'
description: Constant spatial extent of this volume.
time_start:
format: date-time
description: Beginning time of this volume. RFC 3339 format, per OpenAPI
specification.
type: string
time_end:
format: date-time
description: End time of this volume. RFC 3339 format, per OpenAPI specification.
type: string
GetSubscriptionResponse:
description: Response to DSS request for the subscription with the given id.
required:
- subscription
type: object
properties:
subscription:
$ref: '#/components/schemas/Subscription'
SearchSubscriptionsResponse:
description: Response to DSS query for subscriptions in a particular area.
required:
- subscriptions
type: object
properties:
subscriptions:
description: Subscriptions that overlap the specified area.
type: array
items:
$ref: '#/components/schemas/Subscription'
GetFlightsResponse:
description: Response to remote ID provider query for flight information in
an area of interest.
required:
- timestamp
- flights
type: object
properties:
timestamp:
format: date-time
description: The remote ID service provider's timestamp for when this information
was current. RFC 3339 format, per OpenAPI specification.
type: string
flights:
description: A list of all flights that have been within the requested area
within the remote ID retention period. This includes flights that are
not currently within the requested area, but were within the requested
area within the remote ID retention period.
type: array
items:
$ref: '#/components/schemas/RIDFlight'
URL:
description: Valid http or https URL.
type: string
SubscriptionNotificationIndex:
format: int32
description: Tracks the notifications sent for a subscription so the subscriber
can detect missed notifications more easily.
type: integer
SubscriptionState:
description: State of AreaSubscription which is causing a notification to be
sent.
required:
- subscription
type: object
properties:
subscription_id:
$ref: '#/components/schemas/SubscriptionUUID'
notification_index:
$ref: '#/components/schemas/SubscriptionNotificationIndex'
UUIDv4:
description: UUID v4.
maxLength: 36
minLength: 36
type: string
example: 03e5572a-f733-49af-bc14-8a18bd53ee39
Version:
description: A version string used to reference an object at a particular point
in time. Any updates to an object must contain the corresponding version to
maintain idempotent updates.
type: string
EntityUUID:
anyOf:
- $ref: '#/components/schemas/UUIDv4'
description: Universally-unique identifier for an Entity communicated through
the DSS. Formatted as UUIDv4.
SubscriptionUUID:
anyOf:
- $ref: '#/components/schemas/UUIDv4'
description: Universally-unique identifier for a Subscription communicated through
the DSS. Formatted as UUIDv4.
RIDFlightID:
description: |-
ID, unique to a remote ID service provider, which identifies a particular flight for which the remote ID service provider is providing remote ID services.
The following characters are not allowed: \0 \t \r \n # % / : ? @ [ \ ]
maxLength: 255
minLength: 1
type: string
example: uss1.JA6kHYCcByQ-6AfU
RIDAuthData:
description: Additional authentication data.
required:
- format
- data
type: object
properties:
format:
description: Format of additional authentication data.
type: string
data:
description: Authentication data in form specified by `format`.
type: string
GetFlightDetailsResponse:
description: Response to remote ID provider query for details about a specific
flight.
required:
- details
type: object
properties:
details:
$ref: '#/components/schemas/RIDFlightDetails'
HorizontalAccuracy:
description: |-
This is the NACp enumeration from ADS-B, plus 1m for a more complete range for UAs.
`HAUnknown`: Unknown horizontal accuracy
`HA10NMPlus`: > 10NM (18.52km)
`HA10NM`: < 10NM (18.52km)
`HA4NM`: < 4NM (7.408km)
`HA2NM`: < 2NM (3.704km)
`HA1NM`: < 1NM (1852m)
`HA05NM`: < 0.5NM (926m)
`HA03NM`: < 0.3NM (555.6m)
`HA01NM`: < 0.1NM (185.2m)
`HA005NM`: < 0.05NM (92.6m)
`HA30m`: < 30m
`HA10m`: < 10m