IP Library Granted Patent US 10,412,033
Granted Patent B2
US 10,412,033 · App. 15/017,131 · Granted Sep 10, 2019

Event notification method, event notification device, and storage medium

Inventors: Narukazu Hayashi (Oosaka, JP); Kazuhiro Hayashi (Yokohama, JP); Motoaki Kojima (Yokohama, JP)
Assignee: FUJITSU LIMITED
H04L51/14H04L51/26
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,412,033
App. No.
15/017,131
Granted
Sep 10, 2019
Kind
B2
Abstract

An event notification method executed by a processor included in an event notification device, the event notification method includes receiving, from a requesting source of an event, an event notification request for requesting notification of the event, the event notification request including event notification condition information including a notification condition of the event and priority information indicating a priority of notification of the event; acquiring the event from a publishing source of the event; determining whether to perform synchronous delivery of the event based on the notification condition; and notifying the requesting source of the event in an order of priority identified based on the priority information, when it is determined that synchronous delivery of the event be performed.

Claims (57)

1. An event notification method executed by a processor included in an event notification device provided with a display device, the event notification method comprising:

receiving a plurality of notification requests for requesting notification of an event, each of the plurality of notification requests including event notification condition information that includes a topic name related to the event, a callback function for acquiring the event, and priority information that includes a priority of notification of the event;

storing the plurality of notification requests into request information;

when a notification of the event is received, determining whether to perform synchronous delivery of the event based on a naming conversion of a topic name included in the notification of the event;

selecting one or more notification requests corresponding to the notification of the event from the request information when it is determined that the synchronous delivery of the event is to be performed, each of the selected one or more notification requests having a delivery destination of the synchronous delivery;

for the each of the selected one or more notification requests:

determining whether a method is set in the priority information;

converting the method into a numerical value when it is determined that the method is set in the priority information; and

setting an order of notification of the event based on the numerical value converted from the method set in the priority information;

notifying a plurality of requesting sources of the event by using the callback function included in the each of the selected plurality of notification requests, in accordance with the order of notification set for the each of the selected plurality of notification requests; and

displaying the notified event corresponding to each of the plurality of requesting sources on a screen of the display device in response to an instruction by each of the plurality of requesting sources.

2. The event notification method according to claim 1 , further comprising:

determining whether the priority information includes a value indicating that the event be discarded; and

discarding the event when it is determined that the priority information includes the value indicating that the event be discarded.

3. The event notification method according to claim 2 ,

wherein the value indicating that the event be discarded is a negative value.

4. The event notification method according to claim 2 ,

wherein the value indicating that the event be discarded is a value less than or equal to a given value.

5. The event notification method according to claim 1 , further comprising

executing a security check for a publishing source when the event is obtained from the publishing source,

wherein the notifying includes notifying a requesting source of the event when it is determined that the publishing source is under management of the event notification device, through the security check.

6. The event notification method according to claim 1 ,

wherein the event notification condition information further includes a callback function for calling a Subscribe method.

7. The event notification method according to claim 1 ,

wherein the determining includes determining whether to perform the synchronous delivery of the event in accordance with a naming conventions of a suffix of the topic name.

8. The event notification method according to claim 1 , wherein the determining includes:

determining that synchronous delivery of the event is to be performed when a suffix indicating synchronous delivery is included in information on a topic name included in the notification condition; and

determining that asynchronous delivery of the event is not to be performed when the suffix is not included in the information on the topic name.

9. The event notification method according to claim 8 , wherein the notifying includes:

performing notification of a plurality of events including event published from a publishing source to respective requesting sources according to an order in which the plurality of events arrive, when it is determined that synchronous delivery of the event is to be performed.

10. The event notification method according to claim 9 , further comprising:

setting a condition that if the priority in the priority information is a negative value, an update method does not have to be called, and

when determining that asynchronous delivery of the event is not to be performed, setting the priority to the negative value.

11. An event notification device, comprising:

a memory; and

a processor coupled to the memory and configured to:

receive a plurality of notification requests for requesting notification of an event, each of the plurality of notification requests including event notification condition information that includes a topic name related to the event, a callback function for acquiring the event, and priority information that includes a priority of notification of the event,

store the plurality of notification requests into request information,

when a notification of the event is received, determine whether to perform synchronous delivery of the event based on a naming conversion of the topic name included in the notification of the event,

select one or more notification requests corresponding to the notification of the event from the request information when it is determined that the synchronous delivery of the event is to be performed, each of the selected one or more notification requests having a delivery destination of the synchronous delivery,

for the each of the selected one or more notification requests:

determine whether a method is set in the priority information,

convert the method into a numerical value when it is determined that the method is set in the priority information, and

set an order of notification of the event based on the numerical value converted from the method set in the priority information,

notify a plurality of requesting sources of the event by using the callback function included in the each of the selected plurality of notification requests, in accordance with the order of notification set for the each of the selected plurality of notification requests, and

display the notified event corresponding to each of the plurality of requesting sources on a screen of the display device in response to an instruction by each of the plurality of requesting sources.

12. A non-transitory computer-readable storage medium storing a program that causes one or more processors included in a computer to execute a process, the process comprising:

receiving a plurality of notification requests for requesting notification of an event, each of the plurality of notification requests including event notification condition information that includes a topic name related to the event, a callback function for acquiring the event, and priority information that includes a priority of notification of the event;

storing the plurality of notification requests into request information;

when a notification of the event is received, determining whether to perform synchronous delivery of the event based on a naming conversion of a topic name included in the notification of the event;

selecting one or more notification requests corresponding to the notification of the event from the request information when it is determined that the synchronous delivery of the event is to be performed, each of the selected one or more notification requests having a delivery destination of the synchronous delivery;

for the each of the selected one or more notification requests:

determining whether a method is set in the priority information;

converting the method into a numerical value when it is determined that the method is set in the priority information; and

setting an order of notification of the event based on the numerical value converted from the method set in the priority information;

notifying a plurality of requesting sources of the event by using the callback function included in the each of the selected plurality of notification requests, in accordance with the order of notification set for the each of the selected plurality of notification requests; and

displaying the notified event corresponding to each of the plurality of requesting sources on a screen of the display device in response to an instruction by each of the plurality of requesting sources.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 11, 2016
From: HAYASHI, NARUKAZU; HAYASHI, KAZUHIRO; KOJIMA, MOTOAKI
To: FUJITSU LIMITED
Reel/Frame 037796/0272 →
Priority Claims (1)
JP 2015-036899 · Feb 26, 2015 · national
Continuity (1)
Related Publication 20160255165A1 · Sep 1, 2016