WO2017029725A1

WO2017029725A1 - Life log cloud system, life log cloud system control method, life log control method, program, recording medium, and cloud server

Info

Publication number: WO2017029725A1
Application number: PCT/JP2015/073238
Authority: WO
Inventors: 森田　豊久; 英志木村
Original assignee: 株式会社日立システムズ
Priority date: 2015-08-19
Filing date: 2015-08-19
Publication date: 2017-02-23
Also published as: JPWO2017029725A1; JP6145215B1

Abstract

To solve such a problem that, when a user replaces a wearable sensor with another one out of a plurality of wearable sensors for wearing, data of a sensor is registered during only a certain period of time, and data of another sensor cannot be registered during the period of time excluding the certain period of time, the following configuration is provided. A life log cloud system is constituted of sensors 101, 102, and 103 and a server system 114. The sensors 101, 102, and 103 each include a communication unit. The server system 114 includes a communication device 104, an input and output device 105, a storage device 106, and a processing device 107. The storage device 106 includes at least a terminal/user table 109, a life log 110, and a determination logic 111. The processing device 107 includes at least a determination unit 112 and a registration unit 113. The life log 110 includes chronological sensor information for each user. The determination logic 111 includes a description of a condition to be written in the life log 110. The determination unit 112 determines whether this is written in the life log 110 with reference to the determination logic 111 and data input from the sensors 101, 102, and 103. The registration unit 113 performs a write process with respect to the life log 110 with reference to the terminal/user table 109.

Description

Life log cloud system, life log cloud system control method, life log control method, program, recording medium, cloud server

The present invention relates to a life log cloud system, and more specifically, data including life history and exercise history of each individual, body measurement amount, and the like by a wearable sensor used by wearing on a body or clothes, for example, a user's life The present invention relates to a life log cloud system, a life log cloud system control method, a life log control method, a program, a recording medium, and a cloud server that measure state data and manage and utilize the data as personal life log data.

Systems that use such wearable sensors to measure an individual's life history, exercise history, and body measurement amount, and manage and utilize the data as personal life log data are on the market. Further, in order to measure data indicating an exercise state and to improve daily life patterns in close contact with daily life and to grasp an appropriate calorie intake amount, it is described in JP-A-2005-205167 (Patent Document 1). There is a technology.
This publication discloses an exercise state sensing system capable of automatically presenting, in real time, advice on optimizing daily activities to a person to be measured in daily life patterns.

JP-A-2005-205167

According to the system described in Patent Literature 1, the advice of optimizing daily activities has the effect of being able to “improve daily life patterns and grasp appropriate calorie intake in close contact with daily life”.

However, there are the following problems.
When a user prepares multiple sensors for different applications and measures a certain measured value, for example, acceleration, the user replaces the sensor in the middle, and later collects data from multiple sensors and communicates to the server or cloud In the case, it is uncertain which sensor data should be adopted at each time.
For example, a normal sensor 1 that a user is using, a sensor 2 that can be measured during sleep, a waterproof sensor 3 that can be measured even when swimming, and three wearable acceleration sensors are replaced for each time, place, and application. However, consider the case of uploading data to the cloud side in the order of sensor 1, sensor 2, and sensor 3 at appropriate timing of the day.
At this time, it is necessary to decide which sensor of the sensors 1 to 3 to use at each time. For example, the first uploaded data of the sensor 1 is adopted and the data uploaded from the

subsequent sensors

2 and 3 are invalidated, or the last uploaded sensor 3 There may be an implementation where the data is valid and data that was previously uploaded is overwritten.
Of course, these two methods must be set in that way in advance, and even if they are set in that way, in either of the above two methods, “the data of the sensor that has only a certain part is used, It is not possible to use a different sensor for other parts. Also, the result will depend on the order of upload.
There are many wearable sensors on the market that wear and use sensors on clothes and the body. Like a watch, these wearable sensors are suitable for TPO (Time, Place, Occasion). The above-described prior art cannot sufficiently meet the need for appropriately managing the data at each corresponding time as appropriate data by appropriately changing according to the usage), the life scene, and the activity content.

Therefore, in the present invention, when a user replaces and uses a plurality of sensors, which sensor data is used as the user data in which time zone is managed, and which sensor is used by the user at which time. The purpose is to make it possible to utilize appropriate and consistent data as a life log without having to teach each other.
Here, the user does not have to tell which sensor is used at what time, for example, “the sensor 1a is from 10:46 to 11:00 on what day, what month and what day” This means that even if the user does not teach the system, the sensor used by the user can be estimated and learned on the system side.

In order to solve the above problems, one of the representative life log cloud system, life log cloud system control method, life log control method, program, recording medium, and cloud server of the present invention is:
It consists of a sensor and a server system.
The sensor includes a plurality of sensors that can be used by the same person,
The server system includes a communication device, an input / output device, a storage device, and a processing device,
The storage device includes at least a terminal / user table, a life log, a recording unit that stores determination logic,
The terminal / user table includes correspondence information between identifiers of the plurality of sensors and identifiers of users,
The life log includes time-series sensor information for each user,
The determination logic includes a description of conditions to be written to the life log,
The processing device includes at least a determination unit and a registration unit,
The determination unit determines whether to write this to the life log with reference to the data input from the determination logic and the sensor,
The registration unit performs a process of referring to the terminal / user table and writing to the life log when the determination unit satisfies a write condition of the determination logic.

According to the present invention, when a user replaces and wears a plurality of wearable sensors, it is possible to manage which sensor data is adopted as the user data in which time zone. As described above, even when the TPO, the life scene, and the activity content are arbitrarily replaced, they can be managed and utilized as appropriate and consistent data as a life log.
Problems, configurations, and effects other than those described above will be clarified by the following embodiments.

FIG. 1 is a configuration diagram of a life log cloud system showing an embodiment of the present invention. FIG. 2 is a flowchart showing a processing flow of the server system of the present invention. FIG. 3 is a table showing a format example of data communicated from the sensor to the server system. FIG. 4 is a table showing an example of determination logic (determination condition) in the server system. FIG. 5 shows data waveforms output from a plurality of sensors, and shows a use case for explaining the utility of the present invention. FIG. 6 is a table showing a configuration example of a terminal / user table. FIG. 7 is a table showing a configuration example of a life log.

Hereinafter, examples will be described with reference to the drawings. In the following description, various types of information may be described using expressions such as “table”, but the various types of information / data may be expressed using a data structure other than a table. Also, “table” can be called “information” or “data” to indicate that it does not depend on the data structure.
Further, the process may be described with “program” as the subject. The program is executed by a processor, for example, an MP (Micro Processor) or a CPU (Central Processing Unit), and performs a predetermined process. Since the processor performs processing while appropriately using storage resources (for example, a memory) and a communication device (for example, a communication port), the subject of the processing may be a processor. The processor may have dedicated hardware in addition to the CPU. The computer program may be installed on each computer from a program source. The program source may be provided by, for example, a program distribution server or a storage medium.

FIG. 1 is a configuration diagram of a life log cloud system showing an embodiment of the present invention. In the figure, the life log cloud system 100 includes a sensor and a server system (computer) 114.

The sensor includes a plurality of

sensors

101, 102, and 103 (sensors 1a, 1b, and 1c) that can be reused by the same person. For example, if there are three sensors, as shown in FIG. 1, the sensor 101 (sensor 1a), the sensor 102 (sensor 1b), and the sensor 103 (sensor 1c) are constituent elements.
In this example, three examples are given, but at least two sensors are sufficient, and it is not necessary to have three sensors. In addition, an existing sensor is used.
For example, as shown in FIG. 3, each sensor outputs time-series sensor data for each time for each terminal ID. The sensor data includes terminal ID (000101, 000101, 000101, ...), date and time (2015.6.9 15: 28.00, 2015.6.9 15: 30.00, 2015.6.9 15: 32.00, ...), acceleration X (87 , 43.2, 63.1, ...), acceleration Y (23.1, 14.7, 3.2, ...), acceleration Z (1.2, 8.2, 12.1) ...

The server system 114 includes a communication device 104, an input / output device 105, a storage device 106, and a processing device (CPU) 107, and these devices are interconnected by a bus 108.

The communication device 104 is a device having a communication unit / interface that performs data communication with each sensor.
Each of the sensor 1a, the sensor 1b, and the sensor 1c includes a communication unit (not shown) inside, and communicates with the communication device 104 of the server system 114 via the communication unit.

The input / output device 105 serves as an interface for outputting the life log 110 of the storage device 106 to the outside of the server system 114. For example, a keyboard for inputting data, a display for displaying data, and the like can be mounted.

The storage device 106 includes a storage unit that stores and holds at least the terminal / user table 109, the life log 110, and the determination logic 111.

For example, as shown in FIG. 6, the terminal / user table 109 includes a user ID (0100, 0100, 0200,...) For identifying a user and a terminal ID (000101, 000102, 002001,. )) Correspondence table.
Here, a plurality of terminal IDs (000101,000102) are allowed to correspond to one user ID (0100). However, only one user ID corresponds to one terminal ID.

The life log 110 includes time-series data of user measurement values, for example, as shown in FIG. The time-series data of the measurement values includes user ID (0100, 0100, 0100,...), Terminal ID (000101, 000101, 000101,...), Date and time (2015.6.9 15: 28.00, 2015.6.9 15: 30.00, 2015.6.9 15: 32.00, ...), acceleration X (87.6, 43.2, 63.1, ...), acceleration Y (23.1, 14.7, 3.2) ,..., And acceleration Z (1.2, 8.2, 12.1,...).

The determination logic 111 has a plurality of overwrite conditions, for example, as shown in FIG. The overwriting conditions are, for example, as follows, but need not be limited to the following.
Judgment logic ID Overwrite condition (judgment condition)
1 Designated variable> 0
2 (Designated variable) ² > 0
3 Σ _i (designated variable _i ) ² > 0
4 (Designated variable) ² > C1
5 Σ _i (designated variable _i ) ² > C2
C1, C2: Constant

The processing device 107 controls the operation of each device, and controls the operation of each device according to a program stored therein. The processing device 107 includes at least a determination unit 112 and a registration unit 113.

The determination unit 112 has a function of referring to the overwrite condition of the determination logic 111 and data input from the sensor and determining whether or not to write the data to the life log 110.

The registration unit 113 has a function of referring to information in the terminal / user table 109 and performing a process of writing in the life log 110.

FIG. 5 is a diagram for explaining a use case in which the present invention exhibits its utility. Hereinafter, the use case will be described with reference to the components in the configuration diagram of FIG.

The sensor 101 (the sensor 1a used at normal time), the sensor 102 (the sensor 1b used at sleep), and the sensor 103 (the sensor 1c used at swimming) are different sensors. It shows that the activity is measured in different time intervals. Here, the data of each sensor is, for example, acceleration.

In FIG. 5, the horizontal axis indicates time t, and the vertical axis indicates acceleration. As shown in the figure, it is assumed that the sensors 1a, 1b, and 1c are used separately during the day, during normal time, during sleep, and during swimming.
The reason for using different sensors may be that there is a use condition that is suitable (good or bad) for each sensor. For example, specifically, waterproofness, accuracy during sleep, appearance as a decorative item, and the like can be considered.
In this case, it is considered that the same person changes the sensor to measure the acceleration depending on time and case, and then communicates past data to the server system 114 in random order.
In this case, since a plurality of sensor data at one time exists for one user, as a result, which sensor data should be adopted at each time becomes undefined.

When data is communicated to the server system 114 in the order of the sensor 1a, the sensor 1b, and the sensor 1c, for example, the data of the sensor 1a communicated first is adopted, and the data communicated from the subsequent sensors 1b and 1c is used. There may be implementations that are ignored or overwritten each time and the data of the last communicated sensor (in this case, when uploading the sensor 1c) is valid.

Of course, these two methods must be set in that way in advance, but even if they are set in that way, the results will change depending on the order of communication in either of the above two methods. In addition, it is not possible to use data of a sensor that exists only at a certain time portion and use another sensor at other time portions.
Here, for example, it is realized that the data of the sensor 1c is adopted in a certain time zone and the sensor 1b is adopted in another certain time zone.

FIG. 2 is a flowchart showing a processing flow of the server system 114 of the present invention.

In the present embodiment, a certain past time from any one of the sensor 101 (sensor 1a), the sensor 102 (sensor 1b), and the sensor 103 (sensor 1c) (here, for the sake of convenience, the sensor 101 / sensor 1a). When the measured value is communicated to the server system 114 via the communication device 104, the server system 114 writes or does not write the data communicated from the sensor 101 (sensor 1a) to the life log 110 of the storage device 106. Determine. If it is determined that the data is to be written, the data is written to an appropriate position in the life log 110.
Hereinafter, the data writing process will be described.

The operation based on the flowchart of FIG.
First, in step s201, the server system 114 communicates and takes in data from the sensor 101 (sensor 1a) to a temporary storage area (not shown) of the storage device 106 via the communication device 104.

The format of the communication data is as shown in FIG. 3, and the data is time-series sensor data for each time for each terminal ID as shown in FIG.
That is, one record is a measured value of a sensor having a unique terminal ID and a unique time, and the terminal ID (000101, 000001, 00101,...), Date and time (2015.6.9 15: 28.00, 2015.6). .9 15: 30.00, 2015.6.9 15: 32.00, ...), acceleration X (87.6, 43.2, 63.1), acceleration Y (23.1, 14.7, 3.2, ... ..) And acceleration Z (1.2, 8.2, 12.1,...).
In FIG. 3, acceleration data of three axes (X, Y, Z) are recorded in time series.

Next, in step s202, the server system 114 determines whether there is unchecked data in the communication data captured in the storage device 106.
If all the time data are checked in this determination, the process ends. If there is time data that has not been checked, the process proceeds to the next step s203.

In step s203, the server system 114 selects one of the communication data that has not been checked yet, and sends the data at that time to the determination unit 112 of the processing device 107 as a data input.

In step s204, the determination unit 112 in the server system 114 refers to the overwrite condition of the determination logic 111 shown in FIG. 4 described above, and determines whether or not the communication data (data input) is input in step s203 depending on whether the overwrite condition is satisfied. ) Is written in the life log 110 as data at that time.

Here, it is assumed that one of the determination logic IDs (1, 2, 3, 4, 5,...) Of the determination logic 111 has already been selected before the processing 200 is executed. Here, for example, it is assumed that determination logic ID = 3 (Σ _i (designated variable _i ) ² > 0) is selected.
The overwriting condition is that the sum of squares of all the specified variables is positive. When this condition is satisfied, the process proceeds to the next step s205. If this condition is not satisfied, the process returns to step s202.

In addition to the above, the overwriting condition of the determination logic is “specified one variable is positive”, “specified one variable is squared positive”, “designated one variable squared is greater than a constant C1”, “ There may be variations such as “the sum of squares of all the specified variables is greater than a constant C2.”
For example, the acceleration is considered to be zero when the sensor is not attached, but it is assumed that the sensor is attached on such a premise and the overwriting condition is assumed, or the presence of some error is assumed to some extent. It is possible to put a premise such as overwriting by assuming that the sensor is attached only when the above absolute value is observed.

In step s205, the registration unit 113 in the server system 114 writes the data determined to be written in step s204 to an appropriate position in the life log 110.

Also, the registration unit 113 refers to the terminal / user table 109 and extracts a user ID corresponding to the terminal ID of the data determined in step s204. Next, a registered record corresponding to this time of the user ID is extracted from the life log 110.

As illustrated in FIG. 7, the life log 110 includes an array of a user ID, a terminal ID, a date and time (including date, time), and measured values (acceleration X, Y, and Z).
Here, when a record is extracted from the life log 110, it is not necessary for the terminal IDs to match on condition that only the user ID matches or the time matches. The measurement value (data) and terminal ID used in step s204 are written into the records of the life log 110 that match the user ID and the time.

When there is no data at the time of the user ID in the life log 110, the data used in step s204 is added to the life log 110 including the user ID, terminal ID, date and time, and measurement value.
When the above process is completed, the process proceeds to step s202.

