CN118803037A - Message processing method, device, electronic device, storage medium and program product - Google Patents

Abstract

The present disclosure provides a message processing method, apparatus, electronic device, storage medium, and program product. The message processing method is applied to the terminal and comprises the following steps: acquiring current state information of a terminal; based on the state information, sending a first request to a subscription platform; the first request carries state information or attribute information of subscription information; a first message is received from a subscription platform. Therefore, the terminal can determine which data subscription processing needs to be performed based on the state information of the terminal, so that the terminal can dynamically adjust the data subscription and processing strategy to realize more flexible and intelligent management, can meet various requirements, and is suitable for various application scenes. Meanwhile, the subscription platform does not push all relevant messages (full data) to the terminal, but selectively and correspondingly sends subscription information according to the request sent by the terminal. Therefore, the problem of network congestion is solved by the mutual coordination of the terminal and the subscription platform, and the processing efficiency is improved.

Description

Message processing method, device, electronic device, storage medium and program product

Technical Field

The present disclosure relates to the field of communication technology, and in particular to a message processing method, device, electronic device, storage medium and program product.

Background Art

At present, the main way to process messages is to push all relevant notification messages to the terminal side for subscription processing to obtain subscription messages. However, this message processing method is relatively single and rigid, and is not suitable for a variety of application scenarios. At the same time, the existing message processing uses full data, which is easy to cause network congestion and reduce processing efficiency.

Summary of the invention

The present disclosure is proposed in view of the above problems. The present disclosure provides a message processing method, device, electronic device, storage medium and program product.

According to a first aspect of the present disclosure, a message processing method is provided, which is applied to a terminal, and the method includes: obtaining current status information of the terminal; based on the status information, sending a first request to a subscription platform; the first request carries status information or attribute information of the subscription message; and receiving a first message from the subscription platform.

In addition, according to the method of the first aspect of the present disclosure, the status information includes at least one of the following: screen status, battery status, and network status.

In addition, according to the method of the first aspect of the present disclosure, based on the status information, a first request is sent to the subscription platform, including: based on the status information, determining the target level currently corresponding to the terminal in the preset subscription level; the subscription level is used to indicate the importance of the subscription message; sending a first request to the subscription platform, the first request carries attribute information of the subscription message; the attribute information includes at least one of the following: target level, message identifier corresponding to the target level.

In addition, according to the method of the first aspect of the present disclosure, the message identifiers corresponding to the target level include: message identifiers in the first set; wherein the first set is the message set corresponding to the target level; message identifiers in the second set; wherein the second set is the message set corresponding to other subscription levels with higher importance than the target level; wherein, sorted in descending order of importance, the subscription levels include at least one of the following: first level, second level, third level, fourth level; wherein the first level corresponds to subscription messages of the key message layer; the second level corresponds to subscription messages of the general message layer; the third level corresponds to subscription messages of the interactive message layer; and the fourth level corresponds to subscription messages of the ignorable message layer.

In addition, according to the method of the first aspect of the present disclosure, based on the status information, the target level currently corresponding to the terminal is determined in the preset subscription level, including: when the screen status is the screen-off state, determining the target level as the first level; or, when the screen status is the screen-on state, determining the target level as the third level.

In addition, according to the method of the first aspect of the present disclosure, when the current screen state of the terminal changes from the screen-off state to the screen-on state, the method also includes: sending a second request to the subscription platform, the second request is used to request the subscription platform to feedback unsubscribed messages during the screen-off state; the unsubscribed messages include: second-level and/or third-level messages; receiving a second message from the subscription platform.

In addition, according to the method of the first aspect of the present disclosure, the first request is used to request subscription to a first message; and/or, the third request is used to request cancellation of subscription to a third message, where the third message is a subscribed message that does not match the status information.

According to the first aspect of the present disclosure, a message processing method is provided, which is applied to a subscription platform, and the method includes: receiving a first request from a terminal; the first request carries status information of the terminal or attribute information of a subscription message; based on the first request, updating a subscription relationship maintained in the subscription platform; when any first message is received, sending a first message to a target terminal based on the subscription relationship.

In addition, according to the method of the second aspect of the present disclosure, the method also includes: maintaining a subscription relationship in the form of a bitmap; wherein the subscription relationship is stored with the user identifier of any first user as the key and the user identifier of the second user as the value; wherein the first user and the second user have a subscription relationship; wherein the subscription relationship includes: a subscriber relationship and a subscribed relationship.

In addition, according to the method of the second aspect of the present disclosure, based on the first request, the subscription relationship maintained in the subscription platform is updated, including: based on the first request, determining the third user corresponding to the first request; the third user is the subscription object indicated by the first request; establishing a subscription relationship between the first user corresponding to the terminal and the third user; wherein the subscription relationship includes: a subscriber relationship and a subscribed relationship; and storing the subscription relationship in the subscription platform.

In addition, according to the method of the second aspect of the present disclosure, based on the first request, determining the third user corresponding to the first request includes: based on the subscription type of the first request, obtaining a contact set corresponding to the subscription type; based on the contact set, determining the third user; wherein the subscription type includes at least one of the following: contact subscription, enterprise subscription, and member subscription.

In addition, according to the method of the second aspect of the present disclosure, a first message is sent to the target terminal based on a subscription relationship, including: determining the target terminal corresponding to the first message based on the subscription relationship; obtaining the target level currently corresponding to each target terminal; and when the first message belongs to the target level, sending the first message to the target terminal.

In addition, according to the method of the second aspect of the present disclosure, the method also includes: determining the target level currently corresponding to the terminal in the preset subscription level based on the status message carried in the first request; the subscription level is used to indicate the importance of the subscription message; caching or updating the target level.

In addition, according to the method of the second aspect of the present disclosure, based on the status message carried in the first request, the target level currently corresponding to the terminal is determined in the preset subscription level, including: when the screen status carried in the first request is the screen-off state, the target level is determined to be the first level; or, when the screen status carried in the first request is the screen-on state, the target level is determined to be the third level.

In addition, according to the method of the second aspect of the present disclosure, when the screen state in the first request changes from the screen-off state to the screen-on state, the method also includes: receiving a second request from the terminal, the second request is used to request feedback of unsubscribed messages during the screen-off state; the unsubscribed messages include: second-level and/or third-level messages; sending a second message to the terminal; the second message carries the unsubscribed messages during the screen-off state.

According to a third aspect of the present disclosure, a message processing device is provided, which is arranged in a terminal, and the device includes: an acquisition unit, used to acquire current status information of the terminal; a sending unit, used to send a first request to a subscription platform based on the status information; the first request carries status information or attribute information of the subscription message; and a receiving unit, used to receive a first message from the subscription platform.

According to a fourth aspect of the present disclosure, a message processing device is provided, which is arranged on a subscription platform, and the device includes: a receiving unit, used to receive a first request from a terminal; the first request carries status information of the terminal or attribute information of the subscription message; an updating unit, used to update the subscription relationship maintained in the subscription platform based on the first request; and a sending unit, used to send the first message to the target terminal based on the subscription relationship when any first message is received.

According to a fifth aspect of the present disclosure, an electronic device is provided, comprising: a memory for storing computer-readable instructions; and a processor for executing the computer-readable instructions so that the electronic device executes a method as in any embodiment.

According to a sixth aspect of the present disclosure, a non-transitory computer-readable storage medium is provided for storing computer-readable instructions, which, when executed by a processor, causes the processor to execute a method as in any one of the embodiments.

According to a seventh aspect of the present disclosure, a computer program product is provided, including a computer program, and when the computer program is executed by a processor, the method of any embodiment is implemented.

The present disclosure provides a message processing method, device, electronic device, storage medium and program product. The terminal can obtain its own status information. The terminal can determine to send a first request to a subscription platform based on the status information. The first request information carries the status information or the attribute information of the subscription message. Finally, the terminal can receive a first message from the subscription platform. The first message can be understood as a response message to the first request. In this way, the terminal can determine which data needs to be subscribed based on its own status information, so that the terminal can dynamically adjust the data subscription and processing strategy to achieve more flexible and intelligent management, which can meet various needs and is suitable for various application scenarios. At the same time, the subscription platform no longer pushes all relevant messages (full data) to the terminal, but selectively sends subscription information according to the request sent by the terminal. In this way, the mutual cooperation between the terminal and the subscription platform solves the problem of network congestion and improves processing efficiency.

It is to be understood that both the foregoing general description and the following detailed description are exemplary, and are intended to provide further explanation of the technology as claimed.

BRIEF DESCRIPTION OF THE DRAWINGS

The above and other purposes, features and advantages of the present disclosure will become more apparent by describing the embodiments of the present disclosure in more detail in conjunction with the accompanying drawings. The accompanying drawings are used to provide a further understanding of the embodiments of the present disclosure and constitute a part of the specification. Together with the embodiments of the present disclosure, they are used to explain the present disclosure and do not constitute a limitation of the present disclosure. In the accompanying drawings, the same reference numerals generally represent the same components or steps.

FIG. 1 is a system module framework diagram of an embodiment of the present disclosure.

FIG. 2 is an interaction diagram of the message processing method according to an embodiment of the present disclosure.

FIG. 3 is a method for determining a target level provided by an embodiment of the present disclosure.

FIG. 4 is a flow chart of contact subscription provided by an embodiment of the present disclosure.

FIG5 is a flow chart of enterprise subscription provided by an embodiment of the present disclosure.

FIG6 is a flowchart of member subscription provided by an embodiment of the present disclosure.

FIG. 7 is a structural block diagram of a message processing device provided in an embodiment of the present disclosure.

FIG8 is a structural block diagram of a message processing device provided in an embodiment of the present disclosure.

FIG9 is a hardware block diagram of an electronic device provided in an embodiment of the present disclosure;

FIG. 10 is a schematic diagram of a computer-readable storage medium provided in an embodiment of the present disclosure.

DETAILED DESCRIPTION

In order to make the purpose, technical solution and advantages of the present disclosure more obvious, the exemplary embodiments according to the present disclosure will be described in detail with reference to the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present disclosure, rather than all the embodiments of the present disclosure, and it should be understood that the present disclosure is not limited to the exemplary embodiments described here.

At present, the main way to process messages is to push all relevant notification messages to the terminal side for subscription processing to obtain subscription messages. However, this message processing method is relatively single and rigid, and is not suitable for a variety of application scenarios. At the same time, the existing message push uses the method of pushing full data, which is easy to cause network congestion and reduce processing efficiency.

In this way, the present application proposes a message processing method, which can enable the terminal to flexibly adjust the subscription data based on its own status information, and the subscription platform no longer pushes all the full data to the terminal, but selectively sends the subscription data based on the terminal's request, thereby solving the problem of network congestion and improving processing efficiency. First, Figure 1 is a system module framework diagram of an embodiment of the present disclosure. As shown in Figure 1, the entire message processing system includes: a terminal 101 and a subscription platform 102.

Terminal 101, which may also be referred to as terminal equipment, mobile station, mobile terminal, etc., is capable of communicating with the subscription platform side. The terminal may be an application (app) or an information system (web). In the embodiments of the present disclosure, the terminal mainly functions as follows: (1) providing interactive functions with users: login and connection establishment, channel/temporary session creation, monitoring, application/release of speech rights, etc. (2) voice collection, encoding and decoding, playback, collection of intercom-related data, etc.

The subscription platform 102, which may also be referred to as a subscription server, server, etc., may implement subscription message services with terminal devices. In the disclosed embodiment, the subscription platform 102 includes but is not limited to at least one of the following: signaling services, intercom services, and member services.

Among them, the main functions of the signaling service are: (1) maintaining the network communication protocol connection with the terminal's web socket; (2) forwarding uplink and downlink signaling data. The main functions of the intercom service are: (1) receiving and processing temporary sessions or the creation of temporary sessions; (2) receiving and processing applications for speaking rights; maintaining channel or temporary session membership and priority. The main functions of the member service are: (1) maintaining user basic information (such as role, account, etc.) and associated device information; (2) user login authentication; (3) maintenance in offline state.

Next, please refer to Figure 2, which is an interaction diagram of the message processing method of the embodiment of the present disclosure. As shown in Figure 2, the method includes:

In step S101, the terminal obtains current status information.

In the disclosed embodiments, the terminal can obtain its own current status information by collecting. Among them, the status information of the terminal includes but is not limited to at least one of the following: screen status, power status, and network status. The screen status can be the screen is in the bright screen state; the screen is in the off screen state. The power status may include but is not limited to at least one of the remaining battery power and charging status of the terminal device. The network status includes but is not limited to whether the device is connected to the network, the connection type (such as Wi-Fi, cellular data), the network signal strength, etc. The specific method of obtaining the status information is not limited here, and can be flexibly adjusted according to actual needs.

In step S102, the terminal sends a first request to the subscription platform based on the state information; the first request carries the state information or attribute information of the subscription message.

In the embodiment of the present disclosure, after obtaining the current state information, the terminal analyzes its own needs based on the information and sends a first request to the subscription platform accordingly. The first request is a request to subscribe to a first message. The first message is a response message to the first request, and the first message carries the subscription message of the terminal, which may include but is not limited to at least one of the following: a subscription message corresponding to the state information or a subscription message corresponding to the attribute information.

The information carried by the first request is status information or attribute information of the subscription message. When the first request carries status information, the terminal directly sends the status information to the subscription platform, and the subscription platform needs to determine which messages the terminal subscribes to based on the status information; when the first request carries attribute information of the subscription information, the terminal can directly send the subscription message to the subscription platform.

At the same time, it should be noted that the first request is a request for subscription messages, and the terminal sends the current first request to the subscription platform to obtain subscription messages based on the current first request. However, if there is a new first request, the new first request can overwrite the current first request and obtain the subscription message of the new first request. That is, the terminal can repeatedly send the first request to the subscription platform to timely adjust the subscription messages to which it wants to subscribe. In addition, in other embodiments, the terminal can also cancel certain subscription messages previously subscribed by sending a third message to the subscription platform.

In step S103, the subscription platform receives a first request from the terminal.

In the embodiment of the present disclosure, the subscription platform may receive the first request from the terminal by calling an application programming interface (API). The manner in which the subscription platform receives the first request is not limited herein.

In step S104, the subscription platform updates the subscription relationship maintained in the subscription platform based on the first request.

In the embodiment of the present disclosure, the subscription platform will update the subscription relationship maintained by the subscription platform according to the received first request. The subscription relationship includes a subscriber relationship and a subscriber relationship. The subscriber relationship includes at least: the relationship between a "subscriber" and "each subscriber subscribed by the subscriber", that is, the relationship between each subscriber and its subscriber. The subscriber relationship includes at least: the relationship between a "subscriber" and "each subscriber who subscribes to the subscriber", that is, the relationship between each subscriber and its subscriber.

Specifically, the subscription platform can parse the received first request and request data verification. If the requested data verification is valid, the existing subscription relationship is queried. If a subscription relationship exists, the subscription status is updated (e.g., from an inactive status to an active status); if a subscription relationship does not exist, a new subscription relationship is created to update the subscription relationship. The specific update method is not limited here.

In step S105, when any first message is received, the subscription platform sends the first message to the target terminal based on the subscription relationship.

In step S106, the terminal receives a first message from the subscription platform.

In the disclosed embodiment, the target terminal is a terminal determined in the subscription relationship of the subscription platform. The first message can be understood as a response message to the first request, and the first message carries the subscription message of the terminal, which may include but is not limited to at least one of the following: a subscription message corresponding to the status information or a subscription message corresponding to the attribute information. When any first message is received, the subscription platform will send the first message to the target terminal based on the subscription relationship. Specifically, the first message can be received through at least one of an API interface, a message queue, and real-time communication. When any first message is received, the subscription platform can parse the message content, and based on the parsed message content, the subscription platform can search for the subscription relationship maintained by itself and filter out all subscribed target terminals. For each target terminal, the subscription platform can use at least one of an appropriate communication protocol or mechanism to send the first message to the target terminal. The terminal receives the first message from the subscription platform and completes the entire message processing process.

In summary, the terminal can decide which data needs to be subscribed based on its own status information, and can dynamically adjust data subscription and processing strategies to achieve more flexible and intelligent management, which is suitable for a variety of application scenarios. At the same time, the terminal uses its own status information instead of the entire amount of data to process messages, which solves the problem of network congestion and improves processing efficiency.

As mentioned above, the design of determining the subscription request based on the terminal's state information in the disclosed embodiment enables the terminal to dynamically adjust the data subscription and processing strategy to achieve a more intelligent and flexible relationship. The following specifically introduces how the terminal will use the state information to determine the first request.

According to an embodiment of the present disclosure, a method in which a terminal sends a first request to a subscription platform based on state information includes:

Based on the status information, determine the target level currently corresponding to the terminal in the preset subscription level; the subscription level is used to indicate the importance of the subscription message;

A first request is sent to the subscription platform, where the first request carries attribute information of the subscription message; the attribute information includes at least one of the following: a target level and a message identifier corresponding to the target level.

Among them, the status message may include but is not limited to at least one of the following: screen status, power status and network status. The preset subscription level is used to indicate the importance of the user's subscription message. In an exemplary embodiment, multiple levels can be set, and each level has its own corresponding subscription message; for example, the subscription level may include the first level (critical), the second level (general), the third level (interactive), and the fourth level (ignorable). It should be understood that the present disclosure has no special restrictions on the naming method of each level and the message level definition method. The specific correspondence between the subscription level and the message identifier of the subscription level is explained below.

The method for the terminal to determine the target level in the above-mentioned preset subscription levels based on its own status information may be to determine whether a preset condition is met (each subscription level has a preset satisfaction condition). For example, each subscription level has a corresponding screen state, power state, network state, etc., and at least one satisfaction condition (for example, if the screen state is bright, it is the first level). If the preset condition is met, the subscription level is determined as the target level.

The method for the terminal to determine the target level in the above-mentioned preset subscription levels based on its own status information can also be to determine whether the preset corresponding relationship is satisfied (each subscription level has a preset corresponding relationship). For example, each subscription level has at least one corresponding relationship among the screen status, power status and network status (for example, the power status greater than 60% is the first level). If the preset corresponding relationship is satisfied, the subscription level is determined as the target level. The specific setting of the preset corresponding relationship is not limited here.

The terminal sends a first request to the subscription platform according to the determined target level, and the first request carries the attribute information of the message that the terminal wants to subscribe to. The attribute information may include: at least one of the target level and the message identifier corresponding to the target level. When the attribute information is the target level, the target level is sent directly to the subscription platform, and the subscription platform determines the type of subscription message based on the level and updates the subscription relationship (that is, the subscription platform knows the correspondence between the level and the message type maintained by itself). When the attribute information is the message identifier of the target level, the subscription platform can update the subscription relationship according to the message identifier. Among them, the message identifier can be understood as the message name. When the attribute information is the target level and the message identifier corresponding to the target level, the first request can be sent using any of the above methods, or the first request can be sent in combination, which is not limited here.

Exemplarily, in the disclosed embodiment, after initialization, the terminal can establish a secure communication protocol with the subscription platform, can use encryption technology to ensure the confidentiality of communication, establish a continuous and stable message subscription channel, and set up a regular heartbeat detection mechanism. Continuously monitor its own status and send a subscription request to the subscription platform based on the status. Among them, encryption technology can ensure the security of messages, including but not limited to at least one of the following: asymmetric encryption, Advanced Encryption Standard encryption (Advanced Encryption Standard, AES). The channel for message subscription is a real-time communication channel and always exists. As long as the user terminal is online, message subscription can be performed in real time. The heartbeat detection mechanism can ensure the validity of the channel between the terminal and the subscription platform. In this way, the terminal continuously monitors its own status and completes the sending of subscription requests according to the message subscription channel.

As described above, the terminal can determine the target level based on the status information and send a first request to the subscription platform. The first request carries attribute information including the target level and the message identifier corresponding to the target level. The corresponding relationship between the target level and the message identifier is specifically described below.

As follows, the message identifiers corresponding to the target levels include:

Message identifiers in the first set; wherein the first set is a message set corresponding to the target level;

Message identifiers in the second set; wherein the second set is a set of messages corresponding to other subscription levels whose importance is higher than the target level;

In the embodiment of the present disclosure, the message identifiers corresponding to the target level include message identifiers of a first set and message identifiers of a second set.

The first set is the message set corresponding to the target level. The target level is the level that the user is currently following or subscribing to. This set contains all message identifiers belonging to this level. The message identifier can be understood as the message name.

The second set is a message set corresponding to other subscription levels with a higher degree of importance than the target level, and the set includes all message identifiers of other subscription levels with a higher degree of importance than the target level. Among them, the other subscription levels can be one or more, so that the second set can also be one or more. For example, if the target level is the second level (general message layer), then the second set will include all message identifiers belonging to the first level (critical message layer).

In a possible embodiment, the subscription levels, in descending order of importance, include at least one of the following: a first level, a second level, a third level, and a fourth level;

Among them, the first level corresponds to the subscription messages of the key message layer;

The second level corresponds to subscription messages at the general message layer;

The third level corresponds to subscription messages at the interactive messaging layer;

The fourth level corresponds to subscription messages that ignore the message layer.

The subscription levels may be arranged in descending order of importance, and may include but are not limited to: level 1, level 2, level 3, and level 4. Each subscription level corresponds to a message set, which includes all message identifiers belonging to the level.

Specifically, the first level (critical message layer): this level corresponds to the subscription messages of the critical message layer. These messages have the highest importance and priority and require immediate attention and processing. The second level (general message layer): this level corresponds to the subscription messages of the general message layer. The importance of these messages is lower than the first level, but still needs to be noticed and processed by the user. The third level (interactive message layer): this level corresponds to the subscription messages of the interactive message layer. These messages can be interactive information between users, or information that requires user participation or feedback. The fourth level (ignorable message layer): this level corresponds to the subscription messages of the ignorable message layer. These messages are of the lowest importance, and users can selectively ignore them.

Exemplarily, in the disclosed embodiment, the subscription message corresponding to level 1 (key message layer, i.e., the first level) may include, but is not limited to, at least one of the following: key operations of the intercom function, speech control, calling and hanging up, and broadcasting messages, etc., which are critical to the business process. The subscription message corresponding to level 2 (general message layer, i.e., the second level) may include, but is not limited to, at least one of the following: daily operations such as the creation and disbanding of groups and the setting of intercom duration, which are less important but still critical to the normal operation of the business. The subscription message corresponding to level 3 (interface interaction message layer, i.e., the third level) may include, but is not limited to, at least one of the following: operations related to interface interaction such as adding and deleting members, instant messaging (IM messages), and the number of channels, which are basic notifications for interaction between users and the system. The subscription message corresponding to level 4 (temporarily ignorable message layer, i.e., the fourth level) may include, but is not limited to, at least one of the following: changes in the number of members online, group attribute modifications (such as name changes), group owner transfers, etc. Messages at this level are relatively minor, and users can selectively ignore them in specific situations.

As described above, the terminal can determine the target level currently corresponding to the terminal in the preset subscription level according to its own state information, and send a first request to the subscription platform to subscribe to the message. The following will specifically describe how the terminal determines the target level in the preset subscription level based on the state information.

As follows, when the status information of the terminal is the screen status, the method for the terminal to determine the target level currently corresponding to the terminal in the preset subscription level based on the status information includes:

When the screen state is the screen-off state, determining the target level to be the first level;

or,

When the screen state is the bright screen state, the target level is determined to be the third level.

In the disclosed embodiment, the terminal status information is the screen status, including the screen off status and the screen on status. Specifically, the terminal can continuously monitor the screen status (for example, a monitoring process can be created to implement continuous monitoring of the screen status) to determine whether its screen status is the screen on status.

When the screen state is the screen-off state (the current screen is off or in sleep state), the current target level is determined to be the first level. When the target level is the first level, there is no message set of other subscription levels that is more important than the current target level, which means that only the first level messages can be subscribed in the screen-off state. When the screen state is the screen-on state (the current screen is on), the current target level is determined to be the third level. When the target level is the third level, in addition to the message set of this level, there are also the second level and/or the first level that are more important than the current level, which means that in the screen-on state, in addition to the messages of the target level of the third level that can be subscribed, you can also subscribe to the messages corresponding to the second level and/or the first level.

Of course, the current screen state of the terminal may also change from the off-screen state to the bright-screen state. When the current screen state of the terminal changes from the off-screen state to the bright-screen state, the method for determining the target level includes:

Sending a second request to the subscription platform, the second request is used to request the subscription platform to feedback unsubscribed messages during the screen-off state; the unsubscribed messages include: second-level and/or third-level messages;

A second message is received from the subscription platform.

In the disclosed embodiment, when the screen state of the terminal changes from the screen-off state to the screen-on state, the terminal will send a second request to the subscription platform. The purpose of this request is to obtain messages that the user has not subscribed to but belong to the second level and/or the third level during the period when the device is in the screen-off state. Then, the second message sent by the subscription platform is received to fully understand the messages that are missed when the screen state changes, thereby ensuring the integrity of the data. It should be noted that when the terminal receives the second message sent by the subscription platform, it can be sent together with the first message (the second message is carried in the first message), or the second message can be sent separately.

For example, in the disclosed embodiment, when the terminal status information is the screen status, the notification of the screen status can be monitored, and when the screen off notification is received, the subscription of non-first-level messages is cancelled to reduce the network burden. When the screen is on, the first-level and second-level messages are subscribed, and the second-level messages that are not subscribed during the screen off period and the third-level messages of the current page are actively obtained to ensure the real-time and integrity of the information.

As follows, when the status information of the terminal is the power status, the method for the terminal to determine the target level currently corresponding to the terminal in the preset subscription level based on the status information includes:

When the power state is insufficient, determining the target level to be the first level;

or,

When the power state is sufficient, the target level is determined to be the fourth level.

In another embodiment of the present disclosure, the status information of the terminal is the power status, including a sufficient status and an insufficient status. Specifically, the power status of the terminal can be represented by the current remaining power or percentage of the terminal, and the terminal can obtain these data to determine its own power status. Exemplarily, when the remaining power or percentage is greater than a preset threshold, it is determined that the current power status of the terminal is a sufficient state; when the remaining power or percentage is less than the preset threshold, it is determined that the current power status of the terminal is an insufficient state. The preset threshold can be customized, for example, 50%, 80%, etc., without exhaustive enumeration.

When the battery status is insufficient, the current target level is determined to be the first level. When the target level is the first level, there is no message set of other subscription levels with a greater importance than the current target level, which means that in the insufficient state, only the first level messages can be subscribed. When the battery status is sufficient, the current target level is determined to be the fourth level. When the target level is the fourth level, in addition to the message set of this level, there are also the third level, the second level and the first level with a higher importance than the current level. This means that in the sufficient state, in addition to the messages of the target level of the fourth level, you can also subscribe to at least one message of the third level, the second level and the first level.

As follows, when the status information of the terminal is a network status, the method for the terminal to determine the target level currently corresponding to the terminal in the preset subscription level based on the status information includes:

When the network state is stable, the target level is determined to be the first level;

or,

When the network state is an unstable state, the target level is determined to be the fourth level.

In another embodiment of the present disclosure, the status information of the terminal is the network status, which may include a stable state and an unstable state. The network status of the terminal can be represented by the current signal strength of the terminal, and the terminal can obtain these data to determine its own network status. Exemplarily, when the signal strength is greater than a preset threshold, the current network status is determined to be a stable state; when the signal strength is less than the preset threshold, the current network status is determined to be an unstable state. The preset threshold can be customized, for example, 90 milliwatt decibels, 120 milliwatt decibels, etc., which are not exhaustive here.

When the network status is unstable (the current network is unstable or there is no network, etc.), the current target level will be determined to be the first level. When the target level is the first level, there is no message set of other subscription levels with an importance greater than the current target level, which means that the current page status cannot be loaded and only the first level messages can be subscribed. When the network status is stable (the current network is stable or the network is good, etc.), the current target level will be determined to be the fourth level. When the target level is the fourth level, in addition to the message set of this level, there are also the third level, the second level and the first level with an importance higher than the current level, which means that in sufficient state, in addition to the messages of the target level of the fourth level, you can also subscribe to at least one message of the third level, the second level and the first level.

Exemplarily, in an embodiment of the present disclosure, the status information of the terminal may be screen status, power status, and network status. At least one of the screen status, power status, and network status may be judged to determine the target level and subscribe to messages.

As shown in FIG3 , specifically, the terminal can first be initialized, establish a message subscription channel with the subscription server (subscription platform), and subscribe to the first-level message. Then monitor its own screen on/off notification (screen status) to determine whether the screen is off. If the screen is off, directly cancel other subscriptions and subscribe to only the first-level message; if the screen is not off (on), you can subscribe to the second-level message and pull other messages during the screen off period. Next, monitor page changes to determine whether it is on the page (that is, determine whether a page jump occurs and whether it is still on the current page). If it jumps to another page, cancel the subscription to the third-level message; if it is still on the current page, you can subscribe to the third-level message. Finally, monitor the power status or network status to determine whether it is sufficient. If it is sufficient, subscribe to the fourth-level message; if it is insufficient, cancel the subscription to the fourth-level message. In the above, the terminal can intelligently choose whether to subscribe to the fourth-level message according to the screen status and power status. When the power is sufficient and the network is stable, subscribe to the fourth-level message to ensure that the user obtains all relevant information. On the contrary, when resources are limited, cancel the subscription to the fourth-level message to save network resources.

It should be noted that the first request mentioned in any of the above embodiments is used to request subscription to obtain the first message.

Based on the above embodiment, further, the method also includes: the terminal can send a third request to the subscription platform. The third request can be used to request to unsubscribe from a third message, and the third message can be understood as any subscribed message. In an exemplary embodiment, the third message can be specifically: a subscribed message that does not match the status information. That is, the terminal can cancel the subscription message according to its own status information, saving the waste of network resources.

In the embodiment of the present disclosure, the terminal may send a first request for subscribing to information and also send a third request for unsubscribing from information. In this way, it is not necessary to repeatedly subscribe to messages that have already been subscribed. Thus, the information carried in any request may not be all the information to be subscribed or unsubscribed, which saves the waste of network resources and improves the processing efficiency.

In this application, in addition to providing the above-mentioned terminal-side message processing method, a subscription platform message processing method is also provided. The subscription platform message processing is mainly capable of efficient storage and calculation of subscription relationships, which is described in detail below.

The following is a detailed description of how the subscription platform maintains the subscription relationship:

The subscription platform can maintain the subscription relationship. The subscription platform can maintain the subscription relationship in the form of a bitmap; wherein the subscription relationship is stored with the user ID of any first user as the key and the user ID of the second user as the value; wherein the first user and the second user have a subscription relationship; wherein the subscription relationship includes: a subscriber relationship and a subscribed relationship.

In the disclosed embodiment, the subscription platform may maintain subscription relationships in the form of a bitmap, which is an efficient data structure choice, especially when dealing with a large number of users and subscription relationships. The bitmap allows a Boolean value (which may be a relationship that exists or does not exist) to be represented by a single bit. Among them, the subscription relationship includes a subscriber relationship and a subscribed relationship. The subscriber relationship includes at least: the relationship between a "subscriber" and "each subscriber subscribed by the subscriber", that is, the relationship between each subscriber and its subscriber. The subscriber relationship includes at least: the relationship between a "subscriber" and "each subscriber who subscribes to the subscriber", that is, the relationship between each subscriber and its subscriber.

Specifically, the subscription platform can maintain a bitmap for each first user (subscriber), in which each bit can be used to represent a subscription relationship, representing a subscription relationship between a first user (subscriber) and a second user (subscriber). If the first user subscribes to the second user, the corresponding bit will be set to 1 (indicating the existence of a subscription relationship). If the first user does not subscribe to the second user, the corresponding bit will be set to 0 (indicating the non-existence of a subscription relationship). The user ID of the first user is used as the key (Key) to quickly retrieve the corresponding bitmap. The bitmap is associated with the key as a value (Value), storing the subscription status of the first user for all potential subscribers.

For example, the following table shows:

Subscriber X Subscriber Y Subscriber Z Subscriber A 1 1 0 Subscriber B 0 1 1 Subscriber C 1 0 0

Table 1

Table 1 shows the subscriber set, which can be understood as a concrete representation of the subscription relationship in the bitmap. From Table 1, we can see that Subscriber A: [Subscriber X, Subscriber Y]; Subscriber B: [Subscriber Y, Subscriber Z]; Subscriber C: [Subscriber X]. Table 1 shows that the subscriber relationship set contains the relationship mapping between each subscriber and the subscribers it subscribes to.

The subscription platform can maintain a bitmap for each second user (subscriber), where each bit can be used to represent a subscription relationship, representing a subscription relationship between a second user (subscriber) and a first user (subscriber). If the second user is subscribed by the first user, the corresponding bit will be set to 1 (indicating the existence of a subscription relationship). If the second user is not subscribed by the first user, the corresponding bit will be set to 0 (indicating the non-existence of a subscription relationship). The user ID of the second user is used as the key (Key) to quickly retrieve the corresponding bitmap. The bitmap is associated with the key as a value (Value), storing the subscription status of the second user by all subscribers.

For example, as shown in Table 2:

Subscriber A Subscriber B Subscriber C Subscriber X 1 0 1 Subscriber Y 1 1 0 Subscriber Z 0 1 0

Table 2

Table 2 shows the set of subscribers, which can be understood as a concrete representation of the subscription relationship in the bitmap. From Table 2, we can see that Subscriber X: [Subscriber A, Subscriber C]; Subscriber Y: [Subscriber A, Subscriber B]; Subscriber Z: [Subscriber B]. Table 2 shows that the subscription relationship set contains the relationship mapping between each subscriber and the subscribers who subscribe to them.

It should be noted that Table 1 and Table 2 of the subscription platform can be stored separately or stored together in a bitmap. The storage method of Table 1 and Table 2 is limited here.

As described above, the subscription platform can use the bitmap format to efficiently store the subscription relationship. The following will specifically describe how the subscription platform updates the subscription relationship.

As follows, how the subscription platform updates the maintained subscription relationship according to the first request sent by the terminal is specifically described, and the method includes:

Based on the first request, determining a third user corresponding to the first request; the third user is a subscription object indicated by the first request;

Establishing a subscription relationship between a first user and a third user corresponding to the terminal; wherein the subscription relationship includes: a subscriber relationship and a subscribed relationship;

Store subscription relationships in the subscription platform.

In the disclosed embodiment, after receiving the first request, the subscription platform can first parse and identify the third user corresponding to the first request. The third user is the subscription object specified by the first request. The information for specifically identifying the first request can be an identifier for identifying the third user (subscriber). Next, the subscription platform can also perform identity authentication of the terminal that initiates the request to ensure the legitimacy of the subscription operation. Then, after verification, the subscription platform can establish a subscription relationship between the terminal (or subscriber) and the third user (subscriber) according to the request content. This step may include recording the identifiers of both parties, the level of subscription, subscription conditions, target level and other information. Finally, the established subscription relationship can also be stored in the database or subscription management system of the subscription platform. This may include all key information such as the subscriber and subscriber identifiers, subscription identifiers, subscription levels, subscription conditions, timestamps, etc., to ensure that the relationship can be queried, updated and managed.

It should be noted that the subscription types of the present application may include contact subscription, enterprise subscription and member subscription. The terminal may selectively send a first request to the subscription platform to determine the third user according to the different subscription types. The terminal may select different network subscription interface types to subscribe to different messages.

The following specifically describes how the subscription platform determines the third user corresponding to the first request according to the first request for different subscription interface types.

According to an embodiment of the present disclosure, based on the first request, a method for a subscription platform to determine a third user corresponding to the first request includes:

Based on the subscription type of the first request, obtain a contact set corresponding to the subscription type;

Determining a third user based on the contact set;

The subscription type includes at least one of the following: contact subscription, enterprise subscription, and member subscription.

In the disclosed embodiment, the subscription platform may parse the subscription type in the first request according to the received first request. The subscription type includes but is not limited to at least one of the following: contact subscription, enterprise subscription, and member subscription. Then, the subscription platform may obtain the contact set according to the subscription type, which may be obtained by at least one of calling an application program interface and querying a database, and the method of obtaining the contact set is not limited here. Then, the third user of the first request is determined in the contact set.

Specifically, for contact subscription: query the contact list. This can query the contact list based on the information in the first request (such as the target user ID, search conditions, etc.) to obtain the query results. From the query results, determine the third user corresponding to the first request (i.e., the subscribed contact). For enterprise subscription: the subscription platform can query the enterprise list based on the received enterprise subscription request. This can query the enterprise list based on the information in the first request (such as search conditions such as enterprise member ID). From the query results, the system determines the enterprise corresponding to the first request as the third user (i.e., the subscribed enterprise). For member subscription: the subscription platform can query the member list based on the received member subscription request to obtain the query results. Members can refer to members of a team, group or community. From the query results, determine the member corresponding to the first request as the third user (i.e., the subscribed member).

Exemplarily, the steps of contact subscription are shown in FIG4 below: a. The terminal side selects the subscription contact; b. The subscription platform side queries the contact list in the database; c. The subscription platform side updates the contact subscription relationship; d. The subscription platform side updates the contact subscription relationship.

Exemplarily, the steps of enterprise subscription are shown in Figure 5 below: a. The terminal side selects the subscription enterprise; b. The subscription platform side queries the enterprise member list in the database; c. The subscription platform side updates the enterprise member subscription relationship; d. The subscription platform side updates the enterprise member subscription relationship.

Exemplarily, the steps of member subscription are shown in Figure 6 below: a. The terminal side selects the subscription member; b. The subscription platform side subscribes according to the provided member ID; c. The subscription platform side updates the member subscription relationship; d. The subscription platform side updates the member subscription relationship.

In the above, the subscription platform can determine the third user of the request according to the first request sent by the terminal, establish and store the subscription relationship between the first user corresponding to the terminal and the third user. The following specifically introduces the method for the subscription platform to send the first message to the target terminal using the above subscription relationship.

As follows, according to an embodiment of the present disclosure, a method for a subscription platform to send a first message to a target terminal based on a subscription relationship includes:

Based on the subscription relationship, determining a target terminal corresponding to the first message;

Get the target level currently corresponding to each target terminal;

When the first message belongs to the target level, the first message is sent to the target terminal.

In the disclosed embodiment, the subscription platform may first parse the first message and query the subscription relationship. These subscription relationships may be stored in a database and cached in a storage system. Based on the queried subscription relationship, determine which terminals the first message should be sent to. Then, for each determined target terminal, the subscription platform may obtain the target level currently corresponding to the terminal user. Among them, the acquisition method may be obtained by real-time communication or by reading the cache, and the specific acquisition method is not limited here. Then, the first message is compared with the target level corresponding to each target terminal. This can be achieved by comparing at least one method such as numbers, strings or other identifiers. If the first message belongs to the target level of the target terminal (that is, the user wants to receive messages of this level), the first message is sent to the target terminal. The sending method may be specifically set by the type of terminal and the user's preference.

It should be noted that the target level can be determined by the terminal itself based on the status information sent, or by the subscription platform based on the status information sent by the terminal. The following specifically describes the method for the subscription platform to determine the target level.

The subscription platform determines the target level by:

Based on the status message carried in the first request, determining a target level currently corresponding to the terminal in a preset subscription level; the subscription level is used to indicate the importance of the subscription message;

Cache or update the target level.

In an embodiment of the present disclosure, when the subscription platform receives the first request, it can parse and obtain the status information of the request. Among them, the status information may include but is not limited to at least one of the following: screen status, power status and network status. Then, based on the correspondence between the parsed status message and the preset subscription level, determine the target level currently corresponding to the terminal. Finally, the subscription platform can check whether the target level of the terminal has been cached. This can be achieved by querying at least one of the local cache, database or remote service. If cached: compare whether the target level in the cache is the same as the target level calculated based on the current status message. If the same, no further operation is required; if different, the cache needs to be updated. If not cached or needs to be updated: cache the newly calculated target level. The location and method of the cache depends on the architecture and performance requirements of the system, and is not limited here.

It should be noted that the specific division of target levels has been explained on the terminal side mentioned above. Please refer to the previous text for details and will not be repeated here.

The present disclosure also provides a message processing device. FIG7 is a structural block diagram of a message processing device provided by an embodiment of the present disclosure. As shown in FIG7 , the message processing device 700 includes:

The acquisition unit 701 is used to acquire the current status information of the terminal.

The sending unit 702 is used to send a first request to the subscription platform based on the state information; the first request carries the state information or attribute information of the subscription message.

The receiving unit 703 is configured to receive a first message from a subscription platform.

In an exemplary embodiment, the status information includes at least one of the following: screen status, battery status, and network status.

In an exemplary embodiment, based on the status information, a first request is sent to a subscription platform, including: based on the status information, determining a target level currently corresponding to the terminal in a preset subscription level; the subscription level is used to indicate the importance of the subscription message; a first request is sent to the subscription platform, the first request carrying attribute information of the subscription message; the attribute information includes at least one of the following: a target level, a message identifier corresponding to the target level.

In an exemplary embodiment, the message identifiers corresponding to the target level include: message identifiers in a first set; wherein the first set is a message set corresponding to the target level; message identifiers in a second set; wherein the second set is a message set corresponding to other subscription levels whose importance is higher than the target level; wherein, sorted in descending order of importance, the subscription levels include at least one of the following: first level, second level, third level, fourth level; wherein the first level corresponds to subscription messages of a critical message layer; the second level corresponds to subscription messages of a general message layer; the third level corresponds to subscription messages of an interactive message layer; and the fourth level corresponds to subscription messages of an ignorable message layer.

In an exemplary embodiment, based on the status information, the target level currently corresponding to the terminal is determined in the preset subscription level, including: when the screen status is the screen-off state, determining the target level to be the first level; or, when the screen status is the screen-on state, determining the target level to be the third level.

In an exemplary embodiment, when the current screen state of the terminal changes from the screen-off state to the screen-on state, the method also includes: sending a second request to the subscription platform, the second request is used to request the subscription platform to feedback unsubscribed messages during the screen-off state; the unsubscribed messages include: second-level and/or third-level messages; receiving a second message from the subscription platform.

In an exemplary embodiment, the first request is used to request subscription to a first message; and/or the third request is used to request unsubscription to a third message, where the third message is a subscribed message that does not match the status information.

The present disclosure also provides a message processing device. FIG8 is a structural block diagram of a message processing device provided by an embodiment of the present disclosure. As shown in FIG8 , the message processing device 800 includes:

The receiving unit 801 is configured to receive a first request from a terminal; the first request carries the state information of the terminal or the attribute information of a subscription message.

The updating unit 802 is configured to update the subscription relationship maintained in the subscription platform based on the first request.

The sending unit 803 is configured to send the first message to the target terminal based on the subscription relationship when any first message is received.

In an exemplary embodiment, the method also includes: maintaining a subscription relationship in a bitmap form; wherein the subscription relationship is stored using a user identifier of any first user as a key and a user identifier of a second user as a value; wherein the first user and the second user have a subscription relationship; wherein the subscription relationship includes: a subscriber relationship and a subscribed relationship.

In an exemplary embodiment, based on a first request, a subscription relationship maintained in a subscription platform is updated, including: based on the first request, determining a third user corresponding to the first request; the third user is the subscription object indicated by the first request; establishing a subscription relationship between the first user corresponding to the terminal and the third user; wherein the subscription relationship includes: a subscriber relationship and a subscribed relationship; and storing the subscription relationship in the subscription platform.

In an exemplary embodiment, based on the first request, determining the third user corresponding to the first request includes: based on the subscription type of the first request, obtaining a contact set corresponding to the subscription type; based on the contact set, determining the third user; wherein the subscription type includes at least one of the following: contact subscription, enterprise subscription, and member subscription.

In an exemplary embodiment, sending a first message to a target terminal based on a subscription relationship includes: determining a target terminal corresponding to the first message based on the subscription relationship; obtaining a target level currently corresponding to each target terminal; and sending the first message to the target terminal when the first message belongs to the target level.

In an exemplary embodiment, the method further includes: determining a target level currently corresponding to the terminal in a preset subscription level based on a status message carried in the first request; the subscription level is used to indicate the importance of the subscription message; and caching or updating the target level.

In an exemplary embodiment, based on the status message carried in the first request, the target level currently corresponding to the terminal is determined in the preset subscription level, including: when the screen status carried in the first request is the screen-off state, the target level is determined to be the first level; or, when the screen status carried in the first request is the screen-on state, the target level is determined to be the third level.

In an exemplary embodiment, when the screen state in the first request changes from the screen-off state to the screen-on state, the method also includes: receiving a second request from the terminal, the second request is used to request feedback of unsubscribed messages during the screen-off state; the unsubscribed messages include: second-level and/or third-level messages; sending a second message to the terminal; the second message carries the unsubscribed messages during the screen-off state.

FIG9 is a hardware block diagram of an electronic device provided by an embodiment of the present disclosure. The electronic device 900 according to an embodiment of the present disclosure includes at least a processor; and a memory for storing computer-readable instructions. When the computer-readable instructions are loaded and executed by the processor, the processor executes the message processing method described in any of the foregoing embodiments of the present disclosure.

The electronic device 900 shown in FIG9 specifically includes: a central processing unit (CPU) 901, a graphics processing unit (GPU) 902, and a memory 903. These units are interconnected via a bus 904. The central processing unit (CPU) 901 and/or the graphics processing unit (GPU) 902 can be used as the above-mentioned processor, and the memory 903 can be used as the above-mentioned memory for storing computer-readable instructions. In addition, the electronic device 900 may also include a communication unit 905, a storage unit 906, an output unit 907, an input unit 908, and an external device 909, which are also connected to the bus 904.

FIG10 is a schematic diagram of a computer-readable storage medium provided by an embodiment of the present disclosure. As shown in FIG10 , a computer-readable storage medium 1000 according to an embodiment of the present disclosure has computer-readable instructions 1001 stored thereon. When the computer-readable instructions 1001 are executed by a processor, the message processing method described in any of the foregoing embodiments of the present disclosure described with reference to the above figures is executed. The computer-readable storage medium includes, but is not limited to, for example, volatile memory and/or non-volatile memory. Volatile memory may, for example, include random access memory (RAM) and/or cache memory (cache), etc. Non-volatile memory may, for example, include read-only memory (ROM), hard disk, flash memory, optical disk, magnetic disk, etc.

The present disclosure further provides a computer program product, including a computer program, which, when executed by a processor, implements the message processing method described in any of the foregoing embodiments of the present disclosure.

In the above, the message processing method, device, electronic device, storage medium and program product according to the embodiments of the present disclosure are described with reference to the accompanying drawings. The terminal can obtain its own status information, and the terminal can determine to send a first request to the subscription platform based on the status information. The first request information carries the status information or the attribute information of the subscription message. Finally, the terminal can receive the first message from the subscription platform. The first message can be understood as a response message to the first request. In this way, the terminal can determine which data needs to be subscribed based on its own status information, so that the terminal can dynamically adjust the data subscription and processing strategy to achieve more flexible and intelligent management, which can meet various needs and is suitable for various application scenarios. At the same time, the subscription platform no longer pushes all relevant messages (full data) to the terminal, but selectively sends subscription information according to the request sent by the terminal. In this way, the mutual cooperation between the terminal and the subscription platform solves the problem of network congestion and improves processing efficiency.

Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this disclosure.

The basic principles of the present disclosure are described above in conjunction with specific embodiments. However, it should be noted that the advantages, strengths, effects, etc. mentioned in the present disclosure are only examples and not limitations, and it cannot be considered that these advantages, strengths, effects, etc. are required by each embodiment of the present disclosure. In addition, the specific details disclosed above are only for the purpose of illustration and ease of understanding, and are not limitations. The above details do not limit the present disclosure to the necessity of adopting the above specific details to be implemented.

The block diagrams of the devices, apparatuses, equipment, and systems involved in this disclosure are only illustrative examples and are not intended to require or imply that they must be connected, arranged, and configured in the manner shown in the block diagrams. As will be appreciated by those skilled in the art, these devices, apparatuses, equipment, and systems can be connected, arranged, and configured in any manner. Words such as "including," "comprising," "having," and the like are open words, referring to "including but not limited to," and can be used interchangeably therewith. The words "or" and "and" used herein refer to the words "and/or," and can be used interchangeably therewith, unless the context clearly indicates otherwise. The word "such as" used herein refers to the phrase "such as but not limited to," and can be used interchangeably therewith.

Additionally, as used herein, "or" used in a list of items beginning with "at least one" indicates a separate list, so that, for example, a list of "at least one of A, B, or C" means A or B or C, or AB or AC or BC, or ABC (i.e., A and B and C). Furthermore, the word "exemplary" does not mean that the example described is preferred or better than other examples.

It should also be noted that in the system and method of the present disclosure, each component or each step can be decomposed and/or recombined. Such decomposition and/or recombination should be regarded as equivalent solutions of the present disclosure.

Various changes, substitutions, and modifications of the techniques described herein may be made without departing from the teachings defined by the appended claims. Furthermore, the scope of the claims of the present disclosure is not limited to the specific aspects of the processes, machines, manufactures, compositions of events, means, methods, and actions described above. Currently existing or later to be developed processes, machines, manufactures, compositions of events, means, methods, or actions that perform substantially the same functions or achieve substantially the same results as the corresponding aspects described herein may be utilized. Thus, the appended claims include such processes, machines, manufactures, compositions of events, means, methods, or actions within their scope.

The above description of the disclosed aspects is provided to enable any person skilled in the art to make or use the present disclosure. Various modifications to these aspects will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects without departing from the scope of the present disclosure. Therefore, the present disclosure is not intended to be limited to the aspects shown herein, but rather to the widest scope consistent with the principles and novel features disclosed herein.

The above description has been given for the purpose of illustration and description. In addition, this description is not intended to limit the embodiments of the present disclosure to the forms disclosed herein. Although multiple example aspects and embodiments have been discussed above, those skilled in the art will recognize certain variations, modifications, changes, additions and sub-combinations thereof.

Claims (20)

1. A message processing method, applied to a terminal, the method comprising:

acquiring current state information of the terminal;

Based on the state information, sending a first request to a subscription platform; the first request carries the state information or attribute information of subscription information;

a first message is received from the subscription platform.

2. The method of claim 1, wherein the status information comprises at least one of: screen status, power status, network status.

3. The method according to claim 1 or 2, wherein said sending a first request to a subscription platform based on said status information comprises:

Determining a target level currently corresponding to the terminal in a preset subscription level based on the state information; the subscription level is used for indicating the importance degree of the subscription message;

sending the first request to the subscription platform, wherein the first request carries attribute information of the subscription message; the attribute information includes at least one of: and the target level and the message identifier corresponding to the target level.

4. A method according to claim 3, wherein the message identification corresponding to the target level comprises:

Message identification in the first set; the first set is a message set corresponding to the target level;

message identification in the second set; the second set is a message set corresponding to other subscription levels with the importance degree higher than the target level;

Wherein, the subscription levels sequentially comprise at least one of the following according to the descending order of importance degrees: a first level, a second level, a third level, a fourth level;

wherein the first level corresponds to a subscription message of a key message layer;

the second level corresponds to subscription messages of a general message layer;

the third level corresponds to a subscription message of the interactive message layer;

The fourth level corresponds to subscription messages of the negligible message layer.

5. The method according to claim 1, wherein determining, based on the status information, a target level currently corresponding to the terminal among preset subscription levels includes:

when the screen state is the screen-off state, determining that the target level is a first level;

Or alternatively

And when the screen state is a bright screen state, determining that the target level is a third level.

6. The method of claim 5, wherein when the current screen state of the terminal is changed from a rest screen state to a bright screen state, the method further comprises:

sending a second request to the subscription platform, wherein the second request is used for requesting the subscription platform to feed back an unsubscribed message during a screen-off state; the unsubscribed message includes: a second level and/or third level message;

a second message is received from the subscription platform.

7. The method according to any one of claims 1 to 6, wherein,

The first request is used for requesting subscription to the first message;

And/or the number of the groups of groups,

The third request is for requesting to unsubscribe from a third message, the third message being a subscribed message that does not correspond to the status information.

8. A message processing method, applied to a subscription platform, the method comprising:

Receiving a first request from a terminal; the first request carries state information of the terminal or attribute information of subscription information;

Updating the subscription relation maintained in the subscription platform based on the first request;

and when any one first message is received, sending the first message to a target terminal based on the subscription relation.

9. The method of claim 8, wherein the method further comprises:

maintaining the subscription relationship in the form of a bitmap;

wherein, the subscription relation uses the user identification of any first user as a key and uses the user identification of the second user as a value for storage; wherein the first user and the second user have the subscription relationship;

Wherein the subscription relationship comprises: subscriber relationships with subscribed relationships.

10. The method of claim 8, wherein updating the subscription relationship maintained in the subscription platform based on the first request comprises:

Determining a third user corresponding to the first request based on the first request; the third user is a subscription object indicated by the first request;

establishing a subscription relation between a first user corresponding to the terminal and the third user; wherein the subscription relationship comprises: subscriber relationship and subscribed relationship;

The subscription relationship is stored in the subscription platform.

11. The method of claim 10, wherein the determining, based on the first request, a third user to which the first request corresponds comprises:

acquiring a contact person set corresponding to a subscription type based on the subscription type of the first request;

Determining the third user based on the set of contacts;

wherein the subscription type includes at least one of: contact subscriptions, enterprise subscriptions, and member subscriptions.

12. The method according to any of claims 8-11, wherein the sending the first message to a target terminal based on the subscription relationship comprises:

determining a target terminal corresponding to the first message based on the subscription relation;

Obtaining a current corresponding target level of each target terminal;

And when the first message belongs to the target level, sending the first message to the target terminal.

13. The method according to claim 12, wherein the method further comprises:

determining a target level corresponding to the terminal currently in a preset subscription level based on the state message carried in the first request; the subscription level is used for indicating the importance degree of the subscription message;

Caching or updating the target level.

14. The method of claim 13, wherein the determining, based on the status message carried in the first request, a target level currently corresponding to the terminal in a preset subscription level includes:

When the screen state carried in the first request is a screen-off state, determining that the target level is a first level;

Or alternatively

And when the screen state carried in the first request is a bright screen state, determining that the target level is a third level.

15. The method of claim 13, wherein when the first request in-screen state is changed from an off-screen state to a bright-screen state, the method further comprises:

Receiving a second request from the terminal, wherein the second request is used for requesting to feed back an unsubscribed message during the screen-off state; the unsubscribed message includes: a second level and/or third level message;

Sending a second message to the terminal; the second message carries an unsubscribed message during the off-screen state.

16. A message processing apparatus, characterized in that it is provided in a terminal, said apparatus comprising:

The acquisition unit is used for acquiring the current state information of the terminal;

the sending unit is used for sending a first request to the subscription platform based on the state information; the first request carries the state information or attribute information of subscription information;

and the receiving unit is used for receiving the first message from the subscription platform.

17. A message processing apparatus, disposed on a subscription platform, the apparatus comprising:

A receiving unit, configured to receive a first request from a terminal; the first request carries state information of the terminal or attribute information of subscription information;

an updating unit, configured to update a subscription relationship maintained in the subscription platform based on the first request;

And the sending unit is used for sending the first message to the target terminal based on the subscription relation when any one first message is received.

18. An electronic device, comprising:

A memory for storing computer readable instructions; and

A processor for executing the computer readable instructions to cause the electronic device to perform the method of any one of claims 1-15.

19. A non-transitory computer readable storage medium storing computer readable instructions which, when executed by a processor, cause the processor to perform the method of any of claims 1-15.

20. A computer program product comprising a computer program which, when executed by a processor, implements the method of any of claims 1-15.