...
Authentication, authenticates (allows) equipment and units to communicate with each other in accordance with clearly specified rules (Authentication + Authorisation)
Product, the Product Interfaces to Price and Product Services, they deliver information on available products and prices to the Sales Channels
Ticket, the Ticket Interface for “Ticketing Service”, the service that receives orders for tickets and creates an MTB with information and guarantees the validity by means of electronic signatures.
ParticipantMetadata, the interface for processing and updating the central information at ABParticipant Meta Database.
Device, provides KDK and device key keys for copying protection. Device Signature
Validation, "Validation Service" back end interface that a validation device uses to submit completed validations or if validation takes place online where the actual validation is made.
Inspection, equivalent to Validation but for inspection equipment.
Traveller, interface for modules with passenger information.
Booking, used for reserving and booking of demand responsive travels.
Token, used for registration of tokens and to tie them to tickets for ID-based travel.
Account*, reserved for future use.
*Initial idea: account management functions for ID-based Travel.
Resource**, reserved for future use.
**Initial idea: seat booking component in Price and Product Service”
...
Tickets are named Mobile Ticket Bundle (MTB) in the BoB standard. You can issue a ticket from only one participant or you can build tickets that combine tickets from several participants (you collect tickets from different participants ticket engines and bundle them together so that the customer perceives them as one ticket for the whole journey. One ticket to keep track of the time limit, one ticket to validate. Combined tickets requires that the fares, some of the business rules and the geography are coordinated between the participants. However, the product range and prices have no direct connection, so these can be set individually.
...