US20060106840A1 - System and method for tracking notifications in a publish subscribe system - Google Patents
System and method for tracking notifications in a publish subscribe system Download PDFInfo
- Publication number
- US20060106840A1 US20060106840A1 US10/981,184 US98118404A US2006106840A1 US 20060106840 A1 US20060106840 A1 US 20060106840A1 US 98118404 A US98118404 A US 98118404A US 2006106840 A1 US2006106840 A1 US 2006106840A1
- Authority
- US
- United States
- Prior art keywords
- channel
- message
- meta
- messages
- channels
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/55—Push-based network services
Definitions
- the present invention relates to publish/subscribe systems, and more particularly to a system for tracking notifications in a publish/subscribe system.
- the publish/subscribe communication paradigm describes a known form of interaction in distributed computing settings.
- a subscriber may register interest in or subscribe to events pertaining to a given topic; thereafter, the subscriber receives notifications of such events, which are produced by publishers.
- publishers or senders of data do not communicate directly with subscribers or receivers; instead, publishers and subscribers interact through an intermediate entity referred to here as a channel, but also known in the art by various other names, such as notification server, broker or event service.
- Publishers may publish notifications about the occurrence of the events on a channel by first marking these notifications with a particular topic. Subscribers receive notifications in the form of the messages from the channel for events that conform to the topic(s) in which they have registered interest. Since message producers (publishers) and consumers (subscribers) communicate indirectly with each other via a channel, message transmission is decoupled from message reception. As a consequence, neither producers nor consumers need to maintain state about each other, and dependencies between the interacting participants are reduced or eliminated.
- the publish/subscribe scheme is therefore more flexible than other communication paradigms, such as point-to-point messaging, because publishers and subscribers can be started and stopped asynchronously.
- the publish/subscribe mechanism is well suited to messaging systems in which many sensors monitor the dynamically changing state of some underlying system and forward measurement data to a central server site.
- the central server site which receives the measurement data, typically employs an application server that processes the information, stores it in a database, and provides an interface to an application user.
- processors become more and more inexpensive, and as advances are made in wireless communication, many simple sensors may be added to existing systems in order to enhance monitoring and management thereof.
- the sensors produce notifications about changes in state of the underlying system and therefore are modeled as publishers of particular types of events or topics.
- Sensors, in this context are modeled as publishers of particular types of events or topics, and the systems that monitor the events are modeled as subscribers.
- the term “event” refers to a change in state in the underlying system.
- sensors inform the application server about the occurrence of events through notification messages.
- Large, distributed systems may have many, many sensors, and the frequency at which they send notifications may be very high. For example, in an application that uses RFID tags to follow the movement of products in a supermarket, if every article pickup in every supermarket in a chain of stores is sent as a notification to the supermarket chain's back-end server, then the volume of notifications could rise to tens of thousands per second. Thus, an application server can become overloaded if every notification is delivered to it.
- an architectural entity may be placed between the sensors and the application server.
- This entity is termed an edge server, as it is logically located at the edge of the network.
- Edge servers pre-process raw sensor data and may aggregate information to enable certain sensor applications to be scalable.
- edge servers may intercept notifications, process them and send aggregations or summaries of the information they contain to the application server.
- Edge servers subscribe to channels on a given topic and may publish messages to application code on a potentially different channel on the same or a different topic.
- An application server or edge server “wants” to receive only the most condensed or aggregated form of a notification from a sensor; that is, there is no advantage in receiving both the “raw” notification and a summary of the many raw notifications in which it is included.
- edge server based architecture nevertheless raises a number of technical challenges. For one thing, deploying large numbers of edge servers means that failures of parts of the system typically occur so frequently that failure is the norm rather than the exception. This problem is exacerbated by the fact that edge servers often execute in a more hostile and less well-protected environment than application servers, in the sense that edge servers are typically deployed out “in the field” and are not as easily protected as within large, centralized server farms. In such cases, the failure of an edge server that normally collects data from many publishers (such as sensors or other edge servers) is problematic: in the absence of a means for the publishers to learn that they should now publish messages elsewhere, the data will typically be lost.
- a further challenge posed by known messaging systems is that the administration of the entire system becomes more complex with an edge server-based architecture. If a large number of edge servers are deployed, it is extremely difficult to configure each of them manually, so that all entities know to which channels they should subscribe and to which they should publish. Known systems are also difficult to reconfigure as loads change, or as edge servers or channels are stopped and started.
- the Applicant therefore believes that there is a need for more resilient and scalable tracking of notifications in publish/subscribe systems.
- a method for tracking notification messages from a message publisher to a message subscriber in a publish/subscribe system having one or more entities each configured as a message publisher, a channel and/or a message subscriber wherein the method comprises subscribing to a channel that describes the behavior of other channels in the system (from hereon referred to as a meta-channel); and receiving a digest of channel descriptions and/or transformation descriptions from the meta-channel to facilitate tracking of message transformations from raw forms to more processed forms.
- Messages or message descriptions in raw form may comprise raw data that has been collected or detected by an entity in the system such as a sensor, which may publish the raw data to another entity.
- Message transformations in more processed forms may comprise messages or message descriptions including data from a number of other entities that has been aggregated or including data from one or more entities that has been enriched or transformed in some way, depending on the application.
- the method of the invention may enable one of the entities to subscribe to a first channel in response to tracking certain message transformations.
- a subscription to a second channel may be dropped in response to determining that the first channel publishes one or more messages in a more processed form.
- the method may include publishing aggregated or transformed messages.
- the control messages that are published on the meta-channel are formatted in accordance with XML specifications.
- the method of the invention makes use of channel descriptions that describe channels and/or meta-channels.
- Information in the channel descriptions may be used in a manner that improves the resiliency and/or responsiveness of the system in which the invention operates. For example, if the load on the channel or meta-channel is communicated in the channel description the method enables an entity to discriminate between channels offering similar functionality in order to determine where to publish or subscribe, particularly if one of the channels is overloaded.
- Channel descriptions may also include information on the refresh rate or refresh period corresponding to the time between publications of a channel description.
- a channel or meta-channel may use the refresh rate to determine if another entity has stopped functioning, particularly upon nonreception of a channel description after a sufficiently long period compared to the refresh period.
- the meta-channel's refresh period may also be published to the channels it controls, whereupon the method of the invention adjusts the refresh period for the channels, thereby controlling the load on the meta-channel.
- a publish/subscribe system for tracking notification messages from a message publisher to a message subscriber.
- the system includes a plurality of entities that are operatively coupled to one another via an electronic network, and each entity includes at least one processor configured as a message publisher, a channel and/or a message subscriber.
- at least one entity is configured as a channel, which is assigned to the function of acting as a meta-channel and comprises (i) means for receiving one or more channel descriptions or transformation descriptions; and (ii) means for publishing a digest of channel descriptions or transformation descriptions to facilitate tracking of message transformations from raw forms to processed forms.
- the system may have more than one meta-channel, and the meta-channels may subscribe to or publish to each other.
- an apparatus for tracking notification messages from a message publisher to a message subscriber, wherein the apparatus comprises at least one processor operative to: (i) subscribe to a first message publisher to receive a digest of channel descriptions; and (ii) determine whether a second message publisher publishes one or more notifications in an aggregated form. If the second message publisher publishes the one or more notifications in a more aggregated form, the processor is operative to subscribe to the second message publisher.
- the present invention may be implemented in a variety of ways, as those who are skilled in the art will recognize. It will find particular application in distributed data processing system that uses publication/subscribe messaging. Furthermore, as described in further detail below, and with reference to the accompanying drawings, the invention enables entities within a messaging system to dynamically track notifications in order to receive the most aggregated form of a notification. Thus, the invention achieves both resiliency and scalability, particularly for applications and processors that operate within a large distributed system.
- FIG. 1 is a block diagram of a distributed information handling system capable of implementing the present invention
- FIG. 2 shows schematically the relationship between channels and meta-channels according to a preferred embodiment of the invention
- FIG. 3 is a schematic diagram illustrating the relationship between publishers and subscribers according to a preferred embodiment of the invention.
- FIGS. 4A, 4B , 4 C and 4 D illustrate schematically how message transformations are tracked according to a preferred embodiment of the invention.
- the invention may be used in a distributed system wherein sensors are employed to monitor the state of an underlying system and forward measurement data to a central server.
- Example applications of such a messaging system include flood warning applications that monitor water levels in water ways, inventory management applications that track the location and number of goods using radio frequency identification (RFID), or automotive traffic warning schemes that monitor the behavior of vehicles in order to detect and predict congestion.
- RFID radio frequency identification
- the invention may be implemented in a messaging system that uses sensors which may be very limited in their ability to learn about where they should publish their messages or to learn about the evolution of the messaging system as channels move, fail, get switched off, are re-configured, etc.
- the sensors may execute in an environment in which they cannot be externally powered. They may depend on internal batteries and may have to be very simple to reduce their power consumption. They may have the capability to communicate among themselves or to subscribe to a channel to learn about where they should publish their messages, or, alternatively, they may simply broadcast or transmit messages to a preconfigured destination.
- the distributed system 10 preferably includes sensors 20 - 44 , data channels 50 , 60 , edge servers 70 , 80 , application server 90 and database 100 .
- Sensors 20 - 44 , edge servers 70 , 80 and application servers 90 communicate through one or more messaging channels using one or more different technologies.
- Event data may be gathered by sensors 20 - 44 and forwarded to channels 50 , 60 , each of which preferably supports a publish/subscribe mode of interaction.
- Channels 50 , 60 may publish messages 11 , 120 about the events to application code 130 , 140 , 150 running on edge servers 70 , 80 , which are intermediate computation platforms in which data may be processed, filtered and/or reformatted before arriving at an ultimate destination.
- Application code 130 , 140 , 150 running on an edge server 70 , 80 may read from one or more channels 50 , 60 , process the messages, and transform, enrich or aggregate the data received in the message(s).
- edge servers 70 , 80 preferably perform at least some preprocessing of raw data before forwarding messages in more processed forms toward an application server 90 .
- sensors e.g., 20 - 26
- application code 1300 runs on edge server 70 , reads messages 10 from channel 50 and writes processed messages 170 to an application server 90 .
- sensors 30 - 38 send messages 180 - 188 to a second channel 60 on a second edge server 80 on which application code 140 , 150 resides.
- Application code 130 may process messages 110 , 190 that are received from both channel 50 and second channel 60 and may then publish aggregated or transformed messages 200 to the second channel 60 .
- Application code 150 on the second channel 60 may process messages 120 and/or further process messages 200 received at the second edge server 80 and may then write processed messages 210 to software components such as message beans 220 , 222 running on application server 90 .
- the application server 90 comprises a software platform that may run over one or more machines.
- the main application runs on the application server 90 , which may interact with end users.
- a channel (e.g., 50 ) may run on an edge server 70 as illustrated in FIG. 1 or may be supported by an application server (e.g., 90 ) or even by a sensor (e.g. 20 ).
- Data channels 50 , 60 may be supported by different messaging technologies known by those of ordinary skill in the art, such as for example the IBM® WebSphere® MQSeries® middleware system or the CORBA® (Common Object Request Broker Architecture) Notification Service.
- IBM, WebSphere and MQSeries are trademarks of International Business Machines Corporation in the United States, other countries, or both.
- CORBA is a trademark of Object Management Group, Inc. in the United States and/or other countries.
- CORBA refers to a suite of specifications issued by the Object Management Group, Inc. (OMG), for an architecture and infrastructure that computer applications use to work together over networks. The OMG maintains the specifications along with other current documentation at their web site, http://www.omg.org. It is anticipated that the specifications for CORBA
- each channel 250 , 260 within the system 10 is associated with a channel controller 270 , 280 , which extracts control information about a channel 250 , 260 and may publish it periodically to another channel e.g., 290 .
- the channel controller may reside within the same process as the channel or within an entirely different process.
- a given process may contain one or more controllers for one or more channels, but preferably a channel controller 270 , 280 resides on the same machine 300 , 310 as the channel it controls ( 250 , 260 , respectively) to reduce the possibility of inconsistency within the system 10 .
- a channel controller 270 , 280 may determine which topics are available on its underlying channel 250 , 260 either by using mechanisms in the underlying channel such as, for example, the offer list in the CORBA Notification Service, or by interacting with the channel as a normal subscriber, e.g., by sampling traffic.
- the invention uses one or more meta-channels 290 to facilitate the ability of a channel controller 270 to publish control information or control messages to other channels 260 in the network.
- a meta-channel 290 carries information about other channels 250 , 260 and is similar to them in that it supports publish/subscribe interaction.
- a meta-channel 290 may carry only control information or it may also be simultaneously used for carrying normal data messages. Participants in the messaging system that are interested in producing or subscribing to data messages may first subscribe to a meta-channel.
- a consumer may select control information using a standard subscription mechanism and may use the meta-channel 290 to determine the location of a channel where messages of a type the consumer is interested in are being produced, as will be described in further detail below.
- Producers such as channel controllers 270 , 280 may publish channel description information 330 , 340 on a meta-channel 290 .
- a producer e.g., 320
- a meta-channel 290 may therefore use publication/subscribe semantics to distribute control messages 350 about the state of data channels (e.g., 250 , 260 ).
- meta-channel 290 may be used, i.e., meta-channels may be distributed across several entities in the system 10 and may prevent situations in which a single meta-channel becomes a bottleneck. If more than one meta-channel is used, each one may distribute control messages to each other using publication/subscribe messaging.
- each message has a type that is identified by a simple string in order to allow the same mechanisms to be used to control channels that may be supported by different messaging technologies, even though the underlying technologies may support richer typing information.
- Message types identified by simple strings may be directly mapped to subjects on subject-based messaging systems.
- the invention does not require data channels 250 , 260 and control channels (such as, e.g., meta-channel 290 ) to use the same messaging technology.
- a data channel may use a messaging system that uses consume semantics, so that its messages are retained until exactly one consumer receives messages from that data channel, while a mechanism such as a CORBA notification channel may be used to broadcast control information to many subscribers.
- a channel controller may publish channel description information on a meta-channel 290 .
- a channel description may contain information such as: the type of messaging system that is being used; information that is needed to connect to the channel 260 (e.g., address, port); the message type or types that the channel 260 accepts; the message type or types that are currently being published and subscribed to; the load and refresh rate (discussed in further detail below); etc.
- the channel description information can enhance the responsiveness and resiliency of the system in a number of ways.
- Load information in a channel description pertaining to the load on the channel may enable another entity in the system to discriminate between channels offering similar functionality.
- Load information may indicate, for instance, the number of subscribers and/or publishers that subscribe to and/or publish to the channel.
- Load information may be expressed in terms of memory usage, such as by indicating memory consumption as a percentage of the maximum memory, which may be calculated over a time window.
- a message-producing channel may be overloaded and may be able to communicate this fact to other entities via the load information in its channel description.
- a message consumer or publisher that receives the channel description may, upon learning of the heavy load, make the determination to subscribe or publish, respectively, to another channel that is experiencing a lighter load.
- the refresh rate refers to a time period in between publications of a channel description. This time period may be used to help a message receiver determine whether a channel has failed. For example, a receiver might normally expect to receive a channel description every N seconds, where N is announced in the channel description as the refresh period or refresh rate. If the receiver does not receive a channel description in a time period that is proportional to the time period in the previously received channel description, then the receiver may infer that the channel has failed (i.e., if the receiver does not receive a channel description after, say, 2N seconds, the receiver may determine that the channel has failed).
- the information in the channel description may be sent in the form of an electronic document, preferably in a standard format to facilitate the exchange of data across a variety of platforms, such as an eXtensible Markup Language (XML) document.
- XML is based on a well-documented standards-based technology defined by the World Wide Web Consortium (W3C).
- W3C World Wide Web Consortium
- a standard format such as XML is preferred because it may be used even if producers and consumers in the distributed network use different publication/subscribe messaging technologies. Additional information may also be added to messages to aid filtering in specific technologies. For example, if channel descriptions contain information about the message types supported by the channels, then consumers may specify that they are interested only in information about channels carrying messages of a particular type.
- JMS Java Message Service
- the JMS message may include information about the message type(s) in the properties field.
- JMS is a specification for a common API for enterprise messaging. The JMS specification is available on the Web at http://www.java.sun.com. Java is a trademark of Sun Microsystems, Inc. in the United States and other countries. Those of ordinary skill in the art will recognize other ways of conveying message type information when using other publication/subscribe messaging technologies.
- the distributed messaging system 10 may employ more than one meta-channel 290 in order to aid in scalability and resiliency.
- Each meta-channel 290 has a meta-channel controller 370 to enable control information available on one meta-channel 290 to be communicated to other meta-channels 360 .
- a meta-channel controller 370 may create a digest (not shown) about all the channel descriptions on the meta-channel 290 it controls and may publish the digest 380 on other meta-channels 360 , including its own 290 .
- the digest preferably contains a list of channel descriptions of data channels 250 , 260 as well as a channel description of meta-channel 290 .
- Channel controllers 270 , 280 may use the digest as a confirmation that their control information 330 , 340 is being read. They may also use digest information 380 pertaining to the meta-channel controller 370 , such as the refresh period, to guide their behavior and/or the content of their own control messages 330 , 340 . If channel controllers 270 , 280 use the refresh period from the channel description of the meta-channel controller 290 as a minimum for their own control messages, the meta-channel controller 290 can apply back pressure to the channel controllers 270 , 280 to reduce their sending rate.
- channel controller 270 may adjust the refresh period for its channel 250 down to 3N seconds.
- the system 10 can adapt its responsiveness as a function of the load on the meta-channels (e.g., 290 ).
- a channel controller 270 may also subscribe to the meta-channel 290 to learn about another, possibly more appropriate, meta-channel 360 for publication of its controller information 330 .
- Another meta-channel controller 390 may subscribe to the meta-channel controller 370 to learn about other meta-channels in the system 10 . All the entities in the system preferably use a softstate model, described in greater detail below, such that information is periodically refreshed.
- FIG. 2 demonstrates publishers such as sensors 400 and 402 publishing messages 410 , 412 about events of type X and Y respectively, on channels 250 and 260 , respectively.
- Channel controllers 270 and 280 report the events by publishing 330 and 340 , respectively, on their associated meta-channel 290 .
- Meta channel 290 may forward a digest of the event information 380 to other known meta-channels 360 .
- edge server 320 may contain a software platform on which another data channel or meta-channel runs, and/or it may forward data, after preprocessing and/or aggregating the data, toward another edge server or an application server (not shown).
- Edge server 320 subscribes to meta-channel 290 and thereby eventually learns about event type Y, of which edge server 320 has interest.
- Edge server 320 may then subscribe 420 to channel 260 to obtain updates on events of type Y.
- Application code running on edge server 320 may process data, including message data about event Y ( 420 ), to produce and publish messages about events of type Z ( 430 ), as further illustrated in FIG. 4 .
- Messages about events of type Z may be aggregations or transformations of data received at edge server 320 . If events of type Z are published 430 to channel 260 , the associated channel controller 280 may update and publish its channel description 440 on meta-channel 290 . Meta-channel controller 370 may forward this information 450 to other meta-channels 360 .
- Edge server 320 may thus consume messages from publishers such as sensors or other edge servers, which may function as data channels or meta-channels.
- an edge server 320 may use message data (e.g., 420 ) to produce new messages 430 , as described above with respect to FIG. 3 , which the edge server 320 may make available to other edge servers or to an application server.
- an edge server may take a set of messages containing information about temperature measured at sensors in order to produce an aggregated message containing an average temperature.
- an edge server may process raw data by transforming or enriching it.
- edge server 320 may receive one or more messages containing global positioning system (GPS) data and may transform the GPS data into a location on a map, e.g. a street name. The map is an example of a message transformation that the edge server 320 may then publish in the form of a new message.
- GPS global positioning system
- An edge server 320 may learn from a meta-channel 290 about channels (e.g., 250 , 260 ) on which information of interest to it is currently available, as described above with respect to FIG. 2 .
- the edge server 320 may make local decisions based on currently available information (e.g., 350 ) about available resources, to determine from what subset of the available channels the edge server 320 should consume messages.
- edge server 320 may determine locally to which channels (e.g., 260 ) it should place new messages that result from preprocessing performed at the edge server 320 . Decisions made at the edge server 320 may change over time as channels (e.g., 250 , 260 ) come and go and as resource usage fluctuates.
- the edge server 320 may produce aggregated messages which in turn may be further processed to produce even more aggregated messages.
- multiple different messaging technologies may co-exist within one system, as messages ay be read or received according to one messaging scheme and may be processed, aggregated and sent out according to a different mechanism.
- An important aspect of the invention is to allow entities (such as edge server 320 ) of the messaging system 10 to dynamically determine where they should subscribe in order to receive the most aggregated form of a notification.
- the invention enables message consumers to learn (i) where messages of a given type are being produced, (ii) whether these messages have already been transformed or produced to a more aggregated form, and (iii) if so, to where the transformed or aggregated messages are being published.
- message consumers must be able to track the evolution of these message transformations as they change over time.
- an entity such as an edge server may consume messages from a channel or set of channels and use the messages to produce new messages that it may send to another channel or set of channels.
- the edge server preferably publishes this information to a meta-channel using a transformation description message. That is, the edge server publishes the fact that it is subscribing to notifications about a topic on one channel and is using the notification information to produce notifications about another topic on potentially another channel, as will be described in further detail below with regard to FIG. 4 .
- the transformation description message containing this information is preferably treated as a softstate model, i.e., the information must be refreshed regularly, or it will expire.
- the transformation description message is similar to the channel description message described above, in that it is preferably an XML document, and it may provide information including: (i) a set of channel name and message-type pairs for all the messages that the edge server 320 is reading; (ii) a set of channel name and message-type pairs for all the messages that the edge server 320 is writing; (iii) a refresh period; etc. Additional tags may also be added to the technology specific message format in which the XML document is being transported to aid in filtering.
- a message consumer may subscribe to a meta-channel to receive information, not only about the channels on which messages of a given type are being published, but also about any transformations of those messages.
- a message publisher such as an edge server may produce multiple aggregated or transformed messages from the same input: for example, an edge server may produce a message containing an average of a set of temperature readings and may produce another message containing the range of a set of temperature readings.
- FIG. 4 describes an example application in which the invention may be used to help in the monitoring of temperature data detected by sensors 500 , 502 located in a particular environment in order to determine, say, an average temperature.
- sensors 500 , 502 send one or more temperature readings 510 , 512 to Channel 1 ( 550 ), which sends control information 560 about the temperature data to which it subscribes to meta-channel 590 .
- FIG. 4B illustrates meta-channel 590 sending control information 600 to an application server or edge server 610 , which subscribes to meta-channel 590 in order to learn about other channels in the system 10 .
- Application server 610 which has the task of determining an average of the temperatures detected by sensors 500 , 502 , subscribes 620 to Channel 1 ( 550 ). Not shown is the fact that application server 610 may also be subscribing to many other channels to receive raw temperature data, in order to be able to determine an average temperature detected by many sensors.
- another application server or edge server 630 subscribes 640 to Channel 1 ( 550 ) to obtain temperature data 510 , 512 .
- Application server 630 also receives other temperature data (not shown) from other sensors or channels in the system 10 and computes an average temperature based on the temperature from Channel 1 ( 550 ) and from other temperature data producers.
- Application server 630 then publishes the average temperature 650 to Channel 2 ( 660 ).
- the average temperature represents a message transformation, i.e., a message about data that has been aggregated or transformed based on raw data received from one or more entities within the system.
- Application server 630 also publishes a transformation description message in the form of control information 670 to meta-channel 590 , as illustrated schematically in FIG. 4D .
- Control information 670 includes: (i) a description of the events to which application server 630 subscribes (such as temperature data from Channel 1 ), and (ii) a notification that application server 630 is publishing ( 650 ) aggregated temperature data to Channel 2 ( 660 ).
- Channel 2 ( 660 ) is capable of storing the average temperature in memory and is also capable of publishing the average temperature.
- Meta-channel 590 publishes another control message (e.g., 600 ) to its subscribers, including application server 610 .
- application server 610 is now aware that Channel 2 ( 660 ) publishes the average temperature.
- Application server 610 drops the subscription 620 to Channel 1 ( 550 ) and subscribes 670 to Channel 2 ( 660 ).
- application server 610 may now drop a number of other subscriptions it may have had with other publishers, because now application server 610 can obtain aggregated data from a single producer, 660 .
- Application server may also further process the aggregated data, by enriching or transforming it, and may publish the further message transformations on one or more other channels.
- additional channels may further aggregate or process the message transformations (such as the average temperature in the above example) that are available at Channel 2 ( 660 ) and/or application server 630 .
- Control information may be refreshed periodically so that updated information becomes available as data changes or as entities stop or start interacting within the messaging system. Therefore, as discussed above, channel controllers and meta-channel controllers may publish in their summary descriptions the refresh rates at which control data should be resent. Publication of these refresh periods allows the controllers to apply back pressure to prevent channels within the system from becoming clogged or overburdened with control information. A frequent refresh rate may be desirable in order to improve the reactivity of the system in response to change. This objective, however, should be weighed against the higher control overhead that accompanies a higher refresh rate. Thus, for example, for some applications a refresh period on the order of many seconds may be preferable in order to reduce effects of queuing and/or propagation delays.
- processor as used herein is intended to include any processing device, such as, for example, one that includes a CPU (central processing unit).
- memory as used herein is intended to include memory associated with a processor or CPU, such as, for example, RAM, ROM, a fixed memory device (e.g., hard drive), a removable memory device (e.g., diskette), etc. It is also to be understood that various elements associated with a processor may be shared by other processors.
- software components including instructions or code for performing the methodologies of the invention, as described herein, may be stored in one or more of the associated memory devices (e.g., ROM, fixed or removable memory) and, when ready to be utilized, loaded in part or in whole (e.g., into RAM) and executed by a CPU.
- ROM read-only memory
- RAM random access memory
- the methods in accordance with the present invention may therefore be implemented at least partially using software, e.g., computer programs and the invention may provide computer software specifically adapted to carry out the methods described above when installed on data processing means.
- the present invention may be embodied as a computer program product for use with a computer system.
- Such an implementation may comprise a series of computer readable instructions either fixed on a tangible medium, such as a computer readable medium, or transmittable to a computer system, via a modem or other interface device, over either a tangible medium such as optical or analogue communications lines, or intangibly using wireless transmission techniques.
- the series of computer readable instructions embodies all or part of the functionality previously described herein.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Information Transfer Between Computers (AREA)
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/981,184 US20060106840A1 (en) | 2004-11-04 | 2004-11-04 | System and method for tracking notifications in a publish subscribe system |
CN200510120133.3A CN1848732B (zh) | 2004-11-04 | 2005-11-04 | 在发布预订系统中跟踪通知的系统和方法 |
US11/943,567 US8165992B2 (en) | 2004-11-04 | 2007-11-20 | System and method for tracking notifications in a publish subscribe system |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/981,184 US20060106840A1 (en) | 2004-11-04 | 2004-11-04 | System and method for tracking notifications in a publish subscribe system |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/943,567 Continuation US8165992B2 (en) | 2004-11-04 | 2007-11-20 | System and method for tracking notifications in a publish subscribe system |
Publications (1)
Publication Number | Publication Date |
---|---|
US20060106840A1 true US20060106840A1 (en) | 2006-05-18 |
Family
ID=36387682
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/981,184 Abandoned US20060106840A1 (en) | 2004-11-04 | 2004-11-04 | System and method for tracking notifications in a publish subscribe system |
US11/943,567 Expired - Fee Related US8165992B2 (en) | 2004-11-04 | 2007-11-20 | System and method for tracking notifications in a publish subscribe system |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/943,567 Expired - Fee Related US8165992B2 (en) | 2004-11-04 | 2007-11-20 | System and method for tracking notifications in a publish subscribe system |
Country Status (2)
Country | Link |
---|---|
US (2) | US20060106840A1 (zh) |
CN (1) | CN1848732B (zh) |
Cited By (24)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20100057867A1 (en) * | 2008-09-02 | 2010-03-04 | Alibaba Group Holding Limited | Method and System for message processing |
US20110225229A1 (en) * | 2010-03-11 | 2011-09-15 | Yahoo! Inc. | Distributed publish/subscribe system |
US20140064258A1 (en) * | 2012-08-31 | 2014-03-06 | Bruce C. Montag | Information Handling System Proximity-Based Wireless Interface Connectivity |
US20170078423A1 (en) * | 2015-09-10 | 2017-03-16 | International Business Machines Corporation | Sensor-driven eventing and two stage notification |
US20170180289A1 (en) * | 2015-12-18 | 2017-06-22 | Amazon Technologies, Inc. | Publish-Subscribe Message Transformation |
US9699260B2 (en) | 2015-08-07 | 2017-07-04 | Machine Zone, Inc. | Scalable, real-time messaging system |
US9838340B2 (en) | 2015-10-09 | 2017-12-05 | Machine Zone, Inc. | Systems and methods for storing message data |
US9843551B2 (en) | 2015-10-09 | 2017-12-12 | Machine Zone, Inc. | Systems and methods for storing and transferring message data |
US9843640B2 (en) | 2015-08-07 | 2017-12-12 | Machine Zone, Inc. | Scalable, real-time messaging system |
US9860186B1 (en) | 2016-07-06 | 2018-01-02 | Machine Zone, Inc. | Multiple-speed message channel of messaging system |
US9871750B2 (en) | 2016-05-16 | 2018-01-16 | Satori Worldwide, Llc | Maintaining persistence of a messaging system |
US9876745B2 (en) | 2015-10-16 | 2018-01-23 | Satori Worldwide, Llc | Systems and methods for transferring message data |
US20180063039A1 (en) * | 2016-08-23 | 2018-03-01 | Machine Zone, Inc. | Scalable, real-time messaging system |
US9942339B1 (en) | 2016-09-23 | 2018-04-10 | Satori Worldwide, Llc | Systems and methods for providing messages to multiple subscribers |
US9967203B2 (en) | 2016-08-08 | 2018-05-08 | Satori Worldwide, Llc | Access control for message channels in a messaging system |
CN108494815A (zh) * | 2018-02-06 | 2018-09-04 | 北京极智感科技有限公司 | 一种传输消息的方法和系统 |
US10187278B2 (en) | 2017-02-24 | 2019-01-22 | Satori Worldwide, Llc | Channel management in scalable messaging system |
US10270726B2 (en) | 2017-02-24 | 2019-04-23 | Satori Worldwide, Llc | Selective distribution of messages in a scalable, real-time messaging system |
US20190132276A1 (en) * | 2017-11-02 | 2019-05-02 | Sap Se | Unified event processing for data/event exchanges with existing systems |
US10305981B2 (en) | 2016-08-31 | 2019-05-28 | Satori Worldwide, Llc | Data replication in scalable messaging system |
US10404647B2 (en) | 2016-06-07 | 2019-09-03 | Satori Worldwide, Llc | Message compression in scalable messaging system |
US10447623B2 (en) | 2017-02-24 | 2019-10-15 | Satori Worldwide, Llc | Data storage systems and methods using a real-time messaging system |
US20190356622A1 (en) * | 2018-05-17 | 2019-11-21 | Honeywell International Inc. | Rule-based annotation service in a cloud platform |
US10986203B2 (en) * | 2019-02-08 | 2021-04-20 | American Express Travel Related Services Company, Inc. | Balancing and control framework for real-time processing |
Families Citing this family (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102388621B (zh) * | 2009-02-05 | 2016-08-03 | 普尔帕康有限公司 | 基于元信道的媒体系统控制技术 |
US9372739B2 (en) | 2011-04-20 | 2016-06-21 | International Business Machines Corporation | Monitoring of subscriber message processing in a publish/subscribe messaging environment |
US9742651B2 (en) | 2015-03-05 | 2017-08-22 | International Business Machines Corporation | Client-side fault tolerance in a publish-subscribe system |
US9800648B2 (en) | 2015-03-05 | 2017-10-24 | International Business Machines Corporation | Channel ownership in a publish-subscribe system |
US10666712B1 (en) * | 2016-06-10 | 2020-05-26 | Amazon Technologies, Inc. | Publish-subscribe messaging with distributed processing |
US11429290B2 (en) | 2020-11-13 | 2022-08-30 | Argo AI, LLC | Methods and systems for providing a lockless access to a shared memory region in a publish and subscribe system |
US11363099B2 (en) | 2020-11-13 | 2022-06-14 | Argo AI, LLC | Methods and systems for enabling publish-subscribe message transmission in a distributed environment |
US11709620B2 (en) | 2020-11-13 | 2023-07-25 | Ford Global Technologies, Llc | Methods and systems for memory management in a publish and subscribe system |
Citations (17)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6333931B1 (en) * | 1998-12-28 | 2001-12-25 | Cisco Technology, Inc. | Method and apparatus for interconnecting a circuit-switched telephony network and a packet-switched data network, and applications thereof |
US6336135B1 (en) * | 1996-05-24 | 2002-01-01 | International Business Machines Corporation | Gateway for converting synchronous client/server protocols into asynchronous messaging protocols and storing session state information at the client |
US6442169B1 (en) * | 1998-11-20 | 2002-08-27 | Level 3 Communications, Inc. | System and method for bypassing data from egress facilities |
US20030131142A1 (en) * | 2001-03-14 | 2003-07-10 | Horvitz Eric J. | Schema-based information preference settings |
US20030149792A1 (en) * | 2002-02-06 | 2003-08-07 | Leonid Goldstein | System and method for transmission of data through multiple streams |
US20040002988A1 (en) * | 2002-06-26 | 2004-01-01 | Praveen Seshadri | System and method for modeling subscriptions and subscribers as data |
US20040039964A1 (en) * | 2002-08-21 | 2004-02-26 | International Business Machines Corporation | Programmatically serializing complex objects using self-healing techniques |
US20040205613A1 (en) * | 2001-07-17 | 2004-10-14 | International Business Machines Corporation | Transforming data automatically between communications parties in a computing network |
US6807558B1 (en) * | 1995-06-12 | 2004-10-19 | Pointcast, Inc. | Utilization of information “push” technology |
US6816862B2 (en) * | 2001-01-17 | 2004-11-09 | Tiax Llc | System for and method of relational database modeling of ad hoc distributed sensor networks |
US20040257896A1 (en) * | 2003-06-18 | 2004-12-23 | Jeung Seong-Ho | Semiconductor memory device and method of reading data from the semiconductor memory device |
US20050138432A1 (en) * | 1997-02-12 | 2005-06-23 | Ransom Douglas S. | System and method for routing power management via XML firewall |
US20050198299A1 (en) * | 2004-01-26 | 2005-09-08 | Beck Christopher Clemmett M. | Methods and apparatus for identifying and facilitating a social interaction structure over a data packet network |
US20060085412A1 (en) * | 2003-04-15 | 2006-04-20 | Johnson Sean A | System for managing multiple disparate content repositories and workflow systems |
US7091902B2 (en) * | 2003-12-17 | 2006-08-15 | Xerox Corporation | Systems and methods for characterizing the coverage of ad hoc sensor networks |
US7177881B2 (en) * | 2003-06-23 | 2007-02-13 | Sony Corporation | Network media channels |
US7224984B2 (en) * | 2000-08-15 | 2007-05-29 | University Of Maryland, College Park | Method, system and computer program product for positioning and synchronizing wireless communications nodes |
Family Cites Families (58)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4020473A (en) * | 1964-03-11 | 1977-04-26 | Eiji Fujimura | Automatic system for providing telephone number information service |
US4965825A (en) * | 1981-11-03 | 1990-10-23 | The Personalized Mass Media Corporation | Signal processing apparatus and methods |
US6850252B1 (en) * | 1999-10-05 | 2005-02-01 | Steven M. Hoffberg | Intelligent electronic appliance system and method |
US5400325A (en) * | 1993-06-29 | 1995-03-21 | Synoptics Communications, Inc. | Method and apparatus providing for hunt groups in an ATM network of the like |
US5919247A (en) * | 1996-07-24 | 1999-07-06 | Marimba, Inc. | Method for the distribution of code and data updates |
US6173191B1 (en) * | 1997-12-31 | 2001-01-09 | Mdivesity Inc. | Localization of shaped directional transmitting and transmitting/receiving antenna array |
US7430257B1 (en) * | 1998-02-12 | 2008-09-30 | Lot 41 Acquisition Foundation, Llc | Multicarrier sub-layer for direct sequence channel and multiple-access coding |
US7233948B1 (en) * | 1998-03-16 | 2007-06-19 | Intertrust Technologies Corp. | Methods and apparatus for persistent control and protection of content |
US6256664B1 (en) * | 1998-09-01 | 2001-07-03 | Bigfix, Inc. | Method and apparatus for computed relevance messaging |
US6738975B1 (en) * | 1998-11-18 | 2004-05-18 | Software Ag, Inc. | Extensible distributed enterprise application integration system |
US6256676B1 (en) * | 1998-11-18 | 2001-07-03 | Saga Software, Inc. | Agent-adapter architecture for use in enterprise application integration systems |
AU5728500A (en) * | 1999-06-11 | 2001-01-02 | Microsoft Corporation | Data driven remote device control model with general programming interface-to-network messaging adapter |
US6859831B1 (en) * | 1999-10-06 | 2005-02-22 | Sensoria Corporation | Method and apparatus for internetworked wireless integrated network sensor (WINS) nodes |
US6832251B1 (en) * | 1999-10-06 | 2004-12-14 | Sensoria Corporation | Method and apparatus for distributed signal processing among internetworked wireless integrated network sensors (WINS) |
US6735630B1 (en) * | 1999-10-06 | 2004-05-11 | Sensoria Corporation | Method for collecting data using compact internetworked wireless integrated network sensors (WINS) |
US7020701B1 (en) * | 1999-10-06 | 2006-03-28 | Sensoria Corporation | Method for collecting and processing data using internetworked wireless integrated network sensors (WINS) |
US6826607B1 (en) * | 1999-10-06 | 2004-11-30 | Sensoria Corporation | Apparatus for internetworked hybrid wireless integrated network sensors (WINS) |
KR100353861B1 (ko) * | 1999-11-11 | 2002-09-26 | 한국전자통신연구원 | 주파수 매핑 근사 함수를 이용한 광대역 주파수 자동 채널선택 장치 및 그 방법 |
US6466937B1 (en) * | 2000-03-10 | 2002-10-15 | Aether Systems, Inc. | System, method and apparatus for utilizing transaction databases in a client-server environment |
WO2001076120A2 (en) * | 2000-04-04 | 2001-10-11 | Stick Networks, Inc. | Personal communication device for scheduling presentation of digital content |
US6950875B1 (en) * | 2000-05-09 | 2005-09-27 | Sun Microsystems, Inc. | Message conductors in a distributed computing environment |
US6789126B1 (en) * | 2000-05-09 | 2004-09-07 | Sun Microsystems, Inc. | Addressing message gates in a distributed computing environment |
US7577834B1 (en) * | 2000-05-09 | 2009-08-18 | Sun Microsystems, Inc. | Message authentication using message gates in a distributed computing environment |
US6643650B1 (en) * | 2000-05-09 | 2003-11-04 | Sun Microsystems, Inc. | Mechanism and apparatus for using messages to look up documents stored in spaces in a distributed computing environment |
US7248841B2 (en) * | 2000-06-13 | 2007-07-24 | Agee Brian G | Method and apparatus for optimization of wireless multipoint electromagnetic communication networks |
US7162454B1 (en) * | 2000-07-24 | 2007-01-09 | Donner Irah H | System and method for reallocating and/or upgrading and/or selling tickets, other even admittance means, goods and/or services |
US7031945B1 (en) * | 2000-07-24 | 2006-04-18 | Donner Irah H | System and method for reallocating and/or upgrading and/or rewarding tickets, other event admittance means, goods and/or services |
US6819669B2 (en) * | 2000-07-26 | 2004-11-16 | International Business Machines Corporation | Method and system for data communication |
US6704024B2 (en) * | 2000-08-07 | 2004-03-09 | Zframe, Inc. | Visual content browsing using rasterized representations |
WO2002021413A2 (en) * | 2000-09-05 | 2002-03-14 | Zaplet, Inc. | Methods and apparatus providing electronic messages that are linked and aggregated |
US7171487B2 (en) * | 2000-09-22 | 2007-01-30 | International Business Machines Corporation | Method and system for application specific packet forwarding |
US7171475B2 (en) * | 2000-12-01 | 2007-01-30 | Microsoft Corporation | Peer networking host framework and hosting API |
CN1168032C (zh) * | 2001-04-27 | 2004-09-22 | 黎明网络有限公司 | 一种实现多业务数据交换的方法及其装置 |
US7188106B2 (en) * | 2001-05-01 | 2007-03-06 | International Business Machines Corporation | System and method for aggregating ranking results from various sources to improve the results of web searching |
JP3980413B2 (ja) * | 2001-06-05 | 2007-09-26 | インターナショナル・ビジネス・マシーンズ・コーポレーション | 接続選択方法および通信エンドポイント装置 |
US7421411B2 (en) * | 2001-07-06 | 2008-09-02 | Nokia Corporation | Digital rights management in a mobile communications environment |
US7406647B2 (en) * | 2001-12-06 | 2008-07-29 | Pulse-Link, Inc. | Systems and methods for forward error correction in a wireless communication network |
US7340214B1 (en) * | 2002-02-13 | 2008-03-04 | Nokia Corporation | Short-range wireless system and method for multimedia tags |
US7551629B2 (en) * | 2002-03-28 | 2009-06-23 | Precache, Inc. | Method and apparatus for propagating content filters for a publish-subscribe network |
US7627603B2 (en) * | 2002-03-28 | 2009-12-01 | Precache Inc. | Method and apparatus for implementing query-response interactions in a publish-subscribe network |
US7672275B2 (en) * | 2002-07-08 | 2010-03-02 | Precache, Inc. | Caching with selective multicasting in a publish-subscribe network |
US7305084B2 (en) * | 2002-07-24 | 2007-12-04 | Qualcomm Incorporated | Fast encryption and authentication for data processing systems |
US20080313282A1 (en) * | 2002-09-10 | 2008-12-18 | Warila Bruce W | User interface, operating system and architecture |
US7190678B2 (en) * | 2002-10-28 | 2007-03-13 | Cisco Technology, Inc. | Arrangement for router attachments between roaming mobile routers in a clustered network |
US7606939B1 (en) * | 2002-10-31 | 2009-10-20 | Cisco Technology, Inc. | Scaling private virtual local area networks (VLANs) across large metropolitan area networks (MANs). |
US7460473B1 (en) * | 2003-02-14 | 2008-12-02 | Istor Networks, Inc. | Network receive interface for high bandwidth hardware-accelerated packet processing |
US7019637B1 (en) * | 2003-03-28 | 2006-03-28 | Sandia National Laboratories | Systems and methods for detecting and processing |
US7188026B2 (en) * | 2003-05-12 | 2007-03-06 | Dash Navigation, Inc. | Hierarchical floating car data network |
US7076365B2 (en) * | 2003-05-12 | 2006-07-11 | Circumnav Networks, Inc. | Enhanced dead reckoning method |
US6925378B2 (en) * | 2003-05-12 | 2005-08-02 | Circumnav Networks, Inc. | Enhanced mobile communication device with extended radio, and applications |
US6862500B2 (en) * | 2003-05-12 | 2005-03-01 | Circumnav Networks, Inc. | Methods for communicating between elements in a hierarchical floating car data network |
US7194756B2 (en) * | 2003-06-20 | 2007-03-20 | N2 Broadband, Inc. | Systems and methods for provisioning a host device for enhanced services in a cable system |
US7519726B2 (en) * | 2003-12-12 | 2009-04-14 | International Business Machines Corporation | Methods, apparatus and computer programs for enhanced access to resources within a network |
US7143123B2 (en) * | 2004-01-09 | 2006-11-28 | Microsoft Corporation | Well-known transactions in data replication |
US7590098B2 (en) * | 2004-10-27 | 2009-09-15 | Honeywell International Inc. | Publish/subscribe model in a wireless sensor network |
US7561544B2 (en) * | 2004-10-27 | 2009-07-14 | Honeywell International Inc. | Machine architecture for event management in a wireless sensor network |
US7630336B2 (en) * | 2004-10-27 | 2009-12-08 | Honeywell International Inc. | Event-based formalism for data management in a wireless sensor network |
US7664080B2 (en) * | 2004-10-27 | 2010-02-16 | Honeywell International Inc. | Discreet event operators for event management in a wireless sensor network |
-
2004
- 2004-11-04 US US10/981,184 patent/US20060106840A1/en not_active Abandoned
-
2005
- 2005-11-04 CN CN200510120133.3A patent/CN1848732B/zh not_active Expired - Fee Related
-
2007
- 2007-11-20 US US11/943,567 patent/US8165992B2/en not_active Expired - Fee Related
Patent Citations (17)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6807558B1 (en) * | 1995-06-12 | 2004-10-19 | Pointcast, Inc. | Utilization of information “push” technology |
US6336135B1 (en) * | 1996-05-24 | 2002-01-01 | International Business Machines Corporation | Gateway for converting synchronous client/server protocols into asynchronous messaging protocols and storing session state information at the client |
US20050138432A1 (en) * | 1997-02-12 | 2005-06-23 | Ransom Douglas S. | System and method for routing power management via XML firewall |
US6442169B1 (en) * | 1998-11-20 | 2002-08-27 | Level 3 Communications, Inc. | System and method for bypassing data from egress facilities |
US6333931B1 (en) * | 1998-12-28 | 2001-12-25 | Cisco Technology, Inc. | Method and apparatus for interconnecting a circuit-switched telephony network and a packet-switched data network, and applications thereof |
US7224984B2 (en) * | 2000-08-15 | 2007-05-29 | University Of Maryland, College Park | Method, system and computer program product for positioning and synchronizing wireless communications nodes |
US6816862B2 (en) * | 2001-01-17 | 2004-11-09 | Tiax Llc | System for and method of relational database modeling of ad hoc distributed sensor networks |
US20030131142A1 (en) * | 2001-03-14 | 2003-07-10 | Horvitz Eric J. | Schema-based information preference settings |
US20040205613A1 (en) * | 2001-07-17 | 2004-10-14 | International Business Machines Corporation | Transforming data automatically between communications parties in a computing network |
US20030149792A1 (en) * | 2002-02-06 | 2003-08-07 | Leonid Goldstein | System and method for transmission of data through multiple streams |
US20040002988A1 (en) * | 2002-06-26 | 2004-01-01 | Praveen Seshadri | System and method for modeling subscriptions and subscribers as data |
US20040039964A1 (en) * | 2002-08-21 | 2004-02-26 | International Business Machines Corporation | Programmatically serializing complex objects using self-healing techniques |
US20060085412A1 (en) * | 2003-04-15 | 2006-04-20 | Johnson Sean A | System for managing multiple disparate content repositories and workflow systems |
US20040257896A1 (en) * | 2003-06-18 | 2004-12-23 | Jeung Seong-Ho | Semiconductor memory device and method of reading data from the semiconductor memory device |
US7177881B2 (en) * | 2003-06-23 | 2007-02-13 | Sony Corporation | Network media channels |
US7091902B2 (en) * | 2003-12-17 | 2006-08-15 | Xerox Corporation | Systems and methods for characterizing the coverage of ad hoc sensor networks |
US20050198299A1 (en) * | 2004-01-26 | 2005-09-08 | Beck Christopher Clemmett M. | Methods and apparatus for identifying and facilitating a social interaction structure over a data packet network |
Cited By (44)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8838703B2 (en) | 2008-09-02 | 2014-09-16 | Alibaba Group Holding Limited | Method and system for message processing |
EP2321908A1 (en) * | 2008-09-02 | 2011-05-18 | Alibaba Group Holding Limited | Method and system for message processing |
EP2321908A4 (en) * | 2008-09-02 | 2013-01-23 | Alibaba Group Holding Ltd | METHOD AND SYSTEM FOR MESSAGE PROCESSING |
US20100057867A1 (en) * | 2008-09-02 | 2010-03-04 | Alibaba Group Holding Limited | Method and System for message processing |
US20110225229A1 (en) * | 2010-03-11 | 2011-09-15 | Yahoo! Inc. | Distributed publish/subscribe system |
US8489674B2 (en) * | 2010-03-11 | 2013-07-16 | Yahoo! Inc. | Distributed publish/subscribe system |
US9642183B2 (en) * | 2012-08-31 | 2017-05-02 | Dell Products L.P. | Information handling system proximity-based wireless interface connectivity |
US20140064258A1 (en) * | 2012-08-31 | 2014-03-06 | Bruce C. Montag | Information Handling System Proximity-Based Wireless Interface Connectivity |
US10637947B2 (en) | 2015-08-07 | 2020-04-28 | Satori Worldwide, Llc | Scalable, real-time messaging system |
US9699260B2 (en) | 2015-08-07 | 2017-07-04 | Machine Zone, Inc. | Scalable, real-time messaging system |
US10630785B2 (en) | 2015-08-07 | 2020-04-21 | Satori Worldwide, Llc | Scalable, real-time messaging system |
US10182124B2 (en) | 2015-08-07 | 2019-01-15 | Satori Worldwide, Llc | Scalable, real-time messaging system |
US9843640B2 (en) | 2015-08-07 | 2017-12-12 | Machine Zone, Inc. | Scalable, real-time messaging system |
US9942340B2 (en) | 2015-08-07 | 2018-04-10 | Satori Worldwide, Llc | Scalable, real-time messaging system |
US20170078423A1 (en) * | 2015-09-10 | 2017-03-16 | International Business Machines Corporation | Sensor-driven eventing and two stage notification |
US9910668B2 (en) * | 2015-09-10 | 2018-03-06 | International Business Machines Corporation | Sensor-driven eventing and two stage notification |
US10038661B2 (en) | 2015-10-09 | 2018-07-31 | Satori Worldwide, Llc | Systems and methods for storing and transferring message data |
US10541945B2 (en) | 2015-10-09 | 2020-01-21 | Satori Worldwide, Llc | Systems and methods for storing message data |
US10389674B2 (en) | 2015-10-09 | 2019-08-20 | Satori Worldwide, Llc | Systems and methods for storing and transferring message data |
US9843551B2 (en) | 2015-10-09 | 2017-12-12 | Machine Zone, Inc. | Systems and methods for storing and transferring message data |
US10218646B2 (en) | 2015-10-09 | 2019-02-26 | Satori Worldwide, Llc | Systems and methods for storing message data |
US9838340B2 (en) | 2015-10-09 | 2017-12-05 | Machine Zone, Inc. | Systems and methods for storing message data |
US9876745B2 (en) | 2015-10-16 | 2018-01-23 | Satori Worldwide, Llc | Systems and methods for transferring message data |
US11863509B2 (en) * | 2015-12-18 | 2024-01-02 | Amazon Technologies, Inc. | Publish-subscribe message transformation |
US20170180289A1 (en) * | 2015-12-18 | 2017-06-22 | Amazon Technologies, Inc. | Publish-Subscribe Message Transformation |
US9871750B2 (en) | 2016-05-16 | 2018-01-16 | Satori Worldwide, Llc | Maintaining persistence of a messaging system |
US10404647B2 (en) | 2016-06-07 | 2019-09-03 | Satori Worldwide, Llc | Message compression in scalable messaging system |
US9860186B1 (en) | 2016-07-06 | 2018-01-02 | Machine Zone, Inc. | Multiple-speed message channel of messaging system |
US9967203B2 (en) | 2016-08-08 | 2018-05-08 | Satori Worldwide, Llc | Access control for message channels in a messaging system |
CN109964456A (zh) * | 2016-08-23 | 2019-07-02 | 萨托里环球有限责任公司 | 可扩展实时消息传送系统 |
US10374986B2 (en) * | 2016-08-23 | 2019-08-06 | Satori Worldwide, Llc | Scalable, real-time messaging system |
US20180063039A1 (en) * | 2016-08-23 | 2018-03-01 | Machine Zone, Inc. | Scalable, real-time messaging system |
US10305981B2 (en) | 2016-08-31 | 2019-05-28 | Satori Worldwide, Llc | Data replication in scalable messaging system |
US10382574B2 (en) | 2016-09-23 | 2019-08-13 | Satori Worldwide, Llc | Systems and methods for providing messages to multiple subscribers |
US9942339B1 (en) | 2016-09-23 | 2018-04-10 | Satori Worldwide, Llc | Systems and methods for providing messages to multiple subscribers |
US10447623B2 (en) | 2017-02-24 | 2019-10-15 | Satori Worldwide, Llc | Data storage systems and methods using a real-time messaging system |
US10270726B2 (en) | 2017-02-24 | 2019-04-23 | Satori Worldwide, Llc | Selective distribution of messages in a scalable, real-time messaging system |
US10187278B2 (en) | 2017-02-24 | 2019-01-22 | Satori Worldwide, Llc | Channel management in scalable messaging system |
US10659330B2 (en) | 2017-02-24 | 2020-05-19 | Satori Worldwide, Llc | Channel management in scalable messaging system |
US20190132276A1 (en) * | 2017-11-02 | 2019-05-02 | Sap Se | Unified event processing for data/event exchanges with existing systems |
CN108494815A (zh) * | 2018-02-06 | 2018-09-04 | 北京极智感科技有限公司 | 一种传输消息的方法和系统 |
US20190356622A1 (en) * | 2018-05-17 | 2019-11-21 | Honeywell International Inc. | Rule-based annotation service in a cloud platform |
US11700221B2 (en) * | 2018-05-17 | 2023-07-11 | Honeywell International Inc. | Rule-based annotation service in a cloud platform |
US10986203B2 (en) * | 2019-02-08 | 2021-04-20 | American Express Travel Related Services Company, Inc. | Balancing and control framework for real-time processing |
Also Published As
Publication number | Publication date |
---|---|
CN1848732A (zh) | 2006-10-18 |
US8165992B2 (en) | 2012-04-24 |
US20080082562A1 (en) | 2008-04-03 |
CN1848732B (zh) | 2011-04-20 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8165992B2 (en) | System and method for tracking notifications in a publish subscribe system | |
US10747592B2 (en) | Router management by an event stream processing cluster manager | |
AU2006217563B2 (en) | Distributed asset management system and method | |
US7716353B2 (en) | Web services availability cache | |
US8930521B2 (en) | Method, apparatus, and computer program product for enabling monitoring of a resource | |
CN101193078B (zh) | 用于管理订阅匹配的方法和系统 | |
US7817039B2 (en) | Dynamic display of RFID and sensor data | |
Cheung et al. | Load balancing content-based publish/subscribe systems | |
US7454496B2 (en) | Method for monitoring data resources of a data processing network | |
EP3796167B1 (en) | Router management by an event stream processing cluster manager | |
US20190050277A1 (en) | Router management by an event stream processing cluster manager | |
US8549137B2 (en) | Monitoring device, monitoring system, monitoring method, and program | |
US7478401B2 (en) | Business to business event communications | |
US20050071842A1 (en) | Method and system for managing data using parallel processing in a clustered network | |
EP2033086B1 (en) | Peer to peer reporting system on reputation of quality for service | |
CA2647138A1 (en) | Policy based message aggregation framework | |
Levene et al. | Dream: Distributed reliable event-based application management | |
EP1569110A2 (en) | A method for managing execution of a process based on available services | |
US8650261B2 (en) | System and method for updating software using updated data from external sources | |
CN115250233B (zh) | 一种灰度路由控制方法、灰度路由组件及计算机设备 | |
Rooney et al. | Distributed messaging using meta channels and message bins | |
US20040267898A1 (en) | Status information for software used to perform a service | |
Trifa et al. | Messaging methods in a service-oriented architecture for industrial automation systems | |
Cohen et al. | Reducing business surprises through proactive, real-time sensing and alert management | |
CN118227094A (zh) | 并发式系统架构的构建方法、装置以及电子设备 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: INTERNATIONAL BUSINESS MACHINES CORPORATION, NEW Y Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:ROONEY, SEAN G.;REEL/FRAME:015390/0502 Effective date: 20041103 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |