JP2004038889A - Service providing system and service providing method - Google Patents

Abstract

An object of the present invention is to reduce the trouble of building link information and a cooperative relationship prepared for linking service providers, increase the range of service providers that can be selected by the user, and improve the convenience of the user.
Kind Code: A1 A user reads information based on information on a product included in a ticket corresponding to a desired ID (code), information on a service, and storage destination information of a procedure file included in the ticket. And a system that can obtain service provision content information obtained based on the access destination address of the service provider included in the ticket, the ticket can include an ID different from the ID, It is determined whether the ticket corresponding to the requested ID includes a different ID (S38). If the ticket includes a different ID, the different ID is used as a new search key (S40), and the ticket search is performed. This is repeated (S36).
[Selection] Fig. 8

Description

[0001]
TECHNICAL FIELD OF THE INVENTION
The present invention relates to a service providing system that provides a service based on a request from a service user (user), and a service providing method executed by the service providing system.
[0002]
[Prior art]
As a means for the user to obtain a service of interest, providing one service and related services together (for example, providing a travel application and a travel insurance application at the same time; It is common practice to serve French wine in a restaurant). In recent business transactions via the Internet, hyperlinks to websites related to related services have been embedded in advance when creating a website related to one service in order to link multiple industries. I have. For example, a hyperlink to a homepage of an insurance company for applying for travel insurance is embedded in a homepage for applying for travel.
[0003]
[Problems to be solved by the invention]
However, according to the conventional method of providing services to users by cross-linking services of a plurality of industries, a service provider needs to prepare a relationship between a plurality of linked services in advance as a URL link, or It was necessary to partner with major service providers (eg, Yahoo and Nifty) that provide the services. In addition, even if these links are prepared and alliances with other service providers are provided, the types and ranges of services that can be provided must be somewhat fixed, and users can receive the services. There was a problem that service options were limited.
[0004]
In order to avoid this problem, it is common for users to search for relevant service providers by themselves using a search engine on the Internet. However, this method has a problem that it takes time for the user to find the most suitable service provider from a large number of search results.
[0005]
SUMMARY OF THE INVENTION The present invention has been made to solve the above problems, and an object of the present invention is to provide a service providing system and a service providing method for providing services to a user by cross-linking a plurality of industries to provide service to a service provider. An object of the present invention is to reduce the trouble of building link information and a cooperative relationship, and to broaden the range of service providers that can be selected by the user, thereby improving the convenience of the user.
[0006]
[Means for Solving the Problems]
In order to achieve the above object, a service providing system according to the present invention, as described in claim 1, includes a procedure file storing access method information for connecting to a service, a code assigned to a product, Stores the access destination address of the service provider that provides the service related to the product, the storage location information of the procedure file, and the ticket including both or one of the information related to the product and the service related to the product. Ticket storing and managing means for managing, based on a code and a ticket request requested by a user, search controlling means for causing the ticket storing and managing means to search for a ticket corresponding to the code, and a ticket obtained by the search Reads the storage location information of the procedure file included in the Access method information reading means for reading access method information from the procedure file, and reading an access destination address of a service provider included in the ticket obtained by the search, and providing a service based on the access destination address of the service provider. A service information acquisition unit for requesting service provision content information from a provider and acquiring the service information according to an access method stored in a procedure file relating to the service; information relating to the product included in the ticket; information relating to the service; Presentation means for presenting the obtained access method information and the acquired service providing content information to the user, wherein the ticket includes a code different from the code as the information on the product or the information on the service. Is possible, the search The control means determines whether the ticket obtained by the search includes a different code, and when the ticket includes a different code, further executes a search for a ticket corresponding to the different code in the ticket storage management means. It is characterized by making it.
[0007]
In the above service providing system, there is a procedure file in which access method information for connecting to the service is stored, and the ticket storing and managing means stores the code assigned to the product, the service provider providing the service related to the product. , And stores and manages a ticket that includes both or one of the access destination address and the storage destination information of the procedure file, and information about a product and information about a service related to the product. Here, when the user requests the ticket by the code and the ticket request, the search control unit causes the ticket storage management unit to execute the search for the ticket corresponding to the code based on the code and the ticket request. Here, the ticket storage management means searches for a ticket corresponding to the code, so that a ticket is obtained as a search result.
[0008]
Then, the access method information reading means reads the storage location information of the procedure file included in the ticket obtained by the search, and reads the access method information from the procedure file based on the storage location information. Further, the service information obtaining means reads out the access destination address of the service provider included in the ticket obtained by the search, and requests the service provider for service provision content information based on the access destination address of the service provider. , According to the access method stored in the procedure file for the service.
[0009]
Further, the presentation control means presents to the user the information on the product included in the ticket, the information on the service, the read access method information, and the acquired service providing content information. Thus, the user can obtain information on the product included in the ticket corresponding to the desired code, information on the service, access method information read based on the storage location information of the procedure file included in the ticket, and the ticket The service providing content information acquired based on the access destination address of the service provider included in (1) can be obtained.
[0010]
According to the present invention, in such a service providing system, the ticket can include a code different from the code as the information on the product or the information on the service, and the search control unit can output the ticket ( It is determined whether or not the ticket (corresponding to the code requested by the user) includes a different code. If the ticket includes a different code, the ticket storage management unit is further searched for a ticket corresponding to the different code. Let it.
[0011]
Here, similarly to the above, a new ticket is obtained as a search result by the ticket storage management means searching for a ticket corresponding to the different code. Then, the access method information reading means reads the storage location information of the procedure file included in the new ticket obtained by the search, and reads the access method information from the procedure file based on the storage location information. Further, the service information obtaining means reads out the access destination address of the service provider included in the new ticket obtained by the search, and provides the service provider with the service provision content information based on the access destination address of the service provider. Request and obtain according to the access method stored in the procedure file for the service. Further, the presentation control means presents to the user the information on the product included in the new ticket, the information on the service, the read access method information, and the acquired service providing content information.
[0012]
In this manner, a new ticket corresponding to the different code included in the ticket is obtained, and a new product (for example, a product linked with the original product) is obtained from the new ticket information in the same manner as described above. ), Information on a new service (for example, a service cooperating with the original service), access method information thereof, and service provision content information thereof.
[0013]
By configuring one ticket to include a different code in this way, a search for a ticket using the different code, information on a new product included in a new ticket obtained by the search, and a new service The information, the access method information, and the service providing content information can be presented to the user. As a result, link information to be prepared for linking a plurality of service providers and the trouble of constructing an alliance can be reduced, and the range of service providers that can be selected by the user is expanded. Therefore, user convenience can be achieved. The “code” in the present invention includes, for example, a product code for identifying a product, a code relating to a place such as a place where a product is sold or a place where a service is provided, and a moving image / still image that advertises and introduces the contents of the product or service. Includes the code of an image file such as a picture.
[0014]
Further, the service providing system according to the present invention, as described in claim 2, a request receiving means for receiving a code and a ticket request requested by the user together with the identification information of the user, a user's preference information and service usage User information storage means for storing user information including information in association with user identification information, wherein the presentation control means includes a user corresponding to the user identification information obtained by reception by the request reception means. Reading information from the user information storage means, selecting a service provider based on the user information and the service provision content information, and presenting service provision content information and access method information relating to the selected service provider to the user; It is desirable that
[0015]
In this case, the service providing system includes a user information storage unit that stores user information including user preference information and service use information in association with the user identification information, and the request receiving unit is requested by the user. The code and the ticket request are received together with the identification information of the user. The presentation control unit reads user information corresponding to the user identification information obtained by the request reception unit from the user information storage unit, selects a service provider based on the user information and the service provision content information, and selects the service provider. The service providing content information and the access method information relating to the provided service provider are presented to the user.
[0016]
For this reason, the service provider is selected based on the user information including the user's preference information and the service use information and the service provision content information, so that the service provider of the service that the user is supposed to show interest in is provided. Can be selected more reliably, and the service providing content information and the access method information relating to the selected service provider can be presented to the user. As a result, as a service provider, it is possible to more reliably present the contents of service provision to a user who is likely to become a purchaser of a product or a user of the service, and for the user, his or her interests and interests are Information on high-quality products and services can be obtained more reliably, and provision of highly useful services is realized.
[0017]
Further, in the service providing system according to the present invention, as set forth in claim 3, the presentation control means performs a search by a search engine using a keyword included in the information on the product or the information on the service as a search key. Preferably, the link information obtained by the search is presented to the user.
[0018]
In this case, a search is performed by a search engine using a keyword included in the information about the product or the service in the ticket as a search key, and the user can obtain link information obtained by the search. Can eliminate the trouble of performing a search by a search engine using a keyword as a search key, thereby reducing the burden on the user.
[0019]
By the way, the invention relating to the service providing system can be regarded as the invention of the following service providing method. Since these inventions have the same technical idea, they have similar functions and effects.
[0020]
That is, according to the service providing method of the present invention, as described in claim 4, a procedure file storing access method information for connecting to a service, a code assigned to the product, a service related to the product, Storage management means for storing and managing a ticket including an access destination address of a service provider that provides a service, storage destination information of the procedure file, and / or information on the product and / or service related to the product. A service providing method that is executed by the service providing system, comprising: causing the ticket storage management unit to execute a search for a ticket corresponding to the code based on the code and the ticket request requested by the user. Search control step and procedure file included in the ticket obtained by the search An access method information reading step of reading storage location information and reading access method information from the procedure file based on the storage location information, and reading an access destination address of a service provider included in the ticket obtained by the search; A service information obtaining step of requesting service providing content information from a service provider based on an access destination address of the service provider, and obtaining the service information according to an access method stored in a procedure file related to the service; and A presentation control step of presenting information on the product, information on the service, read access method information, and acquired service providing content information to the user, wherein the ticket is information on the product or on the product. For information on related services, see It is possible to include a code different from the code, in the search control step determines whether the ticket obtained by the search includes a different code, if the ticket includes a different code, the different code It is characterized by causing the ticket storage management means to further execute a search for a corresponding ticket.
[0021]
Further, in the service providing method according to the present invention, as set forth in claim 5, the service providing system receives a code and a ticket request requested by a user together with identification information of the user, request receiving means, User information storage means for storing user information including taste information and service usage information in association with user identification information, wherein in the presentation control step, the user identification obtained by reception by the request reception means is provided. Reading the user information corresponding to the information from the user information storage means, selecting a service provider based on the user information and the service providing content information, and providing service providing content information and access method information relating to the selected service provider; It is desirable to present it to the user.
[0022]
Further, in the information provision control method according to the present invention, as described in claim 6, in the presentation control step, a search is performed by a search engine using a keyword included in the information on the product or the information on the service as a search key. And presenting the link information obtained by the search to the user.
[0023]
BEST MODE FOR CARRYING OUT THE INVENTION
Hereinafter, embodiments of the present invention will be described with reference to the drawings. Hereinafter, the “code” according to the present invention is referred to as “ID”. The ticket is information in which information of a product corresponding to the ID, an address of a service provider related to providing a service related to the product, an access method, a service type, and the like are described. It will be described later.
[0024]
[Configuration of service providing system]
FIG. 1 shows an overall configuration of a service providing system according to the present embodiment. As shown in FIG. 1, the service providing system according to the present embodiment is configured by the following components connected or connectable to the network 120. That is, the service providing system newly provides a terminal 100 such as a personal computer (PC), a portable information terminal (Personal Digital Assistant: PDA), or a mobile phone of a user who receives the service, and a terminal 100 to which an ID is given. ID issuing requester (for example, a company that develops or manufactures a new product or obtains a product by purchasing, etc.) 102 that issues an ID issuing request, a group 103 of ID issuing organizations that issue IDs, a ticket A ticket registrant 104 who requests registration, a ticket management unit 105 that performs storage management and retrieval of tickets, and a procedure processing execution unit that presents service provider candidates to a user through a service and acts on behalf of the service provider 106, a procedure file 107, and sales, repair, and information provision. A service provider 108 that provides a service performed via the click, the personal information 109 is configured to include a search engine 110, such as Yahoo (yahoo) and Google (google).
[0025]
Among them, the ID issuing institution group 103 is based on an ID issuance management institution 1031 that manages and manages the entire ID issuance rule of the ID issuing institution group 103 and an ID issuance rule given by the ID issuance management institution 1031. It includes a plurality of ID issuing organizations 1032 and 1033 that issue IDs.
[0026]
The ticket management unit 105 includes a transmission / reception unit 1051 that receives a ticket registration request to the ticket management unit 105 and transmits a search result, a storage unit 1052 that is a huge database for storing tickets, and a search unit that searches for tickets. 1053.
[0027]
The procedure processing execution unit 106 includes a ticket filtering unit 1061 that selects a ticket relating to a service provider that the user can obtain from the ticket search result (a plurality of tickets) based on the ID and that can be processed by the user, and stores a procedure file described in the ticket. A procedure file reading unit 1063 for reading the procedure file of the ticket from the destination (that is, the storage location information of the procedure file 107 regarding the access method information to the service provider (also referred to as a service entity access protocol storage location pointer)); And a procedure processing instruction unit 1062 for instructing a procedure.
[0028]
The procedure file 107 includes a protocol used for the procedure and essential information (for example, when the protocol is determined by the automobile industry, a cryptographic communication method generally used on the Internet, a unique procedure protocol, and information necessary for the procedure. Is described, and is open to anyone via the network 120 for reference. This allows new service providers to select the most appropriate procedural process from a variety of published procedural processes, and use the procedure file simply by describing the storage location of the procedure file in the ticket. Become. It should be noted that the procedure file 107 can authenticate a person requesting information and take measures to appropriately restrict reference to the information as needed in order to ensure security.
[0029]
The personal information 109 used in the processing described later includes names, addresses, hobbies and preferences, a list of possessed items, types of processing that can be performed, and access histories and usage histories to various service providers. The personal information 109 may be held by the user in the terminal 100, may be held in a form such as a Web page in the network, and may refer to a service provider. It may be in the procedure processing execution unit 106 that mediates the procedure.
[0030]
In addition, the object 101 to which an ID has been assigned is a code (combination of numbers and characters) that has been assigned an ID with a barcode, a two-dimensional barcode, an RF-ID, an infrared tag, or the like (a bottle, paper, or the like). Physical objects and electronic objects such as audio files and image files).
[0031]
[Various processes related to service provision]
Hereinafter, various processes related to service provision performed by the service providing system will be described.
[0032]
[ID issuing organization certification processing and ID issuing processing]
FIG. 2 shows an ID issuing organization certification process and an ID issuing process. As shown in FIG. 2, an organization that wishes to apply for certification of an ID issuing organization applies to the ID issuing management organization 1031 for certification to become an ID issuing organization. The ID issuing management organization 1031 examines whether the requesting organization can sufficiently comply with the ID issuing rules and other rules set by the ID issuing management organization 1031 and, if the conditions are satisfied, the applying organization. Is recognized as an ID issuing organization, and an ID issuing rule that can be issued by the applying organization is notified. As a specific example of the ID issuance rule, "the ID assigned by the ID issuing institution A is always prefixed with a character string of JAN" or "the ID assigned by the ID issuing institution B is always prefixed with ISBN. Assign a character string ".
[0033]
Upon receiving an ID issuance request from the ID issuance requester 102, the authorized ID issuance organizations 1032, 1033, etc. examine (check) the name, address and reliability of the ID issuance requester 102, and determine a predetermined condition. If it satisfies, the ID is issued according to the ID issuance rule set by the ID issuance management organization 1031, and the ID is notified to the ID issuance requester 102. By observing such issuance rules, it is possible to prevent the same ID from being duplicated, and to manage various conventional ID systems as non-overlapping code systems.
[0034]
FIG. 3 is a diagram illustrating an ID issuing process that avoids duplication of IDs without performing the ID issuing institution qualification process. As shown in FIG. 3, the ID issuing organization 1032 and the like first make an ID issuance request to the ID issuance management organization 1031 every time an ID issuance request is received from the ID issuance requester 102. The ID issuance management organization 1031 examines whether the ID issuance organization 1032 or the like that has issued the ID issuance request can comply with the ID issuance rules and other rules determined by the ID issuance management organization 1031. A new ID is issued to the ID issuing organization 1032 or the like which has issued the ID issuance request, and the ID is notified. The ID issuing organization 1032 or the like that has received the notification notifies the ID issuing requester 102 of the ID, whereby the ID issuing requester 102 can obtain the ID.
[0035]
Note that the ID issuance management institution 1031 described in FIG. 3 is a form corresponding to an individual ID issuance request when all ID issuances can be managed and operated. Reference numeral 1031 denotes a mode for issuing an ID.
[0036]
[Ticket registration / update processing]
FIG. 4 is a diagram illustrating a ticket registration / update process performed by the ticket management unit 105. As shown in FIG. 4, the ticket management unit 105 receives a ticket registration request from the ticket registrant 104. In general, a ticket registration request is made by a service provider (specifically, an import agency that handles wine with ID = 1224 assigned by a wine maker) for a product (product) to which an ID is assigned. Conceivable. However, the ticket may be registered as a third party by an agent (for example, a sales promotion planning contractor commissioned by the import agency). The ticket registrant 104 updates the ID, ticket, registrant information (for example, name, address on the network, etc.) and the contents of the ticket in the ticket management unit 105, and updates the ticket received when the ticket was previously registered. An identification number (hereinafter referred to as “ticket ID”) is transmitted. The transmission / reception unit 1051 examines the received registrant information, and stores the ticket in the storage unit 1052 when the condition is satisfied. The storage unit 1052 checks the content of the ticket, and checks whether the format of the ticket is correct, whether the content described in the ticket is correct, and the like. If there is no problem, the ticket is stored in the storage unit 1052. Then, the storage unit 1052 transmits to the ticket registrant 104 the ticket storage completion notification indicating that the storage of the ticket has been completed and the ticket ID of the stored ticket. This ticket ID is used again when the content of the ticket changes and is updated.
[0037]
[Ticket search processing and procedure processing]
Next, a ticket search process performed by the ticket management unit 105 and a procedural process performed by the procedural process execution unit 106 will be described with reference to FIG. The flow of individual processing will be described later with reference to FIGS. 8, 9, and 10.
[0038]
First, the user 100 that has acquired the ID from the object 101 to which the ID has been assigned transmits the ID, the ticket request (optimal service destination request) necessary for providing the service, and the user information to the procedure processing instruction unit of the procedure processing execution unit 106 1062. The procedure processing instructing unit 1062 searches the transmitting / receiving unit 1051 of the ticket managing unit 105 for the ID and the ticket request in order to search for “what is the received ID?” And “what services are associated with the ID?” And requester information (information about the procedure processing execution unit 106 including the procedure processing instruction unit 1062).
[0039]
The transmission / reception unit 1051 receives the ID, the ticket request, and the requester information, checks the requester information, and if there is no problem, transmits the ID and the ticket request to the search unit 1053. The search unit 1053 checks whether there is any problem such as inconsistency in the contents of the received ticket request, and transmits the ID and the ticket search request to the storage unit 1052 when there is no problem. The storage unit 1052 performs a ticket search process based on the received ID and the ticket search request, checks the expiration date of the ticket obtained by the search, and passes all tickets that satisfy the expiration date to the transmission / reception unit 1051 as search results. The ticket as a search result is passed to the procedure file reading unit 1063.
[0040]
The procedure file reading unit 1063 reads the procedure information from the procedure file 107 based on the procedure file storage destination information described in the ticket and transmits the procedure information to each of the received tickets to the procedure processing instruction unit 1062. Then, the procedure processing instruction unit 1062 determines whether or not the user 100 can perform a procedure based on the personal information 109 and the procedure information regarding the user 100 who made the ticket request, and determines from the received ticket Perform a procedural refusal check to select only procedural tickets.
[0041]
For the ticket determined to be procedural, the procedure processing instructing unit 1062 makes a service provider detailed inquiry request to the service provider 108, and provides the service detailed content information (for example, “French wine sales, inquiry ID, merchandise” Is expected to be delivered in about two months depending on the product, etc.) according to the access method stored in the procedure file 107 relating to the service.
[0042]
The above-described procedure processing execution unit 106 transmits the “ID, ticket request, and requester information to the transmission / reception unit 1051 of the ticket management unit 105, and makes a service provider detail inquiry request to the service provider 108. The process of receiving the service providing detailed content information "is referred to as a service providing destination candidate extracting process 501. The service providing candidate extraction processing 501 is repeatedly executed based on information (ID, comment on product, comment on service, etc.) described in the received ticket, thereby increasing the number of tickets acquired by the procedure processing instruction unit 1062. It becomes possible. A specific processing flow will be described later with reference to FIGS.
[0043]
Thereafter, the ticket filtering unit 1061 receives the ticket from the procedure processing instruction unit 1062, and narrows down the service providing destination selection candidates required by the user from the received tickets based on the personal information 109. For example, regarding the ticket searched by the wine ID, if the personal information of the user requested this time includes information such as “Tokyo resident” and “Hobby is overseas travel”, the ticket related to overseas travel and Tickets related to service providers in Tokyo are prioritized as top candidates. Then, the ticket filtering unit 1061 presents the selected candidate of the optimum service providing destination to the user 100. If there is a service that the user 100 has requested, the user 100 selects the service provider 108 of the service and makes a service processing execution request to the service provider 108. Then, a contract confirmation process necessary for providing a service such as user authentication is performed between the user 100 and the service provider 108, and the user 100 receives the service.
[0044]
[Ticket structure]
Here, the structure of the ticket will be described with reference to FIG. The ticket includes the following information (1) to (13).
[0045]
That is, (1) an ID which is a string of numeric characters specifying that the ID is assigned. (2) A connection destination of a service provider that provides information and services related to the ID (service provision destination (service entity pointer): for example, an IP address or a URL on a network). (3) Destination where service procedure information describing an access method for connecting to a service is stored (service entity access protocol storage destination pointer: for example, IP address, URL, file name on a network, etc.). (4) Ticket type. As a specific example, for example, “primary (primary)” indicating a ticket that can be issued only by the ID issue requester indicating what the ID is assigned, and issued to provide a service related to the item "Secondary". (5) An object category, which is information for classifying what the ID is assigned to. (6) An object location (ObjectLocation) which is information indicating where the object to which the ID is assigned is located. (7) An object comment (Object Comments) in which various information on an object to which an ID is assigned is described. (8) A service category (Service Category) which is information indicating what kind of service is provided by a service related to an object to which an ID is assigned. (9) A service location (Service Location), which is information indicating in what place or area a service related to an object with an ID is provided. (10) A service comment (Service Comments) in which various information related to service provision related to an object to which an ID is assigned is described. (11) Information about the registrant of the ticket. (12) Expiration date for which the ticket is registered. (13) Permission information indicating a searcher who can browse and search for tickets.
[0046]
Among the information described in the ticket, the information of (2) and (3) is characterized in that it has a structure having only a pointer so as to be compatible with various services, and (4) (5) ( The information of (6), (7), (8), (9), and (10) is characterized in that it has a structure that enables flexible search and can create various services. Also, the information of (11) and (12) is characterized by having a minimum structure for ensuring the validity of the ticket, and the information of (13) is characterized in that information disclosure can be restricted. It is characterized by having a structure. The description of the information of (1), (2), (3), (4), (11), and (12) is indispensable, but the description of other information may or may not be provided. When there is no description of information, it is described as “NULL”.
[0047]
[Ticket registration update process flow]
Next, the flow of a ticket registration update process for registering and updating a ticket as described above will be described with reference to FIG.
[0048]
First, the ticket management unit 105 receives the ID, the ticket body, the ticket ID (NULL for the first registration) and the registrant information (S11 in FIG. 7), and based on the received ticket registrant information, the ticket registrant. Is evaluated (S12). Various methods can be used for the reliability evaluation here, such as a method using an account and a password, a method of changing a password over time, a method of notifying a password to an inquired e-mail address, and the like. Evaluate ticket registrants by combining one or more of them.
[0049]
If it is determined in S12 that the ticket cannot be trusted, the received ticket is discarded (S18), and the registration request source is notified that the ticket storage has failed (S19), and the process ends. On the other hand, if it is determined in S12 that the ticket is reliable, it is next determined whether or not the contents of the ticket are correct (S13). The process of determining whether the content of the ticket is correct is performed by checking whether the structure of the ticket conforms to a prescribed structure, whether essential items to be described in the ticket are described, and the like.
[0050]
If the contents of the ticket are not correct in S13, the received ticket is discarded (S18), and the registration request source is notified that the ticket storage has failed (S19), and the process ends. On the other hand, if the content of the ticket is correct in S13, a process (ticket ID check process) of determining whether a ticket having the same ID, ticket ID, and the same registrant information is already stored in the ticket management unit 105 is performed. Perform (S14). Thus, it is determined whether to register the ticket or update the ticket.
[0051]
If the ticket having the same ID, ticket ID, and the same registrant information is not stored in the ticket management unit 105 in S14, it is determined that the ticket is registered, and the ticket is stored in the storage unit 1052 (S16). Then, the notification that the storage of the ticket is completed and the ticket ID related to the stored ticket are notified to the ticket registrant 104 (or the ticket renewer) (S17), and the process ends.
[0052]
On the other hand, if the ticket having the same ID, ticket ID, and the same registrant information is stored in the ticket management unit 105 in S14, it is determined that the ticket has been updated, and the received ticket is stored in the already stored ticket. The new ticket is overwritten and accumulated (S15). Then, the notification that the storage of the ticket is completed and the ticket ID related to the stored ticket are notified to the ticket registrant 104 (or the ticket renewer) (S17), and the process ends. At this time, it is determined whether or not there is a ticket having the same ID and the same item for all tickets. If the same ticket is found, it is better not to store the ticket, so that the storage capacity of the database is more effective. It is effective to use for
[0053]
[Ticket search process flow]
Next, the flow of ticket search processing in the ticket storage unit and the procedure processing execution unit will be described with reference to FIG. Here, since the subject of the processing has been described above with reference to FIG. 5, it is assumed that the subject is generically represented by the procedure processing execution unit 106 or the ticket management unit 105 instead of the ticket filtering unit 1061 or the like.
[0054]
First, the procedure execution unit 106 receives an ID, a ticket request, and user information from the user 100 (S31 in FIG. 8). Then, the procedure execution unit 106 performs a process of determining whether the user information is correct (S32). If it is determined that the user information is incorrect, the process is immediately interrupted, the user is notified that the process has been interrupted (not shown), and the process is terminated.
[0055]
On the other hand, if it is determined in S32 that the user information is correct, the number of times N representing the number of executions of the service provider candidate extraction process 501 in FIG. 5 is reset to zero “0” (S33), and the ID, ticket request, request The user information is transmitted to the ticket management unit 105 (S34). Then, 1 is added to the number of times N (S35), and a service providing destination candidate extraction process 501 is performed (S36). The service provider candidate extraction processing 501 will be described in detail with reference to FIG. After the service providing destination candidate extraction processing 501 is completed, the ticket searched by the ID and the service providing detailed information on the ticket are received (S37).
[0056]
Then, it is determined whether or not the ID is described in the “Object Comments” and “Service Comments” items of the received ticket (S38). If the ID is not described, a personal information reference process is performed (S41). If the ID is described, it is determined whether or not the number N is less than a predetermined number α of times of execution of the service provider candidate extraction process 501 (S39). If the number N is greater than or equal to the execution number limit α, personal information reference processing is performed (S41). On the other hand, if the number of times N is less than the execution number limit number α, the ID described in the ticket is set as the search target ID (S40), and the ID, ticket request, and requester information are transmitted to the ticket management unit 105 again. (S34). By repeating the process of searching for a ticket again by replacing the ID of the search target in this way, it becomes possible to provide a cross-sectional service in cooperation with various service providers.
[0057]
In the personal information reference process in S41, the personal information 109 refers to personal information such as the user's situation, user's preference, purchasing tendency, and service usage tendency. Then, based on the personal information, the optimum service provider selection process for the user is performed (S42), and the selected service provider candidate performs the optimum service provider presenting process notified to the user terminal (S42). S43).
[0058]
Thereafter, the user determines whether or not to select a service providing destination from the presented service providing destinations, and if so, transmits a service processing execution request. Therefore, in S44, it is determined whether or not a service providing destination has been selected based on whether or not a service processing execution request from the user has been received. If not selected, the process is immediately interrupted, the user is notified that the process has been interrupted (not shown), and the process is terminated.
[0059]
On the other hand, when the service processing execution request from the user is received and it is determined that the service providing destination has been selected, the connection is established with the selected service providing destination (S45), and the process ends. As a result, the service is provided from the service providing destination to the user.
[0060]
Next, as a modification of FIG. 8, a flow of processing in which a part of the search processing is performed by a search engine 110 such as Yahoo or Google on the network will be described with reference to FIG. This process using the search engine 110 is an effective process when the number of tickets as a search result is small.
[0061]
First, the procedure execution unit 106 receives an ID, a ticket request, and user information from the user 100 (S51 in FIG. 9). Then, the procedure processing execution unit 106 performs a process of determining whether the user information is correct (S52). If it is determined that the user information is incorrect, the process is immediately interrupted, the user is notified that the process has been interrupted (not shown), and the process is terminated.
[0062]
On the other hand, if it is determined in S52 that the user information is correct, the ID, the ticket request, and the requester information are transmitted to the ticket management unit 105 (S53), and the service provider candidate extraction processing 501 is performed (S54). The service provider candidate extraction processing 501 will be described in detail with reference to FIG. After the service providing destination candidate extraction processing 501 is completed, the ticket searched by the ID and the service providing content detailed information related to the ticket are received (S55).
[0063]
The search engine 110 performs a search using the comments described in the “Object Comments” and “Service Comments” items of the received ticket as search keys (S56), and performs personal information reference processing (S57). In S57, the personal information 109 refers to personal information such as the situation of the user, the user's preference, the purchase tendency, and the service use tendency. Then, on the basis of the personal information, a service providing destination optimum for the user is selected (S58).
[0064]
The ticket selected here is searched by the search engine 110 by using the comments described in the “Object Comments” and “Service Comments” items of the ticket as search keys (S59). As described above, in order to bring the accuracy of the hyperlink of the service providing destination closer to that required by the user, it is more effective to perform the process on the selected ticket. Then, the candidate of the service providing destination selected in S58 and the hyperlink obtained by the search by the search engine 110 are presented to the user terminal (S60).
[0065]
Thereafter, the user determines whether or not to select a service providing destination from the presented service providing destinations, and if so, transmits a service processing execution request. Therefore, in S61, it is determined whether or not a service providing destination has been selected based on whether or not a service processing execution request from the user has been received. If not selected, the process is immediately interrupted, the user is notified that the process has been interrupted (not shown), and the process is terminated.
[0066]
On the other hand, when the service processing execution request from the user is received and it is determined that the service providing destination is selected, the connection is made with the selected service providing destination (S62). As a result, the service is provided from the service providing destination to the user.
[0067]
In this way, when the number of ticket searches is small, by effectively using the search engine 110, it is possible to detect and extract even a service for which a ticket is not registered as a candidate for a service providing destination. Become.
[0068]
[Flow of service provider candidate extraction processing]
Next, the flow of service provider candidate extraction processing will be described with reference to FIG.
[0069]
The procedure processing instruction unit 1062 in the procedure processing execution unit 106 transmits the ID, the ticket request, and the requester information to the ticket management unit 105. At this time, if the service type requested by the user is known, the service type is transmitted to the ticket management unit 105, so that the search result of the ticket can be narrowed down in advance.
[0070]
The transmission / reception unit 1051 of the ticket management unit 105 receives the ID, the ticket request, and the requester information from the procedure processing instruction unit 1062 (S71 in FIG. 10), and determines whether the requester information is correct (S72). If it is determined that the requester information is not correct, the process is immediately interrupted, and the fact that the process has been interrupted is notified to the requesting procedure processing execution unit 106 (not shown), and the process is terminated.
[0071]
On the other hand, if the requester information is determined to be correct, the ID and the ticket request are transmitted to the search unit 1053 (S73). The search unit 1053 checks whether there is any problem such as inconsistency in the received ticket request, and determines whether the content of the ticket is correct (S74). If the contents of the ticket are not correct, the process is immediately interrupted, and the fact that the process has been interrupted is notified to the requesting procedure processing execution unit 106 (not shown), and the process is terminated.
[0072]
If the content of the ticket is correct, the search unit 1053 transmits the ID and the ticket search request to the storage unit 1052. The storage unit 1052 performs a ticket search process based on the received ticket search request (S75). If the service type requested by the user is specified in advance as a search key, a filtering search is performed based on the service type information, and a ticket extraction process is performed (S76).
[0073]
Then, it is determined whether or not there is a ticket obtained by the search (S77). If there is no ticket, the process is immediately interrupted and the fact that the process is interrupted is notified to the requesting procedure processing unit. The notification (not shown) terminates the processing. On the other hand, if there is a ticket, processing for checking the expiration date of the ticket is performed (S78), and all the tickets satisfying the expiration date are passed from the transmission / reception unit 1051 to the procedure file reading unit 1063 as search results.
[0074]
The procedure file reading unit 1063 performs a process of reading each received ticket (S79), and performs a procedure file reading process (S80) to acquire the procedure information. Then, it is determined whether or not there is a next ticket that has not been subjected to the procedure file reading process (S81). If there is an unprocessed ticket, the reading process (S79) is performed again, and the procedure file reading process (S80) is performed. Do.
[0075]
When there is no next ticket (when the procedure files of all tickets have been read), the procedure processing execution unit 106 determines whether the user 100 who made the ticket request can perform the procedure based on the personal information 109. Thus, only the procedural tickets are selected (the user performs a procedural ticket selection process that can be used) (S82).
[0076]
Then, the user determines whether there is a procedural ticket (S83). If it is determined that there is no procedural ticket, the requester immediately suspends the process and informs that the process has been suspended. It notifies the procedure processing execution unit 106 (not shown) and terminates the processing.
[0077]
On the other hand, if there are any tickets that can be processed in S83, a process of reading out each ticket is performed (S84), and a service providing details inquiry process is performed (S85). Then, it is determined whether or not there is a next ticket that has not been subjected to the service provision content inquiry process (S86). If there is an unprocessed ticket, the ticket reading process (S84) is performed again. Processing is performed (S85).
[0078]
When there is no next ticket (when the service provision details inquiry process for all tickets has been completed), the process ends with each ticket and the service provision details information related to the ticket as a processing result.
[0079]
[Explanation of processing example]
Next, an example of processing will be described with reference to FIGS.
[0080]
Here, it is assumed that three tickets relating to wine (ID: JAN4901336479) are registered in the ticket management unit 105.
[0081]
When the user 100 looks at the object (wine) 101 to which JAN49013360479 has been assigned as an ID and makes a ticket request for a ticket whose ID is JAN4901336479, the ticket search process described above causes the ticket search process shown in FIG. 11A to FIG. One ticket is obtained as a search result.
[0082]
As shown in FIGS. 11A to 11C, JAN4901336479 is described in the ID columns of all three tickets. The procedure processing execution unit 106 refers to the ticket type and the service type from these tickets, and performs an optimum service providing destination presenting process to provide a service suitable for the user 100.
[0083]
FIG. 13 shows an example of the optimum service provision destination list displayed on the terminal of the user 100. In this example, as information relating to the requested ID (JAN4901336479), the information described in the primary ticket shown in FIG. 11A and the two secondary services shown in FIGS. 11B and 11C as services related to the ID. Information described on the ticket is also presented.
[0084]
That is, FIG. 13 shows a search ID, ObjectCategory information and Object Comments information of the primary ticket of FIG. 11A, service entity pointer information of the secondary ticket of FIG. 11B, and FIG. 11C. 2 shows service entity pointer information and service comments information of the secondary ticket shown in FIG.
[0085]
As described above, the service provider that provides the service related to the ID can realize the cooperation of the service provider only by registering the service as the service related to the ID in the ticket, and the link prepared by the service provider in advance It is possible to reduce the trouble of building information and partnerships. In addition, it is possible for the user to constantly change dynamically and to expand the range of service providers that can be selected.
[0086]
Next, it is assumed that one ticket related to wine (ID: JAN49013360479) and two tickets related to a place name (ID: Location-ID245699) are registered in the ticket management unit 105.
[0087]
When the user 100 looks at the object (wine) 101 to which JAN49013360479 has been given as an ID and makes a ticket request for the ticket whose ID is JAN4901336479, the ticket (ID column in FIG. JAN4901336479). In the Object Comments column of the ticket shown in FIG. 12A, Location-ID 245699 indicating a wine production area is described as an ID. Therefore, in the search processing performed by the procedure processing execution unit 106, the tickets in FIGS. 12B and 12C are further selected in addition to the tickets in FIG. The procedure processing execution unit 106 refers to the ticket type and the service type from these tickets, and performs an optimum service providing destination presenting process to provide a service suitable for the user 100.
[0088]
FIG. 14 shows an example of the optimum service providing destination list displayed on the terminal of the user 100. In this example, in addition to the information described in the primary ticket shown in FIG. 12A as information relating to the requested ID (JAN4901336479), the information described in the ticket shown in FIG. Has been presented. Here, based on the personal information 109 of the user 100, of the two tickets of FIGS. 12B and 12C, only the ticket shown in FIG. 12C is selected.
[0089]
That is, FIG. 14 shows a search ID, ObjectCategory information and Object Comments information of the primary ticket shown in FIG. 12A, and service entity pointer information and Service Comments information of the secondary ticket shown in FIG. 12C. It is shown.
[0090]
As described above, according to the present embodiment, it is possible to realize cooperation between service providers only by registering an ID related to the ID in the ticket, and construct link information and a partnership relationship prepared in advance by the service provider. The labor can be reduced. In addition, the range of service providers that can be dynamically changed and selected from the user can be expanded.
[0091]
【The invention's effect】
As described above, according to the present invention, by configuring one ticket to include a different code, a search for a ticket using the different code and a new ticket included in a new ticket obtained by the search are performed. It is possible to present to a user information about a new product, information about a new service, access method information, and service provision content information. As a result, link information to be prepared for linking a plurality of service providers and the trouble of constructing an alliance can be reduced, and the range of service providers that can be selected by the user is expanded. Therefore, user convenience can be achieved.
[Brief description of the drawings]
FIG. 1 is an overall configuration diagram of a service providing system according to an embodiment of the present invention.
FIG. 2 is a diagram for explaining an ID issuing organization certification process and an ID issuing process;
FIG. 3 is a diagram for explaining an ID issuing process of an ID issuing agency that avoids duplication of IDs without performing the ID issuing agency certification process.
FIG. 4 is a diagram illustrating a ticket registration / update process performed by a ticket management unit;
FIG. 5 is a diagram illustrating a ticket search process performed by a ticket management unit and a procedure process performed by a procedure process execution unit;
FIG. 6 is a diagram showing the structure of a ticket.
FIG. 7 is a flowchart of a ticket registration update process.
FIG. 8 is a flowchart of a ticket search process in a ticket storage unit and a procedure processing execution unit.
FIG. 9 is a flowchart of a process in which a part of the search process is performed by a search engine on a network.
FIG. 10 is a flowchart of a service providing destination candidate extracting process.
FIGS. 11A to 11C are diagrams illustrating an example of a search result of a ticket in which JAN4901336479 is described in an ID column.
12A is a diagram illustrating an example of a search result of a ticket in which JAN4901336479 is described in an ID column, and FIGS. 12B and 12C are diagrams illustrating a Location described in an Object Comments column of the ticket of FIG. It is a figure showing an example of the search result of the ticket obtained by having searched ID-245699 as a key.
FIG. 13 is a diagram illustrating an example of an optimum service providing destination list related to the search result of FIG. 11;
FIG. 14 is a diagram illustrating an example of an optimum service providing destination list related to the search result of FIG. 12;
[Explanation of symbols]
100: User terminal, 101: ID assigned, 102: ID issuing requester, 103: ID issuing organization group, 1031: ID issuing management organization, 1032, 1033: ID issuing organization, 104: Ticket registrant, 105: ticket management unit, 1051: transmission / reception unit, 1052: storage unit, 1053: search unit, 106: procedure processing execution unit, 1061: ticket filtering unit, 1062: procedure processing instruction unit, 1063: procedure file reading unit, 107 ... Procedure file, 108: service provider, 109: personal information, 110: search engine, 120: network, 501: service provider candidate extraction process.

Claims (6)

A procedure file that stores access method information for connecting to the service,
The code assigned to the product, the access address of the service provider that provides the service related to the product, the storage location information of the procedure file, and both the information on the product and the information on the service related to the product Or a ticket storage management means for storing and managing a ticket including one of them,
Search control means for causing the ticket storage management means to execute a search for a ticket corresponding to the code, based on the code and the ticket request requested by the user,
Access method information reading means for reading storage location information of a procedure file included in the ticket obtained by the search, and reading access method information from the procedure file based on the storage location information;
Read the access address of the service provider included in the ticket obtained by the search, request service provision information from the service provider based on the access destination address of the service provider, Service information acquisition means for acquiring according to the stored access method;
Presentation control means for presenting to the user the information on the product included in the ticket, the information on the service, the read access method information, and the acquired service providing content information;
With
The ticket may include a code different from the code as information on the product or information on the service,
The search control unit determines whether the ticket obtained by the search includes a different code, and when the ticket includes a different code, searches the ticket storage management unit for a ticket corresponding to the different code. To run further,
A service providing system. Request receiving means for receiving a code and a ticket request requested by a user together with identification information of the user;
User information storage means for storing user information including user preference information and service use information in association with user identification information;
Further comprising
The presentation control means,
Reading the user information corresponding to the user identification information obtained by the request receiving means from the user information storage means, selecting a service provider based on the user information and the service providing content information, and selecting the selected service Presenting service providing content information and access method information relating to the provider to the user,
2. The service providing system according to claim 1, wherein: The presentation control means,
A search is performed by a search engine using a keyword included in the information on the product or the information on the service as a search key, and link information obtained by the search is presented to the user.
The service providing system according to claim 1, wherein: A procedure file storing access method information for connecting to the service, a code assigned to the product, an access destination address of a service provider that provides a service related to the product, and storage destination information of the procedure file, And a ticket storage management unit configured to store and manage a ticket including both or one of information on the product and information on a service related to the product, a service providing method executed by a service providing system,
A search control step of causing the ticket storage management unit to execute a search for a ticket corresponding to the code based on the code and the ticket request requested by the user;
An access method information reading step of reading storage location information of a procedure file included in the ticket obtained by the search, and reading access method information from the procedure file based on the storage location information;
Read the access address of the service provider included in the ticket obtained by the search, request service provision information from the service provider based on the access destination address of the service provider, A service information acquisition step of acquiring according to the stored access method;
A presentation control step of presenting to the user the information on the product included in the ticket, the information on the service, the read access method information, and the acquired service providing content information,
The ticket may include a code different from the code as information on the product or information on a service related to the product,
In the search control step,
Determining whether the ticket obtained by the search includes a different code, and if the ticket includes a different code, causing the ticket storage management unit to further execute a search for a ticket corresponding to the different code;
A service providing method. A request receiving unit that receives the code and the ticket request requested by the user together with the identification information of the user, and associates the user information including the user preference information and the service usage information with the user identification information. Further comprising a stored user information storage means,
In the presentation control step,
Reading from the user information storage means user information corresponding to the user identification information obtained by the reception by the request reception means,
Selecting a service provider based on the user information and the service providing content information,
Presenting service provision content information and access method information relating to the selected service provider to the user;
5. The service providing method according to claim 4, wherein: In the presentation control step,
Performing a search with a search engine using a keyword included in the information on the product or the information on the service as a search key,
Presenting link information obtained by the search to the user,
The service providing method according to claim 4 or 5, wherein:

Images