A message subscription method, apparatus and device

Abstract

The application relates to a message subscription method, device and equipment, which comprises the following steps: collecting a content attribute processing event, the content attribute processing event being generated based on updating a content attribute of content data; analyzing the content attribute processing event to obtain an updated content attribute included in the content attribute processing event and an attribute value of the updated content attribute; matching the updated content attribute with message subscription rules of multiple message subscribers to determine matched message subscribers and matched content attributes subscribed by the matched message subscribers; obtaining callback interface information of the matched message subscribers, and pushing the matched content attributes and the attribute values of the matched content attributes to the corresponding matched message subscribers based on the callback interface information. The application can reduce the access cost of the subscribers and improve the real-time performance of the message subscription.

Description

Technical Field

[0001] This application relates to the field of information processing technology, and in particular to a message subscription method, apparatus and device. Background Technology

[0002] Publish-subscribe is a messaging paradigm where publishers do not send messages directly to specific recipients, but instead categorize their messages into different classes without needing to know which subscribers might exist. Similarly, subscribers can express interest in one or more categories and only receive messages that interest them, without needing to know which publishers exist.

[0003] In existing publish-subscribe (CDS) models, subscribers typically receive subscribed messages in two ways: One is that each subscriber individually receives processing events that modify or alter content attributes, then parses these events to obtain the content attributes of the subscribed content. This method requires each subscriber to receive and parse all processing events, most of which are not subscribed to, resulting in high integration costs and redundant implementation for each subscriber. The other method involves pre-setting the scanning range and content attributes in a script to scan stored content data offline, thereby obtaining the content attributes of the subscribed content. However, this method cannot obtain processing events in real-time, making it unsuitable for subscribers with high real-time requirements, and the extensive scanning work further increases the load on processing equipment. Therefore, a message subscription method that reduces subscriber integration costs and improves the real-time performance of message subscriptions is needed. Summary of the Invention

[0004] The technical problem to be solved by this application is to provide a message subscription method, apparatus and device that enables message subscribers to obtain the corresponding subscription messages according to their own needs, reduces the access cost of message subscribers and improves the real-time performance of message subscription.

[0005] To address the aforementioned technical problems, this application provides a message subscription method, comprising:

[0006] Collect content attribute processing events, which are generated based on updating the content attributes of the content data;

[0007] The content attribute processing event is parsed to obtain the updated content attributes included in the content attribute processing event, and the attribute values ​​of the updated content attributes.

[0008] The updated content attributes are matched with the message subscription rules of multiple message subscribers to determine the matching message subscribers and the matching content attributes subscribed to by the matching message subscribers.

[0009] Obtain the callback interface information of the matching message subscriber, and push the matching content attribute and the attribute value of the matching content attribute to the corresponding matching message subscriber based on the callback interface information.

[0010] On the other hand, embodiments of this application provide another message subscription method, including:

[0011] Collect content attribute processing events, which are generated based on updating the content attributes of the content data;

[0012] The content attribute processing event is parsed to obtain the updated content attributes included in the content attribute processing event, and the attribute values ​​of the updated content attributes.

[0013] The updated content attributes are matched with the message subscription rules of multiple message subscribers to determine the matching message subscribers and the matching content attributes subscribed to by the matching message subscribers.

[0014] Store the attribute values ​​of the matching content attributes subscribed to by the matching message subscriber in the message queue;

[0015] In response to the subscription content attribute query request sent by the matching message subscriber, the attribute value of the matching content attribute in the message queue is returned to the matching message subscriber.

[0016] On the other hand, embodiments of this application provide a message subscription device, including:

[0017] The first event collection module is used to collect content attribute processing events, which are generated based on the update of content attributes of content data;

[0018] The first event parsing module is used to parse the content attribute processing event to obtain the updated content attribute included in the content attribute processing event, and the attribute value of the updated content attribute.

[0019] The first rule matching module is used to match the updated content attributes with the message subscription rules of multiple message subscribers to determine the matching message subscribers and the matching content attributes subscribed to by the matching message subscribers.

[0020] The message push module is used to obtain the callback interface information of the matching message subscriber, and push the matching content attribute and the attribute value of the matching content attribute to the corresponding matching message subscriber based on the callback interface information.

[0021] On the other hand, embodiments of this application provide another message subscription device, including:

[0022] The second event collection module is used to collect content attribute processing events, which are generated based on the update of content attributes of content data;

[0023] The second event parsing module is used to parse the content attribute processing event to obtain the updated content attribute included in the content attribute processing event, and the attribute value of the updated content attribute.

[0024] The second rule matching module is used to match the updated content attributes with the message subscription rules of multiple message subscribers to determine the matching message subscribers and the matching content attributes subscribed to by the matching message subscribers.

[0025] The queue storage module is used to store the attribute values ​​of the matching content attributes subscribed to by the matching message subscriber in the message queue;

[0026] The message query module is used to respond to the subscription content attribute query request sent by the matching message subscriber and return the attribute value of the matching content attribute in the message queue to the matching message subscriber.

[0027] On the other hand, this application provides a message subscription device, the device including a processor and a memory, the memory storing at least one instruction or at least one program, the at least one instruction or the at least one program being loaded and executed by the processor to implement the message subscription method as described above.

[0028] On the other hand, this application provides a computer storage medium storing at least one instruction or at least one program, wherein the at least one instruction or the at least one program is loaded by a processor and executed as described above in the message subscription method.

[0029] Implementing the embodiments of this application has the following beneficial effects:

[0030] This application collects and parses content attribute processing events generated based on the updating of content attributes in content data. This yields the updated content attributes and their corresponding values ​​within the events. By uniformly receiving and parsing these events, each subscriber is no longer required to collect and parse them individually, reducing integration costs and redundant work. The updated content attributes are matched against the message subscription rules of each subscriber to determine the matching subscribers and the content attributes they subscribe to. Based on the callback interface information of the matching subscribers, the matching content attributes and their corresponding values ​​are pushed to the respective subscribers. Through message subscription rule matching, specific subscription messages can be determined for each subscriber and pushed to them based on their interface information. Subscribers only need to receive the pushed subscription messages, reducing their processing burden. Furthermore, this application performs parsing, rule matching, and push operations as soon as content attribute processing events are collected, improving the real-time performance of message subscriptions. Attached Figure Description

[0031] To more clearly illustrate the technical solutions and advantages in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0032] Figure 1 This is a schematic diagram of the implementation environment provided in the embodiments of this application;

[0033] Figure 2 This is a flowchart of a message subscription method provided in an embodiment of this application;

[0034] Figure 3 This is a flowchart of a method for generating content attribute processing events based on content update information, provided in an embodiment of this application.

[0035] Figure 4 This is a flowchart of a content attribute processing event parsing method provided in an embodiment of this application;

[0036] Figure 5 This is a flowchart of a subscription message rule matching method provided in an embodiment of this application;

[0037] Figure 6 This is a flowchart of a message push method provided in an embodiment of this application;

[0038] Figure 7This is a flowchart of another message subscription method provided in an embodiment of this application;

[0039] Figure 8 This is a flowchart illustrating a method for processing subscribed content provided in an embodiment of this application;

[0040] Figure 9 This is a schematic diagram of a message subscription management system provided in an embodiment of this application;

[0041] Figure 10 is a schematic diagram of an example interface provided in an embodiment of this application;

[0042] Figure 11 This is a schematic diagram of a message subscription device provided in an embodiment of this application;

[0043] Figure 12 This is a schematic diagram of another message subscription device provided in an embodiment of this application;

[0044] Figure 13 This is a schematic diagram of a device structure provided in an embodiment of this application. Detailed Implementation

[0045] To make the objectives, technical solutions, and advantages of this application clearer, the application will be further described in detail below with reference to the accompanying drawings. Obviously, the described embodiments are merely some embodiments of this application, and not all embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of this application without creative effort are within the scope of protection of this application.

[0046] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or server that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or devices.

[0047] First, the relevant terms used in the embodiments of this specification are explained as follows:

[0048] Content Big Data: Using storage tools such as Elasticsearch and HBase to store text, image, and video content data imported from relevant applications, browsers, etc., each piece of content has corresponding content attributes; Elasticsearch is a search server based on Lucene, providing a distributed, multi-user full-text search engine; HBase is a distributed, column-oriented open-source database.

[0049] Content attributes: The inherent characteristics or descriptions contained in a text or image article or a video, such as title, cover image, details page, category, tags, activation status, timeliness, whether it is trending, PV (page view), VV (video view), likes, shares, reports, negative feedback, etc.

[0050] Message Subscription: After each piece of content undergoes a series of operations such as review, tagging, and cleaning, additional content attributes are added and modified, such as category, tags, security status, enable / disable, and hot topic timeliness. These content attributes are often of concern to many subscribers and require processing, and they need to subscribe to and process events to obtain the content attributes they have subscribed to.

[0051] Subscriber: The user who integrates the message subscription will provide information such as callback interface, subscription event, and subscription content attributes, and will be assigned a unique subscriber identifier appid for subsequent operation and maintenance.

[0052] Event processing: This involves processing or modifying one or more content attributes, such as making the cover image more concise, machine review, manual review, labeling and categorizing, security crackdowns, deletion and removal, and enabling distribution. Each event processing signifies the completion of processing certain content attributes and can be subscribed to by subscribers.

[0053] Cloud technology refers to a hosting technology that unifies hardware, software, and network resources within a wide area network (WAN) or local area network (LAN) to achieve data computation, storage, processing, and sharing. Cloud storage is a new concept that extends and develops from cloud computing. A distributed cloud storage system (hereinafter referred to as a storage system) refers to a storage system that uses cluster applications, grid technology, and distributed storage file systems to aggregate a large number of various types of storage devices (also called storage nodes) in a network through application software or application interfaces to work together and jointly provide data storage and business access functions. The content data in the embodiments of this application can be stored in a distributed cloud storage system.

[0054] Please see Figure 1The illustration shows an implementation environment provided in this application embodiment. The implementation environment may include: a content processing server 110, a proxy server 120, a subscription management server 130, and multiple message subscriber clients 140; wherein, the content processing server 110 and the proxy server 120, the proxy server 120 and the subscription management server 130, and the subscription management server 130 and the message subscriber clients 140 can communicate via a network.

[0055] Specifically, the content processing service 110 performs update operations such as adding, deleting, and modifying the content attributes of the content data; the proxy server 120 receives the update operation information of the content processing server 110 and broadcasts the update operation information to generate a content attribute processing event; the subscription management server 130 uniformly receives and parses the content attribute processing event to obtain the updated content attribute information contained in the content processing event, and matches it according to the message subscription rules of each subscriber, and pushes the matched updated content attribute information to the corresponding message subscriber client 140.

[0056] The message subscriber client 140 can communicate with the subscription management server 130 using either a browser / server (B / S) or client / server (C / S) architecture. The message subscriber client 140 may include physical devices such as smartphones, tablets, laptops, desktop computers, digital assistants, smart wearable devices, and in-vehicle terminals, and may also include software running on these physical devices, such as applications. The operating system running on the message subscriber client 140 in this embodiment may include, but is not limited to, Android, iOS, Linux, and Windows.

[0057] The various servers in the embodiments of this application can be independent physical servers, server clusters or distributed systems composed of multiple physical servers, or cloud servers that provide basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms.

[0058] To address the issues of high subscription costs and poor real-time performance in existing message publish-subscribe models, this application provides a message subscription method, the execution entity of which can be... Figure 1 For the subscription management server, please refer to [link / reference]. Figure 2 The method may specifically include:

[0059] S210. Collect content attribute processing events, which are generated based on updating the content attributes of the content data.

[0060] In this embodiment, the content attribute processing events collected by the subscription management server originate from the proxy server. Please refer to [link / reference needed] for details. Figure 3 It illustrates a method for a proxy server to generate content attribute processing events based on content update information, the method including:

[0061] S310. When the proxy server receives a message from the content processing server that the content attributes of the content data are updated, it obtains the updated content attributes and the attribute values ​​of the updated content attributes.

[0062] S320. The proxy server broadcasts the updated content attribute and the attribute value of the updated content attribute, and generates the content attribute processing event.

[0063] A proxy server is a separate server from both the content processing server and the subscription management server. It's introduced because tens of millions of content data entries are added daily, while the content processing server needs to process and update content attributes on a massive scale. To avoid impacting the content processing server's normal attribute processing and to decouple content processing from event generation, a proxy server is used to generate and broadcast content attribute processing events based on update information. Specifically, when the content processing server adds, deletes, or modifies content attributes, all actions are handled through the proxy service. This service uses the Hippo component for asynchronous message bypassing, which can be seen as message broadcasting. The subscription management server collects and processes these events through Hippo to ensure uninterrupted content attribute processing. Furthermore, the proxy server can distinguish between critical and non-critical content attributes, only bypassing the processing events for critical attributes to reduce the volume of data processed. Critical content attributes include those relevant to subscribed users; non-critical attributes may include development-related content attributes provided to internal technical staff.

[0064] Introducing a proxy server can reduce the processing pressure on the content processing server and improve the efficiency of generating content attribute processing events.

[0065] S220. The content attribute processing event is parsed to obtain the updated content attributes included in the content attribute processing event, and the attribute values ​​of the updated content attributes.

[0066] Because content data may be obtained from different sources, such as different apps or browsers, the format of the content data may vary. To achieve data format uniformity, the subscription management server will convert the corresponding data formats for unified storage and delivery; please refer to [link to details]. Figure 4 It illustrates a content attribute processing event parsing method, which may include:

[0067] S410. The content attribute processing event is split to obtain the original format content attribute and the original format attribute value corresponding to the original format content attribute.

[0068] S420. Convert the original format content attribute to the target format content attribute, and convert the original format attribute value to the target format attribute value.

[0069] S430. The target format content attribute is determined as the updated content attribute, and the target format attribute value is determined as the attribute value of the updated content attribute.

[0070] Since the content attribute processing event is obtained by updating the content attributes of the data content, the content attribute processing event can include the updated content attributes and the corresponding updated attribute values. During the parsing process, the content attribute processing event can first be split to obtain the content attribute part and the attribute value part of the content attributes. Then, based on the preset format conversion rules, the original format content attributes can be converted into the target format content attributes, and the original format attribute values ​​can be converted into the target format attribute values.

[0071] As can be seen from the above, the content processing server can perform update operations such as adding, deleting, and modifying content attributes of content data. Therefore, for content attribute processing events, the updated content attributes can be newly added, deleted, or modified. For newly added content attributes, the corresponding attribute value can be the newly added attribute value; for deleted content attributes, since the content attribute no longer exists after deletion, the corresponding attribute value can be an empty value; for modified content attributes, the corresponding attribute value can be the modified attribute value.

[0072] S230. Match the updated content attributes with the message subscription rules of multiple message subscribers to determine the matching message subscribers and the matching content attributes subscribed to by the matching message subscribers.

[0073] The message subscription rules can include subscription content attributes and status flags for these attributes. These status flags represent the current update status of the subscription content attributes. As mentioned above, the content processing server can add, delete, and modify content attributes, and each of these operations has corresponding status flags. By matching the status flags of the current content attributes, it can be determined whether the current content attribute meets the push rules. Please refer to the relevant documentation for details. Figure 5 It illustrates a method for matching subscription message rules, which may include:

[0074] S510. Determine the status marker information of the updated content attribute.

[0075] By analyzing the parsed content attribute processing events, the status marker information of updated content attributes can be determined. Specifically, this involves analyzing the operation type of the content attributes contained in the current content attribute processing event to determine whether the modification operation is an add, delete, or modify operation, thereby determining the status marker information of the updated content attributes. An add operation corresponds to an add marker status, a delete operation corresponds to a delete marker status, and a modify operation corresponds to a modify marker status. The specific status marker information of the updated content attributes can be directly carried in the content attribute processing event, or it can be determined based on the updated content attributes and their corresponding marker information.

[0076] S520. Match the updated content attributes and corresponding status flag information with the subscription content attributes and corresponding status flag information of each message subscriber.

[0077] S530. The subscription content attribute that matches the updated content attribute and whose corresponding status flag information matches is determined as the matching content attribute.

[0078] S540. The message subscriber containing the matching content attribute is determined as the matching message subscriber.

[0079] In the specific matching process, we can first check whether there is an updated content attribute in the subscription rules of each message subscriber. For message subscribers whose subscription rules have an updated content attribute, we can further determine whether the status flag information of the updated content attribute is the same as the status flag information of the content attribute found in the subscription rules. When the status flag information is the same, the content attribute found in the subscription rules will be determined as the matching content attribute.

[0080] The process of content attribute matching can be illustrated with an example. For each message subscriber, there are the following subscription rules:

[0081] Table 1

[0082] Message subscribers Subscription Rules A Content attribute 'a', status flag information 's2' B Content attribute 'a', status flag information 's1' C Content attribute b, status flag information is s1

[0083] For example, the updated content attribute 'a' has a corresponding status flag information 's1'. As can be seen from Table 1, the content attribute 'a' and the corresponding status flag information 's1' included in the subscription rules of message subscriber B match the updated content attribute 'a' and the corresponding status flag information 's1'. Therefore, the updated content attribute 'a' and the corresponding status flag information 's1' conform to the subscription rules of message subscriber B. It can be determined that the content attribute 'a' in the subscription rules of message subscriber B is a matching content attribute, and message subscriber B is a matching message subscriber.

[0084] S550. Based on each matching message subscriber and the matching content attribute corresponding to each matching message subscriber, generate the correspondence between the matching message subscriber and the matching content attribute.

[0085] For currently updated content attributes, once the corresponding matching message subscriber is determined, a correspondence can be established between the two to facilitate the subsequent push of subscription messages based on the correspondence. For example, a correspondence can be established between content attribute a and message subscriber B, so that the relevant update information of content attribute a can be pushed to message subscriber B.

[0086] For each message subscriber, the subscription rules it sets may include at least one configuration group, and the conditions within each configuration group can be configured through a logical AND relationship; when the subscription rule includes multiple configuration groups, the configuration groups can be configured through a logical OR relationship.

[0087] Specifically, each configuration group may include multiple subscription content attributes and corresponding status flag information, and the subscription content attributes are configured to have a logical AND relationship, meaning that for the same content, all of its corresponding subscription content attributes must be updated and the corresponding status flag information must match the updated content attributes and corresponding status flag information contained in the content attribute processing event before it meets the subscription conditions of the current configuration group.

[0088] Figure 5In the method shown, when the message subscription rule includes subscription content attributes and corresponding status flag information, it can match the updated content attributes and corresponding status flag information with the subscription content attributes of each message subscriber, focusing on the status change information of the content attributes. Alternatively, when the message subscription rule includes subscription content attributes and corresponding attribute values, it can match the updated content attributes and corresponding attribute values ​​with the subscription content attributes of each message subscriber, focusing on the updated attribute values. Specifically, the corresponding message subscription rules can be configured according to the needs of the message subscribers; this application embodiment does not impose specific limitations.

[0089] S240. Obtain the callback interface information of the matching message subscriber, and push the matching content attribute and the attribute value of the matching content attribute to the corresponding matching message subscriber based on the callback interface information.

[0090] For each message subscriber, its corresponding callback interface information can be stored in the subscription management server. Once a matching message subscriber is identified, the subscription management server will retrieve the callback interface information for that subscriber. This callback interface information includes the callback protocol, authentication information, and routing information. This information can then be pushed to the matching message subscriber. For details, please refer to [link to relevant documentation]. Figure 6 It illustrates a message push method, which may include:

[0091] S610. Determine the callback interface of the matching message subscriber, and authenticate the callback interface based on the authentication information of the callback interface.

[0092] S620. When authentication is successful, the target route is selected based on the routing information of the callback interface.

[0093] When authenticating callback interfaces, authentication can be based on an authentication method agreed upon between the subscription management server and the matching message subscribers. For example, it can be achieved by verifying a signature. When the subscription management server needs to push a message through the callback interface, it sends a request to the matching message subscriber corresponding to that callback interface. This request can include the subscription management server's signature information. The matching message subscriber verifies this signature information; if the verification passes, the callback interface authentication is successful. Authentication of the interface ensures the security of message callbacks, and selecting an appropriate route improves the efficiency and reliability of message callbacks.

[0094] S630. Based on the correspondence between the matching message subscriber and the matching content attribute, the callback protocol and the target route, the matching content attribute and the attribute value of the matching content attribute are pushed to the corresponding matching message subscriber.

[0095] After determining the callback interface information related to the callback interface, as well as the correspondence between the matching message subscriber and the matching content attribute, the corresponding content attribute and its attribute value can be pushed to the corresponding matching message subscriber.

[0096] It should be noted that a content attribute processing event in the embodiments of this application may include update information of the content attributes of a data content, and may specifically include update information of multiple content attributes of a data content; a content attribute processing event may also include update information of the content attributes of multiple data contents, and may specifically include update information of multiple content attributes of multiple data contents.

[0097] In addition, each piece of data can be configured with a corresponding content identifier. Each piece of data corresponds to at least one content attribute, which can carry a corresponding content ID to identify the data content to which it belongs. While pushing the matching content attributes and their corresponding attribute values ​​to the matching message subscribers, the content body of the data content corresponding to the matching content attributes can also be pushed simultaneously. For example, for an image and text piece, its corresponding content attributes include a title attribute. If the current update operation for the title attribute is a modification operation, then while pushing the title attribute and the modified title to the message subscribers, the image and text corresponding to that title attribute can also be pushed to the message subscribers. Furthermore, when pushing the content body of the data content to the message subscribers, the original content body can be pushed directly to the message subscribers, or the original content body can be personalized according to the needs of the message subscribers before being pushed to the corresponding message subscribers, thus meeting the personalized needs of the message subscribers.

[0098] Since each content attribute can carry a corresponding content ID, message subscribers can not only configure the content attributes they subscribe to, but also specify which specific data content attributes they want to subscribe to. This can be achieved through the subscription content ID. When the subscription management server parses the content attribute processing event to obtain the updated content attributes, it can first filter out the content attributes corresponding to each message subscriber from the updated content attributes based on their subscription content ID. Then, it matches the determined content attributes with the subscription content attributes to identify the matching content attributes. Alternatively, it can first determine the content attributes corresponding to each message subscriber from the updated content attributes based on their subscription content attributes, and then filter out the matching content attributes based on the message subscriber's subscription content ID.

[0099] In this embodiment of the application, after determining the matching message subscriber and the matching content attributes, it is not necessary to actively push the subscription message to the message subscriber. Instead, the corresponding subscription message is returned based on the message subscriber's query request. For details, please refer to [link / reference]. Figure 7 It demonstrates another method of message subscription, which may include:

[0100] S710. Collect content attribute processing events, which are generated based on updating the content attributes of the content data.

[0101] S720. The content attribute processing event is parsed to obtain the updated content attributes included in the content attribute processing event, and the attribute values ​​of the updated content attributes.

[0102] S730. Match the updated content attributes with the message subscription rules of multiple message subscribers to determine the matching message subscribers and the matching content attributes subscribed to by the matching message subscribers.

[0103] S740. Store the attribute values ​​of the matching content attributes subscribed to by the matching message subscriber in the message queue.

[0104] S750. In response to the subscription content attribute query request sent by the matching message subscriber, the attribute value of the matching content attribute in the message queue is returned to the matching message subscriber.

[0105] Specifically, a message queue can be created for each matching message subscriber, and the matching content attributes and corresponding attribute values ​​of that subscriber can be stored in the message queue. When a subscription content attribute query request is received from a matching message subscriber, the corresponding content attributes and attribute values ​​can be retrieved from the message queue corresponding to the subscriber's identifier and returned to the subscriber. Figure 7 The method shown allows message subscribers to actively retrieve subscribed messages by sending a subscription content attribute query request to the subscription management server. This is a process in which message subscribers actively query their subscribed messages.

[0106] For a single piece of content data, from the asynchronous bypassing of content attribute processing events to its push to message subscribers, it undergoes many processing steps. To facilitate analysis and identification of each process stage, it can be monitored. Please refer to [link to relevant documentation]. Figure 8 It illustrates a method for processing subscribed content, which may include:

[0107] S810. Determine the subscriber identifier and subscription content identifier corresponding to each subscription content.

[0108] S820. Monitor multiple process stages for processing each subscription content.

[0109] S830. Store the processing information for each subscription content at each of the multiple process stages.

[0110] S840. Based on the subscriber identifier, subscription content identifier, and processing information of each subscription content in the multiple process stages, generate a processing log corresponding to each subscription content.

[0111] S850. In response to a subscription content display request, wherein the subscription content display request includes a target subscription content identifier, the processing log of the subscription content corresponding to the target subscription content identifier is displayed, and the push status of the subscription content corresponding to the target subscription content identifier is displayed.

[0112] Each piece of subscribed content corresponds to at least one content attribute. When updating a content attribute, it can also be considered an update to the subscribed content. Using each piece of subscribed content as a unit, and in conjunction with the big data storage tool Elasticsearch, the processes of event collection, content attribute parsing, rule matching, callback push, and retry queue can be reported in stages, along with the subscriber identifier (appid) and content identifier (id). This facilitates locating each processing stage and the subscription push status. Furthermore, it can be integrated with Kibana to display the processing and reporting logs for each piece of content data, as well as the distribution of events pushed to subscribers, in a graphical format.

[0113] This application also provides a message subscription management system, which may include three functionalities:

[0114] 1. Functional positioning: Provide access to real-time services, that is, provide subscription for incremental processing events.

[0115] 2. Distribution Rules: Assign an appid to each subscriber and create subscription rules based on the processing events and content attributes provided by the subscriber; the subscriber needs to implement a unified protocol callback interface, and when a processing event occurs, push the content attributes to the subscriber through the callback, and support the subscriber to query the content attributes in real time, i.e., push and pull combined.

[0116] 3. Event Collection: Each time content attributes are added or modified, messages are processed asynchronously and bypassed to the outside world; the subscription system collects and processes messages, parses the content attributes contained in the event, and checks whether it matches the processing event that the subscriber is concerned about. If so, the message is pushed through the callback interface.

[0117] Please see Figure 9 Specifically, the system can be divided into a subscriber management module 910, a subscription field management module 920, a subscription rule management module 930, a rule engine module 940, an event collection module 950, a data formatting module 960, an event distribution module 970, a push callback module 980, and a callback interface management module 990. The functions of each module are summarized as follows:

[0118] 1. Subscriber Management Module 910: Used to allocate and maintain subscriber identifiers (appid), and supports modifying and viewing subscriber identifiers (appid).

[0119] 2. Subscription Field Management Module 920: Used to manage existing content attributes and maintain the subscription relationship between subscribers and content attributes. It supports managing, adding, modifying, and subscribing to content attributes for subscription rules.

[0120] 3. Rule Configuration Service Module 930: This module manages the processing events that each subscriber is interested in and allows others to query the effective review configurations. It also provides a web interface to support operations such as adding, modifying, enabling, and disabling rules.

[0121] 4. Rule Engine Module 940: Queries the subscription rules of each subscriber, receives and parses the processing events, matches subscribers that meet the subscription rules and responds to the caller.

[0122] 5. Event Collection Module 950: Collects externally provided processing events, converts the original event protocol into a format recognizable by the subscription system, matches the subscribers that need to be pushed through the rule engine, and then distributes the processing events through the event distribution module.

[0123] 6. Event Dispatch Module 960: This module obtains the content body required by the subscriber through the data formatting module and pushes the content body to the specified subscriber via the push callback module. The event dispatch module can support an event queue, where matched processing events can be stored and maintained. In this case, the subscriber does not need to provide a callback interface, but can actively query whether an event has been generated.

[0124] 7. Data Formatting Module 970: Retrieves the content fields already subscribed to by subscribers and queries content information using storage tools such as Elasticsearch and HBase. It supports various personalized processing of the content body, including data concatenation and format conversion, and also allows subscribers to query the content body by content ID.

[0125] 8. Push Callback Module 980: Obtain the callback interface of the subscriber through the callback interface management and push the content to the specified subscriber.

[0126] 9. Callback Interface Management Module 990: Responsible for maintaining the callback interfaces provided by subscribers, including but not limited to metadata such as callback protocol, timeout, authentication information, host, and routing selection.

[0127] This application collects and parses content attribute processing events generated based on the updating of content attributes in content data. This yields the updated content attributes and their corresponding values ​​within the events. By uniformly receiving and parsing these events, each subscriber is no longer required to collect and parse them individually, reducing integration costs and redundant work. The updated content attributes are matched against the message subscription rules of each subscriber to determine the matching subscribers and the content attributes they subscribe to. Based on the callback interface information of the matching subscribers, the matching content attributes and their corresponding values ​​are pushed to the respective subscribers. Through message subscription rule matching, specific subscription messages can be determined for each subscriber and pushed to them based on their interface information. Subscribers only need to receive the pushed subscription messages, reducing their processing burden. Furthermore, this application performs parsing, rule matching, and push operations as soon as content attribute processing events are collected, improving the real-time performance of message subscriptions.

[0128] The following example illustrates the specific implementation process of this application.

[0129] 1. Field Management

[0130] (1) The meaning and subscription status of each content attribute are displayed in web form. It supports querying subscribed and unsubscribed content attributes by each subscriber. For each content attribute, there are corresponding items such as English field name, Chinese field name, description, type, field value type, field source, field category, subscriber, and person in charge. Please refer to Figure 10(a) for details.

[0131] (2) In the subscription system, the content attributes involved are managed as fields, and the content types are distinguished as text and images, videos, accounts, etc. At the same time, the fields can be modified and added. For details, please refer to Figure 10(b).

[0132] (3) Each subscriber can subscribe to the content attributes they are interested in through the field management interface. Please refer to Figure 10(c) for details.

[0133] 2. Content Subscription Management

[0134] (1) Each subscriber has its own personalized subscription rules and different events to be processed. Therefore, there is a dedicated content subscription interface to manage subscription rules and events. Please refer to Figure 10(d) for details.

[0135] (2) When a subscriber has new subscription rules or needs to adjust existing subscription rules, adjustments can be made through web interaction. Please refer to Figures 10(e) and 10(f) for details. It can be seen that the rule matching groups are logically ORed, and the groups are logically ANDed. For example, 0 and 1 in Figure 10(e) represent the field content corresponding to the content attributes. For example, st_kd=0 indicates that it is not enabled in the content center, st_hotspot_recommend=1 indicates that hotspots are strongly recommended, and the existence of cc_eng_content_allhitkey_tag indicates that the relevant tag exists. Therefore, when performing subscription rule matching, for data content that meets all three conditions, its relevant subscription content attributes and content will be pushed to the message subscriber.

[0136] 3. Subscriber ID (appid) Management

[0137] (1) The allocation and maintenance of the subscriber identifier appid is integrated with the unified appid management system, which allows you to quickly view which subscribers have been assigned. Please refer to Figure 10(g).

[0138] (2) When a new subscriber appid needs to be assigned, it can be done through the new appid tab in Figure 10(h). If the subscriber does not have any special requirements for the appid, random appid generation is supported.

[0139] (3) The name, description and responsible person information of the assigned subscriber appid can be modified. Please refer to Figure 10(i).

[0140] This application, within the big data processing environment of the content center, meets the content attribute acquisition needs of various subscribers, facilitates data output from the content center, and enables content data collaboration with other teams; it supports web-based configuration of subscription fields and rules, greatly reducing online operation costs; it enables unified reception and processing of events, matching subscription rules, and querying content attributes, allowing subscribers to focus only on their own subscription fields and rules when integrating, significantly reducing integration costs.

[0141] This embodiment also provides a message subscription device; please refer to [link / reference]. Figure 11 The device may include:

[0142] The first event collection module 1110 is used to collect content attribute processing events, which are generated based on the update of content attributes of content data;

[0143] The first event parsing module 1120 is used to parse the content attribute processing event to obtain the updated content attribute included in the content attribute processing event and the attribute value of the updated content attribute.

[0144] The first rule matching module 1130 is used to match the updated content attributes with the message subscription rules of multiple message subscribers to determine the matching message subscribers and the matching content attributes subscribed to by the matching message subscribers.

[0145] The message push module 1140 is used to obtain the callback interface information of the matching message subscriber, and push the matching content attribute and the attribute value of the matching content attribute to the corresponding matching message subscriber based on the callback interface information.

[0146] Further, the first processing event collection module 1110 is specifically used to collect the content attribute processing events generated by the proxy server based on the content attribute update information of the content data by the content processing server; wherein, the content attribute processing events generated by the proxy server based on the content attribute update information of the content data by the content processing server include:

[0147] When the proxy server receives a message from the content processing server that the content attributes of the content data have been updated, it obtains the updated content attributes and the attribute values ​​of the updated content attributes.

[0148] The proxy server broadcasts the updated content attributes and their values, generating the content attribute processing event.

[0149] Furthermore, the first event parsing module 1120 includes:

[0150] The event splitting module is used to split the content attribute processing event to obtain the original format content attribute and the original format attribute value corresponding to the original format content attribute;

[0151] The format conversion module is used to convert the original format content attributes into target format content attributes, and to convert the original format attribute values ​​into target format attribute values;

[0152] The first determining module is used to determine the target format content attribute as the updated content attribute, and to determine the target format attribute value as the attribute value of the updated content attribute.

[0153] The message subscription rule includes subscription content attributes and status flag information for the subscription content attributes; correspondingly, the first rule matching module 1130 includes:

[0154] The status marker information determination module is used to determine the status marker information of the updated content attribute;

[0155] The first matching module is used to match the updated content attributes and corresponding status flag information with the subscription content attributes and corresponding status flag information of each message subscriber, respectively.

[0156] The second determining module is used to determine the subscription content attribute that matches the updated content attribute and the corresponding status marker information as the matching content attribute;

[0157] The third determining module is used to determine the message subscriber containing the matching content attribute as the matching message subscriber;

[0158] The mapping generation module is used to generate a mapping relationship between each matching message subscriber and the matching content attribute based on each matching message subscriber and the matching content attribute corresponding to each matching message subscriber.

[0159] The callback interface information includes: callback protocol, authentication information, and routing information; correspondingly, the message push module 1140 includes:

[0160] The authentication module is used to determine the callback interface of the matching message subscriber and to authenticate the callback interface based on the authentication information of the callback interface.

[0161] The routing module is used to select a target route based on the routing information of the callback interface when authentication is successful.

[0162] The first push module is used to push the matching content attributes and their attribute values ​​to the corresponding matching message subscribers based on the correspondence between the matching message subscribers and the matching content attributes, the callback protocol, and the target route.

[0163] The device may also include a monitoring module, which may include:

[0164] The fourth determination module is used to determine the subscriber identifier and subscription content identifier corresponding to each subscription content;

[0165] The process monitoring module is used to monitor multiple process stages for processing each subscription item;

[0166] The information storage module is used to store the processing information of each subscription content in the multiple process stages;

[0167] The processing log generation module is used to generate processing logs corresponding to each subscription content based on the subscriber identifier, subscription content identifier, and processing information of each subscription content in the multiple process stages.

[0168] The display module is used to respond to a subscription content display request, which includes a target subscription content identifier, display the processing log of the subscription content corresponding to the target subscription content identifier, and display the push status of the subscription content corresponding to the target subscription content identifier.

[0169] Please see Figure 12 It demonstrates another messaging subscription device, including:

[0170] The second processing event collection module 1210 is used to collect content attribute processing events, which are generated based on updating the content attributes of content data;

[0171] The second event parsing module 1220 is used to parse the content attribute processing event to obtain the updated content attribute included in the content attribute processing event and the attribute value of the updated content attribute.

[0172] The second rule matching module 1230 is used to match the updated content attributes with the message subscription rules of multiple message subscribers to determine the matching message subscribers and the matching content attributes subscribed to by the matching message subscribers.

[0173] The queue storage module 1240 is used to store the attribute values ​​of the matching content attributes subscribed to by the matching message subscriber in the message queue;

[0174] The message query module 1250 is used to respond to the subscription content attribute query request sent by the matching message subscriber and return the attribute value of the matching content attribute in the message queue to the matching message subscriber.

[0175] The apparatus provided in the above embodiments can execute the methods provided in any embodiment of this application, and has the corresponding functional modules and beneficial effects for executing the method. Technical details not described in detail in the above embodiments can be found in the methods provided in any embodiment of this application.

[0176] This embodiment also provides a computer storage medium storing at least one instruction or at least one program, wherein the at least one instruction or the at least one program is loaded by a processor and executed as any of the methods described in this embodiment.

[0177] This embodiment also provides a computer program product or computer program that includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform any of the methods described in this embodiment.

[0178] This embodiment also provides a device, the structural diagram of which can be found in the following figure. Figure 13 The device 1300 can vary significantly in configuration or performance, and may include one or more central processing units (CPUs) 1322 (e.g., one or more processors) and memory 1332, and one or more storage media 1330 (e.g., one or more mass storage devices) for storing applications 1342 or data 1344. The memory 1332 and storage media 1330 may be temporary or persistent storage. Programs stored in the storage media 1330 may include one or more modules (not shown), each module including a series of instruction operations on the device. Furthermore, the CPU 1322 may be configured to communicate with the storage media 1330 and execute the series of instruction operations in the storage media 1330 on the device 1300. The device 1300 may also include one or more power supplies 1326, one or more wired or wireless network interfaces 1350, one or more input / output interfaces 1358, and / or one or more operating systems 1341, such as Windows Server. TM Mac OS X TM Unix TM Linux TM FreeBSD TM Etc. Any of the methods described above in this embodiment can be based on... Figure 13 The equipment shown is used for implementation.

[0179] This specification provides the operational steps of the methods described in the embodiments or flowcharts, but more or fewer operational steps may be included based on conventional or non-inventive labor. The steps and order listed in the embodiments are merely one possible execution order among many steps and do not represent the only execution order. In actual system or interrupt product execution, the methods shown in the embodiments or drawings can be executed sequentially or in parallel (e.g., in a parallel processor or multi-threaded processing environment).

[0180] The structure shown in this embodiment is only a partial structure related to the solution of this application and does not constitute a limitation on the device to which the solution of this application is applied. Specific devices may include more or fewer components than shown, or combinations of certain components, or arrangements of different components. It should be understood that the methods, apparatuses, etc., disclosed in this embodiment can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative. For example, the division of modules is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection between devices or unit modules through some interfaces.

[0181] Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as a USB flash drive, a portable hard drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0182] Those skilled in the art will further recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed in this specification can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of each example have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0183] The above-described embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application.

Claims

1. A message subscription method, characterized in that, include: Collect content attribute processing events, which are generated based on updating the content attributes of the content data; The content attribute processing event is parsed to obtain the updated content attributes included in the content attribute processing event, and the attribute values ​​of the updated content attributes. The updated content attribute is matched with the message subscription rules of multiple message subscribers to determine the matching message subscriber and the matching content attribute subscribed to by the matching message subscriber. The message subscription rule includes the subscription content attribute and the status flag information of the subscription content attribute. The status flag information is used to characterize the current update status of the subscription content attribute. The step of matching the updated content attribute with the message subscription rules of multiple message subscribers to determine the matching message subscriber and the matching content attribute subscribed to by the matching message subscriber includes: Determine the status marker information of the updated content attributes; The updated content attributes and corresponding status flag information are matched with the subscription content attributes and corresponding status flag information of each message subscriber; The subscription content attribute that matches the updated content attribute and whose corresponding status flag information matches is determined as the matching content attribute; The message subscriber that contains the matching content attribute is identified as the matching message subscriber; Based on each matching message subscriber and the matching content attribute corresponding to each matching message subscriber, a correspondence between matching message subscribers and matching content attributes is generated; Obtain the callback interface information of the matching message subscriber, and push the matching content attribute and the attribute value of the matching content attribute to the corresponding matching message subscriber based on the callback interface information.

2. The message subscription method according to claim 1, characterized in that, The events for handling the collected content attributes include: The proxy server collects the content attribute processing events generated based on the content attribute update information of the content data by the content processing server; The content attribute processing event generated by the proxy server based on the content attribute update information of the content data by the content processing server includes: When the proxy server receives a message from the content processing server that the content attributes of the content data have been updated, it obtains the updated content attributes and the attribute values ​​of the updated content attributes. The proxy server broadcasts the updated content attributes and their values, generating the content attribute processing event.

3. The message subscription method according to claim 1, characterized in that, The step of parsing the content attribute processing event to obtain the updated content attributes included in the content attribute processing event, and the attribute values ​​of the updated content attributes, include: The content attribute processing event is split to obtain the original format content attribute and the original format attribute value corresponding to the original format content attribute; The original format content attributes are converted into target format content attributes, and the original format attribute values ​​are converted into target format attribute values; The target format content attribute is determined as the updated content attribute, and the target format attribute value is determined as the attribute value of the updated content attribute.

4. The message subscription method according to claim 1, characterized in that, The callback interface information includes: callback protocol, authentication information, and routing information; The step of pushing the matched content attribute and its value to the corresponding matched message subscriber based on the callback interface information includes: Determine the callback interface of the matching message subscriber, and authenticate the callback interface based on the authentication information of the callback interface; When authentication is successful, the target route is selected based on the routing information from the callback interface; Based on the correspondence between the matching message subscriber and the matching content attribute, the callback protocol, and the target route, the matching content attribute and its attribute value are pushed to the corresponding matching message subscriber.

5. A message subscription method according to claim 1, characterized in that, The method further includes: Determine the subscriber identifier and subscription content identifier corresponding to each subscription content; Monitor the multiple stages of the process for handling each subscribed content; The processing information for each subscription item is stored at each of the multiple process stages; Based on the subscriber identifier, subscription content identifier, and processing information of each subscription content in the multiple process stages, a processing log corresponding to each subscription content is generated. In response to a subscription content display request, which includes a target subscription content identifier, the processing logs of the subscription content corresponding to the target subscription content identifier are displayed, and the push status of the subscription content corresponding to the target subscription content identifier is displayed.

6. A message subscription method, characterized in that, include: Collect content attribute processing events, which are generated based on updating the content attributes of the content data; The content attribute processing event is parsed to obtain the updated content attributes included in the content attribute processing event, and the attribute values ​​of the updated content attributes. The updated content attribute is matched with the message subscription rules of multiple message subscribers to determine the matching message subscriber and the matching content attribute subscribed to by the matching message subscriber. The message subscription rule includes the subscription content attribute and the status flag information of the subscription content attribute. The status flag information is used to characterize the current update status of the subscription content attribute. The step of matching the updated content attribute with the message subscription rules of multiple message subscribers to determine the matching message subscriber and the matching content attribute subscribed to by the matching message subscriber includes: Determine the status marker information of the updated content attributes; The updated content attributes and corresponding status flag information are matched with the subscription content attributes and corresponding status flag information of each message subscriber; The subscription content attribute that matches the updated content attribute and whose corresponding status flag information matches is determined as the matching content attribute; The message subscriber that contains the matching content attribute is identified as the matching message subscriber; Based on each matching message subscriber and the matching content attribute corresponding to each matching message subscriber, a correspondence between matching message subscribers and matching content attributes is generated; Store the attribute values ​​of the matching content attributes subscribed to by the matching message subscriber in the message queue; In response to the subscription content attribute query request sent by the matching message subscriber, the attribute value of the matching content attribute in the message queue is returned to the matching message subscriber.

7. A message subscription device, characterized in that, include: The first event collection module is used to collect content attribute processing events, which are generated based on the update of content attributes of content data; The first event parsing module is used to parse the content attribute processing event to obtain the updated content attribute included in the content attribute processing event, and the attribute value of the updated content attribute. The first rule matching module is used to match the updated content attributes with the message subscription rules of multiple message subscribers to determine the matching message subscribers and the matching content attributes subscribed to by the matching message subscribers; the message subscription rules include subscription content attributes and status flag information of the subscription content attributes; The status marker information is used to characterize the current update status of the subscribed content attributes; The first rule matching module includes: a status marker information determination module, used to determine the status marker information of the updated content attribute; a first matching module, used to match the updated content attribute and the corresponding status marker information with the subscription content attribute and the corresponding status marker information of each message subscriber; a second determination module, used to determine the subscription content attribute that matches the updated content attribute and the corresponding status marker information as the matched content attribute; a third determination module, used to determine the message subscriber containing the matched content attribute as the matched message subscriber; and a correspondence generation module, used to generate a correspondence between the matched message subscriber and the matched content attribute based on each matched message subscriber and the matched content attribute corresponding to each matched message subscriber. The message push module is used to obtain the callback interface information of the matching message subscriber, and push the matching content attribute and the attribute value of the matching content attribute to the corresponding matching message subscriber based on the callback interface information.

8. The apparatus according to claim 7, characterized in that, The first processing event collection module is used to collect the content attribute processing events generated by the proxy server based on the content attribute update information of the content data by the content processing server; wherein, the content attribute processing events generated by the proxy server based on the content attribute update information of the content data by the content processing server include: When the proxy server receives a message from the content processing server that the content attributes of the content data have been updated, it obtains the updated content attributes and the attribute values ​​of the updated content attributes. The proxy server broadcasts the updated content attributes and their values, generating the content attribute processing event.

9. The apparatus according to claim 7, characterized in that, The first event parsing module includes: The event splitting module is used to split the content attribute processing event to obtain the original format content attribute and the original format attribute value corresponding to the original format content attribute; The format conversion module is used to convert the original format content attributes into target format content attributes, and to convert the original format attribute values ​​into target format attribute values; The first determining module is used to determine the target format content attribute as the updated content attribute, and to determine the target format attribute value as the attribute value of the updated content attribute.

10. The apparatus according to claim 7, characterized in that, The callback interface information includes: callback protocol, authentication information, and routing information; correspondingly, the message push module includes: The authentication module is used to determine the callback interface of the matching message subscriber and to authenticate the callback interface based on the authentication information of the callback interface. The routing module is used to select a target route based on the routing information of the callback interface when authentication is successful. The first push module is used to push the matching content attributes and their attribute values ​​to the corresponding matching message subscribers based on the correspondence between the matching message subscribers and the matching content attributes, the callback protocol, and the target route.

11. The apparatus according to claim 7, characterized in that, The device further includes a monitoring module, which comprises: The fourth determination module is used to determine the subscriber identifier and subscription content identifier corresponding to each subscription content; The process monitoring module is used to monitor multiple process stages for processing each subscription item; The information storage module is used to store the processing information of each subscription content in the multiple process stages; The processing log generation module is used to generate processing logs corresponding to each subscription content based on the subscriber identifier, subscription content identifier, and processing information of each subscription content in the multiple process stages. The display module is used to respond to a subscription content display request, which includes a target subscription content identifier, display the processing log of the subscription content corresponding to the target subscription content identifier, and display the push status of the subscription content corresponding to the target subscription content identifier.

12. A message subscription device, characterized in that, include: The second event collection module is used to collect content attribute processing events, which are generated based on the update of content attributes of content data; The second event parsing module is used to parse the content attribute processing event to obtain the updated content attribute included in the content attribute processing event, and the attribute value of the updated content attribute. The second rule matching module is used to match the updated content attribute with the message subscription rules of multiple message subscribers to determine the matching message subscriber and the matching content attribute subscribed to by the matching message subscriber. The message subscription rule includes the subscription content attribute and status flag information of the subscription content attribute. The status flag information is information used to characterize the current update status of the subscription content attribute. Matching the updated content attribute with the message subscription rules of multiple message subscribers to determine the matching message subscriber and the matching content attribute subscribed to by the matching message subscriber includes: Determine the status marker information of the updated content attributes; The updated content attributes and corresponding status flag information are matched with the subscription content attributes and corresponding status flag information of each message subscriber; The subscription content attribute that matches the updated content attribute and whose corresponding status flag information matches is determined as the matching content attribute; The message subscriber that contains the matching content attribute is identified as the matching message subscriber; Based on each matching message subscriber and the matching content attribute corresponding to each matching message subscriber, a correspondence between matching message subscribers and matching content attributes is generated; The queue storage module is used to store the attribute values ​​of the matching content attributes subscribed to by the matching message subscriber in the message queue; The message query module is used to respond to the subscription content attribute query request sent by the matching message subscriber and return the attribute value of the matching content attribute in the message queue to the matching message subscriber.

13. A message subscription device, characterized in that, The device includes a processor and a memory, the memory storing at least one instruction or at least one program, the at least one instruction or the at least one program being loaded and executed by the processor to implement the message subscription method as described in any one of claims 1 to 6.

14. A computer storage medium, characterized in that, The storage medium stores at least one instruction or at least one program segment, which is loaded and executed by a processor according to any one of claims 1 to 6.

15. A computer program product comprising computer instructions stored in a computer-readable storage medium; a processor of a computer device reading the computer instructions from the computer-readable storage medium, the processor executing the computer instructions to cause the computer device to perform the message subscription method as described in any one of claims 1 to 6.

Images