CN112307318B - Content publishing method, system and device - Google Patents
Content publishing method, system and device Download PDFInfo
- Publication number
- CN112307318B CN112307318B CN201910712968.XA CN201910712968A CN112307318B CN 112307318 B CN112307318 B CN 112307318B CN 201910712968 A CN201910712968 A CN 201910712968A CN 112307318 B CN112307318 B CN 112307318B
- Authority
- CN
- China
- Prior art keywords
- subscription
- event
- primary
- topic
- matching
- 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 46
- 238000012986 modification Methods 0.000 claims description 16
- 230000004048 modification Effects 0.000 claims description 16
- 238000013507 mapping Methods 0.000 claims description 15
- 238000004891 communication Methods 0.000 description 5
- 238000010586 diagram Methods 0.000 description 4
- 230000004044 response Effects 0.000 description 4
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 3
- 238000012545 processing Methods 0.000 description 3
- 238000012360 testing method Methods 0.000 description 3
- 230000005540 biological transmission Effects 0.000 description 2
- 238000001514 detection method Methods 0.000 description 2
- 238000003491 array Methods 0.000 description 1
- 238000012512 characterization method Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000008569 process Effects 0.000 description 1
- 230000000007 visual effect Effects 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/953—Querying, e.g. by the use of web search engines
- G06F16/9535—Search customisation based on user profiles and personalisation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/30—Information retrieval; Database structures therefor; File system structures therefor of unstructured textual data
- G06F16/31—Indexing; Data structures therefor; Storage structures
- G06F16/316—Indexing structures
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/30—Information retrieval; Database structures therefor; File system structures therefor of unstructured textual data
- G06F16/33—Querying
- G06F16/3331—Query processing
- G06F16/334—Query execution
- G06F16/3344—Query execution using natural language analysis
Abstract
The embodiment of the invention provides a content publishing method, a content publishing system and a content publishing device, wherein the content publishing method comprises the following steps: acquiring an event to be issued, which is sent by an issuing client, wherein the event to be issued comprises an event theme and an event attribute; acquiring subscription conditions sent by all subscription clients, wherein the subscription conditions carry subscription topics and topic labels; creating a multi-level index structure according to all the subscription topics; matching the event theme of the event to be issued with subscription themes stored by all root nodes in the multi-level index structure; if the matching is successful, matching the event attribute with the primary topic label stored in the primary node and the secondary topic label stored in the secondary node, which are connected with the root node of the successful matching, one by one, so as to obtain the primary topic label and the secondary topic label of the successful matching; and transmitting the event to be issued to a target subscription client with successfully matched primary topic labels and secondary topic labels. The technical scheme provided by the invention can solve the problem of low subscription matching efficiency in the prior art.
Description
[ field of technology ]
The present invention relates to the field of content publishing technologies, and in particular, to a content publishing method, system, and device.
[ background Art ]
At present, with the rapid development of computer technology, great impact is generated on the traditional teaching mode and knowledge transmission mode. By means of the content management system, expertise and teaching ideas can be easily used for creating rich websites. In the existing content publishing system, when a subscriber wants to subscribe to an event to acquire required information, the subscription matching efficiency is low because of more content in the system.
[ invention ]
In view of the above, the embodiments of the present invention provide a method, a system, and an apparatus for publishing content, which are used to solve the problem of low subscription matching efficiency in the prior art.
In order to achieve the above object, according to one aspect of the present invention, there is provided a content distribution method including: acquiring an event to be issued, which is sent by an issuing client, wherein the event to be issued comprises an event theme and an event attribute; acquiring subscription conditions sent by all subscription clients, wherein the subscription conditions carry subscription topics and topic labels; creating a multi-level index structure according to all the subscription topics, wherein the multi-level index structure comprises root nodes, primary nodes connected with the root nodes and secondary nodes connected with the primary nodes, each root node stores the subscription topics, each primary node stores a primary topic label, each secondary node stores a secondary topic label, and all the nodes store corresponding subscription client identifiers; matching the event theme of the event to be issued with subscription themes stored by all root nodes in the multi-level index structure; if the matching is successful, matching the event attribute with a primary topic label stored in a primary node and a secondary topic label stored in a secondary node which are connected with the root node of the successful matching one by one to obtain a primary topic label and a secondary topic label of the successful matching; and transmitting the event to be issued to a target subscription client which is successfully matched with the primary topic label and the secondary topic label, wherein the target subscription client comprises subscription client identifiers stored by the node where the secondary topic label is successfully matched.
Optionally, after the obtaining the event to be issued sent by the issuing client, the method further includes: determining a primary attribute tag and a secondary attribute tag of the event to be issued according to the event attribute of the event to be issued and a preset tag mapping table, wherein the tag mapping table comprises the corresponding relation between a field representing the event attribute and the primary attribute tag and the secondary attribute tag; matching the first-level attribute tag of the event to be issued with the first-level theme tag stored in each first-level node connected with the successfully matched root node to obtain the successfully matched first-level theme tag; if the matching fails, outputting matching failure indication information; and if the matching is successful, matching the secondary attribute label of the event to be issued with the secondary topic labels stored in each secondary node connected with the successfully matched primary node to obtain the successfully matched primary topic label and secondary topic label.
Optionally, after the subscription conditions sent by all subscription clients are obtained, the method further includes: counting a plurality of subscription conditions of each subscription client; judging whether the number of subscription conditions of the same subscription topic exceeds a preset threshold value within a preset time period; if yes, confirming the subscription theme as a target subscription theme of the subscription client; and pushing the events conforming to the target subscription theme to the subscription client.
Optionally, after the obtaining the event to be issued sent by the issuing client, the method further includes: the event to be issued is classified and stored into a corresponding event group of a preset database according to the event theme and the event attribute, wherein the event group comprises a plurality of events with the same event theme and the same event attribute; pushing all the events in the event group to a subscription client subscribing the events to be distributed according to preset logic.
Optionally, after the creating a multi-level index structure according to all the subscription topics, the method further comprises: acquiring subscription conditions sent by a subscription client, wherein the subscription conditions comprise an identity of the subscription client, a subscription theme and a theme label; judging whether the subscribing client is a new user or not according to the identity; if so, updating the multi-level index structure according to the subscription theme and theme label of the new user.
Optionally, the method further comprises: acquiring a subscription modification instruction of a subscription client, wherein the subscription modification instruction comprises a newly added subscription topic, an unsubscribed topic and a topic label; and correspondingly modifying the root node, the primary node, the secondary node and the subscription client identifications configured by all nodes in the multi-level index structure according to the subscription modification instruction.
Optionally, the subscription condition of the subscription client further includes a routing path of the reception event of the subscription client; the transmitting the event to be issued to the target subscription client with successful matching includes: and sending the event to be issued to the target subscription client which is successfully matched through a routing path stored in a database.
In order to achieve the above object, according to one aspect of the present invention, there is provided a content distribution system including a database, a search module, a subscription management module, and a content distribution device; the database is used for storing the events, and the events are classified into corresponding event groups according to the event topics; the retrieval module is used for retrieving and searching the events in the database; the subscription management module is used for managing the life cycle of subscription, controlling account security, creating editing events and archiving management events; the content distribution device is used for executing the content distribution method.
In order to achieve the above object, according to one aspect of the present invention, there is provided a content distribution apparatus comprising: the first acquisition unit is used for acquiring an event to be issued, which is sent by the issuing client, wherein the event to be issued comprises an event theme and an event attribute; the second acquisition unit is used for acquiring subscription conditions sent by all subscription clients, wherein the subscription conditions carry subscription topics and topic labels; the creation unit is used for creating a multi-level index structure according to all the subscription topics, wherein the multi-level index structure comprises root nodes, primary nodes connected with the root nodes and secondary nodes connected with the primary nodes, each root node stores the subscription topics, each primary node stores a primary topic label, each secondary node stores a secondary topic label, and all nodes store corresponding subscription client identifiers; the first matching unit is used for matching the event theme of the event to be issued with subscription themes stored by all root nodes in the multi-level index structure; the second matching unit is used for matching the event attribute with the primary topic label stored in the primary node and the secondary topic label stored in the secondary node which are connected with the root node which is successfully matched one by one if the matching is successful, so as to obtain the primary topic label and the secondary topic label which are successfully matched; and the sending unit is used for sending the event to be issued to a target subscription client which is successfully matched with the primary topic label and the secondary topic label, wherein the target subscription client comprises subscription client identifiers stored by the node where the secondary topic label is successfully matched.
To achieve the above object, according to one aspect of the present invention, there is provided an electronic device including: at least one processor; and at least one memory communicatively coupled to the processor, wherein the memory stores program instructions executable by the processor, the processor invoking the program instructions to perform the content distribution method described above.
In the scheme, event topics of events to be distributed are matched with subscription topics stored in a root node in the multi-level index structure, then event attributes are used for matching labels on all nodes until the events to be distributed are matched with a certain node in the multi-level index structure, so that subscribers corresponding to subscription client identifiers stored in the node can subscribe to the events to be distributed, and the matching efficiency is improved.
[ description of the drawings ]
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings that are needed in the embodiments will be briefly described below, it being obvious that the drawings in the following description are only some embodiments of the present invention, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a flow chart of an alternative content distribution method provided by an embodiment of the present invention;
FIG. 2 is a schematic diagram of an alternative content distribution system provided by an embodiment of the present invention;
FIG. 3 is a schematic diagram of an alternative content distribution apparatus according to an embodiment of the present invention;
fig. 4 is a schematic diagram of an alternative electronic device according to an embodiment of the present invention.
[ detailed description ] of the invention
For a better understanding of the technical solution of the present invention, the following detailed description of the embodiments of the present invention refers to the accompanying drawings.
It should be understood that the described embodiments are merely some, but not all, embodiments of the invention. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
The terminology used in the embodiments of the invention is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used in this application and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.
It should be understood that the term "and/or" as used herein is merely one relationship describing the association of the associated objects, meaning that there may be three relationships, e.g., a and/or B, may represent: a exists alone, A and B exist together, and B exists alone. In addition, the character "/" herein generally indicates that the front and rear associated objects are an "or" relationship.
It should be understood that although the terms first, second, third, etc. may be used to describe the terminals in the embodiments of the present invention, these terminals should not be limited to these terms. These terms are only used to distinguish terminals from one another. For example, a first terminal may also be referred to as a second terminal, and similarly, a second terminal may also be referred to as a first terminal, without departing from the scope of embodiments of the present invention.
Depending on the context, the word "if" as used herein may be interpreted as "at … …" or "at … …" or "in response to a determination" or "in response to detection". Similarly, the phrase "if determined" or "if detected (stated condition or event)" may be interpreted as "when determined" or "in response to determination" or "when detected (stated condition or event)" or "in response to detection (stated condition or event), depending on the context.
Fig. 1 is a flowchart of a content distribution method according to an embodiment of the present invention, as shown in fig. 1, the method includes:
step S101, an event to be issued, which is sent by an issuing client, is obtained, wherein the event to be issued comprises an event theme and an event attribute. The topic is a bridge between the subscription client and the publishing client, and the topic can be an event topic or a subscription topic. Topics are used to represent learning phases, such as: elementary, junior middle, high, medium, and correspondingly, event topics are used to clarify the topics of events to be issued, event attributes are used to represent subdivision knowledge points, and attributes are layered by using separators (/), e.g., first grade/Chinese;7th gradation/matheat; 7th grade/geometry. The producer of an event is referred to as a publishing client and the consumer of an event is referred to as a subscribing client.
Step S102, obtaining subscription conditions sent by all subscription clients, wherein the subscription conditions carry subscription topics and topic labels. Illustratively, a subscription topic is used to represent topics that are needed or of interest to a subscriber, such as: the subscription topic is primary school, and the topic label is a grade/Chinese.
Step S103, a multi-level index structure is created according to all subscription topics, the multi-level index structure comprises root nodes, primary nodes connected with the root nodes and secondary nodes connected with the primary nodes, wherein each root node stores the subscription topic, each primary node stores a primary topic label, each secondary node stores a secondary topic label, and all nodes store corresponding subscription client identifiers.
The multi-level index structure is tree-shaped, and the subscription theme stored by the root node covers the primary theme label stored by the primary node and the secondary theme label stored by the secondary node. The primary theme tag overlays the secondary theme tag. In other embodiments, knowledge points can be further refined under the secondary topic label to form a tertiary topic label, a quaternary topic label and the like. And will not be described in any greater detail herein. The pointers to the root nodes are correspondingly stored in the index structure, so that when an event to be issued needs to be matched, quick positioning in the multi-level index structure can be performed according to the event attribute.
For example, the subscription topic of the subscription client a is primary, the topic label is a grade/language, and then the identity of the subscription client a is stored in the primary node (storing the grade primary topic label) and the secondary node (storing the language secondary topic label). The subscription client identifier may be an ID code of the subscription terminal, or may be a registration number when the subscription client registers, which is not limited herein.
Step S104, matching the event theme of the event to be issued with the subscription theme stored by all root nodes in the multi-level index structure. It can be appreciated that, through the matching of the event topic and the subscription topic, the target subscription client can be screened out in a large scale, and the subscription matching efficiency is improved.
Step 105, if the matching is successful, matching the event attribute with the primary topic label stored in the primary node and the secondary topic label stored in the secondary node, which are connected with the root node of the successful matching, one by one, to obtain the primary topic label and the secondary topic label of the successful matching.
Step S106, the event to be issued is transmitted to a target subscription client with the primary topic label and the secondary topic label successfully matched, wherein the target subscription client comprises subscription client identifications stored by the nodes where the secondary topic labels are successfully matched.
In the scheme, event topics of events to be distributed are matched with subscription topics stored in a root node in the multi-level index structure, then event attributes are used for matching labels on all nodes until the events to be distributed are matched with a certain node in the multi-level index structure, so that subscribers corresponding to subscription client identifiers stored in the node can subscribe to the events to be distributed, and the matching efficiency is improved.
Optionally, after acquiring the event to be issued sent by the issuing client, the method further includes: determining a first-level attribute tag and a second-level attribute tag of an event to be issued according to the event attribute of the event to be issued and a preset tag mapping table, wherein the tag mapping table comprises the corresponding relation between a field representing the event attribute and the first-level attribute tag and the second-level attribute tag; matching the primary attribute labels of the events to be issued with the primary topic labels stored in the primary nodes connected with the successfully matched root nodes to obtain successfully matched primary topic labels; if the matching fails, outputting matching failure indication information; and if the matching is successful, matching the secondary attribute labels of the events to be issued with the secondary topic labels stored in the secondary nodes connected with the successfully matched primary nodes to obtain the successfully matched primary topic labels and secondary topic labels.
The event attribute may be summary of Primary school Primary language examination knowledge points, the following keywords "Primary school", "Primary grade" and "language" may be obtained by extracting keywords, and "Primary school" and "Primary grade" are obtained by mapping with a preset tag mapping table, and "first grade" and "language" are obtained by mapping.
When an event to be issued is matched, after a matched root node is found in the multi-level index structure, testing a primary node and a secondary node connected with the root node by using event attributes, if the primary node fails to be tested in the testing process, recording a subscription client of the node, and after the testing is finished, eliminating all unsuccessfully matched subscription client identifiers from all subscription client identifiers.
Optionally, after acquiring the subscription conditions sent by all the subscription clients, the method further includes: counting a plurality of subscription conditions of each subscription client; judging whether the number of subscription conditions of the same subscription topic exceeds a preset threshold value within a preset time period; if yes, confirming the subscription theme as a target subscription theme of the subscription client; and pushing the events meeting the target subscription theme to the subscription client.
For example, the preset time period may be 1 month, 2 months, half year, etc., the number of times that the subscription client a subscribes to the subscription topic as a primary school is 20 times in one month, which indicates that the subscription client a is very focused on knowledge points in the primary school stage, the system confirms "primary school" as a target subscription topic, and then pushes to the subscription client a any event to be published that matches the topic of "primary school" among the events to be published.
Optionally, after acquiring the event to be issued sent by the issuing client, the method further includes: according to the event theme and the event attribute, storing the event to be issued into a corresponding event group of a preset database in a classified manner, wherein the event group comprises a plurality of events with the same event theme and the same event attribute; pushing all the events in the event group to a subscription client subscribing the events to be published according to preset logic.
It will be appreciated that multiple events with the same event topic and the same event attribute are classified into an event group and may be stored in the same folder, and when the subscription client B subscribes to one event in the event group, the system will actively push other events in the event group to him. The preset logic may be periodically pushed to the subscribing client from new to old according to the release time of the events in the event group, for example.
Optionally, after creating the multi-level index structure according to all subscription topics, the method further comprises: acquiring subscription conditions sent by a subscription client, wherein the subscription conditions comprise an identity of the subscription client, a subscription theme and a theme label; judging whether the subscribing client is a new user or not according to the identity; if so, the multi-level index structure is updated according to the subscription subject and subject label of the new user.
It can be understood that all the subscription client identifiers are stored in a preset record table, if a new user is present, the subscription client identifier of the new user is used to traverse the preset record table, the same subscription client identifier record cannot be found, if the same subscription client identifier record is found, the new user is not present, and only the subscription client identifier of the user is required to be added in the corresponding node in the multi-level index structure. If the user is a new user, the multi-level index structure needs to be updated according to the subscription theme and the theme label of the new user.
Optionally, the method further comprises: acquiring a subscription modification instruction of a subscription client, wherein the subscription modification instruction comprises a newly added subscription topic, a non-subscription topic and a topic label; and correspondingly modifying the root node, the primary node, the secondary node and the subscription client identifications configured by all the nodes in the multi-level index structure according to the subscription modification instruction.
Optionally, the subscription condition of the subscription client further includes a routing path of the received event of the subscription client; transmitting the event to be issued to the target subscription client with successful matching, comprising: and sending the event to be issued to the target subscription client which is successfully matched through the routing path stored in the database.
The embodiment of the invention provides a content publishing system 100, as shown in fig. 2, which comprises a content publishing device 10, a database 20, a retrieval module 30, a subscription management module 40 and a display module 50.
The content distribution apparatus 10 is configured to execute the content distribution method described above.
The database 20 is used for storing events, and the events are classified into corresponding event groups according to event topics. Wherein each event is a separate piece of data, and the type of data can be a document, video, audio, web page, image, etc. Specifically, for example, educational videos, teaching ppt, recordings, and the like. These data are all stored in a database and are embodied in a multi-level index structure.
And the retrieval module 30 is used for retrieving and searching the events in the database.
Specifically, the retrieval module 30 includes a full text retrieval unit 31, a metadata management unit 32, a context retrieval unit 33, and a multimedia retrieval unit 34. It can be appreciated that full text retrieval is mainly used for retrieving objects such as words, characters, paragraphs and the like of full text data. The multimedia retrieval is mainly used for extracting the semanteme contained in the content of the characterization video or image based on the visual characteristics in the video or image, so that the inquiry and management of the video or image data are realized.
Subscription management module 40 for managing the life cycle of subscriptions, controlling account security, creating editing events, archiving management events.
And a display module 50, configured to implement interaction with the subscription client and the publishing client with the system.
An embodiment of the present invention provides a content distribution apparatus 10 for executing the above content distribution method, as shown in fig. 2, including: a first acquisition unit 101, a second acquisition unit 102, a creation unit 103, a first matching unit 104, a second matching unit 105, a transmission unit 106.
The first obtaining unit 101 is configured to obtain an event to be published, which is sent by the publishing client, where the event to be published includes an event topic and an event attribute.
The topic is a bridge between the subscription client and the publishing client, and the topic can be an event topic or a subscription topic. Topics are used to represent learning phases, such as: elementary, junior middle, high and medium, respectively, topics generally do not contain wild cards to clarify the topic of the event to be issued, event attributes are used to represent subdivision knowledge points, attributes are layered by using separators (/), e.g., first grade/child; 7th gradation/matheat; 7th grade/geometry. The producer of an event is referred to as a publishing client and the consumer of an event is referred to as a subscribing client.
The second obtaining unit 102 is configured to obtain subscription conditions sent by all subscription clients, where the subscription conditions carry a subscription topic and a topic tag. Illustratively, a subscription topic is used to represent topics that are needed or of interest to a subscriber, such as: the subscription topic is primary school, and the topic label is a grade/Chinese.
The creating unit 103 is configured to create a multi-level index structure according to all subscription topics, where the multi-level index structure includes a root node, a primary node connected to the root node, and a secondary node connected to the primary node, each root node stores a subscription topic, each primary node stores a primary topic tag, each secondary node stores a secondary topic tag, and all nodes store corresponding subscription client identifiers.
The multi-level index structure is tree-shaped, and the subscription theme stored by the root node covers the primary theme label stored by the primary node and the secondary theme label stored by the secondary node. The primary theme tag overlays the secondary theme tag. In other embodiments, knowledge points can be further refined under the secondary topic label to form a tertiary topic label, a quaternary topic label and the like. And will not be described in any greater detail herein. The pointers to the root nodes are correspondingly stored in the index structure, so that when an event to be issued needs to be matched, quick positioning in the multi-level index structure can be performed according to the event attribute.
For example, the subscription topic of the subscription client a is primary, the topic label is a grade/language, and then the identity of the subscription client a is stored in the primary node (storing the grade primary topic label) and the secondary node (storing the language secondary topic label). The subscription client identifier may be an ID code of the subscription terminal, or may be a registration number when the subscription client registers, which is not limited herein.
The first matching unit 104 is configured to match an event topic of an event to be issued with subscription topics stored by all root nodes in the multi-level index structure.
And the second matching unit 105 is configured to match the event attribute with the primary topic label stored in the primary node and the secondary topic label stored in the secondary node, which are connected with the root node that is successfully matched, one by one, if the matching is successful, so as to obtain the primary topic label and the secondary topic label that are successfully matched.
And the sending unit 106 is configured to send the event to be issued to a target subscription client with successfully matched primary topic label and secondary topic label, where the target subscription client includes a subscription client identifier stored by a node where the secondary topic label is successfully matched.
In the scheme, event topics of events to be distributed are matched with subscription topics stored in a root node in the multi-level index structure, then event attributes are used for matching labels on all nodes until the events to be distributed are matched with a certain node in the multi-level index structure, so that subscribers corresponding to subscription client identifiers stored in the node can subscribe to the events to be distributed, and the matching efficiency is improved.
Optionally, the apparatus further comprises a tag determination unit,
The tag determining unit is used for determining a primary attribute tag and a secondary attribute tag of the event to be issued according to the event attribute of the event to be issued and a preset tag mapping table, wherein the tag mapping table comprises the corresponding relation between a field representing the event attribute and the primary attribute tag and the secondary attribute tag; matching the primary attribute labels of the events to be issued with the primary topic labels stored in the primary nodes connected with the successfully matched root nodes to obtain successfully matched primary topic labels; if the matching fails, outputting matching failure indication information; and if the matching is successful, matching the secondary attribute labels of the events to be issued with the secondary topic labels stored in the secondary nodes connected with the successfully matched primary nodes to obtain the successfully matched primary topic labels and secondary topic labels.
Optionally, the device further comprises a statistics unit, a first judging unit, a first confirming unit and a pushing unit.
The statistics unit is used for counting a plurality of subscription conditions of each subscription client; the first judging unit is used for judging whether the number of subscription conditions of the same subscription topic exceeds a preset threshold value in a preset time period; the first confirming unit is used for confirming the subscription theme as a target subscription theme of the subscription client; and the pushing unit is used for pushing the event conforming to the target subscription theme to the subscription client.
For example, the preset time period may be 1 month, 2 months, half year, etc., the number of times that the subscription client a subscribes to the subscription topic as a primary school is 20 times in one month, which indicates that the subscription client a is very focused on knowledge points in the primary school stage, the system confirms "primary school" as a target subscription topic, and then pushes to the subscription client a any event to be published that matches the topic of "primary school" among the events to be published.
Optionally, the apparatus further comprises a storage unit.
The storage unit is used for storing the event to be distributed into a corresponding event group of a preset database in a classified manner according to the event theme and the event attribute, wherein the event group comprises a plurality of events with the same event theme and the same event attribute; the pushing unit is further configured to push all the events in the event group to a subscription client subscribing to the event to be published according to a preset logic.
It will be appreciated that multiple events with the same event topic and the same event attribute are classified into an event group and may be stored in the same folder, and when the subscription client B subscribes to one event in the event group, the system will actively push other events in the event group to him. The preset logic may be periodically pushed to the subscribing client from new to old according to the release time of the events in the event group, for example.
Optionally, the device further comprises a third acquisition unit, a second judgment unit and an updating unit.
The third acquisition unit is used for acquiring subscription conditions sent by the subscription client, wherein the subscription conditions comprise the identity of the subscription client, a subscription theme and a theme label; the second judging unit is used for judging whether the subscribing client is a new user or not according to the identity; and the updating unit is used for updating the multi-level index structure according to the subscription theme and the theme label of the new user.
It can be understood that all the subscription client identifiers are stored in a preset record table, if a new user is present, the subscription client identifier of the new user is used to traverse the preset record table, the same subscription client identifier record cannot be found, if the same subscription client identifier record is found, the new user is not present, and only the subscription client identifier of the user is required to be added in the corresponding node in the multi-level index structure. If the user is a new user, the multi-level index structure needs to be updated according to the subscription theme and the theme label of the new user.
Optionally, the method further comprises: acquiring a subscription modification instruction of a subscription client, wherein the subscription modification instruction comprises a newly added subscription topic, a non-subscription topic and a topic label; and correspondingly modifying the root node, the primary node, the secondary node and the subscription client identifications configured by all the nodes in the multi-level index structure according to the subscription modification instruction.
Optionally, the subscription condition of the subscription client further includes a routing path of the received event of the subscription client; the sending unit 60 is further configured to send the event to be issued to the target subscription client that is successfully matched through the routing path stored in the database.
Embodiments of the present invention provide a non-transitory computer readable storage medium storing computer instructions, wherein the computer instructions cause a computer to perform the steps of:
acquiring an event to be issued, which is sent by an issuing client, wherein the event to be issued comprises an event theme and an event attribute; acquiring subscription conditions sent by all subscription clients, wherein the subscription conditions carry subscription topics and topic labels; creating a multi-level index structure according to all subscription topics, wherein the multi-level index structure comprises root nodes, primary nodes connected with the root nodes and secondary nodes connected with the primary nodes, each root node stores the subscription topics, each primary node stores a primary topic label, each secondary node stores a secondary topic label, and all nodes store corresponding subscription client identifiers; matching the event theme of the event to be issued with subscription themes stored by all root nodes in the multi-level index structure; if the matching is successful, matching the event attribute with the primary topic label stored in the primary node and the secondary topic label stored in the secondary node, which are connected with the root node of the successful matching, one by one, so as to obtain the primary topic label and the secondary topic label of the successful matching; and transmitting the event to be issued to a target subscription client with successfully matched primary topic labels and secondary topic labels, wherein the target subscription client comprises subscription client identifiers stored by the nodes where the secondary topic labels are successfully matched.
Optionally, the computer instructions cause the computer to further perform the steps of: determining a first-level attribute tag and a second-level attribute tag of an event to be issued according to the event attribute of the event to be issued and a preset tag mapping table, wherein the tag mapping table comprises the corresponding relation between a field representing the event attribute and the first-level attribute tag and the second-level attribute tag; matching the primary attribute labels of the events to be issued with the primary topic labels stored in the primary nodes connected with the successfully matched root nodes to obtain successfully matched primary topic labels; if the matching fails, outputting matching failure indication information; and if the matching is successful, matching the secondary attribute labels of the events to be issued with the secondary topic labels stored in the secondary nodes connected with the successfully matched primary nodes to obtain the successfully matched primary topic labels and secondary topic labels.
Optionally, the computer instructions cause the computer to further perform the steps of: counting a plurality of subscription conditions of each subscription client; judging whether the number of subscription conditions of the same subscription topic exceeds a preset threshold value within a preset time period; if yes, confirming the subscription theme as a target subscription theme of the subscription client; and pushing the events meeting the target subscription theme to the subscription client.
Optionally, the computer instructions cause the computer to further perform the steps of: according to the event theme and the event attribute, storing the event to be issued into a corresponding event group of a preset database in a classified manner, wherein the event group comprises a plurality of events with the same event theme and the same event attribute; pushing all the events in the event group to a subscription client subscribing the events to be published according to preset logic.
Optionally, the computer instructions cause the computer to further perform the steps of: acquiring subscription conditions sent by a subscription client, wherein the subscription conditions comprise an identity of the subscription client, a subscription theme and a theme label; judging whether the subscribing client is a new user or not according to the identity; if so, the multi-level index structure is updated according to the subscription subject and subject label of the new user.
Optionally, the computer instructions cause the computer to further perform the steps of: acquiring a subscription modification instruction of a subscription client, wherein the subscription modification instruction comprises a newly added subscription topic, a non-subscription topic and a topic label; and correspondingly modifying the root node, the primary node, the secondary node and the subscription client identifications configured by all the nodes in the multi-level index structure according to the subscription modification instruction.
Optionally, the computer instructions cause the computer to further perform the steps of: and sending the event to be issued to the target subscription client which is successfully matched through the routing path stored in the database.
Fig. 4 is a schematic diagram of an electronic device 300 according to an embodiment of the present invention, as shown in fig. 4, the electronic device 300 of the embodiment includes: at least one processor 310 and a communication interface 320; and at least one memory 330 communicatively coupled to the processor 310, wherein the memory 330 stores program instructions executable by the processor 310, the processor 310 invoking the program instructions capable of performing the above-described configurable data monitoring alert method. In order to avoid repetition, details are not repeated here.
The electronic device 300 may be a desktop computer, a notebook computer, a palm computer, a cloud server, or the like. Electronic devices may include, but are not limited to, a processor 310, a communication interface 320, and a memory 330. It will be appreciated by those skilled in the art that fig. 3 is merely an example of an electronic device 300 and is not intended to limit the electronic device 300, and may include more or fewer components than shown, or may combine certain components, or different components, e.g., the electronic device may further include a communication bus 340, etc.
The processor 101 may be a central processing unit (Central Processing Unit, CPU), but may also be other general purpose processors, digital signal processors (Digital Signal Processor, DSP), application specific integrated circuits (Application Specific Integrated Circuit, ASIC), field programmable gate arrays (Field-Programmable Gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
The memory 330 may be an internal storage unit of the electronic device 300, such as a hard disk or a memory of the electronic device 300. The memory 330 may also be an external storage device of the electronic device 300, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card) or the like, which are provided on the electronic device 300. Further, the memory 330 may also include both internal storage units and external storage devices of the electronic device 300. Memory 330 is used to store program instructions as well as other programs and data required by the electronic device. The memory 330 may also be used to temporarily store data that has been output or is to be output.
It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, which are not repeated herein.
In the several embodiments provided in the present invention, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the elements is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple elements or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.
The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional unit in the embodiments of the present invention may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in hardware plus software functional units.
The integrated units implemented in the form of software functional units described above may be stored in a computer readable storage medium. The software functional unit is stored in a storage medium, and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) or a Processor (Processor) to perform part of the steps of the methods according to the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
The foregoing description of the preferred embodiments of the invention is not intended to be limiting, but rather to enable any modification, equivalent replacement, improvement or the like to be made within the spirit and principles of the invention.
Claims (9)
1. A content distribution method, the method comprising:
acquiring an event to be issued, which is sent by an issuing client, wherein the event to be issued comprises an event theme and an event attribute;
acquiring subscription conditions sent by all subscription clients, wherein the subscription conditions carry subscription topics and topic labels;
creating a multi-level index structure according to all the subscription topics, wherein the multi-level index structure comprises root nodes, primary nodes connected with the root nodes and secondary nodes connected with the primary nodes, each root node stores the subscription topics, each primary node stores a primary topic label, each secondary node stores a secondary topic label, and all the nodes store corresponding subscription client identifiers;
matching the event theme of the event to be issued with subscription themes stored by all root nodes in the multi-level index structure;
if the matching is successful, matching the event attribute with a primary topic label stored in a primary node and a secondary topic label stored in a secondary node which are connected with the root node of the successful matching one by one to obtain a primary topic label and a secondary topic label of the successful matching;
Transmitting the event to be issued to a target subscription client which is successfully matched with the primary topic label and the secondary topic label, wherein the target subscription client comprises subscription client identifiers stored by the node where the secondary topic label is successfully matched;
after the event to be issued sent by the issuing client is obtained, the method further comprises the following steps:
determining a primary attribute tag and a secondary attribute tag of the event to be issued according to the event attribute of the event to be issued and a preset tag mapping table, wherein the tag mapping table comprises the corresponding relation between a field representing the event attribute and the primary attribute tag and the secondary attribute tag;
matching the first-level attribute tag of the event to be issued with the first-level theme tag stored in each first-level node connected with the successfully matched root node to obtain the successfully matched first-level theme tag;
if the matching fails, outputting matching failure indication information;
and if the matching is successful, matching the secondary attribute label of the event to be issued with the secondary topic labels stored in each secondary node connected with the successfully matched primary node to obtain the successfully matched primary topic label and secondary topic label.
2. The method of claim 1, wherein after the obtaining subscription conditions sent by all subscribing clients, the method further comprises:
counting a plurality of subscription conditions of each subscription client;
judging whether the number of subscription conditions of the same subscription topic exceeds a preset threshold value within a preset time period;
if yes, confirming the subscription theme as a target subscription theme of the subscription client;
and pushing the events conforming to the target subscription theme to the subscription client.
3. The method of claim 1, wherein after the acquiring the event to be published sent by the publishing client, the method further comprises:
the event to be issued is classified and stored into a corresponding event group of a preset database according to the event theme and the event attribute, wherein the event group comprises a plurality of events with the same event theme and the same event attribute;
pushing all the events in the event group to a subscription client subscribing the events to be distributed according to preset logic.
4. A method according to any one of claims 1 to 3, wherein after said creating a multi-level index structure from all of said subscription topics, the method further comprises:
Acquiring subscription conditions sent by a subscription client, wherein the subscription conditions comprise an identity of the subscription client, a subscription theme and a theme label;
judging whether the subscribing client is a new user or not according to the identity;
if so, updating the multi-level index structure according to the subscription theme and theme label of the new user.
5. The method according to claim 1, wherein the method further comprises:
acquiring a subscription modification instruction of a subscription client, wherein the subscription modification instruction comprises a newly added subscription topic, an unsubscribed topic and a topic label;
and correspondingly modifying the root node, the primary node, the secondary node and the subscription client identifications configured by all nodes in the multi-level index structure according to the subscription modification instruction.
6. The method of claim 1, wherein the subscription conditions of the subscribing client further comprise a routing path of the receiving event of the subscribing client; the transmitting the event to be issued to the target subscription client with successful matching includes:
and sending the event to be issued to the target subscription client which is successfully matched through a routing path stored in a database.
7. The content publishing system is characterized by comprising a database, a retrieval module, a subscription management module and a content publishing device;
the database is used for storing the events, and the events are classified into corresponding event groups according to the event topics;
the retrieval module is used for retrieving and searching the events in the database;
the subscription management module is used for managing the life cycle of subscription, controlling account security, creating editing events and archiving management events;
the content distribution apparatus for executing the content distribution method according to any one of claims 1 to 6.
8. A content distribution apparatus, characterized in that the apparatus comprises:
the first acquisition unit is used for acquiring an event to be issued, which is sent by the issuing client, wherein the event to be issued comprises an event theme and an event attribute;
the second acquisition unit is used for acquiring subscription conditions sent by all subscription clients, wherein the subscription conditions carry subscription topics and topic labels;
the creation unit is used for creating a multi-level index structure according to all the subscription topics, wherein the multi-level index structure comprises root nodes, primary nodes connected with the root nodes and secondary nodes connected with the primary nodes, each root node stores the subscription topics, each primary node stores a primary topic label, each secondary node stores a secondary topic label, and all nodes store corresponding subscription client identifiers;
The first matching unit is used for matching the event theme of the event to be issued with subscription themes stored by all root nodes in the multi-level index structure;
the second matching unit is used for matching the event attribute with the primary topic label stored in the primary node and the secondary topic label stored in the secondary node which are connected with the root node which is successfully matched one by one if the matching is successful, so as to obtain the primary topic label and the secondary topic label which are successfully matched;
the sending unit is used for sending the event to be issued to a target subscription client which is successfully matched with the primary topic label and the secondary topic label, wherein the target subscription client comprises subscription client identifiers stored by the node where the secondary topic label is successfully matched;
the tag determining unit is used for determining a primary attribute tag and a secondary attribute tag of the event to be issued according to the event attribute of the event to be issued and a preset tag mapping table, wherein the tag mapping table comprises the corresponding relation between a field representing the event attribute and the primary attribute tag and the secondary attribute tag; matching the primary attribute labels of the events to be issued with the primary topic labels stored in the primary nodes connected with the successfully matched root nodes to obtain successfully matched primary topic labels; if the matching fails, outputting matching failure indication information; and if the matching is successful, matching the secondary attribute labels of the events to be issued with the secondary topic labels stored in the secondary nodes connected with the successfully matched primary nodes to obtain the successfully matched primary topic labels and secondary topic labels.
9. An electronic device, comprising: at least one processor; and at least one memory communicatively coupled to the processor, wherein the memory stores program instructions executable by the processor, the processor invoking the program instructions to perform the content distribution method of any of claims 1-6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910712968.XA CN112307318B (en) | 2019-08-02 | 2019-08-02 | Content publishing method, system and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910712968.XA CN112307318B (en) | 2019-08-02 | 2019-08-02 | Content publishing method, system and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112307318A CN112307318A (en) | 2021-02-02 |
| CN112307318B true CN112307318B (en) | 2024-03-08 |
Family
ID=74486523
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910712968.XA Active CN112307318B (en) | 2019-08-02 | 2019-08-02 | Content publishing method, system and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112307318B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113609203A (en) * | 2021-08-20 | 2021-11-05 | 苏州良医汇网络科技有限公司 | Medicine data conversion method and system |
| CN115858909A (en) * | 2021-09-10 | 2023-03-28 | 北京字节跳动网络技术有限公司 | Content subscription method, terminal, server, equipment and storage medium |
| CN116204664A (en) * | 2021-12-01 | 2023-06-02 | 北京字节跳动网络技术有限公司 | Content subscription method, device, computer equipment and storage medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102438043A (en) * | 2011-11-11 | 2012-05-02 | 无锡南理工科技发展有限公司 | Releasing/subscribing system for credibly supporting multiple subscribing conditions and non-real-time information subscription |
| CN105740337A (en) * | 2016-01-22 | 2016-07-06 | 东南大学 | Rapid event matching method in content-based publishing subscription system |
| CN105893635A (en) * | 2016-06-23 | 2016-08-24 | 河海大学 | Netted multilevel index matching method for publishing and subscribing |
| CN106933989A (en) * | 2017-02-22 | 2017-07-07 | 深圳云视融通科技有限公司 | A kind of method of Web realease information system |
| CN108183931A (en) * | 2017-12-04 | 2018-06-19 | 中国电子科技集团公司第三十研究所 | A kind of distribution subscription matching process based on demand management tree shape model |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7774378B2 (en) * | 2004-06-04 | 2010-08-10 | Icentera Corporation | System and method for providing intelligence centers |
| US9256859B2 (en) * | 2011-07-26 | 2016-02-09 | Salesforce.Com, Inc. | Systems and methods for fragmenting newsfeed objects |
-
2019
- 2019-08-02 CN CN201910712968.XA patent/CN112307318B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102438043A (en) * | 2011-11-11 | 2012-05-02 | 无锡南理工科技发展有限公司 | Releasing/subscribing system for credibly supporting multiple subscribing conditions and non-real-time information subscription |
| CN105740337A (en) * | 2016-01-22 | 2016-07-06 | 东南大学 | Rapid event matching method in content-based publishing subscription system |
| CN105893635A (en) * | 2016-06-23 | 2016-08-24 | 河海大学 | Netted multilevel index matching method for publishing and subscribing |
| CN106933989A (en) * | 2017-02-22 | 2017-07-07 | 深圳云视融通科技有限公司 | A kind of method of Web realease information system |
| CN108183931A (en) * | 2017-12-04 | 2018-06-19 | 中国电子科技集团公司第三十研究所 | A kind of distribution subscription matching process based on demand management tree shape model |
Non-Patent Citations (1)
| Title |
|---|
| 董俊 等."发布订阅模式中间件中高效事件过滤器的研究".《小型微型计算机系统》.2013,第34卷(第3期),第438-442页. * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112307318A (en) | 2021-02-02 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10613719B2 (en) | Generating a form response interface in an online application | |
| WO2018036272A1 (en) | News content pushing method, electronic device, and computer readable storage medium | |
| US8630972B2 (en) | Providing context for web articles | |
| CN112307318B (en) | Content publishing method, system and device | |
| CN107193974B (en) | Regional information determination method and device based on artificial intelligence | |
| CN103186600B (en) | The specific analysis method and apparatus of internet public feelings | |
| CN109271509B (en) | Live broadcast room topic generation method and device, computer equipment and storage medium | |
| CA3138730C (en) | Public-opinion analysis method and system for providing early warning of enterprise risks | |
| CN110888990A (en) | Text recommendation method, device, equipment and medium | |
| CN109582847B (en) | Information processing method and device and storage medium | |
| CN104462096B (en) | Public sentiment method for monitoring and analyzing and device | |
| CN111371672A (en) | Message pushing method and device | |
| CN111563382A (en) | Text information acquisition method and device, storage medium and computer equipment | |
| CN109960719A (en) | A kind of document handling method and relevant apparatus | |
| CN113705250B (en) | Session content identification method, device, equipment and computer readable medium | |
| JP4031264B2 (en) | Filtering management method, filtering management program, filtering management method for filtering device, and filtering management program for filtering device | |
| CN111737443B (en) | Answer text processing method and device and key text determining method | |
| CN113051460A (en) | Elasticissearch-based data retrieval method and system, electronic device and storage medium | |
| CN107734534B (en) | Network load evaluation method and device | |
| CN111930890A (en) | Information sending method and device, terminal equipment and storage medium | |
| US11106739B2 (en) | Document structures for searching within and across messages | |
| CN110457527A (en) | A kind of XML message comparison method and system | |
| CN107491530B (en) | Social relationship mining analysis method based on file automatic marking information | |
| KR20120029662A (en) | Device and method for managing spam | |
| CN112416626B (en) | Data processing method and device |
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 | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20220718 Address after: 610000 unit 2, building 1, No. 150, hele Second Street, Chengdu high tech Zone, Chengdu pilot Free Trade Zone, Sichuan Province Applicant after: China Mobile (Chengdu) information and Communication Technology Co.,Ltd. Applicant after: CHINA MOBILE COMMUNICATIONS GROUP Co.,Ltd. Address before: Room 106A, 17 houyongkang Hutong, Dongcheng District, Beijing Applicant before: GOVERNMENT AND ENTERPRISES CUSTOMER BRANCH OFFICE OF CHINA MOBILE COMMUNICATIONS Co.,Ltd. Applicant before: CHINA MOBILE COMMUNICATIONS GROUP Co.,Ltd. |
|
| TA01 | Transfer of patent application right | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |