Data service providing method and data service providing system

Abstract

To provide a data service provision method and a data service provision system capable of more simply providing a data service.SOLUTION: A data service provision method includes a service cooperation policy setting step, a re-agreement policy setting step, a data acquisition step, a data generation step, and a data service provision step. The service cooperation policy setting step sets a service cooperation policy including information on service cooperation related use convention and information on agreement of an individual user to the use convention. The re-agreement setting step sets a re-agreement policy. The data acquisition step acquires first data from a data provision business. The data generation step generates second data to be used in a data service to be provided to a service business. The data service provision step provides the service business with the data service.SELECTED DRAWING: Figure 3

Description

[Technical Field]

[0001] FIELD Embodiments of the present invention relate to a data service providing method and a data service providing system. [Background technology]

[0002] There are service businesses that provide services that utilize data, including users' personal data. For example, there are data service businesses that provide customized information that is optimal for users using a wide variety of data, such as shopping history and health care information. In such data service businesses, it is desirable to provide data services more easily. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Publication No. 2020-13193 Summary of the Invention [Problem to be solved by the invention]

[0004] The problem to be solved by the present invention is to provide a data service providing method and a data service providing system that can provide data services more easily. [Means for solving the problem]

[0005] A data service providing method according to an embodiment includes a service collaboration policy setting step, a re-consent policy setting step, a data acquisition step, a data generation step, and a data service providing step. The service collaboration policy setting step sets a service collaboration policy including information regarding service collaboration-related terms of use and information regarding an individual user's consent to the terms of use. The re-consent policy setting step sets the re-consent policy. The data acquisition step acquires first data from the data providing business. The data generation step generates second data to be used in a data service to be provided to the service business. The data service providing step provides a data service to the service business. [Brief explanation of the drawings]

[0006] [Figure 1] FIG. 1 is a configuration diagram of a data service providing system according to a first embodiment. [Figure 2] FIG. 2 is a diagram showing a specific example of the data service providing system. [Figure 3] FIG. 2 is a functional block diagram of the data service providing system. [Figure 4] FIG. 2 is a functional block diagram of a data acquisition unit of the data service providing system. [Figure 5] FIG. 2 is a functional block diagram of a user interface unit and a cooperation control unit of the data service providing system. [Figure 6] FIG. 10 is a diagram showing an example of data providing business collaboration information. [Figure 7] FIG. 10 is a diagram showing an example of service business collaboration information. [Figure 8] FIG. 10 is a diagram showing an example of individual user association information. [Figure 9] FIG. 10 is a diagram showing an example of a service collaboration policy. [Figure 10] FIG. 10 is a diagram showing an example of a service collaboration policy. [Figure 11] Service integration confirmation screen for linked applications. [Figure 12] Service integration confirmation screen for linked applications. [Figure 13]A diagram showing the flow of re-agreeing when the terms of use are changed. [Figure 14] A pre-consultation screen for re-agreeing to changes to the terms of use. DETAILED DESCRIPTION OF THE INVENTION

[0007] Hereinafter, a data service providing method and a data service providing system according to an embodiment will be described with reference to the drawings.

[0008] (First embodiment) [Data service providing system 100] FIG. 1 is a configuration diagram of a data service providing system 100 according to the first embodiment. The data service providing system 100 is a system that provides data services to registered users (individual users U and service providers SP). "Providing data services" includes not only providing the data itself, but also providing data analysis results and various services based on the data.

[0009] The data service providing system 100 is composed of one or more servers. The basic infrastructure of the data service providing system 100 is constructed using a known data distributed processing system. The functions of the data service providing system 100 are realized by programs executed on the processors of the servers.

[0010] FIG. 2 is a diagram showing a specific example of the data service providing system 100. As shown in FIG. 2 includes servers SV1, SV2, SV3, and SV4. The servers SV1, SV2, SV3, and SV4 include hardware such as a processor such as a CPU, a memory, a recording medium such as a hard disk or a flash memory, and a communication device.

[0011] The servers SV1, SV2, SV3, and SV4 may be servers with different types of OS, software, etc. Furthermore, the servers SV1, SV2, SV3, and SV4 may be operated by different operating entities. The servers SV1, SV2, SV3, and SV4 may be installed in different countries or different regions.

[0012] All of the hardware and software resources of servers SV1 and SV2 are dedicated to the data service providing system 100. On the other hand, only some of the hardware and software resources of servers SV3 and SV4 are provided to the data service providing system 100. In other words, the data service providing system 100 may be a system that combines on-site servers such as servers SV1 and SV2 with cloud servers such as servers SV3 and SV4 that provide IaaS (Infrastructure as a Service), PaaS (Platform as a Service), or SaaS (Software as a Service). In the following description, "server" includes any of the above servers.

[0013] The functional blocks of the data service providing system 100 (such as a data acquisition unit 1, a user interface unit 2, a cooperation control unit 3, a provided data generation unit 4, and a data access control unit 5) described below are realized by the operation of servers (for example, servers SV1, SV2, SV3, and SV4 shown in FIG. 2) that are distributed and arranged via a network NW. Note that the functional blocks of the data service providing system 100 may also be realized by the operation of a single server.

[0014] 1, a data service providing system 100 is connected via a network NW to a data device 200 managed by a data provider (DP), a terminal 300 (hereinafter referred to as a personal terminal 300) such as a smartphone, tablet terminal, or personal computer owned by an individual user U, a management device 400 owned by an administrator A of the data service providing system 100, and a service providing device 500 owned by a service provider SP. The data device 200, the management device 400, and the service providing device 500 may be a system configured by one or more servers.

[0015] The network NW may be a wide area network (WAN) such as the Internet, a private network (LAN) within the building where the data service providing system 100 is installed, or a combination thereof. The network NW may be either a wired or wireless network. Communication between devices may involve other devices such as an access point.

[0016] FIG. 3 is a functional block diagram of the data service providing system 100. As shown in FIG. The data service providing system 100 includes a data acquisition unit 1, a user interface unit 2, a cooperation control unit 3, a provided data generation unit 4, and a data access control unit 5.

[0017] The data acquisition unit 1 acquires data including personal data of an individual user U from the data device 200 of a data provider DP and records it as acquired data (first data) D. The data access control unit 5 controls the system to respond to data service requests from service providers SP and the like. The provided data generation unit 4 generates provided data (second data) from the acquired data (first data) D in response to a data access request via the data access control unit 5. The user interface unit 2 provides an interface that enables the individual user U and the administrator A to communicate with the cooperation control unit 3. The cooperation control unit 3 controls service cooperation between a service business SB and a data provision business DB.

[0018] [Data Acquisition Section 1] FIG. 4 is a functional block diagram of the data acquisition unit 1. The data acquisition unit 1 acquires data including personal data of an individual user U from the data device 200 of the data provider DP and records it as acquired data (first data) D (data acquisition step). The data acquisition unit 1 also provides the acquired data D to the provided data generation unit 4. The data acquisition unit 1 has a data import interface 11 and an acquired data recording unit 12.

[0019] The data import interface 11 is an interface for acquiring data from the data device 200 of the data provider DP. The data device 200 of the data provider DP provides data, including personal data of an individual user U, acquired with the consent of the individual user U to the data service providing system 100 via the data import interface 11.

[0020] Based on a contract with the data provider DP, the data import interface 11 acquires data from the data device 200 as the data providing business DB of the data provider DP and records the data in the acquired data recording unit 12. For example, the data import interface 11 periodically acquires data in bulk from the data device 200 of the data provider DP and updates the acquired data D recorded in the acquired data recording unit 12 (bulk type). The data import interface 11 may also acquire data in real time from a device connected via an API (Application Programming Interface) (streaming type).

[0021] The acquired data recording unit 12 is a data storage that records acquired data (first data) D acquired from the data provider DP. The acquired data (first data) D may be the raw data itself acquired from the data provider DP, or may be processed data that has been processed into a standard data format or the like by a data processing unit (not shown). The processed data is, for example, statistical data, aggregated data, anonymized data, pseudonymized data, etc.

[0022] In this embodiment, the data service providing system 100 has three data acquisition units 1. In the following description, when distinguishing between the three data acquisition units 1, they will be referred to as a first data acquisition unit 1A, a second data acquisition unit 1B, and a third data acquisition unit 1C, respectively.

[0023] The data acquisition unit 1 (first data acquisition unit 1A, second data acquisition unit 1B, and third data acquisition unit 1C) acquires and records acquired data D including multiple data types. Data including multiple data types is also called a "data group."

[0024] The first data acquisition unit 1A acquires and records purchasing data D1 provided by the first data providing business DB1, for example, from a data device 200 (hereinafter also referred to as "data device 200A") managed by the data provider DP1. The purchasing data D1 is, for example, purchasing detail data on a receipt or payment data. The data import interface 11 (hereinafter also referred to as "data import interface 11A") of the first data acquisition unit 1A is an interface that can acquire the purchasing data D1 from the data provider DP1.

[0025] The second data acquisition unit 1B acquires and records HR (Human Resources) data D2 provided by the second data providing business DB2, for example, from a data device 200 (hereinafter also referred to as "data device 200B") managed by the data provider DP2. The HR data D2 includes, for example, personnel announcement data, attendance data, salary data, and training data. The data import interface 11 (hereinafter also referred to as "data import interface 11B") of the second data acquisition unit 1B is an interface that can acquire the HR data D2 from the data provider DP2.

[0026] The third data acquisition unit 1C acquires and records health data D3 provided by the third data provider DB3, for example, from a data device 200 (hereinafter also referred to as "data device 200C") managed by the data provider DP3. The health data D3 may be, for example, health checkup data or daily vital health data. The data import interface 11 (hereinafter also referred to as "data import interface 11C") of the third data acquisition unit 1C is an interface that can acquire the health data D3 from the data provider DP3.

[0027] The data import interfaces 11 (data import interface 11A, data import interface 11B, and data import interface 11C) differ depending on the type of data to be handled and the data provider. Note that the data import interface 11 may be a general-purpose interface that can be used regardless of the type of data to be handled or the data provider.

[0028] The data acquisition unit 1 (first data acquisition unit 1A, second data acquisition unit 1B, and third data acquisition unit 1C) is a distributed storage distributed across different servers, and can store acquired data D including multiple data types in a distributed manner. Note that the data acquisition unit 1 (first data acquisition unit 1A, second data acquisition unit 1B, and third data acquisition unit 1C) may be provided on the same server. The acquired data D may include personal data such as intellectual education data, physical education data, moral education data, educational attendance data, qualification acquisition data, medical checkup data, power consumption data, gas usage data, water usage data, communication statement data, schedule data, music and video viewing data, etc.

[0029] [User Interface Part 2] FIG. 5 is a functional block diagram of the user interface unit 2 and the cooperation control unit 3. The user interface unit 2 is an interface connected to the personal terminal 300 and the management device 400 owned by the administrator A of the data service providing system 100. Specifically, the user interface unit 2 includes an API that connects the personal terminal 300, the management device 400, and the cooperation control unit 3. The user interface unit 2 has a personal user interface 22 and an administrator interface 23.

[0030] The personal user interface 22 includes an API that connects the personal terminal 300 and the cooperation control unit 3. The personal user U can access the personal user interface 22 via an application running on the personal terminal 300, such as a cooperation application AP provided by the first service business SB1.

[0031] The administrator interface 23 includes an API that connects the management device 400 owned by the administrator A and the cooperation control unit 3.

[0032] [Coordination Control Unit 3] The linkage control unit 3 sets a service linkage policy P that links the individual user U, the service business SB, and the data providing business DB. The service linkage policy P is information that links the service business SB and the data providing business DB to the individual user U in order to provide data services to the individual user U, and includes member ID data linkage information C1, information regarding terms of use related to service linkage between the data providing business DB and the service business SB (hereinafter also referred to as "service linkage-related terms of use"), and information regarding the individual user U's consent to the terms of use. The service linkage-related terms of use include at least one of the terms of use (first terms of use) TD for the data providing business DB, the terms of use (second terms of use) TS for the service business SB, the comprehensive terms of use for service linkage (third terms of use) TC, and the individual terms of use for service linkage (fourth terms of use) TI. The linkage control unit 3 has a linkage information recording unit 34. Note that the individual terms of use for service linkage (fourth terms of use) TI can also be considered to constitute part of the comprehensive terms of use for service linkage (third terms of use) TC.

[0033] The association information recording unit 34 records association information of users of the data service providing system 100. The association information recording unit 34 has a business operator association information recording unit 35 and an individual user association information recording unit 36. The business operator association information recording unit 35 records data providing business association information 351 and service business association information 354. The individual user association information recording unit 36 ​​records individual user association information 360.

[0034] FIG. 6 is a diagram showing an example of the data providing business collaboration information 351. As shown in FIG. The data providing business collaboration information 351 has first linked member ID data 352, a data providing business service collaboration policy 353, and a re-consent policy 357. The data providing business collaboration information 351 is information that associates the first linked member ID data 352, the data providing business service collaboration policy 353, and the re-consent policy 357.

[0035] The first linked member ID data 352 is member ID data managed by the data provider DP, and is member ID data that identifies the individual user U in the data provided by the data provider DP. The first linked member ID data 352 includes a member ID managed by the data provider DP and member information associated with the member ID (name, address, date of birth, age, gender, email address, etc.). The data provision business linkage information 351 illustrated in FIG. 6 is information managed by the data provider DP1, and includes member ID data managed by the data provider DP1. Note that in the data provision business linkage information 351 illustrated in FIG. 6, member information other than the name (address, date of birth, age, gender, email address, etc.) is omitted from the illustration.

[0036] The member ID of the first linked member ID data 352 may not be the member ID itself managed by the data provider DP, but may be linked member ID data generated to indicate link information.

[0037] The service collaboration policy for data providing business (first policy) 353 is a service collaboration policy for the data providing business DB that includes the terms of use (first terms of use) TD specified for each data providing business DB of the data provider DP, the revision date of the terms of use TD, and the consent data of the individual user U to the terms of use TD.

[0038] The terms of use TD in the data provider business service collaboration policy 353 indicate the type of terms of use specified for each data provider business DB. The data provider business collaboration information 351 illustrated in FIG. 6 includes terms of use TD1 that specifies "non-statistical use (including provision to a third party) that identifies individuals" and terms of use TD2 that specifies "statistical use (including provision to a third party) that does not identify individuals." As shown in FIG. 6, terms of use TD for the same data provider business DB but with different content are managed as separate records. For example, if an individual user U agrees to terms of use TD2 that specifies "statistical use (including provision to a third party) that does not identify individuals" for the first data provider business DB1 and then agrees to terms of use TD1 that specifies "non-statistical use (including provision to a third party) that identifies individuals," the agreements to these terms of use are managed as separate records. Furthermore, "terms of use with different content" include terms of use with different versions. For example, if an individual user U agrees to terms of use TD1 for the first data provider business DB1 and then agrees to terms of use TD1', which is a revised version of terms of use TD1, the agreements to these terms of use are managed as separate records.

[0039] Terms of Use TD1, which specifies "non-statistical use that identifies individuals (including provision to third parties)," includes comprehensive terms of use regarding "third-party provision," for example, when data services based on data obtained from the data provider business DB are provided to a separately agreed-upon third-party provider (service business SB).

[0040] The revision date of the Terms of Use TD is the date on which the Terms of Use TD is revised. Note that the revision date may also be the planned date on which the Terms of Use TD is revised. If the revision date of the Terms of Use TD has not been decided, "NULL (undefined)" is entered as the revision date of the Terms of Use TD. If the Terms of Use TD has an expiration date and the Terms of Use are not planned to be revised before the expiration date, the expiration date is entered as the revision date of the Terms of Use TD.

[0041] The consent data (also referred to as "information regarding consent") in the data provision business service collaboration policy 353 is data indicating the individual user U's consent to the corresponding terms of use TD (whether consent was given, the date of consent, etc.). The consent data included in the data provision business collaboration information 351 illustrated in FIG. 6 indicates the date on which the individual user U agreed to the corresponding terms of use TD. "NULL" entered instead of the date in the consent data indicates that the individual user U has not agreed to the corresponding terms of use.

[0042] The re-consent policy (first re-consent policy) 357 is a policy of the individual user U that includes whether the individual user U needs to re-consent to changes to the terms of use (first terms of use) TD, and predetermined items of the terms of use TD that allow changes without the individual user U needing to re-consent (assuming the individual user U has re-consented) (hereinafter also referred to as "items that do not require re-consent"). The re-consent requirement is set to indicate, for example, either "no re-consent" or "re-consent required." When the re-consent requirement is set to "no re-consent required," items of the terms of use TD that allow changes without the individual user U needing to re-consent are set as the items that do not require re-consent. The individual user U can arbitrarily set items that do not require re-consent. For example, the individual user U selects and sets items that do not require re-consent from an item list (not shown). For example, the individual user U may set only items selected from the item list as items that do not require re-consent, such as setting an item related to "change of service name" as an item that does not require re-consent, while not setting items related to "fees" or "user obligations" in this manner. The individual user U can also set all items in the terms of use TD as items that do not require re-consent.

[0043] For example, in the case of changes to the terms of use TD due to a change in the service name of the data provider DB or a change in the company name of the data provider DP due to a company merger, etc., which are minor changes in actual content and have little impact on individual users U, it is desirable to make these items items that do not require re-consent from the perspective of convenience for individual users U.

[0044] The individual user U can confirm and / or update the re-consent policy 357 recorded in the business collaboration information recording unit 35 via the individual user interface 22. For example, the individual user U can reset the requirement for re-consent for the terms of use TD that was previously set to "no re-consent required" to "re-consent required."

[0045] FIG. 7 is a diagram showing an example of the service business collaboration information 354. As shown in FIG. The service business collaboration information 354 has second linked member ID data 355, a service collaboration policy for the service business 356, and a re-consent policy 358. The service business collaboration information 354 is information that associates the second linked member ID data 355, the service collaboration policy for the service business 356, and the re-consent policy 358.

[0046] The second linked member ID data 355 is member ID data managed by the service provider SP and is member ID data that identifies individual user U and is used by the service provider SB when reading data via the data access control unit 5. The second linked member ID data 355 includes a member ID managed by the service provider SP and member information associated with the member ID (name, address, date of birth, age, gender, email address, etc.). The service business linkage information 354 illustrated in FIG. 7 is information managed by the service provider SP1 and includes member ID data managed by the service provider SP1. Note that in the service business linkage information 354 illustrated in FIG. 7, member information other than the name (address, date of birth, age, gender, email address, etc.) is omitted from the illustration.

[0047] The member ID of the second linked member ID data 355 may not be the member ID data itself managed by the service provider SP, but may be linked member ID data generated to indicate link information.

[0048] The service collaboration policy (second policy) 356 for a service business is a service collaboration policy for an SB for a service business that includes terms of use (second terms of use) TS specified for each service business SB of the service provider SP, the revision date of the terms of use TS, and the consent data of an individual user U to the terms of use TS.

[0049] The terms of use TS in the service collaboration policy 356 for the service provider indicate the type of terms of use defined for each service provider SB. The service business collaboration information 354 illustrated in FIG. 7 includes terms of use TS1 for a first service provider SB1 provided by the service provider SP1 and terms of use TS2 for a second service provider SB2. As illustrated in FIG. 7, terms of use TS for the same service provider SB but with different content are managed as separate records. For example, if an individual user U agrees to terms of use TS1, which defines the basic usage of the first service provider SB1, and then agrees to terms of use TS4, which defines additional optional usage, the agreements to these terms of use are managed as separate records. Furthermore, "terms of use with different content" include terms of use with different versions. For example, if an individual user U agrees to terms of use TS1 for a first service provider SB1 and then agrees to terms of use TS1', which is a revised version of terms of use TS1, the agreements to these terms of use are managed as separate records.

