JP2007249690A - Member management system, service providing terminal and its method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a member management system for preventing service utilization information by one individual from being traced over a plurality of services. <P>SOLUTION: In the member management system (1) of this invention, in the service providing terminal (30) connected to a plurality of service management servers (20) for providing a user with each piece of service information, member IDs different for the respective service management servers (20) are generated from one intrinsic ID stored in the IC card (40-1) of the user, and the service management servers (20) are made to perform the member management of the user by the member IDs different from each other. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to a member management system that manages each member ID of a user who receives a plurality of services.

  Conventionally, in order to enjoy a service, a user performs member registration work such as notifying a service provider of personal information and receiving a member ID from each service provider. In this method, every time a user joins a service of a different business operator, a similar member registration work (for example, a repetitive registration work of common personal information) is forced.

  For this reason, a method for simplifying the member registration work has been studied. One of them is a configuration in which a server that mediates member management of each service provider is provided and personal information is managed by this server. In this configuration, the server that manages the member management of each service provider (member card broker server) issues a member card to the user, and the user uses the unique ID as the primary key in the member card broker server. Member information is associated with each service provider's member ID. This makes it possible to divert personal information, and simplifies troublesome and repeated registration work at the time of member registration (see Patent Document 1).

As another method for avoiding this repeated member registration work, it is also considered to distribute a card with a unique ID to users and share the ID as a member ID among a plurality of service providers.
JP 2001-216479 A

  As described above, several methods for simplifying troublesome repetitive work at the time of member registration have been studied. These methods are very convenient because the user can collect and possess the member ID necessary for using each service on a single card to which a unique ID is assigned.

  However, none of these methods have a regular relationship between the unique ID and the member ID, so a correspondence table must be provided in one place, or the unique ID and the member ID must be the same. It will be regulated by the conditions of.

  For this reason, if information such as the correspondence table is leaked from one location, the usage history of multiple services by individuals can be easily traced from that information, leading to infringement of personal privacy and problems. It is.

  Therefore, an object of the present invention is to provide a member management system, a service providing terminal, and a method thereof that prevent service usage information by one individual from being traced over a plurality of services.

In order to solve the above problems, the present invention is configured as follows.
One aspect of the member management system of the present invention is a unique ID management server for managing a user's unique ID, a plurality of service management servers for managing a plurality of service information for members, and providing service information to a user. It is assumed that service providing terminals to be connected are connected via a communication network. As its features, the service providing terminal includes a unique ID reading unit that reads a user's unique ID, a member ID generation unit that generates a member ID with a different algorithm for each service information based on the read unique ID, and service management Member confirmation request means for transmitting the generated member ID to the server and requesting confirmation that the user is a member. In addition, the service management server includes a member ID holding means for holding a member ID generated by a different algorithm for each service information based on a unique ID in advance, and a member ID for member confirmation received from the service providing terminal. Inquiry means for making an inquiry with the member ID held by the holding means, and means for permitting use of service information corresponding to the service providing terminal when there is a matching member ID by the inquiry.

  The member management system includes a unique ID management server for managing a user's unique ID, a plurality of service management servers for managing a plurality of service information for members, and service information specified by the user after confirming the member. Assuming a configuration in which service providing terminals to be connected to each other via a communication network, the service providing terminal has unique ID reading means for reading a user's unique ID, and service identification information holding for holding identification information of each service information A member ID generating means for generating a member ID from the means, identification information corresponding to the service information designated by the user and the read unique ID, and the service management server managing the service information designated by the user Confirm the membership by sending the generated member ID and requesting confirmation that the user is a member The service management server includes a member ID holding means for holding a member ID, and a member ID for holding the member ID received from the service providing terminal, and the member ID held by the member ID holding means. Inquiry means for making an inquiry and means for permitting the service providing terminal to use the corresponding service information when there is a matching member ID by the inquiry may be provided.

  In addition, as a carrying form of the above unique ID, it can be carried by being stored in an IC card or other card-like storage medium or a form telephone with an IC card function, or it may be stored by itself.

  With the configuration as described above, the user can automatically convert the service providing terminal into a member ID unique to each service provider by simply causing the service providing terminal to read one unique ID. And the member confirmation of the member ID is automatically performed between the service management servers via the communication network, and the service provision terminal can receive the service provision. For this reason, the user does not need to carry each member ID unique for each service as, for example, a plurality of cards, that is, only one unique ID can be carried as, for example, one IC card.

  Further, since it is not necessary to leave information directly indicating the correspondence between the unique ID and the member ID in one place in each device, it is possible to prevent the use of a plurality of services by a specific member from being traced from the outside.

  In addition, in the configuration in which the member ID is generated with the service identification information, even if the service that can be used by the user increases, the service providing information corresponding to the increase may be added to the service providing terminal. Since it is not necessary to add ID information to the service providing terminal, the storage area of the service providing terminal can be saved.

  In the member management system of the present invention, the service providing terminal includes service usage history report means for taking a usage history of service information used by the user and transmitting the usage history to the unique ID management server, and the unique ID management server includes: You may comprise so that the claim processing means which calculates the charge cost with respect to a service provider based on the utilization history of the service information transmitted from the service provision terminal may be provided.

  By configuring in this way, the operator of the unique ID management server that manages the member ID with one unique ID allows the service provider (service provider) to use the service at the service providing terminal by the user. For example, it becomes possible to charge a management fee.

  In the member management system of the present invention, the unique ID management server further includes a unique ID and common personal information related to a user to whom the unique ID is assigned (personal information common to a plurality of service providers of one member). And a service providing terminal that acquires common personal information corresponding to the unique ID read by the unique ID reading means from the unique ID management server. Personal information acquisition means, member application means for transmitting the member ID generated based on the unique ID and the acquired common personal information to the service management server for membership application, the service management server is a service providing terminal It may be configured to include additional registration means for additionally registering the member ID and the common personal information transmitted from the storage means.

  As another aspect, a unique ID holding storage medium (such as a card-like storage medium such as an IC card or a mobile phone with an IC card function) that holds a unique ID and common personal information and can be read by a service providing terminal. So that the user can have the second common personal information acquisition means for reading the common personal information from the storage medium for storing the unique ID, the member ID generated based on the unique ID, and the acquired common personal Member registration means for transmitting information to the service management server for membership application, and the service management server additionally registers the member ID and common personal information transmitted from the service providing terminal in the holding means. You may comprise so that a means may be provided. In this configuration, it is desirable to confirm the unique ID from the service providing terminal to the unique ID management server in order to confirm whether the unique ID is managed by the unique ID management server.

  With this configuration, when registering as a member with the service provider, the common personal information already stored as information can be diverted. Therefore, the user inputs the common personal information each time when registering as a member with the service provider. It is possible to save time and effort.

  In the member management system of the present invention, the service providing terminal further transmits expense confirmation information transmitting means for transmitting the usage history of the service information used by the user to the service management server, and the service management server is transmitted from the service providing terminal. You may comprise so that it may be provided with the billing cost determination means which determines the correctness of the billing cost transmitted from the specific ID management server based on the utilization history.

  In the member management system of the present invention, the service providing terminal further detects information that enables the member ID to be generated from the unique ID when the unauthorized access is detected (for example, algorithm information for generating the member ID from the unique ID, Security processing means for deleting service identification information and the like may be provided.

With this configuration, it is possible to prevent a plurality of service usages by the user from being traced based on the unique ID.
One aspect of the service providing terminal according to the present invention is a service connected via a communication network to a unique ID management server that manages a user's unique ID and a plurality of service management servers that respectively manage a plurality of service information for members. Assuming a configuration in which the service information of the management server is provided to the user, the feature is that a unique ID reading means for reading the user's unique ID and a member ID are generated with a different algorithm for each service information based on the read unique ID. Member ID generation means, and member confirmation request means for transmitting the generated member ID to the service management server and requesting confirmation that the user is a member.

  The member confirmation method of the present invention is performed at a service providing terminal connected by a communication network to a unique ID management server that manages a user's unique ID and a plurality of service management servers that respectively manage a plurality of service information for members. As a premise, the member ID is read with a different algorithm for each service information based on the read unique ID, a step of reading the unique ID of the user, a step of confirming whether or not the unique ID is registered in the unique ID management server A step of generating, transmitting the generated member ID to the service management server, requesting confirmation that the user is a member, and if the user is a member, Providing service information to the user.

  In the member registration method of the present invention, the service providing terminal connected by a communication network with a unique ID management server that manages a user's unique ID and personal information in association with each other and a service management server that manages service information for members. Assuming that it is performed on the management server, a step of reading the unique ID of the user, a step of generating a member ID with a different algorithm for each service information based on the read unique ID, and the read unique ID Acquiring personal information corresponding to the ID from the unique ID management server, transmitting the generated member ID and the acquired personal information to the service management server, and instructing the service management server to register a member; To do.

  One of the other aspects of the member registration method of the present invention is to connect a unique ID management server for managing a user's unique ID and a service management server for managing service information for members via a communication network. A member registration to the service management server using a storage medium for storing a unique ID stored in the service management server, and reading the unique ID from the storage medium for storing a unique ID on the premise that the registration is performed at a service providing terminal; Generating a member ID with a different algorithm for each service information based on the read unique ID; reading the personal information from the storage medium for storing the unique ID; and the generated member ID and the read individual A step of sending information to the service management server and instructing the service management server to register as a member. And, to perform the.

According to the present invention, a user has only one unique ID, and is managed with different member IDs in a plurality of service management servers.
In this case, since it is not necessary for the service providing terminal to store the member IDs for the service management server in association with one unique ID, the storage area can be saved.

  In addition, as described above, since it is not necessary to store the member ID for the service management server in association with one unique ID, service usage information by one user is traced over a plurality of services. Can be prevented.

  In particular, since the member ID of each service is generated based on the unique ID for each service based on the unique ID, the member ID of each service is different and even if the history of the member ID of one service flows out. It is not easy to link with IDs managed by other services. Even when the usage history associated with the member ID of one service leaks, it is not easily associated with the member ID of another service, so that the user's behavior can be prevented from being traced.

  Further, since the service providing terminal only needs to communicate with the service management server when providing the service to the member, the number of communication with the unique ID management server can be reduced as compared with the conventional configuration. Therefore, the communication concentration load on the unique ID management server is greatly suppressed.

Further, according to the present invention, since the user's personal information can be used at the time of membership registration, the membership registration work when the user receives a new service is simplified.
Also, in the present invention, since the user's usage history is recorded at the service providing terminal, the card issuer can grasp the usage status of the user, and based on this information, the service provider uses the system. It is possible to collect a fee.

Hereinafter, the best mode for carrying out the present invention will be described in detail with reference to the drawings.
(First embodiment)
FIG. 1 is a first embodiment of a member management system.

  In this member management system 1, as shown in the figure, a unique ID management server 10, n (n is an integer) service management servers 20 (server 1 to server n), a plurality of service providing terminals 30, and A storage medium for holding a unique ID (in the figure, two forms of an IC card 40-1 and an IC card function-equipped mobile phone 40-2 are shown), and in this example, further to this IC card 40-1. An information terminal 50 with an IC card R / W for writing information such as a unique ID and personal information is configured. These devices (unique ID management server 10, n (n is an integer) number of service management servers 20 (server 1 to server n), a plurality of service providing terminals 30, a mobile phone 40 with IC card function (with IC chip) -2 and the information terminal 50) are memories such as a CPU (Central Processing Unit), a ROM (Read HYPERLINK "http://d.hatena.ne.jp/keyword/Only" Only Memory), and a RAM (Random Access Memory). It is composed of a dedicated computer such as a general-purpose computer having ASIC and an ASIC. The IC card 40-1 (or IC chip) is a contact-type or non-contact-type IC card (or IC chip) provided with a communication unit, a data holding memory, a circuit for reading and writing memory data, and the like.

  Among them, the unique ID management server 10 and the n service management servers 20 are configured on the communication network 60, wait in a state where various programs are started up, and monitor requests transmitted from the communication network 60. Yes. The plurality of service providing terminals 30, the IC card function-equipped mobile phone 40-2, and the information terminal 50 are configured to be connectable to the communication network 60, and the unique ID management server 10 and the n service management servers 20 are connected to each other. When accessing, the communication network 60 is connected. In addition, this connection form is an example, It is not limited to this, You may set freely elsewhere.

  In the case of the above configuration example, the communication network 60 is configured by, for example, the Internet, a LAN (Local Area Network), a dedicated line, and the like. Although not particularly shown below, the transmission information is wiretapped or falsified between transmissions. For example, HYPERLINK "http://e-words.jp/w/E585ACE9968BE98DB5E69A97E58FB7.html" Public key encryption or HYPERLINK "http://e-words.jp/w/E7A798E5AF86E98DB5E69A97E58FB7.html" Encryption, HYPERLINK "http://e-words.jp/w/E38387E382B8E382BFE383ABE8A8BCE6988EE69BB8.html" Digital certificates, HYPERLINK "http://e-words.jp/w/E3838FE38383E382B7E383A5E996A2E695B0.html" Security functions such as hash functions It is assumed that extremely high security level communication such as SSL (Secure Socket Layer) communication is performed. The information terminal 50 and the service providing terminal 30 connect to the Internet via a public network such as a telephone network (not shown) and an ISP (Internet Service Provider) (not shown) that provides a connection service with the Internet. . The IC card-equipped cellular phone 40-2 is connected to the Internet via a cellular phone network (not shown).

  The unique ID management server 10 is a device that assigns a unique ID that does not overlap for each user and manages the user with this unique ID. A member management business operator who operates this unique ID management server 10 (also called a card issue business operator when issuing an IC card) issues a unique ID to a user who has applied for user registration. The ID is registered in an information table (this information table will be described later) formed in, for example, a storage device (not shown) of the unique ID management server 10, and an IC card storing the same ID as the unique ID is distributed to users. . If the user has an IC card or a mobile phone with an IC card function, the information is read into the IC card or the IC chip of the mobile phone via the communication network 60 instead of issuing the IC card. .

  In the unique ID management server 10 of this example, a billing processing unit 100 is further configured. The billing processing unit 100 calculates the usage cost of the member management system based on, for example, “service information usage history”, which will be described later, transmitted from the service providing terminal 30, and the service corresponding to the service information. The billing cost information is transmitted to the information provider (service provider).

  The n service management servers 20 (server 1 to server n) are provided with service information such as programs and data describing the execution procedure of services provided to users for each server. Is managed by member ID. This server is normally operated by each service provider, and service information is updated by the service provider.

  In particular, the service management server 20 of this example includes a holding unit 200, an inquiry unit 202, a service information use permission unit 206, and a billing cost determination unit 204, as shown in FIG.

  The holding unit 200 holds a member ID obtained in advance by generating a different value for each service management server 20 with a predetermined algorithm for the same user. Although this will be described in detail later, for example, the member ID and its personal information are stored in a table format in a storage device such as a hard disk.

  When the introduction unit 202 receives the member ID for member confirmation from the service providing terminal 30 via the communication network 60, the introduction unit 202 makes an inquiry with the member ID held by the holding unit 200. For example, when the member confirmation request information is received from the communication network 60, the member ID to be confirmed included in the information is taken out, and the member ID stored in the above-mentioned storage device in the table format is extracted, and these are extracted. Implement by inquiring.

  The service information use permission unit 206 permits use of service information corresponding to the service providing terminal 30 when there is a matching member ID by the inquiry. This is performed by permitting the service providing terminal 30 that is the transmission source of the member confirmation request information to use service information of a service provider that is permitted to register as a member with the member ID. The service provider's use permission for service information is, for example, issuing an access right to the service information of the service management server 20 operated by the service provider to the service providing terminal 30 that is the transmission source of the member confirmation request information. It is.

  The billing cost determination unit 204 determines the legitimacy of the billing cost of the billing cost information transmitted from the unique ID management server 10 based on a “service information usage history” described later transmitted from the service providing terminal 30. This validity can be determined by, for example, outputting “service information usage history” and “billing cost information” and comparing them with each other, or by comparing the numerical values of each item mechanically. You may make it obtain a result.

The service providing terminal 30 is a device that provides service information managed by the service management server 20 to the user.
FIG. 2 is a hardware configuration diagram of the service providing terminal 30.

  The service providing terminal 30 of this example includes a unique ID reading unit 300, a service identification information holding unit 302, a member ID generation unit 304, a member confirmation request unit 306, a service usage history report unit 308, and a cost confirmation information transmission unit 310. .

  The unique ID reading unit 300 reads the unique ID of the user. For example, unique ID information is generated based on an input signal input from a keyboard, or stored in advance in an IC card of an IC card or a mobile phone with an IC function so that the unique ID can be recognized by a computer. The unique ID is taken into the service providing terminal by contact / non-contact via the communication unit, or the unique ID information (for example, two-dimensional barcode information) displayed on the screen of the IC function mobile phone is scanned and unique. Implement by decrypting the ID.

  The service identification information holding unit 302 holds identification information of each service information. This is because service identification information is assigned in advance to service information provided by a service provider, and this service identification information is stored in a storage device such as a hard disk and the communication destination address of the service management server in which the service information is placed. Are stored in association with each other.

  The member ID generation unit 304 generates a member ID with a different algorithm for each service information based on the read unique ID. In this example, since service identification information is assigned in advance for each service information, a different member ID is generated for each service information by combining one unique ID and service identification information for each service information. The member ID may be generated for all the service identification information registered in advance, or may be performed only for the service identification information designated in advance or designated by the user.

  The member ID may be generated by any method that generates a member ID using a different algorithm for each service information based on the read unique ID, and is limited to a method that uses service identification information as in this example. is not.

  The member confirmation request unit 306 transmits the generated member ID to the service management server 20 and requests confirmation that the user is a member. This can be implemented, for example, by storing the member ID in information provided with a header indicating a member confirmation request and transmitting it to the service management server 20.

  The service usage history reporting unit 308 takes the “service information usage history” used by the user and transmits the usage history to the unique ID management server 10. This means that each time a user uses a service, the service identification information of the service information used by the user and the usage contents are stored as a usage history in a storage device such as a hard disk, for example, at a predetermined timing such as every other month, The usage history is transmitted to the unique ID management server 10.

  The cost confirmation information transmission unit 310 transmits the usage history of the service information used by the user to the service management server. This generates a usage history for each service identification information from the usage history stored in a storage device such as a hard disk, and transmits each usage history to the corresponding service management server 20 at a predetermined timing, for example, every other month. To do.

  The service providing terminal 30 handles a large amount of information that may be traced to others by the use of a plurality of service information by one user. For this reason, it is desirable to have a mechanism that prevents such information from leaking.

FIG. 3 is an example of a system block diagram in a service providing terminal suitable for preventing such information leakage.
The system configuration in the service providing terminal 20 shown in the figure includes a main control unit 200 that includes a CPU and a memory and controls each unit, a storage device unit 201 such as a hard disk, a card access unit 202 connected to a card reader, A display unit 203 connected to a display device such as a CRT monitor or a liquid crystal monitor, an operation unit 204 connected to an input device such as a keyboard, a network interface 205 connected to a communication network, and security processing for managing secret information and the like The units 205 are configured to be connected to the bus 206. Each unit is driven by power supplied from the main power source 207.

  The main control unit 200 reads various programs and data from the storage device unit 201 and the security processing unit 205 and executes various processes. In addition, when performing processing related to the member management system (particularly processing for handling security data that requires security protection), the right to execute the processing is passed to the security processing unit 205.

  The security processing unit 205 receives a control right from the main control unit 200, controls the respective units, a sub-control unit 300, a storage unit 301 that stores security data that needs security protection (for example, secret information described later), a tamper And a tamper resistant control unit 302 that erases security data in the storage unit when a tamper is detected, and an auxiliary power source 303. The auxiliary power source 303 is for supplying power to each unit in the security processing unit 205 when the main power source 207 is off, and this configuration always prevents leakage of security data.

  With this configuration, the sub control unit 300 executes a predetermined calculation process using the security data of the storage device unit 301 in accordance with a command from the main control unit 200 and returns the calculation result to the main control unit 200. For example, when receiving a member ID generation command from the main control unit 200, the sub-control unit 300 acquires a unique ID from the main control unit 200, and together with predetermined algorithm data in the storage device unit 301, the security processing unit A member ID is generated in 205, and the member ID is returned to the main control unit 200. Further, when tampering is detected during execution or standby, the predetermined algorithm data stored in the storage unit 301 is deleted.

Note that important information (for example, personal information) temporarily stored in the service providing terminal is also processed in the security processing unit in order to prevent leakage.
Here, returning to the description of FIG. 1, the IC card will be described.

  The IC card 40-1 is a normal IC card of contact type or non-contact type, and the internal data holding memory has an area for storing a unique ID, and a user who owns the IC card as required. An area for storing personal information is allocated. In this example, an IC card is used, but other card-like storage media (such as a magnetic card) may be used.

Next, the operation of the member management system will be described.
Here, an IC card is taken as an example of a storage medium for holding a unique ID possessed by the user, and a procedure for the user to receive a service is described. In addition, this description will be made with reference to an information table managed by each device.

First, the configuration of the information table managed by each device will be described.
4 to 12 are examples of configuration diagrams of information tables managed by each device.
The unique ID management server 10 stores personal information, service identification information, and inquiry history information in the storage device, and manages them in the form of an information table to be described later.

4 to 6 are examples of the information table.
FIG. 4 is an example of a personal information table.
This information table is for managing the registrants of the member management system, and is particularly necessary in the present system when the registrant is confirmed or the registrant information is diverted.

  The first record includes item information indicating the contents of the record information in the second and subsequent lines, such as “unique ID”, “name”, “phone number”, “date of birth”, “address”, “mail address”, and the like. It is shown.

  In the example of this personal information table, a sequential unique ID indicated by 10-digit alphanumeric characters issued by the card issuer is registered in the “unique ID” item in a serial number from the top to the bottom of the figure. . In addition, items other than the unique ID of each record are composed of personal information (common personal information) necessary for membership registration of each service provider, and are associated with the unique ID in one record.

Also in the table configuration diagram shown below, although not particularly described, it is assumed that the items other than the contents of the items are described in the same format as the personal information table.
FIG. 5 is an example of a service identification information table.

This information table is used for managing service identification information, and in this system, it is particularly necessary for notification of the billing amount for each service provider.
In this service identification information table, sequential service identification codes indicated by 10-digit alphanumeric characters are registered as service identification information sequentially from top to bottom in the figure. The service identification code is associated with the service provider that provides the service information corresponding to the service identification code.

FIG. 6 is an example of the inquiry history information table.
This information table is for managing the user's usage history information transmitted from the service providing terminal. In this system, in particular, when collecting usage information necessary for the basis of the amount charged to the service provider. Necessary.

  This inquiry history information table includes “service identification code” of service information used by the user, “terminal ID” of the service providing terminal using the service information, “use information” indicating the use contents and use time, “access” Information such as “date and time” is stored in association with one record.

  Note that, with such a configuration, it is possible to charge a usage fee for a service provider that provides the service in units of service usage of the user based on the usage content of the service. In addition, when billing is performed each time a member is registered by the user, the inquiry history information table may be generated accordingly. For example, the membership information is held in the service providing terminal, and the information is added to the table and managed.

  The subsequent service management server 20 stores member information of members who can use the service information of the apparatus, server information of the apparatus, terminal information of the service providing terminal, and usage history information of the service information of the apparatus in the storage device. However, it is managed in the format of an information table described later.

7 to 10 are examples of the information table.
FIG. 7 is an example of the member information table.
This information table is for managing information of members who are permitted to use the service information of this apparatus. In this system, the information table is particularly characterized by the structure of member IDs given to members.

  This member information table includes “member ID” and personal information items (“name”, “phone number”, “date of birth”) corresponding to common personal information in the personal information table (FIG. 4) in the unique ID management server 10. , “Address”, “mail address”, etc.) are assigned.

  In the “member ID” item, a random and non-overlapping member ID indicated by 18-digit alphanumeric characters is registered in this example. This member ID is data that is always uniquely generated by a predetermined algorithm based on the member's unique ID and the service identification code of the service information provided by the device in the service providing terminal. Register the one created according to the method.

FIG. 8 is an example of a server information table.
This information table is an information table necessary for authentication between devices, particularly for authentication of a service identification code.

In this server information table, unlike the past, items are shown in the left column and information is shown in the right column.
As shown in the figure, the “service identification code” includes “service identification code” in the service identification information table (FIG. 5) in the unique ID management server 10 corresponding to the service information in this apparatus. A similar 10-digit alphanumeric code is stored. Although only one piece of information is shown in the “service providing terminal communication key”, each communication key of all service providing terminals permitted to access the service management server is identified by each service providing terminal. Is registered in a possible format.

Further, although not specifically shown in the figure, the server information includes server data used for the subsequent explanation of inter-device authentication.
FIG. 9 is an example of a terminal information table.

Similar to the server information table of FIG. 8, this information table is an information table required for inter-device authentication.
In this terminal information table, terminal IDs of all service providing terminals permitted to access the service management server and their specific installation locations are registered.

FIG. 10 is an example of a usage history information table.
This information table is for managing user usage history information transmitted from the service providing terminal. In this system, particularly when checking the validity of the billing information transmitted from the unique ID management server 10. Necessary.

In this usage history information table, for each member ID, a service providing terminal used by the member and detailed usage contents are stored.
In the service providing terminal 30 that follows, secret information and usage history information of service information are stored in the storage device and managed in the form of an information table to be described later.

11 and 12 are examples of the information table.
FIG. 11 is an example of a secret information table.
This information table is particularly necessary when the member ID is generated based on the unique ID read from the user's IC card.

In this secret information table, unlike the other table diagrams, items are shown in the left column and information is shown in the right column.
As shown in the left item of the figure, the items include “terminal ID”, “service identification code”, “unique ID management server communication destination”, “unique ID management server communication key”, “service management server” The “communication destination”, “service management server communication key”, “card access key”, and “member ID generation algorithm” are assigned.

The “terminal ID” corresponds to the “terminal ID” in the information table of the other device, and the terminal ID of the service providing terminal is registered in this device.
In the “service identification code”, service identification information corresponding to service information in the service management server permitted to be used from the service providing terminal is registered.

In the “unique ID management server communication destination” and “unique ID management server communication key”, the address of the unique ID management server and the communication key necessary for communication therewith are registered.
In the “service management server communication destination” and “service management server communication key”, the address of the service management server and the communication key necessary for communication with the service management server are registered.

  The “card access key” stores key information such as a password for accessing a storage area of a unique ID (individual information if necessary) in the IC card. The presence of this information realizes a configuration in which access to the storage area for the unique ID and personal information in the IC card can be made only by a predetermined device.

The “member ID generation algorithm” stores a generation program for generating a member ID from a unique ID described later as an example.
Although only one piece of information is registered in the “content” of the “service identification code” in the figure, the service management server (or service information in one service management server) that can be used from the service providing terminal 30 If there are a plurality of service identification codes, a plurality of service identification codes are registered accordingly, and information on the communication destination and communication key of the service management server that provides the service information indicated by each service identification code is associated with each service identification code. So that each item is registered.

  In addition, such information is desired to be protected under high security management in order to prevent other users from tracing the use of a plurality of service information by the user. In particular, it is still better if only the unique ID and service identification code are used, but if the member ID generation algorithm is leaked to the outside, the service information can be easily used by multiple card users using this program. It is dangerous because it is traced.

Also, if the card access key is leaked, the IC card is copied without permission, and there is a risk that a person other than the registrant may complete the membership and use the service information.
Therefore, it is desirable to store these pieces of information in the above-described storage device (storage device portion of the security processing unit in FIG. 4) having a tamper-proof function with a higher security level.

FIG. 12 is an example of a usage history information table.
This information table is used to keep a record of the usage of service information used by the user at the service providing terminal. In this system, the unique ID management server 10 particularly charges the service provider for the cost of user usage. It is also necessary for the service management server to verify the validity of the cost charged from the unique ID management server.

In this example, the usage history information table has two patterns.
FIG. 12A is a table for attaching a user's usage history for each member ID.
FIG. 12B is a table for attaching a user's usage history for each unique ID.

  In the example shown in the figure, a table configuration is used to store the usage status by the user in detail, such as a process of adding or subtracting points according to service usage, or a member registration process.

  In addition, FIG.12 (b) is a thing of the grade shown additionally. In order to prevent the usage information of a plurality of services by one user from being traced to others, the configuration shown in FIG.

Next, inter-device authentication will be described.
In the member management system of this example, terminal authentication processing such as mutual authentication is performed in initial communication so that information is not erroneously transmitted to devices other than related devices.

FIG. 13 is a sequence diagram of mutual authentication processing between the service providing terminal 30 and the service management server 20.
First, communication connection processing is performed between the service providing terminal 30 and the service management server 20 (steps TS1, KS1).

  When the connection is established with each other, the service identification information held so far in the service providing terminal 30 (each service identification information of one or a plurality of service information managed by the service management server 20, For example, the service identification code in FIG. 11 is transmitted to the service management server 20 (TS2).

  Upon receiving the service identification information, the service management server 20 checks the current service identification information (FIG. 8) assigned to the target service information and returns Ack (KS2). If it has been changed, the service identification information after the change is returned.

  The service identification information is given by the card issuer as an initial setting when each service provider registers with the member management system, and is assigned a value that does not overlap with the identification information of other service information. Are stored in respective information tables (FIGS. 11 and 8) of the service providing terminal 30 and the service management server 20.

  Now, after checking the service identification information, the service providing terminal 30 transmits the terminal ID and date / time information (FIG. 11) to the service management server 20 as the terminal data (TS3).

  The service management server 20 checks whether the terminal data matches the terminal data registered in the information table (FIG. 9) in the server. Then, the terminal data registered in the information table and the server code and server date / time information which are server data of the service management server 20 are returned to the service providing terminal (KS3).

  In the service providing terminal, the terminal data and server data registered in the information table (FIGS. 8 and 8) of the service management server match the data registered in the information table (FIG. 11) in the service providing terminal. Check whether it exists. If the data match, the service providing terminal side establishes authentication of the service management server (TS4).

  After the authentication is established, the server data registered in the information table (FIG. 11) of the service providing terminal 30 is transmitted to the service management server 20 together with the authentication request command (TS5).

  The service management server 20 checks whether the server data registered in the service providing terminal information table (FIG. 11) matches the data registered in the server information table (FIG. 8). Here, if the data match, the service management server side establishes authentication of the service providing terminal (KS4).

After the authentication is established, the service management server 20 transmits the result of the authentication establishment to the service providing terminal 30 (KS5).
When the mutual authentication between the devices is established in this way, data communication with each other is started.

  Such inter-device authentication processing is performed between the service providing terminal and the unique ID management server, or between the unique ID management server and the service management server. This is done by exchanging information. However, the unique ID management server uses terminal data (not shown) in FIG. 5 as device information used for authentication.

Hereinafter, the card issuing procedure and the service information using procedure performed under the above configuration will be described with two examples.
Example 1
FIG. 14 is a sequence diagram of card issuing processing performed between a card issuing company and a user (user).

The figure shows two types of cases where the card issuance process is performed offline (window and mail) and online.
First, the case where the card issuance process is performed at the window and by mail will be described.

  First, the user submits or mails his / her personal information (for example, name, telephone number, date of birth, address, e-mail address, etc.) to the card issuer that issues the card (step OFFS1).

  The card issuer who has received this information assigns a unique ID (in this example, 10-digit alphanumeric sequential combination information) that does not overlap with other users to the user, and associates this unique ID with the user's personal information. Is registered in the information table (FIG. 4) in the unique ID management server 10. Then, at least the unique ID and the personal information are read into the IC card 40-1 in response to the request (HS1). The process of writing the unique ID and personal information to the IC card 40-1 is performed by writing the above various information to the unused IC card set in the information terminal 50 via the IC card R / W. This IC card is an IC card compatible with this system, and the storage area for the unique ID and personal information in the IC card can be accessed only with the encryption key of the reader compatible with this system.

Then, the IC card subjected to the issuing process is distributed to the user by window distribution or mail (OFFS2).
In this way, the card issuing process by the window and mail is performed off-line.

Next, a case where the card issuing process is performed online will be described.
Here, as an example, the description will be made assuming that the present system is constructed by Web technology.

  First, the user accesses the unique ID management server 10 from the information terminal 50, and performs the membership application process for his / her personal information (for example, name, phone number, date of birth, address, e-mail address, etc.). (Step JS1). In this membership application process, first, a web browser is started on the information terminal 50 side, a web server (not shown) of the unique ID management server 10 is accessed, and an application input information screen in the web information managed there is displayed on the screen. To display. Subsequently, the user's personal information is input with an unillustrated keyboard or the like in the items specified on the application input information screen. Then, the input information is packet-transmitted to the unique ID management server 10 as personal information for membership application. In this way, membership application processing can be carried out.

  The Web server of the unique ID management server 10 that has received this packet information retrieves the personal information in the packet when this packet information is information related to a new membership application. For example, for the user who last applied for membership The unique ID assigned in this example (10-digit alphanumeric sequential combination information) is assigned as a unique ID, and the user's personal information is associated with the unique ID in the unique ID management server 10. Register in the personal information table (FIG. 4) (HS2).

  Subsequently, the unique ID management server 10 performs a card issuing process (HS3). In this process, the unique ID management server 10 sends a signal instructing the information terminal 50 to set an unused IC card (or a user-used IC card having a predetermined free space in the storage area). When it is confirmed that an unused IC card is set, an instruction signal for securing a storage area for writing information in the IC card is further transmitted to the information terminal 50. Then, at least the unique ID is transmitted to the information terminal 50, and the personal information is transmitted in response to the request, and a write instruction to the storage area is given. The processing for writing the unique ID and personal information to the IC card is performed only by the information terminal 50 receiving the instruction signal from the unique ID management server 10 from a reader compatible with this system having an encryption key such as a password. This is implemented by securing an inaccessible memory area in an unused IC card and writing the above various information into the memory area. Writing to this IC card is performed via the IC card R / W. Further, when the information terminal 50 finishes writing the various information to the unused IC card, the information terminal 50 detects the end of writing and notifies the unique ID management server 10 of the processing result.

Finally, the unique ID management server 20 sends a reply to the information terminal 50 according to the processing result (result of admission application approval / disapproval) (HS4).
In this way, a series of processing is performed online.

Next, a usage procedure when the user uses service information using an IC card for which a unique ID has been acquired will be described.
FIG. 15 is a sequence diagram when a user uses service information in this system.
In the same figure, two types of sequences, when the user is a member of the service information to be used and when the user is a non-member, are divided into upper and lower parts.

First, a case where the user is a member of service information to be used will be described.
First, the user presents the IC card 40-1 on the service providing terminal 30. For example, when the IC card is a non-contact type IC card, the IC card is placed in the communication unit of the reading device of the service providing terminal 30, and when the IC card is a contact type IC card, the IC card slot of the reading device is inserted. Insert (OFFS10).

  Upon receiving the presentation of the IC card 40-1, the service providing terminal 30 identifies whether or not it is an IC card of the member management system in the reading device. In this identification process, the card access key stored in the information table (FIG. 11) of the service providing terminal 30 is used to detect whether or not the IC card is a type that can read the storage area of the IC card. To implement. If it is an IC card of the member management system, a command for extracting the unique ID from a predetermined area is transmitted to the IC card (TS10).

  When receiving this command, the IC card extracts the unique ID from a predetermined area and transmits it to the reading device of the service providing terminal 30 (CS10). Note that information exchanged between the IC card and the reading device is preferably encrypted.

  In the service providing terminal 30, the “unique ID” that is the transmission information (or the decrypted information if encrypted) is temporarily stored in the memory, and further stored in advance in the information table (FIG. 11) in the service providing terminal. The “service identification information” is read into the memory, and one member ID expectation information is generated for the service information used by the user. As an example, based on “one unique ID” and “one service identification information” read from the IC card 40-1, it is expected as the “member ID” of the service management server corresponding to the service identification information. Information is generated. Expected information includes information that does not correspond to “member ID”, such as when the member is not yet registered or when the unique ID is not legitimate information. (TS11).

FIG. 16 is an example of an algorithm for generating a member ID for each service identification information from the unique ID read from the IC card.
In the example of the figure, a function (for example, a function that shifts a bit) that applies a bijection or bijection mapping is applied to information obtained by adding a service identification code to a unique ID read from an IC card. The member ID is generated. It is difficult to reproduce the original information from the generated member ID by applying a function that gives this injection or bijection mapping.

The process flow is shown on the left of the figure, and the information used for each process and the obtained result information are shown on the right of the figure. The processing flow will be described below.
First, the unique ID is read out on the memory (S1).

  Subsequently, one of the “service identification information” stored in advance in the information table in the service providing terminal (FIG. 11) (if one is specified in advance) is read into the memory. Connect to generate additional information. In this example, the unique ID and the service identification information are connected in this order, and “0x” at the beginning of the service identification information is deleted (S2).

  Subsequently, by applying a function that gives a single-shot or bi-shot map to the additional information (S3), the "member ID" (or "member ID expectation information" at the time of the member ID confirmation process) is obtained. Obtain (S4).

  However, the generated member ID can be prevented from colliding with the generated member ID by making it equal to or greater than the information amount of the information obtained by adding the service identification code to the unique ID.

In this way, through this process, different member IDs corresponding to each service identification information can be generated based on one unique ID owned by one user.
Note that the algorithm for generating the member ID including this example is used in the same manner when generating information registered in the “member ID” of the information table (FIG. 10) in the service management server.

Now, returning to the description of FIG. 15, the description after the member ID generation processing is continued.
When the member ID is generated at the service providing terminal 30, the service providing terminal 30 inquires of the service management server 20 about the member ID. In this process, all generated member IDs may be transmitted to all service management servers to inquire about the member ID, or a service corresponding to a service identification code that is basic information of the generated member ID The member ID may be transmitted to the management server for each member ID, and an inquiry about only the corresponding member ID may be made to each service management server. As an inquiry method, for example, a member confirmation request packet can be generated and transmitted to the target service management server 20. The member confirmation request packet is configured to include, for example, a transmission source information storage unit, a transmission destination information storage unit, a data type storage unit, and a data storage unit. "Terminal data" is stored, "server data of the service management server to which the service identification code that is the original information of the member ID is assigned" is stored in the destination information storage unit, and "member confirmation request" is stored in the data type storage unit "Information indicating" is stored, and "generated member ID" is stored in the data storage unit (TS12).

  The service management server 20 executes a member ID identification process. In this process, the “member ID” in the information table (FIG. 7) of the service management server is extracted, and the “member ID expected information” received from the service providing terminal 30 is referred to as the extracted information. Since this procedure description assumes the case of an existing member, a member ID that matches the “member ID expectation information” is included in the extracted information. Here, the service management server 20 permits the service providing terminal 30 to provide service information to the user. As the permission method, for example, the service providing terminal issues an access right to the predetermined service information of the service management server to the service providing terminal, and the access restriction from the service providing terminal is released for a predetermined period. Alternatively, the permission information is transmitted to the service providing terminal side, and the service providing terminal is made to release the access restriction to the predetermined service information of the service management server on the service providing terminal side for a predetermined period. For example, the predetermined period may be divided by time, or may be the time when the user ends the operation on the service providing terminal (KS10, KS11).

During this time, the service providing terminal 30 provides service information permitted to the user (TS12).
At this time, the service providing terminal 30 monitors the state between the terminal and the service management server, the user's input operation on the terminal, and the like, and records the usage contents of the service information by the user in the service usage history information (FIG. 12). (TS13).

  Then, when the user finishes the process, for example, by ending the service information provision screen, this process ends. At this time, the service providing terminal 30 or the service management server 20 restores the use restriction cancellation of service information to the member.

Next, the case of non-members will be described.
The processing from step OFFS10 to step TS12 is the same as the processing in the case of the above-mentioned existing member. The process at step KS10 is the same as the process at step KS10, but is related to the subsequent process, and will be described from step KS10 here.

  In step KS10, the service management server 20 executes a member ID identification process. In this process, the “member ID” in the information table (FIG. 7) of the service management server is extracted, and the “member ID expected information” received from the service providing terminal 30 is referred to as the extracted information. Since the description of this procedure assumes a non-member case, a member ID that matches the “member ID expectation information” is not included in the extracted information. For this reason, subsequently, the service management server 20 replies to the service providing terminal 30 that the user is a non-member. (KS20).

  Upon receiving this reply result, the service providing terminal 30 displays that fact on the display screen, and further instructs the user to register as a member for using the service information, for example, by displaying a member registration screen. TS20).

The user instructs the service providing terminal 30 to execute member registration from an input device such as a keyboard (OFFS20).
Upon receiving this execution instruction, the service providing terminal 30 first transmits the unique ID read from the user's IC card to the unique ID management server 10 and inquires about the personal information of the user. As an inquiry method, for example, a personal information inquiry packet or the like is generated and transmitted to the unique ID management server 10. The personal information inquiry packet includes, for example, a transmission source information storage unit, a transmission destination information storage unit, a data type storage unit, and a data storage unit. "Terminal data" is stored, "Server data (address, etc.) of the unique ID management server" is stored in the destination information storage section, "Information indicating personal information inquiry" is stored in the data type storage section, and data The “unique ID read from the IC card” is stored in the storage unit (TS21).

  Upon receiving this inquiry request, the unique ID management server 10 searches the personal information table (FIG. 4) for personal information corresponding to the unique ID. For example, when it is determined from the “personal information inquiry request” in the data type storage unit of the received packet that the personal information inquiry is made, for example, the “unique ID” of the personal information table (FIG. 4) is extracted. This is compared with the “unique ID” included in the packet, and when there is a match with this “unique ID”, the personal information corresponding to this is extracted (HS20).

When the personal information corresponding to the unique ID is extracted, the extracted personal information is transmitted from the unique ID management server 10 to the service providing terminal 20 (HS21).
When receiving the personal information from the unique ID management server 10, the service providing terminal 30 adds the “member ID expected information” generated from the unique ID and the “personal information” received from the unique ID management server 10. The instruction information is transmitted to the service management server 20 (TS22).

  Upon receiving the member registration instruction information, the service management server 20 adds the “member ID expectation information” to the “member ID” in the member information table (FIG. 7), and the “personal information” as the “member”. It is added to “various items of personal information” in the member information table (FIG. 7) in association with “ID expected information” (KS21).

Then, after completing the registration process, the service management server 20 transmits a registration completion notification to the service providing terminal 30 (KS22).
When the service providing terminal 30 receives the registration completion notification from the target service management server 20, the service providing terminal 30 notifies the user of the completion of the member registration by displaying the notification on the display screen (TS23) and receives the member registration. The service management server starts providing service information (TS24).

Since the subsequent processing is the same processing (step TS13) as in the case of an existing member, description thereof is omitted.
(Example 2)
In the first embodiment, personal information registered in the unique ID management server is used as personal information for member registration in the non-member membership registration procedure.

  In the second embodiment, personal information stored in the IC card is used as personal information for member registration. In order to prevent leakage of personal information from the IC card and to authenticate the card user, personal information encrypted with a PIN (Personal Identification Number) is used.

  FIG. 17 is a sequence diagram of card issuance processing performed between the card issuer and the user (user). FIG. 18 is a sequence diagram when the user uses service information in this system.

  These correspond to FIG. 14 and FIG. 15 shown in the first embodiment, respectively. Since most of the procedures in FIGS. 17 and 18 are the same as those in the first embodiment, only the parts different from the first embodiment will be described here.

In FIG. 17, steps OFFS30 and HS30 are different in offline processing, and steps JS30 and HS31 are different from those in the first embodiment in online processing.
In off-line processing, in step OFFS30, “PIN information” is provided in addition to personal information as information to be submitted when applying for a window or mailing.

In step HS30, the card issuer writes personal information encrypted with a PIN in addition to the unique ID into the IC card 40-1.
In the online processing, in step JS30, in the membership application processing, the PIN information is input into the newly added PIN information input field in the application input information screen, and the PIN information is transmitted to the unique ID management server 10 together with the personal information. .

  In the card issuing process in step HS31, first, the personal information is encrypted using the PIN information. Further, instruction information for securing the storage area for the encrypted personal information is added to the instruction signal for securing the storage area for writing information in the IC card.

Then, the unique ID and the encrypted personal information are transmitted to the information terminal 50, and a write instruction to the storage area secured in the IC card is given.
Next, in FIG. 18, a different part from Example 1 (FIG. 15) will be described.

  In the procedure shown in the figure, the procedure for existing members is exactly the same, and the procedure for non-members is the same up to step TS20.

When the user receives a notification of non-membership from the display screen of the service providing terminal, the user performs membership registration processing for the service management server in the following procedure.
First, the user inputs PIN information from the input device of the service providing terminal 30, and instructs the service providing terminal 30 to apply for membership registration (OFFS30). At this time, the user is still notified that the user is not a member (TS30).

After this input, the service providing terminal 30 reads the encrypted personal information from the IC card 40-1 set in the reading device of the service providing terminal 30 (CS30).
Subsequently, the service providing terminal combines the encrypted personal information using the PIN information previously input by the user (TS31).

The subsequent processing is the same as in the first embodiment (FIG. 15), and the combined personal information and member ID are transmitted to the service management server to instruct member registration (TS22).
Thereafter, the processing from step KS21 of the first embodiment (FIG. 15) is performed in the same manner.

(Second embodiment)
FIG. 19 shows a second configuration example of the entire member management system.
The difference in configuration between the member management system 500 and the member management system 1 in the first embodiment is that the service management server that can receive service information from the service providing terminal is specified as any one service management server. is there.

  With this configuration, the service management server that can be accessed from the service providing terminal is limited. Therefore, even if secret information leaks from one service providing terminal, the service information usage information by the user is Limited to management servers. Therefore, it becomes difficult to trace the use of service information across a plurality of service management servers by others.

As described above, in this member management system, a user has only one unique ID and is managed with a different member ID in each of a plurality of service management servers.
In this case, since it is not necessary for the service providing terminal to store the member IDs for the service management server in association with one unique ID, the storage area can be saved.

  In addition, as described above, since it is not necessary to store the member ID for the service management server in association with one unique ID, service usage information by one user is traced over a plurality of services. Can be prevented.

  In particular, since the member ID of each service is generated based on the unique ID for each service based on the unique ID, the member ID of each service is different and even if the history of the member ID of one service flows out. The association with IDs managed by other services is not easy. Even when the usage history associated with the member ID of one service leaks, it is not easily associated with the member ID of another service, so that the user's behavior can be prevented from being traced.

  Further, since the service providing terminal only needs to communicate with the service management server when providing the service to the member, the number of communication with the unique ID management server can be reduced as compared with the conventional configuration. Therefore, the communication concentration load on the unique ID management server is greatly suppressed.

Further, in this system, since the user's personal information can be used at the time of member registration, the member registration work when the user receives a new service is simplified.
Also, in this system, since the user's usage history is recorded at the service providing terminal, the card issuer can grasp the usage status of the user, and based on this information, the service provider can use the system. It is possible to collect a fee.

It is a 1st structural example of the whole member management system. 2 is a hardware configuration diagram of a service providing terminal 30. FIG. It is an example of the system block diagram in the service provision terminal suitable for preventing information leakage. It is an example of a personal information table. It is an example of a service identification information table. It is an example of an inquiry history information table. It is an example of a member information table. It is an example of a server information table. It is an example of a terminal information table. It is an example of a usage history information table. It is an example of a secret information table. It is an example of a usage history information table. FIG. 5 is a sequence diagram of mutual authentication processing between a service providing terminal 30 and a service management server 20. It is a sequence diagram of the card issue process performed between a card issuer and a user (the 1). It is a sequence diagram in case a user uses service information with this system (the 1). It is an example of the algorithm which produces | generates member ID from unique ID. It is a sequence diagram of the card issue process performed between a card issuer and a user (user) (the 2). It is a sequence diagram in case a user uses service information with this system (the 2) It is a 2nd structural example of the whole member management system.

Explanation of symbols

1 Member Management System 10 Unique ID Management Server 20 Service Management Server 30 Service Providing Terminal 40-1 IC Card 40-2 Mobile Phone with IC Card Function 50 Information Terminal with IC Card R / W

Claims (11)

A unique ID management server that manages a user's unique ID, a plurality of service management servers that respectively manage a plurality of service information for members, and a service providing terminal that provides the service information to the user are connected via a communication network. A membership management system comprising:
The service providing terminal is:
Unique ID reading means for reading the user's unique ID;
Member ID generation means for generating a member ID with a different algorithm for each service information based on the read unique ID;
A member confirmation requesting means for transmitting the generated member ID to the service management server and requesting confirmation that the user is a member;
With
The service management server
A member ID holding means for holding a member ID generated by the algorithm different for each service information based on a unique ID in advance;
Inquiry means for making an inquiry about the member ID received from the service providing terminal with the member ID held by the member ID holding means;
Means for authorizing the use of service information corresponding to the service providing terminal when there is a matching member ID by the inquiry;
Comprising
Membership management system characterized by that. A unique ID management server that manages a user's unique ID, a plurality of service management servers that respectively manage a plurality of service information for members, and a service providing terminal that provides the service information designated by the user to the user after member confirmation , Is a member management system configured to be connected via a communication network,
The service providing terminal is:
Unique ID reading means for reading the user's unique ID;
Service identification information holding means for holding identification information of each of the service information;
A member ID generating means for generating a member ID from the identification information corresponding to the service information designated by the user and the read unique ID;
A member confirmation requesting means for transmitting the generated member ID to the service management server managing the service information designated by the user and requesting confirmation that the user is a member;
With
The service management server
Member ID holding means for holding the member ID;
Inquiry means for making an inquiry about the member ID received from the service providing terminal with the member ID held by the member ID holding means;
Means for permitting the service providing terminal to use the corresponding service information when there is a matching member ID by the inquiry;
Comprising
Membership management system characterized by that. The service providing terminal is:
Service usage history reporting means for taking a usage history of the service information used by a user and transmitting the usage history to the unique ID management server;
With
The unique ID management server
Billing processing means for calculating a billing cost for a service provider based on a use history of the service information transmitted from the service providing terminal;
Comprising
The member management system according to claim 1 or 2, wherein Furthermore,
The unique ID management server
Common personal information holding means for holding correspondence information that associates the unique ID with the user's common personal information having the unique ID;
With
The service providing terminal is:
First common personal information acquisition means for acquiring common personal information corresponding to the unique ID read by the unique ID reading means from the unique ID management server;
Member application means for transmitting the member ID generated based on the unique ID and the acquired common personal information to the service management server;
With
The service management server
Additional registration means for additionally registering the member ID and the common personal information transmitted from the service providing terminal in the member ID holding means;
Comprising
The member management system according to any one of claims 1 to 3. Furthermore,
A storage medium for holding a unique ID that holds a unique ID and common personal information of the user of the unique ID;
The service providing terminal is:
Second common personal information acquisition means for reading the common personal information from the storage medium for storing the unique ID;
Member application means for transmitting the member ID generated based on the unique ID and the acquired common personal information to the service management server for member application;
With
The service management server
An additional registration means for additionally registering the member ID and the common personal information transmitted from the service providing terminal in the member ID holding means;
The member management system according to any one of claims 1 to 3. The service providing terminal is:
Expense confirmation information transmitting means for transmitting a usage history of the service information used by the user to the service management server;
Further comprising
The service management server
Billing cost determination means for determining the legitimacy of the billing cost transmitted from the unique ID management server based on the usage history transmitted from the service providing terminal;
Further comprising
The member management system according to any one of claims 1 to 5, wherein Furthermore,
The service providing terminal is:
Provided with security processing means for deleting information for generating a member ID when unauthorized access is detected;
The member management system according to any one of claims 1 to 6. Providing the user with the service information of the service management server that is connected to a unique ID management server that manages a user's unique ID and a plurality of service management servers that respectively manage a plurality of service information for members, through a communication network A service providing terminal,
Unique ID reading means for reading the user's unique ID;
Member ID generation means for generating a member ID with a different algorithm for each service information based on the read unique ID;
A member confirmation requesting means for transmitting the generated member ID to the service management server and requesting confirmation that the user is a member;
Comprising
A service providing terminal characterized by that. A member confirmation method performed at a service providing terminal connected via a communication network to a unique ID management server that manages a user's unique ID and a plurality of service management servers that respectively manage a plurality of service information for members.
Reading the user's unique ID;
Checking whether or not a unique ID is registered in the unique ID management server;
Generating a member ID with a different algorithm for each service information based on the read unique ID;
Transmitting the generated member ID to the service management server, and requesting confirmation that the user is a member;
Providing service information of the service management server to the user when the user is a member;
The member confirmation method of the service provision terminal characterized by performing. Member registration to the service management server performed by a service providing terminal connected to a unique ID management server that manages the user's unique ID and personal information in association with each other and a service management server that manages service information for members. A method,
Reading the user's unique ID;
Generating a member ID with a different algorithm for each service information based on the read unique ID;
Obtaining personal information corresponding to the read unique ID from the unique ID management server;
Transmitting the generated member ID and the acquired personal information to the service management server and instructing the service management server to register a member;
A member registration method for a service providing terminal. The service management using a unique ID holding storage medium that stores a unique ID and personal information connected to a unique ID management server that manages a unique ID of a user and a service management server that manages service information for members via a communication network. A member registration method of a service providing terminal for registering a member to a server,
Reading the unique ID from the storage medium for holding the unique ID;
Generating a member ID with a different algorithm for each service information based on the read unique ID;
Reading the personal information from the storage medium for holding the unique ID;
Transmitting the generated member ID and the read personal information to the service management server and instructing the service management server to register a member;
A member registration method for a service providing terminal.