COMMUNICATION SYSTEM, COMMUNICATION DEVICE, AND COMMUNICATION METHOD
The communication system optimizes data communication for groups of devices by adjusting collection cycles and distributing correction values, addressing individual device limitations and unpredictable usage in comprehensive contracts.
Patent Information
- Application Number
- JP2021148021
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2021-09-10
- Publication Date
- 2024-11-29
- Estimated Expiration
- 2041-09-10
AI Technical Summary
In communication systems with comprehensive line contracts, optimizing data communication for individual communication devices can result in insufficient data for each device, even when the total group has sufficient data, and unpredictable communication events like FOTA updates can lead to exceeding data limits.
A communication system with a management server that adjusts data collection cycles for groups of devices based on usage, distributing transmission cycle correction values to optimize data communication across multiple devices.
This approach ensures optimal data communication for the entire group of devices, preventing individual device data limits and managing unexpected data usage effectively.
Smart Images

Figure 0007591999000001 
Figure 0007591999000002 
Figure 0007591999000003
Abstract
Description
[Technical field]
[0001] The present invention relates to a communication system, a communication device, and a communication method. [Background technology]
[0002] In recent years, there has been an increase in cases where communication devices such as wireless routers are used as edge devices to perform various processes such as primary data processing and protocol conversion. Furthermore, FOTA (Firmware Over The Air) technology, which updates and adds these applications (functions), including communication functions, is becoming established.
[0003] The main role of edge devices is to collect data from devices under their control and send it to a server. Many examples of IoT systems use mobile lines such as LTE as their communication network. Mobile lines generally have a monthly data communication limit set for each contract. For this reason, edge devices often extract necessary information and reduce the amount of data sent by performing primary data processing, changing the transmission cycle, and assigning transmission priorities to each type of data.
[0004] For example, in Patent Document 1, data transmission rules for communication data are determined based on communication condition information including conditions for communication costs and conditions for priority for each data type, and fee information indicating a fee system for communication. This provides a communication control system that can immediately notify important data with high priority while communicating so that communication costs are within a budget. [Prior art documents] [Patent documents]
[0005] [Patent Document 1] JP 2015-069403 A Summary of the Invention [Problem to be solved by the invention]
[0006] Generally, the amount of data that a communication device can utilize is limited. However, when a large number of communication devices are connected to a line, the upper limit of the line contract is often set to the total value of the communication volume of all communication devices.
[0007] In the case of Patent Document 1, the data traffic per communication device is optimized, but when a comprehensive line contract is made, the data traffic is not optimized for the entire edge device group. Therefore, even if there is sufficient remaining data when looking at the entire communication device group, there is a possibility that the communication traffic of each communication device may be restricted.
[0008] In addition, when unpredictable communications occur, such as updates to the communications device itself (FOTA), there is a possibility that the calculation of communication volume may be off, resulting in the upper limit being exceeded.
[0009] An object of the present invention is to optimize the amount of data communication for an entire group of communication terminals in a communication system when a comprehensive line contract is made. [Means for solving the problem]
[0010] A communication system according to one embodiment of the present invention has 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 each belong to a different group, are each connected to a subordinate device based on a predetermined data collection period, collect data from the subordinate devices based on a predetermined data collection period, and transmit the amount of data used as communication volume to the communication device management server at regular intervals, 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 devices, and the communication devices correct and update the data collection period for each group based on the transmission cycle correction value, and collect the data from the subordinate devices based on the corrected updated data collection period. Effect of the Invention
[0011] According to one aspect of the present invention, in a communication system, when a comprehensive line contract is made, it is possible to optimize the data communication volume for the entire communication terminal group. [Brief description of the drawings]
[0012] [Figure 1] 1 is a diagram illustrating an overall configuration of a communication system according to a first embodiment. [Diagram 2] FIG. 2 illustrates a hardware configuration of a communication device management server according to the first embodiment. [Diagram 3] FIG. 4 is a diagram showing communication device registration data according to the first embodiment. [Figure 4] FIG. 1 is a diagram illustrating a data collection setting according to the first embodiment. [Diagram 5] FIG. 11 is a diagram showing data collection setting registration data according to the first embodiment. [Figure 6] FIG. 11 is a diagram illustrating a data amount setting according to the first embodiment. [Figure 7] FIG. 11 is a diagram illustrating a WAN-side data volume log according to the first embodiment. [Figure 8] FIG. 11 is a diagram showing data capacity information according to the first embodiment. [Figure 9] FIG. 2 illustrates a hardware configuration of a communication device according to a first embodiment. [Figure 10] FIG. 11 is a diagram illustrating a serial communication setting according to the first embodiment. [Figure 11] FIG. 1 is a diagram illustrating a LAN communication setting according to the first embodiment. [Figure 12] 13 is a WAN side data volume recording file according to the first embodiment. [Figure 13] FIG. 2 is a diagram showing a GUI of a menu screen in the first embodiment. [Figure 14] FIG. 13 is a diagram illustrating a GUI of a communication device registration screen according to the first embodiment. [Figure 15] FIG. 13 is a diagram illustrating a GUI of a data collection setting registration screen according to the first embodiment. [Figure 16] FIG. 13 is a diagram showing a GUI of a data amount setting screen according to the first embodiment. [Figure 17] 13 is a flow of inquiry processing of a server link unit in the communication device of the first embodiment. [Figure 18] 11 illustrates inquiry data transmitted from a server link unit in the communication device to a communication device management server according to the first embodiment. [Figure 19] 13 is a process flow of measuring the amount of WAN-side communication data in a WAN-side communication unit in the communication device of the first embodiment. [Figure 20] 11 is a process flow of a WAN-side communication data volume response of a WAN-side communication unit in the communication device of the first embodiment. [Figure 21] 11 is a process flow of waiting for a query by a communication device management unit in the communication device management server according to the first embodiment. [Figure 22] 11 illustrates inquiry response data transmitted to a communication device by a communication device management unit in the communication device management server according to the first embodiment. [Diagram 23] 11 is a process flow of calculating a transmission cycle correction value in a communication device management unit in the communication device management server according to the first embodiment. [Figure 24] 13 is a process flow of waiting for a communication setting notification in a local communication unit in the communication device according to the first embodiment. [Diagram 25] 13 is a process flow of data collection by a local communication unit in the communication device of the first embodiment. [Figure 26] FIG. 11 is a diagram illustrating a data collection setting according to the second embodiment. [Figure 27] 13 is a process flow of data collection by a local communication unit in the communication device of the second embodiment. [Figure 28] FIG. 13 is a diagram showing communication device registration data according to the third embodiment. [Figure 29] 13 is a process flow of waiting for a query by a communication device management unit in a communication device management server according to a third embodiment. [Diagram 30] FIG. 13 is a diagram showing communication device registration data according to the fourth embodiment. [Diagram 31] 13 is a process flow of waiting for a query by a communication device management unit in a communication device management server according to a fourth embodiment. [Diagram 32] FIG. 13 is a diagram illustrating a data amount setting according to the fifth embodiment. [Diagram 33] FIG. 13 is a diagram showing a GUI of a data amount setting screen according to the fifth embodiment. [Diagram 34] 13 is a process flow of waiting for a query by a communication device management unit in a communication device management server according to a fifth embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0013] Hereinafter, the present embodiment will be described with reference to the drawings. However, the present invention is not limited to the description of the embodiment shown below. It will be easily understood by those skilled in the art that the specific configuration can be changed without departing from the concept or purpose of the present invention.
[0014] In the configurations of the invention described below, the same or similar configurations or functions are given the same reference numerals, and duplicated explanations are omitted. EXAMPLES
[0015] FIG. 1 is a diagram showing the overall configuration of a communication system according to a first embodiment. The communication system includes a communication device management server 100 , user equipment 110 , communication devices 120 , subordinate devices 130 , and a mobile communication network 140 .
[0016] A plurality of communication devices 120 are connected to the communication device management server 100 via a mobile communication network 140. The plurality of communication devices 120 each belong to a different group, and are each connected to a subordinate device 130.
[0017] The communication device management server 100 is a server installed for centralized management of 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 devices 130, a PC for accessing the communication device management server, etc.
[0018] The communication device is a communication device that transmits information of the subordinate device 130 to the user equipment 110 via the communication system 1 and executes management communication via the communication system 2.
[0019] The downstream devices 130 are industrial devices or information devices. For example, servers, air compressors, inverters, etc. correspond to the downstream devices 130. In addition, sensors that output temperature, humidity, etc. may be installed as the downstream devices 130.
[0020] The mobile communication network 140 is assumed to be an LTE line or the like, and is a wireless communication network and backbone communication network that can be used by paying a monthly fee to a communication carrier.
[0021] The communication device management server 100 includes a setting DB 101 , a summary DB 102 , a GUI generation unit 103 , a communication device management unit 104 , and a communication unit 105 .
[0022] The setting DB 101 is a database that stores setting values related to the communication device management server 100 and the communication devices 120. The tally DB 102 is a database that stores tally values related to the communication volume of the communication devices 120 and data required for tallying.
[0023] The GUI generation unit 103 executes returning screen data (HTML) in response to access using HTTP and storing setting values. The communication unit 105 transmits and receives data to and from the user equipment 110 and the communication device 120.
[0024] The communication device management unit 104 stores data received from the communication device 120 in the aggregation DB 102 and manages the amount of data based on information stored in the setting DB 101. The communication unit 105 performs data communication with the communication device 120.
[0025] The communication device 120 includes a server linking unit 121, a WAN communication unit 120, and a local communication unit 123. The server linking unit 121 utilizes the communication system 2 to communicate with the communication device management unit 104 of the communication management server 100, thereby updating setting values related to the information collection contents and collection cycle from the subordinate devices 130.
[0026] The WAN communication unit 122 relays communications performed by the server link unit 121 and the local communication unit 123 via the mobile communication network 140, and measures the amount of data sent to and received from the mobile communication network 140. The subordinate device 130 has operation information 131 and setting information 132.
[0027] The operation information 131 is, for example, information such as the memory usage rate of an information device, the number of rotations per hour of a motor in an industrial device, etc. The setting information 132 is information such as a setting file of a program executed in the information device, a setting value of the number of rotations of a motor in an industrial device, etc.
[0028] The local communication unit 123 of the communication device 120 communicates with the subordinate device 130 in accordance with the setting values, and periodically collects the operation information 131 and the setting information 132 .
[0029] FIG. 2 is a diagram illustrating a hardware configuration of the communication device management server 100 according to the first embodiment. The communication device management server 100 includes 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, all of which are connected via a bus.
[0030] The CPU 200 controls each unit of the communication device management server 100, and loads and executes necessary programs into the main memory device 201. The main memory device 210 is usually configured as a volatile memory such as a RAM, and stores the programs executed by the CPU 200 and data referenced by the CPU 200.
[0031] The auxiliary storage I / F 202 is an interface for connecting an auxiliary storage device such as a HDD, SSD, etc. The input / output I / F 202 is an interface for connecting an input / output device such as a keyboard, a mouse, etc. The network I / F 204 is an interface for connecting to a network.
[0032] The auxiliary storage device 201 has a large storage capacity and stores programs for executing the present embodiment. The communication device management server 100 has a DBMS 210, a GUI generation program 211, a device management program 212, and a communication program installed therein.
[0033] The DBMS 210, the GUI generation program 211, the device management program 212, and the communication program are programs which respectively realize the functions of the setting DB 101, the aggregation DB 102, the GUI generation unit 103, and the communication device management unit 104.
[0034] The setting DB 101 is a database for managing a plurality of setting data, and stores communication device registration data 213, data collection setting 214, data collection setting registration data 215, and data amount setting 216.
[0035] The communication device registration data 213 is data describing information about 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 settings 214 are data referenced by the communication device 120 when acquiring data from the subordinate devices 130, and describe the data acquisition destination, data details, communication method, and collection cycle settings for each piece of acquired data. The setting DB 101 manages multiple data collection settings applied to the communication device 120. The data collection setting registration data 215 is data that records the correspondence between the communication device 120 and the data collection settings.
[0036] 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 summary DB 102 is a database that manages a plurality of summary data. The summary DB 102 stores a WAN side data amount log 217 and data amount information 218.
[0037] The WAN side data volume log 217 is log data that continuously records the increase in the volume of data transmitted and received by each communication device 120. The data capacity information 218 is data that records the data usage status for each group made up of multiple communication devices.
[0038] FIG. 3 is a diagram showing the communication device registration data 213 according to 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 will be described below.
[0039] The model name 301 is a name indicating the model of the communication device 120. The device ID 303 is an ID uniquely assigned to each communication device 120. The ID is determined when the communication device 120 is shipped, written in an internal file of the communication device 120, and written on a nameplate attached to the communication device 120.
[0040] The group ID 303 is an ID for distinguishing a group made up of a plurality of communication devices 120. Usually, the group ID 303 is distinguished based on the shipping destination or the like.
[0041] The hardware ID 304 is an ID for distinguishing the hardware of the communication device 120. The hardware ID 304 is changed when a change occurs in the hardware, such as a change in a part.
[0042] The IMEI 305 indicates an “International Mobile Equipment Identifier” that is assigned to each communication module. The IMEI 305 is an ID for identifying a communication module incorporated in the communication device 120.
[0043] FIG. 4 is a diagram showing the data collection setting 214 according to the first embodiment. The data collection setting 214 has items for each data, such as a data name 401, a connection ID 402, a data storage destination 403, a data length 404, a data type 405, a communication method 406, and a cycle 407. Each item will be described below.
[0044] The data name 401 indicates the name of each piece of data. The connection destination ID 402 is an identifier for uniquely identifying the downstream device 130.
[0045] The data storage destination 403 is information for identifying the location where the data is stored at the connection destination. For example, in the case of Modbus-TCP / RTU, it indicates a register number.
[0046] The data length 404 indicates the number of bytes of data to be acquired.
[0047] The data type 405 indicates the data type of the data to be acquired. For example, Int16B (big endian 16-bit integer type) or FloatL (little endian floating point type) is stored.
[0048] The 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, a LAN or serial is assumed. The 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 started and when the acquired value changes.
[0049] FIG. 5 is a diagram showing the data collection setting registration data 215 according to the first embodiment. The data collection setting registration data 215 stores a device ID 501 and a data collection setting ID 502 on each line. Each item will be described below.
[0050] The device ID 501 is the same as the device ID 302 in the communication device registration data 213. The data collection setting ID 502 is an ID assigned to each data collection setting. The data collection setting ID 502 is an ID written in the format of the date when the data collection setting is registered or created, an underscore, and a serial number, and the serial number is counted up each time a data collection setting is registered or created. When the date is changed, the count returns to 1. In this embodiment, the serial number is written in five digits, but the number of digits may be changed depending on the system scale.
[0051] FIG. 6 is a diagram showing the data amount setting 216 according to the first embodiment. The data amount setting 216 stores a data capacity 602 and a margin 603 for each group ID 601. Each item will be described below.
[0052] Group ID 601 is the same as group ID 302 in communication device registration data 213. Data capacity 602 indicates the data capacity per communication device set for each group in megabytes (MBytes). Data capacity 602 is a value that is set mainly according to the contract type of mobile communication.
[0053] The margin 603 indicates a setting value that determines how much of the total amount of data is not used as a margin value in the group specified by the group ID 601. For example, in a group of 100 machines, if each machine has a data capacity of 20 megabytes, the maximum amount of data is 2000 megabytes, and if the margin is set to 20, then 400 megabytes, which is 20 percent of the total amount of data, is set as the margin value, and data collection is performed within the remaining range of 1600 megabytes.
[0054] FIG. 7 is a diagram illustrating the WAN side data amount log according to the first embodiment. The WAN side data volume log 217 stores, for each line, a device ID 701, a group ID 702, a time stamp 703, and a transmitted / received data volume 704. Each item will be described below.
[0055] The device ID 701 is the same as the device ID in the communication device registration data 213. The group ID 702 is the same as the group ID in the communication device registration data 213. The time stamp 703 indicates the time when the log data in the same row was created.
[0056] The amount of transmitted and received data 704 indicates an increase in the amount of transmitted and received data since the previous recording in the communication device 120 corresponding to the device ID 701 in the same row. The amount of transmitted and received data 704 is calculated by the communication device management unit 104 based on the cumulative amount of transmitted and received data transmitted from the communication device 120.
[0057] FIG. 8 is a diagram showing the data capacity information 218 according to the first embodiment. The data volume information 218 stores, for each group, a group ID 801, a total data volume 802, a remaining communication volume for the current month 803, and a transmission cycle correction value 804. Each item will be described below.
[0058] The group ID 801 is the same as the group ID in the communication device registration data 213. The total data amount 802 indicates the maximum data amount available for each group. The total data amount 802 is calculated by the communication device manager 104 from the number of devices in each group and the data capacity per device.
[0059] The current month communication remaining amount 803 indicates the communication remaining amount obtained by subtracting the margin and the communication amount used during the current month from the total data amount 802. The current month communication remaining amount 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 remaining amount 803 and the daily transmission and reception amount for each communication device.
[0060] FIG. 9 is a diagram illustrating a hardware configuration of the communication device 120 according to the first embodiment. The communication device 120 includes a CPU 900, a main memory device 901, a WAN communication I / F 902, a serial communication I / F 905, a LAN communication I / F 906, and an auxiliary memory I / F 904, all of which are connected via a bus.
[0061] The CPU 900 controls each unit of the communication device 120, and loads and executes necessary programs into the main memory device 901. The main memory device 901 is usually configured as a volatile memory such as a RAM, and stores the programs executed by the CPU 900 and data to be referenced.
[0062] The WAN communication I / F 902 is an interface for connecting to the 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. The auxiliary storage I / F 904 is an interface for connecting an auxiliary storage device such as an EEPROM, HDD, or SSD.
[0063] The serial communication I / F 905 is an interface that connects to the serial communication I / F of the subordinate device 130 when performing serial communication such as Modbus-RTU with the subordinate device 130. The LAN communication I / F 906 is an interface that connects to the LAN communication I / F of the subordinate device 130 when performing LAN communication such as Modbus-TCP with the subordinate device 130.
[0064] The auxiliary storage device 910 has a large storage capacity and stores a setting and recording file 911 and programs for executing this embodiment. The communication device 120 has a server linkage program 912, a WAN communication program 913, and a local communication program 914 installed therein.
[0065] A server linking program 912, a WAN communication program 913, and a local communication program 914 are programs that realize the functions of the server linking unit 121, the WAN communication unit 122, and the local communication unit 123, respectively.
[0066] The setting and recording file 911 is classified into serial communication settings 915, LAN communication settings 916, data collection settings 917, and a WAN side data amount recording file 918. The serial communication settings 915 are data for recording setting items and protocol settings required for serial communication with the subordinate device 130.
[0067] The LAN communication setting 916 is data that records setting items and protocol settings required for LAN communication with the subordinate device 130. The 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.
[0068] The WAN side data volume recording file 918 is a file that records information regarding the communication volume via the mobile communication network 140 .
[0069] FIG. 10 is a diagram showing the serial communication setting 915 according to the first embodiment. The serial communication setting 915 stores a connection destination ID 1001, a baud rate 1002, a bit size 1003, a parity 1004, a stop bit 1005, and a protocol 1006 for each communication target.
[0070] The connection destination ID 1001 is the same as the connection destination ID in the data collection settings. The baud rate 1002 indicates the communication speed (baud rate) of serial communication. The bit size 1003 indicates the bit length from the start bit to the stop bit in serial communication. The parity 1004 indicates the method of applying the error detection code bit in serial communication. The values to be stored are assumed to be none, an even number, or an odd number.
[0071] The stop bit 1005 indicates the length of the stop bit in the serial communication. The protocol 1006 indicates the protocol used in the serial communication. For example, Modbus-RTU is stored.
[0072] FIG. 11 is a diagram showing the LAN communication settings 916 according to 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.
[0073] The destination ID 1101 is the same as the destination ID in the data collection settings. The IP address 1102 indicates the IP address that is the destination of the LAN communication. The port number 1103 indicates the destination TCP port number of the LAN communication. The protocol 1104 indicates the protocol used during the LAN communication. For example, Modbus-TCP is stored.
[0074] FIG. 12 shows the WAN side data amount recording file 918 of the first embodiment. The WAN side data amount record file 918 stores a previous value 1202 and an accumulated value 1203 for each of the items 1201 for transmission and reception on the WAN side.
[0075] The previous value 1202 is an acquired value recorded at the end of processing when the WAN communication unit 122 measures the amount of WAN-side communication data. The communication amount acquired from the WAN-side interface when the most recent WAN-side communication data amount is measured is stored.
[0076] The cumulative value 1203 is the cumulative amount of data transmitted and received since the WAN side data amount record file 918 was last cleared. Considering that the communication amount obtained 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 the WAN side communication data amount is measured.
[0077] FIG. 13 is a diagram showing a GUI of a menu screen 1300 according to the first embodiment. Menu screen 1300 displays menu icons for communication device registration 1301, data collection setting 1302, and data volume 1303. Selecting each icon transitions to a detailed setting screen.
[0078] FIG. 14 is a diagram showing a GUI of a communication device registration screen 1400 according to the first embodiment. By selecting the file selection button 1401, a file selection screen is opened, and a file on the PC being operated can be selected. After the file is selected, the file path of the selected file is displayed in the text box to the left of the file selection button 1401.
[0079] Selecting the upload button 1402 uploads the file selected by the operation when the file selection button 1401 was selected. If the format of the file to be uploaded does not match the format of the communication device registration data 213, a pop-up message stating "Wrong format" is displayed.
[0080] By selecting template download link 1403, a template of communication device registration data 213 can be downloaded. By entering a character string in search box 1404, any communication terminal 120 can be searched for within communication device registration data 213. The search is performed by partial match for all items, and if there is even a partial match between the character string entered in search box 1404 and an item in communication device registration data 213, the corresponding line of communication device registration data 213 is displayed on the screen. Note that if there is no input in search box 1404, all items of communication device registration data 213 are displayed on the screen.
[0081] The display of communication device registration data is checked by selecting the check box 1405. The check boxes in the first row are used to check all rows displayed as search results.
[0082] The communication device registration data display displays the contents of the communication device registration data 213. Up to 30 items can be displayed on one screen. The page scroll link 1407 is a link that displays the next or previous 30 items when 30 or more items of data are registered in the communication device registration data 213.
[0083] Selecting a delete selected terminal button 1408 deletes the data in the row for which a check mark is placed in the check box 1405. The deletion result is reflected in the communication device registration data 213 stored in the setting DB 101. Selecting a link 1409 to the menu transitions to the menu screen.
[0084] FIG. 15 is a diagram showing a GUI of a data collection setting registration screen 1500 according to the first embodiment. By entering a character string in search box 1501, any communication terminal 120 can be searched for within communication device registration data 213. The search is performed by partial match for all items, and if there is even a partial match between the character string entered in search box 1501 and an item in communication device registration data 213, the corresponding line in communication device registration data 213 is displayed on the screen. Note that if there is no input in search box 1501, all items in communication device registration data 213 are displayed on the screen.
[0085] The display of communication device registration data is checked by selecting the check box 1502. The check box 1502 in the first row is used to check all rows displayed as search results.
[0086] The communication device registration data display displays the contents of the communication device registration data 213 and a data collection setting download button 1504. Up to 30 items are displayed on one screen.
[0087] By selecting the data collection setting download button 1504, the data collection setting set for the communication device 120 in the same row can be downloaded. The page scroll link 1505 is a link that displays the next or previous 30 items when 30 or more items of data are registered in the communication device registration data 213.
[0088] By selecting the file selection button 1506, a file selection screen is opened, and a file on the PC being operated can be selected. After the file is selected, the file path of the selected file is displayed in the text box to the left of the file selection button 1506.
[0089] A data collection setting template can be downloaded by selecting a template download link 1507. By selecting a data collection setting registration button 1508, the data collection setting selected with a file selection button 1506 is associated with the communication device 120 in the row in which the check box 1502 is checked.
[0090] When data collection setting registration button 1508 is selected, a data collection setting ID is assigned to the file selected with file selection button 1506 and uploaded to setting DB 101, and the data collection setting ID corresponding to the device ID of communication device 120 in the row for which check box 1502 in the data collection setting registration data is checked is updated. If the format of the selected file does not match the format of the data collection settings, a pop-up message stating "Format is different" is displayed.
[0091] If you keep the cursor on the communication device registration data display for one second or more, a data collection setting content display pop-up will be displayed. The data collection setting content display pop-up will display the data collection settings applied to the communication device 120 on the row where the cursor is located. Selecting the link 1510 to the menu will take you to the menu screen.
[0092] FIG. 16 is a diagram showing a GUI of a data amount setting screen 1600 according to the first embodiment. By entering a character string in search box 1601, any group can be searched for from the group ID display. The search is performed by partial match, and if there is even a partial match between the character string entered in search box 1601 and the group ID, group ID 1603 is displayed on the screen. If there is no input in search box 1601, all group IDs are displayed on the screen.
[0093] Selecting the check box 1602 checks the group ID display. The check box 1602 in the first row checks all rows displayed as search results. The group ID display displays items from the group ID column of the communication device registration data 213 with duplicates removed. Up to 30 items can be displayed on one screen.
[0094] A page scroll link 1604 is a link for displaying the next or previous 30 items when 30 or more items of data are displayed in the group ID display.
[0095] A monthly data capacity per communication device is input as a numerical value in the data capacity input box 1605. A margin is input as a numerical value in the margin input box 1606.
[0096] The combination of group ID, data capacity, and margin for data volume settings is updated by selecting the setting reflection button 1607. If data other than numerical values is entered in the data capacity input box 1605 or margin for margin input box 1606, a pop-up message stating "Input value error" is displayed.
[0097] By keeping the cursor on the group ID display for one second or more, a settings display pop-up 1608 is displayed. The settings display pop-up 1608 displays the data capacity and margin applied to the group ID on the line where the cursor is located.
[0098] FIG. 17 illustrates a flow of a server inquiry process by the server linking unit 121 in the communication device 120 of the first embodiment. The operation of the server link unit will be explained below according to the items in the flowchart.
[0099] In S1700, the following process is started when the communication device 120 is started or when 24 hours or more have passed since the previous execution of the server inquiry process. Note that the present invention does not fix the cycle to 24 hours, but the cycle can be set to any time.
[0100] In S1701, a data volume acquisition request is sent to the WAN communication unit 122 to acquire the WAN side data volume. In S1702, the inquiry data stored in the communication device 120 is referenced, and the WAN transmission data volume and the WAN reception data volume are updated to the values acquired in S1701 and S1702. In S1703 and S1702, the updated inquiry data is sent to the communication device management server 100 using the HTTPS POST method.
[0101] In S1704, since HTTPS utilizes TCP, by confirming receipt of an ACK, it is possible to confirm that the data has reached the communication device management server 100. If the inquiry data sent in S1703 has reached the communication device management server 100, the process proceeds to S1705. If it is not possible to confirm that the data has reached the communication device management server 100, the process proceeds to S1710.
[0102] If a response to the request sent in S1705 and S1703 has been received, the process proceeds to S1706, but if a response has not been received, the process waits for a certain period of time and executes the process of S1705 again.
[0103] If the data collection setting is included in the response data from the communication device management server 100 received in S1706 and S1705, the process proceeds to S1707. If not, the process proceeds to S1708.
[0104] The data collection settings received in S1707 and S1705 are notified to the local communication unit 123. Also, the value of the inquiry data is updated to the data collection setting ID received in S1705.
[0105] If the response data from the communication device management server 100 received in S1708 and S1705 contains a transmission cycle correction value, the process proceeds to S1709. If the response data is not contained, the process proceeds to S1710. The local communication unit 123 is notified of the transmission cycle correction value received in S1709 and S1705. (S1710) The server inquiry process ends.
[0106] FIG. 18 shows inquiry data sent from the server link unit 121 in the communication device 120 to the communication device management server 100 according to the first embodiment. The inquiry data is a JSON file that can be referenced by the server link unit 212, and is recorded in the communication device 120. The inquiry data stores 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.
[0107] Values are written into device ID 1801 and group ID 1802 when the communication device 120 is shipped. Data collection setting ID 1803 is blank until the first communication with the communication device management server 100. At the first communication, a value is written in S1707. WAN transmission data volume 1804 and WAN reception data volume 1805 are blank until the first server inquiry process is executed. When the server inquiry process is executed, values are written in S1702.
[0108] FIG. 19 shows a process flow of measuring the amount of WAN-side communication data in the WAN communication unit 122 in the communication device 120 of the first embodiment. The operation of the WAN side communication unit will be explained below according to the items in the flowchart.
[0109] In S1900, the following process is started when 30 minutes or more have passed since the start of the communication device 120 or the previous measurement of the WAN side communication data volume. Note that the present invention does not fix the cycle to 30 minutes, but the cycle can be set to any time.
[0110] In S1901, the amount of data sent and received is obtained as the current value from the WAN side interface. The Linux (registered trademark) command ifconfig is used to obtain the data. In S1902, the WAN side data amount record file is read and the previous and cumulative values for sending and receiving are obtained.
[0111] 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 it is less, the process proceeds to S1905. S1904) updates the cumulative value acquired in S1902 by subtracting the previous value acquired in S1902 from the cumulative value acquired in S1902.
[0112] The cumulative value acquired in S1905 and S1902 is updated by adding the current value acquired in S1901. The current values acquired 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 volume record file 918. In S1907, the measurement of the WAN side communication data volume is terminated.
[0113] FIG. 20 shows a process flow of the WAN side communication data volume response of the WAN communication unit 122 in the communication device 120 of the first embodiment. The operation of WAN communication unit 122 will be described below according to the items in the flowchart.
[0114] In S2000, the subsequent processing is started when the communication device 120 is started. In S2001, it is confirmed whether an error or the like has occurred and an end of processing has been commanded. If an end has been commanded, the processing proceeds to S2006. If not, the processing proceeds to S2002.
[0115] In S2002, it is confirmed whether a data amount acquisition request has been received from the server link unit 121. If a data amount acquisition request has been received, the process proceeds to S2003. If a data amount acquisition request has not been received, the process returns to S2001.
[0116] In S2003, the WAN side data amount record file 918 is read to obtain the previous value and the cumulative value of the transmitted and received data amount. The previous value and the cumulative value of the transmitted and received data amount obtained in S2004 and S2003 are returned.
[0117] In S2005, the cumulative value of the transmitted and received data volume is substituted with 0, and the WAN side data volume record file is updated. In S2006, the process of the WAN side communication data volume response is terminated.
[0118] FIG. 21 shows a process flow of waiting for an inquiry by the communication device manager 104 in the communication device management server 100 according to the first embodiment. The operation of the device management unit will be described below in accordance with the items in the flowchart.
[0119] In S2100, the subsequent processing is started when the communication device management server 100 is started. In S2101, it is confirmed whether an error or the like has occurred and an end of processing has been commanded. If an end has been commanded, the process proceeds to S2111. If not, the process proceeds to S2102. In S2102, it is confirmed whether a request has been received from the communication device 120 via the communication unit 105. If a request has been received, the process proceeds to S2103. If a request has not been received, the process returns to S2101. From the inquiry data acquired in S2103 and S2102, the device ID, group ID, WAN transmission data volume, and WAN reception data volume of the communication device 120 that sent the request are acquired.
[0120] The time information at the time of processing is obtained and used as a timestamp. The amount of data sent from the WAN and the amount of data received from the WAN are added together to calculate the amount of data sent and received. The device ID, group ID, timestamp, and amount of data sent and received are added to the WAN side data amount log 217 in the summary DB 102.
[0121] In S2104, the data collection setting registration data 215 is obtained from the setting DB 101. A data collection setting ID is obtained from the inquiry data obtained in S2105 and S2102. It is confirmed whether the data collection setting ID obtained in S2104 matches. If they match, the process proceeds to S2108. If they do not match, the process proceeds to S2106.
[0122] In S2106, the data collection setting of the data collection setting ID acquired in S2104 is searched for and acquired from the setting DB 1010. The data collection setting ID acquired in S2107 and S2104 and the data collection setting acquired in S2106 are stored in the HTTPS response body in JSON format.
[0123] In S2108, data capacity information corresponding to the group ID acquired in S2103 is acquired from the aggregation DB 102. A transmission cycle correction value is acquired from the data capacity information acquired in S2109 and S2108, and stored in the HTTPS response body. The HTTPS response body updated in S2110 and S2109 is transmitted to the communication device 120, which is the sender of the request, via the communication unit 105. In S2111, the inquiry waiting process ends.
[0124] 22 shows inquiry response data 2200 that the communication device manager 104 in the communication device management server 100 of the first embodiment sends to the server link unit 121. The inquiry response data 2200 includes a data collection setting key 2201 and a transmission cycle correction value key 2204.
[0125] 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 the data key 2203 is the data collection setting stored in S2107. The transmission cycle correction value 2204 is the transmission cycle correction value stored in S2109.
[0126] FIG. 23 is a process flow of calculating a transmission cycle correction value by the communication device manager 104 in the communication device management server 100 according to the first embodiment. The operation of the device management unit will be described below in accordance with the items in the flowchart.
[0127] In S2300, the following process is started when 24 hours or more have passed since the start of the communication device 120 or the previous calculation of the transmission cycle correction value. Note that the present invention does not fix the cycle to 24 hours, but the cycle can be set to any time.
[0128] In S2301, data volume information is obtained from the aggregation DB 102. In S2302, time information at the time of processing is obtained, and if the date value is 1, the data volume setting is obtained from the setting DB 101 in S2303.
[0129] In S2304, the communication remaining amount for the current month is updated for all rows in the data capacity information of the summary DB 102. The updated value of the communication remaining amount for the current month is calculated by calculating the ratio of the total amount of usable data from the margin of the data capacity setting obtained in S2303, and then multiplying the calculated value by the total amount of data in the data capacity setting obtained in S2301.
[0130] One line of the data capacity information acquired in S2305 and S2301 is read out. The processes from S2306 to S2310 are carried out on the one line of information that has been read out.
[0131] In S2306, the WAN side data volume log 217 that includes the group ID of the row read out in S2305 from the aggregation DB 102 and that has been added since the previous calculation of the transmission cycle correction value is obtained. The values in the column of the transmitted and received data volume in the WAN side data volume log 217 obtained in S2307 and S2306 are all added together to calculate the increase in transmitted and received data per day. The increase in transmitted and received data per day is subtracted from the current month's communication remaining volume in the row read out in S2305 to obtain the new current month's communication remaining volume.
[0132] The number of remaining days in the month is calculated from S2308 and the time information acquired in S2302. After that, the number of remaining days in the month is multiplied by the increase in transmitted and received data per day calculated in S2307 to calculate the expected communication volume for the month. The remaining communication volume for the month in the row read in S2305 is divided by the expected communication volume for the month, and then multiplied by the cycle correction value for the row read in S2305 to calculate a transmission cycle correction value. The calculated transmission cycle correction value is used as the new transmission cycle correction value.
[0133] The data capacity information of the aggregation DB is updated using the group ID read in S2305, the total data amount, the new remaining communication amount for the current month calculated in S2307, and the new transmission cycle correction value calculated in S2308 as one line of data for the data capacity information read in S2309 and S2305.
[0134] If the row of data capacity information read in S2310 and S2305 is the last information, the process proceeds to S2311. If the row is not the last information, the process returns to S2305. In S2311, the process of calculating the transmission cycle correction value ends.
[0135] FIG. 24 illustrates a process flow of communication setting notification waiting by the local communication unit 123 in the communication device 120 according to the first embodiment. The operation of the local communication unit will be described below in accordance with the items in the flowchart.
[0136] In S2400, the subsequent processing is started when the communication device 120 is started. In S2401, it is confirmed whether an error or the like has occurred and an end of the processing has been commanded. If an end has been commanded, the processing proceeds to S2408. If not, the processing proceeds to S2402.
[0137] In S2402, it is confirmed whether a notification has been received from the server link unit 121. If a notification has been received, the process proceeds to S2403. If a notification has not been received, the process returns to S2401.
[0138] It is checked whether the notification received in S2403 and S2402 from the server link unit 121 includes data collection settings. If it has been received, the process proceeds to S2404. If it has not been received, the process proceeds to S2405.
[0139] 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 received from the server link unit 121 in S2405 and S2402 includes a transmission cycle correction value. If it has been received, the process proceeds to S2406. If it has not been received, the process proceeds to S2407. The data is updated using the transmission cycle correction value received in S2406 and S2405 as the new transmission cycle correction value.
[0140] In S2407, a reconfiguration command is sent to the thread that is executing the data collection process, and in S2408, the communication setting notification standby process is terminated.
[0141] FIG. 25 shows a process flow of data collection by 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 in accordance with the items in the flowchart.
[0142] In S2500, the subsequent processing is started when the communication device 120 is started. In S2501, it is confirmed whether an error or the like has occurred and an end of processing has been commanded. If an end has been commanded, the processing proceeds to S2508. If not, the processing proceeds to S2502.
[0143] In S2502, it is confirmed whether a reconfiguration command has been received from the thread executing the communication setting notification waiting. If a reconfiguration command has been received, the process proceeds to S2503. If a reconfiguration command has not been received, the process returns to S2501.
[0144] In S2503, all periodic processes set by the data collection process are stopped. The periodic processes are executed according to the setting file, and collect data from the data storage destination defined by the setting file at each period and transmit the data to the user equipment.
[0145] In S2504, the current settings are discarded, and the data collection settings, LAN communication settings, and serial communication settings are read out. The setting files read out in S2505 and S2504 are checked for any errors in the setting files. An error in the setting files means, for example, that no data collection settings exist, or that no LAN communication settings or serial communication settings exist that correspond to the connection destination ID described in the data collection settings. If there are no errors and the file is normal, the process proceeds to S2506. If an error is found, the process returns to S2501.
[0146] In S2506, a transmission cycle correction value is read. A number of periodic processes are set according to the setting files read in S2507 and S2504. When setting the periodic processes, the cycle read from the data collection setting is multiplied by the transmission cycle correction value (decimals are rounded down) to determine the execution cycle of the periodic processes. From this point on, the periodic processes are executed continuously in a separate thread. In S2508, the data collection process ends.
[0147] 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 performs an inquiry process 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.
[0148] The local communication unit 123 periodically collects data from the subordinate devices 130 and transmits the data to the user equipment by referring to the data collection setting, and corrects the data collection period by referring to the transmission period correction value. This makes it possible to control the amount of data used for a group consisting of multiple communication devices 120 in consideration of the actual usage status of the amount of data. EXAMPLES
[0149] In the first embodiment, all data collection periods are uniformly corrected by the transmission period correction value in the communication device 120. However, there may be data for which the data collection period should be fixed because it is directly related to an abnormality in the device, such as a warning in the subordinate device 130. In the method of the first embodiment, the data collection period is adjusted collectively including this data, which may delay the discovery of an abnormality in the device and lead to losses for the user.
[0150] For this reason, in the second embodiment, a period variable flag is introduced in the data collection setting. The data collection process of the local communication unit 123 is also changed to a process flow that takes into account the period variable flag. The following describes the differences between the first embodiment and the second embodiment with reference to the drawings.
[0151] 26 is a diagram showing the data collection settings of the embodiment 2. A period variable flag 2600 is added as a difference from the embodiment 1. The cycle variable flag 2600 is a flag that determines whether the data collection cycle of the row is affected by the transmission cycle correction value. If the cycle is changed according to the transmission cycle correction value, 0 is set, and if the cycle is not changed, 1 is set.
[0152] 27 shows a process flow of data collection by the local communication unit 123 in the communication device 120 of the embodiment 2. In the embodiment 2, the difference from the embodiment 1 is that the process 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.
[0153] In S2700, for collected data in a row in which the cycle variable flag in the data collection setting is 0, the cycle is multiplied by the transmission cycle correction value in the same manner as in S2507, and then cycle processing is set. In S2701, for collected data in a row in which the cycle variable flag in the data collection setting is 1, cycle processing is set without multiplying the cycle by the transmission correction value.
[0154] According to the second embodiment, it is possible to set whether or not to take the transmission cycle correction value into consideration for each data by introducing the cycle variable flag 2600. Although the effect of reducing the data volume by the transmission cycle correction value becomes weaker, it can be said that the probability of the occurrence of a situation in which the maximum data volume is reached is extremely low due to the effect of the mechanism for continuously adjusting the data volume and the margin.
[0155] This makes it possible to control the amount of data used for a group made up of multiple communication devices 120 in consideration of the actual data usage situation, while maintaining the collection cycle for important data. EXAMPLES
[0156] In the first and second embodiments, the data collection period is uniformly corrected by the transmission period correction value in a group composed of a plurality of communication devices 120. However, the subordinate devices 130 of the communication devices 120 include a wide variety of devices ranging from devices with low priority for data acquisition such as sensors to devices that require optimization through regular device monitoring such as large industrial devices.
[0157] In the method of the first embodiment, the data collection period cannot be changed for each communication device, and it is difficult to set up the communication device while taking into consideration the subordinate devices. In addition, in the method of the second embodiment, it is necessary to generate the data collection setting for each communication device, which is time-consuming.
[0158] For this reason, in the third embodiment, a mechanism is introduced that applies a cycle variable flag to the communication device 120 as well, and can adjust the influence of the transmission cycle correction value for each communication device. The differences between the third embodiment and the second embodiment will be described below with reference to the drawings.
[0159] 28 is a diagram showing communication device registration data of the embodiment 3. As a difference from the embodiment 2, a period variable flag 2800 is added. The cycle variable flag 2800 is a flag that determines whether the terminal in that row is affected by the transmission cycle correction value. If the cycle is changed according to the transmission cycle correction value, 0 is set, and if the cycle is not changed, 1 is set.
[0160] 29 shows a process flow of waiting for an inquiry by the communication device manager 104 in the communication device management server 100 of the third embodiment. As a difference from the second embodiment, the process of S2104 is replaced with S2900. Also, a process of S2901 is added. The operation of the communication device manager will be described below with respect to the differences from the second embodiment.
[0161] In S2900, in addition to the data collection setting registration data acquired in S2104, communication device registration data is acquired from the setting DB 101. 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 sent the request is 1. If it is 1, the process proceeds to S2109. If it is 0, the process proceeds to S2110.
[0162] According to the third embodiment, by introducing a 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 effect of reducing the data volume by the transmission cycle correction value becomes weaker, it can be said that the probability of the occurrence of a situation where the maximum data volume is reached is extremely low due to the effect of the mechanism for continuously adjusting the data volume and the margin.
[0163] This makes it possible to control the amount of data used in a group made up of multiple communication devices 120 in consideration of the actual data usage situation, while maintaining the collection period for the communication devices 120 connected to important subordinate devices 130. EXAMPLES
[0164] Up to the third embodiment, a method has been described for flexibly changing the data collection period for each communication device 120 or each piece of data in a group made up of a plurality of communication devices 120. However, when the types of subordinate devices 130 of the communication devices 120 in a group are diverse, the two types of distinction between fixed period and transmission period correction value may not be sufficient for period adjustment.
[0165] For example, assume that there are three types of industrial equipment: sensors that have a low priority and collect data only for reference, industrial equipment used at production sites, and industrial equipment that is placed in the power supply system for the entire factory.
[0166] Sensors with low priority and only reference-level data acquisition can require small amounts of data at a low frequency, whereas industrial equipment used at production sites requires large amounts of data and control that does not fall below a minimum frequency, and industrial equipment placed in the power supply system for the entire factory must require small amounts of data and must not have its frequency reduced.
[0167] In this case, simply making the sensor cycle variable will not have much effect in reducing the amount of data, and it is unnatural to collect data from industrial equipment used at the production site at the same cycle as the sensor. In consideration of such a case, in the fourth embodiment, a priority can be set for the communication device 120 according to the subordinate device 130. The differences between the fourth embodiment and the third embodiment will be described below with reference to the drawings.
[0168] 30 is a diagram showing communication device registration data of the embodiment 4. As a difference from the embodiment 3, a priority level of 3000 is added. Priority 3000 is a priority that is set according to the subordinate device 130 connected to the communication device 120. Priority is given as a numerical value, with 100 being the maximum and 0 being the minimum in the fourth embodiment. The larger the numerical value, the higher the priority, and the lower the numerical value, the lower the priority. Note that the present invention can achieve the same effect regardless of the numerical range of the priority.
[0169] 31 shows 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. A process of S3100 is added as a difference from the third embodiment. As for S2901 in the third embodiment, the process can be performed in the same manner whether or not the process is included, and therefore the description thereof is omitted in the fourth embodiment. The operation of the communication device manager will be described below with respect to the differences from the third embodiment.
[0170] In S3100, the communication device registration data acquired in S2900 is referenced, and the average priority of the group to which communication device 120, the request sender, belongs is calculated. Then, the priority of communication device 120, the request sender, is divided by the calculated average to calculate a priority correction value. For example, if the average is 50 and the priority of communication device 120 is 75, the priority correction value is 1.5. A transmission cycle correction value is acquired from the data capacity information acquired in S2108, and the value multiplied by the priority correction value is updated as a new transmission cycle correction value.
[0171] According to the fourth embodiment, a priority according to the subordinate device 130 is set for the communication device 120, and a correction according to the priority is additionally performed on 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. EXAMPLES
[0172] Up to the fourth embodiment, a method has been described for flexibly changing the data collection period for each communication device 120 or data by giving priority to communication devices 120 connected to mainly important devices in a group made up of multiple communication devices 120. However, there are cases where an incorrect data collection setting is given due to human error, or a communication device 120 appears that wastes more data than expected during collection. In such cases, if these communication devices are given a high priority, there is a possibility that data will be unnecessarily consumed.
[0173] In the fifth embodiment, a setting item is introduced to perform correction based on the amount of data consumed for each group. In the correction based on the amount of data consumed, a transmission cycle correction value is additionally corrected so as to reduce the amount of data transmitted for communication devices that consume a large amount of data in the same group. The differences between the fifth embodiment and the fourth embodiment will be described below with reference to the drawings.
[0174] 32 is a diagram showing data amount setting in the fifth embodiment. As a difference from the third embodiment, a consumed data amount correction flag 3200 is added. The data consumption amount correction flag 3200 is a flag that determines whether or not to correct the data collection period according to the amount of data consumed within a group having the same group ID.
[0175] 33 is a diagram showing a GUI of a data amount setting screen of the fifth embodiment. As a difference from the third embodiment, a data consumption amount correction check box 3300 is added. When the setting reflect button is pressed with the data consumption amount correction checkbox 3300 selected, the data amount setting is updated with the data consumption amount correction flag set to 1 for the group with the group ID whose checkbox is checked.
[0176] FIG. 34 shows a process flow of waiting for an inquiry by the communication device manager 104 in the communication device management server 100 according to the fifth embodiment.
[0177] As a difference from the fourth embodiment, the process of S2104 is replaced with S3400. Also, the process of S2108 is replaced with S3401. Also, the processes of S3402 and S3403 are added. As for S2901 in the third embodiment and S3100 in the fourth embodiment, the process can be performed in the same manner whether or not the process is included, so the description will be omitted in the fourth embodiment. Below, the operation of the communication device management unit will be described with respect to the difference from the fourth embodiment.
[0178] In S3400, in addition to the data collection setting registration data acquired in S2104 from the setting DB 101, the data volume setting is acquired. In S3401, in addition to the data volume information acquired in S2108 from the summary DB 102, the WAN side data volume log is acquired. For the WAN side data volume log, the latest logs of all communication devices in the group to which the communication device that is the sender of the request belongs are acquired.
[0179] The data amount setting acquired in S3402 and S3400 is referenced, and the data amount correction flag of the group to which the communication device 120 that is the sender of the request belongs is checked. If the data amount correction flag is 1, the process proceeds to S3402. If the data amount correction flag is 0, the process proceeds to S2109.
[0180] The average amount of data sent and received in the latest logs of all communication devices 120 in the group to which the communication device 120 that is the sender of the request acquired in S3403 and S3401 belongs is acquired. Then, the amount of data sent and received by the communication device 120 that is the sender of the request is divided by the calculated average amount to calculate a data consumption amount correction value. A transmission cycle correction value is acquired from the data capacity information acquired in S2108, and the value multiplied by the data consumption amount correction value is updated as the new transmission cycle correction value.
[0181] According to the fifth embodiment, whether or not to perform correction based on the amount of consumed data for each group is determined by a data consumption amount correction flag. If the data consumption amount correction flag is enabled, the transmission cycle correction value is additionally corrected so as to reduce the amount of transmitted data for a communication device that consumes a large amount of data in the same group.
[0182] This makes it possible to prevent a situation in which communication device 120 transmits a large amount of data under settings that are deemed normal when an incorrect data collection setting is given due to human error or when a communication device 120 appears that wastes more data than expected during collection.
[0183] In the above embodiment, a communication device management server 100 that manages the communication devices 120 is installed, and the communication devices 120 to be managed are registered in the communication device management server 100. The communication devices 120 record the amount of communication traffic and transmit the amount of communication traffic to the communication device management server 100 at regular intervals. The communication device management server 100 records the amount of communication traffic received and calculates the remaining amount of data communication for the month according to the number of communication devices 120 it manages. The communication device management server 100 calculates a correction value for the data transmission cycle 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 devices.
[0184] According to the above embodiment, in an IoT system in which a comprehensive line contract is concluded, it is possible to optimize the data volume for a group of terminals, rather than optimizing the data volume for each terminal. [Explanation of symbols]
[0185] 100 Communication device management server 110 User Equipment 120 Communication Equipment 130 Subordinate Equipment 140 Communication Networks 101 Configuration DB 102 Aggregation DB 103 GUI generation section 104 Communication device management department 105 Communications Department 121 Server Linkage Department 122 WAN Communications Department 123 Local Communications Department
Claims
1. 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, The plurality of communication devices Each belongs to a different group, Each is connected to the downstream devices, Collecting data from the subordinate devices based on a preset data collection period, and transmitting a usage data amount to the communication device management server at regular intervals; The communication device management server calculating a transmission cycle correction value for each of the groups based on the amount of data used, and distributing the calculated transmission cycle correction value to the communication devices; The communication device includes: correcting and updating the data collection period for each group based on the transmission period correction value; A communication system comprising: a communication device that collects the data from the subordinate devices based on the corrected update data collection period and transmits the data to an external device.
2. The communication device includes: setting whether or not to take the transmission cycle correction value into consideration for each of the data; When the transmission cycle correction value is set not to be taken into consideration, the data is collected from the subordinate devices based on the data collection cycle; When the transmission cycle correction value is taken into consideration, 2. The communication system according to claim 1, wherein the data is collected from the subordinate devices based on the update data collection period.
3. The communication device includes: A period variable flag is introduced to determine whether the data collection period is affected by the transmission period correction value; 3. The communication system according to claim 2, wherein whether or not the transmission cycle correction value is to be taken into consideration is set for each of the data by referring to the cycle variable flag.
4. The communication device management server setting whether or not to take the transmission cycle correction value into consideration for each of the communication devices belonging to the group; The communication device that is set not to take the transmission cycle correction value into consideration, Collecting the data from the subordinate devices based on the data collection period; The communication device that is 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 devices based on the update data collection period.
5. The communication device management server A period variable flag is introduced to determine whether the communication device is affected by the transmission period correction value; The communication system according to claim 4 , wherein whether or not the transmission cycle correction value is to be taken into consideration is set for each of the communication devices by referring to the cycle variable flag.
6. The communication device management server setting a priority for the communication device according to the subordinate device; re-correcting and updating the transmission cycle correction value based on the set priority; The communication device includes:
2. The communication system according to claim 1, wherein the data is collected from the downstream devices based on the recalibrated update data collection period.
7. The communication device management server Calculating the amount of data consumed by the communication device as the amount of data used; re-correcting and updating the transmission cycle correction value using the calculated consumed data amount; The communication device includes:
2. The communication system according to claim 1, wherein the data is collected from the downstream devices based on the recalibrated update data collection period.
8. The communication device management server 8. The communication system according to claim 7, wherein the transmission cycle correction value is re-corrected by referring to a consumed data amount correction flag that determines whether or not to correct the data collection cycle according to the consumed data amount.
9. The communication device management server A communication unit and a communication device management unit are included. The communication unit is Transferring data exchanged between the communication device and the communication device manager; The communication device management unit Calculating an actual amount of data available per month for each of the groups based on the data capacity per communication device and a margin determined by a user; Calculating a remaining communication amount by referring to the actual data amount and data amount information received from the communication device; The communication device includes: The device has a WAN communication unit, a server linking unit, and a local communication unit, The WAN communication unit is performing WAN communication and recording the WAN communication volume as the amount of data used; The server link unit includes: periodically transmitting the WAN traffic acquired from the WAN communication unit to the communication device management server; The local communication unit is periodically collecting the data from the subordinate devices and transmitting the data 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 transmission cycle correction value to the communication device via the communication unit; The local communication unit of the communication device 2. The communication system according to claim 1, wherein the data collection period is corrected and updated for each of the groups based on the transmission period correction value.
10. 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 of the communication devices; 10. The communication system according to claim 9, wherein the correction value for the data collection period is not returned in response to an inquiry from the communication device that does not correct the data collection period.
11. The subordinate device is 2. The communication system according to claim 1, wherein the communication system is comprised of an industrial device, an information device, or a sensor.
12. A communication device connected to a communication device management server via a network, The communication device includes: each of which belongs to a group made up of a different plurality of the communication devices; Collects data from subordinate devices based on a preset data collection cycle, correcting and updating the data collection period for each group based on the transmission period correction value calculated by the communication device management server; A communication device that collects the data from the downstream devices and transmits the data to an outside source based on the corrected update data collection period.
13. The subordinate device is 13. The communication device according to claim 12, which is composed of an industrial device, an information device, or a sensor.
14. A communication method for a communication system having a communication device management server and a plurality of communication devices, comprising: A plurality of the communication devices are assigned to different groups, A plurality of the communication devices are connected to respective subordinate devices; In the communication device, Collecting data from the subordinate devices based on a preset data collection period, and transmitting a usage data amount to the communication device management server at regular intervals; In the communication device management server, calculating a transmission cycle correction value for each of the groups based on the amount of data used, and distributing the calculated transmission cycle correction value to the communication devices; In the communication device, correcting and updating the data collection period for each group based on the transmission period correction value; A communication method comprising: collecting the data from the downstream device based on the corrected update data collection period and transmitting the data to an outside.
Citation Information
Patent Citations
Data collection system
JP2006186891A
Program execution control system
JP2015069403A
Data collection system, data collection method, server, and gateway
JP2016163242A
