JPH04339455A - Communication control data generating device of facsimile - Google Patents

Abstract

PURPOSE:To obtain facsimile communication control data thought to be interested by a user without increasing the capacity of a memory. CONSTITUTION:Each time the facsimile communication is performed, the data to show the working condition of facsimile equipment are registered classified by time and classified by day to a control data registering part 9. For example, the data of the number of cases, the number of times and the necessary time of transmitting and receiving are registered. When the output command of the data to show the above-mentioned working condition is inputted from a data output instructing part 1a, an arithmetic part 5b processes the data read from the above-mentioned control data registering part 9 and sends them to an output part 3a. The output part 3a adds and outputs the data processed by the arithmetic part 5b to the data read from the control data registering part 9.

Description

[Detailed description of the invention]

0001

[Industrial Application Field] The present invention relates to a facsimile communication management data creation device, and in particular can provide communication management data that shows the operating status of a facsimile machine by time of day, the status of outgoing and incoming calls over a week, etc. The present invention relates to a facsimile communication management data creation device.

0002

[Prior Art] When a conventional facsimile machine sends or receives document information, it stores management data of transmission records and reception records in a memory, and prints out the management data when a user gives an instruction from a console panel. Some devices have a function that automatically prints out data when a predetermined amount of management data has been accumulated. Examples of the management data include the date and time of transmission and reception, communication time, number of sheets, destination name, charges, communication results, and the like.

[0003]For the user, if a communication management report with such data contents is obtained, it is possible to confirm each communication and also to save a record of the communication. As a result, it is possible to prevent troubles related to sending and receiving manuscript information, and if troubles occur,
The problem can be resolved at an early stage.

0004

However, in the facsimile communication management data creation device, management data for each facsimile communication is simply registered, and management data that is of interest to the user is not provided. The problem was that no consideration was given to

An object of the present invention is to provide a facsimile communication management system capable of eliminating the problems of the conventional apparatus described above and providing management data considered to be of interest to the user by calculation from registered data. The objective is to provide a data creation device.

[0006]

[Means for Solving the Problems] In order to achieve the above object, the present invention includes a management data registration unit that records operating status data such as the number of communications per unit time or per day, the number of sent and received sheets, and the required time; When there is a command to read the management data, a calculation section that creates data by processing the operation status data, and a calculation section that creates data by processing the operation status data, and add the data created by the calculation section to the operation status data recorded in the management data registration section. It is characterized in that it is equipped with an output section for additional output.

[0007]

According to the present invention, operating status data such as the number of communications per unit time or per day, the number of sent and received sheets, and the required time is recorded in the management data registration section. Then, when the user issues an instruction to read the operating status data, the calculation section creates data by processing the operating status data. Then, the output unit adds the processed data to the operation status data and outputs the resultant data.

[0008] As a result, the user can easily grasp the operating status of his/her own facsimile machine.

[0009]

DESCRIPTION OF THE PREFERRED EMBODIMENTS The present invention will be described in detail below with reference to the drawings.

FIG. 2 shows a schematic diagram of the hardware configuration of the facsimile machine of the present invention. In the figure, 1 is an operation section consisting of a numeric keypad and various function keys arranged on the console panel, 2 is a reading section that reads document information to be sent, and 3
4 is a recording unit that prints out the received manuscript information; 4 is an image processing unit that performs processing such as encoding or decoding on the transmitted or received manuscript information; 5 is a control unit that controls the entire facsimile communication; 7 is a modulation/demodulation unit, and 7 is a network control unit (NCU). Further, 8 is a clock unit that provides date information and specific time information, and 9 is a management data registration unit that registers management data for transmission and reception by the facsimile machine.

[0011] As the management data registration section 9, a nonvolatile RAM (backup memory) can be used. Further, the management data registration section 9 has an area prepared in advance for registering data measured when there is facsimile communication. For example, an area is provided in which management data described in FIGS. 3 and 4 can be registered.

Next, an example of the management data registered in the area of the management data registration section 9 will be explained with reference to FIG. FIG. 3(a) shows management data in which the number of calls, the number of sheets, and the time required for the calls in one week (7 days) are recorded. Further, FIG. 6(b) shows management data in which the number of incoming calls, the number of calls, and the time required for making the calls in the same week (7 days) are recorded.

FIG. 4 shows data showing the status of outgoing calls and incoming calls by time zone for each day of the week. In addition, in the figure, Erlang (=total communication time for 1 hour/unit time (1 hour)
Although data is also entered in the columns of time)), average, and total, they are not entered in the management data registration section 9 in order to reduce the amount of data. Therefore, a small capacity memory can be used as the management data registration section 9.

An example of the operation of registering the time zone-specific data in the management data registration section 9 will be explained with reference to the flowchart shown in FIG.

First, it is determined whether or not there has been an outgoing or incoming call operation, and if this determination is affirmative, step S2
Then, it is determined whether the outgoing or incoming call was successful. If unsuccessful, the process advances to step S3, and 1 is added to the number column of the management data registration section 9. On the other hand, if the determination in step S2 is affirmative, the process proceeds to step S4 and the start time is stored.

[0016] Next, the number of transmitted or received sheets is counted (
Step S5), 8:00 a.m., 9:00 a.m., 10:00 a.m. in step S6
A judgment is made as to whether or not the time has come. If it is not the break time, the process proceeds to step S7, where it is determined whether or not the calling and receiving operations have been completed. If this determination is negative, the process advances to step S5, and counting of the number of transmitted or received sheets is continued.

If the determination in step S7 is affirmative, the process proceeds to step S8, where the required time is calculated, and then, the process proceeds to step S9, where the number of items in the management data registration section 9,
The number of sheets and time data are updated. Specifically, 1 is added to the number column, the number of sheets counted in step S5 is added to the number column, and the time required for step S8 is added to the time column.

When it is determined in step S6 that the break time has come, the process proceeds to step S10, where the required time from the start time to the break time is calculated, and then the process proceeds to step S11, where the management data registration section 9 cases,
The number of sheets and time data are updated. The updating method is the same as in step S9.

In step S12, the count number is cleared, and in step S13, the start time is updated to a break time. Then, the process returns to step S5 and the same operation as described above is continued again.

Through the above operations, data other than the Erlang, average, and total columns in FIG. 4 are registered in the management data registration section 9.

Next, an example of the operation of registering one week's operating status data (see FIG. 3) in the area of the management data registration section 9 will be explained with reference to the flowchart of FIG.

First, in step S21, it is determined whether or not there has been an outgoing or incoming call operation, and if this determination is affirmative, the process advances to step S22, where 1 is entered in the number of cases column of the management data registration section 9. will be added. Further, the process advances to step S23, and the number of transmitted or received sheets is added to the number of sheets column. Next, the process proceeds to step S24, where the required time is added to the communication time.

[0023] Next, in step S25, it is determined whether or not the cut-off time, that is, 12:00 p.m. Wait for an incoming call.

If the determination in step S25 is affirmative, the process advances to step S26, and the registration fields of the number of items, number of sheets, and communication time in the management data registration section 9 are entered in steps S22 and S23.
And the data obtained in S24 is registered.

As described above, one day's operating status data is registered as one week's operating status data.

[0026] Instead of the above-described method, one week's operating status data may be created based on the time zone-specific data. That is, one day's operating status data may be calculated from the time zone data and registered in the weekly operating status data registration area.

Next, a functional block diagram of an embodiment of the present invention will be explained with reference to FIG. In addition, in the figures, the same or equivalent parts as in FIG. 2 are represented by the same reference numerals or the same reference numerals with a subscript.

In the figure, 5a is a communication control unit that controls facsimile communication, and 5b is a calculation unit, which are shown in FIG.
This is a function that the control unit 5 has. Reference numeral 1a denotes a data output instruction section that instructs the type of data to be read from the management data registered in the management data registration section 9, and is included in the operation section 1. Further, 3a is an output section,
This is the recording section 3 or a display section made of a liquid crystal panel or the like.

Next, the operation of this embodiment will be explained with reference to FIG. Since the facsimile machine has a clock section 8, time data from the clock section 8 is used to record time-related data in the area of the management data registration section 9. For example, data related to the survey date shown in FIG. 3 or data related to time shown in FIG. 4 are recorded.

Furthermore, when a call is made or received using a facsimile machine, data on the number of calls and the number of sheets are registered in correspondence with the time when the call was made. Here, the number of calls is the number of calls made or received, and the number of sheets is the number of originals sent or received per call. As shown in the figure, the reason why the number of calls is greater than the number of sheets is due to the fact that the original information could not be sent because the call was not connected to the other party.

Now, if the user selects the data output instruction section 1a,
When an instruction for data to be output is given from the management data registration section 9, the corresponding management data is read out from the management data registration section 9, and the corresponding management data is read out from the management data registration section 9.
b performs a predetermined calculation corresponding to the management data. Then, the data obtained by the calculation is added to the management data and sent to the output section 3a, and the result is printed out or displayed by the output section 3a.

For example, as shown in the flowchart in FIG.
31 is affirmative), the process advances to step S32, and the management data registration section 9 outputs the data shown in FIGS. 3(a) and 3(b) to the calculation section 5b. The calculation unit 5b is
Execute the calculation program according to the instructions of the data output instruction section 1a, and calculate the total number of cases, number of sheets, and time for one week, as well as the average of each, from the data shown in FIGS. 3(a) and 3(b). Step S33). and,
These calculation results are added to the data shown in FIGS. 3(a) and 3(b) and sent to the output section 3a. As a result, the output unit 3a prints out or displays an operating status report as shown in FIG. 9 (step S3
4).

According to the operation status report shown in FIG. 9, the user can know the total and average of the number of outgoing and incoming calls, number of calls, and time of each week. Incidentally, if necessary, it is also possible to create data that is a sum of the outgoing and incoming data in the arithmetic unit 5b and print it out or display it from the output unit 3a.

Further, as shown in the flowchart of FIG. 8, when the user instructs the output of the operating status by time zone by specifying the date, day of the week, or number of days before from the data output instruction section 1a. (step S41 is affirmative), the management data registration unit 9 sends the Erlang of FIG.
The data of the designated day on which the average and total are not entered is output to the calculation unit 5b (step S42). Arithmetic unit 5b
executes the arithmetic program according to the instructions from the data output instruction section 1a, and outputs the erlangs by time zone shown in FIG.
The number of incoming calls, the number of sheets, the average time, and the total data of outgoing and incoming calls are calculated (step S43). Then, the data from the management data registration section 9 is attached with the data of the calculation result and sent to the output section 3a. As a result, the output unit 3a prints out or displays a time zone operating status report as shown in FIG.
Step S44). Note that since the average is previously inputted as data indicating that the average is taken from what time in the morning to what time in the afternoon, the average for this time is automatically calculated. For example, the average from 8 a.m. to 8 p.m. is calculated. The time for taking this average may be freely specified by the user from the operation section 1.

[0035] Furthermore, when the user selects the data output instruction section 1a,
You can also instruct it to output a week's worth of hourly operating status reports. In this way, it is possible to know trends such as which times of the week are empty or busy, and provide useful data on operational status.
You can get ta.

As described above, according to this embodiment, it is possible to know the operational status of the facsimile machine for one week on a daily basis, and also to know the total and average of outgoing calls, incoming calls, and times for one week. can.

[0037] Also, on a daily basis, the day is divided into 24 hours, and the operating status of the facsimile machine can be known for each hour by outgoing and incoming calls. can be added.

Furthermore, means for converting the management data into graph data is provided on the output side of the arithmetic unit 5b in FIG.
The operation status report may be printed out or displayed in a graphical form starting from a.

[0039]

Effects of the Invention As is clear from the above description, according to the present invention, instead of outputting management data for each facsimile communication as a report as in the past, management data for each facsimile communication can be output in one report. Since the daily operating status can be output, or the operating status by time of day can be output, the user can easily understand the operating status of his or her own facsimile machine by viewing the operating status report. There is.

[Brief explanation of drawings]

FIG. 1 is a functional block diagram of an embodiment of the present invention.

FIG. 2 is a block diagram showing a schematic hardware configuration of an embodiment of the present invention.

FIG. 3 is a diagram showing an example of data registered in the management data registration section of FIG. 1;

FIG. 4 is a diagram showing another example of data registered in the management data registration section of FIG. 1 and an example of an operating status report output from the output section.

FIG. 5 is a flowchart for explaining the operation of registering data in a management data registration unit.

FIG. 6 is a diagram for explaining the operation of registering data in a management data registration section.

FIG. 7 is a flowchart for explaining the operation when outputting a weekly operating status report.

FIG. 8 is a flowchart for explaining the operation when outputting a time zone operating status report.

FIG. 9 is a flowchart showing an example of a week's operating status report output from the output unit.

FIG. 10 is a diagram showing an example of an operating status report expressed in a graph.

[Explanation of symbols]

1a...Data output instruction section, 3a...Output section, 5a...Communication control section, 5b...Calculation section, 8...Clock section, 9...Management data registration section.

Claims (1)

[Claims] Claim 1: A communication management data creation device that creates management data indicating communication history of a facsimile device, comprising:
A management data registration unit that records operating status data such as the number of communications per unit time or per day, the number of sent and received sheets, and the required time, and data that is processed from the operating status data when a command to read the management data is received. facsimile communication management data, comprising: a calculation unit that creates the data; and an output unit that adds and outputs the data created by the calculation unit to the operating status data recorded in the management data registration unit. Creation device.