WO2016050144A1

WO2016050144A1 - Interface update method and client

Info

Publication number: WO2016050144A1
Application number: PCT/CN2015/089958
Authority: WO
Inventors: 彭磊; 金锐; 曾中华
Original assignee: 阿里巴巴集团控股有限公司; 彭磊; 金锐; 曾中华
Priority date: 2014-09-30
Filing date: 2015-09-18
Publication date: 2016-04-07
Also published as: HK1222267A1; CN105450718A

Abstract

The present application provides an interface update method and a client. The method comprises: a client acquires from a server service update data required for updating an interface that is provided by the client and used for presenting service information; the client updates, according to the service update data, first service data used for forming the current interface, so as to obtain second service data, the first service data comprising service grouping data corresponding to a service category presented on the current interface and detail data of a service corresponding to a service view presented in the service category on the current interface, and the service grouping data corresponding to the service category comprising an identifier of a service belonging to the service category; and the client forms a new interface according to the second service data. By means of the technical solution of the present application, the interface update operation can be simplified, and the interface update efficiency can be improved.

Description

Interface update method and client

[Technical Field]

The present application relates to the field of Internet technologies, and in particular, to an interface update method and a client.

【Background technique】

Users can install various application clients on their terminals, and different application clients have different styles of interfaces. The application client can provide an interface and display the services it provides to the user through the interface. The interface of the application client is generally fixed and can be set by a layout configuration file preset in the installation package.

However, with the upgrade and diversity of services that application clients can provide, a fixed interface will not be able to meet the needs of service diversity. Faced with the requirements of updating, sorting, deleting and replacing large-scale service data, the server can only continuously release the upgrade package of the application client, so that the user can manually download and install the upgrade package, and then through the layout configuration file in the upgrade package. To change the interface of the application client. This method is inconvenient and inefficient because it requires the user to manually download and install the upgrade package.

[Summary of the Invention]

Aspects of the present application provide an interface update method and a client for simplifying the operation of updating an interface and improving the efficiency of updating the interface.

An aspect of the present application provides an interface update method, including:

The client obtains, from the server, service update data required to update an interface provided by the client for displaying service information;

The client updates the first service data used to form the current interface according to the service update data, and obtains the second service data. The first service data includes: a service corresponding to the service category displayed by the current interface. Packet data, and the current interface is displayed in the service category The service data corresponding to the service view; the service packet data corresponding to the service category includes: an identifier of the service belonging to the service category;

The client forms the new interface according to the second service data.

In another aspect of the present application, a client is provided, including:

An obtaining module, configured to obtain, from a server, service update data required to update an interface provided by the client for displaying service information;

And an update module, configured to update, according to the service update data, the first service data used by the current interface to obtain the second service data, where the first service data includes: the service category corresponding to the current interface Service packet data, and the current interface presents detailed data of a service corresponding to the service view under the service category; the service packet data corresponding to the service category includes: an identifier of a service belonging to the service category;

And an interface module, configured to form the new interface according to the second service data.

In the present application, the client obtains service update data from the server to update the interface provided by the client for displaying the service information; wherein the current interface displays at least one service category, and in each service category The specific service view is displayed. The first service data includes the service group data corresponding to the service category displayed by the current interface, and the detailed data of the service corresponding to the service view displayed by the current interface in the service category, according to the obtained service. Updating the data, updating the first service data used to form the current interface to obtain the second service data, and forming a new interface according to the second service data. Therefore, in the present application, the client can automatically complete the interface update, and the user does not need to manually download and install the upgrade package, and the interface update operation is relatively simple, which is beneficial to improving the efficiency of the update interface.

[Description of the Drawings]

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings used in the embodiments or the prior art description will be briefly described below. Obviously, the drawings in the following description are the present application. Some embodiments, for those of ordinary skill in the art, do not pay for creation Other drawings can also be obtained from these drawings on the premise of sexual labor.

1 is a schematic flowchart of an interface update method according to an embodiment of the present application;

2 is a schematic diagram of a current interface of a client according to an embodiment of the present disclosure;

FIG. 3 is a schematic diagram of a new interface of a client according to an embodiment of the present disclosure;

FIG. 4 is a schematic structural diagram of a client according to an embodiment of the present application.

【detailed description】

The technical solutions in the embodiments of the present application are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present application. It is a part of the embodiments of the present application, and not all of the embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present application without departing from the inventive scope are the scope of the present application.

FIG. 1 is a schematic flowchart diagram of an interface update method according to an embodiment of the present application. As shown in Figure 1, the method includes:

101. The client obtains, from the server, service update data required to update an interface provided by the client for displaying service information.

102. The client updates, according to the service update data, the first service data that is used by the current interface to obtain the second service data. The first service data includes the service group data corresponding to the service category displayed by the current interface, and the current The interface displays the detailed data of the service corresponding to the service view under the service category; the service packet data corresponding to the service category includes the identifier of the service belonging to the service category.

103. The client forms a new interface according to the second service data.

The embodiment provides an interface update method. The method provided in this embodiment can be executed by a client. The client can be any client that can provide an interface and needs to be adjusted. For example, it can be a browser or an application. , APP) client. The process of the method provided in this embodiment is specifically as follows:

The server stores service information that needs to be presented to the user through an interface provided by the client. The service information that needs to be presented to the user changes as the service provided by the service provider changes. For example, if a new service appears, information that needs to be added to the user's service information needs to be added; if a service is canceled, the information of the service information that needs to be deleted to the user needs to be deleted. If a service is upgraded, the service information that needs to be presented to the user needs to be increased due to the service upgrade.

For example, the above services may be search for food service, movie service, news service, lottery service, reading service, product sub-service, photo service, bus inquiry service or weather inquiry service.

The client obtains service update data from the server, and the service update data refers to data required to update an interface provided by the client for presenting service information to the user. The content and the presentation manner of the interface may determine the data required for the interface update, that is, the content of the service update data may be determined by the content and presentation manner of the interface.

In this embodiment, in order to facilitate clearer presentation of service information to the user, the service is classified into the same service category by classifying the service. This embodiment does not limit the standard of service classification, that is, the definition of the service category and the services that should be included in each service category are not limited.

Based on the idea of service classification, the interface provided by the client needs to display the service information in the service category + service view. In this embodiment, the current page of the client presents a service category, and a specific service view is displayed under the service category. The current page can display a service category or at least two service categories. The service category can display a service view or at least two service views. On the interface, the service information is specifically presented in the form of a service view. The access view information of the service corresponding to the service picture, the operation picture, the title, the subtitle, the background color, and the service view may be displayed on the service view, wherein the access entry information of the service is different according to the service providing manner, for example, If the service is provided in the form of a webpage, the access entry information may be a Uniform Resoure Locator (URL) address that is jumped to the service, if the service is in the form of a local APP or a WEB APP. Provided, the access entry information may be call interface information of the corresponding APP or the like. As shown in Figure 2, a service category for the current page and a service view for that service category. The service view may include an access portal that jumps to the corresponding service. In FIG. 2, the service category presented is entertainment, and the entertainment category includes a search food service view, a movie service view, and a lottery service view. When the user clicks on the service view, it jumps to the corresponding service, and continues to use FIG. 2 as an example. If the user clicks on the search for the gourmet service view, the user can jump to the service of searching for food. Specifically, the service can be in various ways. Provided to the user, for example, may be a web page form, a local APP form, a WEB APP form, or the like. It is worth noting that the service view can be colored and is not limited to the gray shown in Figure 2.

Based on the foregoing, the first service data used to form the current interface includes: service packet data corresponding to the service category displayed by the current interface, and detailed data of the service corresponding to the service view displayed by the current interface in the service category. The service packet data corresponding to the service category includes: an identifier of a service belonging to the service category. The detailed data of the service mainly refers to some configuration data required for generating the service view corresponding to the service, such as a picture of the service, a running picture, a title, a subtitle, a jump URL, and the like.

Based on the first service data described above, the service update data is mainly update data related to the detailed data of the service and/or the service packet data.

After obtaining the service update data, the client updates the first service data used by the current interface according to the service update data to obtain the second service data. Thereafter, a new interface is formed based on the second service data.

It is worth noting that the second service data also includes: service packet data and service specific data, specifically: service packet data corresponding to the service category that needs to be displayed on the new interface, and services that need to be presented in the service. The detailed data of the service corresponding to the service view displayed under the category.

Based on the foregoing, the client may specifically display the service category that needs to be presented on the new interface according to the service group data included in the second service data, and include the service packet data and the second service data included in the second service data. The detailed data of the service, under the service category that needs to be presented, presents a service view that needs to be presented, thereby obtaining a new interface.

Further, the client may trigger the callback manner to display the service category to be presented in the new interface according to the service group data included in the second service data, and include the service packet data and the second service data according to the second service data. The detailed data of the service, showing the service view that needs to be presented under the service category that needs to be presented.

Specifically, the client may include: a data module and a user interface (UI) module. The data module is mainly used to obtain, from the server, the service update data required for updating the interface provided by the client for displaying the service information, and update the first service data used to form the current interface according to the service update data, and obtain the second Service data. The data module here is equivalent to the acquisition module and the update module in the subsequent client device embodiment, but is not limited thereto.

The UI module can pre-register a callback function, which can be identified by the callback function name. After obtaining the second service data, the data module may send a broadcast message, and carry a callback function name for identifying a callback function pre-registered by the UI module in the broadcast message; after receiving the broadcast message, the UI module obtains the broadcast message Callback function name, by using the callback function identified by the callback function name, actively acquiring the service packet data included in the second service data and the detailed data of the service included in the second service data, and then according to the service packet data included in the second service data, The new interface displays the service category to be presented, and according to the service packet data included in the second service data and the detailed data of the service included in the second service data, the service view that needs to be presented is presented under the service category that needs to be presented.

Specifically, the UI module may determine the specific data of the service under each service category according to the service packet data included in the second service data, generate a service view according to the detailed data of each service, and further may follow each service category. The service views are arranged in the order of the services, and finally the service views are displayed on the new interface in the arranged order. On the basis of FIG. 2, as shown in FIG. 3, a service category and a service view under the service category are displayed on the new interface. The service view shown in FIG. 3 may include an access portal that jumps to the corresponding service. In FIG. 3, the service category displayed is entertainment, and the entertainment category includes a lottery service view, a movie service view, and a reading service. Views, news service views, segment subservice views, and beauty service views. When the user clicks on the service view, then jump to the corresponding service, continue to use Figure 3 as an example, if the user clicks to buy the lottery service The service view can be redirected to the service for purchasing the lottery ticket. Specifically, the service can be provided to the user in various ways, for example, it can be a web page form, a local APP form, a WEB APP form, or the like. Compared with Figure 2, the new interface shown in Figure 3 shows less of the original service view and several new service views. It is worth noting that the service view can be colored and is not limited to the gray shown in FIG.

In this embodiment, the client obtains the service update data from the server to update the interface provided by the client for displaying the service information; and according to the acquired service update data, the first service data used to form the current interface is formed. An update is made to obtain second service data, and a new interface is formed according to the second service data. Therefore, in this embodiment, the client can automatically complete the interface update, and the user does not need to manually download and install the upgrade package, and the interface update operation is relatively simple, which is beneficial to improving the efficiency of the update interface.

In addition, the method provided by the embodiment not only simplifies the interface update operation, but also improves the efficiency of updating the interface, and can customize the interface layout according to the upgrade and diversity of the service, optimize the interface layout method, and enhance the client following service. The adaptability of change provides users with a more personalized and customized interface layout, which is conducive to providing more abundant service information.

In practical applications, the server can maintain two types of data: one is the detailed data of the service, and the other is the service packet data.

For each service, the server can store the detailed data of the service. The detailed data here mainly refers to some configuration data required to generate the service view corresponding to the service, and generally includes but is not limited to the following data: service identifier (service_id) , the picture of the service, the operation picture, the background, the creation time of the service, the modification (or update) time of the service, the access entry provided by the service (ie the jump URL) and the type of access (eg whether login is required), service provider, etc. . The service identifier can uniquely identify a service; the service picture, background, operation picture, etc. can be set through a logo field, which can be a Java Object Notation (JSON) value, if configured Various pictures about the service, these picture fields may be picture addresses identified by content://, http://, or assets://. A code example of defining the details of a service for a server as follows:

In this application, the interface provided by the client mainly serves the service view under the service category + service category. The format is displayed. Therefore, the server can configure one service packet data for each service category. For service packet data, the server defines a class of associated services that can be flexibly controlled according to specific business scenarios. The service packet data includes, but is not limited to, the following data: a name and an identifier (id) of the service packet, and a service identification list for storing an identifier of a service belonging to the service class corresponding to the service packet data. A code example that defines service grouping data for the server as follows:

Based on the above, one way for the client to obtain the service update data required by the client to update the interface provided by the client for displaying the service information includes:

The client sends a synchronization request to the server, where the synchronization request includes: a timestamp of the last time the client obtains the service update data;

The server parses the data and locally from the locally stored service according to the timestamp in the synchronization request. In the detailed data of the stored service, the data whose modification time is after the time stamp is obtained as the service update data, and is returned to the client;

The client receives the service update data returned by the server.

In this embodiment, the server is required to record the detailed data of the service and the modification time of the service packet data in order to accurately provide the service update data to the client.

In addition, in this embodiment, both the service specific data and the service packet data are synchronized in an incremental synchronization manner, that is, each time the synchronization service details data and the packet service data are only incremented, so that It saves traffic very well and ensures that the client can successfully receive service update data in case of unstable network.

In another optional implementation manner, considering that the service packet data is relatively simple, the amount of data is small, and the possibility of change is small, the client may adopt a full-quantity synchronization manner, that is, each service packet data is acquired for each service packet data. It can be requested once at a certain time, and the service packet data is not required to be too frequent, which can reduce the processing load of the client and the server, save traffic, and the like. In this optional implementation manner, for the detailed data of the service, it is preferred to adopt the incremental synchronization mode, that is, the client carries the timestamp of the last request service update data in the synchronization request, so that the server returns only the timestamp. The details of the service that changed later or the part of the data that changed in the detail data.

In an optional implementation manner, the service packet data corresponding to the service category displayed by the current interface may include, in addition to the identifier of the service belonging to the service category, a sequence of services between the services belonging to the service category. The first order information of the order.

It should be noted that the first sequence information used to characterize the order between services may be explicit information, for example, the information may be similar to "identity (ID) according to service from large to small or small to large. An explicit description of the order or the order determined according to the online time of the service. Alternatively, the first sequence information used to characterize the order between the services may also be an implicit information, for example, the order of the services may be represented by the order of the identifiers of the services in the service packet data.

Based on the above, the service update data includes at least one of the following:

The service packet data added after the time stamp and the detailed data of the service of the service category corresponding to the newly added service packet data;

First deletion flag information for characterizing service packet data deleted after the time stamp, the first deletion tag information may include an identification and a deletion flag of the deleted service packet data;

Second order information for characterizing the order of precedence between service packet data adjusted after the timestamp;

The detailed data of the service added after the time stamp and the service group data corresponding to the service category to which the added service belongs;

Second deletion flag information for characterizing the detailed data of the service deleted after the time stamp, for example, the second deletion flag information may be an identifier of the deleted service;

Third order information for characterizing the first order information that is updated after the time stamp.

The updated first sequence information indicates: a sequence of adjustments between the services of the service class represented by the current interface and after the time stamp, that is, the third sequence information is actually used to represent the current interface. The order in which the services of the service class are displayed and adjusted after the timestamp.

The following takes several service update data as an example to describe in detail the process of updating the first service data used to form the current interface to obtain the second service data.

The service update data includes: service packet data added after the time stamp and detailed data of the service category service belonging to the added service packet data.

The client specifically adds the new service packet data and the specific data of the service belonging to the service category corresponding to the newly added service packet data to the first service data to obtain the second service data. The second service data is compared with the first service data, and a service packet data is added, and the service identified by the identifier of each service in the service packet data is added (these services are also the service class corresponding to the service group). Detailed data of the service). Compared with the current interface, the new interface displays a service category and a service view displayed under the service category.

If the service update data includes: first deletion flag information for characterizing the service packet data deleted after the time stamp.

The client may delete the service packet data identified by the first deletion tag information and the service class service corresponding to the service packet data identified by the first deletion tag information from the first service data according to the first deletion tag information. Detailed data to obtain second service data. The service of the service category corresponding to the service packet data identified by the first deletion mark information, that is, the service identified by the identifier of each service in the service packet data indicated by the first deletion mark information. The second service data is one less service packet data than the first service data, and the detailed data of the service identified by the identifier of each service in the service packet data. Compared with the current interface, the new interface shows a service category and a service view under the service category.

If the service update data includes: the detailed data of the service added after the time stamp and the service packet data corresponding to the service category to which the added service belongs.

Then, the client adds the specific data of the added service to the first service data, and replaces the original service packet data with the service packet data corresponding to the service category to which the added service belongs to obtain the second service data. Compared with the first service data, the second service data mainly adds the detailed data of one service, and the service packet data in which the added service is located changes, that is, the identifier of the added service is increased. The new interface shows a service view compared to the current interface.

If the service update data includes: second deletion flag information for characterizing the detail data of the service deleted after the time stamp.

The client may delete the detailed data of the service identified by the second deletion tag information from the first service data according to the second deletion tag information, and delete the identifier of the deleted service from the service packet data to which the service belongs. Obtain second service data. The second service data is less than the first service data, and the service packet data of the deleted service is changed, that is, the identifier of the deleted service is deleted. The new interface shows less of a service view than the current interface.

It is worth noting that if the service update data includes two or more types of update data (see several of the above), the client can combine the above-mentioned update process for each data to obtain a complete update process. .

It should be noted that, for the foregoing method embodiments, for the sake of simple description, It is described as a series of combinations of actions, but those skilled in the art will appreciate that the present application is not limited by the sequence of actions described, as some steps may be performed in other sequences or concurrently in accordance with the present application. In the following, those skilled in the art should also understand that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by the present application.

In the above embodiments, the descriptions of the various embodiments are different, and the details that are not detailed in a certain embodiment can be referred to the related descriptions of other embodiments.

FIG. 4 is a schematic structural diagram of a client according to an embodiment of the present application. As shown in FIG. 4, the client includes an acquisition module 41, an update module 42, and an interface module 43.

The obtaining module 41 is configured to obtain, from the server, service update data required for updating an interface provided by the client for displaying service information.

The update module 42 is connected to the acquisition module 41 for updating the first service data used by the current interface according to the service update data acquired by the acquisition module 41 to obtain the second service data. The first service data includes: service group data corresponding to the service category displayed by the current interface, and detailed data of the service corresponding to the service view displayed by the current interface in the service category; the service group data corresponding to the service category includes: The identifier of the service that belongs to the service category.

The interface module 43 is connected to the update module 42 for forming a new interface according to the second service data obtained by the update module 42.

In an optional implementation, the obtaining module 41 is specifically configured to: send a synchronization request to the server, and receive service update data returned by the server; and the synchronization request includes: a timestamp of the last time the service update data is acquired. The service update data is data that is obtained by the server from the locally stored service packet data and the service detail data according to the timestamp, and the modification time is after the time stamp.

In an optional implementation manner, the foregoing service update data may include at least one of the following:

First deletion flag information for characterizing service packet data deleted after the time stamp;

Second deletion flag information for characterizing the detailed data of the service deleted after the time stamp;

The first sequence information is used to represent the sequence between services belonging to the service class represented by the current interface; the updated first sequence information indicates: between the services belonging to the service class represented by the current interface, at time The order of adjustment after the stamping, that is, the third sequence information is actually used to characterize the order of adjustment between the services of the service class belonging to the current interface and after the time stamp.

In an optional implementation manner, the detailed data of the service corresponding to the service view includes: access entry information of the service corresponding to the service view; and correspondingly, the service view includes an access entry that jumps to the service. The access entry information of the service is different according to the service delivery manner. For example, if the service is provided in the form of a webpage, the access entry information may be a URL address that jumps to the service, if the service If the information is provided in the form of a local APP or a WEB APP, the access entry information may be the calling interface information of the corresponding APP.

Based on the foregoing embodiments, the second service data includes service packet data corresponding to the service category that needs to be presented on the new interface, and detailed data of the service corresponding to the service view that needs to be presented under the service category that needs to be presented.

Correspondingly, the interface module 43 is specifically configured to: display the service category to be presented in the new interface according to the service group data included in the second service data, and include the service packet data and the second service data included in the second service data. The detailed data of the service, showing the service view that needs to be presented under the service category that needs to be presented.

Further, the client can use the trigger callback method to form a new interface. Specifically, the update module 42 is further configured to send a broadcast message to the interface module 43, where the broadcast message carries a callback function name for identifying a callback function pre-registered by the interface module 43. The interface module 43 is specifically configured to receive the broadcast message sent by the update module 42 and obtain the second service data after the update module 42 obtains the second service data by using the callback function identified by the callback function name carried in the broadcast message. According to the service packet data included in the service and the detailed data of the service included in the second service data, the service category to be presented is displayed in the new interface according to the service packet data included in the second service data, and the service included in the second service data is included The packet data and the detailed data of the service included in the second service data represent a service view that needs to be presented under the service category that needs to be presented.

The client provided in this embodiment may be any client that can provide an interface and needs to perform interface adjustment, and may be, for example, a browser or an application (APP) client.

The client provided by the embodiment obtains the service update data from the server to update the interface provided by the client for displaying the service information; and according to the acquired service update data, the first service data used to form the current interface is formed. An update is made to obtain second service data, and a new interface is formed according to the second service data. Therefore, the client provided in this embodiment can automatically complete the interface update, and does not require the user to manually download and install the upgrade package. The interface update operation is relatively simple, which is beneficial to improving the efficiency of the update interface.

In addition, the client provided in this embodiment not only simplifies the interface update operation, but also improves the efficiency of updating the interface, and can customize the interface layout according to the upgrade and diversity of the service, and optimize the interface layout method, so that the embodiment is The ability of the client to follow the changes of the service is enhanced, which can provide users with a more personalized and customized interface layout, which is conducive to providing more abundant service information.

A person skilled in the art can clearly understand that for the convenience and brevity of the description, the specific working process of the system, the device and the unit described above can refer to the corresponding process in the foregoing method embodiment, and details are not described herein again.

In the several embodiments provided by the present application, it should be understood that the disclosed system, apparatus, and method may be implemented in other manners. For example, the device embodiments described above are merely illustrative. For example, the division of the unit is only a logical function division. In actual implementation, there may be another division manner, for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above integrated unit can be implemented in the form of hardware or in the form of hardware plus software functional units.

The above-described integrated unit implemented in the form of a software functional unit can be stored in a computer readable storage medium. The software functional unit described above is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor to perform the methods described in various embodiments of the present application. Part of the steps. The foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like, which can store program codes. .

Finally, it should be noted that the above embodiments are only used to explain the technical solutions of the present application, and are not limited thereto; although the present application is described in detail with reference to the foregoing embodiments, those skilled in the art should understand that they can still The technical solutions described in the foregoing embodiments are modified, or the equivalents of the technical features are replaced by the equivalents. The modifications and substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present application.

Claims

An interface update method, comprising:

The client obtains, from the server, service update data required to update an interface provided by the client for displaying service information;

The client updates the first service data used to form the current interface according to the service update data, and obtains the second service data. The first service data includes: a service corresponding to the service category displayed by the current interface. Packet data, and the current interface presents detailed data of a service corresponding to the service view under the service category; the service packet data corresponding to the service category includes: an identifier of a service belonging to the service category;

The client forms the new interface according to the second service data.
The method according to claim 1, wherein the client obtains, from the server, service update data required to update an interface provided by the client for displaying service information, including:

The client sends a synchronization request to the server, where the synchronization request includes: a timestamp of obtaining the service update data last time;

And the server obtains, according to the timestamp, data that is modified after the time stamp from the locally stored service packet data and the service detail data as the service update data, and returns the data to the client;

The client receives the service update data returned by the server.
The method of claim 2, wherein the service update data comprises at least one of the following:

The service packet data added after the time stamp and the detailed data of the service of the service category corresponding to the newly added service packet data;

First deletion flag information for characterizing service packet data deleted after the time stamp;

Second order information for characterizing the order of precedence between service packet data adjusted after the timestamp;

The detailed data of the service added after the time stamp and the service class to which the added service belongs Service packet data corresponding to the destination;

Second deletion flag information for characterizing the detail data of the service deleted after the time stamp;

And third order information for characterizing the first order information that is updated after the timestamp, the first order information being used to represent a sequence of priorities between services belonging to the service class represented by the current interface.
The method according to claim 1, wherein the detailed data of the service corresponding to the service view comprises: access entry information of the service corresponding to the service view; the service view includes access to the service Entrance.
The method according to any one of claims 1 to 4, wherein the second service data comprises: service packet data corresponding to a service category that needs to be presented on the new interface, and needs in the need The detailed data of the service corresponding to the service view displayed under the service category;

Forming, by the client, the new interface according to the second service data, including:

And the client, according to the service group data included in the second service data, displaying the service category that needs to be presented in the new interface, and according to the service packet data and the second information included in the second service data. The detailed data of the service included in the service data presents a service view that needs to be presented under the service category that needs to be presented.
The method according to claim 5, wherein the client presents the service category to be presented in the new interface according to the service group data included in the second service data, and according to the first The service packet data included in the service data and the detailed data of the service included in the second service data, and the service view that needs to be presented are displayed in the service category that needs to be presented, including:

The client adopts a trigger callback manner to display the service category to be presented in the new interface according to the service group data included in the second service data, and according to the service group included in the second service data. The data and the detailed data of the service included in the second service data present a service view that needs to be presented under the service category that needs to be presented.
A client, comprising:

An obtaining module, configured to obtain, from a server, an update provided by the client for displaying service information Service update data required by the interface;

And an update module, configured to update, according to the service update data, the first service data used by the current interface to obtain the second service data, where the first service data includes: the service category corresponding to the current interface Service packet data, and the current interface presents detailed data of a service corresponding to the service view under the service category; the service packet data corresponding to the service category includes: an identifier of a service belonging to the service category;

And an interface module, configured to form the new interface according to the second service data.
The client according to claim 7, wherein the obtaining module is specifically configured to:

Sending a synchronization request to the server, and receiving the service update data returned by the server; the synchronization request includes: a timestamp of obtaining the service update data last time;

The service update data is data that is obtained by the server from the locally stored service packet data and the detailed data of the service after the time stamp according to the time stamp.
The client according to claim 8, wherein the service update data comprises at least one of the following:

The service packet data added after the time stamp and the detailed data of the service of the service category corresponding to the newly added service packet data;

First deletion flag information for characterizing service packet data deleted after the time stamp;

Second order information for characterizing the order of precedence between service packet data adjusted after the timestamp;

The detailed data of the service added after the time stamp and the service packet data corresponding to the service category to which the added service belongs;

Second deletion flag information for characterizing the detail data of the service deleted after the time stamp;

And third order information for characterizing the first order information that is updated after the timestamp, the first order information being used to represent a sequence of priorities between services belonging to the service class represented by the current interface.
The client according to claim 7, wherein the service view corresponds to the service The detailed data of the service includes: access entry information of the service corresponding to the service view; and the service view includes an access entry to the service.
The client according to any one of claims 7 to 10, wherein the second service data comprises: service group data corresponding to a service category that needs to be presented on the new interface, and The detailed data of the service corresponding to the service view displayed under the service category to be displayed;

The interface module is specifically configured to:

And displaying, according to the service group data included in the second service data, the service category that needs to be presented in the new interface, and according to the service packet data included in the second service data and the second service data The detailed data of the service, showing the service view that needs to be presented under the service category that needs to be presented.
The client of claim 11 wherein:

The update module is further configured to: send a broadcast message to the interface module, where the broadcast message carries a callback function name for identifying a callback function pre-registered by the interface module;

The interface module is specifically configured to:

Receiving the broadcast message sent by the update module, and acquiring the second service data after the update module obtains the second service data by using the callback function identified by the callback function name carried by the broadcast message The service packet data included in the service data and the detailed data of the service included in the second service data, and the service category to be presented is presented in the new interface according to the service packet data included in the second service data, And displaying, according to the service packet data included in the second service data and the detailed data of the service included in the second service data, a service view that needs to be presented under the service category that needs to be presented.