JP2019091104A - Linkage service provision system, linkage management system for the same, computer program used in the systems - Google Patents

Abstract

To provide a system which ensures security of respective systems while facilitating linkage between services using user identification information shared by individual systems.SOLUTION: A plurality of individual systems 2 respectively generates a card authentication code unique to a common card ID usable as user identification information and linkage authentication codes unique to the common card ID within a service identified by a service ID for respective individual systems 2. A linkage management system 3 links the card authentication code with the common card ID and linkage data, records the linkage authentication codes in association with the service ID and the card authentication code, and, when an access is requested by any of the individual systems 2 with the service ID and the linkage authentication code designated, determines the associated card authentication code and allows the linkage data corresponding to the card authentication code to be used.SELECTED DRAWING: Figure 3

Description

  The present invention relates to an interlocked service providing system and the like capable of causing interlocking relationships in services among a plurality of systems that identify users and provide services.

  For example, as a system for creating an interlocking relationship between a plurality of services provided via a network, a mobile ID used for identifying a user in a service provided for a mobile terminal, and a PC (personal computer) There is known a system in which a game play record is shared among services by setting an association with a game ID used for user identification in a service provided for reference). When a predetermined condition is satisfied in the game machine, a two-dimensional code is displayed on the screen of the game machine, and the two-dimensional code is read by a mobile communication terminal such as a mobile phone to guide the user to linked Web content. Another known system is also known (see Patent Document 2).

JP, 2014-16992, A JP, 2006-198296, A

  When linking user identification information such as an ID unique to each service in order to create interlocking relationships among multiple services, the user needs to acquire and use different user identification information for each service. Will occur. If user identification information is shared among a plurality of services, such a disadvantage does not occur. However, in order to create an interlocking relationship between services, it is necessary to allow mutual use between services with respect to at least a part of information required to provide the services. If the user identification information is standardized, the difference between services can not be immediately determined from the identification information, which may cause a problem in the security of the individual system providing each service. For example, the scope of services that should generate interlocking relationships is limited between individual systems where the management entity and the operation entity are different, and outside that range, other individual systems may be used for management or operation convenience of each individual system. Want to build a closed system. However, if the user identification information is shared between the individual systems, it is difficult to determine whether the user of the service provided by the own system or the user of the service provided by another individual system is different. There is a possibility that it can not exclude the use of the service out of the restriction range by the system.

  Therefore, the present invention can secure security of each individual system while achieving user's convenience by creating interlocking relationship between services using user identification information shared among a plurality of individual systems. It aims at providing a linked service providing system etc.

  The interlocked service providing system according to an aspect of the present invention includes a plurality of individual systems for providing a predetermined service to a user authenticated based on predetermined identification information, and a predetermined number of services of the plurality of individual systems. The interlocked service providing system includes an interlocked management system that manages interlocked data for generating interlocked relationship between the above, and common identification information that can be used as the identification information in each of the plurality of individual systems. Common authentication information generation means for generating common authentication information uniquely associated with each other, and interlocking authentication information corresponding to the common identification information in at least the common identification information within the range of services that should cause the interlocking relationship Interlocking authentication information generation means which is generated for each individual system so as to be uniquely associated with each other. The interlocking management system records the common authentication information in a predetermined storage unit in association with the common identification information and the interlocking data, and uniquely identifies the interlocking authentication information with respect to the service range. Association setting means for recording in the storage means in association with the set service identification information and the common authentication information, and access is requested by specifying the service identification information and the interlocking authentication information from any of the individual systems In the case, the user authentication means for determining the common authentication information associated with the designated service identification information and the authentication information for linkage, and the linkage data associated with the determined common authentication information, and relates to the determined linkage data And a use management means for permitting use of the individual system of the request source.

  An interlocking management system according to an aspect of the present invention is combined with a plurality of individual systems for providing a predetermined service to a user authenticated based on a predetermined identification information, and a predetermined number of services of the plurality of individual systems are provided. Interlocking management system for managing interlocking data for generating interlocking relationships of the common authentication information uniquely associated with common identification information that can be used as the identification information in each of the plurality of individual systems Common authentication information generation means for generating the common authentication information in association with the common identification information and the interlocking data, and recording the common authentication information in a predetermined storage means, at least within the range of services that should cause the interlocking relationship The association authentication information generated for each individual system uniquely associated with the common identification information is Association setting means for recording in the storage means in association with service identification information uniquely set for each service range and the common authentication information, and specifying the service identification information and the interlocking authentication information from any individual system If access is requested, the user authentication means for determining the common authentication information associated with the designated service identification information and the authentication information for linkage, and the linkage data associated with the determined common authentication information are determined. And a use management means for permitting use of the individual system of the request source regarding the determined interlocking data.

A computer program according to an aspect of the present invention includes a plurality of individual systems for providing a predetermined service to a user authenticated based on predetermined identification information, and a predetermined interlocking relationship between services of the plurality of individual systems. A computer program applied to a computer of a linked service providing system including a linked management system for managing linked data for generating a computer program, the computer comprising: the identification information in each of the plurality of individual systems Means for generating common authentication information generating means for generating common authentication information uniquely associated with common identification information that can be used as a service, and at least interlocking service for interlocking authentication information corresponding to the common identification information. Uniquely associated with the common identification information within the And causing the computer of the interlocking management system to associate the common authentication information with the common identification information and the interlocking data in a predetermined storage unit. Association setting means for recording the interlocking authentication information in association with the service identification information uniquely set for the service range and the common authentication information, and recording the same in the storage means from any of the individual systems User authentication means for determining common authentication information associated with specified service identification information and interlocking authentication information when access is requested by specifying the service identification information and the interlocking authentication information, and determined The interlocked data associated with the common authentication information is determined, and the determined interlocked data is That the requesting those that are configured to function as a usage management means for permitting the use of the individual systems.
Computer program.

  A computer program according to another aspect of the present invention is combined with a plurality of individual systems for providing a predetermined service to a user who has been authenticated based on a predetermined identification information, and a predetermined number of services of the plurality of individual systems are provided. A computer program applied to an interlocking management system for managing interlocking data for generating interlocking relationships between the plurality of individual systems, wherein the computer of the interlocking management system can be used as the identification information in each of the plurality of individual systems Common authentication information generation means for generating common authentication information uniquely associated with common identification information, recording the common authentication information in a predetermined storage means in association with the common identification information and the interlocked data Within the scope of services that should cause the interlocking relationship to the common identification information Association setting in which association authentication information uniquely associated with each other and generated for each individual system is associated with service identification information uniquely set for each service range and the common authentication information and recorded in the storage means When the access is requested by specifying the service identification information and the interlocking authentication information from any of the individual systems, the common service identification information associated with the designated service identification information and the interlocking authentication information is determined. It is configured to function as a user authentication means and usage management means for determining interlocking data associated with the determined common authentication information, and permitting use of the individual system of the request source regarding the determined interlocking data. is there.

FIG. 1 is a diagram showing an overall configuration of a linked service providing system according to an embodiment of the present invention. FIG. 2 is a view showing an example of the association between various types of IDs, codes and data used in the linked service providing system of FIG. 1; The functional block diagram which shows an example of a structure of the principal part linked | related with management of interlocking | linkage relationship in the interlocking | linkage type service provision system of FIG. The flowchart which shows an example of the procedure of the interlocking use setting process performed by an individual system. FIG. 5 is a flowchart showing an example of the procedure of an interlocked use setting process executed by the interlocked management system corresponding to the process of FIG. 4; FIG. The flowchart which shows an example of the procedure of the interlocking | linkage management process performed by an individual system. The flowchart which shows an example of the procedure of the interlocking | linkage authentication process performed by a interlocking | linkage management system. The flowchart which shows an example of the procedure of the process performed in each individual system and interlocking | linkage management system, in order to manage provision and utilization of the service between individual systems.

  Hereinafter, an example of a linked service providing system according to an embodiment of the present invention will be described with reference to the drawings. The linked service providing system 1 of FIG. 1 is an example configured by combining two individual systems 2A and 2B and a linked management system 3. However, the number of individual systems is not limited to two, and may be changed as appropriate. Below, when it is not necessary to distinguish each of separate system 2A, 2B, it may be described with separate system 2. FIG.

  Each individual system 2 is associated with a game via a predetermined network with respect to a client 4 such as, for example, a game machine 4A that allows the user to play a game and a mobile communication terminal device 4B such as a smartphone personally used by the user It is configured as a server system that provides services. In FIG. 1, a single game machine 4A and a single mobile communication terminal 4B are shown as an example of the client 4 for each individual system 2. However, in practice, many game machines 4A and mobile phones are used. The communication terminal 4 B can access the individual system 2 as the client 4. The client 4 is not limited to the game machine 4A and the portable communication terminal device 4B, and a PC, a tablet terminal, a stationary video game machine, a portable game machine or the like may be used as an example of the client 4 as appropriate. The client 4 may be different between the individual systems 2. Although the service provided by the individual system 2 does not necessarily have to be a service associated with a game, the following description will be made taking the case of providing a service related to a game as an example.

  Each of the individual systems 2A and 2B includes a server 6 and a database group 7 appropriately accessed by the server 6. The server 6 is configured by appropriately combining a plurality of server units 6A, 6B,. The server 6 may be configured by a single server unit, or may be configured as a cloud server using cloud computing technology. The database group 7 includes various databases necessary to provide services related to the game. As an example, the database group 7 of the individual system 2A includes a user database DB1, a content database DB2, an account management database DB3, and an interlocking management database DB4. The database group 7 functions as an example of storage means of the individual system 2A by including a storage for recording data and a database server for controlling the recording of data in the storage. Only the databases DB1 to DB4 stored in FIG.

  The user database DB1 is a database in which data associated with the user is recorded. For example, information necessary for user authentication, play data in which the user's play is recorded, and the like are recorded in the user database DB1. The content database DB2 is a database in which various types of content associated with the game are recorded. The account management database DB3 is a database in which account data for each user in which the balance of the electronic currency owned by the user is recorded, and various data associated with the other electronic currency are recorded. The electronic currency recorded in the account management database DB3 can be used to pay for the service provided by at least the individual system 2A. The interlocking management database DB4 is a database in which various data necessary for causing interlocking relationships in services between the individual systems 2 are recorded.

  The server 6 of the individual system 2A provides play data recorded in the user database DB1 to the game machine 4A, or receives play data from the game machine 4A and records it in the user database DB1, or is recorded in the content database DB2 A service is provided to provide content to the mobile communication terminal 4B. This type of service is implemented by various known game systems, and may be implemented by the individual system 2A as well. Therefore, the details will not be described. In addition, the server 6 of the individual system 2A also provides a service for paying the charge using the electronic currency recorded in the account management database DB3. For example, the user owns a charge for playing a game on the game machine 4A, and a charge for purchasing content such as an item related to a game using the game machine 4A or the mobile communication terminal 4B. It can be paid by consumption of electronic currency. This kind of payment service may be implemented in the same manner as a known online payment system, and the details will not be described.

  The server 6 of the individual system 2A acquires the user identification information from the client 4, and verifies the acquired identification information with the information recorded in the user database DB1 to authenticate the user. In the individual system 2A, a card ID unique to each card recorded in the card 8 owned by the user, or a user ID uniquely set for each user using a website etc. is appropriately used as user identification information . For example, the server 6 acquires a card ID as user identification information in response to access from the game machine 4A, and acquires a user ID as user identification information in response to access from the mobile communication terminal device 4B. The card ID and the user ID are associated with each other, and it is possible to determine the other ID based on any one ID. Information for determining the association between the card ID and the user ID is recorded in the user database DB1 as an example.

  Among various types of data to be recorded in the user database DB1, the content database DB2 and the account management database DB3, data to be associated with the user is appropriately correlated and recorded with the card ID or the user ID. For example, data associated with the use in the game machine 4A is recorded in association with the card ID, and data associated with the use in the mobile communication terminal device 4B is recorded in association with the user ID. Account data in the account management database DB3 may be recorded, for example, in association with a unique account ID for each user. In that case, by setting an association between the account ID and the user ID and the card ID, the account data of the user may be determined based on the card ID or the user ID. The user database DB1 may be further divided into a database in which data is recorded in association with a card ID and a database in which data is recorded in association with a user ID.

  At least a part of the card 8 used for authenticating the user in the individual system 2A is issued as a common card in which a common card ID that is also valid as user identification information is set in the other individual systems 2B. In the linked service providing system 1 of this embodiment, the linked relationship between the individual systems 2 is managed based on the common card ID. The server 6 of the individual system 2A cooperates with the interlocking management system 3 to realize interlocking. The interlocking management database DB4 appropriately records information required to be held by the individual system 2 among the information necessary for interlocking. Details will be described later.

  The database group 7 of the individual system 2B is configured in substantially the same manner as the database group 7 of the individual system 2A, and its server 6 authenticates users using the user database DB1 and manages play data, and content of games using the content database DB2 And various processes necessary for managing interlocking using the interlocking management database DB4. However, the configuration of each individual system 2 can be changed as appropriate. For example, in FIG. 1, the function of providing the settlement service to the server 6 of the individual system 2B is not implemented, and therefore, the account management database DB3 does not exist in the database group 7 of the individual system 2B.

  The interlocking management system 3 includes a server 10 and a database group 11 appropriately accessed by the server 10. The server 10 is configured by appropriately combining a plurality of server units 10A, 10B,... The server 10 and the servers 6 of the individual systems 2 are communicably connected to each other via a predetermined network, for example, the Internet. The server 10 may be configured by a single server unit, or may be configured as a cloud server using cloud computing technology. The database group 11 includes various databases necessary to manage the interlocking relationship between the services of the individual systems 2. As an example, the database group 11 of the interlocked management system 3 includes the database DB11 of the card authentication code, the database DB12 of the interlocked authentication code, and the database DB13 of interlocked data. The card authentication code and the interlocking authentication code are information used for authenticating the user in the interlocking management system 3. These codes and the databases DB11 and DB12 will be described in detail later. The database group 11 functions as an example of storage means in the interlocking management system 3 by including a storage for recording data and a database server for controlling the recording of data in the storage, but in FIG. Only the databases DB11 to DB13 stored in FIG. 11 are illustrated.

  The interlocking data is data for causing an interlocking relationship between the services of the individual systems 2A and 2B. The interlocking relationship is, for example, a relationship in which a predetermined change occurs in the other game when the content of the user's play for one game satisfies a predetermined condition between the games provided by each of the individual systems 2A and 2B. Is set. In that case, in the interlocking data, information for determining whether or not a predetermined condition is satisfied in one game is recorded as a type of information for causing an interlocking relationship. The predetermined condition in one game is set in association with information indicating how long the user played the game, such as the number of times the user played, the play time, the play time, and the amount paid for the play fee. It may also be set in association with information indicating what kind of result the user left in the game, such as the score of the user, the progress of the game, and the progress of the specific task. The changes that occur in the other game according to the interlocking relationship may also be used to grant items that can be used in the game, to allow the play of special stages or modes, to discount the play fee, to pay the play fee, etc. in the individual system 2 It may be set as appropriate, such as giving possible points or other monetary value or playing value. Alternatively, it is not limited to the interlocking relationship in which a change occurs in the other game based on the result of one game, and at least one of the games when the predetermined condition is satisfied in both of the interlocking games. It is also possible to make a setting such that a change occurs as a kind of interlocking relationship, or a setting such that a change occurs in both games if the condition is satisfied in at least one of the games. In any case, what kind of interlocking relationship is generated between the services of the individual systems 2A and 2B, and what kind of information is recorded in interlocking data in association with the interlocking relationship is managed by managing the individual systems 2A and 2B. Or, it may be set appropriately between the operating entities. The management entity or the management entity of each individual system 2 may be different from each other or may be the same.

  Next, with reference to FIG. 2, the relationship between various types of IDs and codes used in the linked service providing system 1 will be described. As described above, each individual system 2 can use the common card ID as the identification information of the user. The common card ID is associated with a unique user ID for each user in each individual system 2. The user ID may be generated appropriately for each individual system 2. The user ID is also associated with the interlocking authentication code. The interlocking authentication code is information generated for authenticating the user on the server 10 of the interlocking management system 3, and is an example of interlocking authentication information. In each individual system 2, the cooperation authentication code is also associated with the common card ID by using the user ID as an intermediary by being associated with the user ID. The interlocking authentication code is generated for each individual system 2. The numbering rule for generating the interlocking authentication code may be set appropriately for each individual system 2. Therefore, the interlock authentication code corresponding to each of the different common card IDs may overlap among the individual systems 2.

  The interlocking authentication code is further associated with the service ID. The service ID is an example of service identification information that is set in each individual system 2 to identify the range of the service that should cause the interlocking relationship. Among the services provided by each individual system 2, the service ID is uniquely set for each of the ranges of services for which it is desired to set an interlocking relationship as a unit. The service ID is uniquely set in the entire linked service providing system 1. Therefore, service IDs do not overlap for different service ranges between different individual systems 2. For example, the service ID may be generated on the side of the interlocked management system 3 and provided to the individual system 2 or may be generated in the individual system 2 according to rules differentiated for each individual system 2. In any case, a unique service ID may be generated throughout the system 1.

  In the example of FIG. 1, the service ID is set to include all the services for each individual system 2. That is, a single service ID is set for all services provided by the individual system 2A, and a single service ID different from the service ID of the individual system 2A for all services provided by the individual system 2B. Is set. However, services provided by one individual system 2 may be divided into a plurality of groups, and a service ID may be uniquely set for each group. Even when the same common card ID is used as user identification information in each individual system 2 by setting the service ID to be mutually unique throughout the linked service providing system 1, the service ID and the common card ID Even if the interlocking authentication code corresponding to each of the different common card IDs overlaps between the individual systems 2 by combining with the interlocking authentication code corresponding to the user of the service of the individual system 2 and the user who uses the service And can be uniquely identified.

  In the example of FIGS. 1 and 2, since a single service ID is set for each individual system 2, each individual system 2 generates one interlocking authentication code corresponding to one common card ID. Ru. However, the interlock authentication code corresponding to one common card ID may be separately generated for each service range in which the service ID is set. That is, in the case where a plurality of service IDs are set in one individual system 2, the interlock authentication code may be generated separately for each service ID. In that case, the authentication code for interlocking corresponding to the same common card ID may be identical or different among a plurality of service IDs. That is, the interlock authentication code may be unique to the common card ID within the range of services identified by a single service ID. If the service ID is different, it does not matter whether the interlocking authentication codes corresponding to the different common card IDs overlap or not. In short, the interlocking authentication code may be unique to the common card ID at least within the range of the service that should cause interlocking.

  The interlocking authentication code is further associated with the card authentication code. The card authentication code is a code uniquely generated for the common card ID. The card authentication code is used to authenticate the user in the interlocking management system 3 and to manage interlocking data for each user. The card authentication code is an example of common authentication information unique to the common card ID. The card authentication code is associated with all of the interlocking authentication codes of the individual systems 2 associated with the same common card ID. That is, the interlock authentication code is associated with the card authentication code in a one-to-many relationship.

  Interlocking data is generated for each card authentication code. Interlocking data corresponding to one card authentication code may be further divided by interlocking ID. The interlocking ID is an example of event identification information that is uniquely set for each event in order to identify an event set between services that should generate interlocking relationships among the individual systems 2. An event is a concept that divides interlocking relationships set between individual systems 2. For example, when setting up an interlocking relationship between a specific game provided in the individual system 2A and a specific game provided in the individual system 2B, the concept of dividing that interlocking relationship from other interlocking relationships Is called an event, and an interlocking ID is set as an example of event identification information for identifying the event. Various interlocking relationships can be set between the individual systems 2, and various data for managing the interlocking relationships are recorded in interlocking data. The interlocking ID is used as information for uniquely specifying target data from interlocking data. A common interlocking ID is set for the same event among the individual systems 2. However, when it is not necessary to distinguish and manage interlocking data for each event, the interlocking ID may be omitted. The event may be associated with various elements such as time, area, user attribute, etc., and the scope may be limited, or may be implemented without limitation without such limitation being set.

  As described above, when the association between the common card ID and the interlocking data is set, in the interlocking management system 3, the common card ID of the user can be obtained by acquiring the service ID and the interlocking authentication code from each individual system 2. The card authentication code corresponding to can be determined to authenticate the user. Then, by specifying interlocking data corresponding to the determined card authentication code, it is possible to make the individual system 2 use interlocking data corresponding to the common card ID. If the interlocking ID is notified from the individual system 2 to the interlocking management system 3, it is possible to use the interlocking data corresponding to the interlocked ID for the individual system 2 only.

  By using the service ID and the interlocking authentication code for authenticating the user in the interlocking management system 3, the individual system 2 supports the card authentication code and other individual systems 2 when accessing the interlocking management system 3. There is no need to know any of the interlocking authentication codes. There is no need to provide such information from the interlocking management system 3 to the individual system 2. That is, in order to create interlocking relationships between services of the individual systems 2 via interlocking data, each individual system 2 notifies at least a service ID and an interlocking authentication code to the interlocking management system 3, and interlocks as necessary. All you need to know is the ID. It is not necessary to disclose the user ID used by each individual system 2 in its own system 2 to the link management system 3 or other individual systems 2. The interlocking authentication code used by each individual system 2 to access the interlocking management system 3 can be set independently for each individual system 2. Each individual system 2 does not know how another individual system 2 generates an interlocking code for the common card ID to access the interlocking management system 3. Information can be concealed for each individual system 2. On the other hand, even if the interlocking authentication code is uniquely set for each individual system 2, the service ID and the interlocking authentication code are associated with each other, so in the interlocking management system 3, access is performed using the service ID as a clue. It is possible to identify the service of the individual system 2 making a request and the user thereof, determine the card authentication code corresponding to the common card ID of the user, and determine the interlocking data corresponding thereto.

  The interlocking authentication code is different from the common card ID and user ID used for user authentication when each individual system 2 provides the internal service to the user, and the interlocking authentication code and the common card ID and user ID The association between can be set independently by each individual system 2. Therefore, even if one of the individual systems 2 acquires the interlocking authentication code of another individual system 2 via the interlocking management system 3, the inside of the other individual system 2 is accessed from the interlocking authentication code. It is impossible to determine the method of and the information necessary for its access. Even if one of the individual systems 2 acquires the authentication code for interlocking of another individual system 2 and accesses the other individual system 2, whether or not to provide a service for the access depends on each individual system 2 can be controlled independently. Therefore, it is possible to hide various information held in each individual system 2 from other individual systems 2. Therefore, security of each individual system 2 can be secured.

  The common card ID is information that can be known by any of the individual systems 2, and each individual system 2 is permitted to provide a service using the common card ID as user identification information. However, each individual system 2 can independently set how to authenticate the user using the common card ID. Therefore, even if one of the individual systems 2 attempts to access another individual system 2 using the common card ID, the other individual systems can be set appropriately by setting the procedure such as user authentication based on the common card ID. Security in the individual system 2 can be secured by excluding the use of the service based on the common card ID from 2. For example, when the game machine 4A is configured as a business game machine, unique identification information for each game machine 4A, or an address on the network set for the game machine 4A (an IP address as an example) It is possible to identify the game machine 4A by using the address), and by using the common card ID based on the common card ID by limiting the access to the game machine 4A, the common card ID from the other individual system 2 is used. It is possible to deny access. On the other hand, it is also possible to control to provide a service within a certain range with respect to access using the interlocking authentication code from another individual system 2.

  Next, with reference to FIG. 3, an example of a more specific configuration of the interlocked service providing system 1 will be described. However, FIG. 3 shows the main parts necessary to manage the interlocking relationship using the above-mentioned ID and code, and the following description also centers on the part relating to the interlocking relationship. Moreover, although the relationship of the single separate system 2 and the interlocking | linkage management system 3 is shown in FIG. 3, the other separate system 2 is also the same. The individual system 2 is provided with a control unit 20 and a storage unit 21. The control unit 20 is a computer configured by one or more computer units included in the server 6 of the individual system 2, and the storage unit 21 is an external storage device of the computer. The storage unit 21 stores a computer program (hereinafter abbreviated as a program) PG1. The control unit 20 is provided with a service management unit 22, an interlock management unit 23, and an interlock code for authentication code generation unit 24 as logical devices realized by a combination of the hardware resources of the computer and the program PG1. The service management unit 22 authenticates the user for access from the client 4 using the common card ID or the user ID, and provides a predetermined service to the authenticated user. The service management unit 22 may be appropriately divided and provided according to its function.

  The interlocking management unit 23 executes various processes for managing interlocking relationships in cooperation with the interlocking management system 3. The interlocking authentication code generation unit 24 generates an interlocking authentication code in response to a request from the interlocking management unit 23. That is, a module for causing a predetermined interlocking relationship in cooperation with the interlocking management system 3 is included in the program PG1, and the hardware resource of the control unit 20 executes the module to execute the interlocking management unit 23 and An interlocking authentication code generation unit 24 is provided. Thereby, the function necessary for controlling the interlocking relationship using the interlocking management system 3 is added to the individual system 2. In the interlocking management database DB4, the interlocking authentication code is recorded in association with the user ID, but when the interlocking authentication code is generated for each service ID, the service ID and the interlocking authentication code are correlated and interlocked It is recorded in the management database DB4. However, when a single service ID is set in the entire service of the individual system 2, the interlocking authentication code does not necessarily need to be recorded in association with the service ID. When the interlocking ID is set, the interlocking ID is also recorded in the interlocking management database DB4.

  The interlocking management system 3 is provided with a control unit 30 and a storage unit 31. The control unit 30 is a computer configured by one or more computer units included in the server 10 of the interlocked management system 3, and the storage unit 31 is an external storage device of the computer. The storage unit 31 stores a program PG2. As the logical device realized by the combination of the hardware resource and the program PG 2 in the control unit 30, the interlock setting unit 32, the card authentication code generation unit 33, the user authentication unit 34, the interlocked data management unit 35, and the interlocking device An authentication code providing unit 36 is provided.

  The interlock setting unit 32 takes charge of various settings necessary for causing the individual system 2 to use interlocked data. As an example of the setting, when the card authentication code is newly generated or the interlocking authentication code is newly generated in the individual system 2, the interlocking setting unit 32 causes the card authentication code to be transmitted to the database DB11, and the authentication for interlocking is performed. The code is recorded in the database DB12 respectively. When a card authentication code is newly generated, the interlock setting unit 32 records the card authentication code in the database DB11, and associates interlock data corresponding to the card authentication code in the database DB13 with the card authentication code. Record. Further, the interlocking setting unit 32 acquires, from the interlocking management unit 23 of the individual system 2, the interlocking card authentication code generated in the individual system 2 and the common card ID and service ID corresponding to the interlocking authentication code, The obtained association authentication code is recorded in the database DB 12 in association with the card authentication code and the service ID corresponding to the common card ID. The card authentication code generation unit 33 generates a card authentication code corresponding to the common card ID in response to a request from the interlock setting unit 32.

  The user authentication unit 34 acquires the service ID and the interlocking authentication code from the individual system 2 and sets the service ID and the interlocking authentication code while referring to the database DB11 of the card authentication code and the database DB12 of the interlocking authentication code. The card authentication code corresponding to is determined to authenticate the user. The interlocked data management unit 35 acquires the card authentication code of the user whose user authentication is completed from the user authentication unit 34, searches the database DB 13 using the card authentication code as a key, and identifies interlocked data corresponding to the card authentication code. , Make the individual system 2 use the interlocking data. The use in this case may include both writing and reading of interlocked data. When the interlocked ID is set, the user authentication unit 34 acquires the interlocked ID from the interlocked management unit 23 of the individual system 2 and notifies the interlocked data management unit 35 of the interlocked ID together with the card authentication code. In that case, the interlocking data management unit 35 identifies interlocking data corresponding to both the card authentication code and the interlocking ID, and causes the individual system 2 to use the interlocking data. The interlocking authentication code provision unit 36 acquires an interlocking authentication code associated with the service ID of another individual system 2 in response to a request from any of the individual systems 2, and the interlocking authentication code is a request source. Provided to individual system 2

  Next, with reference to FIGS. 4-8, an example of the procedure regarding the various processes which control part 20, 30 of each system 2 and 3 performs is demonstrated. FIGS. 4 and 5 show an example of the procedure of the interlocked use setting process executed by the control units 20 and 30 in order to enable the use of the interlocked data by the individual system 2. FIG. 4 is an example of processing by the interlocking management unit 23 and the interlocking authentication code generating unit 24 of the individual system 2, and FIG. 5 is an example of processing by the interlocking setting unit 32 and card authentication code generating unit 33 of the interlocking management system 3. is there. First, processing in the individual system 2 will be described with reference to FIG. The process of FIG. 4 is started based on an instruction from a user who uses the game machine 4A or an instruction from the user from the mobile communication terminal device 4B, as an example. However, it is assumed that the association between the user's common card ID and the user ID has been completed before the interlock setting process is started.

  When the linked use setting process of FIG. 4 is started, the linked management unit 23 first determines the common card ID and the user ID to be processed (step S11). For example, in the case of executing the processing of FIG. 4 based on an instruction from the game machine 4A, the game machine 4A is made to read the common card ID recorded on the user's card 8 and the obtained common card ID is While acquiring from the device 4A, the user ID corresponding to the common card ID may be determined. When the process of FIG. 4 is executed based on an instruction from the mobile communication terminal device 4B, the user ID may be acquired from the mobile communication terminal device 4B and the common card ID corresponding to the user ID may be determined. .

  After determining the common card ID and the user ID, the interlocking management unit 23 refers to the interlocking management database DB 4 to determine whether or not the interlocking authentication code associated with the user ID is already recorded (step S12). ). When the interlocking authentication code is not recorded, the interlocking management unit 23 requests the interlocking authentication code generating unit 24 to generate the interlocking authentication code, and the interlocking authentication code generating unit 24 responds to this by the interlocking authentication code. Are generated (step S13). The interlocking authentication code may be generated in accordance with an appropriate numbering rule. It is not necessary to match the numbering rules between the individual systems 2, and the numbering rules may be freely set for each individual system 2. When a plurality of service IDs are set in one individual system 2, a single interlocking authentication code may be generated for all the service IDs, or the interlocking authentication for each service ID. Code may be generated. When the range of the service that the user wants to use is limited to the range associated with the partial service ID, the service ID corresponding to the range of the service used by the user is further determined in step S11, In step S12, it may be further determined whether or not the interlocking authentication code corresponding to the service ID is recorded.

When the interlocking authentication code is generated, the interlocking management unit 23 designates the common card ID, the service ID, and the interlocking authentication code to the interlocking setting unit 32 of the interlocking management system 3 to use interlocking data. Request the necessary settings (step S14). When one service ID is set in the entire individual system 2, the service ID may be determined from the interlocking management database DB4 at this stage and designated. If the service ID is determined in step S11, the service ID may be designated. After the setting request, the interlocking management unit 23 determines whether the setting completion has been notified from the interlocking setting unit 32, and repeats the determination until the completion is notified (step S15). When the setting completion is notified, the linkage management unit 23 records the linkage authentication code generated in step S13 in association with the service ID and the user ID to be compatible with it in the linkage management database DB4 (step S16). .
Next, the interlocking management unit 23 notifies the user that the interlocked use setting has been completed (step S17), and thereafter ends the processing of FIG. If it is determined in step S12 that the interlocking authentication code has already been recorded, the interlocking management unit 23 notifies the user that interlocked use has been set (step S18), and then the process of FIG. 4 is performed. Finish.

  Next, the interlocked use setting process in the interlocked management system 3 will be described with reference to FIG. The process of FIG. 5 is started in response to the setting request of step S14 of FIG. When the linked use setting process of FIG. 5 is started, the linked setting unit 32 determines the common card ID designated from the individual system 2 (step S21), and the card authentication code corresponding to the common card ID is stored in the database DB11. It is determined whether it is already recorded (step S22). If not recorded, the interlock setting unit 32 requests the card authentication code generation unit 33 to generate a card authentication code by designating the common card ID, and the card authentication code generation unit 33 sets the common card ID accordingly. A corresponding card authentication code is generated (step S23). In this case, a unique card authentication code is generated for the common card ID. For example, a card authentication code unique to the common card ID may be generated by converting the common card ID according to a predetermined conversion rule.

  After the card authentication code is generated, the interlock setting unit 32 records the card authentication code in the database DB 11 in association with the common card ID determined in step S21 (step S24). Subsequently, the interlock setting unit 32 newly generates interlocked data to be made to correspond to the newly generated card authentication code, associates the interlocked data with the card authentication code, and records the interlocked data on the database DB 13 to perform card authentication. Interlock data corresponding to the code is prepared (step S25). In this case, the interlocking data may be null data without a value or data into which a predetermined initial value is written. Subsequently, the interlocking setting unit 32 associates the service ID designated from the individual system 2 with the interlocking authentication code, records them in the database DB12, and their service ID and interlocking authentication code, and step S24. An association is set with the card authentication code recorded in the database DB 11 (step S26). After that, the interlocking setting unit 32 notifies the individual system 2 that requested the interlocking use setting of the setting completion (step S27). Thus, the interlocked use setting process of FIG. 5 ends.

  If it is determined in step S22 of FIG. 5 that the card authentication code is recorded, the interlock setting unit 32 skips steps S23 to S25 and proceeds to the process of step S26. If a card authentication code corresponding to the common card ID already exists, a card authentication code corresponding to the same common card ID is generated in response to a setting request from another individual system 2 or the like, and the card authentication code is generated. This is because there is also linked data associated with it.

  Next, with reference to FIG. 6 and FIG. 7, an example of the procedure of the process which the control parts 20 and 30 perform in order to manage utilization of interlocking | linkage data in correlation with provision of the service from the separate system 2 to a user is demonstrated Do. 6 shows an example of interlocking management processing by the service management unit 22 and the interlocking management unit 23 of the individual system 2. FIG. 7 shows interlocked authentication by the user authentication unit 34 and the interlocked data management unit 35 of the control unit 30 of the interlocking management system 3. It is an example of processing. First, interlocking management processing in the individual system 2 will be described with reference to FIG. The process of FIG. 6 is started, for example, based on an instruction from a user who uses the game machine 4A or an instruction from a user from the mobile communication terminal device 4B. However, it is assumed that the association between the common card ID of the user and the user ID is completed before the interlocked management process is started.

  When the interlocked management process of FIG. 6 is started, the service management unit 22 of the individual system 2 authenticates the user based on the user identification information (step S41). For example, the service management unit 22 acquires a common card ID from the game machine 4A, or acquires a user ID as user identification information from the mobile communication terminal device 4B, and the obtained user identification information is recorded in the user database DB1. Authenticate the user on the condition that However, in addition to the user identification information, a password or other authentication information may be further used to authenticate the user. User authentication in the individual system 2 can be appropriately set for each individual system 2. In addition, processing in the case where user authentication is not established may be appropriately set for each individual system 2. In addition, when user authentication is already completed at the time of process start of FIG. 6, the process of step S41 may be skipped.

  Next, the service management unit 22 determines whether to provide a service using the interlocking data (step S42). This determination may be performed according to appropriate conditions. For example, when the user uses a service in which the interlocking relationship is set, utilization of interlocking data may be positively affirmed without exception, and whether to use interlocking data may be determined based on the user's instruction. It is also good. When the user uses a service for which the interlocking relationship is not set, step S42 may be uniformly denied. If it is determined in step S42 that the interlocking data is to be used, the service management unit 22 requests the interlocking management unit 23 to specify a user ID and requests processing, and in response to this, the interlocking management unit 23 determines the user ID It is determined whether or not the linkage authentication code associated with the link is recorded in the linkage management database DB4 (step S43). When the interlocking authentication code is separately managed for each service ID, the interlocking management unit 23 determines the service ID of the service to be the target of using the interlocking data, and is associated with the user ID and the service ID. It is determined whether there is a linked authentication code.

  If it is determined in step S43 that the interlock authentication code is present, the interlock management unit 23 determines the service ID set for the service used by the user (step S44). If the service ID is determined in the process of step S43, the service ID may be used. When an event is set for a service that uses interlocked data and interlocked data corresponding to a specific event is used, the interlocked ID corresponding to the event is also determined in step S44 based on the interlocked management database DB4. Be done. Next, the interlocking management unit 23 designates the interlocking authentication code that is determined to correspond to the user ID in step S43, the service ID determined in step S44, and the interlocking ID as necessary to further control the interlocking management system. The linked authentication is requested to the user authentication unit 34 of 3 (step S45). The interlocked authentication is a process of authenticating the user by the interlocked management system 3 using the service ID and the interlocked authentication code, and an example thereof is the process of FIG.

  After requesting interlocked authentication in step S45, the interlocked management unit 23 determines whether authentication completion has been notified from the user authentication unit 34 (step S46). When the authentication completion is notified, the interlocking management unit 23 notifies the service management unit 22 to that effect, and in response to this, the service management unit 22 cooperates with the interlocking data management unit 35 of the interlocking management system 3 to interlock data Start providing the service to the user while using (step S47). Thus, the process of FIG. 6 ends.

  If it is determined in step S43 that the interlocking authentication code is not recorded, the interlocking management unit 23 guides the user to instruct the interlocked use setting of FIG. 4 (step S48), and then the process of FIG. 6 is performed. Finish. This is because it is determined that the settings necessary for using the interlocking data have not been made yet. If it is determined in step S46 that the authentication completion has not been notified, the interlocking management unit 23 determines whether an error has been notified from the user authentication unit 34 (step S49). If the error is not notified, the interlocking management unit 23 returns to the process of step S46. When an error is notified, the interlocking management unit 23 executes a predetermined error process (step S50), and thereafter ends the process of FIG.

  Next, referring to FIG. 7, the interlocked authentication process in the interlocked management system 3 will be described. The process of FIG. 7 is started in response to the interlocked authentication request of step S45 of FIG. When the linked authentication process of FIG. 7 is started, the user authentication unit 34 determines the service ID and the linked authentication code specified from the individual system 2 (step S61), and the designated linked authentication code is the service ID. It is determined whether or not it is recorded in the database DB 12 in association with (step S62). If the interlock authentication code is present, the user authentication unit 34 determines the card authentication code associated with the designated interlock authentication code (step S63).

  When the card authentication code is determined, the user authentication unit 34 notifies the interlocked data management unit 35 of the card authentication code, and the interlocked data management unit 35 receives the interlocked data associated with the card authentication code. It discriminates (step S64). When the interlocked ID is designated from the individual system 2, the user authentication unit 34 also notifies the interlocked data management unit 35 of the interlocked ID, and the interlocked data management unit 35 outputs interlocked data associated with the card authentication data. And further determine data corresponding to the interlocked ID. If data corresponding to the interlocked ID is not included in the interlocked data associated with the card authentication code, the initial data may be added to the interlocked data in association with the interlocked ID.

  Subsequently, the interlocked data management unit 35 permits the use of the interlocked data by the individual system 2 that is the request source of interlocked authentication (step S65). For example, by releasing the access restriction from the individual system 2 to the interlocked data determined in step S64, processing such as setting the interlocked data in a state where the interlocked data can be written and read by the individual system 2 is performed. You may be In this case, an address on the network for accessing interlocking data permitted to be used is provided to the individual system 2, and the service management unit 22 of the individual system 2 interlocks in the same manner as various data in its own system 2. Data may be manipulated. Alternatively, the interlocked data management unit 35 may operate interlocked data in response to a request from the service management unit 22. When the use of interlocking data is permitted, the interlocking data management unit 35 notifies the user authenticating unit 34 to that effect, and the user authenticating unit 34 notifies the interlocking management unit 23 of the individual system 2 of the request source of authentication completion. (Step S66). Thus, the process of FIG. 7 ends. If it is determined in step S62 that the interlocking authentication code does not exist, the user authenticating unit 34 notifies the interlocking management unit 23 of an error (step S67), and then the process of FIG. 7 is finished.

  FIG. 8 shows an example of a procedure of processing for providing the interlocking authentication code corresponding to another individual system 2 in response to a request from the individual system 2 by the interlocking management system 3. This process is a process for realizing provision and use of services between the individual systems 2 using the interlocking authentication code. FIG. 8 shows the service use processing of the interlocking management unit 23 in the individual system 2 (the individual system 2 of the request source) on the side using the service in the center, and the code provision processing of the interlocking authentication code provision unit 36 of the interlocking management system 3 Is shown on the left side, and the process of the interlocking management unit 23 of the individual system 2 on the service providing side (the individual system 2 of the request destination) is shown on the right side. Note that the process in FIG. 8 is premised on the user ID corresponding to the user's common card ID and the interlocking authentication code already existing in the individual system 2 of the request source and the individual system 2 of the request destination. .

  In the process of FIG. 8, first, the service utilization process is started in the interlocking management unit 23 of the individual system 2 of the request source of the service utilization, in other words, the individual system 2 that receives the provision of the service. The service utilization process may be started, for example, when it becomes necessary to use the service of another individual system 2 while the individual system 2 provides its own service to the user.

  When the interlocking management unit 23 of the individual system 2 of the request source starts the service utilization process of FIG. 8, first, it is generated in the individual system 2 of the request destination corresponding to the user ID of the user who provides its own service. The link authentication code providing unit 36 of the link management system 3 is requested to provide the link authentication code (step S101). In this case, the service ID of the service that the individual system 2 of the request source wants to use (corresponding to the service of the individual system 2 of the request destination, which may hereinafter be referred to as the service ID of the other party) is previously provided. It may be acquired in the individual system 2 of the request source, and the service ID of the other party, and the service ID of its own and the interlocking authentication code of the user corresponding to this may be designated to the interlocking authentication code provision unit 36 . The service ID of the other party is not provided from the interlocking management system 3, and the individual system 2 can not acquire the service ID corresponding to its own service from the interlocking management system 3. However, provision of services between the individual systems 2 and use thereof can be made as long as the management entity and the management entities of the individual systems 2 are appropriately negotiated, and if the service ID is notified according to the agreement, the individual system 2 of the request source From this, it is possible to notify the linked management system 3 of the service ID of the individual system 2 of the request destination.

  The interlock authentication code provision unit 36 of the interlock management system 3 starts the code provision processing of FIG. 8 when the individual system 2 of the request source is requested to provide the interlock authentication code. In the code provision process, the interlocking authentication code provision unit 36 refers to the databases DB11 and DB12 to identify the service ID and the interlocking authentication code specified by the individual system 2 of the request source (however, the individual system 2 of the request source is The corresponding card authentication code is determined (step S111). Subsequently, the interlock authentication code provision unit 36 determines the interlock authentication code corresponding to the service ID by using the card authentication code and the service ID of the individual system 2 of the request destination (step S112). Next, the link authentication code provision unit 36 notifies the link management unit 23 of the individual system 2 of the request source of the obtained link authentication code (step S113), and then ends the code provision processing.

  The interlocking management unit 23 of the individual system 2 of the request source receives the authentication code for interlocking of the individual system 2 of the request destination from the interlocking authentication code provision unit 36 (step S102), and the interlocking authentication code and the service ID of the other party And requests the interlocking management unit 23 of the individual system 2 of the request destination to provide a service (step S103). In response to this, the interlocking management unit 23 of the individual system 2 of the request destination starts the service provision processing of FIG. 8. In the service provision start process, the linkage management unit 23 first determines the linkage authentication code specified from the individual system 2 of the request source (step S121), and determines the user ID associated with the linkage authentication code (step S121) S122).

  Next, among the services provided by the individual system 2 of the request destination in association with the user ID, at least a part of the services associated with the service ID specified from the individual system 2 of the request source. , The provision of the request source to the individual system 2 is permitted (step S123). For example, in FIG. 3, when the use of the individual system 2B is permitted only for the settlement function of the individual system 2A based on the access from the individual system 2B, it is recorded in the account management database DB3 in association with the user ID. Depending on the arrangement between the individual systems 2, another individual system may be provided, such as providing only the process of consuming the amount corresponding to the charge specified by the individual system 2 of the request source from the balance of the user's electronic currency. The availability of use of 2 may be controlled in step S123, and the procedure may be appropriately decided. After permitting the provision of the service, the interlocking management unit 23 of the individual system 2 of the request destination notifies the permission to the interlocking management unit 23 of the individual system 2 of the request source (step S124). Thus, the service providing process of FIG. 8 ends.

  When receiving the permission notification in step S124, the interlocking management unit 23 of the request source individual system 2 notifies the service management unit 22 to that effect, and the service management unit 22 performs the service of the individual system 2 of the request destination according to a predetermined procedure. Start using (step S104). Thus, the service utilization process of FIG. 8 ends. In addition, the procedure at the time of terminating use of the other individual system 2 may be suitably set between the individual systems 2.

  According to the above process, each individual system 2 can use the common card ID as the user identification information to authenticate the user and provide the service to the user. It is possible to eliminate the trouble of properly using 8 and to improve the user's convenience. When authenticating the user by accessing the interlocking management system 3 from each individual system 2, an interlocking authentication code different from any of the common card ID and the user ID generated by each individual system 2 in association with the common card ID And how to generate the authentication code for interlocking with the common card ID can be set independently for each individual system 2. Therefore, the method for each individual system 2 to access the interlocking management system 3 and the information necessary for the access are unique to each individual system 2, and each individual system 2 is different from other individual systems 2 In principle, it is impossible to know whether to access the interlocking management system 3 using information. Since each individual system 2 can be uniquely set for each individual system 2 as to how to use the common card ID to provide its own service to the user, each individual system 2 can be used as a common card ID It is also impossible in principle to use the services of other individual systems 2 on the basis of. On the other hand, in the interlocking management system 3, since the service of the individual system 2 requesting access and its user can be specified by using the service ID as a clue, the authentication code for interlocking is generated according to the rule unique to each individual system Even if this is done, it is possible to determine the card authentication code corresponding to the common card ID of the user, and to determine interlocking data corresponding to this.

  The process of FIG. 8 is an exceptional case in which the interlocking authentication code of another individual system 2 is provided from the interlocking management system 3, but even if such an exception is recognized, the interlocking authentication code is the individual system 2 The information is merely information for accessing the interlocking management system 3, and is not used as information for accessing each individual system 2 and using its service. Therefore, each individual system 2 can appropriately set whether or not to allow access based on the interlocking authentication code, and to what extent the service is to be used even if it is permitted. It is possible to prohibit all use, and it is also possible to set it so that only some services can be used. That is, even if the exceptional processing of FIG. 8 is recognized, the internal information of each individual system 2 can be concealed in accordance with the convenience of each individual system 2.

  As described above, according to the present embodiment, the information used by each individual system 2 can be hidden from the other individual systems 2, so that the security of each individual system 2 can be secured. It is possible. Furthermore, in the interlocking management system 3, a card authentication code is generated in association with the common card ID, and the interlocking authentication code of each individual system 2 and interlocking data are managed using the card authentication code. The common card ID is information that each individual system 2 can know, but how to generate a card authentication code from the common card ID can be uniquely set by the interlocking management system 3, and moreover, the card authentication code There is no need to notify each individual system 2 from the interlocking management system 3. Therefore, security can be enhanced as compared to the case where the common card ID itself is used as a key to manage the interlocking authentication code and the interlocked data.

  In the above embodiment, the card authentication code generating unit 33 of the interlocking management system 3 executes the processing of step S23 of FIG. 5 to function as an example of common authentication information generating means, and the interlocking authentication code of each individual system 2 The generation unit 24 functions as an example of the interlock authentication information generation unit by executing the process of step S13 of FIG. 4, and the interlock setting unit 32 of the interlock management system 3 executes the processes of steps S24 and S26 of FIG. Functions as an example of the association setting generation unit, and the user authentication unit 34 functions as an example of the user authentication unit by executing the processing of steps S61 to S63 of FIG. 7, and the interlocked data management unit 35 performs the step of FIG. By executing the processes of S64 and S65, the function as an example of the usage management means, and the interlocking authentication code provision unit 36 By executing the processing in 8 steps S111~S113 functions as an example of the authentication information providing means.

  The present invention is not limited to the above-described embodiment, but may be implemented with appropriate modifications or changes. For example, although the interlocking authentication code generation unit 24 is provided in the individual system 2 in the above embodiment, this is provided in the interlocking management system 3 and interlocked on the interlocking management system 3 side according to the request from each individual system 2 An authentication code for authentication may be generated and provided to the individual system 2 of the request source. Even in this case, the rules for generating the interlocking authentication code corresponding to the common card ID are differentiated for each individual system, and at least the interlocking authentication code is uniquely generated for the common card ID for each service ID. If it does, it is possible to secure security like the above. The card authentication code generation unit 33 is redundantly provided in each individual system 2, and the interlocking management system 3 acquires the card authentication code and the corresponding common card ID from any of the individual systems 2 and records them in the database DB11. It is also possible to Also in this case, as long as the card authentication code is uniquely generated for the common card ID, the code generation rules of the card authentication code generation unit provided in each individual system 2 may be appropriately differentiated.

  In the above embodiment, although the service range of the individual system 2 is identified using the service ID as an example of the service identification information, the service identification information is the range of the service for which an interlocking relationship is to be generated in the individual system 2 As long as it can be used for identification, appropriate information can be used. For example, when a unique address on the network is fixedly set to the individual system 2, the address information may be used as service identification information. In the above embodiment, the range of services specified by the service ID matches the range of services provided by the individual system 2. However, as described above, the range of services within one individual system is The service ID may be set for each of the plurality of divisions. That is, it is sufficient if service identification information is used to identify which individual system service the interlocking authentication information corresponds to, and the range of the individual system is determined by the service identification information for the sake of securing security. It may be set to include one or more partitioned service areas.

  In the above embodiment, although the service ID and the interlocking authentication code are separately generated and shown as the information to be associated with each other, the service identification information and the interlocking authentication information may be integrally generated as a set. For example, in the case of generating interlocking identification information of a predetermined number of digits, by defining a rule that some digits, for example, the first two digits, are made common for each service range, the interlocking authentication information It is also possible to function a part substantially as service identification information associated with the interlocking authentication information.

  In the above embodiment, the card authentication code as an example of the common authentication information and the interlocking data are associated one by one, and the inside of the interlocking data is classified for each interlocking ID as an example of the event identification information. The correspondence between the common authentication information and the interlocked data, and the configuration of the interlocked data can be changed as appropriate. For example, by associating a plurality of card authentication codes corresponding to the same service ID with the same interlocked data, the interlocked data and the card authentication code may be shared such that interlocked data is shared among users corresponding to those card authentication codes. An association of may be set. In this case, interlocking relationships can be generated uniformly among a plurality of users. For example, it is also possible to create interlocking relationships in units of groups of users. Further, as described above, the association with the interlocking ID may be omitted. How each individual system uses interlocking data may be appropriately decided between each individual system. The range in which interlocking data can be used is appropriately differentiated between the individual systems or the range of services classified by service identification information by, for example, defining the range in which interlocking data can be read and written in each individual system. It is also good.

  In the above embodiment, although the individual system provides the service associated with the game to the user, the service of the individual system is not limited to such an example, and the individual system is constructed for the appropriate service. Good.

  Various aspects of the invention derived from each of the above-described embodiments and variations are described below. In the following description, in order to facilitate understanding of each aspect of the present invention, corresponding components shown in the attached drawings are appended in parentheses, but the present invention is thereby limited to the illustrated form. It is not a thing.

  An interlocked service providing system (1) according to an aspect of the present invention includes: a plurality of individual systems (2A, 2B) for providing a predetermined service to a user authenticated based on predetermined identification information; The interlocked service providing system includes an interlocked management system (3) that manages interlocked data for generating predetermined interlocked relationships among services of individual systems, and the above-mentioned interlocked service provision system includes Common authentication information generation means (33 for generating common authentication information (for example, card authentication code in FIG. 2) uniquely associated with common identification information (for example, common card ID in FIG. 2) usable as identification information , S23), and at least the interlocking relationship, the interlocking authentication information (the interlocking authentication code in FIG. 2 as an example) corresponding to the common identification information. Interlocking authentication information generation means (24, S13) for each individual system so as to be uniquely associated with the common identification information within the range of services to be A service in which the common authentication information is recorded in a predetermined storage unit (11) in association with the common identification information and the interlocking data, and the interlocking authentication information is set uniquely to the range of the service Association setting means (32, S24, S26) for recording identification information (for example, the service ID in FIG. 2) and the common authentication information in association with the common authentication information, the service identification information and the interlocking from any individual system When access is requested by designating the authentication information for authentication, in the specified service identification information and the authentication information for linkage The user authentication means (34, S61 to S63) for determining the associated common authentication information, and the interlocked data associated with the determined common authentication information, and the individual system of the request source related to the determined interlocked data Use management means (35, S64, S65) for permitting use is provided.

  An interlocking management system (3) according to an aspect of the present invention is combined with a plurality of individual systems (2A, 2B) for providing a predetermined service to a user authenticated based on predetermined identification information, An interlocking management system for managing interlocking data for causing a predetermined interlocking relationship between services of individual systems, and common identification information that can be used as the identification information in each of the plurality of individual systems (as an example Common authentication information generation means (33, S23) for generating common authentication information (for example, a card authentication code in FIG. 2) uniquely associated with the common card ID in FIG. 2); While recording in the predetermined storage means (11) in association with the common identification information and the interlocking data, at least the interlocking relationship should be generated. Interlocking authentication information (for example, the interlocking authentication code in FIG. 2) generated for each individual system uniquely associated with the common identification information within the service range is uniquely set for each service range Association setting means (32, S24, S26) associated with the service identification information (the service ID of FIG. 2 as an example) and the common authentication information and recorded in the storage means, and the service identification information from any of the individual systems And user authentication means (34, S61 to S63) for determining common authentication information associated with the designated service identification information and the interlocking authentication information when access is requested by designating the interlocking authentication information; The interlocking data associated with the determined common authentication information is determined, and the individual requester of the determined interlocking data is determined. Use management means which allow the stem use of (35, S64, S65), those having a.

  A computer program (PG1, PG2) according to an aspect of the present invention comprises: a plurality of individual systems (2A, 2B) for providing a predetermined service to a user authenticated based on predetermined identification information; A computer applied to a computer (20, 30) of a linked service providing system (1) including a linked management system (3) that manages linked data for generating a predetermined linked relationship between services of individual systems A program that is uniquely associated with common identification information (for example, common card ID in FIG. 2) that can be used as the identification information in each of the plurality of individual systems. Common authentication information generation means (33, S23) for generating the card authentication code of FIG. 2 as one example, and the common The linkage authentication information (for example, the linkage authentication code of FIG. 2 as an example) corresponding to another information is uniquely associated with the common identification information at least within the range of the service that should cause the linkage. While functioning as interlocking authentication information generation means (24, S13) generated for each individual system, the computer (30) of the interlocking management system associates the common authentication information with the common identification information and the interlocking data. While recording in predetermined storage means (11), the interlocking authentication information is associated with service identification information (service ID in FIG. 2 as an example) uniquely set for the service range and the common authentication information Setting means (32, S24, S26) for recording in the storage means, any one of the individual systems When access is requested by designating the service identification information and the interlocking authentication information from the user, the user authentication means (34, S61) determines the common authentication information associated with the designated service identification information and the interlocking authentication information. ~ S63), and the interlocking data associated with the determined common authentication information, and function as a use management means (35, S64, S65) that permits the use of the individual system of the request source regarding the determined interlocking data It is constructed as follows.

  A computer program (PG2) according to another aspect of the present invention is combined with a plurality of individual systems (2A, 2B) for providing a predetermined service to a user authenticated based on predetermined identification information, A computer program applied to the interlocking management system (3) for managing interlocking data for causing a predetermined interlocking relationship between services of the individual systems, the computer of the interlocking management system comprising the plurality of individual systems Common authentication information (for example, card authentication code in FIG. 2) uniquely associated with common identification information (for example, common card ID in FIG. 2) applicable as the identification information in each of Authentication information generation means (33, S23), the common authentication information, the common identification information and the interlocked data Link authentication generated for each individual system uniquely associated with the common identification information at least within the range of the service that should generate the interlocked relationship while being recorded in association with the predetermined storage means (11) Information (for example, the authentication code for interlocking in FIG. 2) is recorded in the storage means in association with service identification information (for example, service ID in FIG. 2) uniquely set for each service range and the common authentication information. Association setting means (32, S24, S26), when the service identification information and the interlocking authentication information are specified from any of the individual systems and access is requested, the designated service identification information and the interlocking authentication information User authentication means (34, S61 to S63) for determining common authentication information associated with the It is configured to function as a usage management means (35, S64, S65) for determining interlocking data associated with the authentication information and permitting use of the individual system of the request source regarding the determined interlocking data. .

  According to the above aspect, since each of the individual systems can authenticate the user based on the common identification information and provide the service, it is not necessary to use different identification information for each individual system, and the user's convenience can be achieved. it can. When each of the individual systems accesses the interlocking management system, interlocking authentication information different from the common identification information is used, and how to generate interlocking authentication information from the common identification information depends on each individual system. It is possible to set it independently. On the other hand, in the interlocking management system, it is possible to identify the service of the individual system requesting access and its user using the service identification information as a clue, so the interlocking authentication information is generated according to the rules unique to each individual system. Also, common authentication information corresponding to the common identification information of the user can be determined, and interlocking data corresponding to this can be determined. By individually generating linkage authentication information for each individual system, each individual system can not know or need to know each individual system how to access the linkage management system by other individual systems. Absent. Even if an exception is provided for providing interlocking authentication information used by other individual systems from the interlocking management system, the interlocking authentication information is merely used as information for each individual system to access the interlocking management system. Also, it is not used as information for accessing each individual system and using its service. Therefore, the individual system can appropriately set whether or not to allow access to the individual system based on the interlocking authentication information, and to what extent the service is to be used even if the access is permitted. Furthermore, although the common identification information is information that each individual system 2 can know, how to generate the common authentication information from the common identification information can be set independently. In addition, it is not necessary to notify common authentication information from the interlocking management system to each individual system. Therefore, security is enhanced compared to the case of managing interlocking authentication information and interlocking data using the common identification information itself as a key. As described above, according to the above aspect, access to the interlocking management system from each individual system can be controlled based on unique interlocking authentication information for each individual system, and access between the individual systems can be appropriately blocked. Therefore, it is possible to conceal the internal information of the individual system from other individual systems to ensure security.

  Note that the computer program according to an aspect of the present invention may be provided in a state of being stored in a storage medium. If this storage medium is used, for example, the computer program according to the present invention is installed and executed in a computer, whereby the game system of the present invention can be realized using the computer. The storage medium storing the computer program may be a non-transitory storage medium such as a CDROM.

  In the above aspect, the interlocking data is recorded in association with event identification information (an interlocking ID in FIG. 2 as an example) uniquely set for each of a plurality of interlocking events set between services of the individual system. The management means may acquire the event identification information from the individual system of the request source, and determine interlocking data corresponding to the acquired event identification information. According to this, the interlocking data can be classified for each event, and the interlocking data associated with the specific event within the range of the service that the individual system seeks to use can be determined and used for the utilization of the individual system . When interlocking data includes information associated with various events of various services, it is possible to efficiently extract necessary information.

  The common authentication information generation means may be provided in the interlocking management system, and may generate the common authentication information corresponding to common identification information acquired from the individual system. According to this, it is possible to place the procedure for generating the common authentication information corresponding to the common identification information under the management of the interlocked management system and conceal the procedure from the individual system. This can further enhance security.

  The interlocking authentication information generation unit is provided in each individual system, and the association setting unit is configured to generate the common authentication information generation unit that generates the service identification information and the interlocking authentication information acquired from the individual system. It may be recorded in association with authentication information. According to this, it is possible to place the procedure for generating interlocking authentication information corresponding to the common identification information under the control of each individual system, and to hide the procedure from other individual systems or interlocking management systems. Thereby, security can be further enhanced.

  The interlocking management system is interlocking authentication information associated with the common authentication information determined by the user authentication means, and is generated corresponding to another individual system different from the individual system of the request source. The authentication information providing means (36, S111 to S113) may be provided to determine the interlocking authentication information and provide the determined interlocking authentication information to the individual system of the request source. According to this, it is possible to allow an exception in which the individual system acquires the interlocking authentication information corresponding to another individual system, and to facilitate the provision and use of services between the individual systems using the interlocking authentication information. .

