CN107918673B

CN107918673B - Subscription data processing method and device, storage medium and computer equipment

Info

Publication number: CN107918673B
Application number: CN201711320454.7A
Authority: CN
Inventors: 冯锋
Original assignee: Tencent Technology Shenzhen Co Ltd
Current assignee: Tencent Technology Shenzhen Co Ltd
Priority date: 2017-12-12
Filing date: 2017-12-12
Publication date: 2022-11-04
Anticipated expiration: 2037-12-12
Also published as: CN107918673A

Abstract

The invention relates to a subscription data processing method, a device, a storage medium and computer equipment, wherein the subscription data processing method comprises the following steps: receiving a subscription inquiry request corresponding to the requester identifier; responding to the subscription inquiry request, and acquiring a subscription object identifier from a subscription relation storage area; the requester identification has a subscription relation with the acquired subscription object identification; in a subscribed relation storage area, inquiring the subscribed relation of the acquired subscription object identifier to the requester identifier; and feeding back the subscription object identifier of the subscribed relation according to the requester identifier. The scheme provided by the application subscribes to the accuracy of the query.

Description

Subscription data processing method and device, storage medium and computer equipment

Technical Field

The present invention relates to the field of computer technologies, and in particular, to a subscription data processing method, device, storage medium, and computer equipment.

Background

With the development of network technology, more and more users obtain information through the internet. A user can select a target object for subscription through an internet platform, so that information about the target object is obtained. The target object here is, for example, other users or public information providers.

In the conventional technology, a computer device usually records a subscription relationship after a user performs a subscription operation. When the number of users is large or the subscription relationship of the users is complex, the problem of wrong recording of the subscription relationship is easy to occur, so that the accuracy of the obtained query result is low when the users query the subscription data.

Disclosure of Invention

Based on this, it is necessary to provide a subscription data processing method, an apparatus, a storage medium, and a computer device for solving the problem that the accuracy of the query result obtained when the user queries the subscription data is low.

A subscription data processing method, comprising:

receiving a subscription inquiry request corresponding to the requester identifier;

responding to the subscription inquiry request, and acquiring a subscription object identifier from a subscription relation storage area; the requester identification has a subscription relation with the acquired subscription object identification;

in a subscribed relation storage area, inquiring the subscribed relation of the acquired subscription object identifier to the requester identifier;

and feeding back the subscription object identifier of the subscribed relation according to the requester identifier.

A subscription data processing apparatus, comprising:

the receiving module is used for receiving a subscription inquiry request corresponding to the requester identifier;

the acquisition module is used for responding to the subscription inquiry request and acquiring the subscription object identification from the subscription relation storage area; the requester identification has a subscription relation with the acquired subscription object identification;

the query module is used for querying the subscribed relationship of the acquired subscription object identifier to the requester identifier in a subscribed relationship storage area;

and the feedback module is used for feeding back the subscription object identifier inquired about the subscribed relationship according to the requester identifier.

A computer-readable storage medium having stored thereon a computer program which, when executed by a processor, causes the processor to perform the steps of:

and feeding back and inquiring the subscription object identifier of the subscribed relationship according to the requester identifier.

A computer device comprising a memory and a processor, the memory having stored therein a computer program that, when executed by the processor, causes the processor to perform the steps of:

After the subscription query request initiated by the user is obtained, the subscription objects subscribed by the user are obtained from the subscription relation storage area, and then whether the subscription objects are subscribed by the user is queried in the subscribed relation storage area. And only when the subscription relationship of the user to the subscription object and the subscribed relationship of the subscription object to the user exist, the inquired subscription object identifier is fed back to the user, so that the accuracy of the inquiry result obtained when the user inquires the subscription data is improved.

A subscription data processing method, comprising:

receiving a subscription request corresponding to the requester identifier;

extracting a subscription object identifier pointed by the subscription request;

in a subscription relation storage area, adding a subscription relation of the requester identifier to the extracted subscription object identifier;

when the subscription relationship is successfully increased, feeding back a subscription success notification according to the requester identifier;

and in the subscribed relation storage area, adding the subscribed relation of the extracted subscription object identifier to the requester identifier.

A subscription data processing apparatus, comprising:

a receiving module, configured to receive a subscription request corresponding to a requester identifier;

the extracting module is used for extracting the subscription object identifier pointed by the subscription request;

a first adding module, configured to add a subscription relationship of the requester identifier to the extracted subscription object identifier in a subscription relationship storage area;

the feedback module is used for feeding back a subscription success notice according to the requester identifier when the subscription relationship is successfully increased;

and a second adding module, configured to add, in the subscribed relationship storage area, the subscribed relationship of the extracted subscription object identifier to the requestor identifier.

receiving a subscription request corresponding to the requester identifier;

when the subscription relationship is successfully added, feeding back a subscription success notification according to the requester identifier;

According to the subscription data processing method, the device, the storage medium and the computer equipment, after a subscription request initiated by a user is obtained, the subscription relation of the user to a subscription object is written in the subscription relation storage area, and the user is notified after the successful writing. And then writing the subscribed relation of the subscription object subscribed by the user in the subscribed relation storage area. Therefore, the perception of the user to the subscription process is improved, and the subscription relation and the subscribed relation between the user and the subscription object are stored, so that the subscription object identification existing in the subscription relation and the subscribed relation can be fed back to the user when the user performs subscription query subsequently, and the accuracy of the query result obtained when the user queries the subscription data is improved.

Drawings

FIG. 1 is a diagram of an application environment for a method of processing subscription data in one embodiment;

FIG. 2 is a flowchart illustrating a method for processing subscription data according to an embodiment;

FIG. 3 is a schematic diagram of an interface for a terminal to display identification of a subscription object according to an embodiment;

FIG. 4 is a flowchart illustrating a subscription data processing method according to another embodiment;

FIG. 5 is a diagram of the hardware architecture of a subscription data processing method in one embodiment;

FIG. 6 is a timing diagram of subscription data processing in one embodiment;

FIG. 7 is a block diagram of a subscription data processing device in one embodiment;

FIG. 8 is a block diagram of a subscription data processing device in accordance with another embodiment;

FIG. 9 is a block diagram of a subscription data processing apparatus in another embodiment;

FIG. 10 is a block diagram of a subscription data processing device in accordance with another embodiment;

FIG. 11 is a diagram of the internal structure of a computer device in one embodiment.

Detailed Description

In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

FIG. 1 is a diagram of an application environment of a method for processing subscription data in one embodiment. Referring to fig. 1, the subscription data processing method is applied to a subscription data processing system. The subscription data processing system includes a terminal 110 and a server 120. Wherein the terminal 110 and the server 120 are connected through a network. The server 120 is configured to execute the subscription data processing method. The terminal 110 may be a desktop terminal or a mobile terminal, and the mobile terminal may be at least one of a mobile phone, a tablet computer, a notebook computer, and the like. The server 120 may be an independent server, or may be a server cluster formed by a plurality of independent servers.

Fig. 2 is a flowchart illustrating a subscription data processing method according to an embodiment. The embodiment is mainly illustrated by applying the method to the server 120 in fig. 1. Referring to fig. 2, the subscription data processing method specifically includes the following steps:

s202, receiving a subscription inquiry request corresponding to the requester identifier.

The requester identifier may be a character string including at least one of a number, a letter, and a symbol, and uniquely identifies a requester. The requestor is the user who initiated the subscription query request. The subscription query request is a request for querying subscription data. The subscription data comprises subscription objects and subscription object association data. The subscription object association data may include basic information of the subscription object or public information published by the subscription object, etc. A subscription object is an object that is subscribed to.

In one embodiment, after logging in through the requester identifier, the terminal may obtain a trigger instruction, and send a subscription query request to the server according to the trigger instruction, so that the server receives the subscription query request corresponding to the requester identifier. The trigger instruction is an instruction for triggering the subscription inquiry request, and can be triggered in a plurality of trigger modes such as touch operation, pressing of a physical key, a voice control mode or equipment shaking operation.

In one embodiment, the terminal may run an application program, the application program may provide an operation entry for subscribing to the query request, the application program may detect a trigger operation on the operation entry after logging in through the requester identifier, trigger a corresponding trigger instruction according to the detected trigger operation, send the subscription query request to the server according to the trigger instruction, and the server thereby receives the subscription query request corresponding to the requester identifier. The operation entry may be an icon, a text link, a virtual button, or the like.

S204, responding to the subscription inquiry request, acquiring a subscription object identifier from the subscription relation storage area; the requester identity has a subscription relationship with the acquired subscription object identity.

The subscription relation storage area is a storage space for storing subscription relations. A subscription relationship is a one-way correspondence that is pointed to by a subscriber identity to a subscribed identity.

When the server is an independent server, the subscription relationship storage area may be a part of the storage space divided from the storage space of the server itself. The server further stores the subscription relationship in the divided part of the storage space.

When the server is a server cluster formed by a plurality of independent servers, the subscription relation storage area may be a part of a storage space divided from a storage space of a local server that receives the subscription inquiry request, or may be a storage space of another server different from the server that receives the subscription inquiry request. At this time, the server cluster includes at least two independent servers, a logic server and a subscription relationship storage server. The logic server is used for receiving a subscription inquiry request which is sent by the terminal and corresponds to the requester identifier, and continuing subsequent operation. The subscription relation storage server is used for storing the subscription relation.

In one embodiment, the subscription relationship may be stored by a relational database, that is, the subscription relationship storage area may be a relational database, or the subscription relationship storage server may be a relational database server. The relational database stores data in the form of rows and columns, and readability is high. The data rows and the data columns form a data table, and the data tables form a database.

For example, the subscription relationships may be stored in a table structure as described in the following table one.

Table one:

specifically, after receiving the subscription query request, the server takes a requestor identifier corresponding to the subscription query request as a subscriber identifier, and reads a subscribed identifier identified and subscribed by the requesting method, that is, a subscription object identifier, from the subscription relationship storage area. It is to be understood that the requestor identification herein has a subscription relationship with respect to the acquired subscription object identification.

When the server is a server cluster formed by a plurality of independent servers, the logic server receives the subscription query request and then sends a requester identifier corresponding to the subscription query request as a subscriber identifier to the subscription relation storage server. The subscription relation storage server reads the subscribed identifier identified by the request method, namely the subscribed object identifier, and feeds back the subscribed identifier to the logic server.

S206, in the subscribed relation storage area, inquiring the subscribed relation of the acquired subscription object identifier to the requester identifier.

The subscribed relation storage area is a storage space for storing the subscribed relation. The subscribed relationship is a one-way correspondence directed by the subscribed identity to the subscriber identity.

When the server is an independent server, the subscribed relationship storage area may be a part of the storage space divided from the storage space of the server itself. The server further stores the subscribed relationship in the divided part of the storage space. The subscription relation storage area and the subscribed relation storage area may be independent storage areas.

When the server is a server cluster formed by a plurality of independent servers, the subscribed relation storage area may be a part of a storage space divided from a storage space of a local server that receives the subscription query request, or may be a storage space of another server different from the server that receives the subscription query request. At this time, the server cluster includes at least three independent servers, a logic server, a subscription relationship storage server, and a subscribed relationship storage server. The subscribed relation storage server is used for storing the subscribed relation.

In one embodiment, the subscribed relationship may also be stored by a relational database, that is, the subscribed relationship storage area may be a relational database, or the subscribed relationship storage server may be a relational database server.

Specifically, after acquiring the subscription object identifier subscribed by the requester identifier, the server queries, in the subscribed relationship storage area, whether the acquired subscription object identifier has a subscribed relationship with the requester identifier. When the server inquires that the acquired subscription object identifier has a subscribed relationship with the requester identifier, the server judges that the requester identifier and the subscription object identifier satisfy a bidirectional corresponding relationship, and further judges that the subscription relationship of the requester identifier to the acquired subscription object identifier is correct data. When the server does not inquire that the acquired subscription object identifier has a subscribed relationship with the requester identifier, judging that the requester identifier and the subscription object identifier do not satisfy the bidirectional corresponding relationship, and further judging that the subscription relationship of the requester identifier to the acquired subscription object identifier is dirty data. The bidirectional corresponding relation identifies the subscription relation of the subscriber to the subscribed and the subscribed relation of the subscribed to the subscriber exists.

When the server is a server cluster formed by a plurality of independent servers, the logic server sends the subscription object identifier to the subscribed relation storage server after receiving the subscription object identifier fed back by the subscribed relation storage server, so as to obtain a subscriber identifier set corresponding to each subscription object identifier returned by the subscribed relation server, wherein each subscription object identifier has a subscribed relation with the subscriber identifier in the corresponding subscriber identifier set. The logic server further queries, for each subscription object identifier, whether the corresponding subscriber identifier set contains the requester identifier. And if so, judging that the subscription relation of the requester identifier to the acquired subscription object identifier is correct data. If not, the subscription relation of the requester identifier to the acquired subscription object identifier is judged to be dirty data.

For example, assuming that the requestor identifier corresponding to the subscription query request is ID1, the subscription object identifiers ID2 and ID3 are acquired from the subscription relationship storage area. That is, ID1 has a subscription relationship for both ID2 and ID3. From the subscribed relationship storage area, it is queried that ID2 is subscribed by ID1 and ID4, and ID3 is subscribed by ID4 and ID 5. At this time, if ID2 has both a subscription relationship and a subscribed relationship with ID1, it is determined to be correct data. If ID3 has only a subscription relationship with ID1 and has no subscribed relationship, it is determined to be dirty data.

And S208, feeding back and inquiring the subscription object identification of the subscribed relationship according to the requester identification.

Specifically, after querying that a subscription object identifier having both a subscription relationship and a subscribed relationship with the requester identifier exists, the server feeds back the subscription object identifier to the terminal corresponding to the requester identifier.

And after receiving the subscription object identification fed back by the server, the terminal can display the received subscription object identification. Such as by listing the subscription object identifications, etc. For example, fig. 3 is a schematic diagram illustrating an interface for a terminal to expose a subscription object identifier in one embodiment. Referring to fig. 3, the interface includes a subscription object identification 310.

According to the subscription data processing method, after a subscription query request initiated by a user is obtained, subscription objects subscribed by the user are obtained from the subscription relation storage area, and then whether the subscription objects are subscribed by the user is queried in the subscribed relation storage area. And only when the subscription relationship of the user to the subscription object and the subscribed relationship of the subscription object to the user exist, the inquired subscription object identification is fed back to the user, so that the accuracy of the inquiry result obtained when the user inquires the subscription data is improved.

In one embodiment, the subscription data processing method further includes: determining an invalid subscription object identifier; the invalid subscription object identification is the subscription object identification which has a subscribed relation to the requester identification and is not inquired; canceling the feedback of the invalid subscription object identifier; in the subscription relationship storage area, the subscription relationship of the requester identifier to the failed subscription object identifier is deleted.

The invalid subscription object identifier is a subscription object identifier which does not satisfy the bidirectional corresponding relation with the requester identifier. That is, when there is only a subscription relationship between the subscription object identifier and the requester identifier, and there is no subscribed relationship, it is invalid dirty data.

Specifically, when the server does not inquire that the acquired subscription object identifier has a subscribed relationship with the requester identifier in the subscribed relationship storage area, it determines that the acquired subscription object identifier is a failed subscription object identifier, does not feed the failed subscription object identifier back to the terminal corresponding to the requester identifier, and deletes the subscription relationship of the requester identifier with respect to the failed subscription object identifier in the subscription relationship storage area, so as to ensure the accuracy of the data stored in the subscription relationship storage area.

When the server is a server cluster formed by a plurality of independent servers, after the logic server obtains a subscriber identification set corresponding to each subscription object identification returned by the subscribed relation server, for each subscription object identification, whether the corresponding subscriber identification set contains the requester identification is inquired. When inquiring that a subscriber identification set corresponding to a certain subscription object identification does not contain a requester identification, judging that the subscription object identification is a failed subscription object identification, not feeding the failed subscription object identification back to a terminal corresponding to the requester identification, informing a subscription relationship storage server, and deleting the subscription relationship of the requester identification to the failed subscription object identification so as to ensure the accuracy of data stored by the subscription relationship storage server.

In this embodiment, when only a subscription relationship exists between the requestor identifier and the subscription object identifier, but no subscribed relationship exists, the subscription relationship of the requestor identifier to the subscription object identifier in the subscription relationship storage area is deleted, so that consistency of data stored in the subscription relationship storage area and data stored in the subscribed relationship storage area is ensured.

In one embodiment, the subscription data processing method further includes: checking the check mark for the acquired subscription object identifier; when the acquired subscription object identification corresponds to the check mark, executing a step of inquiring the subscribed relation of the acquired subscription object identification to the requester identification in a subscribed relation storage area; and when the subscribed relation is inquired, deleting the check mark corresponding to the subscribed object identifier.

Wherein, the check mark is a mark for indicating that the existence of the subscribed relation needs to be checked. The check here is to check whether a subscribed relationship exists between the two identifiers in which the subscribed relationship exists.

Specifically, after acquiring the subscription object identifiers, the server traverses the subscription object identifiers, and during the traversal, checks whether the traversed subscription object identifiers correspond to check marks. When the traversed subscription object identifier corresponds to the check mark, it is determined whether the subscribed relationship between the traversed subscription object identifier and the requester identifier exists, and therefore, the step of querying the obtained subscribed relationship between the subscription object identifier and the requester identifier in the subscribed relationship storage area is performed.

Further, when the server inquires that the traversed subscription object identifier has a subscribed relationship with the requester identifier, the server determines that the subscription relationship of the requester identifier with the traversed subscription object identifier is correct, and retains the traversed subscription object identifier. At this time, if the process of checking the existence of the subscribed relationship is completed, the check mark corresponding to the subscribed object identifier may be deleted.

When the server inquires that the traversed subscription object identifier does not have the subscribed relationship with the requester identifier, it is determined that the subscription relationship of the requester identifier with the traversed subscription object identifier is wrong and needs to be deleted, that is, the subscription relationship of the requester identifier with the traversed subscription object identifier is deleted in the subscription relationship storage area.

In this embodiment, a check mark is added to the subscription relationship that needs to be checked for existence of the subscribed relationship, so that when a user performs subscription query, only the existence of the subscribed relationship needs to be checked for the subscription object identifier having the check mark, thereby greatly reducing data processing amount and improving data processing efficiency.

In one embodiment, the subscription data processing method further includes: and when the acquired subscription object identification does not correspond to the check mark, reserving the subscription object identification which does not correspond to the check mark. According to the identifier of the requester, feeding back the identifier of the subscription object queried to the subscribed relationship comprises: reserving the identification of the subscription object queried to the subscribed relationship; and after integrating the reserved subscription object identifiers, feeding back according to the identifier of the requester.

Specifically, when the subscription object identifier traversed by the server does not correspond to the check mark, it is determined whether the subscribed relationship between the traversed subscription object identifier and the requester identifier does not need to be checked, and therefore, the step of querying the subscribed relationship of the acquired subscription object identifier to the requester identifier in the subscribed relationship storage area does not need to be executed, and the traversed subscription object identifier can be retained.

It can be understood that the traversed subscription object identifier does not correspond to a check mark, which indicates that the traversed subscription object identifier has been checked in the historical checking process, and the subscription relationship is retained after the check is passed, and resources are wasted without repeated checks.

Further, the server may merge the subscription object identifier retained after the verification and the subscription object identifier retained without the verification, and feed back the merged subscription object identifier to the terminal corresponding to the requester identifier.

In this embodiment, a check mark is added to the subscription relationship that needs to be checked for existence of the subscribed relationship, so that when a user performs subscription query, the existence of the subscribed relationship is not checked for the subscription object identifier without the check mark, thereby greatly reducing the data processing amount and improving the data processing efficiency.

For example, the subscription relationships may be stored in a table structure as described in Table two below.

Table two:

subscriber identification	Identification of subscribed person	Subscription time	Check mark
				ID1	ID2	XXXXX	Is provided with
ID1	ID3	XXXXX	Is composed of
				…	…	…	…

Assuming that the requestor is identified as ID1, it can be seen from the table that ID1 has a subscription relationship with ID2 and corresponds to a check mark, that is, ID2 corresponds to a check mark. Then it is queried whether the subscribed relationship of ID2 to ID1 exists in the subscribed relationship storage area. If the subscribed relation of ID2 to ID1 exists, keeping ID2 and deleting the check mark corresponding to ID2. If the subscribed relation of ID2 to ID1 does not exist, deleting the subscribed relation of ID1 to ID2.

Meanwhile, it can be seen from the table that ID1 has a subscription relationship with ID3, and does not correspond to a check mark, that is, ID3 does not correspond to a check mark. Then it is not necessary to query whether the subscribed relation of ID3 to ID1 exists in the subscribed relation storage area, and ID3 can be directly reserved.

In one embodiment, the subscription data processing method further includes: checking the check passing mark for the acquired subscription object identifier; when the obtained subscription object identification does not correspond to the check mark, executing a step of inquiring the subscribed relation of the obtained subscription object identification to the requester identification in a subscribed relation storage area; and when the subscribed relation is inquired, adding a check passing mark for the subscribed object identifier. And when the acquired subscription object identification corresponds to the check passing mark, reserving the subscription object identification corresponding to the check passing mark. According to the identifier of the requester, the step of feeding back the identifier of the subscription object which inquires the subscribed relationship comprises the following steps: reserving the identification of the subscription object which is inquired to the subscribed relation; and after integrating the reserved subscription object identifiers, feeding back according to the identifier of the requester.

For example, the subscription relationship may be stored according to a table structure as described in table three below.

A third table:

subscriber identification	Subscriber identification	Subscription time	Verification pass flag
				ID1	ID2	XXXXX	Is provided with
ID1	ID3	XXXXX	Is free of
				…	…	…	…

Wherein, the check passing mark is a mark for indicating the existence of the completed subscribed relationship.

Assuming that the requestor ID is ID1, it can be seen from the table that ID1 has a subscription relationship with ID2 and corresponds to a pass flag, that is, ID2 corresponds to a pass flag. Then, it is not necessary to query whether the subscribed relationship of ID2 to ID1 exists in the subscribed relationship storage area, and ID2 can be directly reserved.

Meanwhile, it can be seen from the table that ID1 has a subscription relationship with ID3, and does not correspond to a check passing flag, that is, ID3 does not correspond to a check passing flag. In the subscribed relation storage area, whether the subscribed relation of ID3 to ID1 exists is queried. If the subscribed relation of ID3 to ID1 exists, keeping ID3 and adding a check passing mark for ID3. If the subscribed relation of ID3 to ID1 does not exist, the subscribed relation of ID1 to ID3 is deleted.

In this embodiment, a verification passing mark is added to the subscription relationship which has been verified and passes verification, so that when a user performs subscription query, the verified subscription object identifier is not repeatedly verified any more, data processing amount is greatly reduced, and data processing efficiency is improved.

In one embodiment, the subscription data processing method further includes: receiving a subscription request corresponding to the requester identifier; extracting a subscription object identifier pointed by the subscription request; in the subscription relation storage area, adding a subscription relation of the requester identifier to the extracted subscription object identifier; when the subscription relationship is successfully increased, feeding back a subscription success notification according to the identifier of the requester; and in the subscribed relation storage area, newly adding the subscribed relation of the extracted subscription object identifier to the requester identifier.

Wherein the subscription request is a request for subscribing to a specified subscription object. A subscription object is an object that is subscribed to. The subscription object may be a user, a subscription message provider, a group or topic, and the like.

In one embodiment, after logging in through the requester identifier, the terminal may obtain a trigger instruction, and send a subscription request to the server according to the trigger instruction, so that the server receives the subscription request corresponding to the requester identifier. The trigger instruction is an instruction for triggering the subscription request, and can be triggered in various trigger modes such as touch operation, pressing of a physical key, a voice control mode or equipment shaking operation.

In one embodiment, the terminal may run an application program, the application program may provide an operation entry for a subscription request, the application program may detect a trigger operation on the operation entry after logging in through the requester identifier, trigger a corresponding trigger instruction according to the detected trigger operation, send a subscription request to the server according to the trigger instruction, and the server thereby receives a subscription query request corresponding to the requester identifier. The operation entry can be an icon, a text link, a virtual button or the like.

Specifically, after receiving a subscription request corresponding to the requester identifier, the server extracts a subscription object identifier to which the subscription request points, and adds a subscription relationship of the requester identifier to the extracted subscription object identifier in the subscription relationship storage area. And when the subscription relationship is successfully added, feeding back a subscription success notification to the terminal corresponding to the requester identifier, and adding the subscribed relationship of the extracted subscription object identifier to the requester identifier in the subscribed relationship storage area.

When the server is a server cluster formed by a plurality of independent servers, after receiving a subscription request corresponding to the requester identifier, the logic server extracts the subscription object identifier pointed by the subscription request, and correspondingly sends the requester identifier and the extracted subscription object identifier to the subscription relation storage server, so that the subscription relation storage server adds a subscription relation of the requester identifier to the extracted subscription object identifier. And after the subscription relationship is successfully established, the subscription relationship storage server feeds back a subscription relationship newly-increased success notification to the logic server, and the logic server further feeds back the subscription success notification to the terminal corresponding to the requester identifier.

After receiving the subscription relationship newly-increased success notification fed back by the subscription relationship storage server, the logic server correspondingly sends the requester identifier and the extracted subscription object identifier to the subscribed relationship storage server, so that the subscribed relationship of the extracted subscription object identifier to the requester identifier is newly increased by the subscribed relationship storage server.

In one embodiment, the subscription data processing method further includes: when the subscription relationship is successfully added, adding a check mark for the successfully added subscription relationship; the verification mark is used for indicating that when the subscription object identification is obtained from the subscription relation storage area and the obtained subscription object identification corresponds to the verification mark, the subscribed relation of the obtained subscription object identification to the requester identification is inquired in the subscribed relation storage area; the requester identity has a subscription relationship with the acquired subscription object identity.

In this embodiment, a check mark is added to the newly added subscription relationship, and when the subscription relationship is successfully written, it is determined that the subscription is successful. Therefore, when the user performs subscription inquiry, the existence of the subscribed relation is only verified for the subscription object identifier with the verification mark, so that the data processing amount is greatly reduced, and the data processing efficiency is improved.

In the above embodiment, after the subscription request initiated by the user is obtained, the subscription relationship of the user to the subscription object is written in the subscription relationship storage area, and the user is notified after the successful writing. And then writing the subscribed relation of the subscription object subscribed by the user in the subscribed relation storage area. Therefore, the perception of the user to the subscription process is improved, and the subscription relation and the subscribed relation between the user and the subscription object are stored, so that the subscription object identification existing in the subscription relation and the subscribed relation can be fed back to the user when the user performs subscription query subsequently, and the accuracy of the query result obtained when the user queries the subscription data is improved.

In one embodiment, the subscription data processing method further includes: acquiring a session request corresponding to the identifier of the requester; the session request points to the fed back subscription object identifier; responding to the session request, and establishing a session link between a terminal corresponding to the requester identifier and a terminal corresponding to the pointed subscription object identifier; and transmitting the session message initiated by the requester identifier to the terminal corresponding to the pointed subscription object identifier through the session link.

Wherein the conversation request is a request for membership to a specified object. The conversation can be a double conversation or a group conversation. The session may be a message session based on a message container, a voice session, or a video session.

Specifically, after receiving the subscription object identifiers fed back by the server, the terminal may select one or more of the subscription object identifiers to initiate a session request to the server. The server responds to the session request, establishes a session link between the terminal corresponding to the requester identifier and the terminal corresponding to the subscription object identifier pointed by the session request, and transmits the session message initiated by the requester identifier to the terminal corresponding to the subscription object identifier pointed by the session request through the session link.

In this embodiment, the user may perform a session with the subscription object after subscribing, so as to transfer or acquire more information more quickly, and improve the transfer efficiency and the transfer amount of the information.

In one embodiment, the server may further detect subscription content published by the subscription target identification fed back to the terminal. After detecting that the subscription content is published through the subscription target identifier, pushing the subscription content to a terminal corresponding to the requester identifier, so that the terminal displays the subscription content, thereby improving the pushing efficiency of the subscription message.

In one embodiment, the server may further detect a request for login through a subscription target identifier fed back to the terminal, and notify the requesting party of the terminal corresponding to the identifier after login on the computer device through the subscription target identifier.

Fig. 4 is a flowchart illustrating a subscription data processing method according to an embodiment. The embodiment is mainly illustrated by applying the method to the server 120 in fig. 1. Referring to fig. 4, the subscription data processing method specifically includes the following steps:

s402, receiving a subscription request corresponding to the requester identification.

Specifically, the terminal that requests the login of the identifier may send the identifier of the requester to the server in the subscription request, and the server may extract the identifier of the requester from the subscription request, thereby receiving the subscription request corresponding to the identifier of the requester. The terminal logged in by the requester identifier can also correspondingly send the requester identifier and the subscription request to the server, and the server receives the subscription request correspondingly sent by the requester identifier.

S404, extracting the subscription object identification pointed by the subscription request.

Specifically, the terminal that requests the identifier to log in may carry the identifier of the subscription object in the subscription request and send the subscription request to the server, so that the server may extract the identifier of the subscription object to which the subscription request is directed from the subscription request. The requester identifies the logged-in terminal, and can also correspondingly send the subscription object identification and the subscription request to the server, so that the server can acquire the subscription object identification sent correspondingly to the subscription request.

S406, in the subscription relationship storage area, the new addition requester identifier identifies the subscription relationship to the extracted subscription object identifier.

Specifically, the server may add the new requestor identifier to the subscription relationship of the extracted subscription object identifier in the local subscription relationship storage area. The server can also send the requester identifier and the subscription object identifier to the subscription relationship storage server, so that the subscription relationship storage server adds a subscription relationship of the requester identifier to the extracted subscription object identifier.

And S408, feeding back a subscription success notice according to the identifier of the requester when the subscription relationship is increased successfully.

Specifically, the server may feed back a subscription success notification to the terminal logged in by the requester identifier after the requester identifier added to the local subscription relationship storage area succeeds in the subscription relationship with the extracted subscription object identifier. The server can also feed back a successful subscription notification to the terminal logged in by the requester identifier after the subscription relationship of the new requester identifier added to the subscription relationship storage server for the extracted subscription object identifier is successful.

And S410, adding the newly extracted subscribed relation of the subscription object identifier to the requester identifier in the subscribed relation storage area.

Specifically, the server may add the newly extracted subscription object to identify the subscribed relationship to the requestor identifier in a local subscribed relationship storage area. The server can also send the requester identifier and the subscription object identifier to the subscribed relationship storage server, so that the subscribed relationship storage server adds the subscribed relationship of the extracted subscription object identifier to the requester identifier.

According to the subscription data processing method, after a subscription request initiated by a user is obtained, the subscription relationship of the user to a subscription object is written in the subscription relationship storage area, and the user is notified after the successful writing. And then writing the subscribed relation of the subscription object subscribed by the user in the subscribed relation storage area. Therefore, the perception of the user to the subscription process is improved, and the subscription relation and the subscribed relation between the user and the subscription object are stored, so that the subscription object identification existing in the subscription relation and the subscribed relation can be fed back to the user when the user performs subscription query subsequently, and the accuracy of the query result obtained when the user queries the subscription data is improved.

In one embodiment, the subscription data processing method further includes: when the subscription relationship is successfully added, adding a check mark for the successfully added subscription relationship; the check mark is used for indicating that the subscribed relation of the acquired subscribed object identifier to the requester identifier is inquired in the subscribed relation storage area when the subscribed object identifier is acquired from the subscribed relation storage area and the acquired subscribed object identifier corresponds to the check mark; the requester identity has a subscription relationship with the acquired subscription object identity.

In this embodiment, a check mark is added to the newly added subscription relationship, and when the subscription relationship is successfully written, it is determined that the subscription is successful. Therefore, when the user performs subscription inquiry subsequently, the existence of the subscribed relationship is only verified for the subscription object identifier with the verification mark, and the subscription object identifier with both the subscription relationship and the subscribed relationship is fed back to the user, so that the data processing amount is greatly reduced, and the data processing efficiency is improved.

In one embodiment, the subscription data processing method further comprises: acquiring a subscription object identifier from a subscription relation storage area; the requester identifier has a subscription relationship with the acquired subscription object identifier; when the acquired subscription object identification corresponds to the check mark, inquiring the subscribed relation of the subscription object identification to the requester identification in a subscribed relation storage area; and when the subscribed relation is inquired, deleting the check mark corresponding to the subscription object identifier.

It can be understood that, when the server queries that the subscription object identifier has a subscribed relationship with the requester identifier, it determines that the subscription relationship that the requester identifier has with the traversed subscription object identifier is correct, and retains the traversed subscription object identifier. At this time, if the process of checking the existence of the subscribed relationship is completed, the check mark corresponding to the subscribed object identifier may be deleted. When the server inquires that the subscription object identifier does not have the subscribed relationship with the requester identifier, it is determined that the subscription relationship existing with the requester identifier with respect to the subscription object identifier is wrong and needs to be deleted, that is, the subscription relationship of the requester identifier with respect to the subscription object identifier is deleted in the subscription relationship storage area.

In this embodiment, a check mark is added to the subscription relationship that needs to be checked for the existence of the subscribed relationship, so that when a user performs subscription query, the existence of the subscribed relationship only needs to be checked for the subscription object identifier corresponding to the check mark, thereby greatly reducing the data processing amount and improving the data processing efficiency.

In one embodiment, the subscription data processing method further includes: and when the subscribed relation is not inquired, deleting the subscription relation of the requester identifier to the subscription object identifier in the subscription relation storage area.

It can be understood that, when the subscription object identifier does not correspond to the check mark, it is determined whether the subscribed relationship between the subscription object identifier check and the requester identifier does not need to exist, and therefore, the step of querying the subscribed relationship of the acquired subscription object identifier to the requester identifier in the subscribed relationship storage area does not need to be executed, and the traversed subscription object identifier can be retained. In fact, the subscription object identifier does not correspond to a check mark, which indicates that the traversed subscription object identifier is checked in the historical checking process, and the subscription relation is reserved after the check is passed, and resources are wasted without repeated checking.

In this embodiment, a check mark is added to the subscription relationship that needs to be checked for the existence of the subscribed relationship, so that when a user performs subscription query, the existence of the subscribed relationship is not checked for the subscription object identifier that does not correspond to the check mark, thereby greatly reducing the data processing amount and improving the data processing efficiency.

In the above embodiment, the process of acquiring the subscription object identifier from the subscription relation storage area by the server to check may be an operation actively triggered by the server. For example, the server may set to periodically acquire the identification of the subscription object from the subscription relation storage area for verification. The process of acquiring the subscription object identifier from the subscription relation storage area by the server for verification may be an operation triggered by the requester. The terminal logged in by the requester identifier can initiate a subscription query request to the server, so as to trigger the server to acquire the subscription object identifier from the subscription relation storage area for verification. The server can also feed back the reserved subscription object identifier to the terminal logged in by the requester identifier after the verification is finished.

FIG. 5 is a diagram that illustrates the hardware architecture of the subscription data processing method, in one embodiment. Referring to fig. 5, the hardware architecture includes a requester identity logged in terminal, a logical server, a subscription relationship storage server, and a subscribed relationship storage server. The terminal can run an application logged in by a requester identifier. Such as the palmtop hero alliance, etc.

Referring again to FIG. 6, FIG. 6 illustrates a timing diagram for subscription data processing in one embodiment. The terminal logged in by the requester identifier can initiate a subscription request to the logic server, and after receiving the subscription request corresponding to the requester identifier, the logic server extracts the subscription object identifier pointed by the subscription request, sends the requester identifier and the subscription object identifier to the subscription relation storage server, and informs the subscription relation storage server of newly adding a subscription relation. In this way, the subscription relation storage server adds a check mark to the newly added subscription relation after the newly added requester identifier has a subscription relation with the subscription object identifier, and returns a processing result of the successfully added subscription relation to the logic server. The logic server then feeds back a subscription success notification to the terminal logged in by the requester identifier. The logic server can send the requester identifier and the subscription object identifier to the subscribed relationship storage server to notify the subscribed relationship storage server of adding the subscribed relationship newly, and the subscribed relationship storage server adds the subscribed relationship of the subscription object identifier to the requester identifier newly.

The terminal logged in by the requester identifier can initiate a subscription query request to the logic server, and after receiving the subscription query request corresponding to the requester identifier, the logic server sends the requester identifier to the subscription relation storage server to obtain the subscription object identifier returned by the subscription relation storage server, wherein the requester identifier has a subscription relation with the obtained subscription object identifier. The logic server checks the check mark for the acquired subscription object mark, reserves the subscription object mark which does not correspond to the check mark, sends the subscription object mark and the requester mark which correspond to the check mark to the subscribed relation storage server, and further acquires the result whether the subscribed relation exists between the subscription object mark and the requester mark returned by the subscribed relation storage server. If the subscribed relation exists between the two, the subscribed object identification is reserved and the check mark is deleted. If the subscribed relation does not exist between the two, the subscribed object identifier is considered as a failed subscribed object identifier, and the subscribed relation storage server is informed to delete the subscribed relation of the requester identifier to the failed subscribed object identifier.

The logic server can combine the subscription object identifiers reserved after the verification and the subscription object identifiers reserved without the verification, and feed the combined subscription object identifiers back to the terminal corresponding to the requester identifier.

It should be understood that, although the steps in the flowcharts of the above embodiments are shown in sequence as indicated by the arrows, the steps are not necessarily executed in sequence as indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least a part of the steps in the above embodiments may include multiple sub-steps or multiple stages, which are not necessarily performed at the same time, but may be performed at different times, and the order of performing the sub-steps or the stages is not necessarily performed in sequence, but may be performed alternately or alternately with other steps or at least a part of the sub-steps or the stages of other steps.

As shown in fig. 7, in one embodiment, a subscription data processing apparatus 700 is provided. Referring to fig. 7, the subscription data processing apparatus 700 includes: a receiving module 701, an obtaining module 702, an inquiring module 703 and a feedback module 704.

A receiving module 701, configured to receive a subscription query request corresponding to a requester identifier.

An obtaining module 702, configured to obtain a subscription object identifier from a subscription relation storage area in response to a subscription query request; the requester identity has a subscription relationship with the acquired subscription object identity.

The querying module 703 is configured to query, in the subscribed relationship storage area, the obtained subscribed object identifier for the subscribed relationship identified by the requestor identifier.

And a feedback module 704, configured to feed back, according to the identifier of the requester, the identifier of the subscription object in the subscribed relationship.

After acquiring the subscription query request initiated by the user, the subscription data processing apparatus 700 first acquires the subscription objects subscribed by the user from the subscription relation storage area, and then queries whether the subscription objects are subscribed by the user in the subscribed relation storage area. And only when the subscription relationship of the user to the subscription object and the subscribed relationship of the subscription object to the user exist, the inquired subscription object identifier is fed back to the user, so that the accuracy of the inquiry result obtained when the user inquires the subscription data is improved.

In one embodiment, the query module 703 is further configured to determine an invalid subscription object identifier; the invalid subscription object identification is the subscription object identification which has a subscribed relation to the requester identification and is not inquired; canceling the feedback invalid subscription object identification; and in the subscription relation storage area, deleting the subscription relation of the requester identifier to the invalid subscription object identifier.

In one embodiment, the query module 703 is further configured to check the check mark for the obtained subscription object identification; when the acquired subscription object identification corresponds to the check mark, executing a step of inquiring the subscription relation of the acquired subscription object identification to the requester identification in a storage area of the subscription relation; and when the subscribed relation is inquired, deleting the check mark corresponding to the subscription object identifier.

In one embodiment, the query module 703 is further configured to, when the obtained subscription object identifier does not correspond to the check mark, reserve the subscription object identifier that does not correspond to the check mark. The feedback module 704 is further configured to retain the identification of the subscription object queried to the subscribed relationship; and after integrating the reserved subscription object identifiers, feeding back according to the identifier of the requester.

In one embodiment, the subscription data processing apparatus 700 further comprises: the block 705 is written.

A writing module 705, configured to receive a subscription request corresponding to a requestor identifier; extracting a subscription object identifier pointed by the subscription request; in the subscription relation storage area, adding a subscription relation of the requester identifier to the extracted subscription object identifier; when the subscription relationship is increased successfully, feeding back a subscription success notification according to the identifier of the requester; and in the subscribed relation storage area, adding the subscribed relation of the extracted subscription object identifier to the requester identifier.

In one embodiment, the processing module 705 is further configured to add a check mark to the subscription relationship that is successfully added when the subscription relationship is successfully added; the verification mark is used for indicating that when the subscription object identification is obtained from the subscription relation storage area and the obtained subscription object identification corresponds to the verification mark, the subscribed relation of the obtained subscription object identification to the requester identification is inquired in the subscribed relation storage area; the requester identity has a subscription relationship with the acquired subscription object identity.

As shown in fig. 8, in one embodiment, the subscription data processing apparatus 700 further includes: a write module 705 and a pass-through module 706.

A transfer module 706 configured to receive a session request corresponding to the requestor identifier; the session request points to the fed back subscription object identifier; responding to the session request, and establishing a session link between a terminal corresponding to the requester identifier and a terminal corresponding to the pointed subscription object identifier; and transmitting the session message initiated by the requester identifier to the terminal corresponding to the pointed subscription object identifier through the session link.

As shown in fig. 9, in one embodiment, a subscription data processing apparatus 900 is provided. Referring to fig. 9, the subscription data processing apparatus 900 includes: a receiving module 901, an extracting module 902, a first adding module 903, a feedback module 904 and a second adding module 905.

A receiving module 901, configured to receive a subscription request corresponding to a requester identifier.

The extracting module 902 is configured to extract the identification of the subscription object to which the subscription request points.

A first adding module 903, configured to add, in the subscription relationship storage area, the subscription relationship of the new requester identifier to the extracted subscription object identifier.

And a feedback module 904, configured to feed back a subscription success notification according to the identifier of the requester when the subscription relationship is newly successfully added.

A second adding module 905, configured to add, in the subscribed relationship storage area, a subscribed relationship of the extracted subscription object identifier to the requestor identifier.

After acquiring the subscription request initiated by the user, the subscription data processing device 900 writes the subscription relationship of the user to the subscription object in the subscription relationship storage area, and notifies the user after the successful writing. And then writing the subscribed relation of the subscription object subscribed by the user in the subscribed relation storage area. Therefore, the perception of the user to the subscription process is improved, the subscription relation and the subscribed relation between the user and the subscription object are stored, and the subscription object identification existing in the subscription relation and the subscribed relation can be fed back to the user when the user performs subscription query subsequently, so that the accuracy of the query result obtained when the user queries the subscription data is improved.

In an embodiment, the first adding module 903 is further configured to add a check mark to the subscription relationship that is successfully added when the subscription relationship is successfully added; the verification mark is used for indicating that when the subscription object identification is obtained from the subscription relation storage area and the obtained subscription object identification corresponds to the verification mark, the subscribed relation of the obtained subscription object identification to the requester identification is inquired in the subscribed relation storage area; the requester identity has a subscription relationship with the acquired subscription object identity.

As shown in fig. 10, in one embodiment, the subscription data processing apparatus 900 further includes: a verification module 906.

A checking module 906, configured to obtain a subscription object identifier from the subscription relationship storage area; the requester identifier has a subscription relationship with the acquired subscription object identifier; when the acquired subscription object identifier corresponds to the check mark, inquiring the subscribed relation of the subscription object identifier to the requester identifier in a subscribed relation storage area; and when the subscribed relation is inquired, deleting the check mark corresponding to the subscribed object identifier.

In one embodiment, the checking module 906 is further configured to delete the subscription relationship identified by the requester to the subscription object identification in the subscription relationship storage area when the subscribed relationship is not queried.

FIG. 11 is a diagram illustrating an internal structure of a computer device in one embodiment. The computer device may specifically be the server 120 in fig. 1. As shown in fig. 11, the computer device includes a processor, a memory, and a network interface connected by a system bus. Wherein the memory includes a non-volatile storage medium and an internal memory. The non-volatile storage medium of the computer device stores an operating system and may also store a computer program that, when executed by the processor, causes the processor to implement the subscription data processing method. The internal memory may also have a computer program stored therein, which when executed by the processor, causes the processor to perform the subscription data processing method. Those skilled in the art will appreciate that the architecture shown in fig. 11 is merely a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the computing devices to which the disclosed aspects apply, as particular computing devices may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.

In one embodiment, the subscription data processing apparatus provided in the present application may be implemented in a form of a computer program, where the computer program may be run on a computer device as shown in fig. 11, and a non-volatile storage medium of the computer device may store various program modules that constitute the subscription data processing apparatus, such as the receiving module 701, the obtaining module 702, the querying module 703, the feedback module 704, and the like shown in fig. 7. The computer program composed of the respective program modules causes the processor to execute the steps in the subscription data processing method of the respective embodiments of the present application described in the present specification.

For example, the computer device shown in fig. 11 may receive the subscription query request corresponding to the requester identity through the receiving module 701 in the subscription data processing apparatus 700 shown in fig. 7. The obtaining module 702 obtains the subscription object identifier from the subscription relation storage area in response to the subscription inquiry request; the requester identity has a subscription relationship with the acquired subscription object identity. The obtained subscription object identifier is queried for the subscribed relationship to the requestor identifier in a subscribed relationship storage area through a query module 703. The feedback module 704 feeds back the identification of the subscription object queried to the subscribed relationship according to the identification of the requester.

In one embodiment, a computer readable storage medium is provided, having a computer program stored thereon, which, when executed by a processor, causes the processor to perform the steps of: receiving a subscription inquiry request corresponding to the requester identifier; responding to the subscription inquiry request, and acquiring a subscription object identifier from a subscription relation storage area; the requester identifier has a subscription relationship with the acquired subscription object identifier; in the subscribed relation storage area, inquiring the subscribed relation of the acquired subscription object identifier to the requester identifier; and feeding back and inquiring the subscription object identification of the subscribed relationship according to the requester identification.

In one embodiment, the computer program, when executed by the processor, further causes the processor to perform the steps of: determining an invalid subscription object identifier; the failed subscription object identifier is the subscription object identifier which is not inquired that the subscribed relation exists for the requester identifier; canceling the feedback invalid subscription object identification; and in the subscription relation storage area, deleting the subscription relation of the requester identifier to the invalid subscription object identifier.

In one embodiment, the computer program, when executed by the processor, further causes the processor to perform the steps of: checking the check mark for the acquired subscription object identifier; when the acquired subscription object identification corresponds to the check mark, executing a step of inquiring the subscribed relation of the acquired subscription object identification to the requester identification in a subscribed relation storage area; and when the subscribed relation is inquired, deleting the check mark corresponding to the subscribed object identifier.

In one embodiment, the computer program, when executed by the processor, further causes the processor to perform the steps of: and when the acquired subscription object identification does not correspond to the check mark, reserving the subscription object identification which does not correspond to the check mark. According to the identifier of the requester, the step of feeding back the identifier of the subscription object which inquires the subscribed relationship comprises the following steps: reserving the identification of the subscription object queried to the subscribed relationship; and after integrating the reserved subscription object identifiers, feeding back according to the identifier of the requester.

In one embodiment, the computer program, when executed by the processor, further causes the processor to perform the steps of: receiving a subscription request corresponding to the requester identifier; extracting a subscription object identifier pointed by the subscription request; in the subscription relation storage area, adding a subscription relation of the requester identifier to the extracted subscription object identifier; when the subscription relationship is increased successfully, feeding back a subscription success notification according to the identifier of the requester; and in the subscribed relation storage area, adding the subscribed relation of the extracted subscription object identifier to the requester identifier.

In one embodiment, the computer program, when executed by the processor, further causes the processor to perform the steps of: when the subscription relationship is successfully added, adding a check mark for the successfully added subscription relationship; the verification mark is used for indicating that when the subscription object identification is obtained from the subscription relation storage area and the obtained subscription object identification corresponds to the verification mark, the subscribed relation of the obtained subscription object identification to the requester identification is inquired in the subscribed relation storage area; the requester identity has a subscription relationship with the acquired subscription object identity.

In one embodiment, the computer program, when executed by the processor, further causes the processor to perform the steps of: receiving a session request corresponding to the requester identifier; the session request points to the fed-back subscription object identifier; responding to the session request, and establishing a session link between a terminal corresponding to the requester identifier and a terminal corresponding to the pointed subscription object identifier; and transmitting the session message initiated by the requester identifier to the terminal corresponding to the pointed subscription object identifier through the session link.

After acquiring a subscription query request initiated by a user, the storage medium first acquires the subscription objects subscribed by the user from the subscription relation storage area, and then queries whether the subscription objects are subscribed by the user in the subscribed relation storage area. And only when the subscription relationship of the user to the subscription object and the subscribed relationship of the subscription object to the user exist, the inquired subscription object identification is fed back to the user, so that the accuracy of the inquiry result obtained when the user inquires the subscription data is improved.

In one embodiment, there is provided a computer device comprising a memory and a processor, the memory having stored therein a computer program that, when executed by the processor, causes the processor to perform the steps of: receiving a subscription inquiry request corresponding to the requester identifier; responding to the subscription inquiry request, and acquiring a subscription object identifier from a subscription relation storage area; the requester identifier has a subscription relationship with the acquired subscription object identifier; in the subscribed relation storage area, inquiring the subscribed relation of the acquired subscription object identifier to the requester identifier; and feeding back the subscription object identifier of the subscribed relation according to the requester identifier.

In one embodiment, the computer program, when executed by the processor, further causes the processor to perform the steps of: determining an invalid subscription object identifier; the failed subscription object identifier is the subscription object identifier which is not inquired that the subscribed relation exists for the requester identifier; canceling the feedback of the invalid subscription object identifier; in the subscription relationship storage area, the subscription relationship of the requester identifier to the failed subscription object identifier is deleted.

In one embodiment, the computer program, when executed by the processor, further causes the processor to perform the steps of: checking a check mark for the acquired subscription object identifier; when the acquired subscription object identification corresponds to the check mark, executing a step of inquiring the subscription relation of the acquired subscription object identification to the requester identification in a storage area of the subscription relation; and when the subscribed relation is inquired, deleting the check mark corresponding to the subscribed object identifier.

In one embodiment, the computer program, when executed by the processor, further causes the processor to perform the steps of: and when the acquired subscription object identification does not correspond to the check mark, reserving the subscription object identification which does not correspond to the check mark. According to the identifier of the requester, feeding back the identifier of the subscription object queried to the subscribed relationship comprises: reserving the identification of the subscription object queried to the subscribed relationship; and after integrating the reserved subscription object identifiers, feeding back according to the identifier of the requester.

In one embodiment, the computer program, when executed by the processor, further causes the processor to perform the steps of: receiving a subscription request corresponding to the requester identifier; extracting a subscription object identifier pointed by the subscription request; in the subscription relation storage area, adding a subscription relation of the requester identifier to the extracted subscription object identifier; when the subscription relationship is successfully increased, feeding back a subscription success notification according to the identifier of the requester; and in the subscribed relation storage area, adding the subscribed relation of the extracted subscription object identifier to the requester identifier.

In one embodiment, the computer program, when executed by the processor, further causes the processor to perform the steps of: when the subscription relationship is added successfully, adding a check mark for the newly added subscription relationship; the check mark is used for indicating that the subscribed relation of the acquired subscribed object identifier to the requester identifier is inquired in the subscribed relation storage area when the subscribed object identifier is acquired from the subscribed relation storage area and the acquired subscribed object identifier corresponds to the check mark; the requester identity has a subscription relationship with the acquired subscription object identity.

In one embodiment, the computer program, when executed by the processor, further causes the processor to perform the steps of: receiving a session request corresponding to a requester identifier; the session request points to the fed back subscription object identifier; responding to the session request, and establishing a session link between a terminal corresponding to the requester identifier and a terminal corresponding to the pointed subscription object identifier; and transmitting the session message initiated by the requester identifier to the terminal corresponding to the pointed subscription object identifier through the session link.

After acquiring a subscription query request initiated by a user, the computer device first acquires the subscription objects subscribed by the user from the subscription relation storage area, and then queries whether the subscription objects are subscribed by the user in the subscribed relation storage area. And only when the subscription relationship of the user to the subscription object and the subscribed relationship of the subscription object to the user exist, the inquired subscription object identifier is fed back to the user, so that the accuracy of the inquiry result obtained when the user inquires the subscription data is improved.

In one embodiment, a computer readable storage medium is provided, having a computer program stored thereon, which, when executed by a processor, causes the processor to perform the steps of: receiving a subscription request corresponding to the requester identifier; extracting a subscription object identifier pointed by the subscription request; in the subscription relation storage area, adding a subscription relation of the requester identifier to the extracted subscription object identifier; when the subscription relationship is increased successfully, feeding back a subscription success notification according to the identifier of the requester; and in the subscribed relation storage area, adding the subscribed relation of the extracted subscription object identifier to the requester identifier.

In one embodiment, the computer program, when executed by the processor, further causes the processor to perform the steps of: when the subscription relationship is added successfully, adding a check mark for the newly added subscription relationship; the verification mark is used for indicating that when the subscription object identification is obtained from the subscription relation storage area and the obtained subscription object identification corresponds to the verification mark, the subscribed relation of the obtained subscription object identification to the requester identification is inquired in the subscribed relation storage area; the requester identity has a subscription relationship with the acquired subscription object identity.

In one embodiment, the computer program, when executed by the processor, further causes the processor to perform the steps of: acquiring a subscription object identifier from a subscription relation storage area; the requester identifier has a subscription relationship with the acquired subscription object identifier; when the acquired subscription object identification corresponds to the check mark, inquiring the subscribed relation of the subscription object identification to the requester identification in a subscribed relation storage area; and when the subscribed relation is inquired, deleting the check mark corresponding to the subscription object identifier.

In one embodiment, the computer program, when executed by the processor, further causes the processor to perform the steps of: and when the subscribed relation is not inquired, deleting the subscription relation of the requester identifier to the subscription object identifier in the subscription relation storage area.

After the storage medium acquires a subscription request initiated by a user, the storage medium firstly writes the subscription relationship of the user to a subscription object in the subscription relationship storage area, and notifies the user after the successful writing. And then writing the subscribed relation of the subscription object subscribed by the user in the subscribed relation storage area. Therefore, the perception of the user to the subscription process is improved, the subscription relation and the subscribed relation between the user and the subscription object are stored, and the subscription object identification existing in the subscription relation and the subscribed relation can be fed back to the user when the user performs subscription query subsequently, so that the accuracy of the query result obtained when the user queries the subscription data is improved.

In one embodiment, there is provided a computer device comprising a memory and a processor, the memory having stored therein a computer program that, when executed by the processor, causes the processor to perform the steps of: receiving a subscription request corresponding to the requester identifier; extracting a subscription object identifier pointed by the subscription request; in the subscription relation storage area, adding a subscription relation of the requester identifier to the extracted subscription object identifier; when the subscription relationship is increased successfully, feeding back a subscription success notification according to the identifier of the requester; and in the subscribed relation storage area, adding the subscribed relation of the extracted subscription object identifier to the requester identifier.

In one embodiment, the computer program, when executed by the processor, further causes the processor to perform the steps of: acquiring a subscription object identifier from a subscription relation storage area; the requester identifier has a subscription relationship with the acquired subscription object identifier; when the acquired subscription object identifier corresponds to the check mark, inquiring the subscribed relation of the subscription object identifier to the requester identifier in a subscribed relation storage area; and when the subscribed relation is inquired, deleting the check mark corresponding to the subscribed object identifier.

After the computer device obtains the subscription request initiated by the user, the subscription relationship of the user to the subscription object is written in the subscription relationship storage area, and the user is notified after the successful writing. And then writing the subscribed relation of the subscription object subscribed by the user in the subscribed relation storage area. Therefore, the perception of the user to the subscription process is improved, the subscription relation and the subscribed relation between the user and the subscription object are stored, and the subscription object identification existing in the subscription relation and the subscribed relation can be fed back to the user when the user performs subscription query subsequently, so that the accuracy of the query result obtained when the user queries the subscription data is improved.

It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by a computer program, which can be stored in a non-volatile computer-readable storage medium, and can include the processes of the embodiments of the methods described above when the program is executed. Any reference to memory, storage, database, or other medium used in the embodiments provided herein may include non-volatile and/or volatile memory, among others. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically Programmable ROM (EPROM), electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double Data Rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous Link DRAM (SLDRAM), rambus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).

All possible combinations of the technical features in the above embodiments may not be described for the sake of brevity, but should be considered as being within the scope of the present disclosure as long as there is no contradiction between the combinations of the technical features.

The above examples only show several embodiments of the present invention, and the description thereof is specific and detailed, but not to be construed as limiting the scope of the present invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the inventive concept, which falls within the scope of the present invention. Therefore, the protection scope of the present patent shall be subject to the appended claims.

Claims

1. A method for processing subscription data, the method comprising:

the logic server receives a subscription inquiry request corresponding to the requester identifier;

the logic server responds to the subscription inquiry request and sends the requester identification to a subscription relation storage server;

the subscription relation storage server acquires a subscription object identifier from a subscription relation storage area according to the requester identifier; the requester identification has a subscription relation with the acquired subscription object identification; the subscription relation is a one-way corresponding relation pointed to the subscription object identification by the requester identification;

the logic server checks a check mark for the acquired subscription object identifier, wherein the check mark is used for indicating a mark for checking the existence of the subscribed relation;

when the acquired subscription object identifier corresponds to a check mark, the logic server sends the subscription object identifier and the requester identifier to a subscribed relation storage server; the subscribed relation storage server inquires the subscribed relation of the acquired subscription object identifier to the requester identifier in a subscribed relation storage area; the subscribed relation is a one-way corresponding relation of the subscription object identifier to the requester identifier; when the subscribed relation storage server inquires the subscribed relation, determining that the subscribed relation exists between the subscription object identifier and the requester identifier; the logic server deletes the check mark corresponding to the subscription object identifier and feeds back and inquires the subscription object identifier of the subscribed relationship according to the requester identifier; when the subscribed relation storage server does not inquire the subscribed relation, determining that the subscribed relation does not exist between the subscription object identifier and the requester identifier, and deleting the subscription relation between the requester identifier and the subscription object identifier in a subscription relation storage area by the subscription relation storage server;

when the obtained subscription object identification does not correspond to the check mark, reserving the subscription object identification which does not correspond to the check mark; reserving the identification of the subscription object which is inquired to the subscribed relation; and merging the reserved subscription object identification after the check and the reserved subscription object identification without the check, and feeding back the merged subscription object identification to a terminal corresponding to the requester identification.

2. The method of claim 1, further comprising:

determining an invalid subscription object identifier; the failed subscription object identifier is a subscription object identifier which is not inquired that a subscribed relation exists for the requester identifier;

canceling the feedback of the invalid subscription object identifier;

and deleting the subscription relation of the requester identifier to the invalid subscription object identifier in the subscription relation storage area.

3. The method of claim 1, wherein the subscribing relationship and the subscribed relationship are both stored via a relational database.

4. The method of claim 1, further comprising:

receiving a subscription request corresponding to the requester identifier;

in the subscription relation storage area, adding the subscription relation of the requester identifier to the extracted subscription object identifier;

5. The method of claim 4, further comprising:

when the subscription relationship is successfully added, adding a check mark for the successfully added subscription relationship; the check mark is used for indicating that the subscribed object identification is acquired from the subscribed relation storage area, and when the acquired subscribed object identification corresponds to the check mark, the acquired subscribed relation of the subscribed object identification to the requester identification is inquired in the subscribed relation storage area; the requester identification has a subscription relationship with the acquired subscription object identification.

6. The method according to any one of claims 1-5, further comprising:

receiving a session request corresponding to the requester identifier; the session request points to the fed back subscription object identifier;

responding to the session request, and establishing a session link between a terminal corresponding to the requester identifier and a terminal corresponding to the pointed subscription object identifier;

and transmitting the session message initiated by the requester identifier to the terminal corresponding to the pointed subscription object identifier through the session link.

7. A method for processing subscription data, the method comprising:

the logic server receives a subscription request corresponding to the requester identifier;

the logic server extracts the subscription object identification pointed by the subscription request and sends the requester identification and the extracted subscription object identification to a subscription relation storage server;

the subscription relation storage server adds the subscription relation of the requester identifier to the extracted subscription object identifier in a subscription relation storage area; the subscription relation is a one-way corresponding relation pointed to the subscription object identification by the requester identification;

when the subscription relationship is successfully added, the subscription relationship storage server feeds back a subscription relationship addition success notification to the logic server according to the requester identifier, so that the logic server feeds back the subscription success notification to the terminal corresponding to the requester identifier, and sends the requester identifier and the extracted subscription object identifier to the subscribed relationship storage server, so that the subscribed relationship storage server adds the subscribed relationship of the extracted subscription object identifier to the requester identifier in a subscribed relationship storage area; the subscribed relation is a one-way corresponding relation of the subscription object identifier to the requester identifier;

when the subscription relationship is successfully added, the subscription relationship storage server adds a check mark for the successfully added subscription relationship; the check mark is used for indicating that the acquired subscribed object identification is inquired about the subscribed relation of the acquired subscribed object identification to the requester identification in the subscribed relation storage area when the subscribed object identification is acquired from the subscribed relation storage area and the acquired subscribed object identification corresponds to the check mark; the requester identification has a subscription relationship with the acquired subscription object identification;

the subscription relation storage server acquires a subscription object identifier from the subscription relation storage area; the requester identification has a subscription relationship with the acquired subscription object identification;

when the acquired subscription object identifier corresponds to the check mark, the subscribed relation storage server queries the subscribed relation of the subscription object identifier to the requester identifier in a subscribed relation storage area;

when the subscribed relation is inquired, the logic server deletes the check mark corresponding to the subscribed object identifier;

and when the subscribed relation is not inquired, the logic server deletes the subscription relation of the requester identifier to the subscription object identifier in the subscription relation storage area.

8. The method of claim 7, wherein the subscription object is a subscribed object comprising a user, a subscription message provider, a group, or a topic.

9. The method of claim 7, wherein the subscribing relationship and the subscribed relationship are both stored via a relational database.

10. A subscription data processing apparatus, characterized in that the apparatus comprises:

an obtaining module, configured to send the requester identifier to a subscription relationship storage server in response to the subscription query request, so that the subscription relationship storage server obtains a subscription object identifier from a subscription relationship storage area according to the requester identifier; the requester identification has a subscription relation with the acquired subscription object identification; the subscription relation is a one-way corresponding relation pointed to the subscription object identification by the requester identification;

the query module is used for checking a check mark for the acquired subscription object identifier, wherein the check mark is used for indicating a mark for checking the existence of the subscribed relation; when the acquired subscription object identification corresponds to a check mark, sending the subscription object identification and the requester identification to a subscribed relation storage server; enabling the subscribed relation storage server to inquire the subscribed relation of the acquired subscription object identifier to the requester identifier in a subscribed relation storage area; the subscribed relation is a one-way corresponding relation of the subscription object identifier to the requester identifier; when the acquired subscription object identification does not correspond to the check mark, reserving the subscription object identification which does not correspond to the check mark; reserving the identification of the subscription object which is inquired to the subscribed relation; combining the reserved subscription object identification after the check and the reserved subscription object identification without the check, and feeding back the combined subscription object identification to a terminal corresponding to the requester identification;

the feedback module is used for determining that the subscribed object identifier and the requester identifier have the subscribed relationship when the subscribed relationship is inquired; deleting the check mark corresponding to the subscription object identifier and feeding back the subscription object identifier which is queried to be subscribed according to the requester identifier; and when the subscribed relation is not inquired by the subscribed relation storage server, determining that the subscribed relation does not exist between the subscription object identifier and the requester identifier, and deleting the subscription relation between the requester identifier and the subscription object identifier in a subscription relation storage area by the subscription relation storage server.

11. The apparatus of claim 10, wherein the query module is further configured to:

canceling the feedback of the invalid subscription object identifier;

12. The apparatus of claim 10, wherein the subscribing relationship and the subscribed relationship are both stored via a relational database.

13. The apparatus of claim 10, further comprising:

a write-in module, configured to receive a subscription request corresponding to the requestor identifier; extracting a subscription object identifier pointed by the subscription request; in the subscription relation storage area, adding the subscription relation of the requester identifier to the extracted subscription object identifier; when the subscription relationship is successfully added, feeding back a subscription success notification according to the requester identifier; and in the subscribed relation storage area, adding the subscribed relation of the extracted subscription object identifier to the requester identifier.

14. The apparatus of claim 13, further comprising:

the processing module is used for adding a check mark for the subscription relationship which is successfully added when the subscription relationship is successfully added; the check mark is used for indicating that the subscribed object identification is acquired from the subscribed relation storage area, and when the acquired subscribed object identification corresponds to the check mark, the acquired subscribed relation of the subscribed object identification to the requester identification is inquired in the subscribed relation storage area; the requester identification has a subscription relationship with the acquired subscription object identification.

15. The apparatus according to any one of claims 10-14, further comprising:

the transfer module is used for receiving a session request corresponding to the requester identifier; the session request points to the fed back subscription object identifier;

the transfer module is further configured to, in response to the session request, establish a session link between the terminal corresponding to the requestor identifier and the terminal corresponding to the pointed subscription object identifier;

the transfer module is further configured to transfer, through the session link, a session message initiated by the requestor identifier to a terminal corresponding to the pointed subscription object identifier.

16. A subscription data processing apparatus, characterized in that the apparatus comprises:

a receiving module, configured to enable the logic server to receive a subscription request corresponding to the requestor identifier;

the extracting module is used for enabling the logic server to extract the subscription object identifier pointed by the subscription request and send the requester identifier and the extracted subscription object identifier to the subscription relation storage server;

a first adding module, configured to add a subscription relationship of the requestor identifier to the extracted subscription object identifier in a subscription relationship storage area by a subscription relationship storage server; the subscription relation is a one-way corresponding relation pointed to the subscription object identification by the requester identification;

a feedback module, configured to, when the subscription relationship is successfully added, enable the subscription relationship storage server to feed back a subscription relationship addition success notification to the logic server according to the requestor identifier, so that the logic server feeds back a subscription success notification to the terminal corresponding to the requestor identifier, and sends the requestor identifier and the extracted subscription object identifier to the subscribed relationship storage server;

a second newly-added module, configured to add a newly-added subscribed relationship, to the requestor identifier, of the extracted subscription object identifier in a subscribed relationship storage area by the subscribed relationship storage server; the subscribed relation is a one-way corresponding relation of the subscription object identifier to the requester identifier;

the first adding module is further used for enabling the subscription relationship storage server to add a check mark for the subscription relationship which is successfully added when the subscription relationship is successfully added; the check mark is used for indicating that the subscribed object identification is acquired from the subscribed relation storage area, and when the acquired subscribed object identification corresponds to the check mark, the acquired subscribed relation of the subscribed object identification to the requester identification is inquired in the subscribed relation storage area; the requester identification has a subscription relationship with the acquired subscription object identification;

the checking module is used for acquiring the subscription object identification from the subscription relation storage area; the requester identification has a subscription relationship with the acquired subscription object identification; when the acquired subscription object identifier corresponds to a check mark, enabling the subscribed relation storage server to query the subscribed relation of the subscription object identifier to the requester identifier in a subscribed relation storage area; when the subscribed relation is inquired, the logic server deletes the check mark corresponding to the subscribed object identifier; and when the subscribed relation is not inquired, the logic server deletes the subscription relation of the requester identifier to the subscription object identifier in the subscription relation storage area.

17. The apparatus of claim 16, wherein the subscription object is a subscribed object comprising a user, a subscription message provider, a group, or a topic.

18. The apparatus of claim 16, wherein the subscribing relationship and the subscribed relationship are each stored via a relational database.

19. A computer-readable storage medium, having stored thereon a computer program which, when executed by a processor, causes the processor to carry out the steps of the method according to any one of claims 1 to 9.

20. A computer device comprising a memory and a processor, the memory having stored therein a computer program that, when executed by the processor, causes the processor to perform the steps of the method according to any one of claims 1 to 9.