JP2024025814A - Electronic devices and systems - Google Patents

Abstract

The present invention provides an electronic device that can easily select at least one piece of rule information from a large number of pieces of rule information for realizing an IoT system. According to an embodiment, an electronic device includes a storage section and a display control section. The storage unit stores a plurality of pieces of rule information. The rule information defines typical attribute information when rules are determined, and provides convenience in determining rules. [Selection diagram] Figure 1

Description

Embodiments of the present invention relate to electronic devices and systems.

2. Description of the Related Art IoT (Internet of Things) systems that link objects (referred to as devices) in real space via the Internet are becoming widespread. Creating an IoT system requires advanced technical knowledge such as programming related to device control, and creating an IoT system is not easy.

In recent years, it has been proposed to create an IoT system by linking multiple devices according to rule information such as "if so-and-so, do so-and-so." An IoT system is realized by installing rule information into an electronic device that can control multiple devices.

A user who wants to create an IoT system selects rule information suitable for him from among a large number of previously prepared rule information and downloads it to an electronic device. When the number of rule information prepared in advance increases, it becomes difficult to select the rule information.

Japanese Patent Application Publication No. 2019-145150

An object of the present invention is to provide an electronic device and a system that can easily select at least one rule information etc. from a large number of rule information etc. for realizing an IoT system.

According to one embodiment, an electronic device connected to the plurality of sensors and the plurality of processing modules includes:
When the sense result of at least one sensor among the plurality of sensors is a specific result, at least one processing module among the plurality of processing modules is associated with the sense result to perform a coordinated operation. a storage unit that stores multiple pieces of rule information;
a display control unit that generates a display screen that displays rule identification information included in the plurality of rule information, and
Each of the plurality of pieces of rule information includes identification information of a creator of the rule information and attribute information of the rule information, and the attribute information includes a first information indicating a scene in which a service provided by the rule information is used. , second identification information indicating a theme of the service provided by the rule information, and third identification information indicating a problem to be solved by the service provided by the rule information. An electronic device is provided, including.

FIG. 3 is a diagram illustrating an example of functional blocks of an edge computer in the IoT system according to the first embodiment. FIG. 2 is a diagram illustrating an example of a data structure of rule information used by the IoT system according to the first embodiment. 3 is a diagram showing an example of a data structure of an IF-THEN section in the rule information shown in FIG. 2. FIG. 3 is a diagram showing an example of a data structure of rule attributes in the rule information shown in FIG. 2. FIG. FIG. 3 is a diagram illustrating an example of a data structure of execution history information stored by an edge computer. FIG. 3 is a diagram showing an example of a data structure of evaluation information stored in an edge computer. It is a diagram showing an example of functional blocks of a cloud server in the IoT system according to the first embodiment. FIG. 3 is a diagram illustrating an example of a data structure of usage count ranking information generated by a cloud server. FIG. 3 is a diagram showing an example of a usage frequency ranking table. FIG. 7 is a diagram showing another example of the data structure of usage frequency ranking information. FIG. 7 is a diagram showing another example of the data structure of usage frequency ranking information. FIG. 7 is a diagram showing another example of the usage frequency ranking table. FIG. 3 is a diagram illustrating an example of a data structure of evaluation ranking information generated by a cloud server. It is a figure showing an example of an evaluation ranking table. FIG. 7 is a diagram showing still another example of a usage frequency ranking table. FIG. 7 is a diagram showing still another example of a usage frequency ranking table. It is a figure which shows yet another example of an evaluation ranking table. It is a figure which shows yet another example of an evaluation ranking table. 7 is a flowchart illustrating an example of rule creation by the edge computer according to the first embodiment. FIG. 20 is a diagram showing an example of screen transitions on the display of the edge computer when creating the rules shown in FIG. 19; 20 is a diagram showing another example of screen transitions on the display during rule creation shown in FIG. 19; FIG. 20 is a diagram showing still another example of the screen transition of the display during rule creation shown in FIG. 19. FIG. FIG. 3 is a sequence diagram showing an example of a rule information download process by the edge computer according to the first embodiment. 7 is a flowchart illustrating an example of rule usage by the edge computer according to the first embodiment.

Embodiments will be described below with reference to the drawings. The following description exemplifies devices and methods for embodying the technical idea of the embodiment, and the technical idea of the embodiment includes the structure, shape, arrangement, and material of the components described below. etc., but is not limited to. Modifications that can be easily conceived by those skilled in the art are naturally included within the scope of the disclosure. In order to make the explanation more clear, in the drawings, the size, thickness, planar dimension, shape, etc. of each element may be changed from the actual embodiment and schematically expressed. A plurality of drawings may include elements having different dimensional relationships and ratios. In some drawings, corresponding elements may be designated by the same reference numerals and redundant descriptions may be omitted. Although some elements may be given a plurality of names, these names are merely illustrative, and do not deny that other names may be given to these elements. Furthermore, this does not negate the use of other names for elements that are not given multiple names. Note that in the following description, "connection" means not only direct connection but also indirect connection via other elements.

(Overview of IoT system)
Embodiments relate to an IoT system that allows various devices to cooperate based on rule information. The IoT system of the embodiment allows not only devices but also services provided by software to cooperate. Services include email services provided by programs installed on devices, SNS services, and web services provided by cloud servers. In this specification, devices and services that are units linked by an IoT system may also be referred to as modules. Rule information is information that describes rules that define how to combine multiple modules. In the embodiment, devices and services can be freely combined, so a convenient system can be realized in various scenes at home, at work, and in society.

A service refers to an active operation that combines control of a predetermined entity/state/information and provides a predetermined process, change in state, or content or data/information to a user for a fee or free of charge. In the embodiment, services are provided to users according to rule information. As a form of providing this service, in the embodiment, a cross-border (straddling) combination (crossing) of services in real space or physical space using various devices and services in cyber space using Web services etc. ) services may be provided.

Content means specific content related to a predetermined function, and has specificity that allows individual differences from others to be identified. For example, the abstract concept of "movie" is not included, but specific content for which a "movie name (title)" is set as a means of identification from other content is applicable. Similarly, the abstract concept of a "web screen" displayed on a web browser is not included, but also a specific web page located on a specific URL.

The module includes means for implementing a predetermined function. A module is composed of a combination of a human-recognizable entity (also referred to as a state or information) in a real space in which this predetermined function is realized and its control unit. Services are provided to users by a combination of operations of a plurality of modules controlled by individual control units. A module is a concept of a combination of an entity and a control unit for realizing a predetermined function. The human-perceivable entities that make up the module and their controls need not be physically integrated. For example, a human-recognizable entity and its control unit may be installed at physically separate locations, and the two may be linked using a communication function. The human-recognizable entities that make up the module and their control units do not need to form a physically real object.

A device includes anything that exists in real space and is used to implement a predetermined function. Devices include devices that execute processing, devices that display content, and storage devices that store data. The device may have built-in communication functionality for communicating with external devices. A device may have the ability to act on physical or chemical conditions or phenomena in nature. Devices that passively act on the natural world include sensors and the like. Devices that actively act on the natural world include robots, drive mechanisms, display devices (display elements), and the like. The physical form of the device is not limited to a stationary type, but may be a mobile type. Examples of physical forms of devices that can be worn by the user include band-type sensors that are fixed to the user's arms or legs, belt-type sensors that are fixed to the waist, and VR-type or AR-type head-mounted displays that are worn on the user's head. Including form.

An example of the rule defines a cooperation relationship between modules such that when the state detected by the sensor module is a specific state, the execution module executes a specific process. Rule information that describes rules has various formats, one example of which is condition information (also referred to as an IF part) that indicates a specific state, and information that is executed when the state detected by the sensor module is a specific state. There is a format that includes processing information (also referred to as a THEN section) indicating a specific process executed by the module. However, the format of the rule information is not limited to this format.

An example of rule information in this format is "If the temperature is 26 degrees or higher, operate the air conditioner in cooling mode." In this example, the modules (devices in this case) that the IoT system cooperates with are a temperature sensor that detects temperature, which is an example of a state, and an air conditioner that executes operation in cooling mode, which is an example of processing. Examples of states and processing are not limited to the above examples.

In this specification, modules that detect conditions are referred to as IF modules, and modules that perform processing are referred to as THEN modules. The IoT system includes an IF module, a THEN module, and an electronic device. The electronic device is connected to the IF module and the THEN module, for example wirelessly. The electronic device determines whether the condition detected by the IF module is a particular condition, and if so, provides instructions to the THEN module to perform processing.

An example of an electronic device includes, but is not limited to, a smartphone. The electronic device is installed with rule information and software that controls the IF module and THEN module according to the rule information. The electronic device periodically requests the IF module to detect a state, and if the IF module detects that the state detected is a specific state based on the output of the IF module, the electronic device requests the THEN module to detect the state. Control execution of specific processing.

In one piece of rule information, the number of IF parts and THEN parts, that is, the number of states to be detected and the number of processes to be executed, are not limited to one each. For example, one process may be executed when each of the plurality of states is a plurality of specific states. For example, the rule information may be executed if the condition detected by the first IF module is a first specific condition and the condition detected by the second IF module is a second specific condition. may indicate one process. Alternatively, multiple processes may be executed when one state is one specific state. Furthermore, a plurality of processes may be executed when each of the plurality of states is a plurality of specific states. For example, the rule information may specify a first process to be performed by a first THEN module and a second process to be performed by a second THEN module when the state detected by the detection module is a specific state. May be shown.

Users who want to create or use an IoT system may create their own rule information, but they can also use rule information created by other users. In the embodiment, the user who created the rule information uploads the rule information to the server. A user who wants to use rule information accesses the server, selects and downloads appropriate rule information from among a large number of rule information.

(rule information)
The electronic device requests the IF module identified by the IF module ID included in the valid rule information stored in the memory to detect the state and send the detection result to the electronic device every IF cycle. send a request signal to The IF module detects a state in response to a request signal from the electronic device, and transmits a detection signal indicating the detected state to the electronic device.

The electronic device determines whether the state detected by the IF module is a specific state described in the IF section of any rule information. When the electronic device determines that the detected state is a specific state, the electronic device transmits a request signal requesting the THEN module described in the THEN section of the rule information to execute the process described in the THEN section.

The electronic device thus provides a convenient mechanism (IoT system) by coordinating at least one IF module and at least one THEN module. Note that since rule information defines modules for providing a mechanism and their cooperation, it corresponds to a recipe for cooking, and therefore, in this specification, rule information is also referred to as recipe information.

In order to construct an IoT system using rule information, it is necessary to expand and distribute rule information. It is conceivable that the cloud server includes a rule publication site and publishes a rule list screen showing stored rule information. Note that there may be some rule information that is not permitted to be made public. In that case, the rule publishing site will only publish the rule information that is permitted to be published.

When a user accesses a rule publication site, he or she can view a screen listing published rules. The user can select rule information from the rule list screen and download the selected rule information to the edge computer.

A user can easily configure an IoT system by preparing the IF module and THEN module described in the rule information.

Rule information is created by a user who wants to build an IoT system, but in addition to these users, creators who create it professionally and manufacturers of the IF module and THEN module that make up the rule information can also create rule information. It is possible.

In this way, it is expected that many people will upload a large amount of rule information to the cloud server. When the number of rule information stored in a cloud server increases, it becomes difficult to select appropriate rule information. Therefore, the cloud server provides the user with a list screen of recommended rule information from among a large amount of rule information. This facilitates the user's selection of rule information.

In order to recommend rules, the cloud server needs to calculate recommendation degree information regarding rule information. Recommendation level information is information regarding an index used to recommend rule information. The value of the recommendation degree information corresponds to the degree to which the rule information is recommended. For example, the value of recommendation degree information regarding rule information that is more recommended is greater than the value of recommendation degree information regarding rule information that is less recommended. Recommendation level information may be calculated from a plurality of indicators instead of a single indicator. Examples of indicators include usage frequency, evaluation, and the like. The number of uses includes the cumulative number of uses and the number of uses within a certain period of time. The number of uses within a certain period includes the number of uses in the most recent unit period (for example, one month). Rule information that is frequently used or has a high evaluation may be considered to be more recommended rule information.

The cloud server may provide the user with a ranking table in which rule information is arranged in order of the number of uses and the value of recommendation information regarding evaluation (for example, in descending order) as a rule list screen. The ranking table may consist of a plurality of pages, and the plurality of pages are displayed in descending order of the recommendation degree information value. Thereby, even if there is a large number of rule information, the user can select and download desired rule information from the rule list screen in a short time.

(edge computer)
FIG. 1 is a diagram showing an example of the configuration of an IoT system according to the present embodiment, and particularly shows an example of details of an edge computer 6 in the IoT system. The IoT system according to this embodiment includes a cloud server 2, an edge computer 6, an IF module 8A, and a THEN module 8B. Cloud server 2 and edge computer 6 are connected via network 18. Edge computer 6 and IF module 8A are connected via network 18. The edge computer 6 and THEN module 8B are connected via a network 18. The edge computer 6 is an example of an electronic device that creates rule information. The configuration of the cloud server is shown in Figure 7. The edge computer 6 is an example of an electronic device for each user. Although FIG. 1 shows a single edge computer 6, multiple edge computers 6 of different users or the same user may be connected to the network 18.

The edge computer 6 includes an input device 102, a display device 104, a transmitter 106, a receiver 108, microservices 10A and 10B, an application 20, a rule memory 28, an evaluation memory 122, and a history memory 124. The input device is, for example, a keyboard or a mouse. The display device is, for example, a liquid crystal display or a projector. Input device 102 and display device 104 may be comprised of a single display with touch input functionality instead of being comprised of separate devices.

Examples of the edge computer 6 include a personal computer, a smartphone, a tablet, a signage, a gateway, a router, a car navigation system, a home appliance (such as a television), a multifunction device (copy machine), a cloud server, and the like.

Edge computers 6 can be installed in transportation devices such as trucks, trains, ships, and aircraft, as well as hospitals, factories, apartments, private residences (speech synthesis, email, SNS, etc.), agricultural facilities, fishing facilities, forestry facilities, and schools. , parks and other facilities.

The application 20 that constructs an IoT system based on rule information includes a rule creation section 112, a rule acquisition section 114, an evaluation management section 116, an execution history management section 118, and a rule engine 26. The application 20 is a program for realizing a platform for constructing an IoT system based on rule information. The rule engine 26 includes a rule management section 132, a status monitor 134, and a process starting section 136.

The rule creation unit 112 creates rule information based on the text information input from the input device 102 and sends the rule information to the transmission unit 106.

Examples of rule information are shown in FIGS. 2 to 4.

FIG. 2 shows an example of the data structure of rule information. Rule information includes multiple items. Examples of rule information items include rule ID, rule name, creator ID, creation date and time, IF-THEN section, rule attribute, editability flag, editor ID, and the like. Examples of rule information items are not limited to the example in FIG. 2. For example, rule attributes, editability flags, editor IDs, etc. may be omitted.

The rule ID is unique identification information for each piece of rule information. The rule ID is automatically determined at the time of creation, but does not need to be determined at the time of creation. The creator may freely set rule IDs as long as they do not overlap. The rule name represents the content of the rule, that is, the content of the IoT system. Examples of rule names include, but are not limited to, "cooling operation at high temperature", "visitor notification", "voice guide", "mechanical failure notification", "abnormal heartbeat notification", and the like. The creator ID is unique identification information for each creator of rule information. The creation date and time will be entered automatically.

The IF-THEN section shows cooperation between the IF module 8A and THEN module 8B. An example of the IF-THEN section is shown in FIG.

The rule attribute is information indicating what kind of service the rule information provides. An example of rule attributes is shown in FIG.

A rule creator can permit or prohibit others from editing the rule he or she has created (specifically, the IF-THEN section, rule attributes, etc.). The rule creator sets the editability flag to, for example, "1" when allowing editing of the rule created by the rule creator, and sets the editability flag to, for example, "0" when prohibiting the editing. Note that the specific value of the editability flag is not limited to this.

In this system, if the user downloads editable rule information, the user can edit the rule information. When editable rule information is downloaded, an icon indicating that the rule information can be edited is displayed on the display. When this icon is touched, the rule information can be edited.

Rule information created by editing by the user is uploaded to the server in the same way as newly created rule information. A rule created by editing is registered as a rule having a different rule ID from the original rule before editing. In that case, the creator ID remains unchanged, but the editor ID is added. The editor ID is unique identification information for each editor. It is also possible to create and register multiple rules by editing one editable original rule.

FIG. 3 shows an example of the data structure of the IF-THEN section. The IF-THEN section is input by the creator or edited by the editor, and consists of an IF section and a THEN section.

The IF section includes multiple items. Examples of items in the IF section include, but are not limited to, the IF module ID which is the identification information of the IF module 8A, the condition for starting execution of processing, the IF parameter that defines the details of the condition, and the cycle for checking the condition. Including IF cycle etc. A condition is a particular condition that is compared to the condition detected by IF module 8A. Examples of the IF module 8A include, but are not limited to, temperature sensors, humidity sensors, doors, alcohol detectors, opening/closing sensors, beacons, human sensors, water leak sensors, power generation chairs, power generation floors, weight sensors, and multiplex sensors. Includes functional sensors (light, temperature, humidity, acceleration, gyro, etc.), thermometers, weight scales, microphones, hygrometers, cameras, etc.

The THEN section also includes multiple items. Examples of items in the THEN section include, but are not limited to, a THEN module ID that is identification information of the THEN module 8B, a process that the THEN module 8B executes, a THEN parameter that defines details of the process, and the like. Examples of THEN module 8B include, but are not limited to, communication robots, power strips, notification watches, wristbands, LEDs, remote controls for electronic devices, email transmission, map display, voice synthesis, and the like.

Examples of combinations of the IF part and THEN part are not limited to these, but
"If an object weighing more than XX grams is placed on the tray, it will light up for XX seconds to notify you."
"If the temperature exceeds 〇〇 degrees, operate the air conditioner in 〇〇 mode."
"If the vibration of the machine tool stops for more than XX seconds, a warning message will be displayed for XX seconds to notify the operator."
“When 〇〇 people come to 〇〇, we will start providing audio guidance for 〇〇 in 〇〇 language.
For example, ``If the heart rate exceeds 〇〇, notify the person by 〇〇.''

○○ in the IF section and THEN section are numerical values or options that specify the details of the IF section and THEN section, and are defined by the IF parameter and THEN parameter.

FIG. 4 shows an example of the data structure of rule attributes. The rule attribute includes multiple items. Examples of rule attribute items include, but are not limited to, subject ID, scene ID, theme ID, task ID, and the like. The rule attributes can be used in the rule recommendation process described below. Rule attributes can also be used as keywords in searching for rule information.

The target person ID is identification information indicating the user who is the target of the process executed based on the rule information, that is, the target person of the service provided based on the rule information. Examples of targets include, but are not limited to, employees (ID=P1), managers (ID=P2), professors, nurses, and the like.

The scene ID is identification information indicating a scene in which processing is executed based on the rule information, that is, a scene in which a service provided by the rule information is used. Examples of scenes include, but are not limited to, a conference room, a restaurant, a luggage packing area, a construction site, an office (ID=S1), a factory (ID=S2), a classroom, an elevator, a house site, a living room at home, Grocery stores, coffee shops, parks, school grounds, clothing stores (apparel shops), immigration gates, tourist spots, convenience stores, museums (ID=S3) art museums, railway stations, office buildings, hotels, highways, hotels This includes lobbies, distribution centers, tennis courts, airports, restrooms, bus interiors, etc.

The theme ID is identification information indicating the theme of the process executed based on the rule information, that is, the theme of the service provided by the rule information. Examples of themes include, but are not limited to, security (ID=T1), efficiency (ID=T3), comfort, peace of mind, share expansion (ID=T2), automation, money making/saving, and entertainment (ID=T4). ), health (ID=T5), convenience, etc.

The problem ID is identification information indicating a problem to be solved by a process executed based on the rule information, that is, a problem to be solved by a service provided by the rule information. Examples of issues include, but are not limited to, visualization (ID=O1), functional addition, energy saving (ID=O2), ecology (ID=O3), and the like. The data structure of the rule attribute is not limited to the example shown in FIG.

When creating rule information, the creator may set rule attributes. The creator may set or change the rule attributes at any time rather than when creating the rule information. Note that if the rule ID, rule name, keyword in the IF-THEN section, creator ID, editor ID, etc. are used to search for rule information, and at least one item of rule attributes is not used, the creator cannot use the rule information. There is no need to set the rule attribute item that does not apply. Instead of inputting the rule attribute item, the rule attribute item may be set by displaying the options of the rule attribute item and selecting one of the options. Note that if there is an item among the rule attribute items that does not need to be limited, an ID of all is set for the item.

For convenience of illustration, the rule information is shown divided into three tables; however, in actual rule information, the IF-THEN part shown in Fig. 3 and the rule attributes shown in Fig. 4 are incorporated into the table shown in Fig. 2. It may be a single table.

Returning to the explanation of FIG. 1, the transmitter 106 transmits the rule information to the cloud server 2 via the network 18.

When the user of the edge computer 6 creates rule information, the rule creation unit 112 may display a guidance screen for rule creation on the display device 104. The rule creation unit 112 creates rule information based on information input or selected by the creator from the input device 102 according to the guidance screen. Although an example has been shown in which rule information is created according to the guidance screen, the user may directly input information necessary for creating rules to create rule information without using the guidance screen.

Note that instead of inputting the rule information as text information from the input device 102, this information may be input as an audio signal, and the rule information may be input by performing voice recognition on the audio signal.

The transmitter 106 includes a memory (not shown). The transmitter 106 writes the rule information transmitted from the rule creator 112 into memory. When the sending unit 106 receives a request to send rule information from a user, it may send the rule information in the memory to the cloud server 2, or it may send a certain number of rule information every time a certain number of rule information is stored in the memory. The rule information may be transmitted to the cloud server 2, or the rule information stored in the memory may be transmitted to the cloud server 2 at regular intervals. The user can use the input device 102 to send a request to send rule information to the sending unit 106 .

The rule information transmitted from the plurality of edge computers 6 to the cloud server 2 is stored in the cloud server 2 in the formats shown in FIGS. 2 to 4, for example.

When the user of the edge computer 6 downloads rule information from the cloud server 2, the rule acquisition unit 114 sends a display request signal requesting display of a ranking table of the rule information regarding the recommendation level information specified by the user or a display request signal selected by the user. A download request signal requesting download of the rule information is sent to the transmitter 106. The transmitting unit 106 transmits a display request signal or a download request signal to a rule publication site (not shown) of the cloud server 2 via the network 18.

When the rule publication site receives a display request signal requesting to display a ranking table of rule information for specified recommendation information, it displays ranking information in which multiple pieces of rule information are arranged in descending order of recommendation information on a rule list screen. It is sent to the edge computer 6 as information.

The receiving unit 108 of the edge computer 6 transmits the received rule list screen information to the rule acquiring unit 114. The rule acquisition unit 114 displays a ranking table on the display device 104 based on the rule list screen information.

When the user selects at least one piece of rule information in the displayed ranking table, the rule acquisition unit 114 sends a download request signal to the transmission unit 106 requesting download of the selected rule information. The transmitter 106 transmits the download request signal to the rule publication site via the network 18.

Upon receiving the download request signal for the selected rule information, the rule publication site transmits the selected rule information to the edge computer 6.

The receiving unit 108 of the edge computer 6 sends the received rule information to the rule management unit 132 of the rule engine 26. The rule management unit 132 writes rule information into the rule memory 28. Rule memory 28 stores rule information.

Downloading the rule information may be paid or free. In the case of a charge, for example, the charge may be added to an item in the data structure of the rule information shown in FIG. 2, and when the rule management unit 132 writes the rule information into the rule memory 28, the billing process may be performed.

A state monitor 134 of the rules engine 26 is connected to the microservices 10A, 10B. Microservice 10A is connected to IF module 8A via network 18. Microservice 10B is connected to THEN module 8B via network 18. Note that the network connecting the edge computer 6 and the cloud server 2 and the network connecting the edge computer 6, IF module 8A, and THEN module 8B are described as the same network in the example of FIG. 1, but they are different networks. It's okay. The microservices 10A and 10B are control means for the IF module 8A and THEN module 8B, which are configured by programs using an object-oriented programming language.

For convenience of explanation, FIG. 1 shows a single IF module 8A and a single THEN module 8B, but a plurality of IF modules 8A and a plurality of microservices 10A corresponding to them may be provided, or a plurality of THEN modules may be provided. 8B and a plurality of microservices 10B corresponding thereto may be provided. Note that when configuring an IoT system that provides one service, it is sufficient to have two modules: at least one IF module 8A and at least one THEN module 8B. Further, if one module has the function of detecting a state and the same module has the function of executing processing, it is sufficient to have one module. For example, by using an illuminance sensor with an LED, it is possible to realize an IoT system that follows rule information such that when the illuminance is equal to or higher than a threshold, the LED is turned on.

As described above, the IF module 8A and THEN module 8B are not limited to devices, but include processing, content, or data. Therefore, the microservices 10A and 10B also include program software using AI technology to control transitions between Web pages and screen operations corresponding to specific Web pages. Similarly, the microservices 10A and 10B include an application program that automatically extracts the number of people appearing in a specific video content using AI technology, and an application program that analyzes acquired data using statistical analysis, etc. Also included.

Connections between the IF module 8A, THEN module 8B, and microservices 10A and 10B and the network 18 may be wireless or wired. Examples of wireless connections include Bluetooth (registered trademark), mobile phone line, Wi-Fi (registered trademark), and the like. Examples of wired connections include wired LAN and USB connections.

The IF module 8A and THEN module 8B include a module in real space and a module in cyber space. Examples of modules in real space include, but are not limited to, sensors, beacons, home appliances, mobile terminals such as smartphones and tablets, HMDs (head mounted displays), IoT devices, and GPS satellites. The modules in real space include modules arranged outside the edge computer 6 as shown in FIG. 1 and modules built into the edge computer 6 although not shown in FIG. Examples of included modules include, but are not limited to, temperature sensors, pressure sensors, and gyros.

Examples of modules in cyberspace include, but are not limited to, automatic trading of securities (stocks of specific brands), ordering of specific products, and automatic transfer of received product prices, realized by web service servers and IoT service servers. (billing processing), and user services such as applications for purchasing tickets for movies and music, applications for reservations for travel, etc.

Returning to the explanation of the rule engine 26, the status monitor 134 periodically requests status detection from the microservice 10A corresponding to the IF module 8A described in the IF section of the rule information, and receives a detection signal from the microservice 10A. Receive. When the status monitor 134 receives the detection request from the microservice 10A, the status monitor 134 determines whether the status detected by the IF module 8A is specified in the IF section of any of the valid rule information stored in the rule memory 28. It is determined whether the state matches the state of , and the determination result is sent to the processing starting unit 136.

When the status monitor 134 detects that the detection status of the IF module 8A matches a specific status, the process activation unit 136 sends an execution instruction signal to cause the THEN module 8B to execute the process described in the THEN part of the rule information. is sent to the microservice 10B corresponding to THEN module 8B. When the microservice 10B receives the control signal, it sends a processing execution command to the corresponding THEN module 8B. The control signal is also sent to the execution history management section 118.

Use of the rule information may be paid or free. In the case of a charge, the charge may be added to an item of the data structure of the rule information shown in FIG. 2, for example, and when the processing activation unit 136 performs the activation process, the charging process may be performed.

The execution history management unit 118 creates execution history information based on the control signal output from the processing activation unit 136, writes the execution history information into the history memory 124, and sends the execution history information to the transmission unit 106. History memory 124 stores execution history information. The execution history indicates the history of the execution of the process described in the THEN section, and also indicates the history of the use of the rule information. An example of the execution history information will be described later with reference to FIG.

The transmitting unit 106 includes a memory that stores the execution history information transmitted from the execution history management unit 118 until it is transmitted to the cloud server 2. Upon receiving a request to send execution history information from a user, the transmission unit 106 may transmit the execution history information in the memory to the cloud server 2 via the network 18, or send a certain number of execution history information to the memory. A fixed number of execution history information may be transmitted each time the execution history information is stored, or execution history information stored in the memory may be transmitted at fixed intervals. The user can use the input device 102 to send a request to send execution history information to the sending unit 106 .

The user can input text information indicating the evaluation of the rule information from the input device 102. The evaluation management unit 116 creates evaluation information of rule information based on the text information input from the input device 102. The evaluation information includes character strings such as comments, evaluation values, and the like. There is no limit to the time when evaluation information is created. The user can instruct the edge computer 6 to create or create the evaluation information using the input device 102.

When the evaluation management unit 116 is instructed to create evaluation information, the evaluation management unit 116 generates the evaluation information based on the rule information stored in the edge computer 6 and stored in the rule memory 28 and the execution history stored in the history memory 124. Displays a list of rule information used in the past (rule information for which the process described in the THEN section has been executed) on the display device 104, allows input of evaluation information of the rule information in the list, and also allows evaluation of rule information in the list. Prompt for information input. That is, evaluation information of rule information can only be input by a user who actually used the rule information, and it is not possible for a person who has not used the rule information to input evaluation information. Thereby, the credibility of the evaluation information can be improved.

Note that displaying a list of rule information used in the past is not essential, and the user may select rule information by rule ID, rule name, etc. and input evaluation information. In this case as well, the evaluation management unit 116 does not allow rule information that is not actually used to be selected and evaluation information to be input.

The evaluation management section 116 writes the created evaluation information into the evaluation memory 122 and sends it to the transmission section 106. Details of the evaluation information will be described later with reference to FIG. 6. The evaluation memory stores evaluation information.

Note that instead of inputting the evaluation information as text information from the input device 102, this information may be input as an audio signal, and the evaluation information may be input by performing voice recognition on the audio signal.

The transmitter 106 includes a memory that stores the evaluation information transmitted from the evaluation manager 116 until it is transmitted to the cloud server 2. Upon receiving a request to send evaluation information from a user, the transmitting unit 106 may transmit the evaluation information in the memory to the cloud server 2 via the network 18, or a certain number of evaluation information may be stored in the memory. A fixed number of evaluation information may be transmitted every time, or evaluation information stored in memory may be transmitted at fixed time intervals. The user can use the input device 102 to send a request to send evaluation information to the sending unit 106 .

The rule memory 28, history memory 124, and evaluation memory 122 may be composed of three memories, as shown in FIG. 1, or may be composed of one memory. When configured from one memory, the area of one memory may be divided into three areas, and rule information, execution history information, and evaluation information may be stored in each of the divided areas. When configured from three memories, it may be configured from three independent memory devices, or may be configured from three memories used as one memory device.

Although it has been described that the edge computer 6 creates the rule information, the cloud server 2 instead of the edge computer 6 may create the rule information. Furthermore, not the edge computer 6 or the cloud server 2, but another electronic device (for example, a personal computer or another edge computer) connected to the edge computer 6 via the network 18 creates the rule information and transmits the rule information. It may also be configured to be managed. The edge computer 6 has a function of creating rule information and transmitting the created rule information to the cloud server 2, and a function of downloading the rule information and using the rule information. However, other electronic devices may have the function of creating rule information but may not have the function of using it, that is, they may not have a rule engine. The process of creating rule information on another electronic device is similar to the process of creating rule information on the edge computer 6, so in this specification, the operation of creating rule information on the edge computer 6 will be described.

Although the above explanation assumes that the rule creator and the rule user are different people, the rule creator and the rule user may be the same person. In this case, the rule information created by the edge computer 6 does not need to be registered in the cloud server 2. However, similarly to the above explanation, the rule information may be transmitted from the edge computer 6 to the cloud server 2, registered in the cloud server 2, and then downloaded from the cloud server 2 to the edge computer 6.

Although the rule information stored in the rule memory 28 is automatically used in principle, a large amount of rule information is stored in the rule memory 28, and there are cases where it is not necessary to use all the rule information all the time. For example, you may not want to use specific rule information at night. Based on a user's instruction from the input device 102, the rule management unit 132 may select the rule information to be used from among the large number of pieces of rule information stored in the rule memory 28 as valid rule information. Invalid rule information is not used. The user is not limited to selecting valid/invalid, but when validating, the user can also specify the period/time zone etc. to be valid. Columns such as validity/invalidity of the rule, valid period/time zone, etc. may be added to the rule information in the data structure shown in FIG. 2.

FIG. 5 shows an example of the data structure of execution history information. The execution history information includes multiple items. Examples of items of execution history information include, but are not limited to, execution date and time, rule ID, user attributes, usage device ID, usage location ID, and the like. The execution date and time indicates the execution start date and time of the process described in the THEN section in the rule information. One line of data in the execution history information corresponds to one process execution.

The user attribute indicates the attribute of the user who uses the rule, and consists of a plurality of items. Examples of user attribute items include, but are not limited to, user ID, name, date of birth, gender, nationality, address, occupation, and the like. These items can be set at the time of user registration on the edge computer 6. User attributes can be used in the rule recommendation process described below. User attributes can also be used as keywords in searching for rule information.

The usage device ID identifies the edge computer 6 that executes a specific process based on the rule information, and can be obtained when the edge computer 6 logs in. The usage location ID identifies the location of the edge computer 6 that executes a specific process. If the edge computer 6 is equipped with a GPS function, such as a smartphone, the usage location ID can be obtained from the GPS function. If the edge computer 6 does not have a GPS function, the usage location ID is obtained from the installation location information set at the time of initial setting of the edge computer 6. Since the execution history information shown in FIG. 5 is created by one edge computer 6, the user ID (also the user attribute) and the used device ID indicate the same user and the same used device, respectively. The usage device ID and the usage location ID can also be used in the rule recommendation process described later, and can also be used as keywords in the search for rule information.

When a large amount of execution history information is transmitted from a large number of edge computers 6 to the cloud server 2, a large amount of execution history information with different user IDs and different usage device IDs is accumulated in the server memory 38 of the cloud server 2. When the user attribute, usage device ID, and usage location ID are specified by the user when the cloud server 2 displays a ranking table, it becomes possible to display a ranking table narrowed down based on the specified items. Alternatively, when a user wants to search for rule information held by a rule publication site, the user attribute, usage device ID, and usage location ID can be used as search keywords.

Users can input comments and evaluations of the rule information they have used. The comments and evaluations may be rule comments and rule evaluations regarding the entire rule information, IF module comments and IF evaluations regarding the IF module 8A, and THEN module comments and TNEN module evaluations regarding the THEN module 8B. An example of a rule comment is "This rule realizes a good solution to the problem XX." An example of an IF module comment is "This IF module has high accuracy." An example of a THEN module comment is "This THEN module has a long life." The evaluation is a numerical value, for example, the maximum value is 5.0 and can be set in units of 0.1. The higher the evaluation, the larger the value. Note that inputting either the comment or the evaluation may be omitted.

The evaluation management unit 116 creates evaluation information having the data structure shown in FIG. The evaluation information consists of multiple items. Items of evaluation information include, but are not limited to, for example, rule ID, user ID, rule comment, rule evaluation, IF module comment, IF module evaluation, THEN module comment, THEN module evaluation, and the like. Comments are text and ratings are numerical values. Rule comments, rule evaluations, IF module comments, IF module evaluations, THEN module comments, THEN module evaluations, etc. are created by the evaluation management unit 116 based on input from the user via the input device 102. Note that the rule evaluation, IF module evaluation, THEN module evaluation, etc. may not be input by the user, but the evaluation may be determined by AI analyzing the characters included in the rule comment, IF module comment, and THEN module comment. .

Since the evaluation information shown in FIG. 6 is created by one edge computer 6, the user IDs indicate the same user. Each item of evaluation information can be used in the rule recommendation process described later. Each item of evaluation information can also be used as a keyword in a search for rule information.

The evaluation management unit 116 transmits the evaluation information stored in the evaluation memory 122 to the cloud server 2 via the transmission unit 106. The evaluation management unit 116 may transmit the evaluation information to the cloud server 2 when instructed to do so by the user, or may transmit a certain number of evaluation information each time a certain number of evaluation information is stored in the evaluation memory 122. It may be transmitted to the cloud server 2, or the evaluation information stored in the evaluation memory 122 may be transmitted to the cloud server 2 at regular intervals. Note that if the user is the same user, the evaluation information may be input using various devices, and the evaluation information may be transmitted to the cloud server 2. For example, if the edge computer 6 is a smartphone, evaluation information input using another device (for example, a personal computer) may be transmitted to the cloud server 2.

When a large number of pieces of evaluation information are transmitted from a large number of edge computers 6 to the cloud server 2, evaluation information about the same rule by different users is accumulated in the cloud server 2. Rule creators can view evaluation information of the rule information they created.

(Cloud server)
FIG. 7 shows an example of the configuration of the cloud server 2 in the IoT system.

The cloud server 2 includes a first receiving section 202, a rule writing section 204, a history writing section 206, an evaluation writing section 208, a ranking processing section 210, a server memory 38, a second receiving section 232, a request determination section 234, and a rule selection section 236. , a rule list screen creation section 238, and a transmission section 242.

The server memory 38 includes a rule memory 222, a history memory 224, an evaluation memory 226, and a ranking memory 228.

Rule memory 222 stores rule information. History memory 224 stores execution history information. Evaluation memory 226 stores evaluation information. Ranking memory 228 stores ranking information. The ranking information includes first usage frequency ranking information, second usage frequency ranking information, and third usage frequency ranking information. The first usage frequency ranking information, the second usage frequency ranking information, and the third usage frequency ranking information will be described later. The first receiving unit 202 receives rule information, execution history information, and evaluation information from all edge computers 6 connectable to the cloud server 2.

The operations of the cloud server 2 include operations at the time of rule registration and operations at the time of rule distribution. Rule registration includes receiving rule information created by all the edge computers 6 and transmitted from the edge computers 6 to the cloud server 2, and storing it in the rule memory 222. When the cloud server 2 rather than the edge computer 6 creates the rule information, rule registration includes writing the rule information created by the cloud server 2 into the rule memory 222. Rule registration is executed according to instructions from the edge computer 6.

The rule writing unit 204 writes the rule information from all the edge computers 6 received by the first receiving unit 202 into the rule memory 222. When the rule writing unit 204 receives the rule information, it may transfer the rule information to a certification authority (not shown) and request authentication. When the conditions described in the IF section are satisfied, the certification authority determines whether the THEN module described in the THEN section can correctly execute the process. The rule writing unit 204 may write rule information that has been certified by a certification authority into the rule memory 222.

The history writing unit 206 writes the execution history information from all the edge computers 6 received by the first receiving unit 202 into the history memory 224. The evaluation writing unit 208 writes the evaluation information from all the edge computers 6 received by the first receiving unit 202 into the evaluation memory 226.

The ranking processing unit 210 aggregates the execution date and time information in the execution history information stored in the history memory 224 for each rule, calculates the number of uses for each rule, and writes the usage number ranking information into the ranking memory 228. The ranking processing unit 210 aggregates the evaluation information stored in the evaluation memory 226 for each rule, calculates an overall evaluation for each rule, and writes the overall evaluation ranking information into the ranking memory 228. An example of aggregation includes calculating an average value. Details of the ranking processing section 210 will be described later.

When the rule memory 222, history memory 224, evaluation memory 226, and ranking memory 228 are configured from one memory, one memory area is divided into four areas, and each divided area stores rule information, execution history information, evaluation information, and Ranking information may also be stored. However, the rule memory 222, history memory 224, evaluation memory 226, and ranking memory 228 may be composed of four memories. When configured from four memories, it may be configured from four independent memories. Rule memory 222, history memory 224, evaluation memory 226, and ranking memory 228 may be composed of two or more memories used as one memory.

The second receiving unit 232 receives the request signal from the edge computer 6. The request signal is a display request signal requesting display of a rule list screen, or a download request signal requesting downloading of the selected rule information. The download request signal includes information indicating that a download of the rule information is requested and information specifying the rule information to be downloaded.

If the request signal received by the second receiving unit 232 is a display request signal, the request determination unit 234 transmits the request signal to the rule list screen creation unit 238, and if the request signal is a download request signal, the request signal is used for rule selection. 236.

When the rule list screen creation unit 238 receives the display request signal from the request determination unit 234, it reads ranking information based on the recommendation level information specified in the request signal from the ranking memory 228, and creates a ranking table based on the ranking information on the rule list screen. , and sends the rule list screen information to the transmitter 242. That is, the ranking processing unit 210 and the rule list screen creation unit 238 cooperate to generate a display screen that displays at least one rule information among the plurality of rule information based on the recommendation level information. Therefore, the ranking processing section 210 and the rule list screen creation section 238 may be referred to as a display control section. Note that the display control unit may also include the server memory 38.

When the rule selection unit 236 receives the download request signal from the request determination unit 234 , it reads the rule information to be downloaded from the rule memory 222 and sends the rule information to the transmission unit 242 .

The transmitter 242 transmits the rule list screen information or the rule information to the edge computer 6 that is the source of the request signal.

As a result, the rule list screen is displayed on the display device 104 of the edge computer 6 that requested the display of the rule list screen. Thereafter, when at least one piece of rule information in the rule list screen is selected, the selected rule information is downloaded to the edge computer 6.

Note that the division of functions between the edge computer 6 and the cloud server 2 is not limited to the examples shown in FIGS. 1 and 7. At least a part of the functions of the edge computer 6 shown in FIG. 1 may be realized by the cloud server 2. At least a part of the functions of the cloud server 2 shown in FIG. 7 may be realized by the edge computer 6. Furthermore, a single electronic device may be provided that includes both functions. For example, a configuration corresponding to the microservices 10A, 10B, application 20, rule memory 28, transmitter 106, receiver 108, evaluation memory 122, and history memory 124 in FIG. 1 may be implemented in the cloud server 2. In this case, on the cloud server 2 side, whether the state detected by the IF module 8A matches the specific state described in the IF part of any rule information among the valid rule information stored in the rule memory 28? If they match, a process is performed in which an execution instruction signal for causing the THEN module 8B to execute the process described in the THEN section of the rule information is sent to the microservice 10B corresponding to the THEN module 8B.

(Rule list display)
The ranking processing unit 210 calculates recommendation degree information for each rule information and writes it into the ranking memory 228. The ranking processing unit 210 creates ranking information by arranging a plurality of pieces of rule information in descending order of their values based on recommendation degree information.

At the aggregation timing, the ranking processing unit 210 aggregates the execution history information from all the edge computers 6 stored in the history memory 224 for each rule ID, and calculates the cumulative number of uses for each rule information and the number of uses within a certain period of time. Calculate the number of uses. The aggregation timing may be every time execution history information is written to the history memory 224, or every fixed period.

The ranking processing unit 210 associates the rule ID, the cumulative number of uses, and the number of uses within a certain period, arranges the plurality of rule information in descending order of the number of uses, calculates first usage number ranking information, and calculates the first usage number ranking. Write the information to ranking memory 228. Alternatively, the aggregation timing may be when ranking information is requested. That is, the ranking processing unit 210 may calculate the ranking information in advance and calculate the ranking information when requested, without writing it into the ranking memory 228.

FIG. 8 shows an example of first usage frequency ranking information. In the first use frequency ranking information, a plurality of pieces of rule information are arranged in descending order of the total number of uses, but may be arranged in order of the largest number of uses within a certain period. Note that the ranking processing unit 210 does not need to rearrange the plural pieces of rule information in the order of the number of uses, just by associating the rule ID, the total number of uses, and the number of uses within a certain period of time. When the rule list screen creation unit 238 creates the list screen, the list screen may be created after rearranging the plural pieces of rule information in the ranking information read from the ranking memory 228 in descending order of usage frequency.

When a request to display the first rule list screen regarding the number of uses is sent from the edge computer 6 to the cloud server 2, the rule list screen creation unit 238 generates the first use number ranking information shown in FIG. 8 from the ranking memory 228, for example. A first usage ranking table signal is created based on the first usage ranking information, and the first usage ranking table signal is sent to the edge computer 6 as a rule list screen signal.

As a result, the display device 104 of the edge computer 6 displays, for example, the first usage frequency ranking table shown in FIG. In the first usage frequency ranking table, multiple pieces of rule information (each rule information consists of a rule name and the number of usages) are arranged in descending order of the total number of usages, but they are arranged in descending order of the number of usages within a certain period of time. You can. Whether to display a ranking table of the total number of uses or a ranking table of the number of uses within a certain period can be specified by a display request for the first rule list screen transmitted from the edge computer 6.

The ranking processing unit 210 may calculate not only the number of uses for each rule information, but also the number of uses for each user. The user knows the number of uses for all users from the first usage frequency ranking table shown in FIG. 9, but does not know the number of uses for a specific user. If a user can know the rule information that has been used many times by users who provide services similar to the service he or she wants to provide, he or she can easily or quickly select rule information. In order to calculate the number of usages for a specific user, the ranking processing unit 210 aggregates the execution history information stored in the history memory 224 for each combination of rule ID and user ID at the aggregation timing. The cumulative number of uses and the number of uses within a certain period are calculated for each combination of ID and user ID.

The ranking processing unit 210 obtains second usage frequency ranking information that associates the rule ID, the user ID, the cumulative usage frequency, and the usage frequency within a certain period of time, and writes the second usage frequency ranking information into the ranking memory 228.

FIG. 10 shows an example of the second usage frequency ranking information. The edge computer 6 can display a second usage frequency ranking table for a specific user based on the second usage frequency ranking information. The second usage frequency ranking table is substantially the same as the first usage frequency ranking table shown in FIG. 9, except that the usage frequency is the usage frequency for a specific user. The order of the rule information in the second usage frequency ranking table may be in order of the highest cumulative number of usages or in order of the highest number of usages within a certain period of time. Whether to display a ranking table of the cumulative number of uses or a ranking table of the number of uses within a certain period for which user ID is to be displayed can be specified by a request to display the rule list screen sent from the edge computer 6. be.

Furthermore, the ranking processing unit 210 may calculate the number of uses for each rule attribute item (target person, scene, theme, and task). A rule creator can set a rule attribute that indicates what kind of service the rule information provides. Even if the rule information is the same, the effects may vary depending on the rule attribute items and the usage situation. In order to find rule information suitable for a service desired to be provided by an IoT system, it is useful to specify a rule attribute item and find rule information that is used most often for that item.

In order to calculate the number of uses for the rule attribute item, the ranking processing unit 210 aggregates the execution history information stored in the history memory 224 for each combination of rule ID and rule attribute item at the aggregation timing. Then, the cumulative number of uses and the number of uses within a certain period are calculated for each combination of rule ID and rule attribute. The ranking processing unit 210 calculates third usage frequency ranking information and writes the third usage frequency ranking information into the ranking memory 228. The third usage frequency ranking information includes information that associates a rule ID with the cumulative number of uses, information that associates each rule attribute item with the cumulative number of uses, and rule ID and the number of uses within a certain period of time. and information that associates each item of the rule attribute with the number of uses within a certain period of time.

FIG. 11 shows an example of the third usage frequency ranking information. Note that the rule attribute items do not need to include all of the target person, scene, theme, and task, and may include at least one of these.

The edge computer 6 can display a third usage frequency ranking table shown in FIG. 12 based on the third usage frequency ranking information shown in FIG. 11. In the usage frequency ranking table shown in FIG. 12, a scene is selected as a rule attribute item, and multiple pieces of rule information (each rule information consists of a rule name, usage frequency, and other items of rule attributes) are displayed for a specific scene ID. Although the scenes are arranged in descending order of the cumulative number of times they have been used, they may be arranged in descending order of the number of times they have been used within a certain period of time. Furthermore, items other than scenes may be selected as rule attribute items. Furthermore, a plurality of items of rule attributes may be selected and the number of uses for a combination of the plurality of items may be calculated. The list of rules sent from the edge computer 6 determines whether to display a ranking table of the cumulative number of uses or a ranking table of the number of uses within a certain period for which ID of which item (or items may be plural) of the rule attributes. It can be specified in the screen display request.

When a target person, theme, or task is clicked in the display area of each rule information of the usage frequency ranking table shown in FIG. 12, the usage frequency ranking table for a specific scene is It will be changed to a ranking table of the number of times the assignment has been used.

Also in the third usage frequency ranking information shown in FIG. 11, like the second usage frequency ranking information shown in FIG. may be calculated.

Another example of the recommendation degree information calculated by the ranking processing unit 210 is recommendation degree information regarding evaluation. The evaluation includes rule evaluation, IF module evaluation, and THEN module evaluation. As shown in FIG. 6, the rule evaluation, IF module evaluation, and THEN module evaluation are included in the evaluation information.

At the aggregation timing, the ranking processing unit 210 aggregates the rule evaluation, IF module evaluation, and THEN module evaluation of the evaluation information stored in the evaluation memory 226 for each rule ID, and calculates the rule evaluation aggregate value for each rule information, Calculate the IF module evaluation total value and THEN module evaluation total value. The aggregate value includes an average value of evaluations, a pair of maximum and minimum evaluation values, and the like. The aggregation timing may be every time the evaluation information is written to the evaluation memory 226, or every fixed period.

The ranking processing unit 210 calculates evaluation ranking information that associates the rule ID, the rule evaluation aggregate value, the IF module evaluation aggregate value, and the THEN module evaluation aggregate value, and writes the evaluation ranking information into the ranking memory 228. FIG. 13 shows an example of evaluation ranking information. Note that the evaluation aggregate value does not need to include all of the rule evaluation aggregate value, IF module evaluation aggregate value, and THEN module evaluation aggregate value, and may include at least one of these. In the evaluation ranking information shown in FIG. 13, the rule IDs are arranged in descending order of rule evaluation aggregate value, but they may also be arranged in descending order of IF module evaluation aggregate value or THEN module evaluation aggregate value.

The edge computer 6 can display the rule evaluation ranking table shown in FIG. 14 based on the evaluation ranking information shown in FIG. 13. In the rule evaluation ranking table shown in FIG. 14, a plurality of pieces of rule information (each rule information consists of a rule name, a rule evaluation aggregate value, an IF module evaluation aggregate value, and a THEN module evaluation aggregate value) are arranged in descending order of rule evaluation aggregate value. Although they are arranged in order, they may be arranged in descending order of the IF module evaluation total value or the THEN module evaluation total value. Which of the ranking tables of rule evaluation, IF module evaluation, and THEN module evaluation in descending order is to be displayed can be specified by a rule list screen display request sent from the edge computer 6.

When the IF module evaluation aggregate value or THEN module evaluation aggregate value is clicked in the display area of each rule information of the ranking table shown in FIG. 14, the rule evaluation ranking table displays the clicked IF module evaluation aggregate value or THEN module evaluation Changed to a ranking table based on aggregated values.

In the evaluation ranking information shown in FIG. 13, the number of uses may be calculated for each combination of rule ID, user ID, and evaluation aggregate value, including the user ID, as in the second usage frequency ranking information shown in FIG. 10. good.

Note that the evaluation may include comments (rule comments, IF module comments, THEN module comments) included in the evaluation information. In this case, the ranking processing unit 210 is capable of executing natural language processing using morphological analysis, syntactic analysis, semantic analysis, and context analysis. The ranking processing unit 210 performs natural language processing on a comment made of text and converts the text into a comment value indicating the content of the comment. The ranking processing unit 210 totalizes the comment values for each rule ID and calculates the comment total value of the rule information. The ranking processing unit 210 may calculate second evaluation ranking information that associates the rule ID, the total evaluation value, and the total comment value.

In the above description, the ranking processing unit 210 calculates ranking information in which rule information is arranged in advance regarding specific recommendation level information, writes the ranking information in the ranking memory 228, and receives a rule list display request from the edge computer 6. Then, ranking information is read from the ranking memory 228. However, in the ranking information stored in the ranking memory 228, the rule IDs do not need to be arranged in descending order of the value of the recommendation degree information. The ranking processing unit 210 may write into the ranking memory 228 ranking information that only associates rule IDs with recommendation degree information. The rule list screen creation unit 238 may create the list screen after rearranging the rule IDs in the ranking information read from the ranking memory 228 in descending order of the recommendation level information.

Furthermore, instead of or in addition to the above information, the ranking processing unit 210 calculates the cumulative number of uses, the number of uses within a certain period, or the evaluation aggregate value for each combination of the device ID, the location ID, and the rule. may be calculated.

For example, the rule creator ID may be added to the usage count ranking information shown in FIG. 8, FIG. 10, or FIG. 11. For example, when the rule creator ID is added to the first usage frequency ranking information shown in FIG. 8, a usage frequency ranking table shown in FIG. 15 may be displayed. The usage count ranking table shown in FIG. 15 differs from the ranking table shown in FIG. 9 in that the rule creator is displayed in the display area of each rule information.

In the ranking table shown in FIG. 15, similar to the ranking table shown in FIG. 9, rule information is arranged in descending order of usage frequency, regardless of who created the rule. When a rule creator is clicked in the display area of each rule information of the ranking table shown in FIG. 15, the ranking table displays information about the usage of the rule information created by the specific creator clicked, for example, as shown in FIG. 16. Changed to frequency ranking table. Therefore, by clicking on the rule creator of rule information that has been used frequently, a ranking table of the number of uses of rule information created by the creator of rule information that has been used many times can be displayed. Since it is considered safe to select rule information created by a rule creator who has used it many times, for example, as shown in FIG. 16, a ranking table of the number of uses of rule information created by a specific rule creator is displayed. This is useful for selecting rule information.

Note that the same effect can be obtained by adding the rule creator ID to the evaluation ranking information shown in FIG. 13.

Further, the same effect can be obtained by adding the IF module ID and THEN module ID to the ranking information instead of the rule creator ID. For example, when the IF module ID and THEN module ID are added to the usage count ranking information shown in FIG. 8, the rule evaluation ranking table shown in FIG. 17, for example, is displayed. The ranking table shown in FIG. 17 differs in that the IF module evaluation total value of each rule information in the rule evaluation ranking table shown in FIG. 14 is changed to the IF module ID, and the THEN module evaluation total value is changed to the THEN module ID. Note that instead of adding both the IF module ID and the THEN module ID to the ranking information, only one of the IF module ID and the THEN module ID may be added.

In the ranking table shown in FIG. 17, similar to the ranking table shown in FIG. 14, a plurality of pieces of rule information are arranged in descending order of usage frequency, regardless of the IF module or THEN module. When the IF module ID or THEN module ID is clicked in the display area of each rule information of the ranking table shown in FIG. 17, the ranking table displays the rules that use the clicked IF module or THEN module, as shown in FIG. Changed to a usage ranking table with limited information. Therefore, it is possible to display a usage frequency ranking table of rule information that uses the IF module or THEN module that is used frequently. Since it is considered safe to select rule information that uses an IF module or THEN module that is used frequently, displaying the usage frequency ranking table shown in FIG. 18 is useful for selecting rule information.

A similar effect can be obtained by adding the IF module ID and THEN module ID to the evaluation ranking information instead of adding them to the start-of-use ranking information.

As described above, the embodiment includes a display control unit that generates a display screen that presents rule information that is ultimately recommended to the user based on recommendation level information. The display control unit only needs to generate the final display screen based on the recommendation level information, and there is no limitation on the display screen and the process for generating it. The final display screen is not limited to the above-mentioned usage frequency ranking table and evaluation ranking table, but there is no limit to its form as long as it displays rule information recommended to the user, and the ranking table can be modified in various ways. be. Furthermore, the process of generating a display screen from the recommendation level information is not limited to the process of reading ranking information based on the recommendation level information from the ranking memory 228 and creating a ranking table based on the ranking information as a rule list screen, as described above. , the ranking table may be directly obtained from the recommendation information.

A modified example of the recommendation level information will be explained.

In the above description, recommendation information regarding the number of uses and evaluation was used, but recommendation information regarding creation date and time may also be used. That is, a rule list screen may be displayed in which rules are arranged in order of creation date and time. In this case, it is unnecessary to provide the ranking processing unit 210 and the ranking memory 228 in the cloud server 2. The rule list screen creation unit 238 may read rule information from the rule memory 222 in order of creation date and time, and generate a list screen.

The edge computer 6 also manages the IDs of the IF modules and THEN modules it owns. The edge computer 6 may, for example, transmit these IDs to the cloud server 2 together with a rule list display request. The cloud server 2 searches for rule information that uses the IF module and THEN module owned by the user from the rule information stored in the rule memory 222, and generates a rule list screen consisting of the searched rule information. Can be done. That is, rule information that can be used only with the IF module and THEN module that the user currently owns can be recommended to the user. Users can create IoT systems without purchasing new modules.

If the execution history information includes execution date and time and usage location ID, the cloud server 2 analyzes these and determines what month, day, and time this rule information is often used, or the rule information. You can find out where it is often used. If this knowledge is used to create a list of rules, it is possible to recommend more efficient rule information. That is, the cloud server 2 converts rule information that is often used in the transmission date and time of the request signal for rule list screen display or rule information that is often used in the transmission location of the request signal for rule list screen display into execution history information. can be extracted based on. Alternatively, when the edge computer 6 specifies the date and time of use or the place of use when transmitting the request signal for displaying the rule list screen, the cloud server 2 sends the rules that are often used at the specified date and time or at the specified place. You can create an information list screen.

The user can also send a search request for rule information from the rule acquisition unit 114 of the edge computer 6 to the rule publication site. The search request may be sent while the rule list screen is displayed, or may be sent regardless of the rule list screen.

(rule creation)
FIG. 19 is a flowchart showing an example of rule creation processing by the rule creation unit 112 of the edge computer 12. Here, it is assumed that the edge computer 12 is a smartphone. 20 to 22 show examples of screen transitions on the display device 104 of the edge computer 12 during rule creation.

The rule creation unit 112 displays a rule creation menu on the display device 104 in step S104. An example of the rule creation menu is shown in FIG. 20(a). The rule creation menu includes a rule ID field 302, an IF button 306, and a THEN button 308. In the rule ID column 302, a tens of alphanumeric characters that are the identification number of the edge computer 12 are input. The identification number may be automatically generated.

When the rule creator selects the IF button 306, the rule creator 112 displays the IF module selection screen shown in FIG. 20(b) in step S106, and performs the IF module setting process. The selection screen is a list of IF module icons and names, and the list can be scrolled up and down. IF modules may be grouped by function or type. The order of the names may be in the order of "Aiueo" or in the order of the number of times they have been used.

When the rule creator selects one of the IF module icons, the rule creator 112 displays the IF module condition setting screen shown in FIG. 20(c). Here, an example will be described in which a "button" is selected as the IF module. The condition setting screen includes condition options and a "proceed" button 312. When "when a button is pressed" is selected as the condition, single click, double click, and long click are further displayed as IF parameter options. When the IF parameter is selected, an IF cycle option is also displayed (not shown), and the IF cycle is also set.

When the rule creator selects the "proceed" button 312, the rule creator 112 displays the IF section condition setting completion screen shown in FIG. 21(a). The end screen includes a rule ID field 302, an IF button 306, a THEN button 308, and an icon 314 of the selected IF module.

For example, there are cases where it is desired to include multiple conditions such as "temperature is 25 degrees or higher" and "humidity is 80% or higher" in one piece of rule information. In this case, the rule creator selects the IF button 306 on the end screen. When the IF button 306 is selected, the above-described IF section setting process is executed again, and a plurality of conditions are set in one piece of rule information. Note that the plurality of conditions may be an AND condition or an OR condition. When the IF unit setting process is executed again, the option of whether the plurality of conditions are AND conditions or OR conditions is also set. If the plurality of conditions are AND conditions, the process described in the THEN section will not be executed unless all of the plurality of conditions are satisfied. When the plurality of conditions are OR conditions, if any one of the plurality of conditions is satisfied, the process described in the THEN section is executed.

When the rule creator selects the THEN button 308 on the IF section setting end screen, the rule creation section 112 displays the THEN module selection screen shown in FIG. 21(b) in step S108, and executes the THEN section setting process. I do. The selection screen is a list of THEN module icons and names, and the list can be scrolled up and down. THEN modules may be grouped by function/type. The order of the names may be in the order of "Aiueo" or in the order of the number of times they have been used.

When the rule creator selects any THEN module, the rule creator 112 displays a process setting screen for the THEN module shown in FIG. 21(c). Here, an example will be described in which an LED is selected as the THEN module. The processing setting screen includes processing options and a "proceed" button 316. When "shining" is selected as the process, a lighting pattern such as "flashing every 100 ms" is further displayed as a THEN parameter option.

When the rule creator selects the "proceed" button 316, the rule creator 112 displays the THEN section setting completion screen shown in FIG. 22(a). The setting end screen includes a rule ID field 302, an IF button 306, a THEN button 308, an IF module icon 314, a THEN module icon 318, and a "proceed" button 322.

Similar to the condition setting process, there are cases where it is desired to include multiple processes such as "notify the user by vibration" and "notify the user by email" in one rule information. In this case, the rule creator selects THEN button 308 on the end screen. When the THEN button 308 is selected, the setting process of the THEN section described above is executed again, and a plurality of processes are set in one rule information. Note that the plurality of processes may be an AND process or an OR process. When the THEN section setting process is executed again, the option of whether the plurality of processes is AND processing or OR processing is also set.

When the rule creator selects the "proceed" button 322 on the THEN section setting end screen, the rule creation section 112 displays the rule attribute and editability flag setting screen shown in FIG. 22(b) in step S112. , performs setting processing of rule attributes and editability flags. The setting screen includes options for rule attributes and options for editability flags.

When these options are selected, the rule creation unit 112 displays a transmission confirmation screen shown in FIG. 22(c). The transmission confirmation screen includes the contents of the set rule and a transmission button 326. The user can enter a rule name on this screen.

When the rule creator selects the send button 326, the rule creator 112 sends the rule information to the transmitter 106 in step S114. The transmitter 106 transmits the rule information to the cloud server 2 at a predetermined timing.

In this way, the cloud server 2 stores a lot of rule information transmitted from each edge computer 6 in the rule memory 222.

(Rule download)
When using rules, the user first downloads desired rule information from the cloud server 2 to the edge computer 6. FIG. 23 is a sequence chart showing an example of the process flow of the edge computer 6 and cloud server 2 regarding downloading of rule information.

In the edge computer 6, the rule acquisition unit 114 accesses the rule distribution site of the cloud server 2 in step S122, and transmits a display request signal requesting display of the rule list screen to the cloud server 2 via the transmission unit 106. . The display request signal specifies which recommendation information is requested for ranking.

In the cloud server 2, upon receiving the display request signal, the rule list screen creation unit 238 reads ranking information related to the specified recommendation level information from the ranking memory 228 in step S142, and creates the rule list screen based on the read ranking information. A signal is generated and a rule list screen signal is transmitted to the edge computer 6 via the transmitter 242.

In the edge computer 6, when the receiving unit 108 receives the rule list screen signal, the rule acquisition unit 114 generates the ranking table shown in FIG. 9, FIG. 12, FIG. 14, or FIG. 15 based on the rule list screen signal in step S124. It is displayed on the display device 104.

The user selects desired rule information from the ranking table. The user may scroll the screen to view the ranking table. However, if rule information cannot be selected from the ranking table, the user can request that the displayed ranking table be changed to a different type of ranking table. The rule acquisition unit 114 may execute step S122 again based on an instruction from the user and transmit a display request signal specifying other recommendation level information to the cloud server 2. For example, it is possible to change from a usage frequency ranking table to an evaluation ranking table, or vice versa. Furthermore, even if the ranking table is related to the same recommendation level information, it is also possible to change the ranking table to a narrowed-down ranking table for a specific user, specific rule creator, specific rule attribute, specific IF module, or THEN module. In this case as well, the rule acquisition unit 114 may execute step S122 again based on an instruction from the user and transmit a request signal to narrow down the ranking table to the cloud server 2.

When the user selects a rule from the ranking table, the rule acquisition unit 114 transmits a download request signal for the selected rule information to the cloud server 2 via the transmission unit 106 in step S126.

In the cloud server 2, upon receiving the download request signal, the rule selection unit 236 reads the requested rule information from the rule memory 222 and transmits the rule information to the edge computer 6 via the transmission unit 242 in step S144.

In the edge computer 6, upon receiving the rule information, the rule management unit 132 writes the rule information into the rule memory 28 in step S128.

(Using rules)
FIG. 24 is a flowchart showing an example of a process in which the rule engine 26 of the edge computer 12 uses rules. In step S152, the rule management unit 132 reads the rule information stored in the rule memory 28, and sends the read rule information to the status monitor 134 and the process starting unit 136. If valid/invalid or a valid period is set in the rule information, the rule management unit 132 reads only the currently valid rule information. Here, it is assumed that a plurality of IF modules 8A and THEN modules 8B are prepared. It is also assumed that a plurality of microservices 10A corresponding to the plurality of IF modules 8A and a plurality of microservices 10B corresponding to the plurality of THEN modules 8B are also prepared.

In step S154, the status monitor 134 causes the microservice 10A corresponding to the IF module ID specified in the rule information transmitted from the rule management unit 132 to detect the status of the IF module 8A at regular intervals in the IF cycle. Send a detection request signal. The microservice 10A periodically transmits a state detection request signal to the corresponding IF module 8A, and causes the IF module 8A to detect the state. The IF module 8A detects the state according to the request signal and sends the state detection signal to the microservice 10A.

In step S156, the status monitor 134 receives the status detection signal of the IF module 8A transmitted from the microservices 10a to 10i.

In step S158, the state monitor 134 determines whether the state detected by the IF module 8A satisfies the conditions (conditions that also take into account the IF parameters) described in the IF section of any of the rule information. If the status monitor 134 determines that the status does not satisfy the conditions, it executes the process of step S154 again.

When the state monitor 134 determines that the state satisfies the conditions, it sends the rule information to the rule ID of the rule information.

Upon receiving the rule ID, the process starting unit 136 sends a control signal to the microservice 10B corresponding to the THEN module ID specified in the rule information of the rule ID to execute the process specified in the rule information in step S160. and sends the rule ID to the execution history management section 118. The microservice 10B drives the THEN module 8B to execute the processing specified in the rule information.

Upon receiving the rule ID, the execution history management unit 118 creates execution history information and writes the execution history information into the history memory 124 in step S162.

The execution history management unit 118 transmits the execution history information to the cloud server 2 in step S164.

At an arbitrary timing after the THEN module 8B executes the process (step S166), the evaluation management unit 116 displays a rule comment/evaluation input screen. The user follows the screen and enters comments and evaluations of the rule used. As a result, evaluation information is created.

The evaluation management unit 116 transmits the evaluation information to the cloud server 2 in step S168.

Note that the execution timings of the execution history information transmission step S164 and the evaluation information transmission step S170 may be other timings.

It should be noted that the present invention is not limited to the above-described embodiments as they are, but can be implemented by modifying the constituent elements within the scope of the invention at the implementation stage. Moreover, various inventions can be formed by appropriately combining the plurality of components disclosed in the above embodiments. For example, some components may be deleted from all the components shown in the embodiments. Furthermore, components from different embodiments may be combined as appropriate.

2... Cloud server, 6... Edge computer, 8A... IF module, 8B... THEN module, 10a, 10B... microservice, 18... network, 26... rule engine, 28... rule memory, 204... rule writing unit, 206... history Writing section, 208... Evaluation writing section, 210... Ranking processing section, 222... Rule memory, 224... History memory, 226... Evaluation memory, 228... Ranking memory, 236... Rule selection section, 238... Rule list screen creation section.

Claims (7)

Electronic devices connected to multiple sensors and multiple processing modules are
When the sense result of at least one sensor among the plurality of sensors is a specific result, at least one processing module among the plurality of processing modules is associated with the sense result to perform a coordinated operation. a storage unit that stores multiple pieces of rule information;
a display control unit that generates a display screen that displays rule identification information included in the plurality of rule information,
Each of the plurality of rule information is
Identification information of the creator of the rule information,
including attribute information of the rule information,
The attribute information is
first identification information indicating a scene in which the service provided by the rule information is used;
second identification information indicating a theme of the service provided by the rule information;
at least third identification information indicating a problem to be solved by the service provided by the rule information;
electronic equipment. The electronic device according to claim 1, wherein the sensor and/or the processing module are connected to a microservice via a network. The electronic device according to claim 1, wherein the rule information is downloaded from a rule publication site and stored in a storage unit. 4. The electronic device according to claim 3, further comprising means for accessing said rule publication site, viewing rules published on a rule list screen, and selecting said rule information. further including a rule creation section for creating the rule information,
The rule creation unit stores the following information in the storage unit:
first and second storage areas that specify identification information of a sensor (IF module) and identification information of a processing module (THEN module) in correspondence with one rule identification information;
including third and fourth storage areas that describe sensing contents of the sensor (IF module) and processing contents of the processing module (THEN module);
The electronic device according to claim 1. An electronic device system with multiple sensors, multiple processing modules, and connected to the Internet,
When the sense result of at least one sensor among the plurality of sensors is a specific result, at least one processing module among the plurality of processing modules is associated with the sense result to perform a coordinated operation. a storage unit that stores multiple pieces of rule information;
a display control unit that generates a display screen that displays rule identification information included in the plurality of rule information,
Each of the plurality of rule information is
Identification information of the creator of the rule information,
including attribute information of the rule information,
The attribute information is
first identification information indicating a scene in which the service provided by the rule information is used;
second identification information indicating a theme of the service provided by the rule information;
at least third identification information indicating a problem to be solved by the service provided by the rule information,
the sensor and/or the processing module is connected to the internet via a microservice;
Electronic equipment system. A method for controlling an electronic device connected to multiple sensors and multiple processing modules is
When the sense result of at least one sensor among the plurality of sensors is a specific result, at least one processing module among the plurality of processing modules is associated with the sense result to perform a coordinated operation. Store multiple pieces of rule information in the storage unit,
A display control unit that displays rule identification information included in the plurality of rule information generates a display screen,
Each of the plurality of rule information is
Identification information of the creator of the rule information,
including attribute information of the rule information,
The attribute information is
first identification information indicating a scene in which the service provided by the rule information is used;
second identification information indicating a theme of the service provided by the rule information;
at least third identification information indicating a problem to be solved by the service provided by the rule information;
The sensor and the processing module are made to cooperate based on the rule information,
How to control electronic devices.

Images