Data Management System

Abstract

To provide a data management system that improves user convenience. [Solution] The data management system according to the embodiment is characterized by comprising: a data storage means that stores health-related data acquired from each of the sensors installed in plumbing equipment in multiple facilities, in association with the account information used to acquire the data from among multiple account information held by the user; and an account management means that manages the multiple account information stored in the data storage means in association with each other.

Description

Technical Field

[0001] The disclosed embodiments relate to a data management system.

Background Art

[0002] Techniques for acquiring and managing data related to a user's health from sensors provided in plumbing facilities are known (for example, Patent Document 1). In such a system, the data acquired from the sensors is accumulated in a state associated with the user.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, there is room for improvement in the above prior art. For example, plumbing facilities such as toilets, bathrooms, washrooms, and kitchens are installed in a building, and accounts associated with the facilities may be created for each location, resulting in multiple accounts associated with the facilities. In such a situation, even though the same person is measuring data related to their own health, the data may not be treated as the data of the same person because the accounts are different. Therefore, it is desired to manage the data related to the health of the same person in a unified manner and improve the convenience for the user.

Means for Solving the Problems

[0005] A management system according to one embodiment of the system is characterized by comprising: a data storage means that stores health-related data acquired from each of the sensors installed on plumbing equipment in multiple facilities, in association with the account information used to acquire the data from among multiple account information held by the user; and an account management means that manages the multiple account information stored in the data storage means in association with each other.

[0006] According to a management system in one embodiment, even if a user has multiple accounts and each account is associated with data to be managed, the multiple accounts held by the user are linked, thereby enabling centralized management of health data for the same person and improving user convenience.

[0007] A management system according to one embodiment further comprises a data output means that outputs the managed data stored in the data storage means to the terminal device 10 based on an operation on the terminal device 10, wherein the data output means includes a first output mode that outputs managed data relating to health associated with a first account information held by the user based on a first operation from the terminal device 10, a second output mode that outputs managed data relating to health associated with a second account information held by the user based on a second operation from the terminal device 10, and a third output mode that outputs managed data relating to health associated with the first account information and the second account information held by the user based on a third operation from the terminal device 10.

[0008] According to a management system in one embodiment, in response to operations from a terminal device 10 such as a smartphone or PC, it is possible to check the health-related data associated with the first account, the health-related data associated with the second account, and the health-related data associated with both the first and second accounts. Therefore, even if a user has multiple accounts, it is possible to check the user's health-related data in a unified manner, thereby improving user convenience.

[0009] A management system according to one embodiment further comprises an account registration means for registering new account information held by the user to the account management means, wherein the account management means manages the plurality of account information stored in the data storage means in association with the new account information.

[0010] According to a management system in one embodiment, after a user has started linking multiple accounts, it is possible to add accounts linked to other devices or newly introduced accounts later, and health-related data linked to each account, including the added accounts, can be centrally managed, thereby improving user convenience.

[0011] In a management system according to one embodiment, the managed data is characterized in that it includes any or more of the following: excrement data acquired by sensors of devices installed in the equipment, vital data of users using the equipment, operation data of the control unit that operates the devices installed in the equipment, usage history data of the devices installed in the equipment used by users, data on food and beverages acquired by the equipment, and data from the door opening and closing sensors of the equipment.

[0012] According to one embodiment of the management system, it is possible to handle various types of information obtained from various types of plumbing equipment, and therefore, a highly versatile management system can be provided that can manage sensor data that is expected to be acquired by sensors when each piece of equipment is increasingly IoT (Internet of Things).

[0013] In a management system according to one embodiment, the account information held by the user is characterized in that it is either personal account information acquired by the user or organizational account information individually assigned to the user.

[0014] According to a management system in one embodiment, health-related data associated with each account, including not only accounts acquired by the user personally but also accounts issued to the user by, for example, a sports gym or company to which the user belongs, can be centrally managed, thereby improving user convenience.

[0015] A management system according to one embodiment is further characterized by comprising an account deletion means for deleting one or more of the multiple account information held by the user from the account management means.

[0016] According to a management system in one embodiment, even when health-related data is linked to each account and multiple accounts are associated with each other, it is possible to delete only the information of a specific account, thereby improving user convenience.

[0017] A management system according to one embodiment is characterized by comprising an account update means that adds the health-related managed data associated with the account information deleted by the account deletion means to the health-related managed data associated with other account information held by the user.

[0018] According to a management system in one embodiment, managed data associated with deleted account information can be consolidated with other account information, improving user convenience. For example, even in situations where a specific account must be deleted, such as when a user leaves the company that issued the account, the managed data associated with the deleted account can be added to the managed data associated with other accounts, preventing the loss of managed data and improving user convenience.

[0019] A management system according to one embodiment is characterized by comprising: an account registration means for registering new account information held by the user to the account management means; and an account migration means for transferring the health-related data associated with the account information deleted by the account deletion means to the new account information.

[0020] According to a management system in one embodiment, the managed data associated with a deleted account is associated with a newly registered account, thereby improving user convenience. For example, if an account is an email address and the email address is changed, the old email address can be deleted and the managed data can be migrated to the new email address. Also, if an account is an ID issued by a sports gym and a new ID is issued by the changed sports gym, it is possible to transfer the managed data acquired at the previous sports gym. [Effects of the Invention]

[0021] According to one embodiment, health data of the same person can be managed centrally. [Brief explanation of the drawing]

[0022] [Figure 1] Figure 1 shows an example of the configuration of a data management system according to the embodiment. [Figure 2] Figure 2 is a diagram illustrating the processing overview of the data management system according to the embodiment. [Figure 3] Figure 3 is a diagram for explaining the outline of processing of the data management system according to the embodiment. [Figure 4] Figure 4 is a diagram for explaining the outline of processing of the data management system according to the embodiment. [Figure 5] Figure 5 is a diagram for explaining the outline of processing of the data management system according to the embodiment. [Figure 6] Figure 6 is a block diagram showing an example of the configuration of the data management apparatus according to the embodiment. [Figure 7] Figure 7 is a table diagram showing an example of information stored in the user storage unit according to the embodiment. [Figure 8] Figure 8 is a table diagram showing an example of information stored in the data storage unit according to the embodiment. [Figure 9] Figure 9 is a diagram showing an example of management processing by the data management system according to the embodiment. [Figure 10] Figure 10 is a diagram showing an example of the process of adding account information by the data management system according to the embodiment. [Figure 11] Figure 11 is a diagram showing an example of deletion processing by the data management system according to the embodiment. [Figure 12] Figure 12 is a diagram showing an example of update processing by the data management system according to the embodiment. [Figure 13] Figure 13 is a diagram showing an example of transfer processing by the data management system according to the embodiment. [Figure 14] Figure 14 is a diagram showing an example of output processing by the data management system according to the embodiment.

Embodiments of the Invention

[0023] <1. Embodiment> Hereinafter, embodiments of the present invention will be described with reference to the drawings. In each drawing, the same components are denoted by the same reference numerals, and detailed descriptions thereof are omitted as appropriate.

[0024] <1-1. Overview of processing by the data management system> First, an example of the configuration of the data management system 1 according to the embodiment will be described with reference to Figure 1. Figure 1 is a diagram illustrating an example of the configuration of the data management system according to the embodiment. The data management system 1 is a system that manages user health data acquired by sensors installed in water facilities such as toilets, bathrooms, kitchens, and washrooms. The data management system 1 has a plurality of sensor devices 5-1 to 5-n, a terminal device 10, and a data management device 100. Each component is connected to communicate via wired or wireless means.

[0025] Sensor device 5 is installed in water-related facilities such as toilets, bathrooms, kitchens, and washrooms, and is equipped with various sensors for acquiring sensor data, which is data to be managed regarding the user's health. Sensor data includes excrement data, which is data on the user's excrement; vital data, which is the user's biological data; operation data of devices installed in water-related facilities; usage history data of devices installed in water-related facilities; door opening and closing data for water-related facilities; and data related to food and drink.

[0026] Sensor device 5 is installed, for example, in a toilet and has various sensors such as a stool sensor, a blood flow sensor, and a door opening / closing sensor. For example, the stool sensor of sensor device 5 is a sensor that images stool using a line sensor, camera, etc. In this case, the stool sensor of sensor device 5 images the stool (sometimes simply referred to as "stool") excreted by the user and generates an image including the user's stool. Any sensor capable of detecting the target data item can be used in sensor device 5. For example, the stool sensor of sensor device 5 may be a two-dimensional image sensor capable of detecting at least one of the characteristics of stool, such as color, shape, and quantity.

[0027] Furthermore, the stool sensor can detect the user's urine. For example, the stool sensor may detect the color, amount, etc., of the user's urine. In this case, the sensor device 5 will detect urine data, and the sensor data may include urine data. Note that the analysis of the sensor data, such as the determination of stool characteristics, may be performed by the sensor device 5 or by the data management device 100.

[0028] The above is merely an example, and the sensor device 5 may have various other sensors. For example, the sensor device 5 installed in a toilet may have a sensor that detects sitting on the toilet seat (seat detection sensor). Also, for example, the sensor device 5 may have a sensor that detects the user's vital data in the plumbing. For example, the sensor device 5 may have sensors that detect vital data such as the user's blood flow, heart rate (pulse), respiration, body temperature, brain waves, and muscle activity (electromyography). For example, when the sensor device 5 detects the user's blood flow in a toilet, it may have a blood flow sensor installed on the toilet seat of the toilet device 50.

[0029] Sensor device 5 has sensors that detect the use of plumbing fixtures. For example, sensor device 5 has a human body detection sensor that detects whether or not a person is present in the toilet. Sensor device 5 also has sensors that detect the operation of devices installed in plumbing fixtures. For example, sensor device 5 has a sensor that detects the operation of a remote control, which is an operating unit for operating the toilet equipment.

[0030] Furthermore, the sensor device 5 has an entry detection sensor for collecting information on users entering and leaving water-related facilities. For example, the sensor device 5 has a door opening / closing sensor for detecting the opening and closing of the toilet door. In addition to the above example, it may have various other sensors for collecting sensor data in water-related facilities.

[0031] Water-related facilities are not limited to the user's residence; they may also be installed in buildings or other facilities. While the above example shows the sensor device 5 being placed in a toilet, the sensor device 5 is not limited to toilets; it can be placed in any water-related facility such as a bathroom, kitchen, or washroom. Furthermore, the type of sensor device 5 may be appropriately selected depending on the water-related facility.

[0032] If the plumbing fixtures are located in the bathroom, for example, vital data can be detected by a blood flow sensor installed in the bathroom. Operation data can be detected by a remote control installed in the bathroom. Usage history data can be detected by sensors that measure the amount of water used and the water temperature.

[0033] If the plumbing fixtures are in the kitchen, operation data is detected by a remote control or similar device installed in the kitchen. Usage history data is detected by a door open / close sensor or similar device that detects the opening and closing of the refrigerator door. Furthermore, food and beverage data is detected by cameras or scales installed inside the refrigerator or on the countertop. Food and beverage data may include items such as the estimated amount of food, the type of dish, and the nutrients contained in the cooked food, based on the ingredients detected by the cameras or scales.

[0034] If the plumbing fixtures are located in the bathroom, for example, vital data can be detected by a blood flow sensor installed in the bathroom. Operation data can be detected by a remote control installed in the bathroom. Usage history data can be detected by a sensor that measures the amount of water used.

[0035] The sensor device 5 transmits sensor data collected by detection from various sensors it possesses to the data management device 100 or the terminal device 10. For example, the sensor device 5 transmits various water-related sensor data, such as toilet sensor data, to the terminal device 10.

[0036] Terminal device 10 is an information processing device used by the user. Terminal device 10 can be implemented as, for example, a smartphone, a mobile phone, a PDA (Personal Digital Assistant), a tablet device, or a notebook PC (Personal Computer). Terminal device 10 communicates with sensor device 5 and acquires sensor data from sensor device 5. Terminal device 10 also communicates with data management device 100 and transmits the acquired sensor data to data management device 100. In the example shown in Figure 1, terminal device 10 is shown as a smartphone used by the user.

[0037] The data management device 100 is an information processing device that manages sensor data detected by the sensor device 5. The data management device 100 stores the sensor data acquired by the terminal device 10 from the sensor device 5, associating it with the account information used when the terminal device 10 acquired the sensor data. The data management device 100 may also be a cloud server (server device).

[0038] Account information can be obtained by individuals of their own free will or unintentionally. Therefore, account information may include, for example, personal account information obtained by a user, or organizational account information created and individually assigned by an organization.

[0039] Next, we will explain the challenges present in conventional data management systems with reference to Figures 2 and 3. Figures 2 and 3 illustrate examples of challenges present in conventional data management systems. Figure 2 shows an example where a user has multiple accounts, and sensor data is acquired and stored using different accounts for each location. Figure 2(1) shows the database where sensor data acquired using an individual account is stored. Figure 2(2) shows the database where sensor data acquired using a group account is stored.

[0040] As shown in Figure 2, plumbing facilities such as toilets, bathrooms, kitchens, and washrooms are installed both at the user's home and in different locations, such as in the building where the user works (e.g., Company Q). Furthermore, user A's account is created separately for each location and linked to the specific facility. Therefore, at home, user A uses their own personal account "ID:aaa@********.com" to obtain sensor data from the plumbing facilities at their home, while at Company Q, user A uses the group account "ID:Taro.aaa@******.com" created and assigned by Company Q to obtain sensor data from the plumbing facilities at Company Q. Note that Company Q includes multiple subsidiaries, such as Company (Chigasaki) and Company (Shiodome).

[0041] In this situation, even though the same person is measuring their own health data, different accounts are used to acquire the data, resulting in the acquired data being associated and stored with each account. For example, sensor data acquired from the plumbing fixtures at home is associated with the personal account "ID:aaa@********.com" and stored in the database shown in Figure 2(1). On the other hand, sensor data acquired from the plumbing fixtures of Company Q is associated with the organization account "ID:Taro.aaa@********.com" and stored in the database shown in Figure 2(2).

[0042] The databases shown in Figures 2(1) and 2(2) store information on "account," "location," "date and time," and "acquired data." "Account" indicates the account information used to acquire the sensor data. "Location" indicates the location where the sensor data was acquired. "Date and time" indicates the date and time when the sensor data was acquired. "Acquired data" indicates the content of the sensor data detected by the sensor. For example, if sensor data is acquired from a toilet, the "acquired data" includes item information such as "stool condition," which indicates the state of the stool based on the color, shape, and amount of stool; "gas condition," which indicates the state of the gas based on the composition of the gaseous components of the gas; and "vitals," which indicates biological information based on pulse rate data, etc., and the state is represented by symbols such as ○△×.

[0043] As shown in Figure 2(1), the database stores information such as, for example, "Account: aaa@******.com, Location: Home, Date and Time: July 4th, 7:30 AM, Stool Status: △, Gas Status: △, Vitals: ○, ...". Similarly, the database shown in Figure 2(2) stores information such as, for example, "Account: Taro.aaa@********.com, Location: Company (Chigasaki), Date and Time: July 4th, 10:00 AM, Stool Status: ○, Gas Status: ○, Vitals: △, ...". In this way, each database stores sensor data associated with specific account information.

[0044] Next, Figure 3 shows the information that can be viewed for each account in the example in Figure 2. Figure 3(1) shows an example of a table-format sensor data viewable when logged in with an individual account in Figure 2, and an example of a graph of sensor data with the vertical axis representing state and the horizontal axis representing time. Figure 3(2) shows an example of a table-format sensor data viewable when logged in with an organization account in Figure 2, and an example of a graph of sensor data with the vertical axis representing state and the horizontal axis representing time.

[0045] In the sensor data graphs in Figures 3(1) and 3(2), each item of acquired data is indicated by a symbol: stool condition: ○, gas condition: ◇, vital signs: ▽. The vertical axis of the sensor data graph is divided into areas: ◎ indicating very good condition, ○ indicating good condition, and △ indicating poor condition. The table-formatted sensor data in Figure 3(1) is identical to the information stored in the database in Figure 2(1). Similarly, the table-formatted sensor data in Figure 3(2) is identical to the information stored in the database in Figure 2(2).

[0046] Conventional data management systems only store sensor data linked to the account information used to acquire that data, meaning that the information that can be viewed differs depending on the account used for login. For example, if user A logs in with the "Personal Account: aaa@******.com" shown in Figure 3(1), user A cannot view the data acquired using the other account, "Organization Account: Taro.aaa@******.com," or the graphs based on that data. On the other hand, if user A logs in with the "Organization Account: Taro.aaa@******.com" shown in Figure 3(2), user A cannot view the data acquired using the other account, "Personal Account: aaa@******.com," or the graphs based on that data.

[0047] In other words, in the example in Figure 3, although four managed data items for user A were retrieved on July 4th, because the retrieved accounts were separate, user A can only view two managed data items at a time when logging in with either a personal or organizational account, making it impossible to view user A's managed data in accurate chronological order.

[0048] Thus, when users utilize multiple accounts, even though all the data associated with each account belongs to them, they are unable to view data associated with other accounts because the accounts are different, resulting in low user convenience. Therefore, there was a need to centrally manage health data for the same person to improve user convenience.

[0049] Therefore, the data management system 1 according to this embodiment stores the health-related data acquired from each of the sensors installed in the plumbing equipment present in multiple facilities, associating it with the account information used to acquire the data from among the multiple account information held by the user, and manages the multiple account information in association with each other.

[0050] Here, with reference to Figure 4, an overview of the processing by the data management system 1 according to the embodiment will be explained. Figure 4 is a diagram illustrating the overview of the processing by the data management system according to the embodiment. Figure 4 shows the flow of sensor data acquisition, storage, and user viewing by the data management system 1.

[0051] In the example shown in Figure 4, user A has three accounts: personal account A, which he / she created; group account B, which was created and assigned to him / her by company Q; and group account C, which was created and assigned to him / her by the gym. Here, the data management device 100 manages the multiple account information held by user A, namely personal account A, group account B, and group account C, by associating them with each other.

[0052] When user A uses the plumbing equipment, the data management system 1 performs personal authentication to identify the account information used to acquire sensor data. For example, the data management system 1 identifies the account information used to acquire sensor data from the sensor device 5 by having the terminal device 10 owned by user A and the sensor device 5 communicate using technologies such as BLE (Bluetooth Low Energy). The method of personal authentication by the data management system 1 is not particularly limited to the above example, as long as it is a method that can identify the account information using the sensor device 5 and the terminal device 10.

[0053] Each account is associated with a specific location. For example, individual account A is associated with home, group account B is associated with company Q, and group account C is associated with a gym. Note that each account may also be used to acquire sensor data from a location different from the one it is associated with.

[0054] For example, at home, terminal device 10 uses personal account A to acquire sensor data from sensor device 5 and transmits the acquired sensor data to the cloud (data management device 100). In this case, the transmission of sensor data may be done via a router installed at home.

[0055] Furthermore, in public spaces such as companies, schools, hospitals, and gyms, the terminal device 10 uses the location-specific group account B or group account C to acquire sensor data from the sensor device 5 and transmit the acquired sensor data to the cloud. In this case, the transmission of sensor data may be performed via a gateway installed in the public space.

[0056] The data management device 100 stores the transmitted sensor data in association with account information. For example, sensor data acquired using individual account A is associated with individual account A and stored in individual account A's database. Similarly, sensor data acquired using group account B is associated with group account B and stored in group account B's database. Furthermore, sensor data acquired using group account C is associated with group account C and stored in group account C's database. The data management device 100 may also communicate with other clouds based on the account information and associate it with account information stored in those other clouds.

[0057] User A, who holds personal account A, can view their own sensor data stored in the database, as well as analysis results such as statistics and trends of the sensor data. The analysis results of the sensor data may be cloud-processed on a cloud server, or they may be edge-processed by analyzing information captured by terminal device 10.

[0058] Since the multiple accounts held by User A are linked, for example, if User A logs in using personal account A, User A can view not only the sensor data associated with personal account A, but also the sensor data associated with organization account B and organization account C. Furthermore, not only User A, who is the subject of the sensor data measurement, but also others can view User A's sensor data, such as the company administrator who manages the company User A belongs to, the industrial physician who provides guidance to User A's company, the gym staff of the gym User A contracts with, and the administrator of the cloud server where User A's managed data is stored.

[0059] Next, with reference to Figure 5, an example of data viewable by the data management system 1 according to the embodiment is shown. Figure 5 is a diagram showing an example of data viewable by the data management system according to the embodiment. Figure 5 shows information that can be viewed when multiple accounts are associated. Figure 5(1) shows the accounts held by user A. Figure 5(2) shows the data obtained by the account information of personal account A, group account B, and group account C held by user A. For example, Figure 5(2) shows the information stored in each database where the sensor data obtained by each account information is linked and stored, in the example of Figure 4. Figure 5(2) has a similar configuration to the database in Figure 3.

[0060] In the example in Figure 3, where the account information is not linked to each other, user A could only view sensor data associated with the account information used to log in. However, in the example in Figure 5, the data management system 1 manages and links each of user A's accounts, enabling user A to view data stored in association with multiple account information held by user A, as shown in Figure 5.

[0061] As a result, even if user A has multiple accounts such as "aaa@******.com", "Taro.aaa@******.com", and "aaa.gym@******.co.jp", and each account is associated with managed data, the data management system 1 associates the multiple accounts that user A has. Therefore, no matter which account user A logs in with, they can also view the health-related managed data associated with accounts that user A does not use to log in.

[0062] For example, in Figure 5, data for user A is acquired at five locations: home, company (Chigasaki), company (Shiodome), Gym A, and home. However, the data management system 1 makes it possible to accurately grasp the data for user A acquired over a one-day period in chronological order, regardless of the data measurement location.

[0063] In other words, it enables centralized management of health data for the same person, improving user convenience. Furthermore, because the data management system 1 centrally manages data even if the location where the sensor data was acquired or the account used to acquire the sensor data is different, it makes it possible to track the time-series changes in the managed data related to the user's health, making health management easier.

[0064] The system configuration described above is merely an example, and the data management system 1 may have any system configuration as long as the desired processing is possible. In the following embodiments, the data management device 100 will be described as an example in which various processing is performed, but this does not limit the device that performs the processing, and other configurations of the data management system 1 may also perform these processing.

[0065] <1-2. Configuration of the Data Management Device> Next, the configuration of the data management device 100 according to the embodiment will be described with reference to Figure 6. Figure 6 is a block diagram showing an example of the configuration of the data management device according to the embodiment.

[0066] The data management device 100 includes a communication unit 110, a storage unit 120, and a control unit 130. The data management device 100 may also include an input unit (e.g., a keyboard or mouse) for receiving various operations from the administrator of the data management device 100, and a display unit (e.g., a liquid crystal display) for displaying various information.

[0067] The communication unit 110 is implemented, for example, by a communication circuit. The communication unit 110 is connected to a predetermined network, such as the Internet, by wire or wireless connection, and transmits and receives information with an external information processing device. For example, the communication unit 110 transmits and receives information with other devices having communication functions, such as the sensor device 5 and the terminal device 10, via a predetermined network, such as the Internet.

[0068] The storage unit 120 is implemented by, for example, semiconductor memory elements such as RAM (Random Access Memory) and flash memory, or by storage devices such as hard disks and optical discs. As shown in Figure 6, the storage unit 120 has a user storage unit 121 and a data storage unit 122. The individual parts of the storage unit 120 will be described below.

[0069] The user storage unit 121 stores user information. For example, the user storage unit 121 stores the user's account information. Here, an example of the information stored by the user storage unit 121 will be explained with reference to Figure 7. Figure 7 is a table diagram showing an example of the information stored by the user storage unit according to the embodiment. "User name" refers to information that identifies the user, such as name or nickname. "Account" refers to information that identifies the account held by the user, such as email address, membership number, or ID. "Account type" refers to the type of account, such as a personal account acquired by an individual and an organization account acquired by an organization and assigned to an individual. "Acquisition location" refers to the location where the health-related data was acquired. "Name" refers to the real name of the user who holds the account. "Date of birth" refers to the date of birth of the user who holds the account. "Address" refers to the address of the user who holds the account.

[0070] For example, the user memory unit 121 states that the user "Username: A" has the following accounts: "Account: aaa@******.com", "Account: Taro.aaa@******.com", and "Account: aaa.gym@******.co.jp".

[0071] The account "aaa@******.com" is associated with "Account Type: Personal Account", "Acquisition Location: Residential", and the account holder's name is "****", date of birth is "**** / ** / **", and address is "Tokyo*****". The account "Account:Taro.aaa@********.com" is associated with "Account Type: Group Account", "Acquisition Location: Company", and the account holder's name is "****", date of birth is "**** / ** / **", and address is "Tokyo*****". The account "Account:aaa.gym@******.co.jp" is associated with "Account Type: Group Account", "Acquisition Location: Gym", and the account holder's name is "****", date of birth is "**** / ** / **", and address is "Tokyo*****".

[0072] The data storage unit 122 stores various health-related data of users who use the plumbing facilities and functions as a data storage means. For example, the data storage unit 122 stores sensor data detected by the sensor device 5 installed in the toilet (including data obtained by analyzing the sensor data). The data storage unit 122 stores each piece of sensor data based on the detection by the sensor device 5, associating it with the account information used to acquire the sensor data, the date and time the sensor data was acquired, and the location where the sensor data was acquired.

[0073] Here, an example of the information stored by the data storage unit 122 will be described with reference to Figure 8. Figure 8 is a table diagram showing an example of the information stored by the data storage unit according to this embodiment. The table diagram in Figure 8 has a similar configuration to the database in Figure 3.

[0074] For example, if the plumbing facility is a toilet, the data storage unit 122 stores toilet sensor data, including excrement data such as stool data and urine data detected in the toilet, vital data, operation data, usage history data, and door opening / closing data. The data storage unit 122 stores stool data, which includes data on at least one of the following: amount, shape, color, and composition of stool; gas data, which includes data on one of the following: odorless gas, malodorous gas, etc.; vital data such as blood flow, pulse, respiration, body temperature, brain waves, and muscle activity; operation data of equipment including toilet devices installed in the toilet; usage history data of toilet devices; and door opening / closing data for the toilet entrance.

[0075] The data storage unit 122 stores various sensor data in addition to the examples above. For example, if the plumbing facility is a bathroom, the data storage unit 122 stores sensor data including vital data, operation data, and usage history data detected in the bathroom. If the plumbing facility is a washroom, the data storage unit 122 stores sensor data including vital data, operation data, and usage history data detected in the washroom. If the plumbing facility is a kitchen, the data storage unit 122 stores sensor data including operation data, usage history data, and data related to food and beverages detected in the kitchen.

[0076] The sensor data stored in the data storage unit 122 may be data analyzed by the data management device 100 or the sensor device 5. For example, excretory data such as the shape of stool, the color of stool, the amount of stool, the color of urine, the amount of urine, the flow rate of urine, and the components of urine may be generated based on images of stool or urine.

