WO2023020070A1 - 一种升级包的确定方法及服务端 - Google Patents
一种升级包的确定方法及服务端 Download PDFInfo
- Publication number
- WO2023020070A1 WO2023020070A1 PCT/CN2022/096394 CN2022096394W WO2023020070A1 WO 2023020070 A1 WO2023020070 A1 WO 2023020070A1 CN 2022096394 W CN2022096394 W CN 2022096394W WO 2023020070 A1 WO2023020070 A1 WO 2023020070A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- upgrade
- firmware
- target
- whole machine
- smart device
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 57
- 238000012545 processing Methods 0.000 claims description 16
- 238000012797 qualification Methods 0.000 claims description 4
- 238000010586 diagram Methods 0.000 description 19
- 230000003993 interaction Effects 0.000 description 3
- 238000012790 confirmation Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
- H04W8/24—Transfer of terminal data
- H04W8/245—Transfer of terminal data from a network towards a terminal
Definitions
- the present disclosure relates to the technical field of the Internet of Things, and in particular to a method for determining an upgrade package, a server, an electronic device, and a computer storage medium.
- smart devices such as smart home appliances, etc.
- smart devices need to be upgraded.
- the smart device is usually upgraded by means of Firmware Over-The-Air (FOTA) of the mobile terminal.
- FOTA Firmware Over-The-Air
- the specific upgrade method is: the smart device sends the firmware version number of the whole device to the server. After the upgrade instruction, the server sends the whole machine upgrade package to the smart device to upgrade the smart device.
- the parts that make up the smart device are all produced in advance and programmed in advance, the programs in each part cannot be modified or updated, which leads to the inability of the programs in each part to know the firmware version number of the smart device.
- the existing upgrade method cannot support the whole machine FOTA of the smart device.
- the embodiments of the present disclosure provide a method for determining an upgrade package, a server, an electronic device, and a computer storage medium, so as to solve the problem that the existing upgrade method cannot support the whole machine FOTA of the smart device.
- the first aspect of the embodiments of the present disclosure discloses a method for determining an upgrade package, the method comprising:
- the current component version information of each component constituting the smart device is obtained
- a target upgrade task is obtained by matching from multiple preset upgrade tasks, and a target complete machine upgrade package corresponding to the target upgrade task is obtained, each There is a whole machine upgrade package and a whole machine firmware version number corresponding to the upgrade task;
- the second aspect of the embodiment of the present disclosure discloses a server, the server includes:
- the acquiring unit is configured to acquire the current component version information of each component constituting the smart device if the query instruction sent by the user terminal is received;
- the determination unit is configured to use all the current component version information to determine the target complete machine firmware type and the current complete machine firmware version number of the smart device;
- the first processing unit is configured to obtain a target upgrade task from a plurality of preset upgrade tasks according to the target firmware type and all current component version information, and obtain a target corresponding to the target upgrade task A complete machine upgrade package, each of the upgrade tasks has a corresponding complete machine upgrade package and a complete machine firmware version number;
- the sending unit is configured to send the current whole machine firmware version number and the whole machine firmware version number corresponding to the target upgrade task to the user terminal.
- the third aspect of the embodiments of the present disclosure discloses an electronic device configured to run a program, wherein the method for determining an upgrade package as disclosed in the first aspect of the embodiments of the present disclosure is executed when the program is running.
- the fourth aspect of the embodiment of the present disclosure discloses a computer storage medium, the storage medium includes a stored program, wherein when the program is running, the device where the storage medium is located is controlled to execute the upgrade package as disclosed in the first aspect of the embodiment of the present disclosure method of determination.
- the method is as follows: if the query instruction sent by the user terminal is received, obtain the current component version information of each component that constitutes the smart device; use all current components Version information, to determine the target firmware type of the smart device and the current firmware version number; according to the target firmware type and all current component version information, match the target upgrade task from multiple preset upgrade tasks, and obtain A target whole machine upgrade package corresponding to the target upgrade task; sending the current whole machine firmware version number and the whole machine firmware version number corresponding to the target upgrade task to the user terminal.
- the target firmware type of the smart device and the current firmware version number of the whole machine are determined.
- the target whole machine upgrade package is determined by using the target whole machine firmware type and all current component version information.
- the smart device only needs to report the current version information of each component to determine the corresponding target whole machine upgrade package, and the smart device does not need to save or report the whole machine version information, which improves the scope of application of the whole machine FOTA for smart devices.
- FIG. 1 is a flowchart of a method for determining an upgrade package provided by an embodiment of the present disclosure
- FIG. 2 is a schematic diagram of the relationship between the whole machine version information, the upgrade task and the component version information provided by the embodiment of the present disclosure
- Figure 3(a) is a detailed schematic diagram of the whole machine version information provided by the embodiment of the present disclosure
- Figure 3(b) is a detailed schematic diagram of the upgrade task provided by the embodiment of the present disclosure
- Figure 3(c) is a schematic diagram of the details provided by the embodiment of the present disclosure Another detailed schematic diagram of the upgrade task
- FIG. 3(d) is another detailed schematic diagram of the upgrade task provided by the embodiment of the present disclosure
- Figure 4(a) is a detailed schematic diagram of all current component version information of a smart device provided by an embodiment of the present disclosure
- Figure 4(b) is another detailed schematic diagram of all current component version information of a smart device provided by an embodiment of the present disclosure
- Figure 4(c) is another detailed schematic diagram of all the current component version information of the smart device provided by the embodiment of the present disclosure
- Figure 4(d) is another detailed view of all the current component version information of the smart device provided by the embodiment of the present disclosure schematic diagram
- FIG. 5 is a schematic diagram of interaction between a smart device, a server, and a user terminal provided by an embodiment of the present disclosure
- FIG. 6 is a structural block diagram of a server provided by an embodiment of the present disclosure.
- the term "comprises”, “comprises” or any other variation thereof is intended to cover a non-exclusive inclusion such that a process, method, article, or apparatus comprising a set of elements includes not only those elements, but also includes none. other elements specifically listed, or also include elements inherent in such a process, method, article, or apparatus.
- an element defined by the phrase “comprising a " does not exclude the presence of additional identical elements in the process, method, article or apparatus comprising said element.
- the embodiments of the present disclosure provide a method for determining an upgrade package and a server, which determines the target firmware type and current firmware version number of the smart device according to the current component version information of each component uploaded by the smart device.
- the target whole machine upgrade package is determined by using the target whole machine firmware type and all current component version information.
- the smart device only needs to report the current version information of each component to determine the corresponding target whole machine upgrade package, and the smart device does not need to save or report the whole machine version information, so as to improve the scope of application of the whole machine FOTA for smart devices.
- FIG. 1 it shows a flowchart of a method for determining an upgrade package provided by an embodiment of the present disclosure.
- the method for determining an upgrade package is applicable to a server.
- the method for determining an upgrade package includes:
- Step S101 If a query instruction sent by the user terminal is received, obtain current component version information of each component constituting the smart device.
- the current component version information of each component of the smart device is uploaded by the smart device in advance.
- the smart device uploads the current component version information to the server through the M2M (machine to machine) of the server.
- the current component version information at least includes: the sub-firmware type corresponding to the sub-firmware of the component, the sub-firmware software type (indicated by the sub-firmware software identifier) and the sub-firmware software version number.
- step S101 if the FOTA service of the server receives the query instruction sent by the user terminal (such as sent by APP), the FOTA service of the server obtains the information of each component that constitutes the smart device from the database (data base, DB). Current part version information.
- Step S102 Using all current component version information, determine the target firmware type of the smart device and the current firmware version number of the smart device.
- the FOTA console in the server pre-builds a first preset relationship and a second preset relationship
- the first preset relationship includes multiple sets of first corresponding relationships
- the second preset relationship includes multiple sets of first Two correspondences.
- Each set of first correspondences indicates the association between a whole machine firmware version number (the whole machine firmware version number of the smart device) and multiple pieces of component version information (sub-firmware type+sub-firmware software type+sub-firmware software version number)
- Each set of second correspondences indicates an association between a whole machine firmware type and sub-firmware types and sub-firmware software types in multiple pieces of component version information.
- a plurality of parts of the smart device are pre-selected, and according to the part version information (sub-firmware type+sub-firmware software type+sub-firmware software version number) of the selected parts, multiple parts are constructed.
- the first corresponding relationship between the piece of component version information and the firmware version number of the whole machine.
- For each firmware type of the whole machine pre-select multiple components of the smart device, and construct sub-firmware types and sub-firmware software types of multiple component version information according to the sub-firmware type and sub-firmware software type in the component version information of the selected components The second corresponding relationship with the whole machine firmware type.
- step S102 determine the version number of the whole machine firmware that has a corresponding relationship with all current component version information, and use the determined version number of the whole machine firmware as the current whole machine firmware of the smart device version number. It can be understood that, if it is not determined that the version numbers of the whole machine firmware corresponding to all the current component version information are obtained, information indicating that the current whole machine firmware version number is undefined is displayed to the user terminal.
- the second preset relationship determine the whole machine firmware type corresponding to the sub-firmware type and sub-firmware software type of all current component version information, and use the determined whole machine firmware type as the target whole machine firmware type of the smart device.
- the FOTA console on the server side responds to the creation instruction and creates the sub-firmware of each component (such as WIFI module and computer version, etc.).
- the sub-firmware created is based on its corresponding sub-firmware type, sub-firmware software type and sub-firmware software version number. Uniquely identifies.
- the FOTA console on the server responds to the creation command and creates the version information of the whole machine.
- the FOTA console of the server responds to the selection command, selects the sub-firmware of each component corresponding to the created version information of the whole machine, and needs to define the sub-firmware corresponding to the version information of the whole machine.
- “Complete device firmware type alias” and “Complete device firmware version number alias” at the same time, you also need to fill in the "Complete device version information description" for displaying to users.
- a globally unique identifier (equivalent to the whole machine firmware type here) is assigned to the combination of the sub-firmware type of the selected sub-firmware and the value of the sub-firmware software type,
- the corresponding relationship between the whole machine firmware type and the sub-firmware type and sub-firmware software type of the selected sub-firmware is the second corresponding relationship in the aforementioned second preset relationship.
- a combination of the sub-firmware type, sub-firmware software type and sub-firmware software version number (that is, component version information) corresponding to the selected sub-firmware is assigned a
- the global unique identifier (equivalent to the firmware version number of the whole machine here), the corresponding relationship between the firmware version number of the whole machine and the component version information corresponding to the selected sub-firmware is the first preset relationship mentioned above.
- the whole machine version information at least includes the whole machine firmware version number and the whole machine firmware type.
- Step S103 According to the firmware type of the target complete machine and all current component version information, match the target upgrade task from multiple preset upgrade tasks, and obtain the target complete machine upgrade package corresponding to the target upgrade task.
- each upgrade task has a corresponding whole machine upgrade package and a whole machine firmware version number
- each whole machine upgrade package includes a sub-firmware upgrade package of at least one component of the smart device.
- the limiting conditions of the upgrading task are used to limit the firmware type of the whole machine
- the applicable conditions of the upgrading task are used to limit the software version number of the sub-firmware. Only the firmware type of the whole machine meets the limiting conditions of the upgrading task and the sub-firmware Only smart devices whose software version number meets the applicable conditions of the upgrade task can hit the upgrade task.
- the FOTA console on the server responds to the control command and creates an upgrade task corresponding to any created version information of the whole machine. That is to say, an already created whole machine version information can be selected, and an upgrade task corresponding to the selected whole machine version information can be created.
- the firmware type of the whole machine included in the version information of the whole machine corresponding to the upgrade task is used as a limiting condition of the upgrade task.
- the created whole machine version information includes the whole machine firmware version number and the whole machine firmware type.
- the The firmware type of the whole machine corresponding to the selected version information of the whole machine is used as a limiting condition of the created upgrade task (the limiting condition cannot be modified).
- sub-firmware version number in the applicable conditions of the upgrade task can also be set as a wildcard "*”.
- the sub-firmware version number corresponding to a certain component is a wildcard "*”
- each piece of whole machine version information created may correspond to multiple upgrade tasks and multiple component version information, as shown in FIG.
- Each piece of complete machine version information corresponds to n upgrade tasks and m component version information.
- the whole machine version information includes at least the whole machine firmware type, the whole machine firmware version number, the whole machine firmware type alias, the whole machine firmware version number alias, the whole machine version information description and the whole machine upgrade package and other information.
- the upgrade task at least includes the upgrade task name, limited conditions and applicable conditions.
- the component version information at least includes: the sub-firmware type corresponding to the sub-firmware of the component, the sub-firmware software type, the sub-firmware software version number and the sub-firmware software version description, and the component is a WIFI module, a computer version and a custom hardware.
- the sub-firmware upgrade package of the sub-firmware of each component needs to be uploaded.
- the FOTA service at the server determines, from among multiple preset upgrade tasks, the upgrade task whose qualification condition matches the firmware type of the target whole machine as the first upgrade task. From all the first upgrade tasks, it is determined that the first upgrade tasks whose applicable conditions match the sub-firmware software version numbers in all current component version information are the second upgrade tasks.
- the optimal second upgrade task is the second upgrade task with the highest firmware version number and/or the latest creation time. That is to say, when it is determined that multiple second upgrade tasks are obtained, if there is only one second upgrade task with the highest firmware version number of the whole machine, then the second upgrade task with the highest machine version number is taken as the optimal first upgrade task. Second upgrade task; if there are multiple second upgrade tasks with different version numbers of the whole machine firmware, and there are multiple second upgrade tasks with the highest version number of the whole machine firmware, then the multiple second upgrade tasks with the highest version numbers of the whole machine firmware Among the tasks, the second upgrade task with the latest creation time is taken as the optimal second upgrade task.
- the optimal second upgrade task is the second upgrade task with the highest version number of the whole machine firmware and the latest creation time; if each The whole machine firmware version numbers of the second upgrade tasks are the same, and the second upgrade task with the latest creation time is taken as the optimal second upgrade task.
- each upgrade task corresponds to a corresponding whole machine upgrade package
- the whole machine upgrade package corresponding to the target upgrade task is obtained and used as the target whole machine upgrade package.
- Step S104 Send the current firmware version number of the whole machine and the firmware version number of the whole machine corresponding to the target upgrade task to the user terminal.
- the FOTA service of the server sends the current firmware version number of the whole machine and the firmware version number of the whole machine corresponding to the target upgrade task to the user terminal, so that the user can know the current whole machine firmware of the smart device through the user terminal The version number and the firmware version number of the whole machine that can be upgraded.
- the user can determine whether the smart device needs to be upgraded through the user terminal.
- the user terminal sends the device upgrade instruction to the server, and if the server receives the device upgrade instruction sent by the user terminal, it sends the device upgrade instruction to the smart device.
- the user can click a button such as "upgrade now" to send a device upgrade command to the server.
- the smart device can be upgraded without confirmation by the user, that is, after the server sends the current firmware version number of the whole machine and the firmware version number of the whole machine corresponding to the target upgrade task to the user terminal, the server can directly send the The device upgrade command is sent to the smart device.
- the server can directly send the The device upgrade command is sent to the smart device.
- the M2M at the server side if the M2M at the server side receives the device upgrade instruction for upgrading the smart device sent by the user terminal, the M2M at the server end sends the device upgrade instruction to the smart device, and the device upgrade instruction carries the Or, after the server sends the current whole machine firmware version number and the whole machine firmware version number corresponding to the target upgrade task to the user terminal, the M2M at the server side directly sends the device upgrade instruction to the smart device.
- the server after the server sends the device upgrade command to the smart device, the server receives the download command sent by the smart device, and sends the target machine upgrade package to the smart device, so that the smart device can upgrade the components of each component according to the target machine upgrade package. sub-firmware.
- the resource service (CDN) of the server receives the download command sent by the smart device (based on the url of the target machine upgrade package), and sends the target machine upgrade package to the smart device, so that the smart device can be upgraded according to the target machine
- the package upgrades the sub-firmware of each component.
- the target whole machine upgrade package includes a sub-firmware upgrade package corresponding to at least one component of the smart device, and after the target whole machine upgrade package is sent to the smart device, the smart device can parse it through the IoT component (such as a WIFI module)
- the target whole machine upgrade package obtains the sub-firmware upgrade package, and each sub-firmware upgrade package is sent to the corresponding component by the Internet of Things components (such as WIFI module) of the smart device to upgrade the sub-firmware.
- the M2M on the server side receives the component upgrade progress of each component sent by the smart device, and determines the whole machine upgrade progress of the smart device according to the upgrade progress of each component and It is sent to the user terminal, so that the user terminal knows the upgrade status of the whole smart device, without paying attention to the upgrade status of each component separately.
- the M2M on the server After the server sends the target machine upgrade package to the smart device, the M2M on the server generates a device upgrade log corresponding to the smart device (including device upgrade instructions and the progress of each component upgrade), and receives the post-upgrade log sent by the smart device.
- the component version information of each component and store the device upgrade log in the database through the FOTA service on the server side.
- the target whole machine firmware type and the current whole machine firmware version number of the smart device are determined.
- the target whole machine upgrade package is determined by using the target whole machine firmware type and all current component version information, and the target whole machine upgrade package is sent to the smart device to upgrade the sub-firmware of each component.
- the smart device only needs to report the current version information of each component to determine the corresponding target whole machine upgrade package, and the smart device does not need to save or report the whole machine version information, which improves the scope of application of the whole machine FOTA for smart devices.
- FIG. Fig. 4(a) to Fig. 4(d) it should be noted that the content shown in Fig. 3(a) to Fig. 3(d) and Fig. 4(a) to Fig. 4(d) is only for example.
- Figure 3(a) is a detailed diagram of the version information of the whole machine pre-created by the server;
- Figure 3(b) is a detailed schematic diagram of the upgrade task created by the server in advance, and the upgrade task shown in Figure 3(b) is in the following content Represented by "Complete Device Task A-1";
- Figure 3(c) is a detailed schematic diagram of the upgrade task created in advance by the server, and the upgrade task shown in Figure 3(c) is denoted as "Complete Device Task A-1" in the following content -2" means;
- Figure 3(d) is a detailed schematic diagram of the upgrade task created in advance by the server, and the upgrade task shown in Figure 3(d) is represented by "equipment task A-3" in the following content.
- the upgrade tasks shown in Figure 3(b) to Figure 3(d) all have limited conditions and applicable conditions, and "*" in the applicable conditions indicates that all sub-firmware software version numbers are applicable.
- the server can show the first correspondence and the second correspondence corresponding to the version information of the whole machine according to Figure 3(a), Match all the current component version information in Fig. 4(a), and determine that the whole machine firmware version number of the smart device is the whole machine firmware version number 1.0 and the whole machine firmware type is the whole machine firmware type A.
- the firmware type A of the whole machine and all current component version information in FIG. 4( a ) the “device whole machine task A-1” shown in FIG. 3( b ) can be matched.
- the whole machine firmware version number of the smart device is the whole machine firmware version number 2.0
- the upgraded component version information of each component is shown in Figure 3(b)" The content shown in the column of the whole device firmware version A-2.0.
- the server can perform all the functions in Figure 4(b)
- the current component version information is matched to determine that the whole machine firmware version number of the smart device is the whole machine firmware version number 2.0 and the whole machine firmware type is the whole machine firmware type A.
- the current component version information uploaded by the smart device is as shown in FIG. 4(c).
- the server can, according to the first corresponding relationship and the second corresponding relationship corresponding to the whole device version information shown in the column of "equipment firmware version A-3.0" in Figure 3(c), for all the devices in Figure 4(c)
- the current component version information is matched to determine that the whole machine firmware version number of the smart device is the whole machine firmware version number 3.0 and the whole machine firmware type is the whole machine firmware type A.
- the terminal may display information for indicating that no upgrade task is matched to the user terminal.
- the server uses the first correspondence corresponding to the whole machine version information shown in Figure 3(b) to Figure 3(d) relationship and the second corresponding relationship, the corresponding whole machine firmware version number is not matched, but it can be determined that the whole machine firmware type of the smart device is the whole machine firmware type A.
- the server shows the user terminal to indicate the current whole machine firmware The message that the firmware version number of the machine is not defined.
- Figure 4(d) can be matched to obtain the upgrade task shown in Figure 3(b) and Figure 3(c), the firmware version number of the whole machine firmware shown in Figure 3(b) is the whole machine firmware version number 2.0, Fig.
- the whole machine firmware version number of the upgrade task shown in 3(c) is the whole machine firmware version number 3.0.
- the server uses the upgrade task shown in FIG. 3(c) to upgrade the smart device.
- the smart device's The firmware version number of the whole machine is the firmware version number of the whole machine 3.0.
- the above content is an example of how to determine the current firmware version number of the smart device and how to match the upgrade task.
- FIG. 5 the schematic diagram of the interaction between the smart device, the server and the user terminal shown in FIG. 5 is used as an example for illustration.
- the device in Figure 5 (that is, the smart device, referred to as the device in this example) is composed of WIFI module, computer version A, computer version B and custom hardware, and the server includes at least: FOTA console , DB, resource service, FOTA service and M2M.
- the interaction diagram shown in Fig. 5 includes the following steps.
- Step 1-1 The FOTA console on the server side responds to the instructions of the operator to create and manage sub-firmware and the version information of the whole machine.
- Step 1-2 The FOTA console on the server side responds to the instructions of the operator, and creates and manages the upgrade task.
- Step 2-1 The device reports the current component version information of each component to the M2M of the server.
- Step 2-2 The M2M at the server side reports the current component version information of each component to the FOTA service at the server side.
- Step 3-1 The user clicks on the APP of the user terminal to check whether there is an upgradeable firmware version number of the device.
- Step 3-2 The FOTA service on the server side receives the query command from the user terminal, obtains the current component version information of each component, and matches the target upgrade task from the database according to all current component version information, and updates the firmware of the whole machine corresponding to the target upgrade task The version number and the current firmware version number of the device are fed back to the user terminal.
- Step 3-3 After checking the current firmware version number of the device and the firmware version number corresponding to the target upgrade task through the user terminal, the user can click the "Confirm Upgrade” button, and the user terminal will send the device upgrade command to the M2M server on the server. .
- Step 3-4 The M2M at the server sends the device upgrade instruction to the WIFI module of the device.
- Step 3-5 The WIFI module of the device downloads the target whole machine upgrade package corresponding to the target upgrade task from the resource service according to the url in the device upgrade instruction.
- Steps 3-6 The WIFI module of the device sends each sub-firmware upgrade package in the target whole machine upgrade package to the corresponding components, so that each component upgrades its own sub-firmware.
- Step 3-7 The WIFI module of the device sends the component upgrade progress of each component to the M2M of the server.
- Steps 3-8 The M2M at the server sends the upgrade progress of the whole machine determined by the upgrade progress of each component to the user terminal.
- Step 3-9 The M2M at the server sends the device upgrade log including the device upgrade instruction and the upgrade progress of each component to the FOTA service at the server for storage.
- Step 4 The FOTA console on the server can respond to the instructions of the operator and display the device upgrade log to the operator.
- the embodiment of the present disclosure also provides a structural block diagram of a server, the server includes: an acquisition unit 601, a determination unit 602, a second A processing unit 603 and a sending unit 604;
- the acquiring unit 601 is configured to acquire the current component version information of each component constituting the smart device if a query instruction sent by the user terminal is received.
- the determining unit 602 is configured to use all current component version information to determine the target whole machine firmware type and the current whole machine firmware version number of the smart device.
- the determination unit 602 is specifically configured to: according to the first preset relationship, determine the firmware version number of the whole machine that has a corresponding relationship with all current component version information, and use the determined firmware version number of the whole machine as the current version number of the smart device.
- the firmware version number of the whole machine, the first preset relationship includes multiple sets of first correspondences, and each set of first correspondences indicates the association between a firmware version number of the whole machine and multiple pieces of component version information; according to the second preset relationship , determine the whole machine firmware type that has a corresponding relationship with the sub-firmware type and sub-firmware software type of all current component version information, and use the determined whole machine firmware type as the target whole machine firmware type of the smart device, and the second preset relationship includes multiple A group of second correspondences, each group of second correspondences indicates the association between a whole machine firmware type and sub-firmware types and sub-firmware software types of multiple pieces of component version information.
- the first processing unit 603 is configured to obtain a target upgrade task from a plurality of preset upgrade tasks according to the firmware type of the target complete machine and all current component version information, and obtain a target complete machine upgrade package corresponding to the target upgrade task, Each upgrade task has a corresponding whole machine upgrade package and new whole machine firmware version number.
- the sending unit 604 is configured to send the current whole machine firmware version number and the whole machine firmware version number corresponding to the target upgrade task to the user terminal.
- the target whole machine firmware type and the current whole machine firmware version number of the smart device are determined.
- the target whole machine upgrade package is determined by using the target whole machine firmware type and all current component version information.
- the smart device only needs to report the current version information of each component to determine the corresponding target whole machine upgrade package, and the smart device does not need to save or report the whole machine version information, which improves the scope of application of the whole machine FOTA for smart devices.
- the server further includes:
- the second processing unit is configured to send the device upgrade instruction to the smart device.
- the third processing unit is configured to receive the download instruction sent by the smart device, and send the target whole machine upgrade package to the smart device, so that the smart device upgrades the sub-firmware of each component according to the target whole machine upgrade package, and the target whole machine upgrade package contains at least one A sub-firmware upgrade package for a component.
- the third processing unit is further configured to: receive the component upgrade progress of each component sent by the smart device; determine the whole machine upgrade progress of the smart device according to the upgrade progress of each component and send it to the user terminal.
- the third processing unit is further configured to: generate a device upgrade log corresponding to the smart device, and receive component version information of each component after upgrading sent by the smart device.
- each upgrade task includes limited conditions and applicable conditions;
- the first processing unit includes: a first determination module, a second determination module, a processing module and an acquisition module, and the execution principles of each module for:
- the first determination module is configured to determine, from a plurality of preset upgrade tasks, that the upgrade task whose qualification condition matches the target firmware type is the first upgrade task.
- the second determination module is configured to determine, from all the first upgrade tasks, that the first upgrade task whose applicable conditions match the sub-firmware software version numbers in all current component version information is the second upgrade task.
- the processing module is set to determine that the second upgrading task is the target upgrading task if the number of the second upgrading task is 1; if the number of the second upgrading task is greater than 1, determine the optimal second upgrading task as the target upgrading task, and the optimal
- the second upgrade task is the second upgrade task with the highest firmware version number and/or the latest creation time.
- the acquisition module is set to acquire the target machine upgrade package corresponding to the target upgrade task.
- an embodiment of the present disclosure further provides an electronic device configured to run a program, wherein, when the program is running, the method for determining an upgrade package as mentioned in the foregoing embodiments of the present disclosure is executed.
- an embodiment of the present disclosure further provides a computer storage medium, the storage medium includes a stored program, wherein, when the program is running, the device where the storage medium is located is controlled to perform the determination of the upgrade package as mentioned in the above-mentioned embodiments of the present disclosure. method.
- the embodiments of the present disclosure provide a method for determining an upgrade package and a server.
- the server determines the target firmware type of the smart device and the current firmware of the whole device according to the current component version information of each component uploaded by the smart device. version number.
- the server determines the target whole machine upgrade package by using the target whole machine firmware type and all current component version information, and sends the target whole machine upgrade package to the smart device to upgrade the sub-firmware of each component.
- the smart device only needs to report the current version information of each component to determine the corresponding target whole machine upgrade package, and the smart device does not need to save or report the whole machine version information, which improves the scope of application of the whole machine FOTA for smart devices.
- each embodiment in this specification is described in a progressive manner, the same and similar parts of each embodiment can be referred to each other, and each embodiment focuses on the differences from other embodiments.
- the description is relatively simple, and for related parts, please refer to the part of the description of the method embodiment.
- the systems and system embodiments described above are only illustrative, and the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is It can be located in one place, or it can be distributed to multiple network elements. Part or all of the modules can be selected according to actual needs to achieve the purpose of the solution of this embodiment. It can be understood and implemented by those skilled in the art without creative effort.
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Databases & Information Systems (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
- Information Transfer Between Computers (AREA)
Abstract
本公开提供了一种升级包的确定方法、服务端、电子设备及计算机存储介质，该方法为：若接收到用户终端发送的查询指令，获取构成智能设备的各个部件的当前部件版本信息；利用所有当前部件版本信息，确定智能设备的目标整机固件类型和当前整机固件版本号；根据目标整机固件类型和所有当前部件版本信息，从多个预设的升级任务中匹配得到目标升级任务，并获取与目标升级任务对应的目标整机升级包；将当前整机固件版本号和目标升级任务对应的整机固件版本号发送至用户终端。智能设备仅需上报各个部件的当前版本信息即可确定对应的目标整机升级包，智能设备不需要保存或上报整机版本信息，提高对智能设备进行整机FOTA的适用范围。
Description
本公开要求于2021年8月16日提交中国专利局、申请号为202110937885.8、发明名称“一种升级包的确定方法及服务端”的中国专利申请的优先权，其全部内容通过引用结合在本公开中。
本公开涉及物联网技术领域，具体涉及一种升级包的确定方法、服务端、电子设备及计算机存储介质。
随着物联网的发展，为保障智能设备(如智能家电等)的稳定运行，需对智能设备进行升级。
目前通常以移动终端的空中下载软件升级(Firmware Over-The-Air，FOTA)方式对智能设备进行整机升级，具体升级方式为：智能设备向服务端发送整机固件版本号，当获取用户的升级指令后，服务端向智能设备发送整机升级包以对智能设备进行升级。但是，由于构成智能设备的零部件都是提前生产且预先烧写程序，无法修改或更新各个零部件中的程序，也就导致各个零部件中的程序无法获悉智能设备的整机固件版本号，进而导致现有升级方式不能支持智能设备的整机FOTA。
发明内容
有鉴于此，本公开实施例提供一种升级包的确定方法、服务端、电子设备及计算机存储介质，以解决现有升级方式不能支持智能设备的整机FOTA的问题。
为实现上述目的，本公开实施例提供如下技术方案：
本公开实施例第一方面公开一种升级包的确定方法，所述方法包括：
若接收到用户终端发送的查询指令，获取构成智能设备的各个部件的当前部件版本信息；
利用所有所述当前部件版本信息，确定所述智能设备的目标整机固件类型和当前整机固件版本号；
根据所述目标整机固件类型和所有所述当前部件版本信息，从多个预设的升级任务中匹配得到目标升级任务，并获取与所述目标升级任务对应的目标整机升级包，每个所述升级任务存在与之对应的整机升级包和整机固件版本号；
将所述当前整机固件版本号和所述目标升级任务对应的整机固件版本号发送至所述用户终端。
本公开实施例第二方面公开一种服务端，所述服务端包括：
获取单元，设置为若接收到用户终端发送的查询指令，获取构成智能设备的各个部件的当前部件版本信息；
确定单元，设置为利用所有所述当前部件版本信息，确定所述智能设备的目标整机固件类型和当前整机固件版本号；
第一处理单元，设置为根据所述目标整机固件类型和所有所述当前部件版本信息，从多个预设的升级任务中匹配得到目标升级任务，并获取与所述目标升级任务对应的目标整机升级包，每个所述升级任务存在与之对应的整机升级包和整机固件版本号；
发送单元，设置为将所述当前整机固件版本号和所述目标升级任务对应的整机固件版本号发送至所述用户终端。
本公开实施例第三方面公开一种电子设备，所述电子设备设置为运行程序，其中，所述程序运行时执行如本公开实施例第一方面公开的升级包的确定方法。
本公开实施例第四方面公开一种计算机存储介质，所述存储介质包括存储程序，其中，在所述程序运行时控制所述存储介质所在设备执行如本公开实施例第一方面公开的升级包的确定方法。
基于上述本公开实施例提供的一种升级包的确定方法及服务端，该方法为：若接收到用户终端发送的查询指令，获取构成智能设备的各个部件的当前部件版本信息；利用所有当前部件版本信息，确定智能设备的目标整机固 件类型和当前整机固件版本号；根据目标整机固件类型和所有当前部件版本信息，从多个预设的升级任务中匹配得到目标升级任务，并获取与目标升级任务对应的目标整机升级包；将当前整机固件版本号和目标升级任务对应的整机固件版本号发送至用户终端。本方案中，根据智能设备上传的各个部件的当前部件版本信息，确定智能设备的目标整机固件类型和当前整机固件版本号。利用目标整机固件类型和所有当前部件版本信息确定目标整机升级包。智能设备仅需上报各个部件的当前版本信息即可确定对应的目标整机升级包，智能设备不需要保存或上报整机版本信息，提高对智能设备进行整机FOTA的适用范围。
为了更清楚地说明本公开实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本公开的实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据提供的附图获得其他的附图。
图1为本公开实施例提供的一种升级包的确定方法的流程图；
图2为本公开实施例提供的整机版本信息、升级任务和部件版本信息之间的关系示意图；
图3(a)为本公开实施例提供的整机版本信息的详情示意图；图3(b)为本公开实施例提供的升级任务的详情示意图；图3(c)为本公开实施例提供的升级任务的另一详情示意图；图3(d)为本公开实施例提供的升级任务的另一详情示意图；
图4(a)为本公开实施例提供的智能设备的所有当前部件版本信息的详情示意图；图4(b)为本公开实施例提供的智能设备的所有当前部件版本信息的另一详情示意图；图4(c)为本公开实施例提供的智能设备的所有当前部件版本信息的另一详情示意图；图4(d)为本公开实施例提供的智能设备的所有当前部件版本信息的另一详情示意图；
图5为本公开实施例提供的智能设备、服务端及用户终端的交互示意图；
图6为本公开实施例提供的一种服务端的结构框图。
下面将结合本公开实施例中的附图，对本公开实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本公开一部分实施例，而不是全部的实施例。基于本公开中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本公开保护的范围。
在本申请中，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者设备不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者设备所固有的要素。在没有更多限制的情况下，由语句“包括一个......”限定的要素，并不排除在包括所述要素的过程、方法、物品或者设备中还存在另外的相同要素。
由背景技术可知，在以移动终端的空中下载软件升级(Firmware Over-The-Air，FOTA)方式对智能设备进行整机升级时，智能设备向服务端发送整机固件版本号，并由服务端向智能设备发送整机升级包以对智能设备进行升级。但是由于构成智能设备的零部件都是提前生产且预先烧写程序，无法修改或更新各个零部件中的程序，导致各个零部件中的程序无法获悉智能设备的整机固件版本号，进而导致现有升级方式不能支持智能设备的整机FOTA。
因此，本公开实施例提供一种升级包的确定方法及服务端，根据智能设备上传的各个部件的当前部件版本信息，确定智能设备的目标整机固件类型和当前整机固件版本号。利用目标整机固件类型和所有当前部件版本信息确定目标整机升级包。智能设备仅需上报各个部件的当前版本信息即可确定对应的目标整机升级包，智能设备不需要保存或上报整机版本信息，以提高对智能设备进行整机FOTA的适用范围。
参见图1，示出了本公开实施例提供的一种升级包的确定方法的流程图，该升级包的确定方法适用于服务端，该升级包的确定方法包括：
步骤S101：若接收到用户终端发送的查询指令，获取构成智能设备的各个部件的当前部件版本信息。
需要说明的是，智能设备的各个部件的当前部件版本信息由该智能设备预先上传，具体实现中，智能设备通过服务端的M2M(machine to machine)将该当前部件版本信息上传至服务端中，部件的当前部件版本信息至少包含：部件的子固件对应的子固件类型、子固件软件类型(以子固件软件标识来表示)和子固件软件版本号。
在具体实现步骤S101的过程中，若服务端的FOTA服务接收到用户终端发送(如通过APP发送)的查询指令，该服务端的FOTA服务从数据库(data base，DB)获取构成智能设备的各个部件的当前部件版本信息。
步骤S102：利用所有当前部件版本信息，确定智能设备的目标整机固件类型和当前整机固件版本号。
需要说明的是，服务端中的FOTA控制台预先构建第一预设关系和第二预设关系，该第一预设关系包含多组第一对应关系，该第二预设关系包含多组第二对应关系。每组第一对应关系指示一个整机固件版本号(智能设备的整机固件版本号)与多条部件版本信息(子固件类型+子固件软件类型+子固件软件版本号)之间的关联关系。每组第二对应关系指示一个整机固件类型与多条部件版本信息中的子固件类型和子固件软件类型之间的关联关系。
也就是说，针对每个整机固件版本号，预先选择智能设备的多个部件，根据所选择的部件的部件版本信息(子固件类型+子固件软件类型+子固件软件版本号)，构建多条部件版本信息与该整机固件版本号之间的第一对应关系。针对每个整机固件类型，预先选择智能设备的多个部件，根据所选择的部件的部件版本信息中的子固件类型和子固件软件类型，构建多条部件版本信息的子固件类型和子固件软件类型与该整机固件类型之间的第二对应关系。
在具体实现步骤S102的过程中，根据第一预设关系，确定与所有当前部件版本信息具有对应关系的整机固件版本号，将所确定的整机固件版本号作为智能设备的当前整机固件版本号。可以理解的是，如果未确定得到与所有当前部件版本信息具有对应关系的整机固件版本号，则向用户终端展示用于指示当前整机固件版本号未定义的信息。
根据第二预设关系，确定与所有当前部件版本信息的子固件类型和子固件软件类型具有对应关系的整机固件类型，将所确定的整机固件类型作为智 能设备的目标整机固件类型。
为更好解释说明如何创建第一预设关系和第二预设关系，通过以下过程A1至A3进行解释说明。
A1、服务端的FOTA控制台响应创建指令，创建各个部件(如WIFI模块和电脑版等)的子固件，所创建的子固件以与其对应的子固件类型、子固件软件类型和子固件软件版本号作为唯一标识。
可以理解的是，在创建各个子固件时，需上传各个子固件对应的子固件升级包并填写相应的子固件软件版本描述。
A2、服务端的FOTA控制台响应创建指令，创建整机版本信息。
可以理解的是，在创建整机版本信息时，服务端的FOTA控制台响应选择指令，选择与所创建的整机版本信息对应的各个部件的子固件，并需定义与该整机版本信息对应的“整机固件类型别名”和“整机固件版本号别名”，与此同时还需填写用于向用户展示的“整机版本信息描述”。
当选择与所创建的整机版本信息对应的子固件之后，对所选择的子固件的子固件类型和子固件软件类型的值的组合分配一个全局唯一标识(此处相当于整机固件类型)，该整机固件类型与所选择的子固件的子固件类型和子固件软件类型之间的对应关系即为前述提及第二预设关系中的第二对应关系。
当选择与所创建的整机版本信息对应的子固件之后，对所选择的子固件对应的子固件类型、子固件软件类型和子固件软件版本号(也就是部件版本信息)的值的组合分配一个全局唯一标识(此处相当于整机固件版本号)，该整机固件版本号与所选择的子固件对应的部件版本信息之间的对应关系即为前述提及第一预设关系中的第一对应关系。
也就是说，整机版本信息至少包含整机固件版本号和整机固件类型。
A3、针对所创建的整机版本信息，将该整机版本信息所对应的所有子固件的子固件升级包进行打包，得到对应的整机升级包。
通过上述过程A1至A3所示出的内容，可创建多条整机版本信息及与其对应的整机固件版本号、整机固件类型、第一对应关系和第二对应关系。
步骤S103：根据目标整机固件类型和所有当前部件版本信息，从多个预设的升级任务中匹配得到目标升级任务，并获取与目标升级任务对应的目标 整机升级包。
需要说明的是，每个升级任务存在与之对应的整机升级包和整机固件版本号，每个整机升级包包含智能设备的至少一个部件的子固件升级包。对于每个升级任务，该升级任务的限定条件用于限定整机固件类型，该升级任务的适用条件用于限定子固件软件版本号，只有整机固件类型满足该升级任务的限定条件且子固件软件版本号满足该升级任务的适用条件的智能设备，才能命中该升级任务。
为更好解释说明如何创建升级任务，结合上述过程A1至A3的内容，通过过程A4至A6进行解释说明。
A4、服务端的FOTA控制台响应控制指令，创建任一已创建好的整机版本信息对应的升级任务。也就是说，可选择一个已创建好的整机版本信息，创建与所选择的整机版本信息对应的升级任务。
A5、将与升级任务对应的整机版本信息所包含的整机固件类型，作为该升级任务的限定条件。
可以理解的是，由上述过程A1至A3内容可知，所创建好的整机版本信息包含整机固件版本号和整机固件类型，在创建所选择的整机版本信息对应的升级任务时，将该所选择的整机版本信息对应的整机固件类型作为所创建的升级任务的限定条件(该限定条件不可修改)。
A6、对于整机版本信息对应的升级任务，将预先选择的各个部件(与创建整机版本信息所选择的部件一致，该整机版本信息与升级任务对应)对应的子固件版本号作为该升级任务的适用条件，需要说明的是，可根据实际需求修改选择哪些子固件版本号作为该升级任务的适用条件。
进一步需要说明的是，升级任务的适用条件中的子固件版本号也可设置为通配符“*”，某一部件对应的子固件版本号为通配符“*”时，表示该升级任务的适用条件适用于该部件对应的子固件的所有版本。
可以理解的是，所创建的每条整机版本信息可对应多个升级任务和多个部件版本信息，如图2示出的整机版本信息、升级任务和部件版本信息之间的关系示意图。每条整机版本信息对应n个升级任务和m个部件版本信息。整机版本信息至少包含整机固件类型、整机固件版本号、整机固件类型别名、整机固件版本号别名、整机版本信息描述和整机升级包等信息。升级任务至少 包含升级任务名称、限定条件和适用条件。部件版本信息至少包含：部件的子固件对应的子固件类型、子固件软件类型、子固件软件版本号和子固件软件版本描述，该部件为WIFI模块、电脑版和自定义硬件等部件。于此同时，还需上传各个部件的子固件的子固件升级包。
在具体实现步骤S103的过程中，服务端的FOTA服务从多个预设的升级任务中，确定限定条件与目标整机固件类型相匹配的升级任务为第一升级任务。从所有第一升级任务中，确定适用条件与所有当前部件版本信息中的子固件软件版本号相匹配的第一升级任务为第二升级任务。
若第二升级任务的数量为1，确定第二升级任务为目标升级任务。
若第二升级任务的数量大于1，确定最优的第二升级任务为目标升级任务，最优的第二升级任务为整机固件版本号最高和/或创建时间最新的第二升级任务。也就是说，在确定得到多个第二升级任务的情况下，若整机固件版本号最高的第二升级任务仅存在1个，则将机版本号最高的第二升级任务作为最优的第二升级任务；若存在多个整机固件版本号不同的第二升级任务，且整机固件版本号最高的第二升级任务存在多个，则在整机固件版本号最高的多个第二升级任务中，将创建时间最新的第二升级任务作为最优的第二升级任务，此时该最优的第二升级任务为整机固件版本号最高且创建时间最新的第二升级任务；若各个第二升级任务的整机固件版本号均相同，则将创建时间最新的第二升级任务作为最优的第二升级任务。
由前述内容可知，每个升级任务对应存在相应的整机升级包，获取与目标升级任务对应的整机升级包并将其作为目标整机升级包。
步骤S104：将当前整机固件版本号和目标升级任务对应的整机固件版本号发送至用户终端。
可以理解的是，由前述内容可知，每个升级任务对应存在相应的整机固件版本号，将目标升级任务所对应的整机固件版本号作为升级后的整机固件版本号，相当于智能设备可升级得到的整机固件版本号。
在具体实现步骤S104的过程中，服务端的FOTA服务将当前整机固件版本号和目标升级任务对应的整机固件版本号发送至用户终端，使用户通过该用户终端了解智能设备的当前整机固件版本号和可升级得到的整机固件版本号。
可选的，在将当前整机固件版本号和目标升级任务对应的整机固件版本号发送至用户终端之后，用户可通过用户终端确定是否需要对智能设备进行升级，当用户确定需对智能设备进行升级时，用户终端将设备升级指令发送至服务端，若服务端接收到用户终端发送的设备升级指令，将设备升级指令发送给智能设备。服务端的FOTA服务将当前整机固件版本号和目标升级任务对应的整机固件版本号发送至用户终端后，用户可通过点击诸如“立即升级”的按键，向服务端发送设备升级指令。
需要说明的是，也可不需要通过用户确定才能对智能设备进行升级，即服务端将当前整机固件版本号和目标升级任务对应的整机固件版本号发送至用户终端之后，服务端可直接将设备升级指令发送给智能设备。在此对于如何发送设备升级指令的方式不做具体限定。
在一些具体实施例中，若服务端的M2M接收到用户终端发送的用于升级智能设备的设备升级指令，服务端的M2M将该设备升级指令发送给智能设备，该设备升级指令携带用于下载目标整机升级包的url；或者，服务端将当前整机固件版本号和目标升级任务对应的整机固件版本号发送至用户终端之后，服务端的M2M直接将该设备升级指令发送给智能设备。
可选的，服务端将设备升级指令发送给智能设备后，服务端接收智能设备发送的下载指令，将目标整机升级包发送给智能设备，使智能设备根据目标整机升级包升级各个部件的子固件。
在具体实现中，服务端的资源服务(CDN)接收智能设备发送的下载指令(基于目标整机升级包的url发送)，将目标整机升级包发送给智能设备，使智能设备根据目标整机升级包升级各个部件的子固件。
可以理解的是，目标整机升级包包含智能设备的至少一个部件对应的子固件升级包，在将目标整机升级包发送至智能设备后，智能设备可通过物联部件(如WIFI模块)解析该目标整机升级包得到子固件升级包，并由智能设备的物联部件(如WIFI模块)将各个子固件升级包发送至对应的部件进行子固件的升级。
可选的，服务端将目标整机升级包发送给智能设备之后，服务端的M2M接收智能设备发送的每个部件的部件升级进度，并根据每个部件升级进度确 定智能设备的整机升级进度并将其发送给用户终端，使用户终端了解该智能设备的整机升级情况，而不需要分别关注各个部件的升级情况。
可选的，服务端将目标整机升级包发送给智能设备之后，服务端的M2M生成与智能设备对应的设备升级日志(包含设备升级指令和各个部件升级进度)，并接收智能设备发送的升级后的每个部件的部件版本信息，并通过服务端的FOTA服务将该设备升级日志存储至数据库中。
在本公开实施例中，根据智能设备上传的各个部件的当前部件版本信息，确定智能设备的目标整机固件类型和当前整机固件版本号。利用目标整机固件类型和所有当前部件版本信息确定目标整机升级包，将目标整机升级包发送给智能设备对各个部件的子固件进行升级。智能设备仅需上报各个部件的当前版本信息即可确定对应的目标整机升级包，智能设备不需要保存或上报整机版本信息，提高对智能设备进行整机FOTA的适用范围。
为更好解释说明上述本公开实施例图1中所涉及的如何确定智能设备的当前整机固件版本号和如何匹配升级任务等内容，通过图3(a)至图3(d)，以及通过图4(a)至图4(d)，需要说明的是图3(a)至图3(d)以及图4(a)至图4(d)示出的内容仅用于举例。
图3(a)为服务端预先创建的整机版本信息的详情示意图；图3(b)为服务端预先创建的升级任务的详情示意图，图3(b)示出的升级任务在以下内容中以“设备整机任务A-1”表示；图3(c)为服务端预先创建的升级任务的详情示意图，图3(c)示出的升级任务在以下内容中以“设备整机任务A-2”表示；图3(d)为服务端预先创建的升级任务的详情示意图，图3(d)示出的升级任务在以下内容中以“设备整机任务A-3”表示。图3(b)至图3(d)所示出的升级任务均设置限定条件和适用条件，适用条件中的“*”表示所有子固件软件版本号均适用。
可以理解的是，在图3(b)中“设备整机固件版本A-2.0”一栏所包含的信息为：利用“设备整机任务A-1”这一升级任务对智能设备进行升级后所得到的整机固件类型、整机固件版本号(2.0)和各个部件版本信息；图3(c)和图3(d)所包含的内容的相关解释，可参见关于图3(b)的解释，在此不再赘述。
若智能设备所上传的所有当前部件版本信息为如图4(a)示出的内容，服务端可根据图3(a)示出整机版本信息对应的第一对应关系和第二对应关系，对图4(a)中的所有当前部件版本信息进行匹配，确定该智能设备的整机固件版本号为整机固件版本号1.0和整机固件类型为整机固件类型A。利用整机固件类型A和图4(a)中的所有当前部件版本信息，可匹配得到图3(b)示出的“设备整机任务A-1”。利用“设备整机任务A-1”对智能设备进行升级之后，该智能设备的整机固件版本号为整机固件版本号2.0，且各个部件升级后的部件版本信息参见图3(b)“设备整机固件版本A-2.0”一栏示出的内容。
当该智能设备利用图3(b)示出的“设备整机任务A-1”进行升级后，此时该智能设备上传的当前部件版本信息如图4(b)示出的内容。服务端可根据图3(b)中“设备整机固件版本A-2.0”一栏示出的整机版本信息对应的第一对应关系和第二对应关系，对图4(b)中的所有当前部件版本信息进行匹配，确定该智能设备的整机固件版本号为整机固件版本号2.0和整机固件类型为整机固件类型A。利用整机固件类型A和图4(b)中的所有当前部件版本信息，可匹配得到图3(c)示出的“设备整机任务A-2”。利用“设备整机任务A-2”对智能设备进行升级之后，该智能设备的整机固件版本号为整机固件版本号3.0，且各个部件升级后的部件版本信息参见图3(c)“设备整机固件版本A-3.0”一栏示出的内容。
当智能设备利用图3(c)示出的“设备整机任务A-2”进行升级后，此时该智能设备上传的当前部件版本信息如图4(c)示出的内容。服务端可根据图3(c)中“设备整机固件版本A-3.0”一栏示出的整机版本信息对应的第一对应关系和第二对应关系，对图4(c)中的所有当前部件版本信息进行匹配，确定该智能设备的整机固件版本号为整机固件版本号3.0和整机固件类型为整机固件类型A。利用整机固件类型A和图4(c)中的所有当前部件版本信息，匹配图3(b)至图3(d)所示出的升级任务，未匹配得到对应的升级任务，此时服务端可向用户终端展示用于指示未匹配到升级任务的信息。
若智能设备所上传的所有当前部件版本信息为如图4(d)示出的内容，服务端利用图3(b)至图3(d)所示出的整机版本信息对应的第一对应关系和第二对应关系，未匹配得到相应的整机固件版本号，但可确定得到该智能 设备的整机固件类型为整机固件类型A，此时服务端向用户终端展示用于指示当前整机固件版本号未定义的信息。图4(d)能匹配得到图3(b)和图3(c)示出的升级任务，图3(b)示出的升级任务的整机固件版本号为整机固件版本号2.0，图3(c)示出的升级任务的整机固件版本号为整机固件版本号3.0，此时服务端利用图3(c)示出的升级任务对智能设备进行升级，升级之后该智能设备的整机固件版本号为整机固件版本号3.0。
上述内容为对如何确定智能设备的当前整机固件版本号和如何匹配升级任务等内容的示例。
为更好解释说明上述本公开实施例图1中所涉及的内容，通过图5示出的智能设备、服务端及用户终端的交互示意图进行举例说明。
需要说明的是，图5中的设备(即智能设备，在本示例中称为设备)由WIFI模块、电脑版A、电脑版B和自定义硬件等部件构成，服务端至少包含：FOTA控制台、DB、资源服务、FOTA服务和M2M。
图5所示出的交互示意图包含以下步骤。
步骤1-1：服务端的FOTA控制台响应运营人员的指令，创建并管理子固件和整机版本信息。
步骤1-2：服务端的FOTA控制台响应运营人员的指令，创建并管理升级任务。
步骤2-1：设备向服务端的M2M上报各个部件的当前部件版本信息。
步骤2-2：服务端的M2M将各个部件的当前部件版本信息上报至服务端的FOTA服务。
步骤3-1：用户点击用户终端的APP，查看该设备是否存在可升级的整机固件版本号。
步骤3-2：服务端的FOTA服务接收用户终端的查询指令，获取各个部件的当前部件版本信息，并根据所有当前部件版本信息从数据库中匹配到目标升级任务，将目标升级任务对应的整机固件版本号和设备的当前整机固件版本号反馈给用户终端。
步骤3-3：用户通过用户终端查看设备的当前整机固件版本号和目标升级任务对应的整机固件版本号后，可点击“确认升级”按键，用户终端将设备 升级指令发送至服务端的M2M。
步骤3-4：服务端的M2M将设备升级指令发送给设备的WIFI模块。
步骤3-5：设备的WIFI模块根据设备升级指令中的url，从资源服务下载与目标升级任务对应的目标整机升级包。
步骤3-6：设备的WIFI模块将目标整机升级包中的各个子固件升级包分别发送至对应的部件，使各个部件对自身的子固件进行升级。
步骤3-7：设备的WIFI模块将各个部件的部件升级进度发送至服务端的M2M。
步骤3-8：服务端的M2M将由各个部件升级进度确定的整机升级进度发送至用户终端。
步骤3-9：服务端的M2M将包含设备升级指令和各个部件升级进度的设备升级日志发送至服务端的FOTA服务进行存储。
步骤4：服务端的FOTA控制台可响应运营人员的指令，向运营人员展示设备升级日志。
与上述本公开实施例提供的一种升级包的确定方法相对应，参见图6，本公开实施例还提供了一种服务端的结构框图，该服务端包括：获取单元601、确定单元602、第一处理单元603和发送单元604；
获取单元601，设置为若接收到用户终端发送的查询指令，获取构成智能设备的各个部件的当前部件版本信息。
确定单元602，设置为利用所有当前部件版本信息，确定智能设备的目标整机固件类型和当前整机固件版本号。
在具体实现中，确定单元602具体设置为：根据第一预设关系，确定与所有当前部件版本信息具有对应关系的整机固件版本号，将所确定的整机固件版本号作为智能设备的当前整机固件版本号，第一预设关系包含多组第一对应关系，每组第一对应关系指示一个整机固件版本号与多条部件版本信息之间的关联关系；根据第二预设关系，确定与所有当前部件版本信息的子固件类型和子固件软件类型具有对应关系的整机固件类型，将所确定的整机固件类型作为智能设备的目标整机固件类型，第二预设关系包含多组第二对应 关系，每组第二对应关系指示一个整机固件类型与多条部件版本信息的子固件类型和子固件软件类型之间的关联关系。
第一处理单元603，设置为根据目标整机固件类型和所有当前部件版本信息，从多个预设的升级任务中匹配得到目标升级任务，并获取与目标升级任务对应的目标整机升级包，每个升级任务存在与之对应的整机升级包和新整机固件版本号。
发送单元604，设置为将当前整机固件版本号和目标升级任务对应的整机固件版本号发送至用户终端。
在本公开实施例中，根据智能设备上传的各个部件的当前部件版本信息，确定智能设备的目标整机固件类型和当前整机固件版本号。利用目标整机固件类型和所有当前部件版本信息确定目标整机升级包。智能设备仅需上报各个部件的当前版本信息即可确定对应的目标整机升级包，智能设备不需要保存或上报整机版本信息，提高对智能设备进行整机FOTA的适用范围。
可选的，结合图6示出的内容，该服务端还包括：
第二处理单元，设置为将设备升级指令发送给智能设备。
第三处理单元，设置为接收智能设备发送的下载指令，将目标整机升级包发送给智能设备，使智能设备根据目标整机升级包升级各个部件的子固件，目标整机升级包包含至少一个部件的子固件升级包。
可选的，第三处理单元还设置为：接收智能设备发送的每个部件的部件升级进度；根据每个部件升级进度确定智能设备的整机升级进度并将其发送给用户终端。
可选的，第三处理单元还设置为：生成与智能设备对应的设备升级日志，并接收智能设备发送的升级后的每个部件的部件版本信息。
可选的，结合图6示出的内容，每个升级任务包含限定条件和适用条件；第一处理单元包括：第一确定模块、第二确定模块、处理模块和获取模块，各个模块的执行原理为：
第一确定模块，设置为从多个预设的升级任务中，确定限定条件与目标整机固件类型相匹配的升级任务为第一升级任务。
第二确定模块，设置为从所有第一升级任务中，确定适用条件与所有当前部件版本信息中的子固件软件版本号相匹配的第一升级任务为第二升级任务。
处理模块，设置为若第二升级任务的数量为1，确定第二升级任务为目标升级任务；若第二升级任务的数量大于1，确定最优的第二升级任务为目标升级任务，最优的第二升级任务为整机固件版本号最高和/或创建时间最新的第二升级任务。
获取模块，设置为获取与目标升级任务对应的目标整机升级包。
可选的，本公开实施例还提供了一种电子设备，该电子设备设置为运行程序，其中，该程序运行时执行如上述本公开实施例中所涉及的升级包的确定方法。
可选的，本公开实施例还提供了一种计算机存储介质，该存储介质包括存储程序，其中，在程序运行时控制存储介质所在设备执行如上述本公开实施例中所涉及的升级包的确定方法。
综上所述，本公开实施例提供一种升级包的确定方法及服务端，服务端根据智能设备上传的各个部件的当前部件版本信息，确定智能设备的目标整机固件类型和当前整机固件版本号。服务端利用目标整机固件类型和所有当前部件版本信息确定目标整机升级包，将目标整机升级包发送给智能设备对各个部件的子固件进行升级。智能设备仅需上报各个部件的当前版本信息即可确定对应的目标整机升级包，智能设备不需要保存或上报整机版本信息，提高对智能设备进行整机FOTA的适用范围。
本说明书中的各个实施例均采用递进的方式描述，各个实施例之间相同相似的部分互相参见即可，每个实施例重点说明的都是与其他实施例的不同之处。尤其，对于系统或系统实施例而言，由于其基本相似于方法实施例，所以描述得比较简单，相关之处参见方法实施例的部分说明即可。以上所描述的系统及系统实施例仅仅是示意性的，其中所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可 以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部模块来实现本实施例方案的目的。本领域普通技术人员在不付出创造性劳动的情况下，即可以理解并实施。
专业人员还可以进一步意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、计算机软件或者二者的结合来实现，为了清楚地说明硬件和软件的可互换性，在上述说明中已经按照功能一般性地描述了各示例的组成及步骤。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本公开的范围。
对所公开的实施例的上述说明，使本领域专业技术人员能够实现或使用本公开。对这些实施例的多种修改对本领域的专业技术人员来说将是显而易见的，本文中所定义的一般原理可以在不脱离本公开的精神或范围的情况下，在其它实施例中实现。因此，本公开将不会被限制于本文所示的这些实施例，而是要符合与本文所公开的原理和新颖特点相一致的最宽的范围。
Claims (16)
- 一种升级包的确定方法，所述方法包括：若接收到用户终端发送的查询指令，获取构成智能设备的各个部件的当前部件版本信息；利用所有所述当前部件版本信息，确定所述智能设备的目标整机固件类型和当前整机固件版本号；根据所述目标整机固件类型和所有所述当前部件版本信息，从多个预设的升级任务中匹配得到目标升级任务，并获取与所述目标升级任务对应的目标整机升级包，每个所述升级任务存在与之对应的整机升级包和整机固件版本号；将所述当前整机固件版本号和所述目标升级任务对应的整机固件版本号发送至所述用户终端。
- 根据权利要求1所述的方法，其中，将所述当前整机固件版本号和所述目标升级任务对应的整机固件版本号发送至所述用户终端之后，还包括：将设备升级指令发送给所述智能设备；接收所述智能设备发送的下载指令，将所述目标整机升级包发送给所述智能设备，使所述智能设备根据所述目标整机升级包升级各个所述部件的子固件，所述目标整机升级包包含至少一个所述部件的子固件升级包。
- 根据权利要求1所述的方法，其中，所述利用所有所述当前部件版本信息确定所述智能设备的当前整机固件版本号的过程，包括：根据第一预设关系，确定与所有所述当前部件版本信息具有对应关系的整机固件版本号，将所确定的整机固件版本号作为所述智能设备的当前整机固件版本号，所述第一预设关系包含多组第一对应关系，每组所述第一对应关系指示一个整机固件版本号与多条部件版本信息之间的关联关系。
- 根据权利要求1所述的方法，其中，所述利用所有所述当前部件版本信息确定所述智能设备的目标整机固件类型的过程，包括：根据第二预设关系，确定与所有所述当前部件版本信息的子固件类型和子固件软件类型具有对应关系的整机固件类型，将所确定的整机固件类型作为所述智能设备的目标整机固件类型，所述第二预设关系包含多组第二对应 关系，每组所述第二对应关系指示一个整机固件类型与多条部件版本信息的子固件类型和子固件软件类型之间的关联关系。
- 根据权利要求1所述的方法，其中，每个升级任务包含限定条件和适用条件；所述根据所述目标整机固件类型和所有所述当前部件版本信息，从多个预设的升级任务中匹配得到目标升级任务，并获取与所述目标升级任务对应的目标整机升级包，包括：从多个预设的升级任务中，确定限定条件与所述目标整机固件类型相匹配的升级任务为第一升级任务；从所有所述第一升级任务中，确定适用条件与所有所述当前部件版本信息中的子固件软件版本号相匹配的第一升级任务为第二升级任务；若所述第二升级任务的数量为1，确定所述第二升级任务为目标升级任务；若所述第二升级任务的数量大于1，确定最优的第二升级任务为目标升级任务，所述最优的第二升级任务为整机固件版本号最高和/或创建时间最新的第二升级任务；获取与所述目标升级任务对应的目标整机升级包。
- 根据权利要求2所述的方法，其中，将所述目标整机升级包发送给所述智能设备之后，还包括：接收所述智能设备发送的每个所述部件的部件升级进度；根据每个所述部件升级进度确定所述智能设备的整机升级进度并将其发送给所述用户终端。
- 根据权利要求2所述的方法，其中，将所述目标整机升级包发送给所述智能设备之后，还包括：生成与所述智能设备对应的设备升级日志，并接收所述智能设备发送的升级后的每个所述部件的部件版本信息。
- 一种服务端，所述服务端包括：获取单元，设置为若接收到用户终端发送的查询指令，获取构成智能设备的各个部件的当前部件版本信息；确定单元，设置为利用所有所述当前部件版本信息，确定所述智能设备的目标整机固件类型和当前整机固件版本号；第一处理单元，设置为根据所述目标整机固件类型和所有所述当前部件版本信息，从多个预设的升级任务中匹配得到目标升级任务，并获取与所述目标升级任务对应的目标整机升级包，每个所述升级任务存在与之对应的整机升级包和整机固件版本号；发送单元，设置为将所述当前整机固件版本号和所述目标升级任务对应的整机固件版本号发送至所述用户终端。
- 根据权利要求8所述的服务端，其中，所述服务端还包括：第二处理单元，设置为将设备升级指令发送给所述智能设备；第三处理单元，设置为接收所述智能设备发送的下载指令，将所述目标整机升级包发送给所述智能设备，使所述智能设备根据所述目标整机升级包升级各个所述部件的子固件，所述目标整机升级包包含至少一个所述部件的子固件升级包。
- 根据权利要求8所述的服务端，其中，所述确定单元设置为通过如下方式实现利用所有所述当前部件版本信息确定所述智能设备的当前整机固件版本号的过程：根据第一预设关系，确定与所有所述当前部件版本信息具有对应关系的整机固件版本号，将所确定的整机固件版本号作为所述智能设备的当前整机固件版本号，所述第一预设关系包含多组第一对应关系，每组所述第一对应关系指示一个整机固件版本号与多条部件版本信息之间的关联关系。
- 根据权利要求8所述的服务端，其中，所述确定单元设置为通过如下方式实现利用所有所述当前部件版本信息确定所述智能设备的目标整机固件类型的过程：根据第二预设关系，确定与所有所述当前部件版本信息的子固件类型和子固件软件类型具有对应关系的整机固件类型，将所确定的整机固件类型作为所述智能设备的目标整机固件类型，所述第二预设关系包含多组第二对应关系，每组所述第二对应关系指示一个整机固件类型与多条部件版本信息的子固件类型和子固件软件类型之间的关联关系。
- 根据权利要求8所述的服务端，其中，每个升级任务包含限定条件和适用条件；所述第一处理单元设置为通过如下方式实现根据所述目标整机固件类型和所有所述当前部件版本信息，从多个预设的升级任务中匹配得到目标升级任务，并获取与所述目标升级任务对应的目标整机升级包：从多个预设的升级任务中，确定限定条件与所述目标整机固件类型相匹配的升级任务为第一升级任务；从所有所述第一升级任务中，确定适用条件与所有所述当前部件版本信息中的子固件软件版本号相匹配的第一升级任务为第二升级任务；若所述第二升级任务的数量为1，确定所述第二升级任务为目标升级任务；若所述第二升级任务的数量大于1，确定最优的第二升级任务为目标升级任务，所述最优的第二升级任务为整机固件版本号最高和/或创建时间最新的第二升级任务；获取与所述目标升级任务对应的目标整机升级包。
- 根据权利要求9所述的服务端，其中，所述第三处理单元还设置为：接收所述智能设备发送的每个所述部件的部件升级进度；根据每个所述部件升级进度确定所述智能设备的整机升级进度并将其发送给所述用户终端。
- 根据权利要求9所述的服务端，其中，所述第三处理单元还设置为：生成与所述智能设备对应的设备升级日志，并接收所述智能设备发送的升级后的每个所述部件的部件版本信息。
- 一种电子设备，所述电子设备设置为运行程序，其中，所述程序运行时执行如权利要求1至7中任一所述的升级包的确定方法。
- 一种计算机存储介质，所述存储介质包括存储程序，其中，在所述程序运行时控制所述存储介质所在设备执行如权利要求1至7中任一所述的升级包的确定方法。
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110937885.8 | 2021-08-16 | ||
| CN202110937885.8A CN113835726B (zh) | 2021-08-16 | 2021-08-16 | 一种升级包的确定方法及服务端 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2023020070A1 true WO2023020070A1 (zh) | 2023-02-23 |
Family
ID=78960522
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/CN2022/096394 WO2023020070A1 (zh) | 2021-08-16 | 2022-05-31 | 一种升级包的确定方法及服务端 |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN113835726B (zh) |
| WO (1) | WO2023020070A1 (zh) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113852489A (zh) * | 2021-08-16 | 2021-12-28 | 青岛海尔科技有限公司 | 一种升级包的获取方法及智能设备 |
| CN113835726B (zh) * | 2021-08-16 | 2023-11-28 | 青岛海尔科技有限公司 | 一种升级包的确定方法及服务端 |
| CN114745269A (zh) * | 2022-04-13 | 2022-07-12 | 精伦电子股份有限公司 | 固件升级方法、装置、电子设备和存储介质 |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105743933A (zh) * | 2014-12-08 | 2016-07-06 | Tcl集团股份有限公司 | 一种路由器的模块升级方法及系统 |
| CN107291516A (zh) * | 2017-07-12 | 2017-10-24 | 珠海格力电器股份有限公司 | 一种固件升级方法和系统 |
| CN109117158A (zh) * | 2018-08-02 | 2019-01-01 | 郑州云海信息技术有限公司 | 固件更新方法和装置 |
| KR20200086480A (ko) * | 2019-01-09 | 2020-07-17 | (주) 피엔텔레컴 | 무선충전기기의 펌웨어 업그레이드 방법 및 장치 |
| CN112130883A (zh) * | 2020-09-30 | 2020-12-25 | 苏州臻迪智能科技有限公司 | 软件升级方法及装置、电子设备、存储介质 |
| CN112764803A (zh) * | 2021-01-20 | 2021-05-07 | 青岛海尔科技有限公司 | 版本升级方法及装置、存储介质及电子装置 |
| CN113835726A (zh) * | 2021-08-16 | 2021-12-24 | 青岛海尔科技有限公司 | 一种升级包的确定方法及服务端 |
Family Cites Families (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10188348B2 (en) * | 2006-06-05 | 2019-01-29 | Masimo Corporation | Parameter upgrade system |
| US8653963B2 (en) * | 2007-03-01 | 2014-02-18 | Advanced Computer And Communications, L.L.C. | Emergency alert system and method |
| CN108512684B (zh) * | 2017-02-28 | 2021-07-27 | 阿里巴巴集团控股有限公司 | 固件升级方法和系统以及固件升级管理装置 |
| CN109088783A (zh) * | 2018-11-01 | 2018-12-25 | 郑州云海信息技术有限公司 | 整机柜服务器多级之间刷新进度获取方法、装置及设备 |
| CN110489143B (zh) * | 2019-07-18 | 2023-10-13 | 南京依维柯汽车有限公司 | 新能源汽车上的fota固件远程升级系统及其方法 |
| CN110378123B (zh) * | 2019-07-18 | 2023-11-14 | 上海擎感智能科技有限公司 | 一种用于车载终端的软件升级方法及系统 |
| CN111562935B (zh) * | 2020-07-14 | 2020-10-27 | 江苏海平面数据科技有限公司 | 一种ota安全升级系统及其升级方法 |
| CN112000355B (zh) * | 2020-08-21 | 2023-10-24 | 青岛海尔科技有限公司 | 用于固件升级的方法及装置、家电设备 |
| CN112148326B (zh) * | 2020-08-31 | 2024-05-31 | 山东省科学院自动化研究所 | 一种物联网设备固件远程更新方法、装置及系统 |
| CN113064619A (zh) * | 2021-04-02 | 2021-07-02 | 上海高仙自动化科技发展有限公司 | 一种固件升级方法、装置、系统、设备和存储介质 |
-
2021
- 2021-08-16 CN CN202110937885.8A patent/CN113835726B/zh active Active
-
2022
- 2022-05-31 WO PCT/CN2022/096394 patent/WO2023020070A1/zh active Application Filing
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105743933A (zh) * | 2014-12-08 | 2016-07-06 | Tcl集团股份有限公司 | 一种路由器的模块升级方法及系统 |
| CN107291516A (zh) * | 2017-07-12 | 2017-10-24 | 珠海格力电器股份有限公司 | 一种固件升级方法和系统 |
| CN109117158A (zh) * | 2018-08-02 | 2019-01-01 | 郑州云海信息技术有限公司 | 固件更新方法和装置 |
| KR20200086480A (ko) * | 2019-01-09 | 2020-07-17 | (주) 피엔텔레컴 | 무선충전기기의 펌웨어 업그레이드 방법 및 장치 |
| CN112130883A (zh) * | 2020-09-30 | 2020-12-25 | 苏州臻迪智能科技有限公司 | 软件升级方法及装置、电子设备、存储介质 |
| CN112764803A (zh) * | 2021-01-20 | 2021-05-07 | 青岛海尔科技有限公司 | 版本升级方法及装置、存储介质及电子装置 |
| CN113835726A (zh) * | 2021-08-16 | 2021-12-24 | 青岛海尔科技有限公司 | 一种升级包的确定方法及服务端 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113835726A (zh) | 2021-12-24 |
| CN113835726B (zh) | 2023-11-28 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| WO2023020070A1 (zh) | 一种升级包的确定方法及服务端 | |
| US20220103612A1 (en) | Application Recommendation Method, Device, and System | |
| US8762984B2 (en) | Content distribution infrastructure | |
| US8458658B2 (en) | Methods and systems for dynamically building a software appliance | |
| CA2631696C (en) | System, apparatus, and method for dynamically customizing and configuring applications | |
| US9928041B2 (en) | Managing a software appliance | |
| US8935687B2 (en) | Incrementally updating a software appliance | |
| CN106802814B (zh) | 用于软件版本升级的方法及装置 | |
| CN109905256A (zh) | 一种固件更新方法和装置 | |
| CN104066077A (zh) | 一种ota下载升级方法及装置 | |
| CN108376078A (zh) | 设备的升级方法、装置以及家电设备 | |
| WO2006086582A2 (en) | Systems and method for deploying a software application on a wireless device | |
| WO2008001214A2 (en) | System, apparatus, and method for dynamically configuring application access point settings | |
| JP2010231781A (ja) | Ｕｒｌを利用した分散コントロール方法及び装置 | |
| US20150113423A1 (en) | System and method to configure a field device | |
| EP2131555A1 (en) | Apparatus and method for identification of the characteristics of a communication device | |
| US20130054760A1 (en) | Data upload method using shortcut | |
| JP2009259124A (ja) | アプリケーション更新情報提供システム、及びアプリケーション更新情報提供方法 | |
| CN104504587A (zh) | 广告监测方法及装置、电子设备 | |
| CN107357612A (zh) | 应用程序升级检测方法及装置 | |
| CN111190625A (zh) | App版本升级方法和服务端、客户端及计算机可读存储介质 | |
| WO2023020071A1 (zh) | 一种升级包的获取方法及智能设备 | |
| CN111679842B (zh) | 应用程序热更新处理方法、装置及系统 | |
| CN107124713B (zh) | 一种定制更新方法及移动终端 | |
| CN112596812B (zh) | 一种操作请求的响应方法、装置、设备及存储介质 |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| 121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 22857384 Country of ref document: EP Kind code of ref document: A1 |
|
| NENP | Non-entry into the national phase |
Ref country code: DE |
|
| 122 | Ep: pct application non-entry in european phase |
Ref document number: 22857384 Country of ref document: EP Kind code of ref document: A1 |