JP2016110280A - Data collection system and data collection method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a log management system that avoids the concentration of log collection timing.SOLUTION: A log management system 13 for collecting data via a network from an apparatus used by a user includes: a transmission/reception unit 23 for receiving data from the apparatus; a communication speed calculation unit 252 for estimating a communication load on the transmission/reception unit 23 per user using data in the past received by the transmission/reception unit 23; a communication bandwidth calculation unit 253 for estimating already-used communication bandwidth per time band from a communication log held by the log management system 13; and a job scaling unit 26 for allocating timing when an apparatus of a user causing the largest communication load estimated by the communication speed calculation unit 252 transmits data to a time band having a communication band available for receiving data from the apparatus.SELECTED DRAWING: Figure 4

Description

  The present invention relates to a data collection system and a data collection method.

  Logs generated, stored, and analyzed by devices are collected from the perspective of managing device usage and enhancing security. In addition, in many cases, a log management system connected to a device via a network automatically collects logs as the network environment is improved. In addition, a technique called cloud computing, in which an arbitrary information processing apparatus on a network performs processing, is spreading, and collection of device logs and the like is increasingly provided in the form of a cloud service.

  When logs are collected by a cloud service, the log management system on the cloud collects logs from devices owned by various service users who use the cloud service. There are various scales of service use companies and devices in use, and there are also various communication environments (communication speeds and communication bands) of service use companies. For this reason, if the service use enterprises transmit logs at arbitrary timings, the transmission timings of other service use enterprises overlap, and there is a possibility that log transmissions to the log management system will be concentrated. In this case, the log management system must receive a large amount of concentrated logs without causing delays or failures.

  However, even when a large amount of logs are concentrated and sent to the log management system, it is necessary to improve the processing capacity of the log management system and to invest in communication infrastructure in order to receive logs appropriately. This increases costs for the cloud service.

  For this reason, a technique for avoiding concentration of log transmission by controlling the timing of log collection by the log management apparatus may be employed (for example, see Patent Document 1). Patent Document 1 discloses a log management apparatus that performs log collection according to the priority order based on log properties (service level item, evaluation time limit, log type required for the evaluation, and the like).

  However, in the log management device described in Patent Document 1, for example, a resource is allocated to a service using company whose evaluation deadline is close, and log collection is started. If there are many service using companies whose evaluation deadline is close, log transmission is performed. There is a problem that may concentrate.

  In view of the above problems, an object of the present invention is to provide a log management system capable of avoiding concentration of log collection timing.

  The present invention is a data collection system for collecting data from a device used by a user via a network, using data receiving means for receiving data from the device, and past data received by the data receiving means. Communication load estimating means for estimating the communication load of the data receiving means for each user, communication band estimating means for estimating a used communication band for each time zone from a communication log held by the data collection system, A transmission timing assigning means for assigning a timing at which a user's device having the largest communication load estimated by the communication load estimating means transmits data to a time zone in which there is a communication band available for receiving data from the device; It is characterized by having.

  A log management system capable of avoiding concentration of log collection timing can be provided.

It is an example of a system configuration diagram of a service use system in which a log management system and a service use company are connected via a network. It is an example of the figure explaining the outline of the scheduling of log collection by a log management system. It is an example of the hardware block diagram of a log management system. It is an example of a functional block diagram of a log management system. It is an example of the figure explaining log data. It is an example of the flowchart figure which shows the procedure explaining calculation of log file capacity | capacitance. It is an example of the flowchart figure which shows the procedure in which a communication speed calculation part calculates a communication speed. It is an example of the figure which illustrates the calculation method of a communication band typically. It is an example of the flowchart figure which shows the procedure in which a communication band calculation part calculates a communication band. FIG. 6 is an example of a flowchart illustrating a procedure for scheduling a log file transmission timing by a job scheduling unit. It is an example of the figure explaining scheduling of the transmission timing of a log file. It is a figure which shows an example of the communication band which is not uniform. It is an example of the figure explaining evaluation of the uniformity of the communication band with respect to time. It is an example of the figure explaining the determination method of whether to change the transmission timing of the 1st time after rescheduling. It is an example of the sequence diagram which shows the procedure in which a service utilization company transmits a log file, and a log management system calculates prediction data. FIG. 10 is an example of a sequence diagram illustrating a procedure in which a log management system performs scheduling of timing at which a device of a service using company transmits a log file. It is an example of the sequence diagram which shows the procedure in which a log management system transmits the transmission schedule of a log file to a data transmission / reception control apparatus.

Hereinafter, embodiments for carrying out the present invention will be described with reference to the drawings.
FIG. 1 shows an example of a system configuration diagram of a service utilization system 100 of the present embodiment. In the service utilization system 100, the log management system 13 and one or more service utilization companies 11 are connected via a network 12 so as to be communicable. The log collection scheduling of the present embodiment by the log management system 13 on the premise of such a service utilization system 100 will be described.

  FIG. 2 is an example of a diagram illustrating an outline of log collection scheduling by the log management system 13. FIG. 2A schematically shows a communication band on the receiving side in each time zone of the log management system 13. That is, it indicates how much data the log management system 13 receives for each time zone. Although details will be described later, the log management system 13 estimates the used communication band in this way at the time of scheduling.

  FIG. 2B schematically shows the capacity of a log file transmitted by the service using company 11. Each service using company 11 periodically transmits a log file according to a log information collection interval determined by a contract or the like. The log file capacity is a capacity of a plurality of logs transmitted periodically. Further, the vertical width of the log file capacity represents the communication speed. Although the communication speed will be described in detail later, the communication speed is determined by the equipment provided in the service using company 11 that transmits the log file or a contracted communication line company. The communication time can be calculated from the log file capacity and the communication speed.

  The log management system 13 calculates the log file capacity and communication speed as shown in FIG. 2B for each service using company 11 during scheduling (communication time is calculated from these).

  FIG. 2C shows the log collection scheduling of a certain service using company by the log management system 13. The log management system 13 detects a time zone in which the used communication band is the smallest. In this time zone, the service using company 11 having the largest log file capacity is assigned. Note that it is not always necessary to allocate the service using company 11 having the largest log file capacity in the time zone with the least used communication band, and the service using company 11 is given priority to the time zone with the least used communication band. Assign it.

  By doing so, it is possible to assign a service using company 11 that transmits a log file that is likely to be subjected to a communication load in a time zone in which the communication bandwidth is free for the log management system 13.

  FIG. 2D schematically shows the communication band in each time slot after the service using company 11 is assigned to the time slot with the smallest communication band. The log management system 13 allocates the service using company 11 having the next largest log file capacity in the time zone having the smallest communication bandwidth.

  In this way, by repeatedly assigning each service using company 11 to a time zone in which the communication bandwidth is vacant, the communication bandwidth is made uniform, and log file transmission can be prevented from being concentrated in a certain time zone.

<Terminology>
Log file: This is the transmission target when the log is transmitted. A log file is an example of data. In many cases, the log file contains multiple logs. Note that the log and the log file do not have to be strictly distinguished.
Log collection scheduling is to determine the timing (for example, time) at which the log management system collects log files. When the log management system collects the log file, the log file is transmitted when viewed from the device 15.
Used communication band: A communication band that is already used by the log management system 13, and a communication band that is not used is a usable communication band. In this embodiment, the communication band is represented by the same dimension as the communication speed.

<Configuration example>
The service utilization system 100 will be described with reference to FIG. The log management system 13 provides a cloud service that is a service using cloud computing. The log management system 13 is an example of a data collection system. Although the physical configuration of cloud computing is not strictly defined, the log management system 13 includes at least one information processing apparatus. As an example, cloud computing has a plurality of servers, a rack on which a plurality of servers connected by L1 to L3 switches are mounted, a cluster in which a plurality of racks connected by L1 to L3 switches are integrated, and the like. doing. One server may provide a function as a plurality of servers by virtualization, or data storage may be shared by a plurality of servers. Further, the server on which the function of the log management system 13 is mounted does not need to be fixed, and the physical arrangement of the log management system 13 may vary according to the increase in servers and the rearrangement of racks and clusters. As described above, the physical configuration of the log management system 13 of the present embodiment may not be fixed, and the log management system 13 only needs to have the function of the information processing apparatus.

  Note that the log management system 13 can be provided not by cloud computing but by a single information processing apparatus.

  The service using company 11 is a corporation, a natural person, a group or an individual who can make a contract for a cloud service. The service using company 11 can be referred to as a cloud service user or user. Specifically, the service using company 11 includes, for example, a company, a company office, a company factory, an office, a government office, an incorporated association, a foundation, a school corporation, a religious corporation, and an NPO (Nonprofit Organization).

  The service using company 11 uses a device 15 (indicated by reference numerals 15a to 15e in FIG. 1) that generates a log. The device 15 is, for example, an MFP (Multi Function Peripheral) 15a, a projector 15b, a video conference terminal 15c, an electronic whiteboard 15d, or a PC (Personal Computer) 15e, but is not limited thereto. One device 15 may be provided.

  Each device 15 is connected to a data transmission / reception control device 14. The data transmission / reception control device 14 is a kind of information processing device. The data transmission / reception control device 14 collects the logs generated by the devices 15 and transmits the log files of the devices 15 to the log management system 13 according to the schedule determined by the log management system 13.

  Any of the devices 15 may be substituted for the data transmission / reception control device 14. In this case, the independent data transmission / reception control device 14 is not necessary, and the device 15 functions as the data transmission / reception control device 14.

  Further, the functions of the data transmission / reception control device 14 that the data transmission / reception control device 14 and the device 15 serve may be omitted. In this case, each device 15 transmits the log file of each device 15 to the log management system 13 according to the schedule determined by the log management system 13.

<< Hardware configuration >>
FIG. 3 is an example of a hardware configuration diagram of the log management system 13. The log management system 13 shown in the figure does not have to be housed in a single housing or provided as a single device, and is preferably provided in the log management system 13. Indicates an element.

  The log management system 13 includes a CPU 301, ROM 302, RAM 303, HDD 305, display 308, network I / F 309, keyboard 311, mouse 312, media drive 307, and optical drive 314 connected to the bus 310. The CPU 301 executes a program 320 stored in the HD 304 and controls the overall operation of the log management system 13. The ROM 302 stores a program used for driving the CPU 301 such as IPL. The RAM 303 is used as a work area for the CPU 301. The HD 304 is a storage device equipped with a non-volatile memory, and stores a program 320 for performing log management, an OS, OpenStack software for constructing and managing cloud computing, and the like.

  An HDD (Hard Disk Drive) 305 controls reading or writing of various data with respect to the HD 304 according to the control of the CPU 301. The display 308 displays various information such as a cursor, menu, window, character, or image. A network I / F 309 is an interface with the network 12 such as a LAN or the Internet, and communicates with the data transmission / reception control device 14 and the device 15. A keyboard 311 and a mouse 312 are input / output devices. The keyboard 311 includes a plurality of keys for inputting characters, numerical values, various instructions, and the like, and receives inputs from these keys. The mouse 312 accepts movement of the mouse pointer, selection and execution of various instructions, selection of a processing target, and the like.

  The media drive 307 controls reading or writing (storage) of data with respect to the medium 306 such as a flash memory. The optical drive 314 controls reading or writing of various data with respect to a CD-ROM (Compact Disc Read Only Memory) 313 as an example of a removable recording medium.

  The program 320 is a file in an installable or executable format, and may be recorded and distributed on a computer-readable recording medium such as the medium 306 or the CD-ROM 313. Alternatively, the program 320 may be distributed in a form downloaded from an arbitrary server type information processing apparatus.

  The hardware configuration of the data transmission / reception control device 14 may be the same as that of the log management system 13, and is not shown.

<< About log management system functions >>
FIG. 4 shows an example of a functional block diagram of the log management system 13. The log management system 13 includes a transmission / reception unit 23, a log management unit 22, a log storage unit 21, a log analysis unit 25, a predicted data storage unit 24, a job scheduling unit 26, and a job execution timing control unit 27.

  The transmission / reception unit 23, the log management unit 22, the log storage unit 21, the log analysis unit 25, the predicted data storage unit 24, the job scheduling unit 26, and the job execution timing control unit 27 have the CPU 301 store the program 320 stored in the HD 304. It is a function or means realized by executing and cooperating with the hardware shown in FIG.

  The log management system 13 includes a log data storage unit 31, a service using company data storage unit 32, a predicted data storage unit 33, a communication log storage unit 34, and a log transmission schedule storage unit 35. The log data storage unit 31, the service company data storage unit 32, the prediction data storage unit 33, the communication log storage unit 34, and the log transmission schedule storage unit 35 are constructed in, for example, the HD 304, the RAM 303, the media 306, the CD-ROM 313, or the like. Database or storage area. These need only exist on the network 12 accessible by the log management system 13 and may not be owned by the log management system 13.

  The transmission / reception unit 23 receives a log from the service using company 11 or notifies the service using company 11 of log transmission timing.

  The log management unit 22 collects, stores, and analyzes logs. That is, overall control related to log management is performed.

  The log storage unit 21 stores (stores) the log in the log data storage unit 31. For example, a log is stored for each service using company 11. When the service using company 11 has a plurality of devices 15, it is stored for each device 15. Further, for example, a log whose storage period has expired is deleted, compressed and stored in a large-capacity storage medium.

  The log analysis unit 25 analyzes the log and calculates prediction data. The log analysis unit 25 refers to the service using company data storage unit 32 as necessary. The predicted data is a log file capacity, a communication speed, and a communication band. Here, the predicted data is an estimated log file capacity, communication speed, and communication band at the next log file transmission timing. In order to calculate the prediction data, the log analysis unit 25 includes a log file capacity calculation unit 251, a communication speed calculation unit 252, and a communication band calculation unit 253. Details of these will be described later. The prediction data storage unit 24 stores the prediction data in the prediction data storage unit 33.

  The job scheduling unit 26 schedules log collection timing based on the prediction data. The log collection timing is the log transmission timing when viewed from the device 15, and the log transmission timing or the log collection timing scheduling result is hereinafter referred to as a log transmission schedule. The job scheduling unit 26 stores the log transmission schedule obtained by scheduling in the log transmission schedule storage unit 35. Details will be described later. The job scheduling unit 26 is an example of a transmission timing assignment unit.

  The job execution timing control unit 27 reads the log transmission schedule stored in the log transmission schedule storage unit 35 and requests each service user 11 to transmit a log file. As a result, log files can be collected.

  Next, data held by the log data storage unit 31, the service using company data storage unit 32, the predicted data storage unit 33, the communication log storage unit 34, and the log transmission schedule storage unit 35 will be described.

<< Log data >>
An example of some log data will be described with reference to FIG. Log data as shown in FIG. 5 is transmitted from the service using company 11 and stored in the log data storage unit 31.

FIG. 5A shows an example of a log related to the print function of the MFP that is one of the devices 15. In FIG. 5A, each log is associated with a line number, job time, user ID, job name, job result, file type, file ID, file size, and job time. Each field will be described.
Line number: Log identification information Job time: Time when job execution is started (job is a unit of execution of the function of the device 15)
User ID: Identification information of service using company 11 Job name: Name of job used by user Job result: Job execution result File type: Printed document type File ID: Document identification information file size given by MFP : Printed document size Job time: Time required from the start to the end of printing (an example of time information)
The MFP 15a supports cloud printing. Cloud printing means that a client (such as the PC 15e) deposits a document to be printed in a cloud service, and the user downloads the document to the MFP 15a at an arbitrary location and timing, and the MFP 15a prints it.

  Since the file type and file size are registered in the logs of line numbers 2 and 4, it can be seen that the job of line numbers 2 and 4 is cloud print. The files with line numbers 2 and 4 are files received by the MFP 15a from the cloud service.

  Note that the PC 15e transmits the file to the cloud service in advance. Thus, when a file is transmitted and received using a cloud service, a file transmission event (hereinafter referred to as a file transmission event) from the service using company 11 to the log management system 13 has occurred. The log of the PC 15a is also stored in the log data storage unit 31, and the log management system 13 can acquire the log of the file transmission event.

  FIG. 5B shows an example of a log related to the scan function of the MFP 15 a that is one of the devices 15. The MFP 15a supports cloud scanning. Cloud scanning means that the user causes the MFP 15a to read a document and deposits image data created by the MFP 15a in a cloud service. The user can download the image data to the MFP 15a at any place and timing and print it on the MFP 15a. The PC 15e can also download.

  The log field in FIG. 5B is the same as the log in FIG. Since the file type and file size are registered in the logs of line numbers 2 and 4, it can be seen that the job of line numbers 2 and 4 is a cloud scan. That is, the log of line numbers 2 and 4 indicates that a file transmission event is included.

  FIG. 5C shows an example of a log of the electronic whiteboard 15 d that is one of the devices 15. The log field in FIG. 5C is the same as the log in FIGS. Note that the electronic whiteboard 15d corresponds to a cloud service. The electronic whiteboard 15d deposits a file used in a meeting or the like in a cloud service, and a user downloads the file to the electronic whiteboard 15d at an arbitrary place and timing, and the electronic whiteboard 15d displays or prints the file. be able to. In FIG. 15C as well, the logs with line numbers 2 and 4 indicate that file transmission events are included.

  In addition, logs of the projector 15b and the video conference terminal 15c are also stored in the log data storage unit 31. The projector 15b and the video conference terminal 15c also support the cloud service, and can send and receive files.

表１はサービス利用企業データの一例を模式的に示す図である。サービス利用企業データ記憶部３２には表１のようなサービス利用企業データが記憶されている。サービス利用企業データには、ユーザＩＤに対応づけて、保有機器、台数、ログ情報収集間隔が登録される。ログ情報収集間隔は、ログ管理システム１３がログファイルを収集する収集周期、又は、サービス利用企業１１がログファイルをログ管理システム１３に送信する送信周期である。したがって、ログ管理システム１３はサービス利用企業データを参照することで、サービス利用企業１１が保有する機器１５、各機器１５の台数、及び、ログファイルを収集する周期を読み出すことができる。 << Service using company data >>

Table 1 is a diagram schematically showing an example of service using company data. The service use company data storage unit 32 stores service use company data as shown in Table 1. In the service use company data, the owned device, the number of units, and the log information collection interval are registered in association with the user ID. The log information collection interval is a collection cycle in which the log management system 13 collects log files, or a transmission cycle in which the service using company 11 transmits log files to the log management system 13. Therefore, the log management system 13 can read the device 15 owned by the service using company 11, the number of each device 15, and the period for collecting the log files by referring to the service using company data.

  It should be noted that a provider (such as an operator of a log management system) that provides a log management cloud service can register the owned device, the number of units, and the log information collection period in the service use company data storage unit 32.

表２は、予測データのうちログファイル容量と通信時間の一例を示す図である。ログファイル容量と通信時間がユーザＩＤ及びログ情報収集間隔に対応づけて登録されている。 << Forecast data >>

Table 2 is a diagram showing an example of the log file capacity and the communication time in the prediction data. The log file capacity and communication time are registered in association with the user ID and the log information collection interval.

表３は予測データのうち通信帯域の一例を示す。この通信帯域は使用済みの通信帯域であり、例えば、予め既知の最大の通信帯域から使用済みの通信帯域を減じた通信帯域が利用可能な通信帯域である。表３では、０時台〜２３時台までどの程度の通信帯域が使用済みかが登録されている。使用済みの通信帯域が１時間単位でなく例えば１０分単位の通信帯域を保持することも可能である。

Table 3 shows an example of the communication band in the prediction data. This communication band is a used communication band. For example, a communication band obtained by subtracting a used communication band from a known maximum communication band in advance can be used. In Table 3, it is registered how much communication band has been used from 0:00 to 23:00. It is also possible to hold a used communication band in units of 10 minutes instead of an hour unit.

  In Table 3, the communication bandwidth is shown in a table shape, but it can be expressed as shown in FIG. 2A by graphing the used communication bandwidth in a stepwise manner with respect to the time axis.

表４は通信ログの一例を模式的に示す図の一例である。通信ログ記憶部３４には表４のような通信ログが記憶されている。通信ログは、ログ管理システム１３の送受信部２３がデータを受信した際の通信を記録したものである。通信ログを用いてログ管理システム１３の通信帯域が計算される。 << Communication log >>

Table 4 is an example of a diagram schematically illustrating an example of a communication log. A communication log as shown in Table 4 is stored in the communication log storage unit 34. The communication log is a record of communication when the transmission / reception unit 23 of the log management system 13 receives data. The communication bandwidth of the log management system 13 is calculated using the communication log.

  The data received by the transmission / reception unit 23 includes all data received by the log management system 13 such as files transmitted / received by the cloud service, in addition to log files. Therefore, it is possible to estimate how much data the log management system 13 has received from the communication log. The log of only the data received by the communication log is sufficient because it is a two-way communication of transmission and reception, but if the transmission of data also affects reception, consider the data on the transmission side Also good.

The communication log is sorted by, for example, the communication start time, and has a process ID, a received file size, and a reception time.
Communication start time: Time when the log management system 13 starts to receive data Processing ID: Communication log identification number Received file size: Size of received file (not limited to log file) Received time: Entire received file Time required for reception The communication speed can be calculated by dividing the received file size by the reception time. Since this communication speed uses the communication resource of the log management system 13 over the reception time, a value obtained by accumulating the communication speed over the reception time from the communication start time becomes the used communication band.

表５はログ送信スケジュールの一例を模式的に示す図の一例である。ログ送信スケジュール記憶部３５には表５のようなログ送信スケジュールが記憶されている。ログ送信スケジュールには、各サービス利用企業１１がログファイルをログ管理システム１３に送信を開始する時刻（すなわちタイミング）が登録されている。送信を開始する時刻だけでなく送信が終了する時刻も登録してよい。送信が終了する時刻にログファイルの送信が完了しない場合も生じうるが、この場合はログファイルの全体の送信が完了するまで送信が継続される。 << Log transmission schedule >>

Table 5 is an example of a diagram schematically illustrating an example of a log transmission schedule. The log transmission schedule storage unit 35 stores a log transmission schedule as shown in Table 5. In the log transmission schedule, a time (that is, timing) at which each service using company 11 starts transmitting a log file to the log management system 13 is registered. Not only the time when transmission starts but also the time when transmission ends may be registered. There may be a case where the transmission of the log file is not completed at the time when the transmission is completed. In this case, the transmission is continued until the entire transmission of the log file is completed.

<< About the functions of service companies >>
As shown in FIG. 4, the service using company 11 includes a data transmission / reception control device 14 and one or more devices 15. The data transmission / reception control device 14 has a log acquisition unit 141. The log acquisition unit 141 is a function or means realized by the CPU 301 executing a program stored in the HD 304 and cooperating with the hardware shown in FIG. The log acquisition unit 141 acquires logs from each device 15 according to the log transmission schedule determined by the log management system 13.

<Calculation of forecast data>
Hereinafter, a calculation method of the log file capacity, the communication speed, and the usable communication band will be described as the prediction data.

<< Log file size >>
The log file capacity calculation unit 251 analyzes the log and calculates the log file capacity. The log file capacity is the size of the log file transmitted by the service using company 11 at each transmission timing (every log information collection interval). The log file capacity is the total size of logs for each function of the device 15 of one service using company 11. For example, it is assumed that the service using company 11 has the MFP 15a. When the MFP 15a has a login function, a print function, and a scan function, first, a log file capacity is calculated for each function. The log file capacities of the login function, print function, and scan function are totaled. The data transmission control device 14 transmits at one transmission timing by calculating the total log file capacity of each function for other devices 15 and totaling the log file capacities of all the devices 15 possessed by the service using company. Calculate the log file capacity.

  As described above, the log management system 13 calculates the log file capacity based on the information described in the log, and assigns the service using company to the time zone with the most available communication band based on the log file capacity and the like. This is one of the features of the form.

  FIG. 6 is an example of a flowchart showing a procedure for explaining the calculation of the log file capacity. The procedure in FIG. 6 starts when the log management system 13 receives a log file.

  First, the log file capacity calculation unit 251 reads the log information collection interval stored in the service using company data storage unit 32 (S10). The log information collection interval is a period for calculating the total log file capacity for each function.

  Next, the log file capacity calculation unit 251 refers to the log of the log data storage unit 31 and counts the number of executions of the job at the log information collection interval for each function (S20).

表６はステップＳ２０のカウント結果の一例を示す。表６ではサービス利用企業（ユーザＩＤ）ごとに、ログ情報収集間隔において各機器が各機能を利用したジョブ実行回数（すなわち、機能が利用された利用回数）が登録されている。例えば、ユーザＩＤ（０００１）のログ情報収集間隔は１時間である。このサービス利用企業では１時間にLP0001という機器１５のログインという機能を１０回利用し、クラウドプリントという機能を５回利用している。

Table 6 shows an example of the count result of step S20. In Table 6, for each service using company (user ID), the number of job executions (that is, the number of times the function has been used) that each device has used each function in the log information collection interval is registered. For example, the log information collection interval of the user ID (0001) is 1 hour. In this service use company, the function called login of the device 15 called LP0001 is used 10 times per hour, and the function called cloud print is used 5 times.

  The log file capacity calculation unit 251 acquires similar information from the previous log information collection interval, the previous log information collection interval, and the past log information collection interval. For example, assume that the login function of the device 15 having the latest log information collection interval is A times, the login function of the previous log information collection interval is B times, and the login function of the previous log information collection interval is C times. The number of log information collection intervals in which the number of job executions is counted is N (3 times for the most recent, previous, and last time).

The log file capacity calculation unit 251 obtains the average number of job executions at each log information collection interval (S30).
Average number of job executions = (A times + B times + C times) / N
This is the average job execution count of the login function of a certain device 15 in the log information collection interval.

  Next, the log file capacity calculation unit 251 calculates the log file capacity at the log information collection interval of the function of interest (S40). A log is created for each job execution, but the size of one log is almost constant. On the other hand, the number of log lines created for each function may differ. Therefore, the log file capacity calculation unit 251 holds the number of log lines for each function in advance.

表７は各機器の機能ごとのログの行数を示す。ログファイル容量算出部２５１は機能ごとにログ行数を表７から読み出すことができる。また、ログの１行あたりのログサイズは、例えば数百バイトのように固定的に見積もることができる。ログファイル容量は、ジョブ実行回数の平均に１つのログの行数とログの１行あたりのログサイズを乗算することで求められる。ログファイル容量算出部２５１は以下の式からログ情報収集間隔における１つの機能のログファイル容量を算出できる。ログファイル容量算出部２５１は機能ごとにこの計算を行う。
ジョブ実行回数の平均×１つのログの行数×ログの１行あたりのログサイズ
次に、ログファイル容量算出部２５１はステップＳ４０で求めた機能ごとのログファイル容量（乗算結果）の合計を算出する（Ｓ５０）。

Table 7 shows the number of log lines for each function of each device. The log file capacity calculation unit 251 can read the number of log lines from Table 7 for each function. Further, the log size per line of the log can be fixedly estimated, for example, several hundred bytes. The log file capacity is obtained by multiplying the average number of job executions by the number of lines in one log and the log size per line of the log. The log file capacity calculation unit 251 can calculate the log file capacity of one function at the log information collection interval from the following formula. The log file capacity calculation unit 251 performs this calculation for each function.
Average number of job executions x number of lines in one log x log size per log line Next, the log file capacity calculation unit 251 calculates the total log file capacity (multiplication result) for each function obtained in step S40. (S50).

  Then, the log file capacity calculation unit 251 performs the same calculation for each device 15, and totals the log file capacity for each device 15 (S60). Thereby, the log file capacity transmitted by one service using company 11 at one transmission timing can be calculated.

<< Communication speed calculation >>
The communication speed is a communication speed when the service using company 11 transmits data to the log management system 13. The data used for calculating the communication speed is not particularly limited, but in this embodiment, the communication speed when the device 15 transmits the log file to the log management system 13 by cloud print or cloud scan is used.

  FIG. 7 is an example of a flowchart illustrating a procedure for the communication speed calculation unit 252 to calculate the communication speed. 7 starts when the log management system 13 receives a log file.

  The communication speed calculation unit 252 refers to the log of the service using company 11 that has transmitted the log file, and extracts the log of the file transmission event (S10). The file size and job time are described in the file transmission event log.

  The communication speed calculation unit 252 calculates the communication speed of the file (S20). The communication speed of the file is calculated by dividing the file size by the job time.

  The communication speed calculation unit 252 totals the communication speeds (division results) calculated from all the file transmission events of the service using company 11 that transmitted the log files (S40).

  Next, the communication speed calculation unit 252 calculates the average communication speed by dividing the total calculated in step S40 by the number of file transmission events (S50). The average of the communication speed is determined as the communication speed as prediction data.

  As described above, the log management system 13 calculates the communication speed from the information described in the log, and assigns the service using company to the most available time zone based on the communication speed. It is one.

  Note that the communication speed as the prediction data may be a median in addition to the average. For example, the median communication speed calculated from all the file transmission events calculated in step S40 is used as the communication speed as prediction data. Alternatively, a range of 2σ with respect to the average may be used as the communication speed as the prediction data. For example, if the average + 2σ is the communication speed as the prediction data, the communication speed can be estimated quickly, and the log file collection time of the entire service using company can be shortened. Further, if the average -2σ is the communication speed as the prediction data, the communication speed can be estimated slowly, and scheduling with a margin for the communication band of the log management system 13 becomes possible. The communication speed is not limited to the average + 2σ or the average −2σ, and may be any value in the range of average ± 2σ.

<< Calculation of communication bandwidth >>
FIG. 8 schematically illustrates an example of a communication band calculation method, and FIG. 9 illustrates an example of a flowchart illustrating a procedure for the communication band calculation unit 253 to calculate a communication band. The procedure of FIG. 9 is executed before, for example, scheduling of the transmission log.

  First, the communication band calculation unit 253 calculates a communication band use record for each time period (S10). The communication band shown in FIG. 8A is a communication band use record showing how much communication band has been used as viewed from the log management system 13. In the calculation of the communication band usage record, the communication band is calculated for all data received by the log management system 13 as well as the log file and file transmission event file transmitted by the service using company 11. The communication band calculation unit 253 calculates, for example, a communication band usage record every hour. FIG. 8 shows time zones for every hour from 0 to 23:00.

  The communication band calculation unit 253 reads the communication log stored in the communication log storage unit 34 and specifies the time zone based on the communication start time. That is, if 13:30 is the communication start time, the time zone is 13:00. The communication band calculation unit 253 reads the reception file size and reception time from the communication log in Table 4, calculates “reception file size ÷ reception time”, and calculates the communication speed. This communication speed can be interpreted as a used communication band for the login management system. Therefore, the used communication band can be calculated by adding the communication speeds of all the communication logs in one day for each time period.

  Since the communication band usage record for only one day may include a communication band due to the sudden communication performed by the log management system 13, the communication band calculation unit 253 calculates an average for each time interval (S20). . FIG. 8B shows a communication band in each time zone on the day different from FIG. 8A.

The communication bandwidth calculation unit 253 calculates an average communication bandwidth for each time zone by adding the communication bandwidth for each time zone and dividing by the number of days. For example, in FIG. 8A, there are used communication bands 51A and 51B at the time of 0:00. In FIG. 8B, there are used communication bands of communication bands 51C to 51E in the 0:00 range. Therefore, the average value of the used communication bands can be obtained by dividing the total of the communication bands 51A to 51E by 2 days.
(51A + 51B + 51C + 51D + 51E) / 2 days 1 o'clock, 2 o'clock to 23 o'clock can be calculated similarly.

  For the service using company 11 whose log information collection interval is once a day, the communication band may be calculated as described with reference to FIGS.

  By the way, since the log information collection interval is different for each service using company 11, it is preferable to calculate the communication band in accordance with the log information collection interval. For the service using company 11 whose log information collection interval is once a week, the communication band calculating unit 253 sets the daily communication band for each day of the week (the service using company 11 is to transmit the log file). Is calculated. That is, the communication band calculation unit 253 calculates a daily communication band for the same day of the week, and calculates an average for each time period. For example, if it is Monday, the communication bandwidth of the past Monday is calculated, and the average is calculated for each time zone.

  For the service using company 11 whose log information collection interval is once a month, the communication band calculating unit 253 sets the daily communication band for each day (the service using company 11 is supposed to transmit the log file). Is calculated. That is, the communication band calculation unit 253 calculates the communication band for one day only on the same day in the month (for example, the first day or the 31st day), and calculates the average for each time period. In this way, the communication band corresponding to the log information collection interval can be calculated.

<< Scheduling of log file transmission timing >>
FIG. 10 is an example of a flowchart illustrating a procedure for scheduling the log file transmission timing by the job scheduling unit 26. As will be described later, for example, the job scheduling unit 26 allocates the service user company of the log file having the largest log file capacity to the time zone in which the communication band is vacant (S10). This process is performed for each log information collection interval of each service using company and for each service using company.

  That is, the log file transmission timing is assigned to each service using company 11 for the service using company 11 whose log information collection interval is once a day. Next, the log file transmission timing is assigned to each service using company 11 for the service using company 11 whose log information collection interval is once a week. Next, the log file transmission timing is assigned to each service using company 11 for the service using company 11 whose log information collection interval is once a month.

  The log file transmission timing scheduling will be described with reference to FIG. Note that the scheduling is performed at a fixed timing such as once a month, once every six months, or once a year.

  FIG. 11A shows an example of a communication band as prediction data. Table 8 shows an example of the log file capacity and communication speed as prediction data described for explanation.

ジョブスケジューリング部２６は予測データとしてのログファイル容量、通信容量、及び、通信帯域を用いてサービス利用企業１１にログ収集のためのタイミングを割り当てる。すなわち、以下のような規則に基づき、サービス利用企業１１がログファイルをログ管理システム１３に送信するタイミングを決定する。

The job scheduling unit 26 assigns a log collection timing to the service using company 11 by using the log file capacity, the communication capacity, and the communication band as prediction data. That is, based on the following rules, the service utilization company 11 determines the timing for transmitting the log file to the log management system 13.

The job scheduling unit 26 allocates one of the following service using companies 11 in the time zone with the lowest communication bandwidth.
Assign the log file service company 11 with the largest log file capacity. Assign the log file service company 11 with the fastest communication speed. Assign the log file service company 11 with the longest communication time. The log management system 13 allocates a log file with a large communication load first. That is, one or more of the log file capacity, communication speed, or communication time is an example of communication load information. As a result, since log files with a large communication load are reduced later in the scheduling, the communication band is prevented from being occupied non-uniformly, and log transmission to the log management system 13 is less likely to be concentrated.

  In the following, for convenience of explanation, the log file having the largest log file capacity is described as being given priority. However, the log file having the fastest communication speed or the log file having the longest communication time may be given priority. The log file capacity is an area of a rectangular area of communication speed × communication time.

  Referring to FIG. 11A, there is a time zone with the lowest communication band at 0:20. Also, referring to Table 8, it can be seen that the service using company with the largest log file capacity is the service using company with the user ID “0003”. Therefore, the log file of the service using company whose user ID is “0003” is assigned to 0:20. As a result, as shown in FIG. 11B, the log file 52a is allocated in the time zone from 0:20 to 0:30. That is, a time and a communication band for the service user 11 to transmit the log file 52a of 10 minutes (600 seconds = 60000 bytes × 8 bits / 800 kbps) at a communication speed of 800 [kbps] are secured.

  Next, referring to FIG. 11C, there is a time zone with the lowest communication band at 0:50. Also, referring to Table 8, it can be seen that the user ID of the service using company 11 having the next largest log file capacity is “0001”. Therefore, as shown in FIG. 11D, the log file 52b of the service using company 11 whose user ID is “0001” is assigned to 0:50. That is, a time and a communication band for the service using company 11 to transmit the log file 52b of 10 minutes (600 seconds) at a communication speed of 400 [kbps] are secured.

  The time for transmitting the log file set in this way is stored in the log transmission schedule storage unit 35.

  Since the job scheduling unit 26 assigns the log file having the largest log file capacity to the time zone having the lowest communication band in this way, the large log file can be preferentially transmitted. That is, since the communication band is secured preferentially for a log file that is likely to be subjected to a communication load, it is easy to suppress log concentration even if the remaining log file having a relatively small log file capacity is allocated.

<< More detailed control of scheduling >>
When a log file is assigned to a time zone with the lowest communication bandwidth, the communication bandwidth may not necessarily be uniform. FIG. 12 is a diagram illustrating an example of a non-uniform communication band. When the log file 52c is assigned to the time zone with the lowest communication bandwidth, it is determined in FIG. 12A that the log file is assigned at time 0:20. However, the communication time of the log file 52c is longer than the time zone (0:20 to 0:30) with the lowest communication band.

  For this reason, as shown in FIG.12 (b), the communication band after 0:30 will become large. In such a case, the job scheduling unit 26 detects that the communication band as a result of scheduling is higher than the highest communication band (0:40 to 0:50). Then, as shown in FIG. 12C, for example, the log file 52c is scheduled in a time zone (0:50 past) where the communication band is next lower. Thereby, it can suppress that the maximum value of a communication band becomes high.

  Alternatively, it is also effective to divide the log file as shown in FIG. Prior to scheduling, the job scheduling unit 26 detects a time zone having the lowest communication band and compares it with the communication time of the log file 52c. When “communication time> the time zone with the lowest communication bandwidth”, the log file 52c is divided so that the communication time of the log file 52c is equal to or less than the time zone with the lowest communication bandwidth.

  The log file 52c is divided into the log file 52c1 and the others. The job scheduling unit 26 can divide the log file 52c into a log file 52c2 and a log file 52c3 by performing the same processing on the remaining log files that have been divided. Therefore, it becomes easy to equalize the communication band with respect to time.

  In this way, the service using company 11 having the largest log file capacity is not allocated to the time zone having the smallest used communication bandwidth, but the service using enterprise 11 is assigned with priority to the time zone having the least used communication bandwidth. It is also possible.

  It should be noted that, if the communication time is divided to be too short, the overhead increases and the communication efficiency is lowered. Therefore, it is preferable to provide a prohibition such as not dividing the communication time less than the minimum communication time (for example, 2 minutes).

  Further, since the actual communication band is not likely to be linear as shown in the figure, it is considered that the communication band is constant within a certain range of fluctuation. This facilitates comparison between the communication time and the time zone with the lowest communication band.

<About rescheduling>
In one scheduling, there is a possibility that the communication band with respect to time is not equalized. Therefore, the job scheduling unit 26 evaluates the uniformity of the communication band with respect to time and determines whether to perform scheduling again.

  FIG. 13A is an example for explaining the evaluation of the uniformity of the communication band with respect to time. For example, when the difference 54a between the lowest communication band and the highest communication band is equal to or greater than the threshold value, the job scheduling unit 26 determines to perform log file transmission scheduling again. If rescheduling is performed based on such evaluation, it is possible to suppress the concentration of log file transmission timings.

  Further, as shown in FIG. 13B, it may be determined whether to perform the scheduling again based on the sum of the height differences. The job scheduling unit 26 detects increase / decrease in the communication band in ascending or descending order of time, and accumulates absolute values of the height differences 54b to 54e. In the example of FIG. 13B, the height difference 54b + the height difference 54c + the height difference 54d + the height difference 54e is calculated. When the accumulated value is equal to or greater than the threshold value, it is determined that scheduling is performed again. If rescheduling is performed based on such evaluation, it is possible to suppress non-uniform communication bands that may occur depending on time zones.

  In addition, when the job scheduling part 26 performs scheduling again, it is preferable to change the rule which allocates the service utilization company 11 to a time slot | zone. For example, if the service user company 11 having the largest log file capacity is assigned to the time zone with the lowest communication bandwidth immediately before, the next time the log file with the highest communication speed is assigned to the time zone with the lowest communication bandwidth. All service using companies 11 are allocated. Thereby, it can be expected that the communication band becomes more uniform by rescheduling.

<< Send log file after rescheduling >>
When rescheduling is performed regularly or by reviewing uniformity, the time from the last log file transmission to the next log file transmission may be longer than the log information collection interval. Conversely, due to rescheduling, a situation may occur in which the time from the last log file transmission to the next log file transmission is shorter than the log information collection interval. In such a case, the actual log file capacity is likely to change with respect to the log file capacity as the prediction data.

  Therefore, the job execution timing control unit 27 determines whether or not to change the first transmission timing after rescheduling for each case. FIG. 14 is an example for explaining a method for determining whether to change the first transmission timing after rescheduling.

Case 1) When the next transmission is executed after the elapse of the time within the log information collection interval As shown in FIG. 14A, a service using company 11 transmits a log file 52d at a timing of 0:10. In addition, rescheduling was performed in parallel during this time period, and the process was completed at around 0:30.

  As shown in FIG. 14B, it is assumed that the transmission timing of the log file 52e of the service using company 11 is changed from 0:10 to 0:50. On the other hand, the log information collection interval of the service using company 11 is once a day.

  In this case, the job execution timing control unit 27 causes the log file 52e to be transmitted to the device 15 of the service using company 11 at the transmission timing that comes 20 minutes later. In this case, the log file 52e can be transmitted at the scheduled timing because the estimated transmission amount is not exceeded.

Case 2) When the next transmission is executed after the elapse of the log information collection interval or more, as shown in FIG. 14C, it is assumed that rescheduling is performed at 0: 0 to 0:30. Assume that the transmission timing of the log file 52f of a certain service user 11 before rescheduling is 0:30.

  As shown in FIG. 14D, the transmission timing of the log file 52f of the service using company 11 is rescheduled from 0:30 to 0:10. On the other hand, the log information collection interval of the service using company 11 is once a day.

  In this case, the job execution timing control unit 27 transmits the log file 52f in two steps. For example, since the transmission timing arrives after about 24 hours, a part (for example, half) of the log file 52f is first transmitted 12 hours before the next transmission timing. When the transmission timing after rescheduling arrives (after about 24 hours), the remaining log file 52f is transmitted. In this case, it is conceivable that the log file capacity exceeds the assumed transmission amount. Therefore, by performing transmission in small portions, it is possible to prevent the second and subsequent transmissions from being affected.

<Operation procedure>
FIG. 15 is an example of a sequence diagram illustrating a procedure in which the service using company 11 transmits a log file and the log management system 13 calculates predicted data.
S1: The data transmission / reception control device 14 confirms the transmission schedule. This transmission schedule is notified from the log management system 13 as described in FIG.
S2: The data transmission / reception control device 14 starts processing for log transmission when it is time to transmit the log file.
S3: The log acquisition unit 141 of the data transmission / reception control device 14 requests the device 15 to log. The device 15 sequentially stores logs generated as functions are executed, and the log acquisition unit 141 acquires logs of log information collection intervals from the device 15.
S4: The data transmission / reception control device 14 transmits the log file to the log management system 13. The transmission / reception unit 23 of the log management system 13 receives the log file.
S5: The transmission / reception unit 23 sends the log file to the log management unit 22.
S6: The log management unit 22 sends the log file together with the log analysis request to the log analysis unit 25.
S7: When receiving the log file, the log analysis unit 25 acquires a communication log. The communication log is acquired in order to calculate a communication band as predicted data.
S8: The log analysis unit 25 calculates prediction data.
S9: The prediction data storage unit 24 sends the prediction data to the prediction data storage unit 24. The predicted data storage unit 24 stores the predicted data in the predicted data storage unit 33.
S10: The log management unit 22 sends the log file to the log storage unit 21. As a result, the log storage unit 21 stores the log file in the log data storage unit 31.

FIG. 16 is an example of a sequence diagram illustrating a procedure in which the log management system 13 performs scheduling of the timing at which the device 15 of the service using company 11 transmits the log file. The procedure shown in FIG. 16 starts, for example, at a fixed periodic timing (once every month, once every six months, or once a year) or according to the evaluation result of uniformity.
S1: The log management unit 22 of the log management system 13 requests the job scheduling unit 26 to schedule log file transmission timing.
S2: The job scheduling unit 26 schedules the log file transmission timing using the prediction data.
S3: The job scheduling unit 26 stores the log transmission schedule as a result of the scheduling in the log transmission schedule storage unit 35.

FIG. 17 is an example of a sequence diagram illustrating a procedure in which the log management system 13 transmits a log file transmission schedule to the data transmission / reception control device 14.
S1: The log management unit 22 requests the job execution timing control unit 27 to control the timing of job execution. This job execution is collection of log files.
S2: The job execution timing control unit 27 reads the log transmission schedule from the log transmission schedule storage unit 35. Then, the following processing is performed for each service using company 11.
S3: The job execution timing control unit 27 sends a log transmission timing notification to the transmission / reception unit 23 when the log file transmission timing for any service using company 11 is reached.
S4: The transmission / reception unit 23 transmits a log transmission timing notification to the service user company 11 that has reached the transmission timing of the log file. As a result, as shown in FIG. 15, the service using company 11 transmits the log file to the log management system 13.

<Other application examples>
The best mode for carrying out the present invention has been described above with reference to the embodiments. However, the present invention is not limited to these embodiments, and various modifications can be made without departing from the scope of the present invention. And substitutions can be added.

  For example, in this embodiment, log transmission has been described. However, data transmitted from a service user company to a log management system may not be a log file. For example, a file used for printing or the like created by an application program, a file of image data generated by scanning a document, or the like may be transmitted.

  Also, the functions of the devices illustrated in FIG. 4 and the like are conceptual and do not need to be physically combined as illustrated. The log management system 13 described in the embodiment may be configured by being incorporated in various systems according to applications and purposes, or may be implemented as a system in which the functional units of the log management system 13 are distributed or integrated. .

  In this embodiment, the communication band is represented by the same dimension as the communication speed. However, the communication band may be represented by another physical quantity such as a frequency band.

  Further, in the present embodiment, the communication band is described as being in units of 1 hour or 10 minutes. However, a communication band of 10 minutes untimed time or longer than 1 hour may be calculated.

DESCRIPTION OF SYMBOLS 11 Service utilization company 12 Network 13 Log management system 14 Data transmission / reception control apparatus 15 Equipment 21 Log storage part 22 Log management part 23 Transmission / reception part 24 Predictive data storage part 25 Log analysis part 26 Job scheduling part 27 Job execution timing control part 31 Log data Storage unit 32 Service utilization company data storage unit 33 Predictive data storage unit 34 Communication log storage unit 35 Log transmission schedule storage unit 100 Service utilization system

JP 2013-045313 A

Claims (13)

A data collection system that collects data from a device used by a user via a network,
Data receiving means for receiving data from the device;
A communication load estimation unit that estimates a communication load of the data reception unit for each user using past data received by the data reception unit;
A communication band estimating means for estimating a used communication band for each time period from a communication log held by the data collection system;
Transmission timing assigning means for assigning the timing at which the user's device with the largest communication load estimated by the communication load estimating means transmits data to a time zone in which there is a communication band available for receiving data from the device. And a data collection system. The communication load estimation means estimates the capacity of data to be transmitted next time for each user using the past data received by the data reception means as the communication load,
The transmission timing allocating unit allocates a timing at which a user device having the largest amount of data estimated by the communication load estimating unit transmits data to a time zone in which the available communication band is present. The data collection system described in The communication load estimating means estimates, as the communication load, the communication speed when the device transmits data from the file size described in the data and the time information required for transmission for each user,
The transmission timing allocating unit allocates a timing at which a user's device having the highest communication speed of the data estimated by the communication load estimating unit transmits data to a time zone in which the available communication band is present. The data collection system described in The communication load estimation means estimates the communication time required for the device to transmit data from the capacity and the communication speed as the communication load for each user.
The said transmission timing allocation means allocates the timing which the said user's apparatus with the longest communication time estimated by the said communication load estimation means transmits data to the time slot with the said available communication band. Data collection system.   The transmission timing allocating means includes a user who has the largest capacity of data, a user who has the earliest communication speed, or a user who has the longest communication time in a time zone in which the used communication band is the lowest. The data collection system according to claim 4, wherein the process of assigning the timing at which any device transmits data is repeated for all users. When the time zone in which the used communication band is the lowest is shorter than the communication time of the user having the largest capacity of data, the transmission timing allocation means sets the time in which the used communication band is the lowest. The device of the user with the largest capacity does not assign a timing for transmitting data,
The timing at which the device of the user with the largest capacity transmits data in the time zone with the lowest communication band among the used communication bands having a time period equal to or longer than the communication time of the user with the largest capacity. The data collection system according to claim 4, wherein the data collection system is assigned. When the time zone in which the used communication band is the lowest is shorter than the communication time of the user having the largest capacity of data, the transmission timing allocation means is configured to use the communication time in which the communication time of the data is used. Divide the data with the largest capacity so that is below the lowest time zone,
The data collection system according to claim 4, wherein the divided data is assigned to a time zone in which the used communication band is the lowest, thereby assigning a timing at which the user device having the largest capacity transmits data. After the transmission timing assigning unit has performed processing for all users, the process of assigning the timing at which the user's device transmits data in the time zone in which the used communication band is the lowest,
The transmission timing assigning means evaluates the uniformity of the communication band with respect to the time zone, and determines whether or not to perform again the process of assigning the timing at which the user device transmits data according to the evaluation result. Item 8. The data collection system according to any one of Items 1 to 7. Since the transmission timing assigning means assigns the timing at which the user device transmits data, when the next transmission timing arrives in a time shorter than the data transmission cycle predetermined for each user, the next transmission Send data to the user's device at the timing,
When the next transmission timing arrives in a time longer than the data transmission cycle predetermined for each user, a part of the data is transmitted to the user's device at a timing before the next transmission timing. The data collection system according to claim 1, further comprising a data transmission control unit. When the device used by the user has a plurality of functions, the communication load estimating means calculates an average number of times of use for each function in a data transmission cycle predetermined for each user from past data, Multiplying the log size output by the use of one function by the average number of use, and adding the multiplication result for each function to calculate the data size of one device,
The data collection system according to claim 2, wherein the capacity of data to be transmitted next time by a user's device is estimated by summing the sizes of data of the devices. The communication load estimating means divides the file size described in the data of the file transmission event among the data received by the data receiving means by the time information required for transmission,
The average of dividing a total of a plurality of division results by the number of file transmission events, a median value of the plurality of division results, or an arbitrary value in a range of the average ± 2σ is estimated as the communication time. 4. The data collection system according to 4. The communication band estimation means divides one day into a plurality of time zones, calculates the communication bandwidth used for each time zone from the communication log held by the data collection system, and sums the same, and the same for different days The used communication band is estimated from the average of the communication band of the time zone,
The transmission timing allocating means is a day of the week determined according to a transmission cycle of data predetermined for each user or a time zone in which a usable communication band is available during a day of the month. The data collection system according to claim 1, wherein the device assigns a timing for transmitting data. A data collection method performed by a data collection system that collects data from a device used by a user via a network,
A data receiving step in which the data collection system receives data from the device;
Using the past data received in the data reception step, a communication load estimation step for estimating the communication load of the data collection system for each user;
A communication band estimating step for estimating a used communication band for each time zone from a communication log held by the data collection system;
A transmission timing assigning step for assigning a timing at which a user's device having the largest communication load estimated in the communication load estimating step transmits data to a time zone in which a communication band available for receiving data from the device is present. And a data collection method.

Images