A drone port infrastructure and landing handshake

the following paper will be used as a draft to deploy open droneport infrastructure and architecture.

1) localizing the droneport
2) approach vectors enforced : updated by the droneport at regular intervals
3) departure vectors enforced : updated by the droneport at regular intervals
4) FIFO request management
5) weather transmit : pulling METAR/TAF by the control module of the drone based on coordinates of the nearest ICAO airport/airfield


1) localizing the droneport.

a) GPS module gives coordinates of the ship
b) SSID convention for droneports identifies the port (SSID uses droneport name)
c) basic check to see if droneport GPS (once in WIFI sight) coordinates (fetched on the net - securely) are consistent with the drone own coordinates in close situation to the droneport
d) droneport / drone handshake : drone gives message | FLIGHT NAME | SSID | FROM (opt) | TO (opt) | URGENCY | SERVICE REQUEST |

                 droneport replies   | SSID | FLIGHT NAME | FRAME ACK = 0 | ACCEPTED | QUEUE POSITION (if accepted) | KEEPALIVE | REASON |


                    OR

                 droneport replies   | SSID | FLIGHT NAME | FRAME ACK = 0 | DECLINED | QUEUE POSITION (if accepted) | KEEPALIVE | REASON |
                     
                                 drone confirms :  | FLIGHT NAME | SSID | FRAME ACK |  QUEUE POSITION | REASON |

                    OR

                drone bailout because of long queue : | FLIGHT NAME | SSID | FRAME ACK | REF |  QUEUE POSITION | REASON |

               
                                 drone waits | FLIGHT NAME | SSID | ALIVE < KEEPALIVE time|


                 droneport gives clearance : | SSID | FLIGHT NAME | FRAME ACK | CLEARED | QUEUE = 1 | KEEPALIVE | REASON |


                 droneport gives negative clearance : | SSID | FLIGHT NAME | FRAME ACK | WAIT TIME | QUEUE = 1 | KEEPALIVE | REASON |


                     droneport gives bye : | SSID | FLIGHT NAME | FRAME ACK | BYE | QUEUE (NULL) | KEEPALIVE | REASON |


                       OR


                 droneport gives go away (ban) : | SSID | FLIGHT NAME | FRAME ACK | DECLINED | QUEUE (NULL) | KEEPALIVE | REASON |


For final airpod (landing site) destination, The use of a QRCODE scanned by the drone will confirm that the drone lands in the place it is intended for it.
the QRCODE will be printend on the ground, as an identifier of the landing location.