WO2018235152A1 - Sensor management device, sensor management method and sensor management program - Google Patents

Abstract

On the basis of the respective attributes of a plurality of generated virtual sensors (15), a deletion target selection unit (13) selects, from among the plurality of virtual sensors (15), virtual sensors (15) that are to be deleted. A virtual sensor deletion unit (14) deletes the virtual sensors selected as deletion targets by the deletion target selection unit (13).

Description

Sensor management apparatus, sensor management method and sensor management program

The present invention relates to management of virtual sensors.

A large number of sensors such as temperature / humidity sensors, illuminance sensors, and human sensors are installed in a space such as a building, and services using information obtained from these sensors are provided. For example, an air conditioning control service is provided that uses the information from the sensor to realize comfort in a thermal environment. In addition, a lighting control service is provided that uses the information from the sensor to realize improvement in intellectual productivity. In addition, information posting service tailored to the movement of the user is provided using the information from the sensor. With these services, more detailed services can be provided by increasing the density of sensors. However, the number of sensors that can be installed in the space or the installation position of the sensors is limited due to the limitations of the installation location and the installation cost.
On the other hand, on the service (application) provider side, there is a demand to improve the value of the service by using the sensor value at an arbitrary point in the space. For example, in the case of providing an air conditioning control service that achieves office comfort, it is necessary to sense (sense) the environment around the user. Generally, the sensor installed near the seat measures the environment around the user, but since the user moves in the office, the service level may decrease with the sensor value measured by the sensor installed near the seat There is sex. In such a case, it is desirable to move the sensor in real time, but in reality it is difficult to move the sensor in real time.
In addition, there are cases where it is desirable to move a sensor once installed according to a change in service specification. However, in order to move the sensor, it is necessary for an operator to work in the space to move the sensor. For this reason, it is difficult for the service provider to freely move the sensor at any timing.

From such a background, a sensor (hereinafter, referred to as a virtual sensor) is virtually installed at an arbitrary point in space, and a virtual value of a sensor (hereinafter, referred to as a real sensor) physically installed in the space A technique has been proposed that estimates sensor values of sensors and uses sensor values of virtual sensors. For example, if the sensor management device provides an API (Application Programming Interface) common to the real sensor and the virtual sensor, the application uses the API to make the sensor value of the virtual sensor similar to the sensor value of the real sensor. (Patent Document 1 and Patent Document 2).
Moreover, in order to use a sensor value effectively from an application, the method of providing DB (Database) for management of a sensor, and accumulating attribute information is disclosed (patent document 3).

International Publication WO2015 / 182416 JP, 2015-226102, A International Publication WO 2013/24673

The virtual sensor is generated at any time and at any time according to a request from an application. For example, when providing a service focused on a user in a building, a virtual sensor is generated following the movement of the user. In such applications, the number of virtual sensors increases with time. When the number of virtual sensors increases, the search time of the virtual sensors increases. In addition, when the number of virtual sensors increases, the capacity of the memory that holds the virtual sensors runs short. And as a result, degradation of service response time occurs.
Thus, in the service using virtual sensors, it is important to maintain the number of virtual sensors appropriately.

The main object of the present invention is to maintain an appropriate number of virtual sensors.

The sensor management device according to the present invention is
A deletion target selection unit that selects a virtual sensor to be deleted from among the plurality of virtual sensors based on the attributes of each of the plurality of virtual sensors that have been generated;
And a virtual sensor deletion unit that deletes the virtual sensor selected as the deletion target by the deletion target selection unit.

According to the present invention, an unnecessary virtual sensor can be selected as a deletion target virtual sensor based on the attribute of the virtual sensor, and the unnecessary virtual sensor can be deleted. Therefore, according to the present invention, it is possible to maintain the number of virtual sensors appropriately.

FIG. 2 is a diagram showing an example of a functional configuration of a sensor management device according to the first embodiment. FIG. 6 shows an example of attribute information according to the first embodiment. 6 is a flowchart showing an operation example of the sensor management device according to the first embodiment. FIG. 7 is a diagram showing an example of a functional configuration of a sensor management device according to a second embodiment. 10 is a flowchart showing an operation example of the sensor management device according to the second embodiment. FIG. 13 is a diagram showing an example of a functional configuration of a sensor management device according to a third embodiment. FIG. 16 shows an example of an access model according to the third embodiment. 10 is a flowchart showing an operation example of a sensor management device according to a third embodiment. FIG. 16 is a diagram showing an example of a functional configuration of a sensor management device according to a fourth embodiment. 15 is a flowchart illustrating an operation example of a sensor management device according to a fourth embodiment. FIG. 18 is a diagram showing an example of a functional configuration of a sensor management device according to a fifth embodiment. 15 is a flowchart showing an operation example of the sensor management device according to the fifth embodiment. FIG. 18 is a diagram showing an example of a functional configuration of a sensor management device according to a sixth embodiment. 16 is a flowchart illustrating an operation example of a sensor management device according to a sixth embodiment. FIG. 18 shows a configuration example of a sensor management system according to a seventh embodiment. FIG. 18 is a view showing an example of a screen for specifying a virtual sensor to be deleted according to the seventh embodiment. FIG. 18 is a diagram showing an example of an interface for specifying a virtual sensor to be deleted according to a seventh embodiment. FIG. 2 is a diagram showing an example of a hardware configuration of a sensor management device according to the first embodiment.

Hereinafter, embodiments of the present invention will be described with reference to the drawings. In the following description of the embodiments and drawings, the same reference numerals denote the same or corresponding parts.

Embodiment 1
*** Description of the configuration ***
FIG. 1 shows an example of a functional configuration of the sensor management device 1 according to the first embodiment.
In FIG. 1, the sensor management device 1 manages an actual sensor and a virtual sensor 15.
The operation performed by the sensor management device 1 corresponds to a sensor management method. Further, a program for realizing the sensor management method corresponds to a sensor management program.

The real sensor is physically installed in the space and actually senses the physical quantity in the space.
The actual sensor is, for example, a temperature sensor, a humidity sensor, an illuminance sensor, a human sensor or the like. The actual sensor is a device to which the name "sensor" is given.
In addition to these, real sensors include bar code readers, moving image cameras, thermo cameras, smart devices with built-in sensors, and robots.

The virtual sensor 15 is a virtual sensor installed at an arbitrary point in the space. By interpolation or estimation from the sensor values of the actual sensor, the sensor value of the virtual sensor 15 at an arbitrary point can be obtained.
In the present embodiment, the sensor management device 1 manages, as the virtual sensor 15, the virtual sensor 15a, the virtual sensor 15b, and the virtual sensor 15c.
The sensor management apparatus 1 may manage the virtual sensor 15a, the virtual sensor 15b, and the virtual sensor 15c as an object in object orientation. Further, when requested by the external module, the sensor management device 1 may obtain sensor values of the virtual sensor 15a, virtual sensor 15b and virtual sensor 15c by interpolation or estimation from sensor values of real sensors.
When it is not necessary to distinguish between the virtual sensor 15a, the virtual sensor 15b, and the virtual sensor 15c, the virtual sensor 15a, the virtual sensor 15b, and the virtual sensor 15c are collectively referred to as the virtual sensor 15.

FIG. 18 shows an example of the hardware configuration of the sensor management device 1. Before describing the functional configuration of the sensor management device 1 shown in FIG. 1, the hardware configuration of the sensor management device 1 will be described with reference to FIG. 18.

The sensor management device 1 is a computer.
The sensor management device 1 includes a processor 101, a memory 102, a communication interface 103, and an auxiliary storage device 104 as hardware.
The auxiliary storage device 104 has the functions of the attribute information acquisition unit 12, the deletion target selection unit 13, the virtual sensor deletion unit 14, the virtual sensor generation unit 16, the actual sensor data acquisition unit 17 and the sensor data distribution unit 18 shown in FIG. A program to be realized is stored. These programs are loaded from the auxiliary storage device 104 into the memory 102. Then, the processor 101 reads these programs from the memory 102 and executes these programs. As a result, the processor 101 performs operations of an attribute information acquisition unit 12, a deletion target selection unit 13, a virtual sensor deletion unit 14, a virtual sensor generation unit 16, an actual sensor data acquisition unit 17 and a sensor data distribution unit 18 described later.
In FIG. 18, a program for realizing the functions of the attribute information acquisition unit 12, the deletion target selection unit 13, the virtual sensor deletion unit 14, the virtual sensor generation unit 16, the actual sensor data acquisition unit 17, and the sensor data distribution unit 18 is shown. The state of execution is schematically represented.
Further, the auxiliary storage device 104 implements the attribute information storage unit 11 shown in FIG. Further, the auxiliary storage device 104 stores the sensor value of the actual sensor.
The communication interface 103 is used by the sensor management device 1 to communicate with the outside. Specifically, the communication interface 103 is used by the sensor management device 1 to communicate with an actual sensor.

Next, the functional configuration of the sensor management device 1 will be described with reference to FIG.

The attribute information storage unit 11 stores attribute information.
Attribute information is information in which the attributes of the real sensor and the virtual sensor 15 are indicated.
FIG. 2 shows an example of attribute information. The details of FIG. 2 will be described later.

The attribute information acquisition unit 12 acquires attribute information of the virtual sensor 15 from the attribute information storage unit 11.
The attribute information acquisition unit 12 may acquire attribute information of the virtual sensor 15 at a constant cycle, or may be triggered by an event (for example, reception of a sensor data acquisition request from outside or reception of a virtual sensor deletion request) as a trigger. The attribute information of may be acquired.

The deletion target selection unit 13 selects the virtual sensor 15 to be deleted based on the attribute of each virtual sensor 15 indicated in the attribute information of the virtual sensor 15.
Here, the number of virtual sensors 15 selected as the deletion target by the deletion target selection unit 13 does not matter.
The processing performed by the deletion target selection unit 13 corresponds to deletion target selection processing.

The virtual sensor deletion unit 14 deletes the virtual sensor 15 selected as the deletion target by the deletion target selection unit 13.
If the virtual sensor 15 is generated as an object, the virtual sensor deletion unit 14 deletes the virtual sensor 15 by deleting the corresponding object.
Alternatively, the virtual sensor deletion unit 14 may delete the virtual sensor 15 by adding a flag indicating that the virtual sensor 15 is deleted to the record of the virtual sensor 15 to be deleted in the attribute information. Alternatively, the virtual sensor deletion unit 14 may delete the virtual sensor 15 by setting “delete” in the life cycle column (described later) of the record of the virtual sensor 15 to be deleted in the attribute information.
The processing performed by the virtual sensor deletion unit 14 corresponds to virtual sensor deletion processing.

The virtual sensor generation unit 16 generates a virtual sensor 15.
The virtual sensor generation unit 16 may generate the virtual sensor 15 at a constant cycle, or may generate the virtual sensor 15 triggered by some event (for example, reception of a sensor data acquisition request from the outside).
When generating the virtual sensor 15, the virtual sensor generation unit 16 stores attribute information of the virtual sensor 15 in the attribute information storage unit 11.

The actual sensor data acquisition unit 17 acquires sensor data in which a sensor value is indicated from the actual sensor.
The actual sensor data acquisition unit 17 may acquire sensor data from the actual sensor at a constant cycle, or may acquire sensor data from the actual sensor in response to some event (for example, reception of a sensor data acquisition request from the outside). May be
The sensor data is accumulated in the auxiliary storage device 104 of the sensor management device 1. Also, instead of this, sensor data may be stored in a storage device external to the sensor management device 1.
Further, the sensor management apparatus 1 may process the memory 102 as temporary information without accumulating sensor data.

The sensor data distribution unit 18 transmits sensor data to an external device using the communication module 103. The sensor data distribution unit 18 transmits sensor data in which sensor values of actual sensors are indicated or sensor data in which sensor values of virtual sensors are indicated to an external device.
The sensor data distribution unit 18 may open the interface to the outside, receive a request from an external device, and transmit sensor data to the outside.
The sensor data distribution unit 18 may use HTTP (Hypertext Transfer Protocol) -based WEBAPI as an interface. Also, the sensor data distribution unit 18 may use a Publisher / Subscriber model such as MQTT (Message Queue Telemetry Transport) or a communication protocol with another external device.

Next, attribute information will be described with reference to FIG.

In the example of FIG. 2, the attribute information includes ID, type, expiration date, coordinates, access frequency, access flag, last access time, error, number of users, number of reservation persons, and life cycle.
The attribute information may include all the items shown in FIG. 2 or may include only some of the items shown in FIG.
In the column of ID, the identifier of the virtual sensor 15 or the real sensor is shown. The identifier is a number or symbol assigned to the virtual sensor 15 or real sensor to uniquely identify the virtual sensor 15 or real sensor.
The type column indicates whether the target sensor is a real sensor or a virtual sensor.
The column of the expiration date shows the time when the use of the virtual sensor ends.
In the column of coordinates, coordinate values of the installation position of the sensor are shown.
The access frequency column indicates the number of times the sensor has been accessed by the application. In FIG. 2, the access frequency is counted up each time access to a sensor occurs. The value of the access frequency is cleared every fixed time.
The column of the access flag indicates whether the sensor has been accessed by the application for a certain period of time from the present. When an access to a sensor occurs, the access flag becomes valid, and the access flag is cleared when a certain period of time has elapsed from the occurrence of the access, or when an event (for example, an external sensor data acquisition request is received) .
The last access time column shows the time when the sensor was last accessed by the application.
The error column shows the value of the error which is presumed to be included in the sensor value of the virtual sensor. The error column shows, for example, the value of a statistically estimated error.
The number of users column indicates the number of users using the sensor value.
The number of reservation persons column indicates the number of users who plan to use the sensor value.
The life cycle column shows stages from generation to deletion of virtual sensors.

*** Description of operation ***
FIG. 3 is a flowchart showing an operation example of the sensor management device 1 according to the first embodiment.
More specifically, FIG. 3 shows an operation example of the sensor management apparatus 1 regarding deletion of the virtual sensor 15.

The attribute information acquisition unit 12 acquires attribute information of the virtual sensor 15 from the attribute information storage unit 11 in response to a fixed cycle or some event (step ST101).
The attribute information acquisition unit 12 may acquire attribute information (multiple records) of a plurality of virtual sensors 15 at the same time, or may sequentially acquire attribute information (one record) of each virtual sensor 15. Good.
Here, an example in which the attribute information acquisition unit 12 sequentially acquires attribute information of each virtual sensor 15 will be described.
The attribute information acquisition unit 12 outputs the acquired attribute information of the virtual sensor 15 to the deletion target selection unit 13.

Next, the deletion target selection unit 13 compares the acquired attribute information with the deletion condition of the virtual sensor 15 to determine whether the deletion condition is satisfied (step ST102).
The deletion condition may be held in advance by the sensor management device 1 or may be given from the outside.
An example of the deletion condition will be described later.

The deletion target selection unit 13 selects, as a deletion target, the virtual sensor 15 whose attribute indicated in the attribute information satisfies the deletion condition (step ST103).
The deletion target selection unit 13 assigns, for example, a flag indicating that the selected deletion target virtual sensor 15 has been selected as the deletion target. Further, the deletion target selection unit 13 may simply hold the identifier of the selected virtual sensor 15 to be deleted.

An example of processing in which the deletion target selection unit 13 selects the virtual sensor 15 to be deleted is described below.

For example, the deletion target selection unit 13 can select the virtual sensor 15 included in a certain range from a specific reference point as a deletion target.
Further, the deletion target selection unit 13 can receive an identifier of the virtual sensor 15 to be deleted from the external device, and can select the virtual sensor 15 corresponding to the given identifier as the deletion target.
Further, the deletion target selection unit 13 may select the corresponding virtual sensor 15 as a deletion target according to the deletion condition in which the identifier of the virtual sensor 15 to be deleted is indicated.
Furthermore, the deletion target selection unit 13 may select the virtual sensor 15 to be deleted according to the conditions described below.

For example, the deletion target selection unit 13 may select the virtual sensor 15 to be deleted based on the position of the virtual sensor 15, which is one of the attributes of the virtual sensor 15. More specifically, the deletion target selection unit 13 calculates the distance between the virtual sensors 15 from the coordinates of the attribute information (FIG. 2). In this case, the deletion condition describes the threshold of the distance between virtual sensors. Then, the deletion target selection unit 13 selects the virtual sensor 15 to be deleted by collating the calculated distance between the virtual sensors 15 with the threshold of the distance indicated by the deletion condition.
The threshold value indicated in the deletion condition may be a fixed value or may be dynamically determined by the number of virtual sensors 15 installed in the space.
By doing this, the deletion target selection unit 13 converts a plurality of virtual sensors 15 (virtual sensor 15a, virtual sensor 15b and virtual sensor 15c) within a certain distance into one virtual sensor (for example, virtual sensor 15a) Then, other virtual sensors (for example, the virtual sensor 15 b and the virtual sensor 15 c) are selected as deletion targets.

Further, as another example of the selection of the virtual sensor 15 to be deleted based on the position of the virtual sensor 15, the deletion target selecting unit 13 determines the virtual sensor to be deleted based on the distance between the real sensor and the virtual sensor 15. You may select 15.
More specifically, the deletion target selection unit 13 calculates the distance between the real sensor and the virtual sensor 15 from the coordinates of the attribute information (FIG. 2). In this case, the deletion condition describes the threshold of the distance between the real sensor and the virtual sensor. Then, the deletion target selection unit 13 selects the virtual sensor 15 to be deleted by collating the calculated distance between the actual sensor and the virtual sensor with the threshold of the distance indicated in the deletion condition.
The threshold value indicated in the deletion condition may be a fixed value or may be dynamically determined by the number of virtual sensors 15 installed in the space.
By doing this, the deletion target selection unit 13 selects the virtual sensor 15 within a certain distance from the actual sensor as the deletion target.

Further, the deletion target selection unit 13 may select the virtual sensor 15 to be deleted based on the access status to the virtual sensor 15 which is one of the attributes of the virtual sensor 15.
More specifically, the deletion target selection unit 13 acquires the value of the access frequency of the attribute information (FIG. 2). In this case, an access frequency threshold is described in the deletion condition. Then, the deletion target selection unit 13 collates the acquired value of the access frequency with the threshold indicated in the deletion condition to select the virtual sensor 15 to be deleted.
The threshold value indicated in the deletion condition may be a fixed value or may be dynamically determined by the number of virtual sensors 15 installed in the space.
By doing this, the deletion target selection unit 13 selects a virtual sensor 15 with a low access frequency as a deletion target.

Further, as another example of the selection of the virtual sensor 15 to be deleted based on the access status to the virtual sensor 15, the deletion target selecting unit 13 may select the virtual sensor 15 to be deleted based on the access flag .
More specifically, the deletion target selection unit 13 acquires the value of the access flag in the attribute information (FIG. 2). In this case, the deletion condition describes that the access flag is cleared. Then, the deletion target selection unit 13 collates the acquired value of the access flag with the deletion condition to select the virtual sensor 15 to be deleted.
By doing this, the deletion target selection unit 13 selects, as a deletion target, the virtual sensor 15 for which access has not occurred most recently.

Further, as another example of the selection of the virtual sensor 15 to be deleted based on the access status to the virtual sensor 15, the deletion target selecting unit 13 selects the virtual sensor 15 to be deleted based on the last access time. Good.
More specifically, the deletion target selection unit 13 acquires the value of the last access time of the attribute information (FIG. 2). Then, the deletion target selection unit 13 calculates an elapsed time from the last access time. In this case, the deletion condition describes the threshold of the elapsed time from the last access time. Then, the deletion target selection unit 13 selects the virtual sensor 15 to be deleted by collating the calculated elapsed time with the threshold of the deletion condition.
The threshold value indicated in the deletion condition may be a fixed value or may be dynamically determined by the number of virtual sensors 15 installed in the space.
By doing this, the deletion target selection unit 13 selects, as the deletion target, the virtual sensor 15 for which access has not occurred even if a predetermined time has elapsed from the last access time.

Further, the deletion target selection unit 13 may select the virtual sensor 15 to be deleted based on the time validity of the virtual sensor 15 which is one of the attributes of the virtual sensor 15.
More specifically, the deletion target selection unit 13 acquires the value of the expiration date of the attribute information (FIG. 2). In this case, the deletion condition describes that the expiration date has passed. Then, the deletion target selection unit 13 collates the value of the expiration date with the deletion condition, and selects the virtual sensor 15 to be deleted.
By doing this, the deletion target selection unit 13 selects the virtual sensor 15 whose expiration date has passed as a deletion target.

Further, as another example of the selection of the virtual sensor 15 to be deleted based on the time validity of the virtual sensor 15, the deletion target selecting unit 13 may select the virtual sensor 15 to be deleted based on the life cycle .
More specifically, the deletion target selection unit 13 acquires the value of the life cycle of the attribute information (FIG. 2). In this case, the deletion condition describes that the life cycle is "end of use". Then, the deletion target selection unit 13 collates the life cycle value with the deletion condition to select the virtual sensor 15 to be deleted.
By doing this, the deletion target selection unit 13 selects the virtual sensor 15 whose life cycle is “end of use” as the deletion target.

In addition, the deletion target selection unit 13 may select the virtual sensor 15 to be deleted based on the quality of the sensor value of the virtual sensor 15 which is one of the attributes of the virtual sensor 15. More specifically, the deletion target selection unit 13 acquires the value of the error of the attribute information (FIG. 2). In this case, an error threshold is described in the deletion condition. Then, the deletion target selection unit 13 collates the value of the error with the threshold of the deletion condition to select the virtual sensor 15 to be deleted.
The threshold value indicated in the deletion condition may be a fixed value or may be dynamically determined by the number of virtual sensors 15 installed in the space.
By doing this, the deletion target selection unit 13 selects the virtual sensor 15 whose error is greater than or equal to a certain range as the deletion target.

Further, as another example of the selection of the virtual sensor 15 to be deleted based on the quality of the sensor value, the deletion target selecting unit 13 may select the virtual sensor 15 to be deleted based on the reliability of the sensor value. .
For example, it is considered to add the reliability of the sensor value as the attribute of the virtual sensor 15 to the attribute information. The reliability is an index indicating how reliable the sensor value of the virtual sensor 15 is. The reliability can be calculated, for example, by the following equation.
Reliability = ((the number of actual sensors referred to last time × the number of actual sensors referred to this time) / the square of the number of actual sensors referred to this time) × 100
The deletion target selection unit 13 acquires the value of the reliability from the attribute information. In this case, the threshold of reliability is described in the deletion information. Then, the deletion target selection unit 13 collates the value of the reliability with the threshold of the deletion condition to select the virtual sensor 15 to be deleted.
The threshold value indicated in the deletion condition may be a fixed value or may be dynamically determined by the number of virtual sensors 15 installed in the space.
By doing this, the deletion target selection unit 13 selects the virtual sensor 15 whose reliability of the sensor value is equal to or lower than a certain level as the deletion target.

Further, the deletion target selection unit 13 may select the virtual sensor 15 to be deleted based on the number of users of the virtual sensor 15 which is one of the attributes of the virtual sensor 15. More specifically, the deletion target selection unit 13 acquires the value of the number of users of the attribute information (FIG. 2). In this case, a threshold of the number of users is described in the deletion condition. Then, the deletion target selection unit 13 collates the value of the number of users with the threshold of the deletion condition, and selects the virtual sensor 15 to be deleted.
The threshold value indicated in the deletion condition may be a fixed value or may be dynamically determined by the number of virtual sensors 15 installed in the space.
By doing this, the deletion target selection unit 13 selects virtual sensors 15 whose number of users is equal to or less than a predetermined number as deletion targets.

Further, the deletion target selection unit 13 may select the virtual sensor 15 to be deleted based on the number of reservers of the virtual sensor 15 which is one of the attributes of the virtual sensor 15. More specifically, the deletion target selection unit 13 acquires the value of the number of reserved persons in the attribute information (FIG. 2). In this case, a threshold of the number of reservation persons is described in the deletion condition. Then, the deletion target selection unit 13 collates the value of the number of reserved persons with the threshold of the deletion condition, and selects the virtual sensor 15 to be deleted.
The threshold value indicated in the deletion condition may be a fixed value or may be dynamically determined by the number of virtual sensors 15 installed in the space.
By doing this, the deletion target selection unit 13 selects virtual sensors 15 whose number of reservation persons is equal to or less than a predetermined number as deletion targets.

In addition to the above, the deletion target selection unit 13 selects the virtual sensor 15 to be deleted using attribute information in which the contract number is described and a deletion condition in which the contract number for which the contract has been canceled is described. May be
By doing this, when the contract is canceled, the deletion target selection unit 13 selects the virtual sensor 15 used in the contract as the deletion target.

Further, the deletion target selection unit 13 may select the virtual sensor 15 to be deleted using attribute information in which the model of the virtual sensor 15 is described and a deletion condition regarding the model. The model is a type of virtual sensor such as a virtual sensor of a temperature sensor or a virtual sensor of a humidity sensor.
By doing this, when the virtual sensor 15 of a specific model is not used due to, for example, a change in the service menu, the deletion target selection unit 13 collectively collects virtual sensors 15 of such a specific model. Choose as.

Further, the deletion target selection unit 13 may select the virtual sensor 15 to be deleted using attribute information in which the usage charge of the virtual sensor 15 is described and a deletion condition in which the threshold of the usage charge is described. .
By doing this, the deletion target selection unit 13 selects the virtual sensor 15 whose usage fee is less than a certain level as the deletion target.
If the deleted virtual sensor is used again, there may be overhead in response time. However, the virtual sensor 15 whose usage charge is equal to or higher than a certain level can keep the response time good.

Further, the deletion target selection unit 13 may select the virtual sensor 15 to be deleted using the attribute information in which the usage purpose of the virtual sensor 15 is described and the deletion condition regarding the usage purpose.
By doing this, the deletion target selection unit 13 does not select the virtual sensor 15 used for important applications such as billing operation and emergency guidance as the deletion target, and deletes the virtual sensor 15 for other applications. Select as target.

When the sensor management device 1 manages attribute information of the virtual sensor 15 in a tree structure, the parent ID (P-ID) is included in the attribute information.
At this time, the deletion target selection unit 13 can select the virtual sensor 15 having a specific parent ID (for example, a room, an area, etc.) as a deletion target.
By doing this, the deletion target selection unit 13 can collectively select the virtual sensor 15 installed in a specific room or the virtual sensor 15 installed in a specific ridge as a deletion target.
Similarly, when the sensor management device 1 manages attribute information of the virtual sensor 15 in a tree structure, the group (G-ID) is included in the attribute information.
At this time, the deletion target selection unit 13 can select the virtual sensor 15 having a specific group ID (for example, a room, an area, etc.) as a deletion target.
By doing this, the deletion target selection unit 13 can collectively select the virtual sensor 15 installed in a specific room or the virtual sensor 15 installed in a specific ridge as a deletion target.

Further, the deletion target selection unit 13 may select a virtual sensor to be deleted using an attribute of the virtual sensor 15 different from the above-described attribute.

Next, returning to the flow of FIG. 3, the deletion target selection unit 13 determines whether or not the attribute information of all the virtual sensors 15 has been confirmed (step ST104).
If there remains a virtual sensor 15 whose attribute information has not been confirmed, the process returns to step ST101.
Here, since an example in which the attribute information acquisition unit 12 sequentially acquires attribute information of each virtual sensor 15 is described, the determination in step ST104 is necessary, but the attribute information acquisition unit 12 is not limited to all virtual If it is a method of collectively acquiring sensor attribute information at one time, the process of step ST104 is unnecessary.

When the deletion target selection unit 13 confirms the attribute information of all the virtual sensors 15 (YES in step ST104), the virtual sensor deletion unit 14 selects the virtual sensor 15 selected as the deletion target by the deletion target selection unit 13. Is deleted (step ST105).
When the virtual sensor 15 is generated as an object, the virtual sensor deletion unit 14 deletes the virtual sensor 15 by deleting the corresponding object.
Alternatively, the virtual sensor deletion unit 14 may delete the virtual sensor 15 by adding a flag indicating that the virtual sensor 15 is deleted to the record of the virtual sensor 15 to be deleted in the attribute information.
Also, the virtual sensor deletion unit 14 may delete the virtual sensor 15 by setting “Delete” in the column of the life cycle of the record of the virtual sensor 15 to be deleted in the attribute information.

*** Description of the effects of the embodiment ***
As described above, the sensor management device 1 according to the present embodiment selects the virtual sensor 15 to be deleted based on the attribute of the virtual sensor 15.
Therefore, according to the present embodiment, an unnecessary virtual sensor can be selected as a deletion target virtual sensor based on the attribute of the virtual sensor, and the unnecessary virtual sensor can be deleted. Therefore, according to this embodiment, it is possible to maintain the number of virtual sensors appropriately.

Second Embodiment
In the present embodiment, the difference from the first embodiment will be mainly described.
The items not described below are the same as in the first embodiment.

*** Description of the configuration ***
FIG. 4 shows an example of a functional configuration of the sensor management device 1 according to the second embodiment.

In the present embodiment, in addition to the deletion of the virtual sensor 15, the virtual sensor deletion unit 14 calculates the density of the virtual sensor 15, and requests the virtual sensor generation unit 16 to generate a virtual sensor according to the density.
The density of the virtual sensor 15 is the density of the virtual sensor 15 in the space where the virtual sensor 15 is installed. For example, the virtual sensor deletion unit 14 divides the number of virtual sensors 15 by the volume of space to obtain the density of the virtual sensors 15.
More specifically, the virtual sensor deletion unit 14 calculates the density of the virtual sensor 15 after deletion of the virtual sensor 15 in the space where the virtual sensor 15 is installed. Then, the virtual sensor deleting unit 14 determines the necessity of generation of a new virtual sensor 15 based on the calculated density. When it is determined that the generation of a new virtual sensor 15 is necessary, the virtual sensor deletion unit 14 requests the virtual sensor generation unit 16 to generate the virtual sensor 15.
The virtual sensor generation unit 16 generates the virtual sensor 15 based on the request from the virtual sensor deletion unit 14.
There is no limitation on the method of generating the virtual sensor 15 by the virtual sensor generation unit 16. The virtual sensor generation unit 16 can generate the virtual sensor 15 using a known method.
Note that a hardware configuration example of the sensor management device 1 according to the present embodiment is also as shown in FIG.

*** Description of operation ***
FIG. 5 is a flowchart showing an operation example of the sensor management device 1 according to the second embodiment.
The operation of FIG. 5 is performed after the process of step ST104 of FIG. 3 described in the first embodiment.

First, the virtual sensor deletion unit 14 calculates the density of the virtual sensor 15 before deletion (step ST201).
The virtual sensor deleting unit 14 can obtain the density of the virtual sensors 15 from the number of the virtual sensors 15 in the space, using the coordinates of each virtual sensor 15 indicated in the attribute information.
The virtual sensor deleting unit 14 may calculate one density over the entire space, or may divide the space into areas and calculate the density for each area.
The virtual sensor deleting unit 14 determines the virtual sensor 15 based on the current number of virtual sensors 15, that is, the number of virtual sensors 15 before the virtual sensor 15 to be deleted selected in step ST103 of FIG. 3 is deleted. Find the density of

Next, virtual sensor deletion unit 14 calculates the density of virtual sensor 15 after deletion (step ST202).
That is, the virtual sensor deleting unit 14 obtains the density of the virtual sensors 15 based on the number of virtual sensors 15 after the virtual sensor 15 to be deleted selected in step ST103 of FIG. 3 is deleted.
The calculation method of the density is the same method as the calculation of the density of the virtual sensor 15 before deletion.

Next, the virtual sensor deletion unit 14 determines whether the density of the virtual sensor 15 after deletion is insufficient (step ST203). That is, the virtual sensor deletion unit 14 determines whether the density of the virtual sensor 15 after deletion is less than the threshold.
The threshold of density may be predefined, or may be determined dynamically according to the number of actual sensors and virtual sensors 15.

If the density of the virtual sensor 15 after deletion is insufficient, that is, if the density of the virtual sensor 15 after deletion is less than the threshold (YES in step ST203), the sensor management device 1 determines that the virtual sensor deletion unit 14 is virtual In order to generate the sensor 15, an attribute value of the virtual sensor 15 is defined (step ST204). That is, the virtual sensor deletion unit 14 generates attribute information of the virtual sensor 15 to be newly generated.
The attribute information includes information (e.g., coordinates) necessary to calculate the density of the virtual sensor 15.
The virtual sensor deletion unit 14 generates attribute information of the virtual sensor 15 based on parameters such as the distance to the real sensor.
The virtual sensor deletion unit 14 may collectively define attribute information of a plurality of virtual sensors 15.
In the example of FIG. 5, the virtual sensor deleting unit 14 repeats the processing from step ST202 to step ST204 until the density of the virtual sensor 15 after deletion becomes equal to or higher than the threshold.

When virtual sensor deletion unit 14 determines that the density of virtual sensor 15 after deletion is equal to or higher than the threshold (YES in step ST203), virtual sensor generation unit 16 is requested to generate virtual sensor 15, and virtual sensor generation unit 14 16 generates the virtual sensor 15 according to the attribute information (step ST205).
As described above, the method of generating the virtual sensor 15 by the virtual sensor generation unit 16 is not limited.

Next, the virtual sensor deletion unit 14 deletes the virtual sensor 15 selected as the deletion target in step ST103 of FIG. 3 (step ST206).
The process of deleting the virtual sensor 15 is the same as the process described in the first embodiment.

*** Description of the effects of the embodiment ***
As described above, according to the present embodiment, even when the virtual sensor is deleted, the density of the virtual sensor in the space can be maintained at a certain level or more. Thus, the virtual sensor can be deleted while suppressing the influence on the service.

Third Embodiment
In the present embodiment, the difference from the first embodiment will be mainly described.
The items not described below are the same as in the first embodiment.

*** Description of the configuration ***
FIG. 6 shows an example of a functional configuration of the sensor management device 1 according to the third embodiment.
Compared to FIG. 1, an access probability estimation unit 19 and an access model storage unit 20 are added in FIG.
Note that a hardware configuration example of the sensor management device 1 according to the present embodiment is also as shown in FIG.

The access probability estimation unit 19 estimates the access probability using the access model acquired from the access model storage unit 20.
The access probability is an attribute of the virtual sensor 15. The access probability is an occurrence probability of access to the virtual sensor 15.

The access model storage unit 20 stores an access model.
The access model refers to an access tendency or pattern that can be derived from the past access history or access history of the virtual sensor 15.
An example of the access model will be described later.

In the present embodiment, the deletion target selection unit 13 selects the virtual sensor 15 to be deleted using the attribute information acquired from the attribute information acquisition unit 12 and the access probability acquired from the access probability estimation unit 19.
The determination based on the attribute information is the same as in the first embodiment.
The deletion target selection unit 13 defines a threshold for the access probability.
The deletion target selection unit 13 may define a fixed value according to the type of the virtual sensor 15 as the threshold for the access probability, or dynamically determines the threshold according to the number of virtual sensors 15 or the number of real sensors. May be

FIG. 7 shows an example of the access model according to the present embodiment.

In the ID column, the identifier of the virtual sensor 15 is shown. The identifier is a number or a symbol assigned to the virtual sensor 15 to uniquely identify the virtual sensor 15. In the access model, the same identifier as the identifier described in the attribute information is described.
The time of access to the virtual sensor 15 is indicated in the column of access time.
The access user column indicates the application or user who has made access to the virtual sensor 15.
In the example of FIG. 7, one record of the access model is added each time access occurs.
The access model may be managed by dividing it into unit periods such as one year or one month.
If the unit period is one year, it is possible to generate an access model in which seasonal features are shown. In addition, if the unit period is one month, it is possible to generate an access model in which the latest usage condition of the virtual sensor 15 is indicated.

*** Description of operation ***
FIG. 8 is a flowchart showing an operation example of the sensor management device 1 according to the third embodiment.
The operation of FIG. 8 is performed instead of the operation of FIG. 3 described in the first embodiment.

Since step ST301 is the same as step ST101 of FIG. 3, the description of step ST301 is omitted.

Next, the access probability estimation unit 19 acquires an access model from the access model storage unit 20 in accordance with the process of selecting the virtual sensor 15 to be deleted (ST 302).

Next, the access probability estimation unit 19 estimates the access probability using the acquired access model (ST 303).
If the shape of the probability model is known in advance, the access probability estimation unit 19 may estimate the access probability by deriving the probability model by a parametric method.
In addition, if the shape of the probabilistic model is not known in advance, the access probability estimating unit 19 may estimate the access probability by deriving the probabilistic model using a nonparametric method.

Next, the deletion target selection unit 13 uses the attribute information acquired in step ST301 and the access probability estimated by the access probability estimation unit 19 in step ST303 to determine whether or not the virtual sensor 15 satisfies the deletion condition ( Step ST304).
Since step ST305 to step ST307 are the same as step ST103 to step ST105 of FIG. 3, the description of step ST305 to step ST307 is omitted.

In the example of FIG. 8, the deletion target selection unit 13 selects the virtual sensor 15 to be deleted using the attribute information and the access probability. Instead of this, the deletion target selection unit 13 may select the virtual sensor 15 to be deleted using only the access probability.

*** Description of the effects of the embodiment ***
As described above, in the present embodiment, the virtual sensor 15 to be deleted is selected using the access probability. Therefore, according to the present embodiment, the number of virtual sensors 15 can be more appropriately maintained as compared with the case where the virtual sensor 15 to be deleted is selected using only attribute information.

Fourth Embodiment
In the present embodiment, the difference from the first embodiment will be mainly described.
The items not described below are the same as in the first embodiment.

*** Description of the configuration ***
FIG. 9 shows an example of a functional configuration of the sensor management device 1 according to the fourth embodiment.
Compared with FIG. 1, in FIG. 9, an actual sensor detection unit 21 is added.

The actual sensor detection unit 21 detects a change in the arrangement of the actual sensors in the space where the virtual sensor 15 is installed. That is, the actual sensor detection unit 21 detects the addition of the actual sensor and the change of the installation position.
The actual sensor detection unit 21 can detect a change in the arrangement of the actual sensors by a method of searching for the actual sensors at a constant cycle. Further, the actual sensor detection unit 21 may detect a change in the arrangement of the actual sensors by an event-driven method that receives a notification from the actual sensors.

In the present embodiment, the deletion target selection unit 13 selects the virtual sensor 15 to be deleted based on the positional relationship between the real sensor and the real sensor after the change of the arrangement of the real sensor.

*** Description of operation ***
FIG. 10 is a flowchart showing an operation example of the sensor management device 1 according to the fourth embodiment.
The operation of FIG. 10 is performed instead of the operation of FIG. 3 described in the first embodiment.

First, the actual sensor detection unit 21 detects a change in the arrangement of the actual sensor from the state of the actual sensor (ST401).
The actual sensor detection unit 21 can detect a change in the arrangement of the actual sensors by a method of searching for the actual sensors at a constant cycle. Further, the actual sensor detection unit 21 may detect a change in the arrangement of the actual sensors by an event-driven method that receives a notification from the actual sensors.

When detecting the change in the arrangement of the actual sensors, the actual sensor detection unit 21 determines whether the change is due to the addition of the actual sensors or the change in the installation position of any of the actual sensors (step ST402).

When the change of the arrangement of the actual sensor is the addition of the actual sensor or the change of the installation position of the actual sensor (YES in step ST402), the deletion target selection unit 13 detects the attribute of the virtual sensor 15 via the attribute information acquisition unit 12. Information is acquired from the attribute information storage unit 11 (step ST403).
Then, the deletion target selection unit 13 determines whether the attribute of each virtual sensor 15 satisfies the deletion condition (step ST404). In the present embodiment, it is assumed that the threshold value of the distance from the real sensor is described in the deletion condition. The deletion target selection unit 13 selects, as a deletion target, the virtual sensor 15 in which the distance to the real sensor is less than the threshold value by adding the real sensor or changing the installation position of the real sensor.
Since step ST406 and step ST407 are the same as step ST104 and step ST105 of FIG. 3, the description of step ST406 and step ST407 is omitted.
On the other hand, when the change of the arrangement of the actual sensor is the deletion of the actual sensor in step ST402, the process ends.

*** Description of the effects of the embodiment ***
As mentioned above, according to this embodiment, unnecessary virtual sensor 15 can be deleted according to addition of an actual sensor or change of an installation position. Thereby, according to the present embodiment, the number of virtual sensors 15 can be appropriately maintained without losing the density of sensing.

Embodiment 5
In the present embodiment, the difference from the first embodiment will be mainly described.
The items not described below are the same as in the first embodiment.

*** Description of the configuration ***
FIG. 11 shows a functional configuration example of the sensor management device 1 according to the fifth embodiment.
Compared to FIG. 1, in FIG. 11, a failure sensor detection unit 22 is added.
Note that a hardware configuration example of the sensor management device 1 according to the present embodiment is also as shown in FIG.

The failure sensor detection unit 22 confirms the state of the actual sensor installed in the space where the virtual sensor 15 is installed, and detects the failure of the actual sensor.
The failure sensor detection unit 22 can detect a failure of an actual sensor by a method of searching for the actual sensor at a constant cycle. Further, the failure sensor detection unit 22 may detect the failure of the actual sensor by an event-driven method that receives a notification from the actual sensor.
In the following, the actual sensor having a fault detected by the fault sensor detection unit 22 is also referred to as a fault sensor.

In the present embodiment, the virtual sensor generation unit 16 generates a virtual sensor 15 that substitutes for the failure sensor.

*** Description of operation ***
FIG. 12 is a flowchart showing an operation example of the sensor management device 1 according to the fifth embodiment.
The operation of FIG. 12 is performed independently of the operation of FIG. 3, the operation of FIG. 5, the operation of FIG. 8, and the operation of FIG.

First, the failure sensor detection unit 22 detects a change in the state of an actual sensor (step ST501).
The failure sensor detection unit 22 can detect a change in the state of the real sensor by a method of searching the real sensor in a constant cycle. In addition, the failure sensor detection unit 22 may detect a change in the state of the real sensor by an event-driven method that receives a notification from the real sensor.

Next, the failure sensor detection unit 22 determines whether or not the change in the state of the actual sensor detected in step ST501 is due to the failure of the actual sensor (step ST502).
For example, it is assumed that the auxiliary storage device 104 stores pattern information in which a pattern of change in state that occurs when the actual sensor fails. The failure sensor detection unit 22 reads out the pattern information from the auxiliary storage device 104, and collates the change in the state detected in step ST501 with the pattern information so that the change in the state of the actual sensor detected in step ST501 is an actual sensor. It is determined whether or not it is due to a failure.

If the failure sensor detection unit 22 determines that the actual sensor is broken (YES in step ST 502), the virtual sensor generation unit 16 defines attribute values of the virtual sensor 15 for generation of the virtual sensor 15 (FIG. Step ST503). That is, the virtual sensor generation unit 16 generates attribute information of the virtual sensor 15 to be newly generated.
More specifically, the virtual sensor generation unit 16 acquires attribute information of the failure sensor, and based on the acquired attribute information of the failure sensor, attribute information in which the same model as the failure sensor and the same coordinates as the failure sensor are defined Generate (ST 503 to ST 504).
The virtual sensor generation unit 16 generates the virtual sensor 15 of the same model as the failure sensor on the same coordinates as the failure sensor based on the attribute information.

*** Description of the effects of the embodiment ***
As described above, according to the present embodiment, a new virtual sensor 15 can be added according to the failure of the actual sensor. Thus, according to the present embodiment, even when the actual sensor fails, the number of virtual sensors 15 can be appropriately maintained without losing the density of sensing.

Sixth Embodiment
In the present embodiment, differences from the fifth embodiment will be mainly described.
The items not described below are the same as in the fifth embodiment.

*** Description of the configuration ***
FIG. 13 shows an example of a functional configuration of the sensor management device 1 according to the sixth embodiment.
Compared with FIG. 11, in FIG. 13, a virtual sensor reconfiguration unit 23 is added.

The virtual sensor reconfiguration unit 23 extracts a virtual sensor dependent on the fault sensor as a fault-dependent virtual sensor. Then, the virtual sensor reconfiguration unit 23 changes the attribute of the fault-dependent virtual sensor such that the fault-dependent virtual sensor depends on an actual sensor other than the fault sensor.

In the present embodiment, it is assumed that the attribute information indicates, for each virtual sensor 15, an identifier of an actual sensor that is dependent on the virtual sensor 15 (refers to a sensor value).

*** Description of operation ***
FIG. 14 is a flowchart showing an operation example of the sensor management device 1 according to the sixth embodiment.
The operation of FIG. 14 is performed, for example, instead of the operation of FIG. In addition, the operation of FIG. 14 may be performed together with the operation of FIG. When the operation of FIG. 14 is performed together with the operation of FIG. 12, step ST601 and step ST602 of FIG. 14 are omitted.

Since step ST601 and step ST602 are the same as step ST501 and step ST502 of FIG. 12, the description of step ST601 and step ST602 is omitted.

If the failure sensor detection unit 22 determines that the real sensor is broken (YES in step ST502), the virtual sensor reconfiguration unit 23 acquires attribute information of the virtual sensor 15 from the attribute information storage unit 11 (step ST603). ).
In the example of FIG. 14, the virtual sensor reconfiguration unit 23 sequentially acquires attribute information of each virtual sensor 15, but the virtual sensor reconfiguration unit 23 acquires attribute information of a plurality of virtual sensors 15 in parallel. You may

The virtual sensor reconfiguration unit 23 determines, for each virtual sensor 15, whether or not the attribute of the virtual sensor 15 satisfies the reconstruction condition, using the acquired attribute information (step ST604).
The reconstruction condition describes the condition that the virtual sensor 15 depends on the failure sensor (refers to the sensor value of the failure sensor).
The virtual sensor reconfiguration unit 23 investigates the dependent real sensor using attribute information for each virtual sensor 15, and extracts the virtual sensor 15 depending on the faulty sensor as a fault-dependent virtual sensor.

If there is a virtual sensor 15 that satisfies the reconfiguration condition (YES in step ST604), that is, if there is a fault-dependent virtual sensor, virtual sensor reconfiguration unit 23 reconfigures the fault-dependent virtual sensor (step ST605). ).
Reconfiguration is to change the real sensor that the fault-dependent virtual sensor depends on (refers to the sensor value) from the fault sensor to another real sensor.
That is, on the attribute information of the fault dependent virtual sensor, the virtual sensor reconfiguration unit 23 deletes the dependency of the fault dependent virtual sensor on the fault sensor, and adds the dependency on an actual sensor other than the fault sensor.

When the processing from step ST603 to step ST605 has been performed on all the virtual sensors 15 (step ST606), the virtual sensor reconfiguration unit 23 ends the processing.

*** Description of the effects of the embodiment ***
As mentioned above, according to this embodiment, virtual sensor 15 can be reconfigured according to the failure of an actual sensor. Thereby, according to the present embodiment, even when the actual sensor fails, accuracy degradation of the virtual sensor 15 can be suppressed to a certain level, and as a result, the virtual sensor can be maintained without losing the sensing density. The number of 15 can be maintained properly.

Embodiment 7
In the present embodiment, the difference from the first embodiment will be mainly described.
The items not described below are the same as in the first embodiment.

FIG. 15 shows a configuration example of a sensor management system according to the seventh embodiment.

The sensor management system according to the present embodiment includes a sensor management device 1, a web server device 4, and a terminal device 5.
The sensor management device 1 is the sensor management device 1 described in the first to sixth embodiments, and manages the actual sensor 2 and the virtual sensor 3.
Further, in the present embodiment, the sensor management device 1 plays a role of providing an interface between the web server device 4 and the real sensor 2 and the virtual sensor 3.

The actual sensor 2 is the actual sensor described in the first to sixth embodiments.
The virtual sensor 3 is the virtual sensor 15 described in the first to sixth embodiments. The virtual sensor 3 is generated by the sensor management device 1 and deleted.

The web server device 4 provides a service using sensor data.
The application executed by the Web server device 4 acquires sensor data using the interface of the sensor management device 1 to provide a service.
In the present embodiment, it is assumed that the service is realized as a web service.

The terminal device 5 is used by an end user to receive a service from the Web server device 4.
The terminal device 5 is, for example, a personal computer or a smart device (tablet terminal, smart phone, smart watch).
The end user uses the terminal device 5 to use the service using sensor data by the Web server device 4.

FIG. 16 shows an example of a screen displayed on the terminal device 5 when the end user designates the virtual sensor 3 to be deleted.
The user designates the virtual sensor 3 to be deleted using the screen of FIG.
In the example of FIG. 16, the user can specify the virtual sensor 3 to be deleted on the coordinates of vertical (X), horizontal (Y), and height (Z). The user can also specify the virtual sensor 3 to be deleted in the range of coordinates. Furthermore, the user can also specify the virtual sensor 3 to be deleted using the sensor ID.
When the user clicks the delete button, deletion of the virtual sensor is performed.
The user can also specify the virtual sensor 3 to be deleted using another attribute value of the virtual sensor 3.
For example, when the terminal device 5 accesses the sensor management device 1, the screen shown in FIG. 16 is transmitted from the sensor management device 1 to the terminal device 5 and the screen shown in FIG. 16 is displayed on the display of the terminal device 5. .
In the sensor management device 1, the deletion target selection unit 13 deletes the virtual sensor 3 specified by the end user through the screen shown in FIG.

FIG. 17 shows an example of an interface provided by the sensor management device 1 in order to delete the virtual sensor 15 from the outside of the sensor management device 1.

The sensor management device 1 provides an interface to the outside. The external application can delete the virtual sensor 3 by the interface provided by the sensor management device 1.
The URL 1 is an example of an interface for specifying the virtual sensor 3 to be deleted with a sensor ID and deleting the specified virtual sensor 3.
The URL 2 is an example of an interface for specifying the virtual sensor 3 to be deleted by coordinates and deleting the specified virtual sensor 3.
The URL 3 is an example of an interface for specifying the virtual sensor 3 to be deleted in a hierarchical structure and deleting the specified virtual sensor 3.

As described above, according to the present embodiment, an end user can use a service using an actual sensor and a virtual sensor. Further, according to the present embodiment, the number of virtual sensors can be appropriately maintained so as not to affect the service.

As mentioned above, although embodiment of this invention was described, you may combine and implement two or more among these embodiment.
Alternatively, one of these embodiments may be partially implemented.
Alternatively, two or more of these embodiments may be implemented in combination.
The present invention is not limited to these embodiments, and various modifications can be made as needed.

*** Description of hardware configuration ***
Finally, a supplementary description of the hardware configuration of the sensor management device 1 will be made.
The processor 101 illustrated in FIG. 18 is an integrated circuit (IC) that performs processing.
The processor 101 is a central processing unit (CPU), a digital signal processor (DSP), or the like.
A memory 102 illustrated in FIG. 18 is a random access memory (RAM).
The auxiliary storage device 104 illustrated in FIG. 18 is a read only memory (ROM), a flash memory, a hard disk drive (HDD), or the like.
The communication interface 103 illustrated in FIG. 18 is an electronic circuit that executes communication processing.
The communication interface 103 is, for example, a communication chip or a NIC (Network Interface Card).

Further, an OS (Operating System) is also stored in the auxiliary storage device 104.
Then, at least a part of the OS is executed by the processor 101.
The processor 101 executes at least a part of the OS, while the attribute information acquisition unit 12, the deletion target selection unit 13, the virtual sensor deletion unit 14, the virtual sensor generation unit 16, the actual sensor data acquisition unit 17, the sensor data distribution unit 18, A program that implements the functions of the access probability estimation unit 19, the actual sensor detection unit 21, the failure sensor detection unit 22, and the virtual sensor reconfiguration unit 23 is executed.
As the processor 101 executes the OS, task management, memory management, file management, communication control and the like are performed.
The attribute information acquisition unit 12, the deletion target selection unit 13, the virtual sensor deletion unit 14, the virtual sensor generation unit 16, the actual sensor data acquisition unit 17, the sensor data distribution unit 18, the access probability estimation unit 19, and the actual sensor detection unit 21. , Information indicating the processing result of the fault sensor detection unit 22 and the virtual sensor reconfiguration unit 23, at least one of data, signal value and variable value, the memory 102, the auxiliary storage device 104, the register in the processor 101, and cache memory Are stored in at least one of
The attribute information acquisition unit 12, the deletion target selection unit 13, the virtual sensor deletion unit 14, the virtual sensor generation unit 16, the actual sensor data acquisition unit 17, the sensor data distribution unit 18, the access probability estimation unit 19, and the actual sensor detection unit 21. Programs for realizing the functions of the failure sensor detection unit 22 and the virtual sensor reconfiguration unit 23 are stored in a portable storage medium such as a magnetic disk, a flexible disk, an optical disk, a compact disk, a Blu-ray (registered trademark) disk, and a DVD. It is also good.

The attribute information acquisition unit 12, the deletion target selection unit 13, the virtual sensor deletion unit 14, the virtual sensor generation unit 16, the actual sensor data acquisition unit 17, the sensor data distribution unit 18, the access probability estimation unit 19, and the actual sensor detection unit 21. The “parts” of the failure sensor detection unit 22 and the virtual sensor reconstruction unit 23 may be read as “circuits” or “processes” or “procedures” or “processes”.
Also, the sensor management device 1 may be realized by a processing circuit. The processing circuit is, for example, a logic integrated circuit (IC), a gate array (GA), an application specific integrated circuit (ASIC), or a field-programmable gate array (FPGA).
In this case, the attribute information acquisition unit 12, the deletion target selection unit 13, the virtual sensor deletion unit 14, the virtual sensor generation unit 16, the actual sensor data acquisition unit 17, the sensor data distribution unit 18, the access probability estimation unit 19, the actual sensor detection The unit 21, the failure sensor detection unit 22, and the virtual sensor reconfiguration unit 23 are each realized as part of a processing circuit.
Note that, in this specification, the upper concept of the processor, the memory, the combination of the processor and the memory, and the processing circuit is referred to as "processing circuit".
That is, the processor, the memory, the combination of the processor and the memory, and the processing circuit are specific examples of the "processing circuit".

DESCRIPTION OF SYMBOLS 1 sensor management apparatus, 2 real sensor, 3 virtual sensor, 4 web server apparatus, 5 terminal device, 11 attribute information storage part, 12 attribute information acquisition part, 13 deletion object selection part, 14 virtual sensor deletion part, 15 virtual sensor, 16 virtual sensor generation unit, 17 real sensor data acquisition unit, 18 sensor data distribution unit, 19 access probability estimation unit, 20 access model storage unit, 21 real sensor detection unit, 22 fault sensor detection unit, 23 virtual sensor reconfiguration unit, 101 processor, 102 memory, 103 communication interface, 104 auxiliary storage.

Claims (13)

1. A deletion target selection unit that selects a virtual sensor to be deleted from among the plurality of virtual sensors based on the attributes of each of the plurality of virtual sensors that have been generated;
   A sensor management apparatus comprising: a virtual sensor deletion unit configured to delete a virtual sensor selected as a deletion target by the deletion target selection unit.
2. The deletion target selection unit
   The sensor management apparatus according to claim 1, wherein the virtual sensor to be deleted is selected based on the position of each virtual sensor that is an attribute of each virtual sensor.
3. The deletion target selection unit
   The sensor management device according to claim 1, wherein the virtual sensor to be deleted is selected based on an access situation to each virtual sensor, which is an attribute of each virtual sensor.
4. The deletion target selection unit
   The sensor management device according to claim 1, wherein the virtual sensor to be deleted is selected based on the time validity of each virtual sensor that is an attribute of each virtual sensor.
5. The deletion target selection unit
   The sensor management device according to claim 1, wherein the virtual sensor to be deleted is selected based on the quality of the sensor value of each virtual sensor that is an attribute of each virtual sensor.
6. The deletion target selection unit
   The sensor management apparatus according to claim 1, wherein the virtual sensor to be deleted is selected based on the probability of occurrence of access to each virtual sensor, which is an attribute of each virtual sensor.
7. The virtual sensor deletion unit
   The density of the virtual sensor after virtual sensor deletion in the space where the plurality of virtual sensors are installed is calculated, and based on the calculated density, it is determined whether or not generation of a new virtual sensor is necessary,
   The sensor management device further comprises
   The sensor management device according to claim 1, further comprising: a virtual sensor generation unit that generates a new virtual sensor when it is determined by the virtual sensor deletion unit that generation of a new virtual sensor is necessary.
8. The sensor management device further comprises
   It has an actual sensor detection unit that detects a change in the arrangement of actual sensors in the space where the plurality of virtual sensors are installed,
   The deletion target selection unit
   The sensor management device according to claim 1, wherein the virtual sensor to be deleted is selected based on the positional relationship between each virtual sensor and the actual sensor, which is an attribute of each virtual sensor.
9. The sensor management device further comprises
   A failure sensor detection unit installed in a space where the plurality of virtual sensors are installed, for detecting a failure sensor that is a real sensor that is broken;
   The sensor management device according to claim 1, further comprising: a virtual sensor generation unit configured to generate a virtual sensor that substitutes the failure sensor.
10. The sensor management device further comprises
    A failure sensor detection unit installed in a space where the plurality of virtual sensors are installed, for detecting a failure sensor that is a real sensor that is broken;
    The virtual sensor that depends on the fault sensor is extracted as a fault-dependent virtual sensor from the plurality of virtual sensors, and the fault is dependent on an actual sensor other than the fault sensor installed in the space. The sensor management device according to claim 1, further comprising: a virtual sensor reconfiguration unit that changes an attribute of the dependent virtual sensor.
11. The virtual sensor deletion unit
    The sensor management device according to claim 1, wherein the virtual sensor specified by the user is deleted.
12. The computer selects a virtual sensor to be deleted from among the plurality of virtual sensors based on the attribute of each of the plurality of generated virtual sensors,
    The sensor management method which the said computer deletes the virtual sensor selected as deletion object.
13. A deletion target selection process of selecting a virtual sensor to be deleted from among the plurality of virtual sensors based on the attribute of each of the plurality of virtual sensors that have been generated;
    A sensor management program which causes a computer to execute virtual sensor deletion processing for deleting a virtual sensor selected as a deletion target by the deletion target selection processing.

Images