JP2015061242A - Main device and notification method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a technology for notifying a person concerned of various notification content in an appropriate timing by using a telephone set without adding a dedicated device.SOLUTION: A main device 1 includes: a notification event data storage unit 16 for storing notification event data including at least notification time, notification destination information and notification content; and a notification event processing unit 20 for monitoring the arrival of the notification time of the notification event data stored in the notification event data storage unit 16 to process the notification event data whose notification time has arrived. The notification event processing unit 20 specifies an extension telephone set 2 of the notification destination from among a plurality of extension telephone sets 2 stored in the main device 1 on the basis of the notification destination information of the notification event data whose notification time has arrived, and allows the extension telephone set 2 of the notification destination to display the notification content included in the notification event data.

Description

  The present invention relates to a main apparatus, and more particularly, to a technique for notifying a person concerned of an event of the contents of the event using a telephone housed in the main apparatus.

  Patent Document 1 discloses a conference room reservation apparatus that can efficiently use a conference room. This conference room reservation device calls a conference room telephone when the conference room reservation start date and time comes. When an input for confirming use of the conference room is received from the conference room telephone, the use of the conference room is confirmed. On the other hand, if the input for confirming the use of the conference room is not accepted from the telephone of the conference room, a call is made to the telephone of the reservation person, and the input of information related to the reservation of the conference room is accepted from the telephone of the reservation person.

  According to the conference room reservation apparatus described in Patent Document 1, the reservation of the conference room can be confirmed to the reservation person with simple telephone processing, and the reservation person can easily change the reservation as necessary. . Therefore, when the reservation person does not use the conference room, the conference room can be used by another person, and the conference room can be used efficiently.

JP 2012-165166 A

  However, the conference room reservation apparatus described in Patent Document 1 is only for using the telephone for confirming and changing the reservation of the conference room, and uses the telephone for notifying participants of the start of the conference. I do not consider that. In addition, it does not consider using a telephone for various notification events such as a telephone memo notification, ToDo deadline notification, business trip application notification, and attendance confirmation notification. Furthermore, in Patent Document 1, a dedicated device (conference reservation device) that works with a telephone is required.

  The present invention has been made in view of the above circumstances, and it is an object of the present invention to provide a technique for notifying related parties of various notification contents at an appropriate timing using a telephone without adding a dedicated device. .

  In order to solve the above-described problem, in the present invention, a main device accommodating a plurality of telephones stores notification event data including a notification time, a notification destination, and notification contents, and a notification time of the stored notification event data. Monitor the arrival of. Then, the notification destination telephone is identified from the notification event data when the notification time has arrived, and the notification content included in the notification event data is displayed on the notification destination telephone. At this time, the notification destination telephone may be ringed.

For example, the present invention is a main device for accommodating a plurality of telephones,
Notification event data storage means for storing notification event data including at least notification time, notification destination information, and notification content;
Notification event processing means for monitoring the arrival of the notification time of the notification event data stored in the notification event data storage means and processing the notification event data when the call time has arrived,
The notification event processing means includes:
Based on the notification destination information of the notification event data when the notification time has arrived, the notification destination telephone is identified from the plurality of telephones, and the notification content included in the notification event data is stored in the notification destination telephone. Display.

  In the present invention, the main device that accommodates the telephone stores the notification event data including the notification time, the notification destination, and the notification content, and monitors the arrival of the notification time. The notification content is displayed on the previous telephone. Therefore, according to the present invention, the notification time, the notification destination, and the notification content to be included in the notification event data can be freely set, so that various notification contents can be assigned to the parties at an appropriate timing separately from the main device. Can be notified without using the device.

FIG. 1 is a schematic configuration diagram of a telephone system according to an embodiment of the present invention. FIG. 2 is a sequence diagram for explaining conference start notification processing and conference end notification processing in the telephone system according to one embodiment of the present invention. FIG. 3 is a sequence diagram for explaining conference start notification processing and conference end notification processing in the telephone system according to the embodiment of the present invention, and is a continuation of FIG. FIG. 4 is a sequence diagram for explaining the telephone memo notification process in the telephone system according to the embodiment of the present invention. FIG. 5 is a sequence diagram for explaining ToDo notification processing in the telephone system according to the embodiment of the present invention. FIG. 6 is a sequence diagram for explaining the business trip application notification process in the telephone system according to the embodiment of the present invention. FIG. 7 is a sequence diagram for explaining attendance confirmation notification processing in the telephone system according to one embodiment of the present invention. FIG. 8 is a schematic functional configuration diagram of the data management device 3. FIG. 9 is a diagram schematically illustrating an example of registered contents in the conference data storage unit 31. FIG. 10 is a diagram schematically showing an example of registered contents in the telephone memo data storage unit 32. FIG. 11 is a diagram schematically illustrating an example of registered contents in the ToDo data storage unit 33. FIG. 12 is a diagram schematically showing an example of registered contents in the business trip application data storage unit 34. FIG. 13 is a diagram schematically showing an example of registered contents in the time and attendance data storage unit 35. FIG. 14 is a flowchart for explaining the operation of the data management device 3. FIG. 15 is a schematic functional configuration diagram of the main device 1. FIG. 16 is a diagram schematically showing an example of registered contents in the extension telephone data storage unit 15. FIG. 17 is a diagram schematically illustrating an example of registered contents in the notification event data storage unit 16. FIG. 18 is a diagram schematically illustrating an example of registered contents in the notification event processing rule storage unit 18. FIG. 19 is a flowchart for explaining notification event data generation processing of the main apparatus 1. FIG. 20 is a flowchart for explaining the notification event execution process of the main device 1.

  An embodiment of the present invention will be described below.

  FIG. 1 is a schematic configuration diagram of a telephone system according to the present embodiment.

  As shown in the figure, the telephone system according to the present embodiment includes a main device 1 connected to a public network 5 and a plurality of extension telephones 2-1 to 2-n (hereinafter simply referred to as extensions) accommodated in the main device 1. And a data management device 3 connected to the main device 1 via the LAN 6. The LAN 6 is connected to the IP network 7 via a gateway (GW) 4. The data management device 3 may be connected to the IP network 7 side.

  The data management device 3 manages various data including conference data, telephone memo data, ToDo data, business trip application data, and attendance / leaving data. Here, the conference data includes, for example, a conference start and end time, a venue, and participant identification information (user name, etc.). In addition, the telephone memo data includes, for example, the reception time of the telephone memo, the identification information of the responder, the message destination, the identification information of the message owner (the person who made the call), the telephone number of the message owner, the contents of the memo, and the confirmation status Shall be included. The ToDo data includes, for example, a deadline for ToDo, identification information of a person in charge, identification information of an administrator, a subject, and a progress status. The business trip application data includes, for example, a business trip date, applicant identification information, approver identification information, business trip destination, transportation means, transportation cost, and approval status. In addition, the attendance / leaving data includes, for example, scheduled attendance time, identification information of the attendance management target person, identification information of the manager, attendance time, and attendance time.

  The main device 1 establishes and releases a communication path between the extension telephone 2 and the public network 5 or between the extension telephones 2 by executing call control in cooperation with the extension telephone 2. In addition, the main device 1 generates various notification event data including at least a notification time, a notification destination, and a notification content based on the data acquired from the data management device 3, and if the notification time has arrived, this notification In accordance with the event data, the notification contents are notified to the extension telephone 2 of the notification destination.

  2 and 3 are sequence diagrams for explaining conference start notification processing and conference end notification processing in the telephone system according to the present embodiment.

  First, when a predetermined meeting data request timing such as a predetermined time before the start time arrives (S100), the main apparatus 1 transmits a meeting data request to the data management apparatus 3 via the LAN 6 (S101). In response to this, the data management device 3 searches for the conference data of the conference held today and transmits the searched conference data to the main device 1 (S102).

  Next, the main device 1 generates conference start notification event data and conference end notification event data for each conference data received from the data management device 3. Here, the conference start notification event data includes a notification time that is a predetermined time before the conference start time, and extension telephones 2-2 and 2-3 of the participants of the conference (here, user A and user B). The notification destination, the extension telephone set 2-1 installed at the meeting location, the report destination, and the conference start message informing the conference start time and location are included as notification contents. Further, the conference end notification event data includes a notification time of a predetermined time before the conference end time, a notification destination of the extension telephone set 2-1 installed at the conference location, and a conference informing the conference end time. Include an end message as notification content. Then, the main device 1 starts monitoring the arrival of the notification time included in the conference start notification event data and the conference end notification event data (S103).

  Next, when detecting that the notification time included in the conference start notification event data has arrived (S104), the main device 1 specifies the notification destination from the conference start notification event data (S105). Here, the extension telephone 2-2 of user A and the extension telephone 2-3 of user B are included in the conference start notification event data as notification destinations. The main apparatus 1 notifies the extension telephones 2-2 and 2-3 as the notification destination of the start of the conference specified by the conference start notification event data (S106, S107). Specifically, the extension telephones 2-2 and 2-3 to be notified are ringed a predetermined number of times, and the notification content of the conference start notification event data is displayed on the display panels of these extension telephones 2-2 and 2-3. A conference start message is displayed (S108, S109).

  Here, it is assumed that the extension telephone 2-3 receives a button operation for “attendance” from the user B (S110). In response, the extension telephone 2-3 transmits a PB (Push Button) signal corresponding to the button operation for “attendance” to the main apparatus 1 (S112). On the other hand, it is assumed that the extension telephone 2-2 receives a button operation for “absence” from the user A (S111). In response, the extension telephone 2-2 transmits a PB signal corresponding to the button operation for “absence” to the main apparatus 1 (S113).

  Next, when receiving the PB signal from the extension telephones 2-2 and 2-3 that are the notification destinations, the main apparatus 1 specifies the report destination from the conference start notification event data (S114). Here, the extension telephone set 2-1 set in the conference room is included in the conference start notification event data as a report destination. The main device 1 notifies the contents of attendance of each participant user A and user B specified by the PB signals received from the extension telephones 2-2 and 2-3 to be notified to the extension telephone 2-1 that is the report destination (S115). Specifically, the extension telephone 2-1 as the report destination is ringed a predetermined number of times, and the attendance contents of each participant (in this example, user A “absent”, user B are displayed on the display panel of the extension telephone 2-1). “Attendance” is displayed (S116).

  Next, the main device 1 generates a conference data update request for updating the participant information included in the conference data that is the basis of the conference start notification event data in accordance with the attendance status of the participants. Then, this conference data update request is transmitted to the data management device 3 via the LAN 6 (S117). In response to this, the data management device 3 updates the participant included in the conference data specified by the conference data update request based on the conference data update request (S118).

  Next, when detecting that the notification time included in the conference end notification event data has arrived (S120), the main device 1 specifies the notification destination from the conference end notification event data (S121). Here, the conference end notification event data includes the extension telephone 2-1 installed in the conference room as a notification destination. Then, the main device 1 notifies the extension telephone 2-1 that is the notification destination of the end of the conference specified by the conference end notification event data (S122). Specifically, the extension telephone 2-1 that is the notification destination is ringed a predetermined number of times, and an end message that is the notification content of the conference end notification event data is displayed on the display panel of the extension telephone 2-1 (S123).

  Here, it is assumed that the extension telephone set 2-1 receives a button operation for “extension” from a conference participant (S124). In response to this, the extension telephone 2-1 transmits a PB signal corresponding to the button operation for “extension” to the main apparatus 1 (S125).

  Next, when the main apparatus 1 receives the PB signal from the extension telephone 2-1 that is the notification destination, the main apparatus 1 recognizes from the PB signal that the conference has been extended. Then, the notification time included in the conference end notification event data is changed to a time extended by the time corresponding to the PB signal (S126). The main device 1 also generates a conference data update request for updating the conference end time included in the conference data that is the basis of the conference end notification event data. Then, this conference data update request is transmitted to the data management device 3 via the LAN 6 (S127). In response, the data management device 3 updates the conference end time included in the conference data specified by the conference data update request based on the conference data update request (S128).

  Next, when the main device 1 detects that the notification time (post-extension notification time) included in the conference end notification event data has arrived (S129), the main device 1 specifies the notification destination from the conference end notification event data (S130). . Then, the main apparatus 1 notifies the extension telephone set 2-1 as the notification destination of the end of the conference specified by the conference end notification event data in the same manner as S122 and S123 (S131, S132).

  Here, it is assumed that the extension telephone set 2-1 has received a button operation for approval from a conference participant (S133). In response, the extension telephone 2-1 transmits a PB signal corresponding to the button operation for approval to the main apparatus 1 (S134). Then, the main apparatus 1 recognizes that the end of the conference has been accepted by the PB signal received from the extension telephone 2-1 that is the notification destination, and ends the process.

  FIG. 4 is a sequence diagram for explaining telephone memo notification processing in the telephone system according to the present embodiment.

  First, when a predetermined telephone memo data request timing arrives, such as the elapse of a predetermined interval time (S140), the main apparatus 1 transmits a telephone memo data request to the data management apparatus 3 via the LAN 6 (S141). Receiving this, the data management device 3 searches for telephone memo data whose confirmation status is “unconfirmed”, and transmits the searched telephone memo data to the main device 1 (S142).

  Next, the main device 1 generates phone memo notification event data for each unconfirmed phone memo data received from the data management device 3. Here, in the telephone memo notification event data, the extension telephone 2 of the notification time and message destination (here, user A) is the time after a predetermined time (however, shorter than the above-mentioned predetermined interval time) from the reception time. -2 is the notification destination, the extension telephone 2-3 of the respondent (here, user B) is the reporting destination, and the telephone memo notification message that informs the message owner, the telephone number of the message owner, and the memo content is included as the notification content. Then, the main device 1 starts monitoring the arrival of the notification time included in the telephone memo notification event data (S143).

  Next, when detecting that the notification time included in the telephone memo notification event data has arrived (S144), the main device 1 specifies the notification destination from the telephone memo notification event data (S145). Here, the extension telephone 2-2 of the user A is included in the telephone memo notification event data as a notification destination. The main device 1 notifies the telephone memo specified by the telephone memo notification event data to the extension telephone 2-2 that is the notification destination (S146). Specifically, the extension telephone 2-2 to be notified is ringed a predetermined number of times, and a telephone memo notification message, which is notification contents of telephone memo notification event data, is displayed on the display panel of the extension telephone 2-2 (S147). ).

  Here, it is assumed that the extension telephone 2-2 as the notification destination has received a button operation for “phone” from the user A (S148). In response, the extension telephone 2-2 transmits a PB signal corresponding to the button operation for “telephone” to the main apparatus 1 (S149).

  Next, the main device 1 recognizes that a call to the message owner is instructed by the PB signal received from the extension telephone 2-2 to be notified, and from the telephone memo notification event data, the telephone number of the message owner Is identified. Then, a call is made to the telephone number of the message sender, a call path is established between the extension telephone 2-2 and the message caller, and both calls are relayed (S150). Further, the main device 1 identifies the report destination from the telephone memo notification event data (S151). Here, the extension telephone 2-3 of the user B is included in the telephone memo notification event data as a report destination. The main apparatus 1 notifies the extension telephone 2-3 as the report destination that the telephone memo has been confirmed (S152). Specifically, the extension telephone 2-3 of the report destination is ringed a predetermined number of times, and the fact that the telephone memo has been confirmed by the user A is displayed on the display panel of the extension telephone 2-3 (S153).

  Next, the main device 1 generates a telephone memo data update request for updating the confirmation state included in the telephone memo data that is the basis of the telephone memo notification event data to “confirmed”. Then, this telephone memo data update request is transmitted to the data management device 3 via the LAN 6 (S154). In response to this, the data management device 3 changes the confirmation state included in the telephone memo data specified by the telephone memo data update request from “unconfirmed” to “confirmed” (S155).

  FIG. 5 is a sequence diagram for explaining ToDo notification processing in the telephone system according to the present embodiment.

  First, when a predetermined ToDo data request timing such as a predetermined time before the start of work arrives (S160), the main device 1 transmits a ToDo data request to the data management device 3 via the LAN 6 (S161). In response to this, the data management device 3 searches for ToDo data whose progress status is other than “completed” from ToDo data whose deadline comes before a predetermined number of days from today, and finds the searched ToDo data. It transmits to the main device 1 (S162).

  Next, the main device 1 generates ToDo notification event data for each ToDo data received from the data management device 3. Here, in the ToDo notification event data, for example, a predetermined time during working hours is notified time, the extension telephone 2-3 of the person in charge (here, user B) is notified, and the extension telephone of the administrator (here, user A) 2-2 is included in the report destination, and a ToDo notification message informing the subject and deadline is included as the notification content. Then, the main device 1 starts monitoring the arrival of the notification time included in the ToDo notification event data (S163).

  Next, when the main device 1 detects that the notification time included in the ToDo notification event data has arrived (S164), the main device 1 identifies the notification destination from the ToDo event data (S165). Here, the extension telephone 2-3 of the user B is included in the ToDo notification event data as a notification destination. The main apparatus 1 notifies ToDo specified by the ToDo notification event data to the extension telephone 2-3 that is the notification destination (S166). Specifically, the extension telephone 2-3 to be notified is ringed a predetermined number of times, and a ToDo notification message which is the notification content of the ToDo notification event data is displayed on the display panel of the extension telephone 2-3 (S167).

  Here, it is assumed that the extension telephone 2-3 of the notification destination has received a button operation for “complete” from the user B (S168). In response, the extension telephone 2-3 transmits a PB signal corresponding to the button operation for “complete” to the main apparatus 1 (S169).

  Next, when receiving the PB signal from the extension telephone 2-3 of the notification destination, the main device 1 specifies the report destination from the ToDo notification event data (S170). Here, the extension telephone 2-2 of the user A is included in the ToDo notification event data as a report destination. The main apparatus 1 notifies the extension status 2-2 of the ToDo specified by the PB signal received from the extension telephone 2-3 that is the notification destination to the extension telephone 2-2 that is the report destination (S171). Specifically, the extension telephone 2-2 of the report destination is ringed a predetermined number of times, and the progress status “completed” of the user B's ToDo is displayed on the display panel of the extension telephone 2-2 (S172).

  Further, the main device 1 generates a ToDo data update request for updating the progress status included in the ToDo data that is the basis of the ToDo notification event data to “completed”, and the data management device 3 via the LAN 6. This ToDo data update request is transmitted (S173). In response to this, the data management device 3 changes the confirmation state included in the ToDo data specified by the ToDo data update request from “not started” or “working” to “completed” (S174).

  FIG. 6 is a sequence diagram for explaining the business trip application notification process in the telephone system according to the present embodiment.

  First, the main device 1 transmits a business trip application data request to the data management device 3 via the LAN 6 when a predetermined business trip application data request timing such as a predetermined time before the start of work arrives (S180). . Receiving this, the data management device 3 searches for the business trip application data whose approval status is “unapproved”, and transmits the searched business trip application data to the main device 1 (S182).

  Next, the main device 1 generates business trip application notification event data for each unapproved business trip application data received from the data management device 3. Here, in the business trip application notification event data, for example, a predetermined time during working hours is a notification time, an extension telephone 2-2 of an approver (here, user A) is a notification destination, and the applicant (here, user B) The extension telephone 2-3 includes the report destination, and a business trip application message that informs the business trip date, business trip destination, transportation means, and transportation cost is included as the notification content. Then, the main device 1 starts monitoring the arrival of the notification time included in the business trip application notification event data (S183).

  Next, when detecting that the notification time included in the business trip application notification event data has arrived (S184), the main device 1 identifies the notification destination from the business trip application notification event data (S185). Here, the extension telephone 2-2 of the user A is included in the business trip application notification event data as a notification destination. The main device 1 notifies the extension telephone set 2-2 that is the notification destination of the business trip application specified by the business trip application notification event data (S186). Specifically, the extension telephone 2-2 to be notified is ringed a predetermined number of times, and a business trip application message that is a notification content of the business trip application notification event data is displayed on the display panel of the extension telephone 2-2 (S187). .

  Here, it is assumed that the extension telephone 2-2 as the notification destination has received a button operation for “approval” from the user A (S188). In response to this, the extension telephone 2-2 transmits a PB signal corresponding to the button operation for “approval” to the main apparatus 1 (S189).

  Next, when receiving the PB signal from the extension telephone 2-2 that is the notification destination, the main device 1 identifies the report destination from the business trip application notification event data (S190). Here, the extension telephone 2-3 of the user B is included in the business trip application notification event data as a report destination. The main apparatus 1 notifies the extension telephone 2-3 as the report destination of the approval result of the business trip application specified by the PB signal received from the extension telephone 2-2 as the notification destination (S191). Specifically, the extension telephone 2-3 of the report destination is ringed a predetermined number of times, and the approval result “approval” of the user A is displayed on the display panel of the extension telephone 2-3 (S192).

  In addition, the main device 1 generates a business trip application data update request for updating the approval state included in the business trip application data that is the basis of the business trip application notification event data to “approved”, via the LAN 6. This business trip application data update request is transmitted to the data management device 3 (S193). In response to this, the data management device 3 changes the approval state included in the business trip application data specified by the business trip application data update request from “unapproved” to “approved” (S194).

  FIG. 7 is a sequence diagram for explaining attendance confirmation notification processing in the telephone system according to the present embodiment.

  First, when a predetermined attendance / attendance data request timing such as a predetermined time before the start of work arrives (S200), the main apparatus 1 transmits an attendance / attendance data request to the data management apparatus 3 via the LAN 6 (S201). In response to this, the data management device 3 searches for attendance / attendance data in which the scheduled attendance time is today's time and the attendance time is not registered, and transmits the retrieved attendance / exit data to the main device 1 (S202).

  Next, the main device 1 generates attendance confirmation notification event data for each of the attendance / leaving data received from the data management device 3. Here, in the attendance confirmation notification event data, the notification time is the time before the scheduled attendance time, the extension telephone 2-3 of the attendance management person (here, user B) is notified, and the manager (here, user) The extension telephone 2-2 of A) is set as the report destination, and the attendance confirmation message requesting confirmation of attendance is included as the notification content. Then, the main device 1 starts monitoring the arrival of the notification time included in the attendance confirmation notification event data (S203).

  Next, when detecting that the notification time included in the attendance confirmation notification event data has arrived (S204), the main device 1 specifies the notification destination from the attendance confirmation notification event data (S205). Here, the extension telephone 2-3 of the user B is included in the attendance confirmation notification event data as a notification destination. Then, the main device 1 notifies the attendance confirmation to the extension telephone 2-3 that is the notification destination (S206). Specifically, the extension telephone 2-3 to be notified is ringed a predetermined number of times, and the attendance confirmation message as notification contents of the attendance confirmation notice event data is displayed on the display panel of the extension telephone 2-3 (S207). .

  Here, it is assumed that the extension telephone 2-3 has received a button operation for “commuting” from the user B (S208). In response to this, the extension telephone 2-3 transmits a PB signal corresponding to the button operation for “commuting” to the main apparatus 1 (S209).

  Next, when receiving the PB signal corresponding to the button operation for “commuting” from the extension telephone 2-3 of the notification destination, the main device 1 specifies the report destination from the attendance confirmation notification event data (S210). Here, the extension telephone 2-2 of the user A is included in the business trip application notification event data as a report destination. The main device 1 notifies the extension telephone 2-2, which is the report destination, of the attendance at the notification destination (S211). Specifically, the extension telephone 2-2 of the report destination is ringed a predetermined number of times, and the attendance of the user B is displayed on the display panel of the extension telephone 2-2 (S212).

  Also, the main device 1 generates an attendance / attendance data update request for registering the current time as the attendance time of the attendance / attendance data that is the basis of the attendance confirmation notification event data. Then, the attendance / leaving data update request is transmitted to the data management device 3 via the LAN 6 (S213). In response to this, the data management device 3 registers the current time as the attendance time of the attendance / attendance data specified by the attendance / attendance data update request (S214).

  Next, details of the data management device 3 and the main device 1 constituting the telephone system according to the present embodiment will be described. Since the extension telephone 2 can use an existing extension telephone, its detailed description is omitted.

  First, details of the data management device 3 will be described.

  FIG. 8 is a schematic functional configuration diagram of the data management device 3.

  As shown in the figure, the data management device 3 includes a LAN interface unit 30, a conference data storage unit 31, a telephone memo data storage unit 32, a ToDo data storage unit 33, a business trip application data storage unit 34, and an attendance data. Unit 35 and data management unit 36.

  The LAN interface unit 30 is an interface for connecting to the LAN 6.

  The conference data storage unit 31 stores conference data. FIG. 9 is a diagram schematically illustrating an example of registered contents in the conference data storage unit 31. As shown in the figure, the conference data storage unit 31 stores a conference data record 310 for each conference. The conference data record 310 includes a field 311 for registering a data ID as identification information, a field 312 for registering the data type “conference”, a field 313 for registering the start time of the conference, A field 314 for registering the end time of the conference, a field 315 for registering identification information of the participants of the conference, a field 316 for registering the meeting location, and a field 317 for registering the conference name. And having.

  The telephone memo data storage unit 32 stores telephone memo data. FIG. 10 is a diagram schematically showing an example of registered contents in the telephone memo data storage unit 32. As shown in the drawing, the telephone memo data storage unit 32 stores a telephone memo data record 320 for each telephone memo. The telephone memo data record 320 includes a field 321 for registering a data ID as identification information, a field 322 for registering a data type “phone memo”, and a field 323 for registering a telephone reception time. , A field 324 for registering identification information of the corresponding person of the telephone, a field 325 for registering identification information of the message destination of the telephone memo, and identification information of the other party (message owner) who made the call Field 326, a field 327 for registering the telephone number of the message owner, a field 328 for registering the contents of the message (memo contents), and the confirmation state of the telephone memo (confirmed in the telephone memo message destination) Field 329 for registering whether or not).

  The ToDo data storage unit 33 stores ToDo data. FIG. 11 is a diagram schematically illustrating an example of registered contents in the ToDo data storage unit 33. As illustrated, the ToDo data storage unit 33 stores a ToDo data record 330 for each ToDo. The ToDo data record 330 includes a field 331 for registering a data ID as identification information, a field 332 for registering a data type “ToDo”, a field 333 for registering a deadline for ToDo, and ToDo. Field 334 for registering the identification information of the person in charge, a field 335 for registering the identification information of the administrator of ToDo, a field 336 for registering the subject of ToDo, and the importance of ToDo (“High ”,“ Medium ”,“ low ”), and a field 338 for registering the progress of ToDo.

  The business trip application data storage unit 34 stores business trip application data. FIG. 12 is a diagram schematically showing an example of registered contents in the business trip application data storage unit 34. As shown in the figure, the business trip application data storage unit 34 stores a business trip application data record 340 for each business trip application. The business trip application data record 340 includes a field 341 for registering data ID as identification information, a field 342 for registering the data type “business trip application”, a field 343 for registering a business trip date, and an application. Field 344 for registering the person's identification information, field 345 for registering the person's identification information, field 346 for registering the business trip destination, and field for registering the travel means to the business trip destination 347, a field 348 for registering transportation expenses (travel expenses), and a field 349 for registering approval states (“unapproved”, “approved”, “denied”) by the approver.

  The attendance / leaving data storage unit 35 stores each work scheduled sunrise / disappointment data for each user. FIG. 13 is a diagram schematically showing an example of registered contents in the time and attendance data storage unit 35. As shown in the drawing, the attendance and attendance data storage unit 35 stores an attendance and attendance data record 350 for each scheduled work day for each user. The attendance and attendance data record 350 includes a field 351 for registering a data ID that is identification information, a field 352 for registering a data type “attendance / attendance”, a field 353 for registering a scheduled attendance time, and attendance / leaving management. A field 354 for registering the identification information of the subject person, a field 355 for registering the identification information of the administrator, a field 356 for registering the attendance time, a field 357 for registering the departure time, Have

  The data management unit 36 searches for, reads, deletes, updates, and updates data stored in each of the data storage units 31 to 35 in accordance with a request received from another device including the main device 1 via the LAN interface unit 30. And the addition of the data to each data storage part 31-35 is controlled.

  Note that the functional configuration of the data management device 3 shown in FIG. 8 may be realized by an integrated logic IC such as ASIC (Application Specific Integrated Circuit) or FPGA (Field Programmable Gate Array), or DSP ( It may be realized as software by a computer such as a digital signal processor. Alternatively, in a computer system such as a PC (Personal Computer) equipped with an auxiliary storage device such as a CPU, memory, HDD, DVD-ROM, and a communication interface such as a modem or NIC (Network Interface Card), the CPU executes a predetermined program. It may be realized by loading from an auxiliary storage device onto a memory and executing it. Moreover, the data management apparatus 3 may be implement | achieved on the separate computer system for every data memory | storage parts 31-35.

  FIG. 14 is a flowchart for explaining the operation of the data management device 3.

  When the data management unit 36 receives a data request from the main apparatus 1 via the LAN interface unit 30 (YES in S300), the data management unit 36 analyzes the data type requested by the data request (S301).

  If the data request received from the main device 1 is a conference data request, that is, if the data type requested in the data request is “conference” (“conference” in S301), the data management unit 36 Then, the conference data storage unit 31 is referred to, and the conference data record 310 registered in the field 313 is searched with the current time after the current time as the start time (S302). When the data request received from the main device 1 is a telephone memo data request, that is, when the data type requested in the data request is “phone memo” (“phone memo” in S301), the data management unit 36 refers to the telephone memo data storage unit 32 and searches for a telephone memo data record 320 in which the confirmation state registered in the field 329 is “unconfirmed” (S303). When the data request received from the main device 1 is a ToDo data request, that is, when the data type requested in the data request is “ToDo” (“ToDo” in S301), the data management unit 36 Referring to the ToDo data storage unit 33, the progress status registered in the field 338 is other than “completed”, and the deadline registered in the field 333 is a date before a predetermined number of days from today The ToDo data record 330 is searched (S304). When the data request received from the main device 1 is a business trip application data request, that is, when the data type requested in the data request is “business trip application” (“business trip application” in S301), the data management unit 36 refers to the business trip application data storage unit 34, and searches for the business trip application data record 340 whose approval status registered in the field 349 is “unapproved” (S305). When the data request received from the main device 1 is an attendance / leaving data request, that is, when the data type requested in the data request is “attendance / leaving” (S301: “attendance / leaving”), the data management unit 36 The attendance and attendance data storage unit 35 is referred to, and the attendance and attendance data record 350 in which the attendance time is not registered in the field 356 and the scheduled attendance time registered in the field 353 is today's time is searched (S306).

  Then, the data management unit 36 transmits the data record searched as described above to the main apparatus 1 via the LAN interface unit 30 (S307).

  In addition, when the data management unit 36 receives a data update request from the main apparatus 1 via the LAN interface unit 30 (YES in S310), the data storage unit 31- 35 (if the data type is “conference”, the conference data storage unit 31; if the data type is “phone memo”, the telephone memo data storage unit 32; if the data type is “ToDo”, the ToDo data storage unit 33; If the data type is “Attendance”, the attendance / exit data storage unit 35) is specified, and the specified data storage units 31-35 based on the data ID included in the data update request. From this, the record in which the update target data is stored is specified (S311). Then, the specified record is updated according to the update information included in the data update request (S312). Specifically, according to the update information included in the conference data update request, the end time in the field 314 of the record 310 of the conference data that is the update target data or the participant in the field 315 is changed. Further, according to the update information included in the telephone memo data update request, the confirmation state of the field 329 of the telephone memo data record 320 which is the update target data is changed. Further, according to the update information included in the ToDo data update request, the progress status of the field 338 of the record 330 of the ToDo data that is the update target data is changed. Further, according to the update information included in the business trip application data update request, the approval state of the field 349 of the record 340 of the business trip application data that is the update target data is changed. Also, according to the update information included in the attendance / leaving data update request, the attendance time in the field 356 of the attendance / leaving data record 350 as the update target data is registered.

  Next, details of the main device 1 will be described.

  FIG. 15 is a schematic functional configuration diagram of the main device 1.

  As shown in the figure, the main device 1 includes an extension telephone interface unit 10, a public network interface unit 11, a LAN interface unit 12, a main device function unit 13, a data request unit 14, and an extension telephone data storage unit 15. A notification event data storage unit 16, a notification event data generation unit 17, a notification event processing rule storage unit 18, a data update request unit 19, and a notification event processing unit 20.

  The extension telephone interface unit 10 is an interface for connecting to the extension telephone 2, the public network interface unit 11 is an interface for connecting to the public network 5, and the LAN interface unit 12 is connected to the LAN 6. It is an interface for.

  The main device function unit 13 performs processing necessary to realize the function as the main device 1. Specifically, a call path is established between the extension telephone 2 and the public network 5 or between the extension telephone 2 and another extension telephone 2 by performing call control in cooperation with the extension telephone 2. Or release an established call path. Further, the main device function unit 13 rings the extension telephone 2 or displays the notification content received from the notification event processing unit 20 on the display panel of the extension telephone 2 in accordance with an instruction from the notification event processing unit 20.

  The data request unit 14 transmits a data request to the data management device 3 via the LAN interface unit 12 and receives desired data from the data management device 3.

  The extension telephone data storage unit 15 stores extension telephone data. FIG. 16 is a diagram schematically showing an example of registered contents in the extension telephone data storage unit 15. As shown in the figure, the extension telephone data storage unit 15 stores an extension telephone data record 150 for each extension telephone 2 accommodated in the main apparatus 1. The extension telephone data record 150 registers the field 151 for registering the extension number of the extension telephone 2 and the identification information (user name, etc.) of the user of the extension telephone 2 or the identification information of the installation location (room name, etc.). And a field 152 for

  The notification event data storage unit 16 stores notification event data. FIG. 17 is a diagram schematically illustrating an example of registered contents in the notification event data storage unit 16. As shown in the figure, the notification event data storage unit 16 stores a notification event data record 160 for each notification event. The notification event data record 160 includes a field 161 for registering an event ID as identification information, and a notification event type (“meeting start”, “meeting end”, “phone memo”, “ToDo”, “business trip application” ”,“ Attendance Confirmation ”), a field 163 for registering the notification time, a field 164 for registering the extension number of the notification destination, and a report destination of the response received from the notification destination A field 165 for registering the extension number, a field 166 for registering the contents of notification to the notification destination, a field 167 for registering the data ID and data type of the data that is the source of the notification event, 168, and a field 169 for registering the status of this notification event ("unprocessed", "processing", "completed"), A.

  The notification event data generation unit 17 generates a notification event data record 160 based on the data received from the main device 1 by the data request unit 14 and stores it in the notification event data storage unit 16.

  The notification event processing rule storage unit 18 stores a processing rule for a response from the notification destination for each event type of the notification event data. FIG. 18 is a diagram schematically illustrating an example of registered contents in the notification event processing rule storage unit 18. As shown in the figure, the notification event processing rule storage unit 18 stores a notification event processing rule record 180 for each event type of the notification event. The notification event processing rule record 180 is for registering the event type (“conference start”, “conference end”, “phone memo”, “ToDo”, “business trip application”, “attendance confirmation”) of the notification event data. Registers the field 181 for registering the processing contents when the button 1 of the extension telephone 2 of the notification destination is pressed, and the processing contents when the button 2 of the extension telephone 2 of the notification destination is pressed And a field 184 for registering processing contents when the button 3 of the extension telephone 2 to be notified is pressed.

  In the present embodiment, the following processing contents are registered in the fields 182 to 184, for example.

  In the record 180 in which the event type “conference start” is registered in the field 181, it is registered in the field 182 that the notification destination “attendance” is notified to the report destination as the processing content when the button 1 is pressed. In the field 183, as a processing content when the button 2 is pressed, a notification destination “absent” is notified to the report destination, and a conference data update request for deleting the notification destination from the conference data participants is sent. Transmission to the data management device 3 is registered, and in the field 184, notification of “delay” of the notification destination to the report destination is registered as processing contents when the button 3 is pressed.

  In the record 180 in which the event type “conference end” is registered in the field 181, it is registered in the field 182 that the end of the conference is recognized as the processing content when the button 1 is pressed. In addition, as a processing content when the button 2 is pressed, it is registered that the notification time is extended by 30 minutes and a conference data update request for extending the end time of the conference data by 30 minutes is transmitted to the data management device 3 Then, in the field 184, as a processing content when the button 3 is pressed, the conference data update request for extending the notification time by 60 minutes and extending the conference data end time by 60 minutes is transmitted to the data management device 3. Registered to do.

  In the record 180 in which the event type “phone memo” is registered in the field 181, the notification destination “confirmation” is notified to the report destination in the field 182 as processing contents when the button 1 is pressed. As a processing content when the telephone memo data update request for changing the confirmation state of the telephone memo data to “confirmed” is registered to the data management apparatus 3 and the button 2 is pressed in the field 183. In addition to notifying the report destination of “confirmation”, a telephone memo data update request for changing the confirmation state of the telephone memo data to “confirmed” is transmitted to the data management device 3 and the telephone of the message owner Calling the number is registered.

  Further, in the record 180 in which the event type “ToDo” is registered in the field 181, as a processing content when the button 1 is pressed, the ToDo “complete” is notified to the report destination in the field 182, and the ToDo is also notified. It is registered that a ToDo data update request for updating the data progress status to “completed” is registered to the data management apparatus 3, and in the field 183, as a processing content when the button 2 is pressed, ToDo is notified to the report destination. Is registered to send to the data management device 3 a ToDo data update request for updating the progress status of ToDo data to “working”, and the button 3 is pressed in the field 184 As a processing content in the case of a notification, ToDo's “not yet started” is notified to the report destination and the progress of ToDo data Sending a ToDo data update request for updating the "untouched" to the data management device 3 is registered the situation.

  Further, in the record 180 in which the event type “business trip application” is registered in the field 181, the field 182 notifies the report destination of “approval” of the business trip application as processing contents when the button 1 is pressed. As a processing content when the travel request data update request for updating the approval status of the business trip application data to “approved” is registered to the data management device 3 and the button 2 is pressed in the field 183. It is registered that the report destination is notified of “refusal” of the business trip application, and that the business trip application data update request for updating the approval status of the business trip application data to “denied” is transmitted to the data management device 3.

  Further, in the record 180 in which the event type “attendance check” is registered in the field 181, the notification destination “attendance” is notified to the report destination as the processing content when the button 1 is pressed in the field 181. It is registered that the attendance / leaving data update request for registering the current time at the attendance time of the attendance / attendance data is transmitted to the data management device 3.

  The data update request unit 19 sends data (conference data, telephone memo data, ToDo data, data managed by the data management device 3 to the data management device 3 via the LAN interface unit 12 in accordance with an instruction from the notification event processing unit 20. A data update request for updating business trip application data and attendance data is transmitted.

  The notification event processing unit 20 performs notification to the extension telephone 2 that is the notification destination in accordance with the notification event data stored in the notification event data storage unit 16 and sends a response from the extension telephone 2 that is the notification destination to the report destination It notifies the extension telephone 2 or reflects it in the data managed by the data management device 3.

  The functional configuration of the main apparatus 1 shown in FIG. 15 may be realized by hardware using an integrated logic IC such as ASIC or FPGA, as in the data management apparatus 3, or may be implemented by software using a computer such as a DSP. It may be realized. Alternatively, in a computer system such as a PC equipped with an auxiliary storage device such as a CPU, memory, HDD, DVD-ROM, and a communication interface such as a modem or NIC, the CPU loads a predetermined program from the auxiliary storage device onto the memory. It may be realized by executing.

  FIG. 19 is a flowchart for explaining notification event data generation processing of the main apparatus 1.

  The data request unit 14 transmits a conference data request to the data management device 3 via the LAN interface unit 12 when a predetermined conference data request timing such as a predetermined time before the start time arrives (YES in S400) ( S401). Then, the conference data is received from the data management device 3 (S402) and passed to the notification event data generation unit 17. In response to this, the notification event data generation unit 17 selects unprocessed conference data from the conference data received from the data request unit 14 (S403), and based on the selected conference data, a conference start notification event is selected. The data record 160 is added to the notification event data storage unit 16 (S404).

  Specifically, the notification event data generation unit 17 adds the record 160 to the notification event data storage unit 16, registers a unique event ID in the field 161 of the record 160, and sets the event type “conference start” in the field 162. Register. In the field 163, a time before a predetermined time (for example, 10 minutes) from the start time registered in the field 313 of the record 310 of the selected conference data is registered as the notification time. Further, the extension number of the extension telephone 2 associated with the identification information of each participant registered in the field 315 of the selected conference data record 310 is specified from the extension telephone data storage unit 15, and these extension numbers are specified. Is registered in the field 164 as a notification destination, and the extension number of the extension telephone 2 associated with the identification information of the holding place registered in the field 316 of the selected conference data record 310 is specified, and this extension number is specified. The information is registered in the field 165 as a report destination. Also, using the venue and conference name registered in the fields 316 and 317 of the selected conference data record 310, for example, “(Meeting name) is XX minutes before the start. “Please press button 1 for attendance, press button 2 for absence, and press button 3 for delay.” A conference start message is generated, and this conference start message is registered in the field 166 as notification content. Further, the data ID and data type registered in the fields 311 and 312 of the selected conference data record 310 are registered in the fields 167 and 168, and the state “unprocessed” is registered in the field 169. Accordingly, the record 160 of the conference start notification event data is stored in the notification event data storage unit 16.

  Further, the notification event data generation unit 17 adds the conference end notification event data record 160 to the notification event data storage unit 16 based on the selected conference data (S405).

  Specifically, the notification event data generation unit 17 adds the record 160 to the notification event data storage unit 16, registers a unique event ID in the field 161 of the record 160, and sets the event type “conference end” in the field 162. Register. In the field 163, a time before a predetermined time (for example, 10 minutes) from the end time registered in the field 314 of the selected conference data record 310 is registered as the notification time. Also, the extension number of the extension telephone 2 installed at the venue registered in the field 316 of the selected conference data record 310 is registered in the field 164 as the notification destination, and the report destination in the field 165 is null (blank). ). Also, using the conference name registered in the field 317 of the selected conference data record 310, for example, “(Meeting name) is XX minutes before the end. Press the button 2 and press the button 3 for 60 minutes extension ”, and the conference end message is registered in the field 166 as the notification content. Further, the data ID and data type registered in the fields 311 and 312 of the selected conference data record 310 are registered in the fields 167 and 168, and the state “unprocessed” is registered in the field 169. Thus, the record 160 of the conference end notification event data is added to the notification event data storage unit 16.

  Next, the notification event data generation unit 17 determines whether or not all the conference data received from the data request unit 14 has been processed (S406), and if all the conference data has been processed (YES in S406), Returning to S400, if not processed (NO in S406), the process returns to S403.

  Further, when a predetermined telephone memo data request timing arrives, such as the elapse of a predetermined interval time (YES in S410), the data request unit 14 sends a telephone memo data request to the data management device 3 via the LAN interface unit 12. Transmit (S411). Then, the telephone memo data is received from the data management device 3 (S412) and transferred to the notification event data generation unit 17. In response to this, the notification event data generating unit 17 selects unprocessed conference data from the telephone memo data received from the data requesting unit 14 (S413), and based on the selected telephone memo data, the telephone memo is selected. The notification event data record 160 is added to the notification event data storage unit 16 (S414).

  Specifically, the notification event data generation unit 17 adds a record 160 to the notification event data storage unit 16, registers a unique event ID in the field 161 of this record 160, and sets an event type “phone memo” in the field 162. Register. In the field 163, a time after a predetermined time (for example, 30 minutes) from the reception time registered in the field 323 of the selected telephone memo data record 320 (if this time is earlier than the current time, the current time The time after a predetermined time) is registered as the notification time. Further, the extension number of the extension telephone 2 associated with the identification information of the message destination registered in the field 325 of the record 320 of the selected telephone memo data is specified from the extension telephone data storage unit 15, and this extension number is notified. The extension number of the extension telephone 2 associated with the identification information of the attendant registered in the field 324 of the record 320 of the selected telephone memo data 320 is specified from the extension telephone data storage unit 15 while being registered in the field 164 as the destination. The extension number is registered in the field 165 as a report destination. Further, the message owner, the message owner's telephone number, and the contents of the memo registered in the fields 326, 327, and 328 of the selected telephone memo data record 320 are used, for example, “(message owner) -san (message owner's telephone number). ) Is a message (telephone memo) .Please press button 1 if you agree, press button 2 if you want to call the message. " Register in field 166. Further, the data ID and data type registered in the fields 321 and 322 of the selected telephone memo data record 320 are registered in the fields 167 and 168, and the state “unprocessed” is registered in the field 169. Thereby, the record 160 of the telephone memo notification event data is added to the notification event data storage unit 16.

  Next, the notification event data generation unit 17 determines whether or not all the phone memo data received from the data request unit 14 has been processed (S415), and if all the phone memo data have been processed (YES in S415). ), Return to S400, and if not processed (NO in S415), return to S413.

  In addition, the data request unit 14 transmits a ToDo data request to the data management device 3 via the LAN interface unit 12 when a predetermined ToDo data request timing such as a predetermined time before the start of work arrives (YES in S420). (S421). Then, the ToDo data is received from the data management device 3 (S422) and passed to the notification event data generation unit 17. In response to this, the notification event data generation unit 17 selects unprocessed ToDo data from the ToDo data received from the data request unit 14 (S423), and based on the selected ToDo data, the ToDo notification event data Record 160 is added to the notification event data storage unit 16 (S424).

  Specifically, the notification event data generation unit 17 adds the record 160 to the notification event data storage unit 16, registers a unique event ID in the field 161 of this record 160, and sets the event type “ToDo” in the field 162. Registration is performed, and a predetermined time during working hours is registered in the field 163 as a notification time. Further, the extension number associated with the identification information of the extension telephone 2 of the person in charge registered in the field 334 of the record 330 of the selected ToDo data is specified from the extension telephone data storage unit 15, and this extension number is notified. And the extension number of the extension telephone 2 associated with the identification information of the administrator registered in the field 335 of the record 330 of the selected ToDo data is specified from the extension telephone data storage unit 15. This extension number is registered in the field 165 as a report destination. Also, using the deadline, subject, and importance of ToDo registered in the fields 333, 336, and 337 of the record 330 of the selected ToDo data, for example, the deadline of “(subject) is (deadline)” (importance Todo notification message such as “Press button 1 when completed, press button 2 when working, or button 3 when not yet started.” This ToDo notification message is generated in the field 166 as the notification content. sign up. Further, the data ID and data type registered in the fields 331 and 332 of the record 330 of the selected ToDo data are registered in the fields 167 and 168, and the state “unprocessed” is registered in the field 169. As a result, a record 160 of ToDo notification event data is added to the notification event data storage unit 16.

  Next, the notification event data generation unit 17 determines whether or not all ToDo data received from the data request unit 14 has been processed (S425), and if all ToDo data has been processed (YES in S425), Returning to S400, if not processed (NO in S425), the process returns to S423.

  In addition, the data request unit 14 requests a business trip application data request from the data management device 3 via the LAN interface unit 12 when a predetermined business trip application data request timing such as a predetermined time before the start of work arrives (YES in S430). Is transmitted (S431). Then, business trip application data is received from the data management device 3 (S 432) and passed to the notification event data generation unit 17. In response to this, the notification event data generation unit 17 selects unprocessed business trip application data from the business trip application data received from the data request unit 14 (S433), and based on the selected business trip application data, the business trip application data is selected. The application notification event data record 160 is added to the notification event data storage unit 16 (S434).

  Specifically, the notification event data generation unit 17 adds the record 160 to the notification event data storage unit 16, registers a unique event ID in the field 161 of the record 160, and sets the event type “business trip application” in the field 162. Is registered in the field 163 as a notification time. Further, the extension number of the extension telephone 2 associated with the identification information of the approver registered in the field 345 of the record 340 of the selected business trip application data is specified from the extension telephone data storage unit 15 and the extension number is notified. The extension number of the extension telephone 2 associated with the identification information of the applicant registered in the field 344 of the record 340 of the selected business trip application data is specified from the extension telephone data storage unit 15 while being registered in the field 164 as the destination. The extension number is registered in the field 165 as a report destination. Further, using the business trip date, the applicant, the business trip destination, the transportation means, and the transportation cost registered in the fields 343, 344, 346, 347, 348 of the record 340 of the selected business trip application data, for example, “(applicant) "Business trip date": (Business trip destination): (Destination): (Transportation): (Transportation cost) Press button 1 to approve or press button 2 to reject. And the business trip application message is registered in the field 166 as the notification content. Further, the data ID and data type registered in the fields 341 and 342 of the record 340 of the selected business trip application data are registered in the fields 167 and 168, and the state “unprocessed” is registered in the field 169. As a result, the business trip application notification event data record 160 is added to the notification event data storage unit 16.

  Next, the notification event data generation unit 17 determines whether or not all business trip application data received from the data request unit 14 has been processed (S435), and if all business trip application data has been processed (YES in S435). ), Return to S400, and if not processed (NO in S435), return to S433.

  In addition, the data request unit 14 transmits a time and attendance data request to the data management device 3 via the LAN interface unit 12 when a predetermined time and attendance data request timing such as a predetermined time before the start of work arrives (YES in S440). (S441). Then, the attendance / leaving data is received from the data management device 3 (S442), and is passed to the notification event data generation unit 17. In response to this, the notification event data generation unit 17 selects unprocessed attendance data from the attendance data received from the data request unit 14 (S443), and based on the selected attendance data, the attendance confirmation notification event The data record 160 is added to the notification event data storage unit 16 (S444).

  Specifically, the notification event data generation unit 17 adds a record 160 to the notification event data storage unit 16, registers a unique event ID in the field 161 of this record 160, and sets the event type “attendance confirmation” in the field 162. Register. Further, a time before a scheduled attendance time registered in the field 353 of the record 350 of the selected attendance / leaving data is registered in the field 163 as a notification time. Further, the extension number of the extension telephone 2 associated with the identification information of the attendance and attendance management target person registered in the field 354 of the record 350 of the selected attendance / attendance data is specified from the extension telephone data storage unit 15, and this extension number is specified. The extension number associated with the identification information of the extension telephone 2 of the administrator registered in the field 355 of the record 350 of the selected attendance / attendance data is specified from the extension telephone data storage unit 15 while being registered in the field 164 as the notification destination The extension number is registered in the field 165 as a report destination. Also, for example, an attendance confirmation message such as “Please press button 1 when attending” is generated, and this attendance confirmation message is registered in the field 166 as notification contents. Further, the data ID and data type registered in the fields 351 and 352 of the selected attendance / attendance data record 350 are registered in the fields 167 and 168, and the state “unprocessed” is registered in the field 169. Thus, the attendance confirmation notification event data record 160 is added to the notification event data storage unit 16.

  Next, the notification event data generation unit 17 determines whether or not all the attendance data has been processed from the data request unit 14 (S445), and if all the attendance data have been processed (YES in S445), Returning to S400, if not processed (NO in S445), the process returns to S443.

  FIG. 20 is a flowchart for explaining the notification event execution process of the main device 1.

  The notification event processing unit 20 refers to the notification event data storage unit 16 and monitors the notification time registered in the field 163 of each record 160 in which the state “unprocessed” is registered in the field 169 (S450). If there is a record 160 whose notification time has arrived from among these records 160 (YES in S450), this record 160 is set as a processing target record (S451). Then, the notification event processing unit 20 checks whether or not a flag indicating that notification event processing is in progress is set in the extension telephone 2 that is registered in the field 164 of the processing target record (S452).

  If a flag is set for the extension telephone 2 that is the notification destination (YES in S452), the processing is suspended until the flag is released, and the process proceeds to S460. On the other hand, when the flag is not set (NO in S452), the notification event processing unit 20 instructs the main device function unit 13 to specify the notification extension telephone 2 and to ring for notification. In response to this, the main unit function unit 13 sends a call signal to the extension telephone 2 that is the notification destination via the extension telephone interface unit 10, and rings the extension telephone 2 that is the notification destination a predetermined number of times (S453). Then, the notification event processing unit 20 reads the notification content from the field 166 of the processing target record and passes it to the main device function unit 13. In response to this, the main unit function unit 13 transmits the notification content to the extension telephone 2 that is the notification destination via the extension telephone interface unit 10 and displays the notification content on the display panel of the extension telephone 2 that is the notification destination ( S454).

  Next, the notification event processing unit 20 changes the state registered in the field 169 of the processing target record stored in the notification event data storage unit 16 from “Unprocessed” to “Processing” (S455). The event ID registered in the field 161 of the processing target record 160 is associated with the flag indicating that the notification event is being processed, and this flag is set in the extension telephone 2 that is the notification destination (S456).

  Further, when receiving the PB signal from the extension telephone 2 (YES in S460), the main apparatus function unit 13 notifies the notification event processing unit 20 of this PB signal together with the extension number of the extension telephone 2 that is the PB signal transmission source. In response to this, the notification event processing unit 20 checks whether or not a flag indicating that a notification event is being processed is set in the extension telephone 2 that is the PB signal transmission source (S461). If the flag is set (YES in S461), the notification event processing unit 20 refers to the notification event data storage unit 16, and the event ID associated with this flag is registered in the field 161. A processing target record is identified (S462).

  Next, the notification event processing unit 20 uses the extension telephone data storage unit 15 to identify the user of the extension telephone 2 that is the notification destination that is the PB signal transmission source. Also, the event type registered in the field 162 of the processing target record is specified, and the notification event processing rule record 180 in which this event type is registered in the field 181 is searched from the notification event processing rule storage unit 18. . Then, according to the notification event processing rule registered in the searched record 180, processing corresponding to the button operation specified by the received PB signal is executed (S463). Here, taking the registered content of the notification event processing rule storage unit 18 shown in FIG. 18 as an example, processing (report content display, etc.) according to this button operation will be described.

  When the event type registered in the field 162 of the processing target record is “meeting start”, the notification event processing unit 20 determines that the main device function unit 13 if the received PB signal indicates that the button 1 is pressed. Is displayed on the extension telephone 2 of the report destination registered in the field 165 of the processing target record to the effect that the user of the extension telephone 2 of the notification destination “attends” to the conference. If the received PB signal indicates that the button 2 has been pressed, the main device function unit 13 is controlled to notify the extension telephone 2 of the report destination registered in the field 165 of the processing target record to the notification destination. A message indicating that the user of the extension telephone 2 is “absent” to the conference is displayed, and the data update request unit 19 is controlled to specify the data ID and data type registered in the fields 167 and 168 of the processing target record. Then, a conference data update request for deleting the user of the extension telephone 2 that is the notification destination from the conference participants is transmitted to the data management device 3. If the received PB signal indicates that the button 3 has been pressed, the main apparatus function unit 13 is controlled, and the extension telephone 2 of the notification destination is connected to the extension telephone 2 of the report destination registered in the field 165 of the processing target record. The user of the telephone 2 displays a message “delayed” for the conference.

  In addition, when the event type registered in the field 162 of the processing target record is “conference end”, the notification event processing unit 20 ends the conference if the received PB signal indicates that the button 1 is pressed. Recognize If the received PB signal indicates that the button 2 has been pressed, the notification time registered in the field 163 of the processing target record stored in the notification event data storage unit 16 is extended by 30 minutes, and the data The update request unit 19 is controlled to send a conference data update request for extending the conference end time by 30 minutes, with the designation of the data ID and data type registered in the fields 167 and 168 of the processing target record. It transmits to the management apparatus 3. If the received PB signal indicates that the button 3 is pressed, the notification time registered in the field 163 of the processing target record stored in the notification event data storage unit 16 is extended by 60 minutes, and the data The update request unit 19 is controlled to send a conference data update request for extending the conference end time by 60 minutes with the designation of the data ID and data type registered in the fields 167 and 168 of the processing target record. It transmits to the management apparatus 3.

  When the event type registered in the field 162 of the processing target record is “telephone memo”, the notification event processing unit 20 determines that the main device function if the received PB signal indicates that the button 1 is pressed. The control unit 13 is controlled to display on the extension telephone 2 of the report destination registered in the field 165 of the processing target record that the notification destination “confirmed” the telephone memo, and the data update request unit 19 is controlled. In response to a request for updating the telephone memo data for changing the confirmation state of the telephone memo data to “confirmed” with the designation of the data ID and data type registered in the fields 167 and 168 of the record to be processed. Transmit to device 3. If the received PB signal indicates that the button 2 is pressed, the notification destination displays “confirm” the telephone memo on the extension telephone 2 of the report destination registered in the field 165 of the processing target record. At the same time, the data update request unit 19 is controlled to change the confirmation state of the telephone memo data to “confirmed” with the designation of the data ID and data type registered in the fields 167 and 168 of the processing target record. A telephone memo data update request is transmitted to the data management device 3. Further, the main device function unit 13 is controlled to call the telephone number of the message owner included in the notification content registered in the field 166 of the processing target record, and between the message owner and the extension telephone of the notification destination. Establish a call path in between.

  Further, when the event type registered in the field 162 of the processing target record is “ToDDo”, the notification event processing unit 20 indicates that the processing target record of the processing target record is received if the received PB signal indicates that the button 1 is pressed. On the extension telephone 2 of the report destination registered in the field 165, the notification destination displays that “ToDo” is “completed” and controls the data update request unit 19 to register in the fields 167 and 168 of the processing target record The ToDo data update request for updating the progress status of the ToDo data to “completed” with the specified data ID and data type is transmitted to the data management device 3. If the received PB signal indicates that the button 2 is pressed, the notification destination extension telephone 2 registered in the field 165 of the record to be processed is notified that the notification destination is ToDo. At the same time, the data update request unit 19 is controlled to update the progress status of the ToDo data to “working” with designation of the data ID and data type registered in the fields 167 and 168 of the processing target record. A ToDo data update request is transmitted to the data management device 3. If the received PB signal indicates that the button 3 has been pressed, the report destination extension telephone 2 registered in the field 165 of the record to be processed is notified that the notification destination is ToDo “not started”. At the same time, the data update request unit 19 is controlled to update the progress status of ToDo data to “not yet started” with designation of the data ID and data type registered in the fields 167 and 168 of the processing target record. A ToDo data update request is transmitted to the data management device 3.

  When the event type registered in the field 162 of the processing target record is “business trip application”, the notification event processing unit 20 determines that the received PB signal indicates that the button 1 is pressed, the processing target record Is displayed on the extension telephone 2 of the report destination registered in the field 165, and the fact that the notification destination “approves” the business trip application is displayed, and the data update request unit 19 is controlled to display the fields 167 and 168 of the processing target record. A business trip application data update request for updating the approval state of the business trip application data to “approved” accompanied by the designation of the data ID and data type registered in the data management device 3 is transmitted to the data management device 3. If the received PB signal indicates that the button 2 has been pressed, the report destination extension telephone 2 registered in the field 165 of the record to be processed indicates that the notification destination has “denied” the business trip application. At the same time, the data update request unit 19 is controlled to update the approval state of the business trip application data to “denied” with designation of the data ID and data type registered in the fields 167 and 168 of the processing target record. The business trip application data update request is transmitted to the data management device 3.

  If the event type registered in the processing target record field 162 is “attendance check” and the received PB signal indicates that the button 1 has been pressed, it is registered in the processing target record field 165. The notification destination “attendance” is displayed on the extension telephone 2 of the report destination and the data update request unit 19 is controlled to specify the data ID and data type registered in the fields 167 and 168 of the processing target record The attendance / attendance data update request for registering the current time as the attendance time of attendance / attendance data is transmitted to the data management device 3.

  Next, the notification event processing unit 20 cancels the flag set in the extension telephone 2 of the PB signal transmission source (S464). Then, the state registered in the field 169 of the processing target record stored in the notification event data storage unit 16 is changed from “processing” to “completed” (S465), and then the process returns to S450.

  It should be noted that when a flag indicating that the notification event is being processed has not been released since the flag is set in the extension telephone 2, the flag may be forcibly released.

  The embodiment of the present invention has been described above.

  In the present embodiment, main apparatus 1 stores notification event data including a notification time, a notification destination, and notification contents, and monitors the arrival of the notification time of the stored notification event data. When the notification time arrives, the extension telephone 2 that is the notification destination is specified based on the notification event data, and the notification contents included in the notification event data are displayed on the extension telephone 2. Therefore, according to the present embodiment, by arbitrarily setting the notification time, the notification destination, and the notification content to be included in the notification event data, various notification contents can be sent to the parties at appropriate timing, and the main device 1 Notification can be made without using a separate dedicated device.

  In the present embodiment, the main device 1 rings the extension telephone 2 a predetermined number of times when displaying the notification content on the extension telephone 2 of the notification destination. Therefore, the notification destination user can be more surely notified that there is a notification.

  Further, in the present embodiment, when the main apparatus 1 receives a button operation signal from the extension telephone 2 that is displaying the notification contents according to the notification event data when the notification time has arrived, Performs processing according to the button operation. For example, the extension telephone 2 that is the report destination is specified from the notification event data, and the notification content corresponding to the button operation indicated by the button operation signal is displayed on the extension telephone 2. For this reason, since the user who is the report destination of the notification event can know the response to the notification event of the user who is the notification destination while in his / her seat, the usability is improved.

  Further, in the present embodiment, the main device 1 includes a notification event processing rule storage unit 18 in which the content of the button operation and the content of the processing to be performed are stored in association with each event type. When a button operation signal is received from the extension telephone 2 that is displaying the notification contents according to the notification event data when the time has arrived, the notification event processing rule storage unit 18 is referred to and included in the notification event data. The content of the processing to be performed associated with the event type and the button operation content represented by the button operation signal is specified, and the processing is performed according to the specified processing content. Therefore, according to the present embodiment, it is possible to set the processing for the button operation of the notification destination for each event type, and usability is improved.

  Further, in the present embodiment, the main device 1 acquires data from the data management device 3, and generates and stores notification event data from the acquired data.

  For example, the main device 1 acquires conference data including at least a conference start time, an end time, participants, and a venue from the data management device 3, and uses the acquired conference data as a notification time before the conference start time. Is registered as the notification destination information, the extension phone 2 of the conference location is registered as the report destination information, and the conference start time and location are included as the notification contents The conference start notification event data in which the conference start message is registered, the time before the conference end time is registered as the notification time, the extension telephone 2 of the conference holding location is registered as the notification destination information, and the conference ends as the notification content And conference end notification event data in which the message is registered. When a button operation signal is received from the extension telephone 2 of the participant who is displaying the conference start message according to the conference start notification event data at which the notification time has arrived, the extension of the conference holding location is obtained from the conference start notification event data. The telephone 2 is specified, and the attendance contents of the participant corresponding to the button operation indicated by the received button operation signal are displayed on the specified extension telephone 2. In addition, when a button operation is received from the extension telephone 2 at the venue where the conference end message is being displayed in accordance with the conference end notification event data at which the notification time has arrived, the conference end notification is made according to the button operation represented by this button operation signal. Extend the event data notification time.

  As described above, according to the present embodiment, the conference start notification event data and the conference end notification event data are automatically generated from the conference data acquired from the data management device 3, and the conference start notification event data at which the notification time has arrived or In response to the button operation received from the extension telephone 2 that is the notification destination that is displaying the notification content according to the conference end notification event data, it is possible to set operations corresponding to the conference start notification event data and the conference end notification event data. , Making conference management easier.

  Further, the main device 1 acquires telephone memo data including at least the reception time of the telephone memo, the addressee, the message destination, and the contents of the telephone memo from the data management device 3, and uses the acquired telephone memo data as the notification time. The time after the reception time of the telephone memo is registered, the extension telephone 2 of the message destination is registered as the notification destination information, the extension telephone 2 of the attendee is registered as the report destination information, and the contents of the telephone memo are registered as the notification contents Generated telephone memo notification event data. Then, when a button operation signal is received from the extension telephone 2 that is displaying the contents of the telephone memo according to the telephone memo notification event data when the notification time has arrived, the extension telephone of the attendant is received from the telephone memo notification event data. 2 is specified, and a message indicating that the telephone memo has been confirmed by the message destination is displayed on the specified extension telephone 2.

  As described above, according to the present embodiment, the telephone memo notification event data is automatically generated from the telephone memo data acquired from the data management device 3, and the notification content is displayed according to the telephone memo notification event data when the notification time has arrived. The operation corresponding to the telephone memo notification event data can be set for the button operation received from the extension telephone 2 of the notification destination, and management of the telephone memo becomes easy.

  Further, the main device 1 acquires ToDo data including at least the deadline of ToDo, the person in charge, the administrator, and the subject of ToDo from the data management device 3, and from the acquired ToDo data, the notification time is determined from the ToDo deadline time. The previous time is registered, the extension telephone 2 of the person in charge is registered as the notification destination information, the extension telephone 2 of the manager is registered as the report destination information, and the contents of ToDo including the subject of ToDo and the deadline for deadline are included as notification contents Generate registered ToDo notification event data. When the button operation signal is received from the extension telephone 2 of the person in charge who is displaying the contents of ToDo according to the ToDo notification event data when the notification time has arrived, the extension telephone 2 of the manager is identified from the ToDo notification event data Then, the progress state of the person in charge corresponding to the button operation indicated by the received button operation signal is displayed on the identified extension telephone 2.

  As described above, according to the present embodiment, the ToDo notification event data is automatically generated from the ToDo data acquired from the data management device 3, and the notification content is displayed in accordance with the ToDo notification event data whose notification time has arrived. In response to the button operation received from the extension telephone 2, an operation according to the ToDo notification event data can be set, and the management of ToDo becomes easy.

  Further, the main device 1 acquires business trip application data including at least a business trip date and time, an applicant, an approver, and a business trip destination from the data management device 2, and from the acquired business trip application data, a notification time before the business trip date and time is obtained. The time is registered, the approver's extension telephone 2 is registered as the notification destination information, the applicant's extension telephone 2 is registered as the report destination information, and the notification contents of the business trip application including the business trip date and time, the applicant, and the business trip destination Generate business trip application notification event data with registered contents. Then, when a button operation signal is received from the extension telephone 2 of the approver displaying the contents of the business trip application according to the business trip application notification event data at which the notification time has arrived, the extension telephone of the applicant from the business trip application notification event data 2 is specified, and the approval result of the approver corresponding to the button operation indicated by the received button operation signal is displayed on the specified extension telephone 2.

  Thus, according to the present embodiment, the business trip application notification event data is automatically generated from the business trip application data acquired from the data management device 3, and the notification content is being displayed according to the business trip application notification event data whose notification time has arrived. The operation corresponding to the business trip application notification event data can be set for the button operation received from the extension telephone 2 of the notification destination, and the business trip application can be easily managed.

  In addition, the main device 1 acquires attendance / attendance data including at least the scheduled attendance time, attendance / attendance management person and manager from the data management device, and the time before the scheduled attendance time is registered as the notification time from the acquired attendance / attendance data The extension telephone 2 of the attendance management target person is registered as the notification destination information, the extension telephone 2 of the administrator is registered as the report destination information, and the attendance confirmation notification event data in which the attendance confirmation message is registered as the notification content is generated. . Then, when a button operation signal is received from the extension telephone 2 of the attendance management attendee who is displaying the attendance confirmation message in accordance with the attendance confirmation notification event data at which the notification time has arrived, the extension of the administrator from the attendance confirmation notification event data is received. The telephone set 2 is specified, and the specified extension telephone set 2 displays that the attendance management person has started work.

  As described above, according to the present embodiment, attendance confirmation notification event data is automatically generated from the attendance / leaving data acquired from the data management device 3, and the notification content is being displayed according to the attendance confirmation notification event data when the notification time has arrived. An operation corresponding to the attendance confirmation notification event data can be set for the button operation received from the extension telephone 2 of the notification destination, and attendance management becomes easy.

  In addition, this invention is not limited to said embodiment, Many deformation | transformation are possible within the range of the summary.

  For example, in the above-described embodiment, as the notification event data, conference start notification event data, conference end notification event data, telephone memo notification event data, ToDo notification event data, business trip application notification event data, and attendance confirmation notification event data are used. Although described as an example, the present invention is not limited to notification event data of these event types, and can handle notification event data of various event types.

  In the above embodiment, the main device 1 acquires data from the data management device 3 and generates event notification data from the acquired data. However, the administrator of the main device 1 creates the data in advance. The received event notification data may be input to the main apparatus 1. Further, the function of the data management device 3 may be added to the main device 1 to integrate both.

  1: main device, 2, 2-1 to 2-n: extension telephone, 3: data management device, 4: gateway, 5: public network, 6: LAN, 7: IP network, 10: extension telephone interface unit, 11 : Public network interface unit, 12: LAN interface unit, 13: main device function unit, 14: data request unit, 15: extension telephone data storage unit, 16: notification event data storage unit, 17: notification event data generation unit, 18 : Notification event processing rule storage unit, 19: Data update request unit, 20: Notification event processing unit, 30: LAN interface unit, 31: Conference data storage unit, 32: Telephone memo data storage unit, 33: ToDo data storage unit, 34: Business trip application data storage unit, 35: Attendance data storage unit, 36: Data management unit

Claims (12)

A main device that accommodates a plurality of telephones,
Notification event data storage means for storing notification event data including at least notification time, notification destination information, and notification content;
Notification event processing means for monitoring the arrival of the notification time of the notification event data stored in the notification event data storage means and processing the notification event data when the call time has arrived,
The notification event processing means includes:
Based on the notification destination information of the notification event data when the notification time has arrived, the notification destination telephone is identified from the plurality of telephones, and the notification content included in the notification event data is stored in the notification destination telephone. Main device characterized by displaying. The main device according to claim 1,
The notification event processing means includes:
The main apparatus, wherein when the notification content is displayed on the notification destination telephone, the telephone is ringed. The main apparatus according to claim 1 or 2,
The notification event processing means includes:
When a button operation signal is received from the notification destination telephone that is displaying the notification content according to the notification event data when the notification time has arrived, processing corresponding to the button operation represented by the button operation signal is performed. Main device to do. The main device according to claim 3,
The notification event data includes report destination information,
The notification event processing means includes:
When a button operation signal is received from the notification destination telephone that is displaying the notification contents in accordance with the notification event data when the notification time has arrived, from among the plurality of telephones based on the report destination information of the notification event data A main apparatus characterized in that a report destination telephone is specified and a report content corresponding to a button operation indicated by the button operation signal is displayed on the report destination telephone. The main apparatus according to claim 3 or 4,
For each event type, it further includes a notification event processing rule storage means in which the content of the button operation and the content of the processing to be performed are stored in association with each other,
The notification event data includes an event type,
The notification event processing means includes:
When a button operation signal is received from the notification destination telephone that is displaying the notification content according to the notification event data when the notification time has arrived, the event type included in the notification event data and the button represented by the button operation signal A main apparatus characterized in that, based on the content of an operation, the content of a process to be performed is specified from the notification event rule storage unit, and the process is performed according to the content of the specified process. A main device according to any one of claims 1 to 5,
Data acquisition means for acquiring data including at least time information, related party information, and management target information;
The main apparatus further comprising: notification event data generation means for generating notification event data from the data acquired by the data acquisition means and storing the notification event data in the notification event data storage means. The main device according to claim 6,
The data acquisition means includes
Retrieve meeting data from the data management device, including at least the scheduled start and end times of the meeting, meeting participants, and meeting location,
The notification event data generation means includes:
From the conference data acquired by the data acquisition means, the time before the scheduled start time of the conference is registered as the notification time, the information related to the conference participant's telephone is registered as the notification destination information, and the conference information as the report destination information Information related to the phone at the location of the conference is registered, the conference start notification event data in which the conference start message including the conference location is registered as the notification content, and the time before the scheduled end time of the conference is registered as the notification time , Information related to the conference location phone is registered as notification destination information, and conference end notification event data in which a conference end message is registered as notification content, and
The notification event processing means includes:
When a button operation signal is received from a participant's phone that is displaying a conference start message according to the conference start notification event data when the notification time has arrived, the conference location phone is identified from the conference start notification event data, Display the attendance information of the participant according to the button operation indicated by the button operation signal on the phone,
When a button operation is accepted from the telephone at the venue where the conference end message is displayed in accordance with the conference end notification event data when the notification time has arrived, in response to the button operation indicated by the button operation signal, the conference end notification event data Main device characterized by extending notification time. The main device according to claim 6,
The data acquisition means includes
Retrieve phone memo data from the data management device, including at least the reception time of the phone memo, the respondent, the message destination, and the contents of the phone memo,
The notification event data generation means includes:
From the telephone memo data acquired by the data acquisition means, a time after the reception time of the telephone memo is registered as the notification time, information related to the telephone of the message destination is registered as the notification destination information, and the respondent is reported as the report destination information Phone memo notification event data in which the information related to the phone is registered and the content of the phone memo is registered as the notification content,
The notification event processing means includes:
When a button operation signal is received from the message destination telephone that is displaying the contents of the telephone memo according to the telephone memo notification event data when the notification time has arrived, the telephone of the responder is identified from the telephone memo notification event data, A main device that displays a message on the telephone indicating that the telephone memo has been confirmed by the message destination. The main device according to claim 6,
The data acquisition means includes
ToDo data is acquired from the data management device including at least the deadline of ToDo, the person in charge, the administrator, and the subject of ToDo,
The notification event data generation means includes:
From the ToDo data acquired by the data acquisition means, a time before the ToDo deadline time is registered as a notification time, information relating to the telephone of the person in charge is registered as notification destination information, and an administrator's telephone is used as report destination information ToDo notification event data in which the ToDo content including the ToDo subject and deadline is registered as notification content is registered.
The notification event processing means includes:
When a button operation signal is received from the telephone of the person in charge who is displaying the contents of ToDo according to the ToDo notification event data when the notification time has arrived, the administrator's telephone is identified from the ToDo notification event data, A main apparatus for displaying a progress status of a person in charge according to a button operation indicated by the button operation signal. The main device according to claim 6,
The data acquisition means includes
The travel application data including at least the business trip date and time, the applicant, the approver, and the business trip destination is acquired from the data management device,
The notification event data generation means includes:
From the business trip application data acquired by the data acquisition means, the time before the business trip date is registered as the notification time, the information related to the approver's telephone is registered as the notification destination information, and the reporter information is stored in the applicant's telephone. This information is registered, and the business trip application notification event data in which the content of the business trip application including the business trip date and time, the applicant, and the business trip destination is registered as notification content is generated,
The notification event processing means includes:
When a button operation signal is received from the approver's phone displaying the contents of the business trip application according to the business trip application notification event data when the notification time has arrived, the applicant's phone is identified from the business trip application notification event data, A main apparatus for causing a telephone to display an approval result of an approver according to a button operation represented by the button operation signal. The main device according to claim 6,
The data acquisition means includes
Acquire at least attendance / attendance data including at least the scheduled attendance / attendance / attendance management person and manager from the data management device,
The notification event data generation means includes:
From the attendance / attendance data acquired by the data acquisition means, the time before the scheduled attendance time is registered as the notification time, the information related to the telephone of the attendance / employment management person is registered as the notification destination information, and the administrator's The attendance confirmation notification event data in which the information related to the telephone is registered and the attendance confirmation message is registered as the notification content is generated,
The notification event processing means includes:
When the button operation signal is received from the attendance / work attendance management person who is displaying the attendance confirmation message according to the attendance confirmation notice event data that the notification time has arrived, the administrator's telephone is identified from the attendance confirmation notice event data. The main device displays on the telephone that the attendance management person has worked. A notification method using a main device accommodating a plurality of telephones,
The main unit is
Monitor the arrival of notification time of notification event data including notification time, notification destination information, and notification content stored in the device itself,
Based on the notification destination information of the notification event data when the notification time has arrived, the notification destination telephone is identified from among the plurality of telephones,
A notification method comprising: displaying the notification content included in the notification event data when the notification time has arrived on the identified notification destination telephone.

Images