Page display methods, devices, servers, and storage media

Abstract

This application discloses a page display method, apparatus, server, and storage medium, belonging to the field of computer technology. The method includes: responding to a data acquisition request sent by a first terminal, determining a second format recognizable by the first terminal; acquiring first page data stored corresponding to a first page identifier and belonging to the first format from a first correspondence relationship, wherein the first page identifier is an identifier carried in the data acquisition request; if the second format differs from the first format, using a format conversion protocol to convert the first page data belonging to the first format to obtain first page data belonging to the second format; and sending the first page data belonging to the second format to the first terminal, which then renders the page corresponding to the first page identifier based on the first page data belonging to the second format. This application not only provides page display services for the terminal but also ensures page update efficiency.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a page display method, apparatus, server, and storage medium. Background Technology

[0002] With the continuous development of technology, various applications are emerging. These applications involve web pages, which need to be developed before the application can be released. However, after the application is released, it is often necessary to modify or add pages. According to the current page configuration method, the page needs to be redeployed to realize the modification or addition of pages, which is a cumbersome update process and has low page update efficiency. Summary of the Invention

[0003] This application provides a page display method, apparatus, server, and storage medium, which can provide page display services to terminals, facilitate the updating of page data in the first correspondence relationship, and ensure the efficiency of page updates. The technical solution is as follows:

[0004] On one hand, a page display method is provided, executed by a server, wherein the server stores a first correspondence between page identifiers and page data, and the page data belongs to a first format recognizable by the server, the method comprising:

[0005] In response to a data acquisition request sent by the first terminal, a second format recognizable by the first terminal is determined;

[0006] From the first correspondence, obtain the first page data that corresponds to the first page identifier and belongs to the first format, where the first page identifier is the identifier carried by the data acquisition request;

[0007] When the second format is different from the first format, a format conversion protocol is used to convert the first page data belonging to the first format to obtain the first page data belonging to the second format. The format conversion protocol is used to convert the page data from the first format to the second format.

[0008] The system sends first page data in the second format to the first terminal, which then renders the data based on the first page data in the second format to display the page corresponding to the first page identifier.

[0009] In one possible implementation, the method further includes:

[0010] Receive a data modification request sent by a second terminal, the data modification request carrying a second page identifier and second page data;

[0011] The second page data is converted to a format to obtain second page data in the first format.

[0012] Update the page data stored corresponding to the second page identifier to second page data belonging to the first format.

[0013] In another possible implementation, before receiving the data modification request sent by the second terminal, the method further includes:

[0014] Receive a data access request sent by the second terminal, wherein the data access request carries the second page identifier;

[0015] Query the page data stored corresponding to the second page identifier, and send the page data stored corresponding to the second page identifier to the second terminal;

[0016] The second terminal is used to display page data stored corresponding to the second page identifier; in response to a modification operation on the displayed page data, it modifies the displayed page data to obtain the second page data; and in response to a save instruction for the second page data, it sends the data modification request to the server.

[0017] In another possible implementation, the method further includes:

[0018] Receive a data addition request sent by a second terminal, the data addition request carrying a third page identifier and data to be added to the page;

[0019] The newly added page data is converted to a new page data in the first format;

[0020] The third page identifier is stored in correspondence with the newly added page data belonging to the first format.

[0021] In another possible implementation, after sending the first page data belonging to the second format to the first terminal, the method further includes:

[0022] When the page is displayed on the first terminal, in response to the update instruction for the page data corresponding to the first page identifier, the updated page data corresponding to the first page identifier is obtained;

[0023] The updated page data is converted using the aforementioned format conversion protocol to obtain updated page data belonging to the second format.

[0024] The updated page data in the second format is sent to the first terminal, which then renders the displayed page based on the updated page data in the second format.

[0025] In another possible implementation, the server further stores a second correspondence between terminal type, page identifier, and page data, wherein the page data corresponding to the terminal type belongs to a terminal-recognizable format of that terminal type; the second correspondence is stored by the server when converting the page data into a terminal-recognizable format belonging to that terminal type; the data acquisition request carries the terminal identifier of the first terminal; the step of determining the second format recognizable by the first terminal in response to the data acquisition request sent by the first terminal includes:

[0026] In response to a data acquisition request sent by the first terminal, the terminal type of the first terminal is determined based on the terminal identifier of the first terminal;

[0027] Based on the terminal type of the first terminal and the first page identifier, query the second correspondence;

[0028] If no page data corresponding to the terminal type and the first page identifier of the first terminal is found, a second format that the first terminal can recognize is determined.

[0029] In another possible implementation, when the second format differs from the first format, after using a format conversion protocol to convert the first page data belonging to the first format to obtain the first page data belonging to the second format, the method further includes:

[0030] The terminal type to which the first terminal belongs, the first page identifier, and the first page data belonging to the second format are stored accordingly to update the second correspondence.

[0031] In another possible implementation, after querying the second correspondence based on the terminal type of the first terminal and the first page identifier, the method further includes:

[0032] If page data corresponding to the terminal type of the first terminal and the first page identifier is found, the found page data is sent to the first terminal. The first terminal is used to render the page corresponding to the first page identifier based on the found page data.

[0033] In another possible implementation, the server further stores a third correspondence between terminal identifiers and formats, wherein the format corresponding to the terminal identifier is a format recognizable by the terminal indicated by the terminal identifier, and the data acquisition request also carries the terminal identifier of the first terminal; determining the second format recognizable by the first terminal includes:

[0034] By querying the third correspondence, the second format corresponding to the terminal identifier of the first terminal is obtained.

[0035] On the other hand, a page display device is provided, disposed in a server, the server storing a first correspondence between page identifiers and page data, the page data belonging to a first format recognizable by the server, the device comprising:

[0036] The determination module is used to determine a second format that the first terminal can recognize in response to a data acquisition request sent by the first terminal;

[0037] The acquisition module is used to acquire first page data that corresponds to the first page identifier and belongs to the first format from the first correspondence relationship, wherein the first page identifier is the identifier carried by the data acquisition request;

[0038] The conversion module is used to convert the first page data belonging to the first format to the second format by using a format conversion protocol when the second format is different from the first format. The format conversion protocol is used to convert the page data from the first format to the second format.

[0039] The sending module is used to send first page data belonging to the second format to the first terminal, and the first terminal is used to render based on the first page data belonging to the second format to display the page corresponding to the first page identifier.

[0040] In one possible implementation, the device further includes:

[0041] The receiving module is used to receive a data modification request sent by the second terminal, wherein the data modification request carries a second page identifier and second page data;

[0042] The conversion module is also used to convert the format of the second page data to obtain second page data belonging to the first format;

[0043] The storage module is used to update the page data stored corresponding to the second page identifier to second page data belonging to the first format.

[0044] In another possible implementation, the device further includes:

[0045] The receiving module is further configured to receive a data access request sent by the second terminal, the data access request carrying the second page identifier;

[0046] The query module is used to query the page data stored corresponding to the second page identifier and send the page data stored corresponding to the second page identifier to the second terminal.

[0047] The second terminal is used to display page data stored corresponding to the second page identifier; in response to a modification operation on the displayed page data, it modifies the displayed page data to obtain the second page data; and in response to a save instruction for the second page data, it sends the data modification request to the server.

[0048] In another possible implementation, the device further includes:

[0049] The receiving module is used to receive a data addition request sent by the second terminal, wherein the data addition request carries a third page identifier and new page data;

[0050] The conversion module is also used to convert the format of the newly added page data to obtain newly added page data belonging to the first format;

[0051] The storage module is used to store the third page identifier and the newly added page data belonging to the first format.

[0052] In another possible implementation, the acquisition module is further configured to, when the first terminal displays the page, acquire the updated page data corresponding to the first page identifier in response to an update instruction for the page data corresponding to the first page identifier;

[0053] The conversion module is further configured to use the format conversion protocol to perform format conversion on the updated page data to obtain updated page data belonging to the second format;

[0054] The sending module is further configured to send updated page data belonging to the second format to the first terminal, and the first terminal is configured to render based on the updated page data belonging to the second format to update the displayed page.

[0055] In another possible implementation, the server further stores a second correspondence between terminal type, page identifier, and page data, wherein the page data corresponding to the terminal type belongs to a terminal-recognizable format of that terminal type; the second correspondence is stored by the server when converting the page data into a terminal-recognizable format belonging to the terminal type; the data acquisition request carries the terminal identifier of the first terminal; the determining module is used to respond to the data acquisition request sent by the first terminal, determine the terminal type to which the first terminal belongs based on the terminal identifier of the first terminal; query the second correspondence based on the terminal type to which the first terminal belongs and the first page identifier; and determine the second format recognizable by the first terminal if no page data corresponding to the terminal type to which the first terminal belongs and the first page identifier is found.

[0056] In another possible implementation, the device further includes:

[0057] The storage module is used to store the terminal type to which the first terminal belongs, the first page identifier, and the first page data belonging to the second format, so as to update the second correspondence.

[0058] In another possible implementation, the sending module is further configured to send the queried page data to the first terminal when page data corresponding to the terminal type to which the first terminal belongs and the first page identifier is found. The first terminal is configured to render based on the queried page data to display the page corresponding to the first page identifier.

[0059] In another possible implementation, the server also stores a third correspondence between terminal identifiers and formats, wherein the format corresponding to the terminal identifier is a format recognizable by the terminal indicated by the terminal identifier, and the data acquisition request also carries the terminal identifier of the first terminal; the determining module is used to query the third correspondence to obtain the second format corresponding to the terminal identifier of the first terminal.

[0060] On the other hand, a server is provided, the server including a processor and a memory, the memory storing at least one computer program, the at least one computer program being loaded and executed by the processor to perform the operations performed by the page display method as described above.

[0061] On the other hand, a computer-readable storage medium is provided that stores at least one computer program, which is loaded and executed by a processor to perform the operations performed by the page display method as described above.

[0062] In another aspect, a computer program product is provided, comprising a computer program that, when executed by a processor, performs the operations performed by the page display method described above.

[0063] This application provides a novel page deployment method. The server stores each page's data in a first format that the server can recognize, corresponding to page identifiers. The server is also configured with a format conversion protocol that matches the first format. When a terminal accesses a page, the server queries the first correspondence and, in conjunction with the format conversion protocol, provides the terminal with page data in a recognizable format. The terminal then displays the page, enabling the server to provide page display services to the terminal. Furthermore, the first correspondence between the stored page identifiers and page data has good scalability and facilitates updates to the page data in the first correspondence, ensuring efficient page updates. Attached Figure Description

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

[0065] Figure 1 This is a schematic diagram of the structure of an implementation environment provided in an embodiment of this application;

[0066] Figure 2 This is a flowchart of a page display method provided in an embodiment of this application;

[0067] Figure 3 This is a flowchart of another page display method provided in the embodiments of this application;

[0068] Figure 4 This is a flowchart of another page display method provided in the embodiments of this application;

[0069] Figure 5 This is a flowchart of another page display method provided in the embodiments of this application;

[0070] Figure 6 This is a flowchart of another page display method provided in the embodiments of this application;

[0071] Figure 7 This is a schematic diagram of the structure of a page display device provided in an embodiment of this application;

[0072] Figure 8 This is a schematic diagram of another page display device provided in an embodiment of this application;

[0073] Figure 9 This is a schematic diagram of the structure of a server provided in an embodiment of this application. Detailed Implementation

[0074] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the implementation methods of this application will be further described in detail below with reference to the accompanying drawings.

[0075] The terms “first,” “second,” etc., used in this application may be used herein to describe various concepts, but unless otherwise specified, these concepts are not limited by these terms. These terms are used only to distinguish one concept from another. For example, without departing from the scope of this application, the first format may be referred to as the second format, and similarly, the second format may be referred to as the first format.

[0076] As used in this application, the terms "at least one," "multiple," "each," and "any" have the following meanings: at least one includes one, two, or more; multiple includes two or more; each refers to each of the corresponding multiple; and any refers to any one of the multiple. For example, multiple page data includes three page data items, where each refers to each of the three page data items, and any refers to any one of the three page data items, which could be the first page data item, the second page data item, or the third page data item.

[0077] It should be noted that all information involved in this application (including but not limited to page identifiers and page data) has been authorized by the user or by all parties in full, and the collection, use, and processing of such data must comply with the relevant laws, regulations, and standards of the relevant countries and regions. For example, the page data involved in this application was obtained with full authorization.

[0078] The page display method provided in this application embodiment can be executed by a server. Optionally, the server is a single server, a server cluster consisting of several servers, or a cloud computing service center.

[0079] Figure 1 This is a schematic diagram of an implementation environment provided in an embodiment of this application. See also... Figure 1 The implementation environment includes a first terminal 101 and a server 102. The first terminal 101 and the server 102 are connected via a wireless or wired network.

[0080] The first terminal 101 is used to access the page, and the server 102 is used to provide page services. The server 102 stores a first correspondence between page identifiers and page data. When the first terminal 101 accesses a certain page, it interacts with the server 102 to obtain the page data corresponding to the accessed page from the server 102, so that the first terminal 101 can render the page based on the page data.

[0081] Optionally, the page is a webpage or a page within a first application. When the page is a webpage, server 102 is a web server providing services to the webpage, and the first terminal 101 accesses the webpage through a browser and interacts with server 102. When the page is within a first application, server 102 is a server providing services to the first application, and the first terminal 101 accesses a specific page through the first application and interacts with server 102. Optionally, the first application can be any application, such as a social networking application, a shopping application, or a navigation application.

[0082] Optionally, the implementation environment also includes a second terminal 103, which is connected to the server 102 via a wireless or wired network. The second terminal 103 is used to update the page data stored in the server 102. The second terminal 103 can access the page data in the first correspondence stored in the server 102, and can interact with the server 102 to modify the page data in the first correspondence, or add page identifiers and corresponding page data to the first correspondence.

[0083] Optionally, the second terminal 103 installs a second application provided by the server 102. The second application can be any application, such as a page management application, like a skill management center application. Developers can interact with the server 102 through the skill management center application in the second terminal 103 to update the first correspondence stored by the server 102.

[0084] It should be noted that this application describes the case with the first terminal 101 for accessing the page and the second terminal 103 for managing the page data in the management server 102 being different. In another embodiment, the terminal for accessing the page and the page data in the management server 102 is the same terminal. For example, the first terminal 101 is used to access the page and the page data in the management server 102, or the second terminal 103 is used to access the page and the page data in the management server 102.

[0085] Figure 2 This is a flowchart of a page display method provided in an embodiment of this application, executed by a server, such as... Figure 2 As shown, the method includes:

[0086] 201. In response to the data acquisition request sent by the first terminal, the server determines a second format that the first terminal can recognize.

[0087] In this embodiment, the first terminal is a terminal accessing a page, and the server is a server providing page services. The server stores a first correspondence between page identifiers and page data. This first correspondence indicates the page data corresponding to each page identifier, that is, it indicates the page data corresponding to each page. In the first correspondence, the page data belongs to a first format recognizable by the server, so that the server can recognize the page data in the first correspondence.

[0088] In this embodiment of the application, when the first terminal accesses a certain page, it sends a data acquisition request to the server to request the page data corresponding to the accessed page from the server so that the page can be rendered based on the page data. After receiving the data acquisition request sent by the first terminal, the server needs to determine the format that the first terminal can recognize so that it can provide the first terminal with page data in a recognizable format in the future, ensuring that the page can be rendered normally in the future.

[0089] The page identifier can be represented in any form, for example, as a string. The second format is also arbitrary; the first terminal can recognize page data belonging to the second format, meaning it can render the page based on page data in the second format.

[0090] 202. The server retrieves the first page data, which corresponds to the first page identifier and belongs to the first format, from the first correspondence relationship. The first page identifier is the identifier carried in the data retrieval request.

[0091] In this embodiment, the first page identifier carried in the data acquisition request indicates the page that the first terminal requests to access, that is, the first terminal requests to acquire the page data corresponding to the first page identifier. The first correspondence stored by the server includes the page identifier and the corresponding page data, and the page data in the first correspondence belongs to the first format. After receiving the data acquisition request sent by the first terminal, the server queries the first correspondence based on the first page identifier carried in the data acquisition request, and can then obtain the first page data stored corresponding to the first page identifier and belonging to the first format.

[0092] 203. When the second format is different from the first format, the server uses a format conversion protocol to convert the first page data belonging to the first format to obtain the first page data belonging to the second format. The format conversion protocol is used to convert page data from the first format to the second format.

[0093] In this embodiment, the format recognizable by the terminal accessing the webpage may be the same as or different from the first format recognizable by the server. Since the page data stored on the server belongs to the first format, it is determined whether the second format recognizable by the first terminal is the same as the first format recognizable by the server. In case the first format and the second format are different, the page data requested by the first terminal is converted into the second format recognizable by the first terminal, so that the first terminal can subsequently recognize the page data and render the page, thereby ensuring that the first terminal can successfully access the webpage.

[0094] The format conversion protocol is used to convert the format of page data. This format conversion protocol can be any protocol, for example, the APL protocol.

[0095] 204. The server sends first page data in the second format to the first terminal, which then renders the first page data in the second format to display the page corresponding to the first page identifier.

[0096] In this embodiment of the application, after the server obtains the first page data requested by the first terminal and which belongs to the second format that the first terminal can recognize, it sends the first page data belonging to the second format to the first terminal so that the first terminal can recognize the first page data belonging to the second format and render the page corresponding to the first page identifier based on the first page data belonging to the second format, so as to ensure that the first terminal successfully accesses the webpage.

[0097] This application provides a novel page deployment method. The server stores each page's data in a first format that the server can recognize, corresponding to page identifiers. The server is also configured with a format conversion protocol that matches the first format. When a terminal accesses a page, the server queries the first correspondence and, in conjunction with the format conversion protocol, provides the terminal with page data in a recognizable format. The terminal then displays the page, enabling the server to provide page display services to the terminal. Furthermore, the first correspondence between the stored page identifiers and page data has good scalability and facilitates updates to the page data in the first correspondence, ensuring efficient page updates.

[0098] In the above Figure 2 Based on the embodiments shown, in this embodiment, in response to the page data update corresponding to the page displayed by the first terminal, the server will actively send the updated page data to the first terminal so that the first terminal can update the displayed page. For details of the process, please refer to the following embodiments.

[0099] Figure 3 This is a flowchart of a page display method provided in an embodiment of this application. The method is executed by a server and a first terminal, such as... Figure 3As shown, the method includes:

[0100] 301. In response to the data acquisition request sent by the first terminal, the server determines a second format that the first terminal can recognize.

[0101] In one possible implementation, the server also stores a third correspondence between terminal identifiers and formats, wherein the format corresponding to the terminal identifier is a format recognizable by the terminal indicated by the terminal identifier, and the data acquisition request also carries the terminal identifier of the first terminal; the process of determining the second format recognizable by the first terminal includes: querying the third correspondence to obtain the second format corresponding to the terminal identifier of the first terminal.

[0102] In this embodiment of the application, the third correspondence in the server indicates the formats that can be recognized by various terminals. When the data request sent by the first terminal to the server carries the terminal identifier of the first terminal, the server can determine the second format that the first terminal can recognize by querying the third correspondence based on the terminal identifier of the first terminal, so as to ensure the accuracy of the determined format.

[0103] In one possible implementation, the server stores a fourth correspondence between terminal types and formats, where the format corresponding to the terminal type is a format recognizable by the terminal belonging to that terminal type, and the data acquisition request also carries the terminal information of the first terminal; the process of determining the second format recognizable by the first terminal includes: classifying the terminal information of the first terminal to obtain the terminal type to which the first terminal belongs, and querying the fourth correspondence based on the terminal type to which the first terminal belongs to obtain the second format recognizable by the first terminal.

[0104] The terminal information is used to characterize the first terminal. For example, the terminal information includes the terminal manufacturer, terminal batch number, and terminal configuration information. In this embodiment, the terminal information represents the first terminal. By classifying the terminal information, the terminal type of the first terminal can be determined. Then, the fourth correspondence is queried to obtain the second format corresponding to the terminal type of the first terminal, which is the second format that the first terminal can recognize. Considering that terminals of the same type have the same recognizable format, a classification method is used to classify the terminal information of the first terminal to ensure the accuracy of the determined terminal type, thereby ensuring the accuracy of the determined second format.

[0105] In one possible implementation, step 301 includes: in response to an access operation to a certain page, the first terminal sends a data retrieval request to the server to request page data corresponding to the accessed page; the server receives the data retrieval request sent by the first terminal and, in response to the data retrieval request, determines a second format that the first terminal can recognize.

[0106] The page accessed by the first terminal is either a webpage accessed by the first terminal through a browser, or a page within an application accessed by the first terminal through an application.

[0107] 302. The server retrieves the first page data, which corresponds to the first page identifier and belongs to the first format, from the first correspondence relationship. The first page identifier is the identifier carried in the data retrieval request.

[0108] In this embodiment, the page data in the first correspondence is stored as independent static files. Each page data contains data used to render the corresponding page. For example, the page data belonging to the first format in the first correspondence is page data represented in text format, and the page data represented in text format contains program code for rendering the page. Based on the first page identifier carried in the data acquisition request, the server queries the first correspondence to obtain the first page data corresponding to the first page data. All page data in the first correspondence belongs to the first format, that is, the queried first page data belongs to the first format.

[0109] 303. When the second format is different from the first format, the server uses a format conversion protocol to convert the first page data belonging to the first format to obtain the first page data belonging to the second format. The format conversion protocol is used to convert page data from the first format to the second format.

[0110] In one possible implementation, step 303 includes: when the second format is different from the first format, the server uses a format conversion protocol to parse the first page data belonging to the first format to obtain the first page data belonging to the second format.

[0111] In this embodiment of the application, the server uses a parsing method to convert the format of the first page data to ensure the accuracy of the first page data that belongs to the second format.

[0112] 304. The server sends the first page data, which belongs to the second format, to the first terminal.

[0113] 305. The first terminal receives the first page data of the second format sent by the server, and renders it based on the first page data of the second format to display the page corresponding to the first page identifier.

[0114] In this embodiment, the first terminal can identify first page data belonging to the second format. By rendering the first page data in the second format, the page corresponding to the first page identifier can be rendered, thus enabling page access. For example, if the page corresponding to the first page identifier is the website homepage, the first page data in the second format contains data for each menu button on the website homepage. Based on the first page data in the second format, the first terminal renders the website homepage, displaying each menu button.

[0115] In one possible implementation, the page indicated by the first page identifier is a webpage. The first terminal sends a data retrieval request to the server through a browser. The process of rendering the page includes: the first terminal renders the first page data, which belongs to the second format, through the browser, and displays the page corresponding to the first page identifier in the browser.

[0116] In one possible implementation, the page indicated by the first page identifier is a page in the application. The first terminal sends a data acquisition request to the server through the application. The process of rendering the page includes: the first terminal renders the page based on the first page data belonging to the second format through the application, and displays the page corresponding to the first page identifier in the application.

[0117] 306. When the server displays the page corresponding to the first page identifier on the first terminal, it responds to the update instruction for the page data corresponding to the first page identifier and obtains the updated page data corresponding to the first page identifier.

[0118] In this embodiment, the page data in the first correspondence stored on the server can be updated. When the page data corresponding to a certain page is updated, the content or display style of that page changes. When the first terminal displays a page, once the server detects that the page data corresponding to that page has been updated, it needs to provide the first terminal with the updated page data so that the terminal can display the updated page. Therefore, in response to the update instruction for the page data corresponding to the first page identifier, the updated page data corresponding to the first page identifier is obtained so that new page data can be provided to the first terminal subsequently.

[0119] In one possible implementation, the update instruction for the page data corresponding to the first page identifier is triggered by a second terminal. For example, the second terminal is a terminal used by a developer. This second terminal has the authority to manage the first mapping relationship in the server. The developer can then send an update instruction to the server through the second terminal to update the page data in the second mapping relationship stored on the server, thereby updating the corresponding page. In response to the update operation for the page data corresponding to the first page identifier, the second terminal sends an update request to the server. The server receiving this update request is equivalent to receiving the update instruction for the page data corresponding to the first page identifier.

[0120] In one possible implementation, the process of obtaining the updated page data corresponding to the first page identifier includes: obtaining the updated page data corresponding to the first page identifier from the first correspondence.

[0121] In one possible implementation, the server stores page access records that indicate the page access status of each terminal. Based on these page access records, the server determines the page currently accessed by the first terminal, that is, it determines the page corresponding to the first page identifier currently displayed by the first terminal.

[0122] 307. The server uses a format conversion protocol to convert the updated page data corresponding to the first page identifier into a second format, and then sends the updated page data in the second format to the first terminal.

[0123] In this embodiment, the page data in the first correspondence belongs to a first format that the server can recognize. That is, the page data corresponding to the first page identifier in the first correspondence belongs to a first format that the server can recognize. When the page data corresponding to the first page identifier in the server is updated, the updated page data corresponding to the first page identifier in the updated first correspondence also belongs to the first format. Since the first terminal can recognize the second format, a format conversion protocol is used to convert the updated page data corresponding to the first page identifier to obtain updated page data in the second format that the first terminal can recognize, and then send it to the first terminal so that the first terminal can update the displayed page.

[0124] 308. The first terminal receives the updated page data in the second format sent by the server, and renders the updated page based on the updated page data in the second format to update the displayed page.

[0125] In this embodiment of the application, if the updated page data sent by the server is in a format recognizable by the first terminal, then the updated page data belonging to the second format can be re-rendered to update the displayed page.

[0126] This application provides a novel page deployment method. The server stores each page's data in a first format that the server can recognize, corresponding to page identifiers. The server is also configured with a format conversion protocol that matches the first format. When a terminal accesses a page, the server queries the first correspondence and, in conjunction with the format conversion protocol, provides the terminal with page data in a recognizable format. The terminal then displays the page, enabling the server to provide page display services to the terminal. Furthermore, the first correspondence between the stored page identifiers and page data has good scalability and facilitates updates to the page data in the first correspondence, ensuring efficient page updates.

[0127] Furthermore, when the page data corresponding to the page displayed on the first terminal is updated, the server actively sends the updated page data corresponding to the page and in a second format that the first terminal can recognize to the first terminal, so that the first terminal can re-render based on the updated page data to update the displayed page, ensuring that the displayed page is always the latest page, thereby guaranteeing the accuracy and real-time performance of the displayed page.

[0128] In the above Figure 3 Based on the illustrated embodiment, a page service is configured in the server to provide page data to the terminal. This page server can be any service; for example, it could be a Node (interpreter) service. Then, according to the above... Figure 3 In the illustrated embodiment, the server interacts with the first terminal through a page service. Steps 301-304 and 306-307 are implemented by the server through the page service. According to the solution provided in this application embodiment, when modifying page data or adding pages, there is no need to redeploy the page service on the server, and the updated page data can take effect in real time.

[0129] In the above Figures 2 to 3 Based on the embodiments shown, the embodiments of this application can also update the page data in the first correspondence stored on the server, and the specific process is detailed in the following embodiments.

[0130] Figure 4 This is a flowchart of a page display method provided in an embodiment of this application. The method is executed by a server and a second terminal, such as... Figure 4 As shown, the method includes:

[0131] 401. The server receives a data access request sent by the second terminal, and the data access request carries the second page identifier.

[0132] In this embodiment, the second terminal can interact with the server to access page data in the first correspondence stored on the server, thereby displaying and updating the page data. The second page identifier is any page identifier in the first correspondence stored on the server.

[0133] In one possible implementation, if a second application provided by a server is installed on the second terminal, then step 401 includes: the second terminal logging into the second application based on an object identifier, displaying a page identifier in the first correspondence, and sending a data access request to the server in response to a data access operation on the second page identifier, the data access request carrying the second page identifier, and the server receiving the data access request sent by the second terminal.

[0134] The object identifier logged in by the second terminal has the authority to manage the first mapping relationship stored on the server. The object identifier indicates any object; for example, it could indicate a developer. That is, the developer can manage the first mapping relationship stored on the server through the second terminal. In other words, the second terminal is the terminal used by the developer, who, through interaction with the server, can access page data stored on the server so that the accessed page data can be modified subsequently through the second terminal.

[0135] In this embodiment of the application, when the second terminal logs into the second application, it can display the page identifier in the first correspondence stored on the server, so that the developer can select any page identifier to view it through the second terminal.

[0136] 402. In response to the data access request, the server queries the page data stored corresponding to the second page identifier and sends the page data stored corresponding to the second page identifier to the second terminal.

[0137] In this embodiment, the server responds to a data access request sent by the second terminal by querying a first correspondence to determine the page data in the first correspondence that corresponds to the second page identifier carried in the data access request, and then sends the queried data to the second terminal so that the second terminal can display it for the user to view.

[0138] 403. The second terminal receives the page data corresponding to the second page identifier from the server and displays the page data corresponding to the second page identifier.

[0139] In this embodiment of the application, the second terminal receives and displays page data sent by the server so that the user can view the content contained in the page data.

[0140] In one possible implementation, a second application provided by a server is installed on the second terminal. The second terminal logs into the second application based on an object identifier, which has the authority to manage the first correspondence stored on the server. Then, step 403 includes: the second terminal receiving page data stored corresponding to the second page identifier sent by the server, and displaying the page data stored corresponding to the second page identifier through the second application.

[0141] In this embodiment, the object identifier logged in by the second terminal has the authority to manage the first correspondence stored on the server. The second terminal displays the page data stored corresponding to the second page identifier through the second application, so that the user can query the displayed page data through the second terminal and then modify the page data. This realizes a scheme for modifying page data and ensures the convenience of modifying page data.

[0142] 404. In response to the modification operation on the displayed page data, the second terminal modifies the displayed page data to obtain the second page data. In response to the save instruction on the second page data, the second terminal sends a data modification request to the server. The data modification request carries the second page identifier and the second page data.

[0143] In this embodiment of the application, when the second terminal displays the accessed page data, the user can modify the displayed page data through the second terminal to modify the corresponding page and obtain the modified page data, that is, obtain the second page data corresponding to the second page identifier, and then interact with the server so that the server can update the page data corresponding to the second page identifier in the first correspondence.

[0144] The modification operation instruction modifies the displayed page data, while the save instruction modifies the page data displayed on the second terminal and then saves the currently displayed page data. The currently displayed page data is also the second page data; that is, the save instruction is used to save the second page data.

[0145] In one possible implementation, a second application provided by a server is installed on the second terminal, and the second terminal displays page data through the second application. Then step 404 includes: the second terminal, through the second application, modifies the displayed page data in response to a modification operation on the displayed page data to obtain second page data; and in response to a save instruction on the second page data, sends a data modification request to the server, the data modification request carrying the second page identifier and the second page data.

[0146] 405. The server receives a data modification request sent by the second terminal, performs format conversion on the second page data to obtain second page data belonging to the first format, and updates the page data stored corresponding to the second page identifier to second page data belonging to the first format.

[0147] In this embodiment, the page data in the first correspondence stored by the server belongs to a first format that the server can recognize, while the second page data sent by the second terminal belongs to a format that the terminal can recognize. For example, if the second page data belongs to a second format, after the server receives the data modification request sent by the second terminal, it uses a data conversion protocol to convert the second page data into a first format so that the server can update the first correspondence with the second page data belonging to the first format, thereby updating the page data stored corresponding to the second page identifier in the first correspondence, and ensuring the accuracy of the page data stored in the first correspondence.

[0148] It should be noted that the embodiment of this application takes the second terminal accessing page data first as an example and modifying the accessed page data. In another embodiment, it is not necessary to perform the above steps 401-404. Instead, other methods are adopted, and the second terminal sends a data modification request to the server.

[0149] This application provides a novel page deployment method. The server stores each page's data in a first format that the server can recognize, corresponding to page identifiers. The server is also configured with a format conversion protocol that matches the first format. When a terminal accesses a page, the server queries the first correspondence and, in conjunction with the format conversion protocol, provides the terminal with page data in a recognizable format. The terminal then displays the page, enabling the server to provide page display services to the terminal. Furthermore, the first correspondence between the stored page identifiers and page data has good scalability and facilitates updates to the page data in the first correspondence, ensuring efficient page updates.

[0150] In this embodiment, the second terminal can modify the page data stored in the server. When modifying a page, only the page data corresponding to a certain page identifier in the first correspondence stored in the server needs to be modified. There is no need to redeploy the page. The modification process is simple and improves the convenience of page modification.

[0151] In the above Figures 2 to 4 Based on the embodiments shown, the embodiments of this application can also add new page data to the first correspondence to realize the addition of pages. For details of the process, please refer to the following embodiments.

[0152] Figure 5 This is a flowchart of a page display method provided in an embodiment of this application. The method is executed by a server, such as... Figure 5 The method includes:

[0153] 501. The server receives a data addition request sent by the second terminal. The data addition request carries the third page identifier and the data to be added to the page.

[0154] In this embodiment of the application, the second terminal can obtain the newly added page data and the corresponding third page identifier. By interacting with the server, it can update the first correspondence stored by the server, so as to add the third page identifier and the corresponding newly added page data in the first correspondence, thereby realizing the addition of a page.

[0155] In one possible implementation, the second terminal has a second application installed with services provided by the server. The second terminal logs into the second application based on an object identifier, which has the authority to manage the first correspondence in the server. The process of the second terminal sending a data addition request then includes: the second terminal obtaining the third page identifier and the new page data through the second application, and then sending the data addition request to the server through the second application.

[0156] In this embodiment, the user can edit page data through a second application installed on the terminal. In the second application, the user can edit new page data and the corresponding third page identifier. After editing the new page data, the user can save the new page data. Then, the second terminal can interact with the server and send a data addition request to the server.

[0157] 502. The server performs format conversion on the newly added page data to obtain the newly added page data belonging to the first format.

[0158] In this embodiment, the new page data sent by the second terminal is in a format recognizable by the terminal, while the page data in the first correspondence stored by the server is in a first format recognizable by the server. Therefore, the new page data is converted to a format to obtain new page data in the first format recognizable by the server, so that the server can store the new page data in the first correspondence in the future.

[0159] 503. The server stores the third page identifier in relation to the newly added page data belonging to the first format.

[0160] In this embodiment, the server stores the third page identifier and the newly added page data belonging to the first format in the first correspondence relationship to realize the addition of page data.

[0161] In the application embodiment, the second terminal interacts with the server and sends a third page identifier and corresponding new page data to the server. After the server converts the new page data into a recognizable first format, it stores the new page data with the third page identifier belonging to the first format in the first correspondence relationship. This realizes the addition of page data without redeploying the page. The page addition process is simple and improves the convenience of adding pages.

[0162] In the above Figure 2Based on the embodiment shown in the figure, in this embodiment of the application, when the server converts the page data into a terminal-recognizable format belonging to the terminal type, it stores the page data and the terminal type in a second correspondence relationship. When other terminals request page data, they first query the data from the second correspondence relationship to reduce the time spent on format conversion. For details of the process, please refer to the following embodiments.

[0163] Figure 6 This is a flowchart of a page display method provided in an embodiment of this application. The method is executed by a server, such as... Figure 6 The method includes:

[0164] 601. In response to the data acquisition request sent by the first terminal, the server determines the terminal type of the first terminal based on the terminal identifier of the first terminal.

[0165] In this embodiment, the server further stores a second correspondence between terminal type, page identifier, and page data. The page data corresponding to the terminal type is in a terminal-recognizable format. When different terminals access a page, they interact with the server to obtain the page data corresponding to the accessed page, thereby displaying the page. During the process of a terminal obtaining page data, the server provides the terminal with page data in a terminal-recognizable format. Terminals of the same type have the same recognizable format. Therefore, when a terminal requests page data from the server, the server provides the terminal with page data in a recognizable format and simultaneously stores the terminal type, page identifier, and page data corresponding to that terminal type in the second correspondence. This allows other terminals accessing the same page data to directly obtain it from the second correspondence without needing to query the page data from the first correspondence and perform format conversion again.

[0166] In this embodiment of the application, the terminal identifier of the first terminal can represent the corresponding terminal, and the terminal type to which the first terminal belongs can be determined based on the terminal identifier of the first terminal.

[0167] In one possible implementation, the server stores a correspondence between terminal identifiers and terminal types. Based on the terminal identifier of the first terminal, the server queries the correspondence between the terminal identifier and the terminal type to obtain the terminal type to which the first terminal belongs.

[0168] In one possible implementation, step 601 includes: classifying the terminal information corresponding to the terminal identifier of the first terminal to obtain the terminal type to which the first terminal belongs.

[0169] The terminal information is used to characterize the first terminal. For example, the terminal information includes the terminal manufacturer, the terminal batch number, and the terminal configuration information. By classifying the terminal information, the terminal type to which the first terminal belongs can be determined.

[0170] 602. The server queries the second correspondence based on the terminal type of the first terminal and the first page identifier carried in the data acquisition request.

[0171] In this embodiment of the application, when the server determines the terminal type to which the first terminal belongs and the first page identifier corresponding to the page requested by the first terminal, it queries the second correspondence relationship to determine whether the second correspondence relationship contains page data corresponding to the first page identifier and belonging to the format recognizable by the first terminal.

[0172] 603. If the server does not find page data corresponding to the terminal type and the first page identifier of the first terminal, it determines the second format that the first terminal can recognize, and retrieves the first page data that corresponds to the first page identifier and belongs to the first format from the first correspondence.

[0173] In this embodiment, the server does not find page data corresponding to the terminal type and first page identifier of the first terminal in the second correspondence relationship. This indicates that no terminal of the same terminal type as the first terminal has accessed the page corresponding to the first page identifier. Therefore, the second correspondence relationship does not store page data corresponding to the terminal type and first page identifier of the first terminal. Thus, querying the first page data corresponding to the first page identifier from the first correspondence relationship is effective because the page data stored in the first correspondence relationship by the server all belong to the first format. In other words, it retrieves the first page data stored in the first correspondence relationship that corresponds to the first page identifier and belongs to the first format.

[0174] In this embodiment, the server stores a second correspondence and a first correspondence. In response to a data acquisition request from a first terminal, the server first queries the page data requested by the first terminal from the second correspondence. Only if the page data requested by the first terminal is not found in the second correspondence will the server query the page data requested by the first terminal from the first correspondence. This is to minimize the number of page data format conversions, thereby saving the time required for data requests and ensuring the real-time provision of page data to the terminal.

[0175] In one possible implementation, the server also stores a third correspondence between terminal identifiers and formats. The process by which the server determines the second format that the first terminal can recognize includes: querying the third correspondence based on the terminal identifier of the first terminal carried in the data acquisition request, and obtaining the second format corresponding to the first terminal identifier.

[0176] In this embodiment, the format corresponding to the terminal identifier in the third correspondence is the format that the terminal can recognize, as indicated by the terminal identifier. Based on the terminal identifier of the first terminal carried in the data acquisition request, querying the third correspondence allows us to determine the second format corresponding to the terminal identifier of the first terminal, which is also the second format that the first terminal can recognize. By setting the third correspondence in the server, the format that any terminal can recognize can be quickly determined, thereby ensuring the efficiency of format determination.

[0177] In one possible implementation, if the data acquisition request carries a second format recognizable by the first terminal, then determining the second format recognizable by the first terminal includes: the server acquiring the second format recognizable by the first terminal from the data acquisition request.

[0178] In the embodiments of this application, different terminals may have different recognizable formats, and there are various types of terminals. When a terminal sends a data acquisition request to the server, the data acquisition request carries the format that the terminal can recognize, so that the server can provide page data in a format that the terminal can recognize, thereby ensuring the accuracy of the data provided.

[0179] It should be noted that the embodiments of this application are illustrated using the example of a second correspondence stored in the server. In another embodiment, it is not necessary to perform the above steps 602-603. Instead, other methods are adopted to determine the second format that the first terminal can recognize from the first correspondence in response to the data acquisition request sent by the first terminal, and to acquire the first page data that corresponds to the first page identifier and belongs to the first format. The first page identifier is the identifier carried by the data acquisition request.

[0180] 604. When the second format differs from the first format, the server uses a format conversion protocol to convert the first page data belonging to the first format to obtain the first page data belonging to the second format. The format conversion protocol is used to convert page data from the first format to the second format.

[0181] Step 604 is the same as step 303 above, and will not be repeated here.

[0182] 605. The server sends first page data in the second format to the first terminal, which then renders the first page data in the second format to display the page corresponding to the first page identifier.

[0183] Step 605 is the same as steps 304-305 above, and will not be repeated here.

[0184] 606. The server stores the terminal type of the first terminal, the first page identifier, and the first page data belonging to the second format to update the second correspondence.

[0185] In this embodiment, since the second correspondence does not store the page data corresponding to the terminal type of the first terminal and the first page identifier, when the server obtains the page data corresponding to the terminal type of the first terminal and the first page identifier, it stores the corresponding page data in the second correspondence. This allows a terminal of the same terminal type as the first terminal to directly query and return the queried page data from the second correspondence when requesting the page data corresponding to the first page identifier. This eliminates the need to query the page data from the first correspondence and then perform format conversion, thereby improving the efficiency of data feedback.

[0186] It should be noted that the embodiments of this application are illustrated by taking the example of executing step 605 first and then step 606. In another embodiment, step 606 is executed first and then step 605 is executed, or steps 605 and 606 are executed simultaneously. This application does not limit this.

[0187] It should be noted that the embodiments of this application are described using step 606 as an example, while in another embodiment, step 606 may not be required.

[0188] It should be noted that the above Figure 6 The illustrated embodiment is based on the example of no page data being found. In another embodiment, if page data can be found, the method further includes: if page data corresponding to the terminal type and the first page identifier of the first terminal is found, the method sends the found page data to the first terminal, and the first terminal renders the page corresponding to the first page identifier based on the found page data.

[0189] In this embodiment, the server retrieves page data corresponding to the terminal type and the first page identifier of the first terminal from the second correspondence. If the retrieved page data belongs to the second format that the first terminal can recognize, the server can directly send the retrieved page data to the first terminal without further format conversion, thereby ensuring the efficiency of data feedback.

[0190] It should be noted that the above-mentioned various optional embodiments can be combined in any way to form optional embodiments of this application, and will not be described in detail here.

[0191] Figure 7 This application provides a page display device, which is installed in a server. The server stores a first correspondence between page identifiers and page data. The page data belongs to a first format that the server can recognize, such as... Figure 7 As shown, the device includes:

[0192] The determining module 701 is used to determine a second format that the first terminal can recognize in response to a data acquisition request sent by the first terminal;

[0193] The acquisition module 702 is used to acquire first page data that corresponds to the first page identifier and belongs to the first format from the first correspondence relationship, wherein the first page identifier is the identifier carried by the data acquisition request;

[0194] The conversion module 703 is used to convert the first page data belonging to the first format to the second format by using a format conversion protocol when the second format is different from the first format. The format conversion protocol is used to convert the page data from the first format to the second format.

[0195] The sending module 704 is used to send first page data belonging to the second format to the first terminal. The first terminal is used to render based on the first page data belonging to the second format to display the page corresponding to the first page identifier.

[0196] In one possible implementation, such as Figure 8 As shown, the device also includes:

[0197] The receiving module 705 is used to receive a data modification request sent by the second terminal. The data modification request carries a second page identifier and second page data.

[0198] The conversion module 703 is also used to convert the format of the second page data to obtain the second page data belonging to the first format;

[0199] Storage module 706 is used to update the page data stored corresponding to the second page identifier to second page data belonging to the first format.

[0200] In another possible implementation, such as Figure 8 As shown, the device also includes:

[0201] The receiving module 705 is also used to receive a data access request sent by the second terminal, the data access request carrying a second page identifier;

[0202] The query module 707 is used to query the page data stored corresponding to the second page identifier and send the page data stored corresponding to the second page identifier to the second terminal.

[0203] The second terminal is used to display page data stored corresponding to the second page identifier; in response to a modification operation on the displayed page data, it modifies the displayed page data to obtain the second page data; and in response to a save command on the second page data, it sends a data modification request to the server.

[0204] In another possible implementation, such as Figure 8 As shown, the device also includes:

[0205] The receiving module 705 is used to receive a data addition request sent by the second terminal. The data addition request carries a third page identifier and data for the new page.

[0206] The conversion module 703 is also used to convert the format of the newly added page data to obtain the newly added page data belonging to the first format;

[0207] Storage module 706 is used to store the third page identifier and the corresponding new page data belonging to the first format.

[0208] In another possible implementation,

[0209] The acquisition module 702 is also used to acquire the updated page data corresponding to the first page identifier in response to the update instruction for the page data corresponding to the first page identifier when the first terminal displays a page;

[0210] The conversion module 703 is also used to perform format conversion on the updated page data using a format conversion protocol to obtain updated page data belonging to the second format;

[0211] The sending module 704 is also used to send updated page data belonging to the second format to the first terminal, and the first terminal is used to render based on the updated page data belonging to the second format to update the displayed page.

[0212] In another possible implementation, the server also stores a second correspondence between terminal type, page identifier, and page data, wherein the page data corresponding to the terminal type belongs to a terminal-recognizable format of the terminal type; the second correspondence is stored by the server when converting the page data into a terminal-recognizable format belonging to the terminal type; the data acquisition request carries the terminal identifier of the first terminal; the determining module 701 is used to respond to the data acquisition request sent by the first terminal, determine the terminal type of the first terminal based on the terminal identifier of the first terminal; query the second correspondence based on the terminal type of the first terminal and the first page identifier; and determine the second format recognizable by the first terminal if no page data corresponding to the terminal type and the first page identifier of the first terminal is found.

[0213] In another possible implementation, such as Figure 8 As shown, the device also includes:

[0214] The storage module 706 is used to store the terminal type to which the first terminal belongs, the first page identifier, and the first page data belonging to the second format, so as to update the second correspondence.

[0215] In another possible implementation, the sending module 704 is further configured to send the queried page data to the first terminal when page data corresponding to the terminal type and the first page identifier of the first terminal is found. The first terminal is used to render based on the queried page data to display the page corresponding to the first page identifier.

[0216] In another possible implementation, the server also stores a third correspondence between terminal identifiers and formats, where the format corresponding to the terminal identifier is a format that the terminal can recognize, as indicated by the terminal identifier, and the data acquisition request also carries the terminal identifier of the first terminal; the determination module 701 is used to query the third correspondence to obtain the second format corresponding to the terminal identifier of the first terminal.

[0217] It should be noted that the page display device provided in the above embodiments is only an example of the division of the above functional modules. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the server can be divided into different functional modules to complete all or part of the functions described above. In addition, the page display device and the page display method embodiments provided in the above embodiments belong to the same concept, and the specific implementation process can be found in the method embodiments, which will not be repeated here.

[0218] This application also provides a server, which includes a processor and a memory. The memory stores at least one computer program, which is loaded and executed by the processor to perform the operations performed by the page display method of the above embodiments.

[0219] Figure 9 This is a schematic diagram of a server structure provided in an embodiment of this application. The server 900 can vary significantly due to different configurations or performance. It may include one or more Central Processing Units (CPUs) 901 and one or more memories 902. The memories 902 store at least one computer program, which is loaded and executed by the processor 901 to implement the methods provided in the above-described method embodiments. Of course, the server may also have wired or wireless network interfaces, a keyboard, and input / output interfaces for input and output. The server may also include other components for implementing device functions, which will not be elaborated upon here.

[0220] This application also provides a computer-readable storage medium storing at least one computer program, which is loaded and executed by a processor to implement the operations performed by the page display method of the above embodiments.

[0221] This application also provides a computer program product, including a computer program that, when executed by a processor, performs the operations performed by the page display method of the above embodiments.

[0222] Those skilled in the art will understand that all or part of the steps of the above embodiments can be implemented by hardware or by a program instructing related hardware. The program can be stored in a computer-readable storage medium, such as a read-only memory, a disk, or an optical disk.

[0223] The above description is only an optional embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present application should be included within the protection scope of the present application.

Claims

1. A page display method characterized by comprising: The method is executed by a server, the server stores a first correspondence relationship between a page identifier and page data and a second correspondence relationship between a terminal type, a page identifier and page data, the page data is in a first format recognizable by the server, and the page data corresponding to the terminal type is in a format recognizable by a terminal of the terminal type; The second correspondence relationship is stored when the server converts the page data into a format recognizable by a terminal of the terminal type; the method comprises: In response to a data acquisition request sent by a first terminal, determining a terminal type to which the first terminal belongs based on a terminal identifier of the first terminal, the data acquisition request carrying the terminal identifier of the first terminal and a first page identifier; Based on the terminal type to which the first terminal belongs and the first page identifier, querying the second correspondence relationship; In a case where page data corresponding to the terminal type to which the first terminal belongs and the first page identifier is not queried, determining a second format recognizable by the first terminal; From the first correspondence relationship, acquiring first page data corresponding to the first page identifier and stored in the first format; In a case where the second format is different from the first format, performing format conversion on the first page data in the first format by using a format conversion protocol, to obtain first page data in the second format, the format conversion protocol being used to convert page data from the first format into the second format; Sending the first page data in the second format to the first terminal, the first terminal being used to perform rendering based on the first page data in the second format, to display a page corresponding to the first page identifier.

2. The method of claim 1, wherein, The method further comprises: Receiving a data modification request sent by a second terminal, the data modification request carrying a second page identifier and second page data; Performing format conversion on the second page data, to obtain second page data in the first format; Updating page data corresponding to the second page identifier to the second page data in the first format.

3. The method of claim 2, wherein, Before the receiving of the data modification request sent by the second terminal, the method further comprises: Receiving a data access request sent by the second terminal, the data access request carrying the second page identifier; Querying page data stored corresponding to the second page identifier, and sending the page data stored corresponding to the second page identifier to the second terminal; The second terminal is used to display the page data stored corresponding to the second page identifier; in response to a modification operation on the displayed page data, modifying the displayed page data to obtain the second page data; and in response to a save instruction on the second page data, sending the data modification request to the server.

4. The method of claim 1, wherein, The method further comprises: Receiving a data addition request sent by a second terminal, the data addition request carrying a third page identifier and addition page data; Performing format conversion on the addition page data, to obtain addition page data in the first format; The third page identifier is stored in correspondence with the new page data in the first format.

5. The method of claim 1, wherein, After sending the first page data in the second format to the first terminal, the method further comprises: In the case that the first terminal displays the page, in response to an update instruction for the page data corresponding to the first page identifier, the updated page data corresponding to the first page identifier is acquired; The format conversion protocol is used to convert the updated page data into the second format to obtain updated page data in the second format; The updated page data in the second format is sent to the first terminal, and the first terminal is used to render based on the updated page data in the second format to update the displayed page.

6. The method of claim 1, wherein, After the format conversion protocol is used to convert the first page data in the first format into the second format in the case that the second format is different from the first format, the method further comprises: The terminal type to which the first terminal belongs, the first page identifier and the first page data in the second format are stored in correspondence to update the second correspondence.

7. The method of claim 1, wherein, After the second correspondence is queried based on the terminal type to which the first terminal belongs and the first page identifier, the method further comprises: In the case that the page data corresponding to the terminal type to which the first terminal belongs and the first page identifier is queried, the queried page data is sent to the first terminal, and the first terminal is used to render based on the queried page data to display the page corresponding to the first page identifier.

8. The method according to any one of claims 1 to 5, characterized in that, The server further stores a third correspondence between a terminal identifier and a format, the format corresponding to the terminal identifier is a format recognizable by a terminal indicated by the terminal identifier, and the data acquisition request further carries a terminal identifier of the first terminal; The determination of the second format recognizable by the first terminal comprises: The third correspondence is queried to obtain the second format corresponding to the terminal identifier of the first terminal.

9. A page display device characterized by comprising: The server stores a first correspondence between a page identifier and page data and a second correspondence between a terminal type, a page identifier and page data, the page data is in a first format recognizable by the server, and the page data corresponding to the terminal type is in a format recognizable by a terminal of the terminal type; The second correspondence is stored by the server when the page data is converted into a format recognizable by a terminal of the terminal type; and the apparatus comprises: The determining module is configured to, in response to a data acquisition request sent by a first terminal, determine a terminal type to which the first terminal belongs based on a terminal identifier of the first terminal, the data acquisition request carrying the terminal identifier of the first terminal and a first page identifier; query the second correspondence based on the terminal type to which the first terminal belongs and the first page identifier; and determine a second format recognizable by the first terminal in a case where page data corresponding to the terminal type to which the first terminal belongs and the first page identifier is not queried. The obtaining module is configured to obtain, from the first correspondence, first page data corresponding to the first page identifier and belonging to the first format. The converting module is configured to, in a case where the second format is different from the first format, perform format conversion on the first page data belonging to the first format by using a format conversion protocol, to obtain first page data belonging to the second format, the format conversion protocol being used to convert page data from the first format to the second format. The sending module is configured to send the first page data belonging to the second format to the first terminal, the first terminal being configured to perform rendering based on the first page data belonging to the second format, to display a page corresponding to the first page identifier.

10. A server, characterized by The server comprises a processor and a memory, and the memory stores at least one computer program, the at least one computer program is loaded and executed by the processor to implement the operations performed by the page display method according to any one of claims 1 to 8.

11. A computer readable storage medium, characterized in that, The computer readable storage medium stores at least one computer program, and the at least one computer program is loaded and executed by the processor to implement the operations performed by the page display method according to any one of claims 1 to 8.

Images