CA3176456A1 - Release upgrading method applicable to hybrid application, corresponding device and intelligent equipment - Google Patents
Release upgrading method applicable to hybrid application, corresponding device and intelligent equipmentInfo
- Publication number
- CA3176456A1 CA3176456A1 CA3176456A CA3176456A CA3176456A1 CA 3176456 A1 CA3176456 A1 CA 3176456A1 CA 3176456 A CA3176456 A CA 3176456A CA 3176456 A CA3176456 A CA 3176456A CA 3176456 A1 CA3176456 A1 CA 3176456A1
- Authority
- CA
- Canada
- Prior art keywords
- web
- version
- data
- shell
- application
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 37
- 230000003993 interaction Effects 0.000 claims abstract description 10
- 238000007726 management method Methods 0.000 description 64
- 230000000694 effects Effects 0.000 description 11
- 238000005516 engineering process Methods 0.000 description 10
- 238000011161 development Methods 0.000 description 8
- 230000008569 process Effects 0.000 description 8
- 230000006870 function Effects 0.000 description 7
- 238000012827 research and development Methods 0.000 description 6
- 230000003044 adaptive effect Effects 0.000 description 3
- 230000008901 benefit Effects 0.000 description 3
- 238000009434 installation Methods 0.000 description 3
- 230000002452 interceptive effect Effects 0.000 description 3
- 238000012423 maintenance Methods 0.000 description 3
- 230000008878 coupling Effects 0.000 description 2
- 238000010168 coupling process Methods 0.000 description 2
- 238000005859 coupling reaction Methods 0.000 description 2
- 230000002123 temporal effect Effects 0.000 description 2
- 230000008859 change Effects 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000009877 rendering Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters
Abstract
Disclosed are a method and apparatus applicable to release and upgrade of a hybrid application, and an intelligent device, which relate to the technical field of mobile applications and aim to solve the problem, in the prior art, of consumption of time and workload or a non-user-friendly experience due to the fact that when a hybrid mobile application is released and updated, in order to guarantee a dependency relationship between a Web shell and a Web application, a successive release period needs to be agreed upon so as to guarantee the version consistency. The method comprises: submitting Web shell data and/or Web application data to a version management system and preparing for releasing the data; acquiring, from the version management system, Web application data with a corresponding version number and associatively matching same with the newly submitted Web shell data, and generating Web shell update data; and/or acquiring, from the version management system, Web shell data with a corresponding version number and associatively matching same with the newly submitted Web application data, and generating Web application update data; and when a hybrid application is started, automatically detecting the current Web shell version and an embedded Web application version, and simultaneously accessing the version management system to request for interaction and update.
Description
RELEASE UPGRADING METHOD APPLICABLE TO HYBRID APPLICATION, CORRESPONDING DEVICE AND INTELLIGENT EQUIPMENT
BACKGROUND OF THE INVENTION
Technical Field [0001] The present invention relates to the field of mobile application technology, and more particularly to a release upgrading method applicable to a hybrid application, and corresponding device and intelligent equipment.
Description of Related Art
BACKGROUND OF THE INVENTION
Technical Field [0001] The present invention relates to the field of mobile application technology, and more particularly to a release upgrading method applicable to a hybrid application, and corresponding device and intelligent equipment.
Description of Related Art
[0002] A hybrid mobile application (Hybrid App) is an app between a web application (web-app) and a native application (native-app), the Hybrid App is developed and produced by means of the programming language and the web language together, of which the programming language (Native) is the footstone of client end applications, and the corresponding development language should be selected during development of the application according to the operating system borne on the terminal, for instance, the java language is required to be used for the development of the Android operating system, the Objective-C language is required to be used for the development of the iOS
operating system, the client end application developed and compiled by the programming language should be installed on the terminal for running, the server end application developed and compiled by the web language (Html) is deployed for use in the server end, it is not required to differentiate the operating systems of the terminals, as the crossing-platforms characteristics are possessed, accordingly, the hybrid mobile application possesses both "the advantage of excellent user interactive experiences of the Native App"
and "the advantage of the crossing-platforms development of the Web App".
Date Regue/Date Received 2022-09-22
operating system, the client end application developed and compiled by the programming language should be installed on the terminal for running, the server end application developed and compiled by the web language (Html) is deployed for use in the server end, it is not required to differentiate the operating systems of the terminals, as the crossing-platforms characteristics are possessed, accordingly, the hybrid mobile application possesses both "the advantage of excellent user interactive experiences of the Native App"
and "the advantage of the crossing-platforms development of the Web App".
Date Regue/Date Received 2022-09-22
[0003] Since the hybrid mobile application (shortened as a client end application) possesses the function of a browser, it is therefore possible to load the Web application to realize access through a native Web control, and invoking of such native functions as network requests, data storage, location positioning, and photographing, etc., is supported at the same time, the native Web control uses API of the operating system to create a rendering engine of the embedded webpage, with the main functions to define an interface between the program and the webpage, to allow the webpage to invoke the program, to supply the Web-based application program API, and to embed the Web into the program; this is like the case in which the client end application is a shell, and the Web application is the content inside the shell, therefore, it can be agreed upon that the client end application is referred to as a Web shell, and the content loaded by the Web shell is the Web application, for instance, as regards a Suning sub-module in the Suning Finance App, the Suning sub-module is a separate Web application, while the Suning Finance App is precisely the Web shell.
[0004] Different from the native application for which it is merely required to maintain itself, the constitution of the hybrid mobile application decides that maintenance of the application program should be divided into two parts, namely the Web shell and the Web application, a relation of strong interdependency exists between the two, from the aspect of update and upgrade, the Web shell and the Web application should be independently released;
from the aspect of the relation of strong interdependency, the Web shell and the Web application should be maintained consistent in version, on the basis of the above, the current method of releasing and upgrading the hybrid application is as follows:
from the aspect of the relation of strong interdependency, the Web shell and the Web application should be maintained consistent in version, on the basis of the above, the current method of releasing and upgrading the hybrid application is as follows:
[0005] 1. The Web shell is preferentially released before the Web application, and the Web shell is downwards compatibly developed in program, that is, the Web shell is held to support the currently adaptive Web application version and lower versions, and the Web application is released after the Web shell has been upgraded to cover an agreed period of time;
[0006] 2. The Web shell and the Web application are released substantially at the same period, Date Regue/Date Received 2022-09-22 but the Web shell is required to remind compulsive update and upgrade.
[0007] With respect to mode 1, there is an agreed waiting period, and a certain agreed quantity in advance is required for the interval between the release of the Web shell and the release of the Web application, at the same time, the Web shell should ensure downward compatibility within the agreed period, although user experience can be guaranteed, there are consumptions both in time and in workload on the development level; with respect to mode 2, in the case there are many business lines of the Web application, in order to satisfy version consistency, the Web shell is required to be upgraded compulsively at each time the Web application is upgraded, so that the Web shell is frequently compulsively upgraded, and user experience is rendered very bad.
SUMMARY OF THE INVENTION
SUMMARY OF THE INVENTION
[0008] An objective of the present invention is to provide a release upgrading method applicable to a hybrid application, and corresponding device and intelligent equipment, so as to solve prior-art problems in which, when a hybrid mobile application is being released and updated, in order to guarantee the dependent relation between the Web shell and the Web application, it is required to make agreement on successive release periods to ensure consistency of versions, so that there are consumptions both in time and in workload, and user experiences are rather unfriendly.
[0009] In order to achieve the above objective, according to the first aspect, the present invention provides a release upgrading method applicable to a hybrid application, and the method comprises:
[0010] submitting Web shell data and/or Web application data to a version management system in preparation for release;
[0011] retrieving Web application data of a corresponding version number from the version management system for associated matching with newly submitted Web shell data, and Date Regue/Date Received 2022-09-22 generating Web shell updated data; and/or retrieving Web shell data of a corresponding version number from the version management system for associated matching with newly submitted Web application data, and generating Web application updated data;
[0012] self-checking a current Web shell version and an embedded Web application version when a hybrid application is started, and simultaneously accessing the version management system to request for interaction; and
[0013] correspondingly pushing latest Web shell updated data and/or Web application updated data for update when there are/is the latest Web shell updated data and/or Web application updated data in the version management system.
[0014] Exemplarily, the Web shell data includes one or more selected from an application system platform, a Web shell version number, and a Web shell download link, and the Web application data includes one or more selected from a Web application function serial number, a Web application version number, a Web application access link, and a compatible Web shell version number.
[0015] Preferably, the step of retrieving Web application data corresponding to version number from the version management system for associated matching with newly submitted Web shell data, and generating Web shell updated data includes:
[0016] selecting, when Web shell data is newly submitted to the version management system, one piece of Web application data adapted thereto according to the Web shell version number, and generating Web shell updated data and embedded Web application data.
[0017] Preferably, the step of retrieving Web shell data corresponding to version number from the version management system for associated matching with newly submitted Web application data, and generating Web application updated data includes:
[0018] selecting, when Web application data is newly submitted to the version management system, one piece of Web shell data adapted thereto according to the Web application version number, and updating Web shell updated data and embedded Web application Date Regue/Date Received 2022-09-22 data.
[0019] Preferably, the step of self-checking a current Web shell version and an embedded Web application version when a hybrid application is started, and simultaneously accessing the version management system to request for interaction includes:
[0020] automatically acquiring a currently running Web shell version number and an embedded Web application version number when the hybrid application is started;
[0021] requesting to access the version management system, and extracting the latest Web shell version number and the latest Web application version number from the latest Web shell updated data and embedded Web application data that are to be released; and
[0022] judging whether the currently running Web shell version number is consistent with the extracted latest Web shell version number, and whether the currently embedded Web application version number is consistent with the extracted latest Web application version number, and executing the next step if a judging result is negative, otherwise dispensing with any update of the hybrid application of the current version.
[0023] Further, the step of correspondingly pushing latest Web shell updated data and/or Web application updated data for update when there are/is the latest Web shell updated data and/or Web application updated data in the version management system includes:
[0024] pushing a Web shell updating reminder to a user terminal when there is the latest Web shell updated data in the version management system; and
[0025] automatically embedding matched Web application updated data when there is the latest Web application updated data in the version management system and when the version management system is networked through a currently running Web shell.
[0026] In comparison with prior-art technology, the release upgrading method applicable to a hybrid application provided by the present invention achieves the following advantageous effects.
Date Regue/Date Received 2022-09-22
Date Regue/Date Received 2022-09-22
[0027] In the release upgrading method applicable to a hybrid application provided by the present invention, when the R&D personnel has completed update of the version(s) of the Web shell data and/or the Web application data, it/these can be immediately submitted to the version management system for storage and to be released, in comparison with prior-art technology in which there is the restriction of a relation of strong interdependency during the process of releasing and upgrading the Web shell data and the Web application data, use of the method provided by the present invention makes it unnecessary to set a waiting period of release after completion of the research and development of new versions, whereby working time and workload of the R&D personnel are greatly reduced; in addition, Web application data corresponding to version number should be matched when new Web shell data is submitted, so as to correspondingly generate adapted Web shell updated data, alternatively, Web shell data corresponding to version number should be matched when new Web application data is submitted, so as to correspondingly generate adapted Web application updated data, at the same time, the Web shell updated data and the Web application updated data are disposed in the version management system for the terminal to download and update, subsequently, whenever the terminal hybrid application is started, a self-checking program will be started to detect the current Web shell version and the embedded Web application version, and interactive comparison is made with the version management system according to the detected version numbers, when the comparison result shows that there is the latest Web shell updated data, the version management system will push a Web shell updating reminder to the user terminal, and update is downloaded from the version management system through a Web shell download link after the user has selected the updating mode; when the comparison result shows that there is the latest Web application updated data, and when the version management system is networked through the currently running Web shell, matched Web application updated data is automatically embedded in the Web shell; when the comparison result shows that there is neither the latest Web shell updated data nor the latest Web application updated data, this indicates that the Web shell version and the embedded Web application version currently running in the terminal are of the latest Date Regue/Date Received 2022-09-22 versions, and there is no need to update.
[0028] Seen as such, use of the scheme provided by the present invention can achieve the following effects:
[0029] 1. It is possible to reduce coupling between Web shell update and Web application update when upgrade is released by the hybrid application, whereby the two parts can be independently released, no temporal sequence is required for the releases, and no mutual waiting is demanded, so the releasing efficiency is enhanced;
[0030] 2. Highly effective management is achieved for version matching between the Web shell and the Web application in the hybrid application, the function borne by the Web shell in prior-art technology to make the adaptive version compatible is reduced, light-weight of the Web shell is achieved, and the burden of application development on version maintenance is reduced;
[0031] 3. It is achieved that download and installation are made only when update is required for the Web shell, while the upgrade of the Web application does not necessitate compulsive upgrade of the Web shell, and the upgrading process of the Web application is imperceptible to the user, so the use experience of the user is ensured.
[0032] According to another aspect, the present invention provides a release upgrading device applicable to a hybrid application, the device is applied to the release upgrading method appliable to a hybrid application as recited in the foregoing technical solution, and comprises:
[0033] a pre-releasing unit, for submitting Web shell data and/or Web application data to a version management system in preparation for release;
[0034] a version matching unit, for retrieving Web application data corresponding to version number from the version management system for associated matching with newly submitted Web shell data, and generating Web shell updated data; and/or retrieving Web shell data corresponding to version number from the version management system for associated matching with newly submitted Web application data, and generating Web Date Regue/Date Received 2022-09-22 application updated data;
[0035] a checking unit, for self-checking a current Web shell version and an embedded Web application version when a hybrid application is started, and simultaneously accessing the version management system to request for interaction; and
[0036] a version updating unit, for correspondingly pushing latest Web shell updated data and/or Web application updated data for update when there are/is the latest Web shell updated data and/or Web application updated data in the version management system.
[0037] Preferably, the checking unit includes:
[0038] a version number checking module, for automatically acquiring a currently running Web shell version number and an embedded Web application version number when the hybrid application is started;
[0039] an interacting module, for automatically acquiring a currently running Web shell version number and an embedded Web application version number when the hybrid application is started; and
[0040] a judging module, for judging whether the currently running Web shell version number is consistent with the extracted latest Web shell version number, and whether the currently embedded Web application version number is consistent with the extracted latest Web application version number, and executing the next step if a judging result is negative, otherwise dispensing with any update of the hybrid application of the current version.
[0041] Preferably, the version updating unit includes:
[0042] a Web shell updating module, for pushing a Web shell updating reminder to a user terminal when there is the latest Web shell updated data in the version management system; and
[0043] a Web application updating module, for automatically embedding matched Web application updated data when there is the latest Web application updated data in the version management system and when the version management system is networked through a currently running Web shell.
Date Regue/Date Received 2022-09-22
Date Regue/Date Received 2022-09-22
[0044] In comparison with prior-art technology, the advantageous effects achieved by the release upgrading device applicable to a hybrid application provided by the present invention are identical with the advantageous effects achievable by the release upgrading method applicable to a hybrid application provided by the foregoing technical solution, so these are not redundantly described in this context.
[0045] According to the third aspect, the present invention provides an intelligent equipment that subsumes the release upgrading device applicable to a hybrid application as recited in the foregoing technical solution.
[0046] In comparison with prior-art technology, the advantageous effects achieved by the intelligent equipment provided by the present invention are identical with the advantageous effects achievable by the release upgrading device applicable to a hybrid application provided by the foregoing technical solution, so these are not redundantly described in this context.
BRIEF DESCRIPTION OF THE DRAWINGS
BRIEF DESCRIPTION OF THE DRAWINGS
[0047] The drawings described here are merely meant to provide further understanding of the present invention, and constitute a part of the present invention; exemplary embodiments of the present invention are merely meant to explain the present invention, and do not constitute any improper restriction to the present invention. In the drawings:
[0048] Fig. 1 is a flowchart schematically illustrating a release upgrading method applicable to a hybrid application in Embodiment 1 of the present invention;
[0049] Fig. 2 is a view schematically illustrating specific implementation of the release upgrading method applicable to a hybrid application in Embodiment 1 of the present Date Regue/Date Received 2022-09-22 invention; and
[0050] Fig. 3 is a block diagram illustrating the structure of a release upgrading device applicable to a hybrid application in Embodiment 2 of the present invention.
[0051] Reference Numerals:
[0052] 1 ¨ pre-releasing unit 2 ¨ version matching unit
[0053] 3 ¨ checking unit 4 ¨ version updating unit DETAILED DESCRIPTION OF THE INVENTION
[0054] To make the objectives, features and advantages of the present invention more lucid and clear, the technical solutions in the embodiments of the present invention will be clearly and comprehensively described below in conjunction with accompanying drawings in the embodiments of the present invention. Apparently, the embodiments as described below are merely partial, rather than the entire, embodiments of the present invention. All other embodiments makeable by persons ordinarily skilled in the art on the basis of the embodiments in the present invention without spending any creative effort in the process shall all fall within the protection scope of the present invention.
[0055] Embodiment 1
[0056] Please refer to Fig. 1, this embodiment provides a release upgrading method applicable to a hybrid application, and the method comprises:
[0057] submitting Web shell data and/or Web application data to a version management system in preparation for release; retrieving Web application data of a corresponding version number from the version management system for associated matching with newly submitted Web shell data, and generating Web shell updated data; and/or retrieving Web shell data of a corresponding version number from the version management system for Date Regue/Date Received 2022-09-22 associated matching with newly submitted Web application data, and generating Web application updated data; self-checking a current Web shell version and an embedded Web application version when a hybrid application is started, and simultaneously accessing the version management system to request for interaction; and correspondingly pushing latest Web shell updated data and/or Web application updated data for update when there are/is the latest Web shell updated data and/or Web application updated data in the version management system.
[0058] In the release upgrading method applicable to a hybrid application provided by this embodiment, when the R&D personnel has completed update of the version(s) of the Web shell data and/or the Web application data, it/these can be immediately submitted to the version management system for storage and to be released, in comparison with prior-art technology in which there is the restriction of a relation of strong interdependency during the process of releasing and upgrading the Web shell data and the Web application data, use of the method provided by this embodiment makes it unnecessary to set a waiting period of release after completion of the research and development of new versions, whereby working time and workload of the R&D personnel are greatly reduced; in addition, Web application data corresponding to version number should be matched when new Web shell data is submitted, so as to correspondingly generate adapted Web shell updated data, alternatively, Web shell data corresponding to version number should be matched when new Web application data is submitted, so as to correspondingly generate adapted Web application updated data, at the same time, the Web shell updated data and the Web application updated data are disposed in the version management system for the terminal to download and update, subsequently, whenever the terminal hybrid application is started, a self-checking program will be started to detect the current Web shell version and the embedded Web application version, and interactive comparison is made with the version management system according to the detected version numbers, when the comparison result shows that there is the latest Web shell updated data, the version management system will push a Web shell updating reminder to the user terminal, and Date Regue/Date Received 2022-09-22 update is downloaded from the version management system through a Web shell download link after the user has selected the updating mode; when the comparison result shows that there is the latest Web application updated data, and when the version management system is networked through the currently running Web shell, matched Web application updated data is automatically embedded in the Web shell; when the comparison result shows that there is neither the latest Web shell updated data nor the latest Web application updated data, this indicates that the Web shell version and the embedded Web application version currently running in the terminal are of the latest versions, and there is no need to update.
[0059] Seen as such, use of the scheme provided by this embodiment can achieve the following effects:
[0060] 1. It is possible to reduce coupling between Web shell update and Web application update when upgrade is released by the hybrid application, whereby the two parts can be independently released, no temporal sequence is required for the releases, and no mutual waiting is demanded, so the releasing efficiency is enhanced;
[0061] 2. Highly effective management is achieved for version matching between the Web shell and the Web application in the hybrid application, the function borne by the Web shell in prior-art technology to make the adaptive version compatible is reduced, light-weight of the Web shell is achieved, and the burden of application development on version maintenance is reduced;
[0062] 3. It is achieved that download and installation are made only when update is required for the Web shell, while the upgrade of the Web application does not necessitate compulsive upgrade of the Web shell, and the upgrading process of the Web application is imperceptible to the user, so the use experience of the user is ensured.
[0063] As should be noted, the Web shell data consists of essential fields and inessential fields, of which the essential fields of the Web shell data include an application system platform, a Web shell version number, and a Web shell download link, and the inessential fields of Date Regue/Date Received 2022-09-22 the Web shell data include upgrading mode selection and version upgrading description;
likewise, the Web application data also consists of essential fields and inessential fields, of which the essential fields of the Web application data include a Web application function serial number, a Web application version number, a Web application access link, and a compatible Web shell version number, and the inessential fields of the Web application data include version upgrading description; the compatible Web shell version number means the record field of the Web shell version number to which the Web application data can be adapted.
likewise, the Web application data also consists of essential fields and inessential fields, of which the essential fields of the Web application data include a Web application function serial number, a Web application version number, a Web application access link, and a compatible Web shell version number, and the inessential fields of the Web application data include version upgrading description; the compatible Web shell version number means the record field of the Web shell version number to which the Web application data can be adapted.
[0064] Exemplarily, the structure of the Web shell data in the version management system is as follows:
[0065] ___________________________________________________________________ Platform AppVersion DownloadUrl Upgrade Describe Android 1.1.1 http://... 1 information description Android 1.1.0 http://... 0 information description
[0066] In this table, Upgrade 1 expresses automatic upgrading, and Upgrade 0 expresses manual upgrading, after the user terminal has received the version upgrading reminder, selection of the upgrading mode can be received, so the user is bestowed with flexible upgrading experiences.
[0067] The structure of the Web application data in the version management system is as follows:
[0068] ___________________________________________________________________ ModuleID Version LoadUrl AppVersion Describe 1 1.1.1 web http://... 1.1.1 information description 1 1.1.0 web http://... 1.1.0 information description Date Regue/Date Received 2022-09-22
[0069] Specifically, the step of retrieving Web application data corresponding to version number from the version management system for associated matching with newly submitted Web shell data, and generating Web shell updated data in the foregoing embodiment includes:
[0070] selecting, when Web shell data is newly submitted to the version management system, one piece of Web application data adapted thereto according to the Web shell version number, and generating Web shell updated data and embedded Web application data.
[0071] The step of retrieving Web shell data corresponding to version number from the version management system for associated matching with newly submitted Web application data, and generating Web application updated data includes:
[0072] selecting, when Web application data is newly submitted to the version management system, one piece of Web shell data adapted thereto according to the Web application version number, and updating Web shell updated data and embedded Web application data.
[0073] Exemplarily, the Web shell updated data and embedded Web application data matched and obtained on the basis of the aforementioned Web shell data and Web application data are as shown in the following Table:
[0074]
Platform App Version DownloadUrl Upgrade Describe ModuleID Version LoadUrl Describe Android 1.1.1 http://... 1 information 1 1.1.1 web http://... information description description Android 1.1.0 http://... 0 information 1 1.1.0 web http://... information description description
Platform App Version DownloadUrl Upgrade Describe ModuleID Version LoadUrl Describe Android 1.1.1 http://... 1 information 1 1.1.1 web http://... information description description Android 1.1.0 http://... 0 information 1 1.1.0 web http://... information description description
[0075] In accordance with the newly submitted Web shell data and Web application data, the version management system completes version matching of the Web shell data and the Web application data, and obtains associated Web shell updated data and embedded Web application data after matching, so that the data is supplied to the hybrid application in the form of an API interface to complete the upgrading process.
Date Regue/Date Received 2022-09-22
Date Regue/Date Received 2022-09-22
[0076] The step of self-checking a current Web shell version and an embedded Web application version when a hybrid application is started, and simultaneously accessing the version management system to request for interaction in the foregoing embodiment includes:
[0077] automatically acquiring a currently running Web shell version number and an embedded Web application version number when the hybrid application is started;
requesting to access the version management system, and extracting the latest Web shell version number and the latest Web application version number from the latest Web shell updated data and embedded Web application data that are to be released; judging whether the currently running Web shell version number is consistent with the extracted latest Web shell version number, and whether the currently embedded Web application version number is consistent with the extracted latest Web application version number, and executing the next step if a judging result is negative, otherwise dispensing with any update of the hybrid application of the current version.
requesting to access the version management system, and extracting the latest Web shell version number and the latest Web application version number from the latest Web shell updated data and embedded Web application data that are to be released; judging whether the currently running Web shell version number is consistent with the extracted latest Web shell version number, and whether the currently embedded Web application version number is consistent with the extracted latest Web application version number, and executing the next step if a judging result is negative, otherwise dispensing with any update of the hybrid application of the current version.
[0078] The step of correspondingly pushing latest Web shell updated data and/or Web application updated data for update when there are/is the latest Web shell updated data and/or Web application updated data in the version management system includes:
[0079] pushing a Web shell updating reminder to a user terminal when there is the latest Web shell updated data in the version management system; and automatically embedding matched Web application updated data when there is the latest Web application updated data in the version management system and when the version management system is networked through a currently running Web shell.
[0080] During specific implementation, when the hybrid application is started, the Web shell updated data and the Web application access link are obtained from the version management system, when it is required to update the Web shell, the Web shell updating reminder and the Web application in which a compatible version has been embedded are obtained, thereafter the user manually chooses the updating mode of the Web shell Date Regue/Date Received 2022-09-22 according to the Web shell updating reminder, and download and installation are carried out to complete update of the Web shell; alternatively, when the Web shell should not be updated but the Web application should be updated, the Web application data of an adapted version can be directly obtained according to the Web application access link at this time and embedded in the Web shell for presentation to the user, and the entire process is imperceptible to the user ¨ see Fig. 2 for the specific realization process.
[0081] Embodiment 2
[0082] Please refer to Fig. 1 and Fig. 3, this embodiment provides a release upgrading device applicable to a hybrid application, and the device comprises:
[0083] a pre-releasing unit 1, for submitting Web shell data and/or Web application data to a version management system in preparation for release;
[0084] a version matching unit 2, for retrieving Web application data corresponding to version number from the version management system for associated matching with newly submitted Web shell data, and generating Web shell updated data; and/or retrieving Web shell data corresponding to version number from the version management system for associated matching with newly submitted Web application data, and generating Web application updated data;
[0085] a checking unit 3, for self-checking a current Web shell version and an embedded Web application version when a hybrid application is started, and simultaneously accessing the version management system to request for interaction; and
[0086] a version updating unit 4, for correspondingly pushing latest Web shell updated data and/or Web application updated data for update when there are/is the latest Web shell updated data and/or Web application updated data in the version management system.
[0087] Preferably, the checking unit 3 includes:
[0088] a version number checking module, for automatically acquiring a currently running Web shell version number and an embedded Web application version number when the hybrid Date Regue/Date Received 2022-09-22 application is started;
[0089] an interacting module, for automatically acquiring a currently running Web shell version number and an embedded Web application version number when the hybrid application is started; and
[0090] a judging module, for judging whether the currently running Web shell version number is consistent with the extracted latest Web shell version number, and whether the currently embedded Web application version number is consistent with the extracted latest Web application version number, and executing the next step if a judging result is negative, otherwise dispensing with any update of the hybrid application of the current version.
[0091] Preferably, the version updating unit 4 includes:
[0092] a Web shell updating module, for pushing a Web shell updating reminder to a user terminal when there is the latest Web shell updated data in the version management system; and
[0093] a Web application updating module, for automatically embedding matched Web application updated data when there is the latest Web application updated data in the version management system and when the version management system is networked through a currently running Web shell.
[0094] In comparison with prior-art technology, the advantageous effects achieved by the release upgrading device applicable to a hybrid application provided by this embodiment of the present invention are identical with the advantageous effects achievable by the release upgrading method applicable to a hybrid application provided by Embodiment 1, so these are not redundantly described in this context.
[0095] Embodiment 3
[0096] This embodiment provides an intelligent equipment that subsumes the release upgrading device applicable to a hybrid application as recited in the foregoing embodiments.
Date Regue/Date Received 2022-09-22
Date Regue/Date Received 2022-09-22
[0097] In comparison with prior-art technology, the advantageous effects achieved by the intelligent equipment provided by this embodiment of the present invention are identical with the advantageous effects achievable by the release upgrading device applicable to a hybrid application provided by Embodiment 2, so these are not redundantly described in this context.
[0098] As understandable to persons ordinarily skilled in the art, the entire or partial steps realizing the method of the present invention can be completed via a program to instruct relevant hardware, the program can be stored in a computer-readable storage medium, and subsumes the various steps of the method in the foregoing embodiments when it is executed, and the storage medium can be an ROM/RAM, a magnetic disk, an optical disk, or a memory card, etc.
[0099] What the above describes is merely directed to specific modes of execution of the present invention, but the protection scope of the present invention is not restricted thereby. Any change or replacement easily conceivable to persons skilled in the art within the technical range disclosed by the present invention shall be covered by the protection scope of the present invention. Accordingly, the protection scope of the present invention shall be based on the protection scope as claimed in the Claims.
Date Regue/Date Received 2022-09-22
Date Regue/Date Received 2022-09-22
Claims (10)
1. A release upgrading method applicable to a hybrid application, characterized in comprising:
submitting Web shell data and/or Web application data to a version management system in preparation for release;
retrieving Web application data corresponding to version number from the version management system for associated matching with newly submitted Web shell data, and generating Web shell updated data; and/or retrieving Web shell data corresponding to version number from the version management system for associated matching with newly submitted Web application data, and generating Web application updated data;
self-checking a current Web shell version and an embedded Web application version when a hybrid application is started, and simultaneously accessing the version management system to request for interaction; and correspondingly pushing latest Web shell updated data and/or Web application updated data for update when there are/is the latest Web shell updated data and/or Web application updated data in the version management system.
submitting Web shell data and/or Web application data to a version management system in preparation for release;
retrieving Web application data corresponding to version number from the version management system for associated matching with newly submitted Web shell data, and generating Web shell updated data; and/or retrieving Web shell data corresponding to version number from the version management system for associated matching with newly submitted Web application data, and generating Web application updated data;
self-checking a current Web shell version and an embedded Web application version when a hybrid application is started, and simultaneously accessing the version management system to request for interaction; and correspondingly pushing latest Web shell updated data and/or Web application updated data for update when there are/is the latest Web shell updated data and/or Web application updated data in the version management system.
2. The method according to Claim 1, characterized in that the Web shell data includes one or more selected from an application system platform, a Web shell version number, and a Web shell download link, and that the Web application data includes one or more selected from a Web application function serial number, a Web application version number, a Web application access link, and a compatible Web shell version number.
3. The method according to Claim 2, characterized in that the step of retrieving Web application data corresponding to version number from the version management system for associated matching with newly submitted Web shell data, and generating Web shell updated data includes:
selecting, when Web shell data is newly submitted to the version management system, one piece Date Regue/Date Received 2022-09-22 of Web application data adapted thereto according to the Web shell version number, and generating Web shell updated data and embedded Web application data.
selecting, when Web shell data is newly submitted to the version management system, one piece Date Regue/Date Received 2022-09-22 of Web application data adapted thereto according to the Web shell version number, and generating Web shell updated data and embedded Web application data.
4. The method according to Claim 2, characterized in that the step of retrieving Web shell data corresponding to version number from the version management system for associated matching with newly submitted Web application data, and generating Web application updated data includes:
selecting, when Web application data is newly submitted to the version management system, one piece of Web shell data adapted thereto according to the Web application version number, and updating Web shell updated data and embedded Web application data.
selecting, when Web application data is newly submitted to the version management system, one piece of Web shell data adapted thereto according to the Web application version number, and updating Web shell updated data and embedded Web application data.
5. The method according to Claim 3 or 4, characterized in that the step of self-checking a current Web shell version and an embedded Web application version when a hybrid application is started, and simultaneously accessing the version management system to request for interaction includes:
automatically acquiring a currently running Web shell version number and an embedded Web application version number when the hybrid application is started;
requesting to access the version management system, and extracting the latest Web shell version number and the latest Web application version number from the latest Web shell updated data and embedded Web application data that are to be released; and judging whether the currently running Web shell version number is consistent with the extracted latest Web shell version number, and whether the currently embedded Web application version number is consistent with the extracted latest Web application version number, and executing the next step if a judging result is negative, otherwise dispensing with any update of the hybrid application of the current version.
automatically acquiring a currently running Web shell version number and an embedded Web application version number when the hybrid application is started;
requesting to access the version management system, and extracting the latest Web shell version number and the latest Web application version number from the latest Web shell updated data and embedded Web application data that are to be released; and judging whether the currently running Web shell version number is consistent with the extracted latest Web shell version number, and whether the currently embedded Web application version number is consistent with the extracted latest Web application version number, and executing the next step if a judging result is negative, otherwise dispensing with any update of the hybrid application of the current version.
6. The method according to Claim 5, characterized in that the step of correspondingly pushing latest Web shell updated data and/or Web application updated data for update when there are/is the latest Web shell updated data and/or Web application updated data in the version management system includes:
Date Regue/Date Received 2022-09-22 pushing a Web shell updating reminder to a user terminal when there is the latest Web shell updated data in the version management system; and automatically embedding matched Web application updated data when there is the latest Web application updated data in the version management system and when the version management system is networked through a currently running Web shell.
Date Regue/Date Received 2022-09-22 pushing a Web shell updating reminder to a user terminal when there is the latest Web shell updated data in the version management system; and automatically embedding matched Web application updated data when there is the latest Web application updated data in the version management system and when the version management system is networked through a currently running Web shell.
7. A release upgrading device applicable to a hybrid application, characterized in comprising:
a pre-releasing unit, for submitting Web shell data and/or Web application data to a version management system in preparation for release;
a version matching unit, for retrieving Web application data corresponding to version number from the version management system for associated matching with newly submitted Web shell data, and generating Web shell updated data; and/or retrieving Web shell data corresponding to version number from the version management system for associated matching with newly submitted Web application data, and generating Web application updated data;
a checking unit, for self-checking a current Web shell version and an embedded Web application version when a hybrid application is started, and simultaneously accessing the version management system to request for interaction; and a version updating unit, for correspondingly pushing latest Web shell updated data and/or Web application updated data for update when there are/is the latest Web shell updated data and/or Web application updated data in the version management system.
a pre-releasing unit, for submitting Web shell data and/or Web application data to a version management system in preparation for release;
a version matching unit, for retrieving Web application data corresponding to version number from the version management system for associated matching with newly submitted Web shell data, and generating Web shell updated data; and/or retrieving Web shell data corresponding to version number from the version management system for associated matching with newly submitted Web application data, and generating Web application updated data;
a checking unit, for self-checking a current Web shell version and an embedded Web application version when a hybrid application is started, and simultaneously accessing the version management system to request for interaction; and a version updating unit, for correspondingly pushing latest Web shell updated data and/or Web application updated data for update when there are/is the latest Web shell updated data and/or Web application updated data in the version management system.
8. The device according to Claim 7, characterized in that the checking unit includes:
a version number checking module, for automatically acquiring a currently running Web shell version number and an embedded Web application version number when the hybrid application is started;
an interacting module, for automatically acquiring a currently running Web shell version number and an embedded Web application version number when the hybrid application is started; and a judging module, for judging whether the currently running Web shell version number is consistent with the extracted latest Web shell version number, and whether the currently Date Regue/Date Received 2022-09-22 embedded Web application version number is consistent with the extracted latest Web application version number, and executing the next step if a judging result is negative, otherwise dispensing with any update of the hybrid application of the current version.
a version number checking module, for automatically acquiring a currently running Web shell version number and an embedded Web application version number when the hybrid application is started;
an interacting module, for automatically acquiring a currently running Web shell version number and an embedded Web application version number when the hybrid application is started; and a judging module, for judging whether the currently running Web shell version number is consistent with the extracted latest Web shell version number, and whether the currently Date Regue/Date Received 2022-09-22 embedded Web application version number is consistent with the extracted latest Web application version number, and executing the next step if a judging result is negative, otherwise dispensing with any update of the hybrid application of the current version.
9. The device according to Claim 7, characterized in that the version updating unit includes:
a Web shell updating module, for pushing a Web shell updating reminder to a user terminal when there is the latest Web shell updated data in the version management system;
and a Web application updating module, for automatically embedding matched Web application updated data when there is the latest Web application updated data in the version management system and when the version management system is networked through a currently running Web shell.
a Web shell updating module, for pushing a Web shell updating reminder to a user terminal when there is the latest Web shell updated data in the version management system;
and a Web application updating module, for automatically embedding matched Web application updated data when there is the latest Web application updated data in the version management system and when the version management system is networked through a currently running Web shell.
10. An intelligent equipment, characterized in comprising the release upgrading device applicable to a hybrid application as recited in any one of Claims 7 to 9.
Date Regue/Date Received 2022-09-22
Date Regue/Date Received 2022-09-22
Applications Claiming Priority (3)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910256806.XA CN110113377A (en) | 2019-04-01 | 2019-04-01 | The method and device of release upgrade suitable for mixed mode applications, smart machine |
| CN201910256806.X | 2019-04-01 | ||
| PCT/CN2019/109119 WO2020199543A1 (en) | 2019-04-01 | 2019-09-29 | Method and apparatus applicable to release and upgrade of hybrid application, and intelligent device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CA3176456A1 true CA3176456A1 (en) | 2020-10-08 |
Family
ID=67484793
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CA3176456A Pending CA3176456A1 (en) | 2019-04-01 | 2019-09-29 | Release upgrading method applicable to hybrid application, corresponding device and intelligent equipment |
Country Status (3)
| Country | Link |
|---|---|
| CN (1) | CN110113377A (en) |
| CA (1) | CA3176456A1 (en) |
| WO (1) | WO2020199543A1 (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110113377A (en) * | 2019-04-01 | 2019-08-09 | 苏宁易购集团股份有限公司 | The method and device of release upgrade suitable for mixed mode applications, smart machine |
| CN110941446B (en) * | 2019-11-06 | 2021-06-18 | 深圳市云网万店科技有限公司 | Version release method and device based on multi-environment offline task |
| CN112509379A (en) * | 2020-10-09 | 2021-03-16 | 广州市中南民航空管通信网络科技有限公司 | Flight data submission method, terminal and system |
Family Cites Families (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8191060B2 (en) * | 2006-08-29 | 2012-05-29 | Adobe Systems Incorporated | Software installation using template executables |
| CN104657170A (en) * | 2013-11-25 | 2015-05-27 | 腾讯科技（上海）有限公司 | Data updating method, device and system |
| US9274784B2 (en) * | 2014-06-02 | 2016-03-01 | Sap Se | Automatic deployment and update of hybrid applications |
| CN107153536B (en) * | 2017-03-31 | 2021-05-07 | 北京三快在线科技有限公司 | Application processing method and device |
| CN107391104B (en) * | 2017-05-31 | 2021-06-01 | 杭州大搜车汽车服务有限公司 | Client and reactive native code update dependence management method, device and system |
| CN107832099B (en) * | 2017-10-26 | 2020-12-11 | 咪咕数字传媒有限公司 | Method and device for client version compatibility and storage medium |
| CN108762767B (en) * | 2018-05-31 | 2024-04-02 | 康键信息技术（深圳）有限公司 | Application publishing method, device and computer readable storage medium |
| CN110113377A (en) * | 2019-04-01 | 2019-08-09 | 苏宁易购集团股份有限公司 | The method and device of release upgrade suitable for mixed mode applications, smart machine |
-
2019
- 2019-04-01 CN CN201910256806.XA patent/CN110113377A/en active Pending
- 2019-09-29 CA CA3176456A patent/CA3176456A1/en active Pending
- 2019-09-29 WO PCT/CN2019/109119 patent/WO2020199543A1/en active Application Filing
Also Published As
| Publication number | Publication date |
|---|---|
| CN110113377A (en) | 2019-08-09 |
| WO2020199543A1 (en) | 2020-10-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP6644882B2 (en) | Managing delivery of code and dependent data using application containers | |
| CN108027741A (en) | Document handling method, device, terminal and storage medium based on patch upgrading | |
| CA3176456A1 (en) | Release upgrading method applicable to hybrid application, corresponding device and intelligent equipment | |
| CN102622241B (en) | A kind of method for upgrading software and device | |
| CN107391104B (en) | Client and reactive native code update dependence management method, device and system | |
| US20220156133A1 (en) | Cross-Process Communication Method, Apparatus, and Device | |
| EP2806357A1 (en) | Method and communication device for updating a web application | |
| CN100421072C (en) | Method for realizing software updating | |
| CN106557347B (en) | Software updating method and device | |
| CN105786567A (en) | Middleware for information interaction of light application and main application and iOS application sub-module dynamic updating method | |
| US20120210317A1 (en) | Method and apparatus for updating data card | |
| CN111427594B (en) | Application program running method and device | |
| CN104636159B (en) | The method and apparatus that software in virtual machine is upgraded | |
| CN103617058B (en) | QNX-based system and method for installing and uninstalling application software | |
| CN107239313A (en) | The upgrade method and storage medium of Spring application services | |
| CN107220074A (en) | To the access of supporting layer software function, upgrade method and device | |
| US8612996B2 (en) | Technique for integrating a distributed object system component with a service oriented architecture application | |
| US20140068586A1 (en) | Calendar aware adaptive patching of a computer program | |
| CN112269565A (en) | Container-based edge device operation method, device and system | |
| CN107193565B (en) | Method for developing native APP (application) across mobile terminals | |
| CN113204425B (en) | Method, device, electronic equipment and storage medium for process management internal thread | |
| CN106293790B (en) | application program upgrading method and device based on Firefox operating system | |
| CN110489149B (en) | Control method and system of intelligent equipment | |
| US20170199733A1 (en) | Method for terminal to update operating system, terminal and system | |
| US20110307855A1 (en) | Software project management apparatuses and methods thereof |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| EEER | Examination request |
Effective date: 20220922 |
|
| EEER | Examination request |
Effective date: 20220922 |
|
| EEER | Examination request |
Effective date: 20220922 |
|
| EEER | Examination request |
Effective date: 20220922 |
|
| EEER | Examination request |
Effective date: 20220922 |
|
| EEER | Examination request |
Effective date: 20220922 |
|
| EEER | Examination request |
Effective date: 20220922 |