JP4371838B2 - Information notification device - Google Patents

Description

  The present invention relates to an information notification apparatus, and more particularly to an information notification apparatus that notifies updated information according to a state of a notification destination.

  When certain information is updated, it may be desired to notify the information. For example, a person who buys and sells stocks wants to notify stock price information when the stock price is updated in order to obtain a good timing for buying and selling stocks. Conventionally, there is a database monitoring system as a system that provides information when the information is updated (for example, see Patent Document 1). In this database monitoring system, a plurality of information is managed and notification conditions are registered in advance for the information. When the information is updated so as to satisfy the notification condition, the information is notified to the registered user terminal. Therefore, for example, stock prices are managed as information on the server side, and notification conditions on the client side are registered. The client side can receive a notification from the server when a specific brand has a specific stock price.

  Moreover, if information indicating the presence status of a person as well as information such as a stock price is managed on the server side, for example, when a certain user is present, that fact is notified to other users. Thus, a service that other users can communicate with a certain user is also possible. In such an information notification system that handles the presence status of a person, when a user sets up a user list called a buddy list, the status of a user registered in the buddy list, for example, the “connection status” to the Internet, ”,“ Busy ”, etc. are notified to other users. Other users can communicate appropriately with reference to the notified user's status. The information notification service that handles the presence status of these people is generally called IM (instant message), and has already rapidly spread on the Internet as a service.

  In these information notification services, information is frequently and frequently notified as the number of users increases, the accuracy of information increases, the details increase, and the information update frequency increases. As a result, the load on the information notification server and the network traffic increase, and the possibility of notification delay and non-delivery increases. For example, when the position information of a person can be measured by GPS, it is predicted that the information will be highly accurate, detailed, and updated more frequently, and the number of users will be further increased due to improved convenience. This further increases the load on the information notification server and the traffic on the network, and further increases the possibility of notification delays and non-delivery.

  As means for avoiding such notification delay and non-delivery, a high-speed network line is introduced and a plurality of information notification servers are installed, whereby the load of the information notification server can be distributed. However, if a plurality of information notification servers are installed and a high-speed network line is introduced, the operation cost increases.

  In addition, when notifying information to a plurality of destinations, there is an information distribution method that calculates a margin time for notification based on the status of each notification destination user and the priority of the information (see, for example, Patent Document 2). According to this method, a delay can be avoided by giving priority to a user with a short margin time, but a certain processing capability is required for the apparatus.

  In addition, in a system that performs notification of incoming mail received from the Internet, there is a system in which a mail distribution device changes a condition for transmitting a mail incoming notification to a terminal based on a reason for failure in transmission (for example, Patent Document 3). reference). According to this system, detailed incoming notification according to the standby state of the terminal is performed, and the failure rate of incoming calls is reduced. Note that this system increases the time until retransmission when the terminal is out of service, or shortens the time until retransmission when the terminal is busy based on the reason for the transmission failure. .

  In addition, in an electronic mail system having a mail retransmission function, there is an electronic mail system that allows a user to freely and easily set a retransmission parameter for each mail (see, for example, Patent Document 4).

In addition, even in the arrival notification prohibited time zone, there is an e-mail arrival notification method in which information is notified in the case of an e-mail with high importance and an e-mail from a specific partner (for example, Patent Documents) 5).
JP-A-9-282210 (paragraph numbers [0013] to [0018], FIGS. 1 and 6) JP 2002-314610 A (paragraph numbers [0030] to [0062], FIGS. 3 to 7) JP 2002-111707 A (paragraph number [0044], FIG. 12) JP 11-65961 A (paragraph number [0024], FIG. 4) Japanese Unexamined Patent Publication No. 2000-20418 (paragraph numbers [0013] to [0017], FIGS. 1 to 3)

  However, in the conventional method described above, delays and non-delivery are avoided by physical improvement measures for frequent and large number of information notifications, and physical processing such as the processing capability of the device itself and the upper limit transmission speed of the network is avoided. There is a problem that it cannot be applied to a case where a notification exceeding a certain limit value occurs.

  The present invention has been made in view of these points, and a notification delay or a notification failure may occur regardless of a physical solution such as increasing the processing capability of the device itself or increasing the transmission speed of the network. It is an object of the present invention to provide an information notification device that can reduce the above-described problem.

In the present invention, in order to solve the above problem, in the information notification device that notifies update information to the notification destination, the notification destination state is associated with the notification hold time for holding the update information notification for each notification destination. A notification hold time registration means for registering in the notification hold time management table, an update information receiving means for receiving the update information, a notification destination status receiving means for receiving the status of the notification destination, and the update information being received A notification hold time acquisition unit that acquires from the notification hold time management table a notification hold time corresponding to the state of the notification destination received, and holds the notification hold time and sends the received update information to the notification destination. There is provided an information notification device comprising an information notification means for notification .

According to the information notifying equipment acquires the notification hold time corresponding to the notification destination of the state received when receiving the update information from the notification holding time management table, pending notification hold time, which is received Notify the notification destination of update information.

In the information notification device of the present invention, the notification hold time corresponding to the notification destination state received when the update information is received is acquired from the notification hold time management table, the notification hold time is held, and the received update information is stored. The notification destination is notified. As a result, the load on the information notification device is reduced and the traffic on the network is reduced, so that notification of information is possible without using physical solutions such as increasing the processing capability of the device itself or the transmission speed of the network. It is possible to reduce the possibility of delay and notification failure.

Hereinafter, the principle of the present invention will be described in detail with reference to the drawings.
FIG. 1 is a principle diagram illustrating the principle of the present invention.
As shown in the figure, the information notification device 1 is connected to an information update terminal 2 and a notification destination terminal 3. The information update terminal 2 is a terminal that provides updated information such as a stock price to the notification destination terminal 3 via the information notification device 1. The notification destination terminal 3 is a terminal that receives notification of updated information. A user who uses the notification destination terminal 3 can receive the updated information by receiving the updated information at the notification destination terminal 3.

  The information notification device 1 suspends the updated information sent from the information update terminal 2 according to the state of the notification destination (the user who uses the notification destination terminal 3), and transmits the information to the notification destination terminal 3. The information notification device 1 includes a notification hold time registration unit 1a, an update information reception unit 1b, a notification destination state reception unit 1c, a notification hold time acquisition unit 1d, and an information notification unit 1e.

  In the notification hold time registration unit 1a, a notification hold time for holding notification to the notification destination of information to be updated and a user state of the notification destination terminal 3 are registered in association with each other. For example, the notification hold time is determined for each user status of being present, away from the phone, and on the phone, and these are registered in association with each other.

The update information receiving unit 1 b receives updated information from the information update terminal 2.
The notification destination state receiving unit 1 c receives the notification destination state of the updated information, that is, the state of the user of the notification destination terminal 3 from the notification destination terminal 3.

The notification hold time acquisition unit 1d acquires the notification hold time corresponding to the notification destination state received by the notification destination state reception unit 1c with reference to the notification hold time registration unit 1a.
The information notification unit 1e holds the notification hold time acquired by the notification hold time acquisition unit 1d, and transmits the updated latest information received by the update information reception unit 1b to the notification destination terminal 3 that is the notification destination.

The operation of the principle diagram will be described below.
The information update terminal 2 transmits the updated information to the information notification device 1 when the information is updated, such as a stock price.

  The update information receiving unit 1 b of the information notification device 1 receives the updated information from the information update terminal 2. The notification destination status receiving unit 1 c receives the status of the user of the notification destination terminal 3 that is the notification destination of the updated information from the notification destination terminal 3.

The notification hold time acquisition unit 1d acquires the notification hold time corresponding to the notification destination state received by the notification destination state reception unit 1c with reference to the notification hold time registration unit 1a.
The information notification unit 1e holds the notification hold time acquired by the notification hold time acquisition unit 1d, and transmits the latest information updated from the information update terminal 2 to the notification destination terminal 3 that is the notification destination. Further, when a new information update occurs during the hold, it is suppressed without being transmitted to the notification destination terminal 3.

  As described above, the information notification device 1 acquires the notification suspension time according to the state of the information notification destination with reference to the notification suspension time registration unit 1a. Then, the latest information updated from the information update terminal 2 is transmitted to the notification destination while holding the acquired hold time. Also, information updates that occur during suspension are suppressed without being sent to the notification destination. Therefore, since the notification of the information update which occurs within the notification hold time is suppressed, the load on the information notification device 1 and the network traffic are reduced. Therefore, it is possible to reduce the possibility that information notification delay or notification failure will occur, regardless of physical solution means such as increasing the processing capability of the device itself or increasing the transmission speed of the network.

Next, a first embodiment of the present invention will be described in detail with reference to the drawings.
FIG. 2 is a diagram illustrating a system configuration example of the information notification server according to the first embodiment.
As shown in the figure, the information notification server 10 is connected to the information update terminal 21 and the notification destination terminals 31 and 32 via a network 40 which is the Internet, for example.

  The information update terminal 21 is a terminal that provides information, and transmits the updated information to the information notification server 10 when the information is updated. The information includes, for example, information indicating the state of the user who uses the information update terminal 21, for example, information indicating that the user is on the phone, is present, or is away. When the user status is updated (when there is a change), the information update terminal 21 transmits information indicating the user status to the information notification server 10. Another example of information is a stock price. When the stock price is updated, the information update terminal 21 transmits the stock price to the information notification server 10.

  When the information notification server 10 receives information from the information update terminal 21, the information notification server 10 transmits the received information to the notification destination terminals 31 and 32 of the user who is the information notification destination. At this time, the information notification server 10 holds and transmits the information to be transmitted for a predetermined time.

  The hold time of the information to be transmitted is associated with the state of the user who uses the notification destination terminals 31 and 32 and is registered in the table of the information notification server 10. The information notification server 10 acquires the hold time corresponding to the state of the user who uses the notification destination terminals 31 and 32 with reference to the table. For example, when the user using the notification destination terminal 31 is away from the desk, a different holding time is acquired depending on whether the user is on the phone.

  The notification destination terminals 31 and 32 receive information from the information notification server 10 and display the information on a monitor. Thereby, the user who uses the notification destination terminals 31 and 32 can obtain information from the information update terminal 21.

  As described above, the information notification server 10 acquires the hold time corresponding to the state of the user of the notification destination terminals 31 and 32 that are the information notification destinations with reference to the table. Then, the acquired hold time is held and the latest updated information is transmitted to the notification destination terminals 31 and 32. As a result, the load on the device itself of the information notification server 10 and the traffic on the network 40 can be reduced, and the possibility that information notification delay or notification failure will occur can be reduced.

The information update terminal 21 and the notification destination terminals 31 and 32 are not limited to the number shown in FIG.
Next, the hardware configuration of the information notification server 10 will be described.

FIG. 3 is a block diagram illustrating a hardware configuration of the information notification server.
The information notification server 10 shown in the figure is controlled by a CPU (Central Processing Unit) 10a as a whole. A random access memory (RAM) 10b, a hard disk drive (HDD) 10c, a graphic processing device 10d, an input interface 10e, and a communication interface 10f are connected to the CPU 10a via a bus 10g.

  The RAM 10b temporarily stores at least a part of an OS (Operating System) program to be executed by the CPU 10a and an application program for holding and notifying information. The RAM 10b stores various data necessary for processing by the CPU 10a. The HDD 10c stores an OS, application programs, and the like.

  A monitor 10h is connected to the graphic processing device 10d. The graphic processing device 10d displays an image on the display screen of the monitor 10h in accordance with a command from the CPU 10a. A keyboard 10i and a mouse 10j are connected to the input interface 10e. The input interface 10e transmits a signal transmitted from the keyboard 10i or the mouse 10j to the CPU 10a via the bus 10g.

  The communication interface 10f is connected to the network 40. The communication interface 10f can communicate with other computers connected to the network 40 in accordance with instructions from the CPU 10a.

  With the hardware configuration described above, the information notification server 10 can execute an information notification process. Note that the information update terminal 21 and the notification destination terminals 31 and 32 also have the same hardware configuration as in FIG.

Next, functions of the information notification server 10 will be described.
FIG. 4 is a functional block diagram of the information notification server.
As shown in the figure, the information notification server 10 includes a state information update accepting unit 11, a notification hold control unit 12, a state information notification unit 13, a notification condition management table 14, a state information management table 15, a notification hold time management table 16, and A holding control management table 17 is provided. The notification condition management table 14, the state information management table 15, the notification hold time management table 16, and the hold control management table 17 are constructed in the storage device of the HDD 10c or RAM 10b shown in FIG. In the following, it is assumed that information (status information) indicating the status of the user who uses the information update terminal 21 is sent as information sent from the information update terminal 21.

First, a data configuration example of each table of the information notification server 10 will be described.
FIG. 5 is a diagram illustrating a data configuration example of the notification condition management table.
The notification condition management table 14 stores the user identifier of the user whose status information is updated and the user identifier of the user who is notified of the status information. As shown in the figure, the notification condition management table 14 has columns for an updater user ID and a notification destination user ID. The updater user ID column stores a user identifier assigned to a user who provides and updates state information (a user who uses the information update terminal 21). The notification destination user ID column stores a user identifier assigned to a user who receives notification of state information (a user who uses the notification destination terminals 31 and 32). In the following, the user identifier of the user who uses the information update terminal 21 is User-C, and the user identifier of the user who uses the notification destination terminals 31 and 32 is User-A and User-B.

  In the example of FIG. 5, the identifier of User-C is stored in the update user ID column of the notification condition management table 14. In the column of the notification destination user ID, identifiers of User-A and User-B are stored. Therefore, it can be seen that the state information updated by the user using the information update terminal 21 is notified to the user using the notification destination terminals 31 and 32.

FIG. 6 is a diagram illustrating a data configuration example of the state information management table.
The status information management table 15 stores the current status of the user who updates the status information and the user who receives the status information notification. As shown in the figure, the status information management table 15 has columns of user ID, status, and position. A user identifier is stored in the user ID column. The user ID column stores user identifiers of both the user who updates the state information and the user who receives the notification of the state information. The status column stores the status of the user corresponding to the user ID. The position column stores the position where the user is located.

  In the example of FIG. 6, User-A, User-B, and User-C are stored in the user ID column. In the column of the state corresponding to User-A of the user ID, “present” is stored. The office is stored in the column of the position corresponding to the user ID User-A. Accordingly, it can be understood that the current state of the user who uses the notification destination terminal 31 is present and the position is the office. In the column of the state corresponding to User-User User-C, “on-phone” is stored. The office is stored in the column of the position corresponding to User-User User-C. Thus, it can be seen that the current state of the user who uses the information update terminal 21 is on the phone and the position is the office.

FIG. 7 is a diagram illustrating a data configuration example of the notification suspension time management table.
The notification hold time management table 16 stores a user state, which is a condition for receiving notification of state information, and a notification hold time for holding notification of state information in association with each other. As shown in the figure, the notification hold time management table 16 has a notification destination user ID column, a state condition column, and a notification hold time column. The column of the notification destination user ID stores the user identifier of the user who receives notification of the state information. The status condition column stores a status condition for determining a notification suspension time for a user who receives notification of status information. In the notification hold time column, the time for holding the notification of the status information is stored.

  In the example of FIG. 7, User-A and User-B are stored in the column of the notification destination user ID. In the status condition column for User-A, there are stored being present, calling, and away. 10 seconds is stored in the column of the notification hold time when the state condition of User-A is present. One minute is stored in the column of the notification hold time when the state condition of User-A is on the phone. 60 minutes is stored in the column of the notification suspension time when the state condition of User-A is away. Also, 0 second is stored in the column of the notification hold time when the User-B state condition is present. 30 seconds is stored in the column of the notification hold time when the state condition of User-B is busy. 30 minutes is stored in the column of the notification suspension time when the state condition of User-B is away. As a result, the time for holding the status information with respect to the status of the user who uses the notification destination terminals 31 and 32 is known.

  Note that the notification hold time is set to be short when the user is notified of the state information, when the state information is highly likely to be referred to, for example, when the user is in the seated state. And it sets so that it may become long when there is a high possibility that it will not be referred even if it notifies a user of status information, for example, when it is in a away state.

FIG. 8 is a diagram illustrating a data configuration example of the hold control management table.
The hold control management table 17 stores data necessary for managing users for whom status information notification is held. When the status information notification is suspended, the data of the user whose notification is suspended is deleted from the suspension control management table 17. As shown in the figure, the hold control management table 17 has columns of a notification destination user ID, a notification hold start date and time, and an updater user ID. The column of the notification destination user ID stores the user identifier of the user who is notified of the status information. The notification hold start date and time column stores the date and time when the status information notification hold was started. The updater user ID column stores the user identifier of the user whose status information is updated.

  In the example of FIG. 8, User-A and User-B are stored in the column of the notification destination user ID. In the notification hold start date and time column corresponding to User-A, 2003/03/26/12: 00: 00 is stored. User-C is stored in the updater user ID column corresponding to User-A. In addition, 2003/03/26/12: 00: 00 is stored in the column of the notification hold start date and time corresponding to User-B. User-C is stored in the updater user ID column corresponding to User-B. As a result, it is understood that the user having the user identifiers of User-A and User-B is currently suspended from notification of the state information. In addition, the date and time when the notification is suspended and the user identifier of the user who is updating the status information can be known.

Returning to the description of FIG.
The status information update receiving unit 11 receives the status information updated from the information update terminal 21 and the location where the user using the information update terminal 21 is located via the network 40. Further, the status information update accepting unit 11 receives the status (status information) of the user who uses the notification destination terminals 31 and 32 and the location where the user is located via the network 40. The status information update acceptance unit 11 stores the status information and the position received from the information update terminal 21 and the notification destination terminals 31 and 32 in the status information management table 15 as shown in FIG.

  The notification hold control unit 12 refers to the notification condition management table 14 and acquires a notification destination for the updated state information received by the state information update receiving unit 11. For example, assuming that the updated status information is transmitted by User-C, the notification suspension control unit 12 uses the notification condition management table 14 to indicate User-A and User-B that are user identifiers of notification destinations. Can be obtained.

  Further, the notification hold control unit 12 refers to the hold control management table 17 and determines whether or not the user to whom the updated state information is notified is a user who is in a notification hold state. For example, a user whose user identifier is stored in the notification destination user ID column of the hold control management table 17 can be determined to be a user who is in a notification hold state. In addition, a user whose user identifier is not stored in the column of the notification destination user ID can be determined as a user who is not in a notification pending state. When the user who is notified of the status information is a user who is not in the notification pending state, the notification hold control unit 12 receives the user identifier, the notification hold start date and time (current date and time), and the status information. Are stored in the hold control management table 17.

  The notification hold control unit 12 refers to the state information management table 15 to acquire the state of the notification destination user, and sets the notification hold time corresponding to the acquired notification destination user state to the notification hold time management table 16. Get by referring to. Then, the notification hold control unit 12 acquires the notification hold start date / time of the notification destination user from the hold control management table 17, calculates the hold date / time by adding the notification hold time, and the current date / time has passed the hold date / time. Determine whether or not. That is, the notification hold control unit 12 determines whether or not the status information is held for the notification hold time by determining whether or not the current date has passed the date and time when the status information should be held. The notification hold control unit 12 deletes, from the hold control management table 17, user data for which notification of status information is held when the current date and time has passed the hold date and time.

  When it is determined from the notification hold control unit 12 that the date and time when the state information should be held has passed, the state information notification unit 13 acquires the state information to be notified to the notification destination from the state information management table 15, and the network 40 To the notification destination terminals 31 and 32 as notification destinations. That is, the state information notification unit 13 transmits the state information to the notification destination terminals 31 and 32 that are the notification destinations after the state information is suspended for the notification hold time.

Next, functions of the information update terminal 21 will be described.
FIG. 9 is a functional block diagram of the information update terminal.
As shown in the figure, the information update terminal 21 includes a state change detection unit 21a and a state information update request unit 21b.

  The state change detection unit 21a detects a change in the user's state. A change in the state of the user, for example, a change in the state of being present or away can be detected by the presence or absence of input to an input device such as a keyboard or mouse and the presence or absence of connection to the network 40. The state change during a telephone call can be made by detecting a signal from a telephone line used by the user, for example. In addition, a change in state can be detected (acquired) by allowing the user to input the state directly from the keyboard or mouse. Similarly, the state change detection unit 21a also detects the position where the user is located.

  The status information update request unit 21b transmits status information and position to the information notification server 10 via the network 40, and requests the status information update. The status information update accepting unit 11 of the information notification server 10 receives the status information and position in response to an update request from the information update terminal 21 and updates the status and position columns of the status information management table 15.

Next, the function of the notification destination terminal 31 will be described.
FIG. 10 is a functional block diagram of the notification destination terminal.
As shown in the figure, the notification destination terminal 31 includes a state change detection unit 31a, a state information update request unit 31b, a state information reception unit 31c, and a state information display unit 31d.

  The state change detection unit 31a detects a change in the user's state. A change in the state of the user, for example, a change in the state of being present or away can be detected by the presence or absence of input to an input device such as a keyboard or mouse and the presence or absence of connection to the network 40. The state change during a telephone call can be made by detecting a signal from a telephone line used by the user, for example. In addition, a change in state can be detected (acquired) by allowing the user to input the state directly from the keyboard or mouse. Similarly, the state change detection unit 31a also detects the position where the user is located.

  The state information update request unit 31b transmits the state information and the position to the information notification server 10 via the network 40, and requests an update of the state information. The status information update accepting unit 11 of the information notification server 10 receives the status information and position in response to an update request from the information update terminal 21 and updates the status and position columns of the status information management table 15.

  The state information receiving unit 31 c receives the state information transmitted from the information notification server 10. The status information display unit 31d displays the status information received from the status information receiving unit 31c on the monitor. Here, a screen example of state information displayed on the monitor will be described.

FIG. 11 is an example of a screen displayed on the monitor of the notification destination terminal.
A user status list screen 31e as shown in the figure is displayed on the monitor of the notification destination terminal. As shown in the screen 31e, columns of user ID, state, and position are displayed on the monitor. In the user ID column, the user identifier of the user who uses the information update terminal 21 that provides and updates the status information is displayed. Note that User-D and User-E are user identifiers of users who use the information update terminal 21. In the status column, the status of each user is displayed. In the position column, the position where each user is located is displayed. Thereby, for example, the user using the notification destination terminal 31 can determine whether or not the user using the information update terminal 21 is in a situation where communication is possible.

Note that the notification destination terminal 32 also has the same function as in FIG.
Next, the flow of processing of the information notification server 10, the information update terminal 21, and the notification destination terminal will be described using a flowchart.

First, the process flow of the information update terminal 21 will be described.
FIG. 12 is a flowchart showing a process flow of the information update terminal.
In step S1, the state change detection unit 21a of the information update terminal 21 detects whether or not the user's state has changed. If the user state does not change, step S1 is repeated. If the user status has changed, the process proceeds to step S2.

In step S <b> 2, the state information update request unit 21 b of the information update terminal 21 transmits the state information and the position to the information notification server 10 to request an update of the state information.
In this way, the information update terminal 21 detects a change in the user's state and requests the information notification server 10 to update the state information.

Next, the process flow of the notification destination terminal 31 will be described.
FIG. 13 is a flowchart showing a process flow of the notification destination terminal.
In step S <b> 11, the state information receiving unit 31 c of the notification destination terminal 31 waits for reception of the state information transmitted from the information notification server 10. While the status information is not transmitted from the information notification server 10, the status information reception wait is repeated. When the state information is transmitted from the information notification server 10, the process proceeds to step S12.

  In step S12, the status information display unit 31d of the notification destination terminal 31 displays the status information received from the status information receiving unit 31c on the monitor. As a result, a screen 31e as shown in FIG. 11 can be displayed on the monitor of the notification destination terminal 31, and the user using the notification destination terminal 31 is, for example, the user using the information update terminal 21 It is possible to determine whether or not communication is possible.

  The notification destination terminal 31 also detects a change in the state of the user and requests the information notification server 10 to update the state information. The flow of this process is the same as that shown in the flowchart of FIG.

Next, a processing flow of the information notification server 10 will be described.
FIG. 14 is a flowchart showing the flow of processing of the information notification server.
In step S <b> 31, the status information update accepting unit 11 of the information notification server 10 determines whether or not there is a status information update request from the information update terminal 21 and the notification destination terminals 31 and 32. If there is an update request for status information from the information update terminal 21 or the notification destination terminals 31 and 32, the process proceeds to step S32. If there is no update request for the state information, it continues to wait for the update request for the state information.

  In step S <b> 32, the state information update accepting unit 11 of the information notification server 10 receives the user state information and position from the information update terminal 21 and the notification destination terminals 31 and 32, and updates the state information management table 15. Thereby, the status information management table 15 stores the current status and position of the user who updates the status information and the user who receives the status information notification.

  In step S33, the notification hold control unit 12 of the information notification server 10 searches the notification condition management table 14 for the user ID (identifier) of the notification destination that notifies the updated state information.

  In step S <b> 34, the notification hold control unit 12 of the information notification server 10 determines whether or not the notification destination management ID for notifying the updated state information can be retrieved from the notification condition management table 14. If the user ID can be retrieved from the notification condition management table 14, it is determined that there is a notification destination to which the state information is to be notified, and the process proceeds to step S35. In step S35 and subsequent steps, processing is executed for each notification destination. If the user ID cannot be retrieved from the notification condition management table 14, it is determined that there is no notification destination to which the state information is to be notified, and the process proceeds to step S31.

In step S <b> 35, the notification hold control unit 12 of the information notification server 10 searches whether the notification destination user is registered in the hold control management table 17.
In step S <b> 36, the notification hold control unit 12 of the information notification server 10 determines whether or not the notification destination user has been searched from the hold control management table 17. If the notification destination user can be searched from the hold control management table 17, that is, if the notification destination user is a user who is holding the notification, the process proceeds to step S31. When the notification destination user cannot be searched from the hold control management table 17, that is, when the notification destination user is not a user who is not holding the notification, the process proceeds to step S37.

  In step S37, the notification hold control unit 12 of the information notification server 10 updates the hold control management table 17 by updating the user ID of the notification destination user, the current date and time (notification hold start date and time), and the status information. The user ID is registered.

In step S <b> 38, the notification hold control unit 12 of the information notification server 10 acquires the state of the notification destination user from the state information management table 15.
In step S39, the notification hold control unit 12 of the information notification server 10 refers to the notification hold time management table 16, and acquires the notification hold time corresponding to the state of the notification destination user acquired in step S38. Then, the notification hold control unit 12 obtains the notification hold start date / time of the notification destination user from the hold control management table 17, calculates the hold date / time by adding the notification hold time, and the current date / time has passed the hold date / time. Determine whether or not. If the current date has passed the hold date, the process proceeds to step S41. If the current date is not past the hold date, the process proceeds to step S38.

  In step S <b> 41, the notification hold control unit 12 of the information notification server 10 deletes the user data whose current date and time has passed the hold date and time from the hold control management table 17. That is, the user data that is no longer required to hold the status information notification is deleted from the hold control management table 17.

  In step S42, the state information notification unit 13 of the information notification server 10 acquires the state information to be notified from the state information management table 15, and transmits it to the notification destination terminals 31 and 32 that are the notification destinations. That is, the status information is transmitted to the notification destination terminals 31 and 32 of the notification destination user whose notification suspension is released.

Next, a processing sequence performed between the information notification server 10, the information update terminal 21, and the notification destination terminals 31 and 32 will be described.
FIG. 15 is a diagram illustrating a processing sequence performed between a conventional information notification server, an information update terminal, and a notification destination terminal.

  As shown in the figure, the information update terminal requests the information notification server to update the state information at a cycle of 30 seconds. Further, the status information update process and the update notification process performed by the information notification server are divided according to patterns as shown in the lower right of FIG.

  Upon receiving a status information update request from the information update terminal, the information notification server performs a status information update process. Then, update notification processing is performed on the two notification destination terminals. Conventionally, since notification is not suspended, update notification is always sent to both of two notification destination terminals at a cycle of 30 seconds, and status information is transmitted. That is, even when the user of the notification destination terminal is away from the desk, the status information is always transmitted at a cycle of 30 seconds, and the processing capability of the information notification server is wasted. In addition, network traffic is wasted. In addition, when the update interval of the information update terminal is shortened or the number of notification destination terminals is increased, the notification of the state information increases, and accordingly, the load of the information notification server and the network traffic increase, and the notification delay And the possibility of non-delivery increases.

FIG. 16 is a diagram illustrating a processing sequence performed between the information notification server, the information update terminal, and the notification destination terminal according to the present invention.
As shown in the figure, the information update terminal 21 requests the information notification server 10 to update the state information in a cycle of 30 seconds as shown in FIG. Further, the status information update process, the update notification process, and the notification hold process performed by the information notification server 10 are divided according to patterns as shown in the lower right of FIG. In addition, it is assumed that the state of the user who uses the notification destination terminal 31 is on the phone, and the state of the user who uses the notification destination terminal 32 is in the state of being away from the desk. Then, from the notification hold time management table 16, the notification hold time for the user using the notification destination terminal 31 is 1 minute. From the notice hold time management table 16, the notice hold time for the user using the notification destination terminal 32 is 30 minutes.

  As shown in the figure, the information notification server 10 does not notify the notification destination terminal of the status information every time the status information is updated by performing the notification hold processing. The user of the notification destination terminal 31 in the “in-phone” state is notified at a cycle of 1 minute and 30 seconds by holding the notification for one minute. In addition, the user of the notification destination terminal 32 who is “away from seat” is notified at a cycle of 30 minutes and 30 seconds by holding the notification for 30 minutes. When the notification process is suppressed with respect to the update of the state information that occurs during the notification hold process, the user of the notification destination terminal 31 is notified once with three state information updates. That is, two notifications are suppressed. In addition, the user of the notification destination terminal 32 is notified once by updating the status information 60 times. That is, 59 notifications are suppressed.

  In FIG. 15 and FIG. 16, the interval at which the information update device updates the state information is set to be a constant time period for the sake of simplicity, but the interval at which the information update device updates the state information is actually irregular. It is.

  In this way, the information notification server 10 refers to the hold control management table 17 to acquire the hold time corresponding to the state of the user of the notification destination terminals 31 and 32 that are the notification destinations of the state information. Then, the acquired hold time is held, and the latest information updated from the information update terminal 21 is transmitted to the notification destination terminals 31 and 32. Also, when the status of the notification destination user is in a state where there is a high possibility that it will not be referenced even if status information is notified, the notification hold time is lengthened and information updates that occur during the hold are not sent to the notification destination. Thus, notification of useless state information can be suppressed. As a result, the load on the information notification server 10 is reduced, and the traffic on the network 40 is reduced, so that information can be obtained regardless of physical solutions such as increasing the processing capability of the device itself and the transmission speed of the network. It is possible to reduce the possibility that notification delay or notification failure will occur.

  Further, as described in steps S38 to S40 in FIG. 14, the information notification server 10 acquires the notification destination user status from the status information management table 15, and the notification hold time corresponding to the acquired notification destination user status. Is acquired from the notification hold time management table 16. Then, from the hold control management table 17, the notification hold start date / time of the notification destination user is acquired and the hold date / time is calculated by adding the notification hold time to determine whether the current date / time has passed the hold date / time. The information notification server 10 repeats these steps until the current date and time passes the hold date and time.

  Thereby, when the state of the notification destination is updated while the notification of information is suspended, the notification suspension time corresponding to the updated state is acquired. Therefore, since the notification hold time is changed in response to the state of the notification destination user immediately, the notification destination user can be effectively notified of the state information.

In addition, when the state information satisfies a predetermined notification condition, the state information can be suspended and notified to the notification destination.
FIG. 17 is a diagram illustrating another example of the data configuration example of the notification condition management table.

  As shown in the figure, the notification condition management table 14a is provided with an updater position condition column as compared with the notification condition management table 14 shown in FIG. In the updater position condition column, a condition of a position where an updater (a user who uses the information update terminal 21) is located for notifying information is stored. The notification hold control unit 12 refers to the notification condition management table 14a and determines whether or not the position of the updater sent together with the state information matches the updater position condition. The notification hold control unit 12 holds the notification of the state information when the updater's position matches the updater position condition. In the example of FIG. 17, when a user having a user identifier of User-C is in the office, the updated state information is suspended and notified to the notification destination.

  In this way, not all the state information is notified to the notification destination, but only the state information satisfying the notification condition is notified to the notification destination. As a result, only necessary state information that satisfies the notification condition can be notified to the notification destination, and notification of state information can be suppressed. As another example, when the information to be updated is a stock price, when the stock price reaches a specific value, the stock price can be notified to the notification destination. In the above description, the position of the updater is also regarded as the user status information.

  In addition, when the status information does not satisfy the notification condition while the status information is on hold, the status information is not notified to the notification destination. For example, when the notification condition management table 14 is updated while the notification is suspended, and the updated state information does not satisfy the notification condition, data corresponding to the information that does not satisfy the notification condition is deleted from the hold control management table 17. So that notifications are not made.

  Specifically, in the notification condition management table 14 of FIG. 5, it is assumed that the status information of “User-C” has been updated and the notification to “User-A” has been put on hold. At this time, if the first row of the notification condition management table 14 (the row where the updater user ID is “User-C” and the notification destination user ID is “User-A”) is deleted, “User-C” to “User-C” The condition information notification condition for User-A ”is eliminated. In this case, data corresponding to this status information is deleted from the hold control management table 17 so that notification is not performed.

In this way, it is possible to suppress notification of useless state information by not reporting to the notification destination state information that no longer satisfies the notification condition during suspension.
In the case of the notification condition management table 14a shown in FIG. 17, when the position information of “User-C” changes to other than “office”, the state information (including the user position) satisfies the notification condition. Disappear. Also in this case, as described above, the notification corresponding to the state information that no longer satisfies the notification condition is deleted from the hold control management table 17 so that the notification is not performed.

It is also possible to set the notification hold time for the state of the notification destination for each update source of the state information.
FIG. 18 is a diagram illustrating another example of the data configuration example of the notification suspension time table.

  As shown in the figure, the notification hold time management table 16a is provided with an updater user ID column as compared with the notification hold time management table 16 shown in FIG. The updater user ID field stores an update source user identifier for updating information.

  The notification hold time varies depending on the update source user. In the example of FIG. 18, the notification suspension time while User-A is present is 10 seconds when the update source user is User-C, and 0 seconds when the update source user is User-D. It is.

  As described above, by registering the notification hold time and the notification destination state for each update source of the state information, the notification hold time can be determined based on the value of the state information that is different for each update source.

  Further, the notification hold control unit 12 may change the notification hold time according to the elapsed time from the time when the state of the user of the notification destination is last updated. For example, if the status of the user to be notified is “separated” and the status of “separated” continues for a long time, it is highly likely that the status information will not be referred to even if the status information is suspended. is expected. At this time, it is possible to suppress notification of useless state information by extending the notification hold time according to the elapsed time in the state of “away from seat” (for example, simply adding the elapsed time to the notification hold time). be able to.

Next, a second embodiment of the present invention will be described in detail with reference to the drawings.
FIG. 19 is a diagram illustrating a system configuration example of information notification according to the second embodiment.
When the stock price notification service company 51 according to the second embodiment shown in the figure receives a stock price update notification from the securities company 52, it notifies the user 53 of the stock price. At this time, as in the first embodiment, the stock price notification service company 51 suspends the stock price notification according to the state of the user 53, but the user 53 can change the notification suspension time. It has become.

  Stock price information is information that many users want to obtain quickly. This is because the user needs more up-to-date stock price information in order to obtain profits from stocks. However, if many of the users shorten the notification suspension time, the load on the device itself that provides the service of the stock price notification service company 51 increases, and the network traffic increases. Therefore, only the user who is permitted to change the notification hold time can change the notification hold time. For example, a user who wants to notify a stock price update in a short holding time can receive a notice by paying a price to the stock price notification service company 51. Thereby, the user can enjoy the merit of receiving a stock price notification in a short holding time by paying a consideration. Further, the stock price notification service company 51 can increase facilities by receiving consideration from the user, and can reduce the load on the information notification server and the traffic. In addition, the securities company 52 can enjoy merits by receiving a stock transaction fee from the user.

Next, functions of the information notification server according to the second embodiment installed in the stock price notification service company 51 will be described.
FIG. 20 is a functional block diagram of the information notification server.

  The information notification server 60 shown in the figure is a server installed in the stock price notification service company 51 shown in FIG. The information notification server 60 is different from the information notification server 10 shown in FIG. 4 in that it further includes a notification hold time registration accepting unit 61 and a notification hold time registration permission management table 62. 20, the same components as those in FIG. 4 are denoted by the same reference numerals, and the description thereof is omitted.

  The notification hold time registration receiving unit 61 receives a notification hold time registration request from the notification destination terminal used by the user 53 receiving the information notification, and stores the notification hold time sent from the notification destination terminal in the notification hold time management table 16. sign up. At this time, the notification hold time registration accepting unit 61 accepts only registration requests from users registered in the notification hold time registration permission management table 62, and invalidates registration requests from unregistered users.

The notification hold time registration permission management table 62 stores data necessary for identifying a notification destination terminal that permits registration of the notification hold time.
FIG. 21 is a diagram illustrating a data configuration example of the notification hold time registration permission management table.

  As shown in the figure, the notification hold time registration permission management table 62 has a notification hold time registration permission user ID column. The user ID of a user who can change the notification hold time is stored in the column of the notification hold time registration permission user ID.

  In the example of FIG. 21, User-A and User-B are stored in the column of the notification hold time registration permission user ID. Therefore, the notification hold time registration accepting unit 61 is changed to the registration request only when the user having the user identifiers User-A and User-B requests the notification hold time from the notification destination terminal. The suspension time is received and registered in the notification suspension time management table 16.

  The user who has contracted with the owner of the information notification server 60 and paid the registration fee is given permission to change the notification hold time and is registered in the notification hold time registration permission management table 62. Also good. If the user can be expected to benefit from being notified of information with a shorter notification hold time, the user can contract with the owner of the information notification server 60 and pay a registration fee. Can be notified. Thereby, the user can obtain a profit by paying a registration fee and having the information notified in a short notice suspension time. On the other hand, the information notification server 60 side can obtain a profit from the registration fee from the user, and can enhance the facilities.

Next, functions of the notification destination terminal will be described.
FIG. 22 is a functional block diagram of the notification destination terminal.
The notification destination terminal 71 shown in the figure is a terminal used by the user 53 shown in FIG. The notification destination terminal 71 is different from the notification destination terminal 31 shown in FIG. In FIG. 22, the same components as those in FIG. 10 are denoted by the same reference numerals, and the description thereof is omitted.

The notification hold time registration request unit 72 receives the notification hold time from the user, and requests the information notification server 60 to register the notification hold time.
Note that the information update terminal used in the securities company 52 has the same functional blocks as the information update terminal 21 shown in FIG. 9, and a description thereof will be omitted.

  In this way, by enabling the notification hold time to be changed and registered depending on the notification destination, the notification destination user can obtain information early on important information and late information on unimportant information. You can get it.

  Further, for example, by allowing only authorized users to change and register notification hold time, such as only paid users, it is possible to reduce the load on the information notification server 60 and reduce traffic. It becomes possible.

Furthermore, the information notification server 60 may set a lower limit value for the notification hold time, and may set a lower limit value for the notification hold time for a user who pays a lot of consideration.
Next, a third embodiment of the present invention will be described in detail with reference to the drawings.

FIG. 23 is a diagram illustrating a system configuration example of information notification according to the third embodiment.
When the sales price notification service company 81 according to the third embodiment shown in the figure receives a request for updating the sales price of a product from the product seller 82, it notifies the user 83 of the sales price of the product. At this time, the sales price notification service company 81 holds the notification of the sales price of the product according to the state of the user 83 as in the first embodiment. The sales price can be notified.

  For example, when the sales price of the main product is reduced, the merchandise seller 82 wants to notify the user 83 quickly without a notice hold time. This is because the possibility of receiving orders for products from many users increases. However, if the merchandise seller makes the notification suspension time no longer, the load on the device that provides the service of the sales price notification service company 81 increases, and the traffic on the network increases. Therefore, only the merchandise seller authorized in advance can make the notification suspension time absent. For example, a merchandise seller who wants to notify an update of the sales price of a merchandise without a holding time can notify the sales price notification service company 81 without paying the sales price of the merchandise by holding a price. As a result, the merchandise seller can pay the consideration and notify the user 83 of the sale price of the merchandise without any holding time, and can receive the merit by receiving the order of the merchandise from the user. Further, the sales price notification service company 81 can increase the facilities by receiving consideration from the merchandise seller, and can reduce the load and traffic of the information notification server. In addition, the user 83 can purchase a product at a lower price.

Next, the function of the information notification server according to the third embodiment installed in the sales price notification service company 81 will be described.
FIG. 24 is a functional block diagram of the information notification server.

  The information notification server 90 shown in the figure is a server installed in the sales price notification service company 81 shown in FIG. The information notification server 90 is different from the information notification server 10 shown in FIG. 4 in that the notification hold control unit 12 further includes an emergency notification control processing unit 91. Moreover, the place which has the emergency notification permission management table 92 differs. 24, the same components as those in FIG. 4 are denoted by the same reference numerals, and the description thereof is omitted.

  The emergency notification control processing unit 91 receives an information update request from the information update terminal used by the merchandise seller 82 who updates information. At this time, when urgent notification information is added to the updated information, the notification hold control unit 12 performs the notification process immediately without performing the notification hold process. At this time, the emergency notification control processing unit 91 sets only the information from the information update source registered in the emergency notification permission management table 92 as a target for the notification processing without performing the notification hold processing. The emergency notification information required by the information update source that is not registered in the emergency notification permission management table 92 is invalidated, and notification suspension processing is performed.

The emergency notification permission management table 92 stores data necessary for identifying an information update terminal that permits use of an emergency notification.
FIG. 25 is a diagram illustrating a data configuration example of the emergency notification permission management table.

  As shown in the figure, the emergency notification permission management table 92 has an emergency notification permission update source ID column. In the column of the emergency notification permission update source ID, an update source terminal identifier capable of setting the notification hold time is stored.

  In the example of FIG. 25, the information update terminals A and B are stored in the emergency notification permission update source ID column. Therefore, the emergency notification control processing unit 91 has no registration request and no notification hold time only when a terminal having the terminal identifiers of the information update terminals A and B makes a registration request with the emergency notification information required. Is registered in the emergency notification permission management table 92.

  The merchandise seller who uses the information update terminal that has contracted with the owner of the information notification server 90 and paid the registration fee is given permission to notify the information without suspension, and is registered in the emergency notification permission management table 92. You may make it do. If the merchandise seller using the information update terminal can expect to benefit from providing the information to the notification destination user without holding, if the contract is paid with the owner of the information notification server 90 Information can be provided to the user of the notification destination without putting the notification on hold. As a result, the merchandise seller using the information update terminal pays a registration fee and provides the information to the notification destination user without holding, for example, increasing the order of the merchandise from the notification destination user. Can be obtained. On the other hand, the information notification server 90 side can obtain a profit from a registration fee from a merchandise seller who uses the information update terminal, and can increase facilities.

  Further, the information notification server 90 side can expect an increase in the number of notification destination users by discounting the registration fee registered by the notification destination user described in the second embodiment. As the number of users increases, the merchandise seller who uses the information update terminal also increases the merit of notifying the user of information via the information notification server 90. Therefore, the information notification server 90 side uses the information update terminal. Further increase in registration fee income can be expected due to new acquisition of merchandise sellers to use.

Next, functions of the information update terminal will be described.
FIG. 26 is a functional block diagram of the information update terminal.
An information update terminal 101 shown in the figure is a terminal used by the merchandise seller 82 shown in FIG. The information update terminal 101 is different from the information update terminal 21 shown in FIG. 9 in that the state information update request unit 21b includes an emergency notification information addition processing unit 102. In FIG. 26, the same components as those in FIG. 9 are denoted by the same reference numerals, and the description thereof is omitted.

  The emergency notification information addition processing unit 102 receives an emergency notification information addition request from the merchandise seller. In this case, when transmitting the updated information to the information notification server 90, the status information update request unit 21b transmits the emergency notification information that is required to be added to the updated information.

Note that the notification destination terminal used by the user 83 has the same functional blocks as the notification destination terminal 31 shown in FIG.
In this way, by allowing the update source to invalidate the suspension of notifications of updated information, the update source user can promptly send information to important information that he / she wants to notify the notification destination user quickly. It can be provided to the user of the notification destination, and unimportant information can be provided on hold.

  In addition, for example, only the permitted update source, such as only the update source that paid the fee, can be disabled, thereby reducing the load on the information notification server 90 and reducing the traffic. It becomes possible.

  A program describing the processing contents of the functions that the computer should have is provided. By executing the program on a computer, the above processing functions are realized on the computer. The program describing the processing contents can be recorded on a computer-readable recording medium. Examples of the computer-readable recording medium include a magnetic recording device, an optical disk, a magneto-optical recording medium, and a semiconductor memory. Examples of the magnetic recording device include a hard disk device (HDD) flexible disk (FD) and a magnetic tape. Examples of the optical disc include a DVD (Digital Versatile Disc), a DVD-RAM (Random Access Memory), a CD-ROM (Compact Disc Read Only Memory), and a CD-R (Recordable) / RW (ReWritable). Magneto-optical recording media include MO (Magneto-Optical disk).

  The computer that executes the program stores, for example, the program recorded on the portable recording medium or the program transferred from the server computer in its own storage device. Then, the computer reads the program from its own storage device and executes processing according to the program. The computer can also read the program directly from the portable recording medium and execute processing according to the program. In addition, each time the program is transferred from the server computer, the computer can sequentially execute processing according to the received program.

(Supplementary Note 1) In an information notification device for notifying update destination of update information,
A notification hold time registration means in which a notification hold time for holding a notification to the notification destination of the update information is registered in association with a state of the notification destination;
Update information receiving means for receiving the update information;
Notification destination status receiving means for receiving the status of the notification destination;
A notification hold time acquisition unit that acquires the notification hold time corresponding to the received state of the notification destination from the notification hold time registration unit;
Information notification means for holding the notification hold time and notifying the notification destination of the received update information;
An information notification apparatus comprising:

(Additional remark 2) It further has an identifier registration means in which the identifier of the notification destination is registered,
The information notification device according to claim 1, wherein the information notification unit notifies the update information to the notification destination in which the identifier is registered.

(Additional remark 3) It further has a notification condition registration means in which a notification condition for notifying the update information to the notification destination is registered,
The information notification apparatus according to claim 1, wherein the information notification unit notifies the update information when the update information satisfies the notification condition.

  (Supplementary note 4) The supplementary note 3 is characterized in that the information notification means does not notify the update information when the update information does not satisfy the notification condition while the update information is being held at the notification destination. Information notification device.

  (Supplementary Note 5) When the notification destination state is updated while the update information notification is suspended, the notification suspension time acquisition unit obtains the notification suspension time corresponding to the updated state from the notification suspension time registration unit. The information notification device according to attachment 1, wherein the information notification device is acquired.

(Supplementary note 6) The information notification device according to supplementary note 1, wherein the notification suspension time registration unit registers the notification suspension time and the state of the notification destination for each update source of the update information.
(Supplementary note 7) The information notification device according to supplementary note 1, further comprising notification suspension time changing means for changing the notification suspension time according to a time during which the same state of the notification destination continues.

(Supplementary note 8) The information notification device according to supplementary note 1, wherein the notification suspension time is registered by the notification destination.
(Supplementary note 9) The information notification device according to supplementary note 8, wherein registration of the notification destination is permitted in advance.

(Supplementary note 10) The information notification device according to supplementary note 8, wherein a lower limit value is determined for the notification suspension time.
(Additional remark 11) When the emergency notification information which shows that it is necessary to notify urgently to the said update information is added, the said information notification means notifies the said update information, without hold | maintaining. 1. The information notification device according to 1.

(Additional remark 12) The said emergency notification information is added in the information update terminal which updates the said update information, The information notification apparatus of Additional remark 11 characterized by the above-mentioned.
(Additional remark 13) The information notification apparatus of Additional remark 11 characterized by having an emergency notification information determination means which determines whether the said emergency notification information was added to the said update information with the permitted information update terminal.

(Supplementary Note 14) In an information notification program for notifying update destinations of update information,
On the computer,
A notification hold time registration unit in which a notification hold time for holding a notification to the notification destination of the update information is registered in association with a state of the notification destination;
Update information receiving means for receiving the update information;
Notification destination status receiving means for receiving the status of the notification destination;
A notification hold time acquisition unit for acquiring the notification hold time corresponding to the received state of the notification destination from the notification hold time registration unit;
Information notification means for holding the notification hold time and notifying the notification destination of the received update information;
An information notification program characterized by functioning as

It is a principle figure explaining the principle of this invention. It is the figure which showed the system configuration example of the information notification server which concerns on 1st Embodiment. It is the block diagram which showed the hardware constitutions of the information notification server. It is a functional block diagram of an information notification server. It is the figure which showed the data structural example of the notification condition management table. It is the figure which showed the data structural example of the status information management table. It is the figure which showed the example of a data structure of the notification pending | holding time management table. It is the figure which showed the data structural example of the pending | holding control management table. It is a functional block diagram of an information update terminal. It is a functional block diagram of a notification destination terminal. It is an example of a screen displayed on the monitor of a notification destination terminal. It is the flowchart which showed the flow of the process of an information update terminal. It is the flowchart which showed the flow of the process of a notification destination terminal. It is the flowchart which showed the flow of the process of an information notification server. It is the figure which showed the processing sequence performed among the conventional information notification server, an information update terminal, and a notification destination terminal. It is the figure which showed the processing sequence performed between the information notification server of this invention, an information update terminal, and a notification destination terminal. It is the figure which showed the other example of the data structural example of the notification condition management table. It is the figure which showed the other example of the data structural example of the notification pending | holding time table. It is the figure which showed the system configuration example of the information notification which concerns on 2nd Embodiment. It is a functional block diagram of an information notification server. It is the figure which showed the data structural example of the notification pending | holding time registration permission management table. It is a functional block diagram of a notification destination terminal. It is the figure which showed the system configuration example of the information notification which concerns on 3rd Embodiment. It is a functional block diagram of an information notification server. It is the figure which showed the data structural example of the emergency notification permission management table. It is a functional block diagram of an information update terminal.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 Information notification apparatus 1a Notification hold time registration means 1b Update information reception means 1c Notification destination status reception means 1d Notification hold time acquisition means 1e Information notification means 2, 21 Information update terminal 3, 31, 32 Notification destination terminal 10, 60, 90 Information notification server 11 Status information update acceptance unit 12 Notification hold control unit 13 Status information notification unit 14 Notification condition management table 15 Status information management table 16 Notification hold time management table 17 Hold control management table 61 Notification hold time registration reception unit 62 Notification hold Time registration permission management table 91 Emergency notification control processing unit 92 Emergency notification permission management table

Claims (10)

In an information notification device for notifying update information to a notification destination,
A notification hold time registration means for registering the notification destination state and the notification hold time for holding the update information notification in the notification hold time management table in association with each notification destination ;
Update information receiving means for receiving the update information;
Notification destination status receiving means for receiving the status of the notification destination;
Notification hold time acquisition means for acquiring a notification hold time corresponding to the state of the notification destination received when the update information is received from the notification hold time management table ;
Information notification means for holding the notification hold time and notifying the notification destination of the received update information;
An information notification apparatus comprising: An identifier registration unit in which the identifier of the notification destination is registered;
The information notification device according to claim 1, wherein the information notification unit notifies the update information to the notification destination in which the identifier is registered. A notification condition registration unit in which a notification condition for notifying the update destination of the update information is registered;
The information notification device according to claim 1, wherein the information notification unit notifies the update information when the update information satisfies the notification condition.   4. The information notification according to claim 3, wherein when the update information does not satisfy the notification condition while the update information is being held at the notification destination, the information notification unit does not notify the update information. apparatus.   The notification hold time acquisition unit acquires the notification hold time corresponding to the updated state from the notification hold time registration unit when the state of the notification destination is updated during the notification hold of the update information. The information notification apparatus according to claim 1, wherein:   The information notification apparatus according to claim 1, wherein the notification hold time registration unit registers the notification hold time and the state of the notification destination for each update source of the update information.   The information notifying unit notifies the update information without suspending it when emergency notification information indicating that it is necessary to notify the update information urgently is added. Information notification device.   The information notification apparatus according to claim 7, wherein the emergency notification information is added at an information update terminal that updates the update information.   8. The information notification device according to claim 7, further comprising emergency notification information determination means for determining whether or not the emergency notification information is added to the update information by an authorized information update terminal. In an information notification program for notifying update recipients of update information,
On the computer,
A notification hold time registering means for associating the status of the notification destination and the notification hold time for holding the notification of the update information in the notification hold time management table in association with each notification destination ;
Update information receiving means for receiving the update information;
Notification destination status receiving means for receiving the status of the notification destination;
A notification hold time acquisition means for acquiring a notification hold time corresponding to the state of the notification destination received when the update information is received from the notification hold time management table ;
Information notification means for holding the notification hold time and notifying the notification destination of the received update information;
An information notification program characterized by functioning as

Images