JP2007335960A - Information providing apparatus and information providing method, and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a technology of smoothly and efficiently executing an event notice from the Internet side to a LAN side without the need for changing the setting of a firewall or the like. <P>SOLUTION: An event relay server apparatus 2 receives event information from an event notice apparatus 3 and receives a request of the transmission of the event information from an event receiving apparatus 1. When receiving the request, the event relay server apparatus 2 determines whether or not the event relay server apparatus 2 receives the event information for the event receiving apparatus 1, and when the event relay server apparatus 2 receives notice information (event information) for the event receiving apparatus 1, the event relay server apparatus 2 generates a reply including the event information. When not receiving the event information but receiving the event information before a lapse of a prescribed period of time, the event relay server apparatus 2 responds to the reception of the event information and immediately generates the reply including the event information, and when the event relay server apparatus 2 does not receive the event information even after the lapse of the prescribed period of time, the event relay server apparatus 2 generates a reply denoting the absence of the event information, and transmits the generated reply to the event receiving apparatus 1 via a router apparatus 5. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention relates to a technique for providing information from a device connected to the Internet to a device connected to a LAN (Local Area Network) connected to the Internet via a gateway device.

  There are various restrictions on accessing a device (terminal device) connected to a LAN from a device (server device) connected to the Internet via a gateway device.

For example, when a terminal device does not have a global IP (Internet Protocol) address but has only a local IP address, the gateway device (router) uses a NAT (Network Address Translation) function or a NAPT (Network Address Port Translation) function. There are techniques for converting IP addresses and port numbers.
When converting the IP address and port number of the terminal device using the NAT function and NAPT function, the server device knows the IP address and port number of the terminal device according to a request from the terminal device. Therefore, it is difficult to actively access the terminal device from the server device side.
In addition, when a terminal device connected to a LAN in NAPT communicates with a server device connected to the Internet outside NAPT by a router having a NAPT table, in order to notify an event from the Internet side to the LAN side, it is necessary to explicitly It is necessary to set access permission for the NAPT table from the Internet side to the LAN side.
As a technique for enabling the above-described access without performing such settings, there is a method described in Patent Document 1.
In Patent Document 1, a packet is periodically transmitted from a terminal on the LAN side to a server device on the Internet side, and in this communication, a router mapping table set for a certain period is automatically used. The event is notified by accessing the LAN side from the server on the Internet side.

From the viewpoint of security, there is a technique (so-called firewall) in which the gateway device restricts access from the server device to the terminal device.
There are various firewall technologies, but a method of permitting access from the terminal device to the server device and a response from the server device to the server device, and restricting access from the other server devices to the terminal device, Widely done.
JP 2004-120547 A

The technology described in Patent Document 1 uses UDP (User) for access from a server device to a terminal device.
Datagram Protocol).
However, since UDP does not have a procedure for starting communication or the like, it is difficult to determine which of the terminal device and the server device has started communication.
Therefore, in the firewall technology, there is a case where UDP communication is uniformly restricted, and the method disclosed in Patent Document 1 has a problem that an available environment is restricted. For example, in a company or the like, an HTTP (Hyper Text Transfer Protocol) or HTTPS (Hyper Text Transfer Protocol over Secure Sockets Layer) is allowed to access the server on the Internet side from a terminal on the LAN side via a Web proxy that allows access to the server on the Internet side. Has the problem of being unavailable.
In addition, this method cannot be used when it is necessary to change notification destinations, event notifications to multiple notification destinations, or change event contents according to the situation, such as events. There is a problem.

  The main object of the present invention is to solve the above-mentioned problems, and in an environment where Web access is possible, the security that has already been set is maintained, and there is no need to change router settings or the like. The main purpose is to realize immediate event notification from the local server to the LAN side. Also, the main purpose is to change the transmission destination according to the contents of the event.

An information providing apparatus according to the present invention includes:
One or more notification information transmission devices that transmit notification information, and an information provision device that communicates with an information acquisition device that acquires notification information,
A notification information receiving unit for receiving notification information from each notification information transmitting device;
A request receiving unit for receiving a request for requesting transmission of notification information from the information acquisition device;
When the request reception unit receives a request from the information acquisition device, it determines whether notification information for the information acquisition device is received, and when notification information for the information acquisition device is not received A reply including the notification information in response to reception of the notification information when the notification information for the information acquisition device is received before the elapse of a predetermined period after waiting for reception of the notification information from one of the notification information transmission devices. A reply generation unit that generates a reply that the notification information for the information acquisition device does not exist when the notification information for the information acquisition device is not received even after a predetermined time has passed,
It has a reply transmission part which transmits the reply produced | generated by the said reply production | generation part with respect to the said information acquisition apparatus.

  In the present invention, instead of immediately returning a reply to the request, after receiving the request, it waits for the reception of the notification information, and when the notification information is received before the elapse of a certain period, the notification information is received. In response, a reply including the notification information is transmitted immediately, so that the notification information can be transmitted to the information acquisition device immediately after the notification information is received.

Embodiment 1 FIG.
FIG. 1 is a system configuration diagram showing an example of the overall configuration of the communication system in this embodiment.
The communication system according to the present embodiment includes an event receiving device 1, a router device 5, an event relay server device 2, and an event notification device 3. The event receiver 1 is an example of an information acquisition device. The router device 5 is an example of a relay device. The event relay server device 2 is an example of an information providing device. The event notification device 3 is an example of a notification information transmission device.

The router device 5, the event relay server device 2, and the event notification device 3 are connected to the Internet 4 and can communicate with each other.
The event receiving device 1 is connected to the router device 5 via the LAN, connected to the Internet 4 via the router device 5, and a device (for example, the event relay server device 2) connected to the Internet 4. Can communicate.

The router device 5 has a firewall function.
The router device 5 permits communication from the event receiving device 1 to a device on the Internet side (for example, the event relay server device 2). As a response to this, communication from the Internet side device to the event receiving device 1 is also permitted. However, communication that is not a response to communication from the event receiver 1 is prohibited.
Therefore, although it is possible to access the event relay server device 2 from the event receiving device 1, access from the event relay server device 2 to the event receiving device 1 is not permitted.

The router device 5 has a NAPT function.
The router device 5 converts the local IP address of the event receiving device 1 that is valid only within the LAN using the NAPT function, and connects to the Internet side device.

Although only one event notification device 3 is displayed in FIG. 1, it is assumed that there are a plurality of event notification devices 3.
The event notification device 3 transmits event notification information (hereinafter referred to as event information) for notifying various events to the event relay server device 2. The event notification device 3 may be separately connected to a device that generates an event via a LAN or a unique network.
For example, in a refrigeration equipment system, the event notification function may be included in the refrigeration equipment (for example, an indoor unit or an outdoor unit of an air conditioner) itself, or in a refrigeration equipment controller that performs integrated management control of the refrigeration equipment. You may do it. In the latter case, an event such as an abnormality may be generated by the cooling / heating device itself, or the cooling / heating device controller may monitor the state of the cooling / heating device and generate an event. In this case, the cooling / heating device controller is connected to each cooling / heating device through a unique network, and the cooling / heating device controller is connected to the event relay server device 2 on the Internet via a router device via a LAN or the like. Further, a form in which a plurality of event generation devices (for example, cooling / heating devices) are connected to one event notification device (for example, a cooling / heating device controller) may be employed.
Similarly, each controller and each controller such as a water heater system, a floor heating system, a lighting system, an elevator system, an all-electric system, a security system, a surveillance camera system, or an FA system may have the same relationship.

  The event relay server device 2 transmits the event information from the event notification device 3 to the event reception device 1 via the router device 5.

  The event receiving device 1 may be connected to a device that displays the received event information, or may separately send a mail to a destination that separately sets the received event in cooperation with a mail system or the like. . In addition, the event receiving device 1 may be configured to accumulate event information, cooperate with a Web server function, and the like so that the stored event content can be confirmed from a Web client or the like.

Next, the operation of the communication system according to the present embodiment will be outlined with reference to FIG.
In the present embodiment, the event relay server device 2 (information providing device) is connected to one or more event notification devices 3 (notification information transmission devices) that transmit event information (notification information), The event receiving device 1 (information acquisition device) to be acquired is connected to the router device 5 through the router 5.
Then, the event relay server device 2 receives event information from each event notification device 3, and receives a request for requesting transmission of event information from the event reception device 1. As illustrated in FIG. 3, the event reception device 1 transmits a request every time a reply is received from the event relay server device 2, and continuously transmits requests to the event relay server device 2.
When the event relay server device 2 receives a request from the event reception device 1, the event relay server device 2 determines whether or not event information for the event reception device 1 is received, and receives notification information for the event reception device 1. In this case, a reply including the event information is generated, and the generated reply is transmitted to the event receiving apparatus 1 via the router apparatus 5.
On the other hand, when event information for the event receiving device 1 is not received, waiting for reception of the event information from one of the event notification devices 3, and when event information for the event receiving device 1 is received before a certain period of time elapses In response to the reception of the event information, a reply including the event information is immediately generated, and the generated reply is transmitted to the event receiving device 1 via the router device 5.
Further, if event information for the event receiving device 1 is not received even after a predetermined time has elapsed, a reply indicating that there is no event information for the event receiving device 1 is generated, and the generated reply is sent to the event via the router device 5. Transmit to the receiver 1.
When receiving event information, the event receiving device 1 performs predetermined processing on the event information.
In the example of FIG. 3, replies (1), (2), (n) and (n + 2) which are responses to the requests (1), (2), (n) and (n + 2) are replies with no event information. Yes, reply (n + 1) which is a response to request (n + 1) is a reply including event information.
The terminal access receiving unit 10 and the event receiving relay unit 13 that are components of the event relay server device 2 will be described later.

FIG. 2 is a block configuration diagram illustrating an example of functional block configurations of the event reception device 1, the event relay server device 2, and the event notification device 3 according to the embodiment.
In FIG. 2, the router device 5, the LAN, and the Internet 4 are omitted.

  The event reception device 1 includes a server access unit 6, an event reception control unit 7, an event information analysis unit 8, and an event reception unit 9.

The server access unit 6 communicates with the event relay server device 2. HTTP or HTTPS is used as the communication protocol, but other protocols may be used as long as the protocol is permitted to pass by a normal gateway device, firewall, or proxy.
The event reception control unit 7 generates a request for requesting the event relay server device 2 to transmit event information.
The event information analysis unit 8 analyzes the reply from the event relay server device 2 received by the server access unit 6 and determines whether event information is included in the reply.
When the event information analysis unit 8 determines that event information is included in the reply, the event reception unit 9 receives the event information from the event information analysis unit 8 and performs processing on the event information. For example, as described above, event information is displayed, mail is sent to a predetermined destination, and the like.

