CN110971693A - Event issuing method and device - Google Patents
Event issuing method and device Download PDFInfo
- Publication number
- CN110971693A CN110971693A CN201911218173.XA CN201911218173A CN110971693A CN 110971693 A CN110971693 A CN 110971693A CN 201911218173 A CN201911218173 A CN 201911218173A CN 110971693 A CN110971693 A CN 110971693A
- Authority
- CN
- China
- Prior art keywords
- event
- target object
- client
- events
- subscribed
- 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.)
- Granted
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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/50—Queue scheduling
- H04L47/62—Queue scheduling characterised by scheduling criteria
- H04L47/6245—Modifications to standard FIFO or LIFO
-
- 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/56—Provisioning of proxy services
- H04L67/568—Storing data temporarily at an intermediate stage, e.g. caching
- H04L67/5681—Pre-fetching or pre-delivering data based on network characteristics
-
- 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/56—Provisioning of proxy services
- H04L67/568—Storing data temporarily at an intermediate stage, e.g. caching
- H04L67/5682—Policies or rules for updating, deleting or replacing the stored data
Abstract
The invention discloses an event publishing method and device, which are applied to a server of a subscription and publishing mechanism, wherein the server creates an event table for a target object, creates an event bitmap corresponding to the event table for a client subscribing the target object event, and obtains a triggered event of the target object subscribed by the client by regularly comparing a set bit of the event bitmap with a corresponding table item in the event table. The method reduces the complexity of the service end managing the subscribed event of the target object in the subscription and release mechanism, and improves the operation efficiency of the service end; meanwhile, the invention can reduce the pushing quantity of the subscribed events of the target object by carrying out merging processing on the exclusive events in the subscribed events and timely cleaning the failure events, thereby improving the network throughput and the transmission performance of the network.
Description
Technical Field
The invention relates to the technical field of computers, in particular to an event publishing method and device.
Background
In the subscription and publication mechanism, after a server (i.e., a publisher) receives an event subscription message of a target object initiated by a client (i.e., a subscriber), a First-In First-Out (FIFO) queue is generally adopted to manage a triggered event of the target object subscribed by the client at present. However, as the number of clients and the number of event subscription messages continuously rise, the server needs to push subscribed events of different target objects for each client, and if the FIFO queue is used for management, the server is complex in operation and low in operation efficiency, and network communication delay and other problems are caused. Therefore, how to improve the operation efficiency of the server and save network resources in the subscription and publication mechanism becomes an urgent problem to be solved.
Disclosure of Invention
The invention provides an event publishing method and device, which are applied to a server of a subscription and publishing mechanism, can reduce the complexity of the server for managing a subscribed event of a target object, and improve the operation efficiency of the server, thereby improving the transmission performance of a network.
In a first aspect, the present invention provides an event publishing method, applied to a server subscribing to a publishing mechanism, including the following steps:
the method comprises the steps that a server side creates an event table based on a target object, and the event table manages all events of the target object;
the server receives an event subscription message initiated by a client to the target object, and creates an event bitmap for the client based on the target object, wherein each bit of the event bitmap corresponds to each table entry of the event table one by one;
when any subscribed event of the target object is triggered, the server side updates a corresponding table entry of the event in the event table, and simultaneously sets a bit corresponding to the corresponding table entry in the event bitmap;
according to a set time period, the server searches the triggered corresponding events in the event table in sequence according to all set bits in the event bitmap, packages the triggered events of the target object subscribed by the client, pushes the triggered events to the client through a message, and initializes the event bitmap.
The server receives an event subscription message initiated by a client to the target object, and creates an event bitmap for the client based on the target object, including: when the server receives an event subscription message initiated by the client to at least one target object, sequentially creating corresponding event bitmaps for the client based on each target object in the at least one target object; or when the server receives an event subscription message initiated by the client to the same type of target objects, sequentially creating corresponding event bitmaps for the client based on each target object in the same type of target objects.
In the present invention, when the subscribed events of the target object include at least two mutually exclusive events, the at least two mutually exclusive events correspond to the same table entry in the event table of the target object.
Preferably, when any subscribed event of the target object is triggered, the server updates the corresponding entry of the event in the event table, and sets a bit corresponding to the corresponding entry in the event bitmap, including: if the deletion event subscribed by the target object is triggered, and when the deletion event can cause other subscribed events of the target object to be invalid, the server side updates the corresponding entry of the deletion event in the event table, sets the bit corresponding to the entry of the deletion event in the event bitmap, and initializes the bit corresponding to the invalid corresponding entry of the other subscribed events in the event bitmap.
In the present invention, the time period refers to a time interval for the server to receive a push message set in an event subscription message initiated by the client to the target object.
In a second aspect, the present invention provides an event publishing apparatus, applied to a server subscribing to a publishing mechanism, the apparatus including: the system comprises an event management module, a receiving module and a sending module;
the event management module is used for creating an event table based on a target object, and the event table manages all events of the target object;
the receiving module is used for receiving an event subscription message initiated by a client to the target object;
the event management module is further configured to, after the receiving module receives an event subscription message initiated by the client for the target object, create an event bitmap for the client based on the target object, where each bit of the event bitmap corresponds to each entry of the event table one to one; when any subscribed event of the target object is triggered, updating a corresponding table entry of the event in the event table, and simultaneously setting a bit corresponding to the corresponding table entry in the event bitmap;
the sending module is configured to sequentially search for triggered corresponding events in the event table according to all set bits in the event bitmap in the event management module according to a set time period, and package the triggered events of the target object subscribed by the client and then push the packaged events to the client through a message;
the event management module is further configured to initialize the event bitmap after the sending module pushes the subscribed message to the client according to the set time period.
The receiving module is specifically configured to receive an event subscription message initiated by the client to at least one target object, or receive an event subscription message initiated by the client to a target object of the same class; the event management module is specifically configured to, when the receiving module receives an event subscription message initiated by the client to at least one target object, sequentially create, for the client, corresponding event bitmaps based on each target object of the at least one target object; or, when the receiving module receives an event subscription message initiated by the client to the same type of target object, sequentially creating corresponding event bitmaps for the client based on each target object in the same type of target object.
Preferably, when the subscribed events of the target object include at least two mutually exclusive events, the at least two mutually exclusive events correspond to the same entry in the event table of the target object.
Preferably, the event management module is specifically configured to, if the deletion event that the target object is subscribed to is triggered, and when the deletion event may cause invalidation of other subscribed events of the target object, update the corresponding entry of the deletion event in the event table, set a bit corresponding to the entry of the deletion event in the event bitmap, and initialize a bit corresponding to the invalidated bit corresponding to the corresponding entry of the other subscribed events in the event bitmap.
In the present invention, the time period refers to a time interval for the receiving module to receive a push message set in an event subscription message initiated by the client to the target object.
In summary, in the present invention, the server creates an event table for the target object, creates an event bitmap corresponding to the event table for the client subscribing to the target object event, and periodically compares the set bit of the event bitmap with the corresponding entry in the event table to obtain the triggered event of the target object subscribed by the client. The method reduces the complexity of the service end managing the subscribed event of the target object in the subscription and release mechanism, and improves the operation efficiency of the service end; meanwhile, the invention can reduce the pushing quantity of the subscribed events of the target object by carrying out merging processing on the exclusive events in the subscribed events and timely cleaning the failure events, thereby improving the network throughput and the transmission performance of the network.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings needed to be used in the embodiments will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present invention and therefore should not be considered as limiting the scope, and for those skilled in the art, other related drawings can be obtained according to the drawings without inventive efforts.
Fig. 1 is a flowchart illustrating an event publishing method according to an embodiment of the present invention;
fig. 2 is a schematic diagram illustrating an event publishing device according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. The following detailed description of the embodiments of the present invention, presented in the figures, is not intended to limit the scope of the invention, as claimed, but is merely representative of selected embodiments of the invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments of the present invention without making any creative effort, shall fall within the protection scope of the present invention.
The following are detailed descriptions of the respective embodiments.
Example one
The embodiment of the invention provides an event publishing method, which is applied to a server subscribing a publishing mechanism, and the processing flow chart of the event publishing method is shown in fig. 1, and the method comprises the following steps:
step S101, the server side creates an event table based on the target object, and the event table manages all events of the target object.
In the present invention, the target object may include an interface, a domain name, an IP address, and the like. The event table can be carried in an array mode and the like. When any event of the target object is triggered, updating the corresponding table entry of the event in the event table in real time.
Step S102, the server receives an event subscription message initiated by a client to the target object, and creates an event bitmap for the client based on the target object, where each bit of the event bitmap corresponds to each entry of the event table one to one.
When the server receives an event subscription message initiated by the client to at least one target object, sequentially creating corresponding event bitmaps for the client based on each target object in the at least one target object; or when the server receives an event subscription message initiated by the client to the same type of target objects, sequentially creating corresponding event bitmaps for the client based on each target object in the same type of target objects. For example, IF the server receives an event subscription message initiated by the client 1 to the target objects IF01 and IF02 interfaces, the client is sequentially served based on the target objects IF01 and IF02 interfacesThe client 1 creates a corresponding event Bitmap11，Bitmap12(ii) a IF the server receives an event subscription message initiated by the client 2 to the same type of target object IF interface, and IF the same type of target object IF interface contains M target objects including IF01 and IF02 … … IF0M interfaces, the server creates a corresponding event Bitmap for the client 2 sequentially based on the target objects IF01 and IF02 … … IF0M interfaces21，Bitmap22……Bitmap2MWherein M is a positive integer. It should be noted that the event table is created based on a target object, one target object corresponds to one event table, and the event table is applicable to all clients subscribing to the target object; the event Bitmap is created based on clients subscribing to the target object, and one event Bitmap corresponds to one target object subscribed by one client. Each Bit of the event Bitmap corresponds to each table entry of the event table one by one, that is, each Bit of the event Bitmap represents whether a corresponding event in the event table is triggered.
Step S103, when any subscribed event of the target object is triggered, the server updates the corresponding entry of the event in the event table, and sets a bit corresponding to the corresponding entry in the event bitmap.
In the invention, when any event of a target object is triggered and the server updates the corresponding table entry of the event in the event table in real time, the server sets the Bit corresponding to the corresponding table entry in the event Bitmap for the client subscribing the target object.
As a preferred embodiment of the present invention, when the subscribed events of the target object include at least two mutually exclusive events, the at least two mutually exclusive events correspond to the same entry in the event table of the target object. The entry corresponds to one Bit in the event Bitmap. For example, the Link up event and the Link down event to which the target IF01 interface is subscribed by the client 1 may be regarded as the exclusive event. The two mutually exclusive events correspond to the same entry in the event table of the IF01 interface, and the entry corresponds to one Bit in the event Bitmap. When any one of the Link up event or the Link down event of the IF01 interface is triggered, the same table entry corresponding to the Link up event and the Link down event in the event table of the IF01 interface is updated to be the currently triggered event, and a Bit corresponding to the table entry in the event Bitmap is set for the client subscribing to the Link up event and the Link down event of the IF01 interface.
As another preferred embodiment of the present invention, if a deletion event that a target object is subscribed to is triggered, and when the deletion event may cause other subscribed events of the target object to fail, the server updates a corresponding entry of the deletion event in the event table, sets a Bit corresponding to the corresponding entry of the deletion event in the event Bitmap, and initializes a Bit corresponding to the corresponding entry of the failed other subscribed events in the event Bitmap. For example, when a deletion event subscribed by the client 1 on the target object IF01 interface is triggered, other subscribed events (e.g., Link up event and Link down event) on the IF01 interface may be failed, at this time, the server updates the corresponding entry of the deletion event on the IF01 interface in the event table, sets a Bit corresponding to the corresponding entry of the deletion event in an event Bitmap of the IF01 interface subscribed by the client 1, and initializes a Bit corresponding to the corresponding entry of the failed other subscribed events (e.g., Link up event and Link down event).
Step S104, according to a set time period, the server searches the triggered corresponding events in the event table according to all set bits in the event bitmap, packages the triggered events of the target object subscribed by the client, pushes the triggered events to the client through a message, and initializes the event bitmap.
The time period refers to a time interval for receiving a push message set in an event subscription message initiated by a client to a target object by a server; or, the server side unifies the set time interval of the push message.
In summary, in the present invention, the server creates an event table for the target object, creates an event bitmap corresponding to the event table for the client subscribing to the target object event, and periodically compares the set bit of the event bitmap with the corresponding entry in the event table to obtain the triggered event of the target object subscribed by the client. The method reduces the complexity of the service end managing the subscribed event of the target object in the subscription and release mechanism, and improves the operation efficiency of the service end; meanwhile, the invention can reduce the pushing quantity of the subscribed events of the target object by carrying out merging processing on the exclusive events in the subscribed events and timely cleaning the failure events, thereby improving the network throughput and the transmission performance of the network.
Example two
An embodiment of the present invention provides an event publishing device 20, which is applied to a server subscribing a publishing mechanism, and a schematic diagram of the event publishing device is shown in fig. 2, where the event publishing device includes: an event management module 201, a receiving module 202 and a sending module 203;
the event management module 201 is configured to create an event table based on a target object, where the event table manages all events of the target object;
the receiving module 202 is configured to receive an event subscription message initiated by a client for the target object;
the event management module 201 is further configured to, after the receiving module 202 receives an event subscription message initiated by the client to the target object, create an event bitmap for the client based on the target object, where each bit of the event bitmap corresponds to each entry of the event table one to one; when any subscribed event of the target object is triggered, updating a corresponding table entry of the event in the event table, and simultaneously setting a bit corresponding to the corresponding table entry in the event bitmap;
the sending module 203 is configured to sequentially search triggered corresponding events in the event table according to all set bits in the event bitmap in the event management module 201 according to a set time period, and package the triggered events of the target object subscribed by the client and then push the packaged events to the client through a message;
the event management module 201 is further configured to initialize the event bitmap after the sending module 203 pushes the subscribed message to the client according to the set time period.
The receiving module 202 is specifically configured to receive an event subscription message initiated by the client to at least one target object, or receive an event subscription message initiated by the client to a target object of the same class; the event management module 201 is specifically configured to, when the receiving module 202 receives an event subscription message initiated by the client to at least one target object, sequentially create corresponding event bitmaps for the client based on each target object in the at least one target object; or, when the receiving module 202 receives an event subscription message initiated by the client to a same type of target object, sequentially creating a corresponding event bitmap for the client based on each target object in the same type of target object.
Preferably, when the subscribed events of the target object include at least two mutually exclusive events, the at least two mutually exclusive events correspond to the same entry in the event table of the target object.
Preferably, the event management module 201 is specifically configured to, if the deletion event that the target object is subscribed to is triggered, and when the deletion event may cause invalidation of other subscribed events of the target object, update the corresponding entry of the deletion event in the event table, set a bit corresponding to the entry of the deletion event in the event bitmap, and initialize a bit corresponding to the invalidated bit corresponding to the corresponding entry of the other subscribed events in the event bitmap.
The time period refers to a time interval for receiving a push message set in an event subscription message initiated by the client to the target object by the receiving module 202; or, the sending module 203 unifies the set time intervals of the push messages.
In summary, in the present invention, the server creates an event table for the target object, creates an event bitmap corresponding to the event table for the client subscribing to the target object event, and periodically compares the set bit of the event bitmap with the corresponding entry in the event table to obtain the triggered event of the target object subscribed by the client. The method reduces the complexity of the service end managing the subscribed event of the target object in the subscription and release mechanism, and improves the operation efficiency of the service end; meanwhile, the invention can reduce the pushing quantity of the subscribed events of the target object by carrying out merging processing on the exclusive events in the subscribed events and timely cleaning the failure events, thereby improving the network throughput and the transmission performance of the network.
All parts of the specification are described in a progressive mode, the same and similar parts of all embodiments can be referred to each other, and each embodiment is mainly introduced to be different from other embodiments. In particular, as for the apparatus embodiment, since it is substantially similar to the method embodiment, the description is relatively simple, and the relevant points can be referred to the description of the method embodiment section.
The above description is only for the specific embodiments of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present invention, and all the changes or substitutions should be covered within the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.
Claims (10)
1. An event publishing method is applied to a server subscribing a publishing mechanism, and comprises the following steps:
the method comprises the steps that a server side creates an event table based on a target object, and the event table manages all events of the target object;
the server receives an event subscription message initiated by a client to the target object, and creates an event bitmap for the client based on the target object, wherein each bit of the event bitmap corresponds to each table entry of the event table one by one;
when any subscribed event of the target object is triggered, the server side updates a corresponding table entry of the event in the event table, and simultaneously sets a bit corresponding to the corresponding table entry in the event bitmap;
according to a set time period, the server searches the triggered corresponding events in the event table in sequence according to all set bits in the event bitmap, packages the triggered events of the target object subscribed by the client, pushes the triggered events to the client through a message, and initializes the event bitmap.
2. The method of claim 1, wherein the server receives an event subscription message initiated by a client for the target object, and creates an event bitmap for the client based on the target object, comprising:
when the server receives an event subscription message initiated by the client to at least one target object, sequentially creating corresponding event bitmaps for the client based on each target object in the at least one target object; or the like, or, alternatively,
and when the server receives an event subscription message initiated by the client to the same type of target objects, sequentially creating corresponding event bitmaps for the client based on each target object in the same type of target objects.
3. The method of claim 1, wherein when the events subscribed to by the target object include at least two mutually exclusive events, the at least two mutually exclusive events correspond to a same entry in an event table of the target object.
4. The method of claim 1, wherein when any subscribed event of the target object is triggered, the server updates a corresponding entry of the event in the event table, and sets a bit corresponding to the corresponding entry in the event bitmap, including:
if the deletion event subscribed by the target object is triggered, and when the deletion event can cause other subscribed events of the target object to be invalid, the server side updates the corresponding entry of the deletion event in the event table, sets the bit corresponding to the entry of the deletion event in the event bitmap, and initializes the bit corresponding to the invalid corresponding entry of the other subscribed events in the event bitmap.
5. The method according to any one of claims 1 to 4, wherein the time period refers to a time interval for the server to receive a push message set in an event subscription message initiated by the client for the target object.
6. An event publishing device, applied to a server subscribing to a publishing mechanism, the device comprising: the system comprises an event management module, a receiving module and a sending module;
the event management module is used for creating an event table based on a target object, and the event table manages all events of the target object;
the receiving module is used for receiving an event subscription message initiated by a client to the target object;
the event management module is further configured to, after the receiving module receives an event subscription message initiated by the client for the target object, create an event bitmap for the client based on the target object, where each bit of the event bitmap corresponds to each entry of the event table one to one; when any subscribed event of the target object is triggered, updating a corresponding table entry of the event in the event table, and simultaneously setting a bit corresponding to the corresponding table entry in the event bitmap;
the sending module is configured to sequentially search for triggered corresponding events in the event table according to all set bits in the event bitmap in the event management module according to a set time period, and package the triggered events of the target object subscribed by the client and then push the packaged events to the client through a message;
the event management module is further configured to initialize the event bitmap after the sending module pushes the subscribed message to the client according to the set time period.
7. The apparatus of claim 6,
the receiving module is specifically configured to receive an event subscription message initiated by the client to at least one target object, or receive an event subscription message initiated by the client to a target object of the same type;
the event management module is specifically configured to, when the receiving module receives an event subscription message initiated by the client to at least one target object, sequentially create, for the client, corresponding event bitmaps based on each target object of the at least one target object; or, when the receiving module receives an event subscription message initiated by the client to the same type of target object, sequentially creating corresponding event bitmaps for the client based on each target object in the same type of target object.
8. The apparatus of claim 6, wherein when the events subscribed to by the target object include at least two mutually exclusive events, the at least two mutually exclusive events correspond to a same entry in an event table of the target object.
9. The apparatus of claim 6,
the event management module is specifically configured to, if a deletion event that the target object is subscribed to is triggered, and when the deletion event may cause invalidation of other subscribed events of the target object, update the corresponding entry of the deletion event in the event table, set a bit corresponding to the entry of the deletion event in the event bitmap, and initialize bits corresponding to the invalidated other subscribed events in the event bitmap.
10. The apparatus according to any one of claims 6 to 9, wherein the time period refers to a time interval for the receiving module to receive a push message set in an event subscription message initiated by the client for the target object.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911218173.XA CN110971693B (en) | 2019-12-03 | 2019-12-03 | Event release method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911218173.XA CN110971693B (en) | 2019-12-03 | 2019-12-03 | Event release method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110971693A true CN110971693A (en) | 2020-04-07 |
| CN110971693B CN110971693B (en) | 2023-09-15 |
Family
ID=70032827
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911218173.XA Active CN110971693B (en) | 2019-12-03 | 2019-12-03 | Event release method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110971693B (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20050209990A1 (en) * | 2004-03-18 | 2005-09-22 | Ordille Joann J | Method and apparatus for a publish-subscribe system with access controls |
| US20110099567A1 (en) * | 2008-05-21 | 2011-04-28 | Nagravision S.A. | Method for the allocation and management of subscriptions for the reception of broadcast products |
| CN102150436A (en) * | 2008-09-09 | 2011-08-10 | 纳格拉影像股份有限公司 | Method for the allocation and management of substcriptions for the reception of broadcast products |
| WO2017052213A1 (en) * | 2015-09-22 | 2017-03-30 | 엘지전자 주식회사 | Method for scheduling neighbor awareness network and device using method |
| WO2017121278A1 (en) * | 2016-01-14 | 2017-07-20 | 广州市动景计算机科技有限公司 | Information-pushing device, method, client and machine-readable storage medium |
| CN110262905A (en) * | 2019-05-31 | 2019-09-20 | 四川长虹电器股份有限公司 | The method for pushing of the message-oriented middleware of priority query based on building high performance and scalability |
-
2019
- 2019-12-03 CN CN201911218173.XA patent/CN110971693B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20050209990A1 (en) * | 2004-03-18 | 2005-09-22 | Ordille Joann J | Method and apparatus for a publish-subscribe system with access controls |
| US20110099567A1 (en) * | 2008-05-21 | 2011-04-28 | Nagravision S.A. | Method for the allocation and management of subscriptions for the reception of broadcast products |
| US20130291005A1 (en) * | 2008-05-21 | 2013-10-31 | Nagravision S.A. | Device for the allocation and management of subscriptions for the reception of broadcast products |
| CN102150436A (en) * | 2008-09-09 | 2011-08-10 | 纳格拉影像股份有限公司 | Method for the allocation and management of substcriptions for the reception of broadcast products |
| WO2017052213A1 (en) * | 2015-09-22 | 2017-03-30 | 엘지전자 주식회사 | Method for scheduling neighbor awareness network and device using method |
| WO2017121278A1 (en) * | 2016-01-14 | 2017-07-20 | 广州市动景计算机科技有限公司 | Information-pushing device, method, client and machine-readable storage medium |
| CN110262905A (en) * | 2019-05-31 | 2019-09-20 | 四川长虹电器股份有限公司 | The method for pushing of the message-oriented middleware of priority query based on building high performance and scalability |
Non-Patent Citations (4)
| Title |
|---|
| KUN-LUNG WU等: "Efficient interval indexing for content-based subscription e-commerce and e-service", 《IEEE INTERNATIONAL CONFERENCE ON E-COMMERCE TECHNOLOGY FOR DYNAMIC E-BUSINESS》 * |
| 吴霖;刘振宇;李佳;: "Redis在订阅推送系统中的应用", 电脑知识与技术, no. 07 * |
| 董俊;曹健;李明禄;: "发布订阅模式中间件中高效事件过滤器的研究", 小型微型计算机系统, no. 03 * |
| 路国翠: ""泛在网络环境的发布/订阅路由系统研究"", 《中国优秀硕士学位论文全文数据库》 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110971693B (en) | 2023-09-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7647595B2 (en) | Efficient event notification in clustered computing environments | |
| US8185649B2 (en) | Subscription propagation in a high performance highly available content-based publish/subscribe system | |
| CN106294357B (en) | Data processing method and stream calculation system | |
| CN109905286B (en) | Method and system for monitoring running state of equipment | |
| US7970856B2 (en) | System and method for managing and distributing assets over a network | |
| US10171610B2 (en) | Web caching method and system for content distribution network | |
| JP2007037180A (en) | Mail box polling preemptive reference | |
| CN109783151B (en) | Method and device for rule change | |
| JP2011171867A (en) | Data storage method and mail relay method of data store server in mail system | |
| CN115640110B (en) | Distributed cloud computing system scheduling method and device | |
| WO2014065115A1 (en) | Rule distribution server, as well as event processing system, method, and program | |
| WO2019231645A1 (en) | Change notifications for object storage | |
| CN109977139B (en) | Data processing method and device based on class structured query statement | |
| CN111124717A (en) | Message delivery method, system and computer storage medium | |
| CN103152191A (en) | Processing method and system of service gateway data of internet of things | |
| CN108512917B (en) | Data pushing method and system based on Websocket | |
| CN113806177A (en) | Cluster monitoring method and device, electronic equipment and storage medium | |
| US10812355B2 (en) | Record compression for a message system | |
| CN110971693A (en) | Event issuing method and device | |
| CN114860782B (en) | Data query method, device, equipment and medium | |
| US11016807B2 (en) | Intermediary system for data streams | |
| US11212220B2 (en) | Optimized reconciliation in a controller-switch network | |
| CN110019671B (en) | Method and system for processing real-time message | |
| CN112511595A (en) | Message pushing method and message service system | |
| CN116996481B (en) | Live broadcast data acquisition method and device, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| CB02 | Change of applicant information | ||
| CB02 | Change of applicant information |
Address after: 610041 nine Xing Xing Road 16, hi tech Zone, Sichuan, Chengdu Applicant after: MAIPU COMMUNICATION TECHNOLOGY Co.,Ltd. Address before: 610041 15-24 floor, 1 1 Tianfu street, Chengdu high tech Zone, Sichuan Applicant before: MAIPU COMMUNICATION TECHNOLOGY Co.,Ltd. |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |