diff --git a/IBIS-IP_CustomerInformationService_V2.4.xsd b/IBIS-IP_CustomerInformationService_V2.4.xsd
new file mode 100644
index 0000000..e44f89c
--- /dev/null
+++ b/IBIS-IP_CustomerInformationService_V2.4.xsd
@@ -0,0 +1,239 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ if vehicle is not on a trip and no tripinformation is available occurrence typically is 0
+ if vehicle is on a trip or knows the next trip to run occurrence typically is 1
+ if vehicle is on a trip and also knows the subsequent trip that info can be provided in the second TripInformation so occurrence is 2
+
+
+
+
+ Index of the Stoppoint in the Stopsequence, which is the next Stop
+
+
+
+
+
+ Global display content - this content should be used if no stop specific display content is available
+ please make sure that the global display content and the stop specific content are provided for the same DisplayContentRefs.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Index of the Stoppoint in the Stopsequence, which is the next Stop in the first trip
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Contains the information about route deviation
+
+
+
+
+ Information on DoorState
+
+
+
+
+ Is the Emergency-Button pressed?
+
+
+
+
+ Is the Stop-Button inside the vehicle pressed?
+
+
+
+
+ Defines the exit side
+
+
+
+
+ Gives information, if the vehicle is moving forward, default value is "true"
+
+
+
+
+ DEPRECATED, is of type VehicleModeEnumeration. MyOwnVehicleMode SHOULD BE USED INSTEAD
+
+
+
+
+ Mode- and Submode information vehicle I am in - in accordance with Netex
+
+
+
+
+ Gives information, if the loud speaker is activated for a passenger announcement
+
+
+
+
+ Gives information, if the stopInformation inside the vehicle is in active or in passiv state (intentionally, e.g. due to "route left)
+
+
+
+
+
+
diff --git a/IBIS-IP_DeviceManagementService_V2.3.xsd b/IBIS-IP_DeviceManagementService_V2.3.xsd
new file mode 100644
index 0000000..5fe444c
--- /dev/null
+++ b/IBIS-IP_DeviceManagementService_V2.3.xsd
@@ -0,0 +1,463 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Warnings and errors only, no state messages
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Unique id generated by the controller to identify an update job
+
+
+ Timestamp used for GetUpdateHistory and RetrieveUpdateState responses and for logging
+
+
+ URL from which the device shall download the update file
+
+
+ Optional checksum of update file
+
+
+ Optional size of update file
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Timestamp given by operation InstallUpdate
+
+
+ Current status of update
+
+
+ Optional device specific update log
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Minimum requirement for any device allowing updates is an update history depth of 1,
+ i.e. history shall contain at least the last update performed (regardless of its result), if there was any.
+
+
+
+
+
+
+
+ Timestamp given by operation InstallUpdate
+
+
+ URL from which the device downloaded the update file
+
+
+ Status of update. Typically final status (InstallationSuccessfull or InstallationFailed)
+
+
+ Optional list of updated components
+
+
+ Optional device specific update log
+
+
+
+
+
+
+
+
+
+
+
+
+ Status of update on its finalization
+
+
+
+
+
+
+
+
+
+ Types of checksum
+
+
+ Cyclic redundancy check, 32-bit
+ Message digest algorithm 5, 128-bit
+ Secure hash algorithm, 256-bit
+
+
+
+
+ Information about the result of InstallUpdate
+
+
+ Update will be performed
+ URL type has been rejected, e.g. FTP may not supported by some devices
+ No updates are possible
+ Update has to be postponed
+
+
+
+
+ Information about the current status of update
+
+
+ Update in progress
+ Device has to be restarted by operation RestartDevice
+ Specified update file could not be downloaded from URL
+ Specified update file is not usable
+ State of device firmware already as required
+ Update failed e.g. due to memory write error
+ Update successfully completed
+
+
+
+
+
+ Information on named subdevice
+
+
+
+
+ Used to identify subdevice
+
+
+
+
+ Information on subdevice
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Status information of named subdevice
+
+
+
+
+ Used to identify subdevice
+
+
+
+
+ Status information of subdevice
+
+
+
+
+
+
+ Error messages of named subdevice
+
+
+
+
+ Used to identify subdevice
+
+
+
+
+ Warnings and errors only, no state messages
+
+
+
+
+
+
+
+
+
+
+
diff --git a/IBIS-IP_common_V2.4.xsd b/IBIS-IP_common_V2.4.xsd
new file mode 100644
index 0000000..b893a1a
--- /dev/null
+++ b/IBIS-IP_common_V2.4.xsd
@@ -0,0 +1,1061 @@
+
+
+
+
+
+
+
+
+ Structure for decscribing the informations for an additional announcement
+
+
+
+
+ Reference to the Announcement in the schedule data
+
+
+
+
+ Text of the Announcement
+
+
+
+
+ Text of the Announcement for a text-to-speech-system
+
+
+
+
+
+ true, if the additional annoucement should be pronounced immiditaley
+
+
+
+
+ period in which the addional announcement should be played
+
+
+
+
+ describes a specific point, where the addional announcement should be played
+
+
+
+
+
+
+
+ Structure for decscribing the informations for an regular announcement
+
+
+
+
+ Reference to the Announcement in the schedule data
+
+
+
+
+ Text of the Announcement
+
+
+
+
+ Text of the Announcement for a text-to-speech-system
+
+
+
+
+
+
+ Structure for describing an area at the stop point for detecting the right stop position
+
+
+
+
+ Distance before the defined Stoppoint, where the detection area begins, value in [m]
+
+
+
+
+ Distance behind the defined Stoppoint, where the detection area begins, value in [m]
+
+
+
+
+
+
+ Structure for describing a beacon point
+
+
+
+
+ Reference to the beacon point in the schedule data
+
+
+
+
+ Code of the beacon point
+
+
+
+
+ Shortname of the beaon point
+
+
+
+
+ Text, which gives some additional information on the beacon point
+
+
+
+
+
+
+
+
+ Length of the bytearray of applikationdata
+
+
+
+
+ Applikationdata from Card as Byte-Array
+
+
+
+
+
+
+
+
+
+ Length of the bytearray of ticketdata
+
+
+
+
+ Ticketdata from Card as Byte-Array
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Structure for describing a connection
+
+
+
+
+ StopPoint, where the connection should take place (from planning system)
+
+
+
+
+ StopPoint-referenced connection-reference
+
+
+
+
+ Describes the kind of connection
+
+
+
+
+ Structure for desccribing the information which is shown on a head- or sidesign
+
+
+
+
+ Platform, on which the connection should take place
+
+
+
+
+ Describes the status of the connection
+
+
+
+
+ Describes the mode of the pick-up vehicle, DEPRECATED !, THE ConnectionMode SHOULD BE USED INSTEAD
+
+
+
+
+ Mode- and Submode information of the pick-up vehicle in accordance with Netex
+
+
+
+
+ Information, at which time the leaving vehicle will depart based on realtime information
+
+
+
+
+ Information, at which time the leaving vehicle is planned to depart
+
+
+
+
+
+
+ Structure for describing data-versions
+
+
+
+
+ Kind of data
+
+
+
+
+ Versionreference of the data
+
+
+
+
+
+
+
+
+
+
+
+ Structure for describing destination information
+
+
+
+
+ Reference to the destination-information in the schedule-data
+
+
+
+
+ Text of the destination
+
+
+
+
+ Shorttext of the destination if there is limited space
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Structure for describing the information for a headsign or a sidesign
+
+
+
+
+ Reference to the display content information in the schedule data
+
+
+
+
+ Information on the line, which should be displayed
+
+
+
+
+ Information on the destination, which should be displayed
+
+
+
+
+ Information on the via points which should be displayed
+
+
+
+
+ Additional Information Text, which could be displayed, e.g. "Extra Ride", "Express", ...
+
+
+
+
+ Additional Information Text, which is assigned project-specific
+
+
+
+
+ Additional Information Text, which is assigned project-specific
+
+
+
+
+ Additional Information Text, which is assigned project-specific
+
+
+
+
+ Additional Information Text, which is assigned project-specific
+
+
+
+
+ Additional Information Text, which is assigned project-specific
+
+
+
+
+ Additional Information Text, which is assigned project-specific
+
+
+
+
+ Additional Information Text, which is assigned project-specific
+
+
+
+
+ Additional Information Text, which is assigned project-specific
+
+
+
+
+ Additional Information Text, which is assigned project-specific
+
+
+
+
+ The run number (Kurs-Nummer) the trip is operated
+
+
+
+
+ Group for Display-Information if there is more than one content at the same time
+
+
+
+
+
+
+
+
+ unique ID for the farezone
+
+
+
+
+
+
+
+
+
+
+
+ code according EN 1545
+
+
+
+
+ text according EN 1545
+
+
+
+
+
+
+ Structure for describing a GNSS-Point
+
+
+
+
+ Reference to the point in schedule data
+
+
+
+
+
+
+
+
+
+ Structure for describing a GNSS-Point
+
+
+
+
+
+
+
+
+
+
+ Reference to the stoppoint from the planning system
+
+
+
+
+
+
+
+
+
+
+
+ Information on Connections or Interchanges; not in StopSequence because of RealTimeInformation
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ identifier of a symbol number , which is used by displays see LINIEN_CODE in VDV 452 chapter 9.7.2 REC_LID
+
+
+
+
+
+
+
+
+
+
+
+ Name of the Service or Device, which sends the message, which has to be logged
+
+
+
+
+
+
+
+
+
+
+ ... of the ErrorMessage
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ aus REC-SEL bzw. REC_SEL_ZP der VDV 452
+
+
+
+
+
+
+
+
+ In Analogie zu REC_ORT aus VDV 452
+
+
+
+
+
+ Point, where specific GNSS-Information is provided, "GNSS-Solution" for the Beacon-Points, analogue to REC_OM from VDV 452
+
+
+
+
+
+ Point, where Information for TrafficSignalPriorisation is provided
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ StopIndex on current trip
+
+
+
+
+ Reference to the stoppoint from the planning system
+
+
+
+
+
+
+
+
+
+ This Value is needed for the demonstration at the SSB
+
+
+
+
+ Soll-Abstand zwischen den Haltestellen
+
+
+
+
+ Information on Connections or Interchanges; not in StopSequence because of RealTimeInformation
+
+
+
+
+
+
+
+
+
+ StopIndex on current trip
+
+
+
+
+ Reference to the stoppoint from the planning system
+
+
+
+
+
+
+
+
+
+
+ A resolution of 30s is recommended, for the display it is recommended to show the arrival time in minutes.
+
+
+
+
+
+
+ This Value is needed for the demonstration at the SSB
+
+
+
+
+ Soll-Abstand zwischen den Haltestellen
+
+
+
+
+ Information on Connections or Interchanges; not in StopSequence because of RealTimeInformation
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ List of StopPoints; with additional information
+
+
+
+
+ Information of the location state
+
+
+
+
+ Delay in seconds. Early times are shown as negative values.
+
+ tbd: what happens, if this value isn't set
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ not StopPointAnnouncements; additional announcements; e.g. of the operator or dispatcher
+
+
+
+
+ The direction of the route, 1->forward 2->backwards and 0->UNDEFINED
+
+
+
+
+ The run number (Kurs-Nummer) the trip is operated
+
+
+
+
+ The pattern number (Linienfahrweg-Nummer) the trip is operated
+
+
+
+
+ The path destination number (RoutenZiel-Nummer) the trip is operated
+
+
+
+
+
+
+
+
+
+
+
+
+ Time, at which the trip is starting
+
+
+
+
+
+
+ In Analogie zu LID-Verlauf aus VDV 452
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Structure for describing a via point on journey.
+
+
+
+
+
+ The identifier of the via place in the journey; used to help identify the vehicle journey on arrival boards.
+
+
+
+
+ The name of the via place in the journey; used to help identify the vehicle to the public.
+
+
+
+
+ The short name of the via place in the journey; used to help identify the vehicle to the public.
+
+
+
+
+ Value, which defines a priority to select a number of via points, if not all via points can be shown
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ For compatibility reasons, this structure is now a sequence of members, all of which are optional - of course, at least one member should be included in meaningful data.
+
+
+
+
+
+ If the service returns a heartbeat value and it is not 0, the subscriber can expect that the service will send data at least every heartbeat seconds. This heartbeat can be used to monitor the connection quality by the client.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Value, which allows to decide which Information is shown, if there is not enough time to show all
+
+
+
+
+ If more than one Sign-Information is given, you need to know
+
+
+
+
+ Time-Value, which defines the part of the Periodtime in which this Sign-Information should be shown
+
+
+
+
+
+
+ a combined Mode and SubMode information in accordance with Netex "netex_submode_version.xsd"
+
+
+
+
+
+
+
+
+
+
+
+
+