CN111026416A - Data updating method, system, device, electronic equipment and computer storage medium - Google Patents

Abstract

Embodiments of the present disclosure disclose a data update method, system, device, electronic device, and computer storage medium. The data update method includes uploading update data of a target application to a content distribution server; obtaining the update data in the content Update information on the distribution server, wherein the update information includes information that can obtain a first storage address and a first update timestamp of the update data on the content distribution server; Update information request, and return the update information. The technical solution relieves the pressure of the server receiving the update information request, and at the same time avoids the problem of resource waste caused by the client polling and actively requesting update data.

Description

Data update method, system, device, electronic device and computer storage medium

technical field

The present disclosure relates to the technical field of computer applications, and in particular, to a data update method, system, device, electronic device, and computer storage medium.

Background technique

With the development of Internet technology, users have put forward higher requirements for the enrichment and diversification of client application (APP) functions. Server-side technology developers need to continuously improve the functions of applications, form updated data of applications, and generate new , so that users can update the application on the client side. In the prior art, there are generally two ways for the client to obtain the application update data: the server actively pushes the update data or the client polls and actively requests the update data. The server actively pushes the update data, that is, the server establishes a long link with the client. When the server has updated data of the application, it will actively push the updated data of the application to the target client. The client polls actively to request update data, that is, the client can control the request time period and request the latest application update data from the server.

SUMMARY OF THE INVENTION

In order to solve the problems in the related art, embodiments of the present disclosure provide a data update method, system, apparatus, electronic device, and computer storage medium.

In a first aspect, an embodiment of the present disclosure provides a data update method.

Specifically, the data update method includes:

Upload the update data of the target application to the content distribution server;

Acquiring update information of the update data on the content distribution server, wherein the update information includes information that can obtain a first storage address and a first update timestamp of the update data on the content distribution server;

The update information is returned in response to the update information request by the gateway for the target application.

With reference to the first aspect, in a first implementation manner of the first aspect of the present disclosure, the update information includes the first storage address of the update data on the content distribution server and the first update timestamp .

With reference to the first aspect, in a second implementation manner of the first aspect of the present disclosure, the update information includes a second storage address and a second update timestamp of the index file corresponding to the target application on the content distribution server ; the index file includes the service identifier, storage address and update time stamp of at least one target service of the target application; the update data includes the update data of at least one target service of the target application.

With reference to the second implementation manner of the first aspect, in the third implementation manner of the first aspect of the present disclosure, acquiring the update information of the update data on the content distribution server includes:

acquiring the first storage address and the first update timestamp of the update data on the content distribution server;

Update the index file according to the first storage address and the first update timestamp;

uploading the index file to the content distribution server;

Obtain the second storage address and the second update timestamp.

With reference to the third implementation manner of the first aspect, in a fourth implementation manner of the first aspect of the present disclosure, the updating of the index file according to the first storage address and the first update timestamp includes:

The update address and the update timestamp associated with the service identifier of the target service in the index file are updated to the first storage address and the first update timestamp.

With reference to the second implementation manner of the first aspect, in a fifth implementation manner of the first aspect of the present disclosure, the target service includes a configuration center service, an offline package service, and a patch service.

In a second aspect, an embodiment of the present disclosure provides a data update method.

Specifically, the data update method includes:

receiving a request sent by a target application, wherein the request includes an application identifier of the target application;

Carrying the update information of the target application in the response data and returning it to the client, where the update information includes a first storage address and a first update timestamp on the content distribution server that can obtain the update data of the target application Information.

With reference to the second aspect, in a first implementation manner of the second aspect, the update information includes the first storage address of the update data on the content distribution server and the first update timestamp .

With reference to the second aspect, in a second implementation manner of the second aspect of the present disclosure, the update information includes a second storage address and a second update timestamp of the index file corresponding to the target application on the content distribution server ; the index file includes the service identifier, storage address and update time stamp of at least one target service of the target application; the update data includes the update data of at least one target service of the target application.

With reference to the second aspect, in a third implementation manner of the second aspect of the present disclosure, the carrying the update information of the target application in the response data and returning it to the client includes:

Determine whether the update information of the target application is stored locally according to the application identifier;

When the update information of the target application is stored locally, the update information of the target application is carried in the response data and returned to the client.

With reference to the second aspect, in a fourth implementation manner of the second aspect, after receiving the request sent by the target application, the present disclosure further includes:

obtaining the application identifier of the target application carried in the request;

When the application identifier is not stored in the local application list, the application identifier is added to the local application list.

In conjunction with the fourth implementation manner of the second aspect, in the fifth implementation manner of the second aspect, the present disclosure further includes:

Periodically sending an update information request of the target application to the server;

The update information of the target application returned by the server is received.

With reference to the second implementation manner of the second aspect, in a sixth implementation manner of the second aspect of the present disclosure, the target service includes a configuration center service, an offline package service, and a patch service.

In a third aspect, an embodiment of the present disclosure provides a data update method.

Specifically, the data update method includes:

Send a request carrying the application identifier of the target application to the gateway;

receiving the response data returned by the gateway;

acquiring the update information added by the gateway to the response data, wherein the update information includes information that can acquire the first storage address and the first update timestamp of the update data of the target application on the content distribution server;

Whether to update the target application is determined according to the update information.

With reference to the third aspect, in a first implementation manner of the third aspect of the present disclosure, the update information includes the first storage address of the update data on the content distribution server and the first update timestamp .

With reference to the third aspect, in a second implementation manner of the third aspect of the present disclosure, the update information includes a second storage address and a second update timestamp of the index file corresponding to the target application on the content distribution server ; the index file includes the service identifier, storage address and update time stamp of at least one target service of the target application; the update data includes the update data of at least one target service of the target application.

With reference to the third aspect, in a third implementation manner of the third aspect of the present disclosure, the sending a request carrying the application identifier of the target application to the gateway includes:

Intercepting the request sent by the target application to the server;

The application identifier of the target application is carried in the request and sent to the gateway of the server.

With reference to the first implementation manner of the third aspect, in a fourth implementation manner of the third aspect of the present disclosure, the determining whether to update the target application according to the update information includes:

When the first update time stamp is later than the third local update time stamp of the target application, it is recorded that the target application has update data.

With reference to the first implementation manner of the third aspect, in a fifth implementation manner of the third aspect of the present disclosure, the determining whether to update the target application according to the update information includes:

When the first update time stamp is later than the local third update time stamp of the target application, downloading the update data of the target application from the first storage address;

The target application is updated according to the update data of the target application.

With reference to the second implementation manner of the third aspect, in a sixth implementation manner of the third aspect of the present disclosure, the determining whether to update the target application according to the update information includes:

When the second update time stamp is later than the fourth update time stamp of the local index file, downloading the index file from the second storage address;

Whether to update the target application is determined according to the first update timestamp corresponding to the service identifier of the at least one target service in the index file.

With reference to the sixth implementation manner of the third aspect, in the seventh implementation manner of the third aspect of the present disclosure, the determination is based on the first update timestamp corresponding to the service identifier of the at least one target service in the index file. Whether to update the target application, including:

When the first update time stamp is later than the locally stored fifth update time stamp corresponding to the at least one target service, record that the target service has update data.

With reference to the sixth implementation manner of the third aspect, in the eighth implementation manner of the third aspect of the present disclosure, the determination is based on the first update timestamp corresponding to the service identifier of the at least one target service in the index file. Whether to update the target application, including:

When the first update time stamp is later than the locally stored fifth update time stamp corresponding to the at least one target service, downloading the update data of the target service from the first storage address;

The target service is updated according to the update data of the target service.

With reference to the second implementation manner of the third aspect, in a ninth implementation manner of the third aspect of the present disclosure, the target service includes a configuration center service, an offline package service, and a patch service.

In a fourth aspect, an embodiment of the present disclosure provides a data update method.

Specifically, the data update method includes:

The server uploads the update data of the target application to the content distribution server, and obtains the update information of the update data on the content distribution server, wherein the update information includes that the update data can be obtained on the content distribution server information of the first storage address and the first update timestamp;

The server returns the update information to the gateway in response to the update information request of the gateway for the target application;

The gateway receives the request sent by the target application, and returns the update information of the target application in response data to the client, wherein the request includes the application identifier of the target application;

The client acquires the update information added by the gateway in the response data, and determines whether to update the target application according to the update information.

With reference to the fourth aspect, in a first implementation manner of the fourth aspect of the present disclosure, the update information includes the first storage address of the update data on the content distribution server and the first update timestamp .

With reference to the fourth aspect, in a second implementation manner of the fourth aspect of the present disclosure, the update information includes a second storage address and a second update timestamp of the index file corresponding to the target application on the content distribution server ; the index file includes the service identifier, storage address and update time stamp of at least one target service of the target application; the update data includes the update data of at least one target service of the target application.

With reference to the second implementation manner of the fourth aspect, in a third implementation manner of the fourth aspect of the present disclosure, the acquiring the update information of the update data on the content distribution server includes:

obtaining, by the server, a first storage address and a first update timestamp of the update data on the content distribution server;

The server updates the index file according to the first storage address and the first update timestamp;

The server uploads the index file to the content distribution server;

The server obtains the second storage address and the second update timestamp.

With reference to the third implementation manner of the fourth aspect, in a fourth implementation manner of the fourth aspect of the present disclosure, the server updates the index file according to the first storage address and the first update timestamp, including:

The server updates the update address and the update timestamp associated with the service identifier of the target service in the index file to the first storage address and the first update timestamp.

With reference to the fourth aspect, in a fifth implementation manner of the fourth aspect of the present disclosure, the gateway receives the request sent by the target application, and carries the update information of the target application in response data and returns it to the client end, including:

obtaining, by the gateway, the application identifier of the target application carried in the request;

When the application identifier is not stored in the local application list, the gateway adds the application identifier to the local application list;

The gateway determines whether the update information of the target application is stored locally according to the application identifier;

When the update information of the target application is stored locally, the gateway carries the update information of the target application in the response data and returns it to the client.

In conjunction with the fourth aspect, in a sixth implementation manner of the fourth aspect, the present disclosure further includes:

The gateway periodically sends the update information request of the target application to the server;

The gateway receives the update information of the target application returned by the server.

In conjunction with the fourth aspect, in a seventh implementation manner of the fourth aspect, the present disclosure further includes:

sending, by the client, the request carrying the application identifier of the target application to the gateway;

The client receives the response data returned by the gateway.

With reference to the seventh implementation manner of the fourth aspect, in the eighth implementation manner of the fourth aspect of the present disclosure, the client sends the request carrying the application identifier of the target application to the gateway, include:

The client intercepts the request sent by the target application to the server;

The client sends the request to the gateway of the server by carrying the application identifier of the target application in the request.

With reference to the first implementation manner of the fourth aspect, in a ninth implementation manner of the fourth aspect, the client determines whether to update the target application according to the update information, including:

When the first update timestamp is later than the local third update timestamp of the target application, the client records that the target application has updated data.

With reference to the first implementation manner of the fourth aspect, in a tenth implementation manner of the fourth aspect, the client determines whether to update the target application according to the update information, including:

When the first update timestamp is later than the local third update timestamp of the target application, the client downloads the update data of the target application from the first storage address;

The client updates the target application according to the update data of the target application.

With reference to the second implementation manner of the fourth aspect, in an eleventh implementation manner of the fourth aspect, the client determines whether to update the target application according to the update information, including:

When the second update time stamp is later than the fourth update time stamp of the local index file, the client downloads the index file from the second storage address;

The client determines whether to update the target application according to the first update timestamp corresponding to the service identifier of the at least one target service in the index file.

With reference to the eleventh implementation manner of the fourth aspect, in the twelfth implementation manner of the fourth aspect of the present disclosure, the client is based on the first The update timestamp determines whether to update the target application, including:

When the first update timestamp is later than the locally stored fifth update timestamp corresponding to the at least one target service, the client records that the target service has updated data.

With reference to the eleventh implementation manner of the fourth aspect, in the thirteenth implementation manner of the fourth aspect of the present disclosure, the client is based on the first The update timestamp determines whether to update the target application, including:

When the first timestamp is later than the locally stored fifth update timestamp corresponding to the at least one target service, the client downloads the update data of the target service from the first storage address;

The client updates the target service according to the update data of the target service.

With reference to the second implementation manner of the fourth aspect, in a fourteenth implementation manner of the fourth aspect of the present disclosure, the target service includes a configuration center service, an offline package service, and a patch service.

In a fifth aspect, an embodiment of the present disclosure provides a data update system.

Specifically, the data update system includes: a server, a gateway and a client, wherein,

The server is configured to upload the update data of the target application to the content distribution server, obtain the update information of the update data on the content distribution server, and in response to the update information request for the target application by the gateway, send the update information to the content distribution server. the gateway returns the update information, wherein the update information includes information that can obtain the first storage address and the first update timestamp of the update data on the content distribution server;

the gateway, configured to receive a request sent by the target application, and carry the update information of the target application in response data and return it to the client, where the request includes the application identifier of the target application;

The client is configured to send the request carrying the application identifier of the target application to the gateway, receive the response data returned by the gateway, obtain the gateway and add it to the response data update information, and determine whether to update the target application according to the update information.

With reference to the fifth aspect, in a first implementation manner of the fifth aspect, the update information includes the first storage address of the update data on the content distribution server and the first update timestamp .

With reference to the fifth aspect, in a second implementation manner of the fifth aspect of the present disclosure, the update information includes a second storage address and a second update timestamp of the index file corresponding to the target application on the content distribution server ; the index file includes the service identifier, storage address and update time stamp of at least one target service of the target application; the update data includes the update data of at least one target service of the target application.

With reference to the second implementation manner of the fifth aspect, in a third implementation manner of the fifth aspect, the server is configured to acquire the first storage address and the first storage address of the update data on the content distribution server. Update the timestamp, update the index file according to the first storage address and the first update timestamp, upload the index file to the content distribution server, and obtain the second storage address and the second update time stamp.

With reference to the third implementation manner of the fifth aspect, in a fourth implementation manner of the fifth aspect, the server is configured to associate the service identifier of the target service in the index file with the The update address and the update timestamp are updated to the first storage address and the first update timestamp.

With reference to the fifth aspect, in a fifth implementation manner of the fifth aspect of the present disclosure, the gateway is configured to obtain the application identifier of the target application carried in the request, and the application identifier is not stored in the local application list When applying an identifier, add the application identifier to the local application list, determine whether the update information of the target application is locally stored according to the application identifier, and when the update information of the target application is stored locally, add the update information of the target application to the local application list. The update information of the target application is carried in the response data and returned to the client.

With reference to the fifth aspect, in a sixth implementation manner of the fifth aspect, the gateway is configured to periodically send the update information request of the target application to the server, and receive the information returned by the server. the update information of the target application.

With reference to the fifth aspect, in a seventh implementation manner of the fifth aspect, the client is configured to send the request carrying the application identifier of the target application to the gateway, and receive the request The response data returned by the gateway.

With reference to the seventh implementation manner of the fifth aspect, in the eighth implementation manner of the fifth aspect, the client is configured to intercept the request sent by the target application to the server, and send the request to the server. The application identifier of the target application is carried in the request and sent to the gateway of the server.

With reference to the first implementation manner of the fifth aspect, in a ninth implementation manner of the fifth aspect, the client is configured to: When the timestamp is updated, it is recorded that the target application has updated data.

With reference to the first implementation manner of the fifth aspect, in a tenth implementation manner of the fifth aspect, the client is configured to, when the first update timestamp is later than the local third update timestamp of the target application When the time stamp is updated, the update data of the target application is downloaded from the first storage address, and the target application is updated according to the update data of the target application.

With reference to the second implementation manner of the fifth aspect, in an eleventh implementation manner of the fifth aspect of the present disclosure, when the second update timestamp of the client is later than the fourth update timestamp of the local index file , downloading the index file from the second storage address, and determining whether to update the target application according to the first update timestamp corresponding to the service identifier of the at least one target service in the index file.

With reference to the eleventh implementation manner of the fifth aspect, in the twelfth implementation manner of the fifth aspect of the present disclosure, the first update timestamp of the client is later than the locally stored at least one target service When the corresponding fifth update time stamp is used, it is recorded that the target service has update data.

With reference to the eleventh implementation manner of the fifth aspect, in the thirteenth implementation manner of the fifth aspect of the present disclosure, the first time stamp of the client is later than the locally stored corresponding to the at least one target service. When the fifth update time stamp is set, the update data of the target service is downloaded from the first storage address, and the target service is updated according to the update data of the target service.

With reference to the second implementation manner of the fifth aspect, in the fourteenth implementation manner of the fifth aspect of the present disclosure, the target service includes a configuration center service, an offline package service, and a patch service.

In a sixth aspect, an embodiment of the present disclosure provides a data update apparatus.

Specifically, the data update device includes:

an uploading module, configured to upload the update data of the target application to the content distribution server;

A first obtaining module is configured to obtain update information of the update data on the content distribution server, wherein the update information includes a first storage address that can obtain the update data on the content distribution server and information of the first update timestamp;

The first returning module is configured to return the update information in response to the update information request of the gateway for the target application.

With reference to the sixth aspect, in a first implementation manner of the sixth aspect, the update information includes the first storage address of the update data on the content distribution server and the first update timestamp .

With reference to the sixth aspect, in a second implementation manner of the sixth aspect of the present disclosure, the update information includes a second storage address and a second update timestamp of the index file corresponding to the target application on the content distribution server ; the index file includes the service identifier, storage address and update time stamp of at least one target service of the target application; the update data includes the update data of at least one target service of the target application.

With reference to the second implementation manner of the sixth aspect, in the third implementation manner of the sixth aspect of the present disclosure, acquiring the update information of the update data on the content distribution server includes:

acquiring the first storage address and the first update timestamp of the update data on the content distribution server;

Update the index file according to the first storage address and the first update timestamp;

uploading the index file to the content distribution server;

Obtain the second storage address and the second update timestamp.

With reference to the third implementation manner of the sixth aspect, in a fourth implementation manner of the sixth aspect of the present disclosure, the updating of the index file according to the first storage address and the first update timestamp includes:

The update address and the update timestamp associated with the service identifier of the target service in the index file are updated to the first storage address and the first update timestamp.

With reference to the second implementation manner of the sixth aspect, in a third implementation manner of the sixth aspect of the present disclosure, the target service includes a configuration center service, an offline package service, and a patch service.

In a seventh aspect, an embodiment of the present disclosure provides a data update apparatus.

Specifically, the data update device includes:

a first receiving module, configured to receive a request sent by a target application, wherein the request includes an application identifier of the target application;

The second return module is configured to carry the update information of the target application in the response data and return it to the client, wherein the update information includes the first information on the content distribution server that can obtain the update data of the target application. Store address and first update timestamp information.

With reference to the seventh aspect, in a first implementation manner of the seventh aspect of the present disclosure, the update information includes the first storage address of the update data on the content distribution server and the first update timestamp .

With reference to the seventh aspect, in a second implementation manner of the seventh aspect of the present disclosure, the update information includes a second storage address and a second update timestamp of the index file corresponding to the target application on the content distribution server ; the index file includes the service identifier, storage address and update time stamp of at least one target service of the target application; the update data includes the update data of at least one target service of the target application.

With reference to the seventh aspect, in a third implementation manner of the seventh aspect of the present disclosure, the carrying the update information of the target application in the response data and returning it to the client includes:

Determine whether the update information of the target application is stored locally according to the application identifier;

When the update information of the target application is stored locally, the update information of the target application is carried in the response data and returned to the client.

In conjunction with the seventh aspect, in a fourth implementation manner of the seventh aspect, the present disclosure further includes:

a second obtaining module, configured to obtain the application identifier of the target application carried in the request;

The adding module is configured to add the application identifier to the local application list when the application identifier is not stored in the local application list.

In conjunction with the fourth implementation manner of the seventh aspect, in the fifth implementation manner of the seventh aspect, the present disclosure further includes:

a first sending module, configured to periodically send an update information request of the target application to the server;

The second receiving module is configured to receive the update information of the target application returned by the server.

With reference to the second implementation manner of the seventh aspect, in the sixth implementation manner of the seventh aspect of the present disclosure, the target service includes a configuration center service, an offline package service, and a patch service.

In an eighth aspect, an embodiment of the present disclosure provides a data update apparatus.

Specifically, the data update device includes:

a second sending module, configured to send a request carrying the application identifier of the target application to the gateway;

a third receiving module, configured to receive the response data returned by the gateway;

The third acquiring module is configured to acquire update information added by the gateway to the response data, wherein the update information includes a first storage address on the content distribution server that can acquire the update data of the target application and information of the first update timestamp;

The determining module is configured to determine whether to update the target application according to the update information.

With reference to the eighth aspect, in a first implementation manner of the eighth aspect, the update information includes the first storage address of the update data on the content distribution server and the first update timestamp .

With reference to the eighth aspect, in a second implementation manner of the eighth aspect of the present disclosure, the update information includes a second storage address and a second update timestamp of the index file corresponding to the target application on the content distribution server ; the index file includes the service identifier, storage address and update time stamp of at least one target service of the target application; the update data includes the update data of at least one target service of the target application.

With reference to the eighth aspect, in a third implementation manner of the eighth aspect of the present disclosure, the sending a request carrying the application identifier of the target application to the gateway includes:

Intercepting the request sent by the target application to the server;

The application identifier of the target application is carried in the request and sent to the gateway of the server.

With reference to the first implementation manner of the eighth aspect, in a fourth implementation manner of the eighth aspect of the present disclosure, the determining whether to update the target application according to the update information includes:

When the first update time stamp is later than the third local update time stamp of the target application, it is recorded that the target application has update data.

With reference to the first implementation manner of the eighth aspect, in a fifth implementation manner of the eighth aspect of the present disclosure, the determining whether to update the target application according to the update information includes:

When the first update time stamp is later than the local third update time stamp of the target application, downloading the update data of the target application from the first storage address;

The target application is updated according to the update data of the target application.

With reference to the second implementation manner of the eighth aspect, in a sixth implementation manner of the eighth aspect of the present disclosure, the determining whether to update the target application according to the update information includes:

When the second update time stamp is later than the fourth update time stamp of the local index file, downloading the index file from the second storage address;

Whether to update the target application is determined according to the first update timestamp corresponding to the service identifier of the at least one target service in the index file.

With reference to the sixth implementation manner of the eighth aspect, in the seventh implementation manner of the eighth aspect of the present disclosure, the determination is based on the first update timestamp corresponding to the service identifier of the at least one target service in the index file. Whether to update the target application, including:

When the first update time stamp is later than the locally stored fifth update time stamp corresponding to the at least one target service, record that the target service has update data.

With reference to the sixth implementation manner of the eighth aspect, in the eighth implementation manner of the eighth aspect of the present disclosure, the determination is based on the first update timestamp corresponding to the service identifier of the at least one target service in the index file. Whether to update the target application, including:

When the first update time stamp is later than the locally stored fifth update time stamp corresponding to the at least one target service, downloading the update data of the target service from the first storage address;

The target service is updated according to the update data of the target service.

With reference to the second implementation manner of the eighth aspect, in a ninth implementation manner of the eighth aspect of the present disclosure, the target service includes a configuration center service, an offline package service, and a patch service.

In a ninth aspect, embodiments of the present disclosure provide an electronic device, including a memory and a processor, wherein the memory is used to store one or more computer instructions, wherein the one or more computer instructions are processed by the The controller executes to implement the following method steps:

Upload the update data of the target application to the content distribution server;

Acquiring update information of the update data on the content distribution server, wherein the update information includes information that can obtain a first storage address and a first update timestamp of the update data on the content distribution server;

The update information is returned in response to the update information request by the gateway for the target application.

In a tenth aspect, embodiments of the present disclosure provide an electronic device, including a memory and a processor, wherein the memory is used to store one or more computer instructions, wherein the one or more computer instructions are processed by the The controller executes to implement the following method steps:

receiving a request sent by a target application, wherein the request includes an application identifier of the target application;

Carrying the update information of the target application in the response data and returning it to the client, where the update information includes a first storage address and a first update timestamp on the content distribution server that can obtain the update data of the target application Information.

In an eleventh aspect, an embodiment of the present disclosure provides an electronic device, including a memory and a processor, wherein the memory is used to store one or more computer instructions, wherein the one or more computer instructions are The processor executes to implement the following method steps:

Send a request carrying the application identifier of the target application to the gateway;

receiving the response data returned by the gateway;

acquiring the update information added by the gateway to the response data, wherein the update information includes information that can acquire the first storage address and the first update timestamp of the update data of the target application on the content distribution server;

Whether to update the target application is determined according to the update information.

In a twelfth aspect, an embodiment of the present disclosure provides a readable storage medium on which computer instructions are stored, and when the computer instructions are executed by a processor, implement the first aspect, the first implementation manner of the first aspect to The fifth implements the method described in any one of the implementation manners.

In a thirteenth aspect, an embodiment of the present disclosure provides a readable storage medium on which computer instructions are stored, and when the computer instructions are executed by a processor, implement the second aspect, the first implementation manner of the second aspect to The method described in any one of the sixth implementation manners.

In a fourteenth aspect, an embodiment of the present disclosure provides a readable storage medium on which computer instructions are stored, and when the computer instructions are executed by a processor, implement the first aspect, the first implementation manner of the first aspect to The method described in any one of the ninth implementation manners.

In a fifteenth aspect, an embodiment of the present disclosure provides a readable storage medium on which computer instructions are stored, and when the computer instructions are executed by a processor, implement the first aspect, the first implementation manner of the first aspect to The method described in any one of the fourteenth implementation manners.

According to the technical solutions provided by the embodiments of the present disclosure, the update data of the target application is uploaded to the content distribution server, and the update information of the update data on the content distribution server is obtained, wherein the update information includes the ability to obtain the update data on the content distribution server. The information of the first storage address and the first update timestamp, and then the update information is returned in response to the update information request of the target application by the gateway, thereby relieving the pressure of the server to receive the update information request, and avoiding the client polling actively requesting the update. The problem of waste of resources in the data mode.

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

Description of drawings

Other features, objects and advantages of the present disclosure will become more apparent from the following detailed description of non-limiting embodiments, taken in conjunction with the accompanying drawings. In the attached image:

1 shows a flowchart of a data update method according to an embodiment of the present disclosure;

2 shows a flowchart of acquiring update information of the update data on the content distribution server according to an embodiment of the present disclosure;

3 shows a flowchart of a data update method according to an embodiment of the present disclosure;

4 shows a flowchart of a data update method according to an embodiment of the present disclosure;

5 shows a flowchart of carrying the update information of the target application in response data and returning it to the client according to an embodiment of the present disclosure;

6 shows a flowchart of a data update method according to an embodiment of the present disclosure;

FIG. 7 shows a flowchart of a data update method according to an embodiment of the present disclosure;

8 shows a flowchart of sending a request carrying an application identifier of a target application to a gateway according to an embodiment of the present disclosure;

FIG. 9 shows a flowchart of determining whether to update the target application according to the update information according to an embodiment of the present disclosure;

10 shows a flowchart of determining whether to update the target application according to the first update timestamp corresponding to the service identifier of the at least one target service in the index file according to an embodiment of the present disclosure;

11 shows a flowchart of a data update method according to an embodiment of the present disclosure;

FIG. 12 shows a flowchart of acquiring update information of the update data on the content distribution server according to an embodiment of the present disclosure;

13 shows a flowchart of the gateway receiving the request sent by the target application and returning the update information of the target application to the client in response data according to an embodiment of the present disclosure;

14 shows a flowchart of a data update method according to an embodiment of the present disclosure;

15 shows a flowchart of a data update method according to an embodiment of the present disclosure;

16 shows a flowchart of the client sending the request carrying the application identifier of the target application to the gateway according to an embodiment of the present disclosure;

FIG. 17 shows a flowchart of the client determining whether to update the target application according to the update information according to an embodiment of the present disclosure;

18 shows a flowchart of the client determining whether to update the target application according to the first update timestamp corresponding to the service identifier of the at least one target service in the index file according to an embodiment of the present disclosure;

FIG. 19 shows a schematic structural diagram of a data update system 1900 according to an embodiment of the present disclosure;

FIG. 20 shows a structural block diagram of a data update apparatus 2000 according to an embodiment of the present disclosure;

FIG. 21 shows a structural block diagram of a data update apparatus 2100 according to an embodiment of the present disclosure;

FIG. 22 shows a structural block diagram of a data update apparatus 2200 according to an embodiment of the present disclosure;

FIG. 23 shows a structural block diagram of an electronic device 2300 according to an embodiment of the present disclosure;

FIG. 24 shows a schematic structural diagram of a computer system suitable for implementing the data update method according to an embodiment of the present disclosure.

Detailed ways

Hereinafter, exemplary embodiments of the present disclosure will be described in detail with reference to the accompanying drawings so that those skilled in the art can easily implement them. Also, for the sake of clarity, parts unrelated to describing the exemplary embodiments are omitted from the drawings.

In the present disclosure, it should be understood that terms such as "comprising" or "having" are intended to indicate the presence of features, numbers, steps, acts, components, parts, or combinations thereof disclosed in this specification, and are not intended to exclude a or multiple other features, numbers, steps, acts, components, parts, or combinations thereof may exist or be added.

In addition, it should be noted that the embodiments of the present disclosure and the features of the embodiments may be combined with each other under the condition of no conflict. The present disclosure will be described in detail below with reference to the accompanying drawings and in conjunction with embodiments.

In the way that the server actively pushes the updated data, because the network between the server and the client sometimes becomes unstable, the long link between the server and the client is unstable. Therefore, it is necessary to constantly retry the link to re-establish the connection between the server and the client. long link. At the same time, with the increase of the number of clients, the number of target clients for the server to push the update data will increase, resulting in the uncontrollable situation of the arrival rate, coverage rate and coverage time of the update data pushed by the server. resource.

In the method of client polling and actively requesting update data, the user will shorten the request time period to obtain a fast response from the server, resulting in a rapid increase in the client's request to the server. As the number of clients increases, the pressure on the server will increase. It also needs the support of a large number of databases and other resources at the same time, so it will cause a waste of resources.

FIG. 1 shows a flowchart of a data update method according to an embodiment of the present disclosure, and the data update method is executed on the server side. As shown in Figure 1, the data update method includes the following steps S101-S103:

In step S101, the update data of the target application is uploaded to the content distribution server;

In step S102, the update information of the update data on the content distribution server is obtained, wherein the update information includes a first storage address and a first update address that can obtain the update data on the content distribution server timestamp information;

In step S103, in response to the update information request of the gateway for the target application, the update information is returned.

According to an embodiment of the present disclosure, an application (APP) with different functions is installed in the client, wherein the application may be software installed on the client, such as a communication application, a game application, an entertainment application, a social application, or a practical life application, etc. , which is not specifically limited in the present disclosure. In order to relieve the pressure on the server and improve the response speed and hit rate of data requests, after the technical developer updates the target application, the updated data of the target application can be uploaded to the content distribution server (Content Delivery Network, CDN) through the server. , the target application refers to one or more applications whose data has been updated, and the updated data refers to the changed data in the target application. It should be noted that the server in the embodiment of the present disclosure is the server of the target application, and different target applications may correspond to different servers.

According to an embodiment of the present disclosure, when the number of target applications is two or more, in order to distinguish the update data corresponding to different target applications, the application identifier of the target application and the corresponding update data can be uploaded to the CDN at the same time, wherein, The application identifier is used to identify different versions of different target applications, and the application identifier may include an application unique identifier (appKey) and an application release version number (appVersion). At the same time, the application identifier of the target application and the corresponding update data can be assembled into a key-value data structure and stored in the server's local non-relational database (such as Redis), where the key corresponds to the application identifier and the value corresponds to the update data.

According to the embodiment of the present disclosure, after the update data of the target application is uploaded to the CDN, the update information of the update data on the content distribution server can be further obtained, and the update information includes the first storage address and the first storage address of the content distribution server that can obtain the update data on the content distribution server. Once the information of the time stamp is updated, the update data can be obtained by accessing the first storage address, and the first update time stamp corresponds to the time stamp when the update data is uploaded to the CDN. The present disclosure does not specifically limit the representation form adopted by the first storage address and the method for obtaining the first update timestamp. In order to identify the update information corresponding to the update data of different target applications, the application identifier of the target application and the update information may be stored in association.

As described above, in order to avoid the above-mentioned technical problems that occur in two ways: the server actively pushes the update data or the client polls and actively requests the update data, according to the embodiments of the present disclosure, the gateway can be set to periodically send the update of the target application to the server For the information request, the present disclosure does not specifically limit the period of the update information request, for example, it may be 1S. Since the number of gateways is much smaller than the number of clients, the pressure on the server to receive updated information requests is relieved. In response to the update information request for the target application by the gateway, the server returns the latest update information of the target application. In order to identify the update information requests corresponding to different target applications, the update information request can carry the application identifier of the target application. The server responds to the update information request of the gateway for the target application, and determines the target application corresponding to the current update information request according to the application identifier, and sends The update information of the target application is returned to the gateway.

It should be noted that the gateway mentioned in the embodiments of the present disclosure is a server-side gateway, that is, a gateway through which the server communicates with the outside world. All network requests from the target application on the client to the server side of the target application can enter the server side through the gateway.

According to the technical solutions provided by the embodiments of the present disclosure, the update data of the target application is uploaded to the content distribution server, and the update information of the update data on the content distribution server is obtained, wherein the update information includes the ability to obtain the update data on the content distribution server. The information of the first storage address and the first update timestamp, and then the update information is returned in response to the update information request of the target application by the gateway, thereby relieving the pressure of the server to receive the update information request, and avoiding the client polling actively requesting the update. The problem of waste of resources in the data mode.

According to an embodiment of the present disclosure, the update information includes the first storage address of the update data on the content distribution server and the first update timestamp. In this embodiment, the gateway may directly acquire the first storage address and the first update timestamp from the update information returned by the server. And the update time of the update data of the target application on the CDN can be determined by the first update timestamp, and the update data of the target application can be obtained from the CDN by accessing the first storage address. It can be understood that although the present disclosure uses the first storage address in the form of a Uniform Resource Locator (URL) and the first update timestamp is exemplified by obtaining milliseconds, the present disclosure is not limited thereto. For example, the server uploads the update data of the target application APP1 to the CDN, and obtains the first storage address (https://xxx.xx/a/1json.json) and the first update timestamp (1564114914423) of APP1 on the CDN, The update data can be obtained by accessing the first storage address https://xxx.xx/a/1json.json, and the timestamp of the update data uploaded to the CDN is 1564114914423.

According to another embodiment of the present disclosure, the update information includes a second storage address and a second update timestamp of an index file corresponding to the target application on the content distribution server; the index file includes the target application The service identifier, storage address and update time stamp of at least one target service of the target application; the update data includes the update data of at least one target service of the target application.

According to an embodiment of the present disclosure, the target service may include, but is not limited to, a configuration center service, an offline package service, and a patch service. After one or more target services of the target application have changed, the developer can package the updated one or more target services in the form of updated data of the target service. The following will take the target service as a patch service or an offline package service as an example. However, the present disclosure is not limited thereto. For example, after obtaining the update data of the patch service or the offline package service, the client may update the target application at the local client. If there is only one target service, that is, only one target service of the target application has changed, the update data of the target application includes the update data of this target service; if there are two or more target services, that is, the target application has When two or more target services have changed, the update data of the target application may include the update data of one target service, some target services, or all the target services.

According to the embodiment of the present disclosure, since the update data of the target application may include the update data of one or more target services of the target application, in order to distinguish the update data of different target services, an index file may be established to store the update information of different target services, wherein , the index file may include the service identifier, update address and update timestamp of at least one target service of the target application, wherein the service identifier is used to identify different target services, and the update address corresponds to the latest update address of the target service on the CDN, And by accessing the update address, the update data of the target service can be obtained, and the update time stamp corresponds to the time stamp when the update data of the target service is uploaded to the CDN. The present disclosure will take an example in which the corresponding data of the target application has two target services changed, and the service identifier is in the form of a service name, but the present disclosure is not limited thereto. For example, the target application APP2 has two target services, namely the configuration center service (crystal_config) and the offline package service (speedboat_offline_deploy). Among them, the appKey of APP2 is 25230564, the appVersion is 7.20.4, and the update address of the configuration center service is https: //xxx.xx/b/1json.json, the update timestamp is 1563405958296, the update address of the offline package service is https://xxx.xx/b/2json.json, and the update timestamp is 1564039123355, then the index file of APP2 It can be expressed as:

According to the above embodiments of the present disclosure, the update information includes the second storage address and the second update timestamp of the index file corresponding to the target application on the content distribution server. After receiving the update information, the gateway can access the second storage address by accessing the second storage address. The index file is obtained, and the latest update time of the index file can also be determined by using the second update timestamp. After the index file is obtained through the second storage address, the service identifier, update address and update timestamp of at least one target service of the target application can also be obtained from the index file. For example, the update data newly uploaded by the server to the CDN includes the target application's When updating the data of the target service A, the first storage address and the first update time stamp of the updated data of the target service A on the CDN can be obtained through the index file. The present disclosure does not specifically limit the representation form adopted by the second storage address and the method for obtaining the second update timestamp.

FIG. 2 shows a flowchart of acquiring update information of the update data on the content distribution server according to an embodiment of the present disclosure. As shown in FIG. 2, the step S102, namely acquiring the update information of the update data on the content distribution server, includes the following steps S201-S204:

In step S201, the first storage address and the first update timestamp of the update data on the content distribution server are obtained;

In step S202, the index file is updated according to the first storage address and the first update timestamp;

In step S203, uploading the index file to the content distribution server;

In step S204, the second storage address and the second update timestamp are acquired.

According to the embodiments of the present disclosure, after one or more target services of the target application are updated, the server uploads the updated data to the CDN, and obtains its upload address, that is, the first storage address and the upload time stamp, that is, from the CDN. The first update timestamp. Since the update data of the target application includes the update data of at least one target service of the target application, the first storage address and the first update timestamp of the update data on the content distribution server are obtained, and the The first storage address and the first update time stamp are stored in the index file in association with the service identifiers of one or more target services in the update data, respectively. When the entry is stored, the entry can be updated by using the current first storage address and the first update timestamp, that is, the current index file is updated.

According to the embodiment of the present disclosure, in order to relieve the pressure on the server, the index file can be uploaded to the CDN, and the second storage address and the second update timestamp of the index file on the CDN can be obtained, where the second update timestamp corresponds to The latest timestamp when the index file was uploaded to the CDN. The index file can be obtained by accessing the second storage address, and then the update information of one or more target services corresponding to the target application can be obtained from the index file, for example, the first storage address and the first update timestamp stored in association with the service identifier . When the gateway periodically sends an update information request of the target application to the server, the server may return the second storage address of the index file on the CDN and the second update timestamp to the gateway.

According to an embodiment of the present disclosure, the step S202, that is, updating the index file according to the first storage address and the first update time stamp, may also be implemented as: changing the target service in the index file The update address and the update timestamp associated with the service identifier are updated to the first storage address and the first update timestamp.

In this embodiment, the index file may include update information associated with multiple target service identifiers, and when one or more of the target services are updated, the index file may be updated according to the first storage address of the update data uploaded to the CDN and the first The update timestamp updates the update information corresponding to the service identifiers of one or more target services in the index file. First determine the target service according to the service identifier, then update the update address of the target service to the first storage address, and update the update time stamp to the first update time stamp, thereby completing the update of the index file. For example, the original index file is:

Assuming that only the business file of the configuration center service has changed, and the first storage address is https://xxx.xx/b/3json.json, and the first update timestamp is 1564014914423, the update address of the configuration center service will be https:/ /xxx.xx/b/1json.json is updated to the first storage address https://xxx.xx/b/3json.json, and the update timestamp 1563405958296 is updated to the first update timestamp 1564014914423, thereby obtaining the updated index file for:

FIG. 3 shows a flowchart of a data update method according to an embodiment of the present disclosure, and the data update method is executed on the gateway side. As shown in Figure 3, the data update method includes the following steps S301-S302:

In step S301, a request sent by a target application is received, wherein the request includes an application identifier of the target application;

In step S302, the update information of the target application is carried in the response data and returned to the client, wherein the update information includes a first storage address on the content distribution server that can obtain the update data of the target application and Information about the first update timestamp.

According to the embodiment of the present disclosure, the request sent by the target application on the client to the server of the target application will first reach the gateway of the server, where the target application may be any application installed on the client capable of network communication. In order to determine whether the target application has update information, in the embodiment of the present disclosure, the target application may not directly send the update information request to the server, but a specially developed software development kit (Software Development Kit, SDK) sends the request to the server by intercepting the target application. and add the application identifier of the target application in the request, so as to obtain whether the target application has update information, wherein the application identifier is used to identify different target applications and different versions of the same target application, and the application identifier can include the unique application Identification (appKey) and application release version number (appVersion). Since the request includes a header and a body, the application identifier of the target application can be carried in the header of the request and sent to the server.

According to an embodiment of the present disclosure, after the gateway receives the request data sent by the target application, it can obtain the carried application identifier from the request (eg, packet header), and then compare the application identifier with the application identifier stored locally by the gateway. If the update information corresponding to the application identifier is stored locally, the update information is carried in the response data of the request data and returned to the client. Since the response data includes a header and a body, the update information of the target application can be carried in the header of the response data and returned to the client.

According to the technical solutions provided by the embodiments of the present disclosure, a request sent by a target application that carries an application identifier of the target application is received, and update information of the target application is carried in response data and returned to the client, where the update information includes the ability to Obtain the information of the first storage address and the first update timestamp of the update data of the target application on the content distribution server. The problem of resource waste caused by the client polling and actively requesting update data is avoided, and the gateway directly carries the update information of the target application stored locally in the gateway in the response data and returns it to the client, improving the response of the update data. Speed, so that multiple clients can achieve "second-level" updates at the same time. At the same time, the client sends requests to the server into periodic requests from the gateway to the server, which relieves the pressure on the server to receive update information requests.

According to an embodiment of the present disclosure, the update information includes the first storage address of the update data on the content distribution server and the first update timestamp. In this embodiment, the gateway may directly acquire the first storage address and the first update timestamp from the update information returned by the server. And the update time of the update data of the target application on the CDN can be determined by the first update timestamp, and the update data of the target application can be obtained from the CDN by accessing the first storage address. It can be understood that although the present disclosure uses the first storage address in the form of a Uniform Resource Locator (URL) and the first update timestamp is exemplified by obtaining milliseconds, the present disclosure is not limited thereto. For example, the server uploads the update data of the target application APP1 to the CDN, and obtains the first storage address (https://xxx.xx/a/1json.json) and the first update timestamp (1564114914423) of APP1 on the CDN, The update data can be obtained by accessing the first storage address https://xxx.xx/a/1json.json, and the timestamp of the update data uploaded to the CDN is 1564114914423.

According to another embodiment of the present disclosure, the update information includes a second storage address and a second update timestamp of an index file corresponding to the target application on the content distribution server; the index file includes the target application The service identifier, storage address and update time stamp of at least one target service of the target application; the update data includes the update data of at least one target service of the target application.

According to an embodiment of the present disclosure, the target service may include, but is not limited to, a configuration center service, an offline package service, and a patch service. After one or more target services of the target application have changed, the developer can package the updated one or more target services in the form of updated data of the target service. The following will take the target service as a patch service or an offline package service as an example. However, the present disclosure is not limited thereto. For example, after obtaining the update data of the patch service or the offline package service, the client may update the target application at the local client. If there is only one target service, that is, only one target service of the target application has changed, the update data of the target application includes the update data of this target service; if there are two or more target services, that is, the target application has When two or more target services have changed, the update data of the target application may include the update data of one target service, some target services, or all the target services.

According to the embodiment of the present disclosure, since the update data of the target application may include the update data of one or more target services of the target application, in order to distinguish the update data of different target services, an index file may be established to store the update information of different target services, wherein , the index file may include the service identifier, update address and update timestamp of at least one target service of the target application, wherein the service identifier is used to identify different target services, and the update address corresponds to the latest update address of the target service on the CDN, And by accessing the update address, the update data of the target service can be obtained, and the update time stamp corresponds to the time stamp when the update data of the target service is uploaded to the CDN. The present disclosure will take an example in which the corresponding data of the target application has two target services changed, and the service identifier is in the form of a service name, but the present disclosure is not limited thereto. For example, the target application APP2 has two target services, namely the configuration center service (crystal_config) and the offline package service (speedboat_offline_deploy). Among them, the appKey of APP2 is 25230564, the appVersion is 7.20.4, and the update address of the configuration center service is https: //xxx.xx/b/1json.json, the update timestamp is 1563405958296, the update address of the offline package service is https://xxx.xx/b/2json.json, and the update timestamp is 1564039123355, then the index file of APP2 It can be expressed as:

According to the above embodiments of the present disclosure, the update information includes the second storage address and the second update timestamp of the index file corresponding to the target application on the content distribution server. After receiving the update information, the gateway can access the second storage address by accessing the second storage address. The index file is obtained, and the latest update time of the index file can also be determined by using the second update timestamp. After the index file is obtained through the second storage address, the service identifier, update address and update timestamp of at least one target service of the target application can also be obtained from the index file. For example, the update data newly uploaded by the server to the CDN includes the target application's When updating the data of the target service A, the first storage address and the first update time stamp of the updated data of the target service A on the CDN can be obtained through the index file. The present disclosure does not specifically limit the representation form adopted by the second storage address and the method for obtaining the second update timestamp.

FIG. 4 shows a flowchart of a data update method according to an embodiment of the present disclosure. As shown in FIG. 4, after the step S301, that is, after receiving the request sent by the target application, the following steps S401-S402 are further included:

In step S401, the application identifier of the target application carried in the request is obtained;

In step S402, when the application identifier is not stored in the local application list, the application identifier is added to the local application list.

According to the embodiment of the present disclosure, since all requests sent by the target application in the client to the server of the target application will pass through the gateway on the server side, the gateway can first obtain the application identifier of the target application from the request, and then determine whether the local application list has Store the application identifier of the target application, where the local application list is used to store the application identifiers of different applications. If the application identifier of the target application has been stored, the application identifier does not need to be added to the local application list; if the target application is not stored The application ID of the application is added to the local application list. The present disclosure does not specifically limit the storage method of the application identifier in the local application list, which can be determined according to actual application needs.

FIG. 5 shows a flowchart of carrying the update information of the target application in response data and returning it to the client according to an embodiment of the present disclosure. As shown in FIG. 5, the step S302, that is, carrying the update information of the target application in the response data and returning it, includes the following steps S501-S502:

In step S501, determine whether the update information of the target application is stored locally according to the application identifier;

In step S502, when the update information of the target application is stored locally, the update information of the target application is carried in the response data and returned to the client.

According to an embodiment of the present disclosure, after obtaining the application identifier, it is first determined whether the gateway locally stores the update information of the target application, and if the update information of the target application is stored locally, the update information of the target application is directly carried in the response data and returned to the client, so as to avoid the client directly requesting the update information of the target application from the server; if the update information of the target application is not stored locally, the update information may not be carried in the response data this time, but will be sent by the gateway in the next cycle. After requesting and obtaining the update information of the target application from the server, the update information is carried in the response data and returned to the client.

FIG. 6 shows a flowchart of a data update method according to an embodiment of the present disclosure. As shown in Figure 6, the data update method further includes the following steps S601-S602:

In step S601, periodically sending an update information request of the target application to the server;

In step S602, the update information of the target application returned by the server is received.

According to the embodiment of the present disclosure, the gateway periodically sends the update information request of the target application to the server according to the application identifier of the target application stored in the local application list. The actual situation is limited, for example, it can be 1 second. Since the number of gateways is much smaller than the number of clients, the pressure on the server to receive updated information requests is relieved. In response to the update information request of the target application by the gateway, the server returns the update information of the target application, through which the information of the first storage address and the first update timestamp of the update data of the target application on the CDN can be obtained.

According to the embodiment of the present disclosure, when the gateway obtains the update information of the target application from the server, it can delete the original update information stored locally in the gateway, and store the update information obtained from the server locally instead of the original update information Or, when the gateway obtains the update information of the target application from the server side, it can determine whether to store the update information obtained from the server side according to whether the update information obtained from the server side has been stored locally in the gateway, specifically, if When the update information of one or more target applications is not stored locally, the gateway can directly store the update information locally; if the local update information corresponding to the one or more target applications is stored locally, the gateway can further store the update information locally. The first update time stamp in the obtained update information is compared with the local time stamp in the locally stored local update information. If the first update time stamp in the update information is later than the local time stamp in the local update information, it indicates that the slave server The obtained update information is newer than the locally stored local update information, then the update information of one or more target applications returned by the server can be accepted, and the update information is stored locally in the gateway. On the contrary, it indicates that the locally stored local update information is already the latest update information, the update information may not be stored.

FIG. 7 shows a flowchart of a method for updating data according to an embodiment of the present disclosure, and the method for updating data is executed on a client side. As shown in Figure 7, the data update method includes the following steps S701-S704:

In step S701, a request carrying the application identifier of the target application is sent to the gateway;

In step S702, receiving the response data returned by the gateway;

In step S703, the update information added by the gateway to the response data is obtained, wherein the update information includes a first storage address on the content distribution server that can obtain the update data of the target application and a first update timestamp information;

In step S704, whether to update the target application is determined according to the update information.

According to the embodiments of the present disclosure, the target application in the client sends a request to the server of the target application, and the request will pass through the gateway of the server and then arrive at the server, that is, the request is first sent to the gateway of the server, where the target application refers to the occurrence of data One or more applications that have been updated, the request includes any request made by the target application. When the target application sends a request to the server, it can intercept the request to be sent through the SDK installed locally. In order to know whether the target application has updated information, the SDK can carry the application identifier of the target application in any intercepted request, and send the request to the gateway of the server to obtain whether the target application has updated information. Since the request includes a header and a request body, the application identifier of the target application can be carried in the header of the request and sent to the gateway of the server. Similarly, after the client obtains the response data returned by the gateway, it can also obtain the update information of the target application from the response data through the SDK. The application identifier is used to identify different versions of different target applications, and the application identifier may include an application unique identifier (appKey) and an application release version number (appVersion). Clients can be handheld terminal devices, laptop computers, cellular phones, smart phones, wireless data cards, personal digital assistant computers, tablet computers, cordless phones, Internet of Things devices (IOT devices), or other terminal devices that can access the network , which is not specifically limited in the present disclosure.

According to the embodiment of the present disclosure, after receiving the request sent by the target application, the gateway can obtain the application identifier carried in the packet header of the request, and then compare the application identifier with the application identifier stored locally by the gateway. If the update information corresponding to the application identifier is stored locally, the update information is carried in the response data of the request and returned to the client. Since the response data includes a header and a body, the update information of the target application can be carried in the header of the response data and returned to the client. The client obtains the update information in the response information, where the update information includes the information that can obtain the first storage address and the first update timestamp of the update data of the target application on the CDN, wherein the information can be obtained by accessing the first storage address To update the data, the first update timestamp corresponds to the timestamp when the update data is uploaded to the CDN. The present disclosure does not specifically limit the representation form adopted by the first storage address and the method for obtaining the first update timestamp.

According to the embodiment of the present disclosure, since the client locally stores the last local update information of the target application, by comparing the update information obtained from the gateway with the local update information of the target application, it can be determined that the update information obtained from the gateway corresponds to the update information. Whether the update data has been updated locally, if it has been updated, it is not necessary to process it; if it has not been updated, the update data of the target application can be downloaded from the first storage address in the update information obtained by the gateway, and the target application The application is updated; of course, the update information can also be recorded first, and then updated in batches.

According to the technical solutions provided by the embodiments of the present disclosure, by sending a request carrying the application identifier of the target application to the gateway, receiving the response data returned by the gateway, and acquiring the update information added by the gateway to the response data at the same time, the update information is used to determine whether to Update the target application. The problem of resource waste caused by the client polling and actively requesting to update data is avoided. At the same time, the gateway directly carries the update information of the target application in the response data according to the application identifier of the target application carried in the request sent by the target application. It is returned to the client, so that the client can determine whether the target application needs to be updated according to the update information.

According to an embodiment of the present disclosure, the update information includes the first storage address of the update data on the content distribution server and the first update timestamp. In this embodiment, the gateway may directly acquire the first storage address and the first update timestamp from the update information returned by the server. And the update time of the update data of the target application on the CDN can be determined by the first update timestamp, and the update data of the target application can be obtained from the CDN by accessing the first storage address. It can be understood that although the present disclosure uses the first storage address in the form of a Uniform Resource Locator (URL) and the first update timestamp is exemplified by obtaining milliseconds, the present disclosure is not limited thereto. For example, the server uploads the update data of the target application APP1 to the CDN, and obtains the first storage address (https://xxx.xx/a/1json.json) and the first update timestamp (1564114914423) of APP1 on the CDN, The update data can be obtained by accessing the first storage address https://xxx.xx/a/1json.json, and the timestamp of the update data uploaded to the CDN is 1564114914423.

According to another embodiment of the present disclosure, the update information includes a second storage address and a second update timestamp of an index file corresponding to the target application on the content distribution server; the index file includes the target application The service identifier, storage address and update time stamp of at least one target service of the target application; the update data includes the update data of at least one target service of the target application.

According to an embodiment of the present disclosure, the target service may include, but is not limited to, a configuration center service, an offline package service, and a patch service. After one or more target services of the target application have changed, the developer can package the updated one or more target services in the form of updated data of the target service. The following will take the target service as a patch service or an offline package service as an example. However, the present disclosure is not limited thereto. For example, after obtaining the update data of the patch service or the offline package service, the client may update the target application at the local client. If there is only one target service, that is, only one target service of the target application has changed, the update data of the target application includes the update data of this target service; if there are two or more target services, that is, the target application has When two or more target services have changed, the update data of the target application may include the update data of one target service, some target services, or all the target services.

According to the embodiment of the present disclosure, since the update data of the target application may include the update data of one or more target services of the target application, in order to distinguish the update data of different target services, an index file may be established to store the update information of different target services, wherein , the index file may include the service identifier, update address and update timestamp of at least one target service of the target application, wherein the service identifier is used to identify different target services, and the update address corresponds to the latest update address of the target service on the CDN, And by accessing the update address, the update data of the target service can be obtained, and the update time stamp corresponds to the time stamp when the update data of the target service is uploaded to the CDN. The present disclosure will take an example in which the corresponding data of the target application has two target services changed, and the service identifier is in the form of a service name, but the present disclosure is not limited thereto. For example, the target application APP2 has two target services, namely the configuration center service (crystal_config) and the offline package service (speedboat_offline_deploy). Among them, the appKey of APP2 is 25230564, the appVersion is 7.20.4, and the update address of the configuration center service is https: //xxx.xx/b/1json.json, the update timestamp is 1563405958296, the update address of the offline package service is https://xxx.xx/b/2json.json, and the update timestamp is 1564039123355, then the index file of APP2 It can be expressed as:

According to the above embodiments of the present disclosure, the update information includes the second storage address and the second update timestamp of the index file corresponding to the target application on the content distribution server. After receiving the update information, the gateway can access the second storage address by accessing the second storage address. The index file is obtained, and the latest update time of the index file can also be determined by using the second update timestamp. After the index file is obtained through the second storage address, the service identifier, update address and update timestamp of at least one target service of the target application can also be obtained from the index file. For example, the update data newly uploaded by the server to the CDN includes the target application's When updating the data of the target service A, the first storage address and the first update time stamp of the updated data of the target service A on the CDN can be obtained through the index file. The present disclosure does not specifically limit the representation form adopted by the second storage address and the method for obtaining the second update timestamp.

FIG. 8 shows a flowchart of sending a request carrying an application identifier of a target application to a gateway according to an embodiment of the present disclosure. As shown in Figure 8, the step S701, namely sending a request carrying the application identifier of the target application to the gateway, includes the following steps S801-S802:

In step S801, intercept the request sent by the target application to the server;

In step S802, the application identifier of the target application is carried in the request and sent to the gateway of the server.

According to the embodiments of the present disclosure, when the target application in the client sends a request to the server, the request to be sent can be intercepted by the SDK installed locally. In order to know whether the target application has update information, the SDK can carry the application identifier of the target application in any intercepted request, and send the request to the gateway of the server to obtain the update information of the target application. Since the request includes a packet header and a packet body, the application identifier of the target application can be carried in the packet header of the request and sent to the gateway of the server. Similarly, after the client obtains the response data returned by the gateway, it can also obtain the update information of the target application from the response data through the SDK.

According to an embodiment of the present disclosure, the step S704, that is, determining whether to update the target application according to the update information, may also be implemented as: when the first update timestamp is later than the local first update time of the target application When the time stamp is updated, record that the target application has updated data. In this embodiment, since some target applications only need to confirm whether they have been updated, the update data of the target application does not need to be downloaded immediately. When the first update time stamp is later than the third update time stamp, where the third update time stamp may be the first update time stamp of the update data that was downloaded from the CDN for the last time and updated the target application, it may be determined that the locally stored When the update data of the target application is updated, the situation can be recorded first, so that the update data of the target application can be downloaded and installed at an appropriate time later.

According to an embodiment of the present disclosure, the step S704, that is, determining whether to update the target application according to the update information, may also be implemented as: when the first update timestamp is later than the local first update time of the target application When updating the time stamp, download the update data of the target application from the first storage address; and update the target application according to the update data of the target application. In this embodiment, the first update time stamp can be compared with the local third update time stamp, where the third update time stamp can be the first update time of the latest update data downloaded from the CDN and updated to the target application to determine whether to download and install the update data of the target application. Specifically, when the first update timestamp is later than the local third update timestamp, it indicates that the update data of the target data is updated compared with the update data corresponding to the local target application, so the update of the target application can be downloaded from the first storage address data, and update the target application according to the update data of the target application.

FIG. 9 shows a flowchart of determining whether to update the target application according to the update information according to an embodiment of the present disclosure. As shown in FIG. 9, the step S704, that is, determining whether to update the target application according to the update information, includes the following steps S901-S902:

In step S901, when the second update time stamp is later than the fourth update time stamp of the local index file, the index file is downloaded from the second storage address;

In step S902, whether to update the target application is determined according to the first update timestamp corresponding to the service identifier of the at least one target service in the index file.

According to the embodiment of the present disclosure, the client can store the local index file corresponding to the target application obtained from the server most recently and the fourth update timestamp of the local index file on the CDN, one or the other of the target application recorded in the index file The update data of multiple target services have been updated on the local target application. When the update information obtained from the gateway includes the index file corresponding to the target application, the second storage address of the index file on the CDN, and the second update timestamp, the second update timestamp can be compared with the locally stored local index file. Four update timestamps, where the fourth update timestamp corresponds to the timestamp when the local index file is uploaded to the CDN, so as to determine whether the index file obtained from the gateway is updated. Specifically, when the second update time stamp is later than the fourth update time stamp, it indicates that the index file obtained from the gateway is updated compared to the local index file stored locally, so the latest index file can be downloaded from the second storage address.

According to the embodiment of the present disclosure, since the service identifier, the first storage address and the first update time stamp of the at least one target service are stored in the index file in association, when the index file is updated, it indicates that the at least one target service stored in the index file has occurred. Therefore, whether to update the target application can be determined according to the first update timestamp corresponding to the service identifier of at least one target service in the index file and the update timestamp corresponding to the service identifier of the target service in the locally stored local index file.

10 shows a flowchart of determining whether to update the target application according to the first update timestamp corresponding to the service identifier of the at least one target service in the index file according to an embodiment of the present disclosure. As shown in Figure 10, the step S902, that is, determining whether to update the target application according to the first update timestamp corresponding to the service identifier of the at least one target service in the index file, includes the following steps S1001-S1002:

In step S1001, when the first update time stamp is later than the locally stored fifth update time stamp corresponding to the at least one target service, download the update data of the target service from the first storage address;

In step S1002, the target service is updated according to the update data of the target service.

According to the embodiment of the present disclosure, since the local index file downloaded from the server when the target application was updated last time is stored locally, and the local index file stores the service identifier and the fifth update time stamp of at least one target service of the target application in association, wherein , and the fifth update timestamp corresponds to the timestamp of the locally stored update data of the target service uploaded to the CDN. When the index file downloaded from the second storage address associates and stores the service identifier of at least one target service, the first storage address, and the first update time stamp, the first update time stamp can be compared with the update data of the target service in the local index file. to determine whether to download and install the update data of the target service. Specifically, when the first update time stamp is later than the fifth update time stamp, it indicates that the update data of the target service is updated compared with the update data corresponding to the target service in the local index file, so the update data can be downloaded from the first storage address. Update data of the target service, and update the target service of the target application according to the update data.

For example: the local index file 1 stored locally is as follows:

The index file 2 obtained from the second storage address is as follows:

For the configuration center service, since the first update time stamp 1563405958296 is later than the fifth update time stamp 1563405658296, it indicates that the update data of the locally stored configuration center service has been updated. Therefore, the first storage address https://xxx.xx /b/1json.json downloads the updated data of the configuration center business.

Because some target services in the target application only need to confirm whether they have been updated, there is no need to download the update data of the target service immediately. For example, offline package services and patch services only need to obtain update information, and do not need to download the update of the target service immediately. Therefore, according to an embodiment of the present disclosure, the step S902, that is, determining whether to update the target application according to the first update timestamp corresponding to the service identifier of the at least one target service in the index file, can also be performed by The implementation is: when the first update time stamp is later than or equal to the fifth update time stamp corresponding to the at least one target service stored locally, recording that the target service has update data.

For example: the local index file 1 stored locally is as follows:

The index file 2 obtained from the second storage address is as follows:

For the offline package service, since the first update time stamp 1564039123355 is later than the fifth update time stamp 1564036123355, it can be determined that the update data of the offline package service stored locally has been updated. download and install it at the same time (for example, download the update data of the target service from the server in batches, and update multiple target services of the target application in batches). When the user needs to download the update data of the offline package service, he can further download the update data of the configuration offline package service from the first storage address https://xxx.xx/b/2json.json.

FIG. 11 shows a flowchart of a data update method according to an embodiment of the present disclosure. As shown in Figure 11, the data update method includes the following steps S1101-S1104:

In step S1101, the server uploads the update data of the target application to the content distribution server, and obtains the update information of the update data on the content distribution server, wherein the update information includes the ability to obtain the update data at the location where the update data can be obtained. the information of the first storage address and the first update timestamp on the content distribution server;

In step S1102, the server returns the update information to the gateway in response to the update information request of the gateway for the target application;

In step S1103, the gateway receives the request sent by the target application, and returns the update information of the target application in response data to the client, where the request includes the application of the target application identification;

In step S1104, the client obtains the update information added by the gateway in the response data, and determines whether to update the target application according to the update information.

According to an embodiment of the present disclosure, an application (APP) with different functions is installed in the client, wherein the application may be software installed on the client, such as a communication application, a game application, an entertainment application, a social application, or a practical life application, etc. , which is not specifically limited in the present disclosure. In order to relieve the pressure on the server and improve the response speed and hit rate of data requests, after the technical developers update the target application, they can upload the updated data of the target application to the CDN through the server, where the target application refers to the data that has been updated One or more applications of the target application, update data refers to the data that has changed in the target application.

It should be noted that the server in the embodiment of the present disclosure is the server of the target application, and different target applications may correspond to different servers.

According to an embodiment of the present disclosure, when the number of target applications is two or more, in order to distinguish the update data corresponding to different target applications, the server may simultaneously upload the application identifier of the target application and the corresponding update data to the CDN, wherein , the application identifier is used to identify different versions of different target applications, and the application identifier may include an application unique identifier (appKey) and an application release version number (appVersion). At the same time, the application identifier of the target application and the corresponding update data can be assembled into a key-value data structure and stored in the server's local non-relational database (such as Redis), where the key corresponds to the application identifier and the value corresponds to the update data.

According to the embodiment of the present disclosure, after the server uploads the update data of the target application to the CDN, the server can further obtain the update information of the update data on the CDN, and the update information includes the first storage address and the first storage address of the CDN that can obtain the update data on the CDN. The information of the update time stamp, wherein the update data can be obtained by accessing the first storage address, and the first update time stamp corresponds to the time stamp when the update data is uploaded to the CDN. The present disclosure does not specifically limit the representation form adopted by the first storage address and the method for obtaining the first update timestamp. In order to identify the update information corresponding to the update data of different target applications, the application identifier of the target application and the update information may be stored in association.

As described above, in order to avoid the above-mentioned technical problems that occur in two ways: the server actively pushes the update data or the client polls and actively requests the update data, according to the embodiments of the present disclosure, the gateway can be set to periodically send the update of the target application to the server For the information request, the present disclosure does not specifically limit the period of the update information request, for example, it may be 1S. Since the number of gateways is much smaller than the number of clients, the pressure on the server to receive updated information requests is relieved. In response to the update information request for the target application by the gateway, the server returns the latest update information of the target application. In order to identify the update information requests corresponding to different target applications, the update information request can carry the application identifier of the target application. The server responds to the update information request of the gateway for the target application, and determines the target application corresponding to the current update information request according to the application identifier, and sends The update information of the target application is returned to the gateway.

It should be noted that the gateway mentioned in the embodiments of the present disclosure is a server-side gateway, that is, a gateway through which the server communicates with the outside world. All network requests from the target application on the client to the server side of the target application can enter the server side through the gateway. Clients can be handheld terminal devices, laptop computers, cellular phones, smart phones, wireless data cards, personal digital assistant computers, tablet computers, cordless phones, Internet of Things devices (IOT devices), or other terminal devices that can access the network , which is not specifically limited in the present disclosure.

According to the embodiment of the present disclosure, the request sent by the target application on the client to the server side of the target application will first reach the gateway of the server side. In order to determine whether the target application has update information, in the embodiment of the present disclosure, the target application on the client may not directly send the update information request to the server, but the specially developed SDK on the client intercepts the information sent by the target application to the server. Any request, and the application identifier of the target application is added to the request, so as to obtain whether the target application has update information. Since the request includes a header and a body, the client can send the application identifier of the target application to the server in the header of the request.

According to the embodiments of the present disclosure, after the gateway receives the request data sent by the target application on the client, it can obtain the application identifier carried in the request (for example, the packet header), and then associate the application identifier with the application stored locally on the gateway. identities for comparison. If the gateway locally stores the update information corresponding to the application identifier, the gateway returns the update information to the client after carrying the update information in the response data of the request data. Since the response data includes a header and a body, the gateway can carry the update information of the target application in the header of the response data and return it to the client.

According to an embodiment of the present disclosure, after the client obtains the update information in the response information, since the client locally stores the last local update information of the target application, the client compares the update information obtained from the gateway with the target application locally on the client The update information obtained from the gateway can be judged whether the update data corresponding to the update information obtained from the gateway has been updated locally on the client. The update data of the target application is downloaded from the first storage address in the client application, and the target application is updated locally; of course, the client can also record the update information first, and then update it in batches.

According to the technical solutions provided by the embodiments of the present disclosure, the server uploads the update data of the target application to the content distribution server, and obtains the update information of the update data on the content distribution server, wherein the update information includes the ability to obtain the update data on the content distribution server the information of the first storage address and the first update timestamp, the server returns the update information to the gateway in response to the update information request of the gateway for the target application, the gateway receives the request sent by the target application, and carries the update information of the target application with The response data is returned to the client, wherein the request includes the application identifier of the target application, and the client obtains the update information added by the gateway in the response data, and determines whether to update the target application according to the update information. The problem of resource waste caused by the client polling and actively requesting update data is avoided, and the gateway directly carries the update information of the target application stored locally in the gateway in the response data and returns it to the client, so that the client can update the data according to the update information. The information determines whether the target application needs to be updated, which improves the response speed of updating data, so that multiple clients can achieve "second-level" updates at the same time. The pressure on the server to receive requests for updated information.

According to an embodiment of the present disclosure, the update information includes the first storage address of the update data on the content distribution server and the first update timestamp. In this embodiment, the gateway may directly acquire the first storage address and the first update timestamp from the update information returned by the server. And the update time of the update data of the target application on the CDN can be determined by the first update timestamp, and the update data of the target application can be obtained from the CDN by accessing the first storage address. It can be understood that although the present disclosure uses the first storage address in the form of a Uniform Resource Locator (URL) and the first update timestamp is exemplified by obtaining milliseconds, the present disclosure is not limited thereto. For example, the server uploads the update data of the target application APP1 to the CDN, and obtains the first storage address (https://xxx.xx/a/1json.json) and the first update timestamp (1564114914423) of APP1 on the CDN, The update data can be obtained by accessing the first storage address https://xxx.xx/a/1json.json, and the timestamp of the update data uploaded to the CDN is 1564114914423.

According to another embodiment of the present disclosure, the update information includes a second storage address and a second update timestamp of an index file corresponding to the target application on the content distribution server; the index file includes the target application The service identifier, storage address and update time stamp of at least one target service of the target application; the update data includes the update data of at least one target service of the target application.

According to an embodiment of the present disclosure, the target service may include, but is not limited to, a configuration center service, an offline package service, and a patch service. After one or more target services of the target application have changed, the developer can package the updated one or more target services in the form of updated data of the target service. The following will take the target service as a patch service or an offline package service as an example. However, the present disclosure is not limited thereto. For example, after obtaining the update data of the patch service or the offline package service, the client may update the target application at the local client. If there is only one target service, that is, only one target service of the target application has changed, the update data of the target application includes the update data of this target service; if there are two or more target services, that is, the target application has When two or more target services have changed, the update data of the target application may include the update data of one target service, some target services, or all the target services.

According to the embodiment of the present disclosure, since the update data of the target application may include the update data of one or more target services of the target application, in order to distinguish the update data of different target services, an index file may be established to store the update information of different target services, wherein , the index file may include the service identifier, update address and update timestamp of at least one target service of the target application, wherein the service identifier is used to identify different target services, and the update address corresponds to the latest update address of the target service on the CDN, And by accessing the update address, the update data of the target service can be obtained, and the update time stamp corresponds to the time stamp when the update data of the target service is uploaded to the CDN. The present disclosure will take an example in which the corresponding data of the target application has two target services changed, and the service identifier is in the form of a service name, but the present disclosure is not limited thereto. For example, the target application APP2 has two target services, namely the configuration center service (crystal_config) and the offline package service (speedboat_offline_deploy). Among them, the appKey of APP2 is 25230564, the appVersion is 7.20.4, and the update address of the configuration center service is https: //xxx.xx/b/1json.json, the update timestamp is 1563405958296, the update address of the offline package service is https://xxx.xx/b/2json.json, and the update timestamp is 1564039123355, then the index file of APP2 It can be expressed as:

According to the above embodiments of the present disclosure, the update information includes the second storage address and the second update timestamp of the index file corresponding to the target application on the content distribution server. After receiving the update information, the gateway can access the second storage address by accessing the second storage address. The index file is obtained, and the latest update time of the index file can also be determined by using the second update timestamp. After the index file is obtained through the second storage address, the service identifier, update address and update timestamp of at least one target service of the target application can also be obtained from the index file. For example, the update data newly uploaded by the server to the CDN includes the target application's When updating the data of the target service A, the first storage address and the first update time stamp of the updated data of the target service A on the CDN can be obtained through the index file. The present disclosure does not specifically limit the representation form adopted by the second storage address and the method for obtaining the second update timestamp.

FIG. 12 shows a flowchart of acquiring update information of the update data on the content distribution server according to an embodiment of the present disclosure. As shown in FIG. 12 , acquiring the update information of the update data on the content distribution server in the step S1101 includes the following steps S1201-S1204:

In step S1201, the server obtains the first storage address and the first update timestamp of the update data on the content distribution server;

In step S1202, the server updates the index file according to the first storage address and the first update timestamp;

In step S1203, the server uploads the index file to the content distribution server;

In step S1204, the server obtains the second storage address and the second update timestamp.

According to the embodiments of the present disclosure, after one or more target services of the target application are updated, the server uploads the updated data to the CDN, and obtains its upload address, that is, the first storage address and the upload time stamp, that is, from the CDN. The first update timestamp. Since the update data of the target application includes the update data of at least one target service of the target application, the server obtains the first storage address and the first update timestamp of the update data on the content distribution server, and stores the update data on the content distribution server. The first storage address and the first update time stamp are stored in the index file in association with the service identifiers of one or more target services in the update data, respectively. If the service identifiers of one or more target services have been associated and stored in the index file When there is a corresponding entry, the entry can be updated by using the current first storage address and the first update timestamp, that is, the current index file is updated.

According to the embodiments of the present disclosure, in order to relieve the pressure on the server, the server may upload the index file to the CDN, and obtain the second storage address and the second update timestamp of the index file on the CDN, where the second update timestamp corresponds to The timestamp when the index file was uploaded to the CDN. The index file can be obtained by accessing the second storage address, and then the update information of one or more target services corresponding to the target application can be obtained from the index file, for example, the first storage address and the first update timestamp stored in association with the service identifier . When the gateway periodically sends an update information request of the target application to the server, the server may return the second storage address of the index file on the CDN and the second update timestamp to the gateway.

According to an embodiment of the present disclosure, the step S1202, that is, the server updates the index file according to the first storage address and the first update timestamp, can also be implemented as: the server updates the index file The update address and the update timestamp associated with the service identifier of the target service in the file are updated to the first storage address and the first update timestamp.

In this embodiment, the index file may include update information associated with multiple target service identifiers, and when one or more of the target services are updated, the server may An update timestamp updates the update information corresponding to the service identifiers of one or more target services in the index file. The server first determines the target service according to the service identifier, then updates the update address of the target service to the first storage address, and updates the update time stamp to the first update time stamp, thereby completing the update of the index file. For example, the original index file is:

Assuming that only the business file of the configuration center service is changed, and the first storage address is https://xxx.xx/b/3json.json, and the first update timestamp is 1564014914423, the server will configure the center service update address https: //xxx.xx/b/1json.json is updated to the first storage address https://xxx.xx/b/3json.json, and the update timestamp 1563405958296 is updated to the first update timestamp 1564014914423, so as to obtain the updated index The file is:

FIG. 13 shows a flowchart of the gateway receiving the request sent by the target application, and returning the update information of the target application to the client in response data according to an embodiment of the present disclosure. As shown in FIG. 13 , the step S1103, that is, the gateway receives the request sent by the target application, carries the update information of the target application in the response data and returns it to the client, and further includes the following step S1301 -S1304:

In step S1301, the gateway obtains the application identifier of the target application carried in the request;

In step S1302, when the application identifier is not stored in the local application list, the gateway adds the application identifier to the local application list;

In step S1303, the gateway obtains the application identifier of the target application carried in the request;

In step S1304, when the application identifier is not stored in the local application list, the gateway adds the application identifier to the local application list.

According to the embodiment of the present disclosure, since all requests sent by the target application in the client to the server of the target application will pass through the gateway on the server side, the gateway can first obtain the application identifier of the target application from the request, and then determine whether the local application list of the gateway has Store the application identifier of the target application, where the local application list is used to store the application identifiers of different applications. If the gateway has stored the application identifier of the target application, the application identifier does not need to be added to the local application list; if the gateway does not store the application identifier The application identifier of the target application is added to the local application list. The present disclosure does not specifically limit the storage method of the application identifier in the local application list, which can be determined according to actual application needs.

According to the embodiment of the present disclosure, after the gateway obtains the application identifier, it first determines whether the update information of the target application is stored locally by the gateway, and if the update information of the target application is stored locally, the update information of the target application is directly carried in the response data Return to the client, thereby avoiding the client directly requesting the update information of the target application from the server; if the gateway does not store the update information of the target application locally, the update information may not be carried in the response data this time, but in the next cycle After the gateway requests and obtains the update information of the target application from the server, the gateway carries the update information in the response data and returns it to the client.

FIG. 14 shows a flowchart of a data update method according to an embodiment of the present disclosure. As shown in Figure 14, the data update method further includes the following steps S1401-S1402:

In step S1401, the gateway periodically sends an update information request of the target application to the server;

In step S1402, the gateway receives the update information of the target application returned by the server.

According to the embodiment of the present disclosure, the gateway periodically sends the update information request of the target application to the server according to the application identifier of the target application stored in the local application list. The actual situation is limited, for example, it can be 1 second. Since the number of gateways is much smaller than the number of clients, the pressure on the server to receive updated information requests is relieved. In response to the update information request of the target application by the gateway, the server returns the update information of the target application, through which the information of the first storage address and the first update timestamp of the update data of the target application on the CDN can be obtained.

According to the embodiment of the present disclosure, when the gateway obtains the update information of the target application from the server, it can delete the original update information stored locally in the gateway, and store the update information obtained from the server locally instead of the original update information Or, when the gateway obtains the update information of the target application from the server side, it can determine whether to store the update information obtained from the server side according to whether the update information obtained from the server side has been stored locally in the gateway, specifically, if When the gateway does not store the update information of one or more target applications locally, the gateway can directly store the update information locally; if the gateway locally stores the local update information corresponding to the one or more target applications, the gateway can store the update information locally. Further compare the first update time stamp in the obtained update information with the local time stamp in the locally stored local update information, if the first update time stamp in the update information is later than the local time stamp in the local update information, it indicates that If the update information obtained by the gateway from the server is newer than the local update information stored locally by the gateway, the gateway can accept the update information of one or more target applications returned by the server and store the update information locally in the gateway. The local update information is already the latest update information, the gateway may not store the update information.

FIG. 15 shows a flowchart of a data update method according to an embodiment of the present disclosure. As shown in Figure 15, the data update method further includes the following steps S1501-S1502:

In step S1501, the client sends the request carrying the application identifier of the target application to the gateway;

In step S1502, the client receives the response data returned by the gateway.

According to the embodiment of the present disclosure, the target application in the client sends a request to the server of the target application, and the request will pass through the gateway of the server and then arrive at the server, that is, the request is first sent to the gateway of the server. When the target application in the client sends a request to the server, the request to be sent can be intercepted by the local SDK installed in the client. In order to know whether the target application in the client has updated information, the SDK can carry the application identifier of the target application in any intercepted request, and send the request to the gateway of the server to obtain whether the target application has updated information. Since the request includes a header and a request body, the application identifier of the target application can be carried in the header of the request and sent to the gateway of the server. Similarly, after the client obtains the response data returned by the gateway, it can also obtain the update information of the target application from the response data through the SDK.

FIG. 16 shows a flowchart of the client sending the request carrying the application identifier of the target application to the gateway according to an embodiment of the present disclosure. As shown in FIG. 16, the step S1501, that is, the client sends the request carrying the application identifier of the target application to the gateway, includes the following steps S1601-S1602:

In step S1601, the client intercepts the request sent by the target application to the server;

In step S1602, the client sends the request to the gateway of the server by carrying the application identifier of the target application in the request.

According to the embodiments of the present disclosure, when the target application in the client sends a request to the server, the request to be sent can be intercepted by the SDK installed locally. In order to know whether the target application has update information, the SDK can carry the application identifier of the target application in any intercepted request, and send the request to the gateway of the server to obtain the update information of the target application. Since the request includes a packet header and a packet body, the client can send the application identifier of the target application to the server's gateway in the packet header of the request.

According to an embodiment of the present disclosure, the step S1104, that is, the client determines whether to update the target application according to the update information, may also be implemented as: when the first update timestamp is later than the target application At the local third update timestamp, the client records that the target application has updated data. In this embodiment, since some target applications only need to confirm whether they have been updated, the update data of the target application does not need to be downloaded immediately. When the first update time stamp is later than the third update time stamp, where the third update time stamp may be the first update time stamp of the update data that was downloaded from the CDN for the last time and updated the target application, it may be determined that the locally stored When the update data of the target application is updated, the client can first record the situation, so as to download and install the update data of the target application at an appropriate time later.

According to an embodiment of the present disclosure, the step S1104, that is, the client determines whether to update the target application according to the update information, may also be implemented as: when the first update timestamp is later than the target application At the local third update timestamp, the client downloads the update data of the target application from the first storage address; the client updates the target application according to the update data of the target application. In this embodiment, the first update time stamp can be compared with the local third update time stamp, where the third update time stamp can be the first update time of the latest update data downloaded from the CDN and updated to the target application to determine whether to download and install the update data of the target application. Specifically, when the first update timestamp is later than the local third update timestamp, it indicates that the update data of the target data is updated compared with the update data corresponding to the local target application, so the client can download the target application from the first storage address update data of the target application, and update the target application according to the update data of the target application.

FIG. 17 shows a flowchart of the client determining whether to update the target application according to the update information according to an embodiment of the present disclosure. As shown in FIG. 17, the step S1104, that is, the client determines whether to update the target application according to the update information, includes the following steps S1701-S1702:

In step S1701, when the second update timestamp is later than the fourth update timestamp of the local index file, the client downloads the index file from the second storage address;

In step S1702, the client determines whether to update the target application according to the first update timestamp corresponding to the service identifier of the at least one target service in the index file.

According to the embodiment of the present disclosure, the client can store the local index file corresponding to the target application obtained from the server most recently and the fourth update timestamp of the local index file on the CDN, one or the other of the target application recorded in the index file The update data of multiple target services have been updated on the local target application. When the update information obtained by the client from the gateway includes the index file corresponding to the target application, the second storage address of the index file on the CDN, and the second update timestamp, the second update timestamp can be compared with the locally stored local index file. The fourth update timestamp corresponds to the timestamp when the local index file is uploaded to the CDN, so as to determine whether the index file obtained from the gateway has been updated. Specifically, when the second update timestamp is later than the fourth update timestamp, it indicates that the index file obtained by the client from the gateway is updated compared to the local index file stored locally, so the client can download the latest update from the second storage address index file.

According to the embodiment of the present disclosure, since the service identifier, the first storage address and the first update time stamp of the at least one target service are stored in the index file in association, when the index file is updated, it indicates that the at least one target service stored in the index file has occurred. Therefore, the client can determine whether to update the target application according to the first update timestamp corresponding to the service identifier of at least one target service in the index file and the update timestamp corresponding to the service identifier of the target service in the local index file stored locally.

18 shows a flowchart of the client determining whether to update the target application according to the first update timestamp corresponding to the service identifier of the at least one target service in the index file according to an embodiment of the present disclosure. As shown in FIG. 18 , the step S1702, that is, the client determines whether to update the target application according to the first update timestamp corresponding to the service identifier of the at least one target service in the index file, includes the following step S1801 -S1802:

In step S1801, when the first update timestamp is later than the locally stored fifth update timestamp corresponding to the at least one target service, the client downloads the target service from the first storage address update data;

In step S1802, the client updates the target service according to the update data of the target service.

According to the embodiment of the present disclosure, since the client locally stores the local index file downloaded from the server when the target application was updated last time, and the local index file stores the service identifier of at least one target service and the fifth update timestamp of the target application in association with the local index file , wherein the fifth update timestamp corresponds to the timestamp of the update data of the target service stored locally by the client and uploaded to the CDN. When the index file downloaded by the client from the second storage address associates and stores the service identifier of at least one target service, the first storage address and the first update timestamp, the first update timestamp can be compared with the target service in the local index file. The fifth update timestamp of the update data is used to determine whether to download and install the update data of the target service. Specifically, when the first update time stamp is later than the fifth update time stamp, it indicates that the update data of the target service is updated compared with the update data corresponding to the target service in the local index file, so the client can store the data from the first storage address The update data of the target service is downloaded, and the target service of the target application is updated according to the update data.

For example: the local index file 1 stored locally by the client is as follows:

The index file 2 obtained by the client from the second storage address is as follows:

For the configuration center service, since the first update timestamp 1563405958296 is later than the fifth update timestamp 1563405658296, it indicates that the locally stored update data of the configuration center service has been updated. Therefore, the client can access the first storage address https://xxx .xx/b/1json.json to download the updated data of the configuration center business.

Because some target services in the target application of the client only need to confirm whether they have been updated, they do not need to download the update data of the target service immediately. For example, the offline package service and patch service only need to obtain the update message, and the client does not need to download the update data immediately. The update data of the target service, therefore, according to the embodiment of the present disclosure, the step S1702, that is, the client determines whether to update according to the first update timestamp corresponding to the service identifier of the at least one target service in the index file The target application can also be implemented as: when the first update time stamp is later than or equal to the fifth update time stamp corresponding to the at least one target service stored locally, the client records the target service There is updated data.

For example: the local index file 1 stored locally by the client is as follows:

The index file 2 obtained by the client from the second storage address is as follows:

For the offline package service, since the first update time stamp 1564039123355 is later than the fifth update time stamp 1564036123355, it can be determined that the update data of the offline package service stored locally by the client has been updated, and the client can record the situation first. In order to download and install at an appropriate time later (for example, download update data of the target service from the server in batches, and update multiple target services of the target application in batches). When the user needs to download the update data of the offline package service, he can further download the update data of the configuration offline package service from the first storage address https://xxx.xx/b/2json.json.

FIG. 19 shows a schematic structural diagram of a data update system 1900 according to an embodiment of the present disclosure. As shown in FIG. 19, the data update system includes a server 1901, a gateway 1902 and a client 1903, wherein,

The server 1901 is configured to upload the update data of the target application to the content distribution server, obtain the update information of the update data on the content distribution server, and respond to the update information request for the target application by the gateway to the content distribution server. The gateway returns the update information, wherein the update information includes information that can obtain a first storage address and a first update timestamp of the update data on the content distribution server;

The gateway 1902 is configured to receive a request sent by the target application, and carry the update information of the target application in response data and return it to the client, where the request includes the application identifier of the target application;

The client 1903 is configured to send the request carrying the application identifier of the target application to the gateway, receive the response data returned by the gateway, and obtain the response data added by the gateway to the response data. update information in , and determine whether to update the target application according to the update information.

According to the embodiment of the present disclosure, the server is the server of the target application, and different target applications may correspond to different servers. The gateway is the gateway of the server, that is, the gateway through which the server communicates with the outside world. The network requests from the target application on the client to the server of the target application can enter the server through the gateway. Clients can be handheld terminal devices, laptop computers, cellular phones, smart phones, wireless data cards, personal digital assistant computers, tablet computers, cordless phones, Internet of Things devices (IOT devices), or other terminal devices that can access the network , which is not specifically limited in the present disclosure. The specific implementation details of the embodiments of the present disclosure have been described above, and are not repeated here.

According to an embodiment of the present disclosure, the update information includes the first storage address of the update data on the content distribution server and the first update timestamp. The specific implementation details of the embodiments of the present disclosure have been described above, and are not repeated here.

According to an embodiment of the present disclosure, the update information includes a second storage address and a second update timestamp of an index file corresponding to the target application on the content distribution server; the index file includes at least a The service identifier, storage address and update time stamp of a target service; the update data includes the update data of at least one target service of the target application. The specific implementation details of the embodiments of the present disclosure have been described above, and are not repeated here.

According to an embodiment of the present disclosure, the server is configured to acquire a first storage address and a first update timestamp of the update data on the content distribution server, and update the update data according to the first storage address and the first update timestamp For the index file, upload the index file to the content distribution server, and obtain the second storage address and the second update timestamp. The specific implementation details of the embodiments of the present disclosure have been described above, and are not repeated here.

According to an embodiment of the present disclosure, the server is configured to update the update address and the update timestamp associated with the service identifier of the target service in the index file to the first storage address and the update time stamp. Describe the first update timestamp. The specific implementation details of the embodiments of the present disclosure have been described above, and are not repeated here.

According to an embodiment of the present disclosure, the gateway is configured to acquire the application identifier of the target application carried in the request, and when the application identifier is not stored in the local application list, add the application identifier to the A list of local applications, determining whether the update information of the target application is stored locally according to the application identifier, and when the update information of the target application is stored locally, the update information of the target application is carried in the response data returned to the client. The specific implementation details of the embodiments of the present disclosure have been described above, and are not repeated here.

According to an embodiment of the present disclosure, the gateway is configured to periodically send the update information request of the target application to the server, and receive the update information of the target application returned by the server. The specific implementation details of the embodiments of the present disclosure have been described above, and are not repeated here.

According to an embodiment of the present disclosure, the client is configured to send the request carrying the application identifier of the target application to the gateway, and receive the response data returned by the gateway. The specific implementation details of the embodiments of the present disclosure have been described above, and are not repeated here.

According to an embodiment of the present disclosure, the client is configured to intercept the request sent by the target application to the server, and send the request to the server by carrying the application identifier of the target application in the request of the gateway. The specific implementation details of the embodiments of the present disclosure have been described above, and are not repeated here.

According to an embodiment of the present disclosure, the client is configured to record that the target application has updated data when the first update timestamp is later than a local third update timestamp of the target application. The specific implementation details of the embodiments of the present disclosure have been described above, and are not repeated here.

According to an embodiment of the present disclosure, the client is configured to, when the first update timestamp is later than a local third update timestamp of the target application, download the target application's update timestamp from the first storage address Update data, and update the target application according to the update data of the target application. The specific implementation details of the embodiments of the present disclosure have been described above, and are not repeated here.

According to an embodiment of the present disclosure, when the second update time stamp is later than the fourth update time stamp of the local index file, the client downloads the index file from the second storage address, and according to the index file The first update timestamp corresponding to the service identifier of the at least one target service in determines whether to update the target application. The specific implementation details of the embodiments of the present disclosure have been described above, and are not repeated here.

According to an embodiment of the present disclosure, when the first update timestamp is later than the locally stored fifth update timestamp corresponding to the at least one target service, the client records that the target service has updated data. The specific implementation details of the embodiments of the present disclosure have been described above, and are not repeated here.

According to an embodiment of the present disclosure, the client downloads the target service from the first storage address when the first time stamp is later than a locally stored fifth update time stamp corresponding to the at least one target service update data of the target service, and update the target service according to the update data of the target service. The specific implementation details of the embodiments of the present disclosure have been described above, and are not repeated here.

According to an embodiment of the present disclosure, the target service includes a configuration center service, an offline package service, and a patch service.

FIG. 20 shows a structural block diagram of a data update apparatus 2000 according to an embodiment of the present disclosure. Wherein, the apparatus may be realized by software, hardware or a combination of the two to become part or all of the electronic device. As shown in FIG. 20 , the data updating apparatus includes an uploading module 2010 , a first acquiring module 2020 and a first returning module 2030 .

The uploading module 2010 is configured to upload the update data of the target application to the content distribution server;

The first obtaining module 2020 is configured to obtain update information of the update data on the content distribution server, wherein the update information includes a first storage address that can obtain the update data on the content distribution server and the information of the first update timestamp;

The first returning module 2030 is configured to return the update information in response to the update information request of the gateway for the target application.

According to an embodiment of the present disclosure, the update information includes the first storage address of the update data on the content distribution server and the first update timestamp.

According to an embodiment of the present disclosure, the update information includes a second storage address and a second update timestamp of an index file corresponding to the target application on the content distribution server; the index file includes at least a The service identifier, storage address and update time stamp of a target service; the update data includes the update data of at least one target service of the target application.

According to an embodiment of the present disclosure, acquiring the update information of the update data on the content distribution server includes:

acquiring the first storage address and the first update timestamp of the update data on the content distribution server;

Update the index file according to the first storage address and the first update timestamp;

uploading the index file to the content distribution server;

Obtain the second storage address and the second update timestamp.

According to an embodiment of the present disclosure, the updating of the index file according to the first storage address and the first update timestamp includes:

The update address and the update timestamp associated with the service identifier of the target service in the index file are updated to the first storage address and the first update timestamp.

According to an embodiment of the present disclosure, the target service includes a configuration center service, an offline package service, and a patch service.

The data update apparatus in the embodiment of the present disclosure corresponds to the data update method described in the embodiment shown in FIG. 1 and related embodiments. For details, refer to the data update method shown in FIG. 1 above, which will not be repeated here.

FIG. 21 shows a structural block diagram of a data update apparatus 2100 according to an embodiment of the present disclosure. Wherein, the apparatus may be realized by software, hardware or a combination of the two to become part or all of the electronic device. As shown in FIG. 21 , the data updating apparatus includes a first receiving module 2110 and a second returning module 2120 .

The first receiving module 2110 is configured to receive a request sent by a target application, wherein the request includes an application identifier of the target application;

The second return module 2120 is configured to carry the update information of the target application in response data and return it to the client, wherein the update information includes the first information on the content distribution server that can obtain the update data of the target application. A storage address and first update timestamp information.

According to an embodiment of the present disclosure, the update information includes the first storage address of the update data on the content distribution server and the first update timestamp.

According to an embodiment of the present disclosure, the update information includes a second storage address and a second update timestamp of an index file corresponding to the target application on the content distribution server; the index file includes at least a The service identifier, storage address and update time stamp of a target service; the update data includes the update data of at least one target service of the target application.

According to an embodiment of the present disclosure, carrying the update information of the target application in response data and returning it to the client includes:

Determine whether the update information of the target application is stored locally according to the application identifier;

When the update information of the target application is stored locally, the update information of the target application is carried in the response data and returned to the client.

According to an embodiment of the present disclosure, it also includes:

A second obtaining module 2130, configured to obtain the application identifier of the target application carried in the request;

The adding module 2140 is configured to add the application identifier to the local application list when the application identifier is not stored in the local application list.

According to an embodiment of the present disclosure, it also includes:

The first sending module 2150 is configured to periodically send the update information request of the target application to the server;

The second receiving module 2160 is configured to receive the update information of the target application returned by the server.

According to an embodiment of the present disclosure, the target service includes a configuration center service, an offline package service, and a patch service.

The data updating apparatus in the embodiment of the present disclosure corresponds to the data updating method described in the embodiment shown in FIG. 3 and related embodiments. For details, refer to the data updating method shown in FIG. 3 above, which will not be repeated here.

FIG. 22 shows a structural block diagram of a data update apparatus 2200 according to an embodiment of the present disclosure. Wherein, the apparatus may be realized by software, hardware or a combination of the two to become part or all of the electronic device. As shown in FIG. 22 , the data updating apparatus includes a second sending module 2210 , a third receiving module 2220 , a third obtaining module 2230 and a determining module 2240 .

The second sending module 2210 is configured to send a request carrying the application identifier of the target application to the gateway;

a third receiving module 2220, configured to receive the response data returned by the gateway;

The third obtaining module 2230 is configured to obtain the update information added by the gateway to the response data, wherein the update information includes a first storage address on the content distribution server that can obtain the update data of the target application and the information of the first update timestamp;

The determining module 2240 is configured to determine whether to update the target application according to the update information.

According to an embodiment of the present disclosure, the update information includes the first storage address of the update data on the content distribution server and the first update timestamp.

According to an embodiment of the present disclosure, the update information includes a second storage address and a second update timestamp of an index file corresponding to the target application on the content distribution server; the index file includes at least a The service identifier, storage address and update time stamp of a target service; the update data includes the update data of at least one target service of the target application.

According to an embodiment of the present disclosure, the sending the request carrying the application identifier of the target application to the gateway includes:

Intercepting the request sent by the target application to the server;

The application identifier of the target application is carried in the request and sent to the gateway of the server.

According to an embodiment of the present disclosure, the determining whether to update the target application according to the update information and the local third update timestamp of the target application includes:

When the first update time stamp is later than the third local update time stamp of the target application, it is recorded that the target application has update data.

According to an embodiment of the present disclosure, the determining whether to update the target application according to the update information and the local third update timestamp of the target application includes:

When the first update time stamp is later than the local third update time stamp of the target application, downloading the update data of the target application from the first storage address;

The target application is updated according to the update data of the target application.

According to an embodiment of the present disclosure, the determining whether to update the target application according to the update information and the local third update timestamp of the target application includes:

When the second update time stamp is later than the fourth update time stamp of the local index file, downloading the index file from the second storage address;

Whether to update the target application is determined according to the first update timestamp corresponding to the service identifier of the at least one target service in the index file.

According to an embodiment of the present disclosure, the determining whether to update the target application according to the first update timestamp corresponding to the service identifier of the at least one target service in the index file includes:

When the first update time stamp is later than the locally stored fifth update time stamp corresponding to the at least one target service, record that the target service has update data.

According to an embodiment of the present disclosure, the determining whether to update the target application according to the first update timestamp corresponding to the service identifier of the at least one target service in the index file includes:

When the first update time stamp is later than the locally stored fifth update time stamp corresponding to the at least one target service, downloading the update data of the target service from the first storage address;

The target service is updated according to the update data of the target service.

According to an embodiment of the present disclosure, the target service includes a configuration center service, an offline package service, and a patch service.

The data update apparatus in the embodiment of the present disclosure corresponds to the data update method described in the embodiment shown in FIG. 7 and related embodiments. For details, refer to the data update method shown in FIG. 7 above, which will not be repeated here.

The present disclosure also discloses an electronic device, and FIG. 23 shows a structural block diagram of an electronic device 2300 according to an embodiment of the present disclosure.

As shown in FIG. 23, the electronic device 2300 includes a memory 2301 and a processor 2302; wherein,

The memory 2301 is used to store one or more computer instructions, wherein the one or more computer instructions are executed by the processor 2302 to implement the following method steps:

Upload the update data of the target application to the content distribution server;

Acquiring update information of the update data on the content distribution server, wherein the update information includes information that can obtain a first storage address and a first update timestamp of the update data on the content distribution server;

The update information is returned in response to the update information request by the gateway for the target application.

The present disclosure also discloses an electronic device, the electronic device includes a memory and a processor; wherein,

The memory is used to store one or more computer instructions, wherein the one or more computer instructions are executed by the processor to implement the following method steps:

receiving a request sent by a target application, wherein the request includes an application identifier of the target application;

Carrying the update information of the target application in the response data and returning it to the client, where the update information includes a first storage address and a first update timestamp on the content distribution server that can obtain the update data of the target application Information.

The present disclosure also discloses an electronic device, the electronic device includes a memory and a processor; wherein,

The memory is used to store one or more computer instructions, wherein the one or more computer instructions are executed by the processor to implement the following method steps:

Send a request carrying the application identifier of the target application to the gateway;

receiving the response data returned by the gateway;

acquiring the update information added by the gateway to the response data, wherein the update information includes information that can acquire the first storage address and the first update timestamp of the update data of the target application on the content distribution server;

Whether to update the target application is determined according to the update information.

FIG. 24 shows a schematic structural diagram of a computer system suitable for implementing the data update method according to an embodiment of the present disclosure.

As shown in FIG. 24, a computer system 2400 includes a central processing unit (CPU) 2401 which can be loaded into a random access memory (RAM) 2403 according to a program stored in a read only memory (ROM) 2402 or a program from a storage section 2408 Instead, various processes in the above-described embodiments are performed. In the RAM 2403, various programs and data necessary for the operation of the system 2400 are also stored. The CPU 2401 , the ROM 2402 and the RAM 2403 are connected to each other through a bus 2404 . An input/output (I/O) interface 2405 is also connected to bus 2404 .

The following components are connected to the I/O interface 2405: an input section 2406 including a keyboard, a mouse, etc.; an output section 2407 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 2408 including a hard disk, etc. ; and a communication section 2409 including a network interface card such as a LAN card, a modem, and the like. The communication section 2409 performs communication processing via a network such as the Internet. Drivers 2410 are also connected to I/O interface 2405 as needed. A removable medium 2411, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is mounted on the drive 2410 as needed so that a computer program read therefrom is installed into the storage section 2408 as needed.

In particular, according to the embodiments of the present disclosure, all the methods described above can be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program tangibly embodied on a machine-readable medium, the computer program containing program code for performing the above-described object class determination method. In such an embodiment, the computer program may be downloaded and installed from the network through the communication portion 2409, and/or installed from the removable medium 2411.

The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code that contains one or more functions for implementing the specified logical function(s) executable instructions. It should also be noted that, in some alternative implementations, the functions noted in the blocks may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It is also noted that each block of the block diagrams and/or flowchart illustrations, and combinations of blocks in the block diagrams and/or flowchart illustrations, can be implemented in dedicated hardware-based systems that perform the specified functions or operations , or can be implemented in a combination of dedicated hardware and computer instructions.

The units or modules involved in the embodiments of the present disclosure may be implemented in a software manner, or may be implemented in a programmable hardware manner. The described units or modules may also be provided in the processor, and the names of these units or modules do not constitute a limitation on the units or modules themselves in certain circumstances.

As another aspect, the present disclosure also provides a computer-readable storage medium, and the computer-readable storage medium may be a computer-readable storage medium included in the electronic device or computer system in the above-mentioned embodiments; it may also exist independently , a computer-readable storage medium that does not fit into a device. The computer-readable storage medium stores one or more programs used by one or more processors to perform the methods describing the present disclosure.

The above description is merely a preferred embodiment of the present disclosure and an illustration of the technical principles employed. Those skilled in the art should understand that the scope of the invention involved in the present disclosure is not limited to the technical solutions formed by the specific combination of the above-mentioned technical features, and should also cover the above-mentioned technical features without departing from the inventive concept. Other technical solutions formed by any combination of its equivalent features. For example, a technical solution is formed by replacing the above features with the technical features disclosed in the present disclosure (but not limited to) with similar functions.

Claims (10)

1. a data update method, is characterized in that, comprises: Upload the update data of the target application to the content distribution server; Acquiring update information of the update data on the content distribution server, wherein the update information includes information that can obtain a first storage address and a first update timestamp of the update data on the content distribution server; The update information is returned in response to the update information request by the gateway for the target application. 2. a data update method, is characterized in that, comprises: receiving a request sent by a target application, wherein the request includes an application identifier of the target application; Carrying the update information of the target application in the response data and returning it to the client, where the update information includes a first storage address and a first update timestamp on the content distribution server that can obtain the update data of the target application Information. 3. a data update method, is characterized in that, comprises: Send a request carrying the application identifier of the target application to the gateway; receiving the response data returned by the gateway; acquiring the update information added by the gateway to the response data, wherein the update information includes information that can acquire the first storage address and the first update timestamp of the update data of the target application on the content distribution server; Whether to update the target application is determined according to the update information. 4. a data update method, is characterized in that, comprises: The server uploads the update data of the target application to the content distribution server, and obtains the update information of the update data on the content distribution server, wherein the update information includes that the update data can be obtained on the content distribution server information of the first storage address and the first update timestamp; The server returns the update information to the gateway in response to the update information request of the gateway for the target application; The gateway receives the request sent by the target application, and returns the update information of the target application in response data to the client, wherein the request includes the application identifier of the target application; The client acquires the update information added by the gateway in the response data, and determines whether to update the target application according to the update information. 5. A data update system, comprising: a server, a gateway and a client, wherein, The server is configured to upload the update data of the target application to the content distribution server, obtain the update information of the update data on the content distribution server, and in response to the update information request for the target application by the gateway, send the update information to the content distribution server. the gateway returns the update information, wherein the update information includes information that can obtain the first storage address and the first update timestamp of the update data on the content distribution server; the gateway, configured to receive a request sent by the target application, and carry the update information of the target application in response data and return it to the client, where the request includes the application identifier of the target application; The client is configured to send the request carrying the application identifier of the target application to the gateway, receive the response data returned by the gateway, obtain the gateway and add it to the response data update information, and determine whether to update the target application according to the update information. 6. An electronic device, comprising a memory and a processor; wherein the memory is used to store one or more computer instructions, wherein the one or more computer instructions are executed by the processor to achieve The following method steps: Upload the update data of the target application to the content distribution server; Acquiring update information of the update data on the content distribution server, wherein the update information includes information that can obtain a first storage address and a first update timestamp of the update data on the content distribution server; The update information is returned in response to the update information request by the gateway for the target application. 7. An electronic device, comprising a memory and a processor; wherein the memory is used to store one or more computer instructions, wherein the one or more computer instructions are executed by the processor to achieve The following method steps: receiving a request sent by a target application, wherein the request includes an application identifier of the target application; Carrying the update information of the target application in the response data and returning it to the client, where the update information includes a first storage address and a first update timestamp on the content distribution server that can obtain the update data of the target application Information. 8. An electronic device, comprising a memory and a processor; wherein the memory is used to store one or more computer instructions, wherein the one or more computer instructions are executed by the processor to achieve The following method steps: Send a request carrying the application identifier of the target application to the gateway; receiving the response data returned by the gateway; acquiring the update information added by the gateway to the response data, wherein the update information includes information that can acquire the first storage address and the first update timestamp of the update data of the target application on the content distribution server; Whether to update the target application is determined according to the update information. 9. A readable storage medium having computer instructions stored thereon, wherein the computer instructions implement the method steps of claim 1 when executed by a processor. 10. A readable storage medium having computer instructions stored thereon, wherein the computer instructions implement the method steps of claim 2 when executed by a processor.

Images