CN112363717B - 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
- CN112363717B CN112363717B CN202011181371.6A CN202011181371A CN112363717B CN 112363717 B CN112363717 B CN 112363717B CN 202011181371 A CN202011181371 A CN 202011181371A CN 112363717 B CN112363717 B CN 112363717B
- Authority
- CN
- China
- Prior art keywords
- version number
- configuration file
- function
- file
- acquiring
- 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.)
- Active
Links
- 230000006870 function Effects 0.000 title claims abstract description 170
- 238000000034 method Methods 0.000 title claims abstract description 30
- 238000005192 partition Methods 0.000 claims description 28
- 238000004590 computer program Methods 0.000 claims description 10
- 238000011161 development Methods 0.000 description 15
- 238000012423 maintenance Methods 0.000 description 7
- 238000009434 installation Methods 0.000 description 6
- 238000004519 manufacturing process Methods 0.000 description 5
- 230000009286 beneficial effect Effects 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification 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
- 230000003252 repetitive effect Effects 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
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, a corresponding first configuration file is obtained according to the product identifier, and the first configuration file comprises a first version number; acquiring a corresponding function file according to the first configuration file; after the 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, obtains the product name during loading, loads different configuration files according to the product name at the moment, thereby realizing the loading of different function files and finally completing different system configurations based on different product names.
Description
Technical Field
The present invention relates to the field of software customization, and in particular, to a method and a terminal for loading different functions in a single software.
Background
In doing an item, it is often encountered that different customers in the same item need different functions. If the client A proposes that the function A, the function B, the function C and the function D are needed; customer B proposes that function a, function B and function C are required; the client C proposes that the function A and the function D are needed; the requirements proposed by different customers overlap but are not exactly the same, so the cost of specially developing different software for different customers is too high.
The prior art adopts the following scheme to solve the problems: scheme 1: for clients with different function needs, different software code baselines are used for managing different functions and different image files of the clients; the method is more visual when the modification is required for different clients, but when the number of the projects is large, the modification or maintenance of each project is required for different users, and each modification is required to be carried out on different baselines, so that a large number of repeated works are generated; different mirror image files are required to be made for the same functions in different projects in the production line, so that confusion is easy to cause; when OTA upgrading maintenance is used, the server needs to prepare a set of OTA for different projects of different clients respectively, so that inconvenience is caused;
scheme 2: for clients with different functional 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 common problems occur, only one set of codes needs to be modified, repeated work is reduced, but the production lines are the same, however, the project functions are different, different images are needed, confusion is easy to cause, and in the mode, when OTA upgrading maintenance is carried out, a server is also required to prepare one set of OTA for different projects of different clients respectively;
scheme 3: for clients with different functional requirements, the same software code baseline, the same compiling script and the same mirror image file are used; finally, different functions are managed through pkg (installation package configuration file); specifically, different pkg bags are installed for different clients during production, so that the clients realize function difference after installation; although the functions required by different users are different, a set of software codes is shared, the common problem is that only one code needs to be modified, the repeated workload is reduced, and the same mirror image is finally generated for different projects in a production line, so that confusion is not easy; but this approach fails to achieve an OTA upgrade, once which the software will be confused or errant.
Disclosure of Invention
The technical problems to be solved by the invention are as follows: a method and a terminal for loading different functions in single software are provided, and customization and updating of different functions are realized through the same software code base line.
In order to solve the technical problems, the invention adopts a technical scheme that:
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 the 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 problems, the invention adopts another technical scheme that:
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 the 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, loading 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 function of different products do not need to be distinguished in the development process, the subsequent maintenance and the upgrading are convenient, 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 flow chart of 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 diagram of a terminal loading different functions in a single software according to an embodiment of the present invention;
FIG. 3 is a flowchart showing steps of a method for loading different functions in a single software applied to an actual scene according to an embodiment of the present invention;
description of the reference numerals:
1. a terminal for loading different functions in a single piece of software; 2. a processor; 3. a memory.
Detailed Description
In order to describe the technical contents, the achieved objects and effects of the present invention in detail, the following description will be made with reference to the embodiments in conjunction with the accompanying drawings.
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 the 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 invention are as follows: 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, loading 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 function of different products do not need to be distinguished in the development process, the subsequent maintenance and the upgrading are convenient, 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, before S1, the method further includes:
presetting an OEM partition;
presetting a configuration file catalog for storing the configuration files in the OEM partition;
presetting a function file catalog for storing the function files in the OEM partition;
the S1 specifically comprises the following steps:
loading a product identifier, and acquiring a corresponding first configuration file from the configuration file catalog according to the product identifier, wherein the first configuration file comprises a first version number;
the step S2 is specifically as follows:
and acquiring the corresponding function file from the function file catalog according to the first configuration file.
As can be seen from the above description, a special OEM partition is set, a configuration file directory and a function file directory are set in the OEM partition to store configuration files and function files respectively, and the OEM partition is used as a function partition preset by the system, so that the situation that the files are lost due to misoperation of a user is avoided, and the system is ensured to be capable of being normally configured when the power is on each time.
Further, the S1 specifically is:
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, the loading is exited;
the initial value of the existing version number is 0.
As can be seen from the above description, the version number of the configuration file is obtained and compared with the existing version number stored in the system when the power is on each time, and since the initial existing version number is set to 0 to represent the oldest version, the obtained version number of the file must be newer than the existing version number when the power is on for the first time, the system can obtain the function file corresponding to the configuration file to perform functional configuration, if the configuration file is updated subsequently, the updated version number of the configuration file will automatically load the updated configuration file if the updated version number is newer than the existing version number stored in the system, and the update of the configuration file is realized without dividing different customized functions into a plurality of different installation packages.
Further, the first configuration file in S1 includes a product function;
the step S2 is specifically as follows:
and obtaining a corresponding function file according to the product function.
As can be seen from the above description, according to the function loading corresponding function files of the product stored in the configuration file, different product identifiers correspond to different configuration files, and finally different function files are loaded to configure different function items for the system without making a plurality of different installation packages.
Further, updating the first configuration file is further included:
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, a second configuration file corresponding to the second version number is acquired;
updating the first configuration file according to the second configuration file in an OTA or APK mode.
From the above description, it can be known that the version number of the corresponding configuration file can be obtained from the server and compared with the version number of the configuration file stored by the server, if the version number of the server is newer, the configuration file stored by the server can be updated, the configuration file can be updated by an OTA or APK mode, the configuration file is usually smaller in size, the updating in the OTA mode is stable, the power-down situation is not easy to occur, and better use experience can be provided for the user.
Referring to fig. 2, a terminal for loading different functions in a single software includes a memory, a processor and a computer program stored in the memory and capable of running on the processor, wherein the processor implements 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 the 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, loading 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 function of different products do not need to be distinguished in the development process, the subsequent maintenance and the upgrading are convenient, 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, before S1, the method further includes:
presetting an OEM partition;
presetting a configuration file catalog for storing the configuration files in the OEM partition;
presetting a function file catalog for storing the function files in the OEM partition;
the S1 specifically comprises the following steps:
loading a product identifier, and acquiring a corresponding first configuration file from the configuration file catalog according to the product identifier, wherein the first configuration file comprises a first version number;
the step S2 is specifically as follows:
and acquiring the corresponding function file from the function file catalog according to the first configuration file.
As can be seen from the above description, a special OEM partition is set, a configuration file directory and a function file directory are set in the OEM partition to store configuration files and function files respectively, and the OEM partition is used as a function partition preset by the system, so that the situation that the files are lost due to misoperation of a user is avoided, and the system is ensured to be capable of being normally configured when the power is on each time.
Further, the S1 specifically is:
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, the loading is exited;
the initial value of the existing version number is 0.
As can be seen from the above description, the version number of the configuration file is obtained and compared with the existing version number stored in the system when the power is on each time, and since the initial existing version number is set to 0 to represent the oldest version, the obtained version number of the file must be newer than the existing version number when the power is on for the first time, the system can obtain the function file corresponding to the configuration file to perform functional configuration, if the configuration file is updated subsequently, the updated version number of the configuration file will automatically load the updated configuration file if the updated version number is newer than the existing version number stored in the system, and the update of the configuration file is realized without dividing different customized functions into a plurality of different installation packages.
Further, the first configuration file in S1 includes a product function;
the step S2 is specifically as follows:
and obtaining a corresponding function file according to the product function.
As can be seen from the above description, according to the function loading corresponding function files of the product stored in the configuration file, different product identifiers correspond to different configuration files, and finally different function files are loaded to configure different function items for the system without making a plurality of different installation packages.
Further, the processor, when executing the computer program, further comprises updating a 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, a second configuration file corresponding to the second version number is acquired;
updating the first configuration file according to the second configuration file in an OTA or APK mode.
From the above description, it can be known that the version number of the corresponding configuration file can be obtained from the server and compared with the version number of the configuration file stored by the server, if the version number of the server is newer, the configuration file stored by the server can be updated, the configuration file can be updated by an OTA or APK mode, the configuration file is usually smaller in size, the updating in the OTA mode is stable, the power-down situation is not easy to occur, and better use experience can be provided for the user.
Referring to fig. 1, a first embodiment of the present invention is as follows:
a method of loading different functions in a single piece of software, comprising the steps of;
s1, presetting an OEM partition, presetting a configuration file directory for storing the configuration files in the OEM partition, and presetting a function file directory for storing the function files in the OEM partition;
if a configuration file catalog customer is set, the configuration files customer_A_feature.txt, customer_B_feature.txt and customer_C_feature.txt are stored and generated according to the customization functions of corresponding customers A, B and C respectively; the configuration file includes product functions such as:
customer_A_feature.txt content:
feature_A；
feature_B；
feature_C；
feature_D；
customer_b_feature.txt content:
feature_A；
feature_B；
feature_C；
customer_C_feature.txt content:
feature_A；
feature_D；
in an alternative embodiment, a plurality of function directories are set in the 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 a function a, a function B, a function C and a function D are respectively stored, and parameters, enabling switch values 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 the function files persistence and nv.txt are stored, the attribute persistence.multiple.config=ds of dual-card dual-standby is configured in the function file persistence.txt to indicate that the dual-card dual-standby function is opened, nv.txt configures the nv_uim_hw_sim_config_i parameter of dual-card, the parameter value is 0 to indicate that the item is a single card, the parameter value is 1 to indicate that the item is dual-card, and if the nv_uim_sim_config_i parameter 6907=1 is set, the item is 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 comprises the following steps: loading a product identifier, and acquiring a corresponding first configuration file from the configuration file catalog 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 comprises the following steps: acquiring the corresponding function file from the function file catalog according to the first configuration file, and acquiring the corresponding function file according to the product function;
and S4, after the 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 functions are generally fixed, if a certain client needs to update and release or limit the setting of certain functions, the software image package is generally updated through OTA, because the software image package updates the whole software, if the intercepted risk is larger, the whole software is used as the image package to transmit the excessive consumed flow possibly caused by the oversized image package through OTA, the power failure risk in the upgrading process is improved, and other loopholes are easily introduced into the image package; the present invention proposes a method of loading different functions in a single software, which is different from the first embodiment in that:
further comprising updating the first profile:
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, a second configuration file corresponding to the second version number is acquired;
updating the first configuration file according to the second configuration file in an OTA or APK mode;
s2 specifically comprises the following steps:
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, the loading is exited; the initial value of the existing version number is 0;
in an alternative embodiment, it may also be:
when the power is first applied: s2 specifically comprises the following steps:
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, the loading is exited; the value of the initial existing version number is 0;
s4 specifically comprises the following steps:
after the system configuration is carried out according to the function file, the first version number is used for replacing the initial existing version number as the existing version number;
when power is not first applied: s1 specifically comprises the following steps:
requesting a second version number from a server, comparing the second version number with the existing version number according to a preset rule, and if the second version number is newer than the existing version number, updating the first configuration file corresponding to the first version number; the updating of 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 needed to replace the first configuration file, and the function file corresponding to the second configuration file is updated, so that the whole software package is not needed to be updated, and the configuration file (OEM/customer/customer_feature.txt) in the configuration file directory in the OEM partition or the function file (OEM/feature/feature_x/txt) in the function file directory in the OEM partition can be updated in an OTA or APK mode; wherein, represents wildcards;
the updating of the configuration files in the configuration file catalogue in the OEM partition by means of OTA or APK is specifically: (1) updating by an OTA mode: acquiring the latest OTA software package from a terminal server, specifically, automatically acquiring the OTA package and the OTA package version number in the OTA server after the terminal is started and connected with the network, and downloading the OTA package from the server if the version is newer than the version number stored in the terminal, and upgrading the software 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 customer_feature.txt file needs to be updated, the OTA packet will store the file under the corresponding path, the terminal will automatically update after downloading the OTA packet, and replace the old customer_feature.txt file stored in the terminal with the newly downloaded customer_feature.txt file. (2) update by APK: the APK software package can be put in 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.
Referring to fig. 3, a third embodiment of the present invention is as follows:
the method for loading different functions in the single software is applied to the 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, a product name A is obtained through a ro.product name, a feature loading service is started, the feature loading service is used for loading functions, a corresponding configuration file customer_A_feature.txt under a customer directory in an OEM partition is obtained according to the product name A, and the larger the value of a version number version is set, the newer the configuration file is;
reading the version number of the customer_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 ending loading if the version number of the customer_A_feature.txt is smaller than or equal to the version number saved by the system;
if the version number of the customer_a_feature.txt is greater than the version number stored in the system, it is indicated that the customer_a_feature.txt file is loaded for the first time or has an update, and then the customer_a_feature.txt file is read to obtain the function configuration thereof, where the function configuration includes a function a, a function B, a function C and a function D, and the corresponding function directories feature_ A, feature _ B, feature _c and feature_d are obtained under the function file directory feature, and the function files in the four function directories are read and the system configuration is performed according to the function file loading configuration item; after the system configuration is finished, updating the version number saved by the system by using the version number of the customer_A_feature.txt file, and then finishing loading and restarting the equipment;
in this embodiment, if the update of the configuration file is required, the server issues an update prompt to the terminal, and the terminal obtains the version number of the configuration file customer_a_feature.txt on the server, and if the version number is greater than the version number of the local customer_a_feature.txt, the customer_a_feature.txt on the server is downloaded to replace the local customer_a_feature.txt, and the system is automatically updated when the power is next applied.
Referring to fig. 2, a fourth embodiment of the present invention is as follows:
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 executable on the processor 2, the processor 2 implementing the steps of embodiment one, embodiment two or embodiment three when executing the computer program.
In summary, the invention provides a method and a terminal for loading different functions in a single software, which is provided with a file storage structure formed by an OEM partition, a configuration file directory, a function file directory and a function directory, sets corresponding attributes to obtain product identifiers, determines the configuration file to be loaded in the configuration file directory according to the product identifiers, determines the function file directory to be loaded according to the content in the loaded configuration file, finally loads the function file in the function file directory, completes the function configuration of the system according to the function file, realizes the customization of the same software baseline and the same software version to support different functions, namely, the same software can automatically load different configuration files according to the read different product identifiers, finally realizes the loading of different function files to carry out different configurations, and can adopt the same software mirror package, the same OTA upgrade package or the same APK to carry out the upgrade without customizing different upgrade packages according to different products, thereby reducing the cost of later maintenance and reducing the repetitive work; in addition, the condition of version confusion is reduced by uniformly updating different products, and the processes of updating and maintaining, later programming, production and the like are more efficient by using the same mirror image package for different products; meanwhile, the updating modes of OTA and APK are supported, only updated configuration files or function files can be issued without completely reloading the whole software, the flow is saved, and the stability of the updating process is enhanced.
The foregoing description is only illustrative of the present invention and is not intended to limit the scope of the invention, and all equivalent changes made by the specification and drawings of the present invention, or direct or indirect application in the relevant art, are included in the scope of the present invention.
Claims (2)
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;
s3, after the system configuration is carried out according to the function file, the first version number is saved as the existing version number;
the step S1 further includes:
presetting an OEM partition;
presetting a configuration file catalog for storing the configuration files in the OEM partition;
presetting a function file catalog for storing the function files in the OEM partition;
the S1 specifically comprises the following steps:
loading a product identifier, and acquiring a corresponding first configuration file from the configuration file catalog according to the product identifier, wherein the first configuration file comprises a first version number and a product function;
the step S2 is specifically as follows:
acquiring the corresponding function file from the function file catalog according to the first configuration file; acquiring a corresponding function file according to the product function;
the method also comprises the step of updating the first configuration file;
updating the first configuration file when the power is first applied, the step 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, the loading is exited;
the initial value of the existing version number is 0;
updating the first configuration file when power is not first applied, and the step S1 specifically includes:
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, a second configuration file corresponding to the second version number is acquired;
updating the first configuration file according to the second configuration file in an OTA or APK mode.
2. 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, characterized in that the processor implements 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;
s3, after the system configuration is carried out according to the function file, the first version number is saved as the existing version number;
the processor further includes, prior to executing the S1 of the computer program:
presetting an OEM partition;
presetting a configuration file catalog for storing the configuration files in the OEM partition;
presetting a function file catalog for storing the function files in the OEM partition;
the S1 specifically comprises the following steps:
loading a product identifier, and acquiring a corresponding first configuration file from the configuration file catalog according to the product identifier, wherein the first configuration file comprises a first version number and a product function;
the step S2 is specifically as follows:
acquiring the corresponding function file from the function file catalog according to the first configuration file; acquiring a corresponding function file according to the product function;
the method also comprises the step of updating the first configuration file;
updating the first configuration file when the power is first applied, the step 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, the loading is exited;
the initial value of the existing version number is 0;
updating the first configuration file when power is not first applied, and the step S1 specifically includes:
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, a second configuration file corresponding to the second version number is acquired;
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 CN112363717A (en) | 2021-02-12 |
| CN112363717B true 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 (3)
| 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 |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US11055087B2 (en) * | 2018-03-16 | 2021-07-06 | 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 (3)
| 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 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112363717A (en) | 2021-02-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US6493871B1 (en) | Method and system for downloading updates for software installation | |
| US6098098A (en) | System for managing the configuration of multiple computer devices | |
| US8037198B2 (en) | Firmware upgrade for thin clients using one or more servers | |
| CN105657191B (en) | Application increment upgrading method and system based on Android system | |
| US7657884B2 (en) | Electronic device supporting multiple update agents | |
| CN107870771B (en) | Application program construction and upgrading method and system | |
| CN111258587A (en) | Method, device, equipment and storage medium for realizing android application plug-in | |
| CN106951284B (en) | User interface upgrading method and device based on android system application and intelligent terminal | |
| CN110727503B (en) | Container deployment method, device, equipment, storage medium and container deployment system | |
| CN112615747A (en) | Method and device for automatically deploying and configuring network equipment | |
| CN104765624B (en) | Method and device for updating application program of virtual machine | |
| CN110750286B (en) | Management method, device, system, equipment and medium for upgrading Mbn through OTA | |
| CN114546588A (en) | Task deployment method and device, storage medium and electronic device | |
| JPH09292980A (en) | File distribution system | |
| CN112363717B (en) | Method and terminal for loading different functions in single software | |
| US9792130B2 (en) | Rebooting to a UEFI application from a UEFI supported system | |
| CN112328284A (en) | Application program upgrading method, system, equipment and storage medium | |
| 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 | |
| JP3971642B2 (en) | Content download method and apparatus | |
| JP2021111115A (en) | Communication control system | |
| CN111666090B (en) | Online updating support system for application system extension assembly | |
| CN108664259B (en) | Method and terminal for installing application | |
| CN117251173B (en) | Micro-service item configuration method, micro-service item configuration device and medium | |
| CN109144605A (en) | A kind of applied program processing method and device |
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 |