JP4679048B2 - Electronic ticket management / distribution system and electronic ticket distribution server - Google Patents

Description

  The present invention relates to a technique for transferring and reselling electronic ticket data owned by a user to another person via a network.

  Conventionally, when receiving certain services such as admission to a concert venue, purchase of goods, discounts on prices, etc., a paper ticket in which right information exchangeable for those services is printed on paper is generally used. In recent years, electronic tickets have been developed in which digitized right information (electronic ticket data) is recorded in portable electronic recording devices such as mobile phones and IC cards. Since the electronic ticket data recorded on the electronic ticket can be transferred via a network such as the Internet, the electronic ticket can be easily transferred and resold to others compared to a paper ticket.

  FIG. 29 is a block diagram showing a configuration example of a conventional electronic ticket resale system that resells electronic tickets to others (see, for example, Patent Document 1).

  As shown in the figure, a conventional electronic ticket resale system includes a reseller terminal 201 of a resale applicant who desires to resell an electronic ticket, a user terminal 202 of a purchase applicant who wishes to purchase an electronic ticket, The service provider server 203 is a business operator that mediates the buying and selling of tickets, and a network 204 such as the Internet that connects them to each other.

  The conventional resale system having such a configuration operates as follows.

  The resale applicant accesses the business server 203 using his / her reseller terminal 201. Thereafter, the reseller sends the electronic ticket data recorded in the electronic ticket to be resold from the resale terminal 201 to the business server 203. When the electronic ticket data is sent from the reseller, the business server 203 registers the electronic ticket data in an electronic ticket resale information storage unit (not shown).

  On the other hand, a purchase applicant who wishes to purchase an electronic ticket first accesses the business operator server 203 using his / her user terminal 202 when purchasing an electronic ticket. Accordingly, the business entity server 203 transmits a list of electronic tickets registered in the electronic ticket resale information storage unit to the user terminal 202.

  The user terminal 202 displays a list of resale desired electronic tickets sent from the business server 203, and the purchase requester selects an electronic ticket to be purchased from the displayed list. As a result, the user terminal 202 transmits an electronic ticket purchase request including ticket specifying information indicating the electronic ticket selected by the user to the business operator server 203.

When an electronic ticket purchase request is sent from the user terminal 202, the business server 203 reads the electronic ticket data of the electronic ticket requested for purchase from the electronic ticket resale information storage unit and transfers it to the user terminal 202. As a result, the user terminal 202 records electronic ticket data in a portable electronic recording device (not shown) such as an IC card, and the user uses the electronic recording device in which the electronic ticket data is recorded as an electronic ticket. Use as
JP 2003-50889 A

  According to the above-described conventional electronic ticket resale system, the electronic ticket can be easily resold, but there is a problem in reliability. In other words, the conventional electronic ticket resale system does not check the authenticity of the electronic ticket data sent from the reseller, so there is a risk that the forged electronic ticket data will be resold.

  SUMMARY OF THE INVENTION An object of the present invention is to provide a highly reliable electronic ticket management / distribution system in which counterfeit electronic ticket data is not transferred or resold.

In order to achieve the above object, the first electronic ticket management / distribution system according to the present invention provides:
An electronic ticket management / distribution system in which a user terminal used by a member, an electronic ticket distribution server, and an electronic ticket sales / distribution server are connected via a network,
The electronic ticket distribution server is
An electronic ticket management DB having a data area for each member;
A member management DB in which a member ID and a pointer indicating a data area assigned to the member specified by the member ID are registered;
When a storage request including electronic ticket data is sent from a user terminal, an inquiry request including a ticket ID of the electronic ticket data is sent to the electronic ticket sales / distribution server in order to check the validity of the electronic ticket data. When the inquiry OK is returned from the electronic ticket sales / distribution server in response to the inquiry request, a management ID for uniquely identifying the electronic ticket data is generated, and the generated management ID and the electronic Means for storing a pair with ticket data in a data area assigned to a member using the user terminal;
When a transfer request including a management ID of electronic ticket data to be transferred from a user terminal and a member ID of a transferee member of the electronic ticket data is sent, the transfer request is assigned to a member who uses the user terminal. The electronic ticket data specified by the management ID is extracted from the data area, and the pair of the extracted electronic ticket data and the management ID is included in the transfer request in the pointers registered in the member management DB. Means for storing in the data area indicated by the pointer corresponding to the member ID being
When a reception request including a management ID is sent from the user terminal, the electronic ticket data stored in the data area assigned to the member who uses the user terminal is paired with the management ID. Means for transmitting the electronic ticket data to the user terminal, and recording the electronic ticket data in an electronic ticket terminal connected to or integrated with the user terminal,
The electronic ticket sales / distribution server is
A sales / distribution DB in which the ticket ID of the electronic ticket data sold / distributed is registered;
When an inquiry request is sent from the electronic ticket distribution server, the sales / distribution DB is searched, and the same ticket ID as the ticket ID included in the inquiry request is registered in the sales / distribution DB. And a means for returning an inquiry OK to the electronic ticket distribution server .
A second electronic ticket management / distribution system according to the present invention is the first electronic ticket management / distribution system,
The electronic ticket management DB includes a data area for non-members in addition to a data area for each member.
The electronic ticket distribution server is
When a non-member transfer request including a management ID of electronic ticket data to be transferred is sent from the user terminal, the management ID is specified from the data area allocated to the member using the user terminal. The electronic ticket data to be retrieved, the pair of the retrieved electronic ticket data and the management ID is stored in the non-member data area provided in the electronic ticket management DB, and is associated with the management ID Means for managing temporary IDs and passwords;
When authentication information including a temporary ID and a temporary password is sent from the user terminal, the electronic ticket data specified by the management ID managed in association with the temporary ID and the temporary password is used for the non-member And a means for recording the electronic ticket data in an electronic ticket terminal connected to or integrated with the user terminal .

According to a third electronic ticket management / distribution system of the present invention, in order to enable an electronic ticket sales / distribution company to recognize the final owner of an electronic ticket,
The electronic ticket distribution server includes means for transmitting distribution history data including a ticket ID of electronic ticket data transferred to another member and a transfer destination member ID to the electronic ticket sales / distribution server,
In the sales / distribution history DB, in addition to the ticket ID, the member ID of the member who is the transfer destination of the electronic ticket data specified by the ticket ID is registered,
The electronic ticket sales / distribution server comprises means for updating the sales / distribution history DB based on distribution history data sent from the electronic ticket distribution server .

In order to prevent loss of electronic ticket data due to loss of an electronic ticket terminal, the fourth electronic ticket management / distribution system according to the present invention includes:
The electronic ticket distribution server is
When a withdrawal request including a management ID of electronic ticket data is sent from the user terminal, the electronic ticket data specified by the management ID is retrieved from the data area assigned to the member using the user terminal. The electronic ticket data is recorded in an electronic ticket terminal that is taken out and transmitted to the user terminal and connected to or integrated with the user terminal .

According to a fifth electronic ticket management / distribution system of the present invention, in order to be able to transfer an electronic ticket to a user who has a high probability of using the electronic ticket,
The schedule of members who can use the electronic ticket distribution server is managed, and when a schedule inquiry request including a PIM member ID is sent from the electronic ticket distribution server, the schedule of the member specified by the PIM member ID is displayed. A PIM server for returning to the electronic ticket distribution server , and
In the member management DB, in addition to the member ID and the pointer, the PIM member number for identifying the member indicated by the member ID in the PIM server, and the configuration of the group member designated by the member indicated by the member ID The member ID of the member is registered,
The electronic ticket distribution server is
When a PIM use transfer request including a member ID and a ticket ID of electronic ticket data to be transferred is sent from the user terminal, it is registered in association with the member ID included in the PIM use transfer request. A member ID of a member of a group member is searched from the member management DB, and a PIM member ID registered in association with the member ID of the member of the searched group member is searched from the member management DB. Means for transmitting a schedule inquiry request including the searched PIM member ID to the PIM server;
Based on the schedule of group member constituent members returned from the PIM server in response to the schedule inquiry request, a predetermined number of members who are highly likely to use the electronic ticket are selected from the group member constituent members. Means are provided .

More specifically, a sixth electronic ticket management / distribution system according to the present invention is the fifth electronic ticket management / distribution system,
When accuracy to use the electronic ticket from among the constituent member of the group members by a predetermined number of selecting a high member, in the effective period of the electronic ticket and Turkey to select the membership number of days in many cases it has become a no schedule preferentially Features.

Further, a seventh electronic ticket management / distribution system according to the present invention is such that the electronic ticket can be transferred to a user who has a high probability of using the electronic ticket.
A location information server that manages location information of members who can use the electronic ticket distribution server, and is specified by the device number when a location inquiry request including a device number is sent from the electronic ticket distribution server. A location information server that acquires location information of the location information acquisition device and returns the acquired location information to the electronic ticket distribution server ; and
In the member management DB, in addition to the member ID and the pointer, the device number of the position information acquisition device used for acquiring the position of the member specified by the member ID and the member indicated by the member ID are specified. The member IDs of the constituent members of the selected group members are registered,
The electronic ticket distribution server is
When a location use transfer request including a member ID and a ticket ID of electronic ticket data to be transferred is sent from the user terminal, it is registered in association with the member ID included in the location use transfer request. A member ID of a member of a group member is searched from the member management DB, and a device number registered in association with the member ID of a member of the searched group member is searched from the member management DB; Means for transmitting a location inquiry request including the searched device number to the location information server;
Based on the position information of the constituent members of the group members returned from the position information server in response to the location inquiry request, a predetermined number of members among the constituent members of the group members who are highly likely to use electronic tickets. And means for selecting .

More specifically, an eighth electronic ticket management / distribution system according to the present invention is the seventh electronic ticket management / distribution system,
When accuracy utilizing an electronic ticket from the configuration members of the group members a predetermined number selected high member, the position indicated by the location information, and Turkey select the members close to the using place of the electronic ticket preferentially It is characterized by.

Further, a ninth electronic ticket management / distribution system according to the present invention is such that the electronic ticket can be transferred to a user who has a high probability of using the electronic ticket.
The schedule of members who can use the electronic ticket distribution server is managed, and when a schedule inquiry request including a PIM member ID is sent from the electronic ticket distribution server, the schedule of the member specified by the PIM member ID is displayed. A PIM server to return to the electronic ticket distribution server;
A location information server that manages location information of members who can use the electronic ticket distribution server, and is specified by the device number when a location inquiry request including a device number is sent from the electronic ticket distribution server. A position information server that acquires position information of the position information acquisition device, and returns the acquired position information to the electronic ticket distribution server; and
The member management DB is used to acquire a PIM member number for identifying the member indicated by the member ID in the PIM server in addition to the member ID and the pointer, and the position of the member specified by the member ID. The device number of the location information acquisition device to be registered and the member ID of the constituent member of the group member designated by the member indicated by the member ID,
The electronic ticket distribution server is
When a location / PIM usage transfer request including a member ID and a ticket ID of electronic ticket data to be transferred is sent from the user terminal, the request is associated with the member ID included in the location / PIM usage transfer request. The member ID of the member of the registered group member is retrieved from the member management DB, and the PIM member ID registered in association with the member ID of the member of the retrieved group member is managed as the member. A schedule inquiry request including the searched PIM member ID is transmitted from the DB to the PIM server, and the device number registered in association with the member ID of the member of the searched group member is registered with the member. Means for searching from the management DB and transmitting a location inquiry request including the searched device number to the location information server;
The group member constituent member schedule returned from the PIM server in response to the schedule inquiry request and the group member constituent member position information returned from the location information server in response to the position inquiry request. On the basis of this, there is provided means for selecting a predetermined number of members who are highly likely to use the electronic ticket from among the constituent members of the group member .

More specifically, a tenth electronic ticket management / distribution system according to the present invention is the ninth electronic ticket management / distribution system,
When selecting a member having a high probability of using an electronic ticket from among the members of the group member, the acquired location information indicates that the electronic ticket can be moved to a use place by the expiration date of the electronic ticket, and acquired schedule, and wherein and Turkey to select the members, which shows that there is a vacancy in the schedule during the period from the present time until the expiration date of the electronic ticket.

In addition, an eleventh electronic ticket management / distribution system according to the present invention is the first electronic ticket management / distribution system, in order to be able to transfer electronic tickets for a fee.
A payment server for performing payment processing; and
The electronic ticket distribution server is
When a paid transfer request including a management ID of electronic ticket data to be transferred and a member ID of the transfer destination member of the electronic ticket data is sent from the user terminal, transfer to the user terminal of the transfer destination member for a charge From the data area allocated to the member using the user terminal after the payment server notifies that the transfer destination member has completed the payment. The electronic ticket data specified by the management ID in the paid transfer request is taken out, and the pair of the taken electronic ticket data and the management ID is taken out of the pointers registered in the member management DB. And means for storing in a data area indicated by a pointer corresponding to the member ID included in the request .

Further, in order to enable the twelfth electronic ticket management / distribution system according to the present invention to handle an electronic ticket that has been awarded in an auction, in the first electronic ticket management / distribution system,
A marketplace portal for notifying sellers of electronic ticket data and user terminals of successful bidders that the electronic ticket data has been successfully bid;
And a settlement server to notify the user terminal of the exhibitor of the electronic ticket that from the successful bidder of the electronic ticket data there was a payment for the settlement service providers,
The electronic ticket distribution server is
When a successful bid storage request including electronic ticket data for which a successful bid has been received is sent from the user terminal, an inquiry request including the ticket ID of the electronic ticket data is transmitted to the electronic ticket sales / distribution server. If the inquiry OK is returned from the electronic ticket sales / distribution server in response, a management ID for uniquely identifying the electronic ticket data is generated, and the pair of the generated management ID and the electronic ticket data is used. Means for storing data in a data area allocated to a member who uses a user terminal;
When a successful bid transfer request including a ticket ID of electronic ticket data to be transferred from the user terminal to the winning bidder and the member ID of the winning bidder is sent, the ticket ID is sent to the user terminal of the winning bidder. Means for transmitting transfer electronic ticket information indicating what kind of electronic ticket data is indicated;
When a receipt request is sent from the user terminal to which the transfer electronic ticket information is transmitted, the electronic ticket data corresponding to the transfer electronic ticket information is transmitted to the user terminal and connected to or integrated with the user terminal. And an electronic ticket terminal configured to record the electronic ticket data .

  The first effect is to provide a highly reliable electronic ticket management / distribution system in which counterfeit electronic ticket data is not transferred or resold. This is because the electronic ticket distribution server always inquires of the ticket sales / distribution server about the validity of the electronic ticket data when the electronic ticket data is exchanged.

  The second effect is that loss of electronic ticket data due to loss of the electronic ticket terminal can be prevented. This is because the electronic ticket data can be stored on the electronic ticket distribution server.

  A third effect is that the electronic ticket sales / distribution company can acquire information on the final owner of the electronic ticket. By acquiring the information of the final owner of the electronic ticket, for example, detailed marketing can be easily performed, or refund work can be easily performed due to sudden event cancellation.

  The fourth effect is that the electronic ticket can be transferred to a user who has a high probability of using the electronic ticket. The reason is that a member to be an electronic ticket transfer candidate is selected from the group members based on the member schedule managed by the PIM server and the member location information managed by the location information server. Because.

  The fifth effect is that electronic tickets can be transferred for a fee. The reason is that it includes a settlement server.

  The sixth effect is that electronic tickets that have been awarded at an auction can also be handled. The reason is that it includes a settlement server and a marketplace portal.

  Next, embodiments of the present invention will be described in detail with reference to the drawings.

[Configuration of First Embodiment]
FIG. 1 is a block diagram of a first embodiment of an electronic ticket management / distribution system according to the present invention. Referring to the figure, the electronic ticket management / distribution system of the present embodiment includes an electronic ticket distribution server 11, an electronic ticket management database (DB) 12, a distribution history DB 13, and a member management DB 14 of the electronic ticket distribution service provider 10. User terminals 21 and 31 and electronic ticket terminals 22 and 32 of users 20 and 30, electronic ticket sales and distribution server 41 and sales and distribution history DB 42 of electronic ticket sales and distribution company 40, and electronic ticket distribution portal An electronic ticket distribution portal 51 of the business 50 is configured. The electronic ticket distribution server 11, the user terminal 21, the user terminal 31, the electronic ticket sales / distribution server 41, and the electronic ticket distribution portal 51 are connected to each other via a network 100 such as the Internet.

  An electronic ticket distribution server 11 operated by an electronic ticket distribution service provider 10 that is an electronic ticket management / distribution service provider has the following functions.

A function of signing a use contract for the electronic ticket management / distribution service with the users 20 and 30 via the network 100 and registering member information of the user (member) who has signed the use contract in the member management DB 14.
A function of updating corresponding member information registered in the member management DB 14 in accordance with a member information change request from the user terminals 21 and 31.
When a storage request including electronic ticket data is sent from the user terminals 21 and 31, the electronic ticket sales / distribution server 41 is used to check the validity of the electronic ticket data. A function of registering in the electronic ticket management DB 12.
When a member transfer request including information specifying the electronic ticket to be transferred and information specifying the transfer destination member is sent from the user terminals 21 and 31, each of the electronic ticket management DB 12 provided A function of moving the corresponding electronic ticket data registered in the data area of the requesting member in the data area of each member to the data area of the transferee member.
When a transfer request for non-members including information specifying the electronic ticket to be transferred is sent from the user terminal 21 or 31, the data area for each member provided in the electronic ticket management DB 12 The function of moving the corresponding electronic ticket data registered in the data area of the requesting member to the non-member data area.
-When a withdrawal request including information identifying an electronic ticket is sent from the user terminal 21, 31, the corresponding electronic ticket data registered in the data area of the requesting member is sent to the requesting user. A function to send to the terminal.
-When a reception request including information specifying an electronic ticket is sent from the user terminals 21 and 31, the corresponding electronic ticket data registered in the data area of the requesting member is used as the requesting user terminal. To send to.
A function of additionally registering distribution history data in the distribution history DB 13 or updating corresponding transfer history data registered in the distribution history DB 13 when electronic ticket data is transferred to another person in response to a member transfer request. .
A function of transmitting distribution history data to the electronic ticket sales / distribution server 41.

  FIG. 2 is a diagram showing a configuration example of the electronic ticket management DB 12, which includes data areas 12-1 to 12-n assigned to each member and a data area 121 for non-members. In the present embodiment, one data area is assigned to one member.

  As shown in FIG. 3, the data area 12-i (1 ≦ i ≦ n) includes a plurality of pairs of electronic ticket data and management IDs (such as a unique sequence of alphanumeric characters) that uniquely identify the electronic ticket data. It has a size that can be stored. In the present embodiment, the electronic ticket data includes a ticket ID (such as a unique sequence of alphanumeric characters), a ticket name, service contents, a usable period, duplication permission, a ticket seller, and the like.

  FIG. 4 is a diagram showing an example of the contents of the member management DB 14 in which member information is registered. As shown in the figure, the member information includes a member ID for uniquely identifying the member, a password, a name, a contact information (for example, an e-mail address), and a data area assigned to the member. Contains pointers and group member information. A group member is a community composed of members of an electronic ticket management / distribution service that a user may transfer to electronic ticket data. The group member information includes the member ID of each member described above. A pair with name is included.

  In the example of FIG. 4, for example, in the first line, the member with the member ID “id1” has the password “P1”, the name “XXX”, the contact address “ZZZ”, and the pointer to the data area “#”. 1 ”indicates that the pair of the member ID and name of the group member is“ idj (AAA),... ”.

  FIG. 5 is a diagram showing an example of the contents of the distribution history DB 13 in which distribution history data is registered. As shown in the figure, the distribution history data includes a management ID that identifies electronic ticket data to be managed in the distribution history, a ticket ID included in the electronic data ticket, and a transfer destination of the electronic ticket data. The member ID of the member (transferee) who has become and the storage period limit of the distribution history data are included. For example, a date that is the same as the expiration date of the electronic ticket data or a date that is a predetermined period after the expiration date of the electronic ticket data is stored in the storage expiration date. In this embodiment, only the member ID is set for the item “transferee”, but other information (name, contact information, etc.) regarding the member may also be set.

  In the example of FIG. 5, for example, the distribution history data in the first row includes the electronic ticket data specified by the management ID “ID1”, which includes the ticket ID “TID1” and is transferred to the member with the member ID “idx”. It shows that. Further, the distribution history data is stored until “A month B day” set in the item of the storage period, and then deleted.

  The user terminals 21 and 31 of the users 20 and 30 who use the electronic ticket management / distribution service are realized by an information terminal that can be connected to the Internet and has a browser function, such as a mobile phone, a personal computer, and an in-vehicle terminal. The user terminals 21 and 31 can make various requests such as member registration information, member information update requests, electronic ticket data storage requests, electronic ticket data transfer requests, electronic ticket data withdrawal requests, and electronic ticket data reception requests. Is transmitted to the electronic ticket distribution server 11 via the network 100, and the electronic ticket data sent from the electronic ticket distribution server 11 in response to the withdrawal request or reception request is recorded in the electronic ticket terminals 22 and 32. And a function of reading electronic ticket data recorded in the electronic ticket terminals 22 and 32.

  The electronic ticket terminals 22 and 32 are realized by a small portable electronic recording device such as a mobile phone or an IC card. The electronic ticket terminals 22 and 32 are connected to the user terminals 21 and 31 via the Internet, wireless, infrared rays, a dedicated reader, and the like, and pass the held electronic ticket data to the user terminals 21 and 31, or the user terminal 21. , 31 has a function of holding electronic ticket data. Note that the electronic ticket terminals 22 and 32 may be integrated with the user terminals 21 and 31.

  The electronic ticket sales / distribution server 41 operated by the electronic ticket sales / distribution company 40, which is the electronic ticket sales / distribution source, receives the distribution history data from the electronic ticket distribution server 11. According to the distribution history data, there is a function of updating the corresponding sales / distribution history data stored in the sales / distribution history DB 42 and a function of checking the validity of the electronic ticket data inquired from the electronic ticket distribution server 11. .

  FIG. 6 is a diagram showing an example of the contents of the sales / distribution history DB 42. As shown in the figure, in the sales / distribution history DB 42, the ticket ID of the electronic ticket data that is the management target of the sales / distribution history and the member (transferee) to whom the electronic ticket data is transferred are shown. Sales / distribution history data including a member ID and a storage period are stored.

  In the example of FIG. 6, for example, the first row indicates that the electronic ticket data with the ticket ID “TID1” is transferred to the member with the member ID “idx”. The information in the first line indicates that the information is stored until “A month B day” set in the item of the storage period, and then deleted.

  An electronic ticket distribution portal 51 operated by an electronic ticket distribution portal provider 50 that provides a portal service for using the electronic ticket management / distribution service distributes electronic ticket data to the Web browsers of the user terminals 21 and 31. A function of transmitting a Web page serving as a user interface for accessing the server 11 is provided. The users 20 and 30 can perform service member registration and storage / transfer of electronic ticket data through the electronic ticket distribution portal 51.

[Description of Operation of First Embodiment]
Next, the operation of the present embodiment will be described in detail with reference to the drawings.

  First, an operation when the user 20 concludes a use contract for the electronic ticket management / distribution service with the electronic ticket distribution service provider 10 will be described.

  Referring to FIG. 7, the user 20 accesses the electronic ticket distribution portal 51 using his / her own terminal 21 and acquires the electronic ticket management / distribution service member registration form. After that, necessary information such as name, contact information, and group members is entered in the registration form to perform a use contract procedure (step A1).

  The electronic ticket distribution portal 51 transmits the member registration information including the name, contact information, and group members input by the user 20 using the registration form to the electronic ticket distribution server 11 (step A2).

  When the electronic ticket distribution server 11 receives the member registration information, the electronic ticket distribution server 11 issues a member ID and a password to the user 20, and the name, contact information and group member included in the member registration information, and the member ID and The password is registered in the member management DB 14 as shown in FIG. 4 (step A3). After that, the electronic ticket distribution server 11 secures a data area dedicated to the user 20 (an area for storing electronic ticket data) on the electronic ticket management DB 12 and sends a pointer to the secured data area to the member management DB 14. It is set in the member information of the registered user 20.

  The same operation is also performed when the user 30 enters into an electronic ticket management / distribution service usage contract with the electronic ticket distribution service provider 10.

  Next, an operation when the user 20 transfers the electronic ticket purchased by the user 20 to another person (referred to as a user 30) will be described. The transferee user 30 is also a member of the electronic ticket management / distribution service, and its name and member ID are set to the group member in the member information of the user 20 registered in the member management DB 14. And The electronic ticket is purchased by the user 20 from the electronic ticket sales / distribution company 40 in order to go to a concert or the like with the user 30.

  Referring to FIG. 8, the user 20 connects the electronic ticket terminal 22 in which electronic ticket data to be transferred is recorded to the user terminal 21 (step B1). Thereafter, the user 20 accesses the electronic ticket distribution portal 51 via the user terminal 21, and inputs the member ID and password in the member authentication form (step B2).

  The electronic ticket distribution server 11 authenticates the member ID and password received via the electronic ticket distribution portal 51, and returns an authentication result to the electronic ticket distribution portal 51 (step B3).

  In the case of authentication OK, the electronic ticket distribution portal 51 displays a member-specific ticket management page on the user terminal 21. This page is provided with a menu for selecting a service to be used by the user. In this embodiment, using this menu, “transfer service for electronic ticket members”, “transfer service for non-members of electronic ticket”, “storage service of electronic ticket”, “reception service of electronic ticket”, “ "Electronic ticket withdrawal service", "Member information update service", etc. can be selected.

  Since the transfer destination user 30 is a member of the electronic ticket management / distribution service, the user 20 selects “transfer service for electronic ticket members” from the menu (step B4).

  When the electronic ticket distribution server 11 recognizes that the user 20 has selected “transfer service for electronic ticket members” via the electronic ticket management page for each member, the data area for the user 20 on the electronic ticket management DB 12 The electronic ticket data storage list (including ticket name, service content, management ID, etc.) recorded in the database and the group member list of users 20 recorded in the member management DB 14 are transmitted to the electronic ticket distribution portal 51. At the same time, an instruction to display electronic ticket data is transmitted (step B5).

  Accordingly, the electronic ticket distribution portal 51 displays the electronic ticket data storage list and the group member list on the user terminal 21 via the member-specific electronic ticket management page, and issues an instruction to the user terminal 21. A list of electronic ticket data recorded in the electronic ticket terminal 22 is also displayed on the electronic ticket management page for each member (steps B6 and B7).

  The user 20 who has seen this display selects electronic ticket data to be transferred to the user 30 from the list of electronic ticket data recorded in the electronic ticket terminal. Accordingly, the user terminal 21 transmits a storage request including the electronic ticket data to be transferred to the electronic ticket distribution server 11 via the electronic ticket distribution portal 51 (step B8).

  When the electronic ticket distribution server 11 receives the storage request from the user terminal 21 via the electronic ticket distribution portal 51, the electronic ticket specified by the ticket seller information in the electronic ticket data included in the storage request. An inquiry request including the ticket ID of the electronic ticket data is sent to the sales / distribution server 41. When the electronic ticket sales / distribution server 41 receives the inquiry request, the electronic ticket sales / distribution server 41 searches the sales / distribution history DB 42 to check whether the same ticket ID as the ticket ID included in the inquiry request is registered. Thus, the validity of the electronic ticket data is checked. If registered, the inquiry OK is returned to the electronic ticket distribution server 11, and if not registered, the inquiry NG is returned to the electronic ticket distribution server 11. If the inquiry is OK, the electronic ticket distribution server 11 performs the process of the next step B10. If the inquiry is NG, the electronic ticket distribution server 11 notifies the user terminal of this and ends the process (step B9).

  If the inquiry is OK in step B9, the electronic ticket distribution server 11 generates a management ID for uniquely identifying the electronic ticket data requested to be stored by the user 20, and sets a pair of the electronic ticket data and the management ID. Are stored in the data area dedicated to the user 20 secured on the electronic ticket management DB 12 (step B10). Further, the electronic ticket distribution server 11 gives an invalid instruction including information for specifying the electronic ticket data to the user terminal 21 when the duplication permission / inhibition information in the electronic ticket data indicates that the duplication is impossible. The electronic ticket data on the ticket terminal 22 is invalidated (step B11).

  Thereafter, the electronic ticket distribution server 11 transmits a storage list of electronic ticket data stored in the data area of the user 20 to the electronic ticket distribution portal 51. The electronic ticket distribution portal 51 updates the storage list of electronic ticket data displayed on the user terminal 20 (step B12). By viewing this display, the user 20 recognizes that the storage processing of the electronic ticket data requested for storage has been completed.

  Thereafter, the user selects the electronic ticket data to be transferred to the user 30 from the electronic ticket data storage list displayed on the electronic ticket management page for each member, and selects the user 30 from the group member list. . Thereby, the user terminal 21 transmits a member transfer request including the management ID of the selected electronic ticket data and the member ID of the user 30 (step B13). This member transfer request is sent to the electronic ticket distribution server 11 via the electronic ticket distribution portal 51.

  When the electronic ticket distribution server 11 receives the member transfer request including the management ID of the electronic ticket data to be transferred and the member ID of the transfer destination user 30, the electronic ticket management server 12 stores the electronic ticket management DB 12 based on the management ID. The corresponding electronic ticket data is extracted from the data area for the user 20. Then, the ticket ID in the extracted electronic ticket data is transmitted to the electronic ticket sales / distribution server 41, and the validity of the electronic ticket is inquired (step B14; processing similar to step B9 described above). The inquiry process in step B14 may be omitted.

  Thereafter, in step B14, the electronic ticket distribution server 11 stores the electronic ticket data extracted from the data area for the user 20 and its management ID in the data area for the transfer destination user 30 (step B15). .

  Next, the electronic ticket distribution server 11 searches the distribution history DB 12 to check whether distribution history data including the same management ID as that of the electronic ticket data is registered. If it is not registered, distribution history data including the management ID, the ticket ID in the electronic ticket data, the member ID of the transferee (user 30), and the storage period is stored in the distribution history DB 13. Register additional. On the other hand, if registered, the member ID of the transferee is added to the item of transferee in the distribution history data (step B16).

  Thereafter, the electronic ticket distribution server 11 notifies the user 30 who is the transferee that the electronic ticket has been transferred using, for example, an electronic mail (step B17). Note that the email address of the user 30 can be obtained by searching the member management DB 14 using the member ID of the user 30 as a key. In the present embodiment, the electronic ticket distribution server 11 notifies the transferee user 30 that the electronic ticket has been transferred, but the transferor user 20 notifies the transfer. May be.

  When notified that the electronic ticket has been transferred, the user 30 connects the electronic ticket terminal 32 for recording the transferred electronic ticket data to the user terminal 31 as shown in the flowchart of FIG. C1). Next, the user 30 accesses the electronic ticket distribution portal 51 via the user terminal 31 and inputs the member ID and password in the member authentication form (step C2).

  The electronic ticket distribution server 11 authenticates the member ID and password received via the electronic ticket distribution portal 51, and returns an authentication result to the electronic ticket distribution portal 51 (step C3).

  In the case of authentication OK, the electronic ticket distribution portal 51 displays a member-specific ticket management page on the user terminal 31. The user selects “electronic ticket reception service” from the menu (step C4).

  When the electronic ticket distribution server 11 recognizes that the user 30 has selected “electronic ticket reception service” via the electronic ticket management page for each member, the electronic ticket distribution server 11 records the data in the data area for the user 30 in the electronic ticket management DB 12. The stored electronic ticket data storage list is transmitted to the electronic ticket distribution portal 51. The electronic ticket distribution portal 51 displays a storage list of electronic ticket data on the user terminal 31 via the member-specific electronic ticket management page (steps C5 and C6).

  The user 30 selects electronic ticket data to be acquired from the storage list. As a result, the user terminal 31 sends a reception request including the management ID of the selected electronic ticket data. This reception request is sent to the electronic ticket distribution server 11 via the electronic ticket distribution portal 51 (step C7).

  When receiving the reception request from the user terminal 31, the electronic ticket distribution server 11 extracts the electronic ticket data specified by the management ID included therein from the data area for the user 30 in the electronic ticket management DB 12. Then, the ticket ID in the extracted electronic ticket data is transmitted to the electronic ticket sales / distribution server 41, and the validity of the electronic ticket data is inquired (step C8; the same processing as step B9 described above). The inquiry process in step C8 may be omitted.

  In the case of inquiry OK, the electronic ticket distribution server 11 sends a recording instruction including the electronic ticket data extracted in step C8 to the user terminal 31. Thereby, the user terminal 31 records the electronic ticket data included in the recording instruction on the ticket terminal 32 (step C9).

  After that, the electronic ticket distribution server 11 deletes the electronic ticket data stored in the data area for the user 30 when the duplication permission / inhibition information in the electronic ticket data indicates that the duplication is impossible (step S30). C10). Further, the electronic ticket distribution server 11 retrieves distribution history data related to the electronic ticket data from the distribution history DB 13 and transmits it to the electronic ticket sales / distribution / server 41 (step C11).

  When the distribution history data is sent from the electronic ticket distribution server 11, the electronic ticket sales / distribution server 41 updates the corresponding sales / distribution history data in the sales / distribution history DB 42 accordingly (step C12). That is, the sales / distribution history data having the same ticket ID as the ticket ID in the distribution history data is updated, and the transferee in the sales / distribution history data is replaced with the transferee in the distribution history data. Process. The above is the processing performed when an electronic ticket is transferred to a member of the electronic ticket management / distribution service.

  Next, an operation for transferring an electronic ticket to a nonmember of the electronic ticket management / distribution service will be described.

  In FIG. 1, it is assumed that the users 20 and 30 are members and non-members of the electronic ticket management / distribution service, respectively, and the electronic tickets purchased by the user 20 from the electronic ticket sales / distribution business 40 are used by the non-members. Suppose that it is transferred to the person 30.

  Referring to FIG. 10, the user 20 accesses the electronic ticket distribution portal 51 through the user terminal 21 after connecting the electronic ticket terminal 22 in which electronic ticket data to be transferred is recorded to the user terminal 21. The member ID and password are entered in the member authentication form (steps D1 and D2).

  The electronic ticket distribution server 11 authenticates the member ID and password received via the electronic ticket distribution portal 51, and returns an authentication result to the electronic ticket distribution portal 51 (step D3).

  In the case of authentication OK, the electronic ticket distribution portal 51 displays a member-specific ticket management page on the user terminal 21. Since the transfer destination user 30 is a non-member, the user selects "transfer service for non-members of electronic ticket" from the menu (step D4).

  When the electronic ticket distribution server 11 recognizes that the user 20 has selected “transfer service for non-members of electronic tickets”, the electronic ticket distribution server 11 stores the electronic ticket data recorded in the data area for the user 20 on the electronic ticket management DB 12. The storage list is transmitted to the electronic ticket distribution portal 51 and an instruction to display the electronic ticket data is transmitted (step D5).

  As a result, the electronic ticket distribution portal 51 displays the electronic ticket data storage list on the user terminal 21 via the member-specific electronic ticket management page, and issues an instruction to the user terminal 21 to the electronic ticket terminal 22. A list of recorded electronic ticket data is also displayed on the electronic ticket management page for each member (steps D6 and D7).

  The user 20 who has seen this display selects electronic ticket data to be transferred to the user 30 from the list of electronic ticket data recorded in the electronic ticket terminal 22. Thereby, the user terminal 21 transmits a storage request including the electronic ticket data to be transferred to the electronic ticket distribution server 11 via the electronic ticket distribution portal 51 (step D8).

  When receiving the storage request from the user terminal 21, the electronic ticket distribution server 11 inquires of the electronic ticket sales / distribution server 41 about the validity of the electronic ticket included in the storage request (step D9).

  If the inquiry is OK in step D9, the electronic ticket distribution server 11 generates a management ID for uniquely identifying the electronic ticket data from the user 20, and sets the pair of the electronic ticket data and the management ID as an electronic The data is stored in the data area dedicated to the user 20 secured on the ticket management DB 12 (step D10). Further, when the electronic ticket distribution server 11 indicates that copying is impossible, the electronic ticket distribution server 11 sends an invalid instruction including information for specifying the electronic ticket data to the user terminal 21, and the electronic ticket on the electronic ticket terminal 22 is transmitted. The data is invalidated (step D11).

  Thereafter, the electronic ticket distribution server 11 transmits a storage list of electronic ticket data stored in the data area of the user 20 to the electronic ticket distribution portal 51. The electronic ticket distribution portal 51 updates the storage list of electronic ticket data displayed on the user terminal 20 (step D12).

  Thereafter, the user selects electronic ticket data to be transferred to the non-member user 30 from the electronic ticket data storage list displayed on the electronic ticket management page for each member. As a result, the user terminal 21 transmits a non-member transfer request including the management ID of the selected electronic ticket data (step D13).

  When the electronic ticket distribution server 11 receives the non-member transfer request including the management ID of the electronic ticket data to be transferred, the electronic ticket distribution server 11 receives the corresponding electronic data from the data area for the user 20 of the electronic ticket management DB 12 based on the management ID. Retrieve ticket data. Then, the electronic ticket sales / distribution server 41 is inquired about the validity of the extracted electronic ticket data (step D14). Note that the inquiry process in step D14 may be omitted.

  Thereafter, the electronic ticket distribution server 11 stores the electronic ticket data extracted from the data area for the user 20 in step D14 and its management ID in the non-member data area 121 on the electronic ticket management DB 12 (step D15). ). Furthermore, the electronic ticket distribution server 11 transmits the temporary ID and the temporary password corresponding to the temporary ID to the user terminal 21 and associates the management ID stored in the data area 121 in step D15 with the temporary ID and the temporary password. Manage (step D16).

  The user 20 informs the non-member user 30 of the temporary ID and the temporary password using e-mail or the like (step D17).

  When notified of the temporary ID and temporary password from the user 20, the user 30 connects the electronic ticket terminal 32 to the user terminal 31 as shown in the flowchart of FIG. 11 (step E1). Next, the user 30 accesses the electronic ticket distribution portal 51 via the user terminal 31, and inputs the temporary ID and temporary password notified from the user 20 to the member authentication form (step E2).

  The electronic ticket distribution server 11 authenticates the temporary ID and temporary password received via the electronic ticket distribution portal 51, and returns an authentication result to the electronic ticket distribution portal 51 (step E3).

  In the case of authentication OK, the electronic ticket distribution portal 51 displays a member-specific ticket management page on the user terminal 31. The user 30 selects “electronic ticket reception service” from the menu (step E4).

  When the electronic ticket distribution server 11 recognizes that the user 30 has selected “electronic ticket reception service” via the electronic ticket management page for each member, the user 30 obtains a non-member temporary ID and temporary password. Since it is used, the electronic ticket data to be transferred to the user 30 is taken out from the non-member data area 121, and the validity is inquired of the electronic ticket sales / distribution server 41 (step E5). The electronic ticket data to be transferred to the user 30 can be specified based on the management ID managed in association with the temporary ID and the temporary password in step D16 in FIG. That is, the electronic ticket data that is paired with the management ID in the electronic ticket data stored in the non-member data area 121 is electronic ticket data to be transmitted to the user 30.

  In the case of inquiry OK, the electronic ticket distribution server 11 records the electronic ticket data extracted in step E5 in the electronic ticket terminal 32 via the user terminal 31, and then the corresponding data from the non-member data area 121. The electronic ticket data to be deleted is deleted (steps E6 and E7).

  Next, an operation in the case where the electronic ticket data is stored in the electronic ticket distribution server 11 in order to prevent the electronic ticket data from being lost due to the loss of the ticket terminal or the like will be described.

  Referring to FIG. 12, the user 30 connects the electronic ticket terminal 32 to the user terminal 31 when storing the electronic ticket data recorded in his / her electronic ticket terminal 32 in the electronic ticket distribution server 11 (steps). F1). Next, the user 30 accesses the electronic ticket distribution portal 51 via the user terminal 31, and inputs the member ID and password in the member authentication form (step F2).

  The electronic ticket distribution server 11 authenticates the member ID and password received via the electronic ticket distribution portal 51, and returns an authentication result to the electronic ticket distribution portal 51 (step F3).

  In the case of authentication OK, the electronic ticket distribution portal 51 displays a member-specific ticket management page on the user terminal 31. The user selects “electronic ticket storage service” from the menu (step F4).

  When the electronic ticket distribution server 11 recognizes that the user 30 has selected “electronic ticket storage service” via the electronic ticket management page for each member, it transmits an electronic ticket data display instruction (step F5). This display instruction is sent to the user terminal 31 via the electronic ticket distribution portal 51.

  Thereby, the user terminal 31 displays the electronic ticket data recorded on the electronic ticket terminal 32 (steps F6 and F7). The user selects electronic ticket data to be stored on the electronic ticket distribution server 11 from the displayed electronic ticket data. Thereby, the user terminal 31 sends a storage request including the selected electronic ticket data to the electronic ticket distribution server 11 (step F8).

  When receiving the storage request from the user terminal 31, the electronic ticket distribution server 11 inquires the electronic ticket sales / distribution server 41 about the validity of the electronic ticket data included therein (step F9). In the case of inquiry OK, a management ID is added to the electronic ticket data included in the storage request and stored in the data area for the user 30 of the electronic ticket management DB 12 (step F10).

  Next, an operation when using the electronic ticket data stored on the electronic ticket distribution server 11 as described above will be described.

  When the user 30 uses the electronic ticket data stored in the electronic ticket distribution server 11, as shown in the flowchart of FIG. 13, the user 30 connects the electronic ticket terminal 32 that records the electronic ticket data to the user terminal 31. (Step G1). Next, the user 30 accesses the electronic ticket distribution portal 51 via the user terminal 31, and inputs the member ID and password in the member authentication form (step G2).

  The electronic ticket distribution server 11 authenticates the member ID and password received via the electronic ticket distribution portal 51, and returns an authentication result to the electronic ticket distribution portal 51 (step G3). As a result, the electronic ticket distribution portal 51 displays the member-specific electronic ticket management page on the user terminal 31. The user 30 selects “electronic ticket data withdrawal service” from the menu (step G4).

  When the electronic ticket distribution server 11 recognizes that the “electronic ticket data withdrawal service” has been selected via the member-specific electronic ticket management page, the electronic ticket distribution server 11 stores the electronic ticket stored in the data area for the user 30 in the electronic ticket management DB 12. A ticket data storage list is transmitted (step G5). This storage list is sent to the user terminal 31 via the electronic ticket distribution portal 51 and displayed (step G6). At this time, the electronic ticket data whose end date of the usable period is close (for example, one week before the deadline) is highlighted. In addition to steps G6, when the storage list is displayed, it may be displayed in consideration of the available period. The user 30 who has seen this display selects electronic ticket data to be used from the storage list. Thereby, the user terminal 31 transmits a withdrawal request including the management ID of the selected electronic ticket data (step G7).

  When the electronic ticket distribution server 11 receives the withdrawal request from the user terminal 31 via the electronic ticket distribution portal 51, the electronic ticket distribution server 11 extracts the corresponding electronic ticket data from the data area of the user 30 and electronically transmits the electronic ticket via the user terminal 31. Write to the ticket terminal 32 (step G8).

  Next, an operation when the user updates his / her member information registered in the member management DB 14 will be described.

  Referring to FIG. 14, when the user 30 updates his / her member information registered in the member management DB 14, the user 30 accesses the electronic ticket distribution portal 51 via the user terminal 31 and displays the member on the member authentication form. Enter the ID and password (step H1).

  The electronic ticket distribution server 11 authenticates the member ID and password received via the electronic ticket distribution portal 51, and returns an authentication result to the electronic ticket distribution portal 51 (step H2).

  In the case of authentication OK, the electronic ticket distribution portal 51 displays a member-specific electronic ticket management page on the user terminal 31. The user selects "member information update service" from the menu (step H3).

  When the electronic ticket distribution server 11 recognizes that the user 30 has selected “member information update service” via the electronic ticket management page for each member, the member information of the user 30 stored in the member management DB 14 Is transmitted to the electronic ticket distribution portal 51. The electronic ticket distribution portal 51 displays the current member information of the user 30 on the user terminal 31 via the electronic ticket management page for each member (steps H4 and H5).

  The user 30 updates the displayed member information using a keyboard (not shown) or the like (for example, update of contact information, addition of group members, etc.), and after the update is completed, transmits a member information update request. Instruct. Thereby, the user terminal 31 transmits a member information update request including the updated member information (step H6).

  When the electronic ticket distribution server 11 receives the member information update request via the electronic ticket distribution portal 51, the electronic ticket distribution server 11 updates the member information of the user 30 registered in the member management DB 14 according to the member information included therein ( Step H7).

[Effect of the first embodiment]
The first effect is to provide a highly reliable electronic ticket management / distribution system in which counterfeit electronic ticket data is not transferred or resold. This is because the electronic ticket distribution server always inquires of the ticket sales / distribution server about the validity of the electronic ticket data when the electronic ticket data is exchanged.

  The second effect is that loss of electronic ticket data due to loss of the electronic ticket terminal can be prevented. The reason is that electronic ticket data can be stored on the Internet.

  The third effect is that the electronic ticket sales / distribution company can acquire the information of the final owner of the electronic ticket based on the contents of the sales / distribution history DB 42. By acquiring the information of the final owner of the electronic ticket, for example, detailed marketing can be easily performed, or refund work can be easily performed due to sudden event cancellation. Here, if not only the member ID but also the name and contact information are set in the item “transferee” of the sales / distribution history DB 42, the final owner of the electronic ticket can be obtained simply by referring to the sales / distribution history DB 42. Information can be acquired. If only the member ID is set in the item “transferee”, the member ID set in the item “transferee” is passed to the electronic ticket distribution server 11 and the member corresponding to the member ID is passed. By requesting the name and contact information, it is possible to obtain information on the final owner of the electronic ticket. The electronic ticket distribution server 11 searches the member management DB 14 using the member ID included therein as a key when the above-mentioned request is passed from the electronic ticket sales / distribution server 41, so that the member's name or The contact information is acquired and returned to the electronic ticket sales / distribution server 41.

[Other Embodiments of the Invention]
Next, a second embodiment of the present invention will be described in detail.

  In the second embodiment of the present invention, when an automatic selection of a transferee by PIM data is requested from the transferor, the electronic ticket distribution server selects from among members using the PIM service among group members. A member (candidate member to be transferred) having a high probability of using an electronic ticket is automatically selected, and electronic ticket data transfer processing is performed for the selected candidate member to be transferred. The PIM (Personal Information Manager) service is a service that manages a user's schedule, address book, action list, and the like.

  FIG. 15 is a block diagram showing a configuration example of the present embodiment. A difference from the first embodiment shown in FIG. 1 is that a PIM server 61 operated by the PIM service provider 60 is added. The point is that an electronic ticket distribution server 11 a is provided instead of the electronic ticket distribution server 11, and a member management DB 14 a is provided instead of the member management DB 14.

  The PIM service provider 60 is a provider of a PIM service for electronic ticket management / distribution service members. The PIM server 61 operated by the PIM service provider 60 has a function of managing PIM data for each member.

  In addition to the functions of the electronic ticket distribution server 11 shown in FIG. 1, the electronic ticket distribution server 11a receives electronic tickets to be transferred from members using the PIM service among group members. It has a function of automatically selecting a member (candidate member to be transferred) having a high probability of use based on the PIM data and performing transfer processing of the electronic ticket for the candidate member to be transferred.

  FIG. 16 is a diagram showing an example of the contents of the member management DB 14a used in the present embodiment. FIG. 4 shows that items “PIM member ID” and “PIM password” are added to the member information. This is different from the member management DB 14.

  Next, the operation of the present embodiment will be described in detail.

  First, the operation at the time of member registration will be described taking as an example the case where the user 30 performs member registration. Note that a user who uses only the electronic ticket management / distribution service without using the PIM service may perform member registration according to the flowchart shown in FIG. However, the user who has registered as a member in accordance with the flowchart of FIG. 7 is excluded from the selection when the transferor requests the electronic ticket distribution server 11a to automatically select the transferee based on the PIM data.

  Referring to FIG. 17, the user 30 uses his / her user terminal 31 to access the electronic ticket distribution portal 51, inputs necessary information in the electronic ticket management / distribution service member registration form, and uses the user contract procedure. I do. At the same time, a PIM service use contract procedure is performed (step I1).

  The electronic ticket distribution portal 51 transmits the member 30 registration information of the user 30 to the electronic ticket distribution server 11a (step I2).

  The electronic ticket distribution server 11a transmits the member registration information for the PIM service of the transferee 30 to the PIM server 61, and requests the issuance of the member ID (PIM member ID) and password (PIM password) of the PIM service (step). I3).

  The PIM server 61 issues a PIM member ID and a PIM password of the user 30 and returns them to the electronic ticket distribution server 11a (step I4).

  Thereby, the electronic ticket distribution server 11a registers the member information of the user 30 in the member management DB 14a (step I5). As shown in FIG. 16, the member information includes items “electronic ticket management / distribution service member ID”, “electronic ticket management / distribution service password”, “name”, “contact”, “pointer”, “group”. “Member”, “PIM Service PIM Member ID”, and “PIM Password” are included, but since no data area is reserved for the user 30 at this point, no value is set for “Pointer”.

  Thereafter, the electronic ticket distribution server 11a transmits the member ID and password of the electronic ticket management / distribution service to the user terminal 31 (step I6). Furthermore, the electronic ticket distribution server 11a secures a data area for the user on the electronic ticket management DB 12, and sets a pointer indicating the secured data area in the member information of the user 30 (step I7).

  Next, an operation when the user 20 requests the electronic ticket distribution server 11a to automatically select a transferee by PIM data and transfers the electronic ticket data will be described.

  Referring to FIG. 18, steps B <b> 1 to B <b> 11 in FIG. 8 are performed in the user terminal 21, the electronic ticket distribution portal 51, the electronic ticket distribution server 11 a, and the electronic ticket sales / distribution server 41 of the user 20 who is the transfer person of the electronic ticket. A process similar to the above is performed (step J1). However, in the present embodiment, the menu displayed on the member-specific electronic ticket management page includes “transfer destination automatic selection service based on PIM data” in addition to the menu items described in the first embodiment. The user 20 selects this in step B4. Other operations are the same as those in the first embodiment.

  Thereafter, the electronic ticket distribution server 11 a transmits a storage list of electronic ticket data recorded in the data area for the user 20 on the electronic ticket management DB 12 to the electronic ticket distribution portal 51. The electronic ticket distribution portal 51 displays a storage list of electronic ticket data on the user terminal 21 via the member-specific electronic ticket management page (step J2).

  When the electronic ticket data storage list is displayed, the user 20 selects electronic ticket data to be transferred from the list. As a result, the user terminal 21 transmits a PIM usage transfer request including the management ID of the selected electronic ticket data (step J3).

  When the electronic ticket distribution server 11a receives the PIM use transfer request via the electronic ticket distribution portal 51, the electronic ticket distribution server 11a refers to the member management DB 14a and acquires the member ID of each member constituting the group member from the member information of the user 20. . Thereafter, the member management DB 14a is searched using each acquired member ID as a key, and a member who also subscribes to the PIM service is searched. That is, a member whose values are set in the items “PIM member ID” and “PIM password” in the member information is searched for. Then, the PIM member ID and PIM password of each found member and the usable period of the electronic ticket to be transferred are passed to the PIM server 61, and the usable period and the schedule before and after the usable period (including the planned location, etc.) Query. As a result, the PIM server 61 returns PIM data including the usable period of the electronic ticket of each member specified by the PIM member ID sent from the electronic ticket distribution server 11a and the schedule before and after that (step). J4).

  When the PIM data of each member is returned from the PIM server 61, the electronic ticket distribution server 11a selects a member having a high probability of using the electronic ticket to be transferred based on the returned PIM data of each member. Select as a candidate member to be transferred. As a method of selecting a candidate member to be transferred, for example, a method of preferentially selecting a predetermined number (one or more) of members who have many days without a schedule in the validity period of the electronic ticket, or a planned location is an electronic ticket A method of preferentially selecting a predetermined number (one or a plurality) of members close to the use location can be employed. Then, the selected candidate member to be transferred is notified of the presence of the electronic ticket data transferred from the user 20 using e-mail, the electronic ticket distribution portal 51, or the like (step J5).

  The user 30 receiving the notification of ticket transfer accesses the electronic ticket distribution portal 51 through his / her user terminal 31, inputs the member ID and password in the member authentication form, and enters the group-specific electronic ticket management page. Log in (step J6).

  The electronic ticket distribution server 11a authenticates the member ID and password received via the electronic ticket distribution portal 51 (step J7). In the case of authentication OK, a list of electronic ticket data transferred from the user 20 is transmitted to the user terminal 31 of the user 30 who is a candidate member to be transferred (step J8).

  When the list is sent, the user 30 selects electronic ticket data desired from the list. Thereby, the user terminal 31 sends a transmission request including the management ID of the selected electronic ticket data to the electronic ticket distribution server 11a (step J9).

  When the electronic ticket distribution server 11a receives the transmission request, the electronic ticket distribution server 11a inquires the electronic ticket sales / distribution server 41 about the validity of the electronic ticket data specified by the management ID included therein (step J10).

  In the case of inquiry OK, the transfer target electronic ticket data is moved from the data area for the user 20 on the electronic ticket management DB 12 to the data area of the user 30 (step J11). If the transfer target electronic ticket data is not stored in the data area of the user 20, the fact that the transfer has already been transferred to another user is notified, and the process is terminated.

  Thereafter, the electronic ticket distribution server 11a updates the distribution history DB 13 (step J12). Thereafter, processing similar to steps C9 to C12 in FIG. 9 is performed, and electronic ticket data is recorded in the user terminal 31 of the user 30 and the sales / distribution history DB 42 is updated (steps). J13). When a plurality of users perform the process of step J9, the electronic ticket data is transferred to the user who first performed the process of step J9.

  As described above, in this embodiment, the electronic ticket storage / distribution service is linked with the PIM service, thereby providing the transferor with a service for easily searching for a transferee suitable for ticket transfer. it can. In addition, the transfer target establishment rate can be further improved by expanding the service recipients to the entire service members without being limited to group members.

  Next, a third embodiment of the present embodiment will be described in detail. In the present embodiment, when an automatic selection of a transferee by location information is requested from the transferor, the electronic ticket distribution server selects a transferable candidate member who has a high probability of using an electronic ticket from among the group members. The electronic ticket data is automatically transferred based on the position information of each member, and electronic ticket data transfer processing is performed for the selected transfer target member.

  FIG. 19 is a block diagram showing a configuration example of the present embodiment, which is different from the first embodiment shown in FIG. 1 in that each user 20, 30 is provided with position information acquisition devices 23, 33. The location information server 71 operated by the location information service provider 70 is added, the electronic ticket distribution server 11b is provided instead of the electronic ticket distribution server 11, and the member management DB 14b instead of the member management DB 14 Is different.

  The position information acquisition devices 23 and 33 have a position information acquisition function using GPS, PHS, or the like, and are realized by, for example, a mobile phone with a GPS function or an in-vehicle terminal.

  The location information service provider 70 is a third-party location search service provider. The third-party location search service is a service that enables location information search by a third party other than the owner of the location information acquisition device. The position information server 71 has a function of searching for positions of the position information acquisition devices 23 and 33 and transmitting the position information.

  In addition to the functions of the electronic ticket distribution server 11 shown in FIG. 1, the electronic ticket distribution server 11b has a high probability of using an electronic ticket that is a transfer target among group members (candidate for transfer). Member) is automatically selected based on the position information, and the electronic ticket transfer process is performed for the selected transfer target candidate member.

  FIG. 20 is a diagram showing an example of the contents of the member management DB 14b used in the present embodiment. The member management DB 14 shown in FIG. 4 is that the item “location information acquisition device number” is added to the member information. Is different.

  Next, the operation of this embodiment will be described.

  First, the operation at the time of member registration will be described. The operation at the time of member registration is almost the same as steps A1 to A4 in FIG. 7, but the member registration information transmitted from the user terminals 21 and 31 to the electronic ticket distribution server 11b includes the position information acquisition device number. Is different. A user (not shown) who does not have a location information acquisition device can also register as a member with the electronic ticket distribution service provider 10 (see FIG. 7). When the transferee requests the electronic ticket distribution server 11b to automatically select the transferee based on the position information, the transfer is excluded from the selection target.

  Next, an operation when the user 20 requests the electronic ticket distribution server 11b to automatically select a transferee based on position information and transfers the electronic ticket data will be described.

  Referring to FIG. 21, in the user terminal 21 of the user 20 who is the transferer of the electronic ticket, the electronic ticket distribution portal 51, the electronic ticket distribution server 11b, and the electronic ticket sales / distribution server 41, steps B1 to B11 in FIG. A process similar to the above is performed (step K1). However, in this embodiment, the menu displayed on the member-specific electronic ticket management page includes the “transfer destination automatic selection service based on location information” in addition to the menu items described in the first embodiment. The user 20 selects this in step B4. Other operations are the same as those in the first embodiment.

  Thereafter, the electronic ticket distribution server 11 b transmits a storage list of electronic ticket data recorded in the data area for the user 20 on the electronic ticket management DB 12 to the electronic ticket distribution portal 51. The electronic ticket distribution portal 51 displays a storage list of electronic ticket data on the user terminal 21 via the member-specific electronic ticket management page (step K2).

  When the electronic ticket data storage list is displayed, the user 20 selects electronic ticket data to be transferred from the list. As a result, the user terminal 21 transmits a location use transfer request including the management ID of the selected electronic ticket data (step K3).

  When the electronic ticket distribution server 11b receives the location use transfer request via the electronic ticket distribution portal 51, the electronic ticket distribution server 11b refers to the member management DB 14b and acquires the member ID of each member constituting the group member from the member information of the user 20. . Thereafter, the member management DB 14b is searched using each acquired member ID as a key, and the position information acquisition device number of each member constituting the group member is acquired. Then, the acquired position information acquisition device number of each member is passed to the position information server 71, and the position information of each member is inquired (step K4). Thereby, the location information server 71 acquires location information indicating the current location of the location information acquisition device owned by each member based on the location information acquisition device number passed from the electronic ticket distribution server 11b. The acquired position information is returned to the electronic ticket distribution server 11b (steps K5 and K6).

  When the position information of each member is returned from the position information server 71, the electronic ticket distribution server 11b selects a member having a high probability of using the electronic ticket to be transferred based on the returned position information of each member. Select as a candidate member to be transferred. As a method for selecting the candidate member to be transferred, for example, a method of preferentially selecting a predetermined number (one or a plurality) of members whose positions indicated by the position information are close to the place where the electronic ticket is used can be adopted. After that, the selected candidate member to be transferred is notified of the presence of the electronic ticket data transferred from the user 20 by using an electronic mail or the electronic ticket distribution portal 51 (step K7). Thereafter, processing similar to steps J6 to J13 in FIG. 18 is performed.

  As described above, in the embodiment, the transferer can use electronic ticket data that is close to the expiration date (such as one hour before the start of the event) by linking the electronic ticket storage / distribution service with the location information service. , It can be transferred to a transferee suitable for use of the electronic ticket. In addition, the transfer target establishment rate can be further improved by expanding the service recipients to the entire service members without being limited to group members.

  Next, a fourth embodiment of the present invention will be described in detail. The present embodiment is characterized in that the location information service and the PIM service are linked to the electronic ticket management / distribution service.

  FIG. 22 is a block diagram showing a configuration example of the present embodiment. The third embodiment shown in FIG. 19 is different from the third embodiment in that a PIM server 60 operated by the PIM service provider 60 is added. The difference is that an electronic ticket distribution server 11c is provided instead of the electronic ticket distribution server 11b, and a member management DB 14c is provided instead of the member management DB 14b.

  In addition to the functions of the electronic ticket distribution server 11b shown in FIG. 19, the electronic ticket distribution server 11c has a high probability of using the electronic ticket to be transferred (group candidate) from among group members. Member) is automatically selected based on the position information and the PIM data, and the electronic ticket transfer process is performed for the selected transfer target candidate member.

  FIG. 23 is a diagram showing an example of the contents of the member management DB 14c used in the present embodiment. FIG. 20 shows that items “PIM member ID” and “PIM password” are added to the member information. This is different from the member management DB 14b.

  Next, the operation of this embodiment will be described.

  First, the operation at the time of member registration will be described. The operation at the time of member registration is almost the same as steps I1 to I7 in FIG.

  Next, an operation when the user 20 requests the electronic ticket distribution server 11c to automatically select a transferee based on position information and PIM data and transfers the electronic ticket data will be described.

  Referring to FIG. 24, in the user terminal 21 of the user 20 who is the transferer of the electronic ticket, the electronic ticket distribution portal 51, the electronic ticket distribution server 11c, and the electronic ticket sales / distribution server 41, steps B1 to B11 in FIG. And substantially the same processing is performed (step L1). However, in the present embodiment, the menu displayed on the member-specific electronic ticket management page includes “transfer destination automatic selection service based on location information / PIM data” in addition to the menu items described in the third embodiment. The user 20 selects this in step B4. Other operations are the same as those in the first embodiment.

  Thereafter, the electronic ticket distribution server 11 c transmits the electronic ticket data storage list recorded in the data area for the user 20 on the electronic ticket management DB 12 to the electronic ticket distribution portal 51. The electronic ticket distribution portal 51 displays a storage list of electronic ticket data on the user terminal 21 via the member-specific electronic ticket management page (step L2).

  When the electronic ticket data storage list is displayed, the user 20 selects electronic ticket data to be transferred from the list. As a result, the user terminal 21 transmits a position / PIM usage transfer request including the management ID of the selected electronic ticket data (step L3).

  Thereby, the electronic ticket distribution server 11c queries the position information server 71 for the position information of each member belonging to the group member (step L4), and the position information server 71 electronically stores the position information of each member belonging to the group member. The ticket is returned to the ticket distribution server 11c (steps L5 and L6).

  The electronic ticket distribution server 11c selects a member that can be moved to the usage place by the expiration date of the electronic ticket based on the returned location information of each member, The PIM server 61 is inquired of the PIM data before and after that (step L7).

  Thereafter, the electronic ticket distribution server 11c selects a member (candidate member to be transferred) with a high use probability of the electronic ticket based on the returned PIM data. For this selection, for example, a method of selecting a member having a vacancy in the schedule between the current time and the expiration date of the electronic ticket can be adopted. Then, the selected candidate member to be transferred is notified of the presence of the electronic ticket data transferred from the user 20 using e-mail, the electronic ticket distribution portal 51, or the like (step L8). Thereafter, the same processing as steps J6 to J13 in FIG. 18 is performed (step L9).

  As described above, in this embodiment, the transferer can search for a transferee with higher use accuracy by linking the PIM service with the electronic ticket storage / distribution service in addition to the location information service. Become. For example, an event ticket scheduled to start one hour later can be transferred to a person who is near the event venue and can participate in the event on a scheduled basis. In addition, the transfer target establishment rate can be further improved by expanding the service recipients to the entire service members without being limited to group members. In the embodiment described above, the position information and the schedule are managed using separate servers, but may be managed using a single server (schedule / position management server). .

  Next, a fifth embodiment of the present invention will be described in detail. The present embodiment is characterized in that the transferee pays a ticket fee to the transferee when transferring the electronic ticket data.

  FIG. 25 is a block diagram showing a configuration example of the present embodiment, which is different from the first embodiment shown in FIG. 1 in that it includes a settlement server 81 operated by a settlement service provider 80, and an electronic The difference is that an electronic ticket distribution server 11 d is provided instead of the ticket distribution server 11. The payment service provider 80 is a payment service provider using a credit card or the like, and the payment server 81 has a function of performing payment processing.

  Next, the operation of the present embodiment will be described. Since the present embodiment and the first embodiment differ only in the operation when transferring an electronic ticket for a fee, only the operation when transferring an electronic ticket for a fee will be described here.

  Now, for example, it is assumed that the user 20 transfers an electronic ticket to the user 30 for a fee. It is assumed that the transfer destination user 30 recognizes what electronic ticket is transferred from the user 20. Referring to FIG. 26, first, in the user terminal 21, the electronic ticket distribution portal 51, and the electronic ticket distribution server 11d of the user 20 who is the transferor, the same processing as steps B1 to B11 in FIG. M1). However, in the present embodiment, the menu displayed on the member-specific electronic ticket management page includes the “paid transfer service for electronic tickets” in addition to the menu items described in the first embodiment. The user 20 selects this in step B4. Other operations are the same as those in the first embodiment.

  Thereafter, the electronic ticket distribution server 11 d transmits the storage list of electronic ticket data recorded in the data area for the user 20 on the electronic ticket management DB 12 to the electronic ticket distribution portal 51. The electronic ticket distribution portal 51 displays a storage list of electronic ticket data on the user terminal 21 via the member-specific electronic ticket management page (step M2).

  Thereafter, the user concludes a service use contract with the settlement service provider 80 via the member-specific electronic ticket management page (M3). Further, the user 20 selects the electronic ticket data to be transferred from the displayed electronic ticket data storage list, and the transferee (the user 30 and the user 30) from the displayed group member list. Select (Yes). Accordingly, the user terminal 21 transmits a paid transfer request including the management ID of the selected electronic ticket data and the member ID of the transfer destination user 30 (step M4).

  When the electronic ticket distribution server 11d receives the paid transfer request via the electronic ticket distribution portal 51, the electronic ticket distribution server 11d inquires the electronic ticket sales / distribution server 41 about the validity of the transfer target electronic ticket data (step M5). Note that the process of step M5 may be omitted.

  And in the case of inquiry NG, a process is complete | finished. On the other hand, in the case of inquiry OK, the user terminal 31 of the transfer destination user 30 is notified that the electronic ticket has been transferred using an electronic mail or the like (step M6).

  Upon receiving this notification, the user 30 accesses the electronic ticket distribution portal 51 via the user terminal 31, and inputs the member ID and password (step M7).

  The electronic ticket distribution server 11d authenticates the member ID and password received via the electronic ticket distribution portal 51, and in the case of authentication OK, the transfer indicating what kind of electronic ticket is to be transferred. The electronic ticket information is transmitted to the electronic ticket distribution portal 51. The electronic ticket distribution portal 51 displays the transferred electronic ticket information on the user terminal 31 via the electronic ticket transfer page (step M8).

  Based on the displayed transfer electronic ticket information, the user 30 checks whether the transfer-target electronic ticket is an electronic ticket that is to be transferred from the user 20. If the electronic ticket is not to be transferred from the user 20, the process is terminated. On the other hand, in the case of an electronic ticket that is to be transferred from the user, a procedure for paying the ticket price to the designated account is performed to the settlement service provider 80 via the electronic ticket transfer page. (Step M9). Payment uses a credit card, account deposit, electronic money or the like.

  The settlement server 81 of the settlement service provider 80 notifies the electronic ticket distribution server 11d that the transfer destination user 30 has received payment to the designated account (the account designated by the settlement service provider 80) (step M10). ).

  As a result, the electronic ticket distribution server 11d moves the electronic ticket data to be transferred from the user 20 data area on the electronic ticket management DB 12 to the transfer destination user 30 data area (step M11). .

  The electronic ticket distribution server 11d notifies the settlement server 81 that the transfer of the electronic ticket data to the user 30 has been completed (step M12).

  As a result, the settlement server 81 deposits, to the designated account of the user 20, a fee obtained by removing the fee from the fee transferred to the designated account by the user 30 (Step M 13).

  The electronic ticket distribution server 11d records in the distribution history DB 13 that the owner of the electronic ticket data has been changed from the user 20 to the user 30 (step M14).

  Thereafter, when the transfer destination user 30 records the electronic ticket data transferred from the user 20 in his / her electronic ticket terminal 32, for example, the processing shown in the flowchart of FIG. 9 is performed.

  As described above, in the embodiment, the electronic ticket management / distribution service and the settlement service provider cooperate to pay the ticket price after the transferee confirms the contents of the electronic ticket data. In addition, since the ticket data is transferred after confirming payment of the transferee's ticket price, a safe transaction service can be provided to both the transferee and the transferee. In addition, when electronic ticket data is delivered, it is possible to prevent fraudulent acts caused by duplicated data by inquiring the contents to the ticket sales company.

  Next, a sixth embodiment of the present invention will be described in detail. This embodiment is characterized in that electronic ticket data for which a transaction has been established in the marketplace is delivered using an electronic ticket storage / distribution service.

  FIG. 27 is a block diagram showing a configuration example of the present embodiment. The first embodiment shown in FIG. 1 is different from the first embodiment in that a settlement server 81 operated by a settlement service provider 80 is provided. A difference is that a marketplace portal 91 operated by the portal business 90 is provided, and an electronic ticket distribution server 11e is provided instead of the electronic ticket distribution server 11.

  The marketplace portal provider 90 is a provider of a marketplace portal service such as an auction, and the settlement service provider 80 is a provider of a settlement service using a credit card or the like.

  Next, the operation of this embodiment will be described.

  Assume that the user 20 is an exhibitor in the marketplace and the user 30 is a successful bidder. It is assumed that the users 20 and 30 are already members of the electronic ticket management / distribution service provided by the electronic ticket distribution service provider 10.

  When the user 20 who is an exhibitor receives a notice of a successful bid for an electronic ticket that is exhibited through the marketplace portal 91, the data area for the user 20 on the electronic ticket management DB 12 according to steps F1 to F10 of FIG. The electronic ticket data to be transferred to the successful bidder is stored. The successful bid notification includes the membership number of the user 30 who is the successful bidder.

  On the other hand, as shown in the flowchart of FIG. 28, the user 30 who is a successful bidder receives a successful bid notification from the marketplace portal 91 (step N1), and accesses the marketplace portal 91 to the settlement service provider 80. Then, a procedure for paying the contract price notified from the marketplace portal operator 90 to the designated account is performed (step N2). Payment uses a credit card, account deposit, electronic money or the like.

  The settlement service server 81 notifies the user 20 as an exhibitor that the user 30 has received money in the designated account (step N3).

  The user 20 accesses the electronic ticket distribution portal 51 via the user terminal 21, and inputs the member ID and password in the member authentication form (step N4).

  The electronic ticket distribution server 11e authenticates the member ID and password received via the electronic ticket distribution portal 51 (step N5).

  In the case of authentication NG, the electronic ticket distribution server 11e ends the process. On the other hand, in the case of authentication OK, the storage list of the electronic ticket data recorded in the data area for the transferor 20 of the electronic ticket management DB 12 is transmitted to the electronic ticket distribution portal 51 (step N6). The electronic ticket distribution portal 51 displays an electronic ticket data storage list on the user terminal 21 via the member-specific electronic ticket management page.

  The user 20 selects the electronic ticket data to be transferred from the electronic ticket data storage list via the member-specific electronic ticket management page, and inputs the member ID of the user 30 who is the winning bidder. As a result, the user terminal 21 transmits to the electronic ticket distribution server 11e a transfer request including the member ID and the management ID of the electronic ticket to be transferred and the user 30 who is the winning bidder (step N7).

  The electronic ticket distribution server 11e inquires of the electronic ticket sales / distribution server 41 about the validity of the successful electronic ticket data (step N8).

  In the case of inquiry NG, the electronic ticket distribution server 11e ends the process. On the other hand, in the case of inquiry OK, the marketplace portal 91 is inquired as to whether or not the electronic ticket data sent from the user 20 has the same ticket name / service content as the submitted electronic ticket data ( Step N9).

  In the case of inquiry NG, the electronic ticket distribution server 11e ends the process. On the other hand, in the case of the inquiry OK, the user 30 who is the successful bidder is notified that the successful electronic ticket data has been sent (step N10).

  As a result, the user 30 accesses the electronic ticket distribution portal 51 via the user terminal 31 and inputs the member ID and password (step N11).

  The electronic ticket distribution server 11e authenticates the member ID and password received via the electronic ticket distribution portal 51. In the case of authentication OK, what kind of electronic ticket is sent from the user 20? The transferred electronic ticket information shown is transmitted to the electronic ticket distribution portal 51. The electronic ticket distribution portal 51 displays the transferred electronic ticket information on the user terminal 31 via the electronic ticket transfer page (step N12).

  Based on the displayed transfer electronic ticket information, the user 30 checks whether or not the electronic ticket to be transferred is a successful bid electronic ticket. If it is not a successful electronic ticket, the process is terminated. On the other hand, if it is a successful electronic ticket, a request for receiving electronic ticket data is transmitted to the electronic ticket distribution server 11e (step N13).

  Thereby, the electronic ticket distribution server 11e stores the electronic ticket data to be transferred to the winning bidder stored in the data area of the user 20 in the data area of the user 30 who is the winning bidder (Step N14). Thereafter, the electronic ticket distribution server 11e notifies the settlement server 81 that the transfer of the electronic ticket data has been completed (step N15).

  As a result, the settlement server 81 deposits, to the designated account of the user 20, the fee that has been removed from the fee transferred to the designated account by the user 30 (step N <b> 16).

  The electronic ticket distribution server 11e records in the distribution history DB 13 that the owner of the electronic ticket data has been changed from the user 20 to the user 30 (step N17).

  Thereafter, when the user 30 who is the winning bidder records the winning electronic ticket data in his / her electronic ticket terminal 32, for example, the processing shown in the flowchart of FIG. 9 is performed.

  As described above, in the embodiment, electronic ticket data can be handled on the market place by using the electronic ticket management / distribution service. In addition, by cooperating with the settlement service provider, payment can be made after confirming the contents of the electronic ticket data for which the successful bidder has made a successful bid, and a safe transaction becomes possible. In addition, when electronic ticket data is delivered, it is possible to prevent fraudulent acts caused by duplicated data by inquiring the contents to the ticket sales company.

It is a block diagram which shows the structural example of the 1st Embodiment of this invention. It is a figure which shows the structural example of electronic ticket management DB12. It is a figure which shows the example of the content of data area 12-i on electronic ticket management DB12. It is a figure which shows the example of the content of member management DB14. It is a figure which shows the example of the content of distribution log | history DB13. It is a figure which shows the example of the content of sales and distribution log | history DB42. It is a flowchart which shows the example of a process at the time of member registration. It is a flowchart which shows the example of a process at the time of transferring electronic ticket data for a member. It is a flowchart which shows the example of a process when recording the electronic ticket data to which the member was transferred to own electronic ticket terminal. It is a flowchart which shows the example of a process at the time of transferring electronic ticket data with respect to a nonmember. It is a flowchart which shows the example of a process at the time of recording the electronic ticket data to which the nonmember was transferred to own electronic ticket terminal. 6 is a flowchart illustrating a processing example when requesting storage of electronic ticket data to the electronic ticket distribution server 11. 4 is a flowchart showing an example of processing when extracting electronic ticket data stored in the electronic ticket distribution server 11. It is a flowchart which shows the example of a process when changing member information. It is a block diagram which shows the structural example of the 2nd Embodiment of this invention. It is a figure which shows the example of the content of member management DB14a. It is a flowchart which shows the example of a process at the time of member registration. It is a flowchart which shows the process example of the process which selects automatically the transfer destination of electronic ticket data based on PIM data, and transfers. It is a block diagram which shows the structural example of the 3rd Embodiment of this invention. It is a figure which shows the example of the content of member management DB14b. It is a flowchart which shows the process example of the process which selects and transfers the transfer destination of electronic ticket data automatically based on a positional information. It is a block diagram which shows the structural example of the 4th Embodiment of this invention. It is a figure which shows the example of the content of member management DB14c. It is a flowchart which shows the process example of the process which selects and transfers the transfer destination of electronic ticket data based on PIM data and position information. It is a block diagram which shows the structural example of the 5th Embodiment of this invention. It is a flowchart which shows the process example at the time of performing charge transfer of electronic ticket data. It is a block diagram which shows the structural example of the 6th Embodiment concerning this invention. It is a flowchart which shows the process example in the case of handling the electronic ticket data awarded by the auction. It is a block diagram for demonstrating the prior art.

Explanation of symbols

10 ... Electronic ticket distribution service provider 11, 11a, 11b, 11c, 11d, 11e ... Electronic ticket distribution server 12 ... Electronic ticket management DB
13 ... Distribution history DB
14, 14a, 14b, 14c ... Member management DB
20, 30 ... User 21, 31 ... User terminal 22, 32 ... Electronic ticket terminal 23, 33 ... Location information acquisition device 40 ... Electronic ticket sales / distribution business 41 ... Electronic ticket sales / distribution server 42 ... Sales / distribution History DB
50 ... Electronic ticket distribution portal business 51 ... Electronic ticket distribution portal 60 ... PIM service business 61 ... PIM server 70 ... Location information service business 71 ... Location information server 80 ... Payment service business 81 ... Payment server 90 ... Market place Portal company 91 ... Marketplace portal 100 ... Network

Claims (8)

An electronic ticket management / distribution system in which a user terminal used by a member, an electronic ticket distribution server, and an electronic ticket sales / distribution server are connected via a network,
The electronic ticket distribution server is
A member management DB in which a member ID and a pointer indicating a data area assigned to the member specified by the member ID are registered;
When the member ID is sent from the first user terminal and the storage request including the electronic ticket data is sent, the inquiry including the ticket ID of the electronic ticket data is performed to check the validity of the electronic ticket data. First transmission means for transmitting a request to the electronic ticket sales / distribution server;
A generating unit that generates a management ID for uniquely identifying the electronic ticket data when an inquiry OK is returned from the electronic ticket sales / distribution server in response to the inquiry request;
Each member has a data area, and a pair of the generated management ID and the electronic ticket data is stored in a data area assigned to a member ID of a member who uses the first user terminal. An electronic ticket management DB stored by the means ;
When a transfer request including a management ID of electronic ticket data to be transferred from the first user terminal and a member ID of a transferee member of the electronic ticket data is sent, the first user terminal is used. A first search means for searching electronic ticket data specified by the management ID from a data area assigned to a member,
The pair of the searched electronic ticket data and the management ID is stored in the data area indicated by the pointer corresponding to the member ID included in the transfer request among the pointers registered in the member management DB. Stored by the storage means ,
Second transmission means, the member ID is transmitted from the second user terminal, the received request the second the second user terminal from the user terminal includes the management ID acquired from the data area Electronic ticket data paired with the management ID among the electronic ticket data stored in the data area assigned to the member ID of the member who uses the second user terminal when sent To the user terminal,
The electronic ticket sales / distribution server is
A sales / distribution DB in which the ticket ID of the electronic ticket data sold / distributed is registered;
A second search for searching whether or not the same ticket ID as the ticket ID included in the inquiry request is registered in the sales / distribution DB when an inquiry request is sent from the electronic ticket distribution server Means,
And a third transmission means for returning an inquiry OK to the electronic ticket distribution server when the same ticket ID as the ticket ID included in the inquiry request is registered in the sales / distribution DB. Electronic ticket management / distribution system. The electronic ticket management / distribution system according to claim 1,
The electronic ticket management DB includes a data area for non-members in addition to a data area for each member.
When the electronic ticket distribution server receives a transfer request for non-members including a management ID of electronic ticket data to be transferred from the user terminal, the first search means asks a member who uses the user terminal. Search the electronic ticket data specified by the management ID from the allocated data area,
Pairs of the management ID and the retrieved electronic ticket data, and said management temporary ID associated with the ID and temporary password, the data area for non-member provided in the electronic ticket management DB Stored by storage means ,
When authentication information including a temporary ID and a temporary password is sent from the second user terminal, the first search means uses the management ID managed in association with the temporary ID and the temporary password. Search the specified electronic ticket data from the non-member data area,
The electronic ticket management / distribution system, wherein the fourth transmission means transmits the searched electronic ticket data to the user terminal. The electronic ticket management / distribution system according to claim 1,
A fifth transmitting means transmits distribution history data including the ticket ID of the electronic ticket data transferred to another member and the member ID of the transfer destination to the electronic ticket sales / distribution server;
The electronic ticket vending and distribution server, in addition to the ticket ID, including the sales and distribution history DB which member ID of the member which became a transferee electronic ticket data specified by the ticket ID is Ru is registered by the registration means,
The electronic ticket sales / distribution server assigns the member ID of the transfer destination corresponding to the ticket ID in the sales / distribution history DB identical to the ticket ID of the distribution history data sent from the electronic ticket distribution server to the distribution history. An electronic ticket management / distribution system comprising updating means for updating to a member ID of a data transfer destination . The electronic ticket management / distribution system according to claim 1,
When a withdrawal request including a management ID of electronic ticket data is sent from the second user terminal to the electronic ticket distribution server, the first search means is assigned to a member who uses the user terminal. Electronic ticket management characterized in that the electronic ticket data specified by the management ID is searched from the data area, and the sixth transmission means transmits the searched electronic ticket data to the user terminal.・ Distribution system. The electronic ticket management / distribution system according to claim 1,
A payment server that performs payment processing is connected to the network,
The seventh transmission means of the electronic ticket distribution server sends a chargeable transfer request including a management ID of electronic ticket data to be transferred and a member ID of a transfer destination member of the electronic ticket data from the first user terminal. And that there is electronic ticket data to be transferred for a fee to the user terminal of the transferee member,
The first search means of the electronic ticket distribution server, when notified from the settlement server that payment by the transferee member has been completed, data assigned to the member using the user terminal Search the electronic ticket data specified by the management ID in the paid transfer request from the area,
The pair of the searched electronic ticket data and the management ID is stored in the data area indicated by the pointer corresponding to the member ID included in the transfer request among the pointers registered in the member management DB. An electronic ticket management / distribution system stored by the storage means . The electronic ticket management / distribution system according to claim 1,
A marketplace portal for notifying the electronic ticket data sellers and successful bidder user terminals that the electronic ticket data has been successfully bid, and payment from the successful bidder of the electronic ticket data to the payment service provider. And a payment server for notifying the first user terminal of the seller of the electronic ticket to a network,
The electronic ticket distribution server is
When a member ID is sent from the first user terminal and a successful bid storage request including electronic ticket data for which a successful bid is made is sent, the first transmission means sends an inquiry request including the ticket ID of the electronic ticket data. Is transmitted to the electronic ticket sales / distribution server, and when the inquiry OK is returned from the electronic ticket sales / distribution server in response to the inquiry request, the generation means performs management for uniquely identifying the electronic ticket data. An ID is generated, and the pair of the generated management ID and the electronic ticket data is stored by the storage means in a data area assigned to a member ID of a member who uses the user terminal,
When the successful bid transfer request including the ticket ID of the electronic ticket data to be transferred from the user terminal to the successful bidder and the member ID of the successful bidder is sent, the eighth transmission means sends the successful bidder to the user terminal of the successful bidder. , Transmitting transfer electronic ticket information indicating what kind of electronic ticket data is indicated by the ticket ID,
When a receipt request is sent from the user terminal that is the destination of the transfer electronic ticket information, the ninth transmission means transmits electronic ticket data corresponding to the transfer electronic ticket information to the user terminal. Electronic ticket management / distribution system. When an inquiry request is sent from a user terminal used by a member, an electronic ticket distribution server, a sales / distribution DB in which a ticket ID of electronic ticket data sold / distributed is registered, and the electronic ticket distribution server, Search the sales / distribution DB and return a query OK to the electronic ticket distribution server on condition that the same ticket ID as the ticket ID included in the inquiry request is registered in the sales / distribution DB. An electronic ticket distribution server that is a component of an electronic ticket management / distribution system composed of an electronic ticket sales / distribution server,
A member management DB in which a member ID and a pointer indicating a data area assigned to the member specified by the member ID are registered;
When the member ID is sent from the first user terminal and the storage request including the electronic ticket data is sent, the inquiry including the ticket ID of the electronic ticket data is performed to check the validity of the electronic ticket data. Transmitting means for transmitting a request to the electronic ticket sales / distribution server;
A generating unit that generates a management ID for uniquely identifying the electronic ticket data when an inquiry OK is returned from the electronic ticket sales / distribution server in response to the inquiry request;
Each member has a data area, and a pair of the generated management ID and the electronic ticket data is stored in a data area assigned to a member ID of a member who uses the first user terminal. An electronic ticket management DB stored by the means ;
When a transfer request including a management ID of electronic ticket data to be transferred from the first user terminal and a member ID of a transferee member of the electronic ticket data is sent to the member using the user terminal Search means for searching electronic ticket data from the assigned data area based on the management ID,
The pair of the searched electronic ticket data and the management ID is stored in the data area indicated by the pointer corresponding to the member ID included in the transfer request among the pointers registered in the member management DB. Stored by the storage means ,
Second transmission means, the member ID is transmitted from the second user terminal, the received request the second the second user terminal from the user terminal includes the management ID acquired from the data area Electronic ticket data paired with the management ID among the electronic ticket data stored in the data area assigned to the member ID of the member who uses the second user terminal when sent Is transmitted to the user terminal. In the electronic ticket distribution server according to claim 7 ,
When a withdrawal request including a management ID of electronic ticket data is sent from the user terminal, the second search means is specified by the management ID from the data area assigned to the member using the user terminal. The electronic ticket distribution server, wherein the third transmitting means transmits the searched electronic ticket data to the user terminal.

Images