Data collection device, data collection method and program

Abstract

To properly acquire information on a radio environment or equipment operation while reducing a data size.SOLUTION: In a communication system, a communication device 103 as a data collection device, includes: a storage unit 206 that stores a specific event condition table including event conditions and a collection period defined for each event condition, and a holding time limit; a state acquisition unit 202 that acquires equipment state information and radio communication state information; a temporary storage unit 204 that temporarily stores the equipment state information and the radio communication state information as state data in association with time information for a period designated by the holding time limit; a determination unit 203 that determines whether or not a specific event has occurred in the state data; and a recording object information collection unit 205 that, if the determination unit determines that the specific event has occurred, causes the storage unit 206 to store specific state data stored in the temporary storage unit 204 and pre / post-specific event supplementary information as state data in a collection period before and after a point in time at which the specific event has occurred, as recording object data.SELECTED DRAWING: Figure 2

Description

[Technical field]

[0001] The present invention relates to a data collection device, a data collection method, and a program. [Background technology]

[0002] Conventionally, in order to maintain wireless communication quality, a method has been used in which an abnormality in the wireless environment is monitored, wireless frames are captured, and the collected data is analyzed using a local computer or a server device on the cloud. Normally, when monitoring the wireless environment, information (monitoring information) such as an operation log related to the operation state of the wireless frames or the device is stored in a storage area of ​​the monitoring device, and after an abnormality occurs in wireless communication, the stored monitoring information is acquired to perform analysis. For example, Patent Document 1 discloses a technology related to a device for acquiring wireless environment information. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent Publication No. 2021-190853 Summary of the Invention [Problem to be solved by the invention]

[0004] However, such a method requires that information such as wireless frames and operation logs be recorded continuously until a problem occurs in wireless communication, and therefore requires the equipment that monitors the wireless environment to be equipped with a huge storage area, which increases the cost of the equipment. In addition, when attempting to transmit such monitoring information to a server device or the like on a cloud, the size of the data to be transmitted becomes huge, which raises the problem of increased communication costs related to data transmission and costs related to maintaining the storage area of ​​the server device. An object of the present invention is to provide a data collection device or the like that can appropriately store information related to the wireless environment and abnormal operation of the equipment while reducing the storage area and the size of the data to be transmitted. [Means for solving the problem]

[0005] A data collection device according to one embodiment of the present invention is a data collection device regarding communication between a communication terminal and the device itself, and includes a memory unit that stores a specific event condition table including event conditions and collection periods determined for each event condition, as well as a retention deadline, which is the period for which status data is to be retained; a status acquisition unit that acquires device status information and wireless communication status information; a temporary storage unit that links the device status information and wireless communication status information to current time information and temporarily stores them as status data for the period specified by the retention deadline; a determination unit that determines whether a specific event has occurred among the status data by referring to the specific event condition table; and a record target information collection unit that, when the determination unit determines that a specific event has occurred, stores in the memory unit as record target data the status data including the specific event stored in the temporary storage unit and supplementary information before and after the specific event, which is status data for the collection period based on the time when the specific event occurred.

[0006] With this, even if a specific event occurs in communication between the communication terminal and the data collection device itself (the data collection device), the data collection device only stores specific status data relating to the specific event and supplementary information before and after the specific event for a period based on the collection period, thereby reducing the memory area and the size of the data to be transmitted, and enabling the appropriate acquisition of information relating to abnormalities in the wireless environment and equipment operation.

[0007] The data collection device may further include a reception unit that receives at least the event condition and the collection period from a management terminal connected to the data collection device.

[0008] According to this, the receiving unit can receive request information from the management terminal, including an event condition that defines various information related to the specific event, and a collection period that specifies the range for collecting pre- and post-event supplemental information, which is status data before and after the time when the specific event occurred. Therefore, the administrator can use the management terminal to appropriately obtain information on the wireless environment and abnormalities in device operation at any time.

[0009] The data collection device may further include a communication unit that is communicatively connected to an external server device and transmits the record target data stored in the memory unit to the server device.

[0010] This allows the data collection device to transmit the record target data stored in the data collection device itself to an external server device or the like.

[0011] A data collection method according to one embodiment of the present invention is a data collection method for collecting data regarding communication between a communication terminal and a local device, and includes a storage step for storing a specific event condition table including event conditions and collection periods determined for each event condition, as well as a retention deadline which is the period for which status data is to be retained; an acquisition step for acquiring device status information and wireless communication status information; a temporary storage step for linking the device status information and wireless communication status information to current time information and temporarily storing them as status data for the period specified by the retention deadline; a determination step for determining whether a specific event has occurred among the status data by referring to the specific event condition table; and a record target information collection step for storing, if the determination step determines that a specific event has occurred, the status data including the specific event stored in the temporary storage step and supplementary information before and after the specific event, which is status data for the collection period based on the time when the specific event occurred, as record target data.

[0012] This provides the same effects as the data collection device described above. Effect of the Invention

[0013] The data collection device etc. of the present invention can appropriately acquire information relating to the wireless environment and abnormalities in device operation while reducing the memory area and the size of data to be transmitted. [Brief description of the drawings]

[0014] [Figure 1] FIG. 1 is a schematic diagram showing an example of a communication system according to the present embodiment. [Diagram 2]FIG. 2 is a block diagram showing a functional configuration of the communication device according to the present embodiment. [Diagram 3] FIG. 3 is a flowchart showing a series of processing steps in which the communication device of this embodiment acquires status data and stores it in the temporary storage unit. [Figure 4] FIG. 4 is a flowchart showing a series of processing steps from receiving a notification of event information in a communication device of this embodiment until storing, in a storage unit, status data and pre- and post-event supplemental information relating to specific event information in the notification. [Diagram 5] FIG. 5 is an example of a specific event condition table stored in the communication device according to the present embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0015] Hereinafter, the embodiment will be specifically described with reference to the drawings. The embodiments described below each show a preferred specific example of the present invention. The numerical values, components, the arrangement and connection of the components, steps, and the order of steps shown in the following embodiments are merely examples and are not intended to limit the present invention. Furthermore, among the components in the following embodiments, those components that are not described in the independent claims showing the highest concept of the present invention will be described as any components constituting a more preferred embodiment. Note that the same components will be given the same reference numerals and descriptions may be omitted.

[0016] [Embodiment Mode] An overview of a communication system according to an embodiment of the present invention will be described with reference to FIG. As illustrated in FIG. 1, a communication system 100 includes a server device 101 , a network 102 , a communication device 103 , a management terminal 104 , a child terminal 105 , a communication link 106 , and a communication link 107 .

[0017] The server device 101 is a server that records important parts of data (e.g., data frames, device operation logs, etc.) acquired by the communication device 103 that monitors the operation status of the communication system 100. The server device 101 exists, for example, on a cloud and can receive status data related to information on a specific event (described later) and data related to supplementary information before and after the event (described later) from the communication device 103 via the network 102. The server device 101 also processes the operation status of the communication system 100 received from the communication device 103 and illustrates the information to another administrator terminal (not shown) that may be connected to the network 102, thereby playing the role of an information terminal regarding the operation status, etc. of the communication system 100.

[0018] The network 102 is a general-purpose network including a narrow area network such as an intranet and a wide area network such as the Internet. The network 102 connects the server device 101 and the communication device 103, and transmits data between the server device 101 and the communication device 103. The network 102 may also be connected to a management terminal 104 to be used for communication between the server device 101 and the management terminal 104.

[0019] The communication device 103 is, for example, a wireless access point, and is an example of embodying the data collection device of the present invention. The communication device 103 complies with wireless communication standards such as IEEE802.11 and IEEE802.15, and performs wireless communication with the slave terminal 105 via the communication link 106. The communication device 103 relays communication between a plurality of slave terminals 105 that can be connected via the communication link 106, or communication between the network 102 and the communication link 106. The communication device 103 also monitors and accumulates packet data (communication data) included in the operation state of the device itself and data frames transmitted and received via wireless communication, and can transmit the accumulated information via the network 102 to the server device 101 or a terminal (not shown) connected to the network 102. The communication data accumulated by the communication device 103 is not limited to data frames, and may include data for controlling wireless communication, such as management frames and action frames. In this embodiment, the communication relayed by the communication device 103 is wireless communication, but is not limited to this. For example, the communication device may be a communication device (USB device server) that relays communication between wired communication conforming to a wired communication standard such as IEEE802.3 and bus communication other than a network such as USB (Universal Serial Bus (registered trademark)).

[0020] The management terminal 104 is connected to the communication device 103 via a communication link 107. The management terminal 104 is, for example, a PC (Personal Computer) or a tablet terminal. An administrator who manages the communication system 100 uses, for example, a setting tool provided in the management terminal 104 for making various settings in the communication device 103, accesses the communication device 103 via the communication link 107, and sets conditions (for example, event conditions, retention period, collection period, etc., details of which will be described later) regarding communication between the communication device 103 and the child terminal 105 and collection of data indicating the operating status of each device. Note that, although one management terminal 104 is illustrated in the present embodiment, the present invention is not limited to this, and multiple management terminals may be connected to the communication device 103.

[0021] The child terminal 105 is a communication terminal used by a user who uses the communication system 100. The child terminal 105 is connected to the communication device 103 via a communication link 106. The child terminal 105 communicates with other terminals that may be connected to the network 102 via the communication device 103, the server device 101, and with other child terminals that may be connected via the communication link 106. Although one child terminal 105 is illustrated in this embodiment, the present invention is not limited to this, and a plurality of child terminals may be connected to the communication device 103. Furthermore, the child terminal 105 is not limited to a network device, and may be a peripheral device connected to the communication device 103 by a bus communication standard such as USB.

[0022] The communication link 106 connects the communication device 103 and the child terminal 105. The communication link 106 transmits communication data between the communication device 103 and the child terminal 105 according to a wireless communication standard such as IEEE802.11ac. Note that the connection between the communication link 106 and the child terminal 105 may be replaced with a bus communication standard such as USB instead of the communication link 106.

[0023] The communication link 107 may be realized by, for example, a network interface such as the network 102 or the communication link 106, or may be realized by a bus communication interface such as RS-232C or USB. In addition, the communication link 107 may allow the management terminal 104 to access the communication device 103 by causing the communication link 106 to transmit communication contents corresponding to the communication link 107.

[0024] FIG. 2 is a block diagram showing a functional configuration of a communication device according to an embodiment of the present invention. 2, the communication device 103 includes a timer 201, a status acquisition unit 202, a determination unit 203, a temporary storage unit 204, a record target information collection unit 205, a storage unit 206, a communication unit 207, and a reception unit 208. The above functions of the communication device 103 are realized by hardware such as a central processing unit (CPU), a random access memory (RAM), a read only memory (ROM), a storage device (e.g., a non-volatile storage device such as an embedded multimedia card (eMMC) or a solid state drive (SSD)), and a communication module included in the communication device 103. Specifically, the functions are realized by the CPU reading out a program stored in the ROM or the like and executing the program in cooperation with the hardware.

[0025] When the timekeeping unit 201 receives a time information acquisition request notified by the status acquisition unit 202, it notifies the status acquisition unit 202 of the current time information at the time when the time information acquisition request was received. The timekeeping unit 201 is configured by a device such as an RTC (Real Time Clock) and keeps track of time.

[0026] The status acquisition unit 202 periodically collects device status information indicating the operation status of the communication device 103 (e.g., device error information included in syslog, kernel message, etc., or information on a change in a connection state to a communication interface, etc.) and wireless communication status information (e.g., operation logs of a wireless driver that controls a wireless communication frame and a wireless module related to wireless communication with the slave terminal 105, application software related to authentication control and connection control, or a noise floor value, a bandwidth occupancy rate, etc.) from operation log information of an OS (Operating System), software that controls a wireless communication module, etc., or an interface that manages frames exchanged by a wireless communication module, etc. Furthermore, when the status acquisition unit 202 acquires the device status information and the wireless communication status information, as described above, the status acquisition unit 202 notifies the clock unit 201 of a time information acquisition request at the timing when the status information is acquired. Furthermore, the status acquisition unit 202 notifies the determination unit 203 of status data that is linked to the device status information and the wireless communication status information notified from the clock unit 201. The cycle for periodically collecting the device status information and the wireless communication status information is determined by a setting tool of the management terminal 104 .

[0027] The determination unit 203 checks the status data notified from the status acquisition unit 202 against the event conditions input by the administrator from, for example, a setting tool through the reception unit 208. The event conditions are, for example, information combining conditions such as reception of a frame indicating disconnection of the communication link 106, log information of the control software related to failure of an authentication procedure for joining a wireless network, a decrease in reception strength in the wireless environment information, or error information that may be included in the device status information recorded by the OS running on the communication device 103. One or more types of event conditions are set, and are managed by being compiled in a specific event condition table 500 described later. When the determination unit 203 determines that an event (any event among specific events) that matches any of the event conditions described in the specific event condition table has occurred as a result of referring to the specific event condition table 500 for the status data, it notifies the record target information collection unit 205 of event information indicating that the specific event has occurred. Hereinafter, the status data including the specific event will be referred to as specific status data. Furthermore, the determination unit 203 determines whether or not there is any state data whose retention period has expired for each of the state data held by the temporary storage unit 204. If it is determined that there is state data whose time information exceeds the retention period, the determination unit 203 instructs the temporary storage unit 204 to delete the state data. The retention period is the period during which each state data periodically acquired by the status acquisition unit 202 is to be retained.

[0028] Here, the specific event condition table according to the present embodiment will be described in detail with reference to FIG.

[0029] FIG. 5 shows an example of a specific event condition table. As shown in FIG. 5, the specific event condition table 500 includes an ID field 501, a specific event field 502, and a collection period field 503. The ID field 501 is an item for managing the specific event field 502 and the collection period field 503 in association with each other. The ID field 501 may be managed by an identification number, or may be managed by a specific name (e.g., a text name) or the like. The specific event field 502 stores a condition that the administrator desires to detect as a specific event in the information included in the device status information or wireless communication status information acquired by the status acquisition unit 202 (e.g., in the case of ID field number 1, a log indicating that a deauthentication or disassociation frame indicating that the communication link 106 has been disconnected is received). The collection period field 503 stores a value that specifies a period for collecting pre- and post-event supplementary information (e.g., a period specified by time). The specific event condition table 500 is stored in the storage unit 206.

[0030] Returning to FIG. 2, temporary storage unit 204 stores the status data notified by status acquisition unit 202, regardless of the result of determination by determination unit 203 as to whether or not a specific event has occurred. Furthermore, temporary storage unit 204 holds the status data only for the retention period. Since temporary storage unit 204 has a limited storage area, an upper limit is set for the retention period. In other words, status data having time information determined by determination unit 203 to have exceeded the retention period is discarded, and an area is secured for storing status data that can be newly acquired later. Temporary storage unit 204 is realized by, for example, a volatile storage means such as a RAM, or a non-volatile storage means provided with a specific area for temporary storage in eMMC or the like.

[0031] Upon receiving an event information notification from the determination unit 203 to indicate that the occurrence of a specific event has been detected, the record target information collection unit 205 acquires specific state data from the temporary storage unit 204 and stores the data in the storage unit 206. Based on the information on the collection period (Δt) stored in the specific event condition table 500, the record target information collection unit 205 also acquires state data recorded during the collection periods (T-Δt to T and T to T+Δt) before and after the time information (T) held by the specific state data from the temporary storage unit 204 as pre- and post-event supplementary information and stores the acquired data in the storage unit 206. When the collection period Δt has elapsed since the occurrence of the specific event and the process of collecting the minimum amount of information required for analyzing the event and recording the collected information in the storage unit 206 has been completed, the record target information collection unit 205 may notify the communication unit 207 that the process based on the event information has been completed (event information processing completion notification).

[0032] Furthermore, the record target information collecting unit 205 may store a group of state data including the period before and after the acquired data in the storage unit 206 as record target data, and may also notify the communication unit 207 to transmit the data to the server device 101 connected via the network 102. Note that, as shown in Fig. 5, the collection period Δt may be set to an individual value for each specific event, and the collection periods before and after the occurrence of an event may be different from each other. This is because the data period required for analysis may differ before and after the occurrence of an event depending on the type of event.

[0033] The storage unit 206 stores the status data notified by the record target information collection unit 205. The storage unit 206 is a storage device configured with a non-volatile memory, etc. The storage unit 206 is realized by a non-volatile storage device such as an eMMC, SSD, or HDD (Hard Disk Drive), but may also be configured to set a specific storage area on a volatile storage device such as a RAM to store the status data.

[0034] The communication unit 207 connects the network 102 and the communication device 103. The communication unit 207 may be connected to the network 102 via a wireless network using a wireless communication module or the like, or may be connected to the network 102 via a wired network using a wired communication module or the like.

[0035] The reception unit 208 is connected to the management terminal 104, and receives a request including an information storage setting and a retention period transmitted from the management terminal 104 (setting tool). The information storage setting is request information including an event condition that defines various conditions related to a specific event that the administrator wishes to store, and a collection period (Δt) that specifies the range for collecting pre- and post-event supplementary information that is status data before and after the time (T) when the specific event occurs. When the reception unit 208 receives the information storage setting transmitted from the management terminal 104, it adds the request information included in the information storage setting to the specific event condition table 500 stored in the storage unit 206.

[0036] [Description of state data acquisition flow according to embodiment] Next, a series of processes from when the communication device 103 acquires status data to when it stores record target data will be described with reference to FIG. Step S301 is a step in which the determination unit 203 determines whether or not the temporary storage unit 204 holds state data. If the temporary storage unit 204 holds state data, step S302 is executed (Yes in step S301), and if the temporary storage unit 204 does not hold state data, step S304 is executed (No in step S301).

[0037] Step S302 is a step in which the determination unit 203 determines whether or not there is any state data whose retention period has expired for each of the state data held by the temporary storage unit 204. If there is any state data whose retention period has expired among the state data held by the temporary storage unit 204, the determination unit 203 executes step S303 (Yes in step S302), and if there is no state data whose retention period has expired among the state data held by the temporary storage unit 204, the determination unit 203 executes step S304 (No in step S302).

[0038] Step S303 is a step of deleting, from the temporary storage unit 204, any state data whose retention period has expired, from the temporary storage unit 204. When the deletion of the corresponding state data is completed in this step, the process proceeds to step S304.

[0039] Step S304 is a step in which the status acquisition unit 202 acquires device status information regarding the operating status of the communication device 103 and wireless communication status information from operation log information of the OS, software that controls the wireless communication module, etc., or an interface that manages frames exchanged by the wireless communication module, etc.

[0040] Step S305 is a step of linking the device status information and wireless communication status information acquired by status acquisition unit 202 with the current time notified by clock unit 201. More specifically, when status acquisition unit 202 acquires device status information and wireless communication status information, it notifies clock unit 201 of a time information acquisition request at the timing when the status information is acquired. Upon receiving the notification, clock unit 201 notifies status acquisition unit 202 of the time when the notification was accepted, and status acquisition unit 202 generates status data by linking the notified time information to the device status information and wireless communication status information. The generated status data is notified to determination unit 203, and when the operation of step S305 is completed, the process proceeds to step S306.

[0041] In step S306, temporary storage unit 204 temporarily stores the status data upon receiving notification of the status data from status acquisition unit 202. The status data acquired by status acquisition unit 202 is temporarily stored in temporary storage unit 204 regardless of whether the status data includes a specific event.

[0042] In step S307, the determination unit 203 searches the specific event condition table 500, which stores a plurality of event conditions previously input by the administrator, from the contents of the state data newly stored in the temporary storage unit 204 in step S306, and determines whether or not an event corresponding to the specific event has occurred. The determination unit 203 sequentially checks the plurality of event conditions stored in the specific event condition table 500 from among the state data notified from the state acquisition unit 202, and if it determines that a specific event has been detected, it executes step S308, and if a specific event has not been detected, it returns to step S302.

[0043] Step S308 is a step in which the determination unit 203 notifies the record target information collection unit 205 of the specific event detected in step S306 as event information. The event information includes information on the specific event detected as occurring by the determination unit 203. When the notification in step S308 is completed, the process returns to step S302, and the series of processes for acquiring new state data is continued again.

[0044] [Description of specific event and pre- and post-event supplementary information acquisition flow according to the embodiment] Next, a process of collecting specific state data related to a specific event and record target data including supplemental information before and after the event by the record target information collecting unit 205 included in the communication device 103 will be described with reference to Fig. 4. Note that each process shown in Fig. 4 is executed in parallel with the process shown in Fig. 3, triggered by the process in step S308 in Fig. 3.

[0045] In step S401, the record target information collecting unit 205 receives a notification of event information from the determining unit 203. Upon receiving the notification of the event information, the record target information collecting unit 205 executes step S402.

[0046] In step S 402 , the record target information collector 205 acquires specific state data from the temporary storage unit 204 .

[0047] Step S403 is a step in which the record target information collector 205 identifies the time at which the specific event occurred, which was recorded in the specific status data acquired in step S402.

[0048] Step S404 is a step in which the record target information collecting unit 205 collects from the temporary storage unit 204, based on the time specified in step S403, state data that was acquired before the time the specific event occurred and stored in the temporary storage unit 204 among the supplementary information before and after the event. The record target information collecting unit 205 collects state data from the temporary storage unit 204, which is acquired a predetermined time before the time the specific event occurred, within the range of the collection period described in the specific event condition table 500, based on the time the specific event occurred. Note that in step S404, the record target information collecting unit 205 may include a step of determining whether or not there is state data stored in the temporary storage unit 204 at a time before the time the specific event occurred. The record target information collecting unit 205 acquires even a portion of the state data that was acquired before the time the specific event occurred and remains stored in the temporary storage unit 204, although some of the state data temporarily stored in the temporary storage unit 204 may have passed the retention period and been deleted. On the other hand, it may be the case that, due to some kind of failure, the temporary storage unit 204 does not store any status data acquired before the occurrence time of a specific event. In such a case, the processing flow may proceed to step S405 without performing the information collection process in step S404.

[0049] Step S405 is a step in which the record target information collection unit 205 collects, based on the time specified in step S403, status data from the pre- and post-event supplemental information that was acquired after the time the specific event occurred and stored in the temporary storage unit 204. The record target information collection unit 205 collects, from the temporary storage unit 204, status data after the time the specific event occurred, within the range of the collection period described in the specific event condition table 500, based on the time the specific event occurred.

[0050] Step S406 is a step in which the record target information collecting unit 205 judges whether or not the collection period for additional collection of state data after the occurrence of a specific event has elapsed. The record target information collecting unit 205 repeatedly executes step S405 (No in step S406) until the state data for the period designated by the collection period has been acquired. As a result, the state data acquired in parallel by the state acquiring unit 202 during the collection period (T to T + Δt) after the occurrence time of the specific event is gradually accumulated in the temporary storage unit 204, so that the record target information collecting unit 205 can collect the accumulated state data. When the collection period has elapsed, the record target information collecting unit 205 executes step S407 (Yes in step S406).

[0051] Step S407 is a step in which the record target information collecting unit 205 stores a group of state data (i.e., specific state data and supplementary information before and after a specific event) collected in steps S402, S404, and S405 in the storage unit 206 as record target data. Note that, instead of storing the record target data in the storage unit 206 at the timing when this step S407 is executed, the record target information collecting unit 205 may transmit the record target data to the server device 101 connected to the network 102 via the communication unit 207 and store the data in a storage means provided in the server device 101, or storage in both the device itself and the server device 101 may be performed at the same timing. Also, the record target information collecting unit 205 may transmit the record target data stored in the storage unit 206 to the server device 101, etc. at any timing. Also, the record target information collecting unit 205 may notify the communication unit 207 of an event information processing completion notification after executing step S407, and the communication unit 207 that has received the notification may notify the management terminal 104 that the record target data has been stored in the storage unit 206. This allows the administrator to know that the communication device 103 has detected a specific event, and that the record target data related to the detected specific event has been recorded in the storage unit 206. When the record target information collection unit 205 finishes executing step S407, it completes a series of recording processes of the record target data for the specific event that the determination unit 203 has determined to have occurred. [Industrial Applicability]

[0052] The present invention can be used in a communication device or the like that relays communication while monitoring the communication state based on device state information or state information related to wireless communication. [Explanation of symbols]

[0053] 100 Communication Systems 101 Server device 102 Network 103 Communication equipment 104 Management terminal 105 Child terminal 106 Communication Links 107 Communication Links 201 Timing section 202 Status acquisition unit 203 Judgment section 204 Temporary storage 205 Recording Information Collection Department 206 Memory section 207 Communications Department 208 Reception 500 Specific event condition table 501 ID Field 502 Specific Event Field 503 Collection period field

Claims

1. A data collection device that collects data regarding communication between a communication terminal and the device itself, a storage unit that stores a specific event condition table including a collection period that specifies a period for collecting specific event conditions and pre- and post-event supplementary information, and a retention period that is a period for retaining status data; a status acquisition unit that acquires device status information and wireless communication status information; a temporary storage unit that associates the device status information and the wireless communication status information with time information at that time and temporarily stores the information as status data only for a period designated by the retention period; a determination unit that determines whether a specific event has occurred by referring to the specific event condition table in the status data; a record target information collection unit that, when the determination unit determines that the specific event has occurred, causes the storage unit to store, as record target data, the status data including the specific event stored in the temporary storage unit and specific event pre- and post-event supplementary information, which is the status data for the collection period before and after the time when the specific event occurred; A data collection device comprising:

2. a receiving unit configured to receive at least the specific event condition and the collection period from a management terminal connected to the device itself; The data collection device of claim 1 .

3. Further, a communication unit is provided, the communication unit is communicably connected to an external server device, and transmits the recording target data stored in the storage unit to the server device; 3. The data collection device according to claim 1 or 2.

4. A data collection method for collecting data relating to communication between a communication terminal and a device itself, comprising: a storage step of storing a specific event condition table including a collection period specifying a period for collecting specific event conditions and pre- and post-event supplementary information, and a retention period that is a period for retaining status data; an acquisition step of acquiring device status information and wireless communication status information; a temporary storage step of linking the device status information and the wireless communication status information with time information at that time and temporarily storing the information as status data only for a period designated by the retention period; a determining step of determining whether a specific event has occurred by referring to the specific event condition table in the status data; a record target information collecting step of storing, when the determining step determines that the specific event has occurred, the status data including the specific event stored in the temporary storing step, and supplementary information before and after the specific event, which is the status data for the collection period before and after the time when the specific event occurred, as data to be recorded; Data collection methods, including:

5. A program that causes a computer to execute the data collection method according to claim 4.

Images