[0050] The consent data (also referred to as "consent information") in the service business service collaboration policy 356 is data indicating the individual user U's consent to the corresponding terms of use TS (such as whether consent was granted, the date of consent, etc.). The consent data included in the service business collaboration information 354 illustrated in FIG. 7 indicates the date on which the individual user U agreed to the corresponding terms of use TS. "NULL" entered instead of a date in the consent data indicates that the individual user U has not agreed to the corresponding terms of use. For example, if the terms of use of the service business SB are updated during a period in which the individual user U is not using the service business SB, it is unclear whether the individual user U has agreed to the new terms of use, and therefore the consent data for the individual user U is set to "NULL." Furthermore, if it is unclear for other reasons whether the individual user U has agreed to the terms of use, the consent data for the individual user U is set to "NULL."

[0051] The re-consent policy (second re-consent policy) 358 is a policy of the individual user U that includes whether the individual user U needs to re-consent to changes to the terms of use (second terms of use) TS, and predetermined items (items that do not require re-consent) of the terms of use TS that allow changes without the individual user U needing to re-consent (assuming the individual user U has re-consented). The re-consent requirement is set to indicate, for example, either "no re-consent" or "re-consent required." When the re-consent requirement is set to "no re-consent required," the items of the terms of use TS that allow changes without the individual user U needing to re-consent are set as the items that do not require re-consent. The individual user U can arbitrarily set the items that do not require re-consent. For example, the individual user U selects and sets the items that do not require re-consent from a list of items not shown. Note that the individual user U can also set all items of the terms of use TS as items that do not require re-consent.

[0052] For example, in the case of changes to the terms of use TS due to a change in the service name of a service business SB or a change in the company name of a service provider SP due to a corporate merger, etc., which are minor changes in actual content and have little impact on individual users U, it is desirable to make these items items that do not require re-consent from the perspective of convenience for individual users U.

[0053] The individual user U can confirm and / or update the re-consent policy 358 recorded in the business collaboration information recording unit 35 via the individual user interface 22. For example, the individual user U can reset the requirement for re-consent for the terms of use TS that has been set to "no re-consent required" to "re-consent required."

[0054] FIG. 8 is a diagram showing an example of the individual user association information 360. As shown in FIG. The individual user association information recording unit 36 ​​records individual user association information 360. The individual user association information 360 includes member ID data 361 of a registered individual user U who uses the data service providing system 100, a service association policy 362 for the data service providing system, and a re-consent policy 363.

[0055] Member ID data 361 is member ID data managed by data service providing system 100. Member ID data 361 includes member IDs managed by data service providing system 100 and member information associated with the member ID (name, address, date of birth, age, gender, email address, etc.). Note that in the individual user association information 360 illustrated in Fig. 8, member information other than name (address, date of birth, age, gender, email address, etc.) is omitted from the illustration.

[0056] The service collaboration policy (third policy) 362 for the data service providing system is a service collaboration policy for the data service providing system 100 that includes comprehensive terms of use (third terms of use) TC that govern the use of the data service providing system 100 by individual user U, the revision date of the comprehensive terms of use TC, and the consent data of individual user U to the comprehensive terms of use TC.

[0057] The comprehensive terms of use (third terms of use) TC include comprehensive terms of use for service collaboration between the data providing business DB and the service business SB. The comprehensive terms of use for service collaboration stipulate basic matters that apply when an individual user U uses the service collaboration between the data providing business DB and the service business SB via the data service providing system 100, such as terms of handling personal information and privacy in the service collaboration.

[0058] The consent data (also referred to as "information regarding consent") of the service collaboration policy 362 for the data service providing system is data indicating the consent of the individual user U to the corresponding terms of use TC (whether consent was granted, the date of consent, etc.). The consent data included in the service collaboration policy 362 for the data service providing system illustrated in Figure 8 indicates the date on which the corresponding terms of use TC was agreed to.

[0059] The re-consent policy (third re-consent policy) 363 is a policy of the individual user U that includes whether the individual user U needs to re-consent to changes to the comprehensive terms of use (third terms of use) TC, and predetermined items (items that do not require re-consent) of the comprehensive terms of use TC that allow changes without the individual user U needing to re-consent (assuming the individual user U has re-consented). Whether re-consent is required is set to indicate, for example, either "no re-consent" or "re-consent required." When the "whether re-consent is required" is set, the items of the comprehensive terms of use TC that allow changes without the individual user U needing to re-consent are set as the items that do not require re-consent. The individual user U can arbitrarily set the items that do not require re-consent. For example, the individual user U selects and sets the items that do not require re-consent from a list of items not shown. Note that the individual user U can also set all items of the terms of use TC as items that do not require re-consent.

[0060] The administrator A can update the data recorded in the individual user association information recording unit 36 ​​via the administrator interface 23 .

[0061] The individual user U can confirm and / or update the re-consent policy 363 recorded in the business collaboration information recording unit 35 via the individual user interface 22. For example, the individual user U can reset the requirement for re-consent for the comprehensive terms of use TC, which has been set as "no re-consent required," to "re-consent required."

[0062] 9 and 10 are diagrams showing an example of the service collaboration policy P. FIG. The service linkage policy P has member ID data linkage information C1, a service linkage policy for data providing business 353, a service linkage policy for service business 356, an individual service linkage policy C2, and a re-consent policy C3.

[0063] The individual collaboration policy (fourth policy) C2 is a service collaboration policy for the data service providing system 100 that includes individual terms of use (fourth terms of use) TI that stipulate the individual service collaboration between the data providing business DB and the service business SB, the revision date of the individual terms of use TI, and the consent data of the individual user U to the individual terms of use TI.

[0064] The Individual Terms of Use (Fourth Terms of Use) TI are terms of use that stipulate the specific use in service collaboration between a specific data providing business DB and a specific service business SB. The Individual Terms of Use (Fourth Terms of Use) TI includes terms of use regarding "collection," in which the data service providing system 100 collects data from a specific data providing business DB. The Individual Terms of Use (Fourth Terms of Use) TI also includes terms of use regarding "third-party provision," in which the data service providing system 100 provides a data service based on data collected from a specific data providing business DB, with the third-party provider being a specific service business SB.

[0065] The individual terms of use TI1 illustrated in Figure 10 include terms of use regarding "collection," in which the data service providing system 100 collects data from the data providing business DB1, and terms of use regarding "third-party provision," in which the data service providing system 100 provides a data service based on data collected from the data providing business DB1, with the third-party recipient being the service business SB1.

[0066] The individual terms of use TI2 illustrated in Figure 10 include terms of use regarding "collection," in which the data service providing system 100 collects data from the data providing business DB1, and terms of use regarding "third-party provision," in which the data service providing system 100 provides a data service based on data collected from the data providing business DB1, with the third-party recipient being the service business SB2.

[0067] In addition, the terms of use regarding "collection" and "provision to third parties" in the Individual Terms of Use (Fourth Terms of Use) TI may be included in the Data Provider Business DB Terms of Use (First Terms of Use) TD or the Service Business SB Terms of Use (Second Terms of Use) TS. In such cases, the Individual Terms of Use (Fourth Terms of Use) TI does not need to include overlapping portions. Also, if the terms of use regarding "collection" and "provision to third parties" in the Individual Terms of Use (Fourth Terms of Use) TI are all included in the Data Provider Business DB Terms of Use (First Terms of Use) TD or the Service Business SB Terms of Use (Second Terms of Use) TS, the Individual Terms of Use (Fourth Terms of Use) TI is not necessary.

[0068] The consent data (also referred to as "information about consent") of the individual service cooperation policy C2 is data indicating the consent of the individual user U to the corresponding terms of use TI (whether consent was given, the date of consent, etc.). The consent data included in the individual service cooperation policy C2 illustrated in FIGS. 9 and 10 indicates the date of consent to the corresponding terms of use TI.

[0069] The re-consent policy (fourth re-consent policy) C3 is a policy of the individual user U that includes whether the individual user U needs to re-consent to a change to the individual terms of use (fourth terms of use) TI, and predetermined items (items that do not require re-consent) of the individual terms of use TI that allow changes without the individual user U needing to re-consent (assuming the individual user U has re-consented). Whether re-consent is required is set to indicate, for example, either "no re-consent" or "re-consent required." When the "whether re-consent is required" is set, the items in the individual terms of use TI that allow changes without the individual user U needing to re-consent are set as the items that do not require re-consent. The individual user U can arbitrarily set the items that do not require re-consent. For example, the individual user U selects and sets the items that do not require re-consent from a list of items not shown. Note that the individual user U can also set all items in the individual terms of use TI as items that do not require re-consent.

[0070] The collaboration control unit 3 generates member ID data collaboration information C1 that associates first linked member ID data 352 and second linked member ID data 355 with member ID data 361. The collaboration control unit 3 also generates a "service collaboration policy P" that associates data providing business service collaboration policy 353, service business service collaboration policy 356, individual service collaboration policy C2, and re-consent policy C3 with member ID data collaboration information C1. This enables individual user U, service business SB, and data providing business DB to collaborate with each other in the data service provided by data service providing system 100.

[0071] 9 and 10 is generated when data provided by the data providing business DB1, the use of which is regulated by the terms of use TD1 of the data providing business DB1, is linked to the service businesses SB (first service business SB1, second service business SB2). The service linkage policy P is generated or updated, for example, when at least some of the data constituting the service linkage policy P (member ID data 361, first linked member ID data 352, data providing business service linkage policy 353, second linked member ID data 355, service business service linkage policy 356, individual service linkage policy C2, and re-consent policy C3) is updated. For example, when an individual user U who has agreed to the terms of use TD1 of the data providing business DB1 agrees to the terms of use TS1 of the first service business SB1 and the service business service linkage policy 356 is updated, the service linkage policy P is updated. In the service collaboration policy P illustrated in FIGS. 9 and 10, member information other than the name (address, date of birth, age, sex, email address, etc.) is omitted from the illustration.

[0072] [Provided Data Generation Unit 4] The provided data generation unit 4 generates provided data (second data) from acquired data (first data) D in response to a data access request from a registered user (individual user U and service provider SP) via the data access control unit 5. The data that the registered user (individual user U and service provider SP) can read via the data access control unit 5 is not the acquired data D recorded in the acquired data recording unit 12, but the provided data (second data).

[0073] The provided data generation unit 4 acquires, from the data acquisition unit 1, acquisition data D required for responding to a data access request from the data access control unit 5, based on the service collaboration policy P generated by the collaboration control unit 3.

[0074] Specifically, the provided data generation unit 4 generates provided data (second data) from the acquired data (first data) D based on the data provision business service collaboration policy 353 (see FIGS. 9 and 10) included in the service collaboration policy P. When the acquired data (first data) D used by the service business SB includes data provided by an individual user U, the provided data generation unit 4 generates provided data (second data) using data items permitted for use based on the terms of use of the data provision business DB to which the individual user U agreed.

[0075] For example, suppose that an individual user U who provided data to a first data providing business DB1, which is an electronic receipt business, agrees to terms of use TD1 that stipulate "non-statistical use (including provision to a third party) that identifies individuals." In this case, when the acquired data (first data) D used by the service business SB includes data provided by the individual user U, the provided data generation unit 4 can generate provided data (second data) that includes data items related to the purchasing data D1 of the individual user U (such as the name of the food purchased and the date and time of food purchase) and data items that identify the individual user U (such as name).

[0076] For example, suppose that an individual user U who provided data to a first data providing business DB1, which is an electronic receipt business, agrees to terms of use TD2 that stipulate "statistical use without identifying individuals (including provision to a third party)." In this case, when the acquired data (first data) D used by the service business SB includes data provided by the individual user U, the provided data generation unit 4 can generate provided data (second data) that includes data items related to the purchasing data D1 of the individual user U (such as the name of the food purchased and the date and time of food purchase) but does not include data items that identify the individual user U (such as name). Furthermore, the data access control unit 5 is only permitted to use the generated provided data (second data) if the data access request from the data access control unit 5 is for statistical use.

[0077] [Data Access Control Unit 5] The data access control unit 5 responds to data service requests from registered users (individual users U and service providers SP). After receiving a data service request, the data access control unit 5 issues a data access request to the provided data generation unit 4 to access the provided data (second data) required to provide the requested data service. The data access control unit 5 provides a data service to the data service requester based on the provided data (second data) acquired from the provided data generation unit 4. Providing a data service includes not only providing the data itself, but also providing data analysis results and various services based on the data. Methods of providing a data service include allowing the user to access the provided data generated in the data service providing system 100, and sending the generated provided data to the user via a predetermined network.

[0078] [Operation of the data service providing system 100] Next, the operation of the data service providing system 100 when an individual user U uses the data service providing system 100 will be described.

[0079] Here, it is assumed that individual user U is a user of the first data providing business DB1 and a user of the first service business SB1. By linking the first data providing business DB1 and the first service business SB1, individual user U can also use data services that use data that he or she has provided to the first data providing business DB1 (for example, an electronic receipt business) within the scope of the terms of use that he or she has agreed to in the services provided by the first service business SB1 (for example, a recipe suggestion business).

[0080] For example, an integrated application AP provided by a first service business SB1 (e.g., a recipe suggestion business) can suggest optimal recipes to an individual user U based on the purchasing data D1 of the individual user U obtained from a first data provision business DB1 (e.g., an electronic receipt business).

[0081] <Service collaboration> In order to receive the above data service, the individual user U transmits a service link between the first data providing business DB1 and the first service business SB1 to the data service providing system 100 via the link application AP (a service link request). If necessary, the individual user U transmits information (such as a member ID) indicating that he or she is a member who uses the first data providing business DB1 to the data service providing system 100.

[0082] The collaboration control unit 3 updates the data collaboration policy P (see FIGS. 9 and 10) in the business collaboration information recording unit 35 based on a service collaboration request from the individual user U. Specifically, the member ID data collaboration information C1 is updated, and the data providing business service collaboration policy 353, the service business service collaboration policy 356, the individual service collaboration policy C2, and the re-consent policy C3 related to the individual user U are associated with the updated member ID data collaboration information C1. As a result, the individual user U can use the data service of the first service business SB1 that uses the data that the individual user U has provided to the first data providing business DB1.

[0083] 11 and 12 show the service collaboration confirmation screen WA of the collaboration application AP. The collaboration application AP may be a native application running on the personal terminal 300, or a Web application running on the data service providing system 100. When the collaboration application AP is a native application, the service collaboration confirmation screen WA is generated and controlled by the personal terminal 300 based on communication with the collaboration control unit 3 via the personal user interface 22. When the collaboration application AP is a Web application, the service collaboration confirmation screen WA is generated and controlled by the collaboration control unit 3 based on communication with the personal terminal 300 via the personal user interface 22.

[0084] The service collaboration confirmation screen WA is a screen for confirming the individual user U's consent to the service collaboration between the first data providing business DB1 and the first service business SB1. From the top to the bottom of the screen, the service collaboration confirmation screen WA has a collaborative service confirmation area W1, a message area W2, a consent confirmation area W3, a collaborative data confirmation area W4, and a data handling confirmation area W5.

[0085] The linked service confirmation area W1 clearly displays the two linked services using icons W11 and W12. The linked service confirmation area W1 also displays a data provision direction W13 that clearly indicates the direction in which data is provided in the two linked services. The icon W11 is an icon representing the first data providing business DB1, such as an icon of an application provided by the first data providing business DB1 or a brand logo related to the first data providing business DB1. The icon W12 is an icon representing the first service business SB1, such as an icon of an application provided by the first service business SB1 or a brand logo related to the first service business SB1.

[0086] The message area W2 displays a message or the like prompting consent from the individual user U. The message area W2 may also display information specific to each individual user U.

[0087] The consent confirmation area W3 presents the terms of use for service collaboration to the individual user U, and confirms their agreement to the terms of use and their intention to start service collaboration. The consent confirmation area W3 includes a message W31 displaying the terms of use, an agreement check button W32, a start collaboration button W33, a message W34 displaying information about whether re-consent is required, and a re-consent required check button W35. The message W31 displaying the terms of use is at least a portion of the individual terms of use (fourth terms of use) TI and may include at least a portion of the terms of use (first terms of use) TD, terms of use (second terms of use) TS, and comprehensive terms of use (third terms of use) TC. The agreement check button W32 is a radio button indicating that the individual user U agrees to the terms of use displayed in the message W31. The start collaboration button W33 is a button for confirming that the individual user U intends to start service collaboration.

[0088] The message W34, which displays information regarding the absence of re-consent, displays predetermined items (items that do not require re-consent) of the terms of use that are permitted to be changed without the individual user U's re-consent (assuming the individual user U has re-agreed) in at least one of the terms of use TD1 for the first data provider business DB1, the terms of use TS1 for the first service business SB1, the comprehensive terms of use TC, and the individual terms of use TI1 (at least one of the terms of use related to service collaboration). The re-consent check button W35 is a radio button that indicates whether the individual user U needs to re-consent to the items that do not require re-consent in the terms of use displayed in the message W34. Note that the information regarding the absence of re-consent described in the message W34 may be included in the terms of use described in the message W31. In that case, the message W34 and the re-consent check button W35 are unnecessary. The re-consent check button W35 may also be a button that allows the user to select one or more items from different types of items that do not require re-consent or a combination thereof.

[0089] The linked data confirmation area W4 clearly displays the data that will actually be linked. The linked data confirmation area W4 may also display, for example, an example of the data that will actually be linked.

[0090] The data handling confirmation area W5 displays how the linked data will be handled. The data handling confirmation area W5 has a message W51 explaining how data will be handled, a data provision business terms of use confirmation button W52, and a service business terms of use confirmation button W53. The data provision business terms of use confirmation button W52 is a button that opens a screen where the terms of use TD (e.g., terms of use TD1) of the first data provision business DB1 can be confirmed. The service business terms of use confirmation button W53 is a button that opens a screen where the terms of use TS (e.g., terms of use TS1) of the first service business SB1 can be confirmed. The individual user U can easily access the terms of use of the two linked services.

[0091] When the individual user U indicates his / her agreement to the terms of use by pressing the agreement check button W32 and then presses the cooperation start button W33, the cooperation application AP requests the cooperation control unit 3 to start service cooperation.

[0092] When the start collaboration button W33 is pressed and the re-agreement necessity check button W35 is checked to indicate that re-agreement is not required, the collaboration control unit 3 sets the re-agreement policy (re-agreement policy 357, re-agreement policy 358, re-agreement policy 363, re-agreement policy 36C) corresponding to the terms of use that include the re-agreement not required item to indicate "re-agreement not required." Also, when the start collaboration button W33 is pressed and the re-agreement necessity check button W35 is not checked to indicate that re-agreement is not required, the collaboration control unit 3 sets the corresponding re-agreement policy to indicate "re-agreement required."

[0093] <Re-agreement due to changes in the Terms of Use> FIG. 13 is a diagram showing the flow of re-agreement following changes (revisions, revisions) to the terms of use. If the revision date for any of the terms of use related to service collaboration between the data providing business and the service business (service collaboration related terms of use) is approaching and the terms of use need to be updated, the collaboration control unit 3 executes step S0.

[0094] In step S0, the collaboration control unit 3 confirms whether re-consent from the individual user U is required for the changed terms of use, regardless of the setting of the individual user U's corresponding re-consent policy. For example, if the change to the terms of use is a substantial change in content, a change to an item that has a significant impact on the individual user U, or a change that requires the individual user U's consent again based on laws and regulations, the collaboration control unit 3 determines that re-consent from the individual user U is required, regardless of the setting of the individual user U's corresponding re-consent policy. If it is determined that re-consent from the individual user U is required, regardless of the setting of the re-consent policy, the collaboration control unit 3 executes step S4. Otherwise, the collaboration control unit 3 executes step S1.

[0095] There are various ways that the cooperation control unit 3 can determine that re-consent from the individual user U is necessary, regardless of the setting of the re-consent policy. For example, if the administrator A determines that it is absolutely (forcibly) necessary to request re-consent from the individual user U depending on the changes to the terms of use, the cooperation control unit 3 acquires information indicating that re-consent is necessary for the revision of the terms of use via the administrator interface 23, in response to a request from the management device 400. The cooperation control unit 3 may determine that re-consent is necessary based on the presence or absence of the information indicating that re-consent is necessary.

[0096] In step S1, the collaboration control unit 3 checks whether the individual user U "needs re-agreement" for the changed terms of use by referring to the re-agreement policy (re-agreement policy 357, re-agreement policy 358, re-agreement policy 363, re-agreement policy 36C) corresponding to the changed terms of use. If the individual user U's re-agreement requirement for the changed terms of use is set to "no re-agreement required," the collaboration control unit 3 executes step S2. If the individual user U's re-agreement requirement for the changed terms of use is set to "re-agreement required," the collaboration control unit 3 executes step S4 without automatically updating the consent data.

[0097] In step S2, the cooperation control unit 3 checks whether the change items in the terms of use to be changed correspond to items that do not require re-consent. If the change items correspond to items that do not require re-consent, the cooperation control unit 3 executes step S3. If the change items do not correspond to items that do not require re-consent, the cooperation control unit 3 executes step S4 without automatically updating the consent data.

[0098] For example, the cooperation control unit 3 recognizes the outline of the changed item through natural language processing such as morphological analysis and lexical analysis, and checks whether the changed item corresponds to an item for which re-consent is not required.

[0099] For example, the cooperation control unit 3 has dictionary data containing keywords for each item that does not require re-consent. For example, for the "purpose of use" item that does not require re-consent, the cooperation control unit 3 prepares in advance dictionary data containing keywords that encompass variations in expression, such as "scope of data utilization," "purpose of use of data," and "destination of application of data." The cooperation control unit 3 matches the changed item with keywords related to items that do not require re-consent, and determines that the changed item corresponds to an item that does not require re-consent.

[0100] For example, the cooperation control unit 3 may use keywords for each item that does not require re-consent, which have been generated in advance by machine learning, as dictionary data. By using the dictionary data generated by machine learning, the cooperation control unit 3 can determine that, for example, a more complex change item corresponds to an item that does not require re-consent.

[0101] For example, the cooperation control unit 3 may use a trained model that has previously machine-learned the relationship between the changed items and items that do not require re-consent, to check whether the changed items correspond to items that do not require re-consent.

[0102] The method by which the cooperation control unit 3 determines that the change item corresponds to an item that does not require re-consent can also be applied to determining whether re-consent from the individual user U is required in step 0.

[0103] In step S3, when the revision date of the changed Terms of Use arrives (or before the revision date), the collaboration control unit 3 updates the consent data of the service collaboration policies (data provision business service collaboration policy 353, service business service collaboration policy 356, data service provision system service collaboration policy 362, individual service collaboration policy C2) corresponding to the changed Terms of Use without requiring the individual user U to consent again (by assuming that the individual user U has agreed to the changed Terms of Use without acquiring any further consent information). For example, the collaboration control unit 3 updates the "date of consent" included in the consent data. Alternatively, the collaboration control unit 3 may separately save the previous consent date and then add a new consent date. Furthermore, the collaboration control unit 3 may distinguish the pre-change Terms of Use and the changed Terms of Use as separate terms and add the consent data for the changed Terms of Use as new records.

[0104] When the terms of use are changed to include a change in an item that has little impact on the individual user U, such as a change in the service name, the individual user U can avoid the trouble and time of having to re-agree each time.

[0105] When the individual user U himself / herself links the data that he / she has provided to the first data providing business DB1 with the first service business SB1 via the data service providing system 100, it is desirable to further include "purpose of use of data" as an item for which re-consent is not required. Even if the purpose of use of the data in the terms of use is changed, it is the individual user U who provided the data who will be using it, so if the individual user U has agreed in advance, the individual user U may be omitted from re-consenting to changes to the terms of use that accompany the change in the purpose of use of the data. By not requiring the individual user U to re-consent, the effort and time required for the individual user U to re-consent can be saved.

[0106] In step S4, the collaboration control unit 3 executes a preliminary inquiry for re-agreement to changes to the terms of use. By inquiring of the individual user U about re-agreement to changes to the terms of use in advance on each revision date, the individual user U can smoothly update the terms of use with ample time. The collaboration control unit 3 executes a preliminary inquiry for re-agreement before the revision date of the terms of use by referencing the re-agreement policy (re-agreement policy 357, re-agreement policy 358, re-agreement policy 363, re-agreement policy 36C) corresponding to the terms of use to be changed. It is preferable that the preliminary inquiry for re-agreement be executed at least seven days or more before the revision date, for example.

[0107] FIG. 14 shows a pre-inquiry screen WB for re-agreeing to changes in the terms of use. The pre-inquiry screen WB is a screen of the collaboration application AP that confirms in advance with the individual user U whether they wish to re-agree to changes to the service collaboration-related terms of use. The pre-inquiry screen WB has, from the top to the bottom of the screen, a re-consent request area W6 and a re-consent confirmation area W7.

[0108] The consent re-request area W6 displays a message W61, an alert message W62, etc., prompting the individual user U to re-agree. The consent re-request area W6 may also display information specific to each individual user U. The alert message W62 is a message informing the individual user U that service integration will be terminated if the individual user U does not re-agree to the changed terms of use. The alert message W62 motivates the individual user U to re-agree to the changes to the terms of use before the date of revision of the terms of use, and the individual user U can prevent service integration from being terminated even temporarily after the date of revision. Note that depending on the content of the changes to the terms of use, service integration may not be terminated. In this case, the consent re-request area W6 does not need to display the alert message W62.

[0109] The re-agreement confirmation area W7 presents the updated terms of use to the individual user U, and confirms re-agreement to the terms of use and continued use of the service collaboration. The re-agreement confirmation area W7 has a changes display W71 that displays changes to the terms of use, a terms of use confirmation link W72, a re-agreement check button W73, and a continue use button W74.

[0110] The changes display W71 displays changes to the terms of use. The changes may be content created by an administrator of the terms of use (such as the data provider DP or the administrator of the data service providing system 100), or may be content indicating differences extracted by the cooperation control unit 3 by comparing the terms of use before and after the change. Furthermore, it is preferable that the changes display W71 does not list all of the changes, but rather displays the main changes in bullet points or the like.

[0111] The Terms of Use Confirmation Link W72 is a link that opens a screen where the changed Terms of Use can be confirmed. The individual user U can easily access the full text of the changed Terms of Use. The Re-Agree Check Button W73 is a radio button that indicates that the individual user U re-agreed to the changed Terms of Use. The Continue Use Button W74 is a button that confirms that the individual user U will continue to use the service collaboration.

[0112] When the individual user U indicates that he / she re-agreed to the changed terms of use by pressing the re-agreement check button W73 and then presses the continue use button W74, the collaboration application AP requests the collaboration control unit 3 to continue using the service collaboration. Based on the input of the re-agreement check button W73, the collaboration control unit 3 updates the consent data of the corresponding service collaboration policy (service collaboration policy for data provision business 353, service collaboration policy for service business 356, service collaboration policy for data service provision system 362, individual service collaboration policy C2).

[0113] According to the embodiment described above, the data service providing system 100 not only seamlessly provides data services to the service business SB using data obtained from the data providing business DP, but also collectively manages the terms of use for both the data providing business DB and the service business SB and the individual user U's consent to the terms of use as a service collaboration policy P, making it possible to easily provide data services that strictly apply the terms of use and consent to the terms of use.

[0114] Furthermore, according to the embodiment described above, when there is a change in an item that has little impact on an individual user U, such as a change in the service name, in the terms of use related to the service collaboration between the data providing business DB and the service business SB (service collaboration related terms of use), it is possible to avoid the effort and time required to re-consent each time.

[0115] In the above embodiment, the service collaboration-related terms of use (data provision business DB terms of use (first terms of use) TD, service business SB terms of use (second terms of use) TS, service collaboration comprehensive terms of use (third terms of use) TC, and service collaboration individual terms of use (fourth terms of use) TI) each have a corresponding re-agreement policy. However, the form of the re-agreement policy for the service collaboration-related terms of use is not limited to this. At least one of the service collaboration-related terms of use may have a corresponding re-agreement policy.

[0116] The programs in the above-described embodiments may be recorded on a computer-readable recording medium, and then loaded and executed by a computer system. The term "computer system" as used herein includes hardware such as an OS and peripheral devices. The term "computer-readable recording medium" refers to portable media such as flexible disks, optical magnetic disks, ROMs, and CD-ROMs, as well as storage devices such as hard disks built into a computer system. The term "computer-readable recording medium" may also include media that dynamically store programs for a short period of time, such as communication lines used when transmitting programs via networks such as the Internet or telephone lines, or media that store programs for a fixed period of time, such as volatile memory within a computer system serving as a server or client. The program may also be designed to implement some of the functions described above, or may be capable of implementing the functions described above in combination with a program already stored in the computer system.

[0117] Although several embodiments of the present invention have been described, these embodiments are presented as examples and are not intended to limit the scope of the invention. These embodiments can be implemented in various other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. These embodiments and their modifications are included within the scope and spirit of the invention, as well as within the scope of the invention described in the claims and their equivalents. [Explanation of symbols]

[0118] 100...data service providing system, 1...data acquisition unit, 2...user interface unit, 3...linkage control unit, 4...provided data generation unit, 5...data access control unit, 361...member ID data, 352...first linked member ID data, 353...service linkage policy for data providing business, 355...second linked member ID data, 356...service linkage policy for service business, DP...data provider, DB...data providing business, SP...service provider, SB...service business, TD...terms of use for data providing business (first terms of use), TS...terms of use for service business (second terms of use), TC...comprehensive terms of use (third terms of use), TI...individual terms of use (fourth terms of use)

Claims

1. a service collaboration policy setting step of setting a service collaboration policy including information regarding terms of use related to service collaboration between the data providing business and the service business and information regarding individual users' consent to the terms of use; a re-consent policy setting step of setting a re-consent policy including information on whether the individual user needs to re-consent to the change in the terms of use; a data acquisition step of acquiring first data including data of the individual user from the data providing business based on the service collaboration policy; a data generation step of generating second data to be used for a data service provided to a service business from the first data based on the service collaboration policy; a data service providing step of providing a data service to the service business based on the second data; Equipped with Data service delivery method.

2. and a service collaboration policy update step of updating the service collaboration policy without acquiring information regarding further consent from the individual user when the terms of use are changed and the re-consent policy indicates that re-consent is not required. The data service providing method according to claim 1 .

3. When the terms of use are changed and the re-consent policy indicates the need for re-consent, a re-consent acquisition step is further provided for acquiring re-consent from the individual user to the changed terms of use.

3. The data service providing method according to claim 1.

4. The step of obtaining consent again is performed before the revision date of the changed terms of use. The data service providing method according to claim 3 .

5. 5. The data service providing method according to claim 3, wherein the step of obtaining consent again includes presenting a message to the effect that the service collaboration will be terminated if consent is not obtained again.

6. The method further includes a forced re-consent acquisition step of acquiring re-consent from the individual user regardless of the re-consent policy. The data service providing method according to any one of claims 1 to 5.

7. The necessity of the individual user's re-consent is set for a predetermined item of the terms of use. The data service providing method according to any one of claims 1 to 6.

8. The terms of use related to the service collaboration include the terms of use for the data provision business, The data service providing method according to any one of claims 1 to 7.

9. The terms of use related to the service collaboration include terms of use for service collaboration between a specific data providing business and a specific service business; The data service providing method according to any one of claims 1 to 7.

10. a service linking step of permitting the individual user to link the data providing business for the individual user with the service business for the individual user; The data service providing method according to any one of claims 1 to 9.

11. the service collaboration step includes presenting terms of use regarding the collaboration; The data service providing method according to claim 10.

12. the service linking step includes confirming with the individual user whether or not re-agreement is required to a change in a predetermined item of the terms of use; 12. The data service providing method according to claim 10 or 11.

13. a collaboration control unit that acquires a service collaboration policy including information regarding terms of use related to service collaboration between a data providing business and a service business and information regarding individual users' consent to said terms of use, and sets a re-consent policy including information regarding whether or not the individual users need to re-consent to changes to said terms of use; a data acquisition unit that acquires first data including data of the individual user from a device used in the data providing business based on the service collaboration policy; a provision data generation unit that generates second data to be used for a data service to be provided to a service business from the first data based on the service linkage policy; a data access control unit that provides a data service to a device used in the service business based on the second data; Equipped with Data service provision system.

14. the collaboration control unit, when the terms of use are changed and the re-consent policy indicates that re-consent is not required, updates the service collaboration policy without acquiring information regarding further consent from the individual user; The data service providing system according to claim 13.

15. the cooperation control unit, when the terms of use are changed and the re-consent policy indicates the need for re-consent, obtains re-consent from the individual user for the changed terms of use; 15. A data service providing system according to claim 13 or 14.

16. the cooperation control unit obtains the re-consent of the individual user before the revision date of the terms of use to be changed; 16. The data service providing system according to claim 15.

17. the cooperation control unit, when obtaining re-consent from the individual user and re-consent is not obtained, presents a message to the effect that the service cooperation will be terminated; 17. A data service providing system according to claim 15 or 16.

18. the cooperation control unit obtains the re-consent of the individual user regardless of the re-consent policy; 18. A data service providing system according to any one of claims 13 to 17.

19. The necessity of the individual user's re-consent is set for a predetermined item of the terms of use.

19. A data service providing system according to any one of claims 13 to 18.

20. The terms of use related to the service collaboration include terms of use for service collaboration between a specific data providing business and a specific service business; 20. A data service providing system according to any one of claims 13 to 19.

Images