System and method

Abstract

To provide a system that enables a service provider or the like to obtain behavioral data with environmental data attached.SOLUTION: The system includes a distribution control server that controls the sharing of personal data including user behavioral data. A first service server sends the behavioral data to the distribution control server so that the behavioral data becomes a target for data sharing. The distribution control server stores the received behavioral data and sends acquisition environmental data requirements, which define the environmental data to be acquired, to a second service server. The second service server extracts environmental data that meets the acquisition environmental data requirements from among multiple pieces of environmental data and sends the extracted environmental data to the distribution control server. The distribution control server stores the accumulated behavioral data and the received environmental data in association with each other.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] The present invention relates to a system and a method.

Background Art

[0002] There are systems for linking information held by multiple organizations.

[0003] For example, Patent Document 1 describes providing a cooperation infrastructure system, an information cooperation method, and an information cooperation bridge device that enable cooperation of information managed by multiple organizations. The system of Patent Document 1 is an information cooperation infrastructure system for enabling multiple organizations that respectively manage customer information including a plurality of item information regarding customers to cooperate with each other. In this system, an information cooperation bridge manages association information that associates the organizations with respect to a customer and the item information for which the information cooperation bridge causes at least one item information to be cooperated between at least two organizations. When the item information of a customer is updated in any of the organizations, the information cooperation bridge records data update information indicating the organization, the customer, and the item information. The information cooperation server notifies, based on the data update information, the organizations associated with the organization in which the item information of the customer is updated in the association information that the item information of the customer has been updated.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] As disclosed in Patent Document 1, cooperation of information managed by a plurality of organizations is required. Here, in order to provide a service suitable for customers, operators (connected operators, service providers) connected to the data cooperation infrastructure often need not only the action data of the customers but also the environmental data related to the customers' actions.

[0006] However, at present, in the data cooperation infrastructure, from the viewpoint of privacy protection, the acquisition entities (management entities) of action data (personal data) and environmental data (non-personal data) are often separated. Therefore, it is difficult for connected operators (service providers) to acquire environmental data related to the actions of customers.

[0007] The main object of the present invention is to provide a system and a method that contribute to enabling operators and the like that provide services to users to acquire action data with attached environmental data.

Means for Solving the Problems

[0008] According to a first aspect of the present invention, a first service server that stores action data related to the actions of a user, a second service server that stores a plurality of environmental data related to a predetermined environment, and a distribution control server that controls data sharing of personal data including the action data of the user are included. The first service server transmits the action data to the distribution control server in order to make the action data a target of the data sharing. The distribution control server accumulates the received action data and transmits an acquisition environmental data requirement that defines a requirement for environmental data that needs to be acquired from the plurality of environmental data according to the received action data to the second service server. The second service server extracts the environmental data that matches the acquired acquisition environmental data requirement from the plurality of environmental data and transmits the extracted environmental data to the distribution control server. The distribution control server stores the accumulated action data and the received environmental data in association with each other, and a system is provided.

[0009] According to a second aspect of the present invention, in a system including a first service server that stores behavior data regarding a user's behavior, a second service server that stores a plurality of environmental data regarding a predetermined environment, and a distribution control server that controls data sharing of personal data including the user's behavior data, in order to make the behavior data a target of the data sharing, the behavior data is transmitted to the distribution control server, the received behavior data is accumulated, and acquisition environment data requirements for determining requirements for environmental data that needs to be acquired from among the plurality of environmental data according to the received behavior data are transmitted to the second service server, the environmental data that matches the acquired acquisition environment data requirements is extracted from among the plurality of environmental data, the extracted environmental data is transmitted to the distribution control server, and the accumulated behavior data and the received environmental data are stored in association with each other. A method is provided.

Effects of the Invention

[0010] According to each aspect of the present invention, a system and a method are provided that contribute to enabling an operator or the like who provides a service to a user to acquire behavior data with attached environmental data. Note that the effects of the present invention are not limited to the above. Instead of or together with the above effects, other effects may be achieved by the present invention.

Brief Description of the Drawings

[0011]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

Figure 19

Figure 20

Figure 21

Figure 22

DETAILED DESCRIPTION OF THE INVENTION

[0012] First, an overview of one embodiment will be described. Note that the reference numerals in the drawings appended to this overview are for convenience of each element as an example for assisting understanding, and the description of this overview is not intended to be limiting in any way. Also, unless otherwise specified, the blocks described in each drawing represent a configuration of a functional unit, not a configuration of a hardware unit. The connection lines between the blocks in each figure include both bidirectional and unidirectional ones. The one-way arrow schematically shows the flow of the main signal (data) and does not exclude bidirectionality. In this specification and the drawings, for elements that can be similarly described, duplicate description may be omitted by assigning the same reference numerals.

[0013] A system according to one embodiment includes a first service server 101, a second service server 102, and a distribution control server 103 (see FIG. 1). The first service server 101 stores behavior data regarding the behavior of users. The second service server 102 stores a plurality of environment data regarding a predetermined environment. The distribution control server 103 controls data sharing of personal data including the behavior data of users. The first service server 101 transmits the behavior data to the distribution control server 103 in order to make the behavior data a target of data sharing (step S1 in FIG. 2). The distribution control server 103 accumulates the received behavior data and transmits an acquisition environment data requirement that defines the requirement for the environment data necessary to be acquired from among the plurality of environment data according to the received behavior data to the second service server 102 (step S2). The second service server 102 extracts the environment data that matches the acquisition environment data requirement acquired from among the plurality of environment data and transmits the extracted environment data to the distribution control server 103 (step S3). The distribution control server 103 stores the accumulated behavior data and the received environment data in association with each other (step S4).

[0014] When the actions of the user are accumulated in the system, the circulation control server 103 acquires environmental data related to the actions from the second service server 102 that stores a plurality of environmental data. Instead of a service provider for which it is difficult to acquire action data with attached environmental data, the circulation control server 103 acquires the action data. As a result, service providers and the like that provide services can acquire action data with attached environmental data.

[0015] Specific embodiments will be described in more detail below with reference to the drawings.

[0016] [First Embodiment] The first embodiment will be described in more detail with reference to the drawings.

[0017] [System Configuration] FIG. 3 is a diagram showing an example of the schematic configuration of an information circulation system according to an embodiment disclosed in the present application. As shown in FIG. 3, the participating members (actors) of the information circulation system include an information circulation provider and a service provider.

[0018] An information circulation provider is a provider that provides a platform for a data circulation service (information circulation service) of data accumulated by a service provider. The information circulation provider controls the data circulation of the accumulated data. The information circulation provider includes a circulation control server 10.

[0019] The circulation control server 10 is operated by an information circulation provider. The circulation control server 10 is a server device that controls (realizes) data circulation between service providers. The circulation control server 10 realizes an information circulation service for data held by service providers. The circulation control server 10 controls the data sharing of personal data including user action data.

[0020] A service provider is an entity that provides services to individuals. The service provider may be a private operator or a public institution. Service providers include, for example, hospitals and operators that provide health management services to users, etc.

[0021] Here, among service providers, there are those that handle personal data associated with users and those that handle non-personal data not associated with users.

[0022] For example, personal data includes weight, medical history, etc. Alternatively, an individual's actions and schedule, etc. are also included in personal data.

[0023] For example, non-personal data includes the weather in a given area. Alternatively, inventory information and sales information, etc. in a retail store, etc. are exemplified as non-personal data.

[0024] Note that one service provider may handle both personal data and non-personal data.

[0025] Each service provider is equipped with a service server 20. The service server 20 is managed and operated by each service provider. The service server 20 holds (stores) data generated by the service provider providing services to users, data necessary for providing services to users, etc. The service provider holds personal data (user data) related to the services provided to users.

[0026] Service providers that handle personal data include those that store behavior data regarding the actions of users. Such service providers are equipped with a service server 20 that stores the behavior data.

[0027] Service providers that handle non-personal data include those that store a plurality of environmental data regarding a given environment. Such service providers are equipped with a service server 20 that stores the plurality of environmental data.

[0028] A user who uses the information distribution system uses the terminal 30.

[0029] Each device shown in FIG. 3 is connected to each other via a network. For example, the distribution control server 10 and the service server 20 are connected by wired or wireless communication means and are configured to be able to communicate with each other.

[0030] The configuration shown in FIG. 3 is an example and is not intended to limit the configuration of the information distribution system disclosed in the present application. For example, the information distribution operator may include a plurality of distribution control servers 10. Load distribution and redundancy may be achieved by the plurality of distribution control servers 10.

[0031] [Schematic operation] Subsequently, the schematic operation of the information distribution system according to the first embodiment will be described.

[0032] First, operations related to data accumulation, data sharing, etc. in the information distribution system will be described. Thereafter, the operation of the information distribution system regarding the association of personal data (behavior data) and non-personal data (environmental data) will be described.

[0033] The user individually concludes a contract with the service provider who wants to receive the service. For example, the user offers to conclude a new contract (a contract for enjoying the service) with the service provider while providing the service provider with personal information such as name.

[0034] For example, a user who wants to receive an online health management service accesses the service server 20 operated by the health management service provider and creates an account.

[0035] The service provider generates a "personal identification ID" for identifying new customers (users). For example, a health management service provider generates a membership number or the like for managing customers as the personal identification ID. The service server 20 stores the generated personal identification ID (for example, a membership number or the like) in a database or the like.

[0036] Once the personal identification ID is generated, the user can receive services from the service provider. For example, the user can enjoy health management services online.

[0037] In order for personal data generated by the service provider providing services to the user or the like to be the subject of data circulation, "accumulation" of data is required. Data accumulation is for the service provider (data provider) to register personal data as data that can be provided to a third party in the information circulation system.

[0038] The circulation control server 10 controls data accumulation for making data related to the services provided by the data accumulator (service provider) to the user the subject of data circulation. That is, the circulation control server 10 controls data accumulation for registering personal data as data that can be shared (provided) with a third party in the information circulation system. The accumulated data becomes the subject of data circulation.

[0039] "Sharing" exists as a means of data circulation in the information circulation system. The circulation control server 10 controls data sharing for sharing the personal data registered by data accumulation from the service provider with others. Note that the service provider can also obtain the data (accumulated data) stored in the system by itself through data sharing. As will be described later, the service provider can obtain action data accompanied by environmental data (action data accompanied by environmental data) through data sharing.

[0040] <Generation of System Account> Users of the information circulation system need to perform pre-registration (user registration, system registration). More specifically, the user accesses the circulation control server 10 and performs procedures for account generation. In the following description, the account generated in the information circulation system is referred to as a "system account".

[0041] To generate a system account, the user operates the possessed terminal 30 to access the circulation control server 10. In response to the access of the terminal 30, the circulation control server 10 displays a WEB (web) page for generating a system account.

[0042] The user performs an operation for generating a system account (for example, pressing a predetermined button) to generate a system account. At that time, the circulation control server 10 acquires information necessary for the user to generate a system account. Specifically, the circulation control server 10 acquires the user's login information (login ID, password) and personal information (name, date of birth, contact information, account information, etc.).

[0043] After acquiring the login information, personal information, etc., the circulation control server 10 generates a user ID (Identifier) for uniquely identifying the user in the information circulation system.

[0044] The circulation control server 10 associates and stores the generated user ID of the user, login information, and personal information (for example, name, date of birth, contact information), etc. The circulation control server 10 stores these information in the "account management database". Details of the account management database will be described later.

[0045] The circulation control server 10 pays out the generated user ID to the user (terminal 30). The terminal 30 stores the paid-out user ID.

[0046] <ID Linkage> As described above, in order for the personal data held by a service provider to be the subject of data circulation, "data accumulation" is required. To achieve data accumulation, it is necessary to link the ID of the system account (user ID) and the ID generated by the service provider (personal identification ID). That is, in order for the personal data accumulated by each service provider to be the subject of data sharing, it is necessary to link the service provider's account and the system account.

[0047] For example, a user who wishes to utilize the personal data of a health management service provider operates the terminal 30 to access the service server 20 of the health management service provider (see Fig. 4). The user logs in to the account of the health management service provider and makes an application for data utilization on that account. In response to the application, the service server 20 transmits an "ID linking request" including the user's personal identification information, personal identification ID, and business operator code to the circulation control server 10.

[0048] Personal identification information is information for identifying the user. Examples of personal identification information include the user's name, or a combination of the name and date of birth.

[0049] The business operator code is identification information (ID) for identifying the service providers participating in the information circulation system. For example, different codes are assigned to each service provider. The business operator code is shared among system participants (information circulation business operators, service providers) by any means. For example, when a service provider participates in the information circulation system, the information circulation business operator generates a business operator code to be assigned to the service provider. The information circulation business operator notifies the generated business operator code to the service provider.

[0050] The circulation control server 10 acquires the personal identification information, personal identification ID of the ID linking applicant, and the business operator code of the service provider (e.g., health management service provider) that is the subject of ID linking from the service server 20.

[0051] The distribution control server 10 identifies the service providers that are the targets of ID linkage from the business operator codes. In addition, the distribution control server 10 identifies the users registered in the system account from the personal identification information. The distribution control server 10 associates the service provider and the personal identification ID in the account of the identified user.

[0052] When the personal identification ID is registered in the system account (when the ID linkage is completed), the service providers that are the targets of ID linkage can "accumulate" the personal data of the users who wish to utilize the data.

[0053] <Data accumulation> When a service provider provides a service to a user, the service provider stores the personal identification ID of the user and the personal data (user data) in association with each other. For example, when a service provider provides a service to a user, the service provider stores the data generated by the provision of the service (e.g., blood pressure, weight) in association with the individual identification ID.

[0054] For example, the service server 20 stores the personal identification ID of the user and the personal data in association with each other using the "customer information database". The details of the customer information database will be described later.

[0055] For the users for whom the ID linkage has been completed (the users who have applied for data utilization), the service server 20 performs control related to data accumulation every time it stores personal data (data generated as a result of service provision, data required for service provision).

[0056] Specifically, the service server 20 registers the personal data of the user as accumulated data (data targeted for data distribution) in the information distribution system. Specifically, the service server 20 transmits the "location information" regarding the users for whom the ID linkage has been completed to the distribution control server 10 (see Fig. 5).

[0057] Location information is information regarding the storage location of personal data (the entity that accumulates the data; service provider), etc. Location information includes a data ID for identifying personal data (accumulated data), a personal identification ID, a business operator code, the type of data to be held, and the like.

[0058] Alternatively, location information may include the specific content (specific values) of personal data. For example, when user behavior data is accumulated, the specific content of the actions performed by the user may be included in the location information.

[0059] The distribution control server 10 stores the acquired location information in the "location information database". Details of the location information database will be described later. The location information database stores by associating a data ID, a personal identification ID, a business operator code, and the data type, etc.

[0060] <Data sharing> A service provider, etc. that wishes to acquire data accumulated by another service provider (personal data resulting from the provision of services to users by another service provider) acquires the data by "sharing".

[0061] Here, while referring to FIG. 6, a case where a hospital acquires data (e.g., weight) of a user accumulated by a health management service provider by "sharing" will be described. The health management service provider is equipped with a service server 20-1, and the hospital is equipped with a service server 20-2.

[0062] The service server 20-2 transmits a "sharing request" to the distribution control server 10 (step S11).

[0063] Based on the sharing request, the distribution control server 10 identifies the data accumulator (health management service provider) of the data to be distributed with the user who is the target of data distribution. The distribution control server 10 transmits an inquiry regarding data sharing to the terminal 30 possessed by the identified target (step S12).

[0064] The terminal 30 that has received the data sharing inquiry acquires the user's intention regarding data sharing. For example, the terminal 30 acquires the user's intention using a GUI (Graphical User Interface). In the above example, the terminal 30 displays a GUI with content such as "By sharing your weight with the hospital, you can receive better services. Do you want to share the information?" and acquires the user's intention (agreement or disagreement to data sharing).

[0065] The terminal 30 transmits a response to the data sharing inquiry (agreement to data sharing or rejection of data sharing) to the circulation control server 10 (step S13).

[0066] If the user's consent is obtained, the circulation control server 10 transmits a sharing instruction to the data sharing source (health management service provider) (step S14).

[0067] The service server 20-1 that has received the sharing instruction refers to the customer information database and transmits the personal data (weight, etc.) of the target user to the service server 20-2 that is the designated data sharing destination (step S15).

[0068] Note that the service provider can also obtain the data it has accumulated through data sharing. The service server 20 can obtain the action data accompanied by environmental data by transmitting a sharing request to the circulation control server 10.

[0069] <Association between Personal Data and Non-Personal Data> Subsequently, the operation of the information circulation system regarding the association between personal data (action data) and non-personal data (environmental data) will be described. In the following description, the association between personal data (action data) and non-personal data (environmental data) is referred to as "data linkage".

[0070] <Configuration of the Environment> In explaining the data linkage, consider an area as shown in FIG. 7.

[0071] As shown in FIG. 7, an Open Terrace A is provided along the A River flowing through the urban area of City A. The Open Terrace A is an area where a part of the promenade along the A River is expanded. The Open Terrace A is designated as a "Relaxation Area" as part of the Well-Being improvement measures in City A.

[0072] An office area is adjacent to the Open Terrace A. Many employees and the like work in the buildings and the like constructed in the office area.

[0073] As an application for more comfortable use of the Open Terrace A, Application A (hereinafter referred to as App A) is provided free of charge by City A to the users of the Open Terrace A.

[0074] Users can enter the Open Terrace A by passing through the gate from the sidewalk on the office area side. In the Open Terrace A, unmanned convenience stores, unmanned libraries, and the like are installed. Also, table seats with umbrellas are installed in the terrace area within the Open Terrace A.

[0075] In addition, various sensors are installed in the Open Terrace A. For example, sensors for measuring temperature and humidity, and sensors for measuring noise levels are installed in the Open Terrace A. City A, which is the management entity of the Open Terrace A, collects the information of the sensors.

[0076] Users operate the terminal 30 to download App A from a predetermined website or the like. Users install App A on the terminal 30.

[0077] App A has a plurality of functions. Specifically, App A has a "Check-In function", a "Payment function", a "Rental function", an "Event Reservation function", a "Diary function", and a "Recommendation function".

[0078] When the user enters the open terrace A, the check-in function awards a predetermined number of points to the user.

[0079] The payment function is a function used when the user purchases goods at an unmanned convenience store. The user can use the points awarded at the unmanned convenience store.

[0080] The rental function is a function used when the user rents content at an unmanned library. When the user rents content, a predetermined number of points are awarded to the user.

[0081] The event reservation function is a function for the user to reserve an event held at the open terrace A. When the user reserves an event, a predetermined number of points are awarded to the user.

[0082] The diary function is a function that automatically records the actions of the user while staying at the open terrace A.

[0083] The recommendation function is a function that makes recommendations for the user to have a comfortable stay at the open terrace A.

[0084] Note that detailed descriptions of the above functions provided by App A are omitted. This is because the details of individual applications are different from the gist of the present disclosure.

[0085] The user operates the terminal 30 to use App A. App A communicates with the service server 20 managed by City A and provides the above various functions to the user. The service server 20 of City A manages the personal data obtained by the user using App A. When the user uses App A, the personal data of the user is stored in the system.

[0086] Note that the user registers their own attributes (for example, an office worker working in the office area, a resident of City A, etc.) with the service server 20 of City A when using App A.

[0087] Before using the open terrace A, the user inputs, using Application A, the purpose of using the open terrace A and the planned actions to be taken on the open terrace A. Alternatively, after using the open terrace A, the user inputs, using Application A, the purpose of using the open terrace A and the actions taken on the open terrace A. These purposes and actions (planned or actual) are also accumulated in the system as the user's personal data.

[0088] In the following description, the data regarding the purpose accumulated before using the open terrace A is referred to as purpose data (planned). The data regarding the purpose accumulated after using the open terrace A is referred to as purpose data (actual).

[0089] Also, in the following description, the data regarding the actions accumulated before using the open terrace A is referred to as user action data (planned). Similarly, the data regarding the actions accumulated after using the open terrace A is referred to as user action data (actual).

[0090] Here, the operator of the unmanned convenience store, the operator of the unmanned library, City A which is the management entity of the open terrace A, the weather service provider that provides weather information, etc. collect data related to the open terrace A.

[0091] These entities (service providers) may accumulate the user's personal data in the system, or may hold non-personal data in their own servers, etc.

[0092] For example, the unmanned convenience store accumulates in the system information on the products purchased by the user (purchase history; purchase actual). Alternatively, the unmanned library accumulates in the system information on the products rented by the user (rental history; rental actual).

[0093] Alternatively, the unmanned convenience store stores information about the sold products as non-personal data in its own service server 20. Alternatively, the unmanned library stores information about the content as non-personal data. Alternatively, City A stores information about various sensors installed on Open Terrace A and information about events, etc. Alternatively, the operator providing the weather service stores the weather information on Open Terrace A.

[0094] The service provider that collects and stores non-personal data can store predictions and results for each of the non-personal data. For example, the operator providing the weather service stores the prediction and result regarding the weather of Open Terrace A in the service server 20.

[0095] <Environmental Definition> City A, which is the management entity of Open Terrace A, defines the elements that make up the environment of Open Terrace A. City A defines the elements that make up Open Terrace A as "environmental composition elements". The data obtained by quantifying (quantifying) the environmental composition elements is "environmental data". Since environmental data can exist independently of users, it is also non-personal data. Each environmental data is composed of at least one or more environmental data items.

[0096] For example, the staff of City A generates table information as shown in FIG. 8.

[0097] For example, the staff of City A defines "area weather" as one of the environmental composition elements related to Open Terrace A. The area weather is composed of environmental data items such as location, time, weather, temperature, and humidity.

[0098] <Action Definition by Purpose> City A, which is the management entity of Open Terrace A, assumes the specific attributes of the users of Open Terrace A and sets a plurality of communities. For example, as users of Open Terrace A, office workers working in the office area, residents of City A, etc. are set.

[0099] The staff in City A, for each attribute (community), assume the purposes and behaviors of the users belonging to the community when using the open terrace A, and associate the purposes with the behaviors. As described above, the behaviors (assumed behaviors) of the users include plans and achievements.

[0100] The staff in City A define the behaviors of the users associated with the purposes as "purpose-specific behaviors". In the following description, the purpose-specific behaviors related to the plan are denoted as purpose-specific behaviors (planned), and the purpose-specific behaviors related to the achievement are denoted as purpose-specific behaviors (actual).

[0101] The data representing the purpose-specific behaviors is "purpose-specific behavior data". Each purpose-specific behavior data is defined (represented) by at least one or more behavior data items. In the following description, the purpose-specific behavior data related to the plan is denoted as purpose-specific behavior data (planned), and the purpose-specific behavior data related to the achievement is denoted as purpose-specific behavior data (actual).

[0102] For example, the staff in City A generate table information as shown in FIG. 9, which includes the purposes (purposes of using the open terrace A), purpose-specific behaviors, and purpose-specific behavior data of the workers who work in the office area adjacent to the open terrace A. Note that the behavior data items shown in FIG. 9 are examples, and the purpose-specific behavior data consists of at least one of the multiple behavior data items described in FIG. 9.

[0103] For example, when a user belonging to the worker community has the purpose of "having lunch", behaviors (purpose-specific behaviors) such as checking in to the open terrace A, purchasing lunch, securing a seat, and finally checking out are assumed. Each purpose-specific behavior is defined by the purpose-specific behavior data. For example, the purpose-specific behavior of "checking in" is represented by specific data (numerical values) such as the gate number passed by the user and the check-in time.

[0104] <Component-related Definitions> City A, which is the management entity of Open Terrace A, generates definitions related to components for data linkage by associating environmental definitions with action definitions by purpose. The definitions related to components enable the association of personal data (user behavior data) with non-personal data (environmental data).

[0105] The definitions related to components are composed of the environment, community (user attributes), purpose, actions by purpose, environmental components, and requirements for acquired environmental data. The definitions related to components are composed of at least the association between user actions and requirements for acquired environmental data. The definitions related to components determine the "requirements for acquired environmental data" corresponding to the actual actions (plans, achievements) of the classified users for each actual action of the users.

[0106] The requirements for acquired environmental data (plans, achievements) define the environmental data that needs to be acquired from among the environmental data stored in an external server (service server 20) or the like. More specifically, the requirements for acquired environmental data determine the requirements for the environmental data that needs to be acquired from among a plurality of environmental data according to the action data received by the distribution control server 10. The requirements for acquired environmental data enable the acquisition of environmental data corresponding to the actions (plans, achievements) of the users.

[0107] For example, employees of City A or the like generate table information as shown in FIG. 10 and register it in the distribution control server 10. At that time, employees of City A or the like may use the table information shown in FIGS. 8 and 9.

[0108] For example, consider the case where an office worker working near Open Terrace A plans to check in to eat lunch at Open Terrace A. In this case, the requirements for acquired environmental data (plans) described in the uppermost row and the second row of FIG. 10 specify what kind of area weather and event information to acquire.

[0109] In the example of FIG. 10, if the user is an office worker and the purpose of using the open terrace A is "lunch", "check-in" is defined as an action related to the purpose "lunch". When the user performs a check-in (if performed), "area weather" and "event" are defined as environmental data that needs to be acquired in association with the check-in action.

[0110] Here, environmental data such as area weather has a huge amount of data. Among the huge amount of data, environmental data that meets the acquired environmental data requirements is acquired as data related to the user's actions (plans, achievements). For example, in the example of FIG. 10, as acquired environmental data requirements for area weather, a requirement C1 related to time and a requirement C2 related to range are set.

[0111] For example, the requirement C1 related to time is the following formula (1), and the requirement C2 related to range is the following formula (2).

[0112]

Equation

[0113]

Equation

[0114] According to formula (1), the weather (weather data) from the time when the purpose (action) is accumulated to the end time of the user's action is acquired. According to formula (2), the weather (weather data) within the user's action plan range is acquired. In formulas (1) and (2), α, β, and γ set a predetermined width for time and range.

[0115] In this way, the distribution control server 10 holds the acquisition environment data requirements that define the requirements for the environment data necessary to be acquired from among the plurality of environment data stored in the service server 20 according to the actions of the user. The acquisition environment data requirements are stored together with the actions of the user according to the component-related definitions. In particular, the component-related definitions store the acquisition environment data requirements for each of the actions related to the planned actions to be performed by the user and the actions related to the actual results achieved by the user.

[0116] <Data Linkage> Subsequently, the operation of the information distribution system regarding the association between the action data and the environment data will be described. Here, the data linkage when the target data (plan) regarding the plan of the office worker and the user action data (plan) are accumulated in the system will be described.

[0117] For example, as the target data (plan), "lunch", and as the user action data (plan), "the office worker checks in at 11:55 on May 11th" are accumulated in the system from the application A via the service server 20 in City A (see Fig. 11).

[0118] When the target data (plan) of the office worker and the user action data (plan) are accumulated with data, the distribution control server 10 refers to the component-related definitions.

[0119] The distribution control server 10 acquires the environment data corresponding to the accumulated target data (plan) and user action data (plan) from an external server or the like. At this time, while referring to the component-related definitions, the distribution control server 10 specifies the acquisition environment data requirements (plan) corresponding to the target data (plan) and the user action data (plan).

[0120] In the example of FIG. 10, since the purpose of the office worker is "lunch" and the action (plan) is "check-in", the distribution control server 10 identifies acquisition environment data requirements C1 and C2 regarding the area weather, which correspond to the user's action (plan). Similarly, the distribution control server 10 identifies acquisition environment data requirements C5 and C6 regarding the event, which correspond to the user's action (plan).

[0121] The distribution control server 10 transmits the acquisition environment data requirements C1 and C2 to a server (service server 20 of a meteorological service provider) that holds environment data regarding the area weather, and acquires the corresponding environment data. Similarly, the distribution control server 10 transmits the acquisition environment data requirements C5 and C6 to a server (service server 20 of City A) that holds environment data regarding the event, and acquires the corresponding environment data.

[0122] The distribution control server 10 stores the acquired environment data in association with the above user action data (plan). The distribution control server 10 stores the environment data in association with the accumulated user action data (plan).

[0123] The service server 20 that realizes the function of Application A acquires the user action data (plan) accumulated in the system through data sharing. The service server 20 makes a recommendation regarding Open Terrace A using the user action data (plan) accompanied by environment data. For example, the service server 20 displays a screen as shown in FIG. 12 and makes a recommendation regarding Open Terrace A to the user.

[0124] The user who touches the screen as shown in FIG. 12 inputs to the terminal 30 whether to accept the proposal (recommendation). If the user accepts the recommendation, Application A changes and adds to the user's user action data (plan) according to the content of the recommendation.

[0125] For example, in the example of FIG. 12, participation in Event A is added to the user action data (plan).

[0126] <Data Linkage (Achievement)> Regarding the linkage between the user's actions (achievement) and environmental data, data linkage is possible in the same way as for actions (planned).

[0127] For example, the service server 20 that realizes the functions of Application A accumulates target data (achievement) and user action data (achievement). In response to this data accumulation, the distribution control server 10 acquires environmental data corresponding to the user's actions from an external server.

[0128] The distribution control server 10 associates and stores the acquired environmental data with the user action data (achievement).

[0129] The service server 20 acquires the user action data (achievement) with environmental data attached by data sharing. The service server 20 generates a diary of the user on the open terrace A using the user action data (achievement) with the attached environmental data.

[0130] For example, the service server 20 generates a screen (diary) as shown in FIG. 13 and displays it on the terminal 30. The service server 20 accepts diary corrections by the user. The service server 20 may accumulate the accepted corrections as user action data (achievement).

[0131] Note that service providers other than those in City A that provide Application A can also acquire the user action data (planned, achievement) with environmental data attached through data sharing. By acquiring the user action data (planned, achievement) with environmental data attached, the service provider can provide a more convenient service to the user.

[0132] In this way, the service server 20 (the first service server) that provides services to the user transmits the behavior data to the distribution control server 10 in order to make the behavior data subject to data sharing. The distribution control server 10 accumulates the received behavior data and determines the acquisition environment data requirements that define the requirements for the environment data that needs to be acquired from among a plurality of environment data according to the received behavior data, and transmits the requirements to the second service server (the service server 20 that stores the environment data). The service server 20 extracts the environment data that matches the acquired environment data requirements from among the plurality of environment data, and transmits the extracted environment data to the distribution control server 10. The distribution control server 10 stores the accumulated behavior data and the received environment data in association with each other.

[0133] The service server 20 (the first service server) that provides services to the user acquires the behavior data with attached environment data from the distribution control server 10. The service server 20 provides services to the user using the acquired behavior data with attached environment data, and transmits the new behavior data generated by the result of providing services to the user to the distribution control server 10. For example, the service server 20 in City A provides a behavior recommendation service and a diary generation service to the user via App A. When the user accepts a recommendation or modifies a diary, the operation (evaluation of the user) of the user is accumulated in the system as new behavior (plan, achievement). That is, the user behavior data (plan, achievement) of the user is adjusted by providing services using the behavior data with attached environment data.

[0134] Subsequently, the details of each device included in the information distribution system according to the first embodiment will be described.

[0135] [Distribution Control Server] FIG. 14 is a diagram showing an example of the processing configuration (processing modules) of the distribution control server 10 according to an embodiment of the present disclosure. Referring to FIG. 14, the distribution control server 10 includes a communication control unit 201, a user registration unit 202, an ID cooperation unit 203, a location information management unit 204, a data sharing control unit 205, a definition control unit 206, a data cooperation control unit 207, and a storage unit 208.

[0136] The communication control unit 201 is a means for controlling communication with other devices. For example, the communication control unit 201 receives data (packets) from the service server 20. Also, the communication control unit 201 transmits data to the service server 20. The communication control unit 201 delivers the data received from other devices to other processing modules. The communication control unit 201 transmits the data acquired from other processing modules to other devices. In this way, other processing modules perform data transmission and reception with other devices via the communication control unit 201. The communication control unit 201 has a function as a receiving unit that receives data from other devices and a function as a transmitting unit that transmits data to other devices.

[0137] The user registration unit 202 is a means for realizing the above-described user registration (system registration of users). The user registration unit 202 acquires personal information (name, date of birth, contact information, account information, etc.) from the user's terminal 30.

[0138] When the user registration unit 202 acquires the personal information, it generates a user ID for identifying the user. For example, each time the user registration unit 202 performs system registration of a user, it assigns a unique value, and uses the assigned value as the user ID.

[0139] The user registration unit 202 stores the user ID and personal information in the account management database (see Fig. 15). As shown in Fig. 15, the account management database stores the user ID, personal information, and personal identification ID for each service provider in association with each other. Also, the account management database shown in Fig. 15 is an example and is not intended to limit the items to be stored. For example, the date and time when the user was registered may be registered in the account management database.

[0140] The user registration unit 202 transmits the generated user ID to the terminal 30.

[0141] The ID linkage unit 203 is a means for realizing the above-mentioned ID linkage. The ID linkage unit 203 receives an "ID linkage request" from the service server 20. The ID linkage request includes personal identification information, personal identification ID, and business operator code of a user who wishes to perform ID linkage (registration of a service provider).

[0142] The ID linkage unit 203 searches the account management database using the personal identification information (such as the user's name, combination of name and date of birth, etc.) as a key, and identifies the corresponding user. The ID linkage unit 203 sets the personal identification ID included in the ID linkage request in the field corresponding to the business operator code among the personal identification ID fields of the identified user. That is, the ID linkage unit 203 identifies the user registered in the system account from the personal identification information, and associates the service provider and the personal identification ID in the account of the identified user.

[0143] Referring to the account management database shown in Fig. 15, the user with the name A has an account linkage with the health management service provider and the hospital. Also, the user with the name B has an account linkage with the hospital.

[0144] The location information management unit 204 is a means for managing the location information obtained from service providers. The location information management unit 204 controls the data accumulation for registering personal data generated by service providers providing services to users as data that can be provided to third parties in the information circulation system.

[0145] The location information management unit 204 stores the location information obtained from each service server 20 in a location information database (see FIG. 16). As shown in FIG. 16, the location information database stores by associating personal identification IDs, operator codes, data IDs, data types, data accumulation dates, and the like.

[0146] Note that, as described above, the service server 20 may also transmit the specific content of the accumulated data to the circulation control server 10. For example, the service server 20 in City A that provides App A transmits location information including the specific content of target data (schedules, actual results) and user behavior data (schedules, actual results) to the circulation control server 10.

[0147] In this case, data as shown in FIG. 17 is stored in the location information database. In addition to each data shown in FIG. 16, the location information database may store the specific content of the accumulated data and the environmental data associated with the accumulated data (user behavior data).

[0148] Note that in the location information database shown in FIG. 17, user behavior data (schedules) is denoted as actions (schedules). Similarly, target data (schedules) is denoted as targets (schedules).

[0149] Note that the location information databases shown in FIGS. 16 and 17 are examples and are not intended to limit the items to be stored. For example, the user ID of each user may be stored in the location information database. Also, in the drawings including FIGS. 16 and 17, for ease of understanding, the operator code is denoted using the name of the service provider.

[0150] Referring to the account management database shown in FIG. 15 and the location information database shown in FIG. 16, it can be seen that the user with the individual identification ID of "HL01" has received data accumulation regarding "weight" and "blood pressure" from the health management service provider.

[0151] The data sharing control unit 205 is a means for controlling the data flow by data sharing.

[0152] The data sharing control unit 205 receives a sharing request from the service server 20. The sharing request includes the personal identification ID of the user who is the target of data acquisition, the business operator code of the sender of the sharing request, and the type of data to be acquired. In the example of FIG. 6, the personal identification ID generated by the hospital (service server 20-2) for the user, the business operator code of the hospital, and "weight" as the data type are included in the sharing request.

[0153] The data sharing control unit 205 identifies the target person of the data flow based on the personal identification ID and the business operator code included in the sharing request. Specifically, the data sharing control unit 205 refers to the account management database shown in FIG. 15 to identify the target person. In the above example, when receiving a sharing request including the personal identification ID of "EC01" from the hospital, the data sharing control unit 205 can see from the first row entry shown in FIG. 15 that the user named A is the target person of the data flow.

[0154] After that, the data sharing control unit 205 identifies the service provider that has accumulated the necessary data using the personal identification ID of the identified user and the data type included in the sharing request. Specifically, the data sharing control unit 205 refers to the location information databases shown in FIGS. 16 and 17 to identify the service provider that has accumulated the data corresponding to the data type included in the sharing request. In the above example, based on the personal identification ID "HL01" of the user named A and the data type "weight" included in the sharing request, the health management service provider is identified.

[0155] If the combination of the user's personal identification ID and the data types included in the sharing request is not stored in the location information database, the data sharing control unit 205 sends a negative response indicating that data sharing is not possible to the source of the sharing request.

[0156] When the target of data circulation and the accumulator of the data to be circulated are identified, the data sharing control unit 205 makes an inquiry about data sharing to the target of data circulation. Specifically, the data sharing control unit 205 sends an inquiry regarding data sharing to the contact information of the target of data circulation. In the above example, the inquiry is sent to the terminal 30 owned by the user with name A.

[0157] Note that the inquiry about data sharing includes information such as the source of the data sharing request, the data accumulator, and the data types to be shared. In the above example, the hospital is set as the source of the data sharing request, the health management service provider is set as the data accumulator, and "weight" is set as the data type to be shared.

[0158] The data sharing control unit 205 receives a response to the inquiry about data sharing from the terminal 30.

[0159] If the user rejects data sharing, the data sharing control unit 205 notifies the source of the data sharing request that data sharing is not possible. In the above example, the data sharing control unit 205 sends a negative response to the sharing request to the service server 20-2 of the hospital.

[0160] If the user agrees to data sharing, the data sharing control unit 205 sends a sharing instruction to the data accumulator. In the above example, the sharing instruction is sent to the service server 20-1 of the health management service provider, which is the data accumulator.

[0161] The sharing instruction includes the personal identification ID generated by the data accumulator, information about the data sharing destination, and the type of data to be shared. In the above example, a sharing instruction including the personal identification ID "HL01" of the user named A, the address of the service server 20-2 of the hospital, and the data type "weight" is sent to the service server 20-1 of the health management service provider.

[0162] In this way, the data sharing control unit 205 sends a sharing instruction including the personal identification ID of the user (target person) who has consented to data sharing and generated by the data accumulator.

[0163] As described above, the service provider can obtain the data accumulated by itself through data sharing. More specifically, the service provider can obtain user behavior data (scheduled, actual) accompanied by environmental data through data sharing.

[0164] In this case, the service provider (for example, the service server 20 in City A) sends a sharing request including the personal identification ID of the target person, its own business code, and the data type "user behavior data (scheduled)" or "user behavior data (actual)" to the distribution control server 10.

[0165] When receiving a sharing request including the data type "user behavior data (scheduled)" or "user behavior data (actual)", the data sharing control unit 205 searches the location management database using the personal identification ID and business code included in the sharing request as keys.

[0166] For example, when receiving a sharing request including the personal identification ID "A01", the business code "City A", and the data type "user behavior data (scheduled)", the data sharing control unit 205 identifies the entry in the second row shown in FIG. 17.

[0167] The data sharing control unit 205 sends the set values of the content field and the environmental data field of the identified entry to the source of the sharing request. In the above example, the content "DB01" and the environmental data "DE01" and "DE02" are sent to the service server 20 in City A.

[0168] Note that the content "DB01" includes information such as "An office worker checks in at 11:55 on May 11th". The environmental data "DE01" includes information such as "On May 11th, from 11:50 to 13:00, sunny, temperature 26°C, humidity 50%". The environmental data "DE02" includes information such as "Virtual event, on May 11th from 12:00 to 12:30".

[0169] The definition control unit 206 is a means for mainly performing control related to component-related definitions.

[0170] The definition control unit 206 acquires component-related definitions as shown in FIG. 10 from a service provider (for example, a staff member in City A). The definition control unit 206 may acquire component-related definitions using a GUI (Graphical User Interface), or may acquire component-related definitions using an external memory such as a USB (Universal Serial Bus).

[0171] Note that the definition control unit 206 acquires information on the environment related to the component-related definition from the service provider together with the component-related definition. For example, the definition control unit 206 acquires "Open Terrace A along River A" as the environment name and "An area obtained by expanding a part of the promenade along River A" as its description. The definition control unit 206 stores the acquired environment name, description, and component-related definition in association with each other.

[0172] The definition control unit 206 stores the acquired component-related definition (table information as shown in FIG. 10) in the storage unit 208.

[0173] The data linkage control unit 207 is a means for executing control related to the linkage between user behavior data (schedules, actual results) and environmental data. When the user behavior data (schedules, actual results) is stored in the location information database, the data linkage control unit 207 acquires the environmental data associated with the stored user behavior data (schedules, actual results) from an external server.

[0174] When the user behavior data (scheduled, actual) is stored in the location information database, the data linkage control unit 207 acquires the content of the target data (scheduled, actual) registered in the location information database at substantially the same timing as the user behavior data (scheduled, actual). Further, the data linkage control unit 207 acquires the specific content of the user behavior data (scheduled, actual).

[0175] For example, when the user behavior data (scheduled) on the second line shown in FIG. 17 is stored, the data linkage control unit 207 acquires the specific content of the target data (scheduled) on the first line and the user behavior data (scheduled), respectively. For example, the data linkage control unit 207 acquires contents such as "Purpose: Lunch" and "Action: Office worker is scheduled to check in at 11:55 on May 11th".

[0176] The data linkage control unit 207 refers to the component-related definitions and identifies the environmental components and the acquired environment data requirements that match the content of the acquired target data (scheduled, actual) and the user behavior data (scheduled, actual). For example, in the above example, the area weather and the acquired environment data requirements (C1, C2) and the events and the acquired environment data requirements (C5, C6) corresponding to the community "Office worker", the purpose "Lunch", and the action by purpose "Check-in" are identified.

[0177] The data linkage control unit 207 transmits the corresponding acquired environment data requirements to an external server (service server 20) that stores the identified environmental components. In the above example, the data linkage control unit 207 transmits the acquired environment data requirements C1 and C2 to the service server 20 of the meteorological service provider that holds the area weather. The data linkage control unit 207 transmits the acquired environment data requirements C5 and C6 to the service server 20 in City A that holds the event information.

[0178] The data linkage control unit 207 transmits the acquired environment data requirements to the service server 20 to acquire environment data that meets the requirements. In the above example, the data linkage control unit 207 acquires weather data for the time period when the user visits the open terrace A from among a vast amount of area weather data. Similarly, the data linkage control unit 207 acquires event information held by City A that is held during the time period when the user visits the open terrace A from among the event information held by City A.

[0179] The data linkage control unit 207 stores the acquired environment data in association with the user behavior data (schedules, actual results). The data linkage control unit 207 stores the acquired environment data in the location information data (see FIG. 17).

[0180] The storage unit 208 stores information necessary for the operation of the distribution control server 10. An account management database or the like is constructed in the storage unit 208. The storage unit 208 uses the account management database or the like to store the status of data sharing for each of a plurality of users who participate in the information distribution system.

[0181] [Service Server] FIG. 18 is a diagram showing an example of the processing configuration (processing modules) of the service server 20 according to the embodiment disclosed in the present application. Referring to FIG. 18, the service server 20 includes a communication control unit 301, an ID linkage control unit 302, a data accumulation control unit 303, a data sharing unit 304, a data acquisition unit 305, an environment data control unit 306, and a storage unit 307.

[0182] The communication control unit 301 is a means for controlling communication with other devices. For example, the communication control unit 301 receives data (packets) from the distribution control server 10. Also, the communication control unit 301 transmits data to the distribution control server 10. The communication control unit 301 delivers the data received from other devices to other processing modules. The communication control unit 301 transmits the data acquired from other processing modules to other devices. In this way, other processing modules perform data transmission and reception with other devices via the communication control unit 301. The communication control unit 301 has a function as a receiving unit for receiving data from other devices and a function as a transmitting unit for transmitting data to other devices.

[0183] The ID linkage control unit 302 is a means for controlling the ID linkage of users. The ID linkage control unit 302 acquires a request for ID linkage from a user who has logged in to an account using a GUI (Graphical User Interface) or the like. The ID linkage control unit 302 transmits an "ID linkage request" including personal identification information (such as the name of the logged-in user), a personal identification ID (such as the user's membership number), and a business operator code to the distribution control server 10 according to the request from the user.

[0184] Note that the user's personal identification ID, personal identification information, personal data, etc. are managed using a customer information database (see Fig. 19). As shown in Fig. 19, the customer information database holds information (flag) on whether the ID linkage of the user is completed. When the ID linkage is completed, the ID linkage control unit 302 sets a flag in the ID linkage status field of the corresponding user (in Fig. 19, a circle is set).

[0185] The data storage control unit 303 is a means for controlling the storage of personal data resulting from providing services to users. The data storage control unit 303 associates the personal identification ID of the user with the personal data of the user (data generated as a result of providing services to the user or data necessary for the services provided to the user) and stores it in the customer information database.

[0186] As shown in FIG. 19, the data storage control unit 303 stores personal data in a field corresponding to the type of generated data (stores the specific content of the data). At that time, the data storage control unit 303 generates a data ID for identifying the personal data, and stores the personal data and the data storage date in association with each other. Note that FIG. 19 shows an example of a customer information database constructed in the service server 20 of the health management service provider.

[0187] Here, for a user for whom ID linking is completed, every time the data storage control unit 303 stores personal data in the customer information database, it transmits the location information to the distribution control server 10. For example, consider the case where a health management service is provided to a user with the personal identification ID "HL01" and weight data is generated. In this case, the location information including the personal identification ID "HL01", the operator code "health management service provider", the data ID "HLD01", and the data type "weight" is transmitted to the distribution control server 10.

[0188] In addition, when target data (scheduled, actual) or user behavior data (scheduled, actual) is acquired, the data storage control unit 303 transmits location information including the specific content of the target data and the user behavior data in addition to the personal identification ID, the operator code, the data ID, and the data type.

[0189] The data sharing unit 304 is a means for realizing data acquisition by data sharing. The data sharing unit 304 processes the "sharing instruction" received from the distribution control server 10.

[0190] When a sharing instruction is received, the data sharing unit 304 refers to the customer information database and identifies an entry corresponding to the personal identification ID and the data type included in the sharing instruction.

[0191] The data sharing unit 304 transmits the personal data described in the corresponding data type field of the specified entry to the data sharing destination designated by the sharing instruction. In the example of FIG. 6, "weight" is transmitted to the service server 20-2 of the hospital.

[0192] The data acquisition unit 305 is a means for acquiring the personal data of the user through data sharing. The data acquisition unit 305 transmits a sharing request to the distribution control server 10 according to the operations of the staff of the service provider or the like. Specifically, the data acquisition unit 305 transmits a sharing request including the personal identification ID of the user who is the target of data acquisition, the business operator code, and the data type desired to be acquired to the distribution control server 10.

[0193] In addition, when the service provider acquires the user behavior data (scheduled, actual) accumulated by itself through data sharing, the data acquisition unit 305 transmits a sharing request including the personal identification ID, the business operator code, and the data type "user behavior data (scheduled, actual)" to the distribution control server 10.

[0194] The service server 20 of the service provider that handles non-personal data (environmental data) is provided with an environmental data control unit 306. The environmental data control unit 306 performs control related to the acquisition, storage, provision, etc. of environmental data.

[0195] For example, the environmental data control unit 306 provided in the service server 20 of the weather service provider acquires predictions (forecasts) and results (actuals) related to weather data using various means. The environmental data control unit 306 stores the acquired environmental data in a database or the like.

[0196] The environmental data control unit 306 receives the acquired environmental data requirements from the distribution control server 10. The environmental data control unit 306 extracts the environmental data that matches the received acquired environmental data requirements from the stored environmental data, and transmits the extracted environmental data to the distribution control server 10.

[0197] For example, when the acquisition environment data requirement (scheduled) is received, the environment data control unit 306 extracts prediction data that meets the conditions specified by the requirement from the acquired prediction data (data of the same type as the environment data specified by the acquisition environment data requirement). For example, when the acquisition environment data (scheduled) related to weather data is received, the environment data control unit 306 extracts weather forecast data that meets the acquisition environment data requirement from the weather forecast data.

[0198] When the acquisition environment data requirement (actual result) is received, the environment data control unit 306 extracts result data that meets the conditions specified by the requirement from the acquired result data (data of the same type as the environment data specified by the acquisition environment data requirement). For example, when the acquisition environment data (actual result) related to weather data is received, the environment data control unit 306 extracts weather forecast data that meets the acquisition environment data requirement from the weather history data.

[0199] Note that since the specific acquisition method for individual environment data and the extraction process of environment data that meets the acquisition environment data requirement are different from the gist of the present disclosure, detailed description is omitted.

[0200] The storage unit 307 stores information necessary for the operation of the service server 20.

[0201] [Terminal] Examples of the terminal 30 include mobile terminal devices such as smartphones and tablets, and computers (personal computers, notebook computers). The terminal 30 can be any device or apparatus as long as it can receive the user's operation and communicate with the distribution control server 10 or the like. Also, since the configuration of the terminal 30 and the like are obvious to those skilled in the art, detailed description is omitted.

[0202] When the terminal 30 possessed by the user of the data sharing source receives a sharing inquiry, it acquires the intention of the user regarding data sharing (agreement or disagreement to data sharing) using a GUI or the like. The terminal 30 transmits the acquired intention to the distribution control server 10.

[0203] Note that the service server 20 in City A realizes the functions of App A. However, since the functions of App A are different from the gist of the present disclosure, detailed descriptions thereof are omitted. For the same reason, detailed descriptions such as the interface of App A on the terminal 30 are omitted.

[0204] [System Operation] Subsequently, the operation of the information circulation system according to the first embodiment will be described. FIG. 20 is a sequence diagram showing an example of the operation of the information circulation system according to the embodiment of the present disclosure. With reference to FIG. 20, the operation of the information circulation system when linking action data and environment data will be described.

[0205] When specific user action data with specific content is accumulated, the circulation control server 10 refers to the component-related definitions. By referring to the component-related definitions, the circulation control server 10 identifies the environment data that needs to be acquired in relation to the actions (plans, actual results) of the user. The circulation control server 10 acquires the acquired environment data requirements (step S21).

[0206] After acquiring the acquired environment data requirements, the circulation control server 10 transmits the acquired environment data requirements to the service server 20 (step S22).

[0207] The service server 20 extracts the environment data that matches the acquired environment data requirements from the stored environment data, and transmits the extracted environment data to the circulation control server 10 (step S23).

[0208] The circulation control server 10 associates and stores the accumulated user action data and the environment data acquired from the service server 20 (execution of data linkage; step S24).

[0209] Subsequently, a modification example according to the first embodiment will be described.

[0210] [Modification Example 1] The circulation control server 10 may be provided with a function of assisting the service provider in determining component-related definitions. In this case, the definition control unit 206 pre-acquires environment definitions, action definitions by purpose, and component-related definitions for a predetermined service. For example, the definition control unit 206 pre-acquires environment definitions, action definitions by purpose, and component-related definitions for the service provided by Application A (the service related to the use of Open Terrace A).

[0211] The definition control unit 206 uses the already acquired environment definitions, etc., to assist in generating component-related definitions for services similar to the services for which the environment definitions, etc., have already been acquired. For example, in response to access from a person in charge of the service provider, etc., the definition control unit 206 displays a GUI as shown in FIG. 21 on the terminal used by the person in charge.

[0212] The person in charge of the service provider, etc., inputs the environment name and its description. For example, the person in charge, etc., inputs information such as "Seaside Terrace on the Coast Road" as the environment name and "An area centered around the seaside terrace on B Coast Road" as the description.

[0213] The definition control unit 206 calculates the similarity between the environment name and description for the newly acquired environment and the environment name and description for the already acquired environment, and identifies an existing environment close to the new environment.

[0214] For example, the definition control unit 206 vectorizes the text data of the environment name and description. For example, the definition control unit 206 vectorizes the text data using an existing embedding model such as Word2Vec, FastText, or GloVe.

[0215] The definition control unit 206 calculates the similarity between the vector of the new environment and the vector of the existing environment. The definition control unit 206 calculates metrics such as cosine similarity and Euclidean distance. The definition control unit 206 identifies the existing environment with the highest similarity.

[0216] Alternatively, the definition control unit 206 may estimate the similarity (degree of similarity) between the existing environment and the new environment using a learning model obtained by machine learning. For example, the similarity may be estimated using a learning model called graph AI (Artificial Intelligence).

[0217] The definition control unit 206 generates the GUI shown in FIG. 21 using the environment definition, etc. related to the identified existing environment. Specifically, the definition control unit 206 displays a list of environmental components described in the existing environment definition and provides an interface that enables the person in charge to select environmental components that are considered necessary for the new environment from among the list display. At that time, the definition control unit 206 may provide an interface that allows new environmental components to be added.

[0218] Alternatively, the definition control unit 206 may provide an interface that enables selection of a community suitable for the new environment from among communities of similar environments or an interface for adding a new community with respect to the community of the environment.

[0219] The definition control unit 206 generates component-related definitions as shown in FIG. 10 using the acquired new environmental components, communities, etc. For example, when it is determined that the "event" shown in FIG. 10 is unnecessary for the new environment, the definition control unit 206 generates a component-related definition excluding the event as the definition of the new environment.

[0220] In this way, the definition control unit 206 of the distribution control server 10 acquires component-related definitions regarding the predetermined environment (for example, Open Terrace A) from a service provider who manages the predetermined environment. When the service provider sets a new environment, the definition control unit 206 supports the service provider in setting the new environment using the previously acquired component-related definitions.

[0221] <Modification Example 2> The circulation control server 10 may modify (tune) the action definitions for each purpose and the definitions related to components using the new action data generated by the services provided using the action data with environmental data attached. For example, the circulation control server 10 may use a method such as reinforcement learning to estimate the actions for each purpose that are insufficient in the definitions related to components, etc., and add the estimated actions for each purpose to the definitions related to components, etc. For example, when the user modifies a diary, the actions (actions for each purpose) corresponding to the modified items may be added to the definitions related to components.

[0222] As described above, in the information circulation system according to the first embodiment, when the circulation control server 10 acquires and accumulates the action data (schedules, achievements) of the user, it acquires the environmental data related to the action data (schedules, achievements) from an external server. The circulation control server 10 stores the acquired environmental data and action data in association with each other. The stored action data becomes the target of data circulation, and service providers can obtain the action data with environmental data attached through data sharing. That is, the information circulation system according to the first embodiment incorporates and manages the non-personal data (environmental data) related to a part of the action data (personal data), thereby facilitating personalization when service providers provide services.

[0223] Also, when realizing the above data linkage, the distribution control server 10 refers to the component-related definitions. The component-related definitions describe the environment, customer community, purpose, actions by purpose, etc. By referring to such component-related definitions, the distribution control server 10 can obtain environmental data closely related to the actions of the users. That is, it is assumed that there are multiple communities in a given environment, and there are characteristics (biases) in the purpose and actions of using the environment for each community. Under such an assumption, by setting not only the actions of the users but also the communities, etc. in the component-related definitions, more useful environmental data can be obtained. Thus, in the first embodiment, since the customer community and the purpose of the users are defined, the distribution control server 10 can obtain optimal environmental data in which the biases regarding the actions of different users are considered according to the purpose, etc.

[0224] In addition, the action data accumulated in the system includes action data regarding the schedule of the users and action data regarding the achievements of the users. These two types of action data are shared with other service providers. That is, a service provider who can obtain either one of the action data (schedule) and the action data (achievements) can obtain the other action data that it cannot obtain through data sharing. As a result, a cooperation system among service providers is established.

[0225] Furthermore, the service provider can provide services using the action data attached with environmental data. That is, the service provider can feedback the decisions of the users to the system, such as the recommendation function and diary generation function of Application A. Such feedback enables the tuning of the action definitions by purpose and the component-related definitions.

[0226] Subsequently, the hardware of each device constituting the information distribution system will be described. FIG. 22 is a diagram showing an example of the hardware configuration of the distribution control server 10.

[0227] The distribution control server 10 can be configured by an information processing device (so-called computer) and has the configuration illustrated in FIG. 22. For example, the distribution control server 10 includes a processor 311, a memory 312, an input / output interface 313, a communication interface 314, and the like. The components such as the processor 311 are connected by an internal bus or the like and are configured to communicate with each other.

[0228] However, the configuration shown in FIG. 22 is not intended to limit the hardware configuration of the distribution control server 10. The distribution control server 10 may include hardware not shown, or may not include the input / output interface 313 as necessary. Also, the number of components such as the processor 311 included in the distribution control server 10 is not intended to be limited to the example shown in FIG. 22. For example, a plurality of processors 311 may be included in the distribution control server 10.

[0229] The processor 311 is, for example, a programmable device such as a CPU (Central Processing Unit), an MPU (Micro Processing Unit), or a DSP (Digital Signal Processor). Alternatively, the processor 311 may be a device such as an FPGA (Field Programmable Gate Array) or an ASIC (Application Specific Integrated Circuit). The processor 311 executes various programs including an operating system (OS; Operating System).

[0230] The memory 312 is a RAM (Random Access Memory), a ROM (Read Only Memory), an HDD (Hard Disk Drive), an SSD (Solid State Drive), or the like. The memory 312 stores an OS program, an application program, and various data.

[0231] The input / output interface 313 is an interface for a display device and an input device (not shown). The display device is, for example, a liquid crystal display or the like. The input device is a device that receives user operations such as a keyboard and a mouse.

[0232] The communication interface 314 is a circuit, a module, or the like that communicates with other devices. For example, the communication interface 314 includes a NIC (Network Interface Card) or the like.

[0233] The functions of the distribution control server 10 are realized by various processing modules. The processing modules are realized, for example, when the processor 311 executes a program stored in the memory 312. Also, the program can be recorded on a computer-readable storage medium. The storage medium can be a non-transitory one such as a semiconductor memory, a hard disk, a magnetic recording medium, or an optical recording medium. That is, the present invention can also be embodied as a computer program product. Further, the above program can be downloaded via a network or updated using a storage medium storing the program. Furthermore, the above processing module may be realized by a semiconductor chip.

[0234] Note that the service server 20 or the like can also be configured by an information processing device in the same manner as the distribution control server 10, and its basic hardware configuration is the same as that of the distribution control server 10, so the description thereof is omitted.

[0235] The distribution control server 10, which is an information processing device, is equipped with a computer, and the functions of the distribution control server 10 can be realized by causing the computer to execute a program. Also, the distribution control server 10 executes the control method of the distribution control server 10 according to the program.

[0236] [Modification Example] Note that the configuration, operation, etc. of the information distribution system described in the above embodiment are examples, and are not intended to limit the configuration of the system or the like.

[0237] A service provider that requires user behavior data with environmental data transmits a sharing request to the distribution control server 10 and acquires the user behavior data with the environmental data. At this time, the distribution control server 10 may transmit a sharing instruction to the service server 20 (for example, the service server 20 in City A) that stores the user behavior data with the environmental data, or may directly transmit the user behavior data accumulated in its own device to the data sharing destination.

[0238] In the above embodiment, the case where an account management database or the like is configured inside the distribution control server 10 has been described, but the database may be constructed in an external database server or the like. That is, some functions of the distribution control server 10 may be implemented in another server. More specifically, as long as the "data sharing control unit (data sharing control means)" or the like described above is implemented in any device included in the system.

[0239] The form of data transmission and reception between each device (distribution control server 10, service server 20, etc.) is not particularly limited, but the data transmitted and received between these devices may be encrypted. Between these devices, personal information of users and the like are transmitted and received, and in order to appropriately protect these information, it is desirable that encrypted data be transmitted and received.

[0240] In the flowcharts (flowcharts, sequence diagrams) used in the above description, a plurality of steps (processes) are described in order, but the execution order of the steps executed in the embodiment is not limited to the described order. In the embodiment, for example, each process can be executed in parallel, and the order of the illustrated steps can be changed within a range that does not affect the content.

[0241] The above-described embodiments have been described in detail to facilitate the understanding of the disclosure of the present application, and it is not intended that all the configurations described above are necessary. Further, when a plurality of embodiments are described, each embodiment may be used alone or in combination. For example, it is possible to replace a part of the configuration of one embodiment with the configuration of another embodiment, or to add the configuration of another embodiment to the configuration of one embodiment. Furthermore, it is possible to add, delete, or replace other configurations for a part of the configuration of one embodiment.

[0242] From the above description, the industrial applicability of the present invention is clear. However, the present invention is preferably applicable to an information distribution system that distributes accumulated data related to services provided to users.

[0243] Some or all of the above-described embodiments may be described as follows in the appended claims, but are not limited thereto. [Appendix 1] A first service server that stores behavior data related to the behavior of a user; A second service server that stores a plurality of environment data related to a predetermined environment; A distribution control server that controls data sharing of personal data including the behavior data of the user; including The first service server transmits the behavior data to the distribution control server in order to make the behavior data a target of the data sharing. The distribution control server accumulates the received behavior data, and transmits an acquisition environment data requirement that defines a requirement for environment data necessary to be acquired from the plurality of environment data according to the received behavior data to the second service server. The second service server extracts the environment data that matches the acquired acquisition environment data requirement from the plurality of environment data, and transmits the extracted environment data to the distribution control server. The distribution control server stores the accumulated behavior data and the received environment data in association with each other. A system. [Appendix 2] The circulation control server stores the association between the actions of the user and the acquired environmental data requirements as a component-related definition, and when accumulating the received action data, specifies the acquired environmental data requirements corresponding to the received action data by referring to the component-related definition. The system according to Appendix 1. [Appendix 3] The component-related definition stores the acquired environmental data requirements for each of the actions related to the planned actions performed by the user and the actions related to the achievements made by the user. The system according to Appendix 2. [Appendix 4] The first service server acquires the action data with the environmental data attached thereto from the circulation control server. The system according to Appendix 1. [Appendix 5] The first service server provides a service to the user using the action data with the acquired environmental data attached thereto, and transmits new action data generated by the result of providing the service to the user to the circulation control server. The system according to Appendix 4. [Appendix 6] The circulation control server acquires the component-related definition from a service provider who manages the predetermined environment. The system according to any one of Appendices 1 to 5. [Appendix 7] When the service provider sets a new environment, the circulation control server uses the acquired component-related definition to assist the service provider in setting the new environment. The system according to Appendix 6. [Appendix 8] A first service server that stores action data related to the actions of a user, a second service server that stores a plurality of environmental data related to a predetermined environment, a circulation control server that controls data sharing of personal data including the action data of the user, in a system including To make the action data subject to the data sharing, the action data is transmitted to the distribution control server, accumulate the received action data, and transmit acquisition environment data requirements that define the requirements for the environmental data that needs to be acquired from among the plurality of environmental data according to the received action data to the second service server, extract the environmental data that matches the acquired acquisition environment data requirements from among the plurality of environmental data, and transmit the extracted environmental data to the distribution control server, A method of associating and storing the accumulated action data and the received environmental data.

[0244] In addition, part or all of the configurations described in Appendices 2 to 7 that are subordinate to Appendix 1 described above may be subordinate to Appendix 8 in the same subordinate relationship as Appendices 2 to 7. Furthermore, not limited to Appendices 1 and 8, within the scope not departing from the above-described embodiments, similarly, for various hardware, software, various recording means for recording software, or systems, part or all of the configurations described as appendices may be made subordinate.

[0245] It should be noted that each disclosure of the above-cited prior art documents is incorporated herein by reference. As described above, the embodiments of the present invention have been described, but the present invention is not limited to these embodiments. It will be understood by those skilled in the art that these embodiments are merely illustrative and that various modifications can be made without departing from the scope and spirit of the present invention. That is, the present invention naturally includes various modifications and corrections that can be made by those skilled in the art in accordance with the entire disclosure including the claims and the technical idea.

Explanation of Reference Numerals

[0246] 10 Distribution control server 20 Service server 20-1 Service server 20-2 Service server 30 Terminal 101 First service server 102 Second service server 103 Distribution control server 201 Communication control unit 202 User registration unit 203 ID linkage unit 204 Location information management unit 205 Data sharing control unit 206 Definition control unit 207 Data linkage control unit 208 Memory unit 301 Communication control unit 302 ID linkage control unit 303 Data storage control unit 304 Data sharing unit 305 Data acquisition unit 306 Environmental data control unit 307 Memory unit 311 Processor 312 Memory 313 Input / output interface 314 Communication interface

Claims

1. A first service server that stores behavior data related to the behavior of a user, A second service server that stores a plurality of environment data related to a predetermined environment, A distribution control server that controls data sharing of personal data including the behavior data of the user, Including, The first service server transmits the behavior data to the distribution control server in order to make the behavior data subject to the data sharing, The distribution control server accumulates the received behavior data, and transmits an acquisition environment data requirement that defines a requirement for environment data that needs to be acquired from among the plurality of environment data according to the received behavior data to the second service server, The second service server extracts the environment data that matches the acquired acquisition environment data requirement from the plurality of environment data, and transmits the extracted environment data to the distribution control server, The distribution control server stores the accumulated behavior data and the received environment data in association with each other, a system.

2. The distribution control server, Stores the association between the behavior of the user and the acquisition environment data requirement as a component-related definition, When accumulating the received behavior data, the system according to claim 1, wherein the acquisition environment data requirement corresponding to the received behavior data is specified with reference to the component-related definition.

3. The system according to claim 2, wherein the component-related definition stores the acquisition environment data requirement for each of the behavior related to the plan made by the user and the behavior related to the achievement made by the user.

4. The system according to claim 1, wherein the first service server acquires the behavior data attached with the environment data from the distribution control server.

5. The system according to claim 4, wherein the first service server provides a service to the user using the behavior data attached with the acquired environment data, and transmits new behavior data generated by the result of providing the service to the user to the distribution control server.

6. The system according to any one of claims 1 to 5, wherein the distribution control server acquires the component-related definition from a service provider that manages the predetermined environment.

7. The system according to claim 6, wherein the distribution control server supports the service provider in setting the new environment by using the obtained component-related definition when the service provider sets a new environment.

8. A first service server that stores behavior data regarding the behavior of a user; A second service server that stores a plurality of environment data regarding a predetermined environment; A distribution control server that controls data sharing of personal data including the behavior data of the user; In a system including: Transmitting the behavior data to the distribution control server in order to make the behavior data a target of the data sharing; Accumulating the received behavior data, and transmitting acquisition environment data requirements that define requirements for environment data that needs to be acquired from among the plurality of environment data according to the received behavior data to the second service server; Extracting the environment data that matches the acquired acquisition environment data requirements from among the plurality of environment data, and transmitting the extracted environment data to the distribution control server; A method of associating and storing the accumulated behavior data and the received environment data.

Images