Information processing system, information processing device, information processing method, and program

Abstract

To provide service providers with an environment that enables easy integration of user information from other services. [Solution] The system includes an identification unit (11) that identifies a second service capable of providing user information to the provider of the first service, an inquiry unit (12) that inquires with a user of the first service whether or not they consent to the provider of the first service using their user information in the second service as a result of using the first service, and an integration unit (13) that, when information indicating the user's consent is obtained, links the first service and the second service by associating the user information of the first service and the user information of the second service concerning that user.

Description

Technical Field

[0001] The present invention relates to a technology for coordinating a plurality of services.

Background Art

[0002] A technology for coordinating a plurality of services is known. For example, Patent Document 1 describes a technology in which a request system and a provision system participating in a system for coordinating a plurality of services provide data to a user. When the request system is requested for data by the user and cannot provide the data, and when user authentication by an authentication method corresponding to the data is successful, the data is acquired from another provision system and provided to the user.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] Here, in the technology described in Patent Document 1, when the provider of the request system wants to use the user information in the provision system regardless of the request from the user, user authentication is required each time, which is not realistic. Therefore, in the coordination system described in Patent Document 1, it has been difficult for the provider of the request system to use the user information in the provision system.

[0005] One aspect of the present invention has been made in view of the above problems, and an example of the object is to provide an environment for performing service coordination in which a service provider can easily use user information in other services.

Means for Solving the Problems

[0006] A linkage system according to one aspect of the present invention includes: identification means for identifying a second service capable of providing user information to a first service provider; inquiry means for inquiring with a user of the first service whether or not they consent to the provider of the first service using their user information in the second service as a result of using the first service; and linkage means for linking the first service and the second service by associating the user information of the first service and the user information of the second service relating to the user, when information indicating the user's consent is obtained.

[0007] A linking method according to one aspect of the present invention includes: at least one processor identifying a second service capable of providing user information to a first service provider; querying a user of the first service whether they consent to the provider of the first service using their user information in the second service as a result of using the first service; and, if information indicating the user's consent is obtained, linking the first service and the second service by associating the user information of the first service and the user information of the second service relating to that user.

[0008] A program according to one aspect of the present invention causes a computer to function as: an identification means for identifying a second service capable of providing user information to a first service provider; an inquiry means for inquiring with a user of the first service whether or not they consent to the provider of the first service using their user information in the second service, triggered by their use of the first service; and an integration means for linking the first service and the second service by associating the user information of the first service and the user information of the second service relating to the user, when information indicating the user's consent is obtained. [Effects of the Invention]

[0009] According to one aspect of the present invention, it is possible to provide service providers with an environment that enables service integration, allowing them to easily utilize user information from other services. [Brief explanation of the drawing]

[0010] [Figure 1] This is a block diagram showing the configuration of the collaborative system according to Exemplary Embodiment 1. [Figure 2] This is a flowchart showing the flow of the cooperation method according to Exemplary Embodiment 1. [Figure 3] This is a block diagram showing the configuration of the collaborative system according to exemplary embodiment 2. [Figure 4] This is a flowchart showing the flow of the collaboration method related to exemplary implementation form 2. [Figure 5] This figure illustrates a specific example of catalog information in Exemplary Embodiment 2. [Figure 6] This figure illustrates a specific example of the linked information in Exemplary Embodiment 2. [Figure 7] This flowchart shows the flow of the collaboration method following Figure 4. [Figure 8] This figure shows an example of a login screen in Exemplary Embodiment 2. [Figure 9] This figure shows another example of the login screen in Exemplary Embodiment 2. [Figure 10] This figure shows an example of a login screen in exemplary embodiment 2 that does not include a request for cooperation. [Figure 11] This figure shows an example of a login screen for requesting collaboration in exemplary embodiment 2. [Figure 12] This figure shows another example of the login screen for requesting collaboration in Exemplary Embodiment 2. [Figure 13] This figure illustrates a specific example of user-associated information in Exemplary Embodiment 2. [Figure 14] Figure 7 is a flowchart showing the flow of the collaboration method. [Figure 15]It is a diagram showing an example of the hardware configuration of each device constituting the cooperation system according to each exemplary embodiment.

Mode for Carrying Out the Invention

[0011] 〔Exemplary Embodiment 1〕 The first exemplary embodiment of the present invention will be described in detail with reference to the drawings. This exemplary embodiment is a basic form of the exemplary embodiments described later.

[0012] <Configuration of Cooperation System 1> The configuration of the cooperation system 1 according to this exemplary embodiment will be described with reference to FIG. 1. FIG. 1 is a block diagram showing the configuration of the cooperation system 1.

[0013] As shown in FIG. 1, the cooperation system 1 includes a specifying unit 11, an inquiry unit 12, and a cooperation unit 13. The specifying unit 11 specifies a second service that can provide user information to the provider of the first service. The inquiry unit 12 inquires the user who uses the first service whether the provider of the first service agrees to use the user information regarding the user in the second service on the occasion of using the first service. The cooperation unit 13 associates the user information of the first service and the user information of the second service regarding the user when information indicating the user's consent is obtained, thereby cooperating the first service and the second service.

[0014] <Flow of Cooperation Method S1> The cooperation system 1 configured as described above executes the cooperation method S1 according to this exemplary embodiment. The flow of the cooperation method S1 will be described with reference to FIG. 2. FIG. 2 is a flowchart showing the flow of the cooperation method S1.

[0015] As shown in Figure 2, the linking method S1 includes steps S11 to S13. In step S11, the identification unit 11 identifies a second service that can provide user information to the provider of the first service. In step S12, the inquiry unit 12 inquires with the user using the first service whether or not they consent to the provider of the first service using their user information in the second service as a result of using the first service. In step S13, if information indicating the user's consent is obtained, the linking unit 13 links the first service and the second service by associating the user information of the first service and the user information of the second service concerning that user.

[0016] <Example of implementation using a program> When the collaborative system 1 is configured using a computer, the following program is stored in the memory referenced by the computer. This program causes the computer to function as an identification unit 11 that identifies a second service capable of providing user information to the provider of the first service, an inquiry unit 12 that inquires with a user of the first service whether or not they consent to the provider of the first service using their user information in the second service, triggered by their use of the first service, and a collaboration unit 13 that links the first service and the second service by associating the user information of the first service and the user information of the second service concerning that user when information indicating the user's consent is obtained.

[0017] The aforementioned cooperation method S1 is realized when the computer reads the program from memory and executes it.

[0018] <Effects of this exemplary embodiment> As described above, in this exemplary embodiment, a second service capable of providing user information to the provider of the first service is identified, and a user using the first service is asked whether they consent to the provider of the first service using their user information in the second service as a result of using the first service. If information indicating the user's consent is obtained, the first service and the second service are linked by associating the user information of the first service and the user information of the second service concerning that user.

[0019] According to the above configuration, the first and second services are linked after obtaining the user's consent for the provider of the second service to use the user information in the second service. As a result, the provider of the first service can be provided with an environment for service integration that allows for easy use of user information in the second service.

[0020] [Exemplary Embodiment 2] A second exemplary embodiment of the present invention will be described in detail with reference to the drawings. Components having the same function as those described in Exemplary Embodiment 1 will be denoted by the same reference numerals, and their descriptions will be omitted as appropriate.

[0021] <Configuration of the linked system 1A> The configuration of the collaborative system 1A according to this exemplary embodiment will be described with reference to Figure 3. Figure 3 is a block diagram showing the configuration of the collaborative system 1A. As shown in Figure 3, the collaborative system 1A includes a collaborative server 10, a first server 20, a second server 30, and a user terminal 40. Each of these devices is connected to each other so as to be able to communicate via a network N1. The network N1 may include, but is not limited to, a wired LAN (Local Area Network), a wireless LAN, a WAN (Wide Area Network), mobile data communication, or the Internet. Although Figure 3 shows one of each device, the number of each device may be multiple.

[0022] The integration server 10 is a server that provides integration services. Here, an integration service is a service that links multiple services together. Each of the multiple services is provided by a corresponding service provider. Note that a single service provider may provide multiple services or just one service.

[0023] Among multiple service providers, the service provider that requests user information for other services is referred to as the first service provider. Furthermore, among multiple services, the service provided by the first service provider is referred to as the first service. The first service may be linked to by a linked service. The first server 20 is a server that provides the first service and has the function of requesting and obtaining user information for the second service.

[0024] Furthermore, among the multiple services, the service that can provide user information to the first service provider is referred to as the second service. Also, among the multiple service providers, the service provider that provides the second service is referred to as the second service provider. The second service may be linked through linked services. The second server 30 is a server that provides the second service and has the function of providing user information to the first service provider.

[0025] User terminal 40 is a terminal used by a user. A user using user terminal 40 uses both the first service and the second service. For example, a user may be a user who has completed user registration for both the first service and the second service.

[0026] Furthermore, each service provider can be both the first service provider and the second service provider. In other words, each service can be both the first service and the second service. To put it another way, the first server 20 may also have a functional block of the second server 30. Similarly, the second server 30 may also have a functional block of the first server 20. When there is no need to distinguish between the first service provider and the second service provider, they may simply be referred to as "service providers." Similarly, when there is no need to distinguish between the first service and the second service, they may simply be referred to as "services."

[0027] (Configuration of linked server 10) The collaborative server 10 includes a control unit 110, a storage unit 120, and a communication unit 130. The control unit 110 controls all parts of the collaborative server 10. The storage unit 120 stores various data that the control unit 110 references. The communication unit 130 sends and receives information with other devices via the network N1.

[0028] Furthermore, the control unit 110 includes a specification unit 111, an inquiry unit 112, a linkage unit 113, and a provision unit 114. The specification unit 111 and the specification unit 213 of the first server 20, described later, can be an example of a configuration in which the specification means described in the claims are distributed between the linkage server 10 and the first server 20. The inquiry unit 112 and the inquiry unit 214 of the first server 20, described later, can be an example of a configuration in which the inquiry means described in the claims are distributed between the linkage server 10 and the first server 20. The linkage unit 113 can be an example of a configuration that realizes the linkage means described in the claims. The provision unit 114 can be an example of a configuration that realizes the provision means described in the claims. Furthermore, the storage unit 120 stores catalog information D1, linkage information D2, and user association information D3. Details of each of these units and each data will be explained in the "Flow of Linkage Method S1A~S1C" described later.

[0029] (Configuration of Server 1, 20) The first server 20 includes a control unit 210, a storage unit 220, and a communication unit 230. The control unit 210 controls all parts of the first server 20. The storage unit 220 stores various data referenced by the control unit 210. The communication unit 230 sends and receives information to and from other devices via the network N1.

[0030] The control unit 210 also includes a service provision unit 211, a request unit 212, a specification unit 213, an inquiry unit 214, and a user information request unit 215. The storage unit 220 stores user information U1.

[0031] User information U1 is information about a user who uses the first service. User information U1 includes, for example, the user's authentication information for the first service (for example, user ID and password), as well as the user's attributes. The service provision unit 211 performs processing to provide the first service to the user. The service provision unit 211 also generates and updates user information U1. The service provision unit 211 also performs user authentication processing by referring to the authentication information contained in user information U1. Details of other parts and data in the first server 20 will be explained later in "Flow of Linkage Method S1A~S1C".

[0032] (Configuration of Server 2, 30) The second server 30 includes a control unit 310, a storage unit 320, and a communication unit 330. The control unit 310 controls all parts of the second server 30. The storage unit 320 stores various data referenced by the control unit 310. The communication unit 330 sends and receives information to and from other devices via the network N1.

[0033] The control unit 310 also includes a service provision unit 311, a registration unit 312, and a user information transmission unit 313. The storage unit 320 stores user information U2.

[0034] User information U2 is information about a user who uses the second service. User information U2 includes, for example, authentication information for the second service (such as user ID and password), as well as the user's attributes. The service provision unit 311 performs processing to provide the second service to the user. The service provision unit 311 also generates and updates user information U2. The service provision unit 311 also performs user authentication processing by referring to the authentication information contained in user information U2. Details of other parts and data in the second server 30 will be explained later in "Flow of Linkage Method S1A~S1C". Details of these parts and data will be explained later.

[0035] (Configuration of user terminal 40) The user terminal 40 includes a control unit 410, a storage unit 420, a communication unit 430, an input unit 440, and an output unit 450. The control unit 410 controls all parts of the user terminal 40. The storage unit 420 stores various data referenced by the control unit 410. The communication unit 430 sends and receives information to and from other devices via the network N1. The input unit 440 receives user input operations to the user terminal 40. The input unit 440 may be, for example, a keyboard, mouse, touchpad, or a combination thereof. The output unit 450 outputs information under the control of the control unit 410. The output unit 450 may be, for example, a display, speaker, or a combination thereof. The input unit 440 and the output unit 450 may also be integrally formed, for example, a touch panel.

[0036] <Flowchart of integration method S1A> The collaborative system 1A configured as described above executes the collaborative methods S1A to S1C according to this exemplary embodiment.

[0037] First, the integration method S1A will be explained with reference to Figure 4. Figure 4 is a flowchart showing the flow of integration method S1A. Integration method S1A is a method for identifying a second service that can provide user information U2 to the first service provider. As shown in Figure 4, integration method S1A includes steps S101 to S106. Note that in steps S101 to S105, until the second service is identified in step S106, the service provided by the second server 30 will also be referred to as a "candidate for the second service".

[0038] In step S101, the registration unit 312 of the second server 30 transmits registration information for registering the available attributes to the cooperating server 10. The registration information includes identification information of the candidate for the second service and the available attributes. The available attributes are the attributes of the user information U2 that can be provided to the provider of the first service by the candidate for the second service. The available attributes may be some of the attributes included in the user information U2, or all of them.

[0039] In step S102, the identification unit 111 of the cooperating server 10 refers to the received registration information and registers the available attributes in catalog information D1. Catalog information D1 is information that includes the available attributes for each of the one or more candidate second services. A specific example of catalog information D1 will be explained with reference to Figure 5. Figure 5 is a diagram illustrating a specific example of catalog information D1. As shown in Figure 5, an example of catalog information D1 includes information that associates the identification information of a service (candidate second service) with the available attributes. Hereinafter, a service with identification information of "X" will also be referred to as service X. For example, in this example, the available attributes of service B are age, number of steps, and heart rate. Also, the available attributes of service C are age, number of steps, and residential area. Also, the available attributes of service D are age, number of steps, and gender.

[0040] In step S103, the request unit 212 of the first server 20 sends request information to the cooperating server 10 to request user information U2. For example, the request information includes the identification information of the first service and the request attributes. The request attributes are the attributes of user information U2 requested by the first service provider. Here, let's assume that request information including age and step count is sent as request attributes.

[0041] In step S104, the identification unit 111 of the cooperating server 10 refers to the catalog information D1 and extracts candidates for the second service associated with the available attributes, including the requested attributes. The identification unit 111 also sends a list of the extracted candidates (hereinafter referred to as the candidate list) to the first server 20. For example, in the catalog information D1 shown in Figure 5, the available attributes of services B, C, and D all include the requested attributes age and step count. Therefore, "B, C, D" is sent as the candidate list.

[0042] In step S105, the request unit 212 of the first server 20 selects some or all of the candidate list. The request unit 212 also sends the selected candidates to the cooperating server 10. For example, the request unit 212 may output the candidate list to an output device (not shown) and select some or all of them through input operations by the first service provider to an input device (not shown).

[0043] In step S106, the identification unit 111 of the cooperating server 10 identifies the second service by referring to the catalog information D1 (available attributes) and the request attributes. Specifically, it identifies the candidate received in step S105 as the second service. The identification unit 111 also generates linking information D2 linking the first service and the identified second service, and stores it in the storage unit 120. The identification unit 111 may also notify the first server 20 that the linking with the second service is complete once it has generated the linking information D2.

[0044] A specific example of the linking information D2 will be explained with reference to Figure 6. Figure 6 is a diagram illustrating a specific example of the linking information D2. As shown in Figure 6, one example of the linking information D2 is information that associates the identification information of the first service, the request attribute, and the identification information of the second service. Specifically, the identification unit 111 generates the linking information D2 by associating the identification information and request attribute of the first service included in the request information received in step S103 with the identification information of the second service identified in step S106. For example, in the example in Figure 6, service B is associated with service A (first service) as a second service capable of providing user information U2 with the request attribute "age and number of steps". In addition, services D and E are associated with service B (first service) as second services capable of providing user information U2 with the request attribute "gender".

[0045] For example, the provider of service A (first service provider) may access the catalog information D1 site published by the cooperating server 10, refer to catalog information D1, and then input the request attributes. The provider of service A may then select service B from the extracted list of candidates "B, C, D". As a result, service B is identified as the second service, and the first line of the linking information D2 in Figure 6 is generated. In other words, the first line of the linking information D2 indicates that service A and service B can be linked.

[0046] This concludes the explanation of integration method S1A.

[0047] <Integration Method S1B Flow> Next, the integration method S1B will be explained with reference to Figure 7. Figure 7 is a flowchart showing the flow of integration method S1B. Integration method S1B is executed by referring to the linking information D2 generated in integration method S1A. In integration method S1B, the user is asked whether or not to consent to providing user information U2 in the second service to the first service provider in connection with the integration of the first service and the second service. If consent is obtained, the first service and the second service are integrated. As shown in Figure 7, integration method S1B includes steps S201 to S213.

[0048] In step S201, the identification unit 213 of the first server 20 refers to the association information D2 and identifies the second service that can provide user information U2 to the first service provider. For example, this step may be performed when access to the first service is received from the user terminal 40. Access to the first service may be, for example, access to a web page for using the first service.

[0049] For example, the identification unit 213 may identify the second service linked to the first service by querying the cooperating server 10 which holds the linking information D2. Alternatively, if the identification unit 213 has received notification from the cooperating server 10 that the linking is complete in step S106, it may identify the second service indicated by the linking completion notification without querying the cooperating server 10.

[0050] Furthermore, if multiple second services are linked to the first service in the linking information D2, the identification unit 213 may identify some of them as second services, or it may identify all of them. If multiple second services are identified, the linkage system 1A may perform the subsequent processing for each second service.

[0051] In step S202, the inquiry unit 214 transmits a login screen (an example of the first inquiry screen) to the user terminal 40 for user authentication in the first service. The inquiry unit 214 also includes information on the login screen to inquire whether or not to request the linkage between the first service and the second service. The control unit 410 of the user terminal 40 displays the received login screen on the output unit 450 (in this case, the display).

[0052] Specific example 1 of the login screen will be explained with reference to Figure 8. Figure 8 is a diagram showing an example of a login screen. In this example, the first service is named "Service A," and the second service is named "Service B." The login screen G1 shown in Figure 8 is displayed on the user terminal 40 in response to access to "Service A" from the user terminal 40. The login screen G1 includes user interface (UI) objects G11 to G14. UI objects G11 and G12 accept input of authentication information for Service A (in this example, user ID and password). UI object G13 accepts operations to use Service A without coordinating with Service B. UI object G14 accepts requests for coordination with Service B. In other words, an operation on UI object G13 indicates that no coordination request for Service A and Service B will be made. Conversely, an operation on UI object G14 indicates that a coordination request for Service A and Service B will be made.

[0053] Furthermore, a specific example of the login screen, Part 2, will be explained with reference to Figure 9. Figure 9 shows another example of a login screen. The login screen G1B shown in Figure 9 includes UI objects G11 to G14, similar to login screen G1, as well as UI object G15. An operation on UI object G15 indicates the user's instruction that no further inquiry for linkage requests is necessary. When the inquiry unit 214 receives an operation on UI object G15, it will not include an inquiry for linkage requests with service B on the login screen of service A thereafter.

[0054] A specific example of the login screen displayed when an operation on such UI object G15 (an operation indicating that a linkage request is not required) is received will be explained with reference to Figure 10. Figure 10 shows an example of a login screen that does not include a linkage request. Screen G1C shown in Figure 10 does not include UI object G14, which is used to make a linkage request, among the same UI objects G11 to G14 as login screen G1. This eliminates the inconvenience of being prompted for a linkage request every time a user accesses service A, for users who use service A but not service B, or for users who have chosen not to agree to link with service B. Note that this login screen G1 is also displayed to users who have already linked services A and B.

[0055] In step S203, the control unit 410 of the user terminal 40 sends the authentication information for the first service and the request for linkage between the first and second services to the first server 20. For example, suppose an operation (a linkage request operation) is received on the UI object G14 in the login screens G1 and G1B shown in Figures 8 and 9. In this case, the control unit 410 sends the authentication information (user ID and password) entered in the UI objects G11 and G12, along with the linkage request, to the first server 20. Subsequently, the processing from step S204 is executed. In other words, if the query result for the login screens G1 and G1B (first inquiry screen) indicates a request for linkage, the processing from step S204 is executed.

[0056] If an operation on UI object G13 (an operation that does not request cooperation) is accepted, cooperation method S1B terminates, and the service provision unit 211 executes the first service provision process.

[0057] In step S204, the service provision unit 211 of the first server 20 refers to the user information U1 and the authentication information received in step S203 to perform user authentication processing for the first service. If authentication is successful, the process from step S205 proceeds. If authentication is unsuccessful, the cooperation method S1B terminates.

[0058] In step S205, the inquiry unit 214 of the first server 20 sends a linkage request for the first service and the second service to the linkage server 10. The linkage request includes the user information U1 of the user in question for the first service.

[0059] In step S206, the inquiry unit 112 of the linking server 10 uses the linking information D2 held by its own server as confirmation and makes an inquiry to the user via a login screen for linking requests. Specifically, the inquiry unit 112 checks whether the first service and the second service can link by checking the linking information D2. If the first service and the second service cannot link, linking method S1B ends. If the first service and the second service can link, the inquiry unit 112 makes an inquiry via a login screen for linking requests in step S207, which will be described below. In other words, the inquiry unit 112 makes an inquiry to the user by referring to the linking information D2.

[0060] In step S207, the inquiry unit 112 of the linkage server 10 sends a login screen for linkage requests (an example of the second inquiry screen) for user authentication in the second service to the user terminal 40. The inquiry unit 112 also includes information in the login screen for linkage requests asking whether the user consents to the first service provider using the user information U2 concerning the user in the second service. The control unit 410 of the user terminal 40 displays the received login screen for linkage requests on the output unit 450 (in this case, the display).

[0061] Specific example 1 of the login screen for integration requests will be explained with reference to Figure 11. Figure 11 is a diagram showing an example of a login screen for integration requests. The login screen G2 for integration requests shown in Figure 11 includes UI objects G21 to G24. UI objects G21 and G22 accept input of authentication information for service B (in this example, user ID and password). An operation on UI object G23 indicates consent to the provider of service A (first service provider) using the user information U2 of service B. UI object G24 accepts an operation to consent to the integration of service A and service B.

[0062] Furthermore, the inquiry unit 112 of the cooperating server 10 may further inquire about the scope of user information U2 concerning the user in the second service that the first service provider is permitted to use. Hereafter, such "scope of permitted provision" will also be referred to as the "version of consent."

[0063] For example, let's look at a specific example of a login screen for linking requests that includes a confirmation of the consent version, with reference to Figure 12. Figure 12 shows another example of a login screen for linking requests. The login screen for linking requests G2B shown in Figure 12 includes UI objects G25 and G26 in place of UI object G23, among the same UI objects G21 to G24 as the login screen for linking requests G2. An operation on UI object G25 indicates consent to the provider of service A using the age information from the user information U2 of service B. Similarly, an operation on UI object G26 indicates consent to the provider of service A using the heart rate information from the user information U2 of service B. In other words, by operating on UI objects G25 and G26, the user can specify the consent version.

[0064] In this way, by executing steps S202 to S207, the inquiry unit 214 and inquiry unit 112 inquire whether the user using the first service and the second service agrees to "the provider of the first service using the user information U2 concerning the user in the second service in connection with the linkage of the first service and the second service."

[0065] In step S208, the control unit 410 of the user terminal 40 transmits authentication information for the second service and information indicating consent to the linking of the first and second services to the linking server 10. For example, suppose an operation (a linking consent operation) is received on the UI object G24 in the linking request login screens G2 and G2B shown in Figures 11 and 12. In this case, the control unit 410 transmits the authentication information (user ID and password) entered in the UI objects G21 and G22, and the consent information to the linking server 10.

[0066] In step S209, the linking unit 113 of the linking server 10 requests authentication processing in the second service by sending the authentication information received in step S208 to the second server 30.

[0067] In step S210, the service provision unit 311 of the second server 30 performs user authentication processing for the second service by referring to the user information U2 and the authentication information received in step S209. If authentication is successful, the process from step S210 proceeds. If authentication is unsuccessful, the cooperation method S1B terminates.

[0068] In step S210, the service provision unit 311 of the second server 30 sends information to the cooperating server 10 indicating that authentication was successful.

[0069] In step S211, the integration unit 113 of the integration server 10 associates the user information U1 of the first service and the user information U2 of the second service for the user in question. In other words, by executing steps S208 to S211, if the integration unit 113 obtains information indicating the user's consent to "the provider of the first service using the user information U2 of the user in question in the second service in connection with the integration of the first and second services," it authenticates the user using the authentication information of the second service. Then, if authentication is successful, the integration unit 113 associates the user information U1 of the first service and the user information U2 of the second service for the user in question, thereby integrating the first and second services.

[0070] For example, the linking unit 113 generates user association information D3 that associates the user information U1 for the first service and the user information U2 for the second service for the user in question, and stores it in the storage unit 120. A specific example of user association information D3 will be explained with reference to Figure 13. Figure 13 is a diagram illustrating a specific example of user association information D3. As shown in Figure 13, user association information D3 includes information that associates the user ID of service A (first service), the user ID of service B (second service), and the consent version. For example, the user ID of service A is included in the linking request received by the linking server 10 in step S205. The user ID and consent version of service B are included in the information received by the linking server 10 in step S208. Note that if user information U2 does not exist, it may be newly created.

[0071] For example, in this case, a user using Service A (First Service) with user ID "ID-A_001" also uses Service B (Second Service) with user ID "ID-B_001". Furthermore, the user has given consent for the service provider of Service A to use user information U2, which is managed by Service B, specifically age and step count information. In other words, the version of consent is "age and step count".

[0072] In this example, a user using Service A (the first service) with user ID "ID-A_002" also uses Service B (the second service) with user ID "ID-B_002". Furthermore, the user has given consent for the service provider of Service A to use the age information from the user information U2 managed by Service B for that user. In other words, the version of consent is "age".

[0073] In step S212, the integration unit 113 of the integration server 10 sends information indicating the completion of the integration (integration completion screen) to the user terminal 40. The control unit 410 of the user terminal 40 outputs the received information to the output unit 450. As a result, the user can recognize that the integration of the first service and the second service is complete, and that the first service provider will use the user information U2 in the second service.

[0074] In step S213, the linking unit 113 of the linking server 10 sends information indicating the completion of the linking process (linking completion notification) to the first server 20. The control unit 210 of the first server 20 outputs the received information to an output device (not shown). As a result, the first service provider can recognize that the linking of the first service and the second service is complete, and that the user's consent to the use of user information U2 in the second service has already been obtained.

[0075] From this point forward, the linked system 1A can provide the user with the first and second services in conjunction by referring to the user-associated information D3. For example, if a user successfully authenticates in the first service, they can use the second service without needing to authenticate in the second service. Also, if a user successfully authenticates in the second service, they can use the first service without needing to authenticate in the first service. Furthermore, the user-associated information D3 may also include an integrated ID. The integrated ID may be one newly created in step S211, or it may be an existing integrated ID already possessed by the user. In this case, if the user successfully authenticates the integrated ID, they can use the first and second services without needing to authenticate in the first and second services.

[0076] This concludes the explanation of integration method S1B.

[0077] <Integration Method S1C Flow> Next, the integration method S1C will be explained with reference to Figure 14. Figure 14 is a flowchart showing the flow of integration method S1C. Integration method S1C is executed by referring to the user association information D3 generated in integration method S1B. In integration method S1C, user information U2 in the second service is provided to the first service provider. Since the first server 20 has already obtained the user's consent for the use of user information U2 in the second service in integration method S1B, it does not need to ask the user for consent in integration method S1C. As shown in Figure 14, integration method S1C includes steps S301 to S306.

[0078] In step S301, the user information request unit 215 of the first server 20 requests user information U2 for the second service relating to the user of the first service from the cooperating server 10. For example, the user information request unit 215 sends request information to the cooperating server 10 that includes the identification information of the first service and the user ID of the user using the first service.

[0079] In step S302, the provision unit 114 of the cooperating server 10 refers to the user ID of the first service included in the request information and the user association information D3 to identify the user of the second service that corresponds to the user of the first service. In addition, if a consent version is set, the provision unit 114 obtains the consent version set for the user of the first service by referring to the user association information D3.

[0080] For example, if the request information includes the user ID "ID-A_001" for service A, the service provider 114 refers to the user association information D3 illustrated in Figure 8 and identifies the user ID "ID-B_001" for service B. The service provider 114 also obtains "age, steps" as the consent version.

[0081] In step S303, the service provider 114 requests user information U2 regarding the identified user of the second service from the second server 30. For example, the service provider 114 sends request information to the second server 30 that includes the identified user ID of the second service and the version of consent.

[0082] In step S304, the user information transmission unit 313 of the second server 30 transmits user information U2 relating to the user of the requested second service to the cooperating server 10. For example, if a consent version is set, the user information transmission unit 313 transmits the attribute indicated by the consent version from the user information U2 to the cooperating server 10.

[0083] In step S305, the service provider 114 of the cooperating server 10 refers to the user association information D3 and converts the user information U2 received in the second service into user information U1 in the first service. The conversion process may include, for example, a process to convert the format of user information U2 in the second service into the format of user information U1 in the first service. Information for performing such a conversion may also be included in the user association information D3.

[0084] In step S306, the provisioning unit 114 transmits the converted user information U1 to the first server 20. This allows the provisioning unit 114 to provide the provider of the first service with the user information U2 for the second service, which is associated with the user information U1 for the first service.

[0085] This concludes the explanation of the S1C integration method.

[0086] <Effects of this exemplary embodiment> As described above, this exemplary embodiment employs a configuration in which the second service is identified by referring to the available attributes of the candidate second service and the required attributes requested by the provider of the first service.

[0087] Therefore, the first service provider can more reliably obtain and use the attributes (request attributes) of the user information U2 that it wants to use from the second service.

[0088] Furthermore, in this exemplary embodiment, a configuration is adopted in which linkage information D2 is generated that links the first service and the second service, and inquiries are made to the user by referring to the linkage information D2.

[0089] This allows for more reliable linking of the first and second services by referring to the linked information D2.

[0090] Furthermore, in this exemplary embodiment, a configuration is adopted in which the first service provider is provided with user information U2 of the second service associated with user information U1 of the first service.

[0091] As a result, the first service provider can easily use the user information U2 of the user in the second service without further requesting consent, since the user's consent was obtained when linking the first and second services.

[0092] Furthermore, in this exemplary embodiment, the login screen (first inquiry screen) for user authentication in the first service includes "information to inquire whether or not to request linkage between the first service and the second service." In addition, in this exemplary embodiment, if the query result to the login screen indicates that linkage is requested, the login screen for requesting linkage (second inquiry screen) for user authentication in the second service includes "information to inquire whether or not to consent to the provider of the first service using user information U2 concerning the user in the second service."

[0093] This makes it easier to guide users who access the first service to consent to integration with the second service and the provision of user information U2.

[0094] Furthermore, in this exemplary embodiment, a configuration is adopted in which the version of consent is further queried from the user information U2 concerning the user in the second service.

[0095] This makes it easier to obtain consent for the use of user information U2 from users who request integration between the first and second services.

[0096] [Variation 1] This exemplary embodiment is also applicable when one or both of the first and second services are integrated services that combine multiple services. For example, the first service may manage a first integrated ID that combines the user IDs of each service under its management. The second service may also manage a second integrated ID that combines the user IDs of each service under its management. In this case, the inquiry unit 112 and the inquiry unit 214 make inquiries to users who have the first integrated ID and the second integrated ID. The inquiry content includes "an inquiry as to whether the user consents to the use of user information U2 in each service under the management of the second service by the providers of each service under the management of the first service in connection with the collaboration of the first and second services." Even with this modification, this exemplary embodiment produces the same effects as described above.

[0097] [Variation 2] In this exemplary embodiment, the identification unit 111 and the identification unit 213 may identify a second service in real time that can provide user information U2 to the provider of the first service when a user accesses the first service. Specifically, for example, instead of, or in addition to, pre-generating the linking information D2, the identification unit 111 and the identification unit 213 may generate the linking information D2 in real time when a user accesses the first service. In this case, the linkage system 1A executes steps S104 to S106 in linkage method S1A in step S201 in linkage method S1B. As a result, the second service is identified by referring to the latest catalog information D1.

[0098] [Example 3] In this exemplary embodiment, the inquiry unit 214 may include information in the login screen displayed when access to the first service is accepted, which inquires whether or not to request coordination between the first and second services for a predetermined period. For example, if access to the first service is accepted during the predetermined period, the login screen shown in Figure 8 is displayed on the user terminal 40. At other times, the login screen shown in Figure 10 is displayed. This eliminates the inconvenience for the user of having to inquire about coordination requests each time they access service A, similar to the case in Figure 9.

[0099] [Variation 4] This exemplary embodiment may be modified to operate as follows for users who use the first service but not the second service. For example, the linkage system 1A may guide such users to register for the second service, and when user registration for the second service is completed, the inquiry units 112 and 214 may perform an inquiry. For example, the linkage system 1A may display the user registration screen for the second service when it receives an operation on the UI object G14 on the login screens G1 and G1B shown in Figures 8 and 9. In this case, the linkage system 1A may also display the login screen for linkage requests shown in Figures 11 and 12 when user registration is completed through an operation on the user registration screen. This has the effect of promoting the linkage between the first and second services for users who have not yet used the second service, after obtaining the user's consent for the first service provider to use their user information U2.

[0100] [Other variations] In this exemplary embodiment, the user authentication process in the first service is not limited to being performed by the first server 20, but may be performed by another authentication server. Also, the user information U1 in the first server 20 is not limited to being stored by the first server 20, but may be stored by another server. Similarly, the user authentication process in the second service is not limited to being performed by the second server 30, but may be performed by another authentication server. Also, the user information U2 in the second server 30 is not limited to being stored by the second server 30, but may be stored by another server.

[0101] Furthermore, in this exemplary embodiment, the user's authentication information may include other authentication information in place of, or in addition to, the ID and password. For example, the user's authentication information may include biometric authentication information.

[0102] Furthermore, in this exemplary embodiment, each functional block and each data included in the collaboration system 1A are not limited to the arrangement shown in Figure 3, but may be placed in any of the collaboration servers 10, the first server 20, and the second server 30.

[0103] [Examples of implementation using software] Some or all of the functions of each device constituting the collaborative systems 1 and 1A may be implemented by hardware such as integrated circuits (IC chips) or by software.

[0104] In the latter case, each device constituting the collaborative systems 1 and 1A is realized by a computer that executes instructions for a program, which is software that realizes each function. An example of such a computer (hereinafter referred to as computer C) is shown in Figure 15. Computer C comprises at least one processor C1 and at least one memory C2. The memory C2 stores a program P that causes computer C to operate as each device constituting the collaborative systems 1 and 1A. In computer C, the processor C1 reads program P from the memory C2 and executes it, thereby realizing each function of each device constituting the collaborative systems 1 and 1A.

[0105] Processor C1 can include, for example, a CPU (Central Processing Unit), GPU (Graphic Processing Unit), DSP (Digital Signal Processor), MPU (Micro Processing Unit), FPU (Floating Point Number Processing Unit), PPU (Physics Processing Unit), microcontroller, or a combination thereof. Memory C2 can include, for example, flash memory, HDD (Hard Disk Drive), SSD (Solid State Drive), or a combination thereof.

[0106] Computer C may also be equipped with RAM (Random Access Memory) for loading program P at runtime and for temporarily storing various data. Furthermore, computer C may be equipped with communication interfaces for sending and receiving data with other devices. Additionally, computer C may be equipped with input / output interfaces for connecting input / output devices such as keyboards, mice, displays, and printers.

[0107] Furthermore, program P can be recorded on a non-temporary, tangible recording medium M that is readable by computer C. Such a recording medium M could be, for example, tape, disk, card, semiconductor memory, or programmable logic circuitry. Computer C can acquire program P via such a recording medium M. Program P can also be transmitted via a transmission medium. Such a transmission medium could be, for example, a communication network or broadcast waves. Computer C can also acquire program P via such a transmission medium.

[0108] [Additional Note 1] The present invention is not limited to the embodiments described above, and various modifications are possible within the scope of the claims. For example, embodiments obtained by appropriately combining the technical means provided in the embodiments described above are also included in the technical scope of the present invention.

[0109] [Additional Note 2] Some or all of the embodiments described above may also be described as follows. However, the present invention is not limited to the embodiments described below.

[0110] (Note 1) A means for identifying a second service that can provide user information to the provider of the first service, A query means for inquiring whether a user of the first service consents to the provider of the first service using the user information of that user in the second service, triggered by the use of the first service; When information indicating the user's consent is obtained, a linking means for linking the first service and the second service by associating the user information of the first service and the user information of the second service relating to that user, A collaborative system that includes this.

[0111] (Note 2) The aforementioned specifying means is, In the candidate for the second service, the attributes of the user information that can be provided to the provider of the first service, With reference to the attributes of the user information requested by the provider of the first service, Identify the second service mentioned above. The linked system described in Appendix 1.

[0112] (Note 3) The aforementioned identification means generates linking information that links the first service and the second service, The inquiry means makes an inquiry to the user by referring to the linked information. The linked systems described in Appendix 1 or 2.

[0113] (Note 4) The provision means further includes providing the provider of the first service user information of the second service associated with the user information of the first service, The linked system described in any one of the appendices 1 to 3.

[0114] (Note 5) The aforementioned inquiry means is The first inquiry screen for performing user authentication in the first service includes information to inquire whether or not to request the linkage between the first service and the second service, If the query result for the first query screen indicates that the aforementioned linkage is requested, the second query screen for performing user authentication in the second service shall include information asking whether the user consents to the provider of the first service using the user information of the user in the second service. The linked system described in any one of the appendices 1 through 4.

[0115] (Note 6) The inquiry means further inquires about the extent to which the provider of the first service is permitted to use user information relating to the user in the second service. The linked system described in any one of the appendices 1 through 5.

[0116] (Note 7) At least one processor, Identifying a second service that can provide user information to the provider of the first service, To ask users of the first service whether they consent to the provider of the first service using their user information in the second service as a result of using the first service, A linking method that includes linking the first service and the second service by associating user information of the first service and user information of the second service relating to the user when information indicating the user's consent is obtained.

[0117] (Note 8) Computers, A means for identifying a second service that can provide user information to the provider of the first service, A query means for inquiring whether a user of the first service consents to the provider of the first service using the user information of that user in the second service, triggered by the use of the first service; When information indicating the user's consent is obtained, a linking means for linking the first service and the second service by associating the user information of the first service and the user information of the second service relating to that user, A program that makes something function as such.

[0118] (Note 9) It comprises at least one processor, the processor being, Identification process to identify a second service that can provide user information to the provider of the first service, A query process to ask users of the first and second services whether they consent to the provider of the first service using their user information in the second service in connection with the integration of the first and second services, When information indicating the user's consent is obtained, a linking process is performed to link the first service and the second service by associating the user information of the first service and the user information of the second service relating to that user. A collaborative system that performs this task. Furthermore, this collaborative system may also be equipped with memory, which may store a program that causes the processor to execute the specific processing, the query processing, and the collaborative processing. This program may also be recorded on a computer-readable, non-temporary, tangible recording medium. [Explanation of Symbols]

[0119] 1. 1A Integration System 10. Interconnected Servers 20 Server 1 30 Second Server 40 User terminals 110, 210, 310, 410 Control Unit 120, 220, 320, 420 storage section 130, 230, 330, 430 Communications Department 11, 111, 213 Specific part 12, 112, 214 Inquiry Department 13, 113 Liaison Department 114 Provision Department 211, 311 Service Provision Department 212 Request part 215 User Information Request Section 312 Registration Department 313 User Information Transmission Unit 440 Input section 450 Output section C1 Processor C2 Memory

Claims

1. A determination means for determining which second service can provide user information about the user in the second service to the provider of the first service, based on information about the user using the first service. When information is obtained from a user of the first service indicating consent for the provider of the first service to use the user information of that user in the second service, a linking means for linking the first service and the second service by associating the user information of the first service and the user information of the second service relating to that user, including, Information processing system.

2. The linking means associates information regarding user information attributes that are available to the provider of the first service, selected by the user, with the user information of the second service. The information processing system according to claim 1.

3. The user information mentioned above includes information about gender, If the user agrees to share the gender information with the provider of the first service, the linking means will associate the gender information with the provider of the first service. The aforementioned linking means shall not associate the gender information with the provider of the first service if the user does not consent to the sharing of the gender information with the provider of the first service. The information processing system according to claim 1.

4. The user information mentioned above includes information about gender, The first service outputs information about the first service to the user based on the gender information. The information processing system according to claim 1.

5. The determination means generates linking information that links the first service and the second service, The query means further includes a query means that makes a query to the user by referring to the linked information, The information processing system according to claim 1.

6. The provision means further includes providing the provider of the first service user information of the second service associated with the user information of the first service, The information processing system according to claim 1.

7. The aforementioned inquiry means is The first inquiry screen for performing user authentication in the first service includes information to inquire whether or not to request the linkage between the first service and the second service, If the query result for the first query screen indicates that the aforementioned linkage is requested, the second query screen for performing user authentication in the second service shall include information asking whether the user consents to the provider of the first service using the user information of the user in the second service. The information processing system according to claim 5.

8. A determination means for determining which second service can provide user information about the user in the second service to the provider of the first service, based on information about the user using the first service. When information is obtained from a user of the first service indicating consent for the provider of the first service to use the user information of that user in the second service, a linking means for linking the first service and the second service by associating the user information of the first service and the user information of the second service relating to that user, including, Information processing device.

9. At least one processor, Based on the information of the user using the first service, the provider of the first service determines which second service can provide user information about the said user in the second service. When information is obtained from a user of the first service indicating consent for the provider of the first service to use the user information of that user in the second service, the first service and the second service are linked by associating the user information of the first service and the user information of the second service relating to that user. Information processing methods.

10. Computers, A determination means for determining which second service can provide user information about the user in the second service to the provider of the first service, based on information about the user using the first service. When information is obtained from a user of the first service indicating consent for the provider of the first service to use the user information of that user in the second service, a linking means for linking the first service and the second service by associating the user information of the first service and the user information of the second service relating to that user, A program that makes something function as such.

Images