JP2005141317A - Attribute responder, terminal device, attribute response system, and attribute response method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide an attribute responder, a terminal device, an attribute response system, and an attribute response method allowing a contents provider to prevent acquisition of incorrect attribute information due to erroneous input and the like by a contents user while preventing leakage of the attribute information of the contents user. <P>SOLUTION: An input transmission part 12 in a portable terminal 1 transmits input attribute information. A query part 25 in a contents provider server 2 transmits query data for asking whether the input attribute information is correct or not. A DB collation part 33 in an attribute response institution server 3 collates the input attribute information of the contents user included in the received query data with that stored in an internal DB 35. According to the collation results, an answering part 34 in the attribute response institution 3 transmits only the errata information representing whether the input attribute information is correct or incorrect to the contents provider server 2. <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

  The present invention relates to an attribute response device, a terminal device, an attribute response system, and an attribute response method for responding to an inquiry about attribute information of an online content user.

In recent years, provision of online contents and electronic commerce using a communication network such as the Internet has become popular. For this reason, when the content user uses the content provided by the content provider, there are many opportunities to input attribute values for attributes such as the user's own address and credit card number online.
Usually, when a content provider obtains attribute information of a content user, the following procedure is taken. First, the content provider prepares a form provided with an input field corresponding to the attribute to be acquired. The content provider server operated by the content provider transmits data for displaying the form to the content user's terminal device. The content user inputs an attribute value in the input field of the form displayed on the terminal device, and issues a transmission instruction. The content provider server receives the attribute information input by the content user.

As described above, the attribute information input / transmitted by the content user itself may not necessarily match the actual attribute information due to an input error that is not intended by the content user or an intentional error information input. For this reason, the content provider may not be able to acquire accurate attribute information.
Under such circumstances, if the database storing the content user attributes is located on the communication network and the attribute information can be obtained from the database, the content provider Can obtain accurate attribute information (see, for example, Patent Document 1). In Patent Document 1, attribute information and unauthorized use history information are acquired from a database in which content user attribute information is stored, and the reliability of information input / transmitted by the content user is determined, or authentication processing is performed. Techniques to do are disclosed.
JP 2001-52068 A (paragraph 0026, FIG. 4)

However, since the attribute information of the content user is related to privacy, it is necessary to protect it as personal information, and handling with strict care is required to prevent the attribute information from leaking outside. Therefore, it is not permitted to respond easily to the content provider's request for attribute information and disclose the content user's attribute information to the content provider.
The present invention has been made in view of the above problems, and prevents the content provider from acquiring inaccurate attribute information due to an erroneous input of the content user or the like while preventing the outflow of the attribute information of the content user. An attribute response device, a terminal device, an attribute response system, and an attribute response method are provided.

  In order to solve the above-described problem, the invention according to claim 1 is an attribute response device that responds to an inquiry about an attribute of a content user received from a content provider server, and an attribute for the attribute of the content user. Attribute storage means for storing attribute information representing a value; inquiry receiving means for receiving input attribute information representing an attribute value for the content user attribute inputted from the content provider server; and the inquiry receiving means A matching means for matching the received input attribute information of the content user and the attribute information of the content user stored in the attribute storage means, and according to a matching result by the matching means, the input attribute information Response means for returning only correct / incorrect information indicating correctness to the content provider server. Providing an attribute response device to.

  According to the first aspect of the present invention, in response to an inquiry regarding the content user's attribute, the attribute response device does not disclose the content user's attribute information itself, but only correct / incorrect information indicating the correctness of the input attribute information. Therefore, it is possible to prevent the attribute information of the content user from leaking outside. Moreover, since the content provider server which is an inquiry origin can confirm the correctness of input attribute information with the correctness information received from the attribute response apparatus, it can prevent acquiring incorrect attribute information. If the correct / incorrect information indicates an error, the content provider server discards the input attribute information or sends a message prompting the user to input an accurate attribute value to the content user's terminal device. Therefore, the content provider server can obtain the correct attribute information of the content user.

  The invention according to claim 2 stores, in the attribute response device according to claim 1, authority information indicating whether or not the content provider server has an authority to inquire whether the input attribute information is correct or incorrect. An authority storage unit; and an authority verification unit that acquires authority information of a content provider server that is a transmission source of the input attribute information from the authority storage unit when input attribute information is received by the inquiry reception unit. Provided, only when the authority information acquired by the authority verification means indicates that the authority is possessed, the response information is transmitted by the response means, and is acquired by the authority verification means. If the authority information indicates that the authority is not granted, information for notifying that the authority is not sent is sent to the content provider server. Characterized in that it.

  According to the second aspect of the invention, the attribute response device transmits correct / incorrect information to the content provider server only when the content provider server has the authority to inquire whether the input attribute information is correct or incorrect. The content provider server cannot receive the correct / incorrect information when it is not authorized. For this reason, the attribute response device not only discloses the content user's attribute information itself to the content provider, but also easily discloses the correctness of the input attribute information by following the authority information stored in the authority storage means. Therefore, it is possible to strengthen the security for attribute information and reliably protect the content user's privacy.

  According to a third aspect of the present invention, in the terminal device that transmits the input attribute value for the content user attribute to the content provider server, inquiring the external device for the correctness of the attribute value, the content provision A terminal device is provided, characterized by comprising authority registration means for transmitting authority information indicating whether or not to permit a user server to be registered in the external apparatus.

  According to the invention described in claim 3, the content user can determine whether or not to allow the content provider server to inquire whether the attribute value input to the content user attribute is correct or not. Since it can be specified from the apparatus, the content user can prevent the content provider from easily knowing whether the input attribute value is correct or incorrect. As a result, it is possible to strengthen security for the attribute information of the content user and protect the privacy of the content user.

  According to a fourth aspect of the present invention, when the content provider server receives input attribute information representing an attribute value for the attribute of the content user input from the terminal device, the attribute regarding the received input attribute information. In the attribute response system for making an inquiry to a response device, the terminal device includes input transmission means for transmitting the input attribute information, and the attribute response device stores attribute information representing an attribute value for the attribute of the content user. Attribute storage means, inquiry reception means for receiving the input attribute information transmitted by the input transmission means via the content provider server, input attribute information of the content user received by the inquiry reception means, and the A matching means for matching the attribute information of the content user stored in the attribute storage means, and the matching hand Depending on by butting thereby providing an attribute response system, characterized in that it comprises a response means for transmitting only to the content provider server Errata representing the correctness of the input attribute information. The operation and effect of the invention of claim 4 are the same as those of claim 1.

  The invention according to claim 5 is the attribute response system according to claim 4, wherein the terminal device uses the content stored in the terminal device when transmitting the input attribute information by the input transmitting means. A certificate transmission unit that transmits the electronic certificate of the user in association with the input attribute information, and the attribute storage unit associates the content user with the attribute information of the content user and transmits the electronic certificate of the content user. Identification information included in the certificate is further stored, the inquiry receiving means further receives the identification information included in the electronic certificate transmitted by the certificate transmitting means, and the matching means is received by the inquiry receiving means. The identified information is matched with the identification information stored in the attribute storage means.

  According to the fifth aspect of the present invention, the identification information included in the electronic certificate of the content user stored in the terminal device is used as information for identifying the content user so as to make a collation. Therefore, it is possible to accurately identify the content user due to the high reliability of the electronic certificate. In addition, the identity of the electronic certificate and the presence or absence of falsification can be confirmed at the same time by combining it with the electronic authentication mechanism, so the identity of the content user can be confirmed accurately using the identification information contained in the electronic certificate. be able to.

According to a sixth aspect of the present invention, in the attribute response system according to the fourth or fifth aspect, the attribute information stored in the attribute storage means is a contractor related to a usage contract for a terminal device owned by the content user. It is at least a part of information.
According to the invention described in claim 6, since at least a part of the contractor information related to the use contract of the terminal device is used as the attribute information stored in the attribute storage means, the content user who surely owns the terminal device Attribute information can be prepared. For this reason, the content user's input attribute information input from the terminal device can be reliably matched with the attribute information stored in the attribute storage means.

  The invention according to claim 7 is the attribute response method in which the attribute response server responds to the inquiry about the attribute of the content user received from the content provider server, wherein the attribute response server is input. An inquiry receiving step for receiving, from the content provider server, input attribute information representing an attribute value for the content user attribute; and the content user input attribute information received by the attribute response server in the inquiry receiving step; A matching step of matching the attribute information of the content user stored in the server in advance, and correct / incorrect information indicating whether the input attribute information is correct according to a matching result in the matching step by the attribute response server And a response step of returning only to the content provider server Providing an attribute response wherein.

  According to the attribute response method of claim 7, when the attribute response device receives the input attribute information of the content user, the attribute response device corrects the input attribute information without disclosing the attribute information of the content user itself. Since only correct / incorrect information is represented, it is possible to prevent the content user's attribute information from leaking outside. Moreover, since the content provider server can confirm the correctness of the input attribute information based on the correct / incorrect information returned from the attribute response device, it is possible to prevent acquisition of incorrect attribute information.

  According to the present invention, the attribute response device returns only correct / incorrect information indicating the correctness of the input attribute information without disclosing the attribute information itself of the content user in response to the inquiry from the content provider server. Content user attribute information can be prevented from leaking outside. Moreover, since the content provider server can confirm the correctness of the input attribute information based on the correct / incorrect information received from the attribute response device, it is possible to prevent the acquisition of incorrect attribute information. Further, when the correct / incorrect information indicates an error, the content provider server discards the input attribute information or transmits a message prompting the input of the correct attribute information to the content user's terminal device. Therefore, the content provider server can obtain accurate attribute information of the content user.

Next, the best mode for carrying out the present invention will be described with reference to the drawings. In each drawing referred to in the following description, the same reference numerals are given to the same parts as in the other drawings.
[1. Constitution]
[1.1. overall structure]
FIG. 1 is a block diagram showing a configuration of the entire attribute response system according to the embodiment of the present invention. As shown in the figure, the attribute response system according to the embodiment of the present invention is a mobile terminal 1 owned by a content user, a content provider server 2 that provides content to the mobile terminal 1, and an inquiry about attributes. An attribute response institution server 3 that responds to correctness and an attribute database (hereinafter referred to as “attribute DB”) 4 that manages contractor information related to the usage contract of the portable terminal 1 are provided. These devices are connected via a communication network such as the Internet.
In the figure, only one mobile terminal 1 and one content provider server 2 are shown, but there are actually a plurality of them.

[1.2. Mobile device]
Next, the configuration of the mobile terminal 1 will be described. The mobile terminal 1 has a hardware configuration of a general mobile phone. That is, the mobile terminal 1 includes a CPU (Central Processing Unit) that executes a program and controls the entire mobile terminal 1, a wireless communication interface that performs wireless communication, an SRAM (Static Random Access Memory), and a DRAM (Dynamic Random Access Memory). Storage unit including volatile memory such as flash memory, nonvolatile memory such as flash memory and UIM (User Identity Module), a plurality of operation buttons for giving various commands to the CPU, and a liquid crystal display for displaying various screens And.

  Various data and programs are stored in the storage unit of the mobile terminal 1. For example, the UIM stores a user certificate used for electronic authentication. Here, the user certificate is equivalent to an electronic certificate (public key certificate) used in a public key cryptosystem. In the user certificate, according to the X.509 format, a serial number, a certificate authority name (issuer), an expiration date, a user ID (owner name, user identification information of a user certificate issuer), public key information, and The data representing the signature of the certificate authority is described. The user certificate is downloaded from the Certificate Authority server and stored in the nonvolatile memory of the mobile terminal 1 when the user who owns the mobile terminal 1 makes a contract to apply for the electronic authentication service. It is.

  The non-volatile memory of the portable terminal 1 includes an OS (Operating System) that is basic software, a Web browser that is software for interpreting an HTML (Hyper Text Markup Language) file and displaying a screen, HTTP ( Software for transmitting and receiving HTTP requests / responses according to Hyper Text Transfer Protocol is stored. Various application programs are stored in the nonvolatile memory. The functions of the mobile terminal 1 shown in FIG. 2 are realized by the functions realized by the CPU of the mobile terminal 1 executing these programs and the hardware functions of the mobile terminal 1. Hereinafter, each function will be described with reference to FIG.

The portable terminal 1 includes a form reception unit 11, an input transmission unit 12, a certificate transmission unit 13, a correct / incorrect reception unit 14, and an authority registration unit 15.
The form receiving unit 11 receives, from the content provider server 2, for example, data representing a form provided with an input field for each attribute shown in FIG. 3.
The input transmitting unit 12 inputs the attribute value for the attribute that is input when the user inputs the attribute value in the input field corresponding to the attribute according to the form displayed on the display of the mobile terminal 1 and then performs a transmission instruction. Input attribute information representing a value is transmitted to the content provider server 2.

When the input transmission unit 12 transmits the input attribute information, the certificate transmission unit 13 reads the user certificate stored in the UIM and transmits the read user certificate in association with the input attribute information. . Here, as a method for associating the input attribute information with the user certificate, for example, at the time of transmission, the input attribute information and the user certificate are associated with each other by a session number or a sequence number.
The correct / incorrect receiving unit 14 receives data notifying the correct / incorrect determination result of the input attribute information from the content provider server 2.

The authority registration unit 15 transmits the input authority information to the attribute response institution server 3 when the user inputs authority information from the authority registration screen displayed on the display and gives a transmission instruction.
Here, the authority information is information indicating whether the content provider has the authority to inquire the attribute response authority server 3 about the correctness of the input attribute information. In other words, the authority information is information indicating whether or not the attribute response organization server 3 may reply to the attribute information inquiry from the content provider server 2.

[1.3. Content provider server]
Next, the configuration of the content provider server 2 will be described. The content provider server 2 is a WWW (World Wide Web) server, and has a general computer hardware configuration. That is, the content provider server 2 executes a program and controls the entire server 2, a storage unit including a ROM (Read Only Memory), a RAM (Random Access Memory), and a hard disk, and data via a communication network. Are provided, and these are connected by a bus.

  Various data and programs are stored in the storage unit of the content provider server 2. For example, the storage unit identifies various contents to be provided to the mobile terminal 1, an HTML file for displaying an attribute input form on the display of the mobile terminal 1, and the content provider server 2 on the communication network. A communication address is stored. In addition, the storage unit stores an OS, software for performing communication according to HTTP, and an application program for inquiring the attribute response authority server 3 about the correctness of the input attribute information. The functions shown in FIG. 4 are realized by the functions realized by the CPU of the content provider server 2 reading and executing these programs and the hardware functions of the content provider server 2. Hereinafter, functions provided in the content provider server 2 will be described with reference to FIG.

The content provider server 2 includes a form transmission unit 21, an input reception unit 22, a certificate reception unit 23, a certificate verification unit 24, an inquiry unit 25, a result reception unit 26, and a correct / incorrect notification unit 27.
In response to a request from the mobile terminal 1, the form transmission unit 21 reads an HTML file for displaying an attribute input form from the storage unit, and transmits the HTML file to the mobile terminal 1.
The input receiving unit 22 receives input attribute information from the mobile terminal 1.
The certificate receiving unit 23 receives the user certificate transmitted from the portable terminal 1 in association with the input attribute information at the same time.

The certificate verification unit 24 verifies whether the user certificate received by the certificate reception unit 23 is valid according to the public key cryptosystem. The certificate verification unit 24 retrieves the user ID included in the user certificate when it is verified that the user certificate is valid.
The inquiry unit 25 makes an inquiry to the attribute response agency server 3 as to whether or not the attribute value for each attribute included in the input attribute information received from the mobile terminal 1 is correct. Specifically, the inquiry unit 25 generates inquiry data including the user ID extracted by the certificate verification unit 24 and the input attribute information received by the input reception unit 22, and the generated inquiry data is sent to the attribute response organization server. 3 is transmitted.

As a result of the inquiry by the inquiry unit 25, the result receiving unit 26 receives result information indicating either correct / incorrect / no authority for each attribute value included in the input attribute information from the attribute response organization server 3.
The correctness / incorrectness notification unit 27 shapes the result information received by the result reception unit 26 so as to be displayed on the display of the mobile terminal 1 and generates an HTML file. If the result information received by the result receiving unit 26 indicates “wrong”, the correct / incorrect notification unit 27 includes a message prompting re-input in the HTML file. The correctness / incorrectness notification unit 27 transmits the generated HTML file to the mobile terminal 1.

[1.4. Attribute response authority server]
Next, the configuration of the attribute response agency server 3 will be described. The attribute response organization server 3 has a general server hardware configuration. Various types of data and programs are stored in the storage unit of the attribute response agency server 3. The function realized by the CPU of the attribute response agency server 3 executing these programs, and the storage unit of the attribute response agency server 3. The function of the attribute response organization server 3 shown in FIG. 5 is realized by the data stored in the above and the hardware provided in the attribute response organization server 3. Hereinafter, each function will be described with reference to FIG. The attribute response organization server 3 includes an inquiry receiving unit 31, an authority collating unit 32, a DB matching unit 33, a response unit 34, an internal DB 35, a DB extracting unit 36, an authority DB 37, and an authority registration unit 38.

The internal DB 35 is a database provided on the hard disk of the attribute response agency server 3. FIG. 6 shows the data structure of the internal DB 35. As shown in the figure, the internal DB 35 stores a plurality of sets of “attribute” and “attribute value” for “user ID” included in the user certificate of the user who owns the mobile terminal 1. ing.
The DB extraction unit 36 periodically extracts a combination of the user ID of the user certificate and the user attribute and attribute value identified by the user ID from the attribute DB 4, and corresponds to the user ID, attribute, and attribute value. In addition, it is stored in the internal DB 35.

  Here, the attribute DB 4 is a database managed by a telecommunications carrier that provides a communication service to the mobile terminal 1. The attribute DB 4 stores contractor information about the user of the mobile terminal 1. The contractor information is information that the user of the mobile terminal 1 applied to the communication carrier when the user of the mobile terminal 1 concludes a communication service use contract with the communication carrier. The contractor information includes attribute values for attributes such as “address”, “name”, “birth date”, “phone number”, and the like. Further, here, the user of the mobile terminal 1 has applied for an electronic authentication service contract, and the attribute DB 4 stores information related to the user certificate issued to the user.

  The authority DB 37 is a database provided in the hard disk of the attribute response agency server 3. The authority DB 37 stores authority information indicating whether or not the content provider server 2 is allowed to inquire about user attributes. FIG. 7 shows the data structure of authority information stored in the authority DB 37. As shown in the figure, the authority information includes a “content provider ID” representing a communication address of the content provider server 2, a “user ID” included in the user certificate, an “attribute”, and a content provider ID. The content provider identified by is configured with information indicating “inquiry authority” indicating whether or not it has the authority to inquire about “attributes”. Here, when “inquiry authority” indicates “present”, this indicates that there is an authority to make an inquiry, and when “inquiry authority” indicates “no”, an inquiry is made. Indicates no authority.

The authority registration unit 38 transmits an HTML file for displaying an authority registration screen to the mobile terminal 1 in response to a request from the user, and the authority information transmitted from the mobile terminal 1 in response to the HTML file is displayed. Register in DB37. The inquiry receiving unit 31 receives inquiry data for inquiring whether the input attribute information is correct from the content provider server 2.
The authority collating unit 32 has the authority of the content provider server 2 to inquire about the correctness of each attribute to be queried represented by the input attribute information included in the inquiry data, based on the authority information stored in the authority DB 37. Check whether or not. Specifically, the authority checking unit 32 matches the communication address of the transmission source content provider server 2 added to the inquiry data received by the inquiry receiving unit 31 from the authority DB 37 and the user ID included in the inquiry data. , “Content provider ID” and “user ID” are searched. The authority collation unit 32 acquires authority information including the matching “content provider ID” and “user ID” from the authority DB 37. The authority collation unit 32 checks whether the “inquiry authority” for the “attribute” to be queried is “present” or “not present” in the acquired authority information.

  The DB matching unit 33 performs matching between the input attribute information included in the inquiry data and the attribute information stored in the internal DB 35. Specifically, the DB matching unit 33 searches the internal DB 35 for a “user ID” that matches the user ID included in the inquiry data. The DB matching unit 33 extracts an “attribute value” corresponding to an “attribute” that is associated with a matching “user ID”, is a query target, and has a query authority. The DB matching unit 33 determines whether the data contents of the extracted “attribute value” and the attribute value for the attribute represented by the input attribute information are the same.

  The response unit 34 returns result information to the inquiry data transmitted by the content provider server 2. Specifically, when the authority information acquired by the authority collating unit 32 indicates that there is an authority, the response unit 34 sets the result of the matching by the DB matching unit 33 as either “correct” or “false”. Is transmitted to the content provider server 2 as data representing only. On the other hand, when the authority information acquired by the authority collation unit 32 indicates no authority, only the data indicating “no authority” is transmitted to the content provider server 2.

[1.5. Attribute response processing]
Next, the flow of processing from when the content provider server 2 transmits the attribute input form to the portable terminal 1 until the portable terminal 1 receives the determination result of the input attribute information with reference to FIG. explain. The mobile terminal 1, the content provider server 2, and the attribute response agency server 3 exchange HTTP responses / requests including a transmission destination communication address, a transmission source communication address, and data to be exchanged. In the description, only the data to be exchanged will be described.

In step S01, the form transmission unit 21 of the content provider server 2 reads out an HTML file for displaying the attribute input form stored in the hard disk and transmits the HTML file to the portable terminal 1.
The form receiving unit 11 of the mobile terminal 1 receives an HTML file from the content provider server 2. The Web browser interprets the HTML file and displays a form provided with an attribute input field on the display of the mobile terminal 1.

  In step S <b> 02, the user of the mobile terminal 1 operates the operation button to input an attribute value in the attribute input field, and then instructs transmission. Thereby, the input transmission part 12 of the portable terminal 1 transmits the input attribute information showing the attribute value with respect to the input attribute to the content provider server 2. At the same time, the certificate transmission unit 13 acquires a user certificate from the UIM. The certificate transmission unit 13 adds the sequence number to the user certificate, associates it with the input attribute information, and transmits the user certificate to the content provider server 2.

In step S <b> 03, the input receiving unit 22 of the content provider server 2 receives input attribute information from the mobile terminal 1. In addition, the certificate receiving unit 23 receives a user certificate from the mobile terminal 1.
In step S04, the certificate verification unit 24 of the content provider server 2 confirms whether or not the user certificate received by the certificate receiving unit 23 is valid by using a public key cryptosystem. If it is valid, the process proceeds to step S06, and if not valid, the process proceeds to step S05.

In step S05, since the user certificate is not valid, the content provider server 2 regards the user of the mobile terminal 1 as an unauthorized user, and terminates abnormally without performing the subsequent processing.
In step S06, the content provider server 2 extracts the user ID described in the user certificate received by the certificate receiving unit 23. Then, the content provider server 2 generates inquiry data including the extracted user ID and the input attribute information received by the input receiving unit 22 in order to inquire whether the input attribute information is correct or incorrect. The inquiry unit 25 of the content provider server 2 transmits the generated inquiry data to the attribute response organization server 3.

The inquiry receiving unit 31 of the attribute response organization server 3 receives the inquiry data.
In step S07, the authority verification unit 32 of the attribute response agency server 3 checks whether or not the content provider server 2 that has transmitted the inquiry data has the authority to inquire whether the input attribute information is correct or incorrect. Specifically, the authority collation unit 32 acquires the communication address of the content provider server 2 as the transmission source added to the inquiry data and the user ID included in the inquiry data. Then, the authority verification unit 32 searches the authority DB 37 for “content provider ID” and “user ID” that match the communication content of the content provider server 2 and the data content of the user ID. The authority collation unit 32 acquires authority information including the matching “content provider ID” and “user ID” from the authority DB 37.

  In step S08, the authority collation unit 32 confirms whether or not the content provider server 2 that has transmitted the inquiry data has the authority to inquire about the user attribute, according to the data content of the “inquiry authority”. Specifically, when the “query authority” corresponding to the “attribute” of the query target included in the query data represents “present”, the authority verification unit 32 determines that the content provider server 2 It is determined that the user has an authority to inquire whether or not. On the other hand, when the “query authority” corresponding to the “attribute” to be queried indicates “none”, the authority verification unit 32 has the authority to inquire whether the “attribute” is correct or not. Judge that it is not. If it is determined that there is an attribute having the authority to inquire among the attributes to be inquired, the process proceeds to step S09. Then, it proceeds to step S10.

  If it is determined that there is an authority and the process proceeds to step S09, the DB matching unit 33 searches the internal DB 35 for a “user ID” that matches the user ID included in the inquiry data. The DB matching unit 33 extracts an “attribute value” corresponding to an “attribute” that is associated with a matching “user ID”, is a query target, and has a query authority. The DB matching unit 33 determines whether or not the data content of the extracted “attribute value” and the attribute value for the attribute represented by the received input attribute information are the same.

  In step S <b> 10, the response unit 34 of the attribute response agency server 3 transmits result information for the inquiry to the content provider server 2. Specifically, when it is determined that the content provider server 2 has authority, the response unit 34 displays only the correct / incorrect information represented by the correct / incorrect result of the match by the DB matching unit 33. Send. On the other hand, when it is determined that the content provider server 2 does not have authority, the response unit 34 transmits only information notifying “no authority”.

In step S11, the result receiving unit 26 of the content provider server 2 receives result information indicating the result of the inquiry. When the result information received by the result receiving unit 26 is correct / incorrect information, the content provider server 2 shapes the correct / incorrect information so that it can be displayed on the mobile terminal 1, and An HTML file for notifying correctness is generated. Furthermore, when the correct / incorrect information indicates “wrong”, a message for prompting re-input is included in the HTML file. The correctness / incorrectness notification unit 27 transmits the generated HTML file to the mobile terminal 1.
In step S <b> 12, the correct / incorrect receiving unit 14 of the mobile terminal 1 receives the HTML file from the content provider server 2. The Web browser interprets the HTML file, and notifies the user of the correctness / incorrectness of the attribute information by screen display or the like.

[2. Operation]
Next, the operation in the above configuration will be described with reference to FIG.
As a premise, the DB extraction unit 36 of the attribute response agency server 3 extracts the contractor information and the user ID of the user certificate from the attribute DB 4 and registers them in the internal DB 35 in advance. It is assumed that the data shown is stored.
The communication address for identifying the content provider server 2 here is “123”. This communication address is stored in the storage unit of the content provider server 2 and is added to data exchanged by the content provider server 2. Further, it is assumed that an HTML file for displaying the attribute input form shown in FIG. 3 is stored in the storage unit of the content provider server 2.

  Further, it is assumed that the user ID of the user certificate stored in the mobile terminal 1 is “ABC”. In addition, when the user certificate is transmitted to the content provider server 2, it is determined that the user certificate is valid by the content provider server 2. Moreover, since the user of the portable terminal 1 has registered the authority of the content provider from the authority registration screen displayed by making a request to the attribute response authority server 3, the authority registration unit of the attribute response authority server 3 is registered. Suppose that the authority information 38 is registered in the authority DB 37 in FIG.

In addition, it is assumed that the user of content makes an incorrect input on the date of birth when inputting attribute information from the form displayed on the mobile terminal 1 in the operation described below.
First, the user of the mobile terminal 1 operates the operation button, specifies the URL (Uniform Resource Locator) of the content provider server 2, for example, and instructs to connect to the content provider server 2. Thereby, the portable terminal 1 and the content provider server 2 exchange data by an HTTP request / response, and the user of the portable terminal 1 receives provision of content from the content provider server 2. While receiving the content, the user of the mobile terminal 1 gives an instruction to request a form for attribute input. Thereby, the portable terminal 1 transmits request data for requesting a form for attribute input to the content provider server 2.

The content provider server 2 receives request data from the mobile terminal 1. The form transmission unit 21 reads an HTML file for displaying the form shown in FIG. 3 from the hard disk and transmits it to the portable terminal 1 (step S01).
The form receiving unit 11 of the mobile terminal 1 receives an HTML file from the content provider server 2. The Web browser interprets the HTML file and displays an attribute input form on the display of the mobile terminal 1.

The user operates the operation button of the mobile terminal 1 to input “Tokyo” in the “address” input field, “Hanako Sato” in the “name” input field, and “S30” in the “birth date” input field. After inputting 10.10 ", send is instructed by selecting the send button on the form.
Thereby, the input transmission unit 12 of the mobile terminal 1 inputs the input attribute information indicating the attribute value for the attribute (“attribute value“ Tokyo ”for the attribute“ address ”, attribute value“ Kanako Sato ”for the attribute“ name ”) ”, The attribute value“ S30.10.10 ”for the attribute“ birth date ”is transmitted to the content provider server 2. At this time, the certificate transmission unit 13 reads the user certificate from the UIM, and transmits the user certificate to the content provider server 2 simultaneously with the input attribute information (step S02).

  The input receiving unit 22 of the content provider server 2 receives the input attribute information, and the certificate receiving unit 23 receives the user certificate (step S03). The certificate verification unit 24 of the content provider server 2 determines whether the user certificate received by the certificate receiving unit 23 is valid according to the public key cryptosystem. Here, since it is determined that the user certificate is valid (step S04; Yes), the content provider server 2 uses the user ID described in the user certificate received by the certificate receiving unit 23. Remove “ABC”. Then, in order to inquire whether the input attribute information is correct or not, the content provider server 2 receives the extracted user ID “ABC” and the input attribute information received by the input receiving unit 22 (““ address ”“ Tokyo ”,“ name ”). Inquiry data including “Hanako Sato”, “Date of Birth” “S30.10.10”) is generated. The inquiry unit 25 of the content provider server 2 transmits the generated inquiry data to the attribute response organization server 3 (step S06).

  The inquiry receiving unit 31 of the attribute response organization server 3 receives the inquiry data. The authority verification unit 32 of the attribute response agency server 3 investigates whether or not the content provider server 2 that has transmitted the inquiry data has the authority to inquire about the correctness of the input attribute information of the user (step S07). . Specifically, the authority collation unit 32 acquires the identification information “123” of the content provider server 2 of the transmission source added to the received inquiry data and the user ID “ABC” included in the inquiry data. . Then, the authority checking unit 32 searches the authority DB 37 for “content provider ID” and “user ID” that match the identification information “123” and the user ID “ABC” of the content provider server 2. Here, since the upper right authority information shown in FIG. 7 includes the matching “content provider ID” and “user ID”, the authority verification unit 32 converts the authority information shown in the upper part of FIG. Get more. Then, the authority verification unit 32 checks whether the “inquiry authority” corresponding to the “attribute” of the acquired authority information is “present” or “not present”.

