JP2019117968A - Outgoing and incoming history management device and program - Google Patents

Abstract

To increase the number of pieces of incoming and outgoing call history data that the user can confirm.SOLUTION: An outgoing and incoming history management device includes a first reception unit, a history management unit, a second reception unit, a first acquisition unit, a second acquisition unit, and a transmission unit. The first reception unit receives a call event from a switch issuing a call event that includes an originating telephone number and a terminating telephone number. The history management unit stores, in a first storage device, history data in which the originating telephone number and the terminating telephone number included in the call event are associated with each other. The second reception unit receives identification data from a user terminal. The first acquisition unit refers to number data stored in a second storage device and associating a plurality of telephone numbers, and acquires one or more telephone numbers associated with the identification data. The second acquisition unit acquires, from the first storage device, history data including an originating telephone number or an incoming telephone number associated with the acquired one or more telephone numbers. The transmission unit transmits the acquired history data to the user terminal.SELECTED DRAWING: Figure 1

Description

  The present invention relates to a call origination / reception history management apparatus and program.

  For example, a private branch exchange (PBX: Private Branch eXchange) used on a premises such as in a company enables a call between the originating telephone and an extension telephone on the premises upon receiving a call from the originating telephone. In addition, the private branch exchange, upon receiving a call from a local extension telephone, enables a call between the local extension telephone and an external incoming telephone. In addition, the private branch exchange enables calls between a plurality of extension telephones.

  For example, the extension telephone which has made an incoming / outgoing call stores outgoing / incoming call history data including an incoming / outgoing telephone number, time data, and the like. Then, the extension telephone can display the stored call origination / reception history data.

  It is also possible to assign shared telephone numbers (sublines) to a plurality of extension telephones under the private branch exchange. The shared telephone number may be used as a representative telephone number.

Unexamined-Japanese-Patent No. 2002-204311 JP, 2015-126351, A

  Usually, the number of call origination / deletion history data that can be stored by the extension telephone has an upper limit, such as, for example, up to the latest 30. Therefore, when the number of calls is increased, the necessary call history data may be deleted.

  In addition, depending on the model of the extension telephone, call origination / reception history data for call origination / reception regarding the shared telephone number may not be stored.

  Further, the call origination / receipt history data is stored inside the extension telephone which made / received a call or inside the private branch exchange, and the user who uses a plurality of telephones must actually operate the telephone where the call originated / occurred. Even for the same user, it is difficult to confirm call origination / receipt history data when making / receiving calls with another telephone.

  The present invention has been made in view of the above-mentioned circumstances, and relates to a call origination / reception history management apparatus and program for increasing the number of call origination / reception history data that can be confirmed by the user.

  The call origination / reception history management apparatus according to the example of the embodiment includes a first reception unit, a history management unit, a second reception unit, a first acquisition unit, a second acquisition unit, and a transmission unit. . The first receiving unit receives a call event from a switch which issues a call event including a calling telephone number and a called telephone number at least when receiving a call from a calling telephone or making a call to a called telephone. The history management unit stores, in the first storage device, history data in which a calling telephone number included in a call event is associated with a called telephone number. The second receiver receives identification data from the user terminal. The first acquisition unit refers to number data stored in the second storage device and associating a plurality of telephone numbers, and acquires one or more telephone numbers associated with the identification data. The second acquisition unit acquires, from the first storage device, history data including an originating telephone number or an incoming telephone number associated with the acquired one or more telephone numbers. The transmission unit transmits the acquired history data to the user terminal.

  According to the present invention, it is possible to increase the number of incoming and outgoing call history data that can be confirmed by the user.

BRIEF DESCRIPTION OF THE DRAWINGS The block diagram which shows the example of a structure of a telephone call system provided with the transmission / reception log management apparatus which concerns on 1st Embodiment. FIG. 1 is a block diagram showing an example of a hardware configuration of a call system according to a first embodiment. A data structure figure showing an example of a call event concerning a 1st embodiment. The data structure figure which shows the example of the relationship of the identification data which concern on 1st Embodiment, management data, number data, and transmission / reception historical data. 6 is a flowchart showing an example of call origination / reception history data generation processing of the call origination / reception history management device according to the first embodiment. 6 is a flowchart showing an example of call origination / reception history data acquisition processing of the call origination / reception history management apparatus according to the first embodiment. The figure which shows the example of the display screen of the display apparatus of the user terminal which concerns on 1st Embodiment. FIG. 7 is a block diagram showing an example of the configuration of a call system according to a second embodiment.

  Hereinafter, embodiments will be described with reference to the drawings. In the drawings, the same functions and components will be denoted by the same reference numerals and descriptions thereof will be omitted or will be briefly described.

First Embodiment
In the first embodiment, call origination / reception history data is generated based on a call event issued from the exchange, identification data is received from the user terminal, and one or more registered telephone numbers associated with the identification data are acquired. A call origination / reception history management apparatus that transmits call origination / reception history data corresponding to the acquired one or more registered telephone numbers to the user terminal will be described.

  FIG. 1 is a block diagram showing an example of the configuration of a call system 1 provided with the call origination / reception history management device 3 according to the first embodiment.

  The call system 1 includes the exchange 2 and the call origination / reception history management device 3. The call system 1 may further include the user terminal 4.

  The exchange 2 can communicate with the telephones T1 to Tn. In the first embodiment, the telephone set T0 is not subordinate to the exchange 2, that is, it does not belong to an extension. On the other hand, it is assumed that the telephones T1 to Tn are subordinate to the exchange 2 and belong to the extension telephones. In the example of FIG. 1, the attribute of whether or not the telephone sets T0 to Tn belong to the extension telephone is an example, and can be freely changed.

  In FIG. 1, although the case where the telephone set T0 is a calling telephone set (transmission source) and the telephone set T1 is a reception telephone set (transmission destination) is described as an example, any one of the telephone sets T0 to Tn is a calling telephone set and any one is an incoming call. It may be a telephone. The phones T0 to Tn may be fixed phones or mobile phones.

  Although the user terminal 4 and the telephones T0 to Tn are separately configured in FIG. 1, the user terminal 4 may be any of the telephones T0 to Tn.

  The exchange 2 includes a connection unit 5, an event issuing unit 6, a storage device 7, and an API (Application Programming Interface) control unit 8. In the first embodiment, the exchange 2 will be described as an example of an internal exchange, but the exchange 2 may be another type of telephone exchange.

  When receiving an incoming call from the telephone set T0 which is a transmission telephone, the connection unit 5 communicably connects the telephone set T0 and the telephone set T1 which is a reception telephone set.

  The event issuing unit 6 issues a call event to the call origination / reception history management device 3 together with the connection operation by the connection unit 5, that is, in parallel with the connection operation by the connection unit 5.

  In the first embodiment, the call event includes, for example, an originating telephone number (FROM), an incoming telephone number (TO), and an event type. Furthermore, the call event may include, for example, event occurrence time data.

  As an event type, for example, an incoming event (INCOMING) indicating that the exchange 2 has arrived, an outgoing event (OUTGOING or DIALED) indicating that the exchange 2 has transmitted, and the incoming call T1 for the call from the outgoing telephone T0 There is a response event (CONNECTED) indicating that a response (a call or connection) has been made.

  The storage unit 7 stores number data 9. The storage device 7 may be configured separately from the exchange 2. The storage device 7 may be configured of a plurality of storage devices.

  The number data 9 includes, for example, a telephone number managed by the exchange 2. The number data 9 is, for example, data associating at least one telephone number (hereinafter referred to as a registered telephone number) assigned to the same user. The number data 9 may be, for example, data in the form of a table or data in the form of a list, and its data structure may be such that it is possible to obtain from the telephone number another telephone number associated with the telephone number. Good. The same applies to the data structure of other data described later that associates a plurality of data with each other.

  The identification data may be, for example, the user's name, a user-specific ID or number, device identification data (device ID) used by the user, and attribute data of the user. The attribute data of the user may be, for example, a company, a department, a group or the like to which the user belongs. The identification data may also be the telephone number of the telephone used by the user. For example, the user may be assigned a unique extension number, and this extension number may be used as identification data.

  In the first embodiment, the various telephone numbers may be, for example, unique telephone numbers of telephones, shared telephone numbers assigned to a plurality of telephones, or telephone numbers for virtual extensions.

  Here, a virtual extension is an extension that is defined and managed as extension data in the exchange 2 in the same manner as a normal extension, but is not associated with a physical telephone set (a device such as a communication device) under the exchange 2. is there. A virtual extension can have the same high functionality as a telephone, just like a regular extension, even if it is not associated with a physical telephone. In addition, the virtual extension does not necessarily have to be defined only by data in the exchange 2. The virtual extension may be defined in a form including a program provided in the exchange 2.

  When the API control unit 8 receives a command conforming to a predetermined rule from the call origination / reception history management device 3, the API control unit 8 executes a process according to the command and sends the processing result back to the call origination history management device 3. As a specific example, the API control unit 8 receives a transmission command of the number data 9 from the transmission / reception history management device 3, reads out the number data 9 from the storage device 7 based on the transmission command, and manages the number data 9 It may be sent to the device 3.

  The call reception history management device 3 is an information processing device such as a server device, for example, and can communicate with the exchange 2. The incoming and outgoing call history management device 3 may be, for example, a CTI (Computer Telephony Integration) server.

  The call origination / reception history management device 3 includes a reception unit 10, a history management unit 11, a reception unit 12, a number acquisition unit 13, a history acquisition unit 14, a transmission unit 15, an inquiry unit 23, and a registration unit 24. , And a storage device 16. The transmission history management device 3 can store various data in the storage device 16 or can read out various data from the storage device 16. The incoming and outgoing call history management device 3 may be realized in cooperation with a plurality of information processing devices. The storage device 16 may be configured separately from the call origination / reception history management device 3. The storage device 16 may be, for example, a database management system. The storage device 16 may be configured of, for example, a plurality of storage devices.

  The receiving unit 10 receives a call event issued from the exchange 2.

  The history management unit 11 determines whether the event type included in the call event is any of an incoming call event, an outgoing call event, and a response event.

  Then, when the event type included in the call event indicates an incoming event or an outgoing event, the history management unit 11 indicates the originating telephone number included in the call event, the incoming phone number, and the type indicating the event type. Call origination / reception history data 171 in which data, status (state) data indicating non-response (absent), and time (date and time) data are associated is generated, and call origination / reception history data 171 is stored in storage device 16 .

  Here, when the call event includes event occurrence time data, the event occurrence time data included in the call event may be used as the time data included in the call origination / reception history data 171. Alternatively, the time data included in the transmission / reception history data 171 may be set using the time (system time) managed by the clock function of the transmission / reception history management device 3.

  Also thereafter, the history management unit 11 generates the call reception history data 172 to 17 m each time the type of the call event received by the reception unit 10 is the incoming call event or the outgoing call event, and the call reception history data 172 -17 m are stored in the storage device 16. As a result, the transmission and reception history data 171 to 17 m are stored in the storage device 16. The incoming and outgoing call history data 171 to 17m may be managed, for example, in a table format.

  On the other hand, when the event type included in the call event indicates a response event, the history management unit 11 is included in the call event from among the call origination / reception history data 171 to 17 m stored in the storage device 16. Outgoing / incoming call history data including the outgoing call number and incoming call number are extracted, status data of the extracted outgoing / incoming call history data is updated from non-response to response, and the updated outgoing / outgoing call history data is stored in the storage unit 16 Remember to

  The storage device 16 stores call origination / reception history data 171 to 17 m, management data 43, and telephone number management data 22. Further, the storage device 16 may store number data 9.

  Management data 43 associates identification data with a reference telephone number. Furthermore, the management data 43 may associate various user information with the identification data. In this case, the call origination / reception history management device 3 can perform user authentication or user attribute authentication using the identification data and the management data 43.

  The telephone number management data 22 is, for example, data which is managed by the call origination history management device 3 and used in the telephone directory function, and associates a telephone number with a name or a name.

  The receiver 12 receives identification data from the user terminal 4.

  The number acquisition unit 13 acquires (refers to), for example, the management data 43 stored in the storage device 16. Management data 43 associates identification data with a reference telephone number. The number acquisition unit 13 acquires, from the management data 43, a reference telephone number associated with the identification data received by the reception unit 12.

  The number acquisition unit 13 also acquires, for example, the number data 9 stored in the storage device 16.

  When the number data 9 is not stored in the storage device 16 or when the number data 9 can not be obtained from the storage device 16, the number acquisition unit 13 transmits, for example, a transmission command of the number data 9 to the exchange 2 You may In this case, the API control unit 8 of the exchange 2 receives the transmission command, reads the number data 9 from the storage device 7 according to the transmission command, and transmits the read number data 9 to the call origination / reception history management device 3. The number acquisition unit 13 receives the number data 9 from the exchange 2.

  Then, the number acquisition unit 13 acquires, from the number data 9, one or more registered telephone numbers associated with the acquired reference telephone number.

  When the identification data is a telephone number, the process of acquiring the reference telephone number by the number acquiring unit 13 as described above and the management data 43 may be omitted. In this case, the number acquisition unit 13 may acquire one or more registered telephone numbers from the number data 9 by using the identification data as it is as a reference telephone number.

  The history acquisition unit 13 acquires, from among the transmission and reception history data 171 to 17 m stored in the storage device 16, transmission and reception history data including one or more registered telephone numbers acquired by the number acquisition unit 13.

  For example, it is assumed that the number acquisition unit 13 acquires an extension number used by the user and a plurality of shared telephone numbers as one or more registered telephone numbers. In this case, the history acquisition unit 13 extracts call origination / reception history data including a calling telephone number or a called telephone number that matches any of the acquired extension numbers and the plurality of shared telephone numbers.

  For example, in addition to extracting the call origination / receipt history data based on the matching of the calling phone number or the call arrival phone number as described above, the time data of the call origination / receipt history data is within a predetermined period from the latest. , That the outgoing and incoming history data is within a predetermined number from the latest, that the type data of outgoing and incoming history data is an incoming event, that the type data of outgoing and incoming history data is an outgoing event, state data of outgoing / receiving history data May be added to the extraction condition at least one of unanswered or status data of the call origination / receipt history data being a response.

  The transmission unit 15 transmits all or part of the transmission / reception history data acquired by the history acquisition unit 13 to the user terminal 4.

  For example, the transmitting unit 15 indicates that the time data of the acquired call origination history data is within a predetermined period from the latest, that the call origination history data is within a predetermined number from the latest, and the type data of the call origination history data is received At least an event, a type data of call origination / reception history data being a transmission event, a state data of call origination / reception history data being unanswered, or a state data of call origination / reception history data being a response One may be added to the transmission condition.

  The conditions of the transmission and reception history data transmitted from the transmission and reception history management apparatus 3 to the user terminal 4 may be settable from the user terminal 4.

  The inquiry unit 23 determines whether the telephone number management data 22 stored in the storage device 16 includes the originating telephone number or the incoming telephone number included in the originating and receiving history data acquired by the history acquiring unit 13. To judge. Then, when the calling telephone number or the incoming telephone number included in the acquired call origination / reception history data is not included in the telephone number management data 22, the inquiry unit 23 is not included in the telephone number management data 22. The user terminal 4 is inquired as to whether a calling telephone number or a called telephone number is to be registered in the telephone number management data 22.

  For example, the inquiry unit 23 displays a registration button near the display position of the originating telephone number or the incoming telephone number not included in the telephone number management data 22, and prompts the user to specify the registration button when the user wishes to register. Execute processing for

  When the registration unit 24 receives a registration instruction from the user terminal 4, the registration unit 24 registers, in the telephone number management data 22, the originating telephone number or the incoming telephone number not included in the telephone number management data 22. Thereby, the telephone number management data 22 used in the telephone directory function in the call origination / reception history management device 3 can be enriched.

  The user terminal 4 is an information processing apparatus such as a client apparatus, for example, and can communicate with the call origination / reception history management apparatus 3. The user terminal 4 may be, for example, a personal computer, a tablet computer, a smartphone, a fixed telephone, a portable telephone, or the like.

  The user terminal 4 includes a transmitting unit 18, a receiving unit 19, and a display control unit 20. The transmission unit 18, the reception unit 19, and the display control unit 20 of the user terminal 4 are realized by, for example, an operating system, a browser, an application program, or a combination of two or more thereof.

  The transmission unit 18 transmits identification data to the call origination / reception history management device 3 in accordance with, for example, a user operation. The transmitting unit 18 may notify the calling history management apparatus 3 of, for example, designation of the number of data, time data, type data, and status data as the conditions of the calling history data to be extracted.

  In addition, the transmitting unit 18 transmits, to the transmission / reception history management apparatus 3, a registration instruction regarding the originating telephone number or the incoming telephone number not included in the telephone number management data 22.

  The receiving unit 19 receives call origination / reception history data from the call origination / reception history management device 3. Further, the receiving unit 19 receives, from the call origination / reception history management device 3, an inquiry as to whether to register the originating telephone number or the incoming telephone number not included in the telephone number management data 22 in the telephone number management data 22.

  The display control unit 20 executes control for displaying the received call origination / reception history data. When the display control unit 20 receives an inquiry for registration of the telephone number management data 22, the display control unit 20 displays, for example, an icon for receiving a registration instruction such as a registration button.

  FIG. 2 is a block diagram showing an example of the hardware configuration of the call system 1 according to the first embodiment.

  The exchange 2 includes, for example, a storage device 7, a processor 25, and a communication device 26. The storage device 7 stores the number data 9 and the program 27. The processor 25 executes the program 27 stored in the storage device 7 to function as the connection unit 5, the event issuing unit 6, and the API control unit 8 of FIG. Communicate with other devices.

  The incoming and outgoing call history management device 3 includes, for example, a storage device 16, a processor 28, and a communication device 29. The storage device 16 stores number data 9, call origination / receipt history data 171 to 17m, a program 30, management data 43, and telephone number management data 22. The processor 28 executes the program 30 stored in the storage device 16 to allow the reception unit 10, the history management unit 11, the reception unit 12, the number acquisition unit 13, the history acquisition unit 14, and the transmission unit 15 of FIG. , Functions as an inquiry unit 23 and a registration unit 24, controls the communication device 29, and communicates with other devices.

  The user terminal 4 includes, for example, a storage device 21, an operation device 31, a display device 32, a processor 33, and a communication device 34. The storage unit 21 stores telephone number management data 22 and a program 35. The operating device 31 is a device that receives a user's operation, and may be, for example, an input device such as a touch panel, a keyboard, or a mouse. The display device 32 is, for example, a device capable of displaying text or an image, such as a liquid crystal display or an organic EL display. The processor 33 functions as the transmitting unit 18, the receiving unit 19 and the display control unit 20 of FIG. 1 by executing the program 35 stored in the storage device 21 and controls the communication device 34 to perform other functions. Communicate with the device. The program 35 may be, for example, an operating system, a browser, an application program, or the like.

  In FIG. 2 described above, the number data 9 is stored in the storage unit 7 of the exchange 2 and the storage unit 16 of the call origination / reception history management device 3. It may be stored in any one of the storage device 16.

  FIG. 3 is a data structure diagram showing an example of the call event 36 according to the first embodiment.

  The call event 36 is issued from the exchange 2 to the incoming / outgoing call history management device 3 when various events such as an outgoing call event, an incoming call event, a response event, etc. occur in the exchange 2.

  The call event 36 includes, for example, an originating telephone number 36a, an incoming telephone number 36b, an event type 36c, and event occurrence time data 36d. The event occurrence time data 36 d may not be included in the call event 36. Also, the call event 36 may include call identification data (call ID) specific to the event that occurred.

  The originating telephone number 36a indicates the telephone number of the originating telephone. The incoming call number 36b indicates the telephone number of the incoming call destination telephone.

  The event type 36c may be, for example, an incoming event indicating that the exchange 2 has arrived, an outgoing event indicating that the exchange 2 has originated, or an opposite telephone such as an incoming telephone, for example. It indicates a type such as a response event indicating that the originating telephone and the incoming telephone are in a connected state by responding.

  The incoming call event is, for example, an event in which a call from an outgoing telephone at an outside line or extension to the incoming telephone at an extension via the exchange 2 occurs. The originating event is, for example, an event in which a call from an originating telephone set of an extension to a calling party of an extension or an extension via the exchange 2 occurs. The response event occurs, for example, when the originating telephone and the incoming telephone are connected, regardless of whether the exchange 2 is an incoming call or an outgoing call.

  The event occurrence time data 36 d indicates the time when an event corresponding to the call event 36 has occurred.

  FIG. 4 is a data structure diagram showing an example of the relationship between identification data 37, management data 43, number data 9, and call origination history data 171 to 17m according to the first embodiment. In FIG. 4, the number data 9 represents only the identification data 37 and one or more registered telephone numbers (telephone number 38, telephone number 38a, shared telephone numbers 38b, 38c) associated with the identification data 37. Is shown. The incoming and outgoing call history data 171 to 17m represent only outgoing and incoming call history data 171 and 17m.

  The identification data 37 is, for example, data transmitted from the user terminal 4 to the transmission / reception history management apparatus 3 and is unique identification data assigned to a user who wants to browse the transmission / reception history. The identification data 37 may be, for example, a user ID, a device ID used by the user, a name, an extension number used by the user, or the like if personal identification is possible.

  The management data 43 associates the identification data 37 with the reference telephone number 37a. The management data 43 is used to convert the identification data 37 into the reference telephone number 37a. When the identification data 37 is a telephone number, the conversion process using the management data 43 can be omitted.

  The number data 9 associates, for example, telephone numbers assigned to the same user.

  In the example of FIG. 4, as described above, the number data 9 includes, for example, the telephone number 38 assigned to the same user, the extension telephone number 38a, the shared telephone number 38b, and the shared telephone number 38c. It is related. Therefore, the call origination / receipt history management device 3 searches the number data 9 based on the reference telephone number 37a to obtain the telephone number 38 that matches the reference telephone number 37a and the extension telephone number associated with the telephone number 38. 38a, shared telephone number 38b, and shared telephone number 38c can be obtained as registered telephone numbers for the same user.

  For example, each of the transmission / reception history data 171 to 17m associates a transmission telephone number, a reception telephone number, type data indicating a type of history, status data indicating a call status, and time data.

  The outgoing telephone number, incoming telephone number, and time data of the incoming and outgoing call history data 171 to 17m are generated based on the outgoing telephone number, incoming telephone number, and event occurrence time data of the corresponding call event, respectively.

  The type data of the incoming / outgoing history data 171 to 17m indicates incoming when the event type of the corresponding call event is an incoming event, and indicates outgoing when the event type of the call event is an outgoing event.

  The type data of the incoming / outgoing history data 171 to 17m indicates unanswered when the event type of the corresponding call event is an incoming event or an outgoing event, and responds from unanswered when the event type of the corresponding call event is an answer event To be updated.

  In the example of FIG. 4, the call origination / receipt history data 171 includes, for example, a call origination telephone number 39a, a call reception phone number 39b, type data 39c, status data 39d, and time data 39e.

  In addition, the transmission / reception history data 17m includes, for example, a transmission telephone number 40a, a reception telephone number 40b, type data 40c, status data 40d, and time data 40e.

  The call origination / reception history management device 3 is a call origination / reception history based on one or more registered telephone numbers acquired from the identification data 37, the extension telephone number 38a, the shared telephone number 38b, and the shared telephone number 39c. Data 171 to 17m are searched.

  In the example of FIG. 4, it is assumed that the extension telephone number 38a obtained from the identification data 37 matches the originating telephone number 39a of the originating and receiving history data 171. In addition, it is assumed that the shared telephone number 38c acquired from the identification data 37 matches the incoming telephone number 40b of the outgoing and incoming call history data 17m.

  In this case, as the history data for the user indicated by the identification data 37, the transmission / reception history management device 3 transmits / receives history data 171 including the transmission telephone number 39a that matches the acquired extension telephone number 38a, and the acquired sharing Incoming / outgoing call history data 17 m including the incoming call number 40 b that matches the telephone number 38 c of the above is transmitted to the user terminal 4.

  FIG. 5 is a flowchart showing an example of call origination history data generation processing of the call origination / reception history management device 3 according to the first embodiment. In this FIG. 5, the case where the transmission / reception history data 171 of FIG. 4 is generated based on the issuance of the call event 36 of FIG. 3 will be described as an example.

  In step S501, the receiving unit 10 receives the call event 36 issued from the exchange 2.

  In step S502, the history management unit 11 determines whether the event type 36c included in the call event 36 is an incoming call event or an outgoing call event, or a response event.

  If the event type 36c is an incoming call event or an outgoing call event, in step S503, the history management unit 11 sends the outgoing call number 36a, the incoming call number 36b, the event type 36c, and the event occurrence time data 36d contained in the call event 36. The originating telephone number 39a, the incoming telephone number 39b, the type data 39c, and the time data 39e of the originating and receiving history data 171, respectively. In addition, the history management unit 11 sets the state data 39 d of the transmission / reception history data 171 as unanswered. As a result, call origination / reception history data 171 corresponding to the call event 36 is generated.

  In step S 504, the history management unit 11 stores the generated call origination / reception history data 171 in the storage device 16. Then, the process moves to step S507.

  If it is determined in step S502 that the event type 36c is a response event, in step S505, the history management unit 11 determines, for example, the calling telephone number 36a, the incoming telephone number 36b, and the event included in the call event 36. Based on the occurrence time data 36d, the transmission / reception history data 171 corresponding to the call event 36 is extracted from the storage device 16. More specifically, the history management unit 11 selects, for example, the outgoing call number 39a and the incoming call that match the outgoing call number 36a of the call event 36 and the incoming call number 36b among the plurality of outgoing / incoming call history data 171 to 17m. From the event occurrence time data 36d including the number 39b, it extracts call origination / receipt history data 171 including time data 39e within a predetermined period.

  In step S506, the history management unit 11 updates, for example, status data 39d of the transmission / reception history data 171 extracted based on the call event 36 from non-response to response, and stores the updated transmission / reception history data 171 as a storage device. Store in 16. Then, the process moves to step S507.

  In step S507, the call reception history management device 3 determines whether to continue the call reception history data generation process. When the call origination history data generation process is continued, the process returns to step S501. If the call origination history data generation process is not continued, the process ends.

  FIG. 6 is a flowchart showing an example of call origination history data acquisition processing of the call origination / reception history management device 3 according to the first embodiment. In this FIG. 6, the case where call origination history data 171 and 17m are acquired to identification data 37 is explained as an example.

  In step S601, the receiving unit 12 receives the identification data 37 from the user terminal 4.

  In step S602, the number acquisition unit 13 converts, for example, the identification data 37 into the reference telephone number 37a based on the management data 43, and the number data 9 stored in the storage device 7 or the storage device 16 of the exchange 2. To get

In step S603, the number acquisition unit 13 acquires the telephone number 38, the telephone number 38a, and the shared telephone numbers 38b and 38c as one or more registered telephone numbers related to the reference telephone number 37a from the number data 9. In step S604, the history acquisition unit 13 acquires one or more acquired telephone numbers 38, telephone numbers 38a, and shared telephone numbers 38b and 38c from the transmission / reception history data 171 to 17m stored in the storage device 16. For example, the transmission / reception history data 171 including the acquired telephone number 38a and the transmission / reception history data 17m including the acquired shared telephone number 38c are acquired. In addition, when extracting transmission / reception history data from the transmission / reception history data 171 to 17m, conditions such as type data, status data, time data may be added to extract data satisfying the conditions.

  In step S605, the transmission unit 15 transmits the call origination / reception history data 171, 17m acquired by the history acquisition unit 13 to the user terminal 4. In addition, when transmitting call origination / reception history data 171 and 17m, data satisfying a condition for permitting transmission may be transmitted based on type data, status data, time data, and the like.

  FIG. 7 is a diagram showing an example of the display screen 41 of the display device 32 of the user terminal 4 according to the first embodiment.

  The transmission unit 18 of the user terminal 4 transmits the identification data 37 to the call origination / reception history management device 3 in accordance with the user's operation on the operation device 31.

  The reception unit 19 of the user terminal 4 receives screen data including the transmission and reception history data 171 and 17m corresponding to the identification data 37 and the registration button 42 for the unregistered telephone number from the transmission and reception history management apparatus 3.

  The display control unit 20 causes the display device 32 to display a screen 41 indicating a call origination / reception history associated with the user based on the received screen data. The screen 41 includes a date and time, a sender, a callee, a name, an affiliation such as a company name or a department name, and a registration button 42. Thus, the screen displaying the history and the registration button 42 may be the same.

  Here, it is assumed that the user operates the operation device 31 and designates the displayed registration button 42. Then, the user terminal 4 transmits a registration instruction to the registration unit 24 of the transmission / reception history management device 3. The registration unit 24 of the call origination / reception history management device 3 receives the registration instruction, and registers, in the telephone number management data 22, the transmission telephone number or the reception telephone number for which the registration instruction has been made.

  The features of the call system 1 described above will be specifically described.

  In the call system 1, the call origination / reception history management device 3 is connected to the exchange 2 in compliance with an API or the like, and is set up to be able to receive a call event 36. Data transfer from the exchange 2 to the call reception history management apparatus 3 can be realized according to various protocols such as FTP (File Transfer Protocol), HTTP (Hypertext Transfer Protocol), and a protocol dedicated to the exchange 2, for example. For example, the call origination / reception history management device 3 may be always connected to the exchange 2, and the exchange 2 may secure the connection with the call origination history management device 3 when an event occurs.

  In the first embodiment, when an incoming call, outgoing call, or response event occurs to each of the telephones T1 to Tn subordinate to the exchange 2, the exchange 2 issues a call event 36 related to call origination, call reception, or response (or connection). , Outgoing call, incoming call, and response based processing in parallel. A call event 36 for answering is issued when the other party's telephone (answering telephone) answers the incoming or outgoing call. The call event 36 issued from the exchange 2 to the originating / receiving history management device 3 includes an originating telephone number 36a, an incoming telephone number 36b, and an event type 36c. The event type 36 c indicates, for example, either a sending event, a receiving event, or a response event. The event type 36 c may have other types. The representation method of the event type 36 c of the call event 36 and the notification method of the call event 36 can be appropriately changed according to the type of the exchange 2.

  The call origination / receipt history management device 3 obtains and discriminates the calling telephone number 36a, the incoming telephone number 36b, and the event type 36c from the call event, and generates call origination / receipt history data 171 in a form that can be expressed on the system. Remember to Specifically, when the event type 36c of the call event indicates an incoming or outgoing event, the outgoing / incoming call history management device 3 generates and stores outgoing / incoming call history data 171, and the event type 36c of the call event is a response event State data 39d of the transmission / reception history data 171 stored in the storage device 16 is updated.

  The user terminal 4 transmits the history request command, the designation of the type data to be acquired, the designation of the state data to be acquired, and the identification data 37 to the transmission / reception history management device 3 according to the user's instruction accepted by the operation device 31.

  The call origination / reception history management device 3 receives from the user terminal 4 a history request command, designation of type data to be acquired, designation of state data to be acquired, identification data 37, and identification data 37 from number data 9. Get the registered phone number of. Further, the call origination / receipt history management device 3 acquires call origination / receipt history data 141, 14m including any of the acquired one or more registered telephone numbers, and transmits the acquired call origination / receipt history data 141, 14m to the user terminal 4. Send. The transmission / reception history management device 3 is designated when acquiring transmission / reception history data from the acquired one or more registered telephone numbers, or when transmitting the acquired transmission / reception history data to the user terminal 4. The screening may be performed based on the type data and the designated state data, and only transmission / reception history data satisfying the designated condition may be acquired or transmitted.

  The user terminal 4 receives the call reception history data 141 and 14 m from the call reception history management device 3, and displays the call history data 141 and 14 m on the display device 32. When there is a telephone number not included in the telephone number management data 22 managed by the transmission / reception history management device 3 among the transmission / reception history data 141, 14m transmitted to the user terminal 4, the transmission / reception history management device 3 The screen data is generated so that the registration button 42 is included in the screen 41 displayed by the user terminal 4. When the user operates the operation device 31 of the user terminal 4 and designates the registration button 42, the user terminal 4 transmits a registration instruction to the call origination / reception history management apparatus 3 and the registration unit 24 of the call origination / reception history management apparatus 3 , A telephone number not included in the telephone number management data 22 is registered in the telephone number management data 22.

  In the following, generation of call origination / reception history data 171 relating to call origination or call reception will be described.

  When the event type 36c receives a call reception event or a call event 36 indicating a call reception event from the exchange 2, the call reception history management device 3 makes a call origination number 39a, a call reception phone number 39b, type data 39c indicating call origination or call reception, The transmission and reception history data 171 including the time data 39e is stored in the storage device 16. When the call event 36 does not include the event occurrence time data 36 d, the system time possessed by the call origination / reception history management device 3 may be set as the time data 39 e.

  The call event 36 having the event type 36c indicating the originating event or the incoming event is immediately notified to the originating and receiving history management apparatus 3 when the originating event or the incoming event occurs in the exchange 2. At this point in time, it is not always the case that the other party's telephone is responding, so the state data 39e of the call origination / receipt history data 171 generated in response to the call event 36 is initialized with no response.

  In the case of an outgoing call from an extension telephone to an outside line, the incoming telephone number 36b of the call event 36 includes the prefix "0" indicating that it is an outgoing call to the outside line at the head portion in the form of 0-03-XXXX-YYYY. Therefore, the transmission / reception history management device 3 may delete the prefix from the incoming call number 36 b of the call event 36 to generate the incoming call number 39 b of the transmission / reception history data 171.

  Conversely, in the case of an incoming call from an outside line to an extension, the originating telephone number 36a of the call event 36 includes the prefix “0” indicating that the incoming call is from an outside line at the beginning. Therefore, the transmission / reception history management device 3 may delete the prefix from the transmission telephone number 36 a of the call event 36 to generate the transmission telephone number 39 a of the transmission / reception history data 171.

  When the outgoing telephone number 36a of the call event 36 related to the incoming call is null information, the outgoing / incoming call history data 171 is treated as a non-incoming call, and for example, the outgoing telephone number 39a of the outgoing / incoming call history data 171 may be null information.

  Below, the update of the transmission / reception history data 171 regarding a response is demonstrated.

  Call history management when the other party's telephone responds to an outgoing call from an extension telephone to an extension or extension, or when an extension telephone answers an incoming call to an incoming call from an extension or extension to an extension telephone The device 3 receives from the exchange 2 a call event 36 having an event type 36 c indicating a response event.

  Then, based on the outgoing call number 36a and the incoming call number 36b of the call event 36, the incoming / outgoing call history management device 3 makes an incoming / outgoing call corresponding to the call event 36 among the outgoing / incoming call history data 171 to 17m of the storage device 16. The history data 171 is searched. Specifically, the outgoing / incoming call history management device 3 has outgoing call number 39a and incoming call number 39b that match the outgoing call number 36a and incoming call number 36b of the call event 36, and outgoing / incoming call with unanswered status data 39d The history data 171 is acquired.

  Then, the transmission / reception history management device 3 updates the status data 39 d of the acquired transmission / reception history data 171 to a response, and stores the updated transmission / reception history data 171 in the storage device 16.

  Other conditions such as having call identification data and time data 39e within a predetermined period from the most recent time may be added to the search conditions of the call origination / receipt history data 171.

  This enables the user to confirm that the incoming call and outgoing call have been answered. When the call event 36 having the event type 36c indicating the response event is not issued, the state data 39d of the corresponding call origination / reception history data 171 is maintained as unanswered.

  The association between various data will be described below.

  The user terminal 4 communicably connected to the incoming and outgoing call history management device 3 can browse outgoing and incoming call history data. The user terminal 4 has, for example, identification data 37 indicating an attribute of the user or an extension assigned to the user. Here, it is assumed that the extension number of the user used as the identification data 37 is 2000. This extension number 2000 is assumed to be a telephone-specific extension number used by the user. If the identification data 37 is not a telephone number, the identification data 37 may be converted to the telephone number 2000 using the management data 43.

  In the number data 9, it is assumed that the extension number 2000, the first shared telephone number 3000, the second shared telephone number 3001, and the third shared telephone number 3002 are associated.

  The registered telephone number associated with the extension number 2000 in the number data 9 may not be a shared telephone number, but may be another type of telephone number such as a virtual extension. The number of registered telephone numbers associated with the extension number 2000 in the number data 9 can be freely changed, and there is no need to set an upper limit.

  The call origination / reception history management device 3 may acquire the number data 9 from the exchange 2 using the API, or when the number data 9 can not be acquired from the exchange 2, the storage device 16 to which the call origination / reception history management device 3 can access. It may be obtained from

  When the history of incoming calls is acquired, the incoming call history management device 3 acquires outgoing / incoming history data in which the type data indicates incoming and the incoming telephone number indicates 2000, 3000, 3001, or 3002.

  On the other hand, when acquiring the history of origination, the origination / reception history management device 3 acquires origination / reception history data in which the type data indicates origination and the origination telephone number indicates 2000, 3000, 3001 or 3002.

  In the above example, the extension number 2000 capable of specifying the telephone set used by the user is used as the identification data 37. However, depending on the type of the exchange 2, a telephone terminal name may be used as the identification data 37. In this case, the user terminal 4 may be specified by the extension number 2000 and the telephone terminal name, and one or more registered telephone numbers associated with the user terminal 4 may be acquired.

  The effects achieved by the call system 1 according to the first embodiment described above will be described.

  In the first embodiment, it is possible to store and display more transmission / reception history data 171 to 17m as compared to the case where transmission / reception history data is stored for each telephone. Therefore, the user can check necessary call history data even if the number of calls is increased.

  In the first embodiment, even when an incoming / outgoing call occurs relating to a shared telephone number assigned to a plurality of users, the incoming / outgoing call history data 171 to 17m are stored, and the necessary incoming / outgoing call history data is stored. Can be displayed. Therefore, when the shared telephone number is used as, for example, a representative telephone number, the user can confirm the call origination / reception history data related to this representative telephone number, and the convenience of the user in the call system 1 can be improved. it can.

  In the first embodiment, from identification data 37 such as, for example, an extension number, it is possible to display call origination / reception history data on one or more registered telephone numbers. Therefore, the user can view the call history data related to all one or more telephones he / she uses via the network without directly operating the telephone corresponding to the extension number assigned to the user. is there. Therefore, the user can view the call reception history data via the call reception history management device 3 even from outside, for example, and can improve the convenience of the user who uses the call system 1 in business, for example.

  In the first embodiment, it is possible to display call origination / reception history data within a designated type, a designated state, a designated period from the latest, or within a predetermined period.

  In the first embodiment, the transmission / reception history management device 3 searches for transmission / reception history data 171, 17m related to the user. The retrieved incoming and outgoing call history data 171, 17m includes the telephone number of the other party as the originating telephone number or the incoming telephone number. The call origination history management apparatus 3 can search the telephone number management data 22 used in the telephone directory function by the telephone number of the other party, extract the name of the other party, and notify the user terminal 4 of the name. Further, when the telephone number of the other party sent to the user terminal 4 is not included in the telephone number management data 22, the originating and receiving history management device 3 determines the telephone number and the name of the other party based on the registration instruction from the user. Etc. can be registered in the telephone number management data 22.

Second Embodiment
In the second embodiment, a case will be described where a plurality of exchange switches share a call origination / reception history management device.

  FIG. 8 is a block diagram showing an example of the configuration of a call system 1A according to the second embodiment.

  The call system 1A includes a plurality of switches 2A to 2X.

  Each of the plurality of exchanges 2A to 2X issues a call event to the transmission / reception history management apparatus 3 when a call is received or sent.

  As described in the first embodiment, the call reception history management apparatus 3 generates call reception history data 171 to 17 m according to the received call event, and stores the call reception data in the storage device 16.

  Even when the user operating the user terminal 4 is in an environment where he / she uses a plurality of exchanges 2A to 2X, or when various telephone numbers are used in various telephones, it is sufficient It is possible to check the amount of incoming and outgoing call history data, and to improve the convenience of the user.

  The present invention is not limited to the above embodiment as it is, and at the implementation stage, the constituent elements can be modified and embodied without departing from the scope of the invention. Further, various inventions can be formed by appropriate combinations of a plurality of constituent elements disclosed in the above embodiment. For example, some components may be reduced from all the components shown in the embodiment. Furthermore, components in different embodiments may be combined as appropriate.

  1, 1A: call system, 2, 2, 2A, 2X: exchange, 3 .: call origination record management device, 4: user terminal, T0 to Tn: telephone set, 5: connection unit, 6: event issuing unit, 7, 16, 21 ... storage device, 8 ... API control unit, 9 ... number data, 10, 12, 19 ... reception unit, 11 ... history management unit, 13 ... number acquisition unit, 14 ... history acquisition unit, 15, 18 ... transmission unit, 171 ~ 17m ... call origination history data, 20 ... display control unit, 22 ... telephone number management data, 23 ... inquiry unit, 24 ... registration unit, 36 ... call event, 36a, 39a, 40a ... outgoing telephone number, 36b, 39b, 40b: Incoming telephone number 36c: Event type 36d: Event occurrence time data 37: Identification data 37a: Telephone number for reference 38, 38a: Telephone number 38b, 38c: Shared telephone number 39c, 0c ... type data, 39d, 40d ... state data, 39e, 40e ... time data, 27,30,35 ... program, 43 ... management data.

Claims (6)

A first receiving unit for receiving the call event from a switch which issues a call event including a calling telephone number and a called telephone number at least when receiving a call from a calling telephone or when making a call to a called telephone;
A history management unit for storing, in a first storage device, history data in which the originating telephone number included in the call event and the incoming telephone number are associated with each other;
A second receiving unit for receiving identification data from the user terminal;
A first acquisition unit that acquires one or more telephone numbers associated with the identification data by referring to number data stored in the second storage device and associating a plurality of telephone numbers with each other;
A second acquisition unit for acquiring the history data including the originating telephone number or the incoming telephone number associated with the acquired one or more telephone numbers from the first storage device;
A transmitter configured to transmit the acquired history data to the user terminal;
An incoming and outgoing call history management device equipped with The first acquisition unit refers to management data stored in a third storage device and associating the identification data with a reference telephone number, and converts the identification data into the reference telephone number. Obtaining the one or more telephone numbers associated with the reference telephone number from the number data;
The call origination / reception history management apparatus according to claim 1. The call event includes event type data, the outgoing telephone number, and the incoming telephone number.
The event type data includes a first event indicating that the switch has arrived, a second event indicating that the switch has originated, and a call received by the receiving telephone from the originating telephone via the switch. Indicates any of the third events that indicate a response
The history data associates the originating telephone number, the incoming telephone number, and type data indicating whether the first event or the second event is associated,
The history management unit is configured such that, when the event type data of the call event indicates the third event, the call reception telephone has responded to the history data stored in the first storage device. Updating the history data stored in the first storage device to include state data indicating
The call origination / reception history management apparatus according to claim 1 or 2.   The at least one of the plurality of telephone numbers included in the number data is a shared telephone number shared by a plurality of telephones including the incoming call telephone. The call origination / reception history management device of paragraph. A fourth storage device for storing telephone number management data;
When the originating telephone number or the incoming telephone number included in the acquired history data is not included in the telephone number management data, the originating telephone number or the telephone number not included in the telephone number management data An inquiry unit for inquiring the user terminal whether or not to register an incoming call number in the telephone number management data;
A registration unit which registers the originating telephone number or the incoming telephone number not included in the telephone number management data in the telephone number management data when receiving a registration instruction from the user terminal;
Further equipped,
The call origination / reception history management apparatus according to any one of claims 1 to 4. On the computer
A first reception function of receiving the call event from a switch which issues a call event including a calling telephone number and a called telephone number at least when receiving an incoming call from a calling telephone or making a call to a called telephone;
A history management function of storing, in a first storage device, history data in which the originating telephone number included in the call event and the incoming telephone number are associated with each other;
A second receiving function for receiving identification data from the user terminal;
A first acquisition function of acquiring one or more telephone numbers associated with the identification data by referring to number data stored in the second storage device and associating a plurality of telephone numbers;
A second acquisition function of acquiring the history data including the originating telephone number or the incoming telephone number associated with the acquired one or more telephone numbers from the first storage device;
A transmission function of transmitting the acquired history data to the user terminal;
Program for realizing

Images