CN113900764A

CN113900764A - Page data acquisition method, page data display method and device

Info

Publication number: CN113900764A
Application number: CN202111515562.6A
Authority: CN
Inventors: 杨文强
Original assignee: Beijing Dajia Internet Information Technology Co Ltd
Current assignee: Beijing Dajia Internet Information Technology Co Ltd
Priority date: 2021-12-13
Filing date: 2021-12-13
Publication date: 2022-01-07
Anticipated expiration: 2041-12-13
Also published as: CN113900764B

Abstract

The disclosure relates to a page data acquisition method, a page data display method and a page data display device, wherein the method comprises the following steps: responding to an aggregation message acquisition request, and sending a target aggregation message, a message identifier of the target aggregation message and a message type of the target aggregation message to a request client; responding to a data acquisition request of an associated page corresponding to the target aggregation message, and calling a data sharing interface; the data acquisition request comprises the message identification and the message type; the data sharing interface is used for acquiring associated page data corresponding to the aggregated messages of multiple message types; transmitting the message identification and the message type into the data sharing interface; and acquiring page data of an associated page corresponding to the target aggregation message based on the transmitted message identifier and the data sharing interface of the message type. The method and the device can improve the stability of the server and the development efficiency of the server.

Description

Page data acquisition method, page data display method and device

Technical Field

The present disclosure relates to the field of computer technologies, and in particular, to a page data obtaining method, a page data displaying method, and a page data displaying device.

Background

In the social application, a series of behaviors among users are often transmitted through messages, and the messages can be displayed on a message page, wherein the messages specifically display the interactive behaviors generated among the users. When a user clicks a message, the user enters a message detail page corresponding to the message, namely a secondary page.

Because of the different message types, the database tables of the data store for the respective secondary pages are also different. In the related technology, different page interfaces are defined for different message types, and corresponding page interfaces are called according to the message types to acquire corresponding secondary page data; with the increase of the message types, the number of corresponding page interfaces also increases, so that the problem of interface expansion occurs, and the server is unstable.

Disclosure of Invention

The disclosure provides a page data acquisition method, a page data display method and a page data display device, which are used for at least solving the problem that a server is unstable due to interface expansion when a secondary page corresponding to a polymerization message is accessed in the related art. The technical scheme of the disclosure is as follows:

according to a first aspect of the embodiments of the present disclosure, a method for acquiring page data is provided, including:

responding to an aggregation message acquisition request, and sending a target aggregation message, a message identifier of the target aggregation message and a message type of the target aggregation message to a request client; the target aggregation message is obtained by aggregating a plurality of single messages with the same message type;

responding to a data acquisition request of an associated page corresponding to the target aggregation message, and calling a data sharing interface; the data acquisition request comprises the message identification and the message type; the data sharing interface is used for acquiring associated page data corresponding to the aggregated messages of multiple message types;

transmitting the message identification and the message type into the data sharing interface;

and acquiring page data of an associated page corresponding to the target aggregation message based on the transmitted message identifier and the data sharing interface of the message type.

In an exemplary embodiment, the aggregate message acquisition request includes an object identifier of a request object;

the sending a target aggregation message, a message identifier of the target aggregation message, and a message type of the target aggregation message in response to the aggregation message acquisition request includes:

responding to the aggregate message acquisition request, and calling a message data acquisition interface;

transmitting the object identification of the request object into the message data acquisition interface;

acquiring a plurality of messages of the request object and message types of the plurality of messages based on the message data acquisition interface which has transmitted the object identifier;

aggregating the messages belonging to the same message type based on the message types of the plurality of messages to obtain at least one target aggregated message;

generating a message identifier corresponding to the at least one target aggregation message;

and sending the at least one target aggregation message, the message identification of the at least one target aggregation message and the message type of the at least one target aggregation message to the requesting client.

In an exemplary embodiment, the obtaining, based on the data sharing interface that has transmitted the message identifier and the message type, page data of an associated page corresponding to the target aggregated message includes:

accessing a first data storage table corresponding to the message type based on the data sharing interface;

searching first page data of an associated page corresponding to the message identifier in the first data storage table;

and acquiring the first page data.

In an exemplary embodiment, the method further comprises:

responding to the message type adding request, and generating an adding type information item;

updating the current message type group based on the newly added type information item to obtain an updated message type group;

generating client update information based on the updated set of message types;

and issuing the client updating information.

In an exemplary embodiment, the aggregate message obtaining request includes an object identifier of a request object and version information of the request client;

responding to the aggregate message acquisition request, and acquiring a target aggregate message corresponding to the request object based on the object identification;

under the condition that the target aggregation message comprises at least one newly added aggregation message of a newly added type, carrying out consistency comparison on the version information of the request client and the version information of the target client; the target client is used for receiving the newly added aggregation message;

sending the client update information under the condition that the consistency is not consistent with the version information of the target client, wherein the result indicates that the version information of the request client is inconsistent with the version information of the target client;

determining the message identification of the newly added aggregated message and the message type of the newly added aggregated message;

and sending the newly added aggregation message, the message identifier of the newly added aggregation message and the message type of the newly added aggregation message to the updated client.

In an exemplary embodiment, the invoking a data sharing interface in response to a data obtaining request of an associated page corresponding to the target aggregation message includes:

responding to a data acquisition request of the associated page triggered based on the newly added aggregation message, and calling a data sharing interface; the data acquisition request comprises a message identifier of the newly added aggregation message and a message type of the newly added aggregation message;

