WO2015162750A1

WO2015162750A1 - Server

Info

Publication number: WO2015162750A1
Application number: PCT/JP2014/061553
Authority: WO
Inventors: 近藤　誠
Original assignee: サン電子株式会社; 近藤　誠
Priority date: 2014-04-24
Filing date: 2014-04-24
Publication date: 2015-10-29
Also published as: JPWO2015162750A1

Abstract

　A server (10) supplies template data to a first setting terminal (70) (S12), and acquires, from the first setting terminal (70), first inputted template data that was inputted in accordance with the template data (S18). The server (10) acquires type 1 device data from each of a plurality of type 1 devices (50) (S22). When a first browse data request is acquired from a first browsing terminal (71) (S30), the server (10) generates, on the basis of the acquired type 1 device data, the first inputted template data, and the first browse data request, first browse data indicating the state of occurrence of events in the plurality of type 1 devices (50) (S32). The server (10) supplies the generated first browse data to the first browsing terminal (71) (S34).

Description

server

The technology disclosed in this specification relates to a server that acquires data from a device and generates and supplies browsing data based on the acquired data.

For example, in Nikkei Electronics 1-6-2014 “M2M Rediscovered” (hereinafter referred to as Non-Patent Document 1), as an example of a system using M2M (Machine-To-Machine) communication, the operation status of construction machinery is monitored. Systems for monitoring the operating status of elevators, systems for collecting sales performance information such as vending machines, and the like are disclosed.

In each system of Non-Patent Document 1, devices (construction machines, elevators, vending machines, etc.) supply information indicating the operating status to the server. The server creates a database using data collected from each device, and supplies the data in the database to the management apparatus in response to a request from the management apparatus that manages each device.

Conventionally, when trying to construct each system of Non-Patent Document 1, it is necessary to perform detailed programming on the server for each system, which is a heavy burden on the system builder.

This specification provides technology that can reduce the burden on the system builder.

One technique disclosed in this specification is a server that acquires device data from each of a plurality of devices and stores the device data in a memory. Each device data includes device identification information for identifying a specific device that is a supply source of the device data, time information related to an occurrence time of an event occurring in the specific device, and a type of event occurring in the specific device. Type information to be displayed. The plurality of devices include a plurality of first type devices and a plurality of second type devices. The server includes a template data supply acquisition unit, a device data acquisition storage unit, a browsing data generation unit, and a browsing data supply unit. The template data supply / acquisition unit includes a first setting terminal for a first user to manage a plurality of first type devices, and a second user for managing a plurality of second type devices. Template data for setting a format for storing device data acquired from each of the plurality of devices in the memory is supplied to the second setting terminal, and input from the first setting terminal according to the template data First input template data is acquired, and second input template data input according to the template data is acquired from the second setting terminal. The device data acquisition storage unit acquires the first type of device data from each of the plurality of first type devices, and the acquired first type of device data is included in the first input template data. Storing the second type of device data from each of the plurality of second type devices and storing the acquired second type of device data in the second input template. The data is stored in the second memory in accordance with the second format included in the data. The browsing data generation unit is configured to generate a plurality of first data based on first type stored data that is first type device data acquired from a plurality of first type devices and stored in a first memory. Second browsing data is first type device data that is generated from a plurality of second type devices and stored in a second memory, generating first browsing data indicating the occurrence state of each event in the type of device. Based on the stored data of the seed, second browsing data indicating the occurrence status of each event in the plurality of second-type devices is generated. The browsing data supply unit supplies the first browsing data to the first browsing terminal of the first user, and supplies the second browsing data to the second browsing terminal of the second user.

Here, “supply template data” means transmitting a set of template data to the first setting terminal and the second setting terminal, and the first setting terminal and the second setting terminal accessing the server. Then, the user can view the display screen displayed according to the template data and input information according to the display screen.

According to the server described above, each user can easily set the manner in which the device data is stored in the memory by inputting information according to the template data supplied from the server. The server stores device data according to the format included in the input template data, and generates browsing data. Therefore, when building a system for collecting information from each of a plurality of devices and managing the plurality of devices for each user, it is not necessary to perform different programming for each system in the server. The server acquires device data including device identification information, difference time information, and type information from each of the plurality of devices. When acquiring device data from each device, the contents of the message design to be performed on the device are determined. Therefore, it is not necessary to perform different message design for the first type device and the second type device in order to obtain device data. Therefore, by building a system using the above server, the burden on the system builder can be reduced.

Note that a control method, a computer program, and a computer-readable recording medium storing the computer program for realizing the server are also novel and useful. In addition, the server, a plurality of first type devices, a plurality of second type devices, a first setting terminal, a first browsing terminal, a second setting terminal, and a second A communication system including a browsing terminal is also new and useful.

1 shows a configuration of a communication system. The sequence chart (1) of the operation | movement outline | summary of a communication system is shown. The sequence chart (2) of the operation | movement outline | summary of a communication system is shown. The example of the production | generation method of 1st type device data is shown. The example of 1st type device data is shown. An example of a template data display screen is shown. An example of the setting screen is shown. An example of first input template data is shown. The continuation of the example of the 1st input template data is shown. The correspondence table of kitchen equipment types is shown. The correspondence table of kitchen equipment is shown. The correspondence table of company master is shown. The correspondence table of a store group master is shown. The correspondence table of a store master is shown. The correspondence table of a store is shown. The correspondence table of installed equipment is shown. The correspondence table of each equipment collection data is shown. The example of the 2nd inputted template data is shown. An example of a browsing data screen is shown. The example of a 1st rule input screen is shown. The example of the 1st rule data is shown. The example of the production | generation method of the 1st type device data of 2nd Example is shown. The example of the 1st type device data of 2nd Example is shown. The example of the production | generation method of the 1st type device data of 3rd Example is shown. The example of the 1st type device data of 3rd Example is shown. The example of the production | generation method of the 1st type device data of 4th Example is shown. The example of the 1st type device data of 4th Example is shown.

The main features of the embodiment described below are listed. The technical elements described below are independent technical elements and exhibit technical usefulness alone or in various combinations, and are not limited to the combinations described in the claims at the time of filing. Absent.

(Characteristic 1) The time information may include time difference information between events occurring in the specific device.

According to this configuration, device data that the server acquires from each device includes differential time information. Therefore, if the server uses the first type device data included in the first database in the memory, the event occurrence state in the first type device can be appropriately reproduced in time series. Further, for example, compared with the case of acquiring information indicating the occurrence status of events per second from the first type device, the capacity of the memory that the server should have is small.

(Characteristic 2) The first format may include first base structure information related to an arrangement location of a plurality of first type devices, and the second format includes a plurality of second type devices. Second base structure information related to the placement location may be included. The browsing data generation unit is included in the first type of stored data and the first base structure information when a first browsing data request including information on the first base is acquired from the first browsing terminal. When the second browsing data request including the information regarding the second base is acquired from the second browsing terminal, the first browsing data is generated based on the information regarding the first base to be The second browsing data may be generated based on the second type of stored data and the information on the second base included in the second base structure information.

According to this configuration, when the server supplies the template data to the first setting terminal and the second setting terminal, the first input template data including the first base structure information is supplied from the first setting terminal. The second input template data including the second site structure information can be acquired from the second setting terminal. The server can generate the first browsing data based on the first site structure information and the first type of stored data, and the second based on the second site structure information and the second type of stored data. Browsing data can be generated. Therefore, it is not necessary to perform different programming for each user base structure in the server.

(Feature 3) The server may further include a totaling unit. The aggregation unit aggregates at least a part of the first type of stored data to generate a first type of aggregated data, and aggregates at least a part of the second type of stored data to aggregate the second type of aggregated data. May be generated. Further, the browsing data generation unit can generate the first browsing data using the first type of total data, and can generate the second browsing data using the second type of total data. Also good.

According to this configuration, the server can generate the first browsing data by using the already generated first type aggregate data. Similarly, the server can generate the second browsing data by using the already generated second type aggregate data. Therefore, the load when the server generates browsing data can be reduced.

(Feature 4) The server may further include a condition data acquisition unit and a notification signal supply unit. The condition data acquisition unit acquires first condition data indicating a first condition for causing the server to supply the first notification signal from the first setting terminal, and sends the first condition data to the server from the second setting terminal. Second condition data indicating a second condition for supplying the second notification signal may be acquired. The notification signal supply unit supplies the first notification signal to the first viewing terminal when the first condition is satisfied by the first type of stored data after the first condition data is acquired, After the second condition data is acquired, the second notification signal may be supplied to the second viewing terminal when the second condition is satisfied by the second type of stored data.

According to this configuration, the server can appropriately supply the first notification signal to the first browsing terminal and can appropriately supply the second notification signal to the second browsing terminal.

(Feature 5) The browsing data generation unit generates the first event again after the first event occurs in each of the plurality of first type devices based on the first type stored data. The first browsing data including the number of second events that occurred until the third time can be generated, and each of the plurality of second type devices is configured based on the second type of stored data. It may be possible to generate second browsing data including the number of fourth events that have occurred between the occurrence of this event and the occurrence of the third event again. Here, “occurrence of an event” includes both generation of a single signal and switching of signal high / low states (switching of signal rising / falling). Good.

According to this configuration, the server can appropriately generate the first browsing data that the first user desires to browse, and can appropriately generate the second browsing data that the second user desires to browse. it can. Further, based on only device data acquired from the device side, it is possible to generate browsing data including the number of occurrences of a state in which a plurality of types of events form a specific relationship in time and the occurrence time of the state. it can.

(First embodiment)
(Configuration of communication system 2; FIG. 1)
As illustrated in FIG. 1, the communication system 2 includes a server 10, a plurality of first type devices 50, a plurality of second type devices 60, a first setting terminal 70, and a first browsing. A terminal 71, a second setting terminal 80, and a second browsing terminal 81 are provided. The plurality of first type devices 50 are provided so as to be able to communicate with the server 10. Similarly, a plurality of second type devices 60 are also provided so as to be able to communicate with the server 10. The first setting terminal 70, the first browsing terminal 71, the second setting terminal 80, and the second browsing terminal 81 are also provided so as to be able to communicate with the server 10. In the example of FIG. 1, the plurality of first type devices 50 include, for example, a microwave oven 50a, an oven 50b, and a dishwasher 50c. The plurality of second type devices 60 include, for example, a press machine 60a, a conveyor 60b, and a printing machine 60c.

In this embodiment, the plurality of first type devices 50, the first setting terminal 70, and the first browsing terminal 71 each belong to the first user. In this embodiment, the first user is a kitchen equipment manufacturer that is a vendor of a plurality of first-type devices 50. The plurality of second-type devices 60, the second setting terminal 80, and the second browsing terminal 81 each belong to the second user. In this embodiment, the second user is an industrial equipment manufacturer that is a vendor of a plurality of second type devices 60.

That is, the communication system 2 of the present embodiment includes a first system in which a first user manages a plurality of first type devices 50 using the server 10, and a second user It can be said that the system includes a second system for managing a plurality of second-type devices 60 using the server 10. In this case, the first system includes a plurality of first type devices 50, a server 10, a first setting terminal 70, and a first browsing terminal 71. The second system includes a plurality of second type devices 60, a server 10, a second setting terminal 80, and a second browsing terminal 81.

(Server 10)
The server 10 has a control unit 20. The control unit 20 includes a CPU 22 and a memory 24. The CPU 22 executes various processes according to programs stored in the memory 24. The memory 24 includes a ROM, a RAM, a hard disk, and the like. The memory 24 stores the program executed by the CPU 22. The memory 24 stores template data 25, first user information 26, and second user information 28.

The template data 25 is a format in which the device data acquired by the server 10 from the device (for example, the first type device 50) of the user (for example, the first user) who uses the server 10 is stored in the memory 24 of the server 10. This is data for setting. In other words, the template data is data for inputting metadata regarding each event that occurs in the device. Here, “device data” refers to the interval between device identification information (that is, a device unique number) for identifying a device (referred to as a specific device) that is a supply source of the device data, and each event that occurs in the specific device. Data including difference time information indicating the difference time between them and type information indicating the type of event occurring in the specific device. The difference time information and the type information in the device data may be collectively referred to as “difference data”. A user who uses the server 10 can set a format for storing the device data in the memory 24 of the server 10 by accessing the server 10 and inputting information according to the template data 25 (that is, input). Completed template data can be stored in the memory 24). Detailed contents of the template data 25 and detailed contents of the input template data will be described in detail later.

The first user information 26 includes various data related to management of a plurality of first type devices 50 by the first user. Specifically, the first user information 26 includes first input template data 26a, first rule data 26b, and a first database 26c.

The first input template data 26 a is data acquired from the first setting terminal 70. That is, the first user can generate the first input template data by accessing the server 10 using the first setting terminal 70 and inputting information according to the template data 25 described above. The first input template data includes a first format in which the first type device data acquired by the server 10 from each of the plurality of first type devices 50 is stored in the memory 24. In addition, the first format included in the first input template data also includes information regarding a hierarchical structure when browsing the first type device data acquired from the plurality of first type devices 50. The first setting terminal 70 supplies the first input template data to the server 10. When the server 10 acquires the first input template data including the first format from the first setting terminal 70, the server 10 stores the first input template data in the memory 24 (see reference numeral 26a in FIG. 1). .

The first rule data 26b is also data acquired from the first setting terminal 70. The first rule data 26b includes information indicating a first condition for causing the server 10 to supply the first notification signal. A specific method for the server 10 to acquire the first rule data 26b from the first setting terminal 70 will be described later.

The first database 26c is formed by storing the first type device data acquired from the plurality of first type devices 50 in the memory 24 in accordance with the first format included in the first input template data. Database.

Here, the first type device data is data acquired from each of the plurality of first type devices 50. The first type device data includes a device unique number for identifying the first type device 50 (for example, the microwave oven 50a), type information indicating the type of event that has occurred, and the first type device 50 ( For example, it includes difference time information indicating a difference time between events occurring in the microwave oven 50a).

The second user information 28 includes various data necessary for the second user to manage a plurality of second type devices 60. Specifically, the second user information 28 includes second input template data 28a, second rule data 28b, and a second database 28c. The contents of the second input template data 28a, the second rule data 28b, and the second database 28c are all the first input template data 26a, the second rule data 26b, Since it is almost the same as the contents of the first database 26c, detailed description is omitted.

(Multiple first-type devices 50)
As described above, the plurality of first type devices 50 include the microwave oven 50a, the oven 50b, and the dishwasher 50c. The plurality of first type devices 50 include other first type devices (not shown). Hereinafter, each device (for example, the microwave oven 50a) included in the plurality of first type devices 50 may be simply referred to as “first type device 50”. Each of the plurality of first type devices 50 stores a device unique number for identifying the device. Each of the plurality of first type devices 50 is provided so as to be able to communicate with the server 10 via a network (not shown). Each of the plurality of first-type devices 50 can supply the above-described first-type device data to the server 10.

(Multiple second type devices 60)
As described above, the plurality of second type devices 60 include the press machine 60a, the conveyor 60b, and the printing machine 60c. The plurality of second type devices 60 include other second type devices (not shown). Hereinafter, each device (for example, the press machine 60a) included in the plurality of second type devices 60 may be simply referred to as a “second type device 60”. Each of the plurality of second type devices 60 also stores a device unique number for identifying the device. Each of the plurality of second type devices 60 is provided so as to be able to communicate with the server 10 via a network (not shown). Each of the plurality of second type devices 60 can supply the second type of device data to the server 10. Similar to the first type device data, the second type device data includes a device unique number for identifying the second type device 60, type information indicating the type of event that has occurred, and the second type device data. Difference time information indicating a difference time between each event occurring in the device 60.

(First setting terminal 70, first browsing terminal 71)
The first setting terminal 70 is, for example, a terminal device such as a first user's PC. The 1st browsing terminal 71 is terminal devices, such as a 1st user's tablet terminal, for example. Each of the first setting terminal 70 and the first browsing terminal 71 has an operation unit, a display unit, and a control unit (not shown). The first setting terminal 70 and the first browsing terminal 71 are provided so as to be able to communicate with the server 10 via a network (not shown). In the present embodiment, the first setting terminal 70 and the first browsing terminal 71 are configured as separate terminals. However, the present invention is not limited thereto, and in the modification, the first setting terminal 70 and the first browsing terminal 71 may be configured as one terminal.

(Second setting terminal 80, second browsing terminal 81)
The second setting terminal 80 is, for example, a terminal device such as a second user's PC. The 2nd browsing terminal 81 is terminal devices, such as a 2nd user's tablet terminal, for example. Each of the second setting terminal 80 and the second browsing terminal 81 has an operation unit, a display unit, and a control unit (not shown). The second setting terminal 80 and the second browsing terminal 81 are provided to be able to communicate with the server 10 via a network (not shown). In the modification, the second setting terminal 80 and the second browsing terminal 81 may be configured as one terminal.

(Outline of operation of communication system 2; FIGS. 2 and 3)
Next, an overview of the operation of each component in the communication system 2 will be described with reference to FIGS. 2 and 3, processing executed between the server 10, the first setting terminal 70, the first browsing terminal 71, and the first type device 50 will be described as an example.

FIG. 2 shows the operation of each component when the server 10 acquires the first input template data from the first setting terminal 70 and then supplies the first browsing data to the first browsing terminal 71. The outline of is shown.

In accordance with the operation of the first user, the first setting terminal 70 accesses the server 10 and supplies a template request to the server 10 (S10).

When the server 10 acquires the template request from the first setting terminal 70, the server 10 supplies the template data (see reference numeral 25 in FIG. 1) to the first setting terminal 70 (S12).

When acquiring the template data from the server 10, the first setting terminal 70 displays a template data display screen on the display unit (S14). The contents of the template data display screen will be described in detail later (see FIG. 6). The first user operates the operation unit of the first setting terminal 70 and inputs information according to the template data (S16). As a result, first input template data (see FIGS. 8 and 9) is generated. The first setting terminal 70 supplies the generated first input template data to the server 10 (S18).

When the server 10 acquires the first input template data from the first setting terminal 70, the server 10 stores the acquired first input template data in the memory 24 (S20) (see reference numeral 26a in FIG. 1).

Thereafter, the first type device 50 supplies the first type of device data to the server 10 every time an event (eg, power ON, start of heating, abnormal operation, etc.) occurs in the first type device 50. (S22, S26). As described above, the first type of device data includes a device unique number for identifying the first type of device 50, type information indicating the type of event that has occurred, and each type of device data generated by the first type of device 50. It includes difference time information indicating the difference time between events. The method of generating the first type of device data by the first type device 50 and the contents of the first type of device data will be described in detail later with reference to FIGS. In the modified example, the first type device 50 may generate the first type device data each time an event occurs, and store the generated first type device data in its own memory. Good. In this case, the first type device 50 may supply the server 10 with the first type device data stored in the memory every predetermined period. Further, the first type device 50 supplies the first type device data stored in the memory to the server 10 when a predetermined event occurs (for example, a power-off operation is performed). May be.

Each time the server 10 acquires the first type of device data from the first type of device 50, the server 10 stores the acquired first type of device data in the memory 24 (S24, S28). When the server 10 stores the acquired first type device data in the memory 24, the server 10 stores the acquired first type device data in accordance with the first format included in the first input template data. Thereby, the first database 26 c is constructed in the memory 24. If the server 10 uses the first type of device data included in the first database 26c in the memory 24, the server 10 can appropriately reproduce the event occurrence state in the first type of device 50 in time series. . In the present embodiment, as described above, the server 10 acquires the first type device data from the first type device 50 and stores it. Therefore, for example, the capacity of the memory 24 that the server 10 should have is small compared to the case where information indicating the event occurrence status per second is acquired from the first type device 50. Further, based on the acquired first type device data, the server 10 totals the event occurrence status of the first type device 50 to generate first type total data (S24, S28). The server 10 also stores the first type aggregated data in the memory 24.

Thereafter, according to the operation of the first user, the first browsing terminal 71 accesses the server 10 and supplies the first browsing data request to the server 10 (S30). The first browsing data request includes information indicating a hierarchy (for example, an installation area of the first device 50) for which the first browsing terminal 71 requests browsing of data. Here, the “hierarchy” may be rephrased as a “base” related to the arrangement location of the first type device 50.

When the server 10 acquires the first browsing data request from the first browsing terminal 71, the first type device data included in the first database 26c in the memory 24, the first input template data 26a, Based on the acquired first browsing data request, first browsing data indicating the occurrence status of each event in the first type device 50 is generated (S32). At this time, the server 10 generates first browsing data indicating an event occurrence status (for example, an event occurrence status for each installation district) corresponding to the hierarchy indicated by the information included in the first browsing data request. Further, the server 10 uses the first type of total data in the memory 24 when generating the first browsing data. Since the server 10 generates the first browsing data using the already generated first type of aggregated data, the first data is aggregated after the first browsing data request is acquired. There is no need to generate one browsing data. Therefore, the burden on the server 10 when generating the first browsing data can be reduced. Furthermore, after acquiring the first browsing data request from the first browsing terminal 71, the server 10 can supply the first browsing data 71 to the first browsing terminal 71 that has generated the first browsing data in a short time. The first user does not wait for a long time.

What information is included in the first browsing data includes the contents of the first type of device data included in the first database 26c, the contents of the first input template data 26a, and the first browsing. It depends on the content of the data request. For example, the first browsing data generated by the server 10 is the period from the occurrence of the first event (for example, the start of heating operation) to the occurrence of the first event again in the first type device 50. May include the number of second events (for example, the value of the temperature sensor is 100 ° C. or higher) that occurred.

The server 10 supplies the generated first browsing data to the first browsing terminal 71 (S34).

When the first browsing terminal 71 acquires the first browsing data from the server 10, the first browsing terminal 71 displays a data browsing screen (see FIG. 19) on the display unit according to the acquired first browsing data (S36). On the data browsing screen, the first user can change a hierarchy for browsing data and perform a new first browsing data request operation, for example. In that case, the first browsing terminal 71 supplies a new first browsing data request to the server 10 (S38).

When the server 10 obtains a new first browsing data request from the first browsing terminal 71, the first type of device data included in the first database 26c in the memory 24 and the first input template data Based on 26a and the acquired new first browsing data request, new first browsing data is generated (S40). The server 10 supplies the generated first browsing data to the first browsing terminal 71 (S42).

When the first browsing terminal 71 acquires the first browsing data from the server 10, the first browsing terminal 71 displays a data browsing screen on the display unit according to the acquired first browsing data (S44). Thus, the 1st browsing terminal 71 can acquire the 1st browsing data corresponding to a 1st browsing data request | requirement from the server 10, and can display it on a display part (S36, S44). The first user can know the state of occurrence of each event in the first type device 50 by looking at the data browsing screen displayed based on the first browsing data. In addition, by changing the conditions (that is, the hierarchy) and supplying the first browsing data request to the server 10, it is possible to know the occurrence status of each event under various conditions. As a result, the first user can appropriately manage the first type device 50.

Subsequently, referring to FIG. 3, after the server 10 acquires the first input template data from the first setting terminal 70, the first rule data (reference numeral 26b in FIG. 1) is obtained from the first setting terminal 70. After that, the outline of the operation of each component when supplying the first notification signal to the first viewing terminal 71 will be described.

After the first input template data is supplied to the server 10 (see S18 in FIG. 2), the first setting terminal 70 accesses the server 10 according to the instruction of the first user, and the first rule A first rule input screen request for displaying the input screen (see FIG. 20) is supplied to the server 10 (S50).

When the server 10 acquires the first rule input screen request from the first setting terminal 70, the server 10 generates the first rule input screen data using the first input template data 26a in the memory 24 (S52). ). That is, the content of the first rule input screen data generated in S52 varies depending on the content of the first input template data 26a. The server 10 supplies the generated first rule input screen data to the first setting terminal 70 (S54).

When acquiring the first rule input screen data from the server 10, the first setting terminal 70 displays the first rule input screen (see FIG. 20) on the display unit (S56). The contents of the first rule input screen will be described in detail later. The first user inputs information according to the first rule input screen (S58). As a result, first rule data (see FIG. 21) is generated. The first rule data includes a first condition for causing the server 10 to supply a first notification signal. The first setting terminal 70 transmits the generated first rule data to the server 10 (S60).

When the server 10 acquires the first rule data from the first setting terminal 70, the server 10 stores the first rule data in the memory 24 (S61) (see reference numeral 26b in FIG. 1). Next, the server 10 monitors whether the first condition included in the first rule data is satisfied by the first type of device data included in the first database 26c. When the first condition is satisfied (S62), the server 10 supplies a first notification signal indicating that the first condition is satisfied to the first viewing terminal 71 (S64). The first notification signal also includes information indicating an operation (for example, alarm notification) to be performed by the first browsing terminal 71.

When the first browsing terminal 71 acquires the first notification signal from the server 10, the first browsing terminal 71 performs an operation (for example, alarm notification) according to the content of the acquired first notification signal (S66).

In the above example, each process executed among the server 10, the first setting terminal 70, the first browsing terminal 71, and the first type device 50 has been described as an example. However, substantially the same processing is executed between the server 10, the second setting terminal 80, the second browsing terminal 81, and the second type device 60 (for example, the press 60a in FIG. 1). . In this case, the words “first” and “first type” in the example of FIG. 2 are replaced with “second” and “second type”. Also in this case, the template data supplied from the server 10 to the second setting terminal 80 (see S12) is the same as the template data supplied from the server 10 to the first setting terminal 70 (see reference numeral 25 in FIG. 1). It is data.

That is, in the communication system 2 according to the present embodiment, each user can easily set the manner in which the device data is stored in the memory 24 of the server 10 by inputting according to the template data supplied from the server 10. . The server 10 stores device data according to the format included in the input template data, and generates browsing data. Therefore, when building a system for collecting information from each of a plurality of devices and managing the plurality of devices for each user, it is not necessary to perform different programming for each system in the server 10. Further, the server 10 acquires device data including a device unique number, difference time information, and type information from each of a plurality of devices. When acquiring device data from each device, the contents of the message design to be performed for each device are determined. Therefore, it is not necessary to perform different message design for the first type device 50 and the second type device 60 in order to acquire device data. Therefore, by building a system using the server 10 of this embodiment, the burden on the system builder can be reduced.

(First-type device data generation method; FIGS. 4 and 5)
With reference to FIG. 4, a method in which the first type device 50 generates the first type of device data will be described. FIG. 4 shows an example in which two types of events of type A and type B occur in the first type device 50. As shown in FIG. 4, when a specific event (B1 in FIG. 4) occurs, the first type device 50 has an event (A1 in FIG. 4) that occurred last time of the specific event (B1). The difference time (T1) between the occurrence time (t1) and the occurrence time (t2) of the specific event (B1) is specified. Furthermore, the first type device 50 specifies the type (B) of a specific event. The first type device 50 associates the device unique number (1001) of the first type device 50, the difference time (T1), and the type information indicating the type (B) of a specific event. As a result, as shown in FIG. 5, the first type of device data in which the device unique number, the difference time, and the type information are associated with each other is generated.

The first type device 50 also includes the type information (B, A, A...) And the difference time (T2, T3, T4 ...) is specified. As a result, the first type of device data is generated even when each event after a specific event occurs. The first type device 50 supplies the first type device data to the server 10 as needed. Therefore, for example, the communication load of the first type device 50 can be reduced as compared with the case where information indicating the event occurrence status per second is supplied to the server 10.

In the example of FIGS. 4 and 5, the example in which the first type device 50 generates the first type of device data has been described. However, when the second type device 60 generates the second type of device data, Same as above.

(Template data display screen: Fig. 6)
With reference to FIG. 6, a template data display screen (see S <b> 14 in FIG. 2) displayed on the first setting terminal 70 and the second setting terminal 80 according to the template data supplied by the server 10 will be described.

Fig. 6 shows the template data display screen in the initial state. The template data display screen in the initial state has a tree structure including items of date 102, day of the week 104, month 106, year 108, and calendar 110. When the “+” mark displayed next to each item is selected, the data in each item is expanded. Although not shown, for example, when “+” next to the date 102 is selected, items of date number and date name are displayed. Each item of the date 102, the day of the week 104, the month 106, the year 108, and the calendar 110 includes a plurality of first items on a predetermined date, a predetermined day of the week, a predetermined month, a predetermined year, and a day in the predetermined calendar. This is an item for browsing the occurrence status of events in the seed device 50 or a plurality of second kind devices 60.

(Setting screen; Fig. 7)
When a predetermined item addition operation is performed on the template data display screen of FIG. 6 or when an operation of selecting any of the displayed items is performed, the tree structure shown in FIG. The setting screen shown in Fig. 6 is displayed. The setting screen is also a screen displayed according to the template data. The setting screen of FIG. 7 includes a table in which items, values, and types are associated with each other.

In the item column, “Name”, “DispName”, “ValueType”, “ValueRule”, “TargetType”, and “SignalNumber” are entered in advance. Information (characters or numbers) corresponding to each item can be input in the value column. In the type column, the attributes of the information input in the value column are displayed in characters. The first user and the second user (hereinafter may be collectively referred to as “users”) can input information corresponding to each item in the value column.

“Name” is the name of the item data displayed on the template data display screen. The name indicated by “Name” is a unique name that does not overlap with other names. The user can input a desired name such as “Company” in the value column corresponding to “Name”. Along with the input in the value column, information indicating character information is input in the type column.

“DispName” is the name (display name) when displaying the item. The user can input a desired display name such as “company” in the value column corresponding to “DispName”. Along with the input in the value column, information indicating character information is input in the type column.

“ValueType” indicates the type of event (signal, numerical value, character information, etc.) corresponding to the item. For example, in the first type device 50, various types of events occur. The first type device 50 outputs predetermined information each time an event occurs. For example, when an event such as power ON / OFF, heating operation start, or abnormal operation occurs in the first type device 50, the first type device 50 outputs a pulse signal. The pulse signal includes a single type and a type that switches between high and low. In addition, in the first type device 50, an event may occur in which a predetermined numerical value such as a sensor detection value (for example, temperature), a model number, an ID, or character information is output. The user can input values such as “0”, “1”, and “2” in the value column corresponding to “ValueType”. Here, each value such as “0”, “1”, and “2” corresponds to each type of “signal” and “numerical value”. Along with the input in the value column, for example, information indicating integer information is displayed in the type column.

“ValueRule” indicates a rule relating to information corresponding to the type input in “ValueType”. Specifically, it indicates whether or not the information output from the device can be added. For example, when the information output from the first type device 50 is a pulse signal or numerical information indicating the amount of money, the number of pulse signals and the value indicated by the numerical value can be added. Further, even if the information output from the first type device 50 is a numerical value, the value cannot be added when the information is a unique value such as a numerical value indicating a model number. The user can input values such as “0”, “1”, and “2” in the value column corresponding to “ValueRule”. Each value input in the value column corresponds to “not addable”, “addable”, “unique value”, and the like. Along with the input in the value column, for example, information indicating that it is an integer is displayed in the type column.

“TargetType” indicates the relationship of the actual database structure shown in a tree structure. For example, a relationship is shown such that a base concept corresponding to the second item exists under the base hierarchy corresponding to the first item. The user can input values such as “0”, “1”, and “2” in the value column corresponding to “TargetType”. Each value entered in the value field is "No base in lower hierarchy" (corresponding to item), "There are more bases in lower hierarchy", "Database table item in lower hierarchy" Corresponds to “is present”. Information indicating that it is an integer is displayed in the type column.

“SignalNumber” indicates a signal type number that defines device data acquired from the device. By defining “SignalNumber”, the device data defined by the signal type number is used as the value of the database item. For example, a unique signal type number is assigned to each device, such as “5” for “sensor A signal” and “6” for “sensor B signal”. When the device data is acquired from the device, the server 10 accumulates the number of events indicated by the signal type number for the database item corresponding to the item for which this value is defined, and updates it whenever it changes.

In the setting screen of FIG. 7, the item is displayed on the template data display screen when the user inputs necessary information. The display name of the item is the name input in “DispName”. The item is displayed at a position corresponding to the value input in “TargetType”.

Thus, the user can add items to the template data display screen by displaying the setting screen and inputting necessary information. As a result, a tree structure desired by the user can be formed.

As described above, the user can also display the setting screen by selecting an already set item. In that case, the user can change the setting content of the item on the displayed setting screen.

Accordingly, the user inputs necessary information on the template data display screen of FIG. 6 and the setting screen of FIG. 7, thereby inputting template data (first input template data, first template data) based on the template data. 2 input template data) can be created.

Note that the setting screen shown in FIG. 7 is merely an example. In the modification, the setting screen may include other items.

(Example of first input template data; FIGS. 8 to 17)
Subsequently, referring to FIGS. 8 to 17, an example of first input template data generated by a first user who is a user of the first setting terminal 70 inputting information according to the template data Will be described.

8 and 9 show screens displayed on the display unit of the first setting terminal 70 in accordance with the first input template data. As shown in FIG. 8, the first input template data includes items of date 102, day of week 104, month 106, year 108, and calendar 110, as in the template data display screen in the initial state (FIG. 6). . Further, as shown in FIGS. 8 and 9, the first input template data includes items of the kitchen device type 120, the kitchen device 140, and the period 160. The period 160 includes items of the company master 170, the store group master 180, the store master 200, and the store 220 as lower layers. The store 220 includes items of an installed device 240 and each device collection data 260 as a lower hierarchy.

8 is the same as the template data display screen (FIG. 6) in the initial state, and detailed description thereof is omitted here for each item of date 102, day of the week 104, month 106, year 108, and calendar 110.

The kitchen device type 120 in FIG. 8 includes items of a device type number and a device type name as a lower hierarchy. In the kitchen device type 120, as shown in FIG. 10, a device type number and a device type name are associated with each other. In FIG. 10, for example, the device type number “1” indicates the device type name “oven”.

Further, the kitchen device 140 of FIG. 8 includes a device unique number, a device type number, a device name, and each item of the manufacturer. In the kitchen device 140, as shown in FIG. 11, a device unique number, a device type number, a device name, and a manufacturer are associated with each other. In FIG. 11, for example, the device unique number “1001”, the device type number “1”, the name “kiln oven”, and the manufacturer “T Electronics” are associated with each other.

Further, as described above, the period 160 in FIG. 9 includes items of the company master 170, the store group master 180, the store master 200, and the store 220 as lower layers. The company master 170 includes items of company number and company name. In the company master 170, as shown in FIG. 12, the company number and the company name are associated with each other. In FIG. 12, for example, the company number “1” indicates the company name “S Cafe”. In addition, due to the fact that the company master 170 is provided, the server 10 generates an event in the first type device 50 every time the first type device data is acquired from the first type device 50. The status of occurrence is summarized for each company.

Further, the store group master 180 in FIG. 9 includes items of company number, store group number, and store group name. In the store group 180, as shown in FIG. 13, the company number, the store group number, and the store group name are associated with each other. In FIG. 13, for example, in the company with the company number “1”, the store group number “12” corresponds to the store group name “Kanto”. The correspondence relationship between the store group number and the store group name may be common among companies. That is, as shown in FIG. 13, in the company with the company number “2”, the store group number “12” corresponds to the store group name “Kanto”. In addition, due to the fact that the store group master 180 is provided, the server 10 receives the first type device data from the first type device 50 every time the first type device data is acquired. The event occurrence status is tabulated for each store group.

Further, the store master 200 of FIG. 9 includes items of a store number and a store name. In the store master 200, as shown in FIG. 14, the store number and the store name are associated with each other. In FIG. 14, for example, the store number “170” indicates the store name “S Cafe Marunouchi”. In addition, due to the fact that the store master 202 is provided, the server 10 generates an event in the first type device 50 each time the first type device data is acquired from the first type device 50. The occurrence situation of each is calculated for each store.

Further, the store 220 in FIG. 9 includes items of a store number and a store group number. In the store 220, as shown in FIG. 15, store numbers and store group numbers are associated with each other. In FIG. 15, for example, the store group number “12” and the store number “170” are associated with each other.

Further, as described above, the store 220 in FIG. 9 includes items of the installed device 240 and each device collection data 260 as the lower hierarchy. The installed device 240 includes an item unique number, a use start date, a repair date, and a use end date. In the installation device 240, as shown in FIG. 16, a device unique number, a use start date, a repair date, and a use end date are associated with each other.

Also, each device collection data 260 in FIG. 9 includes items of a device unique number, an A signal accumulated value, a B signal accumulated value, and a C signal accumulated value. In each device collection data 260, as shown in FIG. 17, a device unique number, an A signal accumulated value, a B signal accumulated value, and a C signal accumulated value are associated with each other. The A signal accumulated value, the B signal accumulated value, and the C signal accumulated value respectively indicate accumulated values (that is, the total number of occurrences of events) of each event that occurs in the plurality of first type devices 50.

8 and 9, the device unique number of the installed device 240 and the device unique number of the kitchen device 140 are associated with each other as indicated by an arrow 270. Similarly, the device unique number of each device collection data 260 is also associated with the device unique number of the kitchen device 140. Therefore, for example, when the device unique number is selected while browsing the event occurrence status for each installed device in the first browsing terminal 71, the event occurrence status for each kitchen device can be browsed. . In this case, an item related to the device unique number is provided on both the screen for viewing the event occurrence status for each installed device and the screen for viewing the event occurrence status for each kitchen device. In general, the association indicated by the arrow 270 in FIGS. 8 and 9 may be referred to as a “relation”.

In addition to this, as indicated by an arrow 280 in FIG. 9, the store group number of the store 220 and the store group number of the store group master 180 are associated with each other. Further, as indicated by an arrow 285, the store number of the store 220 and the store number of the store master 200 are associated with each other.

The example of the first input template data has been described above with reference to FIGS. 8 to 17. As described above, when the first setting terminal 70 generates the first input template data, the first setting terminal 70 supplies the generated first input template data to the server 10 (see S18 in FIG. 2). The server 10 stores the first input template data in the memory 24 (see S20 in FIG. 2 and reference numeral 26a in FIG. 1).

(Example of second input template data; FIG. 18)
With reference to FIG. 18, an example of second input template data generated by a second user who is a user of the second setting terminal 80 inputting information according to the template data will be described. As shown in FIG. 18, the content of the second input template data is different from the content of the first input template data (see FIGS. 8 and 9).

FIG. 18 shows a screen displayed on the display unit of the second setting terminal 80 in accordance with the second input template data. As shown in FIG. 18, the second input template data also includes items of date 102, day of the week 104, month 106, year 108, and calendar 110, as in the template data display screen in the initial state (FIG. 6). . Further, as shown in FIG. 18, the second input template data includes items of company A302 and company B304.

The company A302 includes items of a store A310, a store B350, a store C360, a store group 370, and a store 380 as lower layers. The company B304 includes items of a company master and a company.

Further, the store A310 includes items of a part group, a storage location, a parts master, a master set, inventory, a log, and a register. Each item of parts master, master set, inventory, log, and register has a lower hierarchy.

As described above, when the second setting terminal 80 generates the second input template data, the second setting terminal 80 supplies the generated second input template data to the server 10 (see S18 in FIG. 2). The server 10 stores the second input template data in the memory 24 (see S20 in FIG. 2 and reference numeral 28a in FIG. 1).

(Example of browsing data screen; Fig. 19)
Next, an example of the browsing data screen displayed according to the first browsing data (see S34 and S42 in FIG. 2) will be described with reference to FIG. In this example, it is assumed that the first browsing terminal 71 inputs each condition of “microwave oven”, “Kanto area”, “S cafe”, and “within one month” to the first browsing data request. . In this case, the server 10 receives the first type of device data included in the first database 26c in the memory 24, the first input template data 26a, and the first browsing data request (ie, “microwave oven”). Based on the “Kanto area”, “S cafe”, and “within one month” conditions, a first browsing data request is generated and supplied to the first browsing terminal 71. When acquiring the first browsing data request, the first browsing terminal 71 displays the browsing data screen shown in FIG. 19 on the display unit (see S36 and S44 in FIG. 2).

In the browsing data screen of FIG. 19, the store is associated with the number of occurrences of each event (A state, B state, C state). For example, “S Cafe Marunouchi” indicates that the A state occurred 100 times, the B state occurred 50 times, and the C state occurred 40 times during one month. Thus, the 1st browsing terminal 71 can acquire the 1st browsing data corresponding to a 1st browsing data request | requirement from the server 10, and can display it on a display part. The first user can know the occurrence status of each event in the plurality of first-type devices 50 by looking at the browsing data screen displayed based on the first browsing data (S36 in FIG. 2). , S44). Also, by changing the conditions and supplying the first browsing data request to the server 10, it is possible to know the occurrence status of each event under various conditions. As a result, the first user can appropriately manage the plurality of first type devices 50.

The browsing data screen based on the second browsing data will not be described in detail with reference to the drawings, but the same can be said as in the case of the browsing data screen based on the first browsing data (see FIG. 19).

(First rule input screen; FIG. 20)
Next, an example of the rule input screen (see S56 in FIG. 3) displayed according to the first rule input screen data will be described with reference to FIG. When obtaining the first rule input screen data from the server 10, the first setting terminal 70 displays the first rule input screen shown in FIG. 20 on the display unit (see S54 and S56 in FIG. 3).

In the first rule input screen of FIG. 20, items 402 to 412 for setting conditions for causing the server 10 to supply the first notification signal, and the contents of actions (ie actions) to be performed by the server 10 are displayed. An item 420 for setting is displayed. When the first administrator selects each item 402 to 414, 420, a pull-down menu is displayed below the selected item. For example, when the item 402 is selected, a pull-down menu including items such as “current”, “all stores”, “one month”, “Saturday”, “all periods”, and “group” is displayed. The first manager selects a desired item from among the items in the pull-down menu. Thereby, information to be included in each item is determined. Each item included in the pull-down menu is determined according to the content of the first input template data 26 a stored in the memory 24.

(First rule data; FIG. 21)
When information to be included in each of the items 402 to 412 and 420 in FIG. 20 is determined, first rule data (see S60 in FIG. 3) is generated. An example of the first rule data will be described with reference to FIG. In the example of FIG. 21, each item is set on the first rule input screen of FIG. 20, so that the first condition of “alarm notification if the average number of abnormalities in the microwave oven of store A is 10 or more” is set. The first rule data including is generated.

As described above, when the first setting terminal 70 generates the first rule data of FIG. 21, the first setting terminal 70 supplies the generated first rule data to the server 10 (see S60 of FIG. 3). The server 10 stores the first rule data in the memory 24 (S61) (see reference numeral 26b in FIG. 1). Next, the server 10 uses the first type device data acquired from the first type device 50 to determine the first condition included in the first rule data (that is, “the average abnormal frequency of the microwave oven of the store A is 10 or more ") is monitored. In other words, the server 10 monitors that the first condition is satisfied by the first type of device data included in the first database 26c in the memory 24. When the first condition is satisfied (S62), the server 10 supplies a first notification signal indicating that the first condition is satisfied to the first viewing terminal 71 (S64). When the first browsing terminal 71 acquires the first notification signal from the server 10, the first browsing terminal 71 performs an operation (for example, alarm notification) according to the content of the acquired first notification signal (S66).

The second rule input screen and the second rule data will not be described with reference to the drawings, but the first rule input screen (see FIG. 20) and the first rule data (see FIG. 21). The same can be said for.

(Operational effect of this embodiment)
The communication system 2 according to the present embodiment has been described above. In the present embodiment, the server 10 acquires device data including a device unique number, difference time information, and type information from each of a plurality of devices. In contrast, conventionally, when an individual system is constructed for each type of device, device data acquired from each type of device may not include type information. Conventionally, since the message design is individually performed for each device type, if the event type information is consistent between the server and each device, it is not necessary to acquire the type information as device data each time. Due to In the communication system 2 according to the present embodiment, the device data transmitted by each device is configured so as to include event type information, and the message format of the device data acquired from each device is shared. Therefore, it is not necessary to perform different message design for the first type device 50 and the second type device 60 in order to acquire device data. Therefore, by building a system using the server 10 of this embodiment, the burden on the system builder can be reduced.

Thereby, each user can easily set the format in which the device data is stored in the memory 24 of the server 10 by inputting according to the template data supplied from the server 10. The server 10 stores device data according to the format included in the input template data, and generates browsing data. Therefore, when building a system for collecting information from each of a plurality of devices and managing the plurality of devices for each user, it is not necessary to perform different programming for each system in the server 10.

In the present embodiment, the case where the device unique number is included in the device data has been described. However, in the modification, the device unique number is not included in the device data, and may be acquired once together with the first device data, for example. .

In this embodiment, every time the server 10 acquires the first type of device data from the first type of device 50, the server 10 counts the occurrence status of the event of the first type of device 50 to obtain the first type of totaled data. (See S24 and S28 in FIG. 2). The server 10 stores the first type of aggregate data in the memory 24 together with the first type of device data. Thereby, when the first browsing data request is acquired from the first browsing terminal 71, the server 10 generates the first browsing data by using the already generated first type aggregate data. (See S32 and S40 in FIG. 2). The same applies to the case where the second browsing data request is acquired from the second browsing terminal 81. Therefore, the server 10 does not need to generate browsing data after the data is aggregated after the browsing data request is acquired. Therefore, the load when the server 10 generates browsing data can be reduced.

In this embodiment, when the server 10 acquires the first rule data from the first setting terminal 70, the server 10 stores the first rule data in the memory 24 (see S61 in FIG. 3). Next, the server 10 monitors whether the first condition included in the first rule data is satisfied by the first type device data acquired from the first type device 50. When the condition is satisfied (S62), the server 10 supplies a first notification signal indicating that the first condition is satisfied to the first viewing terminal 71 (S64). When the first browsing terminal 71 acquires the first notification signal from the server 10, the first browsing terminal 71 performs an operation (for example, alarm notification) according to the content of the acquired first notification signal (S66). The same applies to the case where the second rule data is acquired from the second browsing terminal 81. Therefore, the server 10 can appropriately supply the first notification signal to the first browsing terminal 71 and can appropriately supply the second notification signal to the second browsing terminal 81.

In the present embodiment, the first browsing data generated by the server 10 (see S32 and S40 in FIG. 2) occurs in the first type device 50 in the first event (for example, the start of heating operation). May include the number of second events (for example, the value of the temperature sensor is 100 ° C. or higher) that occurs between the occurrence of the first event and the occurrence of the first event again. The same can be said for the second browsing data. Therefore, the server 10 can generate first browsing data that the first user desires to browse, and can generate second browsing data that the second user desires to browse.

(Correspondence)
The device unique number is an example of “device identification information”. The tree structure shown in FIGS. 8 and 9 is an example of the “first style”. The tree structure shown in FIG. 18 is an example of the “second style”. The first database 26c is an example of “first type stored data”. Similarly, the second database 28c is an example of “second type stored data”. The hierarchical structure of each item included in FIGS. 8 and 9 is an example of “first base structure information”. The hierarchical structure of each item included in FIG. 18 is an example of “second base structure information”. The memory 24 is an example of a “first memory” and a “second memory”. The conditions included in the first browsing data request (for example, each condition of “microwave oven”, “Kanto area”, “S cafe”, “within one month” in FIG. 19) is an example of “first base”. Similarly, the condition included in the second browsing data request is an example of “second base”. The first rule data in FIG. 21 and the conditions included in the first rule data (that is, the condition “alarm notification if the average number of abnormalities in the microwave oven at store A is 10 or more)” This is an example of “first condition data” and “first condition”. Similarly, the second rule data and the conditions included in the second rule data are examples of “second condition data” and “second condition”, respectively. The difference time is an example of “time information”.

The process of supplying the template data in S12 of FIG. 2 and the process of acquiring the first input template data in S18 are examples of processes executed by the “template data supply acquiring unit”. The process of acquiring and storing the first type of device data in S22 to S28 in FIG. 2 is an example of the process executed by the “device data acquisition storage unit”. The process of generating the first browsing data in S32 and S40 is an example of the process executed by the “browsing data generation unit”. The process of supplying the first browsing data in S34 and S42 is an example of the process executed by the “browsing data supply unit”. The process of generating the first type of aggregate data in S24 and S28 is an example of the process executed by the “aggregator”. The process of acquiring the first rule data in S60 of FIG. 3 is an example of the process executed by the “condition data acquisition unit”. The process of supplying the first notification signal in S64 of FIG. 3 is an example of the process executed by the “notification signal supply unit”.

(Second embodiment: FIGS. 22 and 23)
The second embodiment will be described focusing on the differences from the first embodiment. The basic configuration of the system of the communication system 2 of this embodiment is also common to that of the first embodiment. In the present embodiment, as shown in FIGS. 22 and 23, the method in which the first type device 50 generates the first type of device data is different from the first embodiment.

FIG. 22 also shows an example in which two types of events of type A and type B occur in the first type device 50. Also in the present embodiment, as shown in FIG. 22, when a specific event (B1 in FIG. 22) occurs, the first type device 50 has a previous event (in FIG. 22) of the specific event (B1). A difference time (T1) between the occurrence time (t1) of A1) and the occurrence time (t2) of the specific event (B1) is specified. In the present embodiment, the first type device 50 further specifies the type (A) of the previous event. The first type device 50 associates the device unique number (1001) of the first type device 50, the difference time (T1), and the type information indicating the type (A) of the previous event. As a result, as shown in FIG. 23, the first type of device data in which the device unique number, the difference time, and the type information are associated is generated.

In the first type device 50, when each signal after a specific signal is output, the type information (B, B, A...) And the difference time (T2, T3) are the same as described above. , T4... As a result, the first type of device data is generated even when each event after a specific event occurs. In the examples of FIGS. 22 and 23, the example in which the first type device 50 generates the first type of device data has been described, but when the second type device 60 generates the second type of device data, Same as above.

(Third embodiment: FIGS. 24 and 25)
The third embodiment will be described with a focus on differences from the first embodiment. The basic configuration of the system of the communication system 2 of this embodiment is also common to that of the first embodiment. Also in this embodiment, as shown in FIGS. 24 and 25, the method in which the first type device 50 generates the first type of device data is different from that of the first embodiment.

In the present embodiment, as shown in FIG. 24, the first type device 50 generates a first type event (B1 in FIG. 24) of a different type from the previous event (A1 in FIG. 24) that occurred last time. Then, the following processing is performed. That is, the first type device 50 monitors whether the second type event (A2) different from the first type event (B1) occurs. Further, when the second type event (A2) occurs, the first type device 50 has a period between the occurrence of the previous event (A1) and the occurrence of the second type event (A2). A difference time (T1) between the time (t1) when the first type event (B1) occurs and the time (t2) when the second type event (A2) occurs is specified. Furthermore, when the second type event (A2) occurs, the first type device 50 has a period between the occurrence of the previous event (A1) and the occurrence of the second type event (A2). The number of times (2 times; B1 and B2) that the same type of event as the first type event (B1) is output is specified. Further, the first type device 50 associates the type information (B) of the first type event, the specified differential time (T1), and the specified number of times (twice). As a result, as shown in FIG. 25, the first type of device data in which the device unique number, the difference time, the type information, and the output count are associated with each other is generated.

The first type device 50 also includes the type information (A, B, A...) And the difference time (T2, T2) in the same manner as described above even when each event after the second type event occurs. T3, T4...) And the number of outputs (3, 2, 1,...) Are specified. As a result, the first type of device data is also generated when each signal after the second type of signal is output. In the examples of FIGS. 24 and 25, the example in which the first type device 50 generates the first type of device data has been described. However, when the second type device 60 generates the second type of device data, Same as above.

(Fourth embodiment; FIGS. 26 and 27)
The fourth embodiment will be described with a focus on differences from the first embodiment. The basic configuration of the system of the communication system 2 of this embodiment is also common to that of the first embodiment. In this embodiment, as shown in FIGS. 26 and 27, the method of generating the first type of device data by the first type of device 50 is different from that of the first embodiment.

In the present embodiment, as shown in FIG. 26, the first type device 50 has a first type event (B1 in FIG. 26) of a different type from the previous event (A1 in FIG. 26) output last time. When output, the following processing is performed. That is, the first type device 50 monitors whether the second type event (A2) different from the first type event (B1) occurs. In addition, when the second type event (A2) occurs, the first type device 50 outputs the previous event (A1) at the time (t1) and immediately before the second type event (A2). The difference time (T1) from the output time (t2) of the generated first type event (B2) is specified. Furthermore, when the second type event (A2) occurs, the first type device 50 has a period between the occurrence of the previous event (A1) and the occurrence of the second type event (A2). The number of times (2 times; B1 and B2) that the same type of event as the first type event (B1) has occurred is specified. Further, the first type device 50 associates the type information (B) of the first type event, the specified differential time (T1), and the specified number of times (twice). As a result, as shown in FIG. 27, the first type of device data in which the device unique number, the difference time, the type information, and the output count are associated with each other is generated.

The first type device 50 also includes the type information (A, B, A...) And the difference time (T2, T2) in the same manner as described above even when each event after the second type event occurs. T3, T4...) And the number of outputs (3, 2, 1,...) Are specified. As a result, the first type of device data is also generated when each event after the second type of event occurs. In the examples of FIGS. 26 and 27, the example in which the first type device 50 generates the first type of device data has been described. However, when the second type device 60 generates the second type of device data, Same as above.

As mentioned above, although each Example was described in detail, these are only illustrations and do not limit a claim. The technology described in the claims includes various modifications and changes of the specific examples illustrated above. For example, the following modifications may be adopted.

(Modification 1) In each of the above embodiments, the device data generated by each device and transmitted to the server 10 includes a device unique number, type information, and a difference time. The device data generated by each device and transmitted to the server 10 is not limited to this, and may include a device unique number, type information, and time information. The time information indicates information indicating the occurrence time of an event that occurs in the device. In this modification, the server 10 receives device data (first type device data, second type device data) including time information from each device (first type device 50, second type device 60). get. The server 10 generates browsing data (first browsing data, second browsing data) using the device data stored in the memory. The time information in this modification is also an example of “time information”.

(Modification 2) When the first type device 50 and the second type device 60 specify the difference time, the number of digits (for example, an integer) is smaller than the number of digits that can actually be specified (for example, msec unit). The first type of device data may be generated by specifying in units of seconds. According to this modification, the capacity of the first type device data and the second type device data can be further compressed by reducing the number of digits of the difference time.

(Modification 3) In each of the above-described embodiments, every time the server 10 acquires the first type of device data from the first type of device 50, the server 10 counts the event occurrence status of the first type of device 50. The first type of aggregated data is generated (see S24 and S28 in FIG. 2). When the first browsing data request is acquired from the first browsing terminal 71, the server 10 generates the first browsing data using the already generated first type of aggregated data (FIG. 2). Of S32 and S40). The server 10 is not limited to this, and the server 10 may not generate the first type of aggregate data every time the first type of device data is acquired from the first type of device 50. For example, the server 10 may generate the first type of aggregate data every predetermined period. In another modification, the server 10 may not generate the first type of aggregate data even when acquiring the first type of device data. In that case, the server 10 may generate the first browsing data after the data is aggregated after the first browsing data request is acquired.

(Modification 4) In each of the above embodiments, each of the plurality of first type devices 50 is provided so as to be able to communicate directly with the server 10. Similarly, each of the plurality of second type devices 60 is provided so as to be able to directly communicate with the server 10. The communication system 2 is not limited to this, and the communication system 2 may have any configuration as long as each of the plurality of first type devices 50 and each of the plurality of second type devices 60 can communicate with the server 10. You may have. Therefore, for example, even if each of the plurality of first type devices 50 and each of the plurality of second type devices 60 can communicate with the server 10 via a relay router, a gateway, or the like. Good.

(Modification 5) In each of the above embodiments, the server 10 has the memory 24. However, the memory 24 may be configured as a storage device that is separate from the server 10. In that case, the server 10 and the storage device may be able to communicate with each other via a network (cloud network).

The technical elements described in this specification or the drawings exhibit technical usefulness alone or in various combinations, and are not limited to the combinations described in the claims at the time of filing. In addition, the technology illustrated in the present specification or the drawings achieves a plurality of objects at the same time, and has technical utility by achieving one of the objects.

Claims

A server that acquires device data from each of a plurality of devices and stores it in a memory,
Each device data is
Device identification information for identifying the specific device that is the source of the device data;
Time information related to the occurrence time of an event occurring in the specific device;
And type information indicating the type of the event that occurs in the specific device,
The plurality of devices include a plurality of first type devices and a plurality of second type devices,
The server
A first setting terminal used by the first user to manage the plurality of first type devices, and a second setting terminal used by the second user to manage the plurality of second type devices. Supply template data for setting a mode for storing device data acquired from each of the plurality of devices in a memory to a setting terminal;
From the first setting terminal, obtain first input template data input according to the template data,
A template data supply / acquisition unit for acquiring second input template data input according to the template data from the second setting terminal;
First type device data is acquired from each of the plurality of first type devices, and the acquired first type device data is obtained in accordance with a first format included in the first input template data. Stored in the first memory,
Second type device data is obtained from each of the plurality of second type devices, and the obtained second type device data is obtained in accordance with a second format included in the second input template data. A device data acquisition and storage unit for storing in the second memory;
Based on the first type of stored data which is the first type of device data obtained from the plurality of first type devices and stored in the first memory, the plurality of first type Generating first browsing data indicating the occurrence of each event on the device;
Based on the second type of stored data that is the first type of device data obtained from the plurality of second type devices and stored in the second memory, the plurality of second type A browsing data generation unit that generates second browsing data indicating the occurrence status of each event in the device;
Supplying the first browsing data to the first browsing terminal of the first user;
A browsing data supply unit for supplying the second browsing data to the second browsing terminal of the second user;
A server comprising
The time information includes difference time information indicating a difference time between each event occurring in the specific device.
The server of claim 1.
The first format includes first base structure information related to the location of the plurality of first type devices, and the second format includes the location of the plurality of second type devices. Including second site structure information related to
The browsing data generation unit
When a first browsing data request including information on a first base is acquired from the first browsing terminal, the first type of stored data and the first base structure information included in the first base structure information And generating the first browsing data based on the information on the base of
When a second browsing data request including information on the second site is acquired from the second browsing terminal, the second type of stored data and the second site structure information included in the second site data are included. The server according to claim 1, wherein the second browsing data is generated based on information on two bases.
The server
Aggregating at least a part of the first type of stored data to generate first type aggregated data,
A totaling unit that aggregates at least a part of the second type of stored data and generates second type totaled data;
The browsing data generation unit
The first browsing data can be generated using the first type of aggregated data,
4. The server according to claim 1, wherein the second browsing data can be generated using the second type of aggregate data. 5.
The server further includes:
From the first setting terminal, obtain first condition data indicating a first condition for causing the server to supply a first notification signal;
A condition data acquisition unit for acquiring second condition data indicating a second condition for causing the server to supply a second notification signal from the second setting terminal;
When the first condition is satisfied by the first type of stored data after the first condition data is acquired, the first notification signal is supplied to the first viewing terminal;
A notification for supplying the second notification signal to the second viewing terminal when the second condition is satisfied by the second type of stored data after the second condition data is acquired. The server according to claim 1, comprising a signal supply unit.
The browsing data generation unit
Based on the first type of stored data, the first type of event occurred between the occurrence of the first event and the occurrence of the first event again in each of the plurality of first type devices. The first browsing data including the number of events of two can be generated;
Based on the stored data of the second type, in each of the plurality of second type devices, a third event that occurs between the occurrence of the third event and the occurrence of the third event again. The server according to claim 1, wherein the second browsing data including the number of events of 4 can be generated.