The event relay server device 2 includes a terminal access reception unit 10, an event confirmation unit 11, and an event reception relay unit 13.
The terminal access receiving unit 10 receives a request for requesting transmission of event information from the event receiving device 1.
The event reception relay unit 13 receives event information from each of the plurality of event notification devices 3.
The event confirmation unit 11 determines whether or not the event reception relay unit 13 has received event information for the event reception device 1 when the terminal access reception unit 10 receives a request from the event reception device 1. . When event information for the event receiving device 1 is received, a reply including the event information is generated. On the other hand, when event information for the event receiving device 1 is not received, waiting for reception of the event information from one of the event notification devices 3, and when event information for the event receiving device 1 is received before a certain period of time elapses In response to the reception of the event information, a reply including the event information is generated immediately, and the event information for the event reception device 1 exists when the event information for the event reception device 1 is not received even after a predetermined time has elapsed. Generate a reply to the effect.
Further, the terminal access receiving unit 10 transmits the reply generated by the event confirming unit 11 to the event receiving device 1 via the router device 5.
The terminal access receiving unit 10 is an example of a request receiving unit and a reply transmitting unit. The event confirmation unit 11 is an example of a reply generation unit. The event reception relay unit 13 is an example of a notification information reception unit.

The event notification device 3 includes an event notification unit 14.
The event notification unit 14 displays event information that notifies at least one of an event that has occurred in the event notification device 3 and an event that has occurred in a device (for example, the above-described cooling device) managed by the event notification device 3. 2 to send.

Here, a hardware configuration example of the event reception device 1, the event relay server device 2, the event notification device 3, and the router device 5 according to the present embodiment will be described.
FIG. 15 is a diagram illustrating an example of hardware resources of the event reception device 1, the event relay server device 2, the event notification device 3, and the router device 5 according to the present embodiment and the embodiments described below.
In FIG. 15, an event receiving device 1, an event relay server device 2, an event notification device 3, and a router device 5 are a CPU 911 (Central Processing Unit, a central processing unit, a processing unit, an arithmetic unit, a microprocessor, a microcomputer that executes a program. , Also referred to as a processor). The CPU 911 is connected to, for example, a ROM (Read Only Memory) 913, a RAM (Random Access Memory) 914, a communication board 915, a display device 901, a keyboard 902, a mouse 903, and a magnetic disk device 920 via a bus 912. Control hardware devices. Further, the CPU 911 may be connected to an FDD 904 (Flexible Disk Drive), a compact disk device 905 (CDD), a printer device 906, and a scanner device 907. Further, instead of the magnetic disk device 920, a storage device such as an optical disk device or a memory card read / write device may be used.
The RAM 914 is an example of a volatile memory. The storage media of the ROM 913, the FDD 904, the CDD 905, and the magnetic disk device 920 are an example of a nonvolatile memory. These are examples of a storage device or a storage unit.
The communication board 915, the keyboard 902, the scanner device 907, the FDD 904, and the like are examples of an input unit and an input device.
Further, the communication board 915, the display device 901, the printer device 906, and the like are examples of an output unit and an output device.

The communication board 915 is connected to the Internet or a LAN as shown in FIG.
The magnetic disk device 920 stores an operating system 921 (OS), a window system 922, a program group 923, and a file group 924. The programs in the program group 923 are executed by the CPU 911, the operating system 921, and the window system 922.

The program group 923 stores programs that execute the functions described as “units” in the present embodiment and the following description of the embodiments. The program is read and executed by the CPU 911.
In the file group 924, information, data, and signals described as “determination result of”, “calculation result of”, “processing result of”, “evaluation result of”, etc. in the following description Values, variable values, and parameters are stored as items of “˜file” and “˜database”. The “˜file” and “˜database” are stored in a recording medium such as a disk or a memory. Information, data, signal values, variable values, and parameters stored in a storage medium such as a disk or memory are read out to the main memory or cache memory by the CPU 911 via a read / write circuit, and extracted, searched, referenced, compared, Used for CPU operations such as calculation, calculation, processing, editing, output, printing, and display. Information, data, signal values, variable values, and parameters are stored in the main memory, registers, cache memory, and buffers during the CPU operations of extraction, search, reference, comparison, calculation, processing, editing, output, printing, and display. It is temporarily stored in a memory or the like.
The arrows in the flowchart described below mainly indicate input / output of data and signals. The data and signal values are the RAM 914 memory, FDD 904 flexible disk, CDD 905 compact disk, magnetic disk device 920 magnetic disk, In addition, it is recorded on a recording medium such as an optical disc, a mini disc, or a DVD. Data and signals are transmitted online via a bus 912, signal lines, cables, or other transmission media.

  In addition, what is described as “to part” in this embodiment and the following description of the embodiment may be “to circuit”, “to device”, “to device”, and “means”. It may also be “˜step”, “˜procedure”, “˜processing”. That is, what is described as “˜unit” may be realized by firmware stored in the ROM 913. Alternatively, it may be implemented only by software, or only by hardware such as elements, devices, substrates, and wirings, by a combination of software and hardware, or by a combination of firmware. Firmware and software are stored as programs in a recording medium such as a magnetic disk, a flexible disk, an optical disk, a compact disk, a mini disk, and a DVD. The program is read by the CPU 911 and executed by the CPU 911. That is, the program causes the computer to function as “to part” of the present embodiment and the embodiments described below. Alternatively, it causes a computer to execute the procedures and methods of “to part” of the present embodiment and the embodiments described below.

  As described above, the event reception device 1, the event relay server device 2, the event notification device 3, and the router device 5 shown in the present embodiment and the embodiments described below are a CPU as a processing device, a memory as a storage device, and a magnetic disk. A computer including an input device such as a keyboard, a mouse, and a communication board, an output device such as a display device, a communication board, and the like. This is realized by using a device and an output device.

Next, the operation of the event receiver 1 will be described with reference to the flowchart of FIG.
In S401, the server access unit 6 makes an HTTP or HTTP access to the event relay server device 2 and obtains a reply to the request.
In step S402, the event information analysis unit 8 analyzes the reply data to determine whether event information is included. If event information is not included, the event reception control unit 7 returns to S1 again. If there is event information, the event information analysis unit 8 passes the event information to the event reception unit 9.
In step S403, the event reception unit 9 processes the obtained event information. Thereafter, the process returns to S1 again.

  Next, an operation example (information providing method) of the event relay server device 2 will be described with reference to FIGS.

First, an operation example of the event reception relay unit 13 of the event relay server device 2 will be described with reference to the flowchart of FIG.
First, in S501, the event reception relay unit 13 receives event information from the event notification device 3 (notification information reception step).
In step S <b> 502, the event reception relay unit 13 notifies the event confirmation unit 11 of reception of the event information, and passes the received event information to the event confirmation unit 11. The event confirmation unit 11 stores the event information received from the event reception relay unit 13 in a predetermined buffer memory.

Next, operation examples of the terminal access receiving unit 10 and the event confirmation unit 11 of the event relay server device 2 will be described with reference to the flowchart of FIG.
In S601, in the event relay server device 2, the terminal access receiving unit 10 receives access (HTTP request, HTTPS request) from the event receiving device 1 (request receiving step).
Next, in S602, the event confirmation unit 11 determines whether or not the event information addressed to the event reception device 1 has already been received from the event reception relay unit 13, that is, the event information addressed to the event reception device 1 is stored in the buffer memory. (Reply generation step), and if the event information has already been received, the event confirmation unit 11 proceeds to Step S606 and adds the corresponding event information to generate a reply ( (Reply generating step), the terminal access receiving unit 10 transmits the reply to the event receiving device 1 via the router device 5 (reply transmitting step).
On the other hand, if it is determined in S602 that the event information addressed to the event receiving apparatus 1 has not been received, in S603, the event confirmation unit 11 has passed a predetermined time from the reception of the request in S601, or the event reception relay unit Wait until there is a notification of reception of event information from 13 (reply generation step).
Here, when the event confirmation unit 11 has not received event information from the event reception relay unit 13, that is, when a predetermined time has elapsed (No in S604), the process proceeds to S605, where the event confirmation unit 11 The terminal access reception unit 10 transmits the reply to the event reception device 1 via the router device 5 (reply transmission step). Thereafter, the process returns to S601.
On the other hand, if the event confirmation unit 11 receives event information from the event reception relay unit 13 within a certain period (No in S604), the process proceeds to S606, and immediately adds the corresponding event information and generates a reply. (Reply generation step), the terminal access reception unit 10 transmits the reply to the event reception device 1 via the router device 5 (reply transmission step).

As described above, in the present embodiment, the terminal access reception unit 10 and the event confirmation unit 11 of the event relay server device 2 immediately respond to a request when event information for the event reception device 1 is not received. Instead of returning a reply, it waits for a certain time whether the event reception relay unit 13 receives event information. When the event reception relay unit 13 receives the event information, it immediately returns a reply including the event information. Therefore, immediate notification of the event becomes possible.
This method, which is called a normal polling method, receives a request and immediately returns a response and waits for a certain time on the event receiving device side to transmit the request, so that this immediate notification cannot be made.

The event receiving device communicates with the event relay server device 2 across the NAPT router or the Web proxy. However, since the event relay server device 2 transmits event information only by request / reply reply, Information can pass through a NAPT router or a Web proxy.
That is, all communication between the event receiving device 1 and the event relay server device 2 is realized by HTTP or HTTPS access from the event receiving device 1 to the event relay server device 2 and its reply, so that a NAPT router or Web proxy is used. Communication between the terminal and the server is possible even when accessing via the Internet.
Also, through this communication, event information can be passed from the event relay server device to the event receiving device.
In the present embodiment, an example in which a request according to the HTTP protocol or the HTTPS protocol is transmitted from the event receiving apparatus 1 has been described. However, if the router apparatus 5 is a reply, a communication protocol that permits the passage of data from the outside. Any other format can be used as long as the request is generated in the format. Then, the event relay server device 2 generates a reply in the communication protocol format.

  Further, since it seems that the event receiving device is always connected to the event relay server device, immediate event notification is possible. In this case, an HTTP or HTTPS access is made from the event receiving device to the event relay server device, the state is kept connected for a certain period, and a reply is once returned. Thereafter, by immediately accessing the event relay server device from the event receiving device, the same effect as that of the constant connection is brought about. For this reason, if the router device 5 or the like on the way is determined to be in a no-communication state when it is always connected, the TCP session may be automatically disconnected. However, in this embodiment, such a situation does not occur. . Further, periodic communication (KeepAlive) for preventing automatic session disconnection during no communication is also unnecessary.

As described above, in the present embodiment, the event receiving apparatus including the following means has been described.
(A) Server access means for transmitting event reception apparatus identification information to the event relay server apparatus by HTTP or HTTPS protocol, receiving data as a reply, and passing the data to the event information analysis means;
(B) Analyzing the data passed from the server access means, determining the presence or absence of event information, and including the event information, the event information analyzing means for passing the event information to the event receiving means, or not including the event information If the event information analysis means, do nothing
(C) event reception control means for controlling to repeat the above processing;
(D) Event receiving means for receiving and processing events.

In the present embodiment, the event relay server apparatus including the following means has been described.
(A) After receiving the event receiving device identification information from the event receiving device using the HTTP or HTTPS protocol, the event receiving device receives event information from the event confirming means, and the event information is sent to the event receiving device as a reply of the received data. Terminal access receiving means to return,
(A-2) In the above, if there is no event notification from the event confirmation means for a predetermined time, the terminal access is returned to the event receiving apparatus as a reply of the received data without putting the event information Receiving means.

Further, it has been described that the relay server device according to the present embodiment further includes the following means.
(A) From the event reception relay means, to the terminal access receiving means receiving the event receiving apparatus identification information and event information of the event transmission destination and receiving access from the event receiving apparatus indicated by the event receiving apparatus identification information , Event confirmation means to notify event information,
(B) Event notification means of the event notification device, event reception relay means for receiving event receiving device identification information and event information of the event transmission destination and passing them to the event confirmation means.

Further, in the present embodiment, the event notification device including the following means has been described.
(A) Event notification means for transmitting the event receiving device identification information and event information of the event transmission destination to the event relay means of the event relay server device.

Embodiment 2. FIG.
In the first embodiment described above, the event notification device 3 specified by the event notification device 3 notifies the event receiving device 1 of the event transmission destination of the specified event content as it is. An embodiment in which a drop, simultaneous notification of events to a plurality of destinations, or event notification with changed event contents is performed will be described.

FIG. 7 shows a system configuration example according to the present embodiment.
In FIG. 7, unlike FIG. 1, there are a plurality of event receiving apparatuses 1. Other points are the same as in FIG. The termxx of each event receiving device 1 is an identification number of the event receiving device 1.

FIG. 2 is a block configuration diagram illustrating an example of functional block configurations of the event reception device 1, the event relay server device 2, and the event notification device 3 according to the embodiment.
In FIG. 5, the router device 5, the LAN, and the Internet 4 are omitted.
In FIG. 8, an event notification destination determination unit 12 and an event notification rule table 15 are added as compared with FIG. Other points are the same as in FIG.
The event notification destination determination unit 12 is an example of a transmission destination determination unit.

In FIG. 8, the difference from FIG. 2 is that the event confirmation unit 11 makes a reply for the corresponding event reception device as it is from the event reception device identification information and event information of the event transmission destination obtained from the event reception relay unit 13. Instead of generating the information, the information is once passed to the event notification destination determination unit 12, and the event information obtained from the result is obtained for the zero or more event transmission destinations obtained from the result. It is a point to generate a reply including.
Therefore, when the event transmission destination is 0, the event information is dropped, that is, no event is notified to any event receiving device 1.
When there is one event transmission destination, event information is notified to the transmission destination.
When there are two or more event destinations, the event information is duplicated and broadcast to each destination.

In the present embodiment, the event reception relay unit 13 (notification information reception unit) receives temporary event notification destination information (temporary event notification destination information) indicating a temporary transmission destination of event information from each of the plurality of event notification devices 3 (notification information transmission devices). Event information to which (temporary transmission destination identification information) is added is received.
Then, the event notification destination determination unit 12 (transmission destination determination unit) analyzes the temporary event notification destination information added to the event information, and determines the transmission destination of the event information. For example, as a result of analyzing the temporary event notification destination information, the event notification destination determination unit 12 broadcasts the event information to the event reception devices 1 other than the event reception device 1 indicated as the transmission destination in the temporary event notification destination information. Decide whether to send.
The event confirmation unit 11 (reply generation unit) becomes a target of broadcast transmission when the event notification destination determination unit 12 determines to broadcast the event information to two or more event reception devices 1. In response to requests from two or more event receiving apparatuses 1, a reply including the event information is generated.

Further, the event reception relay unit 13 receives a plurality of types of event information from each of the plurality of event notification devices 3, and the event notification destination determination unit 12 analyzes the type of the event information and transmits the transmission destination of the event information To decide. For example, as a result of analyzing the type of event information, the event notification destination determination unit 12 determines whether or not to broadcast the event information to two or more event reception devices 1.
The event confirmation unit 11 receives two or more events to be broadcast when the event notification destination determination unit 12 determines to broadcast the event information to the two or more event reception devices 1. In response to a request from the device 1, a reply including the event information is generated.

  In addition, the event notification destination determination unit 12 may analyze the temporary event notification destination information added to the event information and the type of the event information to determine the transmission destination of the event information.

  Further, the event notification destination determination unit 12 determines a transmission destination of the event information and determines whether or not to perform data conversion of the event information, and the event confirmation unit 11 is selected by the event notification destination determination unit 12. When it is determined that the event information data conversion is performed, the event information data conversion is performed to generate a reply including the event information after the data conversion.

  In the present embodiment, the event notification destination determination unit 12 analyzes the event information and determines the transmission destination of the event information according to the event notification rule tables of FIGS.

FIG. 9 shows an example of an event notification rule table to be referred to when the event notification destination determination unit 12 determines a transmission destination of event information. FIG. 9 shows an example of an event notification rule table in the case where the transmission destination of event information is determined based on temporary event notification destination information.
In FIG. 9, provisional event transmission destination is provisional event notification destination information and indicates a provisional transmission destination of event information. The actual event transmission destination indicates the event reception device 1 that the event notification destination determination unit 12 determines as a transmission destination that actually transmits event information. Here, termxx is an identification number of the event receiving device 1, and an identification number is set for each event receiving device 1 as shown in FIG.
For example, when term1 is specified as the temporary event transmission destination, term1 is returned as the actual event transmission destination information group, and when term1x is specified as the temporary event transmission destination, term10, term11,. . If term1n is returned and the temporary event transmission destination is term0, this event information is not transmitted.

FIG. 10 shows an example of an event notification rule table when the event information transmission destination is determined based on the type of event information.
FIG. 10 shows types of event information such as INFO, ERROR, FATAL, DEBUG, and the actual event transmission destination is designated for each type.
For example, if the event information is information corresponding to INFO or INFO, term1 is returned as the real event transmission destination information group, term10, term11 is returned for information corresponding to ERROR, and term10, term11 is returned for FATAL. . . . term1n is returned, and in the case of DEBUG, this event is not transmitted.

FIG. 11 shows an example of an event notification rule table when the event information transmission destination is determined based on the combination of the temporary event notification destination information and the type of event information.
FIG. 11 also shows whether or not to perform data conversion such as Japanese conversion, code conversion, and data compression on the event information.
For example, when the event information is information corresponding to INFO and the temporary event transmission destination is term1, term1 and term2 are returned as the actual event transmission destination information group, and the event information is converted into Japanese and transmitted. When the event information is information corresponding to INFO and the temporary event transmission destination is term0, term1 is returned as the actual event transmission destination information group, and the data of the event information is converted and transmitted. In the case of DEBUG, event information is compressed and transmitted.

Next, the operation (1: 1 event notification) according to the present embodiment will be described with reference to FIG.
Each of the event receiving devices 1 (term1, term10, term11,... Term1n) transmits a request to the terminal access receiving unit 10 of the event relay server device 2. In FIG. 12, only requests and replies between the event receiving device 1 (term 1) and the event relay server device 2 are shown for convenience of drawing, but each event receiving device 1 and the event relay server device 2 are shown. Similarly, it is assumed that requests and replies are also transmitted and received between and.
As in the first embodiment, the terminal access receiving unit 10 of the event relay server device 2 holds a request from the event receiving device 1 for a certain period of time and returns a reply when no event information is received. .
The event receiving device 1 that has received the reply transmits the request again. This is repeated.
Assume that the event reception relay unit 13 of the event relay server device 2 receives event information (temporary event transmission destination = term1) from the event notification device 3 (termX) in the above state.
As in the first embodiment, the event reception relay unit 13 notifies the event confirmation unit 11 of reception of the event information and passes the event information to the event confirmation unit 11. The event confirmation unit 11 passes this event information to the event notification destination determination unit 12.
The event notification destination determination unit 12 refers to the event notification rule table and determines the event reception device term1 corresponding to the temporary event transmission destination term1 as the actual event transmission destination (in FIG. 12, the event notification rule table of FIG. Shows an example of use).
The event confirmation unit 11 generates a reply (reply including event information) for the event reception device 1 (term 1) that is the transmission destination of the event information determined by the event notification destination determination unit 12.
Next, the terminal access receiving unit 10 immediately sends a reply to the request from the corresponding event receiving device 1 (term1) (although normally maintaining the connection for a certain period of time). As a result, the event information is passed from the event notification device (termX) to the event reception device 1 (term1).

Next, the operation (1: N event notification) according to the present embodiment will be described with reference to FIG.
Each of the event receiving devices 1 (term1, term10, term11,... Term1n) transmits a request to the terminal access receiving unit 10 of the event relay server device 2. In FIG. 13, only a part of request and reply transmission / reception states are shown for the convenience of drawing. However, FIG. 12 shows between each event receiving device 1 and the event relay server device 2. As described above, it is assumed that requests and replies are continuously transmitted and received.
Here, it is assumed that the event reception relay unit 13 of the event relay server device 2 receives event information (temporary event transmission destination = term1x) from the event notification device 3 (termX).
As in the first embodiment, the event reception relay unit 13 notifies the event confirmation unit 11 of reception of the event information and passes the event information to the event confirmation unit 11. The event confirmation unit 11 passes this event information to the event notification destination determination unit 12.
The event notification destination determination unit 12 refers to the event notification rule table and determines the event reception device 1 (term10.term11,... Term1n) corresponding to the temporary event transmission destination term1 as the actual event transmission destination (in FIG. 12, FIG. 9 shows an example of using the event notification rule table of FIG.
The event confirmation unit 11 generates a reply (reply including event information) for the event reception device 1 (term10.term11,... Term1n) that is the transmission destination of the event information determined by the event notification destination determination unit 12.
Next, the terminal access receiving unit 10 broadcasts a reply to a request from the corresponding event receiving device 1 (term10.term11,... Term1n) immediately (although normally maintaining a connection for a certain period of time). As a result, the event information is transferred from the event notification device (termX) to the event reception device 1 (term10.term11,... Term1n).

  12 and 13, the example using the event notification rule table of FIG. 9 has been described, but the same processing is performed when the event notification rule table of FIGS. 10 and 11 is used.

Next, an operation example of the event relay server device 2 according to the present embodiment will be described with reference to the flowchart of FIG.
In FIG. 14, S1401 to S1405 are the same as S601 to S605 of FIG.
In S1406, based on the temporary event notification destination information and the type of event information indicated in the event information, the event notification destination determination unit 12 determines the transmission destination of the event information according to the event notification rule table of FIGS.
In step S1407, the event confirmation unit 11 generates a reply including event information in response to the request from the event reception device 1 determined as the event information transmission destination by the event notification destination determination unit 12, and the terminal access reception unit 10 sends a reply containing event information.

  As described above, according to the present embodiment, it is possible to change an event notification destination, drop an event notification, simultaneously notify an event to a plurality of destinations, or to change an event content (data format). .

As described above, in the present embodiment, the event relay server apparatus having the following means has been described.
(A) Event confirmation means for obtaining event reception apparatus identification information of a new event transmission destination by passing event reception apparatus identification information of the event transmission destination obtained from the event reception relay means to the event notification destination determination means;
(B) Event notification destination determining means for searching the event notification rule table from event receiving apparatus identification information of the event transmission destination obtained from the event confirmation means, and returning event receiving apparatus identification information of new zero or more event transmission destinations. ,
(C) Event notification rule table having a correspondence table of event notification destination information (referred to as temporary event notification destination information) as a key and zero or more new event notification destination information (referred to as real event notification destination information group) .

In the present embodiment, the event relay server apparatus having the following means has been described.
(A) Event confirmation means for passing the event information obtained from the event reception relay means to the event notification destination determination means and obtaining event reception device identification information of a new event transmission destination;
(B) an event notification destination determination unit that searches the event notification rule table from event information obtained from the event confirmation unit and returns event reception device identification information of new zero or more event transmission destinations;
(C) An event notification rule table having a correspondence table of event information as a key and zero or more new event notification destination information (referred to as a real event notification destination information group).

The event relay server apparatus having the following means has also been described.
(A) The event information obtained from the event reception relay means and / or event transmission destination event reception device identification information is passed to the event notification destination determination means, and the new event content and event transmission destination event reception device identification information Event confirmation means,
(B) an event notification destination determination unit that searches the event notification rule table from the event information obtained from the event confirmation unit and / or the event reception device identification information of the event transmission destination and returns new event information;
(C) An event notification rule table having a correspondence table or event replacement rule between event information as a key and / or event receiving device identification information of an event transmission destination and new event information.

FIG. 3 is a diagram illustrating an example of a system configuration according to the first embodiment. FIG. 3 is a block diagram illustrating a configuration example of an event reception device, an event relay server device, and an event notification device according to the first embodiment. FIG. 3 is a diagram illustrating an outline of operations of the event reception device, the event relay server device, and the event notification device according to the first embodiment. FIG. 3 is a flowchart showing an operation example of the event receiving apparatus according to the first embodiment. FIG. 3 is a flowchart showing an operation example of the event relay server apparatus according to the first embodiment. FIG. 3 is a flowchart showing an operation example of the event relay server apparatus according to the first embodiment. FIG. 4 is a diagram illustrating an example of a system configuration according to a second embodiment. FIG. 4 is a block diagram illustrating a configuration example of an event reception device, an event relay server device, and an event notification device according to the second embodiment. The figure which shows the example of the event notification rule table which concerns on Embodiment 2. FIG. The figure which shows the example of the event notification rule table which concerns on Embodiment 2. FIG. The figure which shows the example of the event notification rule table which concerns on Embodiment 2. FIG. The figure which shows the outline | summary of operation | movement of the event receiver which concerns on Embodiment 2, an event relay server apparatus, and an event notification apparatus. The figure which shows the outline | summary of operation | movement of the event receiver which concerns on Embodiment 2, an event relay server apparatus, and an event notification apparatus. FIG. 6 is a flowchart showing an operation example of the event relay server apparatus according to the second embodiment. The figure which shows the hardware structural example of the event receiver which concerns on Embodiment 1, 2, an event relay server apparatus, an event notification apparatus, and a router apparatus.

Explanation of symbols

  1 event receiving device, 2 event relay server device, 3 event notification device, 4 Internet, 5 router device, 6 server access unit, 7 event reception control unit, 8 event information analysis unit, 9 event reception unit, 10 terminal access reception unit , 11 Event confirmation unit, 12 Event notification destination determination unit, 13 Event reception relay unit, 14 Event notification unit, 15 Event notification rule table.

Claims (12)

One or more notification information transmission devices that transmit notification information, and an information provision device that communicates with an information acquisition device that acquires notification information,
A notification information receiving unit for receiving notification information from each notification information transmitting device;
A request receiving unit for receiving a request for requesting transmission of notification information from the information acquisition device;
When the request reception unit receives a request from the information acquisition device, it determines whether notification information for the information acquisition device is received, and when notification information for the information acquisition device is not received A reply including the notification information in response to reception of the notification information when the notification information for the information acquisition device is received before the elapse of a predetermined period after waiting for reception of the notification information from one of the notification information transmission devices. A reply generation unit that generates a reply that the notification information for the information acquisition device does not exist when the notification information for the information acquisition device is not received even after a predetermined time has passed,
An information providing apparatus comprising: a reply transmission unit configured to transmit a reply generated by the reply generation unit to the information acquisition apparatus. The information providing apparatus includes:
Arranged outside the relay device that blocks access to the information acquisition device from outside, communicate with the information acquisition device via the relay device,
The request receiver
If the relay device is a reply, a request generated in the form of a communication protocol that permits the passage of data from outside is received from the information acquisition device via the relay device,
The reply generation unit
The information providing apparatus according to claim 1, wherein a reply is generated in the format of the communication protocol. The request receiver
Receives a request generated in either of the HTTP (Hyper Text Transfer Protocol) protocol and the HTTPS (Hyper Text Transfer Protocol over Secure Sockets Layer) protocol,
The reply generation unit
The information providing apparatus according to claim 2, wherein the reply is generated in any one of an HTTP protocol and an HTTPS protocol. The notification information receiving unit
Receiving event notification information from each notification information transmitting device for notifying at least one of an event occurring in the notification information transmitting device and an event occurring in a device managed by the notification information transmitting device,
The reply generation unit
The information providing apparatus according to claim 1, wherein a reply including event notification information received by the notification information receiving unit is generated. The request receiver
Receive requests from multiple information acquisition devices,
The notification information receiving unit
From each notification information transmitting device, receive notification information to which temporary transmission destination identification information indicating a temporary transmission destination of notification information is added,
The information providing apparatus further includes:
Analyzing the temporary transmission destination identification information added to the notification information received by the notification information receiving unit, and having a transmission destination determination unit for determining the transmission destination of the notification information;
The reply generation unit
The information providing apparatus according to claim 1, wherein a reply including the notification information is generated for a request from an information acquisition apparatus determined as a transmission destination by the transmission destination determination unit. The request receiver
Receive requests from multiple information acquisition devices,
The notification information receiving unit
Receive multiple types of notification information from each notification information transmission device,
The information providing apparatus further includes:
Analyzing the type of notification information received by the notification information receiving unit, and having a transmission destination determination unit that determines a transmission destination of the notification information,
The reply generation unit
The information providing apparatus according to claim 1, wherein a reply including the notification information is generated for a request from an information acquisition apparatus determined as a transmission destination by the transmission destination determination unit. The notification information receiving unit
Receive multiple types of notification information from each notification information transmission device,
The transmission destination determination unit
6. The temporary transmission destination identification information added to the notification information received by the notification information receiving unit and the type of the notification information are analyzed, and the transmission destination of the notification information is determined. Information provision device. The transmission destination determination unit
Determine the destination of the notification information, determine whether to perform data conversion of the notification information,
The reply generation unit
When it is determined by the transmission destination determination unit to perform data conversion on any of the notification information, a reply including the notification information after the data conversion is generated by performing data conversion on the notification information. Item 8. The information providing device according to any one of Items 5 to 7. The transmission destination determination unit
As a result of analyzing the temporary transmission destination identification information, it is determined whether or not to broadcast the notification information to an information acquisition device other than the information acquisition device indicated as the transmission destination in the temporary transmission destination identification information,
The reply generation unit
When the transmission destination determination unit determines to broadcast the notification information to two or more information acquisition devices, the notification information in response to a request from two or more information acquisition devices to be broadcasted The information providing apparatus according to claim 5, wherein a reply including the message is generated. The transmission destination determination unit
As a result of analyzing the type of notification information, determine whether to broadcast the notification information to two or more information acquisition devices,
The reply generation unit
When the transmission destination determination unit determines to broadcast the notification information to two or more information acquisition devices, the notification information in response to a request from two or more information acquisition devices to be broadcasted The information providing apparatus according to claim 6, wherein a reply including the message is generated. An information providing method for communicating with one or more notification information transmission devices for transmitting notification information and an information acquisition device for acquiring notification information,
A notification information receiving step for receiving notification information from each notification information transmitting device;
A request reception step for receiving a request for requesting transmission of notification information from the information acquisition device;
When the request reception step receives a request from the information acquisition device, it is determined whether notification information for the information acquisition device is received, and when the notification information for the information acquisition device is not received A reply including the notification information in response to reception of the notification information when the notification information for the information acquisition device is received before the elapse of a predetermined period after waiting for reception of the notification information from one of the notification information transmission devices. A reply generation step of generating a reply that the notification information for the information acquisition device does not exist when the notification information for the information acquisition device is not received even after a predetermined time has passed,
A reply transmission step of transmitting the reply generated by the reply generation step to the information acquisition device. One or more notification information transmission devices that transmit notification information, and a computer that communicates with an information acquisition device that acquires notification information,
Notification information reception processing for receiving notification information from each notification information transmitting device;
A request reception process for receiving a request for transmission of notification information from the information acquisition device;
When the request reception process receives a request from the information acquisition device, it determines whether notification information for the information acquisition device is received, and when the notification information for the information acquisition device is not received A reply including the notification information in response to reception of the notification information when the notification information for the information acquisition device is received before the elapse of a predetermined period after waiting for reception of the notification information from one of the notification information transmission devices. A reply generation process for generating a reply indicating that there is no notification information for the information acquisition device when notification information for the information acquisition device is not received even after a predetermined time has passed,
A program for executing a reply transmission process for transmitting a reply generated by the reply generation process to the information acquisition apparatus.