the acquiring, based on the message identifier of the newly added aggregate message and the data sharing interface of the message type of the newly added aggregate message, page data of an associated page corresponding to the target aggregate message includes:

accessing a second data storage table corresponding to the message type of the newly added aggregated message based on the data sharing interface;

searching second page data of an associated page corresponding to the message identifier of the newly added aggregation message in the second data storage table;

and acquiring the second page data.

In an exemplary embodiment, the method further comprises:

rendering the display form of the page data in the associated page to obtain rendered page data;

generating a related page display instruction based on the rendered page data; and the associated page display instruction is used for instructing the requesting client to render and display the associated page based on the rendered page data.

According to a second aspect of the embodiments of the present disclosure, there is provided a page data display method, including:

sending an aggregation message acquisition request;

receiving a target aggregation message sent by a server based on the aggregation message acquisition request, a message identifier of the target aggregation message, and a message type of the target aggregation message; the target aggregation message is obtained by aggregating a plurality of single messages with the same message type;

sending a data acquisition request of an associated page corresponding to the target aggregation message;

receiving page data of an associated page corresponding to the target aggregation message sent by the server; the page data is obtained based on a data sharing interface; the data sharing interface is used for acquiring associated page data corresponding to the aggregated messages of multiple message types;

and displaying the page data.

In an exemplary embodiment, the presenting the page data includes:

receiving an associated page display instruction which is sent by the server and generated based on the rendered page data; the rendered page data is obtained by rendering the display form of the page data in the associated page;

and rendering and displaying the associated page based on the associated page display instruction.

In an exemplary embodiment, the target aggregation message is obtained by performing the same operation on target publishing information based on a plurality of objects; the target aggregation message comprises message text content information, object identification information of a plurality of target objects and identification information of the target release information;

the method further comprises the following steps:

and displaying the message text content information, the object identification information of the target objects and the identification information of the target release information.

According to a third aspect of the embodiments of the present disclosure, there is provided a page data acquiring apparatus including:

a first request response unit configured to execute sending, in response to an aggregated message acquisition request, a target aggregated message, a message identifier of the target aggregated message, and a message type of the target aggregated message to a requesting client; the target aggregation message is obtained by aggregating a plurality of single messages with the same message type;

a second request response unit configured to execute a data acquisition request in response to the associated page corresponding to the target aggregation message, and invoke a data sharing interface; the data acquisition request comprises the message identification and the message type; the data sharing interface is used for acquiring associated page data corresponding to the aggregated messages of multiple message types;

a first import unit configured to perform import of the message identification and the message type into the data sharing interface;

a first obtaining unit, configured to perform obtaining, based on the data sharing interface that has transmitted the message identifier and the message type, page data of an associated page corresponding to the target aggregated message.

the first request response unit includes:

a message data acquisition interface calling unit configured to execute calling a message data acquisition interface in response to the aggregated message acquisition request;

a second incoming unit configured to perform incoming of an object identification of the request object into the message data acquisition interface;

a second obtaining unit configured to perform obtaining, based on the message data obtaining interface into which the object identifier has been passed, a plurality of messages of the request object and message types of the plurality of messages;

the message aggregation unit is configured to perform aggregation on the messages belonging to the same message type based on the message types of the plurality of messages to obtain at least one target aggregated message;

a message identifier generating unit configured to perform generation of a message identifier corresponding to the at least one target aggregated message;

a first sending unit configured to perform sending the at least one target aggregation message, the message identification of the at least one target aggregation message, and the message type of the at least one target aggregation message to the requesting client.

In an exemplary embodiment, the first obtaining unit includes:

a first accessing unit configured to perform accessing a first data storage table corresponding to the message type based on the data sharing interface;

a first lookup unit configured to perform lookup of first page data of an associated page corresponding to the message identifier in the first data storage table;

a first page data acquisition unit configured to perform acquisition of the first page data.

In an exemplary embodiment, the apparatus further comprises:

a type adding unit configured to execute generating an addition type information item in response to the message type addition request;

the message type group updating unit is configured to update the current message type group based on the newly added type information item to obtain an updated message type group;

a client update information generation unit configured to perform generation of client update information based on the updated message type group;

and the client updating information issuing unit is configured to execute issuing the client updating information.

the first request response unit includes:

a third obtaining unit configured to perform, in response to the aggregate message obtaining request, obtaining a target aggregate message corresponding to the request object based on the object identifier;

a consistency comparison unit configured to perform consistency comparison on the version information of the request client and the version information of the target client under the condition that the target aggregated message includes at least one newly added aggregated message of a newly added type; the target client is used for receiving the newly added aggregation message;

an update information transmission unit configured to perform transmission of client update information in a case where the result of the comparison indicates that the version information of the requesting client is inconsistent with the version information of the target client;

an information determining unit configured to perform determining a message identifier of the newly added aggregated message and a message type of the newly added aggregated message;

a second sending unit, configured to execute sending the newly added aggregated message, the message identifier of the newly added aggregated message, and the message type of the newly added aggregated message to the updated client.

In an exemplary embodiment, the second request response unit includes:

the data sharing interface calling unit is configured to execute a data acquisition request responding to the associated page triggered based on the newly added aggregation message and call a data sharing interface; the data acquisition request comprises a message identifier of the newly added aggregation message and a message type of the newly added aggregation message;

the first acquisition unit includes:

a second accessing unit configured to access a second data storage table corresponding to the message type of the newly added aggregated message based on the data sharing interface;

a second searching unit configured to perform searching for second page data of an associated page corresponding to the message identifier of the newly added aggregation message in the second data storage table;

a second page data acquisition unit configured to perform acquisition of the second page data.

In an exemplary embodiment, the apparatus further comprises:

the data rendering unit is configured to render the display form of the page data in the associated page to obtain rendered page data;

a presentation instruction generation unit configured to execute generation of an associated page presentation instruction based on the rendered page data; and the associated page display instruction is used for instructing the requesting client to render and display the associated page based on the rendered page data.

According to a fourth aspect of the embodiments of the present disclosure, there is provided a page data display device, including:

an aggregate message acquisition request transmitting unit configured to perform transmitting an aggregate message acquisition request;

a first receiving unit configured to execute receiving a target aggregation message sent by a server based on the aggregation message acquisition request, a message identifier of the target aggregation message, and a message type of the target aggregation message; the target aggregation message is obtained by aggregating a plurality of single messages with the same message type;

a data acquisition request sending unit configured to execute a data acquisition request for sending an associated page corresponding to the target aggregation message;

a page data receiving unit configured to execute receiving page data of an associated page corresponding to the target aggregation message sent by the server; the page data is obtained based on a data sharing interface; the data sharing interface is used for acquiring associated page data corresponding to the aggregated messages of multiple message types;

a first presentation unit configured to perform presentation of the page data.

In an exemplary embodiment, the first presentation unit includes:

a second receiving unit configured to execute receiving an associated page display instruction generated based on the rendered page data and sent by the server; the rendered page data is obtained by rendering the display form of the page data in the associated page;

and the second presentation unit is configured to perform rendering presentation on the associated page based on the associated page presentation instruction.

the device further comprises:

and the third display unit is configured to perform display of the message text content information, the object identification information of the plurality of target objects, and the identification information of the target release information.

According to a fifth aspect of embodiments of the present disclosure, there is provided an electronic apparatus including: a processor; a memory for storing the processor-executable instructions; wherein the processor is configured to execute the instructions to implement the page data acquisition method or the page data presentation method as described above.

According to a fourth aspect of embodiments of the present disclosure, there is provided a computer-readable storage medium, in which instructions, when executed by a processor of a server, enable the server to perform the page data acquisition method, or the page data presentation method, as described above.

According to a fifth aspect of the embodiments of the present disclosure, there is provided a computer program product, the computer program product comprising a computer program, the computer program being stored in a readable storage medium, from which at least one processor of a computer device reads and executes the computer program, so that the device executes the above-mentioned page data acquisition method or page data presentation method.

The technical scheme provided by the embodiment of the disclosure at least brings the following beneficial effects:

the method comprises the steps of responding to an aggregation message acquisition request, and sending a target aggregation message, a message identifier and a message type to a request client; responding to a data acquisition request of the associated page corresponding to the target aggregation message, and calling a data sharing interface; then, transmitting the message identification and the message type into a data sharing interface; and acquiring page data of an associated page corresponding to the target aggregation message based on the data sharing interface of the transmitted message identifier and the message type. According to the method and the device, for the target aggregated messages of different message types, the page data of the corresponding associated page can be acquired through the same data sharing interface, the problem of expansion of the data interface caused by setting the corresponding data interface for different message types is avoided, the stability of the server is improved, and the development efficiency of the server is improved.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and, together with the description, serve to explain the principles of the disclosure and are not to be construed as limiting the disclosure.

FIG. 1 is a schematic diagram of an implementation environment shown in accordance with an exemplary embodiment.

FIG. 2 is a flowchart illustrating a method for page data acquisition, according to an example embodiment.

Fig. 3 is a flowchart illustrating a method for obtaining aggregated messages according to an example embodiment.

FIG. 4 is a flowchart illustrating a method for page data acquisition, according to an example embodiment.

Fig. 5 is a flowchart illustrating a method for acquiring an add-on aggregation message according to an exemplary embodiment.

Fig. 6 is a flowchart illustrating a method for acquiring associated page data of a newly added aggregate message according to an exemplary embodiment.

FIG. 7 is a flowchart illustrating a method for page rendering presentation according to an example embodiment.

FIG. 8 is a flowchart illustrating a method for presenting page data, according to an example embodiment.

FIG. 9 is a flowchart illustrating another method of page rendering presentation, according to an example embodiment.

FIG. 10 is a diagram illustrating a page data acquisition framework, according to an exemplary embodiment.

Fig. 11 is a block diagram illustrating a page data acquisition apparatus according to an exemplary embodiment.

Fig. 12 is a block diagram illustrating a page data presentation apparatus according to an exemplary embodiment.

FIG. 13 is a block diagram illustrating an electronic device for page data presentation in accordance with an exemplary embodiment.

FIG. 14 is a block diagram illustrating an electronic device for page data acquisition in accordance with an exemplary embodiment.

Detailed Description

In order to make the technical solutions of the present disclosure better understood by those of ordinary skill in the art, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below with reference to the accompanying drawings.

It should be noted that the terms "first," "second," and the like in the description and claims of the present disclosure and in the above-described drawings are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the disclosure described herein are capable of operation in sequences other than those illustrated or otherwise described herein. The implementations described in the exemplary embodiments below are not intended to represent all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present disclosure, as detailed in the appended claims.

It should be noted that, the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data for presentation, analyzed data, etc.) referred to in the present disclosure are information and data authorized by the user or sufficiently authorized by each party.

Referring to fig. 1, a schematic diagram of an implementation environment provided by an embodiment of the disclosure is shown, where the implementation environment may include: at least one first terminal 110 and a second terminal 120, the first terminal 110 and the second terminal 120 being capable of data communication through a network.

Specifically, the first terminal 110 may send an aggregate message acquisition request to the second terminal 120, and the second terminal 120 may return a corresponding aggregate message to the first terminal 110 according to the aggregate message acquisition request; the first terminal 110 may trigger the associated page data obtaining request based on the aggregation message, and the second terminal 120 may call the associated page data obtaining interface, obtain the associated data of the corresponding associated page, and return the associated data to the first terminal 110.

The first terminal 110 may communicate with the second terminal 120 based on a Browser/Server mode (Browser/Server, B/S) or a Client/Server mode (Client/Server, C/S). The first terminal 110 may include: the physical devices may also include software running in the physical devices, such as application programs and the like. The operating system running on the first terminal 110 in the embodiment of the present disclosure may include, but is not limited to, an android system, an IOS system, linux, windows, and the like.

The second terminal 120 and the first terminal 110 may establish a communication connection through a wired or wireless connection, and the second terminal 120 may include an independently operating server, or a distributed server, or a server cluster composed of multiple servers, where the server may be a cloud server.

In order to solve the problem of instability of a server caused by expansion of a data interface in the related art, an embodiment of the present disclosure provides a page data obtaining method, which may be used in a second terminal in fig. 1, please refer to fig. 2, and the method may include:

s210, responding to an aggregation message acquisition request, and sending a target aggregation message, a message identifier of the target aggregation message and a message type of the target aggregation message to a request client; the target aggregation message is obtained by aggregating a plurality of single messages with the same message type.

In a specific embodiment, the aggregated message may be a message obtained by aggregating a plurality of single messages having the same message type, that is, one aggregated message includes a plurality of messages, so that each aggregated message may correspond to one associated page, and the associated page may be used to show details of the plurality of messages included in the aggregated message.

Specifically, the message identifier of the target aggregated message may be information capable of uniquely identifying the target aggregated message, and specifically may be description information of the target aggregated message or number information of the target aggregated message. Further, the message type of the target aggregated message may be added, deleted, or modified according to a specific implementation scenario, and the message type includes but is not limited to a like type, a favorite type, and a stamp-by-stamp type. In addition, the message type of the target aggregated message coincides with the message types of the plurality of messages contained therein. The sending target aggregation message may be directly displayed in the message page of the requesting client, but the message identifier and the message type of the target aggregation message may not be directly displayed in the message page of the requesting client, but are implicit in the target aggregation message, and when corresponding operation is triggered based on the target aggregation message subsequently, the message identifier and the message type of the target aggregation message are automatically carried.

In a specific embodiment, when a request object triggers a message page access request based on a requesting client, the client may generate a corresponding aggregated message acquisition request based on the page access request because the message page may include aggregated messages; when receiving the corresponding target aggregate message, the requesting client can render the message page to display the target aggregate message. Specifically, one aggregate message in the message page may be "user a and 18 other users like user a approve your work", so that it can be stated that the aggregate message includes 18 single messages of the type of approval; the message type of the aggregated message is also of the like type.

S220, responding to a data acquisition request of the associated page corresponding to the target aggregation message, and calling a data sharing interface; the data acquisition request comprises the message identification and the message type; the data sharing interface is used for acquiring associated page data corresponding to the aggregation messages of multiple message types.

In an optional embodiment, the associated page corresponding to the target aggregated message may be a page for displaying the detail information of the target aggregated message, and the detail information of the target aggregated message may include message contents of each single message included in the target aggregated message, and/or an interaction object corresponding to each single message, which may specifically be a user.

In a specific embodiment, the data sharing interface is an interface for acquiring the associated page data of the different types of aggregation messages, that is, the acquisition of the associated page data of the different types of aggregation messages can be realized based on the data sharing interface without passing through other interfaces.

And S230, transmitting the message identification and the message type into the data sharing interface.

S240, based on the transmitted message identification and the data sharing interface of the message type, acquiring page data of an associated page corresponding to the target aggregation message.

In order to clarify the associated page data acquisition method, corresponding parameters, specifically a message identifier and a message type of the target aggregation message, need to be transmitted into the data sharing interface, so that the data sharing interface can acquire corresponding associated page data from a corresponding data storage table based on the message identifier and the message type.

According to the method and the device, for the target aggregated messages of different message types, the page data of the corresponding associated page can be acquired through the same data sharing interface, the problem of expansion of the data interface caused by setting the corresponding data interface for different message types is avoided, the stability of the server is improved, and the development efficiency of the server is improved.

In a specific embodiment, the aggregate message acquisition request includes an object identifier of a request object; reference is thus made to fig. 3, which illustrates an aggregated message retrieval method, which may include:

and S310, responding to the aggregation message acquisition request, and calling a message data acquisition interface.

S320, transmitting the object identification of the request object into the message data acquisition interface.

S330, based on the message data acquisition interface which has transmitted the object identification, acquiring a plurality of messages of the request object and message types of the plurality of messages.

And S340, aggregating the messages belonging to the same message type based on the message types of the plurality of messages to obtain at least one target aggregated message.

And S350, generating a message identifier corresponding to the at least one target aggregation message.

S360, the at least one target aggregation message, the message identification of the at least one target aggregation message and the message type of the at least one target aggregation message are sent to the request client.

Further, the message data obtaining interface may also be a shared message data obtaining interface, which may be configured to obtain messages corresponding to different objects, and specifically, the message data obtaining interface may send the object identifier of the request object into the message data obtaining interface, so that the message data obtaining interface searches the message storage table for multiple messages and corresponding message types corresponding to the object identifier of the request object, where each message and the message type of the message in the message storage table may be stored correspondingly. And acquiring a plurality of messages corresponding to the object identifier, and performing aggregation operation on the plurality of messages of the same type to obtain corresponding target aggregated messages, wherein the message type of the target aggregated messages can be determined based on the message type of the single message contained in the target aggregated messages. In addition, the message identification for the target aggregated message may be generated and assigned by the server when the corresponding target aggregated message is generated.

In an optional embodiment, when the target aggregation message is generated, associated page data corresponding to the target aggregation message may be generated correspondingly, a corresponding relationship between the target aggregation message and the associated page data is established, and the associated page data is stored in a data storage table corresponding to a corresponding message type.

In another optional embodiment, the message aggregation may be performed each time an aggregated message obtaining request is received, and after each time an aggregated message obtaining request is received, when an aggregated message of a target message type has been generated before, whether a new message of the target message type exists may be searched in the message storage table; when the new message of the target message type exists, the target aggregation message can be directly updated based on the new message, and the associated page data corresponding to the target aggregation message is correspondingly updated.

Therefore, when a plurality of messages of the request object are acquired based on the object identification of the request object, the messages of the same type are aggregated, and the messages are displayed to the user in the aggregated message form, so that the message display efficiency is improved, and the problem that a plurality of messages of the same type occupy a message display page is avoided.

In an optional embodiment, the associated page data of the target aggregation message can be acquired through the data sharing interface with the incoming related parameters; referring specifically to fig. 4, a method for acquiring page data is shown, where the method may include:

and S410, accessing a first data storage table corresponding to the message type based on the data sharing interface.

S420, searching first page data of the associated page corresponding to the message identification in the first data storage table.

S430, acquiring the first page data.

The associated page data of the aggregated messages of different message types are stored in different data storage tables, so that the data sharing interface can determine a corresponding first data storage table based on the incoming message type, and then determine corresponding first page data according to the incoming message identifier.

Accessing a corresponding data storage table according to the message type in the incoming data sharing interface, and searching corresponding page data based on the message identifier; the data sharing interface can access different data storage tables according to different transmitted message types, and data access interfaces corresponding to different message types do not need to be set, so that the data acquisition efficiency can be improved.

In an optional embodiment, when there is a new type of message, generating corresponding client update information may specifically include: responding to the message type adding request, and generating an adding type information item; updating the current message type group based on the newly added type information item to obtain an updated message type group; generating client update information based on the updated set of message types; and issuing the client updating information.

Therefore, when a newly added type message exists, the client updating information is correspondingly generated and is issued to the client, so that the client can be updated in time based on the client updating information, the newly added type message is received based on the updated client, and the convenience of information receiving is improved.

In a specific embodiment, the aggregate message acquisition request includes an object identifier of a request object and version information of the request client; when a newly added type aggregation message exists, the corresponding newly added aggregation message can be returned to the request client; referring specifically to fig. 5, a method for acquiring a new aggregation message is shown, where the method may include:

s510, in response to the aggregate message acquisition request, acquiring a target aggregate message corresponding to the request object based on the object identification.

S520, under the condition that the target aggregation message comprises at least one newly added aggregation message of a newly added type, carrying out consistency comparison on the version information of the request client and the version information of the target client; the target client is used for receiving the newly added aggregation message.

S530, under the condition that the consistency ratio indicates that the version information of the request client is inconsistent with the version information of the target client, the client updating information is sent.

S540, determining the message identification of the newly added aggregation message and the message type of the newly added aggregation message.

And S550, sending the newly added aggregation message, the message identifier of the newly added aggregation message and the message type of the newly added aggregation message to the updated client.

Specifically, the target client refers to a client capable of receiving and presenting the newly added aggregated message, and generally, when there is a newly added aggregated message of a newly added type, the newly added aggregated message may be caused by a version update of the client. For example, the updated target client has a new function of "favorites" online, so that a newly added aggregate message of the favorites type is generated; if the client is not updated by the request object, the newly added aggregation message of the collection type may not be received, so that the comprehensive aggregation information can be obtained by updating the client.

It should be noted that the updating of the client does not bring about the updating of the data acquisition mode of the associated page, that is, the data acquisition request of the associated page is initiated based on the updated target client, which is also realized by calling the data sharing interface, and the data acquisition modes of the updated target client and the request client before updating for the aggregated information associated page are consistent. Therefore, the acquisition mode of the associated page of the newly added aggregation message is imperceptible to the client, and the client does not need to adjust the acquisition mode of the associated page data of the newly added aggregation message due to the newly added aggregation message. Therefore, under the condition that the message type is newly added, when the request object requests the aggregation message, the corresponding newly added aggregation message is returned to the client, the newly added message type is only needed to be realized at the server side and is irrelevant to the client, and the development efficiency is further improved.

In an embodiment, please refer to fig. 6, which illustrates a method for acquiring associated page data of a newly added aggregation message, where the method may include:

s610, responding to a data acquisition request of the associated page triggered based on the newly added aggregation message, and calling a data sharing interface; the data acquisition request comprises the message identification of the newly added aggregation message and the message type of the newly added aggregation message.

And S620, accessing a second data storage table corresponding to the message type of the newly added aggregation message based on the data sharing interface.

S630, looking up second page data of the associated page corresponding to the message identification of the newly added aggregation message in the second data storage table.

And S640, acquiring the second page data.

When a request object initiates a request for acquiring a related page of a newly added aggregated message, a message identifier and a message type carried in the request are issued by a server, and a client only needs to trigger based on the newly added aggregated message without other operations, so that the client is unaware of the newly added aggregated message and can automatically realize the method, a set of processing method for accessing the newly added interface is avoided being additionally arranged at the client, the processing flow of the client is simplified, and the development efficiency is improved.

In an alternative embodiment, please refer to fig. 7, which illustrates a page rendering presentation method, which may include:

and S710, rendering the display form of the page data in the associated page to obtain rendered page data.

S720, generating a related page display instruction based on the rendered page data; and the associated page display instruction is used for instructing the requesting client to render and display the associated page based on the rendered page data.

Because the page data may include the detail information of the aggregated message, specifically, the detail information may include message content of each single message, and/or an interactive object corresponding to each single message, rendering the presentation form of the page data in the associated page may include: the method comprises the steps of obtaining head portrait information, object name information, single message content, file information and the like of each interactive object, and filling the obtained information into corresponding display templates, so that data rendering of a server side is realized. And sending the rendered page data to the client so that the client renders and displays the corresponding page data. Data required by data rendering is filled into the display template to form corresponding rendered page data, so that the flexibility of data rendering is improved; in addition, the client side carries out page rendering based on rendered page data, and therefore page rendering efficiency is improved.

Referring to fig. 8, a method for displaying page data according to the present disclosure is shown, where the method is applicable to the first terminal in fig. 1, and the method specifically includes:

and S810, sending an aggregation message acquisition request.

S820, a receiving server acquires a target aggregation message sent by a request based on the aggregation message, a message identifier of the target aggregation message, and a message type of the target aggregation message; the target aggregation message is obtained by aggregating a plurality of single messages with the same message type.

And S830, sending a data acquisition request of the associated page corresponding to the target aggregation message.

S840, receiving page data of an associated page corresponding to the target aggregation message sent by the server; the page data is obtained based on a data sharing interface; the data sharing interface is used for acquiring associated page data corresponding to the aggregation messages of multiple message types.

And S850, displaying the page data.

The aggregate message obtaining request may be that when the request client receives a request object and triggers a message page access request based on the request client, a specific triggering operation may be to open a message page or refresh the message page, and the like. The data obtaining request of the associated page of the target aggregate message may be generated by the request client in response to a trigger operation of the request object on the target aggregate message, and the specific trigger operation may be to click the target aggregate message shown in the message page.

For the specific implementation details of page data acquisition, reference may be made to the above contents of this embodiment, which have corresponding implementation effects, and details are not described herein again.

In an embodiment, please refer to fig. 9, which illustrates another page rendering display method, which may include:

s910, receiving a related page display instruction which is sent by the server and generated based on the rendered page data; and rendering the rendered page data by rendering the display form of the page data in the associated page.

And S920, rendering and displaying the associated page based on the associated page display instruction.

When the request object clicks the target aggregation message displayed in the message page, the request object correspondingly jumps to an associated page corresponding to the target aggregation message, and the associated page can be obtained by rendering the page through an associated page display instruction sent by the client based on the server.

For the specific implementation details of page rendering, reference may be made to the above contents of this embodiment, which have corresponding implementation effects, and details are not described herein again.

In an optional embodiment, the target aggregation message is obtained by performing the same operation on the target publishing information based on a plurality of objects; the target aggregation message comprises message text content information, object identification information of a plurality of target objects and identification information of the target release information; correspondingly, when displaying the target aggregated message, the method specifically includes:

In one embodiment, user a approves your work, you will receive a message: "user a likes your work", the head portrait of user a is shown on the left side of the message, and the front cover picture of the work is shown on the right side of the message. If a plurality of users approve your same work, a common message implementation mode is to aggregate a plurality of messages, specifically, "user a approves your work for 18 users", and similarly, the left side of the message content is an aggregated head portrait of a plurality of people, and the right side of the message content is a cover picture of the work. The aggregate message may be divided into various types depending on the type of message, and clicking on the number 18 will go to a secondary page showing all user information that favors the work.

In the following, a specific example is used to describe the implementation method of the present disclosure, first, a set of self-defined enumerated biztypes is maintained to represent service types, and each bizType corresponds to an aggregated message type corresponding to a message page. Referring to fig. 10, when a message page issues a message Feed stream, we issue secondary page hyperlinks of each aggregated message together, and distinguish with bizType. The specific hyperlinks issued are as follows:

linkUrl:kwai://secondPageLinkUrl

bizType=1

the client side is provided with a set of kwai protocol, can know an actually corresponding server interface, such as/rest/n/notify/listSecondPageUsers, according to linkUrl, requests the interface and takes a parameter bizType on a hyperlink to acquire secondary page data, and a universal secondary page interface mode is achieved. When the aggregation message type needs to be newly added, only different bizType enumerations need to be defined by the server and issued to the client in the message page, the client does not need to modify codes, automatic identification can be achieved, and development efficiency is effectively improved. For the server, only a general secondary page interface/rest/n/notify/listSecondPageUsers needs to be maintained, and the problem of expansion of an API (application program interface) is solved.

a. User entry message page example:

1. the user clicks the message tab, and the client requests the server message page interface (/ rest/n/notify) to acquire the message data.

2. The server side obtains the message owned by the current user from the database related to the message, and sends the message to the client side after data analysis, filtration and rendering, wherein the sent data is as follows:

{

"result":1,// indicates that the current request was successful

"notifies":[

{ },// common message data

{// aggregate messages, i.e. message types where there is a secondary page

1234321,// message id for each message

"headUrls" [ { }, { } ]// multiple avatars on the left side of the aggregated message

' notifyText '. The 18-bit users like Zhang III approve your work '/the specific content of the message

"Right icon": the cover drawing of the work on the right side of the message,// and

"linkUrl":"kwai://secondPageLinkUrl

bizType =1 "// click-through to jump link to secondary page

},

{ }// remaining common message data

]

}

3. The server maintains a set of mappings of enumerated bizTypes of business scenario types, as follows:

{

"unknown":0,// default

"Photolike":1,// works praise

"commentLike":2,// praise

3// stamping one stamp (urging update)

}

4. From the return of step 3, bizType =1 can be seen, i.e. an aggregated message that a work is complied with, and a click (linkUrl) can be entered into a secondary page to obtain all user information that the count site approves the current work.

5. After the client receives the message page data returned by the server in the step 2, when the user really clicks a certain aggregation message, the client makes use of the value kwai:// second PageLinkUrl in linkUrl

bizType =1 will request a secondary page data acquisition interface: /rest/n/notify/listSecondPageUsers, and the current bizType =1, and the parameter information of notifyId is imported.

6. In a secondary page interface/rest/n/notify/listSecondPageUsers of the server, a type of a message of a works praise is known according to a currently received parameter bizType =1, so that secondary page data information is obtained from a photo _ like table of a related database table of the works praise according to the notifyId, and the secondary page data is returned to the client after rendering, as shown in the following:

{

"result" 1, success

"users" [ { user1}, { user2}, { user3}, { user4} ]// the relevant user information of the secondary page, that is, all user information shown to have approved for the current work

}

b. New message type example:

1. adding a new message type, for example, a photo collect message type of the collection of the work, the bizType is as follows:

{

"unknown":0,// default

"Photolike":1,// works praise

"commentLike":2,// praise

"missU":3,// poke one stamp (urging update)

"PhoCollect": 4// Collection of work

}

2. When the user obtains the message page data, if the current user has the aggregated message of the collected works, the return format is as follows:

{

"result":1,// indicates that the current request was successful

"notifies":[

{ },// common message data

{// aggregate like messages, i.e. message types where secondary pages exist

1234321,// message id for each message

"linkUrl":"kwai://secondPageLinkUrl

bizType =1 "// click-through to jump link to secondary page

},

{ },// remaining common message data

{// aggregate favorites messages, i.e. message types where there is a secondary page

345234,// message id for each message

' notifyText ' that 12 users such as king five collect your work '/the specific content of the message

"linkUrl":"kwai://secondPageLinkUrl

bizType =4 "// click into jump link of secondary page

},

]

}

3. When the user clicks the aggregation message of the work collection, the execution process is consistent with the secondary page data acquisition process of clicking the favor of the work, and the user only needs to access a secondary page data acquisition interface/rest/n/notify/listSeconddPageUsers and upload the parameter information of the current bizType =4 and notify Id.

4. And the server acquires the required user information of the secondary page from the user's work collection database table according to bizType =4, similar to the step 6.

From the above process, when a new service scene type is added, the client does not need to have any change of the code logic level, so the client can default to support without development, and has good universality.

Therefore, the method and the device distinguish various different aggregated message service scenes through the bizType and provide a uniform secondary page data interface; when the aggregation message type is newly added, the client does not need to be developed, is not aware, is directly supported by default, and the required iteration speed is increased; in addition, all the secondary page data acquisition interfaces are converged to one API interface through the bizType, so that the problem of expansion of the API interface is solved while the maintenance cost of the server is reduced, and the stability of the service is maintained.

Fig. 11 is a block diagram illustrating a page data acquisition apparatus according to an exemplary embodiment. Referring to fig. 11, the apparatus includes:

a first request responding unit 1110, configured to perform sending, to a requesting client, a target aggregation message, a message identifier of the target aggregation message, and a message type of the target aggregation message in response to an aggregation message obtaining request; the target aggregation message is obtained by aggregating a plurality of single messages with the same message type;

a second request response unit 1120, configured to execute a data acquisition request in response to the associated page corresponding to the target aggregation message, and invoke a data sharing interface; the data acquisition request comprises the message identification and the message type; the data sharing interface is used for acquiring associated page data corresponding to the aggregated messages of multiple message types;

a first import unit 1130 configured to perform import of the message identification and the message type into the data sharing interface;

a first obtaining unit 1140 configured to perform obtaining page data of an associated page corresponding to the target aggregated message based on the data sharing interface having the message identifier and the message type transmitted thereto.

the first request response unit 1110 includes:

In an exemplary embodiment, the first obtaining unit 1140 includes:

In an exemplary embodiment, the apparatus further comprises:

the first request response unit 1110 includes:

In an exemplary embodiment, the second request response unit 1120 includes:

the first obtaining unit 1140 includes:

In an exemplary embodiment, the apparatus further comprises:

Fig. 12 is a block diagram illustrating a page data presentation apparatus according to an exemplary embodiment. Referring to fig. 12, the apparatus includes:

an aggregated message acquisition request transmitting unit 1210 configured to perform transmitting an aggregated message acquisition request;

a first receiving unit 1220, configured to execute receiving a target aggregation message sent by a server based on the aggregation message acquisition request, a message identifier of the target aggregation message, and a message type of the target aggregation message; the target aggregation message is obtained by aggregating a plurality of single messages with the same message type;

a data acquisition request sending unit 1230 configured to execute a data acquisition request for sending an associated page corresponding to the target aggregation message;

a page data receiving unit 1240 configured to perform receiving page data of an associated page corresponding to the target aggregation message sent by the server; the page data is obtained based on a data sharing interface; the data sharing interface is used for acquiring associated page data corresponding to the aggregated messages of multiple message types;

a first presentation unit 1250 configured to perform presentation of the page data.

In an exemplary embodiment, the first presentation unit 1250 includes:

the device further comprises:

With regard to the apparatus in the above-described embodiment, the specific manner in which each module performs the operation has been described in detail in the embodiment related to the method, and will not be elaborated here.

In an exemplary embodiment, there is also provided a computer readable storage medium comprising instructions, which may alternatively be ROM, Random Access Memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, and the like; the instructions in the computer readable storage medium, when executed by a processor of an electronic device, enable the electronic device to perform any of the methods described above.

In an exemplary embodiment, there is also provided a computer program product comprising a computer program stored in a readable storage medium, from which at least one processor of a computer device reads and executes the computer program, causing the device to perform any of the methods described above.

Fig. 13 is a block diagram illustrating an electronic device for page data presentation, which may be a terminal, according to an exemplary embodiment, and an internal structure diagram thereof may be as shown in fig. 13. The electronic device comprises a processor, a memory, a network interface, a display screen and an input device which are connected through a system bus. Wherein the processor of the electronic device is configured to provide computing and control capabilities. The memory of the electronic equipment comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of an operating system and computer programs in the non-volatile storage medium. The network interface of the electronic device is used for connecting and communicating with an external terminal through a network. The computer program is executed by a processor to implement a page data presentation method. The display screen of the electronic equipment can be a liquid crystal display screen or an electronic ink display screen, and the input device of the electronic equipment can be a touch layer covered on the display screen, a key, a track ball or a touch pad arranged on the shell of the electronic equipment, an external keyboard, a touch pad or a mouse and the like.

Fig. 14 is a block diagram illustrating an electronic device for page data acquisition, which may be a server, according to an exemplary embodiment, and an internal structure diagram thereof may be as shown in fig. 14. The electronic device includes a processor, a memory, and a network interface connected by a system bus. Wherein the processor of the electronic device is configured to provide computing and control capabilities. The memory of the electronic equipment comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of an operating system and computer programs in the non-volatile storage medium. The network interface of the electronic device is used for connecting and communicating with an external terminal through a network. The computer program is executed by a processor to implement a page data acquisition method.

Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This application is intended to cover any variations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.

It will be understood that the present disclosure is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims

1. A page data acquisition method is characterized by comprising the following steps:

2. The method according to claim 1, wherein the aggregate message acquisition request includes an object identifier of a request object;

3. The method according to claim 1, wherein the obtaining page data of an associated page corresponding to the target aggregated message based on the data sharing interface having the message identifier and the message type, comprises:

and acquiring the first page data.

4. The method of claim 1, further comprising:

generating client update information based on the updated set of message types;

and issuing the client updating information.

5. The method according to claim 4, wherein the aggregate message acquisition request includes an object identifier of a request object and version information of the request client;

6. The method of claim 5, wherein invoking a data sharing interface in response to a data fetch request for an associated page corresponding to the target aggregate message comprises:

and acquiring the second page data.

7. The method of claim 1, further comprising:

8. A page data display method is characterized by comprising the following steps:

sending an aggregation message acquisition request;

and displaying the page data.

9. The method of claim 8, wherein the exposing the page data comprises:

10. The method of claim 8, wherein the target aggregated message is obtained by performing the same operation on target publishing information based on a plurality of objects; the target aggregation message comprises message text content information, object identification information of a plurality of target objects and identification information of the target release information;

the method further comprises the following steps:

11. A page data acquisition apparatus, comprising:

12. The apparatus according to claim 11, wherein the aggregate message acquisition request includes an object identifier of a request object;

the first request response unit includes:

13. The apparatus of claim 11, wherein the first obtaining unit comprises:

14. The apparatus of claim 11, further comprising:

15. The apparatus according to claim 14, wherein the aggregate message acquisition request includes an object identifier of a request object and version information of the request client;

the first request response unit includes:

an update information transmission unit configured to perform transmission of the client update information in a case where the result of the comparison indicates that the version information of the requesting client is inconsistent with the version information of the target client;

16. The apparatus of claim 15, wherein the second request response unit comprises:

the first acquisition unit includes:

17. The apparatus of claim 11, further comprising:

18. A page data presentation apparatus, comprising:

a first presentation unit configured to perform presentation of the page data.

19. The apparatus of claim 18, wherein the first presentation unit comprises:

20. The apparatus of claim 18, wherein the target aggregated message is obtained by performing the same operation on target publishing information based on a plurality of objects; the target aggregation message comprises message text content information, object identification information of a plurality of target objects and identification information of the target release information;

the device further comprises:

21. An electronic device, comprising:

a processor;

a memory for storing the processor-executable instructions;

wherein the processor is configured to execute the instructions to implement the page data acquisition method of any one of claims 1 to 7 or the page data presentation method of any one of claims 8 to 10.

22. A computer-readable storage medium, wherein instructions in the computer-readable storage medium, when executed by a processor of an electronic device, enable the electronic device to perform the page data acquisition method of any one of claims 1 to 7, or the page data presentation method of any one of claims 8 to 10.

23. A computer program product comprising computer programs/instructions, characterized in that said computer programs/instructions, when executed by a processor, implement the page data acquisition method of any one of claims 1 to 7 or the page data presentation method of any one of claims 8 to 10.