CN116700756A - OTA upgrading method and device, electronic equipment and readable storage medium - Google Patents

OTA upgrading method and device, electronic equipment and readable storage medium Download PDF

Info

Publication number
CN116700756A
CN116700756A CN202310712774.6A CN202310712774A CN116700756A CN 116700756 A CN116700756 A CN 116700756A CN 202310712774 A CN202310712774 A CN 202310712774A CN 116700756 A CN116700756 A CN 116700756A
Authority
CN
China
Prior art keywords
upgraded
equipment
ota
operator
rom version
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202310712774.6A
Other languages
Chinese (zh)
Inventor
陈涌
吴炽强
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Lens Technology Xiangtan Co ltd
Original Assignee
Lens Technology Xiangtan Co ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Lens Technology Xiangtan Co ltd filed Critical Lens Technology Xiangtan Co ltd
Priority to CN202310712774.6A priority Critical patent/CN116700756A/en
Publication of CN116700756A publication Critical patent/CN116700756A/en
Pending legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G06F8/65—Updates
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/70—Software maintenance or management
    • G06F8/71—Version control; Configuration management
    • 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

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Stored Programmes (AREA)

Abstract

The embodiment of the application provides an OTA upgrading method, an OTA upgrading device, electronic equipment and a readable storage medium, and belongs to the technical field of terminals. The method comprises the following steps: configuring an operator mark of the equipment to be upgraded for the equipment to be upgraded; when the equipment to be upgraded is started, determining a target user ROM version line from a plurality of user ROM version lines of an OTA server according to an operator mark of the equipment to be upgraded; the plurality of user ROM version lines are determined and obtained based on a shared ROM version line and a plurality of pre-acquired operator marks; and upgrading the equipment to be upgraded according to the operator mark of the equipment to be upgraded and the target user ROM version line, so that the user ROM version lines of different operators are supported to be upgraded independently through the same shared ROM version line, the equipment of different operators is upgraded, and the maintenance difficulty is reduced.

Description

OTA upgrading method and device, electronic equipment and readable storage medium
Technical Field
The present application relates to the field of terminal technologies, and in particular, to an OTA upgrading method, an OTA upgrading device, an electronic device, and a readable storage medium.
Background
Currently, an operating system OTA (Over-the-air technology) is upgraded to support multiple products, and maintenance of a ROM (Read-Only Memory) and an OTA are separated, and one scheme is to use a multi-branch form, so as to support multiple operators, and the operators can be distinguished by branches on source codes, but seriously affect development efficiency and sharing. In another scheme, a static macro form is adopted, different parameter distinction is introduced during compiling, and source codes can share one branch, but ROM is separated. In the prior art, a plurality of user ROM version lines and upgrade package branches corresponding to a plurality of OTAs need to be prepared for different operators, and the problem of high maintenance difficulty exists.
Disclosure of Invention
In order to solve the technical problems, the embodiment of the application provides an OTA upgrading method, an OTA upgrading device, electronic equipment and a readable storage medium.
In a first aspect, an embodiment of the present application provides an OTA upgrading method, where the method includes:
configuring an operator mark of the equipment to be upgraded for the equipment to be upgraded;
when the equipment to be upgraded is started, determining a target user ROM version line from a plurality of user ROM version lines of an OTA server according to an operator mark of the equipment to be upgraded; the plurality of user ROM version lines are determined and obtained based on a shared ROM version line and a plurality of pre-acquired operator marks;
and upgrading the equipment to be upgraded according to the operator mark of the equipment to be upgraded and the ROM version line of the target user.
In one embodiment, the method further comprises:
and carrying out iterative updating on the ROM of the product line according to upgrading requirements of a plurality of operators to obtain the common ROM version line.
In one embodiment, obtaining each of the user ROM version lines includes:
generating an OTA equipment model of each operator according to the operator mark of each operator;
respectively determining iteration version numbers corresponding to operators in the common ROM version line;
and determining each user ROM version line according to the OTA equipment model number and the iteration version number of each operator.
In an embodiment, the determining each user ROM version line according to the OTA device model number and the iterative version number of each operator includes:
determining identification keywords in each operator mark;
modifying each iteration version number in the corresponding user ROM version line according to each identification keyword to obtain each modified iteration version number;
and establishing a plurality of upgrading projects by taking the OTA equipment model of each operator as a project name, and storing a plurality of modification iteration version numbers corresponding to the OTA equipment model of each operator in each upgrading project to obtain each user ROM version line.
In an embodiment, the determining, according to the operator identifier of the device to be upgraded, a target user ROM version line from a plurality of user ROM version lines of an OTA server includes:
generating an OTA equipment model of the equipment to be upgraded according to the operator marks of the equipment to be upgraded;
and determining the target user ROM version line corresponding to the OTA equipment model of the equipment to be upgraded from a plurality of user ROM version lines, wherein the target user ROM version line comprises a plurality of iteration version numbers.
In one embodiment, the method further comprises:
when the equipment to be upgraded is started, determining an identification keyword of the equipment to be upgraded from an operator mark of the equipment to be upgraded;
and generating an OTA version number of the equipment to be upgraded according to the identification key of the equipment to be upgraded.
In an embodiment, the configuring, for the device to be upgraded, an operator identifier of the device to be upgraded includes:
and setting the operator mark of the equipment to be upgraded in a configuration file, wherein the configuration file is stored in a persistence partition.
In a second aspect, an embodiment of the present application provides an OTA upgrading device, where the OTA upgrading device includes:
the setting module is used for configuring an operator mark of the equipment to be upgraded for the equipment to be upgraded;
the determining module is used for determining a target user ROM version line from a plurality of user ROM version lines of an OTA server according to an operator mark of the equipment to be upgraded when the equipment to be upgraded is started; the plurality of user ROM version lines are determined and obtained based on a shared ROM version line and a plurality of pre-acquired operator marks;
and the upgrading module is used for upgrading the equipment to be upgraded according to the operator mark of the equipment to be upgraded and the ROM version line of the target user.
In a third aspect, an embodiment of the present application provides an electronic device, including a memory and a processor, where the memory is configured to store a computer program, and the computer program executes the OTA upgrading method provided in the first aspect when the processor runs.
In a fourth aspect, an embodiment of the present application provides a computer readable storage medium storing a computer program that, when run on a processor, performs the OTA upgrade method provided in the first aspect.
The OTA upgrading method provided by the application configures the operator mark of the equipment to be upgraded for the equipment to be upgraded; when the equipment to be upgraded is started, determining a target user ROM version line from a plurality of user ROM version lines of an OTA server according to an operator mark of the equipment to be upgraded; the plurality of user ROM version lines are determined and obtained based on a shared ROM version line and a plurality of pre-acquired operator marks; and upgrading the equipment to be upgraded according to the operator mark of the equipment to be upgraded and the target user ROM version line, so that the user ROM version lines of different operators are supported to be upgraded independently through the same shared ROM version line, the equipment of different operators is upgraded, and the maintenance difficulty is reduced.
Drawings
In order to more clearly illustrate the technical solutions of the present application, the drawings that are required for the embodiments will be briefly described, it being understood that the following drawings only illustrate some embodiments of the present application and therefore should not be considered as limiting the scope of the present application. Like elements are numbered alike in the various figures.
Fig. 1 is a flow chart illustrating an OTA upgrading method according to an embodiment of the present application;
FIG. 2 is a schematic diagram of a shared ROM version line according to an embodiment of the present application;
fig. 3 is another flow chart of an OTA upgrading method according to an embodiment of the present application;
FIG. 4 is a schematic diagram of a user ROM version line according to an embodiment of the present application;
fig. 5 is another flow chart of an OTA upgrading method according to an embodiment of the present application;
fig. 6 is another flow chart of an OTA upgrading method according to an embodiment of the present application;
fig. 7 is a schematic flow chart of an OTA upgrading method according to an embodiment of the present application;
fig. 8 is a schematic structural diagram of an OTA upgrading device according to an embodiment of the present application;
fig. 9 shows a schematic structural diagram of an electronic device according to an embodiment of the present application.
Icon: 800-OTA upgrading device, 801-setting module, 802-determining module, 803-upgrading module; 900-electronic device, 901-transceiver, 902-processor, 903-memory.
Detailed Description
The following description of the embodiments of the present application will be made clearly and completely with reference to the accompanying drawings, in which it is apparent that the embodiments described are only some embodiments of the present application, but not all embodiments.
The components of the embodiments of the present application generally described and illustrated in the figures herein may be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of the embodiments of the application, as presented in the figures, is not intended to limit the scope of the application, as claimed, but is merely representative of selected embodiments of the application. All other embodiments, which can be made by a person skilled in the art without making any inventive effort, are intended to be within the scope of the present application.
The terms "comprises," "comprising," "including," or any other variation thereof, are intended to cover a specific feature, number, step, operation, element, component, or combination of the foregoing, which may be used in various embodiments of the present application, and are not intended to first exclude the presence of or increase the likelihood of one or more other features, numbers, steps, operations, elements, components, or combinations of the foregoing.
Furthermore, the terms "first," "second," "third," and the like are used merely to distinguish between descriptions and should not be construed as indicating or implying relative importance.
Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which various embodiments of the application belong. The terms (such as those defined in commonly used dictionaries) will be interpreted as having a meaning that is the same as the context of the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein in connection with the various embodiments of the application.
Example 1
The embodiment of the application provides an OTA upgrading method.
Referring to fig. 1, the ota upgrading method includes steps S101 to S103, and each step is described below.
Step S101, configuring an operator identifier of the device to be upgraded for the device to be upgraded.
In this embodiment, the configuration of the device to be upgraded may be a device such as a mobile phone, a notebook circuit, etc., and the operator identifier of the device to be upgraded may be determined according to the actual situation, for example, may be one of SKT, KT, and LGU. It should be noted that, each device to be upgraded only belongs to one operator, and cannot be configured with a plurality of operator marks, but can be configured with only one operator mark.
Step S102, when the equipment to be upgraded is started, determining a target user ROM version line from a plurality of user ROM version lines of an OTA server according to an operator mark of the equipment to be upgraded.
In this embodiment, the plurality of user ROM version lines are determined based on a common ROM version line and a plurality of operator flags acquired in advance. The plurality of carrier designations may include SKT, KT, and LGU, for example.
In an embodiment, the OTA upgrading method further includes:
and carrying out iterative updating on the ROM of the product line according to upgrading requirements of a plurality of operators to obtain the common ROM version line.
Referring to fig. 2, fig. 2 is a schematic diagram of a common ROM version line, including: AT PXXV 0901S-AT PXXV 0902S-AT PXXV 0903S-AT_PXXV 0904S-AT_PXXV 0905S-AT_PXXV 0906S-AT_PXXV 0907S, there is only one main line. The at_pxxv0901S is a product line ROM, the product line ROM is a base ROM, and based on the product line ROM, the product line ROM is iteratively updated according to the upgrade requirements of 3 operators, namely SKT, KT and LGU, to obtain a common ROM version line shown in fig. 2. The common ROM version line can support SKT, KT, LGU OTA upgrades of the 3 operators through subsequent related processing.
Referring to fig. 3, obtaining each of the user ROM version lines includes:
step S1021, generating an OTA device model of each operator according to the operator identifier of each operator.
Step S1022, determining the iteration version numbers corresponding to the operators in the common ROM version line.
Step S1023, determining each user ROM version line according to the OTA equipment model number and the iteration version number of each operator.
In this embodiment, the operator logo of each operator is used to distinguish the user ROM version lines required by different operators, so that corresponding user ROM version lines are conveniently acquired for different operators based on the common ROM version line. Thus, upgrade services can be provided for different operators through one common ROM version line without providing a plurality of ROM version lines corresponding to a plurality of suppliers.
Referring to fig. 4, a schematic diagram of a plurality of user ROM version lines of the ota server, as shown in fig. 4, the plurality of user ROM version lines may be three user ROM version lines, which are respectively a user ROM version line of an operator SKT, a user ROM version line of an operator KT, and a user ROM version line of an operator LGU, where version numbers correspondingly included are as follows:
SKT:AT_PXXXSV0901S～AT_PXXXSV0902S
AT_PXXXSV0902S～AT_PXXXSV0905S。
KT:AT_PXXXKV0901S～AT_PXXXKV0903S
AT_PXXXKV0903S～AT_PXXXKV0906S。
LGU:AT_PXXXLV0901S～AT_PXXXLV0904S
AT_PXXXLV0904S～AT_PXXXLV0907S。
in this embodiment, a plurality of user ROM version lines may be stored in the OTA server, for example, the user ROM version line of the operator KT shown in fig. 4 may be stored in the OTA server, and the user ROM version line of the operator LGU supports product upgrade of the operator SKT, KT, LGU.
Referring to fig. 5, step S1023 includes:
step S10231, determining identification keywords in each operator mark;
step S10232, modifying each iteration version number in the corresponding user ROM version line according to each identification keyword to obtain each modified iteration version number;
step S10233, using the OTA device model of each operator as a project name, establishing a plurality of upgrade projects, and storing a plurality of modification iteration version numbers corresponding to the OTA device model of each operator in each upgrade project, so as to obtain each user ROM version line.
Referring to fig. 4 again, if the 3 operators are SKT, KT, LGU, it is determined that the identification keywords in the operator flags are S/K/L, so that the version numbers for upgrading different operators can be distinguished by using the keywords S/K/L of the different operator flags. Referring to fig. 2, the iteration version numbers corresponding to SKT include at_pxxxv 0901S-at_pxxxv 0902S-at_pxxxv 0905S, and the version numbers are modified based on the identification key S of the operator SKT, and are adjusted to at_pxxxsv 0901S-at_pxxxsv 0902S-at_pxxxsv 0905S, so as to obtain the user ROM version line of SKT shown in fig. 4.
Please refer to fig. 2 again, the iteration version numbers corresponding to KT include at_pxxxv 0901S-at_pxxxv 0903S-at_pxxxv 0906S, the iteration version numbers are modified based on the identification key K of the operator KT, and are adjusted to at_pxxxkv 0901S-at_pxxxkv 0903S-at_pxxxkv 0906S, so as to obtain the user ROM version line of KT shown in fig. 4.
Referring to fig. 2 again, the iteration version numbers corresponding to the LGU include at_pxxv0901S-at_pxxv0904S-at_pxxv0907S, and the iteration version numbers are modified based on the identification key L of the operator LGU and adjusted to be at_pxxlv 0901S-at_pxxlv 0904S-at_pxxlv 0907S, so as to obtain the user ROM version line of the LGU shown in fig. 4.
Referring to fig. 6, the determining, in step S102, a target user ROM version line from a plurality of user ROM version lines of an OTA server according to the operator flag of the device to be upgraded includes:
step S1024, generating an OTA equipment model of the equipment to be upgraded according to the operator mark;
step S1025, determining the target user ROM version line corresponding to the OTA device model of the device to be upgraded from the plurality of user ROM version lines, where the target user ROM version line includes a plurality of iteration version numbers.
Exemplary, the system attribute is initialized in a boot animation of the device to be upgraded for the first boot (sys. Hls. Rom. Operator is an example). In one embodiment, when the device to be upgraded is started for the first time, if a set attribute configuration, i.e. persistence.sys.hls.rom.operator, the system attributes with the same value, i.e. sys.hls.rom.operator, are synchronously generated. In another embodiment, if the device to be upgraded is first powered on, if there is no above-mentioned persist.sys.hls.rom.operator, a configuration file, such as hnlens.config, is read from the persist partition to generate system attributes persist.sys.hls.operator and sys.hls.rom.operator, and if the operator of the device to be upgraded is marked as SKT, the sys.hls.rom.operator value is SKT.
After the device to be upgraded is started for the first time and the system attribute sys.hls.rom.operator is generated, the device model ro.ota.device, such as AT_PXX-KT, of the device to be upgraded is synchronously and dynamically modified, i.e. the ro.product.model value is added with an operator mark, for example, the operator mark is SKT, KT, LGU. It is further added that, in order to be compatible with the old version, when ro.ota.device is the SKT operator, no suffix is added, and the value is kept as at_pxx.
Exemplary, when the operator of the device to be upgraded is marked as SKT, the values of the system attributes are as follows:
[ ro.ota.device ] [ AT_PXX-SKT ], which is dynamically generated when the AT_PXX-SKT is started, is used for distinguishing equipment models of different operators during upgrading, and uniquely confirms a target user ROM version line.
[ ro.ota.version ] [ AT_PXXSV 0812S ], which is dynamically generated when the AT_PXXSV 0812S is powered on, is used for distinguishing device version numbers of different operators when upgrading.
[ ro.product.model ] [ AT_PXX ], which is generated statically during compiling, is the only model which is unchanged in ROM, and is read by GMS authentication and the like.
[ ro.hls.product.model ] [ AT_PXXK ], which is dynamically generated when the mobile phone is started, is a mobile phone model meeting the requirements of clients, and can be combined into a display version number.
[ ro.hls.product.display_build_number ] [ AT_PXXKV 0812S ], which is dynamically generated when the machine is started, is similar to ro.ota.version, and can be used for display.
And step S103, upgrading the equipment to be upgraded according to the operator mark of the equipment to be upgraded and the ROM version line of the target user.
In this embodiment, since the target user ROM version line has an iteration version number required for the corresponding operator upgrade, the upgrade of the device to be upgraded can be achieved. The same shared ROM version line supports independent upgrade of user ROM version lines corresponding to different operators, and when the user is started for the first time in the user version, different user ROM version lines with different attributes are dynamically generated to distinguish the different user ROM version lines, so that the development and sharing efficiency of the production line can be improved, and the development requirements of different operators can be met through one shared ROM version line.
It can be understood that after the device to be upgraded is started for the first time to initialize the system attribute, the system attribute does not need to be initialized again in the subsequent starting and upgrading processes.
Referring to fig. 7, the OTA upgrading method further includes:
step S104, when the equipment to be upgraded is started, determining an identification keyword of the equipment to be upgraded from an operator mark of the equipment to be upgraded;
step S105, generating an OTA version number of the device to be upgraded according to the identification keyword of the device to be upgraded.
For example, there is only one version number at_pxxv 0812S in the ROM by default, and the at_pxxv 0812S is the system attribute ro. However, when the device to be upgraded is turned on, the OTA version number is dynamically modified, where the OTA version number is a system attribute ro.ota.version, and the system attribute ro.ota.version enables the user ROM version line to distinguish between different operators, for example, S, K, L is used to distinguish SKT, KT, LGU the 3 operators respectively, and exemplary system attributes ro.ota.version of SKT, KT, LGU of the 3 operators are:
SKT:AT_PXXXSV0812S；
KT:AT_PXXXKV0812S；
LGU:AT_PXXXLV0812S。
in an embodiment, the OTA upgrading method further includes:
and setting the operator mark of the equipment to be upgraded in a configuration file, wherein the configuration file is stored in a persistence partition.
Illustratively, a configuration file hnlens. Config is saved in the personast partition, in which an operator flag, e.g., one of SKT, KT, LGU, of the device to be upgraded may be set.
The following are examples of profiles hnlen. Config, e.g., hnlen. Config includes:
thor:/mnt/vendor/persist/hnlens#more hnlens.config；
sys.hls.rom.operator＝SKT。
it should be noted that, the persistent partition reads and writes through the adb command of lscmd in the production line, and the exemplary adb command of lscmd is as follows:
adb shell lscmd cmd_hls_config_write,2,sys.hls.rom.operator,SKT；
adb shell lscmd cmd_hls_config_read,1,sys.hls.rom.operator。
in this embodiment, by storing the operators in the personast partition, dynamically distinguishing different operators by using the operators, the development efficiency is the highest, maintenance with the same functions is minimized, and multiple user ROM version lines can be obtained by using the same ROM version line, so as to support respective upgrades of different operators.
In the OTA upgrading method provided by the embodiment, the operator mark of the equipment to be upgraded is configured for the equipment to be upgraded; when the equipment to be upgraded is started, determining a target user ROM version line from a plurality of user ROM version lines of an OTA server according to an operator mark of the equipment to be upgraded; the plurality of user ROM version lines are determined and obtained based on a shared ROM version line and a plurality of pre-acquired operator marks; and upgrading the equipment to be upgraded according to the operator mark of the equipment to be upgraded and the target user ROM version line, so that the user ROM version lines of different operators are supported to be upgraded independently through the same shared ROM version line, the equipment of different operators is upgraded, and the maintenance difficulty is reduced.
Example 2
In addition, the embodiment of the application provides an OTA upgrading device.
As shown in fig. 8, the OTA upgrading device 800 includes:
a setting module 801, configured to configure an operator identifier of the device to be upgraded for the device to be upgraded;
a determining module 802, configured to determine, when the device to be upgraded is turned on, a target user ROM version line from a plurality of user ROM version lines of an OTA server according to an operator identifier of the device to be upgraded; the plurality of user ROM version lines are determined and obtained based on a shared ROM version line and a plurality of pre-acquired operator marks;
and the upgrading module 803 is configured to upgrade the device to be upgraded according to the operator identifier of the device to be upgraded and the target user ROM version line.
In an embodiment, the OTA upgrading device 800 further includes:
and the updating module is used for carrying out iterative updating on the ROM of the product line according to the upgrading requirements of a plurality of operators to obtain the common ROM version line.
In an embodiment, the OTA upgrading device 800 further includes:
the acquiring module is used for generating OTA equipment models of the operators according to the operator marks of the operators;
respectively determining iteration version numbers corresponding to operators in the common ROM version line;
and determining each user ROM version line according to the OTA equipment model number and the iteration version number of each operator.
In an embodiment, the obtaining module is further configured to determine an identification keyword in each of the operator labels;
modifying each iteration version number in the corresponding user ROM version line according to each identification keyword to obtain each modified iteration version number;
and establishing a plurality of upgrading projects by taking the OTA equipment model of each operator as a project name, and storing a plurality of modification iteration version numbers corresponding to the OTA equipment model of each operator in each upgrading project to obtain each user ROM version line.
In an embodiment, a determining module 802 is configured to generate an OTA device model of the device to be upgraded according to an operator label of the device to be upgraded;
and determining the target user ROM version line corresponding to the OTA equipment model of the equipment to be upgraded from a plurality of user ROM version lines, wherein the target user ROM version line comprises a plurality of iteration version numbers.
In an embodiment, the OTA upgrading device 800 further includes:
the generating module is used for determining the identification key words of the equipment to be upgraded from the operator marks of the equipment to be upgraded when the equipment to be upgraded is started;
and generating an OTA version number of the equipment to be upgraded according to the identification key of the equipment to be upgraded.
In an embodiment, the setting module 801 is further configured to set an operator identifier of the device to be upgraded in a configuration file, where the configuration file is stored in a persistence partition.
The OTA upgrading device 800 provided in this embodiment can implement the OTA upgrading method provided in embodiment 1, and in order to avoid repetition, a description thereof will be omitted.
The OTA upgrading device provided by the embodiment configures an operator mark of the equipment to be upgraded for the equipment to be upgraded; when the equipment to be upgraded is started, determining a target user ROM version line from a plurality of user ROM version lines of an OTA server according to an operator mark of the equipment to be upgraded; the plurality of user ROM version lines are determined and obtained based on a shared ROM version line and a plurality of pre-acquired operator marks; and upgrading the equipment to be upgraded according to the operator mark of the equipment to be upgraded and the target user ROM version line, so that the user ROM version lines of different operators are supported to be upgraded independently through the same shared ROM version line, the equipment of different operators is upgraded, and the maintenance difficulty is reduced.
Example 3
In addition, an embodiment of the present application provides an electronic device, including a memory and a processor, where the memory stores a computer program that, when executed on the processor, performs the OTA upgrading method provided in embodiment 1.
Specifically, referring to fig. 9, the electronic device 900 includes: a transceiver 901, a bus interface, and a processor 902, the processor 902 configured to: configuring an operator mark of the equipment to be upgraded for the equipment to be upgraded;
when the equipment to be upgraded is started, determining a target user ROM version line from a plurality of user ROM version lines of an OTA server according to an operator mark of the equipment to be upgraded; the plurality of user ROM version lines are determined and obtained based on a shared ROM version line and a plurality of pre-acquired operator marks;
and upgrading the equipment to be upgraded according to the operator mark of the equipment to be upgraded and the ROM version line of the target user.
In one embodiment, the processor 902 is further configured to: and carrying out iterative updating on the ROM of the product line according to upgrading requirements of a plurality of operators to obtain the common ROM version line.
In one embodiment, the processor 902 is further configured to: generating an OTA equipment model of each operator according to the operator mark of each operator;
respectively determining iteration version numbers corresponding to operators in the common ROM version line;
and determining each user ROM version line according to the OTA equipment model number and the iteration version number of each operator.
In one embodiment, the processor 902 is further configured to: determining identification keywords in each operator mark;
modifying each iteration version number in the corresponding user ROM version line according to each identification keyword to obtain each modified iteration version number;
and establishing a plurality of upgrading projects by taking the OTA equipment model of each operator as a project name, and storing a plurality of modification iteration version numbers corresponding to the OTA equipment model of each operator in each upgrading project to obtain each user ROM version line.
In one embodiment, the processor 902 is further configured to: generating an OTA equipment model of the equipment to be upgraded according to the operator marks of the equipment to be upgraded;
and determining the target user ROM version line corresponding to the OTA equipment model of the equipment to be upgraded from a plurality of user ROM version lines, wherein the target user ROM version line comprises a plurality of iteration version numbers.
In one embodiment, the processor 902 is further configured to: when the equipment to be upgraded is started, determining an identification keyword of the equipment to be upgraded from an operator mark of the equipment to be upgraded;
and generating an OTA version number of the equipment to be upgraded according to the identification key of the equipment to be upgraded.
In one embodiment, the processor 902 is further configured to: and setting the operator mark of the equipment to be upgraded in a configuration file, wherein the configuration file is stored in a persistence partition.
In an embodiment of the present application, the electronic device 900 further includes: and a memory 903. In fig. 9, a bus architecture may comprise any number of interconnected buses and bridges, with various circuits of the one or more processors, represented in particular by processor 902, and the memory, represented by memory 903, being linked together. The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, power management circuits, etc., which are well known in the art and, therefore, will not be described further herein. The bus interface provides an interface. The transceiver 901 may be a number of elements, i.e., including a transmitter and a receiver, providing a means for communicating with various other apparatus over a transmission medium. The processor 902 is responsible for managing the bus architecture and general processing, and the memory 903 may store data used by the processor 902 in performing operations.
The electronic device 900 provided in the embodiment of the present application may execute the steps of the OTA upgrading method provided in the embodiment 1 of the method, and in order to avoid repetition, the description is omitted here.
Example 4
The present application also provides a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements the OTA upgrading method provided in embodiment 1.
In the present embodiment, the computer readable storage medium may be a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, an optical disk, or the like.
The computer readable storage medium provided in this embodiment may implement the OTA upgrading method provided in embodiment 1, and in order to avoid repetition, a detailed description is omitted here.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or terminal that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or terminal. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article or terminal comprising the element.
From the above description of the embodiments, it will be clear to those skilled in the art that the above-described embodiment method may be implemented by means of software plus a necessary general hardware platform, but of course may also be implemented by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art in the form of a software product stored in a storage medium (e.g. ROM/RAM, magnetic disk, optical disk) comprising instructions for causing a terminal (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to perform the method according to the embodiments of the present application.
The embodiments of the present application have been described above with reference to the accompanying drawings, but the present application is not limited to the above-described embodiments, which are merely illustrative and not restrictive, and many forms may be made by those having ordinary skill in the art without departing from the spirit of the present application and the scope of the claims, which are to be protected by the present application.

Claims (10)

1. An OTA upgrade method, the method comprising:
configuring an operator mark of the equipment to be upgraded for the equipment to be upgraded;
when the equipment to be upgraded is started, determining a target user ROM version line from a plurality of user ROM version lines of an OTA server according to an operator mark of the equipment to be upgraded; the plurality of user ROM version lines are determined and obtained based on a shared ROM version line and a plurality of pre-acquired operator marks;
and upgrading the equipment to be upgraded according to the operator mark of the equipment to be upgraded and the ROM version line of the target user.
2. The OTA upgrade method of claim 1, wherein the method further comprises:
and carrying out iterative updating on the ROM of the product line according to upgrading requirements of a plurality of operators to obtain the common ROM version line.
3. The OTA upgrade method of claim 2 wherein obtaining each of the user ROM version lines comprises:
generating an OTA equipment model of each operator according to the operator mark of each operator;
respectively determining iteration version numbers corresponding to operators in the common ROM version line;
and determining each user ROM version line according to the OTA equipment model number and the iteration version number of each operator.
4. The OTA upgrading method of claim 3 wherein said determining each of said user ROM version lines according to an OTA device model number of each of said operators and an iterative version number thereof comprises:
determining identification keywords in each operator mark;
modifying each iteration version number in the corresponding user ROM version line according to each identification keyword to obtain each modified iteration version number;
and establishing a plurality of upgrading projects by taking the OTA equipment model of each operator as a project name, and storing a plurality of modification iteration version numbers corresponding to the OTA equipment model of each operator in each upgrading project to obtain each user ROM version line.
5. The OTA upgrade method of claim 3 wherein said determining a target user ROM version line from a plurality of user ROM version lines of an OTA server based on the operator logo of the device to be upgraded comprises:
generating an OTA equipment model of the equipment to be upgraded according to the operator marks of the equipment to be upgraded;
and determining the target user ROM version line corresponding to the OTA equipment model of the equipment to be upgraded from a plurality of user ROM version lines, wherein the target user ROM version line comprises a plurality of iteration version numbers.
6. The OTA upgrade method of claim 1, wherein the method further comprises:
when the equipment to be upgraded is started, determining an identification keyword of the equipment to be upgraded from an operator mark of the equipment to be upgraded;
and generating an OTA version number of the equipment to be upgraded according to the identification key of the equipment to be upgraded.
7. The OTA upgrade method of claim 1 wherein the configuring the carrier flag of the device to be upgraded for the device to be upgraded comprises:
and setting the operator mark of the equipment to be upgraded in a configuration file, wherein the configuration file is stored in a persistence partition.
8. An OTA upgrading device, said device comprising:
the setting module is used for configuring an operator mark of the equipment to be upgraded for the equipment to be upgraded;
the determining module is used for determining a target user ROM version line from a plurality of user ROM version lines of an OTA server according to an operator mark of the equipment to be upgraded when the equipment to be upgraded is started; the plurality of user ROM version lines are determined and obtained based on a shared ROM version line and a plurality of pre-acquired operator marks;
and the upgrading module is used for upgrading the equipment to be upgraded according to the operator mark of the equipment to be upgraded and the ROM version line of the target user.
9. An electronic device comprising a memory and a processor, the memory storing a computer program that, when executed by the processor, performs the OTA upgrade method of any one of claims 1-7.
10. A computer readable storage medium, characterized in that it stores a computer program which, when run on a processor, performs the OTA upgrade method of any one of claims 1 to 7.
CN202310712774.6A 2023-06-15 2023-06-15 OTA upgrading method and device, electronic equipment and readable storage medium Pending CN116700756A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202310712774.6A CN116700756A (en) 2023-06-15 2023-06-15 OTA upgrading method and device, electronic equipment and readable storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202310712774.6A CN116700756A (en) 2023-06-15 2023-06-15 OTA upgrading method and device, electronic equipment and readable storage medium

Publications (1)

Publication Number Publication Date
CN116700756A true CN116700756A (en) 2023-09-05

Family

ID=87827319

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202310712774.6A Pending CN116700756A (en) 2023-06-15 2023-06-15 OTA upgrading method and device, electronic equipment and readable storage medium

Country Status (1)

Country Link
CN (1) CN116700756A (en)

Similar Documents

Publication Publication Date Title
CN109542445A (en) A kind of method and apparatus that Android plug-in unit melts hair
CN105630684B (en) Software Development Kit recognition methods and device
CN115204423A (en) Equipment management method and management server
CN109240754B (en) Logic device, method and system for configuring BIOS starting item
CN110750286B (en) Management method, device, system, equipment and medium for upgrading Mbn through OTA
CN104765621A (en) Method and system for deploying program on cluster node
CN112817641A (en) Daughter card initialization method, electronic device and storage medium
EP3091435A1 (en) Resource management method and device for terminal system
CN112083971B (en) Component processing method, device and storage medium
CN108062239B (en) Accelerator loading method and system and accelerator loading device
US20020083226A1 (en) Configuring computer components
CN116700756A (en) OTA upgrading method and device, electronic equipment and readable storage medium
CN116208498A (en) Method, device, equipment and medium for node differential configuration of OpenStack cloud platform
US11671325B1 (en) Determining IoT device compatibility with deployments
CN115544968A (en) Method, system, equipment and storage medium compatible with multi-item equipment tree
CN115576627A (en) Middleware configuration management method, device, equipment, storage medium and operating machine
US11372627B2 (en) System and method for providing integrated development environment (IDE) for programmable software system
CN114510259A (en) Method and device for importing and exporting BIOS configuration based on BMC
CN112527331A (en) Online management method, system and storage medium based on fabric chain code
JP2007026318A (en) Mobile phone, system and method for generating program, and system and method for updating program
CN114090127A (en) Electronic device, loading method and medium of configuration file of electronic device
CN113835708A (en) Internet of things communication protocol processing method, electronic equipment and storage medium
CN113568623A (en) Application deployment method and device and electronic equipment
CN115408031B (en) Application updating method and related equipment
WO2024001168A1 (en) Function management method of network management system, storage medium, and related apparatus

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