A method, system, terminal and readable medium for silent upgrade

Abstract

The application discloses a silent upgrading method, system, terminal and readable medium, and the method comprises the following steps: determining that the upgrading information of a first end is acquired, and a first partition of a second end is in an unoccupied state; mounting the first partition to the first end, wherein the first end is in communication connection with the second end; writing the file system of the first end to the first partition, and setting the starting partition of the first end as the first partition; determining that the first end starts from the first partition; and upgrading the file system in the local partition of the first end according to the upgrading information, and setting the starting partition of the first end as the local partition of the first end. The application can enable multiple clients to share the same backup partition through a network, and can maximize the cost saving under the condition of guaranteeing the in-situ upgrading.

Description

TECHNICAL FIELD

[0001] The application belongs to the technical field of data processing, and particularly relates to a silent upgrade method and system, a terminal and a readable medium. BACKGROUND

[0002] For electronic devices, software update and upgrade of the device is inevitable, but there is a difficult problem in upgrade, that is, upgrade must be restarted to take effect. Software restart, especially for some places with high continuity requirements for device use, the impact on the user is relatively large every time the update is restarted. For example, when someone comes to take a taxi while remotely upgrading the device in a taxi, the device cannot be normally used, and an order will be lost. Or the camera is restarting and updating when a traffic accident occurs, so important video is not recorded. Therefore, a non-sensing upgrade method is needed, that is, without affecting the use of the electronic device, the upgrade action can be normally completed.

[0003] The commonly used non-sensing upgrade method is to use A / B partitioning, that is, all partitions except the boot program are allocated a standby partition. When upgrading, the standby partition is upgraded, and the standby partition is automatically used to start at the next restart, thereby achieving the effect of non-sensing upgrade. However, this method will cause the size of the flash memory used by the saved program to double, resulting in increased costs, especially when there are multiple devices in a set of solutions, the cost increase is more obvious. SUMMARY

[0004] The purpose of the application is to provide a silent upgrade method, system, terminal and readable medium, which aims to solve the problem of high cost of non-sensing upgrade existing in the traditional upgrade method.

[0005] The first aspect of the embodiment of the application provides a silent upgrade method, comprising the following steps:

[0006] Determine that the upgrade information of the first end is acquired, and determine that the first partition of the second end is in an unoccupied state. The first partition is mounted to the first end, wherein the first end and the second end are in communication connection;

[0007] The file system of the first end is written into the first partition, and the start-up partition of the first end is set as the first partition;

[0008] Determine that the first end starts from the first partition, then upgrade the file system in the local partition of the first end according to the upgrade information, and set the start-up partition of the first end as the local partition of the first end.

[0009] In the embodiment of the present application, the first partition of the second end in the unoccupied state enables the first partition of the second end to be mounted on any first end, and then the file system of the first end is written into the first partition, so that the file system of the first end is completely written into the first partition, and when the first partition is started, the same user experience can be provided to the user, and after the file system of the first end is updated locally, the update can be completed after the first end is started again, and the first partition mounted on the first end is released, so that the first partition can be used for upgrading other first ends. The present application upgrades the first end by sharing the second partition of the second end by multiple first ends, reduces the memory cost required for local non-sensing upgrade, and can save the non-sensing update cost of the first end.

[0010] Further, the first partition of the second end is mounted on the first end, and the state value of the first partition in the state partition of the second end is set to a second value, and the second value is used to indicate that the partition is in an occupied state.

[0011] The upgrade information of the first end is downloaded from the upgrade server;

[0012] The state value of the first partition in the state partition of the second end is determined to be a first value, and the first value is used to indicate that the partition is in an unoccupied state;

[0013] The first partition is mounted on the first end, and the state value of the first partition in the state partition of the second end is set to a second value, and the second value is used to indicate that the partition is in an occupied state.

[0014] In the embodiment of the present application, the state of the first partition of the second end is confirmed through the state partition, so as to confirm whether the first partition of the second end is in an unoccupied state, and even if the first partition writes a file, the first partition can still be in an unoccupied state.

[0015] Further, after the start partition of the first end is set as the local partition of the first end, the method further comprises:

[0016] The state value of the first partition in the state partition of the second end is set to a first value.

[0017] In the embodiment of the present application, when the first end completes local update, the state value of the first partition of the second end is updated, and the first partition is in an unoccupied state again, so as to facilitate subsequent update of other first end devices.

[0018] Further, after the file system of the first end is written into the first partition, the above method further comprises the following steps:

[0019] The upgrade information of the first end is written into the first partition.

[0020] In the embodiment of the present application, the file system in the first partition can be updated first, so that the first end can use the updated file system when starting from the first partition, facilitating the user to use the latest version of the system faster.

[0021] Further, the first partition of the second end is mounted to the first end through the network file system.

[0022] In the embodiment, the mounting through the network file system enables the first partition to share the files and directories of the first end.

[0023] Further, the step of determining that the first partition of the second end is in an unoccupied state comprises:

[0024] determining that at least one of the at least two standby partitions of the second end is in an unoccupied state; and the first partition is the standby partition of the second end in the unoccupied state.

[0025] In the embodiment of the present application, after the local file system of the first end is upgraded through the upgrade package, if the first end is not started through the local partition for a long time, the first partition of the second end will be occupied for a long time. In the case that the storage capacity of the second end is sufficient, the upgrade of the file system of the first end can be completed through multiple idle partitions, thereby improving the upgrade efficiency of the first end.

[0026] The second aspect of the embodiment provides a silent upgrade method, applied to a second end, comprising:

[0027] determining that the upgrade information of the second end is acquired and the second partition of the second end is in an unoccupied state, then writing the file system of the second end into the second partition, setting the second partition as a start-up partition, and the second partition is a standby partition of the second end;

[0028] writing the upgrade information into the second partition;

[0029] determining that the second end starts from the second partition, then modifying the default start-up partition of the second end to the second partition, and modifying the original default start-up partition of the second end to a standby partition in an unoccupied state.

[0030] In the embodiment of the present application, whether the first partition in an unoccupied state is inquired, and the upgrade of the file system of the second end is completed in the first partition, so as to complete the silent update of the second end.

[0031] After the default start-up partition is modified, the original default start-up partition of the second end can be modified to an unoccupied state, for the silent upgrade of the file system of the second end or other first ends.

[0032] The third aspect of the embodiment of the present application provides a silent upgrade system, applied to a first end, comprising:

[0033] The mounting module is configured to determine that the upgrade information of the first end is acquired and the first partition of the second end is in an unoccupied state, and mount the first partition to the first end, wherein the first end is in communication connection with the second end.

[0034] The writing module is configured to write the file system of the first end to the first partition, and set the boot partition of the first end as the first partition.

[0035] The first-end upgrade module is configured to determine that the first end is started from the first partition, and then upgrade the file system in the local partition of the first end according to the upgrade information, and set the boot partition of the first end as the local partition of the first end.

[0036] The fourth aspect of the embodiment of the present application provides a silent upgrade system applied to a second end, comprising:

[0037] The partition state confirmation module is configured to determine that the upgrade information of the second end is acquired and the first partition of the second end is in an unoccupied state, and then write the file system of the second end to the first partition, and set the first partition as the boot partition.

[0038] The second-end upgrade module is configured to upgrade the file system in the first partition through the upgrade information.

[0039] The default boot partition modification module is configured to determine that the second end is started from the first partition, and then modify the default boot partition of the second end as the first partition.

[0040] The fifth aspect of the embodiment of the present application provides a silent upgrade terminal, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, and the processor implements the steps of the method as described above when executing the computer program.

[0041] The sixth aspect of the embodiment of the present application provides a computer readable storage medium, which stores a computer program, and the computer program is executable by a processor to implement the steps of the method as described above.

[0042] Compared with the prior art, the silent upgrade method, system, terminal and readable medium provided by the embodiment of the present application can make multiple first ends share the first partition of the same second end through a network, and can maximize the cost saving under the condition of ensuring the no-sense upgrade. BRIEF DESCRIPTION OF DRAWINGS

[0043] Figure 1 The specific flowchart of the silent upgrade method provided by an embodiment of the present application is shown in the figure.

[0044] Figure 2 The specific flowchart of the client silent upgrade method provided by an embodiment of the present application is shown in the figure.

[0045] Figure 3 A specific flowchart of a server-side silent upgrade method provided by an embodiment of the present application is shown in the following table:

[0046] Figure 4 A structural schematic diagram of a silent upgrade system provided by an embodiment of the present application is shown in the following table:

[0047] Figure 5 A schematic diagram of a silent upgrade terminal provided by an embodiment of the present application is shown in the following table. DETAILED DESCRIPTION

[0048] In order to make the technical problems, technical solutions and beneficial effects of the present application clearer, the present application will be further described in detail below in combination with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and do not limit the present application.

[0049] It should be noted that the terms "first", "second", "third" are only used for descriptive purposes and should not be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Therefore, the features limited by "first", "second" can explicitly or implicitly include one or more of the features. In the description of the present application, the meaning of "multiple" is two or more, unless otherwise specifically limited.

[0050] The technical solutions of the present application are described below taking the vehicle-mounted system scenario as an example. For example, the second end is generally selected as the device with the largest flash memory capacity in the current scenario, such as the vehicle-mounted computer in the vehicle-mounted system; the first end can be one or more, such as the vehicle-mounted navigation device, the vehicle-mounted DVR, the vehicle-mounted multimedia, etc. in the vehicle-mounted system. The first partition of the second end is a backup partition, which is used for the non-perception upgrade of each first end. The first end and the second end are connected through a network, which can be a wired network, wifi, Network Files System (NFS), etc.

[0051] Figure 1 A flowchart of a silent upgrade method provided by a preferred embodiment of the present application is shown in the following table, only the parts related to the present embodiment are shown for convenience, and the details are described as follows:

[0052] S102, it is determined that the upgrade information of the first end is acquired, and it is determined that the first partition of the second end is in an unoccupied state.

[0053] When upgrading at the first end (i.e., the client of the vehicle-mounted system), first, upgrade information needs to be obtained from the upgrade server, or the upgrade information pre-written in the local disk is read, which can be a folder containing upgrade files, or an upgrade package. The upgrade of the file system of the first end can be completed by overwriting the files in the file system of the first end, or by unpacking and overwriting the upgrade package to complete the upgrade of the file system of the first end. At the same time, the first end can send a status query request to the second end (i.e., the server end of the vehicle-mounted system) to query whether the first partition (i.e., the standby partition) of the second end is in an unoccupied state. The unoccupied state refers to that no client or server end of the current vehicle-mounted system is accessing or using the first partition.

[0054] S104, mounting the first partition to the first end.

[0055] After the first end confirms that the first partition of the second end is unoccupied, the first partition of the second end can be mounted to the first end through a wireless network, a local area network, or a network file system, so that the first partition can become an extended storage space of the first end.

[0056] S106, writing the file system of the first end to the first partition.

[0057] The file system of the first end, including file directories, kernel files, and root file systems, is written to the first partition, so that the first end can realize the original function of the file system when starting through the first partition.

[0058] S108, setting the start-up partition of the first end to the first partition.

[0059] By modifying the start-up parameters or other ways of modifying the start-up partition, the start-up partition of the first end is modified from the local partition to the first partition. Based on the writing step S106, when the first end starts from the first partition, it can still operate normally.

[0060] S110, determining that the first end starts from the first partition, then upgrading the file system in the local partition of the first end according to the upgrade information, and setting the start-up partition of the first end to the local partition of the first end.

[0061] After the first end starts from the first partition, the local partition of the first end is not used. At this time, the local partition of the first end can upgrade the file system in the local partition through the upgrade information in step S102. After the upgrade is completed, the start-up partition of the first end is set to the local partition of the first end. Therefore, when starting from the local partition of the first end next time, the file system of the first end has been upgraded, and the user can complete the no-sense update of the first end in the process of normally starting and shutting down the first end.

[0062] For each step of the above embodiment, the application also has the following optional implementation:

[0063] S102, determine that the upgrade information of the first end is acquired, and determine that the first partition of the second end is in an unoccupied state.

[0064] In one or more embodiments, the plurality of first ends share the first partition of the second end, so the first partition of the second end needs a large capacity, for example, in the current system, the backup partition size required by the first end 1 is 2G byte, and the backup partition size required by the first end 2 is 1G byte, so the capacity of the first partition of the second end should be at least equal to 2G byte.

[0065] In one or more embodiments, the first partition of the second end is in an unoccupied state, that is, it is determined whether the first partition of the second end is used by other first ends, if the first partition of the second end is used by other first ends, then wait for the first partition of the second end to be released before updating. Generally, the state of the first partition of the server is saved in a state partition which is not overwritten during the upgrade of the partition.

[0066] For example, the current first end needs to be updated, the state partition of the second end can be read first to determine whether the first partition A of the second end is in an unoccupied state, then the corresponding upgrade information is acquired if the first partition A is in an unoccupied state.

[0067] In one or more embodiments, the current first end needs to be updated, the corresponding upgrade information can also be acquired first, and then the size of the partition required by the file system of the first end is determined, and then the state partition of the second end is read to determine whether the first partition A of the second end is in an unoccupied state, or whether there is a backup partition A, B or C in an unoccupied state, for example, the state of partition A in the state partition is 1, which means that partition A is being occupied, and the states of partitions B and C are 0, which means that partitions B and C are not occupied, then if there is a partition in an unoccupied state, the first end can verify the size of the unoccupied state partition according to the size of the partition required by the upgrade information to determine whether the size of the unoccupied state partition meets the upgrade requirement of the first end, for example, the size of partition B is 2G byte, the size of partition C is 1G byte, and the size required by the first end for upgrade is 1.5G byte, then the first end confirms that partition B can be used for upgrade, at this time the first end B accesses the upgrade server to acquire the upgrade package.

[0068] In one or more embodiments, if the size of the unoccupied partition cannot meet the upgrade requirement of the first end, the second end can re-partition the partition according to the upgrade requirement of the first end. For example, the size of partition B is 2G Byte, the size of partition C is 1G Byte, and the upgrade size required by the first end is 2.5G Byte. Then the second end re-partitions the partitions B and C, and re-partitions the partitions into partition B: 2.5G Byte, and partition C: 0.5G Byte, so as to maximize the use of the unoccupied partition of the second end.

[0069] S104, mounting the first partition to the first end.

[0070] In one or more embodiments, when the first partition is in an unoccupied state, the second end is informed to format the first partition as a complete partition, and the network file system service is started to allow the user end to mount the first partition to the local directory of the first end through the network file system. For example, the first partition A is formatted as a complete partition, so that the first end can write files into the first partition in the form of storing files, which is not conducive to file storage if the first partition is divided into multiple small partitions.

[0071] In one or more embodiments, the first end can mount the first partition of the second end to local use through the network file system. The main function of the network file system is to allow different host systems to share files or directories through a network (generally a local area network). The network file system first end can mount the data directory shared by the network file system server to the local system of the network file system first end through mounting. From the local machine of the network file system first end, the directory shared by the network file system second end is like the disk partition or directory of the first end itself, but actually it is the directory of the remote network file system server.

[0072] S106, writing the file system of the first end into the first partition.

[0073] After extracting the kernel file, root file system and various system files in the file system of the first end, they are stored in the mounted backup partition.

[0074] For example, the files in the un-upgraded file system of the first end are written into the first partition. In this way, the next time the first end starts from the first partition, the version of the file system in the first partition can be consistent with the version of the system in the local partition of the first end, so that the user will not feel that the file version has changed.

[0075] In one or more embodiments, while writing the files in the first end's un-upgraded file system in the first partition, the upgrade information can also be written into the first partition, and the file system in the first partition can be upgraded before the next time the first end is started from the first partition, so that the next time the first end is started from the first partition, the user can use the upgraded file system in advance.

[0076] S108, setting the starting partition of the first end to the first partition.

[0077] updating the starting parameter, at this time, the starting parameter is that the first end is started from the first partition in the case that the second end's first partition of the network file system is mounted to the first end, and after the first end is restarted, the system files of the first end are loaded from the first partition, at this time, the system files in the first end are not called to read.

[0078] S110, determining that the first end is started from the first partition, then upgrading the file system in the local partition of the first end according to the upgrade information, and setting the starting partition of the first end to the local partition of the first end.

[0079] Since in step S108, the system files in the first end are not called to read, the first end can obtain the upgrade package from the upgrade server, so that the upgrade package can be upgraded in the local system of the first end, and in this process, the user can normally use the system of the first end from the mounted first partition until the upgrade package of the first end upgrades the local first end to completion, at this time, the first end can be restarted according to the user prompt sent by the first end, or the first end can be restarted when the user completes the existing and closes the first end the next time the first end is started. Therefore, the starting parameter needs to be updated at this time, so that the first end can load the system files from the local partition to start, and complete the upgrade of the first end.

[0080] In one or more embodiments, after setting the starting partition of the first end to the local partition of the first end, if the current first partition is still mounted on the first end, then the first partition is still in the occupied state, and then the second end sends inquiry information to the first end to inquire whether the first end needs to be restarted, if the first end is restarted, the first partition automatically releases the mounting relationship with the first end, at this time, the state of the first partition in the state partition can be modified to the unoccupied state.

[0081] It should be understood that the size of the serial number of each step in the above embodiments does not mean the order of execution, and the execution order of each process should be determined according to its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0082] Specifically, in another embodiment of the present application, referring toFigure 2 and Figure 3 , respectively, are embodiments of the application for upgrading the first end and the second end. In the embodiments, when the first end needs to be upgraded, it is determined whether the second end is using the backup partition, and if not, the backup partition of the second end is mounted to the local, then the upgrade package is written to the mounted directory, then the uboot startup parameter is modified, and at the next startup, the backup partition of the second end is automatically mounted and started. After starting, the upgrade software is written to the original partition of the first end again, and after successful writing, the uboot startup parameter is modified, and at the next startup, the local partition is automatically started.

[0083] When the second end needs to be upgraded, only the upgrade file needs to be written to the backup partition, and then the user is prompted to manually restart, or at the next restart, the backup partition is directly started.

[0084] Referring to Figure 2 , the upgrade process of the first end is as follows:

[0085] First, download the upgrade package and save it in the local data area of the first end.

[0086] The first end inquires the second end whether the backup partition of the second end is currently in use, and if it is in use, waits for the backup partition until it is in an unoccupied state.

[0087] If the backup partition of the second end is not currently in use, the second end is notified to set the current use state of the backup partition to 1, at which time other hosts are prohibited from operating and using the backup partition.

[0088] The first end notifies the second end to format the backup partition into a complete partition, and starts the network file system service to allow the first end to mount the backup partition to the local through the network file system.

[0089] When the second end completes the formatting, the first end is notified, and the first end mounts the backup partition to the local directory.

[0090] The first end extracts the files in the entire file system including the kernel file and the root file system, and stores them in the mounted backup partition.

[0091] The uboot startup parameter of the first end is modified to a first startup parameter value, according to which the kernel file loading and the root file system loading are started from the network file system directory in the backup partition mounted by the second end. At the same time, according to the first startup parameter value, the root file system is modified to mount other subsequent partitions, so that the root file system is also started from the folder corresponding to the mounted backup partition of the second end.

[0092] The user is prompted to restart, or waits for the user to restart next time.

[0093] After next boot, the backup partition of the second end is mounted to the local through the network file system, and then boot. After boot, the upgrade package is written into the local partition of the first end again.

[0094] After the writing is successful, the uboot parameter is modified to the second boot parameter value, so that the first end boots from the local partition. At the next boot, the first end automatically loads the programs of each partition to boot. After boot, the second end is notified to modify the usage state of the backup partition to 0 to release the usage of the backup partition.

[0095] In some cases, the second end also needs to upgrade itself. In order to reasonably use the spare partition divided by the second end for the first end upgrade, the second end self-upgrade method is as shown in Figure 3

[0096] When the second end upgrades, the upgrade package is downloaded first. The upgrade package is generally obtained from the upgrade server through the network, and after the download is completed, the upgrade package is saved in the local data partition of the second end.

[0097] It is judged whether the backup partition of the second end is being used. The usage state of the backup partition is saved in a state partition separately, and the upgrade of the partition will not be overwritten. If the backup partition is being used, it is waited until the usage state is released.

[0098] If the backup partition is not being used, the state area is modified, and the usage state of the backup partition is set to being used, so as to avoid that the backup partition is operated again by other hosts when the second end is using the backup partition.

[0099] The backup partition is formatted according to the partition parameters of the local partition. After the formatting is completed, the upgrade package of the second end is written into the backup partition. The upgrade action of the backup partition is completed.

[0100] After the writing of the upgrade package is successful, the second end changes the next boot partition to the backup partition. At this time, the user can be prompted that the upgrade is successful, and the new function can be experienced manually by restarting. If the user manually restarts, the next boot logic is entered. If the user does not manually restart at present, after the device is powered off, the next time the device is restarted, the next boot logic is also automatically entered.

[0101] At the next restart, the second end judges the recorded boot partition. If the backup partition is used to boot, the backup partition program is loaded to boot, and the backup partition is changed to the local partition, and the local partition is changed to the backup partition. Then the next boot partition is changed to the local partition, and the current usage state of the backup partition is set to 0, so that other first ends or hosts are allowed to operate and use the partition.

[0102] ​In one or more embodiments, the second end can divide multiple backup partitions in the same system for the first end to upgrade, so as to avoid the situation that a first end occupies a backup partition for a long time without restarting.

[0103] It should be noted that in the above embodiments of the present application, the partitions involved in upgrading are program partitions of the second end or the first end, and the data of the program partitions will not change during running. The data that changes are in the data area, and the data area generally does not need to be upgraded and should not be upgraded.

[0104] Through the above embodiments, the present application can enable each device in the same system to complete silent upgrading, while occupying less flash memory space, and can maximize the reduction of the flash memory cost required for device upgrading.

[0105] Figure 4 is a schematic diagram of a silent upgrading system provided by an embodiment of the present application, as shown in Figure 4 The silent upgrading system of the embodiment includes:

[0106] A mounting module is configured to determine that the upgrade information of the first end is acquired, and confirm that the first partition of the second end is in an unoccupied state, and then mount the first partition to the first end, wherein the first end is in communication connection with the second end.

[0107] A writing module is configured to write the file system of the first end to the first partition, and set the start-up partition of the first end as the first partition.

[0108] A first-end upgrading module is configured to determine that the first end starts from the first partition, and then upgrade the file system in the local partition of the first end according to the upgrade information, and set the start-up partition of the first end as the local partition of the first end.

[0109] In one or more embodiments, the silent upgrading system mounting module described above further includes:

[0110] An upgrade information downloading module is configured to download the upgrade information from an upgrade server.

[0111] A state confirming module is configured to determine that the state value of the first partition in the state partition of the second end is a first value, and the first value is used to indicate that the partition is in an unoccupied state.

[0112] A partition mounting module is configured to mount the first partition to the first end, and set the state value of the first partition in the state partition of the second end as a second value, and the second value is used to indicate that the partition is in an occupied state.

[0113] In one or more embodiments, the silent upgrading system described above further includes:

[0114] The status reset module is used to set the status value of the first partition in the status partition of the second end to the first value.

[0115] In one or more embodiments, the upgrade module further includes:

[0116] The first partition upgrade module is used to write the upgrade information from the first end to the first partition, and upgrade the file system of the first end in the first partition according to the upgrade information from the first end.

[0117] In one or more embodiments, the second end further includes a second partition, and the mounting module further includes a second partition mounting module, which is used to mount the second partition to the first end when it is determined that the upgrade information of the first end has been received and the first partition of the second end is in an occupied state, if the second partition is in an unoccupied state.

[0118] Figure 5 This is a schematic diagram of a seamless upgrade terminal provided in one embodiment of this application. For example... Figure 5 As shown, a seamless upgrade terminal 5 in this embodiment includes: a processor 50, a memory 51, and a computer program 52 stored in the memory 51 and executable on the processor 50. When the processor 50 executes the computer program 52, it implements the steps in the various seamless upgrade method embodiments described above, for example... Figure 1 Steps 102 to 110 are shown. Alternatively, when the processor 50 executes the computer program 52, it implements the functions of each module / unit in the above-described device embodiments.

[0119] For example, the computer program 52 can be divided into one or more modules / units, which are stored in the memory 51 and executed by the processor 50 to complete this application. The one or more modules / units can be a series of computer program instruction segments capable of performing specific functions, which describe the execution process of the computer program 52 in the seamless upgrade terminal 5.

[0120] The aforementioned seamless upgrade terminal 5 can be a computing device such as a desktop computer, laptop, handheld computer, or cloud server. The seamless upgrade terminal may include, but is not limited to, a processor 50 and a memory 51. Those skilled in the art will understand that... Figure 5 This is merely an example of a seamless upgrade terminal 5 and does not constitute a limitation on a seamless upgrade terminal 5. It may include more or fewer components than shown, or combine certain components, or different components. For example, the device / terminal equipment may also include input / output devices, network access devices, buses, etc.

[0121] The processor 50 can be a central processing unit (CPU), and can also be other general-purpose processors, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, etc. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor.

[0122] The memory 51 can be an internal storage unit of the non-inductive upgrading terminal 5, for example, a hard disk or a memory of the non-inductive upgrading terminal 5. The memory 51 can also be an external storage device of the non-inductive upgrading terminal 5, for example, a plug-in hard disk, a smart media card (SMC), a secure digital (SD) card, a flash card, etc. equipped on the non-inductive upgrading terminal 5. Further, the memory 51 can also include both the internal storage unit and the external storage device of the non-inductive upgrading terminal 5. The memory 51 is used to store the computer program and other programs and data required by the device / terminal equipment. The memory 51 can also be used to temporarily store data that has been output or will be output.

[0123] Those skilled in the art can clearly understand that, for the convenience and brevity of description, only the division of the above functional units and modules is exemplified, and in actual application, the above functions can be completed by different functional units and modules according to needs, that is, the internal structure of the device is divided into different functional units or modules to complete all or part of the functions described above. Each functional unit and module in the embodiment can be integrated in one processing unit, or each unit can exist physically, or two or more units can be integrated in one unit, and the integrated unit can be realized in the form of hardware or in the form of software functional unit. In addition, the specific names of each functional unit and module are only for easy distinction, and do not limit the protection scope of the present application. The specific working process of the units and modules in the system can refer to the corresponding process in the foregoing method embodiments, which will not be described here.

[0124] In the above embodiments, the description of each embodiment has its own emphasis, and the parts not described or recorded in detail in a certain embodiment can be referred to the relevant description of other embodiments.

[0125] Those skilled in the art can understand that the units and algorithm steps of each example described in combination with the embodiments disclosed herein can be realized by electronic hardware or a combination of computer software and electronic hardware. Whether the functions are realized in hardware or software depends on the specific application and design constraints of the technical solution. A person skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the present application.

[0126] In the embodiments provided in the present application, it should be understood that the disclosed apparatus / terminal device and method can be implemented by other ways. For example, the apparatus / terminal device embodiments described above are only schematic, for example, the division of the modules or units is only a logical function division, and there can be another division manner in actual implementation, for example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the displayed or discussed mutual couplings or direct couplings or communication connections between the units can be indirect couplings or communication connections through some interfaces, devices or units, and can be electrical, mechanical or other forms.

[0127] The units described as separate components can or can not be physically separate, and the components shown as units can or can not be physical units, that is, they can be located in one place, or can be distributed on a plurality of network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the embodiments.

[0128] In addition, each functional unit in each embodiment of the present application can be integrated into a processing unit, or each unit can exist physically independently, or two or more units can be integrated into one unit. The integrated unit can be realized in the form of hardware or in the form of a software functional unit.

[0129] The integrated module / unit, if implemented in the form of a software functional unit and sold or used as an independent product, can be stored in a computer readable storage medium. Based on such understanding, all or part of the processes in the above-mentioned embodiment methods can also be completed by a computer program instructing related hardware, and the computer program can be stored in a computer readable storage medium. The computer program can implement the steps of each method embodiment when executed by a processor. The computer program includes computer program code, which can be in the form of source code, object code, executable files, or some intermediate forms. The computer readable medium can include any entity or device capable of carrying the computer program code, recording medium, U disk, mobile hard disk, magnetic disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signal, telecommunication signal, and software distribution medium, etc. It should be noted that the contents included in the computer readable medium can be appropriately increased or decreased according to the requirements of legislation and patent practice in the jurisdiction, for example, in some jurisdictions, according to legislation and patent practice, the computer readable medium does not include electrical carrier signals and telecommunication signals.

[0130] The above-described embodiments are only used to illustrate the technical solutions of the present application, rather than limit them; although the present application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that: it can still modify the technical solutions recorded in the foregoing embodiments, or make equivalent replacement for part of the technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present application, and should be included in the protection scope of the present application.

Claims

1. A method of silent upgrade, characterized by, The application is applied to a first terminal and comprises the following steps: If it is determined that the upgrade information of the first terminal is obtained and that the first partition of the second terminal is in an unoccupied state, the first partition is mounted to the first terminal, wherein the first terminal is in communication connection with the second terminal; the first partition of the second terminal is a backup partition and is used for the in-sight upgrade of each first terminal; The file system of the first terminal is written into the first partition, and the start-up partition of the first terminal is set as the first partition; If it is determined that the first terminal starts from the first partition, the file system in the local partition of the first terminal is upgraded according to the upgrade information, and the start-up partition of the first terminal is set as the local partition of the first terminal.

2. The method of claim 1, wherein, The step of determining that the upgrade information of the first terminal is obtained and that the first partition of the second terminal is in an unoccupied state, and mounting the first partition to the first terminal comprises the following steps: If it is determined that the upgrade information of the first terminal is obtained and that the state value of the first partition in the state partition of the second terminal is a first value, the following steps are performed: The first partition is mounted to the first terminal, and the state value of the first partition in the state partition of the second terminal is set as a second value; The second value is used to indicate that the partition is in an occupied state, and the first value is used to indicate that the partition is in an unoccupied state.

3. The method of claim 2, wherein, After the start-up partition of the first terminal is set as the local partition of the first terminal, the method further comprises the following steps: The state value of the first partition in the state partition of the second terminal is set as the first value.

4. The method of claim 1, wherein, After the file system of the first terminal is written into the first partition, the method further comprises the following steps: The upgrade information of the first terminal is written into the first partition.

5. The method of claim 1, wherein, The first partition of the second terminal is mounted to the first terminal through a network file system.

6. The method according to any one of claims 1 to 5, characterized in that, The step of determining that the first partition of the second terminal is in an unoccupied state comprises the following steps: It is determined that at least one of the at least two backup partitions of the second terminal is in an unoccupied state; the first partition is one of the backup partitions of the second terminal which is in an unoccupied state.

7. A silent upgrade system applied to a first terminal and comprising the following steps: A mounting module is configured to determine that the upgrade information of the first terminal is obtained and that the first partition of the second terminal is in an unoccupied state, and then mount the first partition to the first terminal, wherein the first terminal is in communication connection with the second terminal; the first partition of the second terminal is a backup partition and is used for the in-sight upgrade of each first terminal; A writing module is configured to write the file system of the first terminal into the first partition and set the start-up partition of the first terminal as the first partition; A first terminal upgrade module is configured to determine that the first terminal starts from the first partition, and then upgrade the file system in the local partition of the first terminal according to the upgrade information and set the start-up partition of the first terminal as the local partition of the first terminal.

8. A silent upgrade terminal comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, The processor executes the computer program to implement the steps of the method according to any one of claims 1 to 6.

9. A computer-readable storage medium storing a computer program, the computer program comprising instructions that, when executed by a computer, cause the computer to perform the method of any one of claims 1 to 8. The computer program is executed by the processor to implement the steps of the method according to any one of claims 1 to 6.

Images