While the audience is gathering. During breaks etc While the audience is gathering. During breaks etc. Simple messages can be added in bold and white letters on the dark blue sea, eg. ”Welcome!”, ”Back at 15.15”
HOW-TO Use subscription and get requests, and TXT messages towards ships This HOW-TO gives guidelines to service for request of voyage plan from ship ,and how to get authorization.
Ask for the ships voyage plan Scenario: A shore centre discover a ship in its service coverage but has not got any voyage plan from the ship. The shore centre wants to ask for the ships (active) voyage plan. Alternatives: The shore centre sends a Subscription request to the ship The shore centre sends a Get request to the ship The shore centre sends a TXT message to the ship The shore centre sends an email, VHF, phone call or any other mean to request the voyage plan
Alternative 1 –no access The shore centre sends a Subscription Request to the ship SC SHIP POST voyageplans/subscription 403 Not authorized Present Non-authorized subscription attempt (Accept or Reject) to operator [Transas] TXT message with Access Deny Min 4 hours One voyage POST voyageplans/subscription
Alternative 2 – no access The shore centre sends a Get request to the ship SC SHIP GET voyageplans?routeStatus=7 403 Present Non-authorized subscription attempt (Accept or Reject) to operator [Transas] TXT message with Access Deny Min 4 hours One voyage GET voyageplans?routeStatus=7
Alternative 3 – no access The shore centre sends a TXT message to the ship SC SHIP Max one TXT per voyage asking for access POST textMessage{} 200 Present the TXT to operator One voyage
Alternative 2 with access The shore centre sends a Get request to the ship SC SHIP GET voyageplans?routeStatus=7 200 + Route in status=7 and uvid=X POST voyageplans\subscription?uvid=X 200 POST voyageplans{route for uvid=X} If the SC is unauthorized, the ship operator will never get more than one notification to accept or reject.
Service Instances One instance in Service Registry One active with external service requests Remaining internal service need to be passive listeners. Instance for ship Ship SC MSR
Summary Only one TXT message may be sent to the ship asking for (access to) voyage plan within same voyage Only one subscription request every 4h within same voyage, if subscription was denied (403) previously Only one get request every 4h within same voyage, if request was denied (403) previously If possible, use GET voyageplans?routeStatus=7
At the end – you could add text in black like ”Thank You !”