JP2005044282A - Travel plan management system, travel plan management method, and travelling information management program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a travel plan management service working together with the travelling condition of transportation facilities. <P>SOLUTION: The protocol converter 200 of a vacant seat management server 100 managed by the transportation facility generates XML data containing vacant seat information or reserved seat reservation information in accordance with a request from a travel itinerary management server 600 operated by a travel agent and transmits, through the Internet 1000, the XML data to the travel itinerary management server 600. The protocol converter 300 of a travelling management server 400 operated by the transportation facility generates XML data containing travelling information in accordance with a request from the travel itinerary management server 600 and transmits the XML data, through the Internet 1000, to the travel itinerary management server 600. Then, the travel itinerary management 600 manages a travel plan for a traveller based on the XML data received from the vacant seat management server 100 or the travelling management server 400. <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

  The present invention relates to a travel plan management system for managing a travel plan of a traveler, a travel plan management method, and an operation information management program for managing the operation status of transportation facilities.

  As a system for managing travel reservations and travel plans, Patent Document 1 describes a reservation management apparatus capable of automatically changing reservation contents according to the operation status of transportation facilities. According to the reservation management apparatus described in Patent Literature 1, when a train is delayed and it becomes impossible to transfer to a reserved train, the operation management server notifies the reservation service management server of information indicating that fact. To do. Then, the reservation service management server instructs the ticket reservation server to change the reservation contents. Then, the ticket reservation server automatically reserves another train that can be transferred according to the change instruction.

  Further, in Patent Document 2, even if a user does not go to a travel agent, he simply creates an optimum travel guide plan suitable for the conditions by instructing the desired travel conditions from a terminal such as home. A travel guidance providing system that can be provided to users is described. According to the travel guidance providing system described in Patent Document 2, when the travel management server receives travel request conditions from the user terminal, the travel management server acquires travel destination information and traffic information that match the received travel request conditions from the database. To do. The travel management server creates a travel plan unique to the user based on the acquired travel destination information and traffic information, and transmits the travel plan to the user terminal via the communication network.

Japanese Patent Laid-Open No. 2002-297984 (page 3-5, FIG. 1) JP 2002-73756 A (page 5-12, FIG. 1)

  In the reservation management apparatus described in Patent Document 1, a reservation service management server connected to an in-house communication network of a transportation facility can acquire operation management information from the operation management server and process the reservation service. . However, a travel agency server that is not connected to the in-house communication network of the transportation system cannot use the operation management information handled by the transportation system. Therefore, the travel agent cannot manage the travel plan of the traveler in conjunction with the current operation status of the train or the like.

  In addition, in order to manage a travel plan that is linked to the operation status, the travel agency server must be connected to the in-house communication network of the transportation facility with a dedicated line or the like, which places a heavy burden on the travel agency.

  Moreover, in the travel guidance system described in Patent Document 2, a travel guidance plan can be provided based on travel destination information and traffic information registered in a database or the like. However, since the operation management information handled by the transportation facility cannot be used, the travel agent cannot manage the travel plan of the traveler or provide the travel guidance in conjunction with the current operation status of the train or the like.

  SUMMARY OF THE INVENTION An object of the present invention is to provide a travel plan management system, a travel plan management method, and an operation information management program that can provide a travel plan management service linked to the operation status of transportation facilities.

  The travel plan management system according to the present invention is a travel plan management system comprising an operation management server operated by a transportation agency that operates a means of transportation, and an agent server operated by a travel agency, the operation management server comprising: Operation information storage means for storing operation information indicating the operation status of the transportation facility, and operation status XML for extracting operation information from the operation information storage means and generating operation status XML data that is XML data including the extracted operation information Data generation means and operation status XML data transmission means for transmitting the operation status XML data to the agency server via the Internet. The agency server determines the travel plan of the traveler based on the operation status XML data. It is characterized by management. To manage a travel plan, for example, if there is a delay in the transportation schedule, notify the affected traveler that the schedule has been changed individually, or provide local services at the travel destination. It is to adjust the schedule with the company. In addition, managing a travel plan provides a traveler with information such as seats such as a train (transportation means) scheduled to be boarded and reservation contents with a local service provider at a travel destination according to the situation of the traveler. The travel navigation for the traveler.

  The travel plan management system extracts seat reservation information from the seat reservation information storage means for storing the seat reservation information indicating the seat reservation status of the transportation means, and includes the extracted seat reservation information. A seat reservation server including seat reservation XML data generating means for generating seat reservation XML data as data, and seat reservation XML data transmitting means for transmitting the seat reservation XML data to the agent server via the Internet. The server may manage a traveler's travel plan based on the seat reservation XML data. According to such a configuration, the agency server receives the seat reservation information as XML data that can be received via the Internet. Accordingly, since seat reservation information can be acquired via the Internet, the travel agent can provide a travel plan management service linked to the seat reservation status of the transportation facility.

  The agency server determines, based on the operation status XML data, a delay occurrence determination means for determining whether or not there is a delay in the transportation means on which the passenger gets and a delay in the transportation means. In some cases, the information may include delay information transmission means for transmitting delay information indicating a delay state of the transportation means to a mobile terminal used by a traveler via the Internet. According to such a configuration, it is possible to reduce time and effort for the travel agency to notify the affected traveler that the schedule has been individually changed.

  The agency server determines whether the traveler is in the state before, during, or after boarding the transportation, based on the transportation date and time information and current time information included in the transportation status XML data. The delay information transmitting means may include delay information transmitting means for determining delay information according to the traveler's condition to the mobile terminal via the Internet. According to such a configuration, the traveler can obtain the latest travel information according to the travel process, and can receive a travel navigation service during the travel.

  The travel plan management system includes a service provider server operated by a travel destination service provider affiliated with a travel agency, and the service provider server manages service reservation information indicating a reservation status of service provision to a traveler. The service server includes service reservation information management means, and when the agent server determines that a delay has occurred in the transportation means on which the traveler gets based on the operation status XML data, the agency server sends the service provider server via the Internet. It may include change information transmitting means for transmitting service-provided change information. To manage service reservation information, for example, in response to a request from an agent server, it accepts a reservation for service provision to a traveler and generates service reservation information, or extracts service reservation information requested for distribution. Or distributing it to an agency server via the Internet. According to such a configuration, it is possible to reduce the trouble for the travel agency to individually adjust the schedule with the local service company when the operation schedule of the transportation facility is delayed. In addition, the local service company can obtain the change information of the estimated arrival time of the traveler accompanying the delay of the transportation in real time, and can cope with the change of the scheduled time.

  The service reservation information management means may manage the hotel reservation status, the delivery vehicle reservation status, or the product purchase reservation information as the service reservation information. To manage reservation information, for example, in response to a request from an agency server, it accepts hotel reservations, taxi dispatch reservations, or product purchase reservations to generate each reservation information, or the distribution reservation requested In other words, the vehicle allocation reservation or product purchase reservation information is extracted and distributed to the agency server via the Internet. According to such a configuration, hotels, taxi companies, stores, etc. can obtain information on changes in the estimated arrival time of travelers due to transportation delays in real time, and can respond to changes in the scheduled time. it can.

  The agency server includes a history information storage means for storing transmission history information of transmission data transmitted to the operation management server, seat reservation server or service provider server, and the operation management server, seat reservation server or service provider server as an agent. The reception history information of data received from the server is stored in the history information receiving means, the received reception history information, and the history information storage means received from the operation management server, seat reservation server or service provider server via the Internet. History determination means for determining whether or not the contents of the transmission history information to be matched match. According to such a configuration, the travel agent, the transportation facility, and the local service company can exchange the usage fee according to the usage record.

  In the travel plan management method according to the present invention, the operation management server operated by the transportation facility that operates the transportation means extracts the operation information indicating the operation state of the transportation facility, and the operation state is XML data including the extracted operation information. A step of generating XML data, a step of the operation management server transmitting the operation state XML data to the agent server operated by the travel agent via the Internet, and the agent server based on the operation state XML data. And managing a traveler's travel plan.

  The operation information management program according to the present invention is an operation information management program for managing operation information indicating the operation status of a transportation facility, which is used by an agent server operated by a travel agent to manage a travel plan of a traveler. Thus, the operation information is extracted to the computer, the operation status XML data that is the XML data including the extracted operation information is generated, and the operation status XML data is transmitted to the agency server via the Internet. And processing.

  According to the present invention, a travel plan management system, a travel plan management method, and an operation information management program are used to generate operation status XML data that is XML data including operation information indicating the operation status of a transportation facility, and the generated operation status XML. Since the data is transmitted to the agency server operated by the travel agency via the Internet, the agency server can receive the operation information as XML data that can be received via the Internet. Therefore, since the operation information can be acquired in real time via the Internet, the travel agent can provide a travel plan management service linked to the operation status of the transportation facility.

Embodiment 1 FIG.
Hereinafter, embodiments of the present invention will be described with reference to the drawings. FIG. 1 is a block diagram showing an example of the configuration of a travel plan management system according to the present invention. As shown in FIG. 1, in a travel plan management system, an operation management server 400 that manages operation information indicating the operation status of transportation facilities, a vacant seat management server (seat reservation server) 100 that manages vacancy information of transportation facilities, and a travel A travel schedule management server (agency server) 600 that manages a person's travel schedule is connected via the Internet 1000.

  The vacant seat management server 100 and the operation management server 400 are servers operated by transportation facilities. In the present embodiment, a case where the transportation facility is a railway company will be described below as an example. Transportation is not limited to railway companies. In the travel plan management system, a plurality of vacant seat management servers 100 and operation management servers 400 may be connected to the Internet 1000, respectively. The vacant seat management server 100 manages vacant seat information of each train, reserved seat reservation information, and the like. The operation management server 400 manages information such as the presence / absence of delay in the train operation schedule and the reason for delay as operation information.

  As shown in FIG. 1, the vacant seat management server 100 includes a protocol conversion device 200. The protocol conversion device 200 generates XML (eXtensible Markup Language) data including vacant seat information and the like, and transmits it to the travel schedule management server 600 via the Internet 1000. Similarly, the operation management server 400 includes a protocol conversion device 300. The protocol conversion apparatus 300 generates XML data including operation information and transmits the XML data to the travel schedule management server 600 via the Internet 1000.

  The travel schedule management server 600 is a server operated by a travel agency that manages a travel plan for a traveler. The travel schedule management server 600 generates request data for requesting vacant seat information and operation information as XML data, and transmits it to the vacant seat management server 100 and the operation management server 400 via the Internet 1000. The travel schedule management server 600 receives XML data from the vacant seat management server 100 and the operation management server 400 via the Internet 1000. The travel schedule management server 600 performs a travel plan management process based on vacant seat information and operation information included in the received XML data.

  FIG. 2 is a block diagram illustrating an example of the configuration of the vacant seat management server 100. The vacant seat management server 100 includes a protocol conversion function that generates XML data and extracts information from the XML data, and a reserved seat reservation function (including a vacant seat management function) that performs reserved seat reservation processing for a train.

  As shown in FIG. 2, the vacant seat management server 100 provides an XML processing device 201, a command processing device 202, a usage record distribution device 203, an access log storage unit 204, a route / Train name accumulating unit 205. In addition, the vacant seat management server 100 includes a reservation management device 101, a vacant seat management device 102, a reserved seat list storage unit 103, and a vacant seat list storage unit 104 in order to provide a reserved seat reservation function.

  The command processing device 202, the reservation management device 101, and the vacant seat management device 102 are realized by a control unit (not shown) of the vacant seat management server 100. The XML processing device (seat reservation XML data generating means) 201 and the usage record distribution device 203 are realized by a control unit of the vacant seat management server 100, a network interface unit (not shown), and the like. The access log storage unit 204, the route / train name storage unit 205, the reserved seat list storage unit (seat reservation information storage unit) 103, and the vacant seat list storage unit 104 are realized by a database (not shown) of the vacant seat management server 100. The The protocol conversion device 200 is realized by an XML processing device 201, an instruction processing device 202, a usage record distribution device 203, an access log storage unit 204, and a route / train name storage unit 205.

  The vacant seat accumulation unit 104 stores vacant seat list information of each train at the current time. The vacant seat management apparatus 102 performs management processing of vacant seat information of each train. For example, when a reserved seat is newly reserved, the vacant seat management apparatus 102 deletes the vacant seat information corresponding to the reserved seat reserved from the list information stored in the vacant seat list storage unit 104.

  The reserved seat list storage unit 103 stores list information of reserved seats reserved at the current time. The reservation management apparatus 101 performs management processing of reserved reserved seat information. For example, when a reserved seat reservation request is newly made, the reservation management apparatus 101 receives current vacant seat information from the vacant seat management apparatus 102. Then, the reservation management apparatus 101 determines a reserved seat based on the vacant seat information, and stores it in addition to the list information stored in the reserved seat list storage unit 103.

  The XML processing apparatus 201 receives request data described in XML format via the Internet 1000 from the travel schedule management server 600 or the like. The XML processing device 201 extracts from the received request data a processing name of processing to be performed by the command processing device 202, a train ID for identifying a train, and a route ID for identifying a route. Train ID and route ID play a role as parameters of processing to be executed by the instruction processing device 202. Further, when receiving the request data, the XML processing apparatus 201 stores information such as a request time, a request source, and a request content in the access log accumulation unit 204.

  The command processing device 202 executes the requested process based on the process name and parameters (train ID and route ID). In the case of reserved seat reservation request processing, the command processing device 202 causes the reservation management device 101 to execute reserved seat reservation processing. When the reservation management device 101 executes the reservation process, the command processing device 202 receives reservation information for the designated seat such as the seat number of the reserved seat that has been reserved from the reservation management device 101.

  The route / train name accumulation unit 205 stores correspondence information between each train ID and a train name, and correspondence information between each route ID and a route name. The instruction processing device 202 converts the train ID included in the request data into a train name and converts the route ID into a route name based on the correspondence information stored in the route / train name accumulation unit 205. The XML processing device 201 generates XML data including the train name and route name along with the reserved seat reservation information, and distributes it to the travel schedule management server 600 via the Internet 1000.

  In addition, the usage record distribution device 203 collects the access history information stored in the access log storage unit 204 for each request source for each predetermined period, and distributes it as usage record information to the travel schedule management server 600 via the Internet 1000. To do.

  FIG. 3 is a block diagram illustrating an example of the configuration of the operation management server 400. The operation management server 400 includes a protocol conversion function for generating XML data and extracting information from the XML data, and an operation information management function for performing operation information management processing.

  As shown in FIG. 3, the operation management server 400 provides an XML processing device 301, a command processing device 302, a usage record distribution device 303, an access log storage unit 304, a route / A train name accumulation unit 305 and a partner list accumulation unit 306 are included. The operation management server 400 includes a delay reason management device 401, a delay time management device 402, a delay reason storage unit 404, and a delay time storage unit 405 in order to provide an operation information management function.

  The command processing device 302, the delay reason management device 401, and the delay time management device 402 are realized by a control unit (not shown) of the operation management server 400 or the like. The XML processing device 301 and the usage record distribution device 303 are realized by a control unit of the operation management server 400, a network interface unit (not shown), and the like. The access log storage unit 304, the route / train name storage unit 305, the partner list storage unit 306, the delay reason storage unit (operation information storage unit) 404 and the delay time storage unit (operation information storage unit) 405 are included in the operation management server 400. This is realized by a database (not shown). The protocol conversion device 300 is realized by an XML processing device (operation status XML data generation means) 301, a command processing device 302, a usage record distribution device 303, an access log storage unit 304, and a route / train name storage unit 305.

  In the present embodiment, the storage device (not shown) of the operation management server 400 stores various programs for managing operation information. For example, the storage device of the operation management server 400 extracts operation information to a computer and generates operation status XML data that is XML data including the extracted operation information and the operation status XML data via the Internet. The operation information management program for executing the processing to be transmitted to the agency server is stored.

  The XML processing apparatus 301 receives request data described in XML format via the Internet 1000 from the travel schedule management server 600 or the like. The XML processing device 301 extracts, from the received request data, a processing name of processing to be performed by the command processing device 302, and a train ID and route ID that are parameters of the processing. Further, when receiving the request data, the XML processing apparatus 301 stores information such as a request time, a request source, and a request content in the access log accumulation unit 304.

  The command processing device 302 executes the requested process based on the process name and parameters (train ID and route ID). When a delay occurs in the train and a delivery request is received from a travel agent or the like, the command processing device 302 requests the delay reason management device 401 for information on the reason for delay. Further, the instruction processing device 302 requests the delay time management device 402 for information regarding the delay time.

  The delay reason accumulation unit 404 stores information such as a delay reason that is input by a person in charge in the central control room of the transportation facility when a delay occurs in the train. When a train delay occurs, for example, when a train station employee reports the cause of the train delay to the central control room of the transportation facility, the person in charge of the central control room inputs the reason for the delay by operating the terminal etc. To do. Then, the delay reason management device 401 of the operation management server 400 stores the input delay reason in the delay reason accumulation unit 404. Further, the delay reason management device 401 can extract information from the delay reason storage unit 404 until the train delay is resolved.

  As shown in FIG. 3, the delay time management device 402 is connected to a plurality of passage time measuring devices 403. The passage time measuring device 403 is installed at each station, and is realized by, for example, a push button device, a time recording device, and a terminal device. For example, when the train arrives at the platform of the station and the station staff presses the push button, the time recording device records the time at that time as the train passing time. Then, the passage time measuring device 403 transfers the detected train passage time and the train ID of the train that has passed to the delay time management device 402 via an in-house communication network of a transportation facility.

  The delay time accumulating unit 405 stores operation schedule information for each train in advance. When the train ID and the passage time are transferred from the passage time measuring device 403, the delay time management device 402 determines the train ID of the delayed train based on the operation schedule information stored in the delay time accumulation unit 405. Identify and calculate the delay time. Then, the delay time management device 402 associates the train ID of the delayed train with the delay time and causes the delay time accumulating unit 405 to store them.

  The delay time management device 402 extracts delay time information from the delay time storage unit 405 in response to a request from the instruction processing device 302. The instruction processing device 302 can receive the delay time information from the delay time management device 402 until the delay time value becomes a predetermined threshold value or less.

  The route / train name accumulation unit 305 stores correspondence information between each train ID and a train name, and correspondence information between each route ID and a route name. When receiving the delay reason information from the delay reason management device 401 and the delay time information from the delay time management device 402, the command processing device 302 requests data based on the correspondence information stored in the route / train name accumulation unit 305. The train ID included in is converted into a train name, and the route ID is converted into a route name. The XML processing device 301 generates XML data including a train name and a route name together with information on a delay reason and a delay time, and distributes the XML data to the travel schedule management server 600 via the Internet 1000.

  In addition, the usage record distribution device 303 collects the access history information stored in the access log storage unit 304 for each request source for each predetermined period, and uses it as the ID information of the partner server stored in the partner list storage unit 306. Based on the information, the information is distributed to the travel schedule management server 600 via the Internet 1000 as usage record information.

  As described above, according to the present embodiment, the vacant seat management server 100 and the operation management server 400 generate XML data including vacant seat information, operation information, and the like that are handled by the transportation facility through its own communication network. Then, the vacancy management server 100 and the operation management server 400 distribute the generated XML data to the travel schedule management server 600 of the travel agency via the Internet 1000.

  Vacant seat information and operation information handled by the transportation system can be used easily without installing a dedicated line to connect to the internal network of the transportation system. It is possible to determine in real time whether the schedule of the product is affected. Therefore, a travel agent can provide a service linked to operation information from a transportation facility to a traveler or a partner local service company. Therefore, the travel agent can provide a travel plan management service linked to the operation status of the transportation facility.

Embodiment 2. FIG.
Next, a second embodiment of the present invention will be described with reference to the drawings. FIG. 4 is a block diagram showing an example of the configuration of the travel plan management system according to the present embodiment. In the present embodiment, the travel agency is affiliated with each local service company of a travel product such as a store, a hotel, a taxi company. As shown in FIG. 4, in the travel plan management system, in addition to the configuration shown in the first embodiment, the mobile terminal 500 used by the traveler, the store server 700 used by the store of the travel destination, A hotel server 800 used by a hotel and a taxi company server 900 used by a taxi company at a travel destination are connected via the Internet 1000.

  In the present embodiment, the travel schedule management server 600 receives operation information such as train delay from the operation management server 400, and then receives information such as train delay from the portable terminal 500 and servers 700, 800, 900 of each local service company. Deliver to.

  The portable terminal 500 is a terminal such as a cellular phone, a PDA (Personal Digital Assistants), or a notebook personal computer used by a traveler. The mobile terminal 500 is installed with a browser or the like and has an Internet 1000 connection function. In the travel plan management system, a plurality of portable terminals 500 may be connected to the Internet 1000.

  The store server 700 is a server used by a store visited by a traveler at a travel destination. In this embodiment, the travel agency is affiliated with a store that sells local special products and the like in advance. The store server 700 manages reservation information for merchandise sales of travelers, and manages inventory information of merchandise sold to travelers. In the travel plan management system, a plurality of store servers 700 may be connected to the Internet 1000.

  FIG. 5 is a block diagram illustrating an example of the configuration of the store server 700. As illustrated in FIG. 5, the store server 700 includes an XML processing device 701, an instruction processing device 702, a usage record distribution device 703, a reservation management device 704, an inventory management device 705, an access log storage unit 706, a reservation ID list storage unit 707. And a product list storage unit 708.

  The command processing device 702, the reservation management device (service reservation information management means) 704, and the inventory management device 705 are realized by a control unit (not shown) of the store server 700. The XML processing device 701 and the usage record distribution device 703 are realized by a control unit of the store server 700, a network interface unit (not shown), and the like. The access log storage unit 706, the reservation ID list storage unit 707, and the product list storage unit 708 are realized by a database (not shown) of the store server 700 or the like.

  The XML processing device 701 extracts processing names and parameters included in request data from the travel schedule management server 600 and generates XML data for distribution to the travel schedule management server 600. The instruction processing device 702 executes the requested process based on the process name and parameters. The product list storage unit 708 stores list information of products handled by the store. The inventory management device 705 performs product inventory management processing based on the product information stored in the product list storage unit 708.

  The reservation ID list storage unit 707 stores list information of product purchase reservations such as travelers. In response to a request from the instruction processing device 702, the reservation management device 704 performs management processing of reservation information for purchasing goods such as travelers. The access log accumulation unit 706 accumulates access history information such as when request data is received. The usage record distribution device 703 collects the access history information stored in the access log accumulation unit 706 for each request destination and distributes it via the Internet 1000 for each predetermined period.

  Hotel server 800 is a server used by a hotel where a traveler stays. In this embodiment, the travel agency is affiliated with a local hotel. The hotel server 800 manages vacancy information and travel reservation information for travelers. In the travel plan management system, a plurality of hotel servers 800 may be connected to the Internet 1000.

  FIG. 6 is a block diagram illustrating an example of the configuration of the hotel server 800. As shown in FIG. 6, the hotel server 800 includes an XML processing device 801, an instruction processing device 802, a usage record distribution device 803, a reservation management device 804, an equipment management device 805, an access log storage unit 806, and a reservation ID list storage unit 807. And a room list storage unit 808.

  The command processing device 802, the reservation management device (service reservation information management means) 804, and the facility management device 805 are realized by a control unit (not shown) of the hotel server 800. The XML processing device 801 and the usage record distribution device 803 are realized by a control unit and a network interface unit (not shown) of the hotel server 800. The access log storage unit 806, the reservation ID list storage unit 807, and the room list storage unit 808 are realized by a database (not shown) of the hotel server 800 or the like.

  The XML processing device 801 extracts processing names and parameters included in request data from the travel schedule management server 600 and generates XML data for distribution to the travel schedule management server 600. The instruction processing device 802 executes the requested process based on the process name and parameters. The room list storage unit 808 stores list information such as hotel vacancies. The room list storage unit 808 also stores facility information such as hotel shuttle cars and heating facilities. The facility management device 805 performs management of hotel facilities based on the empty room information and facility information stored in the room list storage unit 808.

  The reservation ID list storage unit 807 stores list information of reserved rooms. In response to a request from the instruction processing device 802, the reservation management device 804 performs management processing of reservation information for accommodation such as a traveler. The access log storage unit 806 stores access history information such as when request data is received. The usage record distribution device 803 collects the access history information stored in the access log storage unit 806 for each request destination and distributes it via the Internet 1000 for each predetermined period.

  The taxi company server 900 is a server used by a taxi company of a taxi that travelers use to travel on site. In the present embodiment, the travel agency is affiliated with a local taxi company in advance. The taxi company server 900 manages taxi vacant vehicle information and dispatch information. In the travel plan management system, a plurality of taxi company servers 900 may be connected to the Internet 1000.

  FIG. 7 is a block diagram illustrating an example of the configuration of the taxi company server 900. As shown in FIG. 7, the taxi company server 900 includes an XML processing device 901, a command processing device 902, a usage record distribution device 903, a reservation management device 904, an empty vehicle management device 905, an access log storage unit 906, a reservation ID list storage unit. 907 and an empty car list storage unit 908.

  The command processing device 902, the reservation management device (service reservation information management means) 904, and the empty vehicle management device 905 are realized by a control unit (not shown) of the taxi company server 900 or the like. The XML processing device 901 and the usage record distribution device 903 are realized by a control unit and a network interface unit (not shown) of the taxi company server 900. The access log accumulation unit 906, the reservation ID list accumulation unit 907, and the empty vehicle list accumulation unit 908 are realized by a database (not shown) of the taxi company server 900 or the like.

  The XML processing device 901 extracts processing names and parameters included in request data from the travel schedule management server 600 and generates XML data for distribution to the travel schedule management server 600. The instruction processing device 902 executes the requested process based on the process name and parameters. The empty vehicle list accumulation unit 908 stores list information such as taxis in an empty vehicle state. The empty vehicle management device 905 performs taxi dispatch management processing based on the empty vehicle information stored in the empty vehicle list storage unit 908.

  The reservation ID list storage unit 907 stores list information of reserved taxis. The reservation management device 904 performs management processing of taxi reservation information such as a traveler in response to a request from the command processing device 902. The access log accumulation unit 906 accumulates access history information such as when request data is received. The usage record distribution device 903 collects the access history information stored in the access log storage unit 906 for each request destination and distributes it via the Internet 1000 every predetermined period.

  FIG. 8 is a block diagram showing an example of the configuration of the travel schedule management server 600. As shown in FIG. 8, the travel schedule management server 600 includes an XML processing device 600a, a usage record inspection device 601, a usage record recording device 602, a partner company management device 603, a reservation management device 604, a member management device 605, and a travel management device. 606, an access log storage unit 607, a local company list storage unit 608, a transportation agency list storage unit 609, an integrated reservation ID list storage unit 610, a member information list storage unit 611, and a travel route list storage unit 612.

  The usage record inspection device (history determination means) 601, the usage record recording device (history information reception means) 602, the affiliated company management device 603, the reservation management device 604, the member management device 605, and the travel management device 606 are included in the travel schedule management server 600. This is realized by a control unit (not shown). The XML processing apparatus 600a is realized by a control unit of the travel schedule management server 600, a network interface unit (not shown), and the like. An access log storage unit (history information storage unit) 607, a local company list storage unit 608, a transportation agency list storage unit 609, an integrated reservation ID list storage unit 610, a member information list storage unit 611, and a travel route list storage unit 612 This is realized by a database (not shown) of the schedule management server 600. The delay occurrence determination unit and the traveler situation determination unit are realized by the control unit of the travel schedule management server 600 and the like. The delay information transmission unit and the change information transmission unit are realized by the control unit, the network interface unit, and the like of the travel schedule management server 600.

  The XML processing device 600a extracts information from XML data from the vacant seat management server 100, the operation management server 400, and the like, and generates XML data to be distributed to each server. The usage record recording device 602 causes the access log storage unit 607 to store log information of request processing for the vacant seat management server 100 and the operation management server 400 and distribution processing to each server 700, 800, 900 of the local service company. The usage record inspection device 601 detects a usage record such as operation information based on history information received from each server 100, 400, 700, 800, 900 and information stored in the access log storage unit 607.

  The local company list storage unit 608 stores list information of each local service company with which the travel agency is affiliated. For example, the local company list storage unit 608 stores a partner ID, hotel ID, taxi company ID, and the like. The transportation list accumulation unit 609 stores list information of transportation organizations with which the travel agency is affiliated. For example, the transportation list accumulation unit 609 stores the transportation organization ID of the partner. The affiliated company management device 603 manages information on the affiliated company of the travel agency based on the list information stored in the local company list accumulation unit 608 and the transportation organization list accumulation unit 609.

  The integrated reservation ID list storage unit 610 stores list information including all reservation IDs of transportation, hotels, taxis, stores, etc. included in the travel plan for travel products reserved by travelers. Hereinafter, the list information stored in the integrated reservation ID list storage unit 610 is referred to as integrated reservation information. The reservation management device 604 performs reservation management for each traveler based on the integrated reservation information stored in the integrated reservation ID list storage unit 610.

  The member information list storage unit 611 stores list information of member information of travelers who are registered as members of a travel agency. Hereinafter, the list information stored in the member information list storage unit 611 is referred to as member registration information. The member management apparatus 605 performs member information management processing based on the member registration information stored in the member information list storage unit 611.

  The travel route list storage unit 612 stores information on travel products handled by the travel agency. For example, the travel route list storage unit 612 stores travel product information including ID information such as transportation, hotels, taxis, and stores included in the travel plan. The travel management device 606 performs travel product management processing based on the travel product information stored in the travel route list storage unit 612.

  FIG. 9 is an explanatory diagram showing an example of reservation information list information stored in the storage unit of each server. FIG. 9A is an example of the contents of the integrated reservation information stored in the integrated reservation ID list storage unit 610 of the travel schedule management server 600. As shown in FIG. 9A, the integrated reservation information includes an integrated reservation ID, a transportation facility ID, a reserved seat reservation (outbound trip) ID, a reserved seat reservation (return trip) ID, a hotel ID, an accommodation reservation ID, a taxi company ID, Includes taxi reservation ID, store ID, and product reservation ID.

  The integrated reservation ID is identification information for identifying the travel product itself reserved by the traveler. The transportation ID is identification information of the transportation included in the travel plan of the travel product. The reserved seat reservation (outbound / returned) ID is reservation identification information of a round-trip train reserved seat. The hotel ID is identification information of a hotel included in the travel plan. The hotel reservation ID is hotel reservation identification information. The taxi company ID is identification information of a taxi company included in the travel plan. The taxi reservation ID is taxi reservation identification information. The store ID is identification information of a visited store included in the travel plan. The product reservation ID is reservation identification information for product purchase at the visited store.

  FIG. 9B shows reservation information list information stored in the reservation ID list storage unit 807 of the hotel server 800. Hereinafter, the list information stored in the reservation ID list storage unit 807 is referred to as accommodation reservation information. As shown in FIG. 9B, the accommodation reservation information includes an accommodation reservation ID, a traveler's arrival time and departure time, a traveler's room, a traveler's name, and a travel agency's agency ID. The accommodation reservation ID is the same information as the accommodation reservation ID included in the integrated reservation information.

  FIG. 9C shows reservation information list information stored in the reservation ID list storage unit 907 of the taxi company server 900. Hereinafter, the list information stored in the reservation ID list storage unit 907 is referred to as taxi reservation information. As shown in FIG. 9 (c), the taxi reservation information includes a taxi reservation ID, a scheduled departure time of the taxi, a destination, a vehicle number, a crew member name, the number of passengers, a tourist name, and a travel agent's agent ID. . The taxi reservation ID is the same information as the taxi reservation ID included in the integrated reservation information.

  FIG. 9D shows reservation information list information stored in the reservation ID list storage unit 707 of the store server 700. Hereinafter, the list information stored in the reservation ID list storage unit 707 is referred to as product reservation information. As shown in FIG. 4D, the product reservation information includes a product reservation ID, the name of the product reserved for purchase, the number, the reception time, the name of the traveler, and the agent ID of the travel agent. The product reservation ID is the same information as the product reservation ID included in the integrated reservation information.

  FIG. 9E shows reservation information list information stored in the reserved seat list storage unit 103 of the vacant seat management server 100. Hereinafter, the list information of reserved seat reservation contents stored in the reserved seat list storage unit 103 will be referred to as reserved seat reservation information. As shown in FIG. 9E, the reserved seat reservation information includes a reserved seat reservation ID, a route ID, a train ID, a reserved seat list of reserved seats, a traveler's name, and a travel agent's agent ID. The reserved seat reservation ID is the same information as the reserved seat reservation (outward trip) ID or the reserved seat reservation (return trip) ID included in the integrated reservation information.

  Next, the operation will be described. FIG. 10 is a flowchart illustrating an example of an operation information notification process in which the travel schedule management server 600 notifies the mobile terminal 500 and the servers 700, 800, and 900 of operation information such as train delay. The travel schedule management server 600 receives XML data including operation information such as delayed train ID, delay time, and delay reason from the operation management server 400 via the Internet 1000 (step S101). The travel schedule management server 600 receives all reserved seat reservation information requested by the travel schedule management server 600 from the vacant seat management server 100 via the Internet 1000 (step S102).

  The travel schedule management server 600 determines whether the train ID of the delayed train matches the train ID of the reserved seat reservation data based on the train ID included in the reserved seat reservation data. If it is determined that the train IDs match, the travel schedule management server 600 extracts the matched train ID as a delayed train reservation ID (step S103). The travel schedule management server 600 performs the same process for all reserved seat reservation IDs, and temporarily stores the extracted delayed train reservation ID list in a storage device or the like.

  The travel schedule management server 600 obtains the delayed train reservation ID and the reserved seat reservation ID based on the reserved seat reservation (outbound) ID and the reserved seat reservation (return) ID included in the integrated reservation information shown in FIG. It is determined whether or not they match (step S104). If it is determined that they match, the travel schedule management server 600 extracts the integrated reservation ID corresponding to the matched reserved seat reservation ID as the delayed integrated reservation ID. The travel schedule management server 600 performs the same processing for all integrated reservation IDs, and temporarily stores the extracted delayed integrated reservation ID list in a storage device or the like.

  The member registration information stored in the member information list storage unit 611 of the travel schedule management server 600 includes an integrated reservation ID of a travel product reserved by the traveler. The travel schedule management server 600 determines whether or not the delayed integrated reservation ID matches the integrated reservation ID included in the member registration information (step S105). If it is determined that they match, the travel schedule management server 600 extracts the member's email address included in the member registration information. Similarly, the travel schedule management server 600 determines whether or not the delayed integrated reservation ID and the integrated reservation ID match for all members, and extracts all the mail addresses of the members corresponding to the matching integrated reservation ID.

  Then, the travel schedule management server 600 distributes train delay information via the Internet 1000 to the mobile terminals 500 of all applicable travelers based on the extracted mail addresses.

  Further, when the travel schedule management server 600 extracts the delayed integrated reservation ID in step S104, the local service company ID (hotel ID, taxi company ID, store ID) and reservation ID (accommodation ID) are based on the delayed integrated reservation ID. The reservation ID, taxi reservation ID, and product reservation ID) are extracted (step S108). In addition, the travel schedule management server 600 receives the estimated arrival time including the delay time from the operation management server 400 via the Internet 1000 (step S109). Then, the travel schedule management server 600 delivers the changed scheduled arrival time to the store server 700, the hotel server 800, and the taxi company server 900 via the Internet 1000 (step S110).

  As described above, according to the present embodiment, when there is a delay in the transportation schedule, the travel schedule management server 600 searches for an affected travel reservation, and the mobile terminal 500 and each local service company Deliver the schedule information after the change to the server. Therefore, it is possible to reduce the time and effort of the travel agent to individually adjust the schedule with the local service company when the transportation schedule is delayed. In addition, it is possible to reduce the trouble for the travel agent to notify the affected traveler that the schedule has been individually changed.

  In addition, local service companies such as hotels, taxi companies, and stores can acquire in real time information on changes in the estimated arrival time of travelers due to transportation delays, and can respond to changes in the scheduled time.

Embodiment 3 FIG.
Next, a third embodiment of the present invention will be described with reference to the drawings. In the present embodiment, the configuration of the travel plan management system is the same as that of the second embodiment. In the present embodiment, a user (traveler) of a travel product performs membership registration in the travel schedule management server 600 using the mobile terminal 500 in advance. And the user who became a member can confirm the reservation content using the portable terminal 500, and receives member services, such as travel navigation, while traveling.

  The portable terminal 500 transmits registration information such as a user name, a telephone number, an e-mail address, and a password to the travel schedule management server 600 via the Internet 1000 in accordance with the operation of the user who wants to use. When the registration information is received, the member management device 605 of the travel schedule management server 600 assigns a member ID to the user who requested the registration. Then, the member management apparatus 605 generates member registration information including the member ID and each registration information, and stores the member registration information in the member information list storage unit 611.

  FIG. 11 is an explanatory diagram showing an example of the contents of member registration information stored in the member management apparatus 605. As shown in FIG. 11A, the member registration information includes member ID, user name, telephone number, e-mail address, password, integrated reservation ID, and point information. The integrated reservation ID and points are set to “0” at the time of new membership. When the user reserves a travel product or the like, the integrated reservation ID assigned to the travel reservation is added to the member registration information and stored.

  The point is index data used for providing member services such as travel discounts. For example, when a user uses a travel product provided by a travel agency, the value of points is added. And a user can receive member services, such as a travel discount, from a travel agency according to a point value.

  In the present embodiment, a case where the member registration information shown in FIG. 11A is XML data will be described as an example. FIG. 11B is an explanatory diagram showing an example of the contents of XML data indicating member registration information. In the example of the member registration information shown in FIG. 11B, the user's member ID is “0001”, the name is “name 1”, the telephone number is “0312345678”, and the mail address is “taro @ aaa.com "and the password is" aHbE8k3Qz ". Further, the user has already reserved the travel product, and the integrated reservation ID of the reserved travel product is “10324586”. In addition, the user has already used the travel agency several times, and the points have already been added by “13 points”.

  The information included as member registration information is not limited to the information shown in FIG. For example, the member registration information may include information such as the user's address. In this embodiment, the case where one integrated reservation ID can be registered at a time in the member registration information will be described as an example. However, a user can reserve a plurality of travel products at the same time, and a plurality of pieces of integration information can be integrated into the member registration information. A reservation ID may be registered.

  In order to access the travel schedule management server 600, the user who becomes a member operates the portable terminal 500 and inputs a member ID and a password. Then, the portable terminal 500 transmits the input member ID and password to the travel schedule management server 600 via the Internet 1000. When the member ID and password are received, the travel management device 606 extracts information on travel products handled by the travel agency from the travel route list storage unit 612. Then, the travel schedule management server 600 transmits the extracted travel product information to the mobile terminal 500 via the Internet 1000.

  When the travel product information is received, the mobile terminal 500 displays list information of travel products handled by the travel agency based on the received travel product information. The user browses the displayed travel product list, and applies for the travel schedule and the number of tourists. When the travel schedule and the number of travelers are input in accordance with the user's operation, the mobile terminal 500 transmits the input travel schedule and information on the number of travel persons to the travel schedule management server 600 via the Internet 1000.

  The travel schedule management server 600 transmits the travel schedule information received from the portable terminal 500 and the vacancy check request to the vacancy management server 100 via the Internet 1000. When the reserved seat reservation corresponding to the travel schedule is made, the vacant seat management server 100 issues a reserved seat reservation ID and transmits the issued reserved seat reservation ID to the travel schedule management server 600 via the Internet 1000.

  The travel schedule management server 600 transmits a request for each reservation to the store server 700, the hotel server 800, and the taxi company server 900 via the Internet 1000. The travel product information stored in the travel route list storage unit 612 includes ID information of accommodation hotels, visited stores, taxi companies, etc. included in the travel plan. A reservation request is transmitted to each server 700, 800, 900 based on the ID information included in the information. The store server 700, the hotel server 800, and the taxi company server 900 issue each reservation ID (accommodation reservation ID, taxi reservation ID, product reservation ID, etc.) when the reservation is completed, and travel the issued reservation ID via the Internet 1000. It transmits to the schedule management server 600.

  When each reservation ID is received, the reservation management device 604 of the travel schedule management server 600 generates an integrated reservation ID based on the received reservation ID, and stores the generated integrated reservation ID in the integrated reservation ID list storage unit 610. Also, the member management apparatus 605 adds the integrated reservation ID generated by the reservation management apparatus 604 to the member registration information and stores it in the member information list storage unit 611 as shown in FIG.

  Next, an operation of processing for distributing travel information in response to a user request will be described. FIG. 12 is a flowchart illustrating an example of the travel information distribution process. When the user wants to check the latest travel information about the travel product booked after making the travel product reservation, the user operates the portable terminal 500 to access the travel schedule management server 600 and the member ID and Enter the password. Then, the portable terminal 500 transmits a request for travel information together with the input member ID and password to the travel schedule management server 600 via the Internet 1000 (step S200).

  For example, the user operates the mobile terminal 500 and inputs a URL (Uniform Resource Locator) of the travel schedule management server 600 using a browser. Then, portable terminal 500 displays a member ID and password input screen based on the Web page screen information received from travel schedule management server 600 via Internet 1000. When the member ID and password are input by the user, the portable terminal 500 transmits a request for the member ID, password and travel information to the travel schedule management server 600 via the Internet 1000.

  When the travel information request is received, the travel schedule management server 600 extracts the member registration information corresponding to the user from the member information list storage unit 611 based on the received member ID. The travel schedule management server 600 extracts integrated reservation information from the integrated reservation ID list storage unit 610 based on the integrated reservation ID included in the extracted member registration information. Then, the travel schedule management server 600 extracts each reservation ID (designated seat reservation ID, accommodation reservation ID, taxi reservation ID, product reservation ID, etc.) from the extracted integrated reservation information.

  When each reservation ID is extracted, the travel schedule management server 600 transmits a request for reservation contents to the vacant seat management server 100 via the Internet 1000 based on the extracted reserved seat reservation ID (step S201). In addition, the travel schedule management server 600 makes a request for reservation contents to the hotel server 800, taxi company server 900, and store server 700 via the Internet 1000 based on the extracted room reservation ID, taxi reservation ID, and product reservation ID. Transmit (step S202).

  The vacant seat management server 100 extracts the reservation content information (specified seat reservation information) corresponding to the reserved seat reservation ID from the reserved seat list storage unit 103 and transmits it to the travel schedule management server 600 via the Internet 1000 (step S203). ). Each server 700, 800, 900 of the local service company extracts information on reservation contents corresponding to each reservation ID from each storage unit 707, 807, 907 and transmits it to the travel schedule management server 600 via the Internet 1000. (Step S204).

  The travel schedule management server 600 transmits a train departure / arrival time request to the operation management server 400 via the Internet 1000 together with the current time and the train ID included in the received reserved seat reservation information (step S205). When a delay occurs in the operation schedule, the operation management server 400 extracts the departure / arrival scheduled time including the delay time from the delay time storage unit 405 and travels via the Internet 1000 to the travel schedule management server 600. (Step S206).

  The travel schedule management server 600 generates travel information based on the reservation content information received from each of the servers 100, 700, 800, and 900 and the departure / arrival time information received from the operation management server 400. Then, the travel schedule management server 600 transmits the generated travel information to the mobile terminal 500 via the Internet 1000 (step S207).

  When the travel information is received, the mobile terminal 500 displays the received travel information. For example, the mobile terminal 500 displays travel information using a browser based on the screen information of the Web page received from the travel schedule management server 600.

  In addition, the travel schedule management server 600 can further perform travel information distribution processing according to the travel of the traveler. FIG. 13 is a flowchart illustrating an example of a distribution process of travel information according to the travel of the traveler. When the departure / arrival scheduled time is transmitted by the operation management server 400, the travel schedule management server 600 receives the scheduled departure / arrival time including delay information via the Internet 1000 (step S300). Moreover, the travel schedule management server 600 extracts the current time information (step S301).

  The travel schedule management server 600 compares the received departure / arrival scheduled time with the current time, and determines whether the current time corresponds to the departure date of the travel (step S302). If it is determined that the departure date falls, the travel schedule management server 600 further determines whether or not it is a time zone before departure departure (step S303).

  If it is determined that it is the time zone before departure, the travel schedule management server 600 transmits a request for the boarding station and departure time to the operation management server 400 via the Internet 1000 to the operation management server 400. The operation management server 400 extracts boarding station and departure time information from the delay time storage unit 405 and transmits the information to the travel schedule management server 600 via the Internet 1000. Then, the travel schedule management server 600 receives and acquires information on the boarding station and departure time from the operation management server 400 via the Internet 1000 (step S304).

  If it is determined in step S303 that it is not the time zone before departure, the travel schedule management server 600 determines whether or not the current time is a time zone during which the train is being boarded. If it is determined that it is a boarding time zone, the travel schedule management server 600 transmits a request for information accompanying the next stop station to the operation management server 400 via the Internet 1000. The operation management server 400 extracts information associated with the next stop station from the delay time storage unit 405 and transmits the information to the travel schedule management server 600 via the Internet 1000. Then, the travel schedule management server 600 receives and acquires information associated with the next stop station from the operation management server 400 via the Internet 1000 (step S306).

  If it is determined in step S305 that it is not a time zone during boarding, the travel schedule management server 600 determines that the current time is a time zone after getting off such as a train. In this case, the travel schedule management server 600 transmits a request for reservation information to each server 700, 800, 900 of the local service company via the Internet 1000. Each server 700, 800, 900 extracts reservation information from each storage unit 707, 807, 907 and transmits it to the travel schedule management server 600 via the Internet 1000. Then, the travel schedule management server 600 receives and acquires each reservation information of the local service company from each server 700, 800, 900 via the Internet 1000 (step S307).

  If it is determined in step S302 that it is not a departure date, the travel schedule management server 600 determines whether or not the current time falls within the travel period excluding the departure date and the return date (step S308). When it is determined that it is during the travel period excluding the departure date and the return date, the travel schedule management server 600 transmits a request for hotel information to the hotel server 800 via the Internet 1000. The hotel server 800 extracts hotel information from the storage units 807 and 808 and transmits it to the travel schedule management server 600 via the Internet 1000. The travel schedule management server 600 receives and acquires hotel information from the hotel server 800 via the Internet 1000 (step S309).

  If it is determined in step S308 that the travel period is not in progress, the travel schedule management server 600 determines that a travel reservation has not been made, or that a travel reservation has been made but it is outside the travel period. If it is determined that it is not during the travel period, the travel schedule management server 600 extracts the advertisement information of the travel agent (step S310). For example, the travel schedule management server 600 includes an advertisement accumulation unit (not shown) that stores advertisement information of a travel agency, and extracts advertisement information from the advertisement accumulation unit.

  The travel schedule management server 600 generates travel information by collecting the acquired reservation information and advertisement information. Then, the travel schedule management server 600 transmits the generated travel information to the portable terminal 500 via the Internet 1000 for presentation to the traveler (step S311).

  Next, the operation of this embodiment will be described using specific examples. In this example, a case where the member registration information shown in FIG. 11B is registered for the user will be described. The user is given a member ID “0001” at the time of member registration, and is stored in the member information list storage unit 611 of the travel schedule management server 600 as member registration information. The traveler operates the portable terminal 500 to input the member number “0001” and the password to acquire information on the travel product, select the travel product, and make a reservation.

  A reservation request is transmitted from the travel schedule management server 600 to each of the servers 100, 700, 800, 900, and each server is based on parameters (transportation ID, hotel ID, taxi company ID, store ID, etc.) included in the travel product. Each reservation information is generated and stored as XML data by 100, 700, 800, 900.

  FIG. 14 is an explanatory diagram showing an example of the contents of each reservation information generated as XML data. FIG. 14B is an example of the contents of the accommodation reservation information generated as XML data and stored in the reservation ID list storage unit 807 of the hotel server 800. FIG. 14C is an example of the contents of taxi reservation information generated as XML data and stored in the reservation ID list storage unit 907 of the taxi company server 900. FIG. 14D is an example of the content of the product reservation information generated as XML data and stored in the reservation ID list storage unit 707 of the store server 700. FIG. 14E is an example of the contents of reserved seat reservation information generated as XML data and stored in the reserved seat list storage unit 103 of the vacant seat management server 100.

  FIG. 14A is an example of the contents of the integrated reservation information generated as XML data based on each reservation information and stored in the integrated reservation ID list storage unit 610 of the travel schedule management server 600. As shown in FIG. 14A, the integrated reservation information includes accommodation reservation ID “22104” in the accommodation reservation information, taxi reservation ID “3150” in the taxi reservation information, product reservation ID “4203” in the product reservation information, and the designated seat. The reserved seat reservation ID “10001” of the reservation information is included.

  When the traveler inputs a travel information request instruction to confirm the reservation details, the mobile terminal 500 transmits a travel information request to the travel schedule management server 600. The travel schedule management server 600 transmits each reservation ID via the Internet 1000 to the servers 700, 800, 900 and the vacant seat management server 100 of each local service company. The travel schedule management server 600 receives reservation content information from the servers 700, 800, 900 and vacant seat management server 100 of each local service company via the Internet 1000.

  Furthermore, the travel schedule management server 600 manages the request of departure / arrival time, boarding station, etc. via the Internet 1000 together with the information of the route ID “295” and the train ID “5033B” included in the reserved seat reservation information. Send to server 400. The travel schedule management server 600 receives information such as departure / arrival times and boarding stations from the operation management server 400 via the Internet 1000.

  FIG. 15A is an explanatory diagram showing an example of the contents of information such as departure / arrival times and boarding stations received as XML data from the operation management server 400. As shown in FIG. 15A, the XML data received from the operation management server 400 includes information on route names, train names, delay reasons, affected sections, delay times, departure / arrival stations, and departure / arrival times.

  When the portable terminal 500 is an HTML compatible terminal, the travel schedule management server 600 converts the XML data received from the operation management server 400 into HTML (Hyper Text Markup Language) data. Then, the travel schedule management server 600 transmits the converted HTML data to the traveler's portable terminal 500 via the Internet 1000. The portable terminal 500 displays information based on the received HTML data. The travel schedule management server 600 is not limited to HTML data, but may convert XML data into WML (Wireless Markup Language) data for transmission to a mobile terminal compatible with WAP (Wireless Application Protocol), for example.

  FIG. 15B is an explanatory diagram illustrating an example of a display screen of information displayed on the mobile terminal 500 based on HTML data. If there is a delay before departure, the traveler, as shown in FIG. 15 (b), the delay route 1501, the reason for delay 1502, the affected section 1503, the delay time 1504, the scheduled train name 1505, the boarding station 1506, a message screen including a departure time 1507 including a delay can be viewed.

  Further, the message content displayed on the portable terminal 500 differs depending on the operation information and the inquiry time. FIG. 16 is an explanatory diagram illustrating an example of each message screen displayed on the mobile terminal 500. FIG. 16A shows a message screen that is displayed while the user is on a train or the like. The message screen displays the next stop station, stop platform, and stop time. FIG. 16B is a message screen that is displayed after the train gets off when a taxi reservation is made. The message screen displays the taxi stand, the vehicle number of the taxi scheduled to be boarded, and the name of the crew member. FIG. 16C shows a message screen displayed during the travel period. The message screen displays a meal time and a room number. FIG. 16D is a message screen that is displayed outside the travel period in which no reservation is made, and an advertisement for a travel agency is displayed on the message screen.

  As described above, according to the present embodiment, the traveler can confirm the travel information of the reserved travel product. In addition, the traveler can acquire the latest travel information according to the travel process, and can receive a travel navigation service during the trip.

Embodiment 4 FIG.
Next, a fourth embodiment of the present invention will be described with reference to the drawings. The configuration of the travel plan management system is the same as that in the second and third embodiments. In the present embodiment, a case will be described in which a travel product ID is given to each travel product handled by the travel agency, and the user designates the travel product ID and reserves the travel product.

  In order to reserve a travel product, the user operates the mobile terminal 500 to input parameters for travel duration, number of people, member ID, and travel product ID. Then, the mobile terminal 500 transmits the input parameters to the travel schedule management server 600 via the Internet 1000.

  The travel management device 606 of the travel schedule management server 600 extracts travel product information from the travel route list storage unit 612 based on the travel product ID. The travel management device 606 extracts reservation parameters (reservation IDs) for transportation and local service companies from the travel product information. The affiliated company management device 603 of the travel schedule management server 600 has the servers 700, 800, 900, the vacant seat management server 100 and the operations of the local service company that is the communication destination from the local company list storage device 608 and the transportation list storage device 609. ID information of the management server 400 is extracted.

  If the travel product includes a souvenir purchase reservation, the travel schedule management server 600 transmits a reservation request as XML data to the store server 700 via the Internet 1000. When the XML data is received, the XML processing device 701 of the store server 700 expands the received XML data and extracts a processing name and parameters. The instruction processing device 702 of the store server 700 causes the inventory management device 705 to execute inventory status confirmation processing based on the processing name and parameters. If there is a stock, the reservation management apparatus 704 issues a product reservation ID and generates product reservation information. Then, the store server 700 uses the functions of the instruction processing device 702 and the XML processing device 701 to transmit the product reservation information as XML data to the travel schedule management server 600 via the Internet 1000.

  If the travel product includes an accommodation reservation, the travel schedule management server 600 transmits a reservation request as XML data to the hotel server 800 via the Internet 1000. When the XML data is received, the XML processing device 801 of the hotel server 800 expands the received XML data and extracts a processing name and parameters. The instruction processing device 802 of the hotel server 800 causes the reservation management device 804 to execute a confirmation process as to whether or not a reservation having a room and a period overlapping is included based on the processing name and parameters. If it is determined that the room can be secured, the reservation management apparatus 804 issues an accommodation reservation ID and generates accommodation reservation information. Then, the hotel server 800 uses the functions of the instruction processing device 802 and the XML processing device 801 to transmit accommodation reservation information as XML data to the travel schedule management server 600 via the Internet 1000.

  If the travel product includes a taxi reservation, the travel schedule management server 600 transmits a reservation request as XML data to the taxi company server 900 via the Internet 1000. When the XML data is received, the XML processing device 901 of the taxi company server 900 expands the received XML data and extracts a processing name and parameters. The instruction processing device 902 of the taxi company server 900 causes the unoccupied vehicle management device 905 to execute a dispatch arrangement process based on the processing name and parameters. If a taxi can be secured, the reservation management device 904 of the taxi company server 900 issues a taxi reservation ID and generates taxi reservation information. Then, the taxi company server 900 transmits the taxi reservation information as XML data to the travel schedule management server 600 via the Internet 1000 using the functions of the instruction processing device 902 and the XML processing device 901.

  When there is no stock or a hotel or taxi cannot be secured, the travel schedule management server 600 transmits a reservation request to servers 700, 800, 900 of other stores, hotels, or taxi companies. If any reservation of a store, hotel or taxi company cannot be secured in the vicinity of the destination, the travel schedule management server 600 sends information indicating that the travel product cannot be reserved to the mobile terminal via the Internet 1000. Sent to 500.

  In addition, when the transportation schedule is delayed and different from the schedule, the travel schedule management server 600 is linked to the operation management server 400, and in accordance with the procedure of FIG. The latest arrival time information is distributed via the Internet 1000.

  If the transportation schedule is different from the schedule, and if the integrated reservation information includes a store ID and a product reservation ID, the travel schedule management server 600 makes a product reservation to the store server 700 via the Internet 1000. A product receipt time change request is transmitted as XML data together with the ID. When the change request is received, the XML processing device 701 of the store server 700 expands the received XML data and extracts a processing name and parameters. The instruction processing device 702 of the store server 700 causes the reservation management device 704 to execute a delivery time change process corresponding to the received product reservation ID based on the processing name and parameters.

  For example, when the delivery time requested to be changed is within the business hours of the store, the reservation management device 704 changes the reception time corresponding to the product reservation ID. If the change can be made, the XML processing device 701 generates XML data including a character string “true” indicating completion of the change. Then, the shop server 700 transmits the generated XML data to the travel schedule management server 600 via the Internet 1000.

  If the integrated reservation information includes the hotel ID and the accommodation reservation ID, the travel schedule management server 600 sends an arrival time change request together with the accommodation reservation ID to the hotel server 800 via the Internet 1000. Send as data. When the change request is received, the XML processing device 801 of the hotel server 800 expands the received XML data and extracts a processing name and parameters. The instruction processing device 802 of the hotel server 800 causes the reservation management device 804 to execute an arrival time change process corresponding to the received accommodation reservation ID based on the processing name and parameters.

  The reservation management device 804 changes the arrival time corresponding to the accommodation reservation ID. When the arrival time is changed, for example, if the changed arrival time is included in the dinner service period, the hotel's kitchen or an outside meal service company is notified of the changed arrival time. The For example, when the changed arrival time is included in the pick-up time zone, the changed arrival time of the guest is notified to the driver of the hotel pick-up car. If the change can be made, the XML processing device 701 generates XML data including a character string “true” indicating completion of the change. Then, the hotel server 800 transmits the generated XML data to the travel schedule management server 600 via the Internet 1000.

  When the integrated reservation information includes the taxi company ID and the taxi reservation ID, the travel schedule management server 600 requests the taxi company server 900 to change the arrival time together with the taxi reservation ID via the Internet 1000. Is transmitted as XML data. When the change request is received, the XML processing device 901 of the taxi company server 900 expands the received XML data and extracts a processing name and parameters. The instruction processing device 902 of the taxi company server 900 causes the reservation management device 904 to execute a scheduled departure time change process corresponding to the received taxi reservation ID based on the processing name and parameters.

  The reservation management device 904 changes the scheduled departure time corresponding to the taxi reservation ID. If the change can be made, the XML processing apparatus 901 generates XML data including the character string “true” indicating the completion of the change. Then, the taxi company server 900 transmits the generated XML data to the travel schedule management server 600 via the Internet 1000.

  As described above, according to the present embodiment, the latest arrival time is automatically distributed from the travel schedule management server 600 to each server of the local service company when a delay occurs in the transportation schedule. Is done. For this reason, local service companies need to know which train a traveler will arrive on, and prepare meals and pick-ups according to the changed time without estimating the arrival time using the timetable and operation information. be able to. Therefore, even when a delay or the like occurs in the transportation schedule, the local service company can provide the traveler with a service according to the arrival time.

Embodiment 5 FIG.
Next, a fifth embodiment of the present invention will be described with reference to the drawings. The configuration of the travel plan management system is the same as in the second, third, and fourth embodiments. As shown in FIG. 4, since the operation management server 400 includes the protocol conversion device 300, XML data can be transmitted to and received from the travel schedule management server 600 via the Internet 1000. When the travel schedule management server 600 receives the request data from the portable terminal 500, it extracts the member registration information based on the request data, and extracts the integrated reservation ID from the member registration information.

  The travel schedule management server 600 extracts the reserved seat reservation (outbound / return) ID from the integrated reservation information based on the integrated reservation ID. In addition, the travel schedule management server 600 determines whether the inquiry request from the mobile terminal 500 is for the forward trip or the return trip based on the current time. The travel schedule management server 600 extracts the route ID and the train ID based on the reserved seat reservation ID for the outbound or inbound trip. Then, the travel schedule management server 600 transmits an inquiry request for the current operation status together with the route ID and the train ID to the operation management server 400 via the Internet 1000.

  Upon receiving the operation status inquiry request, the command processing device 302 transfers the train ID to the delay time management device 402 and requests a delay time. If the delay time from the delay time management device 402 is equal to or greater than a predetermined threshold, the command processing device 302 determines that a delay has occurred in the train operation schedule. Then, the instruction processing device 302 transfers the route ID to the delay reason management device 401 and requests information on the reason for delay and the affected section. The instruction processing device 302 converts the route ID and the train ID into the route name and the train name based on the information stored in the route / train name accumulation unit 305.

  The XML processing apparatus 301 generates a route name and a train name as XML data together with delay information (delay time, delay reason, affected section, etc.). Then, the operation management server 400 transmits the generated XML data to the travel schedule management server 600 via the Internet 1000. As described above, the travel management device 606 of the travel schedule management server 600 converts the received XML data including the delay information into HTML data for distribution to the mobile terminal 500.

  The travel schedule management server 600 transmits the converted HTML data to the portable terminal 500 via the Internet 1000. Then, the mobile terminal 500 displays delay information and the like based on the received HTML data. For example, as shown in FIG. 15B, the mobile terminal 500 includes a route name 1501, a delay reason 1502, an affected section 1503, a delay time 1504, a train name 1505, a passenger boarding station 1506, and a train at the boarding station. The information of the departure time 1507 is displayed in combination.

  As described above, according to the present embodiment, an operation management system including the delay reason apparatuses and the delay time distribution apparatuses arranged in a distributed manner is configured, and the reservation management apparatus 606 of the travel schedule management server 600 is a traffic Information can be collected in conjunction with the institution's operation management system. Therefore, the traveler can display, browse and check information such as transportation necessary for him / her in conjunction with the current operation status.

Embodiment 6 FIG.
Next, a sixth embodiment of the present invention will be described with reference to the drawings. The configuration of the travel plan management system is the same as that of the second, third, fourth and fifth embodiments. The configuration of the vacant seat management server 100 is the same as the configuration shown in FIG. 2, and the vacant seat management server 100 has functions of vacant seat inquiry, reserved seat reservation, reserved seat cancellation, and specified seat change.

  The XML processing apparatus 201 receives XML-format request data from the travel schedule management server 600 via the Internet 1000 and stores log information of received contents in the access log storage unit 204. The usage record distribution device 203 generates history result information for each request source after a predetermined period has elapsed. Then, the usage record distribution device 203 distributes the generated history result information to the requesting travel schedule management server 600 via the Internet 1000.

  FIG. 17 is an explanatory diagram illustrating an example of the contents of history result information. FIG. 17A is an explanatory diagram illustrating an example of the contents of history result information generated by the usage record distribution device 203. As shown in FIG. 17A, the history result information includes information such as a request source address, a source address, a date when a request is made, a command, and a parameter.

  Similar to the vacant seat management server 100, the operation management server 400 accumulates log information of the request history from the request source. Further, as shown in FIG. 3, the operation management server 400 includes a partner list storage unit 306 that registers ID information of a travel schedule management server 600 of a partner travel agency. When the operation management server 400 spontaneously distributes the delay information, the operation route management server 400 sends the delay route ID and the delay train ID to the travel schedule management server 600 registered in the tie-up list 306 via the Internet 1000. To deliver. When detailed delay information is requested from the delivery destination travel schedule management server 600 and the delay information is transmitted, the operation management server 400 adds the log information of the transmission history to the access log storage unit 304 and stores it.

  The travel schedule management server 600 is a request source for the operation management server 400 and the vacant seat management server 100. When an information request is transmitted to the outside such as the operation management server 400 or the vacant seat management server 100, the usage record recording device 602 of the travel schedule management server 600 stores the log information of the request history in the access log storage unit 607.

  When the usage record inspection device 601 receives history result information from an external server such as the operation management server 400 or the vacant seat management server 100, does the received history result information match the log information of the internal history stored in the access log storage unit 607? Judge whether or not. When it is determined that the history contents match, the usage record inspection device 601 generates record acceptance information indicating that the history contents included in the received record result information are accepted. Then, the usage record inspection device 601 transmits the generated record acceptance information to the operation management server 400 or the vacant seat management server 100 via the Internet 1000.

  If it is determined that the history contents do not match, the usage record checking apparatus 601 generates error information indicating that the history contents do not match and difference information obtained by extracting the mismatched portions of the history contents. Then, the usage record inspection apparatus 601 transmits the difference information together with the error information to the operation management server 400 or the vacant seat management server 100 via the Internet 1000.

  For example, when processing is executed based on a request message transmitted by a third party server other than the partner as a travel schedule management server 600, the history contents do not match. In this case, the usage record inspection device 601 generates a difference in history contents as difference information. The difference information is used for, for example, system failure analysis processing by impersonation processing or the like.

  In addition, when the reservation management device 604 extracts an affected travel reservation based on the delay information received from the transportation operation management server 400, the affiliated company management device 603 is affected by the delay of the transportation facility. ID information of the local service company server is extracted. Then, the travel schedule management server 600 transmits delay information etc. via the Internet 1000 to each server 700, 800, 900 of the local service company based on the extracted ID information. In this case, the usage record recording device 602 stores the log information of the transmission contents in the access log accumulation unit 607.

  Store server 700 stores log information of the contents of distribution in access log storage section 706 when the received time change information is distributed from travel schedule management server 600. After the predetermined period has elapsed, the store server 700 transmits history result information to the travel schedule management server 600 via the Internet 1000 based on the log information stored in the access log storage unit 706. Then, the usage record inspection device 601 of the travel schedule management server 600 extracts the information of the transmission history to the store server 700 from the access log storage unit 607 and matches the reception history of the store server 700 included in the received history result information. Judge whether to do or not.

  If it is determined that the matching results of the histories match, the travel schedule management server 600 transmits the result acceptance information to the store server 700 via the Internet 1000. Further, when it is determined that the collation results do not match, the travel schedule management server 600 transmits the difference information together with the error information to the store server 700 via the Internet 1000.

  When the arrival time change information is distributed from the travel schedule management server 600, the hotel server 800 stores the log information of the distribution contents in the access log storage unit 806. After the predetermined period has elapsed, the hotel server 800 transmits history result information to the travel schedule management server 600 via the Internet 1000 based on the log information stored in the access log storage unit 806. Then, the usage record inspection device 601 of the travel schedule management server 600 extracts the information of the transmission history to the hotel server 800 from the access log storage unit 607 and matches the reception history of the hotel server 800 included in the received history result information. Judge whether to do or not.

  When it is determined that the history comparison results match, the travel schedule management server 600 transmits the result acceptance information to the hotel server 800 via the Internet 1000. Further, when it is determined that the collation results do not match, the travel schedule management server 600 transmits the difference information together with the error information to the store server 700 via the Internet 1000.

  When the change information of the scheduled departure time is distributed from the travel schedule management server 600, the taxi company server 900 stores the log information of the distribution contents in the access log accumulation unit 906. After a predetermined period, the taxi company server 900 transmits history result information to the travel schedule management server 600 via the Internet 1000 based on the log information stored in the access log storage unit 906. Then, the usage record inspection device 601 of the travel schedule management server 600 extracts information on the transmission history to the taxi company server from the access log storage unit 607, and receives the reception history of the taxi company server 900 included in the received history result information. Judgment is made by checking whether they match.

  When it is determined that the history comparison results match, the travel schedule management server 600 transmits the result acceptance information to the taxi company server 900 via the Internet 1000. In addition, when it is determined that the collation results do not match, the travel schedule management server 600 transmits the difference information together with the error information to the taxi company server 900 via the Internet 1000.

  Next, the operation of this embodiment will be described using specific examples. FIG. 17B is an example of the contents of the history information extracted based on the log information accumulated in the transportation management server 400 “abc-train” in accordance with the data format of FIG. The history information shown in FIG. 17B is obtained by extracting the history for the date “2003/3/31” in response to a request from the travel schedule management server 600 “ebc-travel”.

  FIG. 17C is an example of the contents of the history information extracted based on the log information stored in the travel schedule management server 600 “ebc-travel” in accordance with the data format of FIG. The history information shown in FIG. 17C is extracted from the history for the date “2003/3/31” requested to the operation management server 400 “abc-train”.

  The usage record inspection apparatus 601 compares the <requestor> tag shown in FIG. 17B with the <sender> tag shown in FIG. 17C, and determines whether the request source and the request destination match. judge. In addition, the usage record inspection apparatus 601 compares the <sender> tag shown in FIG. 17B with the <destination> tag shown in FIG. 17C, and determines whether the request source and the request destination match. Determine whether.

  If it is determined that the request source and the request destination match, the usage record checking device 601 determines whether the contents of the <item> tag included in the history information shown in FIGS. 17B and 17C match. Judge whether or not. In this example, since the request source and the request destination match with “ebc-travel” and “abc-train”, the usage record inspection device 601 determines whether the contents of the <item> tag match.

  The usage record checking device 601 checks the contents of the <order> tag and the <param> tag in the <item> tag and determines whether or not the requested contents match. If it is determined that they match, the usage record checking device 601 checks the <date> tag, and the difference in the item occurrence time between the history information shown in FIG. 17B and the history information shown in FIG. Is within a predetermined threshold. When the difference in occurrence time is within a predetermined threshold, the usage record inspection device 601 determines that the occurrence times also match and determines that the contents of the items match.

  If it is determined that the contents of the items match, the usage record inspection device 601 determines whether the requested contents of the next <item> tag match. Then, the usage record inspection device 601 repeatedly executes the same determination process for all <item> tags included in the history information of FIGS. 17B and 17C.

  As described above, according to the present embodiment, the history information when the transportation operation information is used is held by the user side server and the provider side server. Then, the travel schedule management server 600 can collate the usage record based on the history information. Therefore, for example, a travel agent, a transportation facility, and a local service company can exchange usage charges according to the usage record. Therefore, the transportation facility can collect the information provision fee of the operation information according to the usage record.

  Moreover, since the users of the operation information are hierarchical, it is possible to pay an information provision fee for the operation information for each layer. For example, when the travel agency that manages the travel schedule management server 600 is a primary user and the local service company that manages the store / hotel / taxi company server is a secondary user, the secondary user Pays the information service fee for the operation information to the primary user. Further, the primary user deducts a predetermined fee and pays the information provision fee for the operation information to the transportation facility.

  In the travel plan management system according to the present invention, the operation information indicating the operation status of the transportation facility is transmitted as XML data to the server of the travel agent via the Internet, and the travel agent acquires the transportation operation information in real time. Can do. Therefore, the travel agent can manage the travel plan of the traveler linked with the operation status of the transportation facility.

It is a block diagram which shows an example of a structure of the travel plan management system by this invention. 3 is a block diagram illustrating an example of a configuration of a vacant seat management server 100. FIG. It is a block diagram which shows an example of a structure of the operation management server. It is a block diagram which shows the other example of a structure of the travel plan management system by this invention. It is a block diagram which shows an example of a structure of the shop server. It is a block diagram which shows an example of a structure of the hotel server. It is a block diagram which shows an example of a structure of the taxi company server. It is a block diagram which shows an example of a structure of the travel schedule management server. It is explanatory drawing which shows the example of the list information of each reservation content. It is a flowchart which shows an example of the operation information notification process which the travel schedule management server 600 notifies operation information to the portable terminal 500 or each server 700,800,900. It is explanatory drawing which shows the example of the content of member information. It is a flowchart which shows an example of the confirmation information delivery process of the reservation content of travel goods. It is a flowchart which shows an example of the delivery process of the travel information according to a traveler's process. It is explanatory drawing which shows the example of the content of each reservation information produced | generated as XML data. It is explanatory drawing which shows the example of the content of information, such as departure / arrival time and a boarding station. It is explanatory drawing which shows the example of each message screen displayed on the portable terminal. It is explanatory drawing which shows the example of the content of log | history result information.

Explanation of symbols

100 Vacant Seat Management Server 101 Reservation Management Device 102 Vacant Seat Management Device 103 Reserved Seat List Storage Unit 104 Vacant Seat List Storage Unit 200 Protocol Conversion Device 201 XML Processing Device 202 Command Processing Device 203 Usage Result Distribution Device 204 Access Log Storage Unit 205 Route / Train Name Storage unit 300 Protocol conversion device 301 XML processing device 302 Command processing device 303 Usage result distribution device 304 Access log storage unit 305 Route / train name storage unit 306 Partner list storage unit 400 Operation management server 401 Delay reason management device 402 Delay time management Device 403 Passing time measuring device 404 Delay reason storage unit 405 Delay time storage unit 600 Travel schedule management server 1000 Internet

Claims (9)

A travel plan management system comprising an operation management server operated by a transportation means that operates a means of transportation, and an agent server operated by a travel agency,
The operation management server is
Operation information storage means for storing operation information indicating the operation status of the transportation facility;
Operation status XML data generating means for extracting operation information from the operation information storage means and generating operation status XML data that is XML data including the extracted operation information;
Operation status XML data transmitting means for transmitting the operation status XML data to the agency server via the Internet,
The agency server manages a travel plan of a traveler based on the operation status XML data. Seat reservation information storage means for storing seat reservation information indicating the seat reservation status of the means of transportation;
Seat reservation XML data generating means for extracting seat reservation information from the seat reservation information storage means and generating seat reservation XML data that is XML data including the extracted seat reservation information;
A seat reservation server including seat reservation XML data transmission means for transmitting the seat reservation XML data to an agent server via the Internet;
The travel plan management system according to claim 1, wherein the agency server manages a travel plan of a traveler based on the seat reservation XML data. The agency server
A delay occurrence determination means for determining whether or not there is a delay in the transportation means on which the traveler gets based on the operation status XML data;
Delay information transmitting means for transmitting delay information indicating a delay status of the transportation means to a mobile terminal used by the traveler via the Internet when it is determined that a delay has occurred in the transportation means; The travel plan management system according to claim 1 or 2. The agency server
A traveler who determines whether the traveler is in a state before, during or after boarding the vehicle based on information on the operation date and time and current time information of the vehicle included in the operation status XML data. Including situation determination means,
The travel plan management system according to claim 3, wherein the delay information transmitting means transmits delay information corresponding to a traveler's situation to the mobile terminal via the Internet. A service provider server operated by a travel destination service provider affiliated with a travel agency,
The service provider server includes service reservation information management means for managing service reservation information indicating a reservation status of service provision to a traveler,
When the agency server determines that there is a delay in the means of transportation on which the traveler gets based on the operation status XML data, the agency server transmits service provision change information to the service provider server via the Internet. The travel plan management system according to any one of claims 1 to 4, further comprising change information transmission means for performing the operation. 6. The service reservation information management means according to any one of claims 1 to 5, wherein the service reservation information manages a hotel reservation status, a delivery vehicle reservation status, or a product purchase reservation information. Travel plan management system. The agency server
History information storage means for storing transmission history information of transmission data transmitted to the operation management server, seat reservation server or service provider server;
Receive history information of data received from the agency server by the operation management server, the seat reservation server or the service provider server from the operation management server, the seat reservation server or the service provider server via the Internet. Receiving history information means;
The travel plan management system according to claim 5 or 6, further comprising: history determination means for determining whether or not the received history information received and the transmission history information stored in the history information storage means match. . A step in which an operation management server operated by a transportation means that operates means of transportation extracts operation information indicating the operation state of the transportation means, and generates operation state XML data that is XML data including the extracted operation information;
The operation management server transmitting the operation status XML data to an agency server operated by a travel agency via the Internet;
The agency server includes a step of managing a travel plan of a traveler based on the operation status XML data. An operation information management program for managing operation information indicating the operation status of transportation facilities, which is used by an agent server operated by a travel agent to manage a traveler's travel plan,
On the computer,
A process of extracting the operation information and generating operation state XML data which is XML data including the extracted operation information;
The operation information management program which performs the process which transmits the said operation condition XML data to the said agency server via the internet.

Images