1 interlocked service providing system 2A, 2B individual system 3 interlocked management system 4 client 4A game machine 4B portable communication terminal device 6, 10 server 7, 11 database group (storage means)
8 card 20, 30 control unit (computer)
23 Interlocking Management Unit 24 Interlocking Authentication Code Generating Unit 32 Interlocking Setting Unit 33 Card Authentication Code Generating Unit 34 User Authentication Unit 35 Interlocking Data Management Unit 36 Interlocking Authentication Code Providing Unit

Claims (12)

Interlocking to manage interlocking data for generating a predetermined interlocking relationship between a plurality of individual systems providing predetermined services to a user authenticated based on predetermined identification information and services of the plurality of individual systems A linked service providing system including a management system,
Common authentication information generation means for generating common authentication information uniquely associated with common identification information that can be used as the identification information in each of the plurality of individual systems;
Interlocking authentication that generates interlocking authentication information corresponding to the common identification information uniquely for each common system so as to be uniquely associated with the common identification information at least within the range of services that should cause the interlocking relationship Information generation means, and
The interlocking management system
The common authentication information is recorded in a predetermined storage unit in association with the common identification information and the interlocking data, and the interlocking authentication information is service identification information uniquely set for the range of the service and the service identification information Association setting means for associating the common authentication information and recording the same in the storage means;
User authentication that determines common authentication information associated with specified service identification information and interlocking authentication information when access is requested by specifying the service identification information and the interlocking authentication information from any of the individual systems Means,
A linked service providing system, comprising: usage management means for determining interlocking data associated with the determined common authentication information and permitting use of the individual system of the request source regarding the determined interlocking data. The interlocking data is recorded in association with event identification information uniquely set for each of a plurality of interlocking events set between services of the individual system.
The interlocked service providing system according to claim 1, wherein the use management unit acquires the event identification information from the individual system of the request source and determines interlocking data corresponding to the acquired event identification information.   The linked service providing system according to claim 1 or 2, wherein the common authentication information generation unit is provided in the interlocking management system, and generates the common authentication information corresponding to the common identification information acquired from the individual system. .   The interlocking authentication information generation unit is provided in each individual system, and the association setting unit generates the common authentication information generation unit that generates the service identification information and the interlocking authentication information acquired from the individual system. The linked service providing system according to any one of claims 1 to 3, which is associated with authentication information and recorded.   The interlocking management system is interlocking authentication information associated with the common authentication information determined by the user authentication means, and is generated corresponding to another individual system different from the individual system of the request source. The interlock according to any one of claims 1 to 4, further comprising authentication information providing means for determining the interlocking authentication information and providing the determined interlocking authentication information to the individual system of the request source. Type service delivery system. Manage interlocking data to create a predetermined interlocking relationship between services of the plurality of individual systems in combination with a plurality of individual systems providing predetermined services to a user authenticated based on predetermined identification information Interlocking management system,
Common authentication information generation means for generating common authentication information uniquely associated with common identification information that can be used as the identification information in each of the plurality of individual systems;
The common authentication information is associated with the common identification information and the interlocking data and recorded in a predetermined storage means, and is uniquely associated with the common identification information within at least the range of services that should cause the interlocking relationship. Association setting means for associating the linkage authentication information generated for each individual system with the service identification information uniquely set for each service range and the common authentication information and recording the association in the storage means;
User authentication that determines common authentication information associated with specified service identification information and interlocking authentication information when access is requested by specifying the service identification information and the interlocking authentication information from any of the individual systems Means,
An interlocking management system comprising: use management means for determining interlocking data associated with the determined common authentication information and permitting use of the individual system of the request source regarding the determined interlocking data. The interlocking data is recorded in association with event identification information uniquely set for each of a plurality of interlocking events set between services of the individual system.
The interlocking management system according to claim 6, wherein the use management unit acquires the event identification information from the individual system of the request source, and determines interlocking data corresponding to the acquired event identification information.   The interlocking management system according to claim 6 or 7, wherein the common authentication information generation unit generates the common authentication information corresponding to the common identification information acquired from the individual system.   The linkage authentication information is generated in each individual system, and the association setting unit generates the common authentication information generated by the common authentication information generation unit, the service identification information acquired from the individual system and the linkage authentication information. The interlocking management system according to any one of claims 6 to 8, which is associated with information and recorded.   The interlocking authentication information associated with the common authentication information determined by the user authentication means, and the interlocking authentication information generated corresponding to another individual system different from the individual system of the request source is determined The interlocking management system according to any one of claims 6 to 9, further comprising authentication information providing means for providing the determined interlocking system authentication information to the individual system of the request source. Interlocking to manage interlocking data for generating a predetermined interlocking relationship between a plurality of individual systems providing predetermined services to a user authenticated based on predetermined identification information and services of the plurality of individual systems A computer program applied to a computer of a linked service providing system including a management system,
The computer,
Common authentication information generation means for generating common authentication information uniquely associated with common identification information that can be used as the identification information in each of the plurality of individual systems, and interlocking authentication corresponding to the common identification information The information is uniquely associated with the common identification information at least within the range of services that should cause the interlocked relationship, and functions as an interlocking authentication information generation unit that is generated for each individual system.
The computer of the interlocking management system,
The common authentication information is recorded in a predetermined storage unit in association with the common identification information and the interlocking data, and the interlocking authentication information is service identification information uniquely set for the range of the service and the service identification information Association setting means associated with common authentication information and recorded in the storage means,
User authentication that determines common authentication information associated with specified service identification information and interlocking authentication information when access is requested by specifying the service identification information and the interlocking authentication information from any of the individual systems A computer program configured to function as usage management means for determining interlocking data associated with the determined common authentication information, and permitting use of the individual system of the request source regarding the determined interlocking data. Manage interlocking data to create a predetermined interlocking relationship between services of the plurality of individual systems in combination with a plurality of individual systems providing predetermined services to a user authenticated based on predetermined identification information A computer program applied to the interlocking management system
The computer of the interlocking management system,
Common authentication information generation means for generating common authentication information uniquely associated with common identification information that can be used as the identification information in each of the plurality of individual systems,
The common authentication information is associated with the common identification information and the interlocking data and recorded in a predetermined storage means, and is uniquely associated with the common identification information within at least the range of services that should cause the interlocking relationship. Association setting means for associating the linkage authentication information generated for each individual system with the service identification information uniquely set for each service range and the common authentication information, and recording the association information in the storage unit
User authentication that determines common authentication information associated with specified service identification information and interlocking authentication information when access is requested by specifying the service identification information and the interlocking authentication information from any of the individual systems A computer program configured to function as usage management means for determining interlocking data associated with the determined common authentication information, and permitting use of the individual system of the request source regarding the determined interlocking data.

Images