You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently our Drone Charging protocol only covers the request for charging, and the bids to provide a charging service. We need a to have a communication protocol for the entire process, so we could for example, as part of a coming integration with Skysense (charging stations provider), support the communication between the drone and the station throughout the mission itself (when the drone is on its way to the station, when charging has started etc.)
Proposal
Add communications for the following stages (after 'bid' stage):
Select Bid - A selection of one bid that wins over the rest. Sent by the service requester (a drone that is looking for charging)
Abort (Requester) - A cancellation message sent by the service requester (the drone) to the service provider, declining the service
Abort (Provider) - A cancellation message sent by the service provider (the charging station) to the service requester, aborting the service
Request Status (Requester) - A request message sent by the service requester to the service provider, asking for a status update
Request Status (Provider) - A request message sent by the service provider to the service requester, asking for a status update
Status (Requester) - A status update sent by the service requester to the service provider
Status (Provider) - A status update sent by the service provider to the service requester
Landing Request - A request message sent by the service requester to the service provider, asking for a permission to land
Landing Approval - A message sent by the service provider to the service requester, approving the drone to land
Start Charging - A request message sent by the service requester to the service provider, when the drone is ready to be charged
Charging Started - A message sent by the service provider to the service requester, notifying the drone that charging has started
Stop Charging - A request message sent by the service requester to the service provider, asking the charging station to stop charging
Charging Stopped - A message sent by the service provider to the service requester, notifying the drone that charging has stopped
Departure Request - A request message sent by the service requester to the service provider, asking for a permission leave the charging station
Departure Approval - A message sent by the service provider to the service requester, approving the drone to leave the charging station
Drone Leave - A message sent by the service requester to the service provider, notifying that the drone has left the charging station
The text was updated successfully, but these errors were encountered:
Abstract
Expand our drone charging protocol to include all post-bid communications (bid selection, flying to station, charging started etc.), similar to what we did in drone delivery protocol
Motivation
Currently our Drone Charging protocol only covers the request for charging, and the bids to provide a charging service. We need a to have a communication protocol for the entire process, so we could for example, as part of a coming integration with Skysense (charging stations provider), support the communication between the drone and the station throughout the mission itself (when the drone is on its way to the station, when charging has started etc.)
Proposal
Add communications for the following stages (after 'bid' stage):
Charging Started - A message sent by the service provider to the service requester, notifying the drone that charging has started
Charging Stopped - A message sent by the service provider to the service requester, notifying the drone that charging has stopped
The text was updated successfully, but these errors were encountered: