Main device, program, and notification method of communication history

Abstract

To provide a technology for sharing communication history between a plurality of portable terminals and a main device housing the portable terminals while suppressing battery consumption of the portable terminals.SOLUTION: A main device 1 transmits to a push notification server 2 a push notification request including designation of a portable terminal 3 and communication history held by itself when any one of conditions of arrival of a prescribed period at each of the portable terminals 3 to house, passage of a prescribed time from previous transmission of the communication history to the portable terminals 3, and accumulation of a prescribed numbers of new communication history by the main device 1 is satisfied. Thus, the push notification server 2 is caused to transmit push notification including the communication history included in the push notification request to the portable terminal 3 designated by the push notification request. When the portable terminal 3 receives the push notification from the push notification server 2, it cancels the same in the case where the terminal itself is in a standby state, and updates the communication history held by the terminal itself on the basis of the communication history included in the push notification.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a main unit that houses a mobile terminal, and more particularly to a technique for notifying a mobile terminal of a communication history from the main unit. [Background technology]

[0002] There is known a technology for sharing communication history such as outgoing calls, incoming calls, responses, and end calls between multiple telephones and the main units that accommodate these telephones. For example, Patent Document 1 discloses a telephone system in which response information for an incoming call is shared between multiple telephones that have received a group call.

[0003] Recently, telephone systems using mobile terminals such as smartphones have become known (see, for example, Patent Document 2). Generally, in this type of telephone system, the mobile terminal activates a call app, which is a dedicated application program, to enable the telephone function, thereby enjoying the telephone services provided by the main unit. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Publication No. 2018-148414 [Patent Document 2] Japanese Patent Application Laid-Open No. 2008-187224 Summary of the Invention [Problem to be solved by the invention]

[0005] In a telephone system using mobile terminals, the main unit can use push notification services such as Apple's Apple Push Notification service (APNs) or Google's Google Cloud Messaging (GCM) to wake up the mobile terminal that it accommodates and share communication history with the calling app, even if the mobile terminal is in standby mode.

[0006] However, when using a push notification service to share communication history between multiple mobile devices and the main unit that houses these mobile devices, if the communication history of the call app is updated on all mobile devices each time a call control operation such as making, receiving, answering, or ending a call is performed, there is a possibility that even mobile devices in standby mode that are not involved in these call controls will consume battery power due to frequent standby mode cancellation.

[0007] The present invention has been made in consideration of the above circumstances, and aims to provide a technology for sharing communication history between multiple mobile terminals and a main unit that accommodates these mobile terminals while reducing battery consumption in the mobile terminals. [Means for solving the problem]

[0008] To solve the above problem, the main device of the present invention sends a push notification request to a push notification server, triggered by one of the following conditions: a predetermined period has elapsed for each of a plurality of mobile terminals accommodated therein, a predetermined time has elapsed since the previous transmission of a communication history to the mobile terminal, or a predetermined number of new communication history entries have been accumulated in the main device, and causes the push notification server to send a push notification including the communication history included in the push notification request to the mobile terminal specified in the push notification request. Meanwhile, when the mobile terminal receives a push notification from the push notification server, it cancels standby mode if it is in standby mode and updates its own communication history based on the communication history included in the push notification.

[0009] For example, the present invention provides A main device that accommodates a plurality of mobile terminals via a network, a communication history storage means for storing a communication history including outgoing and incoming calls; The communication history storage means has a push notification request means for sending a push notification request to a push notification server, the push notification request including a designation of the mobile terminal and the communication history stored in the communication history storage means, when one of the following events occurs: a predetermined period has arrived, a predetermined time has elapsed since the last transmission of the communication history to the mobile terminal, or a predetermined number of new communication history items have been accumulated in the communication history storage means. [Effects of the Invention]

[0010] In the present invention, the main device transmits a push notification request to a push notification server for each of a plurality of mobile devices it accommodates, including a designated mobile device and its own communication history, when one of the following conditions is met: a predetermined period has elapsed, a predetermined time has elapsed since the last communication history transmission to the mobile device, or a predetermined number of new communication history entries have been accumulated by the main device. This causes the push notification server to transmit a push notification including the communication history included in the push notification request to the mobile device designated in the push notification request. Therefore, according to the present invention, by appropriately setting the predetermined period, the predetermined time, and the predetermined number of entries, the frequency with which the mobile devices are released from standby mode can be reduced compared to updating the communication history of all mobile devices each time a call is made, received, answered, or ended, thereby suppressing battery consumption of the mobile devices. This allows communication history to be shared between a plurality of mobile devices and the main device accommodating these mobile devices while suppressing battery consumption of the mobile devices. [Brief explanation of the drawings]

[0011] [Figure 1] FIG. 1 is a schematic diagram of a telephone system according to an embodiment of the present invention. [Figure 2] FIG. 2 is a sequence diagram for explaining an example of a communication history sharing operation in a telephone system according to an embodiment of the present invention. [Figure 3]FIG. 3 is a sequence diagram illustrating an example of a communication history sharing operation in a telephone system according to an embodiment of the present invention, and is a continuation of FIG. [Figure 4] FIG. 4 is a schematic functional configuration diagram of the main device 1. As shown in FIG. [Figure 5] FIG. 5 is a flowchart for explaining the communication history transmission operation of main unit 1. In FIG. [Figure 6] FIG. 6 is a flow diagram for explaining the operation of the main unit 1 for monitoring the difference in communication histories. [Figure 7] FIG. 7 is a flow chart for explaining the condition adjustment operation of main device 1. As shown in FIG. [Figure 8] FIG. 8 is a diagram showing a schematic functional configuration of the mobile terminal 3. As shown in FIG. [Figure 9] FIG. 9 is a flow diagram for explaining the communication history update operation of the mobile terminal 3. In FIG. DETAILED DESCRIPTION OF THE INVENTION

[0012] An embodiment of the present invention will be described below.

[0013] FIG. 1 is a schematic diagram of a telephone system according to the present embodiment.

[0014] As shown in the figure, the telephone system of this embodiment includes a main device 1 and a push notification server 2 connected to a network 4 such as a WAN (Wide Area Network) or a LAN (Local Area Network), and a plurality of mobile terminals 3-1 to 3-3 (hereinafter simply referred to as mobile terminals 3) connected to the network 4 via a base station 5.

[0015] The main unit 1 accommodates a plurality of mobile terminals 3-1 to 3-3 as extension telephones, and provides these mobile terminals 3 with an extension telephone service.

[0016] In response to the push notification request received from the main unit 1, the push notification server 2 transmits a push notification to the mobile terminal 3 specified in the push notification request. If the push notification request received from the main unit 1 includes a communication history including outgoing and incoming calls, the push notification server 2 transmits the push notification to the mobile terminal 3 together with the communication history.

[0017] In response to the push notification received from the push notification server 2, the mobile terminal 3 launches its own call app and receives extension telephone service from the main unit 1. If the mobile terminal 3 is in a standby state, the mobile terminal 3 cancels this standby state before launching the call app. If the push notification received from the push notification server 2 includes a communication history, the mobile terminal 3 updates its own communication history based on this communication history.

[0018] 2 and 3 are sequence diagrams for explaining an example of a communication history sharing operation in the telephone system according to the present embodiment.

[0019] Here, it is assumed that the mobile terminals 3-1 and 3-2 are in a standby state and have not exchanged call control messages with the main unit 1 for a predetermined period of time or longer, which has resulted in a difference between the communication history held by the terminals 3-1 and 3-2 themselves and the communication history held by the main unit 1. It is also assumed that the mobile terminal 3-3 is in an active state and is exchanging the latest call control messages with the main unit 1, which has resulted in the communication history held by the terminal 3-3 itself and the communication history held by the main unit 1 being synchronized (matched).

[0020] The main device 1 monitors whether any of the following conditions (communication trigger occurrence conditions) 1 to 3, which serve as triggers for executing synchronization of communication histories, is met for each mobile terminal 3 (S100).

[0021] [Communication trigger occurrence conditions] Condition 1: A predetermined period has arrived. Condition 2: A predetermined time has elapsed since the previous transmission of the communication history to the mobile terminal 3. Condition 3: A predetermined number of new communication histories have been accumulated in the main unit 1.

[0022] Here, it is assumed that the mobile terminal 3-1 satisfies any one of the above-described communication trigger occurrence conditions 1 to 3, and a trigger to synchronize the communication history occurs for this mobile terminal 3-1 (S101). When the main unit 1 confirms that a difference flag indicating that a difference has occurred between the communication history held by the main unit 1 itself and the communication history held by the mobile terminal 3-1 has been set (difference flag "present") (S102), the main unit 1 transmits a push notification request including a designation of the mobile terminal 3-1 and the communication history held by the main unit 1 itself to the push notification server 2 (S103).

[0023] In response to this, the push notification server 2 transmits a push notification including the communication history included in the push notification request to the mobile terminal 3-1 specified in the push notification request received from the main device 1 (S104).

[0024] Then, when the mobile terminal 3-1 receives the push notification from the push notification server 2, it cancels the standby state of the mobile terminal 3-1 and transitions to an active state (S105), and activates the call application of the mobile terminal 3-1 (S106). The activated call application updates its own communication history based on the communication history included in the push notification received from the push notification server 2 (S107). Thereafter, the mobile terminal 3-1 transmits a communication history update completion notification to the main unit 1 (S108).

[0025] When the main device 1 receives the communication history update completion notification from the mobile terminal 3-1, it clears the difference flag indicating that a difference has occurred between the communication history held by the main device 1 itself and the communication history held by the mobile terminal 3-1 (S109).

[0026] Thereafter, it is assumed that the mobile terminal 3-2 satisfies any one of the above-described communication trigger occurrence conditions 1 to 3, and a trigger for executing synchronization of the communication history for the mobile terminal 3-2 is generated (S110). When the main device 1 confirms that a difference flag indicating that a difference has occurred between the communication history held by the main device 1 and the communication history held by the mobile terminal 3-2 is set (difference flag "present") (S111), the main device 1 transmits a push notification request including a designation of the mobile terminal 3-2 and the communication history held by the main device 1 to the push notification server 2 (S112).

[0027] In response to this, the push notification server 2 transmits a push notification including the communication history included in the push notification request to the mobile terminal 3-2 specified in the push notification request received from the main device 1 (S113).

[0028] Then, when the mobile terminal 3-2 receives the push notification from the push notification server 2, it cancels the standby state of the mobile terminal 3-2 and transitions to an active state (S114), and activates the call application of the mobile terminal 3-2 (S115). The activated call application updates its own communication history based on the communication history included in the push notification received from the push notification server 2 (S116). Thereafter, the mobile terminal 3-2 transmits a communication history update completion notification to the main unit 1 (S117).

[0029] When the main device 1 receives a communication history update completion notification from the mobile terminal 3-2, it clears a difference flag indicating that a difference has occurred between the communication history held by the main device 1 and the communication history held by the mobile terminal 3-2 (S118).

[0030] Thereafter, it is assumed that the mobile terminal 3-3 satisfies any one of the above-described communication trigger occurrence conditions 1 to 3, and a trigger to synchronize the communication history is generated for the mobile terminal 3-3 (S119). The main unit 1 confirms that a difference flag indicating that a difference has occurred between the communication history held by the main unit 1 itself and the communication history held by the mobile terminal 3-3 is not set (difference flag "none") (S120). In this case, the main unit 1 does not send a push notification request including a designation of the mobile terminal 3-3 and the communication history held by the main unit 1 itself to the push notification server 2. Therefore, the mobile terminal 3-3 does not update the communication history based on the push notification.

[0031] Next, details of the main device 1 and the mobile terminal 3 that constitute the telephone system according to this embodiment will be described. Note that, since an existing push notification server can be used as the push notification server 2, detailed description thereof will be omitted.

[0032] First, the main unit 1 will be described in detail.

[0033] FIG. 4 is a schematic functional configuration diagram of the main device 1. As shown in FIG.

[0034] As shown in the figure, the main unit 1 has a network interface unit 10, a call control unit 11, an exchange processing unit 12, a communication history memory unit 13, a difference monitoring unit 14, a communication trigger monitoring unit 15, a push notification request unit 16, a network load measurement unit 17, and a condition adjustment unit 18.

[0035] The network interface unit 10 is an interface for connecting to the network 4 .

[0036] The call control unit 11 establishes and releases a call path between the mobile terminal 3 and the other party in accordance with a call control protocol such as SIP (Session Initiation Protocol).

[0037] The exchange processing unit 12 relays calls between the mobile terminal 3 and the other party via the call path established by the call control unit 11.

[0038] The communication history storage unit 13 stores the communication history of call control messages such as outgoing calls, incoming calls, responses, and end calls exchanged with the mobile terminal 3 by the call control unit 11 as history information including outgoing and incoming calls.

[0039] The difference monitoring unit 14 monitors, for each mobile terminal 3, whether or not a difference has occurred between the communication history held by the mobile terminal 3 and the communication history stored in the communication history storage unit 13, and when it is determined that a difference has occurred, it sets a difference flag if a difference flag has not been set for this mobile terminal 3. When it is determined that no difference has occurred, if a difference flag has been set for this mobile terminal 3, it clears the difference flag.

[0040] Specifically, for each mobile terminal 3, when a call control message is exchanged with another mobile terminal 3 other than this mobile terminal 3, or when there is no response from this mobile terminal 3 to a call control message sent to this mobile terminal 3, the difference monitoring unit 14 determines that a difference has occurred between the communication history held by this mobile terminal 3 and the communication history stored in the communication history storage unit 13. Furthermore, when the difference monitoring unit 14 receives a communication history update completion notification from the mobile terminal 3, it determines that the difference between the communication history held by this mobile terminal 3 and the communication history stored in the communication history storage unit 13 has been resolved.

[0041] The communication trigger monitoring unit 15 monitors for each mobile terminal 3 whether any of the above-mentioned communication trigger occurrence conditions 1 to 3, which serve as a trigger for executing synchronization of communication histories (hereinafter, communication trigger), is met.

[0042] The push notification request unit 16, in accordance with an instruction from the call control unit 11, sends a push notification request including the designation of the mobile terminal 3 to the push notification server 2. Furthermore, if a difference flag is set for the mobile terminal 3 for which the communication trigger monitoring unit 15 has detected the occurrence of a communication trigger, the push notification request unit 16 sends a push notification request including the designation of this mobile terminal 3 and the communication history stored in the communication history storage unit 13 to the push notification server 2.

[0043] The network load measuring unit 17 measures the load status (network usage rate) of the network 4.

[0044] The condition adjustment unit 18 adjusts the communication trigger generating conditions 1 to 3 used by the communication trigger monitoring unit 15 based on the load status of the network 4 measured by the network load measurement unit 17. For example, the parameter values ​​(predetermined cycle, predetermined time, and predetermined number) of the above-mentioned communication trigger generating conditions 1 to 3 are increased or decreased according to an increase or decrease in the load of the network 4. This reduces the frequency of sending push notification requests and prevents an increase in network traffic.

[0045] The functional configuration of main device 1 shown in Fig. 4 may be realized in hardware using an integrated logic IC such as an ASIC (Application Specific Integrated Circuit) or FPGA (Field Programmable Gate Array), or in software using a computer such as a DSP (Digital Signal Processor). Alternatively, it may be realized as a process in a general-purpose computer such as a PC (Personal Computer) equipped with a CPU (Central Processing Unit), memory, an auxiliary storage device such as an SSD (Solid State Drive) or HDD (Hard Disk Drive), and a communication device such as a NIC (Network Interface Card), by the CPU loading a predetermined program from the auxiliary storage device into memory and executing it.

[0046] FIG. 5 is a flowchart for explaining the communication history transmission operation of main unit 1. In FIG.

[0047] First, the communication trigger monitoring unit 15 starts monitoring, for each mobile terminal 3, whether or not the mobile terminal 3 satisfies any of the above-described communication trigger generating conditions 1 to 3 (S200).

[0048] Then, when any of the mobile terminals 3 meets at least one of the above-mentioned communication trigger occurrence conditions 1 to 3 and a trigger (communication trigger) to execute synchronization of communication history occurs for this mobile terminal 3 (YES in S201), the difference monitoring unit 14 determines whether a difference flag is set for this mobile terminal 3 (S202).

[0049] If the difference flag is not set for this mobile terminal 3 (NO in S202), the process returns to S201 and waits for a new communication trigger to occur for any of the mobile terminals 3.

[0050] On the other hand, if a difference flag is set for this mobile terminal 3 (YES in S202), the communication trigger monitoring unit 15 notifies the push notification requesting unit 16 of the communication history stored in the communication history storage unit 13 together with the designation of this mobile terminal 3. In response to this, the push notification requesting unit 16 transmits a push notification request including the designation of this mobile terminal 3 and the communication history stored in the communication history storage unit 13 to the push notification server 2 via the network interface unit 10 (S203). Thereafter, the process returns to S201, and waits for a new communication trigger to occur for any of the mobile terminals 3.

[0051] FIG. 6 is a flow diagram for explaining the operation of the main unit 1 for monitoring the difference in communication histories.

[0052] First, the difference monitor 14 starts monitoring updates to the communication history stored in the communication history storage 13 (S210).

[0053] Then, when the communication history is updated (YES in S211), the communication partner terminal (portable terminal 3) specified by the newly added communication history is identified (S212), and a difference flag is set for the mobile terminals 3 other than the partner terminal (S213). Then, the difference monitoring unit 14 refers to this newly added communication history and determines whether or not the transmission and reception of the call control message with the partner terminal was successful (S214). Specifically, if a response is received from the partner terminal in response to the call control message sent to the partner terminal, it is determined that the transmission and reception of the call control message was successful; if a response is not received, it is determined that the transmission and reception of the call control message with the partner terminal was unsuccessful. Then, if it is determined that the transmission and reception of the call control message with the partner terminal was unsuccessful (NO in S214), a difference flag is also set for the partner terminal (S215).

[0054] Furthermore, when the difference monitor 14 receives a communication history update completion notification from the mobile terminal 3 via the network interface 10 (YES in S216), it clears the difference flag set in this mobile terminal 3 (S217).

[0055] FIG. 7 is a flow chart for explaining the condition adjustment operation of main device 1. As shown in FIG.

[0056] When the periodic load status measurement timing arrives (YES in S220), the condition adjustment unit 18 instructs the network load measurement unit 17 to measure the load status of the network 4. In response to this, the network load measurement unit 17 measures the load status of the network 4 (S221) and notifies the condition adjustment unit 18 of the measurement result.

[0057] Next, the condition adjustment unit 18 adjusts the parameter values ​​of the above-mentioned communication trigger generating conditions 1 to 3 according to the measurement results of the load state of the network 4 notified by the network load measurement unit 17 (S222). For example, as the load state of the network 4 increases, the predetermined period, which is a parameter of the communication trigger generating condition 1, the predetermined time, which is a parameter of the communication trigger generating condition 2, and the predetermined number, which is a parameter of the communication trigger generating condition 3, are increased.

[0058] Next, the mobile terminal 3 will be described in detail.

[0059] FIG. 8 is a diagram showing a schematic functional configuration of the mobile terminal 3. As shown in FIG.

[0060] As shown in the figure, the mobile terminal 3 has a wireless interface unit 30, a man-machine interface unit 31, a call control unit 32, a call processing unit 33, a communication history acquisition unit 34, a communication history storage unit 35, and a communication history update completion notification unit 36.

[0061] The wireless interface unit 30 is an interface for connecting to the network 4 via the base station 5 .

[0062] The man-machine interface unit 31 is an interface that allows the user to make phone calls and perform various operations, and although not shown, it includes, for example, a microphone, a speaker, a camera, and a touch panel display that also serves as an operation unit such as a dial keypad.

[0063] The call control unit 32 cooperates with the main unit 1 to establish and release a call path with the other party in accordance with a call control protocol such as SIP.

[0064] The call processing unit 33 transmits and receives call data to and from the other party via the call path established by the call control unit 32 in accordance with a transmission protocol such as RTP (Realtime Transport Protocol). Specifically, it encodes a voice signal input by the user via the man-machine interface unit 31 into call data and transmits this call data to the other party via the call path, and also receives call data from the other party via the call path, decodes this call data into a voice signal, and outputs it from the man-machine interface unit 31.

[0065] The communication history acquisition unit 34 acquires a communication history from a push notification received from the push notification server 2 via the wireless interface unit 30.

[0066] The communication history storage unit 35 stores the communication history of call control messages such as outgoing calls, incoming calls, responses, and end calls exchanged with the main unit 1 by the call control unit 32. The communication history storage unit 35 also updates the communication history stored therein based on the communication history acquired by the communication history acquisition unit 34.

[0067] The communication history update completion notification unit 36 ​​sends a communication history update completion notification to the main device 1 when the communication history stored in the communication history memory unit 35 is updated based on the communication history acquired by the communication history acquisition unit 34.

[0068] The functional configuration of the mobile terminal 3 shown in Figure 8 is realized by a general-purpose computer such as a smartphone or tablet PC that is equipped with a CPU, memory, an auxiliary storage device such as an SSD or flash memory, and a wireless communication device such as a wireless LAN adapter, in which the CPU loads a predetermined program (call application) from the auxiliary storage device into the memory and executes it.

[0069] FIG. 9 is a flow diagram for explaining the communication history update operation of the mobile terminal 3. In FIG.

[0070] This flow starts when the mobile terminal 3 accepts an operation from a user or receives a push notification from the push notification server 2, thereby terminating the standby state of the mobile terminal 3 and activating the call application.

[0071] When wireless interface unit 30 receives a push notification from push notification server 2 (YES in S300), communication history acquisition unit 34 checks whether the push notification includes a communication history (S301). If the push notification includes a communication history (YES in S301), communication history acquisition unit 34 passes the communication history to communication history storage unit 35. In response to this, communication history storage unit 35 updates the communication history stored therein based on the communication history acquired by communication history acquisition unit 34 (S302). Thereafter, communication history update completion notifying unit 36 ​​transmits a communication history update completion notification to main device 1 via wireless interface unit 30 (S303).

[0072] In addition, when communication (exchange of call control messages such as outgoing call, incoming call, answering, and ending a call) occurs via the call control unit 32 (YES in S304), the communication history storage unit 35 adds the communication history related to this communication to the communication history stored therein, and updates the communication history stored therein (S305).

[0073] One embodiment of the present invention has been described above.

[0074] In the present embodiment, the main device 1 transmits a push notification request to the push notification server 2, specifying the mobile terminal 3 and including the communication history stored therein, as a communication trigger for each of the multiple mobile terminals 3 accommodated therein (communication trigger generation condition 1), when a predetermined period has elapsed since the previous transmission of a communication history to the mobile terminal 3 (communication trigger generation condition 2), or when a predetermined number of new communication history entries have been accumulated in the communication history storage unit 13 (communication trigger generation condition 3). This causes the push notification server 2 to transmit a push notification including the communication history included in the push notification request to the mobile terminal 3 specified in the push notification request. Therefore, according to the present embodiment, by setting appropriate values ​​for the parameters of the above-mentioned communication trigger generation conditions 1 to 3 (predetermined period, predetermined time, predetermined number), the frequency at which the standby state of the mobile terminal 3 is released can be reduced compared to updating the communication history of all mobile terminals 3 each time a call is made, received, answered, or ended, and an increase in battery consumption of the mobile terminal 3 can be suppressed. This allows the communication history to be shared between the main device 1 and the plurality of mobile terminals 3 while suppressing battery consumption of the mobile terminals 3.

[0075] Furthermore, in this embodiment, the main device 1 adjusts the parameter values ​​of the above-described communication trigger generating conditions 1 to 3 according to the load status of the network 4. For example, the greater the load status of the network 4, the greater the predetermined cycle, predetermined time, and predetermined number of communication trigger generating conditions 1 to 3 are set. This reduces the transmission frequency of push notification requests and prevents an increase in network traffic. Furthermore, the mobile terminal 3 can avoid receiving push notifications when the network 4 is in a high load status, thereby smoothly receiving push notifications and suppressing an increase in battery consumption.

[0076] Furthermore, in this embodiment, main device 1 monitors, for each mobile terminal 3, whether a difference has occurred between the communication history held by mobile terminal 3 and the communication history stored in communication history storage unit 13. Then, only when any of mobile terminals 3 satisfies any of the above-described communication trigger occurrence conditions 1 to 3 and a difference has occurred between the communication history held by this mobile terminal 3 and the communication history stored in communication history storage unit 13, main device 1 transmits a push notification request to push notification server 2. This prevents main device 1 from transmitting unnecessary push notification requests that are not used to update the communication history of mobile terminal 3. Therefore, according to this embodiment, mobile terminal 3 can be prevented from receiving unnecessary push notifications that do not contribute to updating the communication history held by itself, thereby suppressing an increase in battery consumption of mobile terminal 3.

[0077] The present invention is not limited to the above-described embodiment, and various modifications are possible within the scope of the present invention.

[0078] For example, in the above embodiment, main device 1 monitors for each mobile terminal 3 whether any of the following conditions is met: when a predetermined period has arrived (communication trigger generation condition 1), when a predetermined time has elapsed since the previous transmission of a communication history to mobile terminal 3 (communication trigger generation condition 2), or when a predetermined number of new communication histories have been accumulated in communication history storage unit 13 (communication trigger generation condition 3).If any of communication trigger generation conditions 1 to 3 is met, this triggers transmission of a push notification request including a designation of mobile terminal 3 and the communication history held by the mobile terminal 3 to push notification server 2. However, the present invention is not limited to this.In addition to the above-mentioned communication trigger generation conditions 1 to 3, the following conditions 4 and 5 may also be added as communication trigger generation conditions.

[0079] [Additional conditions for communication trigger occurrence] Condition 4: A group call was made to the mobile terminal 3, but the call was disconnected because another mobile terminal 3 answered. Condition 5: Prior to sending an incoming call notification to another mobile terminal 3, a push notification request specifying this mobile terminal 3 was sent to the push notification server 2.

[0080] Furthermore, in the above embodiment, the mobile terminal 3 may be able to set, in the main device 1, one or more of the communication trigger generating conditions 1 to 5 to be applied to the mobile terminal 3 in accordance with a user instruction. Here, if there are conditions among the communication trigger generating conditions that theoretically cannot be set simultaneously, it is preferable that the mobile terminal 3 prevents the user from selecting such conditions simultaneously, for example, by graying out one of the conditions when the user selects the other.

[0081] Furthermore, in the above embodiment, the mobile terminal 3 may be configured to set, in accordance with a user's instruction, the initial values ​​of the parameters of the above-mentioned communication trigger generating conditions 1 to 3 applied to the mobile terminal 3 and the adjustment amounts (such as an adjustment ratio for increasing or decreasing the parameter values ​​in accordance with an increase or decrease in the load on the network 4) to be used in accordance with the load status of the network 4 in the main unit 1. Furthermore, whether or not to adjust the parameters of the above-mentioned communication trigger generating conditions 1 to 3 applied to the mobile terminal 3 in accordance with the load status of the network 4 may be set in the main unit 1 in accordance with a user's instruction.

[0082] Furthermore, in the above embodiment, main device 1 monitors, for each mobile terminal 3, whether a difference has occurred between the communication history held by this mobile terminal 3 and the communication history stored in communication history storage unit 13. When any mobile terminal 3 satisfies any of the above-described communication trigger occurrence conditions 1 to 3 and a difference has occurred between the communication history held by this mobile terminal 3 and the communication history stored in communication history storage unit 13, main device 1 transmits a push notification request to push notification server 2. However, the present invention is not limited to this. In accordance with a user's instruction, when mobile terminal 3 satisfies the communication trigger occurrence condition, mobile terminal 3 may cause main device 1 to transmit a push notification request including a designation of its own terminal 3 and the communication history held by main device 1, regardless of whether a difference exists between the communication history held by its own terminal 3 and the communication history held by main device 1. [Explanation of symbols]

[0083] 1: Main unit 2: Push notification server 3: Mobile terminal 4: Network 5: Base station 10: Network interface unit 11: Call control unit 12: Exchange processing unit 13: Communication history storage unit 14: Difference monitoring unit 15: Communication trigger monitoring unit 16: Push notification request unit 17: Network load measurement unit 18: Condition adjustment unit 30: Wireless interface section 31: Man-machine interface section 32: Call control unit 33: Call processing unit 34: Communication history acquisition unit 35: Communication history storage unit 36: Communication history update completion notification unit

Claims

1. A main device that accommodates a plurality of mobile terminals via a network, a communication history storage means for storing a communication history including outgoing and incoming calls; and push notification request means for transmitting, to a push notification server, a push notification request including a designation of the mobile terminal and the communication history stored in the communication history storage means, when any of the following conditions is met: a predetermined period has arrived, a predetermined time has elapsed since the previous transmission of the communication history to the mobile terminal, or a predetermined number of communication histories have been newly accumulated in the communication history storage means. A main device characterized by:

2. 2. The main device according to claim 1, a load monitoring means for monitoring the load status of the network; and a condition adjusting means for adjusting the predetermined period, the predetermined time, and the predetermined number of cases in accordance with the load status of the network monitored by the load monitoring means. A main device characterized by:

3. 3. The main device according to claim 1, The method further comprises a difference monitoring means for monitoring, for each of the mobile terminals, the occurrence of a difference between the communication history held by the mobile terminal and the communication history stored in the communication history storage means, The push notification request means For each of the mobile terminals, if any of the conditions is met and the difference monitoring means determines that a difference has occurred between the communication histories, the mobile terminal sends the push notification request to the push notification server. A main device characterized by:

4. 4. The main device according to claim 3, The difference monitoring means For each of the mobile terminals, if a call control message is exchanged with another mobile terminal other than the mobile terminal, or if there is no response from the mobile terminal to a call control message sent to the mobile terminal, it is determined that a difference has occurred between the communication histories. A main device characterized by:

5. A program that causes a computer to function as a main device that accommodates multiple mobile terminals via a network, a communication history storage means for storing a communication history including outgoing and incoming calls; When any one of the following conditions is met for each of the mobile terminals: a predetermined period has arrived, a predetermined time has elapsed since the previous transmission of the communication history to the mobile terminal, or a predetermined number of communication histories have been newly accumulated in the communication history storage means, the computer is caused to function as push notification request means that sends a push notification request to a push notification server, the push notification request including a designation of the mobile terminal and the communication history stored in the communication history storage means. A program characterized by:

6. A communication history notification method for sharing a communication history including incoming and outgoing calls between a plurality of mobile terminals and a main unit accommodating the plurality of mobile terminals, comprising: The main device is for each of the mobile terminals, when any of the following conditions is met: when a predetermined period has arrived, when a predetermined time has elapsed since the previous transmission of the communication history to the mobile terminal, or when a predetermined number of communication history items have been newly accumulated in the main device, the main device sends a push notification request including a designation of the mobile terminal and the communication history held by the mobile terminal to a push notification server, and causes the push notification server to send a push notification including the communication history included in the push notification request to the mobile terminal designated in the push notification request; The mobile terminal When the device receives the push notification from the push notification server, if the device is in standby mode, the device cancels the standby mode and updates its own communication history based on the communication history included in the push notification. A communication history notification method characterized by:

Images