JP2002215945A - Reservation management method, reservation management program, and storage medium recording reservation management program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To allow a reservation applicant to easily find an accepter most suitable for his desire among a plurality of accepters. SOLUTION: When a reservation management server receives application desired conditions from the reservation applicant, it receives retrieval conditions for retrieving the application desired conditions from the reservation accepters, performs retrievals, and transmits retrieval results to an accepter. The server receives acceptance conditions from the accepter, and it receives a transmission request of the acceptance conditions from the reservation applicant and transmits the acceptance conditions to the applicant. The server receives reservation contents from the applicant, receives a transmission request of the reservation contents from the accepter, transmits the reservation contents to the accepter, and receives the final reservation contents from the accepter.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a method and a program for managing the application and acceptance of a reservation, and a recording medium on which such a program is recorded. About technology.

[0002]

2. Description of the Related Art The Internet has a very large number of computers connected via communication lines. The interconnected computers are the World Wide Web (WWW: W
Information can be transmitted and received using various services such as the Old Wide Web and e-mail. When the WWW service is used, the client system can receive text data and image data stored in a remote server system via a communication line. The client system can display the received web page.

Each web page has a URL (Uniform Resour)
ce Locator). To display a web page, the client system must use the Hyper Text Transfer Protocol (HTTP).
r Protocol), the UR of the web page you want to display
Specify L and request transmission of the page. This request is sent to the server system. Upon receiving the request, the server system sends the requested web page to the client system. Upon receiving the requested web page, the client system displays the web page on a display using a browser. Web pages are written in a hypertext markup language (HTML: Hyper Text M
arkup Language).

[0004] The World Wide Web is used for booking and acceptance. 2. Description of the Related Art Conventionally, a party accepting a reservation for a golf course or the like creates a web page and publishes it on the Internet. The applicant can browse the web pages of a plurality of acceptors, confirm the acceptance conditions, and apply.

[0005]

However, in the above-mentioned conventional method, the applicant can select his / her desired (location, price) from a plurality of service providers (for example, golf courses) that provide similar services. In order to find a suitable service provider, there is a case where a plurality of web pages must be browsed and compared, and there is a problem that it is complicated.

SUMMARY OF THE INVENTION The present invention has been made in view of the above points, and allows an applicant to apply for a reservation with a service provider such as a golf course that satisfies a request without browsing a plurality of web pages. It is an object of the present invention to provide a reservation management method capable of establishing acceptance, a reservation management program used for the method, and a recording medium recording such a reservation management program.

[0007]

SUMMARY OF THE INVENTION In order to solve the above-mentioned problems, the features of the reservation management method of the present invention include: a communication unit capable of transmitting and receiving data through a communication line; a storage unit capable of storing received data; A reservation management method using a control unit capable of retrieving data in the unit, wherein (1) the communication unit receives an application request condition from an applicant who applies for a reservation, and (2) the storage unit A storage step of storing the application desired condition; and (3) a receiving step of the communication unit receiving a search condition for searching for the application desired condition from an acceptor accepting a reservation;
(4) a search step in which the control unit searches for the desired application condition that satisfies the search condition; (5) a transmission step in which the communication unit transmits the search result to the acceptor; (6) A receiving step in which the communication unit receives an acceptance condition from the acceptor; (7) a storage step in which the storage unit stores the acceptance condition;
(8) a receiving step in which the communication unit receives a transmission request for the acceptance condition from the reservation applicant; (9)
A transmitting step in which the communication unit transmits the acceptance condition to the applicant; (10) a receiving step in which the communication unit receives reservation contents from the applicant;
(1) a storage step in which the storage unit stores the reservation content; (12) a reception step in which the communication unit receives a transmission request for the reservation content from the acceptor;
3) The communication unit includes a transmitting step of transmitting the reservation content to the acceptor, and (14) a receiving step of the communication unit receiving final reservation content from the acceptor.

[0008] A random access memory (R
AM) and magnetic storage means such as a hard disk drive (HDD).

The communication section includes a modem, a terminal adapter, a router, and the like.

[0010] The control unit controls the storage unit and the communication unit. For example, (1) a process in which the communication unit receives data, (2) a process of writing the received data to the storage unit, (3) a process of searching the written data for data that satisfies a search condition, (4) ) Control processing for transmitting the search result from the communication unit.

The “application request condition” includes a fee to be paid for the service, a date and time at which the service is to be provided, the number of people who want to receive the service, and a place at which the service is to be provided.

The "acceptance conditions" may be the same as or different from the desired application conditions. For example, if the receiving side (the person who provides the service) can satisfy all the wishes of the applicant (the person who receives the provision of the service), the application request condition and the acceptance condition are the same. If the accepting party is unable to meet some of the applicant's wishes, the modified part becomes the acceptance condition.

[0013] For one application request condition, 1 or 2
The accepting condition is returned from the accepting side.

The "reservation content" refers to only one acceptance condition selected from one or more acceptance conditions.

[0015] "Last reservation contents" means "reservation contents" plus "final decision items". "Final decision item" means an item that is finally decided by the receiving party.

[0016] The reservation applicant can receive the "acceptance conditions" from a plurality of acceptors only by registering the "application desired conditions" once in the reservation management server.

Furthermore, when searching for "application desired conditions", the acceptor can approach many applicants by appropriately changing the search conditions.

[0018]

Embodiments of the present invention will be described below with reference to the drawings.

FIG. 1 is a schematic diagram showing a system configuration according to an embodiment of the present invention. In the present embodiment, a case where a visitor (reservation applicant) reserves a golf course will be described as an example. However, the present invention is not limited in application to golf course reservations.

As shown in FIG. 1, a visitor (applicant) terminal 10, a golf course (acceptor) terminal 20, and a reservation management server 30 are connected to a network 8 such as the Internet.
, Data can be mutually transmitted and received.

The visitor terminal 10 includes an input unit 11, a display unit 12, a communication unit 13, a control unit 14, and a storage unit 15.

The golf course terminal 20 includes an input unit 21, a display unit 22, a communication unit 23, a control unit 24, and a storage unit 25.

The reservation management server 30 includes an input unit 31, a display unit 32, a communication unit 33, a control unit 34, and a storage unit 35.
And The storage unit 35 stores the visitor information file 3
51, a visitor reservation log file 352, a golf course reservation log file 353, and a golf course information file 35.
4, an area information file 355, and a prefecture information file 356 are stored.

FIG. 2 is a schematic diagram showing files stored in the storage unit of the reservation management server 3 shown in FIG.

The visitor information file 351 includes, as data items, a visitor ID, a login ID, a password,
It has a prefecture code, an e-mail address, and other accompanying information.

The visitor reservation log file 352 includes, as data items, a reservation number, a visitor ID, and a golf course I.
D, inquiry time, desired area, desired date, desired number of people,
It has a desired amount, other desired conditions, a reservation access time, a reception time zone (start time), a data reception flag, and a status.

The golf course reservation log file 353 includes a reservation number, a golf course ID, and a visitor I as data items.
D, reply access time, underwriting amount, start time,
Desired area code, desired date, desired number of people, other underwriting conditions,
It has reservation reception time, reception time zone, history, and status.

The golf course information file 354 has, as data items, a golf course ID, a password, a prefecture code, an area code, and other accompanying information.

The area information file 355 has, as data items, an area code, an area name, an area code, and an area name.

The prefectural information file 356 includes, as data items, a prefectural code, a prefectural name, an area code,
Have a region name.

FIG. 3 is a flowchart showing the flow of a reservation process according to the embodiment of the present invention. As shown in FIG. 3, from the visitor terminal, the desired play conditions (application desired conditions)
Is transmitted to the reservation management server (S101), and the reservation management server registers the desired play condition in the storage unit (S102),
The registered desired play conditions are referred to from a plurality of golf course terminals (S103).

Each golf course terminal returns an acceptance condition for a visitor to be obtained (S104), the reservation management server stores the acceptance condition from the golf course in a storage unit (S105), and the visitor terminal returns a response from the golf course. Is received (S106), the conditions for acceptance from the golf course are checked, and comparison is made (S1).
07).

Then, the visitor terminal determines the golf course to which the reservation is to be made and transmits the contents of the reservation to the reservation management server (S10).
8), the reservation management server stores the contents of the reservation from the visitor in the storage unit (S109), and the golf course terminal confirms the contents of the reservation, sets a start time, and replies (S1).
10).

Further, the reservation management server stores the contents of the reply from the golf course terminal in the storage unit and completes the reservation (S
111). The visitor confirms the reservation contents such as the start time by looking at the reservation confirmation list (S112). The contents of each step will be described below.

FIG. 4 is an example of a “user registration” screen displayed on the display unit of the visitor terminal.

Visitors need to perform user registration in advance. For this purpose, the visitor terminal 10 requests the reservation management server 30 to transmit an HTML file constituting the “user registration” screen. The reservation management server 30 is an HTM that configures a “user registration” screen on the visitor terminal 10.
Send the L file. HTML that the visitor terminal 10 configures the “user registration” screen from the reservation management server 30
Receive files. The "user registration" screen is displayed on the display unit 1 of the visitor terminal 10 by the browser of the visitor terminal 10.
2 is displayed.

The input items on the “user registration” screen are
Email address, name, password, zip code, address,
Home phone number, date of birth, gender, and card used for payment.

The data of each registered item is recorded in the visitor information file 351. Home phone number is visitor ID
Becomes

FIG. 5 shows an example of a "play condition input" screen displayed on the display unit of the visitor terminal. This corresponds to step S101 in FIG.

The visitor terminal 10 is connected to the reservation management server 30
Requesting transmission of an HTML file constituting the "play condition input" screen. The reservation management server 30 sends the visitor terminal 10 an HTML file constituting an “play condition input” screen. The visitor terminal 10 receives, from the reservation management server 30, an HTML file constituting the “play condition input” screen. The "play condition input" screen is displayed on the display unit 1 of the visitor terminal 10 by the browser of the visitor terminal 10.
2 is displayed.

The input items on the "play condition input" screen are a desired area, a desired area, a play date, the number of people, a play fee, and a start time.

As a region, for example, Kanto, Kansai, Kinki, Tohoku, etc. are selected from a pull-down menu.

As the area, for example, the Hanshin Expressway, the Joban Expressway, the Tomei Expressway, the Chuo Expressway, the Tohoku Expressway, etc. are selected from the pull-down menu.

In the field of the play fee, the amount desired by the visitor is entered. As the start time, one of radio buttons such as “early”, “late”, and “unspecified” is selected.

If there is another request such as "Request with caddy", the desired content is entered in the comment column.

Clicking on a "Send" button 501
These data are transmitted to the reservation management server (FIG. 3, step S101).

FIG. 6 is a schematic diagram showing the contents of a visitor reservation log file when a visitor's desired play condition is received. The desired play condition issued by the visitor is stored in the visitor reservation log file. Step S in FIG.
102.

The communication section 33 of the reservation management server 30 receives the data via the Internet 8. The received data is stored in the storage unit 35 of the reservation management server 30.

The data of each column of the "play condition input" screen is stored in each field of the visitor reservation log file.

A reservation number is given to each reservation and stored in the "reservation number" field. The visitor's home telephone number is stored in the "Visitor ID" field as the visitor ID.

At this point, no data is stored in the "golf course ID" field. The date and time when the visitor transmitted the desired play condition is stored in the "inquiry time" field. The data in the “desired area: area” column is stored in the “desired area” field. The data in the “play date” column is stored in the “desired date” field. The data in the “desired date” field is used when the golf course searches for the reservation conditions.

The data in the "number of people" column is stored in the "number of desired people" field. The data in the "Play fee" column
It is stored in the "desired amount" field. At this point,
No data is stored in the "reserved access time" field. The data in the “start time” column is stored in the “reception time zone (start time)” field. "comment"
The column data is stored in the “other desired conditions” field of the visitor reservation log file. In the “data reception” field, data indicating “no response” is stored.
Data indicating “inquiry” is stored in the “status” field.

FIG. 7 is an example of a “play wish list” screen displayed on the display unit of the golf course terminal. This corresponds to step S103 in FIG.

The golf course terminal 20 is connected to the reservation management server 30
Requesting transmission of an HTML file that constitutes the “play wish list” screen. The reservation management server 30 configures the golf course terminal 20 with an HTM for configuring a “play wish list” screen.
Send the L file. HT that golf course terminal 20 configures “play wish list” screen from reservation management server 30
Receive the ML file. A “play wish list” screen is displayed on the display unit 22 of the golf course terminal 20 by the browser of the golf course terminal 20. (1) On the screen displayed first, the schedule satisfies all three conditions, that is, from the date of access to the end of the next fiscal year, (2) the total amount of money, and (3) the area to which the golf course receiving the HTML file belongs. The play wish list is displayed.

Various search wish lists can be displayed by appropriately changing the data in the columns of schedule, price, area, and area as search conditions. That is, the user inputs desired search conditions and clicks a “search start” button 70.
Click 1 to open the visitor reservation log file 352
Search starts.

Those that satisfy the search conditions are extracted, and the search result data constituting the “play wish list” section 702 of the “play wish list” screen is transferred to the golf course terminal 20. The browser of the golf course terminal 20 displays a “play wish list section” 702 on the display unit 22 of the golf course terminal 20.

The data of each item is extracted from the visitor reservation log file 352 and displayed.

"◎ (double circle)" in the column of start time
Indicates that the start time is not specified by the visitor.

The desired play conditions issued by the visitor can always be referred to until the reservation is established. However, those that have already returned the acceptance conditions from the golf course are invisible from the golf course. Specifically, when the acceptance condition is returned, the time at which the acceptance condition is returned is stored in the "reply access time" of the golf course reservation log file 353. The “reply access time” is compared with the current time. If the current time is within 48 hours from the “reply access time”, the record is not displayed.

After 48 hours have passed since the reservation conditions were stored in the reservation management server, the number of times the golf course has returned is displayed in the "history" field. When the acceptance condition is returned from the golf course, the value of the “history” field of the golf course reservation log file 353 is counted up one by one. When 48 hours have passed since the golf course returned and the message is displayed again, the value of the "history" field is displayed as "history". There may be a case where a reply is made a plurality of times from the same golf course to the same visitor. That is,
Two or more numerical values may be displayed as “history”.

When "Reply" 703 is clicked, a link destination "input section such as play fee" (801 in FIG. 8) is displayed.

FIG. 8 is an example of a “play wish list (input of play fee, etc.)” screen displayed on the display unit of the golf course terminal. This corresponds to step S104 in FIG.

The "play date", "number of people", "play fee" and "start time" input by the visitor are displayed (801 in FIG. 8).

The acceptor may rewrite the play fee. The acceptor may change the start time from “early” to “late” or from “late” to “early”.

A comment is written as needed in the “comment to customer” column 802. When the “send” button 803 is clicked, the data is transferred to the reservation management server 30. Clicking a “return” button 804 returns to the screen of FIG.

FIG. 9 is a schematic diagram showing the contents of a golf course reservation log file when the golf course reception conditions are received. The acceptance conditions issued from the golf course are stored in a golf course reservation log file. Step S10 in FIG.
Corresponding to 5.

The “reservation number” field and the “visitor I”
The contents of the visitor reservation log file are copied to the "D" field, the "desired area" field, the "desired date" field, and the "desired number of people" field.

The data received from the golf course terminal is stored as the underwriting condition amount and the reception time zone. When the acceptor rewrites the applicant's data, the rewritten data is stored.

In the "status" field, "reply"
Is stored. In the “reply access time” field, the date and time when the golf course responded to the reservation conditions from the visitor is stored. From this time, the acceptance condition for a predetermined time (for example, 48 hours) becomes effective. Increase the value of the "history" field by one.

When the reservation management server 30 stores the conditions for accepting from the golf course in the storage unit 35, an e-mail is sent to the visitor and it is notified that there is a reply from the golf course (step S106).

FIG. 10 is an example of a “accepted golf course list” screen displayed on the display unit of the visitor terminal. This corresponds to step S107 in FIG.