According to the above-described embodiment, when a user replaces and wears a plurality of wearable sensors, a condition for adopting a value is determined in advance, and the observed sensor can be selected by following the conditions. . Thus, even when the wearable sensor is arbitrarily replaced according to the TPO, the life scene, and the activity content like a clock, it can be managed and utilized as appropriate and consistent data as a life log.

The above-described first embodiment can be implemented with the following modifications. Only the steps that have changed from Example 1 are shown below.

In step s205 of the first embodiment, the registration unit 113 has extracted a record in which both the user ID and the time match from the life log 110, but this is changed so that the user ID matches and the time is more granular. It may be considered as a rough time zone, and records in that time zone may be extracted. For example, the time unit may be rounded down, or the minute unit may be divided into 5 minutes. Next, the record of the user ID extracted in that time zone is deleted.

Next, the server system 114 adds the terminal ID, date / time, and measurement value of the communication data used in step s204 to the life log 110. Further, the user ID is entered in the user ID column which is one of the columns of the life log 110.

Here, when the record of the user ID is not extracted from the life log 110 of the storage device 106 in that time zone, the communication data is added to the life log 110 including the user ID, the terminal ID, the date and time, and the measurement value. To do. Finally, similarly to step s205 of the first embodiment, the process proceeds to step s202.
It is also possible to change and implement as described above.

According to the second embodiment described above, overwriting correction is possible even if the date and time are not finely matched up to the second. For example, the sensors 1a, 1b, and 1c do not generate data at the same time because the accuracy of the clock or processing system is poor, so that it is possible to prevent all data from being captured as a result. In addition, the sensor 1a, the sensor 1b, and the sensor 1c perform necessary overwrite correction even if the measurement time interval and the first measurement time do not match.

Further, it is also possible to implement a program in a format capable of executing the method shown in the above embodiment and a storage medium storing the program. It is also possible to implement as a service that makes these programs executable.

The present invention can be used in a system that uses a wearable sensor to manage an individual's life history, exercise history, and body measurement amount, and manages and uses the data as personal life log data.

100 Life log cloud system 101 Sensor 1a
102 Sensor 1b
103 sensor 1c
104 Communication Device 105 Input / Output Device 106 Storage Device 107 Processing Device 108 Bus 109 Terminal / User Table 110 Life Log 111 Determination Logic 112 Determination Unit 113 Registration Unit 114 Server System

Claims

It consists of a sensor and a server system.
The sensor includes a plurality of sensors that can be used by the same person,
The server system includes a communication device, a storage device, and a processing device,
The communication device includes a communication unit that performs data communication with the sensor,
The storage device includes at least a terminal / user table, a life log, a recording unit that stores determination logic,
The terminal / user table includes correspondence information between identifiers of the plurality of sensors and identifiers of users,
The life log includes time-series sensor information for each user,
The determination logic includes a description of conditions to be written to the life log,
The processing device includes at least a determination unit and a registration unit,
The determination unit refers to the data input from the determination logic and the sensor, determines whether to write the sensor data in the life log,
The registration unit performs a process of writing the sensor data in the life log with reference to the terminal / user table when the determination unit satisfies a writing condition of the determination logic in the determination unit. Log cloud system.
In the life log cloud system according to claim 1,
The determination logic includes a condition sufficient for estimating that the user is wearing the sensor as a condition for writing to the life log,
The determination unit determines whether to write the sensor data corresponding to each time in the life log for each time included in the sensor information,
The registration unit, when the determination unit satisfies the condition for writing the determination logic and writes the sensor data to the life log with reference to the terminal / user table, Write to log,
When the condition for writing the determination logic is not satisfied, writing of the sensor data at the writing time to the life log is prevented and skipped.
In the life log cloud system according to claim 1 or 2,
The registration unit further calculates a time zone with coarser granularity than the date and time obtained from the sensor, and writes the sensor data to the life log in the time zone.
It consists of a sensor and a server system.
The sensor includes a plurality of sensors that can be used by the same person,
The server system includes a communication device, a storage device, and a processing device,
Including a communication unit for performing data communication with the sensor;
The storage device includes at least a terminal / user table, a life log, a recording unit that stores determination logic,
The terminal / user table includes correspondence information between identifiers of the plurality of sensors and identifiers of users,
The life log includes time-series sensor information for each user,
The determination logic includes a description of a write condition in the life log,
A control method for a life log cloud system,
The processor is
Referring to the data input from the determination logic and the sensor, and determining whether to write the data to the life log;
In the determination step, when the writing condition of the determination logic is satisfied, the sensor data is written to the life log with reference to the terminal / user table,
A method for controlling a life log cloud system, comprising:
In the control method of the life log cloud system according to claim 4,
The processing device further calculates a coarser time zone than the date and time obtained from the sensor,
And a step of writing the sensor data to the life log of the time period. A control method for a life log cloud system, comprising:
A life log control method for receiving sensor data measured by a plurality of wearable sensors that can be used by the same person and storing the sensor data in a life log,
Holding a terminal / user table including correspondence information between an identifier of the sensor with the wearable sensor and an identifier of a user;
Maintaining a life log including time-series sensor data for each user;
Holding a determination logic including a description of a write condition in the life log;
Determining whether to write the sensor data to the life log based on a write condition of the determination logic;
In the determination step, when the write condition of the determination logic is satisfied, the sensor data is written to the life log with reference to the terminal / user table;
A life log control method comprising:
In the life log control method according to claim 6,
The determination logic includes a condition sufficient for estimating that the user is wearing the sensor as a condition for writing to the life log,
The step of determining includes a determination processing step of determining whether to write the sensor data corresponding to each time in the life log for each time included in the sensor data,
The writing step satisfies the writing condition of the determination logic in the determining step, and when writing the sensor data to the life log with reference to the terminal / user table, the sensor data at the writing time is Write to life log,
A life log control method, wherein when the condition for writing the determination logic is not satisfied, writing of the sensor data at the write time to the life log is prevented and skipped.
The life log control method according to any one of claims 5 to 6, wherein the program is executed by a computer in a format in which the steps can be executed.
A program that receives sensor data measured by a plurality of wearable sensors that can be reused by the same person, and causes a life log system that stores the sensor data in a life log to execute the following steps.
Holding a terminal / user table including correspondence information between a sensor identifier and a user identifier with the wearable sensor;
Maintaining a life log including time-series sensor data for each user;
Holding a determination logic including a description of a condition to be written to the life log;
Determining whether to write the sensor data to the life log based on a condition for writing the determination logic;
The step of writing the sensor data in the life log with reference to the terminal / user table when the writing condition of the determination logic is satisfied in the determining step.
It consists of multiple sensors and server systems that can be reused by the same person.
The server system includes a communication device, a storage device, and a processing device,
The storage device includes at least a terminal / user table, a life log, a recording unit that stores determination logic,
The terminal / user table includes correspondence information between identifiers of the plurality of sensors and identifiers of users,
The life log includes time-series sensor information for each user,
The determination logic includes a description of conditions to be written to the life log,
A computer-readable recording medium recording a program for realizing a life log system for performing data communication between the plurality of sensors and the cloud server via the communication device by a computer,
Referring to the data from the determination logic and the sensor and determining whether to write the data to a life log;
In the determination step, when the condition for writing the determination logic is satisfied, the data from the sensor is written to the life log with reference to the terminal / user table;
The computer-readable recording medium which recorded the program which makes a computer perform.
In a server system that receives data on a user's life state from a plurality of wearable sensors,
Including communication device, storage device, processing device,
The communication device includes a communication unit that performs data communication with the sensor,
The storage device includes at least a terminal / user table, a life log, a recording unit that stores determination logic,
The terminal / user table includes correspondence information between identifiers of the plurality of sensors and identifiers of users,
The life log includes time-series sensor information for each user,
The determination logic includes a description of conditions to be written to the life log,
The processing device includes at least a determination unit and a registration unit,
The determination unit refers to the data input from the determination logic and the sensor, determines whether to write the data to the life log,
The registration unit performs a process of writing data from the sensor to the life log with reference to the terminal / user table when the determination unit satisfies a condition for writing the determination logic. Server system.