WO2013024673A1 - 情報管理装置、ネットワークシステム、情報管理プログラム、および情報管理方法 - Google Patents
情報管理装置、ネットワークシステム、情報管理プログラム、および情報管理方法 Download PDFInfo
- Publication number
- WO2013024673A1 WO2013024673A1 PCT/JP2012/068775 JP2012068775W WO2013024673A1 WO 2013024673 A1 WO2013024673 A1 WO 2013024673A1 JP 2012068775 W JP2012068775 W JP 2012068775W WO 2013024673 A1 WO2013024673 A1 WO 2013024673A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- information
- sensing data
- sensor
- storage unit
- provision
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/50—Service provisioning or reconfiguring
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B15/00—Systems controlled by a computer
- G05B15/02—Systems controlled by a computer electric
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/30—Services specially adapted for particular environments, situations or purposes
- H04W4/38—Services specially adapted for particular environments, situations or purposes for collecting sensor information
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B2219/00—Program-control systems
- G05B2219/20—Pc systems
- G05B2219/25—Pc structure of the system
- G05B2219/25129—Programming a multitasking, virtual sensor network shared by various users
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/02—Services making use of location information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/02—Services making use of location information
- H04W4/029—Location-based management or tracking services
Definitions
- the present invention relates to a technique for providing sensing data generated by a sensor in a form that can be used for various purposes.
- Sensors are classified into various types such as sensors that detect the presence or absence of an object based on changes in physical quantities, sensors that have a function of measuring the position and shape of an object, and sensors that detect a specific gas or liquid. These sensors are generally used by being incorporated in a device or system (hereinafter, collectively referred to as “application”) that performs some processing.
- application a device or system
- Patent Document 1 uses a detection output of a human body detection sensor incorporated in a crime prevention system to perform thinning control of lighting and air conditioning in a place where there is no person in the daytime when the crime prevention system is not operating. It is described.
- Patent Document 2 describes that a position of a moving body is calculated using a vibration gyroscope, a speed sensor, an acceleration sensor, a GPS sensor, and the like, and the calculated position is output together with a value of the probability.
- Patent Document 3 describes that a camera and a wireless tag reader are introduced as sensors, and position information detected by both sensors is integrated to track a moving object.
- sensors are increasingly used for crime prevention and other purposes in factories as well as ordinary homes and public facilities. Further, with the development of communication technology, it is also easy to transmit data detected by these sensors.
- general-purpose devices having both sensor functions and communication functions such as mobile phones and tablet terminals are used by many people.
- Patent Document 4 charges a user who uses sensing data according to the use of the sensing data, and provides the sensing data to an owner who has a sensor or a device that can function as a sensor. It proposes to pay the accompanying consideration.
- the present invention pays attention to the above-mentioned circumstances, and possesses a user who wants to perform some processing using sensing data and a device that can function as a sensor or a sensor (hereinafter collectively referred to as “sensor”). It is an object of the present invention to make effective use of sensing data in connection with a person and to enable a user to easily acquire sensing data according to the purpose.
- the sensor owner may want to set restrictions on the purpose and method of use of the sensing data generated by the sensor for various reasons such as their own interests.
- An object of the present invention is to make it easy for the owner of a sensor to apply restrictions on the purpose and method of use of sensing data.
- the present invention provides an information management apparatus including the following provision condition storage unit, usage condition storage unit, sensing data acquisition unit, identification unit, and sensing data distribution unit.
- provision condition information of sensing data generated by the sensor is registered in association with identification information of the sensor.
- the provision condition information is, for example, restriction information indicating the restriction on the use of the sensing data for the information type of the sensing data, the position information of the sensing target area, and the use of the sensing data.
- the use condition storage unit for each application that requires the use of sensing data, user condition information of the required sensing data is registered in association with the address of the sensing data transmission destination.
- This usage condition information is, for example, information type of sensing data, position information of sensing target area, and usage information indicating the usage of sensing data.
- the sensing data acquisition unit acquires the sensing data generated by the sensor registered in the provision condition storage unit through communication.
- the specifying unit searches the providing condition storage unit for each piece of using condition information registered in the using condition storage unit, and specifies providing condition information that matches the using condition information.
- the sensing data distribution unit acquires the sensor of the identification information corresponding to the specified provision condition information with respect to the transmission destination address corresponding to the use condition information for which the suitable provision condition information is identified. A transmission process using the sensing data is executed.
- provision conditions determined with the owner of the sensor are registered in the provision condition storage unit in advance, and usage conditions determined with the application operator are registered in the use condition storage unit.
- sensing data from each sensor is acquired by communication according to the registered conditions, and for each application, a sensor that generates the sensing data required by the application regarding the area required by the application is specified. Sensing data can be transmitted. Therefore, the operator of the application can easily acquire sensing data necessary for processing without introducing his own sensor. It is possible to easily cope with changes in the sensing target area and the information type of sensing data.
- virtual sensor management information storage unit and the data processing unit described below may be provided.
- management information including identification information of sensors to be combined, definition of integration processing, and information type of sensing data generated by integration is registered.
- the data processing unit integrates the sensing data acquired by the sensing data acquisition unit for a plurality of sensors corresponding to the identification information in the management information registered in the virtual sensor management information storage unit based on the definition in the same management information. Thus, the sensing data of the virtual sensor corresponding to the management information is acquired.
- the specifying unit searches the provision condition storage unit and the virtual sensor management information storage unit based on the use condition information registered in the use condition storage unit, and the sensor whose position information in the sensing target area matches the use condition information Means for specifying a virtual sensor that generates sensing data of a type that matches the usage condition information.
- the sensing data distribution unit transmits the sensing data acquired by the data processing unit based on the virtual sensor management information specified by the specifying unit to a transmission destination address corresponding to the usage condition information targeted for the specific target To do.
- sensing data generated by virtual sensors in various combinations in addition to actual sensors can be provided, so that variations in sensing data can be enriched.
- the sensor owned by the provider has a simple configuration, it is possible to provide highly reliable sensing data by the processing of the virtual sensor.
- information indicating the timing for obtaining sensing data may be included in the usage conditions registered in the usage condition storage unit.
- the specifying unit is adapted to the usage condition information on condition that the usage condition information of the processing target has reached the timing for acquiring the sensing data while circulating the process of sequentially changing to the usage condition information of the processing target.
- This configuration makes it possible to provide sensing data according to the user's request at the timing desired by the user.
- sensing data from other sensors can be provided, so the convenience of the provider, the convenience of the user, the environment It can respond flexibly to changes.
- the provision condition information registered in the provision condition storage unit includes the identification information of the provider of the sensing data and information indicating the amount of consideration desired by the provider for the provision of the sensing data It is good.
- the usage condition information registered in the usage condition storage unit includes identification information of the application receiving the sensing data and information indicating the amount of consideration paid by the operator of the application for the provision of the sensing data.
- the specifying unit is configured to specify providing condition information that matches the use condition information on condition that the amount of consideration determined by the specified providing condition information does not exceed the amount of consideration in the use condition information.
- the application operation is performed for the provision of the sensing data.
- a consideration calculating unit that calculates the amount of consideration paid by the user and the amount of consideration received by the owner of the sensor that generated the sensing data used for transmission.
- the operator of the application can receive the sensing data at a desired price, and the owner of the sensor can obtain the desired price by providing the sensing data.
- the owner of the sensor sets the use restrictions on the sensing data provided. It is possible to restrict transmission to an information utilization device used for different usage purposes. In other words, the owner of the sensor can use the provided sensing data only for the usage that permits the use. Thereby, provision of the sensing data from the owner of the sensor can be promoted, and the sensing data can be effectively utilized.
- the use condition information registered in the provision condition storage unit and the use condition information registered in the use condition storage unit are used to indicate the usage of sensing data required by the application.
- Management information generating unit that generates management information in association with usage information and sensing data that is not restricted for this usage, and management information that stores management information generated by the management information generating unit
- the management information storage unit refers to the management information stored in the information selection unit that selects the sensing data to be transmitted to the application. It is good also as a structure provided.
- the management information stored in the management information storage unit is generated in advance and information to be transmitted to this application is selected. Therefore, the time required for selecting sensing data to be transmitted to an application that has transmitted a request for using sensing data can be reduced.
- provision provision information concerning the contract request is additionally stored in the provision condition storage section, and the use contract section
- the use condition information related to the contract request may be additionally stored in the use condition information storage unit.
- the management information generation unit may generate management information every time a predetermined timing is reached.
- the sensing data provided from the sensor is stored in the information storage unit, and the sensing data selected by the request unit as the sensing data to be transmitted to the application by the information selection unit is not stored in the information storage unit, it is applicable. It is good also as a structure which requests
- the provision condition information may include a usage fee for the sensing data and a recognition level
- the usage condition information may include a usage fee and a priority for the recognition level.
- an information selection part should just be set as the structure which selects the sensing data transmitted to an application according to the priority contained in utilization side information. Thereby, it is possible to improve the service for the user side who uses the information.
- each sensor can be used not only for the purpose intended by the owner but also for other purposes, and sensing data can be used effectively.
- the sensor owner can use the provided sensing data only for the usage that permits the use of the sensor data. Can be used.
- FIG. 1 It is a figure which shows the structure of the network system concerning embodiment of this invention. It is a figure which shows the structural example of the record in sensing data provision condition DB. It is a figure which shows the structural example of the record in sensing data utilization condition DB. It is a figure which shows the structural example of the record in sensing data utilization condition DB. It is a figure which illustrates the sensing data group produced
- FIG. 1 is a diagram showing a configuration of a network system according to an embodiment of the present invention.
- This network system includes an information management device 1, devices in the application-side system 2, and sensors.
- the information management apparatus 1 accepts transmission of sensing data (data indicating detection contents) from a plurality of sensors, and the application requires sensing data in the system 2 on the application side that performs processing using the sensing data. Sometimes the necessary sensing data is distributed.
- the specific distribution destination of the sensing data is one device in the application-side system 2, but is not limited thereto, and common sensing data can be distributed to a plurality of devices.
- Sensors that transmit sensing data are all devices that have a function of generating data representing events outside the device itself.
- sensors such as photoelectric sensors, magnetic sensors, ranging sensors, visual sensors, RFID reader / writers, two-dimensional code readers, bar code readers, digital cameras, etc. are also sensors. Can be used.
- the sensor of this embodiment is provided with a communication function.
- a certain sensor incorporates a mobile phone wireless communication chip and transmits the generated sensing data to the information management apparatus 1 via a mobile phone wireless network.
- Other sensors transmit sensing data to a nearby communication device such as a smartphone via a short-range wireless communication function such as WiFi (registered trademark) or Zigbee (international registered trademark). Sensing data is transmitted to the information management device 1.
- a sensor that transmits sensing data using wired communication using an optical fiber or the like as well as wireless communication.
- a portable communication device itself such as a smartphone or a mobile phone as a sensor.
- position information acquired by a GPS function, an image generated by a built-in camera, information read by a two-dimensional code reading function, and the like can be transmitted as sensing data.
- the image even if the image is not taken by the owner in consideration of detection, the image can function as sensing data as long as the image matches the purpose of the application.
- a combination of a plurality of devices that detect different types of information and a communication device functions as one sensor (the communication device may be included in any one of the devices), and is detected by each device.
- a combination of information can also be output as sensing data.
- sensing data including identification information (ID) and position information read from an RFID tag is output for an object with an RFID tag by combining a distance sensor, an RFID reader / writer, and a communication device. Can do.
- ID identification information
- position information read from an RFID tag is output for an object with an RFID tag by combining a distance sensor, an RFID reader / writer, and a communication device.
- sensing data generated by a virtual sensor by a combination of a plurality of sensors can be provided.
- a real sensor in order to distinguish from a virtual sensor, a real sensor is referred to as a “real sensor”.
- the number of actual sensors is simplified to five and each is indicated by reference numerals S1 to S5.
- the information management apparatus 1 shown in FIG. 1 is configured by one or a plurality of computers, and includes a sensing data provision condition DB 101 (DB is an abbreviation of “database”; the same applies hereinafter), a sensing data use condition DB 102, a contract DB 103, It has storage means such as a sensing data management DB 104, a virtual sensor management DB 105, and a distribution log DB 106. Furthermore, the information management apparatus 1 is provided with functions such as a sensing data acquisition unit 10, a contract matching processing unit 11, a sensing data processing unit 12, a sensing data distribution processing unit 13, and a price adjustment processing unit 14.
- sensing data provision condition DB 101 a record is set for each actual sensor, and various conditions related to provision of sensing data are registered.
- sensing data use condition DB 102 a record is set for each application that uses the sensing data, and various conditions are registered regarding the sensing data used by the application.
- FIG. 2 shows a configuration example of a record stored in the sensing data provision condition DB 101.
- the sensing data provision condition DB 101 relays, as information for identifying an actual sensor, a code (sensor number) unique to the actual sensor, the actual sensor, or sensing data from the actual sensor. And the contract number of the contract exchanged between the owner of the actual sensor and the system operator.
- the sensing data provision condition information includes sensing data type, sensing area position information (including character information indicating the location of the sensing area, latitude and longitude), sensing cycle, sensing data reliability, Information indicating the amount of consideration desired by the owner for the provision, usage permitted by the owner regarding the use of sensing data, and the like are stored.
- the sensing data usage condition DB 102 includes, as information for specifying the corresponding application, a code (application number) unique to the application, the IP address of the device to which the sensing data is transmitted, A contract number (a contract number exchanged between the business operator and the system operator) is stored.
- sensing data usage condition information sensing data type, sensing area location information, sensing cycle, reliability of sensing data, amount of consideration payable per offer, use of sensing data , Etc. are stored.
- Information registered in the sensing data provision condition DB 101 and the sensing data use condition DB 102 is input by a person in charge of the business operator who operates the information management apparatus 1 based on a contract with the owner of the actual sensor or the operator of the application. It is a thing. However, information transmission from the owner of the actual sensor or the operator of the application may be accepted, and registration in the databases 101 and 102 may be performed based on the received information.
- the provision conditions in addition to the example shown in FIG. 2, it is possible to limit the time period for outputting sensing data, or to discriminate detection data on the sensor side and select data that can be output.
- the usage conditions it is possible to limit the time zone for capturing sensing data and to specify the contents of the necessary data.
- a plurality of sensing data can be designated, and in that case, sensing data having different sensing data types can be designated.
- the sensing data type is specified, it can be set as a use condition that all sensing data included in the sensing area is provided within a range in which the price is commensurate.
- FIG. 5 shows a group of sensing data that can be generated by the actual sensors S1 to S5 shown in FIG.
- a further virtual sensor can be set by a combination of virtual sensors like the virtual sensor U3 in FIG.
- the virtual sensor management DB 105 stores management information indicating the configuration and processing method for each set virtual sensor U1, U2, U3.
- FIG. 6A shows the management information of the virtual sensor U1 shown in FIG. 5, and FIG. 6B shows the management information of the virtual sensor U3 born by the combination of the virtual sensors U1 and U2.
- Each of the exemplified management information is used for the process of integrating the sensor number of the virtual sensor, the sensor number of the sensor combined for setting the virtual sensor (hereinafter referred to as “lower sensor”), and the sensing data of the lower sensor. Processing methods are included.
- the processing method includes the data type of sensing data generated by the processing.
- Each real sensor S1 to S5 transmits sensing data according to the sensing cycle indicated by the provision condition information.
- This sensing data includes the sensor number of the transmission source sensor.
- the sensing data acquisition unit 10 receives the sensing data from each of the actual sensors S1 to S5, the sensing data acquisition unit 10 checks the authenticity of the data by referring to the sensing data provision condition DB 101 based on the IP address and sensor number of the device that sent the data. The sensing data recognized as correct is stored in the sensing data management DB 104.
- the contract matching processing unit 11 For each application registered in the sensing data usage condition DB 102, the contract matching processing unit 11 checks the usage condition information of the sensing data in the application with the provision condition information in the sensing data provision condition DB 101, and conforms to the usage condition information. Specify provision condition information. In this collation, the virtual sensor use conditions are similarly collated by referring to the virtual sensor management DB. When provision condition information matching the use condition information is specified, the contract matching processing unit 11 uses the sensor number in the provision condition information as information indicating the sensor that provides the sensing data (hereinafter referred to as “provider sensor number”). )). Also, the application number and IP address in the usage condition information that is the target of collation are set as the application number and address of the sensing data transmission destination. Then, the sensor data delivery processing unit 13 is notified of the provider sensor number, the destination application number, and the address.
- the sensing data distribution processing unit 13 receives the above notification and issues a data acquisition request including the provider sensor number to the sensing data processing unit 12. If the providing source sensor number in the data acquisition request is the sensor number of the actual sensor, the sensing data processing unit 12 reads the latest sensing data associated with the number from the sensing data provision condition DB 101, and the sensing data distribution process Provided to part 13. On the other hand, when the source sensor number included in the data acquisition request is the sensor number of the virtual sensor, the sensing data processing unit 12 refers to the record in the virtual sensor management DB 105 corresponding to the sensor number, and corresponds. The lower sensor is identified from the information in the record. Then, the sensing data of the virtual sensor is generated by processing the sensing data of the lower sensor based on the management information, and provided to the sensing data distribution processing unit 13.
- the sensing data distribution processing unit 13 transmits the sensing data provided from the sensing data processing unit 12 to the IP address of the transmission destination application in response to the data acquisition request. Further, the sensing data distribution processing unit 13 creates log information indicating the content of the transmission and stores it in the distribution log DB 106.
- contract DB 103 specific contents of a contract that the operator of the information management apparatus 1 exchanges with the owner of the actual sensor and the operator of the application side system 2 are registered.
- the registration information in the contract DB 103 can be accessed by the contract number shown in FIGS.
- the information registered in the contract DB 103 includes specific information related to the payment and payment of the payment, such as the payment date of the payment, the notification method of the payment result, and the account to which the payment is transferred.
- the price adjustment processing unit 14 reads the corresponding information from the distribution log DB for each actual sensor and for each application, and the amount of the consideration that should be received by the owner of each actual sensor, Calculate the amount. Furthermore, based on the agreement indicated by the corresponding contract information in the contract DB 103, processing related to the payment of the price to the sensor owner and the charge to the operator of the application is executed.
- the value adjustment processing unit 14 also performs a value calculation process with reference to the virtual sensor management DB 105 for log information related to the virtual sensor.
- the virtual sensor U is set by two real sensors SA and SB. Also.
- the content of the process performed in the virtual sensor U is shown in the dotted line frame indicating the virtual sensor U.
- each real sensor SASB in the example of FIG. 7 has a function of detecting the position of each object, and the sensing areas do not overlap. Using this relationship, in this example, each real sensor SASB is caused to transmit the detected time TA and TB along with the detected position information PA and PB ⁇ .
- each actual sensor SA and SB has a relatively short distance along a route such as a road. If the sensors are arranged apart from each other, the sensing data of the virtual sensor U is considerably reliable. Further, based on an assumed range of the moving speed of the object OB to be detected, an upper limit value and a lower limit value are set for the speed V, and V is output only when the value of V is between the upper limit value and the lower limit value. By doing so, the accuracy of the sensing data can be increased.
- the 8 has the function of reading the identification information (ID) of the object OB in addition to the position of the object OB.
- ID identification information
- the combination of the distance measuring sensor and the RFID reader / writer described above can be used as the actual sensors SA and SB.
- the actual sensors SA and SB ⁇ in this example have a relationship in which the sensing areas overlap, and transmit the detected position information PA, PB and ID together with the detection times TA and TB.
- the absolute value of the difference between the position information PA and PB and the absolute value of the difference between the times TA and TB are obtained on condition that the IDs from both the real sensors A and B match. . If the absolute values are below the predetermined threshold values ⁇ P and ⁇ T, it is determined that the transmission information from the actual sensors A and B is obtained by capturing the same object at the same time, and PA and PB The average value Pav is calculated. Then, the ID, the output (PA and TA) from one real sensor (actual sensor SA in the illustrated example), and the average value Pav are output as sensing data.
- PA and TA are used while referring to the average value Pav as information representing the reliability of the PA.
- Pav can be used as position information.
- the real sensors SA and SB in the example of FIG. 9 also have a function of detecting the position information PA and PB and the identification code (ID) of the object as in the example of FIG. To do. The same is true in that the sensing areas of the actual sensors SA and SB are overlapped.
- the position information output at the same time t from each of the actual sensors SAS and SB is PAt and PBt.
- the sensing data from each of the actual sensors SA and SB is taken in every certain time interval, and information transmitted from each of the actual sensors SA and SB within a period in which the IDs detected by each match ( For a set of PAt, t) (PBt, t), a correlation value S * between the change pattern of (PAt, t) and the change pattern of (PBt, t) is calculated. Further, a value Q obtained by dividing the correlation value S * by a predetermined threshold value is calculated, and each value of PAt and PBt, ID, Q for every hour is output as sensing data.
- the processing it is possible to output the substantial sensing data with the reliability Q added to the ID, PAt, and PBt.
- the reliability Q it is possible to determine the moving route of an object for each ID based on PAt or PBt or an average value of both while referring to the ID. Further, based on the reliability Q, it is possible to determine whether or not to use sensing data and to obtain the reliability of processing in the own system.
- the virtual sensor U is set by the combination of the real sensors SA ⁇ and SB that output the same type of sensing data. May be. For example, it is determined whether or not the sensing data from each actual sensor satisfies a predetermined condition. If both satisfy the condition, “True” is output, otherwise “False” is output.
- the virtual sensor to be performed can be set.
- the number of actual sensors that can be combined for setting a virtual sensor is not limited to two, and three or more actual sensors can be combined. Further, as described above, virtual sensors may be combined or a virtual sensor and a real sensor may be combined. It is also possible to create a plurality of virtual sensors by applying a plurality of types of processing methods to the same sensor combination.
- a plurality of combinations that can function as virtual sensors are selected from the real sensors registered in the sensing data provision condition DB 101, and the processing method of each virtual sensor is determined. For each combination, the management information shown in FIG. 6 is created and registered in the virtual sensor management DB 105.
- the contract matching processing unit 11 pays attention to the applications registered in the sensing data usage condition DB 102 in order, extracts a real sensor or a virtual sensor that matches the usage conditions of the application under consideration, and provides the source sensor from these sensors. Select. When the processing for each application is completed, the processing is returned to the first application again and the same processing is repeated. Each time a source sensor is selected, the sensing data distribution processing unit 13 is notified of the source sensor number, the destination application number, and the IP address. The sensing data distribution processing unit 13 cooperates with the sensing data processing unit 12. To send sensing data.
- the process of specifying the sensing data providing source sensor and the process of transmitting the sensing data from the specified providing source sensor are repeatedly and circulated. Note that the processing speed of each processing unit is ensured so that the time required to complete the processing for each application is less than the sensing cycle guaranteed to the application side.
- the above cyclic processing can be flexibly changed according to the conditions of both without fixing the correspondence between the application that receives the sensing data and the sensor that provides the sensing data. For example, when an actual sensor set to provide sensing data only during the day is selected as the providing sensor, the providing sensor is changed at night. In addition, when the sensing data required by the application varies with time, the provider sensor is also changed in accordance with the change in the type of required sensing data.
- the association between the sensor and the application can also occur when the registration information is changed.
- the actual sensor S1 is suitable for the application based on the use condition information shown in FIG.
- the sensing data type of the actual sensor S1 becomes incompatible with the updated use condition information.
- the virtual sensor U1 is selected as a new source sensor.
- FIG. 10 and FIG. 11 show a procedure of processing executed by the contract matching processing unit 11 for the above-described association processing.
- the contract matching processing unit 11 sets a counter k for specifying the target application to an initial value (for example, 1) (step S1).
- the matching list is initialized (with no data) (step S2).
- step S3 the k-th record information is read from the sensing data use condition DB 102 (step S3), and the k-th application detects the sensing data based on the sensing cycle in the read record and the distribution log information in the distribution log DB. It is determined whether or not it is necessary to use (step S4). If it is determined that it is not necessary to use the sensing data (“NO” in step S4), k is incremented (step S5), and the process proceeds to the next application. If k after the increment is less than or equal to the number of registrations (step S6 is “NO”), the process returns to step S2, and if k after the increment exceeds the number of registrations (S6 is “YES”), the first Return to step S1.
- a counter i for specifying the actual sensor is set to an initial value (for example, 1) ( Step S7). Then, the information of the i-th record in the sensing data provision condition DB is read (step S8), and the provision condition information is collated with the k-th use condition information read in step S3 (step S9).
- step S9 the k-th usage condition information and the i-th provision condition information.
- the sensing data type is completely the same, and the value indicated by the i-th provision condition information regarding the sensing area, sensing period, reliability, and consideration is included in the range specified by the k-th use condition information.
- the purpose indicated by the k-th use condition information is set to an allowable purpose in the i-th provision condition information, it is determined that the i-th provision condition information matches the k-th use condition information.
- step S10 If it is determined that both match (step S10 is “YES”), the process proceeds to step S11, and the sensor number and provision condition information of the i-th sensor are stored in the k-th matching list. If even one item falls outside the above requirements in the collation in step S9, it is determined that the i-th provision condition information does not match the k-th use condition information (step S10 is “NO”), and step S11 is skipped. .
- steps S12 and S13 i is incremented until i reaches the number of registrations, and the above steps S8 to S11 are executed for every hour i, so that all the real sensors that meet the kth use condition information are obtained.
- the combination of each sensor number and provision condition information is extracted and stored in the matching list.
- step S13 the contract matching processing unit 11 sets the third counter j for specifying the virtual sensor to an initial value (for example, 1) (step S14), and the virtual sensor management DB
- the information of the jth record is read (step S15), and it is checked whether or not the type of sensing data generated by the processing method in the jth record conforms to the type specified by the kth use condition information. (Step S16). If it is suitable (step S17 is “YES”), based on the sensor number of the lower sensor in the jth record, provision of the actual sensor located below the jth virtual sensor from the sensing data provision condition DB 101 is provided.
- the condition information is read (step S18), and it is determined whether or not the provision condition information group provided by these lower actual sensors matches the kth use condition information (step S19).
- step S19 it is determined whether or not all the conditions in each lower sensor are compatible with the use condition information with respect to the conditions other than the sensor data type and the consideration. If these values match, the sum of the considerations in each actual sensor is compared with the consideration determined by the use condition information. If the former value does not exceed the latter value, the provision condition information by the lower actual sensor is k It is determined that it conforms to the third usage condition information. If it is determined that they are matched (“YES" in step S20), the provision condition information of the jth virtual sensor is created by integrating the provision condition information of the lower real sensor and the sensing data type of the virtual sensor ( Step S21). Then, the sensor number of the j-th virtual sensor and the provision condition information created in step S21 are stored in the matching list (step S22).
- step S23 and S24 by incrementing j until the value of j reaches the number of registered virtual sensors (steps S23 and S24), by repeating the above processing, all virtual sensors that match the kth usage condition information are extracted. Combinations of these sensor numbers and provision condition information are stored in the matching list.
- step S24 When the value of j reaches the number of registrations (step S24 is “YES”), the contract matching processing unit 11 selects the number of sensors required by the application from the usage condition information of the kth application, and enters the matching list. A required number of sensor numbers are extracted from the stored sensor numbers, and these are set as sensor data providing source sensor numbers (step S25). Furthermore, the set sensor sensor number, the application number of the kth application, and the IP address are notified to the sensing data distribution processing unit 13 (step S26). If the matching list is empty, step S25 is skipped.
- the process of selecting the sensor number as the providing source sensor number in step S25 is performed in consideration of the providing condition information combined with the sensor number. For example, if sensor numbers corresponding to the required number are selected in order from the lowest value, the cost on the application side can be suppressed. Moreover, if the sensor number for a required number is selected in order from the one with the highest reliability, the accuracy of the sensing data to be provided can be increased. Alternatively, a selection criterion may be set for each application in a contract, and the criterion may be registered in the sensing data use condition DB, and sensing data may be selected according to the registered criterion.
- each contract matching processing unit 11 returns to step S5 in FIG. 11, increments the counter k, and proceeds to processing for the next application.
- step S6 becomes “YES”
- the process returns to the first step S1 to return k to the initial value again. As a result, the processing of the next cycle is started.
- FIG. 12 shows a processing procedure by the sensing data distribution processing unit 13 (steps S31 to S35), and FIG. 13 shows a processing procedure by the sensing data processing unit 12 (steps S41 to S48).
- FIG. 12 shows a processing procedure by the sensing data distribution processing unit 13 (steps S31 to S35)
- FIG. 13 shows a processing procedure by the sensing data processing unit 12 (steps S41 to S48).
- the sensing data distribution processor 13 acquires the providing source sensor number, the application number of the transmission destination application, and the IP address notified from the contract matching processing unit 11 (step S31), and provides them to the sensing data processing unit 12. A data acquisition request including the original sensor number is notified (step S32). In response, the sensing data processing unit 12 starts the process shown in FIG.
- the sensing data processing unit 12 receives a data acquisition request (step S41), and searches the sensing data management DB 104 based on the source sensor number included in the request (step S42). If the source sensor number is the actual sensor number, the sensing data corresponding to the sensor number is stored in the sensing data management DB 104, so the determination in step S43 is “YES”. In this case, the latest sensing data corresponding to the providing sensor number is read from the sensing data management DB 104 and provided to the sensing data distribution processing unit 13 (step S44).
- step S43 the determination in step S43 is “NO”.
- the sensing data processing unit 12 accesses the virtual sensor management DB 105 using the providing source sensor number, and reads management information corresponding to the number (step S45). Then, based on the sensor number of each lower sensor in the read management information, the latest sensing data of each lower sensor is read from the sensing data management DB 104 (step S46), and these are defined by the processing method in the management information. Process according to Through this process, sensing data of the virtual sensor is generated (step S47).
- step S45 If the sensor number of the lower sensor read in step S45 is the virtual sensor number, steps S45, S46, and S47 are executed based on the number to generate sensing data for the lower virtual sensor. In step S47, the sensing data is used.
- the sensing data processing unit 12 After the sensing data of the virtual sensor is generated, the sensing data processing unit 12 provides the generated sensing data to the sensing data distribution processing unit 13 (step S48). With the provision of the sensing data in step S48 or the previous step S44, the processing of the sensing data processing unit 12 in response to the data acquisition request ends.
- the sensing data distribution processing unit 13 waits until receiving sensing data according to the request (step S33).
- step S33 becomes “YES”
- the process proceeds to step S34, and the sensing data provided to the IP address acquired in step S31 is transmitted.
- log information having a configuration in which the provided sensor data, the application number and IP address of the transmission destination application, the transmission date and time, and the like are added to the transmitted sensing data is created and stored in the distribution log DB 106 (step S35). .
- the latest sensing data generated by the selected sensor is selected for the application that requires sensing data by selecting the actual sensor or virtual sensor that matches the usage conditions for the application that requires sensing data by the series of steps shown in FIGS. It becomes possible to provide. This makes it possible for any application to perform processing according to each purpose.
- FIG. 14 shows a specific example of an application that receives sensing data from the information management apparatus 1 described above.
- the application of this embodiment uses the image data generated in the monitored area to monitor the passage in the residential area for the purpose of watching.
- Necessary sensing data is provided from a security camera C attached to the entrance of a residence of a person who has contracted with a system operator in a residential area.
- the residents of the houses H1 and H2 are contractors of this system and users of the application, and the RFID reader / writer R is attached to each of the houses H1 and H2 together with the security camera C.
- the image data of each camera C is processed into sensing data combined with the location information of the dwelling in a communication device (such as a smartphone dedicated to processing) at the owner's house, and transmitted to the information management device 1.
- a communication device such as a smartphone dedicated to processing
- the identification information read by the reader / writer R is also incorporated into the sensing data.
- the information management apparatus 1 provides each sensing data to the application side system 2 after confirming that the provision condition information of the sensor in each contractor matches the usage condition information on the application side.
- the application-side system 2 detects pre-registered identification information from sensing data including RFID read data, the characteristics of the person (face, hair color and length, clothes, etc.) included in the image in the sensing data are detected. Color). Thereafter, it is checked whether or not the same feature is included in the image based on other sensing data.
- the person corresponding to the previously detected identification information is arranged by arranging the position information associated with these images in the order in which the features are extracted. Recognize the travel route. It is possible to set a virtual sensor by combining several sensing data used in this example.
- the identification information read from the RFID tag and image processing when the person leaves the house can be checked by associating with the recognized movement route.
- the moving route will leave a predetermined management target area, it is also possible to notify a registered contact.
- the camera C which is fixedly arranged for the purpose of crime prevention, is used as a sensor and used for services to a specific user. Tracker).
- an image from a camera installed for the purpose of fixed point observation is transmitted as sensing data to the information management device 1, this image can be used in a system for analyzing traffic of people and vehicles.
- the image has a high resolution and is an image of a camera installed in a mountainous area or a countryside, it can be provided to an application that provides a service for distributing an image for viewing to a desired person.
- FIG. 15 is a block diagram showing a schematic configuration of a network system according to another embodiment.
- This network system includes an information management device 5, a plurality of information providing devices 6, and a plurality of information using devices 7.
- the information management device 1, the information providing device 6, and the information using device 7 are connected via a network 8 so that they can communicate with each other.
- the information providing device 6 corresponds to the sensor in the above-described embodiment
- the information use device 7 corresponds to the device of the application side system 2 in the above-described embodiment.
- the information providing device 6 acquires information according to the main purpose and executes processing according to the purpose.
- the information providing device 6 is not a specific type of device, but various types of devices.
- the information providing device 6 is a monitoring device that monitors a suspicious person or the like, it acquires a captured image of a camera that images the monitoring target area, detects the presence or absence of a suspicious person, or images the monitoring target area. Display an image on a display device.
- it is an air conditioning control device that controls an air conditioner, the floor temperature is acquired with a temperature sensor, or the captured image of the camera that is capturing the floor is acquired to determine the degree of congestion on the floor, the number of people, etc. And control the operation of the air conditioner.
- it is an automatic ticket gate installed at the ticket gate of a station, it reads the ticket (kip, commuter pass, etc.) for visitors and participants, detects passage of ticket gates as ticket gate processing, Measure the number of participants.
- the information providing device 6 may be an imaging device such as a camera that images the monitoring target area, a temperature sensor that measures the temperature of the floor, or the like.
- a person who operates / manages the information providing apparatus 6 (hereinafter referred to as a provider) can provide information acquired by the information providing apparatus 6 to other apparatuses (information utilization apparatus 7). Further, the provider can limit the use of the information to be provided by the type of application program (hereinafter simply referred to as an application) that can be used.
- an application the type of application program
- the information use device 7 is an information processing device such as a personal computer or a mobile phone held by a user who uses information provided by the information providing device 6.
- an application that uses information provided by the information providing device 6 is installed.
- the information management device 1 provides provider contract information based on a contract for providing information from the information providing device 6 with the provider, and a contract for using information in the information using device 7 with the user. Manage user contract information, etc. based on.
- the information management apparatus 1 acquires information from the information providing apparatus 6 and transmits (provides) information to the information using apparatus 7 based on the provider contract information and the user contract information.
- the information management apparatus 1 does not transmit information that is not permitted to be used due to usage restrictions to the information utilization apparatus 7. As described above, the information management apparatus 1 manages and relays information between the information providing apparatus 6 that provides information and the information using apparatus 7 that uses the provided information.
- FIG. 16 is a block diagram illustrating a configuration of a main part of the information management apparatus.
- the information management apparatus 1 includes a control unit 51, a communication unit 52, a provider contract database 53 (provider contract DB 53), a user contract database 54 (user contract DB 54), and a management information database 55 (management information DB 55). ), An information recording database 56 (information recording DB 56), a usage history database 57 (use history DB 57), a recommendation level management database 58 (recommendation level management DB 58), and an affinity management database 59 (affinity management DB 59). It has.
- the control unit 51 controls the operation of the information management apparatus 1 main body.
- the communication unit 52 performs communication with the information providing device 6 and the information using device 7 via the network 8.
- the provider contract DB 53 registers the contents of a contract related to provision of information exchanged with the provider.
- FIG. 17 is a schematic diagram showing the configuration of the provider contract DB.
- the provider contract DB 53 corresponds to the provision condition storage unit referred to in the present invention.
- the provider contract DB 53 includes a contract number (contract No.), a provider ID, a device type, a device address, a device URL, a detection range, a password, a maintenance request notification address, information for each contract related to provision of information with the provider.
- a record in which a type, an information storage location address, a usable application type, a usable user attribute, a recognition rate, and a usage fee are associated is registered. The provider exchanges this contract for each information to be provided.
- the contract number is a unique number assigned individually for each contract related to provision of information with the provider.
- the provider ID identifies the provider.
- the device type is a type of the information providing device 6 that acquires the information to be provided, and is, for example, the above-described automatic ticket gate, monitoring device, air conditioning control device, monitoring camera, voice sensor, or the like.
- the device address is the IP address of this device.
- the device URL is a URL (Uniform Resource Locator) of this device.
- the detection range indicates a range in which information provided by the information providing device 6 is acquired.
- this range is registered by latitude and longitude is taken as an example.
- the password is a character string that is input to confirm whether the operator is the provider when the contract is changed or updated. This password is set by the provider at the time of contract.
- the maintenance request notification address is an e-mail address designated by the provider, and is a transmission destination (destination) of an e-mail related to a maintenance request for the information providing apparatus 6.
- the maintenance request is made when information is not provided.
- the information type is a type of information provided from the information providing device 6, and information (raw data) acquired by the information providing device 6, such as video data and audio data, OD data, number of people data, attribute data (adult, Processing data (metadata) obtained by processing raw data acquired by the information providing device 6 such as attribute data indicating children, women, and men).
- information raw data acquired by the information providing device 6, such as video data and audio data, OD data, number of people data, attribute data (adult, Processing data (metadata) obtained by processing raw data acquired by the information providing device 6 such as attribute data indicating children, women, and men).
- the information storage location address indicates an address on a recording medium (information recording DB 56, which will be described later) on which information provided from the information providing device 6 is recorded and stored.
- the available application type indicates the type of application that is permitted to use the information.
- the available user attribute indicates the attribute (individual, corporation, etc.) of the user who is permitted to use the information.
- the available application type and the available user attribute are restrictions on the use of information provided by the provider when making a contract, and correspond to the restriction data referred to in the present invention.
- the type of application permitted to be used and the user attribute are registered as usage restrictions, but the configuration may be such that the type of application not permitted to be used and the user attribute are registered. .
- the recognition rate indicates the accuracy of the information, and is based on an error (information detection accuracy in the information providing device 6) included in the information acquired by the information providing device 6 in three stages of high, medium, and low. It is classified. That is, the recognition rate is the reliability of the information provided.
- the usage fee is an amount charged to a user who uses the information.
- FIG. 17 shows a charge per 1 MB, the charge for one use may be used, or the charge may be determined in other forms.
- FIG. 18 is a schematic diagram showing the configuration of the user contract DB.
- This user contract DB 54 corresponds to the use condition storage unit referred to in the present invention.
- the user contract DB 54 includes a contract number (contract No.), a user ID, a used application type, a desired use detection range, a priority item, a usage recognition rate range, and a usage fee for each contract related to provision of information with the user. Records that associate ranges are registered.
- the contract number is a unique number assigned individually to the contract for providing information with the user.
- the user ID identifies the user.
- the used application type is a type of application that uses information provided by the user.
- the desired use information type indicates the type of information to be used.
- the desired use detection range indicates the range from which information to be used is acquired.
- this range is registered by latitude and longitude.
- Priority indicates whether to prioritize cost or recognition rate when using information.
- the use recognition rate range defines the lower limit of the recognition rate of information to be used.
- the usage fee range defines the upper limit of the fee for information to be used.
- the priority, usage recognition rate range, and usage fee range can be set by the user at the time of contract.
- the management information DB 55 is generated based on the registration contents of the provider contract DB 53 and the user contract DB 54 described above.
- FIG. 19 is a schematic diagram showing the configuration of the management information DB.
- the management information DB 55 corresponds to the management information storage unit referred to in the present invention.
- the management information DB 55 includes, for each user, a contract No (user contract number), a user ID, a use application type, a use desired information type, a detection range, a priority item, an information storage location address, a device URL, and a device state. A record in which the recognition rate, the maintenance request notification address, and the usage fee are associated with each other is registered.
- the control unit 51 generates the management information DB 55 based on the registration contents of the provider contract DB 53 and the user contract DB 54 described above at a predetermined timing (for example, every day at midnight). Thereby, the management information DB 55 reflects the update of the provider contract DB 53 and the user contract DB 54 at a predetermined timing.
- the management information DB 55 includes sensor state information. This is confirmed by communication with the corresponding information providing apparatus 6.
- the information recording DB 56 is a database that records and manages information provided from the information providing apparatus 6.
- FIG. 20 is a schematic diagram showing the configuration of the information recording DB.
- the information record DB 56 registers a record in which a file name, a password, a contract number (provider contract number), a provider ID, and an information storage location address are associated with each other.
- the file name is a file name given to information provided from the information providing apparatus 6.
- the password, contract number (provider contract number), provider ID, and information storage location address are registered in the provider contract DB 53.
- the control unit 51 also generates the information recording DB 56 with reference to the provider contract DB 53 described above at a predetermined timing.
- the timing for generating the information recording DB 56 and the timing for generating the management information DB 55 may be the same or different.
- the usage history DB 57 is a database in which the usage history of information provided by the provider is registered.
- FIG. 21 is a schematic diagram showing the configuration of the usage history DB.
- the usage history DB 57 registers a record in which a provider ID, a file name, an information storage location address, a used application type, an access date and time, and a user ID are associated with each other.
- the usage history DB 17 a usage application type, an access date and time, and a user ID are additionally registered for the used information every time the user uses the information.
- the usage history DB 17 is used for calculating a fee to be paid to the provider according to the use of the provided information, and for calculating a fee charged to the user according to the use of the information.
- the affinity management DB 59 is a database in which the affinity in a combination of information of these two types is registered for each type of application when the information uses two information.
- FIG. 24 is a flowchart showing the operation of the information management apparatus in the provision contract process.
- the information management device 1 is waiting for a contract conclusion request for providing information from the provider via the network 8 (S51).
- the provider who concludes a contract for providing information has registered in advance and has a provider ID.
- the provider operates the information providing apparatus 6 that acquires information to be actually provided, a personal computer, or the like, and transmits a contract conclusion request for providing information to the information management apparatus 1.
- This fastening request includes the provider ID.
- the information management apparatus 1 When the information management apparatus 1 receives a request for conclusion of a contract for providing information by the communication unit 52, the information management apparatus 1 transmits an input screen for the information provision contract to the apparatus that has transmitted the conclusion request (S52).
- the input screen transmitted in S52 includes device type, device address, device URL, detection range, password, maintenance request notification address, information type (multiple), available application type, available user attribute, recognition rate, and usage fee.
- An input field is provided. That is, this input screen is a screen for requesting input for items registered in the provider contract DB 53. The provider performs input in each input field, and returns this to the information management apparatus 1.
- the information management apparatus 1 When the information management apparatus 1 receives the contents of all the items necessary for the conclusion of the contract for providing information (S53), the information management apparatus 1 records the contract number and the address on the recording medium for recording and storing the current contract ( The information storage location address) is determined and registered in the provider contract DB 53 (S54). Further, the information management apparatus 1 transmits a screen for notifying the completion of the contract to the apparatus that has transmitted the contract conclusion request for the provision of the current information (S55), and returns to S51. In S55, the contents of the contract relating to the provision of the current information are transmitted to the provider.
- the provider when the provider concludes a contract for providing information, the provider can set the usable application type and the usable user attribute as usage restrictions on the information. The provider can also set a usage fee for using the information, and can determine the value of the information to be provided.
- FIG. 25 is a flowchart showing the operation of the information management apparatus in this usage contract process.
- the information management apparatus 1 waits for a request to conclude a contract related to the use of information from the user via the network 8 (S61).
- a user who concludes a contract related to the use of information performs user registration in advance and has a user ID.
- the user operates the information utilization device 7 or the like that actually receives the information to transmit a request for concluding a contract related to the use of the information to the information management device 1.
- This fastening request includes a user ID.
- FIG. 26 is a display example of an input screen related to type selection transmitted from the information management apparatus 1 in S62 in the information use apparatus 7 or the like.
- the user selects the type of the application that uses the information on the input screen for selecting the type, and transmits it to the information management apparatus 1.
- the information management device 1 presents the type of information recommended for use of information, the combination of information with high affinity, etc., according to the type of application that uses the information transmitted from the information use device 7 or the like, An input screen requesting input of necessary items in the usage contract is transmitted (S63, S64).
- FIG. 27 is a display example of the input screen transmitted from the information management apparatus 1 in S64 in the information use apparatus 7 or the like.
- the type of recommended information is information of a type for which the recommended level stored in the recommended level management DB 58 exceeds a predetermined threshold for the selected type of application. Further, this is a combination of information in which the affinity stored in the affinity management DB 59 exceeds a predetermined threshold.
- FIG. 27 exemplifies a case where child watching is selected as the application type.
- the user inputs the type of information desired to be used, the sensing range, the upper limit of the usage fee, the priority (cost or recognition rate), etc. while confirming the screen display shown in FIG.
- the information management apparatus 1 When the information management apparatus 1 receives all the items necessary for the conclusion of the contract related to the use of information (S65), the information management apparatus 1 determines the contract number and registers it in the user contract DB 54 (S66). Further, the information management apparatus 1 transmits a screen for notifying the completion of the contract to the apparatus that has transmitted the contract conclusion request relating to the use of the current information (S67), and returns to S61. In S67, the contents of the contract relating to the use of this information are transmitted to the user.
- the user can set the type of information to be used, the upper limit of usage charges, priorities, etc. as desired.
- FIG. 28 is a flowchart showing the management information DB update process.
- the information management apparatus 1 selects one user registered in the user contract DB 54 (S71). For the user selected in S71, the information management apparatus 1 selects one usage type application for which the user has signed a usage contract (S72). The information management apparatus 1 performs a search process for extracting all information that can be provided to the usage type application selected in S72 from the provider contract DB 53 (S73). In S73, information that can be provided is searched based on the type of application permitted to be provided by the provider at the time of contract and the attribute of the user. That is, the provision of information to the user is restricted by the restriction on the use of information set by the provider at the time of contract. The information management apparatus 1 registers the available information searched in S73 in the management information DB 55 in association with the usage type application selected in S72 (S74).
- the information management apparatus 1 determines, for the user selected in S71, whether or not the processing related to S72 to S74 described above has been executed for all types of usage applications for which the user has concluded a usage contract ( S75). In S75, if there is a type of application for which the processing related to S72 to S74 is not processed for the user, the information management apparatus 1 returns to S72 and repeats the above processing.
- the information management apparatus 1 determines for all users registered in the user contract DB 54. It is determined whether or not the processing relating to S72 to S75 has been executed (S76). In S76, if there is a user who has not yet performed the processes in S72 to S75 in S76, the information management apparatus 1 returns to S71 and repeats the above processes.
- the provision is made.
- the user contract DB 53 and the user contract DB 54 are updated.
- the information management apparatus 1 repeatedly executes the management information DB update process shown in FIG. 28 at a predetermined timing, thereby updating the management information DB 55 in response to the update of the provider contract DB 53 and the user contract DB 54. Is going.
- FIG. 29 is a flowchart showing this information use processing in the information management apparatus.
- the information management apparatus 1 waits for an information use request to be transmitted in the communication unit 52 (S81).
- the information management device 1 searches the management information DB 55 using the user ID and the usage application type included in the usage request (S82).
- the information management apparatus 1 determines whether or not usable information is registered in the management information DB 55 for the use type application for which use of information is requested this time (S83).
- the information management apparatus 1 proceeds to S93 described later.
- the information management apparatus 1 determines whether there is one or a plurality of registered usable information (S84). If there is one piece of information that can be used, the information management apparatus 1 selects that information as information to be used (S86). On the other hand, if there is a plurality of usable information, the information management apparatus 1 selects the information to be used from the plurality of information based on the priority items (S85). In S85, if the cost is prioritized, the information with the lowest usage fee is selected, and if the recognition rate is prioritized, the information with the highest recognition rate is selected.
- the information management device 1 determines whether the information selected in S85 or S86 is stored in the information recording DB 66 (S87). If the information selected in S85 or S86 is not stored in the information recording DB 56, the information management device 1 requests the information providing device 6 that is contracted to provide this information to send information. (S88). When the information management apparatus 1 receives information from the information providing apparatus 6 that has requested transmission of information in S88, the information management apparatus 1 stores the information in the information record DB 56 (S89, S90). In S90, the information received from the information providing device 6 this time is recorded in a predetermined file name and a predetermined address.
- the information management device 1 transmits information to be provided to the information utilization device 7 that has transmitted the utilization request this time, creates a utilization history associated with the transmission of this information, and registers it in the utilization history DB 57 (S91, S92).
- the information provider can set restrictions on the use of the information provided by the information providing device 6.
- the information management apparatus 1 generates the management information DB 55 based on the registered contents of the provider contract DB 53 and the user contract DB 54, and this management information in response to the information use request from the information use apparatus 7.
- the DB 55 is searched to select information to be provided to the information utilization device 7. Therefore, the time required for selecting information to be provided to the information utilization device 7 can be shortened.
- FIG. 30 is a schematic diagram showing the use of information in the child watch app installed in the information use device.
- the GPS server 4 is a device that requests a contracted GPS function-equipped terminal (such as a mobile phone) to notify the current position and acquires the current position transmitted from the GPS function-equipped terminal.
- the GPS function-equipped terminal has a known GPS function, and can measure the position of the terminal itself.
- the GPS function-equipped terminal is possessed by the child of the user of the information utilization device 7.
- the user operates the information utilization device 7 to execute the child watching application.
- the information using device 7 first performs a process of acquiring the current position of the user's child.
- This process is a process for requesting the GPS server 4 to notify the position of the GPS function-equipped terminal possessed by the child.
- the GPS server 4 is a server with which the user contracts separately from this system, and performs a process of notifying the information utilization device 7 of the position of the child (that is, the position of the terminal equipped with the GPS function).
- the GPS server 4 requests the corresponding GPS function-equipped terminal to notify the current position.
- the GPS function-equipped terminal acquires the position of the own terminal and notifies the GPS server 4 of this.
- the GPS server 4 transfers the position notified from the GPS function-equipped terminal to the information utilization device 7.
- the information using device 7 acquires the current position of the GPS function-equipped terminal, that is, the current position of the child.
- the information use device 7 makes an information use request to the information management device 1.
- This use request includes the user ID, the type of application that uses the information (child watching application), the current position of the child acquired from the GPS server 4, and the like.
- the information management apparatus 1 selects information to be provided to the information utilization apparatus 7 based on this utilization request. For example, the captured image of the monitoring camera 2a is selected as information to be provided to the information utilization device 7.
- the detection range (that is, the imaging area) of the monitoring camera 2a includes the current position of the child acquired from the GPS server 4 this time. The reason why the monitoring cameras 2b and 2c are not selected is that the imaging area is far from the current position of the child, the usage fee is high, the recognition rate is low, and the like.
- the information management device 1 transmits the captured image (video information) of the monitoring camera 2a to the information use device 7.
- the information utilization device 7 displays the captured image of the monitoring camera 2a transmitted from the information management device 1 on a display or the like. The user confirms the state of the child from the displayed image.
Abstract
Description
成したセンシングデータをセンシングデータ配信処理部13に提供する(ステップS48)。このステップS48または先のステップS44によるセンシングデータの提供をもって、データ取得要求に対するセンシングデータ処理部12の処理は終了する。
推奨度
=(その種別のアプリの利用者の中で、その種別の情報を利用している利用者数)/(その種別のアプリの利用者の総数)
により算出している。
推奨度=10/100=0.1
である。
親和度
=(その種別のアプリの利用者の中で、これら2つの種別の情報を利用している利用者数)/(その種別のアプリの利用者の総数)
により算出している。
推奨度=5/100=0.05
である。
2…アプリケーション側システム
6…情報提供装置
7…情報利用装置
8…ネットワーク
10…センシングデータ取得部
11…契約マッチング処理部
12…センシングデータ処理部
13…センシングデータ配信処理部
14…対価精算処理部
51…制御部
52…通信部
53…提供者契約DB
54…利用者契約DB
55…管理情報DB
56…情報記録DB
57…利用履歴DB
58…推奨度管理DB
59…親和度管理DB
101…センシングデータ提供条件DB
102…センシングデータ利用条件DB
103…契約DB
104…センシングデータ管理DB
105…仮想センサ管理DB
S1~S5…実センサ
U1,U2,U3…仮想センサ
Claims (13)
- センサ毎に、そのセンサで生成されるセンシングデータの提供条件情報がセンサの識別情報に対応づけられて登録される提供条件記憶部と、
センシングデータの利用を必要とするアプリケーション毎に、必要とするセンシングデータの利用条件情報が、センシングデータの送信先のアドレスに対応づけられて登録される利用条件記憶部と、
前記提供条件記憶部に登録されているセンサにより生成されたセンシングデータを通信により取得するセンシングデータ取得部と、
前記利用条件記憶部に登録された利用条件情報毎に前記提供条件記憶部を検索して当該利用条件情報に適合する提供条件情報を特定する特定部と、
前記適合する提供条件情報が特定された利用条件情報に対応する送信先アドレスに対し、前記特定された提供条件情報に対応する識別情報のセンサに対して前記センシングデータ取得部が取得したセンシングデータを用いた送信処理を実行するセンシングデータ配信部と、を備えた情報管理装置。 - 前記提供条件情報は、そのセンサで生成されるセンシングデータの情報種別とセンシング対象エリアの位置情報とを含み、
前記利用条件情報は、必要とするセンシングデータの情報種別とセンシング対象エリアの位置情報とを含む、請求項1に記載の情報管理装置。 - 前記提供条件記憶部に登録されているセンサの中の複数を組み合わせてこれらのセンサによるセンシングデータを統合することにより新たなセンシングデータを生成する仮想センサを設定するために、組み合わせられるセンサの識別情報と前記統合処理の定義と統合により生成されるセンシングデータの情報種別とを含む管理情報が登録される仮想センサ管理情報記憶部と、
仮想センサ管理情報記憶部に登録された管理情報中の識別情報に対応する複数のセンサにつきセンシングデータ取得部が取得したセンシングデータを、同じ管理情報中の定義に基づき統合することによって、当該管理情報に対応する仮想センサのセンシングデータを取得するデータ処理部と、を備え、
前記特定部は、利用条件記憶部に登録された利用条件情報に基づき提供条件記憶部および仮想センサ管理情報記憶部を検索して、センシング対象エリアの位置情報が前記利用条件情報に適合するセンサの組み合わせにより当該利用条件情報に適合する種別のセンシングデータを生成する仮想センサを特定する手段を含み、
前記センシングデータ配信部は、前記特定部により特定された仮想センサの管理情報に基づいて前記データ処理部が取得したセンシングデータを、その特定の対象とした利用条件情報に対応する送信先アドレスに対して送信する、請求項1、または2に記載の情報管理装置。 - 前記利用条件記憶部に登録される利用条件には、センシングデータを取得するタイミングを示す情報が含まれており、
前記特定部は、処理対象の利用条件情報を順に変更する処理を循環させながら、処理対象の利用条件情報がセンシングデータを取得するタイミングに達していることを条件として前記利用条件情報に適合する提供条件情報を特定し、
前記配信部は、利用条件記憶部に登録された一利用条件情報に対する特定部による特定処理が終了する都度、その特定の対象とした利用条件情報に対応する送信アドレスにセンシングデータを送信する、請求項1~3のいずれかに記載の情報管理装置。 - 前記提供条件記憶部に登録される提供条件情報には、センシングデータの提供者の識別情報と、センシングデータの提供に対して当該提供者が希望する対価の額を示す情報とが含まれ、
前記利用条件記憶部に登録される利用条件情報には、センシングデータの提供を受けるアプリケーションの識別情報と当該アプリケーションの運営者がセンシングデータの提供に対して支払う対価の額を示す情報が含まれており、
前記特定部は、特定される提供条件情報により求まる対価の額が利用条件情報中の対価の額を上回らないことを条件として、利用条件情報に適合する提供条件情報を特定し、前記特定部による特定処理と、前記配信部による送信に使用されたセンシングデータに対応する提供条件情報および送信先アドレスに対応する利用条件情報に基づき、センシングデータの提供に対して前記アプリケーションの運営者が支払う対価の額と、前記送信に使用されたセンシングデータを生成したセンサの所有者が受け取る対価の額とを算出する対価算出部を備える、請求項1~4のいずれかに記載の情報管理装置。 - 前記提供条件情報は、そのセンサで生成されるセンシングデータの利用用途に対するセンシングデータの利用制限を示す制限情報を含み、
前記利用条件情報は、必要とするセンシングデータの利用用途を示す利用用途情報を含む、請求項1~5のいずれかに記載の情報管理装置。 - 前記アプリケーション毎に、前記提供条件記憶部に登録されている前記提供条件情報、および前記利用条件記憶部に登録されている前記利用条件情報を用いて、そのアプリケーションが必要とするセンシングデータの利用用途を示す利用用途情報と、この利用用途に対して利用が制限されていないセンシングデータと、を対応付けた管理情報を生成する管理情報生成部と、
前記管理情報生成部が生成した管理情報を記憶する管理情報記憶部と、
いずれかの前記アプリケーションから、センシングデータの利用要求を受信すると、前記管理情報記憶部が記憶している前記管理情報を参照し、このアプリケーションに送信するセンシングデータを選択する情報選択部と、を備えた請求項6に記載の情報管理装置。 - 新たにセンシングデータの提供にかかる契約要求を受け付けたとき、この契約要求にかかる前記提供条件情報を、前記提供条件記憶部に追加登録する提供契約部と、
前記アプリケーションでの新たなセンシングデータの利用を希望する旨の契約要求を受け付けたとき、この契約要求にかかる前記利用条件情報を、前記利用条件記憶部に追加登録する利用契約部と、を備え、
前記管理情報生成部は、予め定めたタイミングになる毎に、前記管理情報の生成を行う、請求項7に記載の情報管理装置。 - 前記センサから提供されたセンシングデータを記憶するセンシングデータ記憶部と、
前記情報選択部が前記アプリケーションに送信するセンシングデータとして選択したセンシングデータが、前記情報記憶部に記憶されていなければ、該当するセンサに対して、センシングデータを要求する要求部と、を備えている請求項7、または8に記載の情報管理装置。 - 前記提供条件情報は、センシングデータ毎に、そのセンシングデータの利用料金、および認識度を含み、
前記利用条件情報は、利用料金、および認識度に対する優先度を含み、
前記情報選択部は、前記利用側情報に含まれている優先度に応じて、前記アプリケーションに送信するセンシングデータを選択する、請求項7~9のいずれかに記載の情報管理装置。 - センシングデータを生成する複数のセンサと、センシングデータを必要とする複数のアプリケーションと、前記センサと前記アプリケーションとの間でセンシングデータを中継する情報管理装置と、を通信可能に接続したネットワークシステムにおいて、
前記情報管理装置は、
前記センサ毎に、そのセンサで生成されるセンシングデータの提供条件情報がセンサの識別情報に対応づけられて登録される提供条件記憶部と、
センシングデータの利用を必要とするアプリケーション毎に、必要とするセンシングデータの利用条件情報が、センシングデータの送信先のアドレスに対応づけられて登録される利用条件記憶部と、
前記提供条件記憶部に登録されているセンサにより生成されたセンシングデータを通信により取得するセンシングデータ取得部と、
前記利用条件記憶部に登録された利用条件情報毎に前記提供条件記憶部を検索して当該利用条件情報に適合する提供条件情報を特定する特定部と、
前記適合する提供条件情報が特定された利用条件情報に対応する送信先アドレスに対し、前記特定された提供条件情報に対応する識別情報のセンサに対して前記センシングデータ取得部が取得したセンシングデータを用いた送信処理を実行するセンシングデータ配信部と、を備えている、
ネットワークシステム。 - センサ毎に、そのセンサで生成されるセンシングデータの提供条件情報をセンサの識別情報に対応づけて提供条件記憶部に登録する第1のステップと、
センシングデータの利用を必要とするアプリケーション毎に、必要とするセンシングデータの利用条件情報をセンシングデータの送信先のアドレスに対応づけて利用条件記憶部に登録する第2のステップと、
前記提供条件記憶部に登録されているセンサにより生成されたセンシングデータを通信により取得する第3のステップと、
前記利用条件記憶部に登録された利用条件情報毎に前記提供条件記憶部を検索して当該利用条件情報に適合する提供条件情報を特定する第4のステップと、
前記適合する提供条件情報が特定された利用条件情報に対応する送信先アドレスに対し、前記特定された提供条件情報に対応する識別情報のセンサに対して前記センシングデータ取得部が取得したセンシングデータを用いた送信処理を実行する第5のステップと、をコンピュータに実行させる情報管理プログラム。 - センサ毎に、そのセンサで生成されるセンシングデータの提供条件情報をセンサの識別情報に対応づけて提供条件記憶部に登録する第1のステップと、
センシングデータの利用を必要とするアプリケーション毎に、必要とするセンシングデータの利用条件情報をセンシングデータの送信先のアドレスに対応づけて利用条件記憶部に登録する第2のステップと、
前記提供条件記憶部に登録されているセンサにより生成されたセンシングデータを通信により取得する第3のステップと、
前記利用条件記憶部に登録された利用条件情報毎に前記提供条件記憶部を検索して当該利用条件情報に適合する提供条件情報を特定する第4のステップと、
前記適合する提供条件情報が特定された利用条件情報に対応する送信先アドレスに対し、前記特定された提供条件情報に対応する識別情報のセンサに対して前記センシングデータ取得部が取得したセンシングデータを用いた送信処理を実行する第5のステップと、をコンピュータが実行する情報管理方法。
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/238,637 US20140214726A1 (en) | 2011-08-12 | 2012-07-25 | Information management device, network system, information management program, and information management method |
EP12824104.9A EP2743883B1 (en) | 2011-08-12 | 2012-07-25 | Information management device, network system, information management program, and information management method |
JP2013528944A JP5605512B2 (ja) | 2011-08-12 | 2012-07-25 | 情報管理装置、ネットワークシステム、情報管理プログラム、および情報管理方法 |
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2011176477 | 2011-08-12 | ||
JP2011-176477 | 2011-08-12 | ||
JP2012-005147 | 2012-01-13 | ||
JP2012005147 | 2012-01-13 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2013024673A1 true WO2013024673A1 (ja) | 2013-02-21 |
Family
ID=47714997
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2012/068775 WO2013024673A1 (ja) | 2011-08-12 | 2012-07-25 | 情報管理装置、ネットワークシステム、情報管理プログラム、および情報管理方法 |
Country Status (4)
Country | Link |
---|---|
US (1) | US20140214726A1 (ja) |
EP (1) | EP2743883B1 (ja) |
JP (1) | JP5605512B2 (ja) |
WO (1) | WO2013024673A1 (ja) |
Cited By (14)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2014222480A (ja) * | 2013-05-14 | 2014-11-27 | 株式会社東芝 | サービス提供システム、サービス提供方法およびサービス提供管理装置 |
WO2015128954A1 (ja) * | 2014-02-26 | 2015-09-03 | オムロン株式会社 | デバイス情報提供システム、デバイス情報提供方法 |
EP2974233A1 (en) * | 2013-03-15 | 2016-01-20 | Dana Limited | System and method for data collection and analysis using a multi-level network |
JP2016014641A (ja) * | 2014-07-03 | 2016-01-28 | 株式会社ビスキャス | 移動体の存在位置検知システム |
JP2017102793A (ja) * | 2015-12-03 | 2017-06-08 | オムロン株式会社 | データフロー制御装置およびデータフロー制御方法 |
JP6298204B1 (ja) * | 2017-09-01 | 2018-03-20 | ヤフー株式会社 | 算出装置、算出方法および算出プログラム |
JP2019046435A (ja) * | 2018-02-21 | 2019-03-22 | ヤフー株式会社 | 算出装置、算出方法および算出プログラム |
WO2019107404A1 (ja) * | 2017-12-01 | 2019-06-06 | オムロン株式会社 | データ生成装置、データ生成方法、データ生成プログラムおよびセンサ装置 |
US20200136846A1 (en) * | 2014-06-26 | 2020-04-30 | Ainemo Inc | Terminal and method for bidirectional live sharing and smart monitoring |
WO2020184535A1 (ja) * | 2019-03-12 | 2020-09-17 | 凸版印刷株式会社 | IoT機器信用度算出装置、IoT機器信用度算出システム、IoT機器信用度算出装置の利用方法、IoT機器信用度算出方法、記憶媒体、IoTデータプラットフォーム、および、IoTデータプラットフォームによるIoTデータの処理方法 |
JP2020182229A (ja) * | 2020-07-10 | 2020-11-05 | Kddi株式会社 | データ管理装置、データ管理方法及びプログラム |
JP2022093415A (ja) * | 2020-07-10 | 2022-06-23 | Kddi株式会社 | データ管理装置、データ管理方法及びプログラム |
US11546180B2 (en) | 2016-08-31 | 2023-01-03 | Kddi Corporation | Data management apparatus, data management method, and data communication system |
JP7221467B1 (ja) * | 2022-06-08 | 2023-02-13 | 三菱電機株式会社 | 制御装置、制御システム、機器制御方法およびプログラム |
Families Citing this family (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10051060B2 (en) * | 2015-12-04 | 2018-08-14 | International Business Machines Corporation | Sensor data segmentation and virtualization |
US10072951B2 (en) | 2015-12-04 | 2018-09-11 | International Business Machines Corporation | Sensor data segmentation and virtualization |
JP6372508B2 (ja) * | 2016-03-15 | 2018-08-15 | オムロン株式会社 | データフロー制御装置およびデータフロー制御方法 |
US10043100B2 (en) | 2016-04-05 | 2018-08-07 | Omni Ai, Inc. | Logical sensor generation in a behavioral recognition system |
EP3279752A1 (en) * | 2016-08-01 | 2018-02-07 | Siemens Aktiengesellschaft | Virtual sensor system and method for generating output values |
JP6390692B2 (ja) * | 2016-12-15 | 2018-09-19 | オムロン株式会社 | データ配信システム、指示装置、データ配信装置、センサ管理装置、データ配信方法、およびプログラム |
EP3686832B1 (en) * | 2017-09-19 | 2024-04-24 | Omron Corporation | Mobile sensor management unit, mobile sensor apparatus, matching apparatus, sensing data distribution system, data provision method, and data provision program |
JP6501007B1 (ja) * | 2018-02-13 | 2019-04-17 | オムロン株式会社 | 出力管理装置、出力管理方法及びプログラム |
JP6489250B1 (ja) * | 2018-02-13 | 2019-03-27 | オムロン株式会社 | 候補抽出装置、候補抽出方法及びプログラム |
US10782655B2 (en) * | 2018-06-16 | 2020-09-22 | International Business Machines Corporation | Composable time-series observability in sensor data fusion |
Citations (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH05111077A (ja) | 1991-10-15 | 1993-04-30 | Matsushita Electric Works Ltd | 総合監視制御システム |
JP2002117184A (ja) * | 2000-10-05 | 2002-04-19 | Shimizu Corp | モバイルセンサネットワークシステム |
JP2005004359A (ja) * | 2003-06-10 | 2005-01-06 | Nec Corp | プローブカー情報システム、収集提供方法、および収集提供プログラム |
JP2005031955A (ja) | 2003-07-11 | 2005-02-03 | Kddi Corp | 移動体追跡システム |
JP2005321934A (ja) | 2004-05-07 | 2005-11-17 | Nec Corp | センサネットワークシステム、管理装置、センサ、利用者端末、センサ方法およびプログラム |
JP2006031723A (ja) * | 2000-10-02 | 2006-02-02 | Omron Corp | 情報仲介システムとそれに用いられる情報仲介方法 |
JP2009104365A (ja) * | 2007-10-23 | 2009-05-14 | Hitachi Electronics Service Co Ltd | センシングデータの配信方法、センサネットシステム及び広告配信装置 |
JP2011002355A (ja) | 2009-06-19 | 2011-01-06 | Clarion Co Ltd | ナビゲーション装置および車両制御装置 |
Family Cites Families (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6909921B1 (en) * | 2000-10-19 | 2005-06-21 | Destiny Networks, Inc. | Occupancy sensor and method for home automation system |
US7602413B2 (en) * | 2002-10-18 | 2009-10-13 | Sony Corporation | Information processing system and method, information processing apparatus, image-capturing device and method, recording medium, and program |
KR100548154B1 (ko) * | 2003-06-11 | 2006-01-31 | (주)엔텔스 | 유무선 통신망에서의 패킷 전송 제어 및 패킷 과금 데이터생성을 위한 방법 및 장치 |
US20070073608A1 (en) * | 2005-09-23 | 2007-03-29 | Garcia Crisostomo B | Cash only marketplace system for trading securities |
JP5076587B2 (ja) * | 2007-03-27 | 2012-11-21 | 富士通株式会社 | センサ情報管理システム、センサ情報管理方法、センサ情報管理プログラム |
US20100302042A1 (en) * | 2009-05-28 | 2010-12-02 | David Barnett | Sensor-based independent living assistant |
US20110055255A1 (en) * | 2009-08-26 | 2011-03-03 | Pharos Systems International Inc. | Method for downloading a data set to an output device |
JP5018914B2 (ja) * | 2010-03-03 | 2012-09-05 | 沖電気工業株式会社 | センサデータ提供システム、方法及び装置 |
-
2012
- 2012-07-25 EP EP12824104.9A patent/EP2743883B1/en active Active
- 2012-07-25 US US14/238,637 patent/US20140214726A1/en not_active Abandoned
- 2012-07-25 WO PCT/JP2012/068775 patent/WO2013024673A1/ja active Application Filing
- 2012-07-25 JP JP2013528944A patent/JP5605512B2/ja active Active
Patent Citations (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH05111077A (ja) | 1991-10-15 | 1993-04-30 | Matsushita Electric Works Ltd | 総合監視制御システム |
JP2006031723A (ja) * | 2000-10-02 | 2006-02-02 | Omron Corp | 情報仲介システムとそれに用いられる情報仲介方法 |
JP2002117184A (ja) * | 2000-10-05 | 2002-04-19 | Shimizu Corp | モバイルセンサネットワークシステム |
JP2005004359A (ja) * | 2003-06-10 | 2005-01-06 | Nec Corp | プローブカー情報システム、収集提供方法、および収集提供プログラム |
JP2005031955A (ja) | 2003-07-11 | 2005-02-03 | Kddi Corp | 移動体追跡システム |
JP2005321934A (ja) | 2004-05-07 | 2005-11-17 | Nec Corp | センサネットワークシステム、管理装置、センサ、利用者端末、センサ方法およびプログラム |
JP2009104365A (ja) * | 2007-10-23 | 2009-05-14 | Hitachi Electronics Service Co Ltd | センシングデータの配信方法、センサネットシステム及び広告配信装置 |
JP2011002355A (ja) | 2009-06-19 | 2011-01-06 | Clarion Co Ltd | ナビゲーション装置および車両制御装置 |
Cited By (26)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP2974233A1 (en) * | 2013-03-15 | 2016-01-20 | Dana Limited | System and method for data collection and analysis using a multi-level network |
JP2014222480A (ja) * | 2013-05-14 | 2014-11-27 | 株式会社東芝 | サービス提供システム、サービス提供方法およびサービス提供管理装置 |
WO2015128954A1 (ja) * | 2014-02-26 | 2015-09-03 | オムロン株式会社 | デバイス情報提供システム、デバイス情報提供方法 |
JP5822050B1 (ja) * | 2014-02-26 | 2015-11-24 | オムロン株式会社 | デバイス情報提供システム、デバイス情報提供方法 |
EP2940601A4 (en) * | 2014-02-26 | 2016-10-12 | Omron Tateisi Electronics Co | SYSTEM AND METHOD FOR PROVIDING DEVICE INFORMATION |
US9679032B2 (en) | 2014-02-26 | 2017-06-13 | Omron Corporation | Device information providing system and device information providing method |
US20200136846A1 (en) * | 2014-06-26 | 2020-04-30 | Ainemo Inc | Terminal and method for bidirectional live sharing and smart monitoring |
US11115227B2 (en) * | 2014-06-26 | 2021-09-07 | Ainemo Inc. | Terminal and method for bidirectional live sharing and smart monitoring |
JP2016014641A (ja) * | 2014-07-03 | 2016-01-28 | 株式会社ビスキャス | 移動体の存在位置検知システム |
JP2017102793A (ja) * | 2015-12-03 | 2017-06-08 | オムロン株式会社 | データフロー制御装置およびデータフロー制御方法 |
WO2017094442A1 (ja) * | 2015-12-03 | 2017-06-08 | オムロン株式会社 | データフロー制御装置およびデータフロー制御方法 |
US11546180B2 (en) | 2016-08-31 | 2023-01-03 | Kddi Corporation | Data management apparatus, data management method, and data communication system |
JP6298204B1 (ja) * | 2017-09-01 | 2018-03-20 | ヤフー株式会社 | 算出装置、算出方法および算出プログラム |
JP2019046177A (ja) * | 2017-09-01 | 2019-03-22 | ヤフー株式会社 | 算出装置、算出方法および算出プログラム |
WO2019107404A1 (ja) * | 2017-12-01 | 2019-06-06 | オムロン株式会社 | データ生成装置、データ生成方法、データ生成プログラムおよびセンサ装置 |
US11657303B2 (en) | 2017-12-01 | 2023-05-23 | Omron Corporation | Data generating apparatus, data generating method, data generating program and sensing apparatus |
JP2019101749A (ja) * | 2017-12-01 | 2019-06-24 | オムロン株式会社 | データ生成装置、データ生成方法、データ生成プログラムおよびセンサ装置 |
JP2019046435A (ja) * | 2018-02-21 | 2019-03-22 | ヤフー株式会社 | 算出装置、算出方法および算出プログラム |
JP2020149218A (ja) * | 2019-03-12 | 2020-09-17 | 凸版印刷株式会社 | IoT機器信用度算出装置、IoT機器信用度算出システム、IoT機器信用度算出装置の利用方法、IoT機器信用度算出方法、プログラム、IoTデータプラットフォーム、および、IoTデータプラットフォームによるIoTデータの処理方法 |
WO2020184535A1 (ja) * | 2019-03-12 | 2020-09-17 | 凸版印刷株式会社 | IoT機器信用度算出装置、IoT機器信用度算出システム、IoT機器信用度算出装置の利用方法、IoT機器信用度算出方法、記憶媒体、IoTデータプラットフォーム、および、IoTデータプラットフォームによるIoTデータの処理方法 |
JP7346853B2 (ja) | 2019-03-12 | 2023-09-20 | 凸版印刷株式会社 | IoT機器信用度算出装置、IoT機器信用度算出システム、IoT機器信用度算出装置の利用方法、IoT機器信用度算出方法、プログラム |
JP2022093415A (ja) * | 2020-07-10 | 2022-06-23 | Kddi株式会社 | データ管理装置、データ管理方法及びプログラム |
JP2020182229A (ja) * | 2020-07-10 | 2020-11-05 | Kddi株式会社 | データ管理装置、データ管理方法及びプログラム |
JP7311669B2 (ja) | 2020-07-10 | 2023-07-19 | Kddi株式会社 | データ管理装置、データ管理方法、プログラム及びデータ通信システム |
JP7221467B1 (ja) * | 2022-06-08 | 2023-02-13 | 三菱電機株式会社 | 制御装置、制御システム、機器制御方法およびプログラム |
WO2023238298A1 (ja) * | 2022-06-08 | 2023-12-14 | 三菱電機株式会社 | 制御装置、制御システム、機器制御方法およびプログラム |
Also Published As
Publication number | Publication date |
---|---|
JP5605512B2 (ja) | 2014-10-15 |
EP2743883A4 (en) | 2015-03-18 |
JPWO2013024673A1 (ja) | 2015-03-05 |
EP2743883A1 (en) | 2014-06-18 |
US20140214726A1 (en) | 2014-07-31 |
EP2743883B1 (en) | 2017-09-06 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
JP5605512B2 (ja) | 情報管理装置、ネットワークシステム、情報管理プログラム、および情報管理方法 | |
JP6615243B2 (ja) | 車共有ユーザ仲介方法およびシステム | |
KR100383870B1 (ko) | 무인 주차 관리 시스템 및 무인 주차 관리 방법 | |
KR101044990B1 (ko) | 증강 현실을 이용한 상하수도 관거 종합 관리 시스템 및 방법 | |
WO2014030510A1 (ja) | デバイス管理装置及びデバイス管理方法 | |
US20040105005A1 (en) | Networked camera system and a monitoring method thereof | |
CN104202717A (zh) | 以基本单位短程围栏的信息平台及应用方法 | |
US20090198623A1 (en) | System and method for executing and authenticating an activity at a remote location | |
CN105933737A (zh) | 基于与多个在线设备联系的概况的目标电视广告 | |
KR20170079536A (ko) | 공공 디스플레이를 통한 사용자 맞춤형 광고 제공 시스템 및 이를 이용한 광고 제공 방법 | |
JP2014006741A (ja) | 賃貸スペース管理システム | |
KR20160071828A (ko) | 데이터 중개 시스템 및 방법 | |
JP2017130029A (ja) | 空き駐車スペースの時間貸しシステム | |
KR20200080505A (ko) | 지능형 소상공인 지원 서비스 제공 시스템, 서버 및 방법 | |
KR101947874B1 (ko) | 외부 서비스와 연동된 주차 요금 결제 시스템 및 방법 | |
JP2004234644A (ja) | 情報配信装置および情報配信方法 | |
KR20200020457A (ko) | 관심지점 리스트에 대한 구독과 리뷰 정보에 기초하여 보상을 제공하는 방법 및 시스템 | |
WO2017149777A1 (ja) | スペース貸出システム、スペース貸出方法及びプログラム | |
KR20190075220A (ko) | Gps를 이용한 독서실 좌석정보 제공시스템 | |
KR102490018B1 (ko) | 무인 차량 대여 시스템 | |
KR102370821B1 (ko) | 챗봇 기반의 피플 카운팅 모니터링 시스템, 서버 및 방법 | |
JPWO2013038905A1 (ja) | 情報管理装置、ネットワークシステム、情報管理プログラム、および情報管理方法 | |
KR20200047504A (ko) | 관심지점 리스트에 대한 구독과 리뷰 정보에 기초하여 보상을 제공하는 방법 및 시스템 | |
KR20170039463A (ko) | 사용자 장치, 비콘, 서비스 제공 장치, 그를 포함하는 결제 시스템, 그의 제어 방법 및 컴퓨터 프로그램이 기록된 기록매체 | |
KR101382063B1 (ko) | 영상 인식을 이용한 전시장 관리 시스템 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 12824104 Country of ref document: EP Kind code of ref document: A1 |
|
DPE1 | Request for preliminary examination filed after expiration of 19th month from priority date (pct application filed from 20040101) | ||
ENP | Entry into the national phase |
Ref document number: 2013528944 Country of ref document: JP Kind code of ref document: A |
|
REEP | Request for entry into the european phase |
Ref document number: 2012824104 Country of ref document: EP |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 14238637 Country of ref document: US |