WO2021051747A1 - Data update method, system and device, electronic device, and computer storage medium - Google Patents

Abstract

Provided are a data update method, system and device, an electronic device and a computer storage medium. The method comprises: uploading update data of a target application to a content distribution server (S101); obtaining update information of the update data on the content distribution server, wherein, the update information comprises information capable of acquiring a first storage address and a first update timestamp of the update data on the content distribution server (S102); returning the update information in response to a gateway's update information request for the target application (S103). The method alleviates the pressure of the server in receiving the update information request, and at the same time avoids the problem of resource waste caused by the client polling for actively requesting the update data.

Description

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

Cross-references to related applications

This disclosure claims the priority of the Chinese patent application number "CN201910878239.1" filed on September 17, 2019, the entire content of which is incorporated into this application as a whole.

Technical field

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

Background technique

With the development of Internet technology, users have put forward higher demands for the enrichment and diversification of client application (APP) functions. Server-side technology developers need to continuously improve application functions, form application update data, and generate new The version of the application that allows users to update the application on the client. In related technologies, the client generally uses two methods to obtain application update data: the server actively pushes the update data or the client polls and actively requests the update data. The server actively pushes updated 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 by itself and request the latest application update data from the server.

Summary of the invention

The embodiments of the present disclosure provide a data update method, system, device, electronic equipment, and computer storage medium.

In the first aspect, an embodiment of the present disclosure provides a data update method, which includes: uploading update data of a target application to a content distribution server; obtaining update information of the update data on the content distribution server, where the update information includes being able to obtain The first storage address of the update data on the content distribution server and the first update timestamp information; in response to the gateway's update information request for the target application, the update information is returned.

In a second aspect, an embodiment of the present disclosure provides a data update method, including: receiving a request sent by a target application, where the request includes the application identifier of the target application; carrying the update information of the target application in the response data and returning it to the client Terminal, where the update information includes information capable of obtaining the first storage address and the first update timestamp of the update data of the target application on the content distribution server.

In a third aspect, an embodiment of the present disclosure provides a data update method, which includes: sending a request carrying an application identifier of the target application to a gateway; receiving response data returned by the gateway; obtaining update information added by the gateway to the response data, Wherein, the update information includes information capable of obtaining the first storage address and the first update timestamp of the update data of the target application on the content distribution server; according to the update information, it is determined whether to update the target application.

In a fourth aspect, an embodiment of the present disclosure provides a data update method, which includes: a server uploads update data of a target application to a content distribution server, and obtains update information of the update data on the content distribution server, where the update information includes The information of the first storage address and the first update timestamp of the update data on the content distribution server can be obtained; the server responds to the gateway's update information request for the target application and returns update information to the gateway; the gateway receives the request sent by the target application, and The update information of the target application is carried in the response data and returned to the client, where the request includes the application identification of the target application; 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.

In a fifth aspect, an embodiment of the present disclosure provides a data update system, including: a server, a gateway, and a client. The server is used to upload update data of the target application to the content distribution server, and obtain the update data in the content distribution server. The update information on the server, and in response to the gateway's update information request for the target application, the update information is returned to the gateway, where the update information includes the first storage address and the first update timestamp that can obtain the update data on the content distribution server Information; gateway, used to receive the request sent by the target application, the update information of the target application is carried in the response data and returned to the client, where the request includes the application identification of the target application; the client is used to send the target carrying the target to the gateway The request for the application identifier of the application receives the response data returned by the gateway, obtains the update information added by the gateway to the response data, and determines whether to update the target application according to the update information.

In a sixth aspect, an embodiment of the present disclosure provides a data update device, including: an upload module configured to upload update data of a target application to a content distribution server; a first acquisition module configured to acquire update data in the content The update information on the distribution server, where the update information includes information capable of obtaining the first storage address and the first update timestamp of the update data on the content distribution server; the first return module is configured to respond to the gateway’s response to the target application Update information request, return update information.

In a seventh aspect, an embodiment of the present disclosure provides a data update device, including: a first receiving module configured to receive a request sent by a target application, wherein the request includes the application identifier of the target application; and a second return module, It is configured to carry the update information of the target application in the response data and return it to the client, where the update information includes information capable of obtaining the first storage address and the first update timestamp of the update data of the target application on the content distribution server.

In an eighth aspect, an embodiment of the present disclosure provides a data update device, including: a second sending module configured to send a request carrying an application identifier of a target application to a gateway; and a third receiving module configured to receive the gateway Returned response data; the third obtaining module is configured to obtain the update information added by the gateway to the response data, where the update information includes the first storage address and the first update on the content distribution server that can obtain the update data of the target application Time stamp information; the determining module is configured to determine whether to update the target application according to the update information.

In a ninth aspect, an embodiment of the present disclosure provides an electronic device, including a memory and a processor, where the memory is used to store one or more computer instructions, where one or more computer instructions are executed by the processor to achieve the following The method of any one of the first aspect, the second aspect, the third aspect to the fourth aspect.

In a tenth aspect, an embodiment of the present disclosure provides a readable storage medium with computer instructions stored thereon. When the computer instructions are executed by a processor, the first aspect, the second aspect, the third aspect to the fourth aspect are implemented. Any one of the methods.

According to the technical solution provided by the embodiments of the present disclosure, the pressure on the server to receive the update information request is alleviated, and at the same time, the problem of resource waste generated in the way that the client polls actively requests to update the data is avoided.

It should be understood that the above general description and the following detailed description are only exemplary and explanatory, and cannot limit the present disclosure.

Description of the drawings

With reference to the accompanying drawings, through the following detailed description of the non-limiting implementation manners, other features, purposes and advantages of the present disclosure will become more apparent. In the attached picture:

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

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

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

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

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

FIG. 6 shows a structural block diagram of a data update device 600 according to an embodiment of the present disclosure;

FIG. 7 shows a structural block diagram of a data update device 700 according to an embodiment of the present disclosure;

FIG. 8 shows a structural block diagram of a data update device 800 according to an embodiment of the present disclosure;

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

Fig. 10 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 description

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. In addition, for the sake of clarity, parts that are not related to the description of the exemplary embodiments are omitted in the drawings.

In the present disclosure, it should be understood that terms such as "including" or "having" are intended to indicate the existence of the features, numbers, steps, actions, components, parts, or combinations thereof disclosed in this specification, and are not intended to exclude one The possibility of existence or addition of multiple other features, numbers, steps, behaviors, components, parts or combinations thereof.

In addition, it should be noted that the embodiments in the present disclosure and the features in the embodiments can be combined with each other if there is no conflict. Hereinafter, the present disclosure will be described in detail with reference to the drawings and in conjunction with the embodiments.

In the way that the server actively pushes the update data, the network between the server and the client sometimes becomes unstable, which causes the long link between the server and the client to be 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, as the number of clients increases, the number of target clients for the server to push updated data will increase, resulting in an uncontrollable situation in which the arrival rate, coverage rate, and coverage time of the server push updated data. Therefore, it will cost more Resources.

In the client polling active request update data mode, the user will shorten the request time period to obtain the server's fast response, resulting in the rapid increase of client requests to the server. As the number of clients increases, the pressure on the server will increase. The larger the future, the support of a large number of resources such as databases is also required, and therefore, a waste of resources will be formed.

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, upload the update data of the target application to the content distribution server;

In step S102, obtain update information of the update data on the content distribution server, where the update information includes information capable of obtaining the first storage address and the first update timestamp of the update data on the content distribution server;

In step S103, in response to the gateway's update information request 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, where 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. There is no specific limitation in the embodiments of the present disclosure. In order to relieve the pressure on the server and improve the response speed and hit rate of data requests, when the technical developer updates the target application, the update data of the target application can be uploaded to the content delivery 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 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 application identification of the target application and the corresponding update data can be uploaded to the CDN at the same time, where: 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 identification 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 Key corresponds to the application identification and 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 on the content distribution server that can obtain the update data. An update time stamp information, wherein the update data can be obtained by accessing the first storage address, and the first update time stamp corresponds to the time stamp of the update data uploaded to the CDN. The embodiment of 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 identification of the target application and the update information can be stored in association.

As mentioned above, in order to avoid the above-mentioned technical problems caused by the server actively pushing update data or the client polling actively requesting update data, according to the embodiment of the present disclosure, the gateway can be set to periodically send the update of the target application to the server. Information request, the embodiment of 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 gateway's request for update information of the target application, the server returns the latest update information of the target application. In order to identify the update information request corresponding to different target applications, the update information request can carry the application identification of the target application. The server responds to the gateway's update information request for the target application and determines the target application corresponding to the current update information request according to the application identification. The updated information of the target application is returned to the gateway.

It should be noted that the gateway mentioned in the embodiment of the present disclosure is a gateway on the server side, 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 of the target application can enter the server through the gateway.

According to the technical solution provided by the embodiments of the present disclosure, the pressure on the server to receive the update information request is alleviated, and at the same time, the problem of resource waste generated in the way that the client polls actively requests to update the data is avoided.

According to an embodiment of the present disclosure, the update information includes a first storage address of the update data on the content distribution server and a first update timestamp. In this embodiment, the gateway can directly obtain 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 through 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 embodiment of the present disclosure uses a uniform resource locator (Uniform Resource Locator, URL) representation form for the first storage address, and the first update timestamp is illustrated by obtaining milliseconds, the embodiment of the present disclosure is not limited to this. 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"), by accessing the first storage address "https://xxx.xx/a/1json.json", the updated data can be obtained, and the timestamp "1564114914423" of the updated data uploaded to the CDN can be obtained.

According to another embodiment 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; the index file includes the service identification and storage of at least one target service of the target application. Address and update timestamp; the update data includes 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, configuration center service, offline package service, and patch service. After one or more target businesses of the target application change, the developer can package the updated one or more target businesses in the form of updated data of the target business. The following will take the target business as a patch business or an offline package business as an example Note, but the embodiments of the present disclosure are not limited to this. For example, after the client obtains the update data of the patch service or offline package service, the target application can be updated on the local client. If there is only one target business, that is, the target application has only one target business changed, the update data of the target application includes the update data of this target business; if there are two or more target businesses, that is, the target application has If two or more target businesses have changed, the update data of the target application may include update data of one target business, may include update data of part of the target business, or may include update data of all target businesses.

According to the embodiments 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 can be established to store the update information of different target services, where , The index file may include the service identifier, update address, and update timestamp of at least one target service of the target application, where 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 timestamp corresponds to the timestamp of the update data of the target service uploaded to the CDN. In the embodiment of the present disclosure, the corresponding data of the two target services in the target application will be changed, and the service identifier will be illustrated in the form of the service name, but the embodiment of the present disclosure is not limited to this. 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" and the appVersion is "7.20.4". The update address of the central business is "https://xxx.xx/b/1json.json", the update timestamp is "1563405958296", and the update address of the offline package business is "https://xxx.xx/b/2json. json", the update timestamp is "1564039123355", the index file of APP2 can be expressed as:

{"speedboat_offline_deploy":25230564-7.20.4-1564039123355;

https://xxx.xx/b/2json.json",

"crystal_config":"25230564-7.20.4-1563405958296; https://xxx.xx/b/1json.json"}.

According to the above-mentioned embodiment 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 The index file is acquired, and the latest update time of the index file can also be determined through the second update timestamp. After the index file is obtained through the second storage address, the service identification, 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 latest update data uploaded by the server to the CDN includes information about the target application. When the data of the target service A is updated, the first storage address and the first update timestamp of the updated data of the target service A on the CDN can be obtained through the index file. The embodiment of 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.

According to an embodiment of the present disclosure, the step S102, that is, obtaining the update information of the update data on the content distribution server, includes the following steps: obtaining the first storage address and the first update timestamp of the update data on the content distribution server; Update the index file with the first storage address and the first update timestamp; upload the index file to the content distribution server; obtain 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 its update data to the CDN, and obtains its upload address, that is, the first storage address, and the upload timestamp, that is, from the CDN. The first update timestamp. Since the update data of the target application includes 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 acquired, and the The first storage address and the first update timestamp are associated and stored in the index file with the business identification of one or more target services in the update data. If the index file has been associated and stored corresponding to the business identification of one or more target services In the case of the entry, the current first storage address and the first update timestamp can be used to update the entry, that is, to update the current index file.

According to an 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 index file is uploaded to the latest timestamp on the CDN. The index file can be obtained by accessing the second storage address, and 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 a request for update information of the target application to the server, the server may return the second storage address and the second update timestamp of the index file on the CDN to the gateway.

According to an embodiment of the present disclosure, the update of the index file according to the first storage address and the first update timestamp may also be implemented as: update the update address and 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.

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

{"speedboat_offline_deploy":25230564-7.20.4-1564039123355;

https://xxx.xx/b/2json.json",

"crystal_config":"25230564-7.20.4-1563405958296; https://xxx.xx/b/1json.json"}

Assuming that only the business file of the configuration center business is changed, and the first storage address is "https://xxx.xx/b/3json.json" and the first update timestamp is "1564014914423", then the configuration center business update will be changed The 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 time Stamp "1564014914423" to obtain the updated index file as:

{"speedboat_offline_deploy":25230564-7.20.4-1564039123355;

https://xxx.xx/b/2json.json",

"crystal_config":"25230564-7.20.4-1564014914423; https://xxx.xx/b/3json.json"}.

Fig. 2 shows a flowchart of a data update method according to an embodiment of the present disclosure, and the data update method is executed at the gateway end. As shown in Figure 2, the data update method includes the following steps S201-S202:

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

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

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 that can perform network communication. In order to determine whether the target application has update information, in the embodiments of the present disclosure, the target application may not directly send an update information request to the server, but a specially developed software development kit (SDK) is sent to the target application by intercepting the target application. Any request from the server, and the application identifier of the target application is added to the request to obtain update information about the target application. The application identifier is used to identify different target applications and different versions of the same target application, and the application identifier may include the application Unique 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 application identifier carried in the request (for example, a 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 then 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 solution provided by the embodiments of the present disclosure, the problem of resource waste generated in the way that the client polls actively requests to 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 For the client, the response speed of update data is improved, so that multiple clients can achieve "second-level" updates at the same time. At the same time, the client sends a request to the server into a periodic request from the gateway to the server, which relieves the server from receiving update information. The pressure of the request.

According to an embodiment of the present disclosure, the update information includes a first storage address of the update data on the content distribution server and a first update timestamp. For the specific implementation details of the embodiments of the present disclosure, reference may be made to the relevant description in the data update method executed on the server side above, which will not be repeated here.

According to another embodiment 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; the index file includes the service identification and storage of at least one target service of the target application. Address and update timestamp; the update data includes update data of at least one target service of the target application. For the specific implementation details of the embodiments of the present disclosure, reference may be made to the relevant description in the data update method executed on the server side above, which will not be 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. For the specific implementation details of the embodiments of the present disclosure, reference may be made to the relevant description in the data update method executed on the server side above, which will not be repeated here.

According to an embodiment of the present disclosure, after receiving the request sent by the target application, the method further includes the following steps:

Obtain 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.

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

According to an embodiment of the present disclosure, carrying the update information of the target application in the response data and returning includes the following steps: determining 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 the 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. 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, thereby avoiding 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 the gateway will be used 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.

According to an embodiment of the present disclosure, the data update method further includes the following steps: periodically sending a request for update information of the target application to the server; and receiving 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 embodiment of the present disclosure does not specifically limit the update information request period. It can be limited according to actual conditions, 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 gateway's request for update information of the target application, the server returns the update information of the target application, and 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 through the update information.

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 to replace the original update information. ; Or, when the gateway obtains the update information of the target application from the server, it can determine whether to store the update information obtained from the server according to whether the update information obtained from the server 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. The first update timestamp in the acquired update information is compared with the local timestamp in the locally stored local update information. If the first update timestamp in the update information is later than the local timestamp in the local update information, it indicates that the slave server The obtained update information is newer than the local update information stored locally, you can accept the update information of one or more target applications returned by the server and store the update information locally in the gateway. Otherwise, it indicates that the locally stored local update information is already The latest update information may not be stored.

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 client. As shown in Figure 3, the data update method includes the following steps S301-S304:

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

In step S302, the response data returned by the gateway is received;

In step S303, the update information added by the gateway to the response data is obtained, where the update information includes information capable of obtaining the first storage address and the first update timestamp of the update data of the target application on the content distribution server;

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

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 server-side gateway before reaching the server, that is, the request is first sent to the server-side gateway, where the target application refers to the data generation If one or more applications are updated, the request includes any request issued 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 update information, the SDK can carry the application identifier of the target application in any intercepted request, and send the request to the server's gateway, so as to obtain whether the target application has update 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. In the same way, after the client obtains the response data returned by the gateway, the update information of the target application can also be obtained 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). The client can be a handheld terminal device, a laptop computer, a cellular phone, a smart phone, a wireless data card, a personal digital assistant computer, a tablet computer, a cordless phone, an Internet of Things device (IOT device) or other terminal devices that can access the network There is no specific limitation in the embodiments of the present disclosure.

According to the embodiments of the present disclosure, after the gateway receives the request sent by the target application, it can obtain the application identifier carried in the 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 then 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 first storage address and the first update timestamp information on the CDN that can obtain the update data of the target application, where it can be obtained by accessing the first storage address The data is updated, and the first update timestamp corresponds to the timestamp when the update data is uploaded to the CDN. The embodiment of 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 update information of the target application locally, it can be determined that the update information obtained from the gateway corresponds to Whether the update data has been updated locally, if it has been updated, no processing is required. 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 can be updated locally The application is updated; of course, you can also record the update information first, and then update it in batches.

According to the technical solution provided by the embodiments of the present disclosure, the problem of resource waste generated in the way that the client polls actively requests to update data is avoided. At the same time, the gateway directly sends the application identifier of the target application according to the application identifier of the target application carried in the request sent by the target application. The response data carries the update information of the target application and 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 a first storage address of the update data on the content distribution server and a first update timestamp. For the specific implementation details of the embodiments of the present disclosure, reference may be made to the relevant description in the data update method executed on the server side above, which will not be repeated here.

According to another embodiment 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; the index file includes the service identification and storage of at least one target service of the target application. Address and update timestamp; the update data includes update data of at least one target service of the target application. For the specific implementation details of the embodiments of the present disclosure, reference may be made to the relevant description in the data update method executed on the server side above, which will not be 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. For the specific implementation details of the embodiments of the present disclosure, reference may be made to the relevant description in the data update method executed on the server side above, which will not be repeated here.

According to an embodiment of the present disclosure, the step S301, that is, sending a request carrying the application identifier of the target application to the gateway, includes the following steps: intercepting the request sent by the target application to the server; carrying the application identifier of the target application in the request and sending Gateway to the server.

According to the embodiment 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 through 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 server's gateway 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 request header and sent to the server's gateway. In the same way, after the client obtains the response data returned by the gateway, the update information of the target application can also be obtained from the response data through the SDK.

According to an embodiment of the present disclosure, the step S304, that is, determining whether to update the target application according to the update information, can also be implemented as: when the first update timestamp is later than the third update timestamp of the target application locally, recording the target The app has updated data. In this embodiment, since some target applications only need to confirm whether they have been updated, there is no need to download the update data of the target application immediately. When the first update timestamp is later than the third update timestamp, where the third update timestamp may be the first update timestamp of the update data that was most recently downloaded from the CDN and updated the target application, and the locally stored If the update data of the target application has been 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 S304, which is to determine whether to update the target application according to the update information, can also be implemented as: when the first update timestamp is later than the third update timestamp of the target application locally A storage address downloads the update data of the target application; the target application is updated according to the update data of the target application. In this embodiment, the first update timestamp may be compared with the local third update timestamp, where the third update timestamp may be the first update time of the update data that was most recently downloaded from the CDN and updated the target application Stamp to determine whether to download and install the updated data of the target application. Specifically, when the first update timestamp is later than the third local update timestamp, it indicates that the update data of the target data is updated compared to 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 updated data of the target application.

According to an embodiment of the present disclosure, the step S304, that is, determining whether to update the target application according to the update information, includes the following steps: when the second update timestamp is later than the fourth update timestamp of the local index file, from the second storage address Download the index file; 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.

According to an embodiment of the present disclosure, the client can store the local index file corresponding to the target application last obtained from the server and the fourth update timestamp of the local index file on the CDN, and one or more of the target applications recorded in the index file The updated data of multiple target services has 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 first update timestamp of the local index file stored locally. Four update timestamps, where the fourth update timestamp corresponds to the timestamp when the local index file is uploaded to the CDN 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 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 index file stores the service identifier, the first storage address, and the first update timestamp of at least one target service in association, when the index file is updated, it indicates that at least one target service stored in the index file has occurred. Update, so that 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 local index file stored locally.

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 the following steps: the first update timestamp is later than at least one stored locally At the fifth update timestamp corresponding to the target service, download the update data of the target service from the first storage address; update the target service according to the update data of the target service.

According to the embodiment of the present disclosure, 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 timestamp of at least one target service of the target application in association with each other. , 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 stores the service identifier of at least one target service, the first storage address, and the first update timestamp in association, the first update timestamp 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 timestamp is later than the fifth update timestamp, 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. Therefore, the update data can be downloaded from the first storage address. Update data of the target business, and update the target business of the target application according to the updated data.

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

{"speedboat_offline_deploy":25230564-7.20.4-1564036123355;

https://xxx.xx/b/22json.json",

"crystal_config":"25230564-7.20.4-1563405658296; https://xxx.xx/b/21json.json"}

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

{"speedboat_offline_deploy":25230564-7.20.4-1564039123355;

https://xxx.xx/b/2json.json",

"crystal_config":"25230564-7.20.4-1563405958296; https://xxx.xx/b/1json.json"}

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 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 only need to confirm whether they have been updated, it is not necessary to download the update data of the target service immediately, for example, offline package services and patch services only need to obtain update messages, but do not need to download the update of the target service immediately Therefore, according to the embodiment of the present disclosure, step S902, which is to 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, can also be implemented as: at the first update time When the stamp is later than or equal to the fifth update timestamp corresponding to at least one target service stored locally, it is recorded that the target service has update data.

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

{"speedboat_offline_deploy":25230564-7.20.4-1564036123355;

https://xxx.xx/b/22json.json",

"crystal_config":"25230564-7.20.4-1563405658296; https://xxx.xx/b/21json.json"}

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

{"speedboat_offline_deploy":25230564-7.20.4-1564039123355;

https://xxx.xx/b/2json.json",

"crystal_config":"25230564-7.20.4-1563405958296; https://xxx.xx/b/1json.json"}

For offline packet services, since the first update timestamp "1564039123355" is later than the fifth update timestamp "1564036123355", it can be determined that the update data of offline packet services stored locally has been updated, and this situation can be recorded first. In order to download and install at an appropriate time later (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 for configuring the offline package service from the first storage address "https://xxx.xx/b/2json.json".

Fig. 4 shows a flowchart of a data update method according to an embodiment of the present disclosure. As shown in Figure 4, the data update method includes the following steps S401-S404:

In step S401, 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, where the update information includes the first storage address that can obtain the update data on the content distribution server And the information of the first update timestamp;

In step S402, the server returns update information to the gateway in response to the gateway's update information request for the target application;

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

In step S404, the client obtains the update information added by the gateway to 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, where 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. There is no specific limitation in the embodiments of the present disclosure. In order to relieve the pressure on the server and improve the response speed and hit rate of data requests, when the technical developer updates the target application, the update data of the target application can be uploaded to the CDN through the server. The target application refers to the data update. For one or more applications, 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 can upload the application identification of the target application and the corresponding update data to the CDN at the same time, where 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 identification 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 Key corresponds to the application identification and Value corresponds to the update data.

According to an 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. The update information includes the first storage address and the first storage address of the CDN that can obtain the update data. Update the information of the timestamp, where the update data can be obtained by accessing the first storage address, and the first update timestamp corresponds to the timestamp of the update data uploaded to the CDN. The embodiment of 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 identification of the target application and the update information can be stored in association.

As mentioned above, in order to avoid the above-mentioned technical problems caused by the server actively pushing update data or the client polling actively requesting update data, according to the embodiment of the present disclosure, the gateway can be set to periodically send the update of the target application to the server. Information request, the embodiment of 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 gateway's request for update information of the target application, the server returns the latest update information of the target application. In order to identify the update information request corresponding to different target applications, the update information request can carry the application identification of the target application. The server responds to the gateway's update information request for the target application and determines the target application corresponding to the current update information request according to the application identification. The updated information of the target application is returned to the gateway.

It should be noted that the gateway mentioned in the embodiment of the present disclosure is a gateway on the server side, 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 of the target application can enter the server through the gateway. The client can be a handheld terminal device, a laptop computer, a cellular phone, a smart phone, a wireless data card, a personal digital assistant computer, a tablet computer, a cordless phone, an Internet of Things device (IOT device) or other terminal devices that can access the network There is no specific limitation in the embodiments of the present disclosure.

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. In order to determine whether the target application has update information, in the embodiments of the present disclosure, the target application on the client does not need to directly send an update information request to the server. Instead, the specially developed SDK on the client intercepts the target application sent to the server. Any request, and add the application identifier of the target application 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 carry the application identifier of the target application in the header of the request and send it to the server.

According to the embodiment 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 in the gateway. Identifies 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 the 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 can be judged whether the update data corresponding to the update information obtained from the gateway has been updated locally on the client. If it has been updated, it can not be processed. If it has not been updated, the client can obtain the update information from the gateway. The first storage address in downloads the update data of the target application, and updates the target application locally; of course, the client can also record the update information first, and then update it in batches.

According to the technical solution provided by the embodiments of the present disclosure, the problem of resource waste generated in the way that the client polls actively requests to 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 determine whether it needs to update the target application according to the update information, which improves the response speed of the update data, so that multiple clients can achieve "second-level" updates at the same time, and at the same time, the client sends a request to the server to convert In order for the gateway to periodically initiate requests to the server, the pressure on the server to receive requests for updated information is relieved.

According to an embodiment of the present disclosure, the update information includes a first storage address of the update data on the content distribution server and a first update timestamp. For the specific implementation details of the embodiments of the present disclosure, reference may be made to the relevant description in the data update method executed on the server side above, which will not be repeated here.

According to another embodiment 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; the index file includes the service identification and storage of at least one target service of the target application. Address and update timestamp; the update data includes update data of at least one target service of the target application. For the specific implementation details of the embodiments of the present disclosure, reference may be made to the relevant description in the data update method executed on the server side above, which will not be 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. For the specific implementation details of the embodiments of the present disclosure, reference may be made to the relevant description in the data update method executed on the server side above, which will not be repeated here.

According to an embodiment of the present disclosure, obtaining the update information of the update data on the content distribution server in the step S401 includes the following steps: the server obtains the first storage address and the 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.

According to the embodiments of the present disclosure, after one or more target services of the target application are updated, the server uploads its update data to the CDN, and obtains its upload address, that is, the first storage address, and the upload timestamp, 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 adds The first storage address and the first update timestamp are associated and stored in the index file with the service identification of one or more target services in the update data. If the index file has already associated and stored the service identification of one or more target services For the corresponding entry, the current first storage address and the first update timestamp can be used to update the entry, that is, to update the current index file.

According to the embodiment of the present disclosure, in order to relieve the pressure of 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 is uploaded to the CDN. The index file can be obtained by accessing the second storage address, and 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 a request for update information of the target application to the server, the server may return the second storage address and the second update timestamp of the index file on the CDN to the gateway.

According to an embodiment of the present disclosure, the server updates the index file according to the first storage address and the first update timestamp, which may also be implemented as: the server updates the update address and update timestamp associated with the service identifier of the target service in the index file The update is 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. When one or more of the target services is updated, the server may according to the first storage address and the first storage address of the update data uploaded to the CDN. An update timestamp updates the update information corresponding to the service identification 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 timestamp to the first update timestamp, thereby completing the update of the index file. For example, the original index file is:

{"speedboat_offline_deploy":25230564-7.20.4-1564039123355;

https://xxx.xx/b/2json.json",

"crystal_config":"25230564-7.20.4-1563405958296; https://xxx.xx/b/1json.json"}

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 The 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" to obtain the updated index file as:

{"speedboat_offline_deploy":25230564-7.20.4-1564039123355;

https://xxx.xx/b/2json.json",

"crystal_config":"25230564-7.20.4-1564014914423; https://xxx.xx/b/3json.json"}.

According to the embodiment of the present disclosure, the step S403, that is, the gateway receives the request sent by the target application, and returns the update information of the target application in the response data to the client, and further includes the following step: the gateway obtains the target carried in the request The application identifier of the application; 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 obtains 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 ID is added to the local application list.

According to the embodiments of the present disclosure, since all requests sent by the target application to the server of the target application in the client terminal will pass through the server-side gateway, the gateway can first obtain the application identification of the target application from the request, and then determine whether the local application list of the gateway is already 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 already stored the application identifier of the target application, there is no need to add the application identifier 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 embodiment of the present disclosure does not specifically limit the storage manner of the application identifier in the local application list, and may be determined according to actual application requirements.

According to the embodiment of the present disclosure, after the gateway obtains the application identifier, it first determines whether the gateway locally stores the update information of the target application. 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.

According to an embodiment of the present disclosure, the data update method further includes the following steps: 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.

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 embodiment of the present disclosure does not specifically limit the update information request period. It can be limited according to actual conditions, 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 gateway's request for update information of the target application, the server returns the update information of the target application, and 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 through the update information.

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 to replace the original update information. ; Or, when the gateway obtains the update information of the target application from the server, it can determine whether to store the update information obtained from the server according to whether the update information obtained from the server 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 The first update timestamp in the obtained update information is further compared with the local timestamp in the locally stored local update information. If the first update timestamp in the update information is later than the local timestamp in the local update information, it indicates The update information that the gateway obtains from the server is newer than the local update information stored locally in 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. Otherwise, it indicates that the gateway stores locally. If the local update information of is already the latest update information, the gateway may not store the update information.

According to an embodiment of the present disclosure, the data update method further includes the following steps: the client sends a request carrying the application identifier of the target application to the gateway; 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 passes through the server-side gateway and then reaches the server, that is, the request is first sent to the server-side gateway. When the target application in the client sends a request to the server, it can intercept the request to be sent through the SDK installed locally in the client. In order to know whether the target application in the client has update information, the SDK can carry the application identifier of the target application in any intercepted request, and send the request to the server's gateway to obtain whether the target application has update 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. In the same way, after the client obtains the response data returned by the gateway, the update information of the target application can also be obtained from the response data through the SDK.

According to an embodiment of the present disclosure, the client sends a request carrying the application identification of the target application to the gateway, including the following steps: the client intercepts the request sent by the target application to the server; the client carries the application identification of the target application in the request The gateway sent to the server in the.

According to the embodiment 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 through 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 server's gateway to obtain the update information of the target application. Since the request includes a packet header and a packet body, the client can carry the application identifier of the target application in the request header and send it to the server's gateway.

According to an embodiment of the present disclosure, the step S404, that is, the client determines whether to update the target application according to the update information, can also be implemented as: when the first update timestamp is later than the third update timestamp of the target application locally, 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, there is no need to download the update data of the target application immediately. When the first update timestamp is later than the third update timestamp, where the third update timestamp may be the first update timestamp of the update data that was most recently downloaded from the CDN and updated the target application, and the locally stored If the update data of the target application is updated, the client can record the situation 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 S404, that is, the client determines whether to update the target application according to the update information, can also be implemented as: when the first update timestamp is later than the third update timestamp of the target application locally, 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 timestamp may be compared with the local third update timestamp, where the third update timestamp may be the first update time of the update data that was most recently downloaded from the CDN and updated the target application Stamp to determine whether to download and install the updated data of the target application. Specifically, when the first update timestamp is later than the third local update timestamp, it indicates that the update data of the target data is updated compared to 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.

According to an embodiment of the present disclosure, the step S404, that is, the client determines whether to update the target application according to the update information, includes the following steps: when the second update timestamp is later than the fourth update timestamp of the local index file, the client starts from The index file is downloaded at the second storage address; the client terminal determines 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.

According to an embodiment of the present disclosure, the client can store the local index file corresponding to the target application last obtained from the server and the fourth update timestamp of the local index file on the CDN, and one or more of the target applications recorded in the index file The updated data of multiple target services has 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 of, where the fourth update timestamp corresponds to the timestamp of the local index file uploaded to the CDN 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. Therefore, the client can download the latest update from the second storage address. Index file.

According to the embodiment of the present disclosure, since the index file stores the service identifier, the first storage address, and the first update timestamp of at least one target service in association, when the index file is updated, it indicates that at least one target service stored in the index file has occurred. Update, so that 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.

According to an embodiment of the present disclosure, 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, including the following steps: the first update timestamp is later than the locally stored When the fifth update timestamp corresponding to 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.

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 associatedly stores the service identifier and the fifth update timestamp of at least one target service of the target application , Where the fifth update timestamp corresponds to the timestamp at which the update data of the target service stored locally in the client is uploaded to the CDN. When the index file downloaded by the client from the second storage address stores the service identification of at least one target service, the first storage address, and the first update timestamp in association, the first update timestamp can be compared with the target service information 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 timestamp is later than the fifth update timestamp, 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. Therefore, the client can download from the first storage address Download the updated data of the target business, and update the target business of the target application according to the updated data.

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

{"speedboat_offline_deploy":25230564-7.20.4-1564036123355;

https://xxx.xx/b/22json.json",

"crystal_config":"25230564-7.20.4-1563405658296; https://xxx.xx/b/21json.json"}

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

{"speedboat_offline_deploy":25230564-7.20.4-1564039123355;

https://xxx.xx/b/2json.json",

"crystal_config":"25230564-7.20.4-1563405958296; https://xxx.xx/b/1json.json"}

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 download from 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 client's target application only need to confirm whether they have been updated, there is no need to download the update data of the target business immediately. For example, offline package services and patch services only need to obtain update messages, and the client does not need to download the update immediately. The update data of the target service. Therefore, according to the embodiment of the present disclosure, 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 at least one target service in the index file, which can also be implemented as : When the first update timestamp is later than or equal to the fifth update timestamp corresponding to at least one target service stored locally, the client terminal records that the target service has update data.

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

{"speedboat_offline_deploy":25230564-7.20.4-1564036123355;

https://xxx.xx/b/22json.json",

"crystal_config":"25230564-7.20.4-1563405658296; https://xxx.xx/b/21json.json"}

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

{"speedboat_offline_deploy":25230564-7.20.4-1564039123355;

https://xxx.xx/b/2json.json",

"crystal_config":"25230564-7.20.4-1563405958296; https://xxx.xx/b/1json.json"}

For offline packet services, since the first update timestamp "1564039123355" is later than the fifth update timestamp "1564036123355", it can be determined that the update data of offline packet services stored locally on the client has been updated, and the client can first Record the situation so that it can be downloaded and installed at an appropriate time later (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 for configuring the offline package service from the first storage address "https://xxx.xx/b/2json.json".

FIG. 5 shows a schematic structural diagram of a data update system 500 according to an embodiment of the present disclosure. As shown in Figure 5, the data update system includes a server 501, a gateway 502, and a client 503.

The server 501 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 gateway's update information request for the target application, return the update information to the gateway, where the update The information includes information capable of obtaining the first storage address and the first update timestamp of the update data on the content distribution server;

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

The client 503 is configured to send a request carrying the application identifier of the target application to the gateway, receive response data returned by the gateway, obtain update information added by the gateway to the response data, 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 on the server side, that is, the 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. The client can be a handheld terminal device, a laptop computer, a cellular phone, a smart phone, a wireless data card, a personal digital assistant computer, a tablet computer, a cordless phone, an Internet of Things device (IOT device) or other terminal devices that can access the network There is no specific limitation in the embodiments of the present disclosure.

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

According to an embodiment 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; the index file includes the service identification, storage address, and storage address of at least one target service of the target application. Update time stamp; the update data includes update data of at least one target service of the target application.

According to an embodiment of the present disclosure, the server is configured to obtain 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, and upload the index file to The content distribution server obtains the second storage address and the second update timestamp.

According to an embodiment of the present disclosure, the server is configured to update the update address and update timestamp associated with the service identification of the target service in the index file to the first storage address and the first update timestamp.

According to an embodiment of the present disclosure, the gateway is used to obtain the application identification of the target application carried in the request, and when the application identification is not stored in the local application list, the application identification is added to the local application list, and the application identification is used to determine whether the target application is stored locally 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, the gateway is used 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.

According to an embodiment of the present disclosure, the client is used to send a request carrying the application identifier of the target application to the gateway, and receive response data returned by the gateway.

According to the embodiment of the present disclosure, the client is used to intercept the request sent by the target application to the server, and carry the application identifier of the target application in the request and send it to the gateway of the server.

According to an embodiment of the present disclosure, the client is used to record that the target application has update data when the first update timestamp is later than the third update timestamp of the target application locally.

According to an embodiment of the present disclosure, the client is configured to download the update data of the target application from the first storage address when the first update timestamp is later than the third update timestamp of the target application locally, and update according to the update data of the target application Target application.

According to an embodiment of the present disclosure, 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, according to the corresponding service identifier of at least one target service in the index file The first update timestamp determines whether to update the target application.

According to an embodiment of the present disclosure, when the first update timestamp is later than the fifth update timestamp corresponding to at least one target service stored locally, the client records the update data of the target service.

According to an embodiment of the present disclosure, when the first time stamp is later than the fifth update time stamp corresponding to at least one target service stored locally, the client downloads the update data of the target service from the first storage address, and then downloads the update data of the target service according to the update data of the target service. Update the target business.

According to an embodiment of the present disclosure, target services include configuration center services, offline package services, and patch services.

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

FIG. 6 shows a structural block diagram of a data update device 600 according to an embodiment of the present disclosure. Wherein, the device can be implemented as part or all of the electronic equipment through software, hardware or a combination of the two. As shown in FIG. 6, the data update device includes an upload module 610, a first acquisition module 620, and a first return module 630.

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

The first obtaining module 620 is configured to obtain update information of the update data on the content distribution server, where the update information includes information capable of obtaining the first storage address and the first update timestamp of the update data on the content distribution server;

The first return module 630 is configured to return 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 a first storage address of the update data on the content distribution server and a first update timestamp.

According to an embodiment 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; the index file includes the service identification, storage address, and storage address of at least one target service of the target application. Update time stamp; the update data includes update data of at least one target service of the target application.

According to an embodiment of the present disclosure, obtaining the update information of the update data on the content distribution server includes: obtaining the first storage address and the first update timestamp of the update data on the content distribution server; according to the first storage address and the first update Update the index file with the timestamp; upload 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, updating the index file according to the first storage address and the first update timestamp includes: updating the update address and 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. An update timestamp.

According to an embodiment of the present disclosure, target services include configuration center services, offline package services, and patch services.

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

FIG. 7 shows a structural block diagram of a data update device 700 according to an embodiment of the present disclosure. Wherein, the device can be implemented as part or all of the electronic equipment through software, hardware or a combination of the two. As shown in FIG. 7, the data update device includes a first receiving module 710 and a second returning module 720.

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

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

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

According to an embodiment 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; the index file includes the service identification, storage address, and storage address of at least one target service of the target application. Update time stamp; the update data includes update data of at least one target service of the target application.

According to the embodiment of the present disclosure, carrying the update information of the target application in the response data and returning it to the client includes: determining 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 the embodiment of the present disclosure, it further includes:

The second obtaining module 730 is configured to obtain the application identifier of the target application carried in the request;

The adding module 740 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 the embodiment of the present disclosure, it further includes:

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

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

According to an embodiment of the present disclosure, target services include configuration center services, offline package services, and patch services.

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

FIG. 8 shows a structural block diagram of a data update device 800 according to an embodiment of the present disclosure. Wherein, the device can be implemented as part or all of the electronic equipment through software, hardware or a combination of the two. As shown in FIG. 8, the data update device includes a second sending module 810, a third receiving module 820, a third acquiring module 830, and a determining module 840.

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

The third receiving module 820 is configured to receive response data returned by the gateway;

The third obtaining module 830 is configured to obtain the update information added by the gateway to the response data, where the update information includes information capable of obtaining the first storage address and the first update timestamp of the update data of the target application on the content distribution server ；

The determining module 840 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 a first storage address of the update data on the content distribution server and a first update timestamp.

According to an embodiment 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; the index file includes the service identification, storage address, and storage address of at least one target service of the target application. Update time stamp; the update data includes update data of at least one target service of the target application.

According to an embodiment of the present disclosure, 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; carrying the application identifier of the target application in the request and sending it to the gateway of the server.

According to an embodiment of the present disclosure, determining whether to update the target application according to the update information and the local third update timestamp of the target application includes: recording the target when the first update timestamp is later than the third update timestamp of the target application locally The app has updated data.

According to an embodiment of the present disclosure, 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 timestamp is later than the third update timestamp of the target application locally, from Download the update data of the target application at the first storage address; update the target application according to the update data of the target application.

According to an embodiment of the present disclosure, 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 timestamp is later than the fourth update timestamp of the local index file, starting from the first 2. Download the index file from the storage address; 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.

According to an embodiment of the present disclosure, 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 first update timestamp is later than the locally stored at least one target service corresponding to When the fifth time stamp is updated, the update data of the target business is recorded.

According to an embodiment of the present disclosure, 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 first update timestamp is later than the locally stored at least one target service corresponding to When the fifth time stamp is updated, the update data of the target service is downloaded 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, target services include configuration center services, offline package services, and patch services.

The data update device in the embodiment of the present disclosure corresponds to the data update method of the embodiment shown in FIG. 7 and related embodiments. For specific 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. 9 shows a structural block diagram of an electronic device 900 according to an embodiment of the present disclosure.

As shown in FIG. 9, the electronic device 900 includes a memory 901 and a processor 902; where

The memory 901 is configured to store one or more computer instructions, where one or more computer instructions are executed by the processor 902 to implement any method according to the embodiments of the present disclosure.

Fig. 10 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. 10, the computer system 1000 includes a central processing unit (CPU) 1001, which can be based on a program stored in a read only memory (ROM) 1002 or a program loaded from a storage part 1008 into a random access memory (RAM) 1003 The various processes in the above-mentioned embodiment are executed. In the RAM 1003, various programs and data required for the operation of the system 1000 are also stored. The CPU 1001, ROM 1002, and RAM 1003 are connected to each other through a bus 1004. An input/output (I/O) interface 1005 is also connected to the bus 1004.

The following components are connected to the I/O interface 1005: an input part 1006 including a keyboard, a mouse, etc.; an output part 1007 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and speakers, etc.; a storage part 1008 including a hard disk, etc. ; And a communication part 1009 including a network interface card such as a LAN card, a modem, and the like. The communication section 1009 performs communication processing via a network such as the Internet. The driver 1010 is also connected to the I/O interface 1005 as needed. A removable medium 1011, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 1010 as needed, so that the computer program read therefrom is installed into the storage portion 1008 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, an embodiment of the present disclosure includes a computer program product, which includes a computer program tangibly embodied on a machine-readable medium, and the computer program includes program code for executing the foregoing object category determination method. In such an embodiment, the computer program may be downloaded and installed from the network through the communication part 1009, and/or installed from the removable medium 1011.

The flowcharts and block diagrams in the accompanying drawings illustrate the possible implementation architecture, functions, and operations of the system, method, and computer program product according to various embodiments of the present disclosure. In this regard, each block in the route diagram or block diagram can represent a module, program segment, or part of the code, and the module, program segment, or part of the code contains one or more executables that are used to implement the specified logical functions. instruction. It should also be noted that, in some alternative implementations, the functions marked in the block may also occur in a different order from the order marked in the drawings. For example, two blocks shown in succession can actually be executed substantially in parallel, and they can sometimes be executed in the reverse order, depending on the functions involved. It should also be noted that each block in the block diagram and/or flowchart, and the combination of the blocks in the block diagram and/or flowchart, can be implemented by a dedicated hardware-based system that performs the specified functions or operations Or it can be realized by a combination of dedicated hardware and computer instructions.

The units or modules involved in the embodiments described in the present disclosure can be implemented in software or hardware. 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 under certain circumstances.

As another aspect, the present disclosure also provides a computer-readable storage medium. The computer-readable storage medium may be the computer-readable storage medium included in the electronic device or computer system in the above-mentioned embodiments; or it may exist alone. , A computer-readable storage medium that is not installed in the device. The computer-readable storage medium stores one or more programs, and the programs are used by one or more processors to execute the methods described in the present disclosure.

The above description is only a preferred embodiment of the present disclosure and an explanation of the applied technical principles. Those skilled in the art should understand that the scope of the invention involved in this disclosure is not limited to the technical solutions formed by the specific combination of the above technical features, and should also cover the technical solutions described above without departing from the inventive concept. Other technical solutions formed by arbitrarily combining equivalent features. For example, the above-mentioned features and the technical features disclosed in the present disclosure (but not limited to) having similar functions are replaced with each other to form a technical solution.

Claims (78)

A data update method, which includes: Upload the updated data of the target application to the content distribution server; Obtaining update information of the update data on the content distribution server, where the update information includes information capable of obtaining a first storage address and a first update timestamp of the update data on the content distribution server; In response to the gateway's request for update information for the target application, return the update information. The method according to claim 1, wherein the update information includes the first storage address of the update data on the content distribution server and the first update timestamp. The method according to claim 1, wherein 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 The service identification, storage address, and update timestamp of at least one target service of the target application; the update data includes update data of at least one target service of the target application. The method according to claim 3, wherein obtaining the update information of the update data on the content distribution server comprises: 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. 4. The method according to claim 4, wherein said updating said index file according to said first storage address and said first update timestamp, comprising: adding said business information of said target business in said index file Identify that the associated update address and the update timestamp are updated to the first storage address and the first update timestamp. The method according to claim 3, wherein the target service includes a configuration center service, an offline package service, and a patch service. A data update method, which includes: Receiving a request sent by a target application, where the request includes the application identifier of the target application; The update information of the target application is carried in the response data and returned to the client, where the update information includes the first storage address and the first update timestamp on the content distribution server that can obtain the update data of the target application Information. 8. The method according to claim 7, wherein the update information includes the first storage address of the update data on the content distribution server and the first update timestamp. The method according to claim 7, wherein 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 The service identification, storage address, and update timestamp of at least one target service of the target application; the update data includes update data of at least one target service of the target application. The method according to claim 7, wherein said carrying the update information of the target application in response data and returning it to the client comprises: Determining whether 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. The method according to claim 7, wherein after the receiving the request sent by the target application, the method further comprises: Acquiring 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. The method according to claim 11, further comprising: Periodically sending the update information request of the target application to the server; Receiving the update information of the target application returned by the server. The method according to claim 9, wherein the target service includes a configuration center service, an offline package service, and a patch service. A data update method, which includes: Send a request carrying the application identifier of the target application to the gateway; Receiving response data returned by the gateway; Acquiring the update information added by the gateway to the response data, where the update information includes information capable of acquiring the first storage address and the first update timestamp of the update data of the target application on the content distribution server; Determine whether to update the target application according to the update information. The method according to claim 14, wherein the update information includes the first storage address of the update data on the content distribution server and the first update timestamp. The method according to claim 14, wherein 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 The service identification, storage address, and update timestamp of at least one target service of the target application; the update data includes update data of at least one target service of the target application. The method according to claim 14, wherein the sending the request carrying the application identifier of the target application to the gateway comprises: Intercept 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. The method according to claim 15, wherein the determining whether to update the target application according to the update information comprises: when the first update timestamp is later than a third local update timestamp of the target application At the time, record that the target application has updated data. The method according to claim 15, wherein the determining whether to update the target application according to the update information comprises: When the first update timestamp is later than the third local update timestamp of the target application, download 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. The method according to claim 16, wherein the determining whether to update the target application according to the update information comprises: When the second update timestamp is later than the fourth update timestamp of the local index file, download the index file from the second storage address; Determine 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. The method according to claim 20, wherein 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 comprises: When the update timestamp is later than the fifth update timestamp corresponding to the at least one target service stored locally, it is recorded that the target service has update data. The method according to claim 20, wherein 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 comprises: Downloading the update data of the target service from the first storage address when the first update timestamp is later than the fifth update timestamp corresponding to the at least one target service stored locally; The target service is updated according to the updated data of the target service. The method according to claim 16, wherein the target service includes a configuration center service, an offline package service, and a patch service. A data update method, which 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, where 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 gateway's update information request for the target application; The gateway receives the request sent by the target application, and returns the update information of the target application to the client in response data, where the request includes the application identifier of the target application; The client obtains the update information added by the gateway to the response data, and determines whether to update the target application according to the update information. The method according to claim 24, wherein the update information includes the first storage address of the update data on the content distribution server and the first update timestamp. The method according to claim 24, wherein 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 The service identification, storage address, and update timestamp of at least one target service of the target application; the update data includes update data of at least one target service of the target application. The method according to claim 26, wherein said obtaining update information of said update data on said content distribution server comprises: Acquiring, by the server, the first storage address and the 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; Uploading the index file to the content distribution server by the server; The server obtains the second storage address and the second update timestamp. The method according to claim 27, wherein the server updates the index file according to the first storage address and the first update timestamp, comprising: the server updates all of 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. The method according to claim 24, wherein the gateway receiving the request sent by the target application, and carrying the update information of the target application in response data and returning it to the client, comprises: Acquiring, 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; Determining, by the gateway, according to the application identifier, whether the update information of the target application is stored locally; 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. The method according to claim 24, further comprising: 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. The method according to claim 24, further comprising: 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. The method according to claim 31, wherein the client sending the request carrying the application identifier of the target application to the gateway comprises: The client intercepts the request sent by the target application to the server; The client carries the application identifier of the target application in the request and sends it to the gateway of the server. The method according to claim 25, wherein the client determines whether to update the target application according to the update information, comprising: a local third update of the target application when the first update timestamp is later than When the time stamp is used, the client records the update data of the target application. The method according to claim 25, wherein the client determining whether to update the target application according to the update information comprises: When the first update timestamp is later than the third local update timestamp of the target application, the client downloads the update data of the target application from the first storage address; The client terminal updates the target application according to the update data of the target application. The method according to claim 26, wherein the client determining whether to update the target application according to the update information comprises: 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; 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. The method according to claim 35, wherein 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, comprising: When the first update timestamp is later than the fifth update timestamp corresponding to the at least one target service stored locally, the client records that the target service has update data. The method according to claim 35, wherein 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 comprises: When the first time stamp is later than a fifth update time stamp corresponding to the at least one target service stored locally, the client downloads the update data of the target service from the first storage address; The client terminal updates the target service according to the update data of the target service. The method according to claim 26, wherein the target service includes a configuration center service, an offline package service, and a patch service. A data update system, which includes: a server, a gateway, and a client, in which, 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 gateway's update information request for the target application, send the update information to the content distribution server. The gateway returns the update information, where the update information includes information capable of obtaining the first storage address and the first update timestamp of the update data on the content distribution server; The gateway is configured to receive a request sent by the target application, and return the update information of the target application to the client in response data, 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, and obtain that the gateway is added to the response data According to the update information, determine whether to update the target application. The system according to claim 39, wherein the update information includes the first storage address of the update data on the content distribution server and the first update timestamp. The system according to claim 39, wherein 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 The service identification, storage address, and update timestamp of at least one target service of the target application; the update data includes update data of at least one target service of the target application. The system according to claim 41, wherein the server is configured to obtain a first storage address and a first update timestamp of the update data on the content distribution server, according to the first storage address and the first update time stamp. Update the timestamp to update the index file, upload the index file to the content distribution server, and obtain the second storage address and the second update timestamp. The system according to claim 42, wherein 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 first update timestamp. The system according to claim 39, wherein the gateway is configured to obtain the application identifier of the target application carried in the request, and when the application identifier is not stored in the local application list, the application The identifier is added to the local application list, and it is determined 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 all The response data is returned to the client. The system according to claim 39, wherein 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 information. The system according to claim 39, wherein 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 system according to claim 46, wherein the client is configured to intercept the request sent by the target application to the server, and carry the application identifier of the target application in the request to send The gateway to the server. The system according to claim 40, wherein the client is configured to record the update data of the target application when the first update timestamp is later than the third update timestamp of the target application locally. The system according to claim 40, wherein the client is configured to download from the first storage address when the first update timestamp is later than the third update timestamp of the target application locally. The update data of the target application updates the target application according to the update data of the target application. The system according to claim 40, wherein the client downloads the index file from the second storage address when the second update timestamp is later than the fourth update timestamp of the local index file, according to The first update timestamp corresponding to the service identifier of the at least one target service in the index file determines whether to update the target application. The system according to claim 50, wherein when the first update timestamp is later than the fifth update timestamp corresponding to the at least one target service stored locally, the client records that there is an update for the target service data. The system according to claim 50, wherein the client downloads from the first storage address when the first time stamp is later than the fifth update time stamp corresponding to the at least one target service stored locally The update data of the target business updates the target business according to the update data of the target business. The system according to claim 41, wherein the target service includes a configuration center service, an offline package service, and a patch service. A data update device, which includes: The upload module is configured to upload update data of the target application to the content distribution server; The 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 capable of obtaining the update data on the content distribution server and The information of the first update timestamp; The first return module is configured to return the update information in response to the update information request of the gateway for the target application. The apparatus according to claim 54, wherein the update information includes the first storage address of the update data on the content distribution server and the first update timestamp. The apparatus according to claim 54, wherein 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 The service identification, storage address, and update timestamp of at least one target service of the target application; the update data includes update data of at least one target service of the target application. The apparatus according to claim 56, wherein acquiring the update information of the update data on the content distribution server comprises: 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. The apparatus according to claim 57, wherein said updating said index file according to said first storage address and said first update timestamp comprises: changing said service of said target service in said index file Identify that the associated update address and the update timestamp are updated to the first storage address and the first update timestamp. The apparatus according to claim 56, wherein the target service includes a configuration center service, an offline package service, and a patch service. A data update device, which includes: The first receiving module is configured to receive a request sent by a target application, where 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 response data and return it to the client, where the update information includes the first update data on the content distribution server that can obtain the update data of the target application. Store the information of the address and the first update timestamp. The apparatus according to claim 60, wherein the update information includes the first storage address of the update data on the content distribution server and the first update timestamp. The apparatus according to claim 60, wherein 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 The service identification, storage address, and update timestamp of at least one target service of the target application; the update data includes update data of at least one target service of the target application. The apparatus according to claim 60, wherein said carrying the update information of the target application in response data and returning it to the client comprises: Determining whether 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. The device according to claim 60, further comprising: The second obtaining module is 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. The device according to claim 64, further comprising: The first sending module is configured to periodically send the 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. The device of claim 62, wherein: The target business includes configuration center business, offline package business and patch business. A data update device, which includes: The second sending module is configured to send a request carrying the application identifier of the target application to the gateway; The third receiving module is configured to receive response data returned by the gateway; The third obtaining module is configured to obtain the update information added by the gateway to the response data, where 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 is configured to determine whether to update the target application according to the update information. The apparatus according to claim 67, wherein the update information includes the first storage address of the update data on the content distribution server and the first update timestamp. The apparatus according to claim 67, wherein 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 The service identification, storage address, and update timestamp of at least one target service of the target application; the update data includes update data of at least one target service of the target application. The apparatus according to claim 67, wherein the sending the request carrying the application identifier of the target application to the gateway comprises: Intercept 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. The apparatus according to claim 68, wherein the determining whether to update the target application according to the update information and a third local update timestamp of the target application comprises: when the first update timestamp is later than When the target application has a third local update time stamp, it is recorded that the target application has update data. The apparatus according to claim 68, wherein the determining whether to update the target application according to the update information and a third local update timestamp of the target application comprises: When the first update timestamp is later than the third local update timestamp of the target application, download 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. The apparatus according to claim 69, wherein the determining whether to update the target application according to the update information and a third local update timestamp of the target application comprises: When the second update timestamp is later than the fourth update timestamp of the local index file, download the index file from the second storage address; Determine 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. The apparatus according to claim 73, wherein 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 comprises: When the update timestamp is later than the fifth update timestamp corresponding to the at least one target service stored locally, it is recorded that the target service has update data. The apparatus according to claim 73, wherein 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 comprises: Downloading the update data of the target service from the first storage address when the first update timestamp is later than the fifth update timestamp corresponding to the at least one target service stored locally; The target service is updated according to the updated data of the target service. The apparatus according to claim 69, wherein the target service includes a configuration center service, an offline package service, and a patch service. 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 executed by the processor to implement claim 1- 38 of the method steps described in any one of them. A readable storage medium having computer instructions stored thereon, wherein the computer instructions implement the method steps of any one of claims 1-38 when the computer instructions are executed by a processor.

Images