CN112363717A - Method and terminal for loading different functions in single software - Google Patents
Method and terminal for loading different functions in single software Download PDFInfo
- Publication number
- CN112363717A CN112363717A CN202011181371.6A CN202011181371A CN112363717A CN 112363717 A CN112363717 A CN 112363717A CN 202011181371 A CN202011181371 A CN 202011181371A CN 112363717 A CN112363717 A CN 112363717A
- Authority
- CN
- China
- Prior art keywords
- version number
- configuration file
- function
- acquiring
- file
- 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.)
- Granted
Links
- 230000006870 function Effects 0.000 title claims abstract description 174
- 238000000034 method Methods 0.000 title claims abstract description 35
- 238000005192 partition Methods 0.000 claims description 28
- 238000004590 computer program Methods 0.000 claims description 10
- 238000011161 development Methods 0.000 description 15
- 238000004519 manufacturing process Methods 0.000 description 7
- 238000009434 installation Methods 0.000 description 6
- 238000012423 maintenance Methods 0.000 description 5
- 230000009977 dual effect Effects 0.000 description 4
- 238000012986 modification Methods 0.000 description 4
- 230000004048 modification Effects 0.000 description 4
- 230000009286 beneficial effect Effects 0.000 description 3
- 230000002688 persistence Effects 0.000 description 3
- 238000013515 script Methods 0.000 description 2
- 238000013459 approach Methods 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/36—Software reuse
-
- 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
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Abstract
The invention provides a method and a terminal for loading different functions in single software, wherein a product identifier is loaded, and a corresponding first configuration file is obtained according to the product identifier, wherein the first configuration file comprises a first version number; acquiring a corresponding function file according to the first configuration file; after system configuration is carried out according to the function file, the first version number is saved as the existing version number; the invention sets the configuration file corresponding to the product name and the function file corresponding to the configuration file, acquires the product name when loading, and loads different configuration files according to the product name, thereby realizing the loading of different function files and finally finishing different system configurations based on different product names.
Description
Technical Field
The invention relates to the field of software customization, in particular to a method and a terminal for loading different functions in single software.
Background
In the process of doing projects, different customers in the same project need different functions. If the client A proposes the requirement of the function A, the function B, the function C and the function D; the client B proposes a required function A, a required function B and a required function C; the client C proposes a required function A and a required function D; the proposed demand functions of different customers are overlapped but not completely the same, so that it is too costly to develop different software specifically for different customers.
The following scheme is adopted to solve the problems in the prior art at present: scheme 1: different software code baselines are used for managing different functions and different image files of customers with different function requirements; the method is more intuitive when modification is needed for different clients, but when the number of projects is large, modification or maintenance is inconvenient for each project aiming at different users, and the same modification needs to be carried out on different baselines every time of modification, so that a large amount of repeated work is generated; different mirror image files are needed to be made for the same function in different projects in a production line, so that confusion is easy to cause; when OTA is used for upgrading and maintaining, a server needs to prepare a set of OTA for different projects of different clients respectively, which is inconvenient;
scheme 2: for clients with different function requirements, the same software code base line is used, different compiling scripts are used for managing different functions and different image files, users with different requirements share one set of software codes, if a common problem occurs, only one code needs to be modified, repeated work is reduced, but production lines are the same, but project functions are different, different images are needed, confusion is easily caused, and in the method, when OTA is upgraded and maintained, a server also needs to prepare one set of OTA for different projects of different clients;
scheme 3: for clients with different function requirements, the same software code baseline, the same compiling script and the same mirror image file are used; eventually managing different functions through pkg (installation package configuration file); specifically, different pkg packages are installed for different customers during production, so that the customers realize functional difference after installation; although the functions required by different users are different, a set of software codes are shared, the common problem only needs to modify one code, the repeated workload is reduced, and the same mirror image is finally generated for different projects in a production line, so that the confusion is not easy to happen; however, this approach does not enable OTA upgrades, and once an OTA upgrade is performed, the software will be confused or corrupted.
Disclosure of Invention
The technical problem to be solved by the invention is as follows: the method and the terminal for loading different functions in single software are provided, and customization and updating of different functions are realized through the same software code baseline.
In order to solve the technical problems, the invention adopts a technical scheme that:
a method for loading different functions in a single software, comprising the steps of:
s1, loading a product identifier, and acquiring a corresponding first configuration file according to the product identifier, wherein the first configuration file comprises a first version number;
s2, acquiring a corresponding function file according to the first configuration file;
and S3, after system configuration is carried out according to the function file, the first version number is saved as the existing version number.
In order to solve the technical problem, the invention adopts another technical scheme as follows:
a terminal for loading different functions in a single piece of software, comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the following steps when executing the computer program:
s1, loading a product identifier, and acquiring a corresponding first configuration file according to the product identifier, wherein the first configuration file comprises a first version number;
s2, acquiring a corresponding function file according to the first configuration file;
and S3, after system configuration is carried out according to the function file, the first version number is saved as the existing version number.
The invention has the beneficial effects that: setting a configuration file corresponding to the product name and a function file corresponding to the configuration file, acquiring the product name during loading, loading different configuration files according to the product name at the moment, thereby realizing the loading of different function files, finally completing different system configurations based on different product names, and identifying the configuration files by using version numbers; the corresponding configuration files are automatically loaded according to the product names, the whole program can be packaged in the development process, the configuration and the functions of different products are not required to be distinguished in the development process, the subsequent maintenance and upgrading are facilitated, the development period is shortened, the development efficiency is improved, the customization of different functions is realized only by one software code base line, and the development cost is reduced.
Drawings
FIG. 1 is a flowchart illustrating steps of a method for loading different functions in a single piece of software according to an embodiment of the present invention;
fig. 2 is a schematic structural diagram of a terminal in which different functions are loaded in a single piece of software according to an embodiment of the present invention;
FIG. 3 is a flowchart illustrating steps of a method for loading different functions in a single software in an actual scenario according to an embodiment of the present invention;
description of reference numerals:
1. a terminal with different functions is loaded in a single software; 2. a processor; 3. a memory.
Detailed Description
In order to explain technical contents, achieved objects, and effects of the present invention in detail, the following description is made with reference to the accompanying drawings in combination with the embodiments.
Referring to fig. 1, a method for loading different functions in a single software includes the steps of:
s1, loading a product identifier, and acquiring a corresponding first configuration file according to the product identifier, wherein the first configuration file comprises a first version number;
s2, acquiring a corresponding function file according to the first configuration file;
and S3, after system configuration is carried out according to the function file, the first version number is saved as the existing version number.
From the above description, the beneficial effects of the present invention are: setting a configuration file corresponding to the product name and a function file corresponding to the configuration file, acquiring the product name during loading, loading different configuration files according to the product name at the moment, thereby realizing the loading of different function files, finally completing different system configurations based on different product names, and identifying the configuration files by using version numbers; the corresponding configuration files are automatically loaded according to the product names, the whole program can be packaged in the development process, the configuration and the functions of different products are not required to be distinguished in the development process, the subsequent maintenance and upgrading are facilitated, the development period is shortened, the development efficiency is improved, the customization of different functions is realized only by one software code base line, and the development cost is reduced.
Further, the S1 is preceded by:
presetting an OEM partition;
presetting a configuration file directory for storing the configuration file in the OEM partition;
presetting a function file directory for storing the function files in the OEM partition;
the S1 specifically includes:
loading a product identifier, and acquiring a corresponding first configuration file from the configuration file directory according to the product identifier, wherein the first configuration file comprises a first version number;
the S2 specifically includes:
and acquiring the corresponding function file from the function file directory according to the first configuration file.
According to the above description, a special OEM partition is set, the configuration file directory and the function file directory are set in the OEM partition to store the configuration file and the function file, respectively, and the OEM partition is used as a preset function partition of the system, so that the situation that the files are lost due to misoperation of a user is avoided, and the system can be normally configured every time the system is powered on.
Further, the S1 specifically includes:
acquiring a stored existing version number, acquiring a corresponding first configuration file according to the product identifier, acquiring a first version number in the first configuration file, comparing the first version number with the existing version number according to a preset rule, and executing the step S2 if the first version number is newer than the existing version number; otherwise, quitting loading;
the initial value of the existing version number is 0.
It can be known from the above description that the version number of the configuration file is obtained at each power-on and compared with the existing version number stored in the system, and since the initial existing version number is set to 0 to represent the oldest version, the file version number obtained at the first power-on is certainly newer than the existing version number, the system can obtain the function file corresponding to the configuration file for function configuration, and if the configuration file is updated subsequently, the updated configuration file can be automatically loaded if the version number of the updated configuration file is newer than the existing version number stored in the system, so that the configuration file is updated without dividing different customized functions into a plurality of different installation packages.
Further, the first configuration file in S1 includes product functions;
the S2 specifically includes:
and acquiring a corresponding function file according to the product function.
According to the description, the corresponding function files are loaded according to the product functions stored in the configuration files, different product identifiers correspond to different configuration files, and finally different function files are loaded to realize different function items configured for the system without manufacturing a plurality of different installation packages.
Further, the method also comprises the following steps of updating the first configuration file:
requesting a second version number from a server, and comparing the second version number with the first version number according to a preset rule;
if the second version number is newer than the first version number, acquiring a second configuration file corresponding to the second version number;
and updating the first configuration file according to the second configuration file in an OTA or APK mode.
According to the description, the version number of the corresponding configuration file can be acquired from the server side and compared with the version number of the configuration file stored in the server side, if the version number of the server side is newer, the configuration file stored in the server side can be updated, the configuration file can be updated in an OTA or APK mode, the size of the configuration file is usually smaller, the updating in the OTA mode is stable, the power failure condition is not easy to occur, and better use experience can be provided for a user.
Referring to fig. 2, a terminal with different functions loaded in a single software includes a memory, a processor, and a computer program stored in the memory and running on the processor, and when the processor executes the computer program, the following steps are implemented:
s1, loading a product identifier, and acquiring a corresponding first configuration file according to the product identifier, wherein the first configuration file comprises a first version number;
s2, acquiring a corresponding function file according to the first configuration file;
and S3, after system configuration is carried out according to the function file, the first version number is saved as the existing version number.
The invention has the beneficial effects that: setting a configuration file corresponding to the product name and a function file corresponding to the configuration file, acquiring the product name during loading, loading different configuration files according to the product name at the moment, thereby realizing the loading of different function files, finally completing different system configurations based on different product names, and identifying the configuration files by using version numbers; the corresponding configuration files are automatically loaded according to the product names, the whole program can be packaged in the development process, the configuration and the functions of different products are not required to be distinguished in the development process, the subsequent maintenance and upgrading are facilitated, the development period is shortened, the development efficiency is improved, the customization of different functions is realized only by one software code base line, and the development cost is reduced.
Further, the S1 is preceded by:
presetting an OEM partition;
presetting a configuration file directory for storing the configuration file in the OEM partition;
presetting a function file directory for storing the function files in the OEM partition;
the S1 specifically includes:
loading a product identifier, and acquiring a corresponding first configuration file from the configuration file directory according to the product identifier, wherein the first configuration file comprises a first version number;
the S2 specifically includes:
and acquiring the corresponding function file from the function file directory according to the first configuration file.
According to the above description, a special OEM partition is set, the configuration file directory and the function file directory are set in the OEM partition to store the configuration file and the function file, respectively, and the OEM partition is used as a preset function partition of the system, so that the situation that the files are lost due to misoperation of a user is avoided, and the system can be normally configured every time the system is powered on.
Further, the S1 specifically includes:
acquiring a stored existing version number, acquiring a corresponding first configuration file according to the product identifier, acquiring a first version number in the first configuration file, comparing the first version number with the existing version number according to a preset rule, and executing the step S2 if the first version number is newer than the existing version number; otherwise, quitting loading;
the initial value of the existing version number is 0.
It can be known from the above description that the version number of the configuration file is obtained at each power-on and compared with the existing version number stored in the system, and since the initial existing version number is set to 0 to represent the oldest version, the file version number obtained at the first power-on is certainly newer than the existing version number, the system can obtain the function file corresponding to the configuration file for function configuration, and if the configuration file is updated subsequently, the updated configuration file can be automatically loaded if the version number of the updated configuration file is newer than the existing version number stored in the system, so that the configuration file is updated without dividing different customized functions into a plurality of different installation packages.
Further, the first configuration file in S1 includes product functions;
the S2 specifically includes:
and acquiring a corresponding function file according to the product function.
According to the description, the corresponding function files are loaded according to the product functions stored in the configuration files, different product identifiers correspond to different configuration files, and finally different function files are loaded to realize different function items configured for the system without manufacturing a plurality of different installation packages.
Further, the processor, when executing the computer program, further updates the first configuration file by:
requesting a second version number from a server, and comparing the second version number with the first version number according to a preset rule;
if the second version number is newer than the first version number, acquiring a second configuration file corresponding to the second version number;
and updating the first configuration file according to the second configuration file in an OTA or APK mode.
According to the description, the version number of the corresponding configuration file can be acquired from the server side and compared with the version number of the configuration file stored in the server side, if the version number of the server side is newer, the configuration file stored in the server side can be updated, the configuration file can be updated in an OTA or APK mode, the size of the configuration file is usually smaller, the updating in the OTA mode is stable, the power failure condition is not easy to occur, and better use experience can be provided for a user.
Referring to fig. 1, a first embodiment of the present invention is:
a method for loading different functions in single software comprises the steps of;
s1, presetting an OEM partition, presetting a configuration file directory for storing the configuration file in the OEM partition, and presetting a function file directory for storing the function file in the OEM partition;
if the configuration file catalog is set, storing the configuration files client _ A _ feature.txt, client _ B _ feature.txt and client _ C _ feature.txt, and respectively generating the configuration files according to the customization functions of the client A, the client B and the client C; the configuration file comprises product functions, such as:
content of customer _ a _ feature.
feature_A；
feature_B；
feature_C；
feature_D；
content of customer _ b _ feature.
feature_A；
feature_B；
feature_C；
content of customer _ C _ feature.
feature_A；
feature_D；
In an optional implementation manner, a plurality of function directories are set in a function file directory, each function directory stores a function file corresponding to the function, for example, a function file directory feature is set, function directories feature _ A, feature _ B, feature _ C and feature _ D are stored, function files corresponding to function a, function B, function C and function D are stored, and parameters, an enable switch and the like can be configured in the function files;
if feature _ a is a dual-card dual-standby function, the function directory may be named as feature _ dual _ SIM according to the rule, where function files persistence and nv.txt are stored, a property persistence of dual-card dual-standby is configured in the function file persistence, which indicates that the dual-card dual-standby function is opened, nv.txt configures an NV _ UIM _ HW _ SIM _ CONFIG _ I parameter of a dual card, where the parameter value is 0, which indicates that the item is a single card, and the parameter value is 1, which indicates that the item is a dual card, and if the NV _ UIM _ HW _ SIM _ CONFIG _ I parameter 6907 is set, which indicates that the item is a dual card;
s2, loading a product identifier, and acquiring a corresponding first configuration file according to the product identifier, wherein the first configuration file comprises a first version number; the method specifically comprises the following steps: loading a product identifier, and acquiring a corresponding first configuration file from the configuration file directory according to the product identifier, wherein the first configuration file comprises a first version number and a product function;
s3, acquiring a corresponding function file according to the first configuration file; the method specifically comprises the following steps: acquiring the corresponding function file from the function file directory according to the first configuration file, and acquiring the corresponding function file according to the product function;
and S4, after system configuration is carried out according to the function file, the first version number is saved as the existing version number.
The second embodiment of the invention is as follows:
the existing software version function is generally fixed, if a certain client needs to update and release or limit the setting of certain functions, a software image package is generally upgraded through an OTA (over the air) software, because the software image package is used for updating the whole software, if the intercepted risk is large, the whole software is taken as the image package to be transmitted through the OTA, the consumed flow is too much and the power failure risk in the upgrading process is improved due to the fact that the image package is too large, and in addition, other loopholes are easily introduced into the image package; the present invention provides a method for loading different functions in a single software, which is different from the first embodiment in that:
further comprising updating the first configuration file:
requesting a second version number from a server, and comparing the second version number with the first version number according to a preset rule;
if the second version number is newer than the first version number, acquiring a second configuration file corresponding to the second version number;
updating the first configuration file according to the second configuration file in an OTA or APK mode;
s2 specifically includes:
acquiring a stored existing version number, acquiring a corresponding first configuration file according to the product identifier, acquiring a first version number in the first configuration file, comparing the first version number with the existing version number according to a preset rule, and executing the step S2 if the first version number is newer than the existing version number; otherwise, quitting loading; the initial value of the existing version number is 0;
in an alternative embodiment, it is also:
when the power is firstly powered on: s2 specifically includes:
acquiring a stored initial existing version number, acquiring a corresponding first configuration file according to the product identifier, acquiring a first version number in the first configuration file, comparing the first version number with the initial existing version number according to a preset rule, and executing the step S2 if the first version number is newer than the initial existing version number; otherwise, quitting loading; the value of the initial existing version number is 0;
s4 specifically includes:
after system configuration is carried out according to the function file, the first version number replaces the initial existing version number to be used as an existing version number;
when not first powered up: s1 specifically includes:
requesting a second version number from a server, comparing the second version number with the existing version number according to a preset rule, and updating the first configuration file corresponding to the first version number if the second version number is newer than the existing version number; wherein updating the first configuration file corresponding to the first version number specifically includes: acquiring a second configuration file corresponding to the second version number; updating the first configuration file according to the second configuration file in an OTA or APK mode;
specifically, only the second configuration file is used for replacing the first configuration file, the function file corresponding to the second configuration file is updated, the whole software package is not required to be updated, and the configuration file (OEM/customer _ feature.txt) in the configuration file directory of the OEM partition or the function file (OEM/feature _/. txt) in the function file directory of the OEM partition can be updated in an OTA or APK manner; wherein, denotes a wildcard character;
the updating of the configuration file in the configuration file directory in the OEM partition in the OTA or APK manner specifically includes: (1) updating through an OTA mode: the method comprises the steps that a latest OTA software package is obtained from a terminal server, specifically, after the terminal is started and networked, the OTA package and the OTA package version number in the OTA server can be automatically obtained, if the version is newer than the version number stored in the terminal, the OTA package can be downloaded from the server, and software upgrading can be carried out after the downloading is completed; the OTA software package is an increment difference package, and the part needing to be updated is in the OTA increment package; if the client _ feature.txt file needs to be updated, the OTA packet stores the file in a corresponding path, the terminal automatically updates after downloading the OTA packet, and replaces the old client _ feature.txt file stored in the terminal with the newly downloaded client _ feature.txt file: (2) updating by APK: the APK software package can be put into the OTA package, so that the APK can be upgraded while the OTA package is upgraded, or the APK software package is manually installed after the user downloads the OTA package from the official website.
Referring to fig. 3, a third embodiment of the present invention is:
the method for loading different functions in single software is applied to an actual scene:
setting an attribute ro.product.name to obtain a product identifier, wherein in the embodiment, the product name is used as the product identifier;
when the machine is started, acquiring a product name A through a ro.product.name, starting a feature loading service, wherein the feature loading service is used for loading a function, acquiring a corresponding configuration file client _ A _ feature.txt in a client directory in an OEM partition according to the product name A, and the larger the value of the set version number version is, the newer the configuration file is;
reading the version number of the client _ A _ feature.txt, comparing the version number with the version number saved by the system, wherein the initial value of the version number saved by the system is 0, and if the version number of the client _ A _ feature.txt is less than or equal to the version number saved by the system, ending the loading;
if the version number of the customer _ a _ feature.txt is greater than the version number saved by the system, it is described that the customer _ a _ feature.txt file is loaded for the first time or updated, at this time, the customer _ a _ feature.txt file is read, and the function configuration is obtained, where the present embodiment includes function a, function B, function C, and function D, the corresponding function directories, feature _ A, feature _ B, feature _ C and feature _ D, are obtained under the function file directory feature, the function files in the four function directories are read, and the configuration item is loaded according to the function files to perform system configuration; after the system configuration is finished, updating the version number saved by the system by using the version number of the client _ A _ feature.txt file, and then finishing the loading and restarting the equipment;
in this embodiment, if a configuration file needs to be updated, the server issues an update prompt to the terminal, the terminal obtains a version number of the configuration file client _ a _ feature.txt on the server, and if the version number of the configuration file client _ a _ feature.txt is greater than that of the local client _ a _ feature.txt, the client _ a _ feature.txt on the server is downloaded to replace the local client _ a _ feature.txt, and the system automatically updates when the system is powered on next time.
Referring to fig. 2, a fourth embodiment of the present invention is:
a terminal 1 for loading different functions in a single piece of software, comprising a processor 2, a memory 3 and a computer program stored on the memory 3 and operable on the processor 2, wherein the processor 2 implements the steps of the first embodiment, the second embodiment or the third embodiment when executing the computer program.
To sum up, the present invention provides a method and a terminal for loading different functions in a single software, wherein a file storage structure consisting of an OEM partition, a configuration file directory, a function file directory and a function directory is added, corresponding attributes are set to obtain a product identifier, a configuration file to be loaded in the configuration file directory is determined according to the product identifier, the function file directory to be loaded is determined according to the content of the loaded configuration file, a function file in the function file directory is finally loaded, the function configuration of the system is completed according to the function file, the customization that the same software baseline and the same software version support different functions is realized, that is, the same software automatically loads different configuration files according to the read different product identifiers, the loading of different function files is finally realized, and the same software image package can be adopted for different configurations during upgrading, The same OTA upgrade package or the same APK is carried out, different upgrade packages do not need to be customized according to different products, the later maintenance cost is reduced, and the repeated work is reduced; moreover, the condition of version disorder is reduced by uniformly updating different products, and the different products are updated and maintained by using the same mirror image packet, and then processes such as programming, production and the like are performed more efficiently; meanwhile, the method supports the updating modes of OTA and APK, can only issue the updated configuration file or function file without completely reinstalling the whole software, saves the flow and enhances the stability of the updating process.
The above description is only an embodiment of the present invention, and not intended to limit the scope of the present invention, and all equivalent changes made by using the contents of the present specification and the drawings, or applied directly or indirectly to the related technical fields, are included in the scope of the present invention.
Claims (10)
1. A method for loading different functions in a single piece of software, comprising the steps of:
s1, loading a product identifier, and acquiring a corresponding first configuration file according to the product identifier, wherein the first configuration file comprises a first version number;
s2, acquiring a corresponding function file according to the first configuration file;
and S3, after system configuration is carried out according to the function file, the first version number is saved as the existing version number.
2. The method as claimed in claim 1, wherein the step of loading different functions in a single piece of software further comprises, before the step of S1:
presetting an OEM partition;
presetting a configuration file directory for storing the configuration file in the OEM partition;
presetting a function file directory for storing the function files in the OEM partition;
the S1 specifically includes:
loading a product identifier, and acquiring a corresponding first configuration file from the configuration file directory according to the product identifier, wherein the first configuration file comprises a first version number;
the S2 specifically includes:
and acquiring the corresponding function file from the function file directory according to the first configuration file.
3. The method according to claim 1, wherein the S1 is specifically configured to:
acquiring a stored existing version number, acquiring a corresponding first configuration file according to the product identifier, acquiring a first version number in the first configuration file, comparing the first version number with the existing version number according to a preset rule, and executing the step S2 if the first version number is newer than the existing version number; otherwise, quitting loading;
the initial value of the existing version number is 0.
4. The method of claim 1, wherein the first configuration file in S1 includes product functions;
the S2 specifically includes:
and acquiring a corresponding function file according to the product function.
5. The method of claim 1, further comprising updating the first configuration file to:
requesting a second version number from a server, and comparing the second version number with the first version number according to a preset rule;
if the second version number is newer than the first version number, acquiring a second configuration file corresponding to the second version number;
and updating the first configuration file according to the second configuration file in an OTA or APK mode.
6. A terminal for loading different functions in a single piece of software, comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor when executing the computer program implements the steps of:
s1, loading a product identifier, and acquiring a corresponding first configuration file according to the product identifier, wherein the first configuration file comprises a first version number;
s2, acquiring a corresponding function file according to the first configuration file;
and S3, after system configuration is carried out according to the function file, the first version number is saved as the existing version number.
7. The terminal according to claim 6, wherein the processor before executing the S1 further comprises:
presetting an OEM partition;
presetting a configuration file directory for storing the configuration file in the OEM partition;
presetting a function file directory for storing the function files in the OEM partition;
the S1 specifically includes:
loading a product identifier, and acquiring a corresponding first configuration file from the configuration file directory according to the product identifier, wherein the first configuration file comprises a first version number;
the S2 specifically includes:
and acquiring the corresponding function file from the function file directory according to the first configuration file.
8. The terminal according to claim 6, wherein the S1 is specifically configured to:
acquiring a stored existing version number, acquiring a corresponding first configuration file according to the product identifier, acquiring a first version number in the first configuration file, comparing the first version number with the existing version number according to a preset rule, and executing the step S2 if the first version number is newer than the existing version number; otherwise, quitting loading;
the initial value of the existing version number is 0.
9. The terminal of claim 6, wherein the first configuration file in S1 includes product functions;
the S2 specifically includes:
and acquiring a corresponding function file according to the product function.
10. The terminal of claim 6, wherein the processor, when executing the computer program, further comprises updating the first configuration file by:
requesting a second version number from a server, and comparing the second version number with the first version number according to a preset rule;
if the second version number is newer than the first version number, acquiring a second configuration file corresponding to the second version number;
and updating the first configuration file according to the second configuration file in an OTA or APK mode.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011181371.6A CN112363717B (en) | 2020-10-29 | 2020-10-29 | Method and terminal for loading different functions in single software |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011181371.6A CN112363717B (en) | 2020-10-29 | 2020-10-29 | Method and terminal for loading different functions in single software |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112363717A true CN112363717A (en) | 2021-02-12 |
| CN112363717B CN112363717B (en) | 2024-01-12 |
Family
ID=74513672
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011181371.6A Active CN112363717B (en) | 2020-10-29 | 2020-10-29 | Method and terminal for loading different functions in single software |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112363717B (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104965721A (en) * | 2014-07-10 | 2015-10-07 | 腾讯科技（深圳）有限公司 | Method and apparatus for updating an application |
| CN107729041A (en) * | 2017-07-26 | 2018-02-23 | 上海壹账通金融科技有限公司 | The hot update method of application program, device, terminal and storage medium |
| CN108108181A (en) * | 2017-12-14 | 2018-06-01 | 深圳市雷鸟信息科技有限公司 | The function renewal method, apparatus and computer readable storage medium of application program |
| US20190286437A1 (en) * | 2018-03-16 | 2019-09-19 | Google Llc | Leveraging previously installed application elements to install an application |
-
2020
- 2020-10-29 CN CN202011181371.6A patent/CN112363717B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104965721A (en) * | 2014-07-10 | 2015-10-07 | 腾讯科技（深圳）有限公司 | Method and apparatus for updating an application |
| CN107729041A (en) * | 2017-07-26 | 2018-02-23 | 上海壹账通金融科技有限公司 | The hot update method of application program, device, terminal and storage medium |
| CN108108181A (en) * | 2017-12-14 | 2018-06-01 | 深圳市雷鸟信息科技有限公司 | The function renewal method, apparatus and computer readable storage medium of application program |
| US20190286437A1 (en) * | 2018-03-16 | 2019-09-19 | Google Llc | Leveraging previously installed application elements to install an application |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112363717B (en) | 2024-01-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US6493871B1 (en) | Method and system for downloading updates for software installation | |
| US7657884B2 (en) | Electronic device supporting multiple update agents | |
| CN102622241B (en) | A kind of method for upgrading software and device | |
| US20120210312A1 (en) | Software upgrading method, software upgrading system and client | |
| CN111381858B (en) | Application program upgrading method, server and terminal equipment | |
| CN106951284B (en) | User interface upgrading method and device based on android system application and intelligent terminal | |
| CN112615747B (en) | Method and device for automatically deploying and configuring network equipment | |
| CN111258587A (en) | Method, device, equipment and storage medium for realizing android application plug-in | |
| CN103200271A (en) | Advanced Risc machine (ARM) server and method of automatic installation system thereof | |
| CN104699511A (en) | Plug-in upgrading method and plug-in upgrading device | |
| CN104765624B (en) | Method and device for updating application program of virtual machine | |
| CN110851151B (en) | Method, device, terminal, server and storage medium for pre-installing application | |
| CN110750286B (en) | Management method, device, system, equipment and medium for upgrading Mbn through OTA | |
| CN110413292B (en) | Light application installation method of application program, mobile terminal and storage medium | |
| CN114385251A (en) | Operating system booting method, system, terminal and storage medium based on memory | |
| CN110677732A (en) | Method for starting APK (android package) during startup, storage medium and smart television | |
| CN112328284A (en) | Application program upgrading method, system, equipment and storage medium | |
| CN112363717B (en) | Method and terminal for loading different functions in single software | |
| US9792130B2 (en) | Rebooting to a UEFI application from a UEFI supported system | |
| CN112235639A (en) | Extensible Linux smart television operating system easy to upgrade | |
| CN114221865B (en) | Method, device, equipment and storage medium for realizing business function of Internet of things terminal | |
| CN107783837B (en) | Method and device for performing storage expansion and electronic equipment | |
| CN114443166A (en) | Shared file processing method, device and medium | |
| CN113721959A (en) | Information processing method and device and electronic equipment | |
| JP2021111115A (en) | Communication control system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |