JP4033727B2 - Information provision control system and information provision control method - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention relates to an information provision control system and an information provision control method for providing service information to a user by cross-linking a plurality of industries. In particular, the present invention relates to supporting presentation of information from a user belonging to a community (that is, a group of a plurality of users having a common preference) and information acquisition by the user.
[0002]
[Prior art]
Conventionally, as a community constructed and operated on a network, each of the servers that access / login to a system such as a single server that manages the community and exchanges information within the server, and a distributed server are connected to each other. Some of them linked information transmission on the server.
[0003]
Among these, in the community formed by one server, there is a problem that there are restrictions on system resources such as a possibility that access is concentrated and a temporary overload state may occur. On the other hand, in a community where information is distributed and interconnected to a plurality of distributed servers, there are few restrictions on system resources.
[0004]
However, the latter community (information transmission type community with a plurality of distributed servers) needs to prepare a relationship between a plurality of systems linked in advance as a URL link in order to maintain system interconnection. Or it was necessary to partner with a large information provider (for example, Yahoo or Nifty) that provides information comprehensively.
[0005]
[Problems to be solved by the invention]
However, there has been a problem that a community in which information is constantly updated requires extremely complicated work to establish link information and partnerships for maintaining system interconnection.
[0006]
On the other hand, the community generally does not aim to present information to a large number of unspecified users, but aims to present information to a specific user (ie, a member of a community) who promises to comply with a predetermined rule. . For this reason, it is necessary for a community that distributes and interconnects information to a plurality of distributed servers to construct a mechanism in which information is presented only to users who are permitted to present information according to the content of the information presented. It was.
[0007]
The present invention was made to solve the above-mentioned problems, and its purpose is to establish link information and partnerships in an information provision control system and information provision control method for providing service information to a user by cross-linking a plurality of industries. It is intended to facilitate the convenience of the information sender and user by presenting information only to appropriate users according to the content of the information while reducing the time and effort.
[0008]
[Means for Solving the Problems]
In order to achieve the above object, an information provision control system according to the present invention includes a procedure file storing access method information for connecting to a service and a code assigned to a product as described in claim 1. A ticket including an access destination address of a service provider that provides a service related to the product, storage information of the procedure file, and information related to the product and information related to the service related to the product Ticket storage managing means for storing and managing, request receiving means for receiving the code and ticket request requested by the user together with the identification information of the user, and user information including the user preference information stored in association with the user identification information User information storage means and the code obtained by the acceptance by the request acceptance means. And a search control means for causing the ticket storage management means to search for a ticket corresponding to the code based on the ticket request, and reading storage location information of the procedure file included in the ticket obtained by the search, Access method information reading means for reading access method information from the procedure file based on storage location information, and an access destination address of the service provider included in the ticket obtained by the search, and an access destination of the service provider Service information acquisition means for requesting service provision content information to the service provider based on the address and acquiring according to the access method stored in the procedure file related to the service, information regarding the product included in the ticket, and the service Information, read access Presentation control means for presenting the legal information and the acquired service provision content information to the user, and the ticket includes permission condition information indicating a condition of the user permitted to present the information included in the ticket. The presentation control means reads user information corresponding to the identification information of the user obtained by the reception from the user information storage means, and based on the user information and the permission condition information included in the ticket, It is determined whether or not the information included in the ticket is allowed to be presented to the user, and when the presentation is permitted, the information is presented to the user.
[0009]
In the information provision control system, there is a procedure file that stores access method information for connecting to a service, and user information storage means that stores user information including user preference information in association with user identification information. The ticket storage management means relates to the code assigned to the product, the access address of the service provider providing the service related to the product, the storage information of the procedure file, and the information related to the product and the product. It stores and manages tickets that include both or one of information related to services. Here, when the user requests a ticket by the code and ticket request together with the identification information of the user, the request reception unit receives the code and ticket request together with the identification information of the user, and the search control unit receives the code and ticket. Based on the request, the ticket storage management unit is caused to search for a ticket corresponding to the code.
[0010]
The ticket storage management means searches for a ticket corresponding to the code, whereby a ticket is obtained as a search result. Here, 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 acquisition means reads the access address of the service provider included in the ticket obtained by the search, and requests service provision content information from the service provider based on the access address of the service provider. , According to the access method stored in the procedure file for the service.
[0011]
Then, the presentation control means presents the information related to the product included in the ticket, the information related to the service, the read access method information, and the acquired service provision content information to the user. As a result, the user can access the information related to the product included in the ticket corresponding to the desired code, the information related to the service, the access method information read based on the storage location information of the procedure file included in the ticket, and the ticket. The service provision content information acquired based on the access destination address of the service provider included in the service provider can be obtained.
[0012]
In particular, when the present invention is applied to a community, it is possible to reduce the time and effort for constructing link information and partnerships as in the past, and to facilitate the operation of the community.
[0013]
In the present invention, in such an information provision control system, the ticket includes permission condition information indicating a condition of a user permitted to present information included in the ticket, and the presentation control means receives The user information corresponding to the obtained user identification information is read from the user information storage means, and the information included in the ticket is presented to the user based on the user information and the permission condition information included in the ticket. It is determined whether or not to allow. The presentation control means presents the information included in the ticket to the user when the presentation is permitted. As a result, the information included in the ticket is presented only to an appropriate user according to the permission condition information included in the ticket.
[0014]
As described above, according to the present invention, by reducing the time and effort for constructing conventional link information and partnerships, by presenting information only to appropriate users according to the contents of information, Convenience can be achieved. The “code” in the present invention includes, for example, a code for identifying a product, a code related to a location such as a product sales location or a service providing location, and a video / still image that promotes / introduces the content of the product or service The code of the image file such as is included.
[0015]
In addition, the information provision control system according to the present invention, as described in claim 2, provides a predetermined number of users belonging to a community as a system for exchanging information operated by a group of a plurality of users having a common preference. The user registration means for registering the registration information of the user in response to a registration request from the user, and the registered user who wishes to provide information on the access destination address of the user as the service provider A ticket registration request that accepts a registration request for a ticket including a code given to a product related to the user's preference and the access address of the user from the user, and requests the ticket storage management unit to register the ticket And the ticket storage management means based on the ticket registration request, It is desirable to adopt a configuration for registering a new ticket including said a code access address.
[0016]
In this case, the user registration means stores and manages predetermined registration information of users belonging to the community, and registers the registration information of the user in response to a registration request from the user. Then, the registered user becomes a service provider and wishes to provide information on the access destination address of the user to other users, and the code given to the product related to the user's preference and the user's When requesting registration of a ticket including an access destination address, the ticket registration requesting unit receives the ticket registration request and requests the ticket storage management unit to register the ticket. The ticket storage management means registers a new ticket including the code and the access destination address based on the ticket registration request. As a result, information on this new ticket is presented to other users who use the information provision control system, and the user simply makes a user registration request to the community, and only makes a ticket registration request. It is possible to easily construct a mechanism for presenting own service provision information to other users.
[0017]
In addition, the information provision control system according to the present invention, as described in claim 3, provides a predetermined number of users belonging to a community as a system for exchanging information operated by a group of a plurality of users having commonality regarding preferences. Registration information for registering the registration information of the user in response to a registration request from the user, and a ticket information presentation request regarding the product related to the user's preference from the registered user The user stored in the user information storage means so that the user information of the user corresponds to the permission condition information related to the ticket so that presentation of the information included in the ticket to the user is permitted It is desirable to further comprise a user information management means for updating the user information.
[0018]
In this case, the user registration means stores and manages predetermined registration information of users belonging to the community, and registers the registration information of the user in response to a registration request from the user. Then, when the registered user requests the ticket information presentation related to the product related to the user's preference, the user information management means accepts the ticket information presentation request, and the user of the information included in the ticket The user information of the user stored in the user information storage means is updated so that the user information of the user corresponds to the permission condition information regarding the ticket so that the user information is permitted.
[0019]
Thus, based on the updated user information of the user and the permission condition information regarding the ticket, presentation of the information included in the ticket to the user is permitted. You can receive the information contained in the desired ticket. As described above, the user can easily receive the desired ticket information by simply making a user registration request to the community and making a ticket information presentation request.
[0020]
By the way, the invention according to the information provision control system can also be understood as the invention of the following information provision control method. Since these inventions are the same in terms of technical idea, they exhibit the same actions and effects.
[0021]
That is, the information provision control method according to the present invention is related to a procedure file storing access method information for connecting to a service, a code assigned to a product, and the product as described in claim 4 Ticket storage management for storing and managing a ticket that includes an access destination address of a service provider that provides a service, storage information of the procedure file, and information on the product and / or information on the service related to the product An information provision control method executed by an information provision control system comprising: means and user information storage means for storing user information including user preference information in association with user identification information, A request receiving step for receiving the requested code and ticket request together with the identification information of the user; A search control step 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 obtained by the paste, and a procedure file included in the ticket obtained by the search Read the storage location information, read the access method information from the procedure file based on the storage location information, and read the access destination address of the service provider included in the ticket obtained by the search, A service information acquisition step of requesting service provision content information to the service provider based on the access destination address of the service provider and acquiring according to the access method stored in the procedure file related to the service, and the ticket included in the ticket Information about products, related to the service Information, the read access method information, and the presentation control step of presenting the acquired service provision content information to the user, and the ticket is the information of the user permitted to present the information included in the ticket. Including permission condition information representing a condition, and in the presentation control step, user information corresponding to the user identification information obtained by the reception is read from the user information storage means, and the permission included in the user information and the ticket Based on the condition information, it is determined whether or not the presentation of the information included in the ticket is permitted to the user, and the presentation to the user is performed when the presentation is permitted.
[0022]
Moreover, in the information provision control method according to the present invention, as described in claim 5, the information provision control system is a system for exchanging information operated by a group of a plurality of users having commonality regarding preferences. The system further comprises user registration means for storing and managing predetermined registration information of a user belonging to the community and registering the registration information of the user in response to a registration request from the user, and serving as the service provider of the access destination address of the user Based on the registration request of the ticket including the code given to the product related to the user's preference and the access destination address of the user from the registered user who wants to provide information, the ticket storage management means A registration request step for requesting registration of the ticket, and the ticket storage management means to register the ticket. Based on the determined, it is desirable to further include a ticket registration step of registering a new ticket including said access address and said code.
[0023]
Furthermore, in the information provision control method according to the present invention, as described in claim 6, the information provision control system is a system for exchanging information operated by a group of a plurality of users having a common preference. A user registration unit that stores and manages predetermined registration information of a user belonging to the community of the user and registers the registration information of the user in response to a registration request from the user, and the user's preference from the registered user The user information of the user corresponds to the permission condition information related to the ticket so that the information presented in the ticket is permitted to be presented to the user based on a ticket information presentation request related to the product. A user information update step for updating the user information of the user stored in the user information storage means; Desirable.
[0024]
DETAILED DESCRIPTION OF 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”. Also, the ticket is information in which information on the product corresponding to the ID, the address of the service provider related to the service provision related to the product, the access method, the service type, etc. are described. It will be described later.
[0025]
[Configuration of information provision control system]
FIG. 1 shows the overall configuration of the information provision control system according to the present embodiment. As shown in FIG. 1, the information provision control system according to the present embodiment includes the following components connected to or connectable to a network 120. In other words, the information provision control system newly adds a terminal 100 such as a personal computer (PC), a portable information terminal (PDA), a cellular phone, etc. of a user who receives the service, and a thing to which an ID is given. ID issuance requester (for example, a person who develops or manufactures a new product, a person who obtains a product by purchasing, etc.) 102, a group 103 of ID issuing organizations that issue ID, A ticket registrant 104 that requests ticket registration, a ticket management unit 105 that performs storage management and retrieval of tickets, and a procedure processing that presents a service provider candidate to the user through the service and performs a procedure related thereto Unit 106, a procedure file 107, and a service for performing sales, repairs, information provision, etc. via a network A service provider 108, the personal information 109, a user management unit 110 to operate the community, is configured to include a Web page 121, 122, and 123 individuals to transmit information.
[0026]
Of these, the ID issuing organization group 103 is based on the ID issuing management organization 1031 that manages and operates the overall ID issuing rules of the group 103 of ID issuing organizations, and the ID issuing rules given by the ID issuing management organization 1031. It includes a plurality of ID issuing organizations 1032 and 1033 that issue IDs.
[0027]
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.
[0028]
The procedure processing execution unit 106 selects a ticket related to a service provider requested by the user from a ticket search result (a plurality of tickets) based on the ID and stores a procedure file stored in the ticket. Based on the procedure file reading unit 1063 that reads the procedure file of the ticket from the destination (that is, the storage location information of the procedure file 107 related to the access method information to the service provider (also referred to as the service entity access protocol storage destination pointer)), and the procedure processing And a procedure processing instruction unit 1062 for instructing the procedure.
[0029]
The procedure file 107 contains a protocol used for the procedure and essential information (for example, in the case of a protocol defined by the automobile industry, an encryption communication method generally used on the Internet, a unique procedure protocol, and information necessary for the procedure. (Information on the type of the file) is described, and is open to the public so that anyone can refer to it via the network 120. As a result, new services can be used by simply selecting the optimal procedure from various publicly available procedures and writing the procedure file storage location in the ticket. Become. Note that the procedure file 107 may be configured to authenticate a person who requests information and to appropriately restrict reference as necessary in order to ensure security.
[0030]
The user management unit 110 relates to information such as a transmission / reception unit 111 that transmits and receives information such as user registration, a user registration unit 112 that performs user registration and manages user registration information, and information such as a web page related to the registered user at the time of user registration A ticket registration unit 113 for requesting registration of a ticket to the ticket management unit 105 and a personal information management unit 114 for updating the personal information 109 of the user at the time of user registration are configured.
[0031]
The personal information 109 used in the processing described later includes name and address, hobbies and preferences, list of possessed items, types of processing that can be processed, and access history and usage history for various service providers. The personal information 109 may be held in the terminal 100 by the user, or may be held in the form of the web pages 121, 122, 123 in the network, or the service. The procedure processing execution unit 106 may introduce the provider and mediate the procedure. The personal information 109 may be distributed and held in a plurality of places as shown in FIG. However, in that case, the personal information 109 in a plurality of places has the same content, and all the personal information 109 is updated in synchronization by the personal information management unit 114 when the personal information is updated.
[0032]
In addition, the object 101 given the ID is a code made up of a combination of numbers and characters, which is given the ID by a barcode, two-dimensional barcode, RF-ID, infrared tag, etc. Physical objects, electronic objects such as audio files and image files).
[0033]
[Various processing related to service provision]
Hereinafter, various processes related to service provision executed by the information provision control system will be described.
[0034]
[ID issuer certification process and ID issue process]
FIG. 2 shows ID issuing organization certification processing and ID issuing processing. As shown in FIG. 2, an organization that desires an application 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 issuance management institution 1031 examines whether the institution that has made an application can sufficiently comply with the ID issuance rules and other rules established by the ID issuance management institution 1031. Is issued as an ID issuing organization, and the issuing rules of IDs that can be issued by the organization that has applied are notified. As a specific example of the ID issuance rule, “an ID string given by ID issuing agency A must always be prefixed with the character string JAN” or “an ID given by ID issuing agency B must always be prefixed with ISBN” “Append a character string”.
[0035]
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 predetermined conditions. If the ID is satisfied, the ID is issued in accordance with the ID issuance rule set by the ID issuance management organization 1031 and the ID is issued to the ID issuance requester 102. By observing such an issue rule, it is possible to prevent the same ID from being duplicated, and it is possible to manage various conventional ID systems as non-overlapping code systems.
[0036]
FIG. 3 is a diagram illustrating ID issuing processing that avoids duplication of IDs without performing ID issuing organization certification processing. As shown in FIG. 3, first, the ID issuing organization 1032 or the like makes an ID issuing request to the ID issuing management organization 1031 every time an ID issuing request is received from the ID issuing 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 that issued the ID issuance request, and the ID is notified. Upon receiving the notification, the ID issuing organization 1032 or the like notifies the ID issuing requester 102 of the ID, and the ID issuing requester 102 can obtain the ID.
[0037]
Note that the ID issuance management organization 1031 described in FIG. 3 corresponds to an individual ID issuance request when all ID issuances can be managed and operated. 1031 is a form for issuing an ID.
[0038]
[Ticket registration / update process]
FIG. 4 is a diagram for explaining ticket registration / update processing 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. When a ticket registration request is made by a person who provides a service related to a product (product) to which an ID is assigned (specifically, an import agent that handles wine of ID = 1224 assigned by a wine manufacturer). Conceivable. However, the ticket may be registered by a third-party agent (for example, a sales promotion planning contractor commissioned by a previous import agent). When the ticket registrant 104 updates the ticket management unit 105 with an ID, a ticket, registrant information (for example, name, network address, etc.), and the contents of the ticket, the ticket registrant 104 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 if the condition is satisfied. The storage unit 1052 checks the contents of the ticket, and checks whether the ticket format is correct and whether the contents described in the ticket are correct. 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 a ticket storage completion notification indicating that the ticket has been stored, and the ticket ID of the stored ticket. This ticket ID is used again when the content of the ticket changes and is updated.
[0039]
[Ticket search processing and procedure processing]
Next, a ticket search process performed by the ticket management unit 105 and a procedure process performed by the procedure process execution unit 106 will be described with reference to FIG. Note that the flow of individual processing will be described later with reference to FIGS.
[0040]
First, the user 100 who has obtained an ID from the object 101 to which the ID is assigned, obtains the ID, a ticket request (optimum service providing destination request) necessary for service provision, and user information from the procedure processing instruction unit 106 of the procedure processing execution unit 106. To 1062. The procedure processing instruction unit 1062 searches the transmission / reception unit 1051 of the ticket management unit 105 for an ID and a ticket request in order to search for “what is the received ID?” And “what kind of service is associated with the ID?” And requester information (information on the procedure processing execution unit 106 including the procedure processing instruction unit 1062).
[0041]
The transmission / reception unit 1051 receives the ID, ticket request, and requester information, checks the requester information, and transmits the ID and ticket request to the search unit 1053 if there is no problem. The search unit 1053 checks whether or not there is a problem such as inconsistency in the contents of the received ticket request, and if there is no problem, transmits the ID and ticket search request to the storage unit 1052. The storage unit 1052 performs ticket search processing based on the received ID and 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 the search result is passed to the procedure file reading unit 1063.
[0042]
For each received ticket, the procedure file reading unit 1063 reads the procedure information from the procedure file 107 based on the procedure file storage location information described in the ticket and transmits it to the procedure processing instruction unit 1062. Then, the procedure processing instruction unit 1062 determines whether each user 100 can perform a procedure based on the personal information 109 and the procedure information regarding the user 100 who has requested the ticket, thereby determining whether each user ticket can be processed. A procedure check is performed to select only tickets that can be processed.
[0043]
For a ticket that is determined to be able to be processed, the procedure processing instruction unit 1062 requests the service provider 108 for detailed service provision details, and provides detailed service provision information (for example, “French wine sales, inquiry ID, product). Information such as “the sales price is 4500 yen, and the delivery is expected to be delivered in about two months depending on the product”) according to the access method stored in the procedure file 107 related to the service.
[0044]
The above-mentioned procedure processing execution unit 106 sends “the ID, the ticket request, and the requester information to the transmission / reception unit 1051 of the ticket management unit 105 to make a service provision details inquiry request to the service provider 108. The process of “receiving service provision detailed content information” is referred to as a service provider candidate extraction process 501. The service provider candidate extraction process 501 is repeatedly executed based on information (ID, product comment, service comment, 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.
[0045]
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 requested by the user from the received tickets based on the personal information 109. For example, for a ticket searched with a wine ID, if the user's personal information requested this time contains information such as “live in Tokyo” or “hobbies travel abroad” Priority is given to tickets related to service providers in Tokyo. Then, the ticket filtering unit 1061 presents the selected optimal service providing destination candidate to the user 100. When there is a requested service, the user 100 selects the service provider 108 of the service and makes a service processing execution request to the service provider 108. 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.
[0046]
[Ticket structure]
Here, the structure of the ticket will be described with reference to FIG. The ticket includes the following information (1) to (13).
[0047]
That is, (1) an ID that is a string of numeric characters that specifies that an ID is assigned. (2) Connection destination of a service provider who provides information and services related to the ID (service provider (service entity pointer): for example, an IP address or URL on the network). (3) A destination where service procedure information describing an access method for connecting to a service is stored (service entity access protocol storage destination pointer: IP address, URL, file name, etc. on a network, for example). (4) Ticket type. As a specific example, for example, “primary” indicating a ticket that can be issued only by an ID issuance requester indicating what is given an ID, and is issued to provide a service related to the thing “Secondary” etc. (5) An object category (Object Category) which is information for classifying what an ID is assigned to. (6) An object location (Object Location), 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 related to the object given the ID is described. (8) A service category (Service Category) that is information indicating what kind of service the service provision related to the object to which the ID is assigned is classified. (9) A service location that is information indicating in what place or region the service provision related to the object to which the ID is assigned is performed. (10) Service comments in which various information related to the provision of services related to the object to which the ID is assigned is described. (11) Information about the registrant of the ticket. (12) The registered expiration date of the ticket. (13) Permission information indicating a searcher who can browse by ticket search.
[0048]
Among these information described in the ticket, the information of (2) and (3) is characterized by having a structure that has only a pointer so that it can correspond to various services, and (4) (5) ( 6) (7) (8) (9) (10) is characterized by having a structure that enables flexible search and can create various services. In addition, the information in (11) and (12) is characterized by having a minimum structure for ensuring the validity of the ticket, and the information in (13) is for enabling restriction of information disclosure. It is characterized by having a structure. Information on (1), (2), (3), (4), (11), and (12) must be described, but other information may or may not be described. When there is no description of information, it is described as “NULL”.
[0049]
[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.
[0050]
First, the ticket management unit 105 receives an ID, a ticket body, a ticket ID (NULL in the case of first registration), receives registrant information (S11 in FIG. 7), and based on the received ticket registrant information. Is evaluated for reliability (S12). Various methods can be used for the reliability evaluation here, for example, a method using an account and a password, a method of changing a password with time change, a method of notifying a password to an email address inquired, etc. Evaluate ticket registrants in any combination or combination.
[0051]
If it is determined in S12 that it is not reliable, the received ticket is discarded (S18), the registration request source is notified that the ticket storage has failed (S19), and the process is terminated. On the other hand, if it is determined that the ticket is reliable in S12, it is next determined whether or not the contents of the ticket are correct (S13). The process for determining whether or not the contents of the ticket are correct is performed by checking whether the ticket structure matches the prescribed structure, whether the essential items to be described in the ticket are described, and the like.
[0052]
If the contents of the ticket are not correct in S13, the received ticket is discarded (S18), the registration request source is notified that the ticket storage has failed (S19), and the process is terminated. On the other hand, if the content of the ticket is correct in S13, a process of determining whether or not a ticket having the same ID, the ticket ID, and the same registrant information is already stored in the ticket management unit 105 (ticket ID check process) is performed. Perform (S14). This determines whether the ticket is registered or the ticket is updated.
[0053]
If the same ID, ticket ID and the same registrant information are 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 ticket registrant 104 (or ticket updater) is notified of the notification that the storage of the ticket has been completed and the ticket ID related to the stored ticket (S17), and the process ends.
[0054]
On the other hand, if a ticket having the same ID and ticket ID and the same registrant information is stored in the ticket management unit 105 in S14, it is determined that the ticket is updated, and the ticket already received is received. The new ticket is overwritten and accumulated (S15). Then, the ticket registrant 104 (or ticket updater) is notified of the notification that the storage of the ticket has been completed and the ticket ID related to the stored ticket (S17), and the process ends. At this time, it is determined whether or not there is a ticket having the same ID and all the items of the ticket. If there is an identical ticket, the storage capacity of the database is more effective if the ticket is not stored. It is effective for use.
[0055]
[Flow of ticket search processing]
Next, the flow of ticket search processing in the ticket storage unit and procedure processing execution unit will be described with reference to FIG. Here, since the processing subject has been described with reference to FIG. 5, it is generically represented not by the ticket filtering unit 1061 or the like but by the procedure processing execution unit 106 or the ticket management unit 105.
[0056]
First, the procedure processing execution unit 106 receives an ID, a ticket request, and user information from the user 100 (S31 in FIG. 8). Then, the procedure processing execution unit 106 determines whether or not 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.
[0057]
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 providing destination candidate extraction process 501 in FIG. 5 is reset to zero “0” (S33), ID, ticket request, request The person information is transmitted to the ticket management unit 105 (S34). Then, 1 is added to the number N (S35), and a service provider candidate extraction process 501 is performed (S36). The service provider candidate extraction process 501 will be described in detail with reference to FIG. After the service providing destination candidate extraction process 501 is completed, the ticket searched by the ID and the detailed information on the service providing contents related to the ticket are received (S37).
[0058]
Then, it is determined whether or not an 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 implementations of the service provider candidate extraction process 501 set in advance (S39). If the number N is greater than or equal to the implementation number limit number α, personal information reference processing is performed (S41). On the other hand, if the number N is less than the execution number limit number α, the ID described in the ticket is set as the ID to be searched (S40), and the ID, ticket request, and requester information are transmitted to the ticket management unit 105 again. (S34). In this way, by replacing the search target ID and repeating the process of searching for a ticket again, it becomes possible to provide a cross-sectional service in cooperation with various service providers.
[0059]
In the personal information reference process in S41, personal information such as the user's situation and user's preference, purchase tendency, service usage tendency, and the like is referred to from the personal information 109. Then, based on the personal information, a service providing destination selection process optimal for the user is performed (S42), and the selected service providing destination candidate performs an optimal service providing destination presentation process notified to the user's terminal ( S43).
[0060]
Thereafter, the user determines whether or not to select a service providing destination from the presented service providing destinations, and when selecting, selects 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. Here, 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.
[0061]
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 selected service providing destination is connected (S45), and the processing is terminated. As a result, the service is provided from the service providing destination to the user.
[0062]
[Service provider candidate extraction process flow]
Next, the flow of service provider candidate extraction processing will be described using FIG.
[0063]
The procedure processing instruction unit 1062 in the procedure processing execution unit 106 transmits the ID, ticket request, and requester information to the ticket management unit 105. At this time, if the service type requested by the user is known, the service search result can be narrowed down in advance by transmitting the service type to the ticket management unit 105.
[0064]
The transmission / reception unit 1051 of the ticket management unit 105 receives the ID, ticket request, and requester information from the procedure processing instruction unit 1062 (S71 in FIG. 9), and determines whether the requester information is correct (S72). If it is determined that the requester information is not correct, the processing is immediately interrupted, and the request processing procedure execution unit 106 is notified that the processing is interrupted (not shown), and the processing ends.
[0065]
On the other hand, if it is determined that the requester information is correct, the ID and ticket request are transmitted to the search unit 1053 (S73). The search unit 1053 determines whether or not the content of the ticket is correct by checking whether there is a problem such as inconsistency in the received ticket request (S74). If the contents of the ticket are not correct, the processing is immediately interrupted and the request processing procedure execution unit 106 is notified that the processing is interrupted (not shown), and the processing ends.
[0066]
If the ticket content is correct, the search unit 1053 transmits an ID and a ticket search request to the storage unit 1052. The storage unit 1052 performs ticket search processing based on the received ticket search request (S75). If the service type requested by the user is designated in advance as a search key, a filtering search based on the service type information is performed and a ticket extraction process is performed (S76).
[0067]
Then, it is determined whether or not there is a ticket obtained by the search (S77). If there is no ticket, the processing is immediately interrupted and the request processing procedure execution unit is notified that the processing is interrupted. Notify (not shown), and the process is terminated. On the other hand, if there is a ticket, processing for checking the expiration date of the ticket is performed (S78), and all tickets that satisfy the expiration date are passed from the transmission / reception unit 1051 to the procedure file reading unit 1063 as search results.
[0068]
The procedure file reading unit 1063 performs a process of reading each received ticket (S79), and performs a procedure file read process (S80) to acquire the procedure information. Then, it is determined whether or not there is a next ticket that has not been processed (S81). If there is an unprocessed ticket, the reading process (S79) is again performed, and the procedure file reading process (S80) is performed. Do.
[0069]
When there is no next ticket (when the procedure files of all tickets have been read), the procedure processing execution unit 106 determines whether or not the user 100 who has issued the ticket request can perform the procedure based on the personal information 109. Thus, only the tickets that can be processed are selected (the ticket selection process of the procedure process available to the user is performed) (S82).
[0070]
Then, it is determined whether or not there is a ticket that can be processed by the user (S83), and if it is determined that there is no ticket that can be processed, the requester informs that the processing is immediately stopped and the processing is interrupted. The procedure processing execution unit 106 is notified (not shown), and the processing ends.
[0071]
On the other hand, if there is a ticket that can be processed in S83, a process of reading out each ticket is performed (S84), and a service provision details inquiry process is performed (S85). Then, it is determined whether or not there is a next ticket that has not been processed in service provision details query processing (S86). If there is a ticket that has not been processed, ticket read processing (S84) is performed again, and the details of service provision query. Processing is performed (S85).
[0072]
If there is no next ticket (when the service provision details inquiry process for all tickets is completed), the processing is terminated as a result of processing each ticket and the service provision details for the ticket.
[0073]
[Description of processing example]
Next, a processing example when the present invention is applied to a community will be described with reference to FIGS.
[0074]
Here, three tickets relating to pet food (ID is 4901234petfood232) are registered in the ticket management unit 105, and a user 100 is routinely purchased with a thing (pet food) 101 given 4901234petfood232 as an ID. User.
[0075]
When the user 100 makes a ticket request for a ticket with an ID of 4901234petfood232, the above-described ticket search process obtains three tickets shown in FIGS. 10A to 10C as search results.
[0076]
As shown in FIGS. 10A to 10C, 4901234petfood232 is described in the ID column 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 presentation process in order to provide a service suitable for the user 100.
[0077]
An example of the optimum service provider presentation process is shown in FIG. That is, as shown in FIG. 15, first, an ID, a service provider presentation request, and a search ID are received (S101), the requester's personal information is acquired from the personal information 109 using the ID as a key, and the search ID is supported. The ticket to be acquired is acquired (S102). Then, the personal information of the requester and the permission information of the ticket are collated (S103). Based on the comparison result, it is determined whether or not there is a ticket that is permitted to be presented (S104). If there is a ticket that is permitted to be presented, a service providing destination presentation screen is created based on the information of the ticket, and It is presented to the requester (S105). On the other hand, when there is no ticket permitted to be presented, the requester is presented that the service provider cannot be presented (S106).
[0078]
For example, FIG. 11 (a) shows a viewable service provider presentation screen of Mr. A before membership registration in the community operated by the pet food lovers group, and FIG. 11 (b) shows Mr. A's at that time. Indicates personal information. Since Mr. A has not been registered in the community, the pet food ID is not described in the personal information of Mr. A as shown in FIG. 11B (pet food ID = NULL). When such Mr. A finds 4901234petfood232 as petfoodID in a certain pet food packaging and makes a service provider presentation request using this petfoodID as a search ID, the ID of 4901234petfood232 is obtained by the process of FIG. Three tickets (a) to (c) are candidates for presentation.
[0079]
However, since petfoodID = NULL in Mr. A's personal information, the service providing destination information presented to Mr. A as a result by comparing this information with the permission information of each of the tickets in FIGS. , Only the page related to the ticket of FIG. 10A (which can be understood from the Object Comments as a page holding information transmission about pet food and a meeting of pet food friends). That is, in the tickets shown in FIGS. 10B and 10C, it is determined that the permission information does not match the personal information of Mr. A, and therefore browsing of the page is not permitted to Mr. A. Accordingly, only the information related to the ticket shown in FIG. 10A is displayed on the browseable service provider presentation screen presented to Mr. A as shown in FIG. When accessing the actual information, an authentication procedure such as a password is separately performed for the requester, so that an illegal procedure processing execution unit 106 presents service provider information to an unauthorized user. Even if the user does not get the permission, the actual information is not presented to the user.
[0080]
Here, the flow of the user registration process in the user management unit 110 that manages the community will be described with reference to FIG. When the user registration request from the user (for example, Mr. A) 100 is received by the transmission / reception unit 111 (S91), the user management unit 110 transmits a transmission request for predetermined user information to the user 100 by the user registration unit 112 (S92). ). When the user information from the user 100 is received by the transmission / reception unit 111 (S93), the user registration unit 112 performs processing for registering the received user information (S94).
[0081]
When this user registration process is completed, the ticket registration unit 113 issues a ticket registration request to the ticket management unit 105 in order to register a ticket related to the information transmission of the user 100 for allowing the user 100 to participate in community formation (S95). . As a result, the address of the page for information transmission by the user 100 is registered in the ticket management unit 105 as one ticket, and the page of the user 100 forms a community by the above ticket search processing or the like. It can be browsed by other users.
[0082]
For example, when the user 100 is Mr. A, a ticket as shown in FIG. 13 is registered in the ticket management unit 105. Here, in the permission information of the ticket in FIG. 13, “petfoodID = 4901234petfood232”, which is information common to members of the community operated by the pet food lovers group, is set. The viewing of Mr. A's page is permitted by the ticket permission information of FIG.
[0083]
Next, the personal information management unit 114 performs an update process so as to give an ID indicating that the user is a member of the community in the personal information of the user 100 in the personal information 109 (S96). Thereby, the user 100 can browse the information transmission of the participant who forms another community by this ID. As described above, the personal information in the personal information 109 can be updated by the personal information management unit 114. However, it is assumed that the personal information management unit 114 performs the update on the condition that the update permission is received from the user 100 to be updated or the procedure processing execution unit 106 during the update.
[0084]
For example, FIG. 14B shows an example of personal information of Mr. A after registration. As shown in FIG. 14B, when Mr. A has registered as a user in the community, petfoodID = 4901234petfood232 is automatically added as A's personal information.
[0085]
In this state, when Mr. A makes a service provision destination presentation request using 4901234petfood232 as a search ID, the three tickets in FIGS. 10A to 10C whose ID is 4901234petfood232 are candidates for presentation by the processing in FIG. However, because petfoodID = 4901234petfood232 is registered as personal information of Mr. A by the above update, the permission information in the tickets of FIGS. 10B and 10C matches the personal information of Mr. A. These tickets B will be allowed to view Mr. B's page and Mr. C's page corresponding to. Accordingly, the viewable service provider presentation screen presented to Mr. A after registering the member, as shown in FIG. 14 (a), together with information on the ticket in FIG. 10 (a) (pet food web page), The link information of each page of B and C corresponding to the tickets in FIGS. 10B and 10C is displayed (links to each page are formed).
[0086]
As described above, according to the present embodiment, for a user, by registering a user in a community, a ticket registration process (S95 in FIG. 12) and a personal information update process (S96) are automatically executed, and a plurality of distributed servers It is possible to participate in the information dissemination type community. In addition, it becomes easy to form a community, and it is possible to interconnect information transmission pages without the trouble of building link information and partnerships.
[0087]
The present invention can be applied to general information provision control other than community management, and is not limited to application to a community.
[0088]
【The invention's effect】
As described above, according to the present invention, the information sender and the information sender can be provided by presenting information only to an appropriate user according to the content of the information while reducing the time and effort for constructing the conventional link information and partnership. User convenience can be achieved.
[Brief description of the drawings]
FIG. 1 is an overall configuration diagram of an information provision control system according to an embodiment of the present invention.
FIG. 2 is a diagram for explaining ID issuing institution certification processing and ID issuing processing;
FIG. 3 is a diagram for explaining ID issuing processing of an ID issuing organization that avoids ID duplication without performing ID issuing organization certification processing;
FIG. 4 is a diagram for explaining ticket registration / update processing of a ticket management unit;
FIG. 5 is a diagram for explaining ticket search processing performed in a ticket management unit and procedure processing performed in a procedure processing execution unit;
FIG. 6 is a diagram illustrating a ticket structure.
FIG. 7 is a flowchart of ticket registration update processing.
FIG. 8 is a flowchart of ticket search processing in a ticket storage unit and a procedure processing execution unit.
FIG. 9 is a flowchart of a service provider candidate extraction process.
FIGS. 10A to 10C are diagrams illustrating examples of ticket search results in which an ID of a predetermined pet food is described in an ID column.
11A is a diagram showing a service provider presentation screen that can be viewed by Mr. A before member registration, and FIG. 11B is a diagram showing personal information of Mr. A before member registration.
FIG. 12 is a flowchart of a user registration process in a user management unit that manages a community.
FIG. 13 is a diagram showing an example of a ticket registered along with member registration.
14A is a diagram showing a service providing destination presentation screen that can be browsed by Mr. A after member registration, and FIG. 14B is a diagram showing personal information of Mr. A after member registration.
FIG. 15 is a flowchart showing an example of optimum service providing destination presentation processing;
[Explanation of symbols]
DESCRIPTION OF SYMBOLS 100 ... User terminal, 101 ... The thing to which ID was given, 102 ... ID issue requester, 103 ... ID issue organization group, 1031 ... ID issue management organization, 1032, 1033 ... ID issue organization, 104 ... Ticket registrant, DESCRIPTION OF SYMBOLS 105 ... Ticket management part, 1051 ... Transmission / reception part, 1052 ... Storage part, 1053 ... Search part, 106 ... Procedure processing execution part, 1061 ... Ticket filtering part, 1062 ... Procedure processing instruction part, 1063 ... Procedure file reading part, 107 ... Procedure file 108... Service provider 109 109 Personal information 110 User management unit 111 Transmission / reception unit 112 User registration unit 113 Ticket registration unit 114 Personal information management unit 120 Network 121 122, 123... Web page, 501.

Claims (6)

A procedure file containing access method information for connecting to the service;
Both the code assigned to the product, the access destination address of the service provider that provides the service related to the product, the storage information of the procedure file, and the information related to the product and the service related to the product Or ticket storage management means for storing and managing tickets including one of them,
Request accepting means for accepting the code and ticket request requested by the user together with the identification information of the user;
User information storage means for storing user information including user preference information in association with user identification information;
Search control means for causing the ticket storage management means to search for a ticket corresponding to the code based on the code and ticket request obtained by reception by the request reception means;
Access method information reading means for reading storage location information of the 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;
The access destination address of the service provider included in the ticket obtained by the search is read, the service provider content information is requested from the service provider based on the access destination address of the service provider, and the procedure file related to the service is stored. Service information acquisition means for acquiring according to the stored access method;
Presentation control means for presenting information related to the product included in the ticket, information related to the service, read access method information, and acquired service provision content information to the user;
With
The ticket includes permission condition information indicating a condition of a user permitted to present information included in the ticket,
The presentation control means includes
User information corresponding to the identification information of the user obtained by the reception is read from the user information storage unit, and based on the user information and permission condition information included in the ticket, information on the information included in the ticket is read. It is determined whether or not presentation to the user is permitted, and when the presentation is permitted, the presentation to the user is performed.
An information provision control system characterized by that. Stores and manages predetermined registration information of users belonging to the community as a system for exchanging information operated by a group of a plurality of users having a common preference, and the registration information of the user in response to a registration request from the user User registration means for registering,
A ticket including a code given to a product related to the user's preference from the registered user who wants to provide information on the access destination address of the user and the access destination address of the user A ticket registration requesting unit that accepts a registration request and requests the ticket storage management unit to register the ticket;
Further comprising
The ticket storage management means includes:
Registering a new ticket including the code and the access address based on the ticket registration request;
The information provision control system according to claim 1. Stores and manages predetermined registration information of users belonging to the community as a system for exchanging information operated by a group of a plurality of users having a common preference, and the registration information of the user in response to a registration request from the user User registration means for registering,
The user information of the user is received so that a request to present information on a ticket related to a product related to the user's preference from the registered user is accepted and the presentation of the information included in the ticket to the user is permitted. User information management means for updating the user information of the user stored in the user information storage means so as to correspond to permission condition information regarding the ticket;
The information provision control system according to claim 1, further comprising: A procedure file in which access method information for connecting to the service is stored; a code assigned to the product; an access address of a service provider that provides a service related to the product; and storage location information of the procedure file; In addition, a ticket storage management means for storing and managing a ticket including information related to the product and / or a service related to the product, and user information including user preference information are stored in association with the user identification information. An information provision control method executed by an information provision control system comprising:
A request receiving step for receiving a code and a ticket request requested by a user together with identification information of the user;
A search control step for causing the ticket storage management means to search for a ticket corresponding to the code based on the code obtained by the reception and the ticket request;
An access method information reading step of reading storage location information of the 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;
The access destination address of the service provider included in the ticket obtained by the search is read, the service provider content information is requested from the service provider based on the access destination address of the service provider, and the procedure file related to the service is stored. A service information acquisition step of acquiring according to a stored access method;
A presentation control step of presenting to the user information related to the product included in the ticket, information related to the service, read access method information, and acquired service provision content information,
The ticket includes permission condition information indicating a condition of a user permitted to present information included in the ticket,
In the presentation control step,
User information corresponding to the identification information of the user obtained by the reception is read from the user information storage unit, and based on the user information and permission condition information included in the ticket, information on the information included in the ticket is read. It is determined whether or not presentation to the user is permitted, and when the presentation is permitted, the presentation to the user is performed.
An information provision control method characterized by the above. The information provision control system stores and manages predetermined registration information of users belonging to the community as a system for exchanging information operated by a group of a plurality of users having common preferences, and responds to registration requests from users. In response, the apparatus further comprises a user registration means for registering registration information of the user,
A ticket including a code given to a product related to the user's preference from the registered user who wants to provide information on the access destination address of the user and the access destination address of the user A registration request step for requesting the ticket storage management means to register the ticket based on a registration request;
A ticket registration step of registering a new ticket including the code and the access destination address based on the ticket registration request by the ticket storage management unit;
The information provision control method according to claim 4, further comprising: The information provision control system stores and manages predetermined registration information of users belonging to the community as a system for exchanging information operated by a group of a plurality of users having common preferences, and responds to registration requests from users. In response, the apparatus further comprises a user registration means for registering registration information of the user,
The user of the user is allowed to present the information included in the ticket to the user based on a request for information presentation of a ticket related to a product related to the user's preference from the registered user. 5. The information provision control method according to claim 4, further comprising a user information update step of updating the user information of the user stored in the user information storage means so that the information corresponds to permission condition information regarding the ticket. .

Images