Here, since the “inquiry authority” corresponding to the “attribute”, “address”, “name”, and “birth date” of the authority information is all “present”, the authority collating unit 32 determines all the attributes to be queried. It is determined that the content provider server 2 has authority and can collate (step S08; Yes).
The DB matching unit 33 searches the internal DB 35 for a “user ID” that matches the user ID “ABC”. The DB matching unit 33 stores “attribute information” (““ address ”” “Tokyo”, “name” “Hanako Sato”, “date of birth” stored in association with the matching “user ID” “ABC”. "S10.10.10") is taken out from the internal DB 35. The DB matching unit 33 extracts the extracted “attribute information” and the input attribute information (““ address ”“ Tokyo ”,“ name ”“ Hanako Sato ”,“ date of birth ”“ S30. 10.10 ") and check whether or not the attribute values for the respective attributes to be queried match (step S09).

  Here, the attribute values for the attribute “address” and the attribute “name” match, but the attribute values for the attribute “birth date” do not match. Correct / incorrect information indicating a result (“address” “correct”, “name” “correct”, “birth date” “incorrect”) is generated, and only the correct / incorrect information is transmitted to the content provider server 2 (step S10). .

The result receiving unit 26 of the content provider server 2 receives correct / incorrect information. The content provider server 2 generates an HTML file for displaying information notifying whether the input attribute value is correct and a message prompting the user to re-enter the date of birth based on the received correct / incorrect information. The correctness / incorrectness notification unit 27 transmits the generated HTML file to the mobile terminal 1 (step S11).
The right / wrong receiving unit 14 of the mobile terminal 1 receives the HTML file. The web browser interprets the received HTML file and displays the screen on the display (step S12). As a result, the user can confirm that the “birth date” has not been correctly input, and can perform re-input.

As described above, the content provider server 2 causes the content user to input the attribute information of the content user to be acquired from the form displayed on the mobile terminal 1, and the input attribute information input and the user certificate user When the ID is transmitted to the attribute response agency server 3 and inquired, whether or not the attribute with authority matches the attribute value stored in the internal DB 35 is returned as result information. If they do not match, the content provider is prevented from acquiring an attribute value that is different from the actual value due to an erroneous input by the content user, etc. It becomes possible to do.
Further, the attribute response agency server 3 responds only whether the input attribute information transmitted from the content provider server 2 matches the attribute value stored in the internal DB 35, and discloses the attribute information of the user as it is. Because it does not, you can consider the privacy of the user.

[3. Modified example]
Although the embodiments of the present invention have been described above, the present invention is not limited to such embodiments, and various modifications may be made within the scope of the claims. For example, the following modifications can be considered.
(1) In the above-described embodiment, the user ID of the user certificate is used as a key (user identification information) for matching the input attribute information with the attribute information stored in the internal DB 35. However, without being limited thereto, for example, the telephone number or IP (Internet Protocol) address of the mobile terminal 1 can be used.

(2) In the above-described embodiment, it has been described that the attribute DB 4 stores all contractor information and user IDs to be registered in the internal DB 35. However, data stored in the attribute DB 4 is stored on the communication network. It may be distributed and stored in a plurality of servers. In the above-described embodiment, the attribute information to be registered in the internal DB 35 has been described as using contractor information on the use contract of the mobile terminal 1, but the information to be registered is not limited to contractor information. User information of other service contracts may be used, and if available, information on the resident register managed by the municipal office may be used.

(3) In the above-described embodiment, it has been described that data is transmitted and received according to HTTP. However, a protocol such as RTSP (Real Time Streaming Protocol) or SOAP (Simple Object Access Protocol) may be used.
Further, although the content provider server 2 stores an HTML file for displaying an attribute input form, the content provider server 2 may store an XML (eXtensible Markup Language) file. An HTML file for dynamically displaying an input form may be generated according to the attribute to be acquired.

(4) The data configuration of the internal DB 35 and the authority DB 37 in the above-described embodiment is an example. For example, in the authority DB 37, an attribute whose “inquiry authority” is “none” is also stored, but only an attribute whose “inquiry authority” is “present” may be stored. In the above-described embodiment, the authority DB 37 has a data configuration for storing the authority for each content provider and for each attribute. However, the authority DB 37 may have a data configuration for storing the authority for each content provider regardless of the attribute. Good.

(5) Although the mobile terminal 1 in the above-described embodiment has been described as a mobile phone, it may be a PHS (Personal Handyphone System). If there is no need to have contractor information regarding a communication service use contract, a PDA (Personal Digital Assistance) or a personal computer may be used. In the above-described embodiment, the user certificate is stored in the UIM of the mobile terminal 1, but may be stored in the nonvolatile memory of the mobile terminal 1.

  The present invention is an industry in which it is necessary to check whether the information applied / input by the user is correct while protecting the privacy of the user, and to perform processing based on accurate user attribute information, for example, It can be used for product sales, product delivery, contract conclusion, market research, etc.

It is a block diagram which shows the structure of the attribute response system which concerns on embodiment of this invention. It is a functional block diagram of the portable terminal which concerns on the same embodiment. It is a figure which shows an example of the form for attribute input which concerns on the embodiment. It is a functional block diagram of the content provider server which concerns on the embodiment. It is a functional block diagram of the attribute response organization server concerning the embodiment. It is a figure which shows the data structure of internal DB which concerns on the embodiment. It is a figure which shows the data structure of authority DB which concerns on the embodiment. It is a figure for demonstrating the flow of the attribute response process which concerns on the same embodiment.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 Mobile terminal 11 Form reception part 12 Input transmission part 13 Certificate transmission part 14 Correct / error reception part 15 Authority registration part 2 Content provider server 21 Form transmission part 22 Input reception part 23 Certificate reception part 24 Certificate verification part 25 Inquiry part 26 Result receiving part 27 Correct / incorrect notifying part 3 Attribute response organization server 31 Receiving part 32 Authority checking part 33 Collision part 34 Response part 35 Internal DB
36 Extraction unit 37 Authority DB
38 Authority Registration Unit 4 Attribute DB

Claims (7)

In an attribute response device that responds to an inquiry about a content user attribute received from a content provider server,
Attribute storage means for storing attribute information representing an attribute value for the content user attribute;
Inquiry receiving means for receiving input attribute information representing an attribute value for the content user attribute input from the content provider server;
A matching unit that matches the input attribute information of the content user received by the inquiry reception unit and the attribute information of the content user stored in the attribute storage unit;
An attribute response device comprising: response means for returning only correct / incorrect information indicating correctness / incorrectness of the input attribute information to the content provider server in accordance with a match result by the match means. Authority storage means for storing authority information indicating whether the content provider server has authority to inquire whether the input attribute information is correct or incorrect;
An authority verification unit that acquires authority information of a content provider server that is a transmission source of the input attribute information from the authority storage unit when the input attribute information is received by the inquiry reception unit;
Only when the authority information acquired by the authority verification unit represents that the authority is present, the corrector information is transmitted by the response unit,
If the authority information acquired by the authority verification means indicates that the authority is not granted, information for notifying that the authority is not sent is sent to the content provider server. The attribute response device according to claim 1, wherein: In the terminal device that transmits the input attribute value for the content user attribute to the content provider server,
It further comprises authority registration means for transmitting authority information indicating whether or not to allow the content provider server to inquire the external device about whether the attribute value is correct or incorrect. A terminal device. When the content provider server receives from the terminal device input attribute information representing an attribute value for the content user's attribute, the attribute response system inquires the attribute response device regarding the received input attribute information In
The terminal device includes input transmission means for transmitting the input attribute information,
The attribute response device
Attribute storage means for storing attribute information representing an attribute value for the content user attribute;
Inquiry reception means for receiving the input attribute information transmitted by the input transmission means via the content provider server;
A matching unit that matches the input attribute information of the content user received by the inquiry reception unit and the attribute information of the content user stored in the attribute storage unit;
An attribute response system comprising: response means for transmitting only correct / incorrect information indicating correctness / incorrectness of the input attribute information to the content provider server in accordance with a match result by the match means. When the terminal device transmits the input attribute information by the input transmission unit, the terminal device transmits the content user's electronic certificate stored in the terminal device in association with the input attribute information. Further comprising means,
The attribute storage means further stores identification information included in the electronic certificate of the content user in association with the attribute information of the content user,
The inquiry reception means further receives identification information included in the electronic certificate transmitted by the certificate transmission means,
The attribute response system according to claim 4, wherein the matching unit matches the identification information received by the inquiry reception unit with the identification information stored in the attribute storage unit.   6. The attribute according to claim 4, wherein the attribute information stored in the attribute storage means is at least a part of contractor information related to a usage contract of a terminal device owned by the content user. Response system. In an attribute response method in which an attribute response server responds to an inquiry about a content user attribute received from a content provider server,
An inquiry reception step in which the attribute response server receives input attribute information representing an attribute value for the attribute of the content user input from the content provider server;
A matching step in which the attribute response server matches the input attribute information of the content user received in the inquiry reception step with the attribute information of the content user stored in advance in the server;
The attribute response method comprising: a response step in which the attribute response server returns only correct / incorrect information indicating correctness of the input attribute information to the content provider server in accordance with a match result in the match step. .

Images