[0077] The control unit 130 is implemented, for example, by a CPU (Central Processing Unit) or GPU (Graphics Processing Unit) executing a program (for example, a data management program) stored inside the data management device 100 using RAM or the like as a working area. Alternatively, the control unit 130 can be implemented by an integrated circuit such as an ASIC (Application Specific Integrated Circuit) or FPGA (Field Programmable Gate Array).

[0078] The control unit 130 includes an acquisition unit 131, a response unit 132, a management unit 133, a registration unit 134, a deletion unit 135, an update unit 136, a migration unit 137, and an output unit 138, and realizes or executes the information processing functions and operations described below. Note that the internal configuration of the control unit 130 is not limited to the configuration shown in Figure 4, and other configurations are also acceptable as long as they perform the information processing described later.

[0079] The acquisition unit 131 receives various information from various computers such as the sensor device 5 and the terminal device 10. For example, the acquisition unit 131 acquires health-related management data and account information detected by various sensors of the sensor device 5 installed in the plumbing equipment from the sensor device 5 or the terminal device 10. For example, the acquisition unit 131 acquires health-related management data acquired from each of the sensors installed in plumbing equipment in multiple facilities. For example, the acquisition unit 131 acquires health-related management data by receiving sensor data from various sensors of the sensor device 5 in each plumbing equipment. The acquisition unit 131 may also acquire management data associated with account information from the sensor device 5 or the terminal device 10.

[0080] The acquisition unit 131 acquires sensor data from the sensor device 5 of the toilet equipment, including excrement data, vital data, operation data, usage history data, and door opening / closing data. The acquisition unit 131 also acquires sensor data from the sensor device 5 of the bathtub or control panel in the bathroom, including vital data, operation data, and usage history data. Furthermore, the acquisition unit 131 acquires sensor data from the sensor device 5 of the dressing table or faucet in the washroom, including vital data, operation data, and usage history data. In addition, the acquisition unit 131 acquires sensor data from the sensor device 5 of the refrigerator or cooking appliances in the kitchen, including operation data, usage history data, and food and beverage data.

[0081] The correspondence unit 132 stores the managed health data in association with account information. For example, the correspondence unit 132 associates the managed health data with the account information used to acquire the managed data from the account information held by the user. More specifically, the correspondence unit 132 stores the managed health data acquired by sensors such as blood flow sensors, defecation sensors, and gas sensors installed in the toilet of the house, in association with account information in the data storage unit 122. Note that the association between sensor data and account information may be performed not only by the correspondence unit 132, but also by the sensor device 5 or by the terminal device 10.

[0082] The management unit 133 manages multiple account information in association with each other. For example, the management unit 133 functions as an account management means that manages multiple account information stored in the data storage unit 122 in association with each other. Now, referring to Figure 9, the processing by the management unit 133 will be explained. Figure 9 is a diagram showing an example of processing by the management unit according to this embodiment.

[0083] First, the data management device 100 acquires sensor data detected by the sensor device 5. At this time, the acquired sensor data is stored in the data storage unit 122 in association with the account information used to acquire the sensor data. In the example in Figure 9, sensor data acquired using the first account information is stored in association with the first account information, and sensor data acquired using the second account information is stored in association with the second account information.

[0084] Next, the management unit 133, which functions as an account management means, manages multiple account information by associating them with each other. In the example in Figure 9, the management unit 133 manages the first account information and the second account information by associating them with each other. By associating the first account information and the second account information, the sensor data stored in association with the first account information and the sensor data stored in association with the second account information are managed as information of the same person.

[0085] This allows the management unit 133 to view not only the managed data associated with the specific account information, but also the managed data associated with other account information linked to that specific account information, even when a user logs in using that specific account information, thereby improving user convenience.

[0086] The management unit 133 manages the new account information by associating it with the multiple account information stored in the data storage unit 122. Now, with reference to Figure 10, the process of adding account information by the data management system 1 will be explained. Figure 10 shows an example of the process of adding account information by the data management system 1 according to this embodiment. In the example in Figure 10, the management unit 133 manages the first account information and the second account information by associating them. When a third account information is newly registered by the registration unit 134, which will be described later, the management unit 133 manages the newly registered third account information by associating it with the first account information and the second account information that have already been registered.

[0087] This allows the management unit 133 to add accounts linked to other equipment or newly introduced accounts after a user has started linking multiple accounts, and to centrally manage health-related data linked to each account, including the added accounts, thereby improving user convenience.

[0088] The registration unit 134 registers account information with the management unit 133. For example, the registration unit 134 functions as an account registration means that registers new account information held by a user with the management unit 133.

[0089] The registration unit 134 registers new account information held by the user with the management unit 133. For example, if new account information stored in the user storage unit 121 that has not been associated with the management unit 133 is used to retrieve managed data, the registration unit 134 registers the new account information with the management unit 133.

[0090] At this time, the registration unit 134 verifies whether the account information to be added belongs to the same person as the account information already registered. For example, the registration unit 134 accepts the input of the account information to be added and basic information such as name, date of birth, and address, and verifies that the account information to be added and the account information already registered belong to the same person by comparing the entered basic information with the basic information of the already registered account information. Then, if it is confirmed that the account information belongs to the same person, the registration unit 134 registers the new account information held by the user to the management unit 133.

[0091] For example, suppose user A has three accounts: "aaa@******.com", "Taro.aaa@******.com", and "aaa.gym@******.co.jp". If managed data is retrieved using the new account information, "aaa.gym@******.co.jp", then the account information "aaa.gym@******.co.jp", which is associated with the retrieved managed data, is registered in the management unit 133. The management unit 133 then associates each of the three accounts: "aaa@******.com", "Taro.aaa@******.com", and "aaa.gym@******.co.jp".

[0092] The deletion unit 135 causes the management unit 133 to delete the account information. For example, the deletion unit 135 functions as an account deletion means that deletes one or more of the multiple account information held by the user from the management unit 133. For example, the deletion unit 135 receives an operation from the user on the terminal device 10 and deletes the account information selected by the operation.

[0093] Here, the deletion process by the data management system 1 will be explained with reference to Figure 11. Figure 11 is a diagram showing an example of the deletion process by the data management system according to the embodiment. As shown in Figure 11, in a situation where the management unit 133 manages the first account information, the second account information, and the third account information in association, the deletion unit 135 deletes the second account information. At this time, the association between the first account information and the second account information that has not been deleted by the deletion unit 135 remains.

[0094] For example, in a situation where user A owns three accounts, "aaa@******.com", "Taro.aaa@******.com", and "aaa.gym@******.co.jp", which are managed in association, the deletion unit 135 will delete the "Taro.aaa@******.com" account owned by user A. Note that the deletion of an account by the deletion unit 135 means the deletion of the account information for "Taro.aaa@******.com" managed by the management unit 133, or the deletion of the account information for "Taro.aaa@******.com" stored in the user storage unit 121 and associated with other accounts. In this case, the managed data that was associated with the deleted account information "Taro.aaa@******.com" is not deleted.

[0095] As a result, the deletion unit 135 can, for example, delete only the unnecessary gym group account information when a user cancels their gym membership, in a situation where the user possesses personal account information, company group account information, and gym group account information.

[0096] The update unit 136 adds the health-related managed data associated with the account information deleted by the deletion unit 135 to the health-related managed data associated with other account information held by the user. For example, the update unit 136 functions as an account update means that adds the health-related managed data associated with the account information deleted by the deletion unit 135 to the health-related managed data associated with other account information held by the user.

[0097] For example, if account information is deleted by the deletion unit 135, the update unit 136 refers to the data storage unit 122 and associates the managed data that was associated with the deleted account information with other account information that was associated with the deleted account information.

[0098] At this time, the update unit 136 may accept the selection of account information to which health-related managed data will be added. For example, the update unit 136 accepts an operation from the user of the terminal device 10 and adds the health-related managed data associated with the deleted account information to the health-related managed data associated with the selected account information.

[0099] Here, the update process by the data management system 1 will be explained with reference to Figure 12. Figure 12 is a diagram illustrating an example of the update process by the data management system according to the embodiment. As shown in Figure 12, in a situation where the management unit 133 manages the first account information, the second account information, and the third account information in association, if the second account information is deleted by the deletion unit 135, the update unit 136 associates the managed data that was associated with the deleted second account information with the first account information or the third account information.

[0100] For example, suppose user A has three associated accounts: "aaa@******.com", "Taro.aaa@******.com", and "aaa.gym@******.co.jp", and the "Taro.aaa@******.com" account is deleted. In this case, the update unit 136 refers to the data storage unit 122 and associates the managed data that was associated with the deleted "Taro.aaa@******.com" account with the "aaa@******.com" account or the "aaa.gym@******.co.jp" account that was associated with the deleted "Taro.aaa@******.com" account in the management unit 133.

[0101] As a result, even in situations where it is necessary to delete a specific account, such as when a user leaves the company to which the account was assigned or when a user cancels their gym membership, the update unit 136 can prevent the loss of managed data by adding the managed data associated with the account to be deleted to the managed data associated with other accounts.

[0102] The migration unit 137 transfers the health-related data associated with the account information deleted by the deletion unit 135 to the new account information registered by the registration unit 134. The migration unit 137 functions as an account migration means that transfers the health-related data associated with the account information deleted by the deletion unit 135 to the new account information. For example, when account information is deleted by the deletion unit 135, the migration unit 137 refers to the data storage unit 122 and associates the data that was associated with the deleted account information with the new account information registered by the registration unit 134.

[0103] Here, the new account information from which the migration unit 137 takes over the managed data may be newly registered account information, or it may be already registered account information for which no associated managed data exists. If there are multiple new account information entries, the migration unit 137 accepts an operation from the user on the terminal device 10 and performs the transfer by associating the health-related managed data associated with the deleted account information with the selected account information.

[0104] Here, the migration process by the data management system 1 will be explained with reference to Figure 13. Figure 13 is a diagram illustrating an example of the migration process by the data management system according to the embodiment. As shown in Figure 13, in a situation where the management unit 133 manages the first account information, the second account information, and the third account information in association, when the second account information is deleted by the deletion unit 135, the migration unit 137 associates the managed data that was associated with the deleted second account information with the newly registered fourth account information.

[0105] For example, in a situation where user A owns three accounts, "aaa@******.com", "Taro.aaa@******.com", and "aaa.gym@******.co.jp", and these are managed in association, if a new account, "*****@******.com", is registered and associated with the other accounts owned by user A, and then the "Taro.aaa@******.com" account is deleted, the migration unit 137 refers to the data storage unit 122 and associates the managed data that was associated with the deleted "Taro.aaa@******.com" account with the newly registered account "*****@******.com".

[0106] As a result, the migration unit 137 associates the managed data associated with the deleted account with the newly registered account, preventing the loss of managed data when changing jobs or switching gyms, and allowing users to retrieve managed data in the migrated account by carrying over data acquired in the account before the migration, thereby improving user convenience.

