3.3. Process Scheduled Trip Event
The process or execution of a scheduled trip event depends on the type of event to execute. The following type of events can be received:
- NodePass: This is an internal system event that is used to register that the traveler has passed by a node of one of its scheduled trip segments. It needs no execution (only the storage of the event in the list of historical events).
- TripStateChange: This is an internal system event that is used to change the current state/phase/stage of the trip.
- ScheduledNotification: This event is used for sending a text message to a traveler using a phone number or an e-mail. The message is sent using the NotifyInformationToTraveler service, provided by the MOBILE interface. These events are generated by the service subscriptions of the trip.
- SegmentValidation: Segment validation is carried out by using the FindTrips CORE function for checking if a given trip segment is still scheduled by the JP that originally provided it. If the validated segment remains as originally scheduled, then no action is needed. In the case the validated segment is no longer scheduled as was originally provided, then it’s necessary to check the changes and disturbances produced in the trip. This is made using the Manage Trip Changes function, described later.