WO2012048617A1

WO2012048617A1 - Method and system for updating widget, widget client and widget server

Info

Publication number: WO2012048617A1
Application number: PCT/CN2011/080099
Authority: WO
Inventors: 张锐利
Original assignee: 中兴通讯股份有限公司
Priority date: 2010-10-15
Filing date: 2011-09-23
Publication date: 2012-04-19
Also published as: CN101977217A

Abstract

The invention relates to a method and system for updating Widget, a Widget client and a Widget server. The method comprises: the Widget client transmits an update request to the Widget server（201）; after receiving the update request, the Widget server extracts the application package of the current version of the Widget client and the application package of the latest version and compares the two application packages（202）; the Widget server constructs a response body and transmits the response body to the Widget client, wherein the response body comprises an update document constructed according to the comparison result and a preset update policy（203）; and the Widget client receives the response body and performs the update according to the update document（204）. The invention can realize part of updating and increase the updating efficiency.

Description

Widget update method, system, Widget client and Widget server

Technical field

The present invention relates to communication technologies, and in particular, to a Widget technology for a mobile terminal.

Background technique

Widget is a small web application developed using existing standard web technologies like regular web pages, including HTML (HyperText Mark-up Language), CSS (cading Style Sheet), cascading Style sheets, which are a set of formatting rules), JavaScript (a client-side scripting language), XML (Extensible Markup Language), and Ajax (Asynchronous JavaScript and XML, asynchronous JavaScript and XML). The most striking difference from a normal web page is that it does not rely on the browser display framework and is designed to have specific features such as stocks, weather forecasts, clocks, games, and more.

Due to its advantages of small size, light weight, complete functions, and diverse personalization, Widgets have been applied to the field of mobile terminals to enhance the user experience and provide cost-effective services. And the Widget app has another feature - updateability. Even if the Widget app has been released, it allows developers to continually refine the Widget application, fix bugs in previous versions, or add more features. Users can download the latest Widget app to get the latest and more reasonable experience.

When the Widget application is published, all local files of the application, such as javascript scripts or images, are compliant with the zip (a file format) standard, and are packaged and integrated using the deflate algorithm (a computer file compression algorithm) or a storage method. A zip file, usually suffixed with .wgt, as shown in Figure 1.

The Widget application zip package conforming to the Widget standard definition consists of three parts: a file data area, a file directory area, and a file directory end area. The file data area represents the file data in the compressed package. How many files and directories have the file data area? This is also the main part of the zi compression package, which contains the data of all files; each file data area corresponds to one file. Directory area, this part only records the directory name or file name, and the offset of the corresponding file data area starting position in the entire zip file; the file directory end area is the last part of the zip archive, contains the directory inside the compressed package File The number, and the size of the file directory area. According to the internal relationship of the zip format, when the file data area changes, the file directory area and the file directory end area also change, but the information content of the latter two areas is small, and the size of the entire zip package is very small, sometimes It may not be 1%. Taking Figure 1 as an example, the existing Widget application package named weekdays contains 4 file data areas, namely index.html, config.xmK scripts ^ scripts/ dayfinder js , and also contains 4 file directory areas and 1 file directory. End zone.

When only a few files in the Widget application package are modified, only the corresponding file data areas change, and most of the rest of the content has not changed. At this time, if the traditional Widget update method is used, the Widget application package data is all downloaded. This wastes network resources and even generates additional traffic charges, and excessive data interaction increases the risk of update failure. Summary of the invention

The technical problem to be solved by the present invention is to provide a Widget update method, system, Widget client and Widget server to improve update efficiency.

To solve the above technical problem, the present invention provides a method for updating a widget (Widget), the method comprising:

The Widget client sends an update request to the Widget server;

After receiving the update request, the Widget server extracts the current version of the Widget application package and the latest version of the Widget application package of the Widget client, and compares them;

The widget server constructs a response body and sends the response body to the Widget client, the response body including an update document constructed according to the comparison result and a preset update policy;

The widget client receives the response body and updates according to the update document. The update request sent by the Widget client carries the current Widget version number, and the Widget server obtains the current version Widget application package according to the current Widget version number.

The method further includes: updating the correspondence between the Widget client and the Widget version number when the Widget server sends the response body; the step of extracting the current version Widget application package of the Widget client includes: the Widget server according to the The mapping between the Widget client and the Widget version number obtains the current version Widget application package. The updating policy is: constructing the updated document according to the changed file and information; or determining whether the number and/or size of the changed file exceeds a preset threshold, and if so, using all files of the latest version as Update the document, if not exceeded, construct the updated document based on the changed files and information.

Each Widget application package includes a file data area, a file directory area, and a file directory end area; the steps of comparing the current version of the widget client's Widget application package with the latest version of the Widget application package include:

Parse the current version of the Widget application package and the latest version of the Widget application package;

The first data area sequence and the second data area sequence are respectively generated by using the current version Widget application package and the latest version Widget application package, and the content (Data) of each file data area in each data area sequence and the file/directory corresponding to the content The name (ID) is a node of the sequence of the data area;

Comparing each node of the second data region sequence with all nodes of the first data region sequence one by one, for one node in the second data region sequence: if there is the same in the first data region as the node ID but If the node is different, the node is marked as updated; if there is no node in the first data area that is the same as the node ID, the node is marked as new; for a node in the first data area : if there is no node with the same node ID in the second data area, the node is marked as deleted;

The update file includes updated file data area information, newly added file data area information, deleted file data area information, and a file directory area and a file directory end area of the latest version.

The updated file data area information includes an ID and a data, the added file data area information includes an ID, a location in a current version of the Widget application package, and Data, and the deleted file data area information includes an ID.

The response body further includes an update document type indication, configured to indicate that the update document is a total update document or a partial update document; and the updating according to the update document comprises: the Widget client determining, according to the updated document type indication Update the document type; when the update document is all updated documents, the Widget client will update the document to replace the current version of the Widget application package; when the update document is a partial update document, the Widget client performs the current version of the Widget application package according to the updated document. Partially updated. The step of the Widget client partially updating the current version Widget application package according to the update document includes:

Parsing the updated document, extracting the Data and the ID corresponding to the Data, and classifying and representing the management by updating, deleting, and adding a mark, and extracting the file directory area and the file directory end area at the same time.

Parsing the current version of the Widget application package, identifying each file data area in sequence, and the ID corresponding to the data area, forming a compressed packet data area management sequence (OrigSeq);

Deleting the file data area marked as deleted in the update document from the OrigSeq sequence; replacing the updated file data area in the updated document with the file data area in the OrigSeq sequence; marking the updated document Inserting the newly added file data area into the OrigSeq sequence according to the specified location; replacing the file directory area and the file directory end area extracted from the updated document with the file directory area and the file directory end area of the OrigSeq sequence to form a new version Compressed packet data area management sequence (NewSeq).

To solve the above technical problem, the present invention further provides a Widget server, the Widget server comprising:

a network interaction unit, configured to: receive an update request sent by the Widget client, and send a response body to the Widget client, where the response body includes an update document;

a Widget application package database, which is configured to store each version of the Widget application package;

a version comparison unit configured to compare a current version of the Widget client package with a latest version of the Widget application package;

The response body construction unit is configured to construct the update document and construct the response body according to the comparison result of the version comparison unit and the preset update policy.

To solve the above technical problem, the present invention further provides a Widget client, where the Widget client includes:

a network interaction unit, configured to: send an update request to the Widget server, and receive a response body sent by the Widget server, where the response body includes an update document, where the update document is the Widget server according to the current current of the Widget client The version of the Widget application package is compared with the latest version of the Widget application package and the update strategy is constructed;

A widget update unit configured to complete the widget update based on the updated document. In the technology of the present invention, the Widget server generates an update document according to the comparison result between the current version application package and the latest version application package, and the Widget client performs the Widget update according to the update document, thereby implementing partial update of the Widget and effectively improving the update efficiency. BRIEF abstract

Figure 1 is the zip package format of the Widget application;

2 is a schematic diagram of a method for updating a Widget of the present invention;

3 is a flowchart of implementing an update of a Widget server according to an embodiment of the present invention;

4 is a flowchart of a Widget client completing an update according to an embodiment of the present invention;

5 is a flowchart of a method for judging content comparison content of a Widget server according to the present invention;

6 is a schematic diagram of a Widget update system of the present invention;

7 is a block diagram showing a module structure of a version comparison unit of a Widget server;

8 is a block diagram showing a module structure of a Widget update unit of a Widget client;

Figure 9 is a block diagram showing the structure of a partial update module. Preferred embodiment of the invention

In the technology of the present invention, the Widget server generates an update document according to the comparison result between the current version application package and the latest version application package, and the Widget client performs Widget update according to the update document, thereby implementing partial update of the Widget.

As shown in FIG. 2, the Widget update method of the present invention includes:

Step 201: The Widget client sends an update request to the Widget server. Step 202: After receiving the update request, the Widget server extracts the current version application package of the Widget client and the latest version application package, and compares ;

The Widget server includes but is not limited to the following two ways to obtain the current version of the Widget client application package:

Manner 1: The update request sent by the Widget client carries the current version number of the Widget, and the Widget server obtains the current version application package according to the current version number of the Widget. If the Widget server can provide multiple Widget application packages, the update request should also carry the corresponding Widget ID or name to uniquely identify a Widget application package along with the version number.

Manner 2: When the Widget server sends the response body, the corresponding relationship between the Widget client and the Widget version number is updated, and when the Widget server receives the update request, the Widget server obtains the update request according to the widget client and its corresponding relationship. The current version of the application package.

The Widget application package includes a file data area, a file directory area, and a file directory end area, and comparing the current version application package of the Widget client with the latest version application package includes:

Al. Parsing the current version of the application package and the latest version of the application package;

Bl. respectively generate a data area sequence for the current version and the latest version, wherein each file data area content (Data) and its corresponding file/directory name (ID) are used as a node of the data area sequence; cl. will be the latest version Each node is compared with each node of the current version one by one. If the latest version of a node is the same as the current version of a node ID and Data is different, the latest version of the node is marked as an update, if the latest version of a node is If there is no corresponding ID in the current version, the node of the latest version is marked as new. If a node of the current version does not have a corresponding ID in the latest version, the node of the current version is marked as deleted.

Step 203: The Widget server constructs a response body and sends the response body to the Widget client, where the response body includes an update document constructed according to the comparison result and a preset update policy.

Specific update policies can be flexibly set, including but not limited to the following strategies:

Strategy 1: constructing the updated document according to the changed file and information;

Strategy 2: Determine whether the number and/or size of the changed files exceeds a preset threshold. If it exceeds, all the files of the latest version are used as the updated document. If not, the update is constructed according to the changed files and information. Documentation. Preferably, the second strategy is employed.

In the present invention, an updated document constructed based on a changed file and information is also referred to as a partial update document, and an updated document constructed based on the latest version of all files is referred to as a full update document.

Step 204: The Widget client receives the response body and updates according to the update document.

The (partial) update document includes updated file data area information, and a new file data area. Information, deleted file data area information, and the latest version of the file directory area and file directory end area, specifically:

The updated file data area information includes a file/directory name and a file data area content, where the newly added file data area information includes a file/directory name, a location in a current version application package, and a file data area content, The deleted file data area information includes the file/directory name.

If the update policy uses the policy 2, the response body further includes an update document type indication, configured to indicate that the update document is a full update document or a partial update document; and the Widget client 4 determines according to the updated document type indication. Update the document type; when the update document is all updated documents, the Widget client will update the document to replace the current Widget application package; when the update document is a partial update document, the Widget client partially updates the current Widget application package according to the updated document. .

If the update document is constructed according to the changed file and information, the update of the Widget client according to the update document includes:

A2. Parse the updated document, extract the Data and the corresponding ID, and classify and represent the management according to the update, delete, and new tags, and extract the file directory area and the file directory end area content.

B2. Parsing the current version of the application package, identifying each Data and its corresponding ID in order, forming a compressed packet data area management sequence (OrigSeq);

C2. deleting the file data area marked as deleted in the update document from the OrigSeq sequence; replacing the file data area marked as updated in the update document with the corresponding file data area in the OrigSeq sequence; The newly added file data area is inserted into the OrigSeq sequence according to the specified position; the new version of the file directory area and the file directory end area are replaced with the corresponding areas of the OrigSeq sequence to form a new version of the compressed package data area management sequence (NewSeq). .

Embodiment 1

The Widget update method of the present invention includes:

A. The Widget client sends an update network request carrying the current Widget application version number (VI) and the Widget application URI (Uniform Resource Identifier) to the corresponding Widget server; B. After receiving the network request, the Widget server performs policy judgment—taking the VI version of the Widget application package from the local server and comparing it with the latest version of the Widget application package;

C. The Widget server constructs and returns a response body;

If there are more files in the new version of the Widget application package (such as exceeding the set threshold), or if the total size of the changed file is larger than the Widget application package (such as exceeding the set threshold), then directly The version of the Widget application package is returned to the Widget client as a response body of the A step;

If only a few files have been changed and the size ratio is small, the server constructs a partial update document containing updated file data area information, new file data area information, deleted file data area information, and file directory area. , the end of the file directory. Return the document as a response body of step A to the Widget client;

D. After the Widget client receives the response body of the server, it completes the update.

If the response body is a Widget application package, the Widget client receives all of them, replacing the old Widget application package;

If the response body is partially updated in the document format, the Widget client parses the file data area information in the read document, replaces the corresponding file data area in the current version, or deletes the specified data area, or inserts the newly added file data area to Specify the location. Finally, replace the corresponding part of the current version with the file directory area and the file end area in the document to complete the update process of the Widget application package.

Embodiment 2

According to the Widget server, the Widget update method includes: after receiving the update request sent by the Widget client, the Widget server extracts the current version application package of the Widget client and the latest version application package, and compares the same; The Widget server constructs a response body and sends the response body to the Widget client, and the response body includes an update document constructed according to the comparison result and a preset update policy.

The update policy may be the foregoing policy one or the second one. Preferably, the embodiment uses the second strategy. The processing flow of the Widget server of the present invention will be described in more detail below with reference to the accompanying drawings and embodiments. The number of changed files is proportional to the width T1 and the size ratio is wide. The value T2 is 60% and 70%, respectively.

As shown in FIG. 3, the method for implementing update of the Widget server includes:

301. The Widget server receives the update request sent by the Widget client, and parses out the Widget application name and the current application version number;

302. The Widget server reads the Widget application package with the specified version number and name from the database storing the Widget application, and the latest version of the Widget application package;

303. The Widget server parses the current version of the Widget application package and the latest version of the Widget application package according to the zi compression file standard, and constructs a node for each file data area content (data) and corresponding file name or directory name information (id) in order. Adding to the sequence structure, generating two data area sequences, the data area sequence of the current version application package is Seql, and the data area sequence of the latest version application package is Seq2;

304. The Widget server reads each node of Seq2 in order, according to the content comparison decision algorithm (refer to FIG. 5), and compares with the nodes in the Seql sequence, if there is a data area with the same file name or directory name (ie, the same id), Then, it is determined whether the content data of the data area is the same. If the content is different, it indicates that the data area is updated, and the node of Seq2 is marked as updated; if there is no data area with the same id, the data area is added, and Seq2 is added. The node is marked as new; when traversing the node in Seql and finding that the id of a node does not match the node id in Seq2, the node in Seql is marked as deleted.

305. The Widget server performs an update policy judgment. Traversing the Seq2 sequence to obtain the number and total size of the data area to be updated and added. If the number of data areas that have changed is too large, it exceeds T1, or the total size accounts for a larger proportion of the entire Widget application package, exceeding T2. Then it is not suitable for partial update, execute all update policies, go to step 306', if the number of changed data areas and the total size are smaller than the corresponding threshold, execute the partial update policy, and go to step 306;

306. The Widget Server Configuration section updates the documentation. Take the XML markup language as an example. The document should contain updated file data area information, new file data area information, deleted file data area information, and a new version of the file directory area and file directory end area.

For each updated file data area, it is represented by an <updateEntry></updateEntry> element. At least the following attributes are included: ID indicates the file/directory name corresponding to the data area, and length indicates the The size of the data area. The content between the open tag < updateEntry > and the closed tag </ updateEntry > is the updated file data area, and its length is consistent with the value of the length attribute, and can be 0.

For each deleted file data area, it is represented by a <(161£1^1></(161£1^1> element. At least the following attributes are included: ID indicates the file/directory name corresponding to the data area.

For each new file data area, it is represented by a <newEntry></newEntry> element. It includes at least the following attributes: ID indicates the file name or directory name corresponding to the data area, position indicates the position where the data area should be inserted, and length indicates the size of the data area. The content between the open tag <newEntry> and the closed tag </newEntry> is a new file data area whose length is consistent with the length attribute value and can be 0.

For the file directory area and the file directory end area, represented by 11 (1£1^1 >< 11 (1£1^1> elements, at least the following attributes: length indicates the size of the data area. Open label < endEntry > and The content between the closed tags </ endEntry > is the new version of the file directory area and the file directory end area body, and its length is consistent with the length attribute value.

Thus, a partial update document represented by an XML structure is constructed. Take Figure 1 as an example, if the partial update document is of the form:

<updateEntry ID="config.xml" length="400">config.xml body data </updateEntry>

<updateEntry ID="index.html" length="1200"> index.html body data </updateEntry>

<newEntry ID="sciripts/daySearch.js" position="3" length="600"> number of daysSearch.js text </ηε νΕη1τγ>

</updateDescription >

It means that there are two file data areas to be updated, a deleted file data area, and a new file data area, which should be inserted after the third file data area. 306'. The Widget server performs a full update policy. The server reads the latest version of the Widget application package from the database storing the Widget application and uses it as an update document.

307. The Widget server constructs a response body of the Widget client update request, which is encapsulated according to a specific application layer protocol. If it is a partial update, the partial update document is used as a response body text, and the corresponding MIME (Multipurpose Internet Mail Extensions) is indicated. Web mail extension) type, for XML documents, the MIME type is application/xml, which means the application of XML type. If it is all updates, the latest version of the Widget application package is directly used as the body of the update request response body, and the MIME type is specified. Application/Widget, which means the application of the Widget type;

308. The Widget server sends the encapsulated response body to the Widget client through the network to complete the update process on the Widget server side.

Embodiment 3

The method for updating the Widget of the present invention includes: a Widget client sends an update request to the Widget server; the Widget client receives a response body sent by the Widget server, and the response body includes an update document. The update document is constructed by the Widget server according to a comparison result and an update policy of a current version application package of the Widget client and a latest version application package; and the Widget client updates according to the update document.

The processing flow of the Widget client of the present invention will be described in more detail below with reference to the accompanying drawings and embodiments. As shown in FIG. 4, the process of updating the Widget client in the embodiment includes:

401. The Widget client receives the response body of the Widget server to the update request, and parses the MIME type and the body data;

402. Update type judgment;

The judgment is based on the MIME type. If the MIME type is application/Widget, it means that all updates, the body data is the new version of the Widget application package, and directly replaces the current version of the Widget application package, and executes 409'; if the MIME type is application/xml, It means that the partial update, the body data is a partial update document, and the execution continues to 403.

403. Parse the partial update document. Parsing the updated document, extracting the Data and the corresponding ID, and classifying and representing the management according to the update, delete, and newly added tags, and extracting the file directory area and the file directory end area content: constructing an update data area node sequence (updateSeq) ), for each <updateEntry> to generate a node, with the ID attribute value as the node identifier, and save the data area content of the element; construct a delete data area node sequence (delSeq), construct a node for each <delEntry>, The ID attribute value is used as the node identifier. Construct a new data area node sequence (newSeq), construct a node for each <newSeq>, use the ID attribute value as the node identifier, and save the position attribute value and the data area content; finally, 11 (1£1) in the document The ^1> element content (file directory area and file directory end area) is saved to the buffer (bufferl).

404. Parsing the current version of the Widget application package;

Identifying the contents of each file data area and its corresponding file/directory name in sequence, forming a compressed packet data area management sequence (OrigSeq), specifically, following the zip format standard, extracting the contents of each file data area to form a node The file name or directory name represented by the data area is used as a node identifier to form a file data area sequence (OrigSeq), and the last node of the sequence saves the file directory area and the file directory end area content.

Deleting the file data area marked as deleted in the update document from the OrigSeq sequence; replacing the file data area marked as updated in the update document with the corresponding file data area in the OrigSeq sequence; marking the update document as The newly added file data area is inserted into the OrigSeq sequence according to the specified position; the new version of the file directory area and the file directory end area are replaced with the corresponding areas of the OrigSeq sequence to form a new version of the compressed package data area management sequence (NewSeq). That is, the following steps 405 to 408 are performed;

405. Traversing the deleted data area node sequence delSeq to complete the deletion operation;

The corresponding node is found in the current Widget application file data area sequence OrigSeq according to the ID identification value of each node, and the node is deleted;

406. Traverse the update data area node sequence updateSeq to complete the content update operation of the corresponding node;

Specifically, according to the ID identifier value of each node (Node2), the corresponding node (Node1) is found in the OrigSeq sequence, and the file data area content of the Node2 node is replaced with the Node1 node. Data area.

407. Traverse the newly added data area node sequence newSeq to complete the new operation;

Constructs a new node based on the ID of the node and the contents of the data area, inserted after the node in the OrigSeq sequence at the position pointed to by the position attribute.

408. Replace the new version of the file directory area and the file directory end area content (buffer) with

The data area of the last node of OrigSeq;

This completes the update. If delSeq or newSeq or updateSeq is empty, the steps corresponding to these sequences are not performed.

409. At this point, OrigSeq is already a sequence that stores the updated data area, writing the contents of each node's data area to a local temporary file.

409'. Perform all updates to save the body of the response directly to the local temporary file;

410. Delete the current version of the Widget application package, change the temporary file name to the same name Widget application, and complete the update of the Widget application.

Figure 5 is a flow chart of the algorithm for comparing the content of the Widget server:

501. The node is taken from the N2 position of the new version data area sequence Seq2, and the initial value of N2 is 0.

502. If the N2 node is empty, indicating that the Seq2 sequence has been traversed, and if the N2 node is not empty, the N2 node is compared with the nodes of the Seq1 sequence one by one, and step 503 is performed;

503. Traverse the Seql sequence from the N1 position (the initial value of N1 is 0) until the node with the same ID identifier is found, or the Seql traversal ends;

504. If the IDs of the N1 node and the N2 node are the same, that is, the file data area of the same file name or directory name, step 506 is performed to determine the content of the data area. If the ID is not found in Seql, Execute 505;

505. There is no node in Seql that is consistent with the N2 node ID, indicating that the N2 node is a new node, then N2 is marked as "new" and points to the next node of Seq2, repeating 501;

506. Mark the N1 node as "not deleted" in Seql, indicating that the N1 node is in Seq2 There is a corresponding node, and it is determined whether the contents of the file data area of the N1 node and the N2 node are the same. If they are the same, step 508 is performed. If not, step 507 is performed;

507. Indicates that the N1 node content of Seql has been updated, and the N2 node is marked as "update" in Seq2;

508. The node comparison with the ID is completed, pointing to the next node of Seq2, pointing to the N1 node of Seql, continuing the node comparison, and repeating step 501 until the Seq2 traversal ends.

At the end of the Seq2 traversal, nodes in Seql that are not marked as "not deleted" are marked as "deleted", ie, those nodes marked as "delete" do not find the ID-instance node in Seq2.

To implement the above method, the present invention further provides a Widget update system. As shown in FIG. 6, the system includes a Widget client and a Widget server, and the Widget client includes:

a network interaction unit, configured to: send an update request to the Widget server, and receive the Widget server to send to the response body, where the response body includes an update document;

The update request sent by the Widget client carries the current version number of the Widget, and the version comparison unit of the Widget server obtains the current version of the application package according to the current version number of the Widget.

The widget update unit is configured to complete a widget update according to the update document; the widget server includes:

a network interaction unit configured to receive the update request and send the response body to the Widget client;

a version comparison unit configured to compare a current version application package of the Widget client with a latest version application package;

The response body construction unit is configured to construct the update document based on the comparison result and the preset update policy, and construct the response body.

The update strategy is:

Constructing the updated document based on the changed file and information; or, It is judged whether the number and/or size of the changed files exceeds a preset threshold. If it is exceeded, all the files of the latest version are taken as the updated document, and if not, the updated document is constructed according to the changed files and information.

The Widget application package includes a file data area, a file directory area, and a file directory end area. Specifically, as shown in FIG. 7, the version comparison unit of the Widget server includes:

a Widget package content extraction module, configured to generate a data area sequence respectively for the current version and the latest version, wherein the content (Data) of each file data area in each data area sequence and the corresponding file/directory name (ID) a node for the sequence of data regions;

a version comparison module, configured to compare each node of the latest version with each node of the current version one by one, if the node of the latest version is different from the node ID of the current version, the latest version of the node is marked For the update, if the latest version of a node does not have a corresponding ID in the current version, the node of the latest version is marked as new. If a node of the current version does not have a corresponding ID in the latest version, the current The node of the version is marked for deletion;

The (partial) update document constructed by the response body construction unit includes updated file data area information, newly added file data area information, deleted file data area information, and a latest version file directory area and file directory end area.

The updated file data area information includes a file/directory name and a file data area content, and the newly added file data area information includes a file/directory name, a location in the compressed package, and a file data area content, and the deleted content. The file data area information includes the file/directory name.

Further, the response body further includes an update document type indication, which is used to indicate that the update document is a total update document or a partial update document. As shown in FIG. 8, the Widget update unit includes an update determination module, all update modules, and a portion. Update module

The update judging module is configured to judge the update document type according to the update document type indication; the update module is configured to replace the update file with the current Widget application package when the update document is all updated documents;

The partial update module is configured to partially update the current Widget application package according to the update document when the update document is a partial update document. Further, as shown in FIG. 9, the partial update module includes:

The document analysis sub-module is updated, and is configured to: parse the update document, extract the Data and the corresponding ID, and classify and represent the management according to the update, delete, and new tags, and extract the file directory area and the file directory end area content. ;

The Widget package content extraction sub-module is configured to: parse the current version application package, identify each file data area content in sequence, and the file/directory name identifier corresponding to the content, and form a compressed package data area management sequence (OrigSeq); as well as

a Widget package content update submodule, configured to delete a file data area marked as deleted in the update document from the OrigSeq sequence; replacing the updated file data area in the OrigSeq sequence with the file data area marked as updated in the update document Inserting the file data area marked as new in the update document into the OrigSeq sequence according to the specified location; replacing the new version of the file directory area and the file directory end area with the corresponding area of the OrigSeq sequence to form a new version of the compressed package Data Area Management Sequence (NewSeq).

The present invention further provides a Widget server, the Widget server includes: a network interaction unit, configured to: receive an update request sent by a Widget client, and send a response body to the Widget client, where the response body includes an update Document

The updating policy is: constructing the updated document according to the changed file and information; or, determining whether the number and/or size of the changed file exceeds a preset threshold, and if so, using all files of the latest version as Update the document, otherwise construct according to the changed file and information The update document. For example, if the quantity and size are each smaller than a certain threshold, the partial update; if there is too much file data area to be updated, or the changed file data area size is large, all are updated.

Further, the Widget application package includes a file data area, a file directory area, and a file directory end area, and the version comparison unit of the Widget server traverses the sequence of the two versions of the data area, compares the changes of the data area, and records the updated file. The number and size of the data area, used for update mode decision making. Specifically, if the content of the corresponding file data area (ie, the data area representing the same file or directory) is updated, the data area of the file is marked and the size is recorded; if there is a new file data area , then mark the data area and record its size. The result is the number of file data areas where the content has changed, as well as the total size.

Specifically, the version comparison unit of the Widget server includes:

The Widget package content extraction module is configured to: generate a data area sequence by using the current version Widget application package and the latest version Widget application package, wherein each file data area content (Data) and the file/directory name (ID) corresponding to the content ) as a node of the sequence of data regions;

a version comparison module, configured to: compare each node of the latest version with each node of the current version one by one, if the latest version of one node is the same as the current version of one node ID, Data is different, then the latest version of the node The node is marked as updated. If the latest version of a node does not have a corresponding ID in the current version, the node of the latest version is marked as new. If the current version of a node does not have a corresponding ID in the latest version, the current The node of the version is marked for deletion;

The (partial) update document constructed by the response body construction unit includes updated file data area information, newly added file data area information, deleted file data area information, and a latest version file directory area and file directory end area. Partially updated documents can use XML or other contracted markup languages.

The updated file data area information includes a file/directory name and a file data area content, where the newly added file data area information includes a file/directory name, a location in the current version application package, and a file data area content, The deleted file data area information includes the file/directory name.

In addition, the present invention further provides a Widget client, where the Widget client includes:

a network interaction unit, configured to: send an update request to the Widget server, and receive the location a response body sent by the Widget server, where the response body includes an update file, where the update document is constructed by the Widget server according to a comparison result and an update policy of a current version application package of the Widget client and a latest version application package;

A widget update unit configured to complete the widget update based on the updated document.

The (partial) update document includes updated file data area information, newly added file data area information, deleted file data area information, and a latest version file directory area and a file directory end area, and the updated file data area information includes File/directory name and file data area content, the newly added file data area information includes file/directory name, location in the current version application package, and file data area content, deleted file data area information including file/ Directory name.

Further, the response body further includes an update document type indication, configured to indicate that the update document is a total update document or a partial update document; and the widget update unit includes:

An update judging module configured to determine an update document type according to an update document type indication; a full update module, configured to: replace the current Widget application package with the update document when the update document is all updated documents;

A partial update module, which is configured to: when the updated document is a partial update document, partially update the current widget application package according to the updated document.

The partial update module includes an update document analysis submodule, a widget package content extraction submodule, and a widget package content update submodule, wherein

The update document analysis sub-module is configured to: parse the update document, extract the Data and the corresponding ID, and classify and represent the management according to the update, delete, and new mark, and extract the file directory area and the file directory end area content;

The Widget package content extraction sub-module is configured to: parse the current version of the application package, identify each file data area content in sequence, and corresponding file/directory name identifiers, and form a compressed package data area management sequence (OrigSeq);

The Widget package content update submodule is configured to: delete the file data area marked as deleted in the update document from the OrigSeq sequence; replace the file data area marked as updated in the update document with the corresponding file data area in the OrigSeq sequence; The file data area marked as newly added in the update document is inserted into the OrigSeq sequence according to the specified position; the new version of the file directory area and the file directory end area are replaced with corresponding areas of the OrigSeq sequence to form a new version of the compressed package data area. Management Sequence (NewSeq)

One of ordinary skill in the art will appreciate that all or a portion of the above steps may be accomplished by a program instructing the associated hardware, such as a read-only memory, a magnetic disk, or an optical disk. Alternatively, all or part of the steps of the above embodiments may also be implemented using one or more integrated circuits. Correspondingly, each module/unit in the above embodiment may be implemented in the form of hardware or in the form of a software function module. The invention is not limited to any specific form of combination of hardware and software.

The method, system and device of the present invention compare the current version of the Widget client with the latest version of the application package, and generate a targeted update document according to the comparison result and the preset update policy, and then the Widget client performs the Widget update according to the update document. , can effectively provide update efficiency, especially when the number or size of changed files is less, the wireless network resources can be utilized more effectively, the network interaction time of the Widget application update is reduced, and the possible network abnormality is caused to cause the update failure. risks of.

Industrial Applicability Compared with the prior art, in the present invention, the Widget server generates an update document according to the comparison result between the current version application package and the latest version application package, and the Widget client performs Widget update according to the update document, thereby implementing the Widget part. Update and effectively improve update efficiency.

Claims

Claim

1. A method for updating a widget (widget), including:

The Widget client sends an update request to the Widget server;

The widget client receives the response body and updates according to the update document.

The method of claim 1, wherein the update request sent by the Widget client carries a current Widget version number, and the Widget server obtains the current version Widget application package according to the current Widget version number.

The method of claim 1, further comprising: updating the correspondence between the Widget client and the Widget version number when the Widget server sends the response body; extracting a current version Widget application package of the Widget client The step of the method includes: obtaining, by the Widget server, the current version of the Widget application package according to the correspondence between the Widget client and the Widget version number.

4. The method of claim 1, wherein the update policy is:

Constructing the updated document according to the changed file and information; or

It is judged whether the number and/or size of the changed file exceeds the preset threshold. If it is exceeded, all the files of the latest version are used as the update document, and if not, the updated document is constructed according to the changed file and information.

5. The method of claim 1, wherein each Widget application package includes a file data area, a file directory area, and a file directory end area; and the current version of the Widget client Widget application package is compared with the latest version of the Widget application package. The steps to compare include: Parsing the current version of the Widget application package and the latest version of the Widget application package;

The method of claim 5, wherein the updated file data area information comprises an ID and a data, and the added file data area information comprises an ID, a location in a current version of the Widget application package, and a data. The deleted file data area information includes an ID.

The method of claim 1, wherein the response body further comprises an update document type indication, configured to indicate that the update document is a total update document or a partial update document; and the updating according to the update document comprises: The Widget client determines to update the document type according to the updated document type indication; when the update document is all updated documents, the Widget client replaces the current version of the Widget application package; when the updated document is a partial update document, The Widget client partially updates the current version of the Widget application package according to the update document.

8. The method of claim 7, wherein the step of the Widget client partially updating the current version of the Widget application package according to the updated document comprises:

Parsing the updated document, extracting the ID corresponding to the Data and the Data, and classifying and representing the management according to the update, delete, and newly added tags, and extracting the file directory area and the file directory end area; parsing the current version of the Widget application package, and pressing Identify each Data sequentially, and corresponding to the Data ID, forming a compressed packet data area management sequence (OrigSeq);

Deleting the file data area marked as deleted in the update document from the OrigSeq sequence; replacing the updated file data area in the updated document with the file data area in the OrigSeq sequence; marking the updated document Inserting the newly added file data area into the OrigSeq sequence according to the specified location; replacing the file directory area and the file directory end area extracted from the updated document with the file directory area and the file directory end area of the OrigSeq sequence, respectively, to form a new Version of the compressed package data area management sequence (NewSeq).

9. A Widget server, including:

10. The server according to claim 9, wherein the update policy is:

Constructing the updated document based on the changed files and information; or

The server according to claim 9, wherein each Widget application package includes a file data area, a file directory area, and a file directory end area, and the version comparison unit includes:

a Widget package content extraction module configured to generate a first data region sequence and a second data region sequence respectively, using a current version Widget application package and a latest version Widget application package, wherein each of the data region sequences has a content of each file data region ( Data) and the file/directory name (ID) corresponding to the content constitute a node of the sequence of the data area;

a version comparison module, configured to: each node of the second data sequence and the first data sequence All nodes are compared one by one, for one node in the second data zone sequence: if there is a node in the first data zone that is the same as the node ID but different in Data, the node is marked as updated; If there is no node in the data area that is the same as the node ID, the node is marked as new; for one node in the first data area: if there is no same in the second data area as the node ID Node, then mark the node as deleted;

The file data area information, the deleted file data area information, and the latest version of the file directory area and the file directory end area.

12. A Widget client, including:

The Widget client according to claim 12, wherein the response body further includes an update document type indication, which is used to indicate that the update document is a total update document or a partial update document; the widget update unit includes:

An update judging module, configured to determine an update document type according to an update document type indication; a total update module, configured to replace the current version Widget application package with the update document when the update document is all updated documents;

And a partial update module, configured to perform a partial update of the current version of the Widget application package according to the update document when the update document is a partial update document.

14. The Widget client of claim 13, wherein the partial update module comprises:

Updating a document analysis sub-module, configured to: parse the update document, extract a file data area content (Data) in the update document, and a file/directory name (ID) corresponding to the content, and press update, delete, new Add tags to classify the management, and extract the new version of the file directory area and text End of directory

The Widget package content extraction sub-module is configured to: parse the current version of the Widget application package, identify each Data in sequence, and the ID corresponding to the Data, and form a compressed packet data area management sequence (OrigSeq);

a Widget package content update submodule, configured to: delete a file data area marked as deleted in the update document from the OrigSeq sequence; replace the updated file data area in the OrigSeq sequence with the file data area marked as updated in the update document Inserting the file data area marked as new in the update document into the OrigSeq sequence according to the specified location; replacing the file directory area and the file directory end area of the new version with the file directory area and the file directory end area in the OrigSeq sequence , form a new version of the compressed packet data area management sequence (NewSeq).

A Widget update system, comprising the Widget server according to any one of claims 9 to 11 and the Widget client according to any one of claims 12 to 14.