WO2022190315A1

WO2022190315A1 - Computer system and data processing method

Info

Publication number: WO2022190315A1
Application number: PCT/JP2021/009825
Authority: WO
Inventors: 俊二川村; 茜鈴木; 夏樹塚野
Original assignee: 株式会社日立製作所
Priority date: 2021-03-11
Filing date: 2021-03-11
Publication date: 2022-09-15

Abstract

This computer system provides a service, and connects to another computer system which provides a different service. At least one other computer system manages account relationship management information storing data indicating a relationship between accounts. If a service usage request requiring confirmation of the relationship between a first account and a second account is received from a terminal operated by a user that has the first account, a confirmation request for confirming the relationship between the first account and the second account is transmitted to the other computer system that manages the account relationship management information. The usage request is processed on the basis of a response transmitted from the other computer system.

Description

Computer system and data processing method

The present invention relates to technology for providing services in cooperation with multiple systems.

Various digital services such as storage services, electronic payment services, email services, video distribution services, and SNS (Social Networking Services) are provided.

Techniques for using information from other services when using a certain service, such as SAML (Security Assertion Markup Language) and OpenID Connect, are known. Also, an invention described in Patent Document 1 is known.

Patent Literature 1 describes a method and device for managing cloud computing resources using external accounts, wherein the resources are associated with one or more internal main accounts. verifying the identity of the account and, if the identity of the external account is verified, determining whether the virtual subaccount is tied to the external account, wherein the virtual subaccount is one or more internal main accounts; If it is determined that one of the accounts is subordinate to an internal main account and a virtual subaccount is tied to an external account, one based on the preconfigured rights of the virtual subaccount. and allowing external accounts to manage resources associated with the internal main account."

Japanese Patent Application Publication No. 2018-523866

When another person (for example, an agent) uses a digital service on behalf of the person, it is necessary to confirm not only the identity verification but also the relationship between the person and the other person. However, digital services cannot be provided if a system that provides digital services does not hold information indicating the relationship between the person and others.

The present invention provides a system and method for providing digital services using information managed by an external system that indicates the relationship between a person and others.

A representative example of the invention disclosed in the present application is as follows. That is, a computer system that provides services and includes at least one computer, is connected to a plurality of other computer systems that provide different services, and at least one of the other computer systems indicates the relationship between accounts. A request to use the first service requiring confirmation of the relationship between the first account and the second account is received from a terminal operated by a user who manages account relationship management information storing data and has a first account. In this case, a first confirmation request for confirming the relationship between the first account and the second account is transmitted to the first other computer system that manages the account relationship management information, and the first other computer system Based on the transmitted response, the processing for the usage request is executed.

According to the present invention, a computer system can provide digital services using information that indicates the relationship between a person and others managed by an external system (another computer system). Problems, configurations, and effects other than those described above will be clarified by the following description of the embodiments.

1 is a diagram illustrating an example of a configuration of a computer system of Example 1; FIG. It is a figure which shows an example of the hardware configuration of a service provision system, and a software configuration. 4 is a diagram illustrating an example of the data structure of account management information in Example 1; FIG. 4 is a diagram showing an example of the data structure of account relationship management information of Example 1. FIG. 4 is a diagram showing an example of the data structure of account cooperation management information of Example 1. FIG. 4 is a diagram illustrating an example of the data structure of service management information in Example 1; FIG. 4 is a diagram showing an example of the data structure of service provision condition management information of Example 1. FIG. 4 is a sequence diagram showing the flow of service providing processing in the computer system of Example 1; FIG. FIG. 5 is a diagram showing an example of a screen displayed on the terminal of Example 1; FIG. 4 is a diagram showing an example of a screen displayed on the service providing system of Example 1; FIG. FIG. 5 is a diagram showing an example of a screen displayed on the terminal of Example 1; FIG. 5 is a diagram showing an example of a screen displayed on the terminal of Example 1; FIG. 11 is a sequence diagram showing the flow of service providing processing in the computer system of Example 2; FIG. 12 is a diagram showing an example of the data structure of account cooperation management information of Example 3; FIG. 13 is a diagram showing an example of the data structure of service provision condition management information of Example 3; FIG. 11 is a sequence diagram showing the flow of service providing processing in the computer system of Example 3;

Hereinafter, embodiments of the present invention will be described with reference to the drawings. However, the present invention should not be construed as being limited to the description of the embodiments shown below. Those skilled in the art will easily understand that the specific configuration can be changed without departing from the idea or gist of the present invention.

In the configurations of the inventions described below, the same or similar configurations or functions are given the same reference numerals, and overlapping descriptions are omitted.

The notations such as "first", "second", "third", etc. in this specification etc. are attached to identify the constituent elements, and do not necessarily limit the number or order.

The position, size, shape, range, etc. of each configuration shown in the drawings, etc. may not represent the actual position, size, shape, range, etc., in order to facilitate the understanding of the invention. Therefore, the present invention is not limited to the positions, sizes, shapes, ranges, etc. disclosed in the drawings and the like.

FIG. 1 is a diagram showing an example of the configuration of the computer system of the first embodiment.

The computer system consists of multiple service providing systems 100 and multiple terminals 101 . A plurality of service providing systems 100 and a plurality of terminals 101 communicate with each other via a network 102 . The network 102 is, for example, a WAN (Wide Area Network), a LAN (Local Area Network), or the like, and the connection method may be either wired or wireless.

The service providing system 100 is a system that provides digital services. For example, storage services, electronic payment services, mail services, video distribution services, and digital services such as SNS are conceivable. Note that the present invention is not limited to the types and contents of digital services provided by the service providing system 100 . In the following description, digital services are referred to as services.

In this specification, the service providing system 100 that accepts inquiries regarding the relationship between accounts is referred to as the linked service providing system 100. For purposes of this specification, the users with accounts that confirm the relationship are different. However, the present invention can be applied even when the same user has different accounts.

A terminal 101 is a terminal used by an end user who uses the service. Terminals 101 are, for example, personal computers, smart phones, and tablet terminals. The terminal 101 has a processor, main storage device, sub storage device, communication device, input device, and output device (not shown).

FIG. 2 is a diagram showing an example of the hardware configuration and software configuration of the service providing system 100. As shown in FIG.

The service providing system 100 consists of at least one computer 200. In this specification, a service providing system 100 composed of one computer 200 will be described as an example. Note that the service providing system 100 may include a network switch, a storage system, and the like.

The computer 200 has a processor 201, a communication device 202, a main storage device 203, and a secondary storage device 204 as hardware elements. Each hardware element is connected to each other via an internal bus.

The processor 201 executes programs stored in the main memory device 203 . The processor 201 operates as a functional unit (module) that implements a specific function by executing processing according to a program. In the following description, when the processing is described with the functional unit as the subject, it means that the processor 201 is executing a program that implements the functional unit.

The communication device 202 is a device for communicating with an external device and an external system, such as a network interface.

The main storage device 203 is a DRAM (Dynamic Random Access Memory) or the like, and stores programs executed by the processor 201 and information used by the programs. The main memory device 203 is also used as a work area.

The secondary storage device 204 is a HDD (Hard Disk Drive), SSD (Solid State Drive), etc., and permanently stores information.

The programs and information stored in the main storage device 203 may be stored in the secondary storage device 204. In this case, processor 201 reads programs and information from secondary storage device 204 and loads them into main storage device 203 . Information stored in the secondary storage device 204 may be stored in the main storage device 203 .

The main storage device 203 stores programs that implement the service providing unit 210 , the account management unit 211 , the account relationship management unit 212 , and the inquiry unit 231 . The secondary storage device 204 stores account management information 220 , account relationship management information 221 , account cooperation management information 222 , service management information 223 and service provision condition management information 224 .

The account management information 220 stores information for managing accounts of users who use the services provided by the service providing system 100. The data structure of the account management information 220 will be explained using FIG.

The account relationship management information 221 stores information for managing relationships between multiple accounts in the service providing system 100 . The data structure of the account relationship management information 221 will be explained using FIG. In the description below, the relationship between multiple accounts is referred to as account relationship.

The account cooperation management information 222 stores information for managing accounts in the cooperation service providing system 100 of users who use services provided by the service providing system 100 . The data structure of the account linkage management information 222 will be explained using FIG.

The service management information 223 stores information used for accessing the cooperative service providing system 100. The data structure of the service management information 223 will be explained using FIG.

The service provision condition management information 224 stores information for managing the provision conditions of available services based on account relationships. The data structure of the service provision condition management information 224 will be explained using FIG.

The service providing unit 210 controls the provision of services. The account management unit 211 manages accounts of users who use the service providing system 100 . The account relationship management unit 212 manages account relationships in the service providing system 100 . The inquiry unit 213 makes an inquiry about the account relationship to the cooperative service providing system 100 .

It should be noted that, with respect to each functional unit that the computer has, a plurality of functional units may be integrated into one functional unit, or one functional unit may be divided into multiple functional units for each function.

It should be noted that the service providing system 100 that does not hold the account relationship management information 221 may exist in the computer system. Further, the computer system may include a service providing system 100 that does not have the inquiry unit 213 .

FIG. 3 is a diagram showing an example of the data structure of the account management information 220 of the first embodiment.

The account management information 220 stores entries including account ID 301, name 302, date of birth 303, address 304, payment information 305, and status 306. There is one entry for one account. It should be noted that the fields included in the entry are just examples and are not limited to these. Some of the fields described above may not be included, and fields other than the fields described above may be included.

The account ID 301 is a field that stores an ID that is identification information of an account. A name 302 is a field that stores the name of a user who has an account. The date of birth 303 is a field for storing the date of birth of the user who has the account. Address 304 is a field that stores the address of the user who has the account. The payment information 305 is a field for storing information indicating the payment status of service usage fees of users who have accounts. Status 306 is a field that stores the status of users who have accounts. For example, it stores values such as the onset of death, dementia (unable to judge by the person himself/herself), and the like. The state 306 is used for determination of service provision using the execution timing 712, which will be described later. The status 306 is registered and updated by the administrator using status information provided by the user himself/herself or others, a copy of the family register, a long-term care insurance recipient qualification certificate, or the like. The information may be obtained from another service providing system 100 . For example, it is conceivable to acquire family register information from the service providing system 100 operated by a local government.

FIG. 4 is a diagram showing an example of the data structure of the account relationship management information 221 of the first embodiment.

The account relationship management information 221 stores entries including ID 401, relationship account 402, relationship 403, update date 404, and confirmation information 405. There is one entry for one set of accounts. It should be noted that the fields included in the entry are just examples and are not limited to these. Some of the fields described above may not be included, and fields other than the fields described above may be included.

The ID 401 is a field that stores the identification information of the entry in the account relationship management information 221. A related account 402 is a field that stores a set of IDs of accounts having arbitrary account relationships. The related account 402 stores two or more account IDs. The relation 403 stores a value indicating the account relation that the set of accounts has. The relationship 403 stores a value indicating a couple, parent and child, same household, proxy, and the like. The update date 404 is a field that stores the date and time when the account relationship was confirmed or updated. Confirmation information 405 is a field for storing information used to confirm account relationships.

FIG. 5 is a diagram showing an example of the data structure of the account cooperation management information 222 of the first embodiment.

The account linkage management information 222 stores entries including account IDs 501 and linkage services 502 . There is one entry for one account. It should be noted that the fields included in the entry are just examples and are not limited to these. Some of the fields described above may not be included, and fields other than the fields described above may be included.

The account ID 501 is the same field as the account ID 301. The linked service 502 is a field group for storing account information of the linked service providing system 100 . The linked service 502 includes a service ID 511 and an account ID 512. FIG. A service ID 511 is a field for storing identification information of the cooperative service providing system 100 . Account ID 512 is a field for storing account IDs in the cooperative service providing system 100 .

Each service providing system 100 transmits and receives the same user's account ID in advance and registers it in the account linkage management information 222 .

FIG. 6 is a diagram showing an example of the data structure of the service management information 223 of the first embodiment.

The service management information 223 stores entries including service ID 601, name 602, access destination 603, and access method 604. One entry exists for one cooperative service providing system 100 . It should be noted that the fields included in the entry are just examples and are not limited to these. Some of the fields described above may not be included, and fields other than the fields described above may be included.

The service ID 601 is the same field as the service ID 511. The access destination 603 is a field that stores a URL or the like for accessing the cooperative service providing system 100 . An access method 604 is a field that stores a method for accessing the cooperative service providing system 100 . The access method 604 stores, for example, the names of APIs provided by the cooperative service providing system 100 .

Each service providing system 100 transmits and receives information necessary for access in advance and registers it in the service management information 223 .

FIG. 7 is a diagram showing an example of the data structure of the service provision condition management information 224 of the first embodiment.

The service provision condition management information 224 stores an entry consisting of an account ID 701, a service type 702, and a condition 703. There is one entry for one account. It should be noted that the fields included in the entry are just examples and are not limited to these. Some of the fields described above may not be included, and fields other than the fields described above may be included.

The account ID 701 is the same field as the account ID 301. The service type 702 is a field that stores information indicating the type of service provided by the service providing system 100 . A condition 703 is a field group for storing service provision conditions. Condition 703 includes relationship 711 and execution timing 712 . A relationship 711 is a field for storing account relationships necessary for using the service. The execution timing 712 is a field that stores the execution timing of the service.

One entry contains the number of lines according to the combination of service type, account relationship, and execution timing.

Data is registered and updated in the service provision condition management information 224 based on the information transmitted from the terminal 101 to the service provision system 100 . Also, the administrator may register and update data in the service provision condition management information 224 based on an application from the user. Also, registration and updating may be performed in accordance with the conditions stipulated by the service.

The flow of processing when a user who has a certain account uses the service provided for that account is a well-known technique, so the explanation is omitted. This embodiment is characterized by processing when a user having a certain account uses a service provided for another account.

FIG. 8 is a sequence diagram showing the flow of service provision processing in the computer system of the first embodiment. 9 and 10 are diagrams showing examples of screens displayed on the terminal 101 of the first embodiment.

Here, the flow of processing when the user having the first account of service providing system 100-1 uses the first service provided to the user having the second account of service providing system 100-1 will be described as an example. do. Here, it is assumed that the service providing system 100-1 does not hold data indicating the account relationship between the first account and the second account.

The terminal 101 operated by the user having the first account transmits an identity verification request to the service providing system 100-1 (step S101). Account management unit 211 of service providing system 100-1 performs account authentication and notifies terminal 101 of the processing result. Here, it is assumed that account authentication has succeeded. Since the account authentication is a well-known technique, detailed explanation is omitted.

Next, the terminal 101 operated by the user having the first account transmits a request for using the first service to the service providing system 100-1 (step S102). The use request includes the ID of the first account, the ID of the second account, the type of the first service, and the like.

The service providing system 100-1 determines that it is necessary to confirm the account relationship between the first account and the second account, and redirects the terminal 101 to authenticate the account relationship (step S103). Specifically, the following processing is executed.

(S103-1) The service providing unit 210 determines that the request is for use of a service provided to an account (second account) different from the account (first account) that sent the use request. Therefore, the service providing unit 210 refers to the service provision condition management information 224, searches for an entry in which the ID of the second account is stored in the account ID 701, and the service type included in the use request is stored in the service type 702. Get the value of the row relationship 711 . The service providing unit 210 outputs the value to the account relationship managing unit 212 .

(S103-2) The account relationship management unit 212 refers to the account relationship management information 221, sets the ID pair of the first account and the second account in the relationship account 402, and inputs the relationship 403. Search for an entry with a value set to Here, it is assumed that the aforementioned entry does not exist. The account relationship management unit 212 responds that the entry does not exist in the service providing unit 210 .

(S103-3) The service providing unit 210 redirects to the linked service providing system 100-2 to inquire about account relationships. At this time, the service providing unit 210 presents the terminal 101 with an input screen 900 shown in FIG. Here, the input screen 900 will be described.

The input screen 900 includes a related person ID input field 901 , a relationship input field 902 , an add button 903 , a password input field 904 , a send button 905 and a cancel button 906 .

The related person ID input field 901 is a field for inputting the ID of the account whose relevance is to be confirmed. The ID of the account in the cooperative service providing system 100 is entered in the related party ID entry field 901 . A relationship input field 902 is a field for inputting an account relationship.

The add button 903 is an operation button for adding the person concerned ID input field 901 . When the add button 903 is operated, a person concerned ID input field 901 is added to the input screen 900 . For a service that uses account relationships between three or more accounts, an add button 903 is operated.

A password entry field 904 is a field for entering a password for accessing the cooperative service providing system 100 . In the password entry field 904, for example, the login password of the first account in the cooperative service providing system 100 is entered.

A send button 905 is an operation button for sending a relationship confirmation request. A cancel button 906 is an operation button for canceling the operation of the input screen 900 . The above is the description of the input screen 900 .

The above is the description of the processing in step S103.

Next, the terminal 101 transmits a relationship confirmation request to the cooperative service providing system 100-2 (step S104). The relationship confirmation request includes the ID of the first account, the ID of the second account, a value indicating account relationship, a password, and the like.

Upon receiving the relationship confirmation request, the linked service providing system 100-2 refers to the account relationship management unit 212 and verifies the specified account relationship. Here, it is assumed that it has been correctly verified. In this case, service providing system 100-2 issues a token to terminal 101 (step S105).

The verification of the account relationship can be considered to be the same process as the process of S103-2. If necessary, information stored in the confirmation information 405 of the searched entry may be used. Alternatively, an administrator who operates the service providing system 100-2 may manually perform verification using a verification screen 1000 as shown in FIG. Here, the verification screen 1000 will be described.

The verification screen 1000 includes account

ID display fields

1001 and 1003, name display fields 1002 and 1004, relationship display fields 1005, confirmation information display fields 1006, an OK button 1007, and an NG button 1008.

The account ID display field 1001 and the name display field 1002 are fields for displaying the ID of the account that wishes to use the service and the name of the user who has the account. An account ID display field 1003 and a name display field 1004 are fields for displaying the ID of an account whose account relationship is to be confirmed and the name of the user who has the account. Note that the verification screen 1000 may include columns for displaying items such as address and date of birth. The relationship display column 1005 is a column for displaying account relationships to be verified. A confirmation information display column 1006 is a column for displaying information used to verify the account relationship. For example, a copy of a family register or the like is displayed in the confirmation information display field 1006 . An OK button 1007 is an operation button for permitting approval of account relationships. An NG button 1008 is an operation button for denying approval of the account relationship. The above is the description of the verification screen 1000 .

Return to the description of Fig. 8. Next, the terminal 101 transmits a usage request including the issued token to the service providing system 100-1 (step S106).

After verifying the token, the inquiry unit 213 of the service providing system 100-1 transmits a token confirmation request to the cooperative service providing system 100-2 (step S107).

In addition, in verifying the token, the inquiry unit 213 may use the account cooperation management information 222 to convert the account ID of the cooperation service providing system 100-2 into the account ID of the service providing system 100-1. Further, the inquiry unit 213 may acquire information necessary for verification from the cooperative service providing system 100-2.

Upon receiving the token confirmation request, the account relationship management unit 212 of the cooperative service providing system 100-2 verifies the token. Here, it is assumed that it has been correctly verified.

The account relationship management unit 212 of the cooperative service providing system 100-2 transmits a response including the verification result to the service providing system 100-1 (step S108).

The inquiry unit 213 of the service providing system 100-1 determines whether or not the service can be used based on the response, and outputs the determination result to the service providing unit 210. Here, it is assumed that use of the service is permitted. In this case, service providing unit 210 of service providing system 100-1 provides service to terminal 101 (step S109).

At this time, the account relationship management unit 212 updates the account relationship management information 221 based on the verification result. Note that if the verification result includes the account ID of the linked service providing system 100-2, the account relationship management unit 212 refers to the account linkage management information 222, converts the account ID, and converts the account relationship management information into the account relationship management information. 221 update.

If information such as the status of a user having an account is required to determine execution timing, service providing system 100-1 receives information from linked service providing system 100-2 via query unit 213 or the like. may be obtained.

Note that the service providing system 100-1 may present a confirmation screen 1100 as shown in FIG. 11 to the terminal 101 based on the response received from the linked service providing system 100-2. Here, the confirmation screen 1100 will be described.

The confirmation screen 1100 includes a person ID display field 1101, a related person ID display field 1102, a relationship display field 1103, a system display field 1104, a result display field 1105, and a close button 1106.

The personal ID display field 1101 is a field for displaying the ID of the account that requested the use of the service. The related person ID display column 1102 is a column for displaying the ID of the account having the account relationship verified by the cooperative service providing system 100 . The relationship display column 1103 is a column for displaying account relationships verified by the cooperative service providing system 100 . A system display column 1104 is a column for displaying identification information and the like of the cooperative service providing system 100 for which the account relationship has been verified. The result display column 1105 is a column for displaying the verification result. A close button 1106 is an operation button for closing the confirmation screen 1100 . The above is the description of the confirmation screen 1100 .

Next, we will explain the variations of the service provision process.

(1) Account authentication may be performed by an authentication system (not shown). Also, account authentication may be performed by the cooperative service providing system 100 . In this case, a screen including a related person ID input field 901, a relationship input field 902, a password input field 904, and the like is displayed together with fields for inputting the ID and password of the account to be authenticated.

(2) If the linked service providing system 100 does not hold the information necessary for verifying the account relationships and service providing conditions, the information may be obtained from another service providing system 100 . For example, it is conceivable to acquire family register information from the service providing system 100 operated by a local government.

(3) The cooperative service providing system 100 may inquire about the account relationship to the terminal 101 operated by the user having the account whose account relationship is to be verified, and issue a token based on the inquiry result. For example, as an inquiry method to the terminal 101, presenting an inquiry screen 1200 as shown in FIG. 12 is conceivable. Here, the inquiry screen 1200 will be described.

The inquiry screen 1200 includes account ID display fields 1201 and 1203, name display fields 1202 and 1204, relationship display fields 1205, an OK button 1206, and an NG button 1207.

The account ID display field 1201 and the name display field 1202 are fields for displaying the ID of the account owned by the user who operates the terminal 101 and the name of the user who has the account. An account ID display field 1203 and a name display field 1204 are fields for displaying the ID of an account that wishes to use the service and the name of the user who has the account. Note that fields for displaying items such as address and date of birth may be included. The relationship display column 1205 is a column for displaying account relationships. An OK button 1206 is an operation button for permitting approval of account relationships. An NG button 1207 is an operation button for denying approval of account relationships. The above is the description of the inquiry screen 1200 .

(4) The terminal 101 may transmit a relationship confirmation request regarding the same or different account relationships to a plurality of cooperative service providing systems 100 . In this case, the service providing system 100 that has received the usage request containing the token transmits a token confirmation request to at least one cooperative service providing system 100 that has verified the account relationship. When sending a token confirmation request to a plurality of cooperative service providing systems 100, the service providing system 100 may integrate responses from each cooperative service providing system 100 and determine whether or not to provide the service.

If there are multiple available cooperative service providing systems 100, the input screen 900 is provided with a field for designating the cooperative service providing system 100 to be inquired.

(5) Account relationship verification may be performed manually by an administrator who operates the service providing system 100 that has received the usage request, referring to the verification screen 1000 or the like. In this case, the cooperative service providing system 100-2 performs authentication and the like without verifying the account relationship. When receiving the token confirmation request, the cooperative service providing system 100-2 transmits a response including information necessary for verifying the account relationship.

(6) An administrator who operates the service providing system 100 may manually determine whether the service can be provided.

According to the first embodiment, the service providing system 100 requests the cooperation service providing system 100 to verify the account relationship, and based on the verification result, one account is provided to another account having the account relationship. You can use the services provided. That is, account relationships can be linked between the service providing systems 100 .

In the second embodiment, the service providing system 100 directly transmits the relationship confirmation request to the linked service providing system 100. The second embodiment will be described below, focusing on the differences from the first embodiment.

The configuration of the computer system of the second embodiment is the same as that of the first embodiment. The configuration of the service providing system 100 of the second embodiment is the same as that of the first embodiment. The data structure of information held by the service providing system 100 of the second embodiment is the same as that of the first embodiment.

In the second embodiment, the processing procedure for service provision processing is partially different. FIG. 13 is a sequence diagram showing the flow of service provision processing in the computer system of the second embodiment.

The terminal 101 operated by the user having the first account transmits an identity verification request to the service providing system 100-1 (step S101).

The terminal 101 uses an input screen 900 as shown in FIG. 9 to transmit a usage request (step S151).

Note that the ID of the account of the service providing system 100-1 is entered in the related party ID entry field 901.

The service providing system 100-1 determines that it is necessary to confirm the account relationship between the first account and the second account, and transmits a relationship confirmation request to the service providing system 100-2 (step S152). Specifically, the following processing is executed.

(S152-1) The service providing unit 210 determines that the request is for use of a service provided to an account different from the account that sent the use request. Therefore, the service providing unit 210 refers to the service provision condition management information 224, searches for an entry in which the ID of the second account is stored in the account ID 701, and the service type included in the use request is stored in the service type 702. Get the value of the row relationship 711 . The service providing unit 210 outputs the value to the account relationship managing unit 212 .

(S152-2) The account relationship management unit 212 refers to the account relationship management information 221, sets the pair of IDs of the first account and the second account in the relationship account 402, and inputs the relationship 403. Search for an entry with a value set to Here, it is assumed that the aforementioned entry does not exist. The account relationship management unit 212 responds that the entry does not exist in the service providing unit 210 .

(S152-3) The service providing unit 210 refers to the account cooperation management information 222 and converts the IDs of the first account and the second account into account IDs of the cooperation service providing system 100.

(S152-4) The inquiry unit 213 generates a relationship confirmation request including the account relationship and the account ID of the cooperative service providing system 100. Also, the inquiry unit 213 transmits a relationship confirmation request to the cooperative service providing system 100 based on the service management information 223 .

The above is the description of the processing in step S152.

When receiving the relationship confirmation request, the account relationship management unit 212 of the service providing system 100-2 refers to the account relationship management unit 212, verifies the specified account relationship, and responds with the verification result. to the service providing system 100-1 (step S153). Here, it is assumed that it has been correctly verified.

The inquiry unit 213 of the service providing system 100-1 determines whether or not the service can be used based on the response, and outputs the determination result to the service providing unit 210. Here, it is assumed that service use is permitted. The service providing unit 210 of the service providing system 100-1 provides a service to the terminal 101 (step S109).

It should be noted that the terminal 101 may include a parameter or the like for confirming the account relationship in the usage request. In this case, the service providing unit 210 calls the inquiry unit 213 and instructs transmission of the relationship confirmation request.

According to the second embodiment, it is possible to reduce the amount of communication and reduce the man-hours required for verifying account relationships.

In the third embodiment, the linked service providing system 100-2 receives a request from the terminal 101 of the user who has the first account, and the linked service providing system 100-2 uses the second account (related party) ID to access the service providing system. Perform identity verification for 100-1. The third embodiment will be described below, focusing on the differences from the first embodiment.

The configuration of the computer system of Example 3 is the same. The configuration of the service providing system 100 of the third embodiment is the same as that of the first embodiment.

The data structure of the information held by the service providing system 100 of the third embodiment is partially different.

FIG. 14 is a diagram showing an example of the data structure of the account cooperation management information 222 of the third embodiment. In addition to the field example of Example 1, the account PW (password) 1401 field is included.

FIG. 15 is a diagram showing an example of the data structure of the service provision condition management information 224 of the third embodiment. A service ID 1501 is included instead of the service type 702 of the first embodiment. Service ID 1501 is the same field as service ID 511 . In the account cooperation management information 222, when a plurality of cooperation services 502 are associated with an account ID, a condition 703 is held for each service ID 1501 of the cooperation service.

In Example 3, the processing procedure for service provision processing is partially different. FIG. 16 is a sequence diagram showing the flow of service providing processing in the computer system of the third embodiment.

The terminal 101 operated by the user having the first account transmits an identity verification request to the cooperative service providing system 100-2 (step S1601).

The account management unit 211 of the cooperative service providing system 100-2 performs account authentication and notifies the terminal 101 of the processing result (step S1602). Here, it is assumed that account authentication has succeeded. Since the account authentication is a well-known technique, detailed explanation is omitted.

The terminal 101 operated by the user having the first account transmits a relationship confirmation/service list provision request to the cooperative service providing system 100-2 (step S1603). The request includes an account (second account) different from the account (first account) sent in step S1601.

The linked service providing system 100-2 confirms the account relationship between the first account and the second account, and generates a service list of services of the other service providing system 100-1 that the first account can use with the second account. Then, the terminal 101 is notified of the service list as a processing result (step S1604). Specifically, the following processing is executed.

(S1604-1) Account management unit 211 refers to account management information 220, searches for an entry corresponding to the second account, acquires status 306 of the searched entry, and outputs it to account relationship management unit 212. .

(S1604-2) The account relationship management unit 212 refers to the account relationship management information 221, searches for an entry in which the ID of the first account and the ID of the second account are stored in the relationship account 402, and finds an entry. If so, the value of the relationship 403 is acquired. Here, it is assumed that there is an entry.

(S1604-3) The account relationship management unit 212 refers to the service provision condition management information 224, searches for an entry in which the ID of the second account is stored in the account ID 701, and sets the service ID 1501 and condition 703 of the searched entry. to get

(S1604-4) Based on the relationship 403 between the first account and the second account acquired in S1604-2 and the state 306 of the second account acquired in S1601-1, the account relationship management unit 212 sets the condition It is determined whether 703 (relationship 711, execution timing 712) is satisfied. Satisfying the condition indicates that the first account can use other services of the second account.

(S1604-5) If there are multiple service IDs 1501, a list of service IDs satisfying the conditions is repeatedly generated and output to the service providing unit 210. Here, it is assumed that there exists a service that satisfies the conditions. The service list may be provided with information on whether or not each service can be provided, and services that do not satisfy the conditions in S1604 may also be included in the list. A service list for each of a plurality of second accounts may be generated and output by not including the second account in the request of S1603 or including a plurality of second accounts. If the request does not include the second account, S1604-2 searches for an entry based on the first account.

(S1604-6) The service providing unit 210 transmits the service list to the terminal 101.

The terminal 101 operated by the user having the first account transmits an identity verification request to the cooperative service providing system 100-2 (step S1605). The request here is a request for terminal 101 to use the service provided by service providing system 100-1, and includes the first account ID, the second account ID, and the service ID of service providing system 100-1.

If the conditions are met, the service providing system 100-2 transmits an identity verification request including the second account to the service providing system 100-1 (step S1606). Specifically, the following processing is executed.

(S1606-1) The linked service providing system 100-2 determines whether the combination of the first and second accounts and the service included in the request satisfies the conditions. Since the determination of this condition is the same processing as in steps S1604-1 to S1604-4, detailed description thereof will be omitted. The service list generated in step S1604 is held by the cooperative service providing system 100-2, and may be used for determination. It is assumed here that the conditions are satisfied.

(S1606-2) The service providing unit 210 refers to the account cooperation management information 222, and the received second account ID is stored in the account ID 501, and the received service ID is stored in the service ID 511 of the cooperation service 502. The entry is searched, and the account ID 512 and account PW 1401 of the linked service of the line included in the entry are acquired.

(S1606-3) The service providing unit 210 transmits an identity verification request to the service providing system 100-1. The request includes the account ID of the cooperative service acquired in step S1606-2, the account PW1401, and the like.

The account management unit 211 of the service providing system 100-1 performs account authentication and notifies the cooperative service providing system 100-2 of the processing result (step S1607). Here, it is assumed that account authentication has succeeded. Since the account authentication is a well-known technique, detailed explanation is omitted.

The linked service providing system 100-2 notifies the terminal 101 that the service providing system 100-1 has been successfully authenticated (step S1608). This means that the user who has the first account has successfully authenticated the service providing system 100-1 with the second account.

The terminal 101 transmits the service use request of the service providing system 100-1 to the cooperative service providing system 100-2 (step S1609).

The linked service providing system 100-2 transmits a service use request to the service providing system 100-1 using the second account (step S1610). Acquisition of the ID of the second account is similar to step S1606-2.

The service providing system 100-1 provides the service to the linked service providing system 100-2 (step S1611).

The linked service providing system 100-2 provides the terminal 101 with the service provided by the service providing system 100-1 (step S1612).

After the authentication is successful in step S1607, the terminal 101 transmits a service use request to the service providing system 100-1 without going through the cooperative service providing system 100-2, and the service providing system 100-1 sends the terminal 101 may be served.

According to the third embodiment, it is possible to simplify the management information and functions implemented in the service providing system 100-1, and to control the provision of services to persons (agents, relatives, etc.) other than the principal.

It should be noted that the present invention is not limited to the above-described embodiments, and includes various modifications. Further, for example, the above-described embodiments are detailed descriptions of the configurations for easy understanding of the present invention, and are not necessarily limited to those having all the described configurations. Moreover, it is possible to add, delete, or replace a part of the configuration of each embodiment with another configuration.

In addition, each of the above configurations, functions, processing units, processing means, etc. may be realized in hardware, for example, by designing a part or all of them with an integrated circuit. The present invention can also be implemented by software program code that implements the functions of the embodiments. In this case, a computer is provided with a storage medium recording the program code, and a processor included in the computer reads the program code stored in the storage medium. In this case, the program code itself read from the storage medium implements the functions of the above-described embodiments, and the program code itself and the storage medium storing it constitute the present invention. Examples of storage media for supplying such program code include flexible disks, CD-ROMs, DVD-ROMs, hard disks, SSDs (Solid State Drives), optical disks, magneto-optical disks, CD-Rs, magnetic tapes, A nonvolatile memory card, ROM, or the like is used.

Also, the program code that implements the functions described in this embodiment can be implemented in a wide range of programs or script languages, such as assembler, C/C++, perl, Shell, PHP, Python, and Java.

Furthermore, by distributing the program code of the software that implements the functions of the embodiment via a network, it can be stored in storage means such as a hard disk or memory of a computer, or in a storage medium such as a CD-RW or CD-R. Alternatively, a processor provided in the computer may read and execute the program code stored in the storage means or the storage medium.

In the above examples, the control lines and information lines indicate those that are considered necessary for explanation, and not all the control lines and information lines are necessarily indicated on the product. All configurations may be interconnected.

Claims

A computer system comprising at least one computer and providing services,
Connect with multiple other computer systems that provide different services,
at least one of the other computer systems manages account relationship management information storing data indicating relationships between accounts;
When a request for use of the first service requiring confirmation of the relationship between the first account and the second account is received from the terminal operated by the user having the first account, the first sending a first confirmation request for confirming the relationship between the first account and the second account to another computer system;
A computer system that executes processing for the usage request based on a response transmitted from the first other computer system.
A computer system according to claim 1,
A computer system, wherein the response includes a verification result of the relationship between the first account and the second account by the first other computer system.
A computer system according to claim 1,
When the response including information for accessing the account relationship management information is received, the relationship between the first account and the second account is determined from the account relationship management information via the first other computer system. Acquiring the data indicating the sex,
verifying the relationship between the first account and the second account using the acquired data;
A computer system that executes data processing for the usage request based on the result of the verification.
A computer system according to claim 3,
managing the account relationship management information;
A computer system, wherein the account relationship management information is updated based on the data indicating the relationship between the first account and the second account, which is included in the response.
A computer system according to claim 1,
managing the account relationship management information;
The computer system is
When a second confirmation request for confirming the relationship between the third account and the fourth account is received from the second other computer system, the third account and the fourth account based on the account relationship management information perform data processing to verify the relationship between
A computer system that transmits a response including a result of the data processing to the second other computer system.
A computer system according to claim 1,
When a confirmation request for confirming the relationship between the third account and the fourth account is received from the second other computer system, indicating the relationship between the third account and the fourth account from the first other computer system obtaining said data;
perform data processing to verify the relationship between the third account and the fourth account;
A computer system that transmits a response including a result of the data processing to the second other computer system.
A computer system according to claim 1,
A computer system characterized by transmitting said first confirmation request to said first other computer system via said terminal.
A data processing method executed by a computer system that includes at least one computer and provides services,
the computer system is connected to a plurality of other computer systems that provide different services;
at least one of the other computer systems manages account relationship management information storing data indicating relationships between accounts;
The data processing method includes:
When the computer system receives, from a terminal operated by a user having a first account, a request for use of a first service that requires confirmation of the relationship between the first account and the second account, the account relationship management information a first step of sending a first confirmation request for confirming the relationship between the first account and the second account to a first other computer system managing the
and a second step in which the computer system executes processing for the usage request based on the response transmitted from the first other computer system.
The data processing method according to claim 8,
The data processing method, wherein the response includes a verification result of the relationship between the first account and the second account by the first other computer system.
The data processing method according to claim 8,
The second step includes
When the computer system receives the response containing the information for accessing the account relationship management information, the first account and the obtaining the data indicating the relationship of the second account;
a step in which the computer system verifies the relationship between the first account and the second account using the acquired data;
A data processing method, wherein the computer system executes data processing for the usage request based on the result of the verification.
The data processing method according to claim 10,
The computer system manages the account relationship management information,
The second step includes updating the account relationship management information by the computer system based on the data indicating the relationship between the first account and the second account included in the response. A data processing method characterized by:
The data processing method according to claim 8,
The computer system manages the account relationship management information,
The data processing method includes:
When the computer system receives a second confirmation request for confirming the relationship between the third account and the fourth account from the second other computer system, based on the account relationship management information, the third account and performing data processing to verify the relationship of said fourth account;
A data processing method, comprising the step of: said computer system transmitting a response including said data processing result to said second other computer system.
The data processing method according to claim 8,
When the computer system receives a confirmation request for confirming the relationship between the third account and the fourth account from the second other computer system, the third account and the fourth account from the first other computer system obtaining the data indicating the relationship of
the computer system executing data processing to verify the relationship between the third account and the fourth account;
A data processing method, comprising the step of: said computer system transmitting a response including said data processing result to said second other computer system.
The data processing method according to claim 8,
A data processing method, wherein said first step includes a step of said computer system transmitting said first confirmation request to said first other computer system via said terminal.