Configuration and regular status checks while the SBD is idle is described here: Configuration and status checking.
It is possible for the SBD to have direct communication with a DCS, including through a broker, and only use the BagDropService for local configuration/information and transaction logging (BagNotify). The sequence diagram below shows the use of BagDropService in this setting.
The SBD is responsible for managing all aspects of the DCS communication.
NB! All calls to BagDropService related to one bag delivery process must use the same TransactionId. See also Use of TransactionId.
|
- The passenger initiates the bag drop by scanning the bag tag.
- The SBD must call GetOperatingCarrier to get the actual operating carrier. This also informs the bag drop service that a new bag drop has started.
- Any DCS communication in this use case is the responsibility of the SBD.
This initial communication would be to verify the bag.
- If required by the airline the boarding pass must be scanned.
- Any DCS communication in this use case is the responsibility of the SBD.
- The SBD must call LocalVerifyBag to ensure that the bag is acceptable for the airport. This also indicates to the bag drop service that the bag is (close to) accepted by the SBD.
- Any DCS communication in this use case is the responsibility of the SBD.
- The SBD must call BagNotify to notify the bag drop service that the bag has been sent on to the baggage handling system at the airport.
|