The visitor terminal 10 is connected to the reservation management server 30
Requesting transmission of an HTML file constituting the “reception golf course list” screen. The reservation management server 30 configures the visitor terminal 10 to configure the “accepted golf course list” screen H
Send the TML file. The visitor terminal 10 receives, from the reservation management server 30, an HTML file constituting the “accepted golf course list” screen. The “reception golf course list” screen is displayed on the visitor terminal 10 display unit 12 by the browser of the visitor terminal 10.

A list of acceptance conditions returned from the golf course is displayed. A list (1001) of replies to the desired play conditions issued by the visitor is displayed.

A plurality of acceptance conditions can be presented for one desired condition. However, reservations cannot be made for multiple golf courses.

The acceptance condition returned by the golf course is valid for 48 hours from the time of the reply. After 48 hours, it disappears from the list.

When the “application” button 1002 is clicked, the visitor terminal 10 receives the HTML file constituting the “reservation transmission confirmation” screen (FIG. 11) from the reservation management server 30. The “reservation transmission confirmation” (FIG. 11) screen is displayed on the display unit 12 of the visitor terminal 10 by the browser of the visitor terminal 10.

FIG. 11 is an example of a “reservation transmission confirmation” screen displayed on the display unit of the visitor terminal. This corresponds to step S108 in FIG.

After the visitor confirms the contents of the reservation, the "send"
When the button 1101 is clicked, the contents of the reservation are transmitted to the reservation management server 30.

FIG. 12 is a schematic diagram showing the contents of the visitor reservation log file when the reservation contents from the visitor are received. This corresponds to step S109 in FIG.

The communication section 33 of the reservation management server 30 receives the data via the Internet 8. The received data is stored in the visitor reservation log file 352.

In the “Golf course ID” field, the golf course I
D is stored. The “Status” field is changed from “Inquiry” to “Reserved”. The "data reception" field is changed from "no response" to "with response" when "the first response from the golf course" is received. When the first reply is received, the "data reception" field is changed from "no response" to "with a response" and an e-mail is sent (step S106). Even if a reply is received from the golf course, the e-mail is sent to the visitor. Is not transmitted.

FIG. 13 is an example of a “reservation list” screen displayed on the display unit of the golf course terminal. This corresponds to step S110 in FIG.

The golf course terminal 20 is connected to the reservation management server 30
Requesting transmission of an HTML file constituting the “reservation list” screen 1310. The reservation management server 30 configures a “reservation list” screen 1310 on the golf course terminal 20 as H
Send the TML file. The golf course terminal 20 receives the HTML file constituting the “reservation list” screen 1310 from the reservation management server 30. The “booking list” screen 1310 is displayed on the display unit 22 of the golf course terminal 20 by the browser of the golf course terminal 20.

When "reception" 1311 is clicked, a "reservation reception" screen 1320 of the link destination is displayed.

After confirming the contents of the reservation and selecting the start time, a comment is input if necessary, and when a “reply” button 1321 is clicked, a reply is sent to the reservation management server 30.

FIG. 14 is a schematic diagram showing the contents of the golf course reservation log file when the final reservation contents are received from the golf course. The final reservation content issued from the golf course is stored in the golf course reservation log file 353. This corresponds to step S111 in FIG.

The “reservation number” field, “visitor I”
"D" field, "golf course ID" field, "reply access time" field, "desired area" field, "desired date" field, "desired number of people" field,
The contents of the “underwriting condition amount” field and the “reception time zone” field are not changed.

The "reservation reception time" field stores the date and time when the golf course returned the contents of the last reservation. The “Status” field is changed from “Reply” to “Reserved”. The “start time” field stores the time selected by the golf course. At this point, the reservation is established.

FIG. 15 is an example of a “reservation confirmation” screen displayed on the display unit of the visitor terminal. Step S in FIG.
112.

The visitor terminal 10 is connected to the reservation management server 30
Request transmission of an HTML file that constitutes the “reservation confirmation” screen. The reservation management server 30 stores the visitor terminal 10
To send an HTML file that constitutes the “reservation confirmation” screen. The visitor terminal 10 receives, from the reservation management server 30, an HTML file constituting a “reservation confirmation” screen. The “reservation confirmation” screen is displayed on the visitor terminal 10 display unit 12 by the browser of the visitor terminal 10.

The reservation number, play date, start time, golf course name, number of people, play charge, and golf course telephone number are displayed.

The visitor can check the reservation status. According to this embodiment, the visitor (user)
The "acceptance conditions" can be received from a plurality of golf courses only by registering the "request conditions" once in the reservation management server. Visitors can save the trouble of browsing a plurality of web pages and searching for golf courses that are close to their wishes.

The visitor compares the plurality of "acceptance conditions" and transmits the "reservation contents" only to the golf course most liked. Then, the golf course sets the start time so that the “final reservation content” is determined.

It is not necessary to determine the start time of the golf course when the "acceptance conditions" are returned, and the start time can be finally determined within the time frame of "early" or "late". By determining the start time when the reservation is confirmed, the golf course can finely adjust the time zone to be accepted according to the availability. Basically, at the time of replying the acceptance conditions, the time period of the desired date (late etc.)
Must be free, but "accurate"
If the start time is determined after the reservation is made, the "vacant" can be effectively used as a golf course.

Further, the golf course can approach a large number of visitors by changing the search conditions when searching for the “play desired conditions”.
In addition to waiting for inquiries by phone or email from visitors, for example, without setting search conditions,
By displaying "all" of the visitors who have issued the "playing desired condition", various approaches can be attempted to the visitor selected from these visitors. For example, it is possible to approach a visitor whose desired area is "Jobando" by presenting various conditions such as "eat meal" from a golf course along "Hanshin Expressway".

Further, when the reservation management server receives the "acceptance conditions" from the golf course, the e-mail is transmitted to the visitor to inform the visitor of the "acceptance conditions". There is no need to browse web pages.

[0097]

As described above, by the method, the program and the recording medium of the present invention, the applicant can register the "application desired condition" only once in the reservation management server, and receive the "accepting condition" from a plurality of acceptors. "Can be received. For this reason, the applicant can save the trouble of browsing a plurality of web pages and searching for an acceptor who is close to his / her request.

Further, when retrieving the "application desired condition", the acceptor can approach many applicants by appropriately changing the retrieval condition.

[Brief description of the drawings]

FIG. 1 is a schematic diagram illustrating a system configuration according to an embodiment of the present invention.

FIG. 2 is a schematic diagram showing files stored in a storage unit of the reservation management server shown in FIG.

FIG. 3 is a flowchart illustrating a flow of a reservation process according to the embodiment of the present invention.

FIG. 4 is an example of a “user registration” screen displayed on the display unit of the visitor terminal.

FIG. 5 is an example of a “play condition input” screen displayed on the display unit of the visitor terminal.

FIG. 6 is a schematic diagram showing the contents of a visitor reservation log file when a desired play condition is received from a visitor.

FIG. 7 is an example of a “play wish list” screen displayed on the display unit of the golf course terminal.

FIG. 8 is an example of a “play wish list (input of play fee, etc.)” screen displayed on the display unit of the golf course terminal.

FIG. 9 is a schematic diagram showing the contents of a golf course reservation log file when reception conditions are received from a golf course.

FIG. 10 is an example of a “reception golf course list” screen displayed on the display unit of the visitor terminal.

FIG. 11 is an example of a “reservation transmission confirmation” screen displayed on the display unit of the visitor terminal.

FIG. 12 is a schematic diagram showing the contents of a visitor reservation log file when reservation contents are received from a visitor.

FIG. 13 is an example of a “reservation list” screen displayed on the display unit of the golf course terminal.

FIG. 14 is a schematic diagram showing the contents of a golf course reservation log file when the final reservation contents are received from the golf course.

FIG. 15 is an example of a “reservation confirmation” screen displayed on the display unit of the visitor terminal.

[Explanation of symbols]

 8 Internet 10 Visitor (subscriber) terminal 11 Visitor (subscriber) terminal input unit 12 Visitor (subscriber) terminal display unit 13 Visitor (subscriber) terminal communication unit 14 Visitor (subscriber) terminal control unit 15 Visitor (subscriber) ) Terminal storage unit 20 Golf course (acceptor) terminal 21 Golf course (acceptor) terminal input unit 22 Golf course (acceptor) terminal display unit 23 Golf course (acceptor) terminal communication unit 24 Golf course (acceptor) terminal Control unit 25 golf course (acceptor) terminal storage unit 30 reservation management server 31 reservation management server input unit 32 reservation management server display unit 33 reservation management server communication unit 34 reservation management server control unit 35 reservation management server storage unit 351 visitor information file 352 visitor reservation log file 353 go Ruf field reservation log file 354 Golf course information file 355 Area information file 356 Prefectural information file

──────────────────────────────────────────────────続 き Continued on the front page (51) Int.Cl. ⁷ Identification symbol FI Theme coat ゛ (Reference) G06F 17/60 322 G06F 17/60 322 326 326 330 330 330 502 502 502

Claims (6)

[Claims] 1. A reservation management method using a communication unit capable of transmitting and receiving data through a communication line, a storage unit capable of storing received data, and a control unit capable of searching for data in the storage unit. A receiving step of receiving an application request condition from an applicant who applies for a reservation; a storage step of storing the application desired condition; and a search for the communication unit to search for the application desired condition. A receiving step of receiving a condition from an acceptor accepting a reservation; a search step in which the control unit searches for the application desired condition satisfying the search condition; and the communication unit transmits a result of the search to the acceptor. A receiving step in which the communication unit receives an acceptance condition from the acceptor; and the storage unit stores the acceptance condition. A storage step; a receiving step in which the communication unit receives a transmission request for the acceptance condition from the reservation applicant; a transmission step in which the communication unit transmits the acceptance condition to the applicant; Receiving a reservation content from the applicant; a storage step in which the storage unit stores the reservation content; and a reception step in which the communication unit receives a transmission request for the reservation content from the acceptor. A reservation management method comprising: a transmission step in which the communication unit transmits the reservation content to the acceptor; and a reception step in which the communication unit receives final reservation content from the acceptor. 2. The reservation management method according to claim 1, wherein:
The reservation management method further includes a transmission step of, when the communication unit receives the acceptance condition from the acceptor, transmitting an electronic mail indicating that the acceptance condition can be referred to to the applicant. 3. A computer, comprising: a communication unit for receiving an application request condition from an applicant; a storage unit for storing the application request condition; and a communication unit for receiving a search condition for retrieving the application request condition from an acceptor. Search means for searching for the desired application condition that satisfies the search condition; communication means for transmitting the result of the search to the acceptor; communication means for receiving the acceptance condition from the acceptor; storage means for storing the acceptance condition Communication means for receiving a request for transmission of the acceptance condition from the applicant; communication means for transmitting the acceptance condition to the applicant; communication means for receiving reservation content from the applicant; storage means for storing the reservation content. Communication means for receiving a request for transmission of the reservation content from the acceptor; Communication means, reservation management program for causing to function final reservation contents as a communication means for receiving from the receiving party to send containers. 4. The reservation management program according to claim 3, further comprising: upon receiving the acceptance condition from the acceptor, transmitting an e-mail to the applicant indicating that the acceptance condition can be referred to. A reservation management program characterized by including functioning as communication means. 5. A communication means for receiving a desired application condition from an applicant, a storage means for storing the desired application condition, a communication means for receiving a search condition for retrieving the desired application condition from an acceptor, Search means for searching for the application desired condition that satisfies the search condition; communication means for transmitting the result of the search to the acceptor; communication means for receiving an acceptance condition from the acceptor; storage means for storing the acceptance condition; Communication means for receiving a transmission request for the acceptance condition from the applicant; communication means for transmitting the acceptance condition to the applicant; communication means for receiving reservation content from the applicant; storage means for storing the reservation content; Communication means for receiving a request for transmission of the reservation content from the acceptor; Communication means for transmitting, a computer-readable recording medium characterized in that the final reservation contents were recorded reservation management program to function as a communication means for receiving from said receiving user. 6. The recording medium according to claim 5, further comprising: when receiving the acceptance condition from the acceptor, transmitting an e-mail to the applicant indicating that the acceptance condition can be referred to. A computer-readable recording medium having recorded thereon a reservation management program for functioning as a means.