JP6750526B2 - Communication device and communication method - Google Patents

Description

The present invention relates to a communication device and a communication method.

Various IoT (Internet of Things) services have been realized with the diversification of devices such as smartphones, tablet terminals, and wearable computers. Media data sensed by a camera, a microphone, or the like mounted on the device is utilized for such an IoT service. For example, there is known a life log that records human life, actions, and experiences in addition to position information as well as media data such as video and audio.

Here, when the IoT device used for the IoT service is a user device carried by the user, there is a battery limitation in its operation. For this reason, there are cases where a field device installed in various environments such as a facility or a section of the facility substitutes the IoT service by the user device.

JP, 2014-217023, A JP, 2004-336310, A

However, in the above technique, the device used for the IoT service may frequently switch.

That is, the user may stay in a certain place until the IoT service ends, or the user's whereabouts may not be constant. For this reason, if the location of the user is not fixed even when trying to utilize the field device installed in the environment, the device used for the IoT service must be switched from the user device to the field device and then returned from the field device to the user device again. Fall into a situation where it must be. If the switching frequently occurs in this way, the subject performing the sensing also frequently switches, and thus the quality of the IoT service deteriorates.

In one aspect, an object of the present invention is to provide a communication apparatus and a communication method that can reduce the frequency of switching devices used for IoT services.

In one aspect, a detection unit that detects a time when the first terminal enters an area where the first terminal can access the device and a time when the access is disabled, and a storage unit that stores an accessible time determined from each detected time. When the second terminal detects that the own terminal is accessible, the selecting section selects the own apparatus or the second terminal based on the accessible time stored in the storage section.

The frequency of switching devices used for the IoT service can be reduced.

FIG. 1 is a diagram illustrating a configuration example of the IoT system according to the first embodiment. FIG. 2 is a block diagram of the functional configuration of the server device according to the first embodiment. FIG. 3 is a diagram showing an example of access history data. FIG. 4 is a diagram showing an example of access history data. FIG. 5 is a flowchart of a device selection process procedure according to the first embodiment. FIG. 6 is a flowchart showing a procedure of an application example of the device selection processing. FIG. 7 is a diagram illustrating a hardware configuration example of a computer that executes the communication program according to the first and second embodiments.

A communication device and a communication method according to the present application will be described below with reference to the accompanying drawings. Note that this embodiment does not limit the disclosed technology. Then, the respective embodiments can be appropriately combined within a range in which the processing contents do not contradict each other.

[IoT system]
FIG. 1 is a diagram illustrating a configuration example of the IoT system according to the first embodiment. The IoT system 1 shown in FIG. 1 provides a device selection service for selecting an IoT device that performs sensing of media data used for an IoT service from the user device 30 or the field devices 50A to 50C.

As shown in FIG. 1, the IoT system 1 includes a server device 10, a user device 30, and field devices 50A to 50C. Although one user device 30 and three field devices 50A to 50C are illustrated in FIG. 1, any number of user devices and field devices may be accommodated in the server device 10. Hereinafter, the field devices 50A to 50C may be collectively referred to as "field device 50".

The server device 10 is connected to the user device 30 and the field device 50 via the network NW. This network NW can be constructed by any communication network, whether wired or wireless. Furthermore, a wired or wireless communication network may be mixed in a part of the network NW. For example, the network NW may include a relay device such as the nearest base station or access point corresponding to the cell accommodating the user device 30.

The server device 10 is a computer that provides the user device 30 with the device selection service described above.

As one embodiment, the server device 10 can be implemented by installing a device selection program that realizes the above-described device selection service in a desired computer as packaged software or online software. For example, the server device 10 may be implemented as a Web server that provides the device selection service described above, or may be implemented as a cloud that provides the device selection service described above by outsourcing.

The user device 30 is an IoT device carried by a user.

As one embodiment, not only a mobile communication terminal such as a smartphone, a mobile phone or a PHS (Personal Handyphone System) but also a tablet terminal or a slate terminal can be adopted as the user device 30. As described above, the user device 30 is not limited to the handheld type mobile terminal device, and the user device 30 may be a wearable device such as a head mounted display, smart glasses or smart watches, or any mobile terminal device.

The user device 30 can sense media data such as audio and video using a sensor mounted on the user device 30. For example, a microphone mounted on the user device 30 can be used for voice sensing. The microphone may have directivity in a specific direction or may be non-directional. Further, a camera mounted on the user device 30 can be used for image sensing. The image captured by this camera may be a still image or a moving image.

The field device 50 is an IoT device installed in various environments. The “environment” mentioned here may include any place as long as the IoT device can be placed. For example, a facility, a room or a tenant included in the facility, or a booth or a compartment divided into the facility, the room, or the tenant is included.

As one aspect, the ICT infrastructure of the field device 50, for example, the network connection function, the media sensing function, and the like are open to users who use the IoT service. That is, the user is given an account used for using the IoT service, and by logging in to this account via the user device 30, it is possible to receive the above-mentioned device selection service from the server device 10. It becomes a state.

For example, the field device 50 may be a stationary device or a stationary device. For example, a camera with a microphone may be provided in the environment from the viewpoint of realizing entrance/exit management, monitoring, authentication, and the like. Such a camera with a microphone can perform media data sensing performed by the user device 30 in accordance with an instruction from the server device 10. Besides, a stationary or notebook computer, such as a personal computer, in which a microphone is connected via a microphone terminal can be mounted as the field device 50. Further, in many relay devices such as a gateway device, various devices can be connected via a USB (Universal Serial Bus) terminal, so that this can be mounted as the field device 50. In addition, a display device may be installed in the facility for the purpose of guidance, advertisement, issuance of coupons, and the like. Techniques such as line-of-sight recognition, voice recognition, and gesture recognition may be used for operations on the display device. In this case, since a camera or a microphone is attached to or built in the display device, such a display device can also be mounted as the field device 50. Thus, the field device 50 can be a device connected to an external power source such as a commercial power source. Here, for convenience of explanation, the case where the field device 50 is a stationary or stationary device is illustrated as an example, but a user device carried by another user may be the field device 50. it can.

As described above, in the IoT system 1, not only the user device 30 but also the field device 50 is added as an option of the IoT device that executes the sensing of the media data used for the IoT service.

That is, the user device 30 described above is not always able to operate in a state of being connected to an external power source, and operates by the power supplied from the battery. Under such a circumstance, if the microphone and the camera are continuously driven, the battery consumption becomes heavy. As a result, the battery of the user device 30 may run out before the IoT service ends.

As one aspect of suppressing the interruption of the IoT service due to such battery exhaustion, the server device 10 delegates media data sensing to the field device 50 existing around the user device 30. For example, in FIG. 1, as an example, three field devices 50A, 50B and 50C are installed in service areas E1, E2 and E3. As described above, there is a situation in which the three other devices such as the field devices 50A, 50B, and 50C can be made to act for sensing the media data in the user device 30. For example, as shown in FIG. 1, when the user device 30 is located in the service area E2, the field device 50B can be made to act on behalf of sensing the media data in the user device 30.

However, the user may stay in a certain place until the IoT service ends, or the user's whereabouts may not be constant. For this reason, if the user's location is not constant even when trying to utilize the field device 50 installed in the environment, the device used for the IoT service is switched from the user device 30 to the field device 50, and then the field device 50 returns to the user. It falls into the situation where it has to be returned to the device 30. If the switching frequently occurs in this way, the subject performing the sensing also frequently switches, and thus the quality of the IoT service deteriorates.

Therefore, the server device 10 according to the present embodiment is a medium used for the IoT service based on the accessible time of the user device 30 estimated from the period from the time when the device 50 installed in the environment becomes accessible to the time when the device 50 becomes unavailable. It controls whether or not the sensing of data is switched to the field device 50. Therefore, when there is a high possibility that the user's location is not constant, it is possible to suppress switching to the field device 50. Therefore, according to the server device 10 according to the present embodiment, it is possible to reduce the switching frequency of the device used for the IoT service. As a result of reducing the switching frequency of the devices used for the IoT service in this way, it is possible to suppress deterioration of the quality of the IoT service. Furthermore, when the user is likely to stay in a certain place, it is possible to switch to the field device 50. Therefore, the battery consumption of the user device 30 can be suppressed.

[Configuration of server device 10]
FIG. 2 is a block diagram illustrating a functional configuration of the server device 10 according to the first embodiment. As shown in FIG. 2, the server device 10 includes a communication I/F (InterFace) unit 11, a storage unit 13, and a control unit 15. Note that FIG. 2 shows a solid line representing a data transfer relationship, but FIG. 2 shows only a minimum part for convenience of explanation. That is, the input/output of data relating to each processing unit is not limited to the illustrated example, and the input/output of data other than the illustrated one, for example, between the processing units and the processing units, between the processing units and the data, and between the processing units and the outside. Data may be input/output between devices.

The communication I/F unit 11 is an interface that controls communication with other devices, for example, the user device 30 and the field device 50.

As one embodiment, a network interface card such as a LAN (Local Area Network) card can be adopted as the communication I/F unit 11. For example, the communication I/F unit 11 receives a start request or an end request for the IoT service from the user device 30, or receives media data sensed by the user device 30 or the field device 50. The communication I/F unit 11 also transmits a media data sensing instruction to the user device 30 or the field device 50.

The storage unit 13 is a storage device that stores data used for various programs such as an OS (Operating System) executed by the control unit 15 and an application program that realizes the device selection service.

As an embodiment, the storage unit 13 can be implemented as an auxiliary storage device in the server device 10. For example, a HDD (Hard Disk Drive), an optical disk, an SSD (Solid State Drive), or the like can be adopted as the storage unit 13. The storage unit 13 does not necessarily have to be implemented as an auxiliary storage device, and can be implemented as a main storage device in the server device 10. In this case, various semiconductor memory elements such as a RAM (Random Access Memory) and a flash memory can be used as the storage unit 13.

The storage unit 13 stores the field device data 13a and the access history data 13b as an example of data used for the program executed by the control unit 15. In addition to these data, the following electronic data can be stored. For example, in addition to media data sensed by the user device 30 or the field device 50, definitions relating to various IoT services, for example, types of media data used for the IoT service (voice, video, voice+video, etc.) and application periods of the IoT service. Information such as can also be stored together.

The field device data 13 a is data regarding the field device 50.

As one embodiment, the field device data 13a can be data including items such as a device ID (IDentification) and a position. The “device ID” mentioned here refers to identification information for identifying the IoT device, but here, as an example, the device ID of the field device 50 is held as the field device data 13a. The “position” refers to the position where the IoT device is located, and may be global coordinates such as latitude and longitude, or may be locally defined coordinates. Here, as an example, the case where the position of the field device 50 is managed by the field device data 13a is illustrated, but the position of the user device 30 is not limited to the field device 50 and can be managed. In this case, every time the position information is acquired from the user device 30, the field of the position of the record corresponding to the device ID of the user device 30 is updated to manage the device data including the current position of the user device 30. it can.

The access history data 13b is data relating to the access history of the user device 30 with respect to each device 50.

As one embodiment, the access history data 13b may be data in which items such as a device ID, a start time, and an accessible time are associated with each field device 50. The “device ID” here refers to identification information for identifying the IoT device, but here, as an example, the device ID of the user device 30 is held as the access history data 13b. The “start time” refers to the time when the user device 30 can access the field device 50. Furthermore, the “access continuation period” refers to a period during which the state in which the user device 30 can access the field device 50 continues, and whether or not the accessible state is continuing together with the information indicating the period. Are held in a state in which they can be identified by a computer through binary information or the like.

The control unit 15 is a processing unit that controls the entire server device 10.

As one embodiment, the control unit 15 can be implemented by a hardware processor such as a CPU (Central Processing Unit) or MPU (Micro Processing Unit). Here, the CPU and the MPU are illustrated as an example of the processor, but the processor can be implemented by any processor regardless of general-purpose type and specialized type. In addition, the control unit 15 may be realized by a hard-wired logic such as an ASIC (Application Specific Integrated Circuit) or an FPGA (Field Programmable Gate Array).

The control unit 15 implements a network management function for realizing the above-mentioned network management service function on a work area of a RAM such as a DRAM (Dynamic Random Access Memory) or an SRAM (Static Random Access Memory) implemented as a main storage device (not shown). By developing the program, the following processing units are virtually realized.

As shown in FIG. 2, the control unit 15 includes a detection unit 15a, an update unit 15b, an estimation unit 15c, and a selection unit 15d.

The detection unit 15a is a processing unit that detects whether or not access to the field device 50 is possible.

As an embodiment, the detection unit 15a can access the field device 50 by the user device 30 or access the field device 50 by the user device 30 depending on the geographical conditions of the user device 30 and the field device 50. Detect whether is impossible.

More specifically, the detection unit 15a selects a user device from a work area of an internal memory (not shown) that holds a list of device IDs of the user device 30 associated with the user's account in which the IoT service such as a life log is being implemented. One device ID of 30 is selected. Then, the detection unit 15a acquires the position information from the user device 30 corresponding to the device ID selected previously. For example, the detection unit 15a can acquire, as the position information of the user device 30, the latitude and longitude measured by a GPS (Global Positioning System) receiver mounted on the user device 30. In addition, the detection unit 15a can also acquire, from the user device 30, position information of a base station of a cell in which the user device 30 is accommodated, such as an access point. The position information of the access point can be used as it is as the position information of the user device 30, or the position information of the user device 30 can be calculated by using the distance between the user device 30 and the access point, which is calculated from the received signal strength of the user device 30. It is also possible to obtain position information. Then, the detection unit 15a refers to the field device data 13a stored in the storage unit 13 to search for a field device 50 accessible by the user device 30. For example, by comparing, for each device ID of the field device 50 included in the field device data 13a, the position of the field device 50 associated with the device ID with the position information of the user device 30, It is determined whether there is a field device 50 whose distance is within a predetermined range, for example, within 10 m.

In addition, here, the case where it is determined whether or not the user device 30 can access the field device 50 based on the geographical condition is illustrated, but the present invention is not limited to this. For example, a list of SSID (Service Set Identifier) can be obtained from the user device 30 instead of the position information. As described above, it is determined whether the user device 30 can access the field device 50 according to whether the SSID corresponding to the field device 50 is included in the list of SSIDs acquired from the user device 30. It can also be determined.

The update unit 15b is a processing unit that updates the access history data 13b.

As one aspect, the updating unit 15b executes the following process every time the detecting unit 15a detects whether or not there is a field device 50 whose distance from the user device 30 is within a predetermined range. .. For example, when there is a field device 50 that is within a predetermined range from the user device 30, it can be estimated that the user device 30 can access the field device 50. In this case, the update unit 15b determines whether or not an access history entry including the device ID of the user device 30 has been created in the access history regarding the device 50 that the user device 30 can access. Here, even if there is an access history entry including the device ID of the user device 30 in the access history of the device 50 accessible by the user device 30, the binary value included in the access continuation period of the entry. When binary information indicating that the accessible state is not maintained is held as information, even if an entry having the device ID of the same user device 30 is treated as another access history, the user device 30 concerned is handled. It is determined that the access history entry including the device ID is not created. Then, when the entry of the access history including the device ID of the user device 30 has been created, the update unit 15b updates the access duration period included in the entry of the access history of the user device 30. For example, the update unit 15b can calculate the latest access continuation period by the calculation of subtracting the start time from the current time referred to by the system time and the like, and can perform the update by overwriting the latest access continuation period. On the other hand, if the access history entry for the user device 30 has not been created, the update unit 15b newly creates an access history entry for the user device 30. That is, the updating unit 15b stores the device ID of the user device 30 that has become accessible to the field device 50 in the field of "device ID" as the access history of the field device 50 that the user device 30 can access. The "start time" field stores the current time when the local device 50 is accessible, that is, the record creation time, and the "access duration" field stores a NULL value or Create a new entry containing a value such as zero.

On the other hand, when there is no field device 50 within a predetermined range from the user device 30, it is estimated that the user device 30 cannot access the field device 50. In this case, it turns out that the field device 50 capable of performing media data sensing instead of the user device 30 does not exist around the user device 30. In this case, there is no room for the field device 50 to perform sensing of media data used for the IoT service. Therefore, the user device 30 is selected as the sensing device for sensing the media data by the selection unit 15d described later.

The estimation unit 15c is a processing unit that estimates the time when the user device 30 can access the field device 50. Below, the time when the user device 30 can access the field device 50 may be described as “accessible time”.

As one aspect, the estimation unit 15c activates the process when a new entry is created in the access history data 13b. For example, the estimation unit 15c reads the entry of the access history regarding the device 50 in which the new entry is created. Then, the estimation unit 15c performs a predetermined statistical process during the access duration included in each entry. As an example of this statistical processing, it is possible to execute processing of calculating various statistical values such as a mode value, a median value, a weighted average value and an arithmetic average value. Here, as an example, the case where the average value of the access duration of each entry, that is, the arithmetic average value is calculated is illustrated. As a result, the average value of the access duration of each entry is estimated as the “accessible time”.

The selection unit 15d is a processing unit that selects any one of the user device 30 and the field device 50 as a device that executes sensing of media data used for the IoT service. Hereinafter, a device that executes sensing of media data used for the IoT service may be referred to as a “sensing device”.

As one aspect, the selection unit 15d determines whether to switch the sensing device from the user device 30 to the field device 50 by comparing the accessible time estimated by the estimation unit 15c with a predetermined threshold value. As an example of such a threshold, the shortest duration that can be set for each IoT service can be used. For example, when an IoT service such as a life log is used, a moving image is sensed as media data. In this case, if the image pickup device for picking up a moving image is switched in a short period of time, only a moving image in which the viewpoint from which the moving image is captured, the imaging range, and the like are frequently switched can be obtained. Therefore, the user, the designer or the administrator of the IoT system 1, or the like can set the shortest time, for example, 10 minutes, that allows the imaging device to be switched as the “shortest duration”.

For example, the selection unit 15d determines whether the accessible time is equal to or more than the shortest duration, that is, the accessible time≧the shortest duration. Here, in the case of accessible time≧shortest duration, it can be expected that the field device 50 can be used as a sensing device instead of the user device 30 for a period equal to or longer than the shortest duration. In other words, after switching the sensing device from the user device 30 to the field device 50, it can be estimated that there is a high possibility that re-switching of switching the sensing device from the field device 50 to the user device 30 can be suppressed within the shortest duration. In this case, the selection unit 15d selects the field device 50 as a sensing device. On the other hand, when the accessible time is not the shortest duration ≥ the sensing device is switched from the user device 30 to the field device 50, it is not possible to suppress the re-switching of switching the sensing device from the field device 50 to the user device 30 within the shortest duration. It can be presumed that the property is high. In this case, the selection unit 15d selects the user device 30 as the sensing device.

Then, the selection unit 15d instructs the sensing device to perform sensing and transmission of media data. After that, the audio or video stream data transmitted from the sensing device is decoded, and the decoded media data is output to a predetermined output destination, for example, an application program corresponding to the IoT service. As a result, the IoT service is provided using the media data by the application program corresponding to the IoT service.

In addition, when there are a plurality of field devices 50 each having the accessible time equal to or longer than the shortest continuation time, one is selected from them. The selection criterion of this alternative is not limited to a specific criterion, but as an example, a sensor that selects the field device 50 that has the shortest distance from the user device 30 among the plurality of field devices 50, or that performs imaging, recording, or the like. The field device 50 on which the sensor having the highest performance is mounted can be selected.

As another aspect, the selection unit 15d performs the following process for each account of the user whose field device 50 is selected as the sensing device among the accounts of the user who is implementing the IoT service. That is, the selection unit 15d determines that the detection unit 15a determines that there is no field device 50 whose distance from the user device 30 is within the predetermined range, or continues during the access continuation period included in the access history data 13b. It is monitored whether the binary information indicating that it is not is stored. If any of these conditions are met, it is found that there is no field device 50 in the vicinity of the user device 30 that can perform media data sensing instead of the user device 30. In this case, there is no room for the field device 50 to perform sensing of media data used for the IoT service. Therefore, the selection unit 15d selects the user device 30 as the sensing device.

[Specific example of sensing device selection method]
Next, a specific example of the sensing device selection method will be described with reference to FIGS. 3 and 4. 3 and 4 are diagrams showing an example of the access history data 13b. 3 and 4 show access history data 13bA regarding the field device 50A installed on the road and access history data 13bB regarding the field device 50B installed in the store. Further, FIG. 3 shows access history data 13bA and access history data 13bB at 11:00 on June 7, and FIG. 4 shows time at 11:12 on June 7. Access history data 13bA and access history data 13bB are shown. Further, in FIGS. 3 and 4, an area where the field device 50A and the field device 50B can be accessed is shown by being filled. Furthermore, in FIGS. 3 and 4, the loci of position information of the user devices 30C and user devices 30E with the device IDs "user30C" and "user30E" having entries in the access history data 13bB, so-called flow lines, are indicated by alternate long and short dashed lines and two It is indicated by the dotted line.

Under such a situation, a method of selecting a sensing device in the case where the user carrying the user device 30A having the device ID “user 30A” moves according to the locus of position information indicated by the dotted lines in FIGS. 3 and 4 will be described.

As indicated by a dotted arrow in FIG. 3, at 11:00 on June 7, the user device 30A having the device ID “user30A” is located at the position (x1, y1) of the field device 50A included in the field device data 13a. ) And enter the area within 10m. Along with this, the detection unit 15a detects that the user device 30A can access the field device 50A. At this stage, there is no entry of the access history of the user device 30A in the access history data 13bA of the field device 50A, so an entry of the access history of the user device 30A is newly created. That is, the "device ID" field stores "user30A", the "start time" field stores the current time of June 7, 11:00, and the "access continuation period". In the field "", a new entry in which "0:00" is stored is created in the access history data 13bA.

When a new entry is created in this way, the estimating unit 15c estimates the accessible time. That is, of the access history data 13b, each entry of the access history data 13bA relating to the device 50A in which the new entry is created is referred to. Excluding new entries among these entries, the access history data 13bA shown in FIG. 3 shows that the user device 30B with the device ID "user30B", the user device 30C with the device ID "user30C", and the user with the device ID "user30D". An access history entry for device 30D is included.

The access durations included in the entries of the device ID “user30B”, the device ID “user30C”, and the device ID “user30D” are read. That is, “2 minutes” is read as the access duration of the user device 30B having the device ID “user30B”. Further, "2 minutes" is read as the access continuation period of the user device 30C having the device ID "user30C". Further, "5 minutes" is read as the access duration of the user device 30D having the device ID "user30D". The accessible time can be estimated as "3 minutes" by performing a calculation for averaging the access durations, that is, "(2 minutes+2 minutes+5 minutes)/3".

The selection unit 15d determines whether to switch the sensing device from the user device 30A to the field device 50A based on the accessible time estimated in this way. That is, it is determined whether the accessible time is equal to or longer than the shortest duration of the IoT service. Here, the field device 50A is installed on a road, and there is a high possibility that a user who travels on the road will pass not only around the field device 50A. It is possible to determine whether to switch the sensing device to the field device 50A according to the accessible time when such a tendency appears. In this example, the accessible time is "3 minutes"<the shortest duration "10 minutes". Therefore, the sensing device cannot be switched from the user device 30A to the field device 50A.

Then, as indicated by a dotted arrow in FIG. 4, at 11:02, the user device 30A with the device ID “user30A” is 10 m from the position (x1, y1) of the field device 50A included in the field device data 13a. Escape from within the area. Accordingly, the detection unit 15a detects that the user device 30A cannot access the field device 50A. At this stage, the access history data 13bA of the field device 50A has an entry of the access history of the user device 30A. Therefore, the access continuation period included in the access history entry of the user device 30A is updated. That is, the latest access continuation period "2 minutes" is calculated by the update unit 15b by subtracting the start time 11:00 from the current time 11:02. Then, of the entries included in the access history data 13bA, the update unit 15b performs an update by overwriting the latest access duration "2 minutes" in the access duration included in the access history entry of the user device 30A. To be done.

Then, as indicated by a dotted arrow in FIG. 4, at 11:12, the user device 30A with the device ID “user30A” is 10 m from the position (x2, y2) of the field device 50B included in the field device data 13a. Enter the area within. Accordingly, the detection unit 15a detects that the user device 30A can access the field device 50B. At this stage, since there is no entry of the access history of the user device 30A in the access history data 13bB of the field device 50B, a new entry of the access history of the user device 30A is created. That is, "user30A" is stored in the field of "device ID", 11:12 of June 7 which is the current time is stored in the field of "start time", and "access continuation period" is stored. In the field "", a new entry in which "0:00" is stored is created in the access history data 13bA.

When a new entry is created in this way, the estimating unit 15c estimates the accessible time. That is, of the access history data 13b, each entry of the access history data 13bB relating to the device 50B in which the new entry is created is referred to. Excluding new entries among these entries, the access history data 13bB shown in FIG. 4 includes access history entries relating to the user device 30C with the device ID "user30C" and the user device 30E with the device ID "user30E". ..

The access durations included in the entries of the device ID “user30C” and the device ID “user30E” are read. That is, "30 minutes" is read as the access duration of the user device 30B having the device ID "user30C". Further, "42 minutes (continuation)" is read as the access duration of the user device 30C having the device ID "user30E". The accessible time can be estimated as "36 minutes" by performing a calculation for averaging these access durations, that is, "(30 minutes + 42 minutes)/2".

Based on the accessible time estimated in this way, the selection unit 15d determines whether or not to switch the sensing device from the user device 30A to the field device 50B. Here, unlike the field device 50A, the field device 50B is installed in a store, and a user who visits the store may stay in the shop where the field device 50B is installed for a certain period of time. high. For example, as indicated by an alternate long and short dash line arrow in FIG. 4, the user carrying the user device 30C having the device ID “User 30C” is in a store where the field device 50B is installed after passing through the road where the field device 50A is installed. It can be seen from the access history data 13bA and the access history data 13bB that the user visited and stayed in the store for 30 minutes after that. Further, as indicated by the chain double-dashed arrow in FIG. 4, the user carrying the user device 30E having the device ID “User 30E” is still staying in the store where the field device 50B is installed for 42 minutes. This can be seen from the access history data 13bB. For these reasons, the field device 50B is more likely to be used as a sensing device instead of the user device 30A for a longer period than the field device 50A. It is possible to determine whether to switch the sensing device to the field device 50B according to the accessible time when such a tendency appears. In this example, the accessible time is “36 minutes”>the shortest duration is “10 minutes”. Therefore, the sensing device is switched from the user device 30A to the field device 50B.

As described above, in the present embodiment, it is possible to suppress switching to the field device 50A installed in an environment in which the user is unlikely to stay for a period of the minimum duration of the IoT service or longer. Therefore, according to the present embodiment, it is possible to reduce the switching frequency of the devices used for the IoT service and suppress the deterioration of the quality of the IoT service. In addition, in the present embodiment, it is possible to perform switching to the field device 50B installed in an environment in which the user is likely to stay for a period longer than the shortest duration of the IoT service. Therefore, it is possible to operate the field device 50 as a sensing device instead of the user device 30 and thereby suppress the battery consumption of the user device 30.

In addition, in the present embodiment, the access history data 13bA relating to the field device 50A or the access history data 13bB relating to the field device 50B is used to estimate the accessible time used for determining the suitability for switching to the field device 50A or the field device 50B. .. Both the access history data 13bA and the access history data 13bB can be created from the access history of the unspecified user device 30. That is, in the access history data 13bA and the access history data 13bB, even if the field device 50A and the field device 50B are not necessarily selected as sensing devices, an area in which an unspecified user can access the field device 50A or the field device 50B is a user device. It can be created by carrying 30 and carrying out an action, such as moving or staying. Furthermore, the access history data 13bA and the access history data 13bB may not necessarily be created from the access history of the user device 30 used for the same IoT service and the user device 30 used by the same user. This is because, even if the user's individual difference appears in the length of time that the user stays in the environment where the field device 50 is installed, whether the user stays in the environment where the field device 50 is installed depends on whether the user stays in the environment where the field device 50 is installed. This is because the proportion that depends on the nature of the environment is higher than the proportion that depends on individual differences.

3 and 4 illustrate the case where each data of the field device data 13a and the access history data 13b is stored in the storage unit 13 in the table format, but the present invention is not limited to this. For example, each data may be data described in a tag format in a markup language such as XML (Extensible Markup Language), or may be described in commas or line breaks such as CSV (Comma-Separated Values). It may be data.

[Process flow]
FIG. 5 is a flowchart of a device selection process procedure according to the first embodiment. As an example, this process is repeatedly executed at regular intervals as long as the user device 30 corresponding to the user's account in which the IoT service is being implemented exists.

As shown in FIG. 5, the detection unit 15a determines the device ID of the user device 30 from the work area of the internal memory that holds the list of the device IDs of the user device 30 associated with the user account in which the IoT service is being performed. Is selected (step S101).

Subsequently, the detection unit 15a acquires the position information from the user device 30 corresponding to the device ID selected in step S101 (step S102). Then, the detection unit 15a refers to the field device data 13a stored in the storage unit 13 and searches for a field device 50 accessible by the user device 30 (step S103).

At this time, when the field device 50 hits (Yes in step S104), the update unit 15b includes the access history regarding the field device 50 accessible by the user device 30 selected in step S101 in the access history data 13b. It is determined whether or not an access history entry including the device ID of the user device 30 has been created (step S105). If the field device 50 does not hit (No in step S104), the process proceeds to step S108.

Then, when the entry of the access history including the device ID of the user device 30 has been created (Yes in step S105), the updating unit 15b updates the access duration period included in the entry of the access history of the user device 30 ( Step S106).

On the other hand, if the entry of the access history including the device ID of the user device 30 has not been created (No in step S105), the updating unit 15b newly creates the entry of the access history related to the user device 30 (step S107).

After that, the processes from step S101 to step S107 are repeatedly executed until the device ID of the unselected user device 30 does not exist in the list used at step S101 (No at step S108). Then, when the device ID of the unselected user device 30 does not exist in the list used in step S101 (Yes in step S108), the estimation unit 15c determines whether a new entry is created in the access history data 13b (step). S109).

At this time, when a new entry is created in the access history data 13b (Yes in step S109), the estimation unit 15c determines a predetermined statistic during the access duration included in each entry of the access history regarding the device 50 in which the new entry is created. The "accessible time" is estimated by performing the process (step S110). If no new entry is created in the access history data 13b (No in step S109), the process ends as it is.

Subsequently, the selection unit 15d determines whether or not the accessible time estimated in step S110 is equal to or longer than the shortest duration, that is, the accessible time≧the shortest duration (step S111).

Here, when accessible time≧shortest duration (Yes in step S111), it can be expected that the local device 50 can be used as a sensing device instead of the user device 30 for a period equal to or longer than the shortest duration. In other words, after switching the sensing device from the user device 30 to the field device 50, it can be estimated that there is a high possibility that re-switching of switching the sensing device from the field device 50 to the user device 30 can be suppressed within the shortest duration. In this case, the selection unit 15d selects the field device 50 as the sensing device (step S112), and ends the process.

On the other hand, if the accessible time is not the shortest duration (No in step S111), the sensing device is switched from the user device 30 to the field device 50, and then the sensing device is switched from the field device 50 to the user device 30 within the shortest duration again. It can be estimated that there is a high possibility that the In this case, the selection unit 15d selects the user device 30 as the sensing device (step S113), and ends the process.

[One side of effect]
As described above, the server device 10 according to the present embodiment is based on the accessible time of the user device 30 estimated from the history of the period during which access to the place device 50 installed in the environment becomes unavailable. It controls whether or not the sensing of media data used for the service is switched to the field device 50. Therefore, when there is a high possibility that the user's location is not constant, it is possible to suppress switching to the field device 50. Therefore, according to the server device 10 according to the present embodiment, it is possible to reduce the switching frequency of the device used for the IoT service. As a result of reducing the switching frequency of the devices used for the IoT service in this way, it is possible to suppress deterioration of the quality of the IoT service. Furthermore, when the user is likely to stay in a certain place, it is possible to switch to the field device 50. Therefore, the battery consumption of the user device 30 can be suppressed.

Although the embodiments of the disclosed device have been described so far, the present invention may be implemented in various different forms other than the embodiments described above. Therefore, other embodiments included in the present invention will be described below.

[Estimation of accessible time]
In the above-described first embodiment, the case where the accessible time is estimated by averaging the access durations included in each entry of the access history regarding the device 50 in which the new entry is created has been exemplified, but the accessible time is estimated. The method is not limited to this. For example, the worst value of the access durations included in each entry, that is, the minimum value of the time when the field device 50 can be used in the future, can be estimated as the accessible time. As a result, even if an error occurs in the estimation of the accessible time, it is possible to suppress the re-switching of switching the sensing device from the field device 50 to the user device 30 within the shortest duration.

For example, when estimating the accessible time of the field device 50A shown in FIG. 3, “2 minutes” is read as the access duration of the user device 30B with the device ID “user 30B”. Further, "2 minutes" is read as the access continuation period of the user device 30C having the device ID "user30C". Further, "5 minutes" is read as the access duration of the user device 30D having the device ID "user30D". In this case, the minimum value of 2 minutes, 2 minutes, and 5 minutes, 2 minutes, is estimated as the accessible time. When estimating the accessible time of the field device 50B shown in FIG. 4, “30 minutes” is read as the access duration of the user device 30B with the device ID “user30C”. Further, "42 minutes (continuation)" is read as the access duration of the user device 30C having the device ID "user30E". In this case, the minimum value of 30 minutes and 42 minutes, 30 minutes, is estimated as the accessible time.

[Estimation of accessible time 2]
In addition, the estimation unit 15c may calculate a plurality of accessible times and control switching to the field device 50 in case there are a plurality of user stay patterns in the environment in which the field device 50 is installed. it can. For example, the switching to the field device 50 is controlled by comparing the first accessible time with the shortest duration of the IoT service, and when the switching to the field device 50 is not performed, the field device 50 is accessible. When the state continues longer than the first accessible time, it is possible to further control the switching to the field device 50 by comparing the second accessible time with the shortest duration of the IoT service.

FIG. 6 is a flowchart showing a procedure of an application example of the device selection processing. The flowchart shown in FIG. 6 shows a changed portion from the flowchart shown in FIG. The processing from step S109 shown in FIG. 5 can be replaced with the processing from step S201 to step S211 shown in FIG.

As shown in FIG. 6, when a new entry is created in the access history data 13b (Yes in step S109), the estimation unit 15c causes the access continuation period included in each entry of the access history regarding the device 50 in which the new entry is created. Clustering is performed (step S201).

Then, the estimation unit 15c selects two clusters having the highest number of elements included in the cluster among the clusters obtained by the clustering in step S201 (step S202). Then, the estimation unit 15c estimates, for each of the two clusters selected in step S202, the accessible durations by averaging the access durations included in the clusters (step S203). The shorter one of the two accessible times estimated in this way is identified as the first accessible time, while the longer one is identified as the second accessible time.

Subsequently, the selection unit 15d determines whether or not the first accessible time estimated in step S203 is equal to or longer than the shortest duration, that is, whether the first accessible time≧shortest duration. (Step S204).

At this time, if the first accessible time≧shortest duration (Yes in step S204), the selection unit 15d selects the field device 50 as the sensing device (step S205), and ends the process.

On the other hand, if the first accessible time is not the shortest duration (No in step S204), the selection unit 15d selects the user device 30 as the sensing device (step S206), and reserves the determination using the second accessible time. The re-determination flag used for is set to "TRUE" (step S207), and the process ends.

When no new entry is created in the access history data 13b (No in step S109), the selection unit 15d determines whether TRUE is set in the redetermination flag, that is, whether the redetermination flag=TRUE. The determination is made (step S208).

At this time, when the re-determination flag=TRUE (Yes in step S208), the selection unit 15d determines that the elapsed time after the user device 30 having the re-determination flag set to TRUE can access the field device 50. It is determined whether it is equal to or longer than the accessible time of 1, or whether the elapsed time≧the first accessible time (step S209).

Then, when the elapsed time≧the first accessible time, the selection unit 15d sets the re-determination flag to FALSE, and then the second accessible time estimated in step S203 is equal to or longer than the shortest duration time. It is determined whether or not, that is, whether or not the second accessible time≧shortest duration (steps S210 and 211).

Here, when the second accessible time≧shortest duration (step S211 Yes), the selection unit 15d selects the field device 50 as a sensing device (step S205), and ends the process. If the second accessible time≧shortest duration is not satisfied (No in step S211), the process ends without switching to the field device 50.

By the above-described processing, even when the user's stay pattern for the environment in which the field device 50 is installed is branched into a plurality of, the plurality of accessible times are estimated according to the stay pattern of the branch destination, and the plurality of accessible times to the field device 50 are estimated. The switching can be controlled. For example, in the example of FIG. 4, the store in which the device 50B is installed may be divided into a pattern of passing in front of the store and a pattern of entering and staying in the store. In this case, by comparing the first accessible time estimated from the cluster corresponding to the former pattern with the shortest duration, the elapsed time passes the first accessible time without switching to the field device 50B. The sensing device can be switched to the field device 50B later by comparing the second access time estimated from the cluster corresponding to the latter pattern with the shortest duration. Therefore, when a user passing around the store passes by, the sensing device is controlled as it is as the user device 30, and when a user passing around the store enters and stays in the store, the sensing device is used as the field device 50B. You can switch to. Therefore, the frequency of re-switching can be reduced more effectively.

[Estimation of accessible time 3]
In the above-described first embodiment, an example in which entries relating to different types of IoT services and entries relating to different user devices 30 are also used in estimating the accessible time has been described. However, only entries having the same type of IoT service are extracted. It is also possible to estimate the accessible time by estimating the accessible time, extract only the entries related to the same user device 30 to estimate the accessible time, and use the same IoT service type and the same user device 30. It is also possible to estimate the accessible time by extracting the entry that is.

[Battery level]
In the above-described first embodiment, the case where the user device 30 is selected as the sensing device when the accessible time is not longer than the shortest duration is illustrated, but the field device 50 may be conditionally selected as the sensing device. For example, when the battery remaining amount acquired from the user device 30 is a predetermined threshold value, for example, 20% or less, the field device 50 can be selected as the sensing device even if the accessible time is not longer than the shortest duration. That is, in the example of the flowchart shown in FIG. 5, after the process proceeds to the branch of step S109 Yes, the process of acquiring the remaining battery amount from the user device 30 and the determination whether the remaining battery amount is equal to or less than a predetermined threshold value are determined. Insert the process to do. Then, if the battery remaining amount is less than or equal to the predetermined threshold value, the process proceeds to step S113, that is, the process of selecting the user device 30 as the sensing device. If the battery remaining amount is not less than or equal to the predetermined threshold value, the process proceeds to step S110. It may be decided to move.

[Minimum duration]
In the above-described first embodiment, the case where the shortest duration is set by the instruction input of the user of the IoT system 1, the administrator, the designer, or the like has been exemplified, but the present invention is not limited to this, and the frequency of media output and It is also possible to estimate the remaining duration of the IoT service from the timing. That is, although the life log is illustrated as an example of the IoT service in the above-described first embodiment, the content such as the audio content and the video content stored in the user device 30 is transmitted to the external reproduction device, and the external reproduction device is transmitted. There is a case where a content reproduction service or the like in which an external reproduction device is treated like a jukebox is used by reproducing the content by. In such a case, the user device 30 is caused to measure the media output time from the start of the output of the video content or the audio content by the media player or the like to the end thereof, and then the media output history data is stored. Then, the media output history data is uploaded to the server device 10 at a fixed cycle, a regular time, or a timing of creating a new entry. Thereby, in the server device 10, the storage unit 13 can manage the media output history data for each device ID of the user device 30. For example, when the above content reproduction service is implemented as the IoT service, the media output time is read from the media output history data corresponding to the device ID of the user device 30 using the service, and the statistical value of the media output time, for example, By calculating the average value, the remaining duration of the content reproduction service can be calculated. By comparing the remaining continuation time with the accessible time, switching control to the field device 50 can be realized.

[Device selection execution subject]
In the above-described first embodiment, when the control unit 15 illustrated in FIG. 2 realizes the detection unit 15a, the update unit 15b, the estimation unit 15c, and the selection unit 15d, that is, when the execution subject of the device selection process is the server device 10. However, the server device 10 does not necessarily have to be the execution subject of the device selection process. That is, the processor included in the field device 50 may virtually realize the detection unit 15a, the update unit 15b, the estimation unit 15c, and the selection unit 15d by expanding the device selection program on the RAM. In this case, when one field device 50 controls the switching of all field devices 50 including other field devices 50 as a representative, the same process as that of the server device 10 may be executed. When selecting a sensing device from the field device 50 and the user device 30 for each field device 50, the location information of the other field device 50 does not necessarily have to be present, and the user device that is performing the IoT service first. Only the device ID of 30 need be identified.

Distributed and integrated
In addition, each component of each illustrated device may not necessarily be physically configured as illustrated. That is, the specific form of distribution/integration of each device is not limited to that shown in the figure, and all or part of the device may be functionally or physically distributed/arranged in arbitrary units according to various loads and usage conditions. It can be integrated and configured. For example, the detecting unit 15a, the updating unit 15b, the estimating unit 15c, or the selecting unit 15d may be connected as an external device of the server device 10 via a network. Also, even if another device has the detection unit 15a, the update unit 15b, the estimation unit 15c, or the selection unit 15d, respectively, and is connected to a network to cooperate with each other, the functions of the server device 10 described above may be realized. Good. Further, another device has all or part of the field device data 13a or the access history data 13b stored in the storage unit, respectively, and realizes the functions of the server device 10 by being network-connected and cooperating. It doesn't matter if you do.

[Communication program]
The various processes described in the above embodiments can be realized by executing a prepared program on a computer such as a personal computer or a workstation. Therefore, in the following, an example of a computer that executes a communication program having the same functions as those in the above embodiments will be described with reference to FIG. 7.

FIG. 7 is a diagram illustrating a hardware configuration example of a computer that executes the communication program according to the first and second embodiments. As shown in FIG. 7, the computer 100 includes an operation unit 110a, a speaker 110b, a camera 110c, a display 120, and a communication unit 130. Further, the computer 100 has a CPU 150, a ROM 160, an HDD 170, and a RAM 180. Each unit of these 110 to 180 is connected via a bus 140.

As shown in FIG. 7, the HDD 170 stores a communication program 170a that exhibits the same functions as the detecting unit 15a, the updating unit 15b, the estimating unit 15c, and the selecting unit 15d described in the first embodiment. This communication program 170a may be integrated or separated similarly to each component of the detecting unit 15a, the updating unit 15b, the estimating unit 15c, and the selecting unit 15d shown in FIG. That is, the HDD 170 does not necessarily need to store all the data described in the first embodiment, and the data used for the processing may be stored in the HDD 170.

Under such an environment, the CPU 150 reads out the communication program 170a from the HDD 170 and then expands it in the RAM 180. As a result, the communication program 170a functions as the communication process 180a, as shown in FIG. The communication process 180a expands various data read from the HDD 170 in an area allocated to the communication process 180a in the storage area of the RAM 180, and executes various processes using the expanded various data. For example, the processing illustrated in FIGS. 5 and 6 is included as an example of the processing executed by the communication process 180a. Note that in the CPU 150, not all the processing units described in the above-described first embodiment may operate, and the processing unit corresponding to the processing to be executed may be virtually realized.

The communication program 170a does not necessarily have to be stored in the HDD 170 or the ROM 160 from the beginning. For example, the communication program 170a is stored in a “portable physical medium” such as a flexible disk inserted into the computer 100, a so-called FD, CD-ROM, DVD disk, magneto-optical disk, IC card, or the like. Then, the computer 100 may acquire and execute the communication program 170a from these portable physical media. Further, the communication program 170a is stored in another computer or a server device connected to the computer 100 via a public line, the Internet, a LAN, a WAN, etc., and the computer 100 acquires and executes the communication program 170a from these. You may do so.

1 IoT system 10 server device 11 communication I/F unit 13 storage unit 13a field device data 13b access history data 15 control unit 15a detection unit 15b update unit 15c estimation unit 15d selection unit 30 user device 50A, 50B, 50C field device

Claims (5)

A detection unit that detects the time when the first terminal enters the area where the first device can access the device and the time when the first device becomes inaccessible;
A storage unit that stores the accessible time determined from each detected time,
When it is detected that the second terminal can access the own device, a selection unit that selects the own device or the second terminal based on the accessible time stored in the storage unit,
A communication device comprising: The storage unit further includes an estimation unit that estimates a statistical value obtained by performing a predetermined statistical process on a plurality of accessible times stored in the storage unit as an accessible time of the second terminal,
The communication device according to claim 1, wherein the selection unit selects the own device or the second terminal depending on whether or not the accessible time estimated by the estimation unit is equal to or more than a predetermined threshold value. The communication device according to claim 2, wherein the estimation unit estimates the accessible time of the second terminal by calculating an average value of a plurality of accessible times stored in the storage unit. By selecting two clusters from among the clusters in which the plurality of accessible times stored in the storage unit are clustered and calculating the statistical value of the accessible time included in the cluster for each of the two clusters An estimation unit that estimates an accessible time and a second accessible time that is longer than the first accessible time;
The selection unit selects the self-device or the second terminal depending on whether the first accessible time is equal to or more than a predetermined threshold value, and when the second terminal is selected, the second terminal is selected. 2. The self-device or the second terminal is selected according to whether or not the second accessible time is equal to or more than the threshold value after the first accessible time has elapsed since the first time. Communication device. Detecting the time when the first terminal enters the area where it can access its own device and the time when it becomes inaccessible,
Register the accessible time determined from each detected time in a predetermined storage unit,
When it is detected that the second terminal can access the own device, the own device or the second terminal is selected based on the accessible time stored in the storage unit,
A communication method, wherein the processing is executed by a computer.

Images