[0107] The output unit 138 outputs the managed data to the terminal device 10. For example, the output unit 138 displays the managed data stored in the data storage unit 122 on the display of the terminal device 10. The output unit 138 functions as a data output means that outputs the managed data stored in the data storage unit 122 to the terminal device 10 based on operations performed on the terminal device 10.

[0108] The output unit 138 includes first to third output modes that output different managed data based on operations such as pressing a button on the terminal device 10. For example, the output unit 138 includes a first output mode that outputs managed health data associated with a first account information held by the user based on a first operation from the terminal device 10, a second output mode that outputs managed health data associated with a second account information held by the user based on a second operation from the terminal device 10, and a third output mode that outputs managed health data associated with the first and second account information held by the user based on a third operation from the terminal device 10.

[0109] Here, the output processing by the output unit 138 will be explained with reference to Figure 14. Figure 14 is a diagram showing an example of the processing by the output unit 138 according to the embodiment. In the example of Figure 14, managed data acquired using the first account information is stored in association with the first account, and managed data acquired using the second account information is stored in association with the second account information. Furthermore, the management unit 133 manages the first account information and the second account information in association.

[0110] The output unit 138 outputs managed data associated with each account information based on the operation of the terminal device 10. The output unit 138 has first to third output modes. In the first output mode, as shown in Figure 14(1), the output unit 138 outputs managed data associated with the first account information held by the user based on the first operation from the terminal device 10. In the second output mode, as shown in Figure 14(2), the output unit 138 outputs managed data associated with the second account information held by the user based on the second operation from the terminal device 10. In the third output mode, as shown in Figure 14(3), the output unit 138 outputs managed data associated with the first and second account information held by the user based on the third operation from the terminal device 10.

[0111] The first, second, and third operations are operations performed on the terminal device 10 to select the managed data to be output by the output unit 138. In the example in Figure 14, the first account may be one or more accounts owned by the user. The second account may be one or more accounts owned by the user that are not the first account.

[0112] Furthermore, in the example in Figure 14, the first account and the second account may each be one or more account information that matches the conditions specified by the user. For example, the first account and the second account may each be one or more accounts that match the conditions such as the type of account and the location where the data was obtained, as specified by the user.

[0113] The output unit 138 outputs managed data that matches the conditions specified by the user. For example, the output unit 138 outputs managed data that matches conditions such as the date and time of data acquisition, location, and type of account information used for acquisition. In this way, the output unit 138 outputs managed data that matches conditions such as a specific period, enabling the user to view the data they request.

[0114] Embodiments of the present invention have been described above. However, the present invention is not limited to these descriptions. Modifications made by those skilled in the art to the above-described embodiments are also included within the scope of the present invention, as long as they retain the features of the present invention. For example, the shape, dimensions, material, arrangement, etc., of each element of the data management system 1, sensor device 5, terminal device 10, data management device 100, etc., are not limited to those exemplified and can be modified as appropriate. Furthermore, each element of each of the above-described embodiments can be combined to the extent technically feasible, and combinations thereof are also included within the scope of the present invention, as long as they retain the features of the present invention. [Explanation of symbols]

[0115] 1. Data Management System 5. Sensor device 10 Terminal devices 100 Data Management Devices 110 Communications Department 120 Storage section 121 User Storage Unit 122 Data Storage Unit 130 Control Unit 131 Acquisition Department 132 Corresponding section 133 Management Department 134 Registration Department 135 Deleted section 136 Update Department 137 Transition Section 138 Output section

Claims

1. A data storage means that stores health-related data acquired from sensors installed in plumbing equipment in multiple facilities, in association with the account information used to acquire the data from among the user's multiple account information accounts, An account management means for managing the plurality of account information stored in the data storage means in association with each other, A data management system characterized by having the following features.

2. The system further includes a data output means that outputs the managed data stored in the data storage means to the terminal device based on an operation on the terminal device, The data output means is A first output mode that outputs health-related data associated with a first account information held by the user, based on a first operation from the terminal device, A second output mode that outputs health-related managed data associated with the second account information held by the user, based on a second operation from the terminal device, A third output mode that outputs the first account information held by the user and the health-related data associated with the second account information, based on a third operation from the terminal device, The data management system according to claim 1, characterized by comprising the following:

3. The system further includes an account registration means for registering new account information held by the user with the account management means, The account management means manages the multiple account information stored in the data storage means by associating it with the new account information. The data management system according to feature 1.

4. The aforementioned managed data is This includes any or more of the following: excrement data acquired by sensors on devices installed in the equipment, vital data of users using the equipment, operation data of the control unit that operates the devices installed in the equipment, usage history data of the devices used by the user, data on food and beverages acquired by the equipment, and data from the door opening / closing sensors of the equipment. The data management system according to feature 1.

5. The account information held by the user is either personal account information acquired by the user or organizational account information assigned to the user individually. The data management system according to feature 1.

6. The account management means further comprises an account deletion means for deleting one or more of the multiple account information held by the user from the account management means. The data management system according to feature 1.

7. Account update means: Adds the health-related managed data associated with the account information deleted by the account deletion means to the health-related managed data associated with other account information held by the user. The data management system according to claim 6, characterized by comprising the following:

8. An account registration means for registering new account information held by the user with the account management means, An account migration means for transferring the health-related data associated with the account information deleted by the account deletion means to the new account information, The data management system according to claim 6, characterized by comprising the following:

Images