JP2023040842A - Communication system, communication device, and communication method - Google Patents

Abstract

To optimize the amount of data communication for an entire communication terminal group when a comprehensive line contract is concluded, in a communication system.SOLUTION: A communication device management server calculates a transmission cycle correction value for each group based on an amount of used data and distributes it to a communication device. The communication device corrects and updates a data collection cycle for each group based on the transmission cycle correction value, and collects data from subordinate apparatuses based on the corrected update data collection cycle.SELECTED DRAWING: Figure 1

Description

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

In recent years, there have been an increasing number of cases where communication devices such as wireless routers perform primary processing of data, various processing such as protocol conversion, etc. as edge devices. Furthermore, FOTA (Firmware Over The Air) technology is being established for updating and adding these applications (functions) including communication functions.

The edge device mainly plays the role of collecting data from devices under its control and transmitting it to the server. Many examples of IoT systems utilize mobile lines such as LTE for communication networks. For mobile lines, it is common for each contract to set an upper limit on the amount of data communication in one month. For this reason, edge devices often reduce the amount of data to be transmitted by extracting necessary information by performing primary processing of data, changing the transmission cycle, and assigning transmission priority to each data.

For example, in Patent Document 1, data transmission rules for communication data are based on communication condition information including communication cost conditions and priority conditions for each data type, and charge information representing a charge system for communication. to decide. This provides a communication control system capable of immediately notifying high-priority important data while communicating so as to keep the communication cost within the budget.

JP 2015-069403 A

In general, the amount of data that can be used by communication devices is limited. However, when a large number of communication devices are connected to the line, the upper limit of the line contract is often set as the total value of the communication traffic of all the communication devices.

In the case of Patent Document 1, the data communication volume is optimized for each communication device, but when a comprehensive line contract is made, the data communication volume is optimized for the entire edge device group. do not have. For this reason, even if there is a sufficient amount of remaining data for the group of communication devices as a whole, there is a possibility that the amount of communication for each communication device will be limited.

In addition, when unpredictable communication occurs, such as an update (FOTA) of the communication device itself, there is a possibility that the communication volume will be miscalculated and the maximum charge will be exceeded.

SUMMARY OF THE INVENTION An object of the present invention is to optimize the amount of data communication for the entire communication terminal group when a comprehensive line contract is concluded in a communication system.

A communication system according to one aspect of the present invention is a communication system including a communication device management server and a plurality of communication devices connected to the communication device management server via a network, wherein the plurality of communication devices are: Each belongs to a different group, is connected to each of the subordinate devices, collects data from the subordinate devices based on a preset data collection cycle, and sends the communication device management server to the communication device management server at regular intervals as the amount of data used as the amount of communication. and the communication device management server calculates a transmission cycle correction value for each group based on the amount of data used and distributes it to the communication device, and the communication device calculates the transmission cycle correction value based on the transmission cycle correction value Then, the data collection cycle is corrected and updated for each group, and the data is collected from the subordinate devices based on the corrected update data collection cycle.

According to one aspect of the present invention, in a communication system, when a comprehensive line contract is concluded, it is possible to optimize the amount of data communication for the entire communication terminal group.

1 is a diagram showing the overall configuration of a communication system of Example 1; FIG. 3 is a diagram illustrating a hardware configuration of a communication device management server of Example 1; FIG. FIG. 4 is a diagram showing communication device registration data according to the first embodiment; FIG. 10 is a diagram showing data collection settings in Example 1; FIG. 10 is a diagram showing data collection setting registration data of Example 1; FIG. 10 is a diagram showing data amount setting in Example 1; 4 is a diagram showing a WAN-side data amount log of Example 1. FIG. 4 is a diagram showing data capacity information in Example 1. FIG. 3 is a diagram illustrating the hardware configuration of the communication device of Example 1; FIG. FIG. 4 is a diagram showing serial communication settings according to the first embodiment; FIG. 4 is a diagram showing LAN communication settings according to the first embodiment; 4 is a WAN-side data amount recording file of Example 1. FIG. FIG. 10 is a diagram showing a GUI of a menu screen in Example 1; FIG. 10 is a diagram showing a GUI of a communication device registration screen according to the first embodiment; FIG. FIG. 10 is a diagram showing a GUI of a data collection setting registration screen according to the first embodiment; FIG. 10 is a diagram showing a GUI of a data amount setting screen in Example 1; 4 is an inquiry processing flow of the server cooperation unit in the communication device of the first embodiment; FIG. 10 is inquiry data transmitted to the communication device management server by the server cooperation unit in the communication device according to the first embodiment; FIG. 4 is a processing flow of WAN-side communication data amount measurement by a WAN-side communication unit in the communication apparatus of the first embodiment; 7 is a processing flow of a WAN-side communication data amount response of a WAN-side communication unit in the communication apparatus according to the first embodiment; 7 is a processing flow of waiting for an inquiry by the communication device management unit in the communication device management server of the first embodiment; FIG. 10 is inquiry response data transmitted to the communication device by the communication device management unit in the communication device management server of the first embodiment; FIG. 7 is a processing flow of transmission cycle correction value calculation of the communication device management unit in the communication device management server of the first embodiment; 7 is a processing flow of waiting for a communication setting notification of the local communication unit in the communication device of the first embodiment; 4 is a processing flow of data collection by the local communication unit in the communication device of the first embodiment; FIG. 10 is a diagram showing data collection settings of Example 2; 10 is a processing flow of data collection by a local communication unit in the communication device of Example 2; FIG. 12 is a diagram showing communication device registration data of the third embodiment; 10 is a processing flow of waiting for an inquiry by the communication device management unit in the communication device management server according to the third embodiment; FIG. 13 is a diagram showing communication device registration data of Example 4; FIG. 11 is a process flow of waiting for an inquiry by the communication device management unit in the communication device management server of the fourth embodiment; FIG. FIG. 13 is a diagram showing data amount settings in Example 5; FIG. 21 is a diagram showing a GUI of a data amount setting screen of Example 5; FIG. 11 is a processing flow of waiting for an inquiry by a communication device management unit in a communication device management server according to a fifth embodiment; FIG.

Hereinafter, this embodiment will be described with reference to the drawings. However, the present invention should not be construed as being limited to the contents of the examples described below. Those skilled in the art will easily understand that the specific configuration can be changed without departing from the idea or gist of the present invention.

In the configurations of the invention described below, the same or similar configurations or functions are denoted by the same reference numerals, and overlapping descriptions are omitted.

FIG. 1 is a diagram showing the overall configuration of a communication system according to the first embodiment.
The communication system comprises a communication device management server 100 , user equipment 110 , communication device 120 , subordinate device 130 and mobile communication network 140 .

A plurality of communication devices 120 are connected to the communication device management server 100 via a mobile communication network 140 . A plurality of communication devices 120 belong to different groups and are connected to subordinate devices 130 respectively.

The communication device management server 100 is a server installed to collectively manage the communication devices 120 . The user equipment 110 is a server or network device installed by the user of the communication device 120 to collect information on the subordinate device 130, and a PC or the like for accessing the communication device management server.

The communication device is a communication device that performs information transmission of the subordinate device 130 to the user equipment 110 via the communication system 1 and communication for management via the communication system 2 .

The subordinate equipment 130 is industrial equipment or information equipment. For example, servers, air compressors, inverters, and the like correspond to the subordinate devices 130 . Further, sensors for outputting temperature, humidity, and the like may be installed as subordinate devices 130 .

The mobile communication network 140 is assumed to be an LTE line or the like, and is a wireless communication network and a backbone communication network that can be used by paying a monthly charge to a communication carrier.

The communication device management server 100 has a setting DB 101 , a tally DB 102 , a GUI generation section 103 , a communication device management section 104 and a communication section 105 .

The setting DB 101 is a database that stores setting values related to the communication device management server 100 and the communication device 120 . The tally DB 102 is a database that stores tally values related to communication traffic of the communication device 120 and data required for tallying.

The GUI generation unit 103 returns screen data (HTML) to access using HTTP and stores setting values. The communication unit 105 transmits and receives data to and from the user equipment 110 and the communication device 120 .

The communication device management unit 104 stores the data received from the communication device 120 in the aggregation DB 102 and manages the amount of data based on the information stored in the setting DB 101 . The communication unit 105 performs data communication with the communication device 120 .

The communication device has 120 , a server cooperation unit 121 , a WAN communication unit 120 and a local communication unit 123 . The server coordinating unit 121 communicates with the communication device management unit 104 of the communication management server 100 using the communication system 2 to update the set values related to information collection contents and collection cycles from the subordinate device 130 .

The WAN communication unit 122 relays communication performed by the server cooperation unit 121 and the local communication unit 123 via the mobile communication network 140 and measures the amount of data sent and received to the mobile communication network 140 . The subordinate device 130 has operating information 131 and setting information 132 .

The operating information 131 is, for example, information such as the memory usage rate of the information equipment and the number of revolutions per hour of the motor in the industrial equipment. The setting information 132 is information such as a setting file of a program executed by the information equipment and a setting value of the motor rotation speed of the industrial equipment.

The local communication unit 123 of the communication device 120 communicates with the subordinate device 130 according to the setting values, and periodically collects the operation information 131 and the setting information 132 .

FIG. 2 is a diagram showing the hardware configuration of the communication device management server 100 of the first embodiment.
The communication device management server 100 has a form in which a CPU 200, a main memory device 201, an auxiliary memory I/F 202, an input/output I/F 203, and a network I/F 204 are connected by a bus.

The CPU 200 controls each part of the communication device management server 100, loads necessary programs into the main storage device 201, and executes them. The main memory device 210 is generally composed of a volatile memory such as a RAM, and stores programs executed by the CPU 200 and data to be referred to.

The auxiliary storage I/F 202 is an interface for connecting auxiliary storage devices such as HDDs and SSDs. The input/output I/F 202 is an interface for connecting input/output devices such as a keyboard and a mouse. A network I/F 204 is an interface for connecting with a network.

The auxiliary storage device 201 has a large storage capacity, and stores programs for executing this embodiment. A DBMS 210 , a GUI generation program 211 , a device management program 212 and a communication program are installed in the communication device management server 100 .

The DBMS 210, the GUI generation program 211, the device management program 212, and the communication program are programs that implement the functions of the setting DB 101, total DB 102, GUI generation section 103, and communication device management section 104, respectively.

The setting DB 101 is a database that manages a plurality of setting data. The setting DB 101 stores communication device registration data 213 , data collection settings 214 , data collection setting registration data 215 , and data amount settings 216 .

The communication device registration data 213 is data describing information on the communication device 120 managed by the communication device management server 100 . The data collection settings 214 are settings related to data collection executed by the communication device 120 . The data collection setting 214 is data that the communication device 120 refers to when it obtains data from the subordinate device 130. For each piece of data to be obtained, the data acquisition destination, data details, communication method, and collection cycle setting are described. . The setting DB 101 manages a plurality of data collection settings applied to the communication device 120 . The data collection setting registration data 215 is data for recording correspondence between the communication device 120 and data collection settings.

The data amount setting 214 is data that records the correspondence between the group of the communication device 120 and the setting related to the data amount. The tally DB 102 is a database that manages a plurality of tally data. The total DB 102 stores a WAN-side data amount log 217 and data amount information 218 .

The WAN-side data volume log 217 is log data that continuously records an increase in the transmission/reception data volume of each communication device 120 . The data capacity information 218 is data that records the usage status of data for each group composed of a plurality of communication devices.

FIG. 3 is a diagram showing communication device registration data 213 of the first embodiment.
The communication device registration data 213 has items of model name 301 , device ID 302 , group ID 303 , hardware ID 304 and IMEI 305 for each communication device 120 . Each item is explained below.

The model name 301 is a name indicating the model of the communication device 120 . A device ID 303 is an ID uniquely assigned to each communication device 120 . It is determined when the communication device 120 is shipped, written in an internal file of the communication device 120 , and written on a label attached to the communication device 120 .

A group ID 303 is an ID that distinguishes a group composed of a plurality of communication devices 120 . Normally, the group ID 303 is distinguished based on the shipping destination or the like.

A hardware ID 304 is an ID that distinguishes hardware of the communication device 120 . The hardware ID 304 is changed when there is a change in hardware such as a part change.

IMEI 305 indicates an "International Mobile Equipment Identifier" assigned to each communication module. An ID for identifying a communication module incorporated in communication device 120 .

FIG. 4 is a diagram showing data collection settings 214 of the first embodiment.
The data collection setting 214 has items of data name 401, connection destination ID 402, data storage destination 403, data length 404, data type 405, communication method 406, and period 407 for each data. Each item is explained below.

The data name 401 indicates the name of each data. The connection destination ID 402 is an identifier that uniquely identifies the subordinate device 130 .

The data storage destination 403 is information specifying a location where data is stored at the connection destination. For example, for Modbus-TCP/RTU, it indicates a register number.

A data length 404 indicates the number of bytes of data to be acquired.

A data type 405 indicates the data type of data to be acquired. For example, Int16B (big endian 16-bit integer type) and FloatL (little endian floating point type) are stored.

A communication method 406 indicates a method by which the communication device 120 communicates with the subordinate device 130 . In the case of the first embodiment, LAN or serial is assumed. A cycle 407 indicates a cycle in seconds at which the communication device 120 acquires data. When the cycle 407 is set to 0, data is transmitted when the communication device 120 is activated and when the acquired value changes.

FIG. 5 is a diagram showing the data collection setting registration data 215 of the first embodiment.
The data collection setting registration data 215 stores a device ID 501 and a data collection setting ID 502 for each line. Each item is explained below.

Device ID 501 is the same as device ID 302 of communication device registration data 213 . A data collection setting ID 502 is an ID assigned to each data collection setting. The data collection setting ID 502 is an ID described in the format of the date when the data collection setting is registered/generated, an "underscore", and a serial number, and the serial number is counted up each time the data collection setting is registered/generated. The count goes back to 1 when the date is changed. Although the serial number is described with five digits in this embodiment, the number of digits may be changed according to the scale of the system.

FIG. 6 is a diagram showing the data amount setting 216 of the first embodiment.
The data amount setting 216 stores the data capacity 602 and margin margin 603 for each group ID 601 . Each item is explained below.

Group ID 601 is the same as group ID 302 of communication device registration data 213 . The data capacity 602 indicates the data capacity per communication apparatus set for each group in units of megabytes (MBytes). The data capacity 602 is a value set mainly according to the mobile communication contract form.

A margin margin 603 indicates a set value that determines how much data in the total amount of data in the group specified by the group ID 601 is not used as a margin value. For example, in a group of 100 units, if each unit has a data capacity of 20 megabytes, the maximum data amount is 2000 megabytes. data collection in the remaining 1600 megabytes.

FIG. 7 is a diagram showing a WAN side data amount log of the first embodiment.
The WAN side data amount log 217 stores a device ID 701, a group ID 702, a time stamp 703, and a transmission/reception data amount 704 for each line. Each item is explained below.

The device ID 701 is the same as the device ID of the communication device registration data 213 . Group ID 702 is the same as the group ID of communication device registration data 213 . A time stamp 703 indicates the time when the log data of the same line was created.

The transmission/reception data amount 704 indicates the amount of increase in the transmission/reception data amount from the previous recording in the communication device 120 corresponding to the device ID 701 in the same row. The transmission/reception data amount 704 is calculated by the communication device management unit 104 based on the cumulative transmission/reception data amount transmitted from the communication device 120 .

FIG. 8 is a diagram showing the data capacity information 218 of the first embodiment.
The data capacity information 218 stores a group ID 801, total data amount 802, current month communication remaining amount 803, and transmission cycle correction value 804 for each group. Each item is explained below.

Group ID 801 is the same as the group ID of communication device registration data 213 . A data total amount 802 indicates the maximum amount of data that can be used for each group. The data total amount 802 is calculated by the communication device management unit 104 from the number of devices in each group and the data capacity per device.

The communication remaining amount 803 for the current month indicates the communication remaining amount obtained by subtracting the communication amount used during the current month from the data total amount 802 . The current month communication balance 803 is calculated by the communication device management unit 104 . The transmission cycle correction value 804 indicates a correction value calculated by the communication device management unit 104 from the current month communication balance 803 and the daily transmission/reception volume of each communication device.

FIG. 9 is a diagram showing the hardware configuration of the communication device 120 according to the first embodiment.
The communication device 120 has a form in which a CPU 900, a main storage device 901, a WAN communication I/F 902, a serial communication I/F 905, a LAN communication I/F 906, and an auxiliary storage I/F 904 are coupled by a bus.

The CPU 900 controls each part of the communication device 120, loads necessary programs into the main storage device 901, and executes them. A main storage device 901 is generally composed of a volatile memory such as a RAM, and stores programs executed by the CPU 900 and data to be referred to.

WAN communication I/F 902 is an interface for connecting with mobile communication network 140 . The input/output I/F 903 is an interface for connecting input/output devices such as a keyboard and a mouse. Auxiliary storage I/F 904 is an interface for connecting auxiliary storage devices such as EEPROM, HDD, and SSD.

The serial communication I/F 905 is an interface that connects with the serial communication I/F of the subordinate device 130 when performing serial communication with the subordinate device 130 such as Modbus-RTU. The LAN communication I/F 906 is an interface that connects with the LAN communication I/F of the subordinate device 130 when performing LAN communication such as Modbus-TCP with the subordinate device 130 .

The auxiliary storage device 910 has a large storage capacity, and stores a setting/record file 911 and a program for executing this embodiment. A server cooperation program 912 , a WAN communication program 913 , and a local communication program 914 are installed in the communication device 120 .

A server cooperation program 912, a WAN communication program 913, and a local communication program 914 are programs that implement the functions of the server cooperation unit 121, the WAN communication unit 122, and the local communication unit 123, respectively.

The setting/recording file 911 is classified into serial communication setting 915 , LAN communication setting 916 , data collection setting 917 , and WAN side data amount recording file 918 . The serial communication setting 915 is data for recording setting items and protocol settings necessary for serial communication with the subordinate device 130 .

The LAN communication setting 916 is data for recording setting items and protocol settings required for LAN communication with the subordinate device 130 . A data collection setting 917 is one of a plurality of data collection settings stored in the setting DB 101 of the communication device management server 100 .

The WAN-side data amount recording file 918 is a file that records information on the amount of communication via the mobile communication network 140 .

FIG. 10 is a diagram showing serial communication settings 915 of the first embodiment.
Serial communication setting 915 stores connection destination ID 1001, baud rate 1002, bit size 1003, parity 1004, stop bit 1005, and protocol 1006 for each communication target.

The connection destination ID 1001 is the same as the connection destination ID of the data collection settings. The baud rate 1002 indicates the communication speed (baud rate) of serial communication. Bit size 1003 indicates the bit length from the start bit to the stop bit in serial communication. Parity 1004 indicates an application scheme of error detection code bits in serial communication. Assumes none, even, and odd values to be stored.

A stop bit 1005 indicates the length of the stop bit in serial communication. A protocol 1006 indicates a protocol for serial communication. For example, Modbus-RTU is stored.

FIG. 11 is a diagram showing LAN communication settings 916 of the first embodiment.
The serial communication setting 916 stores a connection destination ID 1101, an IP address 1102, a port number 1103, and a protocol 1104 for each communication target.

The connection destination ID 1101 is the same as the connection destination ID of the data collection setting. The IP address 1102 indicates the IP address that is the destination of LAN communication. A port number 1103 indicates a destination TCP port number for LAN communication. A protocol 1104 indicates a protocol for LAN communication. For example, Modbus-TCP is stored.

FIG. 12 shows the WAN side data amount recording file 918 of the first embodiment.
The WAN-side data amount recording file 918 stores a previous value 1202 and an accumulated value 1203 for items 1201 of transmission and reception on the WAN side, respectively.

The previous value 1202 is an acquired value recorded at the end of processing when the WAN communication unit 122 measures the WAN side communication data amount. The amount of communication acquired from the WAN side interface when measuring the latest amount of communication data on the WAN side is stored.

The cumulative value 1203 is the cumulative transmission/reception data amount since the WAN side data amount recording file 918 was last cleared. Considering that the amount of communication acquired from the WAN side interface is reset when the power of the communication device 120 is turned off, the difference from the previous value is cumulatively added when measuring the amount of communication data on the WAN side.

FIG. 13 is a diagram showing the GUI of the menu screen 1300 of the first embodiment.
On the menu screen 1300, menu icons of communication device registration 1301, data collection setting 1302, and data amount 1303 are displayed. By selecting each icon, you can transition to a detailed setting screen.

FIG. 14 is a diagram showing the GUI of the communication device registration screen 1400 according to the first embodiment.
By selecting a file selection button 1401, a file selection screen is opened and a file of the PC being operated can be selected. After selecting the file, the file path of the selected file is displayed in the text box on the left of the file selection button 1401 .

By selecting the upload button 1402, the file selected by the operation when the file selection button 1401 was selected is uploaded. If the format of the file to be uploaded does not match the format of the communication device registration data 213, a message "The format is different" is displayed in a pop-up.

A template of the communication device registration data 213 can be downloaded by selecting the template download link 1403 . Any communication terminal 120 can be searched from the communication device registration data 213 by entering a character string in the search window 1404 . The search is executed by partial matching for all items. displayed on the screen. Note that when there is no input in the search window 1404, all items of the communication device registration data 213 are displayed on the screen.

By selecting a check box 1405, the communication device registration data display is checked. The check box on the first line checks all the lines displayed as search results.

The contents of the communication device registration data 213 are displayed in the communication device registration data display. Up to 30 items are displayed on one screen. A page scroll link 1407 is a link for displaying the next or previous 30 data when 30 or more data are registered in the communication device registration data 213 .

By selecting the selected terminal deletion button 1408, the data of the line with the check box 1405 checked is deleted. The deletion result is reflected in the communication device registration data 213 stored in the setting DB 101 . By selecting the link 1409 to the menu, the screen transitions to the menu screen.

FIG. 15 is a diagram showing the GUI of the data collection setting registration screen 1500 of the first embodiment.
By entering a character string in the search window 1501, any communication terminal 120 can be searched from the communication device registration data 213. FIG. The search is executed by partial matching for all items. displayed on the screen. Note that when there is no input in the search window 1501, all items of the communication device registration data 213 are displayed on the screen.

By selecting a check box 1502, the communication device registration data display is checked. Check boxes 1502 on the first line check all lines displayed as search results.

The contents of the communication device registration data 213 and a data collection setting download button 1504 are displayed in the communication device registration data display. Up to 30 items are displayed on one screen.

By selecting a data collection setting download button 1504, the data collection settings set in the communication device 120 on the same line can be downloaded. A page scroll link 1505 is a link for displaying the next or previous 30 data when 30 or more data are registered in the communication device registration data 213 .

By selecting a file selection button 1506, a file selection screen is opened and a file of the PC being operated can be selected. After selecting the file, the file path of the selected file is displayed in the text box to the left of the file selection button 1506 .

By selecting the template download link 1507, a template for data collection settings can be downloaded. By selecting the data collection setting registration button 1508, the data collection setting selected by the file selection button 1506 is associated with the communication device 120 of the line with the check box 1502 checked.

When the data collection setting registration button 1508 is selected, the data collection setting ID is assigned to the file selected by the file selection button 1506, uploaded to the setting DB 101, and the row with the data collection setting registration data check box 1502 checked. , the data collection setting ID corresponding to the device ID of the communication device 120 is updated. If the format of the selected file does not match the format of the data collection settings, a pop-up message will appear stating that the format is incorrect.

By keeping the cursor on the communication device registration data display for one second or longer, a data collection setting content display popup is displayed. The data collection setting content display popup displays the data collection settings applied to the communication device 120 on the line where the cursor is located.
By selecting the link 1510 to the menu, the screen transitions to the menu screen.

FIG. 16 is a diagram showing the GUI of the data amount setting screen 1600 of the first embodiment.
By entering a character string in the search window 1601, any group can be searched from the group ID display. The search is executed by partial matching, and if there is an item that even partially matches the character string and the group ID entered in the search window 1601, the group ID 1603 is displayed on the screen. Note that when there is no input in the search window 1601, all group IDs are displayed on the screen.

By selecting a check box 1602, the group ID display is checked. Check boxes 1602 on the first line mark all the lines displayed as search results. In the group ID display, items from the column of the group ID of the communication device registration data 213 are displayed without duplication. Up to 30 items are displayed on one screen.

A page scroll link 1604 is a link for displaying the next or previous 30 items when 30 items or more of data are displayed in the group ID display.

In the data volume input box 1605, the monthly data volume per communication device is entered numerically. In the margin margin input box 1606, the numerical margin is entered.

By selecting the setting reflection button 1607, the combination of the group ID, the data capacity, and the margin margin of the data amount setting is updated. If data other than numerical values are entered in the data capacity input box 1605 and margin margin input box 1606, a pop-up message "input value error" is displayed.

By keeping the cursor on the group ID display for one second or longer, a setting display popup 1608 is displayed. A setting display popup 1608 displays the data capacity and margin margin applied to the group ID of the line where the cursor is present.

FIG. 17 is a server inquiry processing flow of the server cooperation unit 121 in the communication device 120 of the first embodiment.
The operation of the server cooperation unit will be described below according to the items in the flowchart.

In S1700, when the communication device 120 is started and when 24 hours or more have passed since the previous execution of the server inquiry processing, the subsequent processing is started. It should be noted that the present invention does not fix the period to 24 hours, but allows the period to be set to any time.

In S1701, a data amount acquisition request is transmitted to the WAN communication unit 122, and the WAN side data amount is acquired. In S1702, the inquiry data stored in the communication device 120 is referenced, and the WAN transmission data amount and WAN reception data amount are updated to the values obtained in S1701 and S1702. The inquiry data updated in S1703 and S1702 is transmitted to the communication device management server 100 using the POST method of HTTPS.

In S1704, since HTTPS uses TCP, arrival at the communication device management server 100 can be confirmed by confirming reception of ACK. If the inquiry data transmitted in S1703 reaches the communication device management server 100, the process proceeds to S1705. If arrival at the communication device management server 100 cannot be confirmed, the process proceeds to S1710.

If responses to the requests sent in S1705 and S1703 are received, the process advances to S1706. If it has not been received, it waits for a certain period of time and executes the processing of S1705 again.

If the data collection setting is included in the inquiry response data from the communication device management server 100 received in S1706 and S1705, the process advances to S1707. If not included, the process proceeds to S1708.

The local communication unit 123 is notified of the data collection settings received in S1707 and S1705. Also, the value of the inquiry data is updated to the data collection setting ID received in S1705.

If the inquiry response data from the communication device management server 100 received in S1708 and S1705 includes the transmission cycle correction value, the process advances to S1709. If not included, the process proceeds to S1710. The local communication unit 123 is notified of the transmission cycle correction values received in S1709 and S1705.
(S1710) End the server inquiry process.

FIG. 18 shows query data transmitted to the communication device management server 100 by the server cooperation unit 121 in the communication device 120 of the first embodiment.
The inquiry data is a JSON file that can be referenced by the server cooperation unit 212 and is recorded in the communication device 120 . A device ID 1801, a group ID 1802, a data collection setting ID 1803, a WAN transmission data amount 1804, and a WAN reception data amount 1805 are stored in the inquiry data.

Values are written in the device ID 1801 and group ID 1802 when the communication apparatus 120 is shipped. The data collection setting ID 1803 is blank until the initial communication with the communication device management server 100 . At the time of initial communication, a value is written in S1707. The WAN transmission data amount 1804 and WAN reception data amount 1805 are blank until the first server inquiry process is executed. When the server inquiry process is executed, the value is written in S1702.

FIG. 19 is a processing flow of WAN side communication data amount measurement of the WAN communication unit 122 in the communication apparatus 120 of the first embodiment.
The operation of the WAN side communication unit will be described below according to the items in the flowchart.

In S1900, when the communication device 120 is activated or 30 minutes or more have passed since the previous measurement of the WAN side communication data amount, the subsequent processing is started. It should be noted that the present invention does not fix the period to 30 minutes, but allows the period to be set to an arbitrary time.

In S1901, the transmission/reception data amount is acquired from the WAN side interface as the current value. For example, ifconfig, which is a Linux (registered trademark) command, is used to acquire the data. In S1902, the WAN side data amount recording file is read, and the previous value and cumulative value for each of transmission and reception are acquired.

The current value acquired in S1903 and S1901 is compared with the previous value acquired in S1902, and if the current value is greater than the previous value, the process proceeds to S1904. If smaller, the process proceeds to S1905. S1904) and update by subtracting the previous value acquired in S1902 from the cumulative value acquired in S1902.

The current value obtained in S1901 is added to the cumulative value obtained in S1905 and S1902 to update the accumulated value. The current value obtained in S1906 and S1901 and the cumulative value updated in S1905 are used as the new previous value and cumulative value to update the WAN side data amount recording file 918 . In S1907, the WAN side communication data amount measurement ends.

FIG. 20 is a processing flow of a WAN side communication data amount response of the WAN communication unit 122 in the communication device 120 of the first embodiment.
The operation of the WAN communication unit 122 will be described below according to the items of the flowchart.

In S2000, the subsequent processing is started when the communication device 120 is activated. In S2001, it is checked whether an error or the like has occurred and an instruction to end processing has not been issued. If the end has been instructed, the process proceeds to S2006. If not, the process advances to S2002.

In S 2002 , it is checked whether a data amount acquisition request has been received from the server cooperation unit 121 . If received, the process proceeds to S2003. If not received, the process returns to S2001.

In S2003, the WAN side data volume recording file 918 is read, and the previous value and accumulated value of the transmission/reception data volume are acquired. The previous value and accumulated value of the amount of transmitted/received data acquired in S2004 and S2003 are returned.

In S2005, 0 is substituted for the total value of the transmitted/received data amount, and the WAN side data amount recording file is updated. In S2006, the processing of the WAN side communication data amount response is terminated.

FIG. 21 is a processing flow of waiting for an inquiry by the communication device management unit 104 in the communication device management server 100 of the first embodiment.
The operation of the device management unit will be described below according to the items in the flow chart.

In S2100, the subsequent processing is started when the communication device management server 100 is activated.
In S2101, it is checked whether an error or the like has occurred and an instruction to terminate processing has not been issued. If the termination has been instructed, the process proceeds to S2111. If not, the process advances to S2102.
In S<b>2102 , it is checked whether a request has been received from the communication device 120 via the communication unit 105 . If so, the process advances to S2103. If not received, the process returns to S2101. From the inquiry data acquired in S2103 and S2102, the device ID, group ID, WAN transmission data amount, and WAN reception data amount of the communication apparatus 120 that transmitted the request are acquired.

Get the time information at the time of processing and use it as a time stamp. The WAN transmission data amount and the WAN reception data amount are added to calculate the transmission/reception data amount. The device ID, group ID, time stamp, and transmission/reception data amount are added to the WAN side data amount log 217 of the aggregation DB 102 .

In S2104, the data collection setting registration data 215 is obtained from the setting DB 101. FIG. A data collection setting ID is obtained from the inquiry data obtained in S2105 and S2102. It is checked whether the data collection setting ID acquired in S2104 matches. If they match, the process proceeds to S2108. If they do not match, the process proceeds to S2106.

In S2106, the data collection setting of the data collection setting ID acquired in S2104 is searched from the setting DB 1010 and acquired. The data collection setting ID obtained in S2107 and S2104 and the data collection setting obtained in S2106 are stored in the JSON format in the response body of HTTPS.

In S2108, data capacity information corresponding to the group ID acquired in S2103 is acquired from the total DB 102. FIG. A transmission cycle correction value is acquired from the data volume information acquired in S2109 and S2108, and stored in the HTTPS response body. The HTTPS response body updated in S2110 and S2109 is transmitted via the communication unit 105 to the communication device 120 that is the source of the request. At S2111, the process of waiting for an inquiry is terminated.

FIG. 22 shows inquiry response data 2200 that the communication device management unit 104 in the communication device management server 100 according to the first embodiment transmits to the server cooperation unit 121 . The inquiry response data 2200 consists of a data collection setting key 2201 and a transmission cycle correction value key 2204 .

The data collection setting key 2201 includes a data collection setting ID key 2202 and a data key 2203 . The value of the data collection setting ID key 2202 is the data collection setting ID stored in S2107. The value of data key 2203 is the data collection setting stored in S2107. A transmission cycle correction value 2204 is a transmission cycle correction value stored in S2109.

FIG. 23 is a processing flow of transmission cycle correction value calculation of the communication device management unit 104 in the communication device management server 100 of the first embodiment.
The operation of the device management unit will be described below according to the items in the flow chart.

In S2300, when the communication apparatus 120 is activated or when 24 hours or more have passed since the previous calculation of the transmission cycle correction value, the subsequent processing is started. It should be noted that the present invention does not fix the period to 24 hours, but allows the period to be set to any time.

In S2301, data volume information is acquired from the total DB 102. FIG. In S2302, the time information at the time of processing is acquired, and if the date value is 1, the data amount setting is acquired from the setting DB 101 in S2303.

In S2304, the current month communication remaining amount of all rows in the data capacity information of the total DB 102 is updated. The updated value of the communication remaining amount for the current month is calculated by calculating the ratio of the total usable data amount from the margin margin of the data amount setting acquired in S2303, and then multiplying the calculated value by the total data amount of the data amount setting acquired in S2301. do.

One line of the data capacity information acquired in S2305 and S2301 is read. The processing from S2306 to S2310 is performed on one line of read information.

In S2306, the WAN side data amount log 217 that includes the group ID of the row read out in S2305 from the tally DB 102 and that has been added since the previous calculation of the transmission cycle correction value is acquired. All the values in the column of the amount of transmitted/received data in the WAN-side data amount log 217 acquired in S2307 and S2306 are added to calculate the increased amount of transmitted/received data per day. By subtracting the increase in transmission/reception data per day from the communication remaining amount of the current month of the row read in S2305, a new communication remaining amount of the current month is obtained.

The number of remaining days in the current month is calculated from the time information acquired in S2308 and S2302. After that, the number of remaining days in the current month is multiplied by the increase in transmission/reception data per day calculated in S2307 to calculate the expected traffic volume for the current month. The transmission cycle correction value is calculated by dividing the communication remaining amount of the row read in S2305 by the expected communication volume of the month, and multiplying it by the cycle correction value of the row read out in S2305. The calculated transmission cycle correction value is used as a new transmission cycle correction value.

The group ID read out in S2305, the total amount of data read out in S2305, the new communication remaining amount for the current month calculated in S2307, and the new transmission cycle correction value calculated in S2308 are added to one line for the data amount information read out in S2309 and S2305. As the data, the data capacity information of the total DB is updated.

If the row of data capacity information read out in S2310 and S2305 is information at the end, the process proceeds to S2311. If it is not the last information, the process returns to S2305. In S2311, the processing for calculating the transmission cycle correction value is terminated.

FIG. 24 is a processing flow of waiting for communication setting notification of the local communication unit 123 in the communication device 120 of the first embodiment.
The operation of the local communication unit will be described below according to the items in the flowchart.

In S2400, the subsequent processing is started when the communication device 120 is activated. In S2401, it is checked whether an error or the like has occurred and an instruction to terminate processing has not been issued. If the end has been instructed, the process proceeds to S2408. If not, the process advances to S2402.

In S2402, it is checked whether a notification has been received from the server cooperation unit 121. FIG. If received, the process proceeds to S2403. If not received, the process returns to S2401.

It is checked whether the notification from the server cooperation unit 121 received in S2403 and S2402 includes the data collection setting. If received, the process advances to S2404. If not received, the process proceeds to S2405.

The data is updated using the data collection settings received in S2404 and S2403 as new data collection settings. It is checked whether the notification from the server cooperation unit 121 received in S2405 and S2402 includes the transmission cycle correction value. If received, the process proceeds to S2406. If not received, the process proceeds to S2407. The data is updated using the transmission cycle correction value received in S2406 and S2405 as a new transmission cycle correction value.

In S2407, a reset command is sent to the thread executing the data collection process. At S2408, the communication setting notification waiting process is terminated.

FIG. 25 is a data collection processing flow of the local communication unit 123 in the communication device 120 of the first embodiment.
The operation of the local communication unit will be described below according to the items in the flowchart.

In S2500, the subsequent processing is started when the communication device 120 is activated. In S2501, it is checked whether an error or the like has occurred and an instruction to terminate processing has not been issued. If the termination has been instructed, the process proceeds to S2508. If not, the process advances to S2502.

In S2502, it is checked whether a reset command has been received from the thread that is waiting for the communication setting notification. If received, the process proceeds to S2503. If not received, the process returns to S2501.

At S2503, all periodic processing set by the data collection processing is stopped. Periodic processing is data collection processing that is executed according to a setting file, and collects data from the data storage destination of the connection destination defined by the setting file each time the period arrives, and transmits the collected data to the user equipment.

In S2504, the current settings are discarded, and the data collection settings, LAN communication settings, and serial communication settings are read. The configuration file group read out in S2505 and S2504 is checked to see if there are any deficiencies in the configuration files. Insufficiency of the setting file means, for example, that the data collection setting does not exist, or that the LAN communication setting or serial communication setting corresponding to the connection destination ID described in the data collection setting does not exist. If there is no defect and the file is normal, the process proceeds to S2506. If a defect is found, the process returns to S2501.

In S2506, the transmission cycle correction value is read. A plurality of periodic processes are set according to the setting file group read in S2507 and S2504. When setting the periodic processing, the period read from the data collection setting is multiplied by the transmission period correction value (fractional numbers are discarded) to determine the execution period of the periodic processing. After that, the periodic processing is continuously executed in another thread. At S2508, the data collection process ends.

According to the first embodiment, the transmission cycle correction value is updated for each group ID once every 24 hours. The transmission cycle correction value is distributed once every 24 hours when the communication device 120 makes an inquiry to the communication device management server 100 . The distributed transmission cycle correction value is notified to the local communication unit 123 of the communication device 120 .

The local communication unit 123 periodically collects data from the subordinate device 130 and transmits data to the user equipment by referring to the data collection setting, and corrects the data collection cycle by referring to the transmission cycle correction value. As a result, it becomes possible to control the amount of data used in consideration of the actual usage status of the amount of data for a group composed of a plurality of communication devices 120 .

In the first embodiment, the communication device 120 uniformly corrects all data collection cycles with the transmission cycle correction value. However, there may be data for which the data collection cycle should be fixed because it is directly linked to an abnormality in the device such as a warning of the subordinate device 130 . In the method of the first embodiment, the data collection period is adjusted collectively including these data, which may lead to a delay in discovering an abnormality in the device, leading to loss for the user.

Therefore, in the second embodiment, a cycle variable flag is introduced in the data collection settings. Also in the data collection processing of the local communication unit 123, the processing flow is changed to one in consideration of the cycle variable flag. Hereinafter, differences of the second embodiment from the first embodiment will be described with reference to the drawings.

FIG. 26 is a diagram showing data collection settings according to the second embodiment. A cycle variable flag 2600 is added as a difference from the first embodiment.
The cycle variable flag 2600 is a flag for determining whether the data collection cycle of the row is affected by the transmission cycle correction value. 0 is set when the period is to be changed in accordance with the value of the transmission period correction value, and 1 is set when the period is not to be changed.

FIG. 27 is a processing flow of data collection of the local communication unit 123 in the communication device 120 of the second embodiment. In the second embodiment, as a difference from the first embodiment, the processing of S2507 is divided into S2700 and S2701.
The operation of the local communication unit will be described below with respect to differences from the first embodiment.

In S2700, the cycle is multiplied by the transmission cycle correction value in the same manner as in S2507, and then cycle processing is set for the collected data in the rows in which the cycle variable flag in the data collection setting is 0.
In S2701, periodic processing is set without multiplying the period by the transmission correction value for the collected data in the row in which the period variable flag of the data collection setting is 1.

According to the second embodiment, the introduction of the cycle variable flag 2600 makes it possible to set whether or not to consider the transmission cycle correction value for each data. Although the effect of reducing the amount of data due to the transmission cycle correction value becomes weaker, it can be said that the probability of reaching the maximum amount of data due to the effect of the mechanism for continuously adjusting the amount of data and the margin margin is extremely rare.

As a result, it is possible to control the amount of data used in consideration of the actual usage status of the amount of data for a group composed of a plurality of communication devices 120 while maintaining the collection cycle for important data.

In Example 1 and Example 2, the data collection cycle in a group composed of a plurality of communication devices 120 is uniformly corrected with the transmission cycle correction value. However, the subordinate devices 130 of the communication device 120 include a wide variety of devices, from devices with low data acquisition priority such as sensors to devices that require optimization through constant device monitoring such as large industrial devices. exists.

In the method of the first embodiment, the data collection cycle cannot be changed for each communication device, and it is difficult to make settings considering subordinate devices. Moreover, in the method of the second embodiment, it is necessary to generate data collection settings for each communication device, which is time-consuming.

Therefore, in the third embodiment, a mechanism is introduced in which the cycle variable flag is applied to the communication device 120 as well, and the influence of the transmission cycle correction value can be adjusted for each communication device. Differences between the third embodiment and the second embodiment will be described below with reference to the drawings.

FIG. 28 is a diagram showing communication device registration data according to the third embodiment. As a difference up to the second embodiment, a cycle variable flag 2800 is added.
The cycle variable flag 2800 is a flag for determining whether the terminal on that row is affected by the transmission cycle correction value. 0 is set when the period is to be changed in accordance with the value of the transmission period correction value, and 1 is set when the period is not to be changed.

FIG. 29 is a process flow of waiting for an inquiry by the communication device management unit 104 in the communication device management server 100 of the third embodiment. As a difference up to the second embodiment, the processing of S2104 is replaced with S2900. Moreover, the processing of S2901 is added.
The operation of the communication device management unit will be described below with respect to differences up to the second embodiment.

In S2900, communication device registration data is acquired from the setting DB 101 in addition to the data collection setting registration data acquired in S2104. By referring to the communication device registration data acquired in S2901 and S2900, it is confirmed whether the cycle variable flag of the communication device 120 that is the source of the request is 1 or not. If it is 1, the process proceeds to S2109. If it is 0, the process proceeds to S2110.

According to the third embodiment, by introducing the cycle variable flag for each communication device, it becomes possible to set whether or not to consider the transmission cycle correction value for each communication device. As in the second embodiment, although the data amount reduction effect due to the transmission cycle correction value is reduced, the probability of reaching the maximum data amount due to the effect of the mechanism for continuously adjusting the data amount and the margin margin is extremely rare. I can say there is.

As a result, while maintaining the collection cycle for the communication device 120 connected to the important subordinate device 130, the group composed of a plurality of communication devices 120 can be used in consideration of the actual usage of the amount of data. Data amount control becomes possible.

Up to the third embodiment, the method of flexibly changing the data collection period for each communication device 120 or data in a group composed of a plurality of communication devices 120 has been described. However, if the types of subordinate devices 130 of the communication device 120 are diverse in the group, there is a possibility that the period adjustment may not be sufficient by distinguishing between the fixed period and the transmission period correction value.

For example, it is assumed that there are three types of sensors: low-priority sensors that are acquired only for reference, industrial equipment that is used at production sites, and industrial equipment that is arranged in the power supply system of the entire factory.

Sensors that have low priority and only acquire data for reference can be used in small quantities and in low cycles, and industrial equipment used in production sites requires control that is large in volume and does not fall below the minimum cycle, and is installed in the power supply system of the entire factory. The industrial equipment used shall be in small quantities and the cycle shall not be reduced.

In this case, the effect of reducing the amount of data is small even if only the sensor is made cycle-variable, and it is unnatural to collect the industrial equipment used in the production site in the same cycle as the sensor. Considering such a case, in the fourth embodiment, the communication device 120 is configured to be able to set the priority according to the subordinate device 130 . Differences between the fourth embodiment and the third embodiment will be described below with reference to the drawings.

FIG. 30 is a diagram showing communication device registration data of the fourth embodiment. A priority of 3000 is added as a difference up to the third embodiment.
A priority 3000 is a priority set according to the subordinate device 130 connected to the communication device 120 . The priority is given by a numerical value, and in the fourth embodiment, 100 is the maximum and 0 is the minimum. A higher number has a higher priority, and a lower number has a lower priority. In addition, the present invention can obtain the same effect regardless of the numerical range of the priority.

FIG. 31 is a process flow of waiting for an inquiry by the communication device management unit 104 in the communication device management server 100 of the fourth embodiment. As a difference up to the third embodiment, the processing of S3100 is added. Regarding S2901 of the third embodiment, the description is omitted in the fourth embodiment because the processing can be performed in the same way regardless of whether the processing is included or not.
The operation of the communication device management unit will be described below with respect to differences up to the third embodiment.

In S3100, the communication device registration data acquired in S2900 is referred to, and the average value of the priority in the group to which the communication device 120 that is the source of the request belongs is calculated. After that, a priority correction value is calculated by dividing the priority of the communication device 120, which is the transmission source of the request, by the calculated average value. For example, if the average is 50 and the priority of the communication device 120 is 75, the priority correction value is 1.5. A transmission cycle correction value is acquired from the data volume information acquired in S2108, and a value obtained by multiplying the priority correction value is updated as a new transmission cycle correction value.

According to the fourth embodiment, by setting a priority corresponding to the subordinate device 130 to the communication apparatus 120, correction corresponding to the priority is additionally executed with respect to the transmission cycle correction. This makes it possible to adjust the data collection cycle of the communication device 120 according to the importance of the connected subordinate device 130 .

Up to the fourth embodiment, a method of flexibly changing the data collection cycle for each communication device 120 and each data in a form of giving priority to the communication device 120 connected to an important device in a group composed of a plurality of communication devices 120 has been described. bottom. However, there are cases where incorrect data collection settings are given due to human error, or communication devices 120 appear that waste more data than expected during collection. At this time, if these communication devices are prioritized with high priority, there is a possibility that the amount of data will be consumed unnecessarily.

The fifth embodiment introduces a setting item for performing correction based on the amount of data consumed for each group. In the correction based on the consumption data amount, the transmission cycle correction value is additionally corrected so as to reduce the transmission data amount for the communication device with the large consumption data amount in the same group. Differences between the fifth embodiment and the fourth embodiment will be described below with reference to the drawings.

FIG. 32 is a diagram showing data amount setting in the fifth embodiment. As a difference up to the third embodiment, a consumption data amount correction flag 3200 is added.
The consumption data amount correction flag 3200 is a flag for determining whether or not to correct the data collection period according to the consumption data amount within the group having the same group ID.

FIG. 33 is a diagram showing the GUI of the data amount setting screen of the fifth embodiment. As a difference up to the third embodiment, a consumption data amount correction check box 3300 is added.
When the setting reflection button is pressed with the data consumption correction check box 3300 selected, the data amount is changed with the consumption data amount correction flag set to 1 for the group of the group ID whose check box is checked. Settings are updated.

FIG. 34 is a process flow of waiting for an inquiry by the communication device management unit 104 in the communication device management server 100 of the fifth embodiment.

As a difference up to the fourth embodiment, the processing of S2104 is replaced with S3400. Also, the processing of S2108 is replaced with S3401. In addition, processing of S3402 and S3403 is added. S2901 of the third embodiment and S3100 of the fourth embodiment can be similarly processed regardless of whether the processing is included or not. The operation of the communication device management unit will be described below with respect to differences up to the fourth embodiment.

In S3400, in addition to the data collection setting registration data acquired in S2104, the data amount setting is acquired from the setting DB 101. FIG. In S3401, in addition to the data volume information acquired in S2108, the WAN side data volume log is acquired from the aggregation DB 102. FIG. The WAN side data amount log acquires the latest logs of all communication devices in the group to which the communication device that is the source of the request belongs.

The data amount setting acquired in S3402 and S3400 is referred to, and the consumption data amount correction flag of the group to which the communication device 120 that is the source of the request belongs is confirmed. If the consumption data amount correction flag is 1, the process proceeds to S3402. If the consumption data amount correction flag is 0, the process proceeds to S2109.

The average value of the amount of transmitted/received data in the latest logs of all the communication devices 120 in the group to which the communication device 120 which is the source of the request acquired in S3403 and S3401 belongs is acquired. After that, the data consumption correction value is calculated by dividing the transmission/reception data amount of the communication device 120, which is the transmission source of the request, by the calculated average value. A transmission cycle correction value is acquired from the data volume information acquired in S2108, and a value obtained by multiplying the consumption data amount correction value is updated as a new transmission cycle correction value.

According to the fifth embodiment, the consumption data amount correction flag determines whether or not to perform correction based on the consumption data amount for each group. If the consumption data amount correction flag is valid, the transmission cycle correction value is additionally corrected so as to reduce the transmission data amount for the communication device with a large amount of data consumption within the same group.

As a result, if an incorrect data collection setting is given due to human error, or if a communication device 120 wastes a larger amount of data than expected during collection, the communication device 120 is considered to be normal. Therefore, it is possible to prevent a situation in which a large amount of data is transmitted.

In the above embodiment, the communication device management server 100 that manages the communication device 120 is installed, and the communication device 120 to be managed is registered in the communication device management server 100 . The communication device 120 records the amount of communication and transmits the amount of communication to the communication device management server 100 at regular intervals. The communication device management server 100 records the amount of communication received, and calculates the monthly data communication remaining amount according to the number of communication devices 120 to be managed. The communication device management server 100 calculates a data transmission cycle correction value based on the remaining amount of data communication, the number of days until the end of the month, and the number of communication devices, and transmits the correction value to the communication device.

According to the above embodiment, in an IoT system with a comprehensive line contract, it is possible to optimize the amount of data for a group of terminals instead of optimizing the amount of data for each terminal.

100 communication device management server 110 user equipment 120 communication device 130 subordinate device 140 communication network 101 setting DB
102 Aggregation DB
103 GUI generation unit 104 Communication device management unit 105 Communication unit 121 Server cooperation unit 122 WAN communication unit 123 Local communication unit

Claims (15)

A communication system comprising a communication device management server and a plurality of communication devices connected to the communication device management server via a network,
the plurality of communication devices,
belong to different groups,
connected to each subordinate device,
collecting data from the subordinate devices based on a preset data collection cycle, and transmitting the amount of data used as the amount of communication to the communication device management server at regular intervals;
The communication device management server,
calculating a transmission cycle correction value for each group based on the amount of data used and distributing it to the communication device;
The communication device
correcting and updating the data collection cycle for each group based on the transmission cycle correction value;
A communication system that collects the data from the subordinate device based on the corrected update data collection period. The communication device
setting whether or not to consider the transmission cycle correction value for each of the data;
when the transmission cycle correction value is set not to be considered, collecting the data from the subordinate device based on the data collection cycle;
When set in consideration of the transmission cycle correction value,
2. The communication system according to claim 1, wherein the data is collected from the subordinate device based on the update data collection cycle. The communication device
introducing a cycle variable flag for determining whether the data collection cycle is affected by the transmission cycle correction value;
3. The communication system according to claim 2, wherein whether or not to consider the transmission cycle correction value is set for each data with reference to the cycle variable flag. The communication device management server,
setting whether or not to consider the transmission cycle correction value for each of the communication devices belonging to the group;
The communication device set not to consider the transmission cycle correction value,
Collecting the data from the subordinate device based on the data collection cycle;
The communication device set considering the transmission cycle correction value,
2. The communication system according to claim 1, wherein the data is collected from the subordinate device based on the update data collection cycle. The communication device management server,
introducing a cycle variable flag for determining whether the communication terminal is affected by the transmission cycle correction value;
5. The communication system according to claim 4, wherein whether or not to consider the transmission cycle correction value is set for each communication device by referring to the cycle variable flag. The communication device management server,
setting a priority according to the subordinate device for the communication device;
re-correcting and updating the transmission cycle correction value based on the set priority;
The communication device
2. The communication system according to claim 1, wherein the data is collected from the subordinate device based on the re-corrected update data collection period. The communication device management server,
calculating the amount of data used as the amount of data consumed by the communication device;
recorrecting and updating the transmission cycle correction value using the calculated consumption data amount;
The communication device
2. The communication system according to claim 1, wherein the data is collected from the subordinate device based on the re-corrected update data collection period. The communication device management server,
8. The transmission cycle correction value is re-corrected with reference to a consumption data amount correction flag for determining whether or not to correct the data collection period according to the consumption data amount. communication system. The communication device management server,
having a communication unit and a communication device management unit,
The communication unit
mutually transferring data exchanged between the communication device and the communication device management unit;
The communication device management unit
calculating, for each group, the amount of actual data that can be used each month based on the data amount per communication device and a margin determined by the user;
calculating a communication remaining amount by referring to the actual data amount and the data amount information received from the communication device;
The communication device
having a WAN communication unit, a server cooperation unit and a local communication unit,
The WAN communication unit
performing WAN communication and recording the amount of WAN communication as the amount of data used;
The server cooperation unit
periodically transmitting the WAN communication volume acquired from the WAN communication unit to the communication device management server;
The local communication unit
2. The communication system according to claim 1, wherein the data is periodically collected from the subordinate device and transmitted to the outside via the WAN communication unit. The communication device management unit of the communication device management server,
calculating the transmission cycle correction value based on the remaining communication amount, the number of days until the end of the month, and the number of the communication devices belonging to the group, and transmitting the correction value to the communication device via the communication unit;
The local communication unit of the communication device,
10. The communication system according to claim 9, wherein the data collection cycle is corrected and updated for each group based on the transmission cycle correction value. The communication device management unit of the communication device management server,
managing whether or not to correct the data collection period collected by the local communication unit for each communication device;
10. The communication system according to claim 9, wherein the correction value of the data collection cycle is not answered in response to an inquiry from the communication device that does not correct the data collection cycle. The subordinate device is
2. The communication system according to claim 1, comprising an industrial device, an information device, or a sensor. A communication device connected to a communication device management server via a network,
The communication device
belong to a group composed of a plurality of different communication devices,
Based on the preset data collection cycle, data is collected from subordinate devices,
correcting and updating the data collection cycle for each of the groups based on the transmission cycle correction value calculated by the communication device management server;
A communication device that collects the data from the subordinate device based on the corrected update data collection cycle. The subordinate device is
14. The communication device according to claim 13, comprising an industrial device, an information device, or a sensor. A communication method for a communication system having a communication device management server and a plurality of communication devices,
making the plurality of communication devices belong to different groups,
connecting each of the plurality of communication devices to a subordinate device;
In the communication device,
collecting data from the subordinate devices based on a preset data collection cycle, and transmitting the amount of data used as the amount of communication to the communication device management server at regular intervals;
In the communication device management server,
calculating a transmission cycle correction value for each group based on the amount of data used and distributing it to the communication device;
In the communication device,
correcting and updating the data collection cycle for each group based on the transmission cycle correction value;
A communication method, comprising collecting the data from the subordinate device based on the corrected update data collection cycle.

Images