CN111814091B - Message distribution method and related device - Google Patents
Message distribution method and related device Download PDFInfo
- Publication number
- CN111814091B CN111814091B CN202010691554.6A CN202010691554A CN111814091B CN 111814091 B CN111814091 B CN 111814091B CN 202010691554 A CN202010691554 A CN 202010691554A CN 111814091 B CN111814091 B CN 111814091B
- Authority
- CN
- China
- Prior art keywords
- topic
- message
- node
- tree
- path
- 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.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 64
- 230000004044 response Effects 0.000 claims abstract description 4
- 238000012217 deletion Methods 0.000 claims description 9
- 230000037430 deletion Effects 0.000 claims description 9
- 238000004891 communication Methods 0.000 claims description 3
- 238000010586 diagram Methods 0.000 description 14
- 239000000284 extract Substances 0.000 description 6
- 238000003672 processing method Methods 0.000 description 6
- 230000009286 beneficial effect Effects 0.000 description 4
- 230000008859 change Effects 0.000 description 4
- 230000008569 process Effects 0.000 description 4
- 238000004590 computer program Methods 0.000 description 3
- 230000006978 adaptation Effects 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 238000012423 maintenance Methods 0.000 description 2
- 238000003058 natural language processing Methods 0.000 description 2
- 206010044565 Tremor Diseases 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 230000008451 emotion Effects 0.000 description 1
- 238000004880 explosion Methods 0.000 description 1
- 238000009472 formulation Methods 0.000 description 1
- 238000002955 isolation Methods 0.000 description 1
- 238000007726 management method Methods 0.000 description 1
- 239000000203 mixture Substances 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000012216 screening Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/958—Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/953—Querying, e.g. by the use of web search engines
Landscapes
- Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The present disclosure relates to a message distribution method and related apparatus, wherein the message distribution method includes determining a message topic to which a message in message data belongs in response to a message data publishing operation; determining a subordinate path of the message topic in a topic tree; the subordinate path is a topic node path from a root node in the topic tree to a topic node corresponding to the message topic; and distributing the message to a subscription terminal subscribed with any topic node in the subordinate path. The scheme provided by the disclosure not only can distribute the message to the subscription terminal subscribed with the message topic, but also can distribute the message to the subscription terminal subscribed with the upper message topic of the message topic, and different message topics have connectivity due to the upper and lower subordinate relations of the topic tree, so that the message distribution is more flexible.
Description
Technical Field
The disclosure relates to the technical field of internet, and in particular relates to a message distribution method and a related device.
Background
Publish-subscribe is a paradigm of messages in a software architecture. Subscribers using the subscription terminal may register one or more topics of interest with a message distribution system that maintains a preset topic node configuration of the subscription terminal. The publisher may publish messages and message topics to the message distribution system using the publication terminal.
The message distribution system screens the subscription terminals based on the message subject to which the message belongs and the preset subject node configuration of the subscription terminals, and distributes the message to the screened subscription terminals.
However, in the related art, the message distribution system has a plurality of message topics, the message topics are independent from each other and at the same hierarchical level, and one message belongs to one message topic. In this case, the message can only be distributed to the subscription terminal subscribing to the message topic, and if the subscription terminal does not subscribe to the message topic, the message corresponding to the message topic cannot be received, so that the message distribution process is isolated and inflexible.
Disclosure of Invention
The present disclosure provides a message distribution method and related apparatus to at least solve the problem of isolation and inflexibility of a message distribution process in the related art. The technical scheme of the present disclosure is as follows:
according to a first aspect of an embodiment of the present disclosure, there is provided a message distribution method, including:
responding to a message data publishing operation, and determining a message theme to which a message in the message data belongs;
determining a subordinate path of the message topic in a topic tree; the subordinate path is a topic node path from a root node in the topic tree to a topic node corresponding to the message topic;
And distributing the message to a subscription terminal subscribed with any topic node in the subordinate path.
Wherein said determining a subordinate path of said message topic in a topic tree comprises:
determining a topic node corresponding to the message topic in the topic tree;
querying a parent node of the topic node upwards in the topic tree;
repeatedly executing parent node operation of inquiring the parent node upwards in the theme tree until the parent node is a root node;
and determining a topic node path from a root node in the topic tree to a topic node corresponding to the message topic as the subordinate path.
Wherein the distributing the message to the subscription terminal subscribed with any topic node in the subordinate path comprises:
judging whether the preset theme node configuration of the subscription terminal has intersection with the subordinate path or not specifically comprises the following steps: judging whether the preset subject node configuration and the subordinate path have the same subject node or not;
if there is an intersection, the message is distributed to the subscriber terminal.
The message data also comprises event labels to which the messages belong;
the distributing the message to the subscribing terminal subscribed to any topic node in the subordinate path comprises:
Judging whether the preset theme node configuration of the subscription terminal has intersection with the subordinate path or not specifically comprises the following steps: judging whether the preset subject node configuration and the subordinate path have the same subject node or not;
if the intersection exists, judging whether the preset event tag configuration of the subscription terminal comprises the event tag or not;
and if the preset event label configuration of the subscription terminal comprises the event label, distributing the message to the subscription terminal.
Wherein, still include:
receiving an increase request for increasing a new message topic; wherein the add request includes a new message topic and an upper message topic to which the new message topic belongs;
determining topic nodes corresponding to the upper level message topics in the topic tree;
and adding a topic node corresponding to the new message topic to the topic node in the topic tree.
Wherein, still include:
receiving a deleting request for deleting the existing message theme; wherein the delete request includes an existing message topic;
deleting the topic node corresponding to the existing message topic in the topic tree, and deleting the child node of the topic node corresponding to the existing message topic;
and sending a deleting instruction to a subscription terminal subscribed with the topic node and the child node corresponding to the existing message topic, so that the subscription terminal deletes the topic node and the child node corresponding to the existing message topic in preset topic node configuration.
According to a second aspect of the embodiments of the present disclosure, there is provided a message distribution apparatus, including:
a determining subject unit configured to perform a publishing operation in response to message data, determining a message subject to which a message in the message data belongs;
a determining path unit configured to perform determining a subordinate path of the message topic in a topic tree; the subordinate path is a topic node path from a root node in the topic tree to a topic node corresponding to the message topic;
and the distribution unit is configured to perform distribution of the message to subscription terminals subscribed with any topic node in the subordinate path.
Wherein the determining path unit includes:
a first determining unit configured to perform determining that the message topic corresponds to a topic node in the topic tree;
a second determining unit configured to perform an upward query of a parent node of the subject node in the subject tree;
a query unit configured to perform parent node operations of repeatedly performing upward queries of the parent node in the subject tree until the parent node is a root node;
and the third determining unit is configured to determine a topic node path from a root node in the topic tree to a topic node corresponding to the message topic as the subordinate path.
Wherein the distribution unit comprises:
the first judging unit is configured to execute judgment on whether the preset theme node configuration of the subscription terminal has intersection with the subordinate path, and specifically includes: judging whether the preset subject node configuration and the subordinate path have the same subject node or not;
a first distributing message unit configured to perform distributing the message to the subscriber terminal if there is an intersection.
The message data also comprises event labels to which the messages belong;
the distribution unit comprises:
a second judging unit configured to perform judgment as to whether the preset subject node configuration and the subordinate path have the same subject node;
a third judging unit configured to execute, if there is an intersection, judging whether a preset event tag configuration of the subscription terminal includes the event tag;
and the second message distribution unit is configured to execute the distribution of the message to the subscription terminal if the preset event tag configuration of the subscription terminal comprises the event tag.
Wherein the message distribution apparatus further comprises:
an adding unit configured to perform receiving an add request to add a new message topic; wherein the add request includes a new message topic and an upper message topic to which the new message topic belongs; determining topic nodes corresponding to the upper level message topics in the topic tree; and adding a topic node corresponding to the new message topic to the topic node in the topic tree.
Wherein the message distribution apparatus further comprises:
a deletion unit configured to perform receiving a deletion request to delete an existing message topic; wherein the delete request includes an existing message topic; deleting the topic node corresponding to the existing message topic in the topic tree, and deleting the child node of the topic node corresponding to the existing message topic;
the sending unit is configured to send a deleting instruction to a subscription terminal subscribed with the topic node corresponding to the existing message topic and the child node thereof, so that the subscription terminal deletes the topic node corresponding to the existing message topic and the child node thereof in the preset topic node configuration.
According to a third aspect of embodiments of the present disclosure, there is provided a server comprising:
a processor;
a memory for storing the processor-executable instructions;
wherein the processor is configured to execute the instructions to implement the message distribution method.
According to a fourth aspect of embodiments of the present disclosure, there is provided a storage medium, which when executed by a processor of a server, enables the server to perform the message distribution method.
According to a fifth aspect of embodiments of the present disclosure, there is provided a message distribution system comprising:
A plurality of publishing terminals, a plurality of subscribing terminals and a server in communication connection with the plurality of publishing terminals and the plurality of subscribing terminals;
the release terminal is used for constructing message data and releasing the message data to the server;
the server is used for realizing the message distribution method.
According to a sixth aspect of embodiments of the present disclosure, there is provided a computer program product, which when executed by a processor of a server, enables the server to implement the message distribution method.
The technical scheme provided by the embodiment of the disclosure at least brings the following beneficial effects:
the present disclosure provides for managing message topics in a topic tree that employs a tree structure among a plurality of topic nodes in the topic tree to represent dependencies, i.e., the topics are no longer at the same level, but have upper and lower dependencies.
After determining the message topic to which the message belongs, the present disclosure may further determine a subordinate path of the message topic in the topic tree, where the subordinate path includes each topic node from a root node in the topic tree to a topic node corresponding to the message topic, and then may be distributed to a subscription terminal subscribed to any topic node in the subordinate path.
The scheme provided by the disclosure not only can distribute the message to the subscription terminal subscribed with the message topic, but also can distribute the message to the subscription terminal subscribed with the upper message topic of the message topic, and different message topics have connectivity due to the upper and lower subordinate relations of the topic tree, so that the message distribution is more flexible.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the disclosure and together with the description, serve to explain the principles of the disclosure and do not constitute an undue limitation on the disclosure.
FIG. 1 is a block diagram of a message distribution system shown in accordance with an exemplary embodiment;
FIG. 2a is a flow chart illustrating a message topic processing method in accordance with an exemplary embodiment;
FIG. 2b is a schematic diagram of a theme tree, shown, according to an example embodiment;
FIG. 3 is a schematic diagram of a server change topic tree shown in accordance with an exemplary embodiment;
FIG. 4 is a flow chart illustrating one embodiment of a message distribution method according to one exemplary embodiment;
FIG. 5a is a flow chart illustrating a message distribution method embodiment two according to an exemplary embodiment;
FIG. 5b is a flow chart illustrating a message distribution method embodiment three according to an exemplary embodiment;
FIG. 6 is a schematic diagram illustrating one subscription rule, according to an example embodiment;
FIG. 7 is a flow chart illustrating a message distribution method embodiment five according to an exemplary embodiment;
FIG. 8 is a flow chart illustrating a message distribution method embodiment six according to an exemplary embodiment;
FIG. 9 is a block diagram of a message publishing device according to an example embodiment;
FIG. 10 is a block diagram of a server device according to an exemplary embodiment;
fig. 11 is a block diagram of a message distribution apparatus according to an exemplary embodiment.
Detailed Description
In order to enable those skilled in the art to better understand the technical solutions of the present disclosure, the technical solutions of the embodiments of the present disclosure will be clearly and completely described below with reference to the accompanying drawings.
It should be noted that the terms "first," "second," and the like in the description and claims of the present disclosure and in the foregoing figures are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments of the disclosure described herein may be capable of operation in sequences other than those illustrated or described herein.
The implementations described in the following exemplary examples are not representative of all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present disclosure as detailed in the accompanying claims.
To facilitate an understanding of the technical architecture of the present disclosure by those skilled in the art, a message distribution system is provided. Fig. 1 is a block diagram of a message distribution system according to an exemplary embodiment. Referring to fig. 1, the message distribution system includes: a plurality of publication terminals 100, a plurality of subscription terminals 200, and a server 300 having a communication connection with the plurality of publication terminals 100 and the plurality of subscription terminals 200.
The server 300 herein may be implemented as a single server or may be implemented as a cluster of servers, and the disclosure is not limited to a specific implementation.
The present disclosure provides a message topic processing method, which may be applied to the server 300 shown in fig. 1, where the server 300 constructs a topic tree and stores the topic tree; the message topic processing method can also be applied to other processors besides the server, and the message topic processing method is sent to the server 300 after the other processors construct the topic tree, so that the server 300 can save the topic tree. Whether implemented within a server or outside a server, are within the scope of the present disclosure.
Fig. 2a is a flow chart illustrating a message topic processing method in accordance with an exemplary embodiment. Referring to fig. 2a, the message topic processing method comprises the steps of:
in step S201, a plurality of message topics and dependencies between the plurality of message topics are determined.
Because the message topics in the message distribution system in the related art are mutually independent and in the same level, the granularity of the message topics is thicker and has no layering sense. To increase the layering and fine granularity of message topics, three implementations are provided:
first implementation form: some sub-message topics can be added for the existing message topics based on the application scene, and some sub-message topics are added for the sub-message topics, so that the existing message topics are layered and granularity is thin. In this case, the plurality of message topics includes an existing message topic and an extended new message topic.
The second implementation form: and constructing proper subordinate relations among the existing message topics based on the application scene, so that the existing message topics are layered and have thin granularity. In this case, the plurality of message topics includes an existing message topic.
Third implementation: combining the first implementation with the second implementation.
Adding sub-message topics aiming at partial existing message topics based on the application scene, and adding sub-message topics for the sub-message topics; and constructing proper subordinate relations among part of existing message topics, so that the existing message topics are hierarchical and have small granularity. In this case, the plurality of message topics includes an existing message topic and an extended new message topic.
The three implementations can be selectively used according to actual application scenarios, and the disclosure is not limited thereto.
In step S202, a root node is created and a plurality of topic nodes corresponding to the message topics one by one are created;
since the subject tree is created in the subsequent step S203, any tree structure requires a root node. Here, the root node may create a non-subject root node, that is, the root node does not belong to the multiple message subjects determined in step S201, so as to avoid that the subscriber selects the root node as the subject node (the root node is a parent node of all the subject nodes, so selecting the root node is equivalent to selecting all the subject nodes, so that the root node is arranged as the non-subject root node in the actual scenario).
In addition, a plurality of topic nodes corresponding to the message topics one to one are needed to be created.
In step S203, a tree structure of the plurality of topic nodes and the root node is constructed according to the subordinate relations among the plurality of message topics, and the topic tree is generated.
According to the subordinate relations among the message topics in the step S201, the subordinate relations among the topic nodes are represented in a tree structure, and the father topic node at the highest level in the topic nodes is used for connecting root nodes, so that a topic tree is constructed. It will be appreciated that to distinguish between different topic nodes, each topic node has a different topic node identity.
If steps S201 to S203 are performed by the server shown in fig. 1, the server may store the subject tree.
If steps S201 to S203 are not performed by the server shown in fig. 1, other processors may send the topic tree to the server, so that the server may save the topic tree.
Through the technical features provided by the embodiment of fig. 2a, the present disclosure has the following beneficial effects:
the present disclosure provides for managing message topics in a topic tree that includes a root node and a plurality of topic nodes having affiliations, where the tree structure of parent and child topic nodes in the topic tree may express affiliations between topic nodes.
The subject nodes in the subject tree are subordinate relations, and not all subjects are in the same hierarchy, so that layering is achieved among the subject nodes. Also, a parent topic node may have at least one child topic node in the topic tree, so the granularity of the topic nodes may be tapered.
Because the topic nodes have the upper and lower subordinate relations and are not independent, the topic nodes have larger information quantity, the topic node formulation mode is more flexible and diversified, and the subscription relation is more diversified.
Because of the upper and lower subordinate relations between the topic nodes, under the condition that the topic explosion growth occurs when the subscription requirement is changed continuously, a subscriber can subscribe the father node shared by a plurality of topic nodes according to the requirement, so that the problem of message missing or message storm caused by too many choices and omission or too many message topics can be avoided.
FIG. 2b is a schematic diagram of a theme tree, shown, according to an example embodiment. Referring to fig. 2B, the topic tree includes a root node, under which a topic node a and a topic node B are included, under which a topic node C and a topic node D are included, and under which a topic node F is included. The subject node B includes a subject node E.
Each topic node in the topic tree has a unique identifier (topic id), in the illustration, the root node is identified as "0", the topic node A is identified as "1", the topic node B is identified as "2", the topic node C is identified as "3", the topic node D is identified as "4", the topic node E is identified as "5", and the topic node F is identified as "6".
The topic node may further include a subordinate path of the topic node in a topic tree, where the subordinate path is a topic node path from a root node in the topic tree to a topic node corresponding to the message topic. That is, the subordinate path of one subject node represents the subject node identifier to be passed through from the root node to reach the subject node, and the subordinate path can reflect the subordinate relationship of the subject node. Taking the subject node F as an example, the subordinate paths may be denoted as "0-1-4-6".
Because each subject node identity is unique, the subordinate path of each subject node is also unique. All the upper nodes of a subject node can be traced back through the subordinate paths. The sum of the subordinate paths of all the topic nodes in the topic tree can form a complete topic tree.
With the continuous progress of technology and the expansion of user demands in application scenarios, new topics may be added or existing topics may be deleted, so that the server may maintain a topic tree later in order to continuously adapt to the changes of the application scenarios.
FIG. 3 is a schematic diagram of a server change topic tree, shown in accordance with an exemplary embodiment.
First case: and adding a topic node corresponding to the new topic under the condition that a new topic needs to be added and a father topic node identification is specified in the topic tree.
In the case that a new topic needs to be added, the server can receive an addition request for adding the new message topic; wherein the add request includes a new message topic and an upper message topic to which the new message topic belongs; determining topic nodes corresponding to the upper level message topics in the topic tree; and adding a topic node corresponding to the new message topic to the topic node in the topic tree.
Second case: and deleting the topic corresponding to the existing topic in the topic tree under the condition that the existing topic needs to be deleted, and deleting the existing topic and the subtopic of the existing topic in the preset topic node configuration of the subscription terminal.
In the case that the existing subject needs to be deleted, the server may receive a deletion request for deleting the subject of the existing message; wherein the delete request includes an existing message topic; deleting the topic node corresponding to the existing message topic in the topic tree, and deleting the child node of the topic node corresponding to the existing message topic.
And sending a deleting instruction to a subscription terminal subscribed with the topic node and the child node corresponding to the existing message topic, so that the subscription terminal deletes the topic node and the child node corresponding to the existing message topic in preset topic node configuration.
According to the embodiment, in the case that the message theme needs to be changed, only the theme nodes in the theme tree need to be changed, and code configuration in the publishing terminal and the subscribing terminal does not need to be modified for each changed theme. In addition, because the topic nodes have the upper and lower subordinate relations, under the condition that the topic nodes are changed, the topic nodes can be changed through the subordinate relations among the message topics, so that the management and maintenance of the message topics are more convenient.
According to an embodiment of the present application, in order to make the method still applicable to the message distribution method and the message publishing method in the case of a change of the topic tree, the preset topic node configuration of the subscription terminal and the publishing topic configuration of the publishing terminal may be modified synchronously (or the preset topic node configuration of the subscription terminal and the publishing topic configuration of the publishing terminal may not be modified) in the case of a change of the topic tree.
First case: the topic tree adds new topic nodes.
For a distribution terminal: after the new topic nodes are added to the topic tree, a reminding message can be sent to each release terminal so that each release terminal can check whether the release topic configuration of the release terminal needs to be expanded. If so, the publishing terminal can add a new message theme in the local publishing theme configuration, and if not, the publishing terminal does not operate the local publishing theme configuration.
For a subscribing terminal: after the new topic node is added to the topic tree, a reminding message can be sent to each subscription terminal so that each subscription terminal can check whether the preset topic node configuration of the subscription terminal needs to be expanded or not.
If the subscriber needs, the server receives the subscription instruction of the subscription terminal, and adds a new message theme added in the theme tree in the preset theme node configuration of the subscription terminal. If the subscriber does not need, the server receives the order that the subscriber terminal refuses the subscription or does not receive any order, and the default continues to use the preset topic node configuration of the subscriber terminal without adding new message topics.
Second case: the topic tree deletes the existing topic nodes.
For a distribution terminal: under the condition that existing topic nodes and sub-topic nodes thereof are deleted in the topic tree, in order to ensure absolute correctness, the existing topic nodes and sub-topic nodes thereof related to the distribution topic configuration of each distribution terminal can be deleted together. Without deletion, the publisher may be caused to select an invalid topic node, affecting the user experience.
For a subscribing terminal: in the case of deleting the existing topic nodes and the sub-topic nodes thereof in the topic tree, in order to ensure absolute correctness, the existing topic nodes and the sub-topic nodes thereof in the preset topic node configuration of each subscription terminal can be deleted together. Therefore, the configuration of the preset topic nodes can be simplified, and invalid topic nodes can be deleted.
The present disclosure provides a first embodiment of a message distribution method, which is applied to the server shown in fig. 1. Taking a system fault maintenance application scenario as an example, the message distribution method is described together. In this case, the message may be a fault content, and the message subject may be a fault type, such as a port fault, a network fault, a device fault, and the like.
Fig. 4 is a flow chart illustrating one embodiment of a message distribution method according to one exemplary embodiment. See fig. 4. A first embodiment of a message distribution method may include the steps of:
step S301: and responding to the message data publishing operation, and determining the message subject to which the message in the message data belongs.
Step S302: determining a subordinate path of the message topic in a topic tree; the subordinate path is a topic node path from a root node in the topic tree to a topic node corresponding to the message topic.
Step S303: and distributing the message to a subscription terminal subscribed with any topic node in the subordinate path.
The embodiment shown in fig. 4 may be described in detail with reference to the embodiment shown in fig. 5a, and will not be described again here.
The technical scheme provided by the embodiment of the disclosure at least brings the following beneficial effects:
the present disclosure provides for managing message topics in a topic tree that employs a tree structure among a plurality of topic nodes in the topic tree to represent dependencies, i.e., the topics are no longer at the same level, but have upper and lower dependencies.
After determining the message topic to which the message belongs, the present disclosure may further determine a subordinate path of the message topic in the topic tree, where the subordinate path includes each topic node from a root node in the topic tree to a topic node corresponding to the message topic, and then may be distributed to a subscription terminal subscribed to any topic node in the subordinate path.
The scheme provided by the disclosure not only can distribute the message to the subscription terminal subscribed with the message topic, but also can distribute the message to the subscription terminal subscribed with the upper message topic of the message topic, and different message topics have connectivity due to the upper and lower subordinate relations of the topic tree, so that the message distribution is more flexible.
The topic tree has a plurality of topic nodes with subordinate relations, so that layering sense can be provided among the topic nodes. Furthermore, the parent topic node may have at least one child topic node in the topic tree, which may enable the granularity of the topic nodes to be tapered compared to the prior art where the topic nodes are independent of each other.
Fig. 5a is a flow chart illustrating a message distribution method embodiment two according to an exemplary embodiment. Referring to fig. 5a, the following steps may be included:
in step S401, the publishing terminal determines a message and a message topic.
When the issuing terminal finds that a fault occurs, the issuing terminal can determine fault content (such as unrecognizable ports, machine downtime, excessive device temperature and the like) and generate a message containing the fault content.
The publishing terminal may employ two implementations to determine the message topic.
The first implementation mode:
the distribution terminal displays the local distribution topic configuration and selects the appropriate message topic from the same.
The second implementation mode:
and acquiring the latest topic tree from the server side, and selecting a proper message topic from the topic tree.
Either implementation may be implemented, and the particular implementation may depend on the particular application scenario, which is not limited.
In step S402, the issuing terminal constructs message data.
The distribution terminal constructs message data including a message and a message topic.
In step S403, the publishing terminal transmits the message data to the server.
In step S404, the server receives the message data.
In step S405, the server determines the message topic of the message data in the topic tree.
The server receives the message data sent by the issuing terminal and acquires the message and the message theme from the message data. The topic tree comprises a root node of a non-topic and a plurality of topic nodes with subordinate relations.
In step S406, the server stores the message data.
The server may store message data in a message queue.
In the case that the message queues are classified according to the message topics, the server may store the message data into the message queues corresponding to the message topics. Message distribution and message distribution are performed asynchronously, so the server stores the message first and then distributes the message.
In step S407, the server acquires the message data and determines the message topic of the message data. The server may extract message data from a message queue, which may be a first-in-first-out queue, and the server may process messages in the message queue one by one.
If the message queue is not classified by message topic in step S406, the server may extract the message and message topic from the message data. If the message queues in step S406 are classified by message topic, the server may directly determine the message topic based on the message queues, and extract the message from the message data.
In step S408, the server determines a subordinate path of the message topic in the topic tree.
In the case that the topic nodes in the topic tree contain subordinate paths, the subordinate paths can be directly extracted from the message topic nodes corresponding to the message topics in the topic tree.
In the case where the subject nodes in the subject tree do not contain subordinate paths, the following steps may be employed to determine the subordinate paths of the message subject in the subject tree including:
step S11: determining a topic node corresponding to the message topic in the topic tree;
step S12: querying a parent node of the topic node upwards in the topic tree;
step S13: repeatedly executing parent node operation of inquiring the parent node upwards in the theme tree until the parent node is a root node;
step S14: and determining a topic node path from a root node in the topic tree to a topic node corresponding to the message topic as the subordinate path.
That is, after determining the message topic, the server may determine the location of the message topic node in the topic tree based on the message topic, and then trace the location of the message topic node to the root node. The path from the root node to the message topic node in the topic tree is the subordinate path of the message topic in the topic tree.
Referring to fig. 2b, taking the subject node F as an example, its subordinate path is: 0-1-4-6.
In step S409, the server distributes the message to the subscription terminal subscribed to any topic node in the subordinate path.
The subordinate path can be used for judging whether the two subject nodes have the upper-lower relationship. If the subordinate path of one topic node contains another topic node identification, another topic node is represented as an upper topic node of the topic node. See "topic F" in FIG. 2b, whose subordinate paths are "0-1-4-6", then their upper level topic node identifications are "0", "1", "4", respectively.
To ensure that subscribers do not miss interesting messages, this disclosure indicates that the subscription topic has downward one-way transitivity. For a subscription terminal, if the subscription terminal subscribes to an upper level topic node, the subscription terminal may have a subscription relationship between the upper level topic node and all lower level topics.
For example, a subscription terminal subscribes to topic node a, then it is equivalent to subscription terminal subscribing to topic node a, topic node C, topic node D, and topic node F; when the message topic of the published message is any one of the topic node A, the topic node C, the topic node D and the topic node F, the message is sent to the subscription terminal, so that the subscriber cannot miss the interested message.
To avoid subscribers receiving uninteresting messages, the lower level topic nodes cannot possess the subscription relationship of the upper level topic nodes. For example, a subscription terminal subscribes to topic node D, then it is equivalent to subscription terminal subscribing to topic node D and topic node F; under the condition that the message topic of the published message is the topic node A, the message is not sent to the subscription terminal, so that the subscriber is prevented from receiving irrelevant messages, and excessive messages are prevented.
In order to ensure that the subscriber does not miss the interesting message and avoid the subscriber receiving the interesting message, the server may determine whether the preset topic node configuration of each subscriber terminal has an intersection with the subordinate path, that is, determine whether the preset topic node configuration and the subordinate path have the same topic node.
If the preset topic node configuration of a subscription terminal has an intersection with the subordinate path, the subscription terminal is subscribed with the upper topic node of the message topic, so that the message is distributed to ensure that the subscriber cannot miss the interested message.
If the preset topic node configuration of a subscription terminal does not have intersection with the subordinate path, if the upper topic node and the message topic of the message topic are not subscribed by the subscription terminal, the message is not distributed to the subscription terminal, so that the subscriber is prevented from receiving the uninteresting message.
Step S410: the subscriber terminal receives and displays the message.
Through the technical features provided by the embodiment of fig. 5a, the present disclosure has the following beneficial effects:
because the topic tree has the advantages of multiple layers and granularity thinning, the message can be accurately endowed with the message topic with proper granularity, and the message distribution with finer granularity can be realized based on the topic tree. And in the process of distributing the message based on the topic tree, the subscription relationship between topic nodes can be transferred and inherited according to the subordinate relationship between topic nodes on the topic tree.
The embodiment can execute the message publishing operation and the message distributing operation based on the topic tree, and the downward unidirectional transitivity of the subscription relationship can be realized by means of the affiliation of the topic nodes in the topic tree due to the affiliation of the topic nodes in the topic tree.
The subscription terminal subscribed with the upper topic node can enjoy the subscription relation of the upper topic node and the lower topic node, thereby realizing the purpose of ensuring that the subscriber cannot miss the interested message. A subscription terminal subscribed with a lower topic node cannot enjoy the subscription relation of an upper topic node so as to avoid that a subscriber receives uninteresting messages.
Because the topic tree is formulated according to the service requirement in the application scene, under the condition that technicians worry about excessive received messages, only interested subordinate topic nodes can be formulated, so that the technicians do not worry about excessive received messages any more; the technology director can customize the upper level topic nodes so as to avoid missing messages for any lower level topic node.
In the prior art, because topics are independent and have no hierarchy, the preset topic node configuration of the subscription terminal needs to be synchronously modified every time a new topic is added. In the present disclosure, due to the downward unidirectional transitivity, if an upper level topic node is subscribed, if the upper level topic node is newly added with a lower level topic node, the subscription terminal can enjoy the subscription relationship of the new topic node without changing the configuration of the preset topic node.
The present disclosure provides a third embodiment of a message distribution method, which is applied to the server shown in fig. 1. On the basis of the second embodiment of the message distribution method, event tag screening is added.
Fig. 5b is a flow chart illustrating a message distribution method embodiment three according to an exemplary embodiment. Referring to fig. 5b, the method comprises the steps of:
In step S501, the publishing terminal determines a message, a message subject, and an event tag.
The event tag is to illustrate the message from another point of view outside the subject, as compared to the addition of the event tag in step S401.
In step S502, the issuing terminal constructs message data.
The publishing terminal constructs message data comprising the message, the message topic and the event tag.
In step S503, the publishing terminal transmits message data to the server.
In step S504, the server receives the message data.
In step S505, the server determines the message topic of the message data in the topic tree.
In step S506, the server stores the message data.
In step S507, the server acquires the message data and determines the message topic and event tag of the message data. The server may extract message data from the message queue and extract event tags from the message data.
In step S508, the server determines a subordinate path of the message topic in the topic tree.
In step S509, the server distributes the message to the subscribing terminal subscribed to any topic node in the subordinate path and subscribed to the event tag.
The server judges whether the preset theme node configuration of the subscription terminal has intersection with the subordinate path. If the intersection exists, judging whether the preset event label configuration of the subscription terminal comprises the event label or not. And if the preset event label configuration of the subscription terminal comprises the event label, distributing the message to the subscription terminal.
In this embodiment, the topic tree and the event tag are used in cooperation, and a message can be received by a subscriber only if the preset topic node configuration of the subscriber terminal is satisfied, but also if the interesting time tag configuration of the subscriber terminal is satisfied.
FIG. 6 is a schematic diagram illustrating one subscription rule, according to an example embodiment.
Referring to fig. 6, the subscription rules for subscribers are: topic a and event label "tag=a", then the message topic representing a message is topic a or lower topic C and carries label "tag=a", before it can be sent to the subscriber's subscription terminal; other unrelated topics, such as topic B, or other event tags, such as Tag "tag=b", are determined to be not compliant with the subscription rules and are not sent to the subscriber.
Step S510: the subscriber terminal receives and displays the message.
In the embodiment, the topic and the event label are matched, and two dimensions are adopted to screen the message, so that a subscriber can obtain the required message more accurately. The steps in the second embodiment of the message distribution method may be referred to in the detailed description of the first embodiment of the message distribution method, and will not be described herein.
In the above embodiment, the publishing terminal determines the message theme when publishing the message, and another application scenario is provided below, where the publishing terminal only sends the message and the publishing terminal is not required to determine the message theme.
The present disclosure provides a fourth embodiment of a message distribution method, which is applied to the server shown in fig. 1. The method for distributing the message will be described together by taking application scenes of short video applications (such as fast hands, tremble sounds, etc.), text sharing applications (such as well-known, jian Shu, etc.), video websites (Tencent, aiqi, etc.) as examples. In this case, the message may be short video, article, image, etc., and the message subject may be a message type, such as emotion type, military type, international type, etc.
Fig. 7 is a flow chart illustrating a message distribution method embodiment five according to an exemplary embodiment. Referring to fig. 7, the following steps may be included:
in step S701, a terminal determination message is issued.
The distribution terminal can freely distribute some messages, so the messages are not limited by the distribution terminal. The publishing terminal can determine the message, and the message can be short video, article or image and other contents in different application scenes.
In step S702, the issuing terminal constructs message data.
The distribution terminal constructs message data containing the message.
In step S703, the publishing terminal transmits message data to the server.
In step S704, the server receives the message data.
In step S705, the server identifies the message data and determines the message topic of the message data in the topic tree.
The server executes the identification operation corresponding to the application scene on the message to determine the message theme. In the case where the message is a video class or an image class, the message topic of the message data may be determined based on image recognition. In the case where the message is a literal, the message topic of the message data may be determined based on natural language processing techniques.
In step S706, the server stores the message data.
In step S707, the server acquires the message data and determines the message topic of the message data.
In step S708, the server determines a subordinate path of the message topic in the topic tree.
In step S709, the server distributes the message to the subscription terminal subscribed to any topic node in the subordinate path.
Step S710: the subscriber terminal receives and displays the message.
Compared with the first embodiment of the message distribution method, the message theme can be automatically identified by the server, so that the situation applicable to different application scenes is increased. The steps in the fifth embodiment of the message distribution method may be referred to in the detailed description of the first embodiment of the message distribution method, and will not be described herein.
The present disclosure provides a sixth embodiment of a message distribution method, which is applied to the server shown in fig. 1. On the basis of the fifth embodiment, an event tag is added.
Fig. 8 is a flowchart illustrating a message distribution method embodiment six according to an exemplary embodiment. Referring to fig. 8, the following steps may be included:
in step S801, the issuing terminal determines a message and an event tag.
The distribution terminal can freely distribute some messages, so the messages are not limited by the distribution terminal. The publishing terminal can determine the message, and the message can be short video, article or image and other contents in different application scenes. The message may carry an event tag, such as "# spring festival evening party #".
In step S802, the issuing terminal constructs message data.
The publishing terminal constructs message data comprising the message and the event tag.
In step S803, the publishing terminal transmits the message data to the server.
In step S804, the server receives the message data.
In step S805, the server determines a message topic and an event tag of the message data.
The server executes the identification operation corresponding to the application scene on the message to determine the message theme. In the case where the message is a video class or an image class, the message topic of the message data may be determined based on image recognition. In the case where the message is a literal, the message topic of the message data may be determined based on natural language processing techniques.
The server extracts the event tag from the message data.
In step S806, the server stores the message data.
In step S807, the server acquires the message data and determines the message subject of the message data.
In step S808, the server determines the subordinate paths of the message topic in the topic tree.
In step S809, the server distributes the message to the subscribing terminals subscribed to any topic node in the subordinate path and to event tags.
The server judges whether the preset theme node configuration of the subscription terminal has intersection with the subordinate path. If the intersection exists, judging whether the preset event label configuration of the subscription terminal comprises the event label or not. And if the preset event label configuration of the subscription terminal comprises the event label, distributing the message to the subscription terminal.
In this embodiment, the topic tree and the event tag are used in cooperation, and a message can be received by a subscriber only if the preset topic node configuration of the subscriber terminal is satisfied, but also if the interesting time tag configuration of the subscriber terminal is satisfied.
Step S810: the subscriber terminal receives and displays the message.
Compared with the second embodiment of the message distribution method, the message theme can be automatically identified by the server, and the situation applicable to different application scenes is increased. The steps in the sixth embodiment of the message distribution method may be described in detail in the second embodiment of the message subscription method, which is not described herein.
Fig. 9 is a block diagram of a server device, according to an example embodiment. Referring to fig. 10, the message distribution apparatus includes:
a determining topic unit 91 configured to perform a publishing operation in response to message data, determining a message topic to which a message in the message data belongs;
a determining path unit 92 configured to perform determining a subordinate path of the message topic in a topic tree; the subordinate path is a topic node path from a root node in the topic tree to a topic node corresponding to the message topic;
a distributing unit 93 configured to perform distribution of the message to subscription terminals subscribed to any subject node in the subordinate path.
Wherein the determining path unit 92 includes:
a first determining unit 921 configured to perform determining that the message topic corresponds to a topic node in the topic tree;
a second determining unit 922 configured to perform an upward query of a parent node of the subject node in the subject tree;
a query unit 923 configured to perform a parent node operation of repeatedly performing an upward query on the parent node in the subject tree until the parent node is a root node;
a third determining unit 924 is configured to perform determining, as the subordinate path, a topic node path between a root node in the topic tree and a topic node corresponding to the message topic.
Wherein the distribution unit 93 includes:
the first determining unit 11 is configured to perform determining whether the preset topic node configuration of the subscription terminal intersects with the subordinate path, and specifically includes: judging whether the preset subject node configuration and the subordinate path have the same subject node or not;
a first distribution message unit 12 configured to perform distribution of the message to the subscriber terminal if there is an intersection.
The message data also comprises event labels to which the messages belong; the distribution unit 93 comprises:
a second judging unit 21 configured to perform judgment as to whether the preset subject node configuration and the subordinate path have the same subject node;
a third judging unit 22 configured to execute, if there is an intersection, judging whether a preset event tag configuration of the subscription terminal includes the event tag;
a second message distribution unit 23 configured to perform distribution of the message to the subscriber terminal if a preset event tag configuration of the subscriber terminal includes the event tag.
The message distribution device further comprises:
a build topic tree unit 94 configured to perform determining a plurality of message topics and dependencies between the plurality of message topics, create a root node and create a plurality of topic nodes corresponding to the plurality of message topics one by one, build a tree structure of the plurality of topic nodes and the root node according to the dependencies between the plurality of message topics, and generate the topic tree.
An adding unit 95 configured to perform receiving an add request to add a new message topic; wherein the add request includes a new message topic and an upper message topic to which the new message topic belongs; determining topic nodes corresponding to the upper level message topics in the topic tree; and adding a topic node corresponding to the new message topic to the topic node in the topic tree.
A deletion unit 96 configured to perform receiving a deletion request to delete an existing message topic; wherein the delete request includes an existing message topic; deleting the topic node corresponding to the existing message topic in the topic tree, and deleting the child node of the topic node corresponding to the existing message topic;
the sending unit 97 is configured to send a deletion instruction to a subscription terminal subscribed with a topic node corresponding to the existing message topic and a child node thereof, so that the subscription terminal deletes the topic node corresponding to the existing message topic and the child node thereof in a preset topic node configuration.
Fig. 10 is a block diagram of a server device, according to an example embodiment. Referring to fig. 10, comprising:
a processor 1000;
a memory 1001 for storing the processor-executable instructions;
Wherein the processor is configured to execute the instructions to implement any one of the first to sixth embodiments of the message issuing method.
Fig. 11 is a block diagram of a server device, according to an example embodiment. Referring to fig. 11, comprising:
a processor 1100;
a memory 1101 for storing the processor-executable instructions;
wherein the processor is configured to execute the instructions to implement any one of the first to sixth embodiments of the message distribution method.
The specific manner in which the various modules perform the operations in the apparatus of the above embodiments have been described in detail in connection with the embodiments of the method, and will not be described in detail herein.
In an exemplary embodiment, a storage medium is also provided, e.g., a memory, comprising instructions executable by the processor 1000 of fig. 10 to perform any one of the first through sixth embodiments of the message issuing method.
In an exemplary embodiment, a storage medium is also provided, e.g., a memory, comprising instructions executable by the processor 1100 of fig. 11 to perform any one of the first through sixth embodiments of the message distribution method.
Alternatively, the storage medium may be a non-transitory computer readable storage medium, which may be, for example, ROM, random Access Memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, and the like.
The present disclosure also provides a computer program product that, when executed by a processor of a server, enables the server to perform a message publishing method.
The present disclosure also provides a computer program product that, when executed by a processor of a server, enables the server to perform a message distribution method.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This disclosure is intended to cover any adaptations, uses, or adaptations of the disclosure following the general principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
It is to be understood that the present disclosure is not limited to the precise arrangements and instrumentalities shown in the drawings, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.
Claims (15)
1. A method of message distribution, comprising:
responding to a message data publishing operation, and determining a message theme to which a message in the message data belongs;
determining a subordinate path of the message topic in a topic tree; the subordinate path is a topic node path from a root node in the topic tree to a topic node corresponding to the message topic;
and distributing the message to a subscription terminal subscribed with any topic node in the subordinate path.
2. The message distribution method of claim 1, wherein the determining a subordinate path of the message topic in a topic tree comprises:
determining a topic node corresponding to the message topic in the topic tree;
querying a parent node of the topic node upwards in the topic tree;
repeatedly executing parent node operation of inquiring the parent node upwards in the theme tree until the parent node is a root node;
And determining a topic node path from a root node in the topic tree to a topic node corresponding to the message topic as the subordinate path.
3. The message distribution method according to claim 1 or 2, wherein the distributing the message to a subscribing terminal subscribed to any topic node in the subordinate path comprises:
judging whether the preset theme node configuration of the subscription terminal has intersection with the subordinate path or not specifically comprises the following steps: judging whether the preset subject node configuration and the subordinate path have the same subject node or not;
if there is an intersection, the message is distributed to the subscriber terminal.
4. The message distribution method according to claim 1 or 2, wherein the message data further includes an event tag to which the message belongs;
the distributing the message to the subscribing terminal subscribed to any topic node in the subordinate path comprises:
judging whether the preset theme node configuration of the subscription terminal has intersection with the subordinate path or not specifically comprises the following steps: judging whether the preset subject node configuration and the subordinate path have the same subject node or not;
if the intersection exists, judging whether the preset event tag configuration of the subscription terminal comprises the event tag or not;
And if the preset event label configuration of the subscription terminal comprises the event label, distributing the message to the subscription terminal.
5. The message distribution method according to claim 1, characterized by further comprising:
receiving an increase request for increasing a new message topic; wherein the add request includes a new message topic and an upper message topic to which the new message topic belongs;
determining topic nodes corresponding to the upper level message topics in the topic tree;
and adding a topic node corresponding to the new message topic to the topic node in the topic tree.
6. The message distribution method according to claim 1 or 5, characterized by further comprising:
receiving a deleting request for deleting the existing message theme; wherein the delete request includes an existing message topic;
deleting the topic node corresponding to the existing message topic in the topic tree, and deleting the child node of the topic node corresponding to the existing message topic;
and sending a deleting instruction to a subscription terminal subscribed with the topic node and the child node corresponding to the existing message topic, so that the subscription terminal deletes the topic node and the child node corresponding to the existing message topic in preset topic node configuration.
7. A message distribution apparatus, comprising:
a determining subject unit configured to perform a publishing operation in response to message data, determining a message subject to which a message in the message data belongs;
a determining path unit configured to perform determining a subordinate path of the message topic in a topic tree; the subordinate path is a topic node path from a root node in the topic tree to a topic node corresponding to the message topic;
and the distribution unit is configured to perform distribution of the message to subscription terminals subscribed with any topic node in the subordinate path.
8. The message distribution apparatus according to claim 7, wherein the determination path unit includes:
a first determining unit configured to perform determining that the message topic corresponds to a topic node in the topic tree;
a second determining unit configured to perform an upward query of a parent node of the subject node in the subject tree;
a query unit configured to perform parent node operations of repeatedly performing upward queries of the parent node in the subject tree until the parent node is a root node;
and the third determining unit is configured to determine a topic node path from a root node in the topic tree to a topic node corresponding to the message topic as the subordinate path.
9. The message distribution apparatus according to claim 7 or 8, wherein the distribution unit includes:
the first judging unit is configured to execute judgment on whether the preset theme node configuration of the subscription terminal has intersection with the subordinate path, and specifically includes: judging whether the preset subject node configuration and the subordinate path have the same subject node or not;
a first distributing message unit configured to perform distributing the message to the subscriber terminal if there is an intersection.
10. The message distribution apparatus according to claim 7 or 8, wherein the message data further includes an event tag to which the message belongs;
the distribution unit comprises:
a second judging unit configured to perform judgment as to whether the preset subject node configuration and the subordinate path have the same subject node;
a third judging unit configured to execute, if there is an intersection, judging whether a preset event tag configuration of the subscription terminal includes the event tag;
and the second message distribution unit is configured to execute the distribution of the message to the subscription terminal if the preset event tag configuration of the subscription terminal comprises the event tag.
11. The message distribution apparatus according to claim 7, further comprising:
an adding unit configured to perform receiving an add request to add a new message topic; wherein the add request includes a new message topic and an upper message topic to which the new message topic belongs; determining topic nodes corresponding to the upper level message topics in the topic tree; and adding a topic node corresponding to the new message topic to the topic node in the topic tree.
12. The message distribution apparatus according to claim 7 or 11, characterized by further comprising:
a deletion unit configured to perform receiving a deletion request to delete an existing message topic; wherein the delete request includes an existing message topic; deleting the topic node corresponding to the existing message topic in the topic tree, and deleting the child node of the topic node corresponding to the existing message topic;
the sending unit is configured to send a deleting instruction to a subscription terminal subscribed with the topic node corresponding to the existing message topic and the child node thereof, so that the subscription terminal deletes the topic node corresponding to the existing message topic and the child node thereof in the preset topic node configuration.
13. A server, comprising:
a processor;
a memory for storing the processor-executable instructions;
wherein the processor is configured to execute the instructions to implement the message distribution method of any of claims 1 to 6.
14. A storage medium, which when executed by a processor of a server, enables the server to perform the message distribution method of any one of claims 1 to 6.
15. A message distribution system, comprising:
a plurality of publishing terminals, a plurality of subscribing terminals and a server in communication connection with the plurality of publishing terminals and the plurality of subscribing terminals;
the release terminal is used for constructing message data and releasing the message data to the server;
the server is configured to implement the message distribution method according to any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010691554.6A CN111814091B (en) | 2020-07-17 | 2020-07-17 | Message distribution method and related device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010691554.6A CN111814091B (en) | 2020-07-17 | 2020-07-17 | Message distribution method and related device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111814091A CN111814091A (en) | 2020-10-23 |
| CN111814091B true CN111814091B (en) | 2023-11-28 |
Family
ID=72866139
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010691554.6A Active CN111814091B (en) | 2020-07-17 | 2020-07-17 | Message distribution method and related device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111814091B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113239307A (en) * | 2021-05-17 | 2021-08-10 | 北京百度网讯科技有限公司 | Method and device for storing message theme |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101193077A (en) * | 2006-11-30 | 2008-06-04 | 国际商业机器公司 | Method and system for subscribing matching |
| CN102859541A (en) * | 2010-04-19 | 2013-01-02 | 国际商业机器公司 | Controlling message delivery in publish/subscribe messaging |
| CN107888499A (en) * | 2017-11-17 | 2018-04-06 | 北京邮电大学 | A kind of distribution subscription system and message forwarding method based on SDN |
| CN110557423A (en) * | 2018-06-04 | 2019-12-10 | 珠海全志科技股份有限公司 | message pushing method and system |
| CN111159382A (en) * | 2019-12-27 | 2020-05-15 | 苏州思必驰信息科技有限公司 | Method and device for constructing and using session system knowledge model |
-
2020
- 2020-07-17 CN CN202010691554.6A patent/CN111814091B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101193077A (en) * | 2006-11-30 | 2008-06-04 | 国际商业机器公司 | Method and system for subscribing matching |
| CN102859541A (en) * | 2010-04-19 | 2013-01-02 | 国际商业机器公司 | Controlling message delivery in publish/subscribe messaging |
| CN107888499A (en) * | 2017-11-17 | 2018-04-06 | 北京邮电大学 | A kind of distribution subscription system and message forwarding method based on SDN |
| CN110557423A (en) * | 2018-06-04 | 2019-12-10 | 珠海全志科技股份有限公司 | message pushing method and system |
| CN111159382A (en) * | 2019-12-27 | 2020-05-15 | 苏州思必驰信息科技有限公司 | Method and device for constructing and using session system knowledge model |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111814091A (en) | 2020-10-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108170428B (en) | Page construction processing method, device and system | |
| CN109889424B (en) | Information processing method, device and storage medium | |
| US9110884B2 (en) | Message publishing and subscribing method and apparatus | |
| CN111813570A (en) | Event-driven message interaction method for power Internet of things | |
| CN111970198A (en) | Service routing method, device, electronic equipment and medium | |
| US20130226878A1 (en) | Seamless context transfers for mobile applications | |
| CN107908637B (en) | Entity updating method and system based on knowledge base | |
| US10764233B1 (en) | Centralized communication platform with email which organizes communication as a plurality of information streams and which generates a second message based on and a first message and formatting rules associated with a communication setting | |
| US20230046891A1 (en) | Asynchronous execution of tasks and ordering of task execution | |
| US20170193084A1 (en) | Systems and methods for multi-protocol, multi-format universal searching | |
| US20190138424A1 (en) | Systems and methods for safely implementing web page updates | |
| WO2014066554A2 (en) | Event search engine for web-based applications | |
| CN111814091B (en) | Message distribution method and related device | |
| CN113779422B (en) | Method and device for realizing relationship chain label, electronic equipment and storage medium | |
| US10708217B1 (en) | Efficient creation of drafts associated with sponsored content | |
| CN112511868B (en) | Video playing method and device, electronic equipment and computer storage medium | |
| US20170193051A1 (en) | Systems and methods for automatic archiving, sorting, and/or indexing of secondary message content | |
| CN110839061B (en) | Data distribution method, device and storage medium | |
| US20150134562A1 (en) | Image index routing | |
| CN113965538B (en) | Equipment state message processing method, device and storage medium | |
| CN110520878A (en) | Organized programmable intranet sending out notice | |
| US20180157733A1 (en) | Systems and methods for generating content | |
| CN110908745B (en) | Data analysis display method and system, storage medium, server and client | |
| CN112306984A (en) | Data source routing method and device | |
| Nikkar et al. | Transmission of multimedia content between social networks without reloading |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |