| Message Type: | TSDUPD |
|---|---|
| Version: | D |
| Release: | 01C |
| Contr. Agency: | UN |
| Revision: | 2 |
| Date: | 2001-11-07 |
| SOURCE: | D10 Travel, Tourism and Leisure (SWG) |
|
For general information on UN standard message types see UN Trade Data Interchange Directory, UNTDID, Part 4, Section 2.3, UN/ECE UNSM General Introduction |
|
This message also occurs in the following versions of this standard: D00B, D01A, D01B, D01C, D02A, D02B, D03A, D03B, D04A, D04B |
This specification provides the definition of the Timetable static data update - interactive message (TSDUPD) to be used in Electronic Data Interchange (EDI) between trading partners involved in administration, commerce and transport.
A TSDUPD message provides static data complementary to travel schedule information conveyed by a SKDUPD - schedule update interactive message, such as information about locations and parties. A travel service provider sends timetable static data to other service providers or agencies such as government departments, traffic authorities and timetable publishing.
The Timetable static data update - interactive message may be used for both national and international applications. It is based on universal practice related to administration, commerce and transport, and is not dependent on the type of business or industry.
-The message is designed to transmit new or changed schedule information in order to update the recipient system.
-The message can contain either a complete set of schedule information data or updates to a former delivery.
-The message may also be used to formulate a request for re- transmission of the data in case of error.
-The message may be sent spontaneously when the travel service provider has new information available, or as a response to a SKDREQ - schedule request interactive message.
See UNTDID, Part 4, Chapter 2.3 UN/ECE UNSM - General Introduction, Section 1.
See UNTDID, Part 4, Chapter 2.3 UN/ECE UNSM - General Introduction, Section 2.
See UNTDID. Part 4, Chapter 2.6 UN/ECE UNSM - General Introduction, Section 2
This section should be read in conjunction with the segment table which indicates mandatory, conditional and repeating requirements.
A service segment starting and uniquely identifying a message. The message type code for the Timetable static data update - interactive message is TSDUPD.
Note: Timetable static data update - interactive messages conforming to this document must contain the following data in segment UIH, composite S306:
| Data element | 0065 | TSDUPD |
| 0052 | D | |
| 0054 | 01C | |
| 0051 | UN |
A segment to specify the type and business function of the message.
A segment to specify details related to the originator of the schedule update.
A segment to specify information applicable to the entire message.
A segment to provide free text information relating to the entire message.
A segment to specify a reference relating to the entire message.
A segment to provide country specific information as summer or wintertime transition date and currency, applying to the entire message.
Segment providing information about the time zone applying to the entire message.
A segment to provide the language in which the language dependent objects are expressed in the entire message.
A group of segments to specify an error condition.
A segment to specify the type of application error.
A segment to reference the erroneous element.
A segment to provide text related to the error.
SG4-SG5 A group of segments to provide information related to a
A segment to identify a location and its geographical co-ordinates.
A segment to provide address information related to the location.
A segment to provide dates and times related to the location.
A segment to provide contact information related to the location.
A segment to specify traffic restrictions relating to the location.
A segment to provide information related to the country of the location.
A segment to provide information about the time zone wherein the location is situated.
A segment to specify a language related to the location.
A segment to provide information about facilities available at the location.
A segment to provide free text information related to the location.
A segment group to provide information about services available at the location.
A segment to provide information about a service available at the location.
A segment to provide contact information related to the service.
A segment group to provide information about connecting transport services available at the location.
A segment specifying a connecting transport service available at the location.
A segment providing facility information about the connecting transport service.
A segment to provide frequency information relating to the connecting transport service.
A segment to provide free text information related to the connecting transport service.
A segment specifying location (e.g. terminus) and corresponding time information relating to the connecting transport service.
A segment group to provide information about transport services from the location to other destination locations.
A segment referring to a destination location to which transport services are available.
A segment providing facility information about the connecting transport service.
A segment to provide information about a transport services to the destination location.
A segment to provide time information related to the transport service.
A segment to provide facility information related to the transport service.
A group of segments to provide information about parties.
A segment to identify a party.
A segment to provide address information related to the party.
A segment to provide contact information related to the party.
A segment group to provide information about other parties to which the party is related.
A segment referring to another related party.
A segment to specify the kind of relation existing between both parties.
A service segment ending a message, giving the total number of segments in the message (including the UIH & UIT) and the control reference number of the message.
| ADS | Address | |
| ALS | Additional location information | |
| ASD | Service details | |
| CNY | Country information | |
| CON | Contact information | |
| ERI | Application error information | |
| FRQ | Frequency | |
| HDR | Header information | |
| IFT | Interactive free text | |
| LNG | Language | |
| MSD | Message action details | |
| NME | Name | |
| ORG | Originator of request details | |
| POP | Period of operation | |
| POR | Location and/or related time information | |
| PRD | Product identification | |
| RFR | Reference | |
| RLS | Relationship | |
| SER | Facility information | |
| TIZ | Time zone information | |
| TRF | Traffic restriction details | |
| UIH | Interactive message header | |
| UIT | Interactive message trailer |
| ├─UIH Interactive message header | ×1 | (M) |
| ├─MSD Message action details | ×1 | (M) |
| ├─ORG Originator of request details | ×1 | (C) |
| ├─HDR Header information | ×1 | (C) |
| ├─IFT Interactive free text | ×9 | (C) |
| ├─RFR Reference | ×1 | (C) |
| ├─CNY Country information | ×1 | (C) |
| ├─TIZ Time zone information | ×1 | (C) |
| ├─LNG Language | ×1 | (C) |
| ├─Segment Group 1 | ×99 | (C) |
| │─├─ERI Application error information | ×1 | (M) |
| │─├─RFR Reference | ×1 | (C) |
| │─└─IFT Interactive free text | ×1 | (C) |
| ├─Segment Group 2 | ×99999 | (C) |
| │─├─ALS Additional location information | ×1 | (M) |
| │─├─ADS Address | ×1 | (C) |
| │─├─POP Period of operation | ×9 | (C) |
| │─├─CON Contact information | ×1 | (C) |
| │─├─TRF Traffic restriction details | ×1 | (C) |
| │─├─CNY Country information | ×1 | (C) |
| │─├─TIZ Time zone information | ×1 | (C) |
| │─├─LNG Language | ×1 | (C) |
| │─├─SER Facility information | ×1 | (C) |
| │─├─IFT Interactive free text | ×9 | (C) |
| │─├─Segment Group 3 | ×99 | (C) |
| │─│─├─ASD Service details | ×1 | (M) |
| │─│─└─CON Contact information | ×1 | (C) |
| │─├─Segment Group 4 | ×99 | (C) |
| │─│─├─PRD Product identification | ×1 | (M) |
| │─│─├─SER Facility information | ×1 | (C) |
| │─│─├─FRQ Frequency | ×1 | (C) |
| │─│─├─IFT Interactive free text | ×1 | (C) |
| │─│─└─POR Location and/or related time information | ×1 | (C) |
| │─└─Segment Group 5 | ×99 | (C) |
| │───├─RFR Reference | ×1 | (M) |
| │───└─Segment Group 6 | ×99 | (C) |
| │─────├─PRD Product identification | ×1 | (M) |
| │─────├─POP Period of operation | ×1 | (C) |
| │─────└─SER Facility information | ×1 | (C) |
| ├─Segment Group 7 | ×99 | (C) |
| │─├─NME Name | ×1 | (M) |
| │─├─ADS Address | ×1 | (C) |
| │─├─CON Contact information | ×1 | (C) |
| │─└─Segment Group 8 | ×99 | (C) |
| │───├─RFR Reference | ×1 | (M) |
| │───└─RLS Relationship | ×1 | (C) |
| └─UIT Interactive message trailer | ×1 | (M) |