JP2022173490A - Data management server, data management method, and data management program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a data management server for providing an interface capable of easily performing access to the data of a data storage, without requiring an API for allowing an application to access measurement data and to provide a data management method and a data management program.

SOLUTION: A data management server 100 of a data management system 1 includes, as its functions, a data layer management part 130 for generating a data layer for each type of a measurement device 300 in measurement data DB 121, a data management part 140 for generating an account in the data layer for each user using the measurement device 300, an application generation part 150 for performing predetermined arithmetic operation on biological data from the measurement data, and an interface providing part 160 for providing the interface for allowing the application to access the measurement data.

SELECTED DRAWING: Figure 1

COPYRIGHT: (C)2023,JPO&INPIT

Description

The present disclosure relates to a data management server, a data management method, and a data management program that receive measurement data from a measuring device and perform calculations on biological data.

2. Description of the Related Art Continuously measuring a user's biometric data using a measuring device for measuring biometric data, and detecting changes in the data at an early stage of illness or detecting changes in the condition is effective for health management. To do this, it is necessary not only to measure biological data, but also to comprehend various health conditions from multiple biological data, so it is necessary to create software that uses a large amount of measurement data and a mathematical model based on it to perform various calculations. There is

For example, there is known a development support server that provides a mathematical model in which various calculations are performed based on user's measurement data (see, for example, Patent Document 1). The development support server disclosed in Patent Literature 1 generates a mathematical model that is a causal relationship for performing calculations from measurement data to biological information data, and provides the mathematical model in a usable manner. This allows software developers to easily use mathematical models based on user measurement data to create application software.

Japanese Patent No. 6257015

By the way, in such application software (hereinafter referred to as "application"), data storage is provided for each application, and various data including necessary measurement data are stored respectively, so various data are stored redundantly. may have. Moreover, in order to use such an application, it is necessary to create a user account for each application, which is a troublesome task for the user.

New value is expected to be created by sharing various types of data in this way. To achieve this, an API (Application Programming Interface) is created for each application, and each application accesses the data in the data storage. It needs to be able to do so, and it requires extra work for software developers.

Therefore, in the present disclosure, a data management server, a data management method, and a data management program that provide an interface for applications to access measurement data will be described.

A data management server in one aspect of the present disclosure is a data management server that receives measurement data from a measurement device via a network and performs calculation from the measurement data to biological data, and generates a data layer for each measurement device. a layer management unit, a data management unit that generates an account for each user who uses the measuring device, is divided into data layers corresponding to the measuring device, and stores measurement data for each account; detects the state of the user; An application generating unit that generates application software for performing predetermined calculations on biological data from measured data; and an interface providing unit that provides an interface for the application software to access the measured data. provides access to one or more data layers utilized by , and provides access to one or more per-account metering data.

A data management method according to one aspect of the present disclosure is a data management method for receiving measurement data from a measurement device via a network and performing calculation from the measurement data to biometric data, wherein the data layer management unit performs a data layer management step of generating a data layer in the data management unit, generating an account for each user who uses the measuring device, dividing the measurement data into data layers corresponding to the measuring device, and storing measurement data for each account an application generation step of detecting a user's state and generating application software for performing predetermined calculations on biometric data from measurement data; an application generation step performed by an application generation unit; an interface providing step of providing an interface for accessing the data, the interface providing step providing access to one or more data layers utilized by the application software and providing access to one or more account-specific measurement data. .

Further, a data management program in one aspect of the present disclosure is a data management program that receives measurement data from a measurement device via a network and performs calculation from the measurement data to biological data, and generates a data layer for each measurement device a data layer management step of creating an account for each user who uses the measuring device, classifying it into data layers corresponding to the measuring device and storing the measured data for each account; and detecting the state of the user. and causing a computer to execute an application generation step of generating application software for performing predetermined calculations on biological data from measurement data, and an interface providing step of providing an interface for the application software to access the measurement data, The provisioning step provides access to one or more data layers utilized by the application software and provides access to one or more per-account metering data.

According to the present disclosure, the app includes an interface for accessing measurement data, and allows access to measurement data that is classified by measurement device and stored for each user's account. This makes it possible for an application that performs calculations from measurement data to biometric data to easily access the measurement data.

1 is a block configuration diagram showing a data management system according to an embodiment of the present disclosure; FIG. FIG. 2 is a block configuration diagram showing the structure of a data layer in a measurement data DB 121 of FIG. 1; FIG. FIG. 2 is a schematic diagram showing an example of tag information associated with the measurement data DB 121 of FIG. 1; FIG. FIG. 2 is a schematic diagram showing an example of data correction in the measurement data DB 121 of FIG. 1; FIG. FIG. 2 is a diagram for explaining an example of an electrocardiogram waveform and a pulse wave measured by the measuring device 300 of FIG. 1; FIG. 2 is a flowchart showing an example of processing of the data management system 1 of FIG. 1; 1 is a block configuration diagram showing a data management system according to an embodiment of the present disclosure; FIG. 6 is a functional block configuration diagram showing an example configuration of a computer 600 according to an embodiment of the present disclosure; FIG.

Hereinafter, embodiments of the present disclosure will be described with reference to the drawings. It should be noted that the embodiments described below do not unduly limit the content of the present disclosure described in the claims. Also, not all the components shown in the embodiments are essential components of the present disclosure.

(Embodiment 1)
<Configuration>
FIG. 1 is a block configuration diagram showing a data management system 1 according to Embodiment 1 of the present disclosure. The data management system 1 is, for example, a system for receiving measurement data from a measuring device that measures user's biological data, receiving the measurement data via a network, and performing calculations on the biological data.

The data management system 1 has a data management server 100, a user terminal device 200, a measuring device 300, a data layer creator terminal 400, an application provider terminal 500, and a network NW. The data management server 100, the user terminal device 200, the data layer creator terminal 400, and the application provider terminal 500 are connected via a network NW. The network NW includes the Internet, an intranet, a wireless LAN (Local Area Network), a WAN (Wide Area Network), and the like.

The data management server 100 is, for example, a device that receives user measurement data from the measurement device 300 via a network via the user terminal device 200 and performs calculations from the measurement data to biometric data, and provides various web services. It is composed of a server device that provides.

The user terminal device 200 is an information processing device such as a personal computer, a tablet terminal, a smart phone, a smart watch, a mobile phone, a PHS, a PDA, etc. owned by the user. is used to display the waveform graph or the like. Information such as the user's date of birth, gender, height, weight, stride length, etc., of the user is registered in advance in the user terminal device 200, and user information such as age calculated from the date of birth is associated with the measurement data to connect the network NW. to the data management server 100 via the

In addition, the user terminal device 200 can input a state in which the user acquires data from the measuring device 300 using a touch panel or the like. The user terminal device 200 can input the “data acquisition state” as hash tag information such as “#running” when running, “#eating” when eating. can be done. The user terminal device 200 associates the measurement data received from the measurement device 300 with hash tag information and transmits the measurement data to the data management server 100 via the network NW.

The measuring device 300 is a device that measures a user's biological data, and is, for example, a wearable device that the user wears on his or her body such as an arm. This measurement device 300 is a device of a plurality of types for measuring, for example, data of a user's electrocardiogram, pulse wave, temperature (body temperature), and acceleration.

As a specific example of the configuration of the measurement device 300, two electrodes may be brought into contact with the skin, and an electrocardiogram may be obtained as electrocardiogram data from changes in the detected potential difference over time. The waveform may be data obtained by galvanic skin response. In addition, the skin is irradiated with light from LEDs that emit green, red, and infrared light, and the change in intensity of the light received by the photodiode over time changes the volume of blood vessels caused by the heartbeat of the user, generating a pulse wave. It may be configured with a device that acquires pulse waveform data, and the pulse waveform that can be detected by this method is a photoelectric volume pulse waveform. Alternatively, the apparatus may be configured by a device that acquires the user's skin temperature as data from a temperature sensor that is brought into contact with the user's skin. Furthermore, it may be composed of a three-axis acceleration sensor that detects the deformation state of each of the orthogonal XYZ axes, and acquires the user's motion as acceleration data. The device 300 acquires acceleration data as an acceleration obtained by combining arm swing and whole-body movement.

Between the user terminal device 200 and the measuring device 300, Bluetooth (registered trademark), Near Field radio Communication (NFC), Afero (registered trademark), Zigbee (registered trademark), Z-Wave (registered trademark) ), or a wireless LAN or the like. A wired connection may be used instead of such a wireless connection. Further, the user terminal device 200 and the measuring device 300 may be an integrated device. For example, the measuring device 300 may be provided with a communication function so that it can directly communicate with the data management server 100 .

One or a plurality of user terminal devices 200 are connected to the network NW for the number of users using the measuring device 300 . One or a plurality of measuring devices 300 are connected to the user terminal device 200 by the number used by one user. When one user uses multiple measuring devices 300 , multiple measuring devices 300 are connected to one user terminal device 200 .

The data layer creator terminal 400 is a data layer creator's terminal that stores measurement data and manages a data layer, which will be described later, and is a device for managing access to the data layer. The application provider terminal 500 is a device for managing downloads of applications (application software), which will be described later, using biometric data. The data layer creator terminal 400 and the application provider terminal 500 are configured by, for example, personal computers.

The data management server 100 includes a communication section 110 , a storage section 120 , a data layer management section 130 , a data management section 140 , an application generation section 150 , an interface provision section 160 and a calculation section 170 .

The communication unit 110 is a communication interface for communicating with the user terminal device 200, the data layer creator terminal 400, and the application provider terminal 500. For example, a communication protocol such as TCP/IP (Transmission Control Protocol/Internet Protocol) is used. Communication is performed by

The storage unit 120 stores programs, input data, etc. for executing various control processes and functions of the data layer management unit 130, the data management unit 140, the application generation unit 150, the interface provision unit 160, and the calculation unit 170. It is composed of RAM (Random Access Memory), ROM (Read Only Memory) and the like. The storage unit 120 also includes a measurement data DB 121 that stores measurement data obtained by the measuring device 300, a biological information data DB 122 that stores biological data calculated and generated from the measurement data, and a measurement data stored in the measurement data DB 121. It stores an interface DB 123 that stores an interface for accessing data, and an application DB 124 that notifies the user's health management information using biometric data, for example. Furthermore, the storage unit 120 temporarily stores data that has been communicated with the user terminal device 200 , the data layer creator terminal 400 , and the application provider terminal 500 .

Data layer management section 130 generates a data layer for each type of measuring device 300 in measurement data DB 121 of storage section 120, and manages access to the data layer.

A data layer generated in the measurement data DB 121 of the storage unit 120 will now be described. FIG. 2 is a block configuration diagram showing the structure of the data layer in the measurement data DB 121 of FIG. 1. As shown in FIG. As shown in FIG. 2, the measurement data DB 121 is divided into a plurality of data layers 121a, 121b, and 121c.

The data layers 121a, 121b, and 121c are data storage spaces (data storages) provided for each type of the measuring device 300. For example, the data layers 121a , 121b and 121c are provided, respectively. The data layers 121a, 121b, and 121c are generated, for example, by operating the data layer creator terminal 400 by a data layer creator who is a company that manages the data layers.

Devices A, B, and C are devices in which measurement data is transmitted to the data management server 100 and biometric data is calculated when a user registers an account. An account has been generated. In the example shown in FIG. 2, user X's account X is created in data layers 121a and 121b, and user Y's account Y is created in data layers 121a and 121c. This is because user X uses devices A and B, and user Y uses devices A and C. Data measured by device A of user X is stored in account X of data layer 121a, and data measured by device B of user X is stored in account X of data layer 121b. Further, measurement data of user Y's device A is stored in account Y of the data layer 121a, and measurement data of user Y's device C is stored in account Y of the data layer 121c.

The applications AP1 and AP2 generated by the application generation unit 150 to be described later access the measurement data DB 121 to read measurement data, generate biometric data, and cause the user terminal device 200 to display the biometric data. These applications AP1 and AP2 are programs for referring to a desired data layer of the measurement data DB 121 according to the type and purpose when a software developer develops an application. In the example shown in FIG. 2, the application AP1 is set to access the data layers 121a and 121b, and the application AP2 is set to access the data layers 121b and 121c.

In this way, data layers 121a, 121b, and 121c are divided into data layers 121a, 121b, and 121c so as to correspond to devices A, B, and C for each type of measuring apparatus 300, and devices A used by users X and Y are stored in data layers 121a, 121b, and 121c. , B and C, accounts X and Y are generated because by integrating the measurement data in this way, the software developer (application software provider) can measure according to the type and purpose of the application. This is because it is easy to refer to a desired data layer in the data DB 121, and the labor for creating an API can be reduced. In addition, the data layer management unit 130 generates a data layer, and the data management unit 140, which will be described later, creates an account and centrally manages measurement data. is possible.

Data management section 140 creates an account in a predetermined data layer for each user who uses measuring device 300 . This account generation is performed when the user using the measuring device 300 registers an account with the user terminal device 200 . Also, the data management unit 140 stores measurement data for each account in the data layer corresponding to the measurement device 300 . Therefore, the data management unit 140 controls whether or not to allow access to the applications AP1 and AP2 for each data layer, and controls whether or not to allow access to the user terminal device 200 of the user for each account. Also, at this time, the data management unit 140 can store the measurement data in association with predetermined tag information.

FIG. 3 is a schematic diagram showing an example of tag information associated with the measurement data DB 121 of FIG. Data D1 shown in FIG. 3 is measurement data of the measurement device 300 . The tag T1 is tag information associated with the data D1. For example, time information when the measuring device 300 measured the data D1 or time information when the data D1 was transmitted from the measuring device 300 to the user terminal device 200 is time-series. stored as data. Alternatively, both the measured time information and the transmitted time information may be associated. For example, in the first line of the tag T1 shown in FIG. 3, "20180620120746144" is stored, which indicates June 20, 2018 12:07:46:144 milliseconds. Such time information can be obtained from communication logs. This makes it possible to ascertain which time zone the measurement data belongs to.

The association of the measurement data by such tag information is not limited to the time information, and physical information and activity information indicating the user's physical condition and activity may be entered freely and stored as tag information. Select from predetermined options (for example, to the question "How are you feeling now?", select one of "1: good, 2: normal, 3: bad", etc.), and make the selection The answers given may be stored.

Further, for example, the data management unit 140 can rearrange (sort) the data D1 in chronological order of the tags T1, as shown in FIG. The reason for such a configuration is that the measurement data is obtained in time series based on the user's biological data, and it is easier to process it if it is arranged in time series. When receiving data via the unit 110, there may be cases where the received data is reversed (the later transmitted data is received earlier than the earlier transmitted data) due to changes in the communication status. , to prevent inconsistency of the measurement data at that time. This makes it possible to prevent inconsistencies in measurement data.

Furthermore, the data management unit 140 can correct loss of measurement data due to communication errors or the like. FIG. 4 is a schematic diagram showing an example of data correction in the measurement data DB 121 of FIG. Data D2 shown in FIG. 4 is measurement data of measuring device 300 similar to data D1 in FIG. 3, and tag T2 is tag information associated with data D1.

The data measured by the measuring device 300 may be periodic signals such as electrocardiograms and pulse waves, or time-series data such as temperature (body temperature) that changes slowly to some extent. is possible. Therefore, when measurement data at a predetermined time is missing as shown in data D2 in FIG. It is possible to estimate For estimation of this missing data, for example, the average value of the measurement data received immediately before the time and the measurement data received immediately after the time, or the estimated value from the time transition in the time series data may be used. . In addition, it is not limited to data immediately before and after, and may be estimated from data before and after a predetermined range (for example, five data before and after). In such a case, the data management unit 140 estimates the measurement data at another time as the measurement data at the current time and associates the tag information with the measurement data.

The application generation unit 150 performs predetermined calculations related to biometric data, such as calculating biometric data from the measurement data stored in the measurement data DB 121 and using the calculated biodata. An application that can be executed by the data management server 100 or the user terminal device 200 is generated to notify the health management information. This biometric data is, for example, the user's blood pressure information, heart rate information, blood oxygen content information, electrocardiographic information, respiratory rate, body temperature information, stride information, and position information of the center of gravity. An app is created for you. The biometric data generated by the calculation is stored in the biometric information data DB 122 . Also, the generated application is stored in the application DB 124 . Furthermore, this application is delivered to the user terminal device 200 when the user terminal device 200 is operated by the user's request.

Here, as an example of an application generated by the application generation unit 150, a method of calculating the maximum blood pressure and the minimum blood pressure, which are biological information data, from measurement data will be described. FIG. 5 is a diagram for explaining an example of an electrocardiographic waveform and a pulse wave measured by the measuring device 300 of FIG. , a photoelectric volume pulse waveform, a velocity pulse waveform obtained by first-order differentiation of the photoelectric volume pulse waveform with time, and an acceleration pulse waveform obtained by second-order differentiation of the photoelectric volume pulse waveform with time. FIG. 5 shows, in order from the top, an electrocardiographic waveform, a photoelectric volume pulse waveform, a velocity pulse waveform, and an acceleration pulse waveform. The vertical axis indicates the intensity of each waveform, and the electrocardiogram waveform and photoelectric volume pulse waveform are expressed in mV, which indicates potential. The horizontal axis indicates the passage of time, from left to right.

An electrocardiogram is a waveform that represents the periodic variations in electrical signals that cause the human heart to beat. An electrocardiographic waveform is assigned names of P wave, Q wave, R wave, S wave, and T wave to the inflection points of its shape, and indicates one cycle of heartbeat. The P-wave represents atrial contraction, the Q-wave, R-wave, S-wave represents the state of ventricular contraction, and the T-wave represents the onset of ventricular dilation.

A photoelectric volume pulse waveform is a waveform that indicates changes in blood pressure and volume in the peripheral vasculature accompanying the beating of the human heart. The photoelectric plethysmogram is assigned names of A wave, P wave, V wave, and D wave to the inflection points of its shape, and indicates one cycle of heartbeat. With the A wave as the reference point at which the arterial pulse wave is generated, the P wave is the percussion wave (shock wave) generated by left ventricular ejection, the V wave is the Valley wave (wave due to double upheaval) generated when the aortic valve closes, and the D wave. indicates a Dicrotic wave (overlapping wave) which is a reflected oscillatory wave.

The velocity plethysmogram is obtained by first differentiating the photoelectric volume plethysmogram with respect to time. The acceleration pulse waveform is obtained by first-order differentiation of the velocity pulse waveform with respect to time, that is, second-order differentiation of the photoelectric volume pulse waveform. As shown in FIG. 5, the acceleration pulse waveform has a wave (positive wave at the beginning of systole), wave b (negative wave at the beginning of systole), wave c (re-rising wave in the middle of systole), wave d (shock wave) at each peak of the waveform. late re-descending wave), e-wave (extended early positive wave), and f-wave (extended early negative wave).

The ratio of the intensity of the b-wave to the intensity of the a-wave and the ratio of the intensity of the f-wave to the intensity of the e-wave are parameters indicating the stretchability or elasticity of the blood vessel, respectively. The main vascular components are endothelium, elastin, collagen, and smooth muscle. These components have different properties, and Collagen and Elastin have a strong influence on the elasticity of blood vessels at maximum and minimum blood pressure, respectively. Therefore, the elasticity that varies depending on the blood pressure value is indicated by the parameters of (b/a), which is the ratio of the b-wave intensity to the a-wave intensity, and (f/e), which is the ratio of the f-wave intensity to the e-wave intensity. These values also fluctuate due to the influence of age, gender, and environmental variables. Therefore, the values of (b/a) and (f/e) can be calculated as characteristic information of the acceleration pulse waveform.

As shown in FIG. 5, the difference between the time Tr at which the R wave occurs and the time Tp at which the P wave occurs is the ventricular systolic pulse wave propagation time PTT_SYS. The difference between the time Tt at which the T wave occurs and the time Td at which the D wave occurs is the ventricular diastolic pulse wave propagation time PTT_DIA. That is, from the R-wave time Tr and T-wave time Tt of the electrocardiographic waveform and the T-wave time Tp and D-wave time Td of the photoelectric volume pulse waveform, the ventricular systolic pulse wave propagation time PTT_SYS and ventricular diastole A pulse wave transit time PTT_DIA can be calculated.

In addition, it is known that the relationship between the pulse wave velocity and the longitudinal elastic modulus of the arterial wall has a correlation expressed by a predetermined formula, and the relationship between the longitudinal elastic modulus and the blood pressure value is also expressed by a predetermined formula. known to be correlated. Therefore, the systolic pulse wave transit time PTT_SYS can be obtained using a predetermined formula, and the minimum blood pressure can be obtained using a predetermined formula using the ventricular diastolic pulse wave transit time PTT_DIA. This makes it possible to calculate the systolic blood pressure and the diastolic blood pressure.

The interface providing unit 160 provides an interface stored in the interface DB 123 for the application to access the measurement data. This interface is provided by a data layer creator who centrally manages access to the data layer, unlike APIs created by software developers to access data in the data storage. , is provided for each data layer. This eliminates the need for a software developer to create an API, and makes it possible to easily refer to a desired data layer in the measurement data DB 121 according to its type and purpose.

The calculation unit 170 controls the overall operation of the data management server 100 by executing the application generated by the application generation unit 150, and is composed of a CPU (Central Processing Unit) and the like.

A software developer can use the interface obtained from the data management server 100 in the application provider terminal 500 to create an application that generates biometric information data from the measurement data and detects the condition of the subject. Also, the software developer can upload the created application from the application provider terminal 500 to the application DB 124 of the data management server 100 .

A user who wishes to use an application accesses the data management server 100 from the user terminal device 200 via the network NW and downloads the desired application to the user terminal device 200 . The user can use the application by accessing the data management server 100 and creating his/her own account.

<Process flow>
The flow of processing of the data management method executed by the data management system 1 will be described with reference to FIG. FIG. 6 is a flow chart showing an example of processing of the data management system 1 of FIG.

As the process of step S101, in the data layer management section 130, a data layer is generated in the measurement data DB 121 of the storage section 120 for each type of measuring device 300 according to the instruction of the data layer creator. After that, the data layer management unit 130 manages access for each data layer.

As the process of step S<b>102 , the data management section 140 creates an account in a predetermined data layer corresponding to the measurement device 300 in the measurement data DB 121 of the storage section 120 for each user who uses the measurement device 300 . The processing of steps S101 and S102 is performed as preprocessing for the user to use the measuring device 300 .

As the process of step S103 , when the user uses the measuring device 300 , measurement data is transmitted from the measuring device 300 to the data management server 100 via the user terminal device 200 and received via the communication section 110 . The data management unit 140 stores measurement data for each account in the data layer corresponding to the measuring device 300 in the measurement data DB 121 of the storage unit 120 .

As the process of step S<b>104 , the application generation unit 150 generates an application that can be executed by the data management server 100 or the user terminal device 200 from the measurement data stored in the measurement data DB 121 . The generated application is stored in application DB 124 .

As the process of step S105, the interface providing unit 160 provides the application generated in step S104 with an interface stored in the interface DB 123 for accessing a predetermined data layer. This allows the app to access measurement data within a given data layer.

As the process of step S106, when the application generated in step S104 is used, the calculation unit 170 accesses a predetermined data layer of the measurement data DB 121 to read the measurement data, and performs predetermined processing such as calculation of biometric data. Arithmetic is performed. The biometric data calculated by the calculation is stored in the biometric information data DB 122, and can be used by the app or other apps.

<effect>
As described above, in the data management system according to the present embodiment, the data layer management unit generates data layers corresponding to the types of measuring devices, and the data management unit creates an account for each user in each data layer. generated and the user's measurement data is stored for each user's account. As a result, measurement data is centrally managed, so data duplication is eliminated, and wasteful use of resources can be reduced.

In addition, the interface providing unit provides an interface for the application to access a predetermined data layer, and the software developer can refer to the measurement data of the desired data layer according to the type and purpose of the application. . This saves the trouble of creating an API, so it is possible to easily develop an application.

Furthermore, by storing the tag information associated with the measurement data by the data management unit, it is possible to store the time when the measurement data was measured and the measurement state of the user, so that the measurement data can be used with higher accuracy. becomes possible.

(Embodiment 2)
FIG. 7 is a block configuration diagram showing a data management system 1A according to Embodiment 2 of the present disclosure. This data management system 1A is different from the first embodiment in that it is a system for receiving measurement data from a measuring device that measures the user's biological data, receiving the measurement data via a network, and performing calculations on the biological data. Although similar, as shown in FIG. 7, the data management server 100A differs from the first embodiment in that a payment information calculation unit 180 is provided.

The payment information calculation unit 180 calculates payment information for users, data layer creators, and software developers (application software providers) for using the data management server 100A. Specifically, the payment information for calculating the usage fee for the user using the measuring device 300 to use the data management server 100A is calculated, and the data reference fee for the data layer is calculated for the data layer creator. Payment information is calculated for the software developer, and payment information for calculating the data usage fee for the measurement data is calculated. Other configurations are the same as those of the first embodiment.

The payment relationship between users, software developers, and data layer creators will now be described. A software developer is a person who provides an application (application software provider), but it may be a person who purchases an application and distributes it on the network NW. Also, the data layer creator is the person who created the data layer in the data management server 100A, but may be the manager of the data storage in the data management server 100A. First, a user who uses the measuring device 300 pays a usage fee to the operator of the data management server 100A. This usage fee includes a usage fee for using the application for the software developer and a usage fee for using the data layer for the data layer creator. This usage fee is calculated, for example, according to the usage time of the user and the amount of data used.

The data layer creator pays the operation cost of the data management server 100A to the operator of the data management server 100A. This operation cost is calculated according to the free data capacity secured in the storage unit 120, for example. Then, the operator of the data management server 100A pays the data reference fee to the data layer creator. This reference fee is calculated according to, for example, the number of times the data layer is accessed and the amount of data referred to (reference data amount).

The software developer pays the operator of the data management server 100A a usage fee for the billing tool provided by the application to the user. This usage fee is calculated, for example, according to the number of user downloads. Then, the operator of the data management server 100A pays the application fee to the software developer. This usage fee is calculated according to, for example, the number of times the application has been downloaded or the number of times the application has been used by the user.

The payment information calculation unit 180 calculates the usage time of the user, the amount of data used, the number of accesses to the data layer, the amount of data referred to, the number of downloads of the application, and the usage of the application by the user, which are based on such payment information. Count the number of times, etc., and calculate payment information.

Note that each payment may be made by electronic money or credit card, and the data management server 100A may have a function of accessing a server that provides electronic money or credit card services to make payments. good.

According to the present embodiment, in addition to the effects of the above-described first embodiment, the payment information calculation unit is provided. payment information between the developer and the payment information between the software developer and the operator of the data management server can be managed appropriately.

(Embodiment 3 (program))
FIG. 8 is a functional block configuration diagram showing an example of the configuration of a computer (electronic calculator) 600. As shown in FIG. A computer 600 includes a CPU 601 , a main memory device 602 , an auxiliary memory device 603 and an interface 604 .

Here, a control program for realizing each function constituting the data layer management unit 130, the data management unit 140, the application generation unit 150, the interface provision unit 160, and the payment information calculation unit 180 according to the first and second embodiments. Details will be explained. These functional blocks are implemented in computer 600 . The operations of these components are stored in the auxiliary storage device 603 in the form of programs. The CPU 601 reads out the program from the auxiliary storage device 603, develops it in the main storage device 602, and executes the above processing according to the program. Further, the CPU 601 secures a storage area corresponding to the above-described storage unit in the main storage device 602 according to the program.

Specifically, in the computer 600, the program generates a data layer management step for generating a data layer for each measuring device, and an account for each user who uses the measuring device, and divides it into a data layer corresponding to the measuring device. a data management step of storing measured data for each account; a calculation step of calculating from measured data to biological data; detecting a user's state; A control program for realizing, by a computer, an application generation step of generating application software to be used and an interface provision step of providing an interface for the application software to access measurement data.

Note that the auxiliary storage device 603 is an example of a non-temporary tangible medium. Other examples of non-transitory tangible media include magnetic disks, magneto-optical disks, CD-ROMs, DVD-ROMs, semiconductor memories, etc. that are connected via interface 604 . Further, when this program is distributed to the computer 600 via a network, the computer 600 receiving the distribution may develop the program in the main storage device 602 and execute the above process.

Also, the program may be for realizing part of the functions described above. Furthermore, the program realizes the above-described functions in combination with other programs already stored in the auxiliary storage device 603, a so-called difference file (difference program).
may be

Although the disclosed embodiments have been described above, they can be implemented in various other forms, and can be implemented with various omissions, substitutions, and modifications. These embodiments, modifications, omissions, substitutions and modifications are included within the technical scope of the claims and their equivalents.

1, 1A data management system, 100, 100A data management server, 110 communication unit, 120 storage unit, 121 measurement data DB, 122 biological information data DB, 123 interface DB, 124 application DB, 130 data layer management unit, 140 data management Unit, 150 Application generation unit, 160 Interface provision unit, 170 Operation unit, 180 Payment information calculation unit, 200 Terminal device, 300 Measurement device, 400 Data layer creator terminal, 500 Application provider terminal, NW network

Claims (15)

A data management server that receives measurement data from a measurement device via a network and performs calculation from the measurement data to biological data,
a data layer management unit that generates a data layer for each measurement device;
a data management unit that generates an account for each user who uses the measuring device, divides the data layer into data layers corresponding to the measuring device, and stores the measurement data for each account;
an application generation unit that detects the state of the user and generates application software that performs predetermined calculations on the biometric data from the measurement data;
an interface providing unit that provides an interface for the application software to access the measurement data;
A data management server, wherein the interface providing unit accesses one or more of the data layers used by the application software and accesses the measurement data for each of one or more of the accounts. The data layer management unit generates the data layer based on instructions from a data layer creator,
The data management unit generates the account based on the user's account registration,
2. The data management server according to claim 1, wherein said application generator generates said application software provided by an application software provider. Payment information that the user pays to the server operator;
payment information between the data layer creator and the server operator;
3. The data management server according to claim 2, further comprising a payment information calculation unit for calculating payment information between said application software provider and said server operator. The payment information calculation unit
When the data layer creator calculates payment information for the server operator, calculating the payment information for the data layer creator based on the number of accesses to the data layer or the amount of reference data,
When the application software provider calculates payment information for the server operator, the payment information for the application software provider is calculated based on the number of downloads of the application software or the number of times the application software is used by the user. The data management server according to claim 3. The data management unit controls permission/denial of access to the application software for each data layer, and controls permission/denial of access to the measurement data for each account of the user. Item 5. The data management server according to any one of Item 4. The data management server according to any one of claims 1 to 5, wherein the data management unit associates the measurement data with tag information and stores the measurement data for each account. 7. The data management unit according to claim 6, wherein the measurement data, which is time-series data, is associated with time information when the measurement device measures and/or transmits the measurement data as tag information. data management server. 8. The data management server according to claim 7, wherein said data management unit sorts said measurement data in chronological order of said time information. When the measurement data at a predetermined time cannot be received, the data management unit performs the measurement at the time based on the measurement data received before the time and the measurement data received after the time. 9. The data management server according to claim 7 or 8, which estimates data and associates said time information of said time as tag information. 10. The data management server according to any one of claims 6 to 9, wherein the data management unit associates activity information indicating the activity state of the user as tag information. 11. The data management server according to any one of claims 1 to 10, wherein said application generation unit distributes said generated application software to said user's terminal device. 12. The data management server according to any one of claims 1 to 11, wherein said measurement data is data including at least one of electrocardiogram, pulse wave, temperature and acceleration of said user. 3. The biometric data includes at least one of blood pressure information, heart rate information, blood oxygen level information, electrocardiogram information, respiratory rate, body temperature information, stride information, and center of gravity position information of the user. The data management server according to any one of claims 1 to 12. A data management method for receiving measurement data from a measurement device via a network and performing calculations from the measurement data to biological data,
a data layer management step of generating a data layer for each measuring device, performed by a data layer management unit;
a data management step of generating an account for each user who uses the measuring device, classifying the data layer corresponding to the measuring device, and storing the measured data for each account, performed by a data management unit;
an application generation step of detecting the state of the user and generating application software for performing predetermined calculations on the biometric data from the measurement data, performed by the application generation unit;
an interface providing step of providing an interface for the application software to access the measurement data, performed by an interface providing unit;
The data management method, wherein the interface providing step allows access to one or more of the data layers used by the application software and access to the measurement data for each of one or more of the accounts. A data management program that receives measurement data from a measurement device via a network and performs calculation from the measurement data to biological data,
a data layer management step of generating a data layer for each measurement device;
a data management step of creating an account for each user who uses the measuring device, classifying the data layer corresponding to the measuring device, and storing the measured data for each account;
an application generation step of detecting the state of the user and generating application software for performing predetermined calculations on the biometric data from the measurement data;
an interface providing step of providing an interface for the application software to access the measurement data;
The data management program, wherein the interface providing step allows access to one or more of the data layers used by the application software and access to the measurement data for each of one or more of the